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

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

From Bravo Fleet
(Difference between pages)
 
(Added clarity on use of archived commands)
 
Line 1: Line 1:
{{Specification
{{icons|bfo}}Last Update: 2 March 2023
| image = [[File:Narendra1.png]]
| displayName = '''''Narendra'' Class'''
| name = Narendra
| affiliation = [[United Federation of Planets]]
| operator = [[Starfleet]]
| status = Active
| role = Outpost
| type =
| precedingClass =
| succeedingClass =
| dateEntered = 2375
| productionEnd =
| retired =
| expectedDuration =
| expectedRefit =
| timeResupply =
| crewComplement = 2000
| emergencyCap =
| civilians = 2000-4000
| populationCap = 15000
| flightCrew =
| passengers =
| length =
| width =
| diameter = 1,000 meters
| height =
| decks =
| propulsionSystem = Manuvering Thrusters
| cruiseSpeed =
| maxSpeed =
| emergencySpeed =
| energyWeapons = 12 Type-XII Phaser Arrays
*4x dorsal
*4x mid
*4x ventral
24 Type-X Phaser Banks
*6x dorsal
*12x mid
*6x ventral
| torpLaunchers = 8 Torpedo Launchers
*4x dorsal
*4x ventral
| torpPayload =
| shields = Graviton Shields
| dockingfacilities =
| shuttleBays =
| shuttles = *Numerous shuttles
*Numerous workerbees
| runabouts = 4
| fighters =
| aux =
| msd =
}}
The '''''Narendra''-class station''' is a mid-sized Federation space station design that draws design inspiration from the likes of the far larger ''[[Canopus Class|Canopus]]'' and [[Spacedock Class|''Spacedock''-class]] stations. Designed to be assembled at manufacturing facilities within the Federation and then shipped in pieces to their final locations, the ''Narendra'' is essentially a kitset station designed for rapid deployment. If parts are in stock and available, a ''Narendra'' can be brought online in a new location in a matter of months, versus the years or decade it may take for a larger facility.


The intention was for a class of station to support Federation and Starfleet interests at a minimal cost in border sectors while not appearing as an escalation of assets to Federation neighbours who may take umbrage with a larger, more capable and fortified station. Not without their teething issues upon initial activation, each ''Narendra'' station has contributed to the success of the next station. Upgrades for the first generation are being considered, though this too is likely in the form of kitset compartments being deployed to expedite the work on site.
=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=


==Layout==
#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
|}


[[File:Narendra2.png|right|thumb|Narendra-class under construction]]The exterior of a ''Narendra''-class is reminiscent of Starfleet's various spacedock classes - a giant mushroom in space. Compared to the similar ''Canopus'', it could be described as only having half the stem. The dorsal and ventral aspects of the station house large antenna farms, allowing the station to act as a regional communications relay and repeater as required. Dedicated shield generators protect the antenna farms from focused attacks.
== 3.1 - Starship Strength ==


Designed for forward deployment, the ''Narendra''-class carries a wide variety of defensive screens and weaponry. The surface of the station is dotted with phaser array strips, torpedo launchers and older phaser banks in certain locations to provide focused firepower to dissuade attacks along prescribed vectors. Due to the size of the station, it is not intended or expected to hold off a dedicated attack, but to dissuade raids and rapid strikes as well as buy enough time for reinforcements to arrive.
# 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.


The central core of the station houses the primary computer cores as well as truck access for vital services up and down the height of the station. Primary cargo lifts are located here as well to transport materials from the cargo bays to wherever they need to go.
{| 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.


This class of station, like many others, is divided into a number of different sections, which take the form of several different bands which house all of the station's facilities of a particular type together.
== 3.2 - Starbase Strength ==


===Operations Section===
# 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.


The topmost levels of the station house the Operations division, typically referred to as Ops. The station's primary command and control functions can be located here as well as offices for the station command staff. Offices and facilities abound for the Starfleet personnel aboard the station to perform their duties. Of note is a large auditorium built into each station, capable of hosting a hundred officers and guests in a single sitting. While a holdover of the original ''Narendra'' design requirements, the auditorium has become standard to the class and can function as a large-scale briefing room to concert hall as required.
{| 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]]||
|}


===Galleria===
== 3.3 - Attached Ships ==


One of the larger sections of the station the galleria functions as the core of station life and commerce, so named because of the twenty massive viewports that offer impressive views of space. Spread over multiple levels, with terraces descending down the levels, and wrapped around the station core, no two gallerias are the same once the stations come online. Vendors and locals alike soon discover that the modular nature of the station is more than amenable to modification across the galleria, by design, and modifications are relatively simple to engage in. Bulkheads in the shopping area can be moved and the terraces shifted with a bit more work.
# 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.
# 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.


This tends to result in a quick fashion that each galleria becomes its own architectural marvel. Restaurants, kiosks, salons, parlours and a variety of shops can and will be found across the galleria as local enterprises take root. Most tend to be representative of the galactic neighbourhood they find themselves in, with encouragement to galactic neighbours to take part in order to help build report and economic ties as well as informal diplomatic channels.
{| class="wikitable"
|+Starbase Attached Ship Options
|[[Aerie Class|Aerie]]
|
|
|
|
|-
|[[Aquarius Class|Aquarius]]
|
|
|
|
|-
|[[Sydney Class|Sydney]]
|
|
|
|
|}


===Sciences Section===
== 3.4 - Requesting Squadron Ships ==


