Bravo Fleet
Difference between pages "Melissa Vane" and "OCS Policy"

Difference between pages "Melissa Vane" and "OCS Policy"

From Bravo Fleet
(Difference between pages)
m
 
 
Line 1: Line 1:
{{Character
{{icons|bfo}}
| name =Melissa Vane
The Office of the Chief of Staff (OCS) is the administrative arm of Bravo Fleet responsible for a wide variety of logistical activities in the fleet including awards, promotions, competitions, transfers, name changes, and overall management of the Bravo Fleet roster. The Office of the Chief of Staff is responsible for the timely execution of these duties as the primary facilitator of many facets of the fleet. Below you will find the key policies that the office operates through, with more detailed policies linked throughout. Any questions regarding these policies should be directed at the current Chief of Staff.
| fullname =Melissa Renée Vane
| image =[[File:MelissaVane.jpg]]
| species =Human
| gender =Female
| dateofbirth =25 September 2339
| age =60
| placeoforigin =Luna, Sol System
| posting =[[Starbase 72]]
| position = Head of Shipyard Operations
| rank =Commander
| affiliation =Starfleet
}}
'''Commander Vane''' is the Head of Shipyard Operations aboard [[Starbase 72]], with responsibility for the construction of new starships and any repairs or refits conducted on visiting starships. She's had a long career as a member of the [[Ma:Starfleet Corps of Engineers|Starfleet Corps of Engineers]] and is considered an expert in starship technology. Often short-tempered, she tends to experience friction when starship commanders attempt to dictate to her how she should conduct repairs and refits, as she considers the starship to be hers once it's in the yard.


== History ==
= Policy =
== Section 1 - Awards & Promotions ==
* All promotion and award recommendations should be submitted through BFMS and include clear, concise language about what the member did and, if applicable, how they did it. Recommendations can include information about a person's personality and character, but should provide factual information on the things that they have done.
* All medals and promotions should be known and directed through (up and down) the chain of command appropriately so each leader knows what is being requested and can avoid instances of denial due to double dipping, or an award being recommended for the same thing within a short period.
* All awards and promotions should come directly from the source of which they’re being awarded. For instance, a merit award for work in the Lore Office should come from the Loremaster. A merit award for general activity activity should come from TF staff. If there is a grouping from different sources to complete an award or promotion recommendation, then there should be only one primary recommendation (usually from the TF staff) and as many supplemental recommendations as needed. If you think you may want to group up activities in different areas of Bravo Fleet for an award or promotion, ‘’reach out’’ to other leaders to have them add in!
* Awards and promotions, once granted, can only be revoked by the Magistrate’s Office. This does not apply to obvious administrative or technical errors, which can be administratively (rather than judicially) removed by the Office of the Chief of Staff.
* When in doubt, ask.


=== Early Life (2339-2357) ===
=== Awards ===
Melissa Vane was born in the Lunar Colonies in 2339, where she was constantly surrounded by technology. Because everyday life on Luna required artificial gravity, life support, and all sorts of other systems, it was par for the course for colonists there to learn how to repair their own technology themselves, and Vane was no exception. By high school, Vane was a better technician than many people would be after twenty years of experience.
* Awards are split into two categories: merit and activity.
** Activity awards (ribbons) are given out, usually within their respective departments, for completing activities within Bravo Fleet.
** Merit awards are awards that recognize a member’s overall activity and contribution to the fleet and are typically given for the accumulation of activities either through activity ribbons, project work, leadership, or any other metric that can be tangibly tracked. Merit awards are further broken down into two categories:
*** Recognition Awards (Tier 1) — typically awarded for more standard activity.
*** Distinction Awards (Tier 2) — typically awarded for levels of activity and work for the fleet that go above and beyond.
* Awards cannot double dip activity within their respective category. Any activity, once recognized by an award, cannot be used toward future medals. For activity ribbons this is self explanatory in that once an activity is awarded for, it cannot be awarded again. For merit awards this is more prone to happening if a person writing a rec doesn’t read through previous merit awards to see what has already been awarded for. This, however, does not always apply to promotions, which tend to be focused on the total of accomplishments since a member’s last promotion. There has been confusion around these subjects, so example situations are listed below to provide further clarification:
**A member receives a Silver Palm for participation in a large-scale Task Force event. Four months later, that same member is recommended for a Star Cross for activity in the intervening period, as well as the participation in the large-scale Task Force event. That Star Cross will be rejected.
**Continuing from the above, if that member is instead recommended for a promotion (and assuming all guidelines and requirements are met), that would be acceptable.
**If a member is promoted appropriately (assuming all guidelines and requirements are met) for work only internal to their Task Force, and then is recommended for a recognition award for the completion of several projects for a Department — that award is appropriate.
**If a Task Force Commanding Officer is promoted for their long-term work for their task force to an admiralty rank, and then is recommended for a recognition award for work internal to the task force one month later, that medal will be rejected.
* All awards have a minimum position requirement for the nominator, but that isn’t the only award they can nominate for. For instance, the Star Cross must be nominated by at least a TFCO, but anyone above a TFCO can also nominate someone for it. Alternatively, if you are below TFCO and want to nominate someone for a Star Cross, talk to your TFCO!


