Mission Command

From UFStarfleet Wiki

Jump to: navigation, search
350px.
Branch/Division motto/slogan.
Mission Command
General Data
*Branch: Command
*Division: Office of the Chief UF Starfleet Operations
*Fleet Affiliation: Starfleet
*Founded: 2385
*Status: Active
*Location: Pinastri Sector, Delta Quadrant
*Homebase: UF Starfleet Command Headquarters
Department Staff
*Department Head: Kermie Mistwallow
*Vice Department Head: Zania Turner
*Vice Department Head: Leo Ravenheart
*Yeoman: n/a


General

Mission Command is unique, as it's not a normal branch, division, or department within the UFS, so you won't be able to find an area for Mission Command on the forums. It is an out-of-character (OOC) support group, founded by Admiral Calhoun and being rebooted by the Joint Chiefs after input sessions on how to improve the state of roleplaying within the region. Anyone can be part of Mission Command, irregardless of their branch, division, department, ship or station.

Headquarters Staff

United Federation Starfleet Mission Command
Mission Strategist CO R-a1.png Kermie Mistwallow
Mission Strategist XO R-a1.png Zania Turner
Mission Strategist SO R-o4.png Leo Ravenheart
Mission Strategist R-blank.png Vacant
Mission Strategist R-blank.png Vacant
Mission Strategist R-blank.png Vacant

How Does Mission Command Work?

Mission Command has a very big responsibility within United Federation Starfleet. Following the direction of the Chief of UF Starfleet Operations, this group supports and supplements roleplay within the UFS.

The support provided by Mission Command is at the discretion of the Chief of UF Starfleet Operations, however it can include but is not limited to the following:

1) Brainstorming for region-wide RPs,

2) Assisting CO's, XO's & BH's who request ideas for future RPs

3) Assisting the Chief of UF Starfleet Operations with running an ongoing region-wide RP

4) Initiating smaller region-wide RPs that support the current ongoing RP

5) Reaching out to members to help increase participation in the RP

6) Providing props or special effects as needed

7) Serving as NPCs during various storylines to substitute for or supplement an external group’s participation

Communication is essential. To help keep as many people as possible informed as to what's going on, we hold regular meetings once per week for anyone who can attend. These meetings are open, so anyone - even those who are not part of Mission Command - can still attend and participate.

What Positions are Available

Although there are no billets, there are several roles within Mission Command where one can help out to get involved:

1) Mission Writers - This position is available for creating various missions and submitting it to the Chief of UF Starfleet Operations for consideration for region-wide RPs (major and minor), including ones that may involve other groups (i.e. Orion’s Swords, etc). Mission writers can also assist ship/station COs if they request ideas for their own RPs.

2) Mission Advisors - This position works closely with the Chief of UF Starfleet Operations on the continued implementation of region-wide RPs. They can initiate minor region-wide RPs that are related to the major ongoing storyline.

3) Mission Specialist - These Mission Command members are permitted to help man Nimbus during region-wide RP activity, providing support in the areas where needed (depending on their branch, i.e. Medical, Science, Security, etc). They insert themselves into the situation, and can help to encourage others to participate in the missions.

4) Special Effects - These individuals will use their inventories to provide props and other special effects as needed for region-wide RPs, or for ship/station RPs as needed. This can include, but is not limited to weather effects, tidal waves, traps, and other items used to help bring realism to the storyline.

5) Mission Support - Although it’s preferred to invite other groups to participate with the missions we have planned, this position can help to provide the equivalent of NPC characters for various RPs. It is recommended that these individuals have a variety of avatars that they can use for different appearances, as necessary, to play out the roles that they are asked to fill.

Unlike with a branch, division, or department, there are no roll calls within Mission Command, and all duties are performed by volunteers. Volunteers can take on any number of positions within Mission Command. And, very true to the art of roleplaying itself, new positions can be created to provide necessary support as the group and needs evolve. It is the fulfillment of the duties, by volunteers, which really makes things work.

Things to Consider

A) RUNNING A MISSION - One common misconception is that Mission Command actively runs the missions that they create. 99.9% of the time, this is not true. When a mission is created by Mission Command, it is given to Chief of UF Starfleet Operations, who will put it into motion from Nimbus Station (Command HQ) by starting to call for reports over the comms.

