2 replies to this topic

[DarkFib3r]

 

The key services the Air Force Office (AFO) offers to the community are as follows:

1. Manage UOAF servers for community use.
2. Promote and moderate flight simulation events.
3. Organize fight simulation participation.
4. Manage training material on the UO wiki.

The AFO accomplishes its objectives through two delegate groups:

1. The Event Fragging Team, who create, promote and coordinate events and pickup flights. These teams are split by geographic location.
2. The Instructor Pilots, who develop and host training sessions to improve the quality of our members.

Oversight, direction, guidance, and responsibility falls on the AFO officers: Gusy, DarkFib3r. Responsibilities include ensuring continuity of weekly flight simulation events, assisting with mission fragging and training as required, and ensuring the wiki is maintained. AFO officers also ensure participant conduct is in compliance with the UO Charter and relevant Community SOPs.

 

The AFO has a governance group known as the Fellowship of the Wing, which provides guidance for the future of the UOAF. Furthermore, new roster members will be ultimately approved by this group. This group includes the AFO officers, Krause, and Force_Majeure.

 

The backbone of UOAF is its roster members. These players represent the core values of UOAF and act as role models for our guest. They are expected to be flight commander capable, possess a high degree of competence in flight simulation, and maintain a good reputation and behavior.

 

Event fragging teams

 

Instructor pilots

 

UOAF roster members

• Krause
• Force_Majeure
• Fluffer 
• Ghostdog 
• DarkFib3r 
• Domestos 
• Hellhound 
• Briland 
• Neuro 
• Brainling 
• Gusy 
• Bawki 
• Flukey 
• Lexi 
• Scope 
• Gasman 
• Foxy 
• Nebojsa 
• CenterMass 
• Nighthawk
• Beatty

UOAF SOPs

Edited by Gusy, 2017-08-28 @ 19:46.
Grammar corrections - Present tense.

[DarkFib3r]

 

 

The Event Fragging Teams will create, promote and coordinate flight simulation events and pickups at United Operations. Fragging team members must be UOAF roster members. The two teams are split by geographic location.

 

Frag Team NORAD - North American Fragging Team

• Gusy
• DarkFib3r
• Brainling

Frag Team Eurocorps - European Fragging Team 

• Nebosja
• Neuro
• Domestos

Frag Team members responsibilities:

 

1.) Event Management

    a.) Management and Moderation of Weekly Pickup Flights and Official Events.

    b.) Frag weekly missions for events for a contiguous, long-running campaign.

    c.) Document and Post events to the Forums.

2.) Communicate any server issues to AFO and GSO.

 

AFO officers will be responsible for pinning the event posts, creating RSVP event calendar, and adding a front page article of the event as required.

Edited by Gusy, 2017-08-28 @ 19:44.

[Gusy]

UOAF Standard Operation Procedures(SOPs)

 

1.0 Gameplay SOPs

1.1 The chain of command will be respected and enforced at all times. Leadership consists of a Package Commander, a Flight Leader, and an Element Leader.

1.2 Under no circumstance will pilots be able to edit their load outs, it is lead's (#1) or element lead's (#3)'s decision to do so and theirs only.

1.3 Under no circumstance will pilots except Lead(#1) or the Package Commander change steer points in the 2D planner.

1.4 Under no circumstance will pilots edit or move ground troops without notifying or consulting a second party of their action.

1.5 Comms integrity will be maintained at all times and without exception.

1.6 Discipline will be maintained in the air and without exception.

1.7 Wingmen will follow their leads' orders and aircraft at all times and will respond to all directives appropriately. Failure to do so will result in a kick or ban from the community. Countermanding orders will lead to decisive disciplinary action.

1.8 Flights will function within their assigned roles and flight plans as part of the package at all times and without exception.

 

2.0 UOAF Event SOPs

2.1 UOAF events are open to all members of the UO community who consider themselves ready. UOAF’s most frequent event type is for BMS, though occasionally DCS events are organized.

2.2 Members of the UO community that wish to attend a UOAF event must RSVP on the event’s calendar post.

2.3 RSVP priority will be as follows; Roster members, UO Regulars, UO Donors, Old Guest, New Guest.

2.4 Players will show up on time with all hardware and installations ready to go.

2.5 Players will indicate unforeseen tardiness or absence in the event thread on the forum.

2.6 New Players flying their first Event will be required to have flown on a pickup flight with a player that has flown past events. This SOP can be overridden at Event Moderator's discretion.

2.7 Event Moderator's are UOAF Frag Team members that ensure events run smoothly.

2.8 All players will follow the directions of the Event Moderator/s.

 

3.0 UOAF Pickup SOPs

3.1 Players are welcome to create and run pickup flights outside of main events.

3.2 Players can join or create a pickup flight by asking in discord, teamspeak, or the forums.

3.3 Players are expected to follow flight standards laid out in 1.0 Gameplay SOPs.

 

4.0 UOAF Roster SOPs

4.1 Roster members are expected to be flight commander capable, possess a high degree of competence in flight simulation, and maintain a good reputation and behavior.

4.2 Roster members are governed by the Fellowship of the Wing, current and former leaders of the UOAF.

4.3 Roster members are expected to take flight leader and element leader positions during flights.

4.4 Roster members are to discuss changes and report player behavior using discord UOAF-Private channel.

Edited by Gusy, 2017-06-21 @ 18:39.