Bravo Fleet
Difference between pages "Intrepid Class" and "Command Policy"

Difference between pages "Intrepid Class" and "Command Policy"

From Bravo Fleet
(Difference between pages)
m
 
(Added clarity on use of archived commands)
 
Line 1: Line 1:
{{Specifications
{{icons|bfo}}Last Update: 2 March 2023
| image = [[Image:Intrepidclass.png|275px]]
| name = Intrepid
| affiliation = Starfleet
| role = Light Explorer
| dateEntered = 2370
| expectedLife = 100 Years
| expectedRefit = 10 Years
| timeResupply = 3 Years
| crewComplement = 170
| emergencyCap = 500
| length = 344 meters
| width = 133 meters
| height = 66 meters
| decks = 15
| propulsionSystem = Matter/Antimatter powered warp drive
| cruiseSpeed = Warp 7
| maxSpeed = Warp 9.7
| emergencySpeed = Warp 9.975 (36 hours)
| energyWeapons =*13x Type-X phaser arrays
| torpLaunchers =*2 forward
* 2 aft
| torpPayload =*40 Photon Torpedoes
*20 Quantum Torpedoes
| shields =Multi-Layered Shielding System
| shuttleBays =1
| shuttles =4
| runabouts =1
}}The ''Intrepid''-class starship is the culmination of experimental technologies for Starfleet in its efforts to launch a new generation of exploration type vessels. As a test bed, the Intrepid was a decade in the making to offer the exploration and scientific capabilities of the ''Galaxy''-class without the massive space frame or resources required to operate the much larger ''Galaxy''. The seven year journey of the USS ''Voyager'' to return home from the Delta Quadrant only validated the versatility and endurance of the ''Intrepid''-class, making it a mainstay of Starfleet’s exploration arm.


=== Exploration and Science ===
=1 - Registry Definition=
The ''Intrepid'', at the time of its launch, was almost on par with the ''Galaxy''-class sensor suite. Even decades later, few ships of its size are comparable and only large, front-line explorers like the ''Century''-class are able to best it. The Intrepid is widely capable of long-term exploration missions without copious amounts of support; ranging from logging gaseous anomalies to planetary analysis to scanning sub-quantum mass particulates.
#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=


The only area that the Intrepid inherently cannot compare with its larger counterparts is available space. The Intrepid is limited in space due to its smaller size which downsizes the amount of labs, research space, and number of scientists it can carry. The limited space on the Intrepid also limits the available length of its deep space assignments. While the ''Century'' was built in the same vein of former front-line explorers of being able to complete many multi-year missions, the Intrepid was not. Until the circumstances of the USS ''Voyager'' was understood by Starfleet, it wasn’t even believed that the ''Intrepid'' could survive that long in deep space without any support.
#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.
#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
|}


The ''Intrepid''-class was also given one more unique feature: the ability to land and take off from a planetary surface, a first for a Starfleet vessel. The ''Intrepid''-class hull design allows for a smooth atmospheric entry and egress, while landing gear on the bottom of the vessel supports the starship firmly on the surface of a planet, allowing for all ships systems to be taken offline if necessary. Landing mode was a two-fold problem solver for Starfleet. It allows for both extensive repairs in the field that would otherwise require a spacedock, and also allows for easier transfer of equipment and personnel for any extensive planetary surveys.
== 3.1 - Starship Strength ==


=== Diplomacy ===
# Ship classes are allocated a certain level of Strength depending on their size, power, modernity, and so forth.
The ''Intrepid'' has a secondary purpose of diplomatic duties, but like its scientific abilities, is limited by its own size. The ''Intrepid'' is also on par with the ''Galaxy'' in general diplomatic capabilities, but is severely lacking in the amount of diplomacy it can carry out. While the ''Galaxy'' could carry out any and all diplomatic functions necessary of it, the ''Intrepid''’s size limits it to only specific diplomatic functions which it carries out at a standard above most other Starfleet vessels.
# 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.