=== Starfleet Academy (2357-2361) ===
=== Promotions ===
After acing the entrance examination, Vane entered Starfleet Academy in 2357 knowing exactly what she wanted to do: become a starship engineer. Her laser-like focus on this goal was noted by several professors, and she earned a number of awards in her first two years that led her to be assigned to Gold Squadron, the elite training unit for cadets intending to become engineers and operations officers.
* Unlike awards, promotions are more a sum of the actions of a member since their last promotion. A promotion should include all of their activity, awards, and projects they’ve completed and this activity should be reasonably recent.
* Once promoted, all activity in the previous rank is “consumed” and cannot be used again for any promotion or medal. This, however, does not necessarily apply for department work or projects that may be long term and overlap through promotions as long as that work is not mentioned and used in a previous promotion.
* Promotions between ranks have time-in-rank requirements. These requirements are not absolute, and there may be extreme circumstances where it may be waived in the case of senior officer promotions, but this is highly unlikely, and the standard(s) of activity are significantly higher for rapid promotions.


=== USS ''Galaxy'' (2361-2370) ===
== Section 2 - Transfers ==
Vane’s first posting after Starfleet Academy was to the USS ''Galaxy'' herself, the prototype of the legendary class of explorers. She started out as a Warp Propulsion specialist, before gradually working up the ranks to Assistant Chief Engineer at the end of her nine-year stint aboard the ship.
* Transfer requests are not a forum for argument or discussion. Problems with unit superiors should be addressed directly between the relevant members.
* Transfers between task forces may be held until such time that the OCS is satisfied with the reasons for the transfer.
* The direct recruitment of members from one unit to another with promises of medals, promotions, or other entitlements is forbidden and may result in disciplinary action. This does not include application periods for positions open to all of Bravo Fleet.
* Reserve hopping, wherein a member transfers to Reserve status before transferring to a new task force, is forbidden and may result in disciplinary action when discovered.
* Members accepting leadership positions in units to which they do not currently belong should first request a transfer to the appropriate unit with confirmation of the appointment given as reason.