Each ''Narendra'' hosts an array of research laboratories, as befitting any generalist Starfleet station. While not as expansive or well equipped as larger stations or dedicated science stations, their modular nature does mean that over time they can be readjusted as local conditions may require on a more regular basis. Each station does host a sizable stellar cartography installation, combined with the station's long-range sensors and telescopes, to help map new regions and collate information from nearby starships. This area of the station does contain its own communication center for coordinating scientific endeavors, backup computer cores, small lecture halls and secure storage facilities.
# Members must use BFMS to request any Commands under the Squadron system, as was done with previous Command requests.
 
# 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.
===Accommodation Section===
## 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.
Spread across multiple levels is the station's living quarters. Containing hundreds of single-, double-, and family-sized occupancy quarters as well as a handful of diplomatic suites. Recreation centers, game rooms, holosuites, and a small selection of eateries, typically similar to those found on the galleria, can be located in this section of the station. Occupying a large space in the middle, wrapped around the station's support trunk, lies the station's arboretum, a full forty meters in height.
## 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.
=== Docking Section ===
Located on the lowest levels of the upper hull and comprising the widest part of the station is the docking section. There are twelve docking ports capable of supporting starships of nearly any size.
 
===Medical Sections===
 
The medical section of the station contains facilities typically greater than mere starships, but small and ill-equipped compared to larger stations. Six separate infirmaries dominate this section of the station, each equivalent to a large starship, and specializing in its own field of medicine. Counseling offices, wards for a variety of species and isolation facilities accompany cutting edge, at the time of assembly, scientific labs, limited research facilities and cryogenic suspension facilities for cases that can't be resolved on-station. A triage center lies in the heart of the station, with its own dedicated transporter facility and quick access to the primary sickbays. Each sickbay and the triage center all possess their own EMH, though with programming adjusted for their field of work.
 
===Cargo Operations and Hanger Deck===
 
The midline of the station is a cavernous space split into six main bays, or “wedges,” with reinforced support bulkheads dotted with pressure hatches and forcefield backups that enable any of the six wedges to be isolated from the others as needed. The internal configuration of stationary hatches and pass-throughs could allow a small craft to enter one wedge and exit out the opposite side of the station, though this is rarely encouraged in practice given the extensive traffic in and out of the station. The available internal volume of the wedges contains significant space for cargo pallets and shipping containers, short-term and long-term repair bays, propellant stores, warp coil stacks, impulse engine spares, and secured armaments facilities for any armed small craft.
 
===Engineering Complex===
 
The Engineering Complex is located below the midpoint of the station and above the fusion generators. Engineering comprises four large levels and is interconnected via turbolifts, jefferies tubes and humble ladders as required. Engineering contains all the essential services for keeping a ''Narendra''-class operational as well as housing backup computer cores and a hardened auxiliary command center commonly used for damage control but capable of full station control if required.
 
===Fusion Generators===
 
Primary power generation aboard the ''Narendra''-class is achieved by three massive fusion generators located at the bottom of the station. Each generator plant contains four linked fusion reactors that collectively distribute plasma throughout the station. Two of the generator plants are enough to meet the station's power demands which allow for regular rotation in and out of service for maintenance purposes and hardware longevity. Each generation facility can be independently jettisoned from the station in an emergency.
 
== Engineering ==
Because of their modular nature, ''Narendra''-class stations vary widely in terms of their sophistication. The oldest units continue with their original mid-24th century systems, while the newest ones are built to modern specifications. Being modular means that upgrades are relatively easy to accomplish, but given that they are meant to be deployed quickly, they typically do not come stock with the latest and greatest technologies. Rather, they are tried-and-true, well-designed stations that have few peaks and valleys in their capabilities.
 
== Docking and Cargo Facilities ==
While substantially more capable than smaller stations to service starships, ''Narendra''-class stations are not primarily meant to handle starship construction tasks, as this is suited to dedicated shipyards to Spacedock-type facilities. The twelve docking ports they possess allow for large numbers of starships to come and go on a daily basis, however, and they are more than capable of handling light repair tasks or for patching a ship up to give it the spaceworthiness to proceed to a dedicated repair base.
 
== Defensive Capabilities ==
Many of these stations are deployed in contested areas, and so they are intended to defend themselves, but they are not fortresses. Indeed, one of the strategies Starfleet has in mind with this class is that they should avoid attracting undue attention. Weapons systems are mounted in two bands, one under the galleria and another directly above the fusion reactors. Taking a similar approach to other stations, these wide bands of weapons provide comprehensive firepower--as long as threats don't get too close.
 
== Population & Stationboard Life ==
 
== History ==
 
==Gallery==
<gallery widths="200px">
File:Narendra1.png|With visitors
File:Narendra2.png|Galleria on show
File:Narendra3.png|With some not nice visitors
File:Narendra4.png|Narendras come in small packages. Same day delivery with SCE Prime subscription.
</gallery>
 
 
==''Narendra''-class stations In-Play==
*While not the largest or most capable of stations, like the larger [[Canopus_Class|''Canopus'']] or [[Spacedock_Class|''Spacedock'']] facilities, the ''Narendra'' are a comfortable forward deployment designed to support the Federation's interest while not posing as a serious concern to the Federation's neighbours. More than adequate at defending themselves from local raiders or pirates, a serious threat to a ''Narendra'' would best be answered with a fleet garrison until local tensions deescalate.
*They serve as important border hubs for travel and commerce as well as providing essential services to outbound Starfleet vessels. While capable of providing servicing to Starfleet ships, outside of general maintenance it can best be described as sufficient to return to a more capable facility for proper repairs.
*Smaller than the ''Canopus'' facilities, a ''Narendra'' has a regular staff of a few thousand, with a capacity for the same again in regular civilian attendance. In an emergency, ''Narendra'' life support systems can accommodate 15000 people, but to call the situation cramped would be accurate.
 
{{clear}}
[[Category:Federation Space Station Classes]]

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