=== Engineering ===
{| class="wikitable" style="margin:auto"
Upon its launch, the ''Intrepid'' was the testbed for experimental, cutting edge technology that later became standard issue on all ships ahead of it. Among the largest of these technologies is the cutting edge class-9 warp drive, variable-geometry warp nacelles, integrated bio-neural circuitry, and the Emergency Medical Hologram system.
|+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.


The ''Intrepid'' was the first design to implement the new class-9 warp drive which allowed it to top speeds of warp 9.975, which made it the fastest Starfleet vessel at the time of its launch. Additionally, it was the first Starfleet vessel to field variable-geometry warp nacelles. The nacelles, when at warp velocities, pivot up at an angle. These two things combined made it the most subspace friendly vessel that Starfleet had fielded to date with concerns of subspace damage due to extensive warp use spreading across the Alpha Quadrant. It also allowed the Intrepid to sustain much higher warp speeds for much longer periods of time than any vessel before it.
== 3.2 - Starbase Strength ==


As a supplement to the ship’s medical facilities, the Intrepid was one of the first to also field the Emergency Medical Hologram. Utilizing the holographic emitters in the Intrepid’s sickbay, the program was meant to supplement medical staff in the case of an emergency, allowing a holographic doctor to help diagnose, triage, and treat patients. In the case of at least one starship, it was able to completely replace the ships entire medical staff with several expansions to its program. Overall, the technology proved to be incredibly useful to Starfleet vessels, particularly those Intrepid-class starships on the frontier, and has been supplemented, enhanced, and improved across multiple Starfleet classes since the first implementation on the Intrepid.
# 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.


Finally, one of the biggest enhancements the ''Intrepid'' was first to field over any other starship was its integrated bio-neural circuitry. As a supplement to the traditional isolinear circuitry, the bio-neural gel packs act as a nervous system throughout the Intrepid. The bio-neural gel packs allows the ''Intrepid''-class computer core and systems to process information more efficiently, using more instinctive data processing, speed up probability calculations, and cutting down on the amount of crew needed to maintain its systems. The Intrepid also proved as a steep learning curve for the bio-neural systems. While far more robust and durable than traditional circuitry systems, and therefore requiring far less maintenance, they proved to require just as much previously unforeseen medical monitoring as they do engineering monitoring.
{| 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]]||
|}


=== Tactical ===
== 3.3 - Attached Ships ==
Classified officially as a “light cruiser”, the ''Intrepid'' boasts a modest array of weaponry in its arsenal. While not necessarily going to stand toe-to-toe with a Romulan warbird, the Intrepid has impressive phaser array coverage with very little blind spots. The 13 phaser arrays are, shared from the ''Galaxy''-class design, of the Type-X variety. However, the ''Intrepid'' lacks the vastly superior power supply that the Galaxy affords its main phaser array, putting out only a fraction of the firepower the ''Galaxy'' can while at peak operating power. The ''Intrepid'' also sports two forward and two aft torpedo launchers, all of which are capable of firing both photon and quantum torpedoes as needed. The launchers can also be configured to fire probes and tricobalt devices if mission priorities require it.


=== Shipboard Life ===
# 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.
Another area that the Intrepid lacks compared to its larger explorer counterparts is available crew amenities. The ''Intrepid'' boasts a crew mess, an adjoining officers mess, two holodecks, a crew lounge, and a gymnasium. The holodecks of the ''Intrepid'' were unique as they were the first enhanced generation of holodecks since the implementation of the technology on the Galaxy-class. The ''Intrepid'' holodecks were more advanced, more efficient, and far more interactively dynamic.
# 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.


The crew quarters for the Intrepid are broken into three separate categories: standard crew quarters, officer’s quarters, and the captain’s quarters. The delineation of these different categories of crew quarters was no different than any other contemporary Starfleet vessel with size and personal space increasing with rank.
{| class="wikitable"
|+Starbase Attached Ship Options
|[[Aerie Class|Aerie]]
|
|
|
|
|-
|[[Aquarius Class|Aquarius]]
|
|
|
|
|-
|[[Sydney Class|Sydney]]
|
|
|
|
|}


== Class History ==
== 3.4 - Requesting Squadron Ships ==
The ''Intrepid''-class was an astonishing feat of technological marvel that began its development in the midst of the launch of the ''Galaxy''-class platform. As Starfleet pined for larger, more multi-mission starships in lieu of the ''Constitution''-class starships a century before, there were some in Starfleet Command who wanted to bring forward a new line of smaller, faster, less resource-intensive exploration vessels; essentially bringing the ''Galaxy''-class down into a starship with a crew no more than 200. In order to do so, the Starfleet Corps of Engineers would have to bring to life technologies that were only thoughts in the imagination.


The hull design for the ''Intrepid''-class was simple and sleek, but it was the internal mechanisms that took over a decade to develop. When the ''Intrepid''-class launched in the early 2370s it was believed to be a sufficient supplement to Starfleet’s exploratory wing. During the Dominion War, several ''Intrepid''-class starships proved to be invaluable assets because of their incredible speed and extensive sensor suite. But it wasn’t until 2378 when the starship ''Voyager'' returned to the Alpha Quadrant after being stranded in the Delta Quadrant for 7 years that Starfleet finally knew it had a robust workhorse exploratory vessel that could withstand the rigors of deep space for extended periods of time. Now, the Intrepid-class can be found mostly on the frontier of Federation space exploring the unknown.
# Members must use BFMS to request any Commands under the Squadron system, as was done with previous Command requests.
[[Category:Federation starship classes]]
# 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.
[[Category:Light Explorers]]
## 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.
## 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.
## 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.
# 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.

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=Intrepid_Class&oldid=8677"