=== USS ''Challenger'' (2370-2378) ===
== Section 3 - Competitions ==
In 2370, Vane transferred to the ''Galaxy''‘s sister ship: the ''Challenger'' as Chief Engineering Officer at the rank of commander. The ''Challenger'' was a few years newer than the ''Galaxy'' and many of her systems incorporated lessons learned in the construction of the prototype. Still, keeping a ''Galaxy-''class ship running was a monumental task that Vane relished. The ''Challenger'' embarked on a long-range exploratory mission in the Beta Quadrant, but it was pulled back to Federation space when the Dominion War broke out, serving in the core of Starfleet’s main battle fleets, which kept Vane busy with constant repairs and upgrades. Following the war, the ''Challenger'' once again returned to exploratory missions, and Vane continued to serve aboard the ship until it put back to port in 2378 for its first major refit.
* To avoid timing conflicts, members wishing to organize a competition must get approval from their unit leaders. All competitions must be approved by the OCS staff through administration on BFMS.
* All competitions must have clearly defined guidelines on how they will be judged.
* Competitions in Bravo Fleet are tiered based on their target audience, with the placement awards shifting in each situation. These are:
** Bravo Fleet-wide Fleet Action Events:
*** Starfleet Gold Star
*** Starfleet Silver Star
*** Starfleet Bronze Star
** Bravo Fleet-wide:
*** First Place: Action Medal with Galaxy Cluster
*** Second Place: Action Medal with Star Cluster
*** Third Place: Action Medal with Planet Cluster
** Task Force-wide:
*** First Place: Action Medal with Star Cluster
*** Second Place: Action Medal with Planet Cluster
*** Third Place: Action Medal with Moon Cluster
** Task Group-wide:
*** First Place: Action Medal with Planet Cluster
*** Second Place: Action Medal with Moon Cluster
*** Third Place: Action Medal with Comet Cluster
* A Fleet Action is a club-wide event consisting of several smaller events in phases. These smaller events fit into an overall storyline impacting multiple facets of Bravo Fleet canon. Fleet Actions are run by the Bravo Fleet Senior Staff at the direction of the BFCO and BFXO, and directly influence the direction of Bravo Fleet canon via the Loremaster.
* All competitions are expected to be judged and closed within (30) days of the end date. Competitions still open after this time will result in a warning email to the organizers.
** After 45 days, the OCS will take over judging the competition. At this point, an AWOL competition organizer may have their privileges to run competitions suspended by the OCS office.
* Competitions with valid participation are expected to place action medals accordingly, but there are always situations where no submission has met the subjective criteria for placement. Should this situation arise, the OCS must be notified of the situation and provided with the competition runner’s reasoning.
** Subjectively graded competitions (including but not limited to: fiction, graphics, poetry, caption contests, and other forms of creative activities) should not have ties when finalized, as there is always a method of discerning appropriate placements.
** Any competition that is likely to end in multiple ties should have clearly defined guidelines of how ties will be delineated so that there will only be one first, second, and third place finisher.
* Competition organizers and co-organizers are ineligible for placement in their competitions.


=== Corps of Engineers (2378-2381) ===
== Section 4 - Names & Usernames ==
While she had wanted to lead the refit herself, Vane was tapped to head a team within the Starfleet Corps of Engineers that was devoted to evaluating the oldest starships in current service to make recommendations for refits, retirements, or other actions. She is widely seen as being one cause for the final retirement of the ''Miranda''-class, but her team’s recommendations only confirmed what many other engineers had recommended as early as 2350. Her team was also responsible for developing a mid-life refit plan for the ''Ambassador''-class.
* Names of canon Star Trek characters are generally prohibited. If you are unsure if your character's name is in question, contact the OCS to work with you.
* Offensive names — while there is no formal list of names that are considered offensive, the Office of the Chief of Staff reserves the right to review potential or actually offensive names.


=== USS ''Belmopan'' (2381-2390) ===
== Section 5 - Dossier Deletion ==
With plans for the Romulan evacuation going from zero to Warp 9, Vane was posted to the starship ''Belmopan'' in 2381 to handle the construction of new facilities for refugees on worlds near Romulan space. While she was first and foremost a starship engineer, Starfleet needed every engineer it could get contributing to the rescue operations and Utopia Planitia was already working at full tilt with a large contingent of Synth labor, while ground facilities were in short supply. While on the ''Belmopan'', Vane found herself working very closely with the ship’s captain, Leighton Mortcombe. They’d met before; he’d been a year ahead of her at the academy and they’d shared an engineering course, but never interacted much. Both officers had devoted themselves to their career at the expense of personal relationships, but they clicked in a way that surprised Vane; after several years working together the relationship turned romantic, and they married in 2389. Their first child, Tyler, was born the next year.
* Any member who wishes to leave Bravo Fleet in totality may do so by requesting their dossier be deleted by the OCS. Once a dossier is deleted it is done so in full and not retrievable.
* Any awards, promotions, or recognitions that were on a dossier that has been deleted are not transferable to a new dossier created by the same member.


