Bravo Fleet
Difference between pages "Challenger (NX-03)" and "Command Policy"

Difference between pages "Challenger (NX-03)" and "Command Policy"

From Bravo Fleet
(Difference between pages)
m
 
(Added clarity on use of archived commands)
 
Line 1: Line 1:
{{Starship
{{icons|bfo}}Last Update: 2 March 2023
| name = Challenger
| prefix = <nowiki></nowiki>
| image = [[File:Nx-03-a.jpg|400px|center]]
| registry = NX-03
| class = NX
| affiliation = [[United Earth Starfleet]], [[United Earth Commonwealth]]
| status = Active
| commission = February 8th, 2155
| decommission =
| destroyed =
| taskforce =
| quadrant = [[Alpha Quadrant|Alpha]] & [[Beta Quadrant|Beta Quadrants]]
| role = Deep Space Explorer
| co = Fleet Captain [[bfms_char:13950|Lloyd Burton]]
| xo = Commander Alex Rodham
| dedication =
[[File:NX plaque challenger.png|400px|center]]
[[File:Challengerpatch.png|175px|center]] [[File:Maco challenger logo.png|175px|center]]
}}
:"''Ad utilitatem omnium''"
:   —'''''Ship's Dedication Quote'''''
The '''''Challenger'' (NX-03)''' was the third [[NX Class|''NX''-class]] to be launched by the [[United Earth Commonwealth|United Earth’s]] [[United Earth Starfleet|Starfleet]]. The ship was launched on February 8th, 2155 from the orbital facilities above Earth. She was named after the ill-fated space shuttle craft ''[[wikipedia:Space_Shuttle_Challenger|Challenger]]''. The ship’s motto was in Latin and meant ''To the benefit of all''.


= History =
=1 - Registry Definition=
#The registry lists all starships, starbases, and other entities available to Bravo Fleet for use as Commands or Games.
#The registry’s purpose is to maintain consistency across Bravo Fleet and its ongoing canon. As such, entries will not be added to, removed, or altered from the registry without permission of the Intelligence Office.
#The registry represents the In Character starships and starbases available to the Fourth Fleet in {{Year}}, and the starships and starbases available for Games and Commands.
##Exceptions such as non-Starfleet ships or ships of a different era have been created for Fictions or Games, and may not be used as Primary Commands. These will be more often added, deleted, or altered.
##The use of registry entries in Games is governed by Section 4 of the Operations Policy.
#Ships in the registry should only be used in lore by the members or Task Forces (in the case of TFHQ ships or Flagships only) to which they are assigned. If a story requires another ship, it should use a name not listed in the registry and would fall within the bounds of member canon.
#Events involving registry ships ''prior to'' 2399 may be referenced in circumstances such as character service records and backstory. This restriction changes at 2399 as this is when the current fleet canon went live; members should not be dictating fleet or member canon after this outside of their own characters and Command.
#Ships are assigned to a member's dossier when they are created as Commands on BFMS. A member must create an application for the Command that the Intel Office processes. The IO does not create Commands for members. Commands exist to house Missions, Stories, and crew rosters; they show the ship on the member's dossier, and ensure the registry displays what ships are available or unavailable. ''All'' ships in use require a Command, including RPGs and squadron ships.
##Once a ship has been relinquished, the BFMS Command will be labelled as 'Archive' and exist on the member's dossier for archival purposes only. Members may edit the Command page or the roster, but they may not add further Missions or Stories.
#Members should not apply for Commands on BFMS until they are ready to acquire or change their Primary Command, or for a fiction/RPG proposal to be discussed with the Intelligence Officer/Operations Officer. Draft Commands or proposals self-identifying as WIPs will have their registry link removed or be deleted.
#Upon a Command's assignment, a member may not change that Command until three months have elapsed or they are promoted, whichever comes first
##Exceptions may be permitted at the discretion of the Intelligence Officer. This may apply in cases such as the release of new starship classes or other significant alterations to the command registry.
=2 - Primary Commands=
#Primary Commands are attached to a member's dossiers as their character's starship or auxiliary craft. They are the vessels assigned In Character to a member’s Task Force in the Fourth Fleet in {{Year}}.
#Members can write on their Primary Commands on their own or with others. Writing with others on a Primary Command does not require a proposal or activity commitment being sent to the Intelligence Office. Members ''may not'' use their Primary Command as an RPG; ie, they may not openly recruit for crew or create a separate website, and collaboration should be limited to invitation-only. RPGs which any member of the Fleet may apply to join must be accepted by the Bravo Fleet Operations Officer, and thus Primary Commands are unsuitable for this purpose.
#All Commands will be removed from a member's dossier upon transfer to the Reserves.
#When a member reaches the rank of Midshipman they may request a ship on the registry for use as their Primary Command. Ship classes available are unlocked upon reaching certain ranks.
#Members below the rank of Captain may only have one Primary Command. Requesting a new eligible Primary Command will result in the current registry ship being removed from the member's dossier and returned to the pool of available ships.
{| class="wikitable" style="margin:auto"
|+Ship classes by rank
|-
!Midshipman!!Lieutenant Commander!!Commander!!
|-
|[[Raven Class|Raven]]||[[California Class|California]]|| colspan="2" |[[Akira Class|Akira]]
|-
| ||[[Challenger Class|Challenger]]|| colspan="2" |[[Defiant Class|Defiant]]
|-
| ||[[Cheyenne Class|Cheyenne]]|| colspan="2" |[[Excelsior II Class|Excelsior II]]
|-
| ||[[Diligent Class|Diligent]]|| colspan="2" |[[Gagarin Class|Gagarin]]
|-
| ||[[Grissom Class|Grissom]]|| colspan="2" |[[Inquiry Class|Inquiry]]
|-
| ||[[Intrepid Class|Intrepid]]|| colspan="2" |[[Luna Class|Luna]]
|-
|
|[[New Orleans Class|New Orleans]]
| colspan="2" |[[Manticore Class|Manticore]]
|-
| ||[[Norway Class|Norway]]|| colspan="2" |[[Nebula Class|Nebula]]
|-
| ||[[Nova Class|Nova]]|| colspan="2" |[[Pathfinder Class|Pathfinder]]
|-
| ||[[Olympic Class|Olympic]]|| colspan="2" |[[Prometheus Class|Prometheus]]
|-
|
|[[Parliament Class|Parliament]]
| colspan="2" |[[Rhode Island Class|Rhode Island]]
|-
| ||[[Reliant Class|Reliant]]|| colspan="2" |[[Sutherland Class|Sutherland]]
|-
| ||[[Saber Class|Saber]]|| colspan="2" |
|-
| ||[[Springfield Class|Springfield]]
|-
| ||[[Steamrunner Class|Steamrunner]]
|}
=3 - Squadrons=