Mission Command will serve as an advisor, passively monitoring the progress and participation in the mission, and working behind the scenes to develop significant changes, events and twists that will keep the mission fresh, exciting, and going for a while. If a CO takes the lead with trying to determine a resolution, these adjustments are usually conveyed via IMs or via an ACTION statement which everyone can see.

Only in EXTREMELY rare occasions, when nobody is available from Nimbus to run the mission, someone from Mission Command can actively take a role with running it. Members of Mission Command could, with permission of the station/facility COs, assist with manning the Operations Centers for those facilities if they are short handed. Even in those instances, their role will be extremely minimal.

B) LOCATION - Mission Command is responsible for creating missions for the entire region - for all of Sector001 and 002. This provides our focus, but also a challenge to try and incorporate all locations within the region.

Those who create missions should keep in mind that things should not be restricted to just one facility, and what takes place on there. Our goal is to create missions that incorporate everything within Sector001 and 002, when at all possible, including but not limited to Tranquility Station, Pathfinder Research Facility, Alexandria Station and the rest of the colony/planet.

Starting a mission at another location is okay (i.e. with the help of an external facility, or a ship); however, the main bulk of the mission should take place within Sector001 & 002.

C) MISSION VARIETY - Another challenge faced by Mission Command is to create a variety of missions. One pitfall is to have too many missions that tend to focus on just one area, like combat. It is very easy to become complacent, and just focus on a certain type of mission; however, this will usually result in a drop in participation.

The decline is often attributed to getting "bored" of the same thing every single time, or other factors attributed to Second Life (i.e. lag) which can have a significant impact on the ability to conduct regular business within the region.

A variety of missions should be created and implemented by the members of Mission Command. If one is mainly known for creating science-focused missions, a challenge would be for them to create a combat-related mission, or something that can give medical, engineering, or another area their chance to shine in the spotlight.

D) GIVE EVERYONE SOMETHING TO DO - Another important aspect of creating a mission for the entire region is to try and give everyone something to do. This is a major challenge, since we can't guarantee participation for all of the branches/divisions/departments we try to include in our efforts.

This also includes civilians and cadets, who should be given a role as well and not just relegated or herded into Alexandria or the Welcome Center for their "safety."

If there is a particular mission where you want to maximize the involvement/participation from a particular branch/division/department, it's best to contact them in advance

When creating a mission, it is important to give everyone something to do. This should be automatic, whenever a member of Mission Command creates a mission. It's not necessary to consult with the Branches/Divisions/Departments before doing so, unless maximizing their involvement is required.

E) COORDINATION - Coordination between other members of Mission Command can be very helpful when it comes to trying to improve and enhance the overall quality of our missions. Additionally, it not only allows us to prevent similar missions being run back-to-back, but also the possibility of having missions that stretch over the course of several days.

F) INVOLVING SHIPS/OTHER FACILITIES - Other ships and/or facilities are more than welcome to participate in the region-wide missions. Joining in occasionally on missions may help to create more realism, excitement, and enhance interaction between everyone within the region and the crews involved.

Although a member of Mission Command may come up with a mission, they should not involve the other ships without first seeking permission from the appropriate COs/XOs. It is simple common courtesy. The stations/facilities located in Sector 001 and 002 are the exceptions to this, since it would be hard for them to not participate in the events taking place.

Other ship/facility COs/XOs are also welcome to contact Mission Command (or join it) and willingly offer the involvement of their ship/facility for a region-wide mission. They are also just as welcome to create region-wide missions, which could be played out in Sector001 and 002, which would involve their crews.

G) CONTINUITY - One element to consider is continuity. Damage probably will inevitably happen on board a ship or station. Because we're in the Delta Quadrant, we don't have the resources like we would if we were in the Alpha or Beta Quadrants. There isn't a Starbase just around the corner, where one can stop off for repairs, so it'll likely take a bit longer.

It is important to keep in mind any existing damage to the ship/station and it's systems when going about your duties during a mission. If you are creating a mission, and you aren't sure about the damage that might be present, contact the CO/XO of that ship/station.

Database