=== USS ''Hathaway'' (2390-2396) ===
== Section 6 - Other ==
Vane and Mortcombe transferred to the USS ''Hathaway'' in 2390, which was a much larger ship, with facilities much better suited to raising a family, which expanded to include Jackson and Madison in 2391 and 2393. While Vane had always considered herself to be a career-focused officer, Vane found herself dreading the time she spent in the engine room away from her children almost as much as she dreaded giving up her career for motherhood. She and Mortcombe balanced their work and family lives as best they could, but with the ''Hathaway'' assigned to charting operations beyond Romulan space, both of them realized that they needed something more stable if they were going to be able to stay in the fleet and raise a family at the same time.
* No ranks, medals, or awards from any other Star Trek club are transferable to Bravo Fleet.


=== Starbase 72 (2396-Present) ===
[[Category:OCS Policy]]
Along with her husband who was assigned as Executive Officer, Vane joined the crew of Starbase 72 in 2396 as the Head of Shipyard Operations, where she would supervise both the construction of new ships and the repair and refit of visiting ships. This assignment suited her, as she had a long history with starship engineering, but it allowed her to spend more time with her family. Vane prefers to take a hands-on approach with this job, and she prides herself on having personally worked on every single starship launched from Starbase 72 under her tenure.
 
=== Service Record ===
{| class="wikitable"
|+
!Date
!Position
!Posting
!Rank
|-
|2357-2358
|Engineering Cadet
|Starfleet Academy
|Cadet Fourth Class
|-
|2358-2359
|Engineering Cadet
|Starfleet Academy
|Cadet Third Class
|-
|2359-2360
|Engineering Cadet
|Starfleet Academy
|Cadet Second Class
|-
|2360-2361
|Engineering Cadet
|Starfleet Academy
|Cadet First Class
|-
|2361-2363
|Warp Systems Specialist
|USS ''Galaxy''
|Ensign
|-
|2363-2366
|Warp Systems Specialist
|USS ''Galaxy''
|Lieutenant Junior Grade
|-
|2366-2368
|Shift Engineer
|USS ''Galaxy''
|Lieutenant
|-
|2368-2370
|Assistant Chief Engineering Officer
|USS ''Galaxy''
|Lieutenant Commander
|-
|2370-2378
|Chief Engineering Officer
|USS ''Challenger''
|Commander
|-
|2378-2381
|Team Leader, Starship Evaluation Team
|Starfleet Corps of Engineers
|Commander
|-
|2381-2390
|Chief Engineering Officer
|USS ''Belmopan''
|Commander
|-
|2390-2396
|Chief Engineering Officer
|USS ''Hathaway''
|Commander
|-
|2396-Present
|Head of Shipyard Operations
|Starbase 72
|Commander
|}
 
== Commander Vane In-Play ==
 
* As a Task Force 72 NPC, you are free to use Commander Vane in your own fiction writing or if your game (RPG) visits Starbase 72 during a mission. The information here is meant as a guide for folks to use this character consistently across different stories, but feel free to take some liberties with her exact characterization. Her rank, position, gender, species, and other mundane details shouldn’t be changed, though. Also, don’t kill her; that wouldn’t be nice.
* Vane is a brilliant engineer, but she’s a territorial one: if your ship is in her yard, she’s not going to take kindly to interference in her plans for it.
* As the Head of Shipyard Operations, Vane is the person you’d interact with if your ship needed repairs–or if it was under construction at Starbase 72. She’d work with you and your Chief Engineering Officer to assess what needs to be done, and then her teams from the starbase would get to work.
* The shipyard at Starbase 72 doesn’t just make starships: if you needed new shuttles or runabouts for your hanger, you’d requisition them from Commander Vane as well, especially if your ship isn’t equipped to build them on its own.
* Having served on two of the original ''Galaxy''-class ships, Vane has a very long resumé and experience with a broad range of starship types.
* Commander Vane is 1.75 meters tall and of African descent.

Revision as of 22:49, 2 May 2021

This article is official Bravo Fleet Official Policy.