== Construction ==
#The Squadron system allows members holding the dossier rank of Captain and above greater flexibility in their Command choices. Where Commanders and below may pick a single Primary Command from a list, Captains are entitled to a certain level of ‘Squadron Strength’ in their Command selection. This gives them options like choosing between a single, larger ship or multiple smaller ones.
Construction on ''Challenger'' had begun at the start of 2153, one month after the launch of [https://memory-alpha.fandom.com/wiki/Columbia ''Columbia'' (NX-02)]. As Starfleet engineers were well aware of previous technical issues from the construction of the first two ''NX''-class ships, ''Challenger’s'' construction took half the time compared to its older sisters. Construction of the ship went without a hitch and she performed exceptionally well in tests and her trial runs. Project Management was given to Captain Rani Karim, its designated commanding officer when the ship launched. Sadly, though Karim would not see the christening of ''Challenger'', as her and her chief science officer and second officer (Lieutenant Commander Alec Rossi) were killed in a shuttlepod accident days before the ship was to be launched. Instead Starfleet gave command of the ship to the only other person who knew it so well, Karim’s presumptive first officer and chief armoury officer: Commander Lloyd Burton. Rear Admiral Samuel Gardner would give Burton a promotion to Captain and at the official launching ceremony would hand him command of the third warp five capable ship.
#If a member holds multiple Commands under the Squadrons system, these ships are all subject to the same usage requirements as outlined under Primary Commands above. They may not be used as RPGs, and IC are starships assigned to the member’s Task Force.
##All ships must have their own Command on BFMS. This is solely to ensure the registry accurately reflects what ships are in use and dossiers show all of a member's ships. Members are free, however, to house Stories and Missions involving the ship and crew on any of their squadron BFMS Commands.
##Members with multiple ships should designate one as their Primary Command on BFMS. This is solely for display and organisational purposes, and has no other or IC significance. The Primary Command must be a Squadron Commands, and may not be an RPG or Fiction.
##Members have some freedom on how to IC depict these multiple ships. They may be entirely unaffiliated, all falling directly under their Task Force’s IC chain of command, with the member using them to tell totally different stories.
##Members may use all/some of them to form an IC-only unit within their Task Force, referred to as a squadron. This typically takes its title from the squadron’s ‘lead ship’ or starbase (for example, a squadron led by the USS Endeavour would be called ‘Endeavour Squadron’). This ensures all squadrons have a unique IC name. Members may not call these IC units ‘task groups’, to avoid confusion with the OOC unit.
##Members may create an officer in command of this squadron, who may or may not also be the commanding officer of one of these starships/starbase, and who falls IC under the chain of command of the member’s Task Force. All Canon Policy rank restrictions remain.
#The Squadron Strength to which a member is entitled is dependent on their dossier rank.
{| class="wikitable"
|+'''Squadron Strength by Dossier Rank'''
!Captain
!Fleet Captain
!Commodore
!Rear Admiral
!Vice Admiral
!Admiral
!Fleet Admiral
|-
|3
|4
|6
|7
|8
|9
|10
|}


=== 2155-2156 ===
== 3.1 - Starship Strength ==
The crew of ''Challenger'' would take some time to adjust to the changes in its command crew, as Burton had lost a few other senior staff who were unable to remain on the ship after Karim and Rossi’s death. It was not a reflection on his ability to lead the ship, but many of them had worked closely with Karim on previous assignments and felt they couldn’t stay. Before the ship’s launch, Burton had to find a number of new officers, including a first officer. He was fortunate enough to be able to pull in a few favours and before he had received the ship’s first set of orders, he had fully staffed his new ship.


''Challenger’s'' first mission was to lead a convoy of allied ships (Vulcan, Andorian and Tellarite) to Denobula to convince the Denobulan government in joining the Coalition of Planets. On board leading the delegates would be Earth’s Foreign Secretary, Madilyn Campbell. The convoy was attacked by the Orions and some of the crew (along with other delegates) were captured by them to be sold on the Orion Slave Market. Burton led the efforts to rescue those kidnapped and showed the Orion Syndicate (who were actually being paid by the Romulans to undertake such aggression) exactly what the Coalition could achieve when they worked together.  
# Ship classes are allocated a certain level of Strength depending on their size, power, modernity, and so forth.
# Members may select any number of ships as their Commands under the Squadrons system, so long as the total Strength does not exceed their rank entitlement.


When the ship arrived in orbit of Denobula, they worked with the delegates to convince the Denobulan government and its public to join the Coalition without reservation. In fact the crew became extremely popular with the general population, especially Captain Burton who was returning to the planet after saving a number of their citizens during a previous assignment. The crew’s efforts though were ruined when the Romulan Star Empire attacked Coridan Prime. The Denobulan government’s referendum on joining the Coalition Compact was withdrawn in fear of a similar attack taking place against them, something they wanted to avoid.  
{| class="wikitable" style="margin:auto"
|+Ship classes by rank
|-
!1!!2!! colspan="2" |3
!4
|-
|Small Civilian Ship|| colspan="2" |[[Akira Class|Akira]]||[[Century Class|Century]]
|[[Odyssey Class|Odyssey]]
|-
|[[California Class|California]]|| colspan="2" |[[Defiant Class|Defiant]]||[[Galaxy Class|Galaxy]]
|
|-
|[[Challenger Class|Challenger]]|| colspan="2" |[[Excelsior II Class|Excelsior II]]||[[Obena Class|Obena]]
|
|-
|[[Cheyenne Class|Cheyenne]]|| colspan="2" |[[Gagarin Class|Gagarin]]||[[Ross Class|Ross]]
|
|-
|[[Diligent Class|Diligent]]|| colspan="2" |[[Inquiry Class|Inquiry]]||[[Sovereign Class|Sovereign]]
|
|-
|[[Grissom Class|Grissom]]|| colspan="2" |[[Luna Class|Luna]]||[[Typhon Class|Typhon]]
|
|-
|[[Intrepid Class|Intrepid]]|| colspan="2" |[[Manticore Class|Manticore]]||[[Vesta Class|Vesta]]
|
|-
|[[New Orleans Class|New Orleans]]|| colspan="2" |[[Nebula Class|Nebula]]||
|
|-
|[[Norway Class|Norway]]|| colspan="2" |[[Pathfinder Class|Pathfinder]]||
|
|-
|[[Nova Class|Nova]]|| colspan="2" |[[Prometheus Class|Prometheus]]||
|
|-
|[[Olympic Class|Olympic]]|| colspan="2" |[[Rhode Island Class|Rhode Island]]||
|
|-
|[[Parliament Class|Parliament]]||[[Sutherland Class|Sutherland]]
|-
|[[Reliant Class|Reliant]]||
|-
|[[Saber Class|Saber]]||
|-
|[[Springfield Class|Springfield]]
|
|-
|[[Steamrunner Class|Steamrunner]]
|
|}
#For example, upon reaching the rank of Captain a member has a Squadron Strength entitlement of 3. If they already have a Commander-level ship, they are only using 2 of their Squadron Level. They may ‘upgrade’ as they did upon reaching the rank of Commander, returning their current ship to the registry and choosing a single new Command with a Strength of 3. If they keep their ship with its Strength of 2, they may choose to add to their dossier another ship with a Strength of 1.
##Members are under no obligation to use their total Squadron Strength. These Commands are a reflection of the hard work of members, however, and may be chosen for storytelling opportunities or simple prestige.
#‘Small Civilian Ship’ is a catch-all term for non-Starfleet civilian vessels members may wish to use for different kinds of storytelling. It refers to ships of, for example, the [[Kaplan F17 class]] or the [[Groumall class]], usually freighters, that are not affiliated IC with Starfleet and may be used for trading, prospecting, exploration, or other adventures. Acquiring a ship like this is subject to a successful Fiction Proposal, and so they are not listed as available on the registry but created as required by the Intelligence Office.
#The Intelligence Office may make adjustments to ship class Strengths to account for balance as the system and canon evolve. No member will have an asset removed because of a rebalance, but they would only be grandfathered in until they wanted to change their squadron, at which point the new strength values would be used.


At the end of February 2155, ''Challenger'' led Starfleet’s efforts to defend the new colony on Archer IV when the Romulans attempted to destroy the planet through the use of nuclear warheads. Starfleet was successful and forced the Romulans to retreat from the system. Burton and his crew would save the colonists and help begin their setup of making a new home. At the start of the next month, ''Challenger'' returned to Earth to witness the signing of the Coalition Compact between Earth, Vulcan, Andoria and Tellar.
== 3.2 - Starbase Strength ==


By April 2155, the ship had continued its original mission of exploration. The crew scanned and catalogued more space than ''Enterprise'' and ''Columbia'' did in their first fifty days. They were later ordered to Andoria on a diplomatic mission to meet with the new Andorian leader. During this meeting an Andorian colony was attacked by a joint Malurian-Nausicaan invasion force. Under the terms set out by the Coalition Compact, Captain Burton had to respond to the attack by joining the Andorian fleet sent to deal with the invasion. Unfortunately the Andorian fleet was heavily damaged during their initial rescue attempt and Captain Burton was made an Honouree Commander within the Imperial Guard. He was given command of the remnants of the task force and was temporarily made a Commodore by the President of the United Earth Commonwealth. With this power he and his crew worked to remove the Malurian–Nausicaan invasion force from the colony. By the end of the mission they uncovered that the Romulans had funded and supported the attack. Both governments of Maluria and Nausicaa released a statement, each denying any official involvement in the fight and it was recorded that those that attacked the Andorians were hired mercenaries.
# Starbases as Commands work the same as starships under the Squadron system, but are subject to different requirements. They represent starbases assigned In Character to the member’s Task Force in the Fourth Fleet in 2400.
# Members do not have to choose between a starbase or starship under the Squadron system. They are only restricted by their rank’s total Squadron Strength.
# Registry Starbases are created by the Intelligence Office, and will have their own wiki article explaining the location and setting material relevant to that starbase that has been ratified by the Intelligence Office. This is Fleet Canon that cannot be altered without permission of the Intelligence Office, even by the member to whom the starbase registry is attached. As such, members should heavily consider their choice, as a Starbase Command is under more restrictions and requirements from the Intelligence Office.
## If you are interested in a Starbase Command, please speak with the Intelligence Office to develop your concept so the registry can be created.
# Members may choose to depict any of their other ships as attached to or operating out of the starbase.


Over a month later and ''Challenger'' was ordered to make official first contact with the Deltan Union. With the possibility of more conflict with the Romulans on the horizon, the Coalition of Planets was keen to make more allies and expand their influence in the region. ''Challenger'' was once again pulled into a local conflict, one between the Deltans and the Carreons (the Deltans’ aggressive neighbours). Attempting to escape from the fight, ''Challenger'' was repeatedly attacked by the Carreons. Eventually Captain Burton ordered a majority of the crew to abandon ship. Those who escaped took refuge on a planet inhabited by a pre-warp civilisation. The humanoid civilisation called themselves the Ardanans and they had impressive technology that allowed the rich and powerful members of their society to live on “cloud cities”. After they were rescued by Commander Anthi and the Andorian crew of the ''Avenkerev'', the crew returned to the ship and made their way home. Sadly though the conflict between the Deltans and Carreons ended with both sides inflicting heavy damage to one another. Again ''Challenger'' discovered that the Romulans were involved in destabilising relations between the two races. ''Challenger'' returned to Earth for extensive repairs and upgrades, on its way home the crew were informed that [[Earth-Romulan War|war]] with the Romulans had been declared.
{| class="wikitable" style="margin:auto"
|+Starbase classes by Strength
|-
!2!!3!!4
|-
|[[Jupiter Class|Jupiter]]||[[Anchorage Class|Anchorage]]||[[Canopus Class|Canopus]]
|-
|[[K Class|K-Type]]||[[Copernicus Class|Copernicus]]||[[Unity Class|Unity]]
|-
|[[Regula Class|Regula]]||[[Narendra Class|Narendra]]||
|-
|[[Vision Class|Vision]]||[[Presidium Class|Presidium]]||
|-
| ||[[Watchtower Class|Watchtower]]||
|}


Once repairs were completed to the ship, ''Challenger'' was sent to determine what happened at Deneva colony. The Starfleet relief task force sent to support it  reported that the [[Discovery (NX-04)|''Discovery'' (NX-04)]] and [[Armstrong (NCC-100)|''Armstrong'' (NCC-100)]] had both gone missing. The crew soon find the debris belonging to the ''Armstrong'' along with some survivors. Bringing the ''Armstrong''<nowiki/>'s crew on board, the crew hunted down the ''Discovery''. Both ships had engaged a small task group of [[ma:Romulan_drone_ship|Romulan drone ships]] but the ''Discovery'' had led a number of them away from the original battle, allowing the ''Armstrong'' the time it needed to send a message to Starfleet about the attack. Following the trail left by their sister ship, ''Challenger'' tracked their sister ship down into the [[ma:The_Barrens|Barrens]]. The unique properties of the  unique region prevented the Romulans from controlling their drone ships, leaving them to attack their enemies using their limited automated systems and programming. Saving the ''Discovery'' from its attackers, ''Challenger'' removed the threat of the final drone ships but soon found out why the drones were attacking ''Discovery''. Captain [[Frank Müller]] and his crew had captured one of the drone ships.  ''Discovery'' was fixed and investigations on the captured ship gave access to its database.  Both crews reviewed the data and found one particular target that interested them. Plans were prepared to use the drone ship to deal the Romulans a crippling blow by attacking the outpost they were using to control the drone ship fleet. Deep in the [[ma:Bassen_Rift|Bassen Rift]] the Romulans had concealed their command base and were using a micro-singularity to boost their telemetry. A mixed team compromised of crews from both the ''Challenger'' and ''Discovery'' made their way onboard the captured drone ship (designated the ''Prowler)'' to attack the Romulan base. The attack was a success but is resulted in the loss of several ''Challenger'' crewmembers and the destruction of the captured ship. With the outpost now destroyed, the Romulans ability to control their drone ships over significant distance was removed, this gave Earth the breathing space needed to repair its fleet and defensives.
== 3.3 - Attached Ships ==


==Design & Layout ==
# Certain commands, like starbases, have an attached ship, which has its own registry entry but has an effective Strength of 0. Whether or not an attached ship is selected does not affect a member’s Squadron Strength.
Similar to other ''NX-''class ships, the ''Challenger'' followed in a similar arrangements and this included the internal colour scheme of different shades of blue and turquoise being used across the ship. Unlike ''Enterprise'' and ''Columbia'', ''Challenger'' does have carpet installed in the centre aisle of each corridor and within each quarter. A small taste of luxury.  
# Most attached ships are assigned to starbases. Upon requesting a starbase, the member should identify to the Intelligence Office an appropriate choice of ship from the registry. That ship will then be removed from the public pool. It will not be given a BFMS Command, but should be written about as part of the starbase’s Command.
# The ''Odyssey''-class always has an ''Aquarius''-class ship attached. Unlike with starbases, the ''Aquarius''-class’s name is predetermined and cannot be changed. Details about an ''Odyssey’s'' ''Aquarius''-class will be listed on the ship’s wiki page.


A majority of the systems that were installed on the ''Challenger'' had become tried and tested systems as a result it was rare for the ship to come across any technical issues during its missions.
{| class="wikitable"
|+Starbase Attached Ship Options
|[[Aerie Class|Aerie]]
|
|
|
|
|-
|[[Aquarius Class|Aquarius]]
|
|
|
|
|-
|[[Sydney Class|Sydney]]
|
|
|
|
|}


One thing that Starfleet insisted before the ship was launched was that it was heavily armed with the best weaponry and defence technology. Her hull armour was thicker and her phase cannons could throw a heavier punch. This allowed the ship to last longer in battles, something that came into use during the Earth-Romulan War.
== 3.4 - Requesting Squadron Ships ==


==Crew==
# Members must use BFMS to request any Commands under the Squadron system, as was done with previous Command requests.
===Command Staff===
# BFMS requests for new Commands under the Squadron system must use the ‘Lore Office Proposal’ window to clearly communicate their allocation of their Squadron Level. This must include what ships, if any, are being returned to the registry.
*'''Commanding Officer:'''
## If a new Captain requests a Command with a Strength of 3 with no further detail, the Intelligence Office will assume they are returning their current ship to the registry, just as with previous upgrades, and process accordingly.
**Captain Rani Karim (Human Female) <small>(2154-2155)</small>
## If a Member wishes to retain their current Command and add another, they may request the new ship under BFMS and say so in the Proposal window. A simple message, such as ‘I am keeping the USS Lollipop (Strength 2), and adding this one (Strength 1) for a total Squadron Strength of 3’ will suffice.
**Captain/Fleet Captain Lloyd Burton (Human Male) <small>(2155+)</small>
## If a Member wishes to return any of their ships to the registry, they must say so. Any requests for additional Commands that does not include a registry return and would bring a member over their Squadron Strength will be deleted. A simple message, such as ‘I am returning the USS Lollipop (Strength 2) and adding this one (Strength 3) for a total Squadron Strength of 3’ will suffice.
*'''Executive Officer:'''
# If the Intelligence Office receives competing requests for the same starship, requests for a primary command from Lieutenant Commanders or Commanders will be prioritised, or upgrades to a single Strength 3 starship for new Captains. After that, ships will be allocated on a first-come, first-served basis.
**Commander Lloyd Burton (Human Male) <small>(2154-2155)</small>
**Commander Nicolette Levesque (Human Female) <small>(2155)</small>
**Commander Michael Stanton (Human Male) <small>(2155)</small>
**Commander Alex Rodham (Human Male) <small>(2155+)</small>
*'''Second Officer:'''
**Lieutenant Commander Alec Rossi (Human Male) <small>(2154-2155)</small>
**Commander Michael Stanton (Human Male) <small>(2155)</small>
**Lieutenant Commander/Commander Cooper Walker (Human Male) <small>(2155+)</small>
*'''Third Officer:'''
**Lieutenant Commander Caspar Slater (Human Male) <small>(2154-2155)</small>
**Lieutenant Commander John Callahan (Human Male) <small>(2155)</small>
**Sub Commander T'Plau (Vulcan Female) <small>(2155)</small>
**Lieutenant Commander Kefira Ben-Ami <small>M.D</small>  (Human Female) <small>(2155+)</small>
 
=== Senior Staff/Department Heads ===
*'''Chief Science Officer:'''
**Lieutenant Commander Alec Rossi (Human Male) <small>(2154-2155)</small>
**Commander Nicolette Levesque (Human Female) <small>(2155)</small>
**Ensign/Lieutenant junior grade Martha Habiba (Human Female) <small>(2155) ''(Acting Chief Science Officer)''</small>
**Lieutenant Commander/Commander Cooper Walker (Human Male) <small>(2155+)</small>
*'''Chief Engineer:'''
**Lieutenant Commander Caspar Slater (Human Male) <small>(2154-2155)</small>
**Commander Michael Stanton (Human Male) <small>(2155)</small>
**Lieutenant Sakura Masuko (Human Female) <small>(2155+)</small>
*'''Chief Armoury Officer:'''
**Commander Lloyd Burton (Human Male) <small>(2154-2155)</small>
**Lieutenant Commander John Callahan (Human Male) <small>(2155)</small>
**Sub Commander T'Plau (Vulcan Female) <small>(2155)</small>
**Lieutenant junior grade Rachele Cortez (Human Female) <small>(2155+)</small>
*'''Chief Medical Officer:'''
**Lieutenant Calista Moralez <small>M.D</small>  (Human Female) <small>(2154-2155)</small>
**Lieutenant/Lieutenant Commander Kefira Ben-Ami <small>M.D</small>  (Human Female) <small>(2155+)</small>
*'''Chief Helm Officer:'''
**Ensign Ezrah Alcott (Human Male) <small>(2155)</small>
**Ensign/Lieutenant junior grade Jack Conrad (Human Male) <small>(2155)</small>
**Commander Alex Rodham (Human Male) <small>(2155+)</small>
*'''Chief Communications Officer / Protocol Officer:'''
**Ensign Mattias Hansson (Human Male) <small>(2154-2155)</small>
**Ensign/Lieutenant junior grade Ned Hennessey (Human Male) <small>(2155+)</small>
**Ensign Tanisha Avery (Human Female) <small>(2155) ''(Acting Chief Communications Officer)''</small>
*'''Gamma Shift Officer of the Watch:'''
**Lieutenant Commander Rosa Sandoval (Human Female) <small>(2155+)</small>
*'''MACO Detachment Unit Commander:'''
**Major Viktoria Yu (Human Female) <small>(2155)</small>
**First Lieutenant Khawla al-Fayaad (Human Female) <small>(2155) ''(Acting Unit Commander)''</small>
**Captain Luis Trommler (Human Male) <small>(2155+)</small>
 
=== Other Crew ===
 
==== Command Department ====
 
* '''Chief of the Boat / Quartermaster:'''
** Senior Chief Petty Officer Ghislaine Dubois (Human Female) <small>(2154+)</small>
* '''Yeoman:'''
** Crewmember First Class Jamie Harris (Human Male) <small>(2155+)</small>
 
==== Helm Department ====
 
* '''Second Helm Officer:'''
** Ensign Angela Hathaway (Human Female) <small>(2155+)</small>
* '''Third Helm Officer:'''
** Ensign Cristiano Gonçalves (Human Male) <small>(2154+)</small>
* '''Fourth Helm Officer:'''
** Petty Officer First Class Adrian Kowalski (Human Male) <small>(2154+)</small>
 
==== Engineering Department ====
 
* '''Second Engineer:'''
** Lieutenant junior grade/Lieutenant  Sakura Masuko (Human Female) <small>(2154-2155)</small>
** Lieutenant junior grade Colleen Malone (Human Female) <small>(2155+)</small>
* '''Third Engineer:'''
** Ensign Theodoros Metaxas (Human Male) <small>(2154+)</small>
* '''Fourth Engineer:'''
** Ensign Elijah Peterson (Human Male) <small>(2154+)</small>
* '''Chief Culinary Specialist / Chef & Morale Officer:'''
** Petty Officer First Class Montana Lawson (Human Female) <small>(2155+)</small>
 
==== Armoury Department ====
 
* '''Second Armoury Officer:'''
** Ensign Rachele Cortez (Human Female) <small>(2154-2155)</small>
** Ensign Adrian Reddick (Human Male) <small>(2155+)</small>
* '''Third Armoury Officer:'''
** Ensign Kimberly Brewster (Human Female) <small>(2155+)</small>
 
==== Science Department ====
 
* '''Second Science Officer/Chief Biologist:'''
** Ensign/Lieutenant junior grade Martha Habiba (Human Female) <small>(2154+)</small>
* '''Third Science Officer/ Chief Physicist:'''
** Ensign Sebastian Dalton (Human Male) <small>(2154+)</small>
* '''Fourth Science Officer/Chief Chemist:'''
** Ensign Ramya Dey (Human Female) <small>(2154+)</small>
 
==== Medical Department ====
 
* '''Second Medical Officer:'''
** Lieutenant junior grade Hillary Payne <small>M.D</small> (Human Female) <small>(2155+)</small>
 
* '''Senior Nursing Officer:'''
** Ensign/Lieutenant junior Niall Stewart (Human Male) <small>(2155+)</small>
 
==== Communications Department ====
 
* '''Second Communications Officer:'''
** Ensign Erik Larsen (Human Male) <small>(2154-2155)</small>
** Ensign Tanisha Avery (Human Female) <small>(2155+)</small>
* '''Xenolinguistics Specialist / Protocol Aide:'''
** Petty Officer First Class Craig Johnson (Human Male) <small>(2154+)</small>
* '''Communications Systems Specialist:'''
** Petty Officer Third Class Lily Howard (Human Female) <small>(2154+)</small>
 
==== MACO Detachment Unit ====
 
* '''Detachment Deputy Commander:'''
** First Lieutenant Khawla al-Fayaad (Human Female) <small>(2155)</small>
** First Lieutenant Sheridian Alder (Human Female) <small>(2155+)</small>
* '''Detachment Assistant Commander:'''
** Second Lieutenant Luis Trommler (Human Male) <small>(2155)</small>
** Second Lieutenant Alizeh Javini (Human Female) <small>(2155+)</small>
* '''Detachment First Sergeant:'''
** Staff Sergeant Rupesh Iyer (Human Male) <small>(2155+)</small>
* '''Support Specialist & Field Medic:'''
** Lance Corporal/Corporal Liam Jenkins (Human Male) <small>(2155+)</small>
* '''Assault Operator:'''
** Private Harvey Rafferty (Human Male) <small>(2155+)</small>

Revision as of 11:35, 2 March 2023

This article is official Bravo Fleet Official Policy.








Last Update: 2 March 2023

1 - Registry Definition

  1. The registry lists all starships, starbases, and other entities available to Bravo Fleet for use as Commands or Games.
  2. The registry’s purpose is to maintain consistency across Bravo Fleet and its ongoing canon. As such, entries will not be added to, removed, or altered from the registry without permission of the Intelligence Office.
  3. The registry represents the In Character starships and starbases available to the Fourth Fleet in 2401, and the starships and starbases available for Games and Commands.
    1. Exceptions such as non-Starfleet ships or ships of a different era have been created for Fictions or Games, and may not be used as Primary Commands. These will be more often added, deleted, or altered.
    2. The use of registry entries in Games is governed by Section 4 of the Operations Policy.
  4. Ships in the registry should only be used in lore by the members or Task Forces (in the case of TFHQ ships or Flagships only) to which they are assigned. If a story requires another ship, it should use a name not listed in the registry and would fall within the bounds of member canon.
  5. Events involving registry ships prior to 2399 may be referenced in circumstances such as character service records and backstory. This restriction changes at 2399 as this is when the current fleet canon went live; members should not be dictating fleet or member canon after this outside of their own characters and Command.
  6. Ships are assigned to a member's dossier when they are created as Commands on BFMS. A member must create an application for the Command that the Intel Office processes. The IO does not create Commands for members. Commands exist to house Missions, Stories, and crew rosters; they show the ship on the member's dossier, and ensure the registry displays what ships are available or unavailable. All ships in use require a Command, including RPGs and squadron ships.
    1. Once a ship has been relinquished, the BFMS Command will be labelled as 'Archive' and exist on the member's dossier for archival purposes only. Members may edit the Command page or the roster, but they may not add further Missions or Stories.
  7. Members should not apply for Commands on BFMS until they are ready to acquire or change their Primary Command, or for a fiction/RPG proposal to be discussed with the Intelligence Officer/Operations Officer. Draft Commands or proposals self-identifying as WIPs will have their registry link removed or be deleted.
  8. Upon a Command's assignment, a member may not change that Command until three months have elapsed or they are promoted, whichever comes first
    1. Exceptions may be permitted at the discretion of the Intelligence Officer. This may apply in cases such as the release of new starship classes or other significant alterations to the command registry.

2 - Primary Commands

  1. Primary Commands are attached to a member's dossiers as their character's starship or auxiliary craft. They are the vessels assigned In Character to a member’s Task Force in the Fourth Fleet in 2401.
  2. Members can write on their Primary Commands on their own or with others. Writing with others on a Primary Command does not require a proposal or activity commitment being sent to the Intelligence Office. Members may not use their Primary Command as an RPG; ie, they may not openly recruit for crew or create a separate website, and collaboration should be limited to invitation-only. RPGs which any member of the Fleet may apply to join must be accepted by the Bravo Fleet Operations Officer, and thus Primary Commands are unsuitable for this purpose.
  3. All Commands will be removed from a member's dossier upon transfer to the Reserves.
  4. When a member reaches the rank of Midshipman they may request a ship on the registry for use as their Primary Command. Ship classes available are unlocked upon reaching certain ranks.
  5. Members below the rank of Captain may only have one Primary Command. Requesting a new eligible Primary Command will result in the current registry ship being removed from the member's dossier and returned to the pool of available ships.
Ship classes by rank
Midshipman Lieutenant Commander Commander
Raven California Akira
Challenger Defiant
Cheyenne Excelsior II
Diligent Gagarin
Grissom Inquiry
Intrepid Luna
New Orleans Manticore
Norway Nebula
Nova Pathfinder
Olympic Prometheus
Parliament Rhode Island
Reliant Sutherland
Saber
Springfield
Steamrunner

3 - Squadrons

  1. The Squadron system allows members holding the dossier rank of Captain and above greater flexibility in their Command choices. Where Commanders and below may pick a single Primary Command from a list, Captains are entitled to a certain level of ‘Squadron Strength’ in their Command selection. This gives them options like choosing between a single, larger ship or multiple smaller ones.
  2. If a member holds multiple Commands under the Squadrons system, these ships are all subject to the same usage requirements as outlined under Primary Commands above. They may not be used as RPGs, and IC are starships assigned to the member’s Task Force.
    1. All ships must have their own Command on BFMS. This is solely to ensure the registry accurately reflects what ships are in use and dossiers show all of a member's ships. Members are free, however, to house Stories and Missions involving the ship and crew on any of their squadron BFMS Commands.
    2. Members with multiple ships should designate one as their Primary Command on BFMS. This is solely for display and organisational purposes, and has no other or IC significance. The Primary Command must be a Squadron Commands, and may not be an RPG or Fiction.
    3. Members have some freedom on how to IC depict these multiple ships. They may be entirely unaffiliated, all falling directly under their Task Force’s IC chain of command, with the member using them to tell totally different stories.
    4. Members may use all/some of them to form an IC-only unit within their Task Force, referred to as a squadron. This typically takes its title from the squadron’s ‘lead ship’ or starbase (for example, a squadron led by the USS Endeavour would be called ‘Endeavour Squadron’). This ensures all squadrons have a unique IC name. Members may not call these IC units ‘task groups’, to avoid confusion with the OOC unit.
    5. Members may create an officer in command of this squadron, who may or may not also be the commanding officer of one of these starships/starbase, and who falls IC under the chain of command of the member’s Task Force. All Canon Policy rank restrictions remain.
  3. The Squadron Strength to which a member is entitled is dependent on their dossier rank.
Squadron Strength by Dossier Rank
Captain Fleet Captain Commodore Rear Admiral Vice Admiral Admiral Fleet Admiral
3 4 6 7 8 9 10

3.1 - Starship Strength

  1. Ship classes are allocated a certain level of Strength depending on their size, power, modernity, and so forth.
  2. Members may select any number of ships as their Commands under the Squadrons system, so long as the total Strength does not exceed their rank entitlement.
Ship classes by rank
1 2 3 4
Small Civilian Ship Akira Century Odyssey
California Defiant Galaxy
Challenger Excelsior II Obena
Cheyenne Gagarin Ross
Diligent Inquiry Sovereign
Grissom Luna Typhon
Intrepid Manticore Vesta
New Orleans Nebula
Norway Pathfinder
Nova Prometheus
Olympic Rhode Island
Parliament Sutherland
Reliant
Saber
Springfield
Steamrunner
  1. For example, upon reaching the rank of Captain a member has a Squadron Strength entitlement of 3. If they already have a Commander-level ship, they are only using 2 of their Squadron Level. They may ‘upgrade’ as they did upon reaching the rank of Commander, returning their current ship to the registry and choosing a single new Command with a Strength of 3. If they keep their ship with its Strength of 2, they may choose to add to their dossier another ship with a Strength of 1.
    1. Members are under no obligation to use their total Squadron Strength. These Commands are a reflection of the hard work of members, however, and may be chosen for storytelling opportunities or simple prestige.
  2. ‘Small Civilian Ship’ is a catch-all term for non-Starfleet civilian vessels members may wish to use for different kinds of storytelling. It refers to ships of, for example, the Kaplan F17 class or the Groumall class, usually freighters, that are not affiliated IC with Starfleet and may be used for trading, prospecting, exploration, or other adventures. Acquiring a ship like this is subject to a successful Fiction Proposal, and so they are not listed as available on the registry but created as required by the Intelligence Office.
  3. The Intelligence Office may make adjustments to ship class Strengths to account for balance as the system and canon evolve. No member will have an asset removed because of a rebalance, but they would only be grandfathered in until they wanted to change their squadron, at which point the new strength values would be used.

3.2 - Starbase Strength

  1. Starbases as Commands work the same as starships under the Squadron system, but are subject to different requirements. They represent starbases assigned In Character to the member’s Task Force in the Fourth Fleet in 2400.
  2. Members do not have to choose between a starbase or starship under the Squadron system. They are only restricted by their rank’s total Squadron Strength.
  3. Registry Starbases are created by the Intelligence Office, and will have their own wiki article explaining the location and setting material relevant to that starbase that has been ratified by the Intelligence Office. This is Fleet Canon that cannot be altered without permission of the Intelligence Office, even by the member to whom the starbase registry is attached. As such, members should heavily consider their choice, as a Starbase Command is under more restrictions and requirements from the Intelligence Office.
    1. If you are interested in a Starbase Command, please speak with the Intelligence Office to develop your concept so the registry can be created.
  4. Members may choose to depict any of their other ships as attached to or operating out of the starbase.
Starbase classes by Strength
2 3 4
Jupiter Anchorage Canopus
K-Type Copernicus Unity
Regula Narendra
Vision Presidium
Watchtower

3.3 - Attached Ships

  1. Certain commands, like starbases, have an attached ship, which has its own registry entry but has an effective Strength of 0. Whether or not an attached ship is selected does not affect a member’s Squadron Strength.
  2. Most attached ships are assigned to starbases. Upon requesting a starbase, the member should identify to the Intelligence Office an appropriate choice of ship from the registry. That ship will then be removed from the public pool. It will not be given a BFMS Command, but should be written about as part of the starbase’s Command.
  3. The Odyssey-class always has an Aquarius-class ship attached. Unlike with starbases, the Aquarius-class’s name is predetermined and cannot be changed. Details about an Odyssey’s Aquarius-class will be listed on the ship’s wiki page.
Starbase Attached Ship Options
Aerie
Aquarius
Sydney

3.4 - Requesting Squadron Ships

  1. Members must use BFMS to request any Commands under the Squadron system, as was done with previous Command requests.
  2. BFMS requests for new Commands under the Squadron system must use the ‘Lore Office Proposal’ window to clearly communicate their allocation of their Squadron Level. This must include what ships, if any, are being returned to the registry.
    1. If a new Captain requests a Command with a Strength of 3 with no further detail, the Intelligence Office will assume they are returning their current ship to the registry, just as with previous upgrades, and process accordingly.
    2. If a Member wishes to retain their current Command and add another, they may request the new ship under BFMS and say so in the Proposal window. A simple message, such as ‘I am keeping the USS Lollipop (Strength 2), and adding this one (Strength 1) for a total Squadron Strength of 3’ will suffice.
    3. If a Member wishes to return any of their ships to the registry, they must say so. Any requests for additional Commands that does not include a registry return and would bring a member over their Squadron Strength will be deleted. A simple message, such as ‘I am returning the USS Lollipop (Strength 2) and adding this one (Strength 3) for a total Squadron Strength of 3’ will suffice.
  3. If the Intelligence Office receives competing requests for the same starship, requests for a primary command from Lieutenant Commanders or Commanders will be prioritised, or upgrades to a single Strength 3 starship for new Captains. After that, ships will be allocated on a first-come, first-served basis.
Retrieved from "https://wiki.bravofleet.com/index.php?title=Challenger_(NX-03)&oldid=8677"