Difference between revisions of "Fragteam"
Jump to navigation
Jump to search
(*everything*) |
|||
| Line 3: | Line 3: | ||
<br /> | <br /> | ||
| − | == | + | ==Current members== |
{| class="wikitable" | {| class="wikitable" | ||
!BMS | !BMS | ||
| Line 52: | Line 52: | ||
|} | |} | ||
| − | == | + | ==Role and responsibilities== |
The UOAF fragteam is a group of players, not necessarily Roster members, responsible for the creation and publication of the weekly BMS events. They also maintain documentation relative to best fragging practices, checklists, and other procedure necessary to maintain the quality of the generated events. | The UOAF fragteam is a group of players, not necessarily Roster members, responsible for the creation and publication of the weekly BMS events. They also maintain documentation relative to best fragging practices, checklists, and other procedure necessary to maintain the quality of the generated events. | ||
<br /> | <br /> | ||
| − | === Joining the fragteam === | + | ==='''Joining the fragteam'''=== |
Anyone can apply to be part of the fragteam; current members of the team assess the request, if necessary arrange training/instruction to ensure the applicant can frag events independently and with the required quality standard. This is not supposed to be a heavy, technical process, but simply a way to ensure quality. | Anyone can apply to be part of the fragteam; current members of the team assess the request, if necessary arrange training/instruction to ensure the applicant can frag events independently and with the required quality standard. This is not supposed to be a heavy, technical process, but simply a way to ensure quality. | ||
<br /> | <br /> | ||
| − | === Competences === | + | ===Competences=== |
Players intending to create missions/events at UOAF should: | Players intending to create missions/events at UOAF should: | ||
| − | * Be experts at using the mission editor and generating missions that are technically sound (meaning among other items, that waypoints, timings, takeoff order, server flight, etc are taken care of to minimize delays and headaches on game day) | + | *Be experts at using the mission editor and generating missions that are technically sound (meaning among other items, that waypoints, timings, takeoff order, server flight, etc are taken care of to minimize delays and headaches on game day) |
| − | * Be knowledgeable in the various missions, munitions, profiles, and airframes | + | *Be knowledgeable in the various missions, munitions, profiles, and airframes |
| − | * Constantly review the process and document best practices and The Fragging Checklist | + | *Constantly review the process and document best practices and The Fragging Checklist |
| − | * Be able to independently assemble products for briefing and planning (including maps, comms plans - as “standardized”) | + | *Be able to independently assemble products for briefing and planning (including maps, comms plans - as “standardized”) |
| − | * Try to spread the workload in the best way to avoid burnout | + | *Try to spread the workload in the best way to avoid burnout |
| − | * Be capable of getting people up to speed on all of the above to expand the squadron’s fragging manpower (depending on how we decide to arrange things, this can be a requirement for fragging official events) | + | *Be capable of getting people up to speed on all of the above to expand the squadron’s fragging manpower (depending on how we decide to arrange things, this can be a requirement for fragging official events) |
<br /> | <br /> | ||
| − | == | + | ==Fragging workflow== |
| − | * During planning meetings, some time is set aside to discuss the two upcoming events, allocating as many people as possible to the two events (coordinator, package lead, server host/backup, and a fragger) | + | *During planning meetings, some time is set aside to discuss the two upcoming events, allocating as many people as possible to the two events (coordinator, package lead, server host/backup, and a fragger) |
| − | * The overall situation in the campaign should be addressed briefly to give some background and input to the fragging process | + | *The overall situation in the campaign should be addressed briefly to give some background and input to the fragging process |
| − | * After the meeting, the event coordinator ensures work proceeds on the event, and is responsible for finding replacements for key figures if need be | + | *After the meeting, the event coordinator ensures work proceeds on the event, and is responsible for finding replacements for key figures if need be |
| − | * The fragger and package lead can collaborate to hatch and refine a plan | + | *The fragger and package lead can collaborate to hatch and refine a plan |
| − | * The fragger creates the mission and products according to sop/other resources established by the frag team, and finally posts event to discord (format TBD) | + | *The fragger creates the mission and products according to sop/other resources established by the frag team, and finally posts event to discord (format TBD) |
| − | * This can be done individually or as a team effort (group fragging is encouraged for less experienced people) | + | *This can be done individually or as a team effort (group fragging is encouraged for less experienced people) |
| − | * The frag can also be double checked by other fraggers, spontaneously or on request of the fragger | + | *The frag can also be double checked by other fraggers, spontaneously or on request of the fragger |
| − | * Players RSVP indicating preferred slot, and are expected to read and process the briefing, in order to expedite briefing | + | *Players RSVP indicating preferred slot, and are expected to read and process the briefing, in order to expedite briefing |
| − | * On game night, Package commander should be already aware of the tactical situation, possibly having planned with fragger ahead of time; package brief is kept to a minimum and flight briefs/question time can take most of the briefing time | + | *On game night, Package commander should be already aware of the tactical situation, possibly having planned with fragger ahead of time; package brief is kept to a minimum and flight briefs/question time can take most of the briefing time |
| − | * Mission is played, everyone has a good time | + | *Mission is played, everyone has a good time |
| − | * Debriefing of event, feedback to fragger/pl/fl; keep track of issues and over time propose changes to fragging SOPs if necessary | + | *Debriefing of event, feedback to fragger/pl/fl; keep track of issues and over time propose changes to fragging SOPs if necessary |
<br /> | <br /> | ||
| − | == | + | ==Fragging checklist== |
| − | * Does each steerpoint for each flight have a cruise air speed > 300 knots? | + | *Does each steerpoint for each flight have a cruise air speed > 300 knots? |
| − | * Will the SEAD and/or escort be in front of the strikers in time to deal with threats? | + | *Will the SEAD and/or escort be in front of the strikers in time to deal with threats? |
| − | * Is there at least 1 minute between each take off time? | + | *Is there at least 1 minute between each take off time? |
| − | * Does the escort and SEAD have enough time to work their steer points before strikers arrive? | + | *Does the escort and SEAD have enough time to work their steer points before strikers arrive? |
| − | * Is there at least 1 minute between each flight TOT on a co-located target? | + | *Is there at least 1 minute between each flight TOT on a co-located target? |
| − | * Are all the flight plan steer points either deconflicted by time on steer or space? | + | *Are all the flight plan steer points either deconflicted by time on steer or space? |
| − | * Does every flight have an abort airfield that is safe and close to the FLOT? | + | *Does every flight have an abort airfield that is safe and close to the FLOT? |
| − | * Are navigation steerpoints separated by a minimum of 20-30nm (Med Alt Only) + logical? | + | *Are navigation steerpoints separated by a minimum of 20-30nm (Med Alt Only) + logical? |
| − | * Does the package have the means (weapons, terrain) to deal with every threat within range of the flight plan? | + | *Does the package have the means (weapons, terrain) to deal with every threat within range of the flight plan? |
| − | * Is there an AWACS fragged? | + | *Is there an AWACS fragged? |
| − | * Is the server flight fragged in a location to maximize the server's FPS performance? | + | *Is the server flight fragged in a location to maximize the server's FPS performance? |
<br /> | <br /> | ||
| − | == | + | ==To do:== |
A few items have to be clarified for SOP inclusion: | A few items have to be clarified for SOP inclusion: | ||
| − | * Weather: dynamic or not, i didn’t completely follow the discussion but i saw there are issues with jolts when the map changes | + | *Weather: dynamic or not, i didn’t completely follow the discussion but i saw there are issues with jolts when the map changes |
| − | * Exact server flight procedures (mostly for timing, does it have to go in to ramp? when?) | + | *Exact server flight procedures (mostly for timing, does it have to go in to ramp? when?) |
| − | * Tools to use for products (WDP? Comms card? VMT?) | + | *Tools to use for products (WDP? Comms card? VMT?) |
| − | * Discord format | + | *Discord format |
| − | * Editing REDFOR: yay or nay? | + | *Editing REDFOR: yay or nay? |
[[Category:SOPs]] | [[Category:SOPs]] | ||
__FORCETOC__ | __FORCETOC__ | ||
Revision as of 09:57, 27 July 2019
This page contains the description, role and responsibilities, SOPs and process documentation for the UOAF fragteam.
Contents
Current members
| BMS | DCS |
|---|---|
| Bibleclinger
DarkFib3r Domestos DrSlaughterRex Foxy Fumes GasMan Gusy Krause Nighthawk Oirien Wh1t3b0Y |
Abelian
Darkfiber Domestos DrSlaughterRex Eagle HellHound Krause Nighthawk Oirien Woody
|
Role and responsibilities
The UOAF fragteam is a group of players, not necessarily Roster members, responsible for the creation and publication of the weekly BMS events. They also maintain documentation relative to best fragging practices, checklists, and other procedure necessary to maintain the quality of the generated events.
Joining the fragteam
Anyone can apply to be part of the fragteam; current members of the team assess the request, if necessary arrange training/instruction to ensure the applicant can frag events independently and with the required quality standard. This is not supposed to be a heavy, technical process, but simply a way to ensure quality.
Competences
Players intending to create missions/events at UOAF should:
- Be experts at using the mission editor and generating missions that are technically sound (meaning among other items, that waypoints, timings, takeoff order, server flight, etc are taken care of to minimize delays and headaches on game day)
- Be knowledgeable in the various missions, munitions, profiles, and airframes
- Constantly review the process and document best practices and The Fragging Checklist
- Be able to independently assemble products for briefing and planning (including maps, comms plans - as “standardized”)
- Try to spread the workload in the best way to avoid burnout
- Be capable of getting people up to speed on all of the above to expand the squadron’s fragging manpower (depending on how we decide to arrange things, this can be a requirement for fragging official events)
Fragging workflow
- During planning meetings, some time is set aside to discuss the two upcoming events, allocating as many people as possible to the two events (coordinator, package lead, server host/backup, and a fragger)
- The overall situation in the campaign should be addressed briefly to give some background and input to the fragging process
- After the meeting, the event coordinator ensures work proceeds on the event, and is responsible for finding replacements for key figures if need be
- The fragger and package lead can collaborate to hatch and refine a plan
- The fragger creates the mission and products according to sop/other resources established by the frag team, and finally posts event to discord (format TBD)
- This can be done individually or as a team effort (group fragging is encouraged for less experienced people)
- The frag can also be double checked by other fraggers, spontaneously or on request of the fragger
- Players RSVP indicating preferred slot, and are expected to read and process the briefing, in order to expedite briefing
- On game night, Package commander should be already aware of the tactical situation, possibly having planned with fragger ahead of time; package brief is kept to a minimum and flight briefs/question time can take most of the briefing time
- Mission is played, everyone has a good time
- Debriefing of event, feedback to fragger/pl/fl; keep track of issues and over time propose changes to fragging SOPs if necessary
Fragging checklist
- Does each steerpoint for each flight have a cruise air speed > 300 knots?
- Will the SEAD and/or escort be in front of the strikers in time to deal with threats?
- Is there at least 1 minute between each take off time?
- Does the escort and SEAD have enough time to work their steer points before strikers arrive?
- Is there at least 1 minute between each flight TOT on a co-located target?
- Are all the flight plan steer points either deconflicted by time on steer or space?
- Does every flight have an abort airfield that is safe and close to the FLOT?
- Are navigation steerpoints separated by a minimum of 20-30nm (Med Alt Only) + logical?
- Does the package have the means (weapons, terrain) to deal with every threat within range of the flight plan?
- Is there an AWACS fragged?
- Is the server flight fragged in a location to maximize the server's FPS performance?
To do:
A few items have to be clarified for SOP inclusion:
- Weather: dynamic or not, i didn’t completely follow the discussion but i saw there are issues with jolts when the map changes
- Exact server flight procedures (mostly for timing, does it have to go in to ramp? when?)
- Tools to use for products (WDP? Comms card? VMT?)
- Discord format
- Editing REDFOR: yay or nay?