The Office of the Chief of Staff (OCS) is the administrative arm of Bravo Fleet responsible for a wide variety of logistical activities in the fleet including awards, promotions, competitions, transfers, name changes, and overall management of the Bravo Fleet roster. The Office of the Chief of Staff is responsible for the timely execution of these duties as the primary facilitator of many facets of the fleet. Below you will find the key policies that the office operates through, with more detailed policies linked throughout. Any questions regarding these policies should be directed at the current Chief of Staff.

Policy

Section 1 - Awards & Promotions

  • All promotion and award recommendations should be submitted through BFMS and include clear, concise language about what the member did and, if applicable, how they did it. Recommendations can include information about a person's personality and character, but should provide factual information on the things that they have done.
  • All medals and promotions should be known and directed through (up and down) the chain of command appropriately so each leader knows what is being requested and can avoid instances of denial due to double dipping, or an award being recommended for the same thing within a short period.
  • All awards and promotions should come directly from the source of which they’re being awarded. For instance, a merit award for work in the Lore Office should come from the Loremaster. A merit award for general activity activity should come from TF staff. If there is a grouping from different sources to complete an award or promotion recommendation, then there should be only one primary recommendation (usually from the TF staff) and as many supplemental recommendations as needed. If you think you may want to group up activities in different areas of Bravo Fleet for an award or promotion, ‘’reach out’’ to other leaders to have them add in!
  • Awards and promotions, once granted, can only be revoked by the Magistrate’s Office. This does not apply to obvious administrative or technical errors, which can be administratively (rather than judicially) removed by the Office of the Chief of Staff.
  • When in doubt, ask.

Awards

  • Awards are split into two categories: merit and activity.
    • Activity awards (ribbons) are given out, usually within their respective departments, for completing activities within Bravo Fleet.
    • Merit awards are awards that recognize a member’s overall activity and contribution to the fleet and are typically given for the accumulation of activities either through activity ribbons, project work, leadership, or any other metric that can be tangibly tracked. Merit awards are further broken down into two categories:
      • Recognition Awards (Tier 1) — typically awarded for more standard activity.
      • Distinction Awards (Tier 2) — typically awarded for levels of activity and work for the fleet that go above and beyond.
  • Awards cannot double dip activity within their respective category. Any activity, once recognized by an award, cannot be used toward future medals. For activity ribbons this is self explanatory in that once an activity is awarded for, it cannot be awarded again. For merit awards this is more prone to happening if a person writing a rec doesn’t read through previous merit awards to see what has already been awarded for. This, however, does not always apply to promotions, which tend to be focused on the total of accomplishments since a member’s last promotion. There has been confusion around these subjects, so example situations are listed below to provide further clarification:
    • A member receives a Silver Palm for participation in a large-scale Task Force event. Four months later, that same member is recommended for a Star Cross for activity in the intervening period, as well as the participation in the large-scale Task Force event. That Star Cross will be rejected.
    • Continuing from the above, if that member is instead recommended for a promotion (and assuming all guidelines and requirements are met), that would be acceptable.
    • If a member is promoted appropriately (assuming all guidelines and requirements are met) for work only internal to their Task Force, and then is recommended for a recognition award for the completion of several projects for a Department — that award is appropriate.
    • If a Task Force Commanding Officer is promoted for their long-term work for their task force to an admiralty rank, and then is recommended for a recognition award for work internal to the task force one month later, that medal will be rejected.
  • All awards have a minimum position requirement for the nominator, but that isn’t the only award they can nominate for. For instance, the Star Cross must be nominated by at least a TFCO, but anyone above a TFCO can also nominate someone for it. Alternatively, if you are below TFCO and want to nominate someone for a Star Cross, talk to your TFCO!

Promotions

  • Unlike awards, promotions are more a sum of the actions of a member since their last promotion. A promotion should include all of their activity, awards, and projects they’ve completed and this activity should be reasonably recent.
  • Once promoted, all activity in the previous rank is “consumed” and cannot be used again for any promotion or medal. This, however, does not necessarily apply for department work or projects that may be long term and overlap through promotions as long as that work is not mentioned and used in a previous promotion.
  • Promotions between ranks have time-in-rank requirements. These requirements are not absolute, and there may be extreme circumstances where it may be waived in the case of senior officer promotions, but this is highly unlikely, and the standard(s) of activity are significantly higher for rapid promotions.

Section 2 - Transfers

  • Transfer requests are not a forum for argument or discussion. Problems with unit superiors should be addressed directly between the relevant members.
  • Transfers between task forces may be held until such time that the OCS is satisfied with the reasons for the transfer.
  • The direct recruitment of members from one unit to another with promises of medals, promotions, or other entitlements is forbidden and may result in disciplinary action. This does not include application periods for positions open to all of Bravo Fleet.
  • Reserve hopping, wherein a member transfers to Reserve status before transferring to a new task force, is forbidden and may result in disciplinary action when discovered.
  • Members accepting leadership positions in units to which they do not currently belong should first request a transfer to the appropriate unit with confirmation of the appointment given as reason.

Section 3 - Competitions

  • To avoid timing conflicts, members wishing to organize a competition must get approval from their unit leaders. All competitions must be approved by the OCS staff through administration on BFMS.
  • All competitions must have clearly defined guidelines on how they will be judged.
  • Competitions in Bravo Fleet are tiered based on their target audience, with the placement awards shifting in each situation. These are:
    • Bravo Fleet-wide Fleet Action Events:
      • Starfleet Gold Star
      • Starfleet Silver Star
      • Starfleet Bronze Star
    • Bravo Fleet-wide:
      • First Place: Action Medal with Galaxy Cluster
      • Second Place: Action Medal with Star Cluster
      • Third Place: Action Medal with Planet Cluster
    • Task Force-wide:
      • First Place: Action Medal with Star Cluster
      • Second Place: Action Medal with Planet Cluster
      • Third Place: Action Medal with Moon Cluster
    • Task Group-wide:
      • First Place: Action Medal with Planet Cluster
      • Second Place: Action Medal with Moon Cluster
      • Third Place: Action Medal with Comet Cluster
  • A Fleet Action is a club-wide event consisting of several smaller events in phases. These smaller events fit into an overall storyline impacting multiple facets of Bravo Fleet canon. Fleet Actions are run by the Bravo Fleet Senior Staff at the direction of the BFCO and BFXO, and directly influence the direction of Bravo Fleet canon via the Loremaster.
  • All competitions are expected to be judged and closed within (30) days of the end date. Competitions still open after this time will result in a warning email to the organizers.
    • After 45 days, the OCS will take over judging the competition. At this point, an AWOL competition organizer may have their privileges to run competitions suspended by the OCS office.
  • Competitions with valid participation are expected to place action medals accordingly, but there are always situations where no submission has met the subjective criteria for placement. Should this situation arise, the OCS must be notified of the situation and provided with the competition runner’s reasoning.
    • Subjectively graded competitions (including but not limited to: fiction, graphics, poetry, caption contests, and other forms of creative activities) should not have ties when finalized, as there is always a method of discerning appropriate placements.
    • Any competition that is likely to end in multiple ties should have clearly defined guidelines of how ties will be delineated so that there will only be one first, second, and third place finisher.
  • Competition organizers and co-organizers are ineligible for placement in their competitions.

Section 4 - Names & Usernames

  • Names of canon Star Trek characters are generally prohibited. If you are unsure if your character's name is in question, contact the OCS to work with you.
  • Offensive names — while there is no formal list of names that are considered offensive, the Office of the Chief of Staff reserves the right to review potential or actually offensive names.

Section 5 - Dossier Deletion

  • Any member who wishes to leave Bravo Fleet in totality may do so by requesting their dossier be deleted by the OCS. Once a dossier is deleted it is done so in full and not retrievable.
  • Any awards, promotions, or recognitions that were on a dossier that has been deleted are not transferable to a new dossier created by the same member.

Section 6 - Other

  • No ranks, medals, or awards from any other Star Trek club are transferable to Bravo Fleet.
Retrieved from "https://wiki.bravofleet.com/index.php?title=Melissa_Vane&oldid=2987"