Bravo Fleet
Difference between pages "Command Policy" and "USS Atlantis"

Difference between pages "Command Policy" and "USS Atlantis"

From Bravo Fleet
(Difference between pages)
 
 
Line 1: Line 1:
{{icons|bfo}}Last Update: 29 March 2023
{{Starship
| name = Atlantis
| prefix = USS
| image = [[File:Sovereign1.png]]
| registry = NCC-90562
| class = Sovereign
| type = explorer
| affiliation = [[Starfleet]]
| status = Active
| commission = 2400
| decommission =
| destroyed =
| unit =
| role = Deterrence Explorer
| taskforce = Task Force 47
| taskgroup = Task Group 13
| squadron =
| mothership =
| homeport =
| co = [[bfms_char:26791|Captain Tikva Theodoras]]
| xo = [[bfms_char:36429|Commander Charles MacIntyre]]
| dedication = [[File:Atlantisplaque.png]]
}}
{{quote|Ad iter te audacter committe.|'''Abandon yourself boldly to the journey. - ''Ship's Dedication Quote'''''}}


=1 - Registry Definition=
'''USS ''Atlantis'' (NCC-90562)''' is one of the newest [[Sovereign Class|''Sovereign''-class]] starships constructed for [[Starfleet]] and assigned to the [[Fourth Fleet]]'s [[Task Force 47]] under the command of [[bfms_char:26791|Captain Tikva Theodoras]]. A product of the [[Beta Antares Shipyard]], she features the latest in technological innovations and systems that have been incorporated into the modern design specifications for ships of her class. With Task Force 47's remit of exploration in the [[Thomar Expanse]], she is well suited to provide tactical support for elements of the task force when required in conjunction with her own exploration duties.
#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]]||[[Intrepid Class|Intrepid]]
|
|-
| ||[[New Orleans Class|New Orleans]]|| colspan="2" |[[Inquiry Class|Inquiry]]
|-
|
|[[Norway Class|Norway]]
| colspan="2" |[[Luna Class|Luna]]
|-
| ||[[Nova Class|Nova]]|| colspan="2" |[[Manticore Class|Manticore]]
|-
| ||[[Olympic Class|Olympic]]|| colspan="2" |[[Nebula Class|Nebula]]
|-
| ||[[Parliament Class|Parliament]]|| colspan="2" |[[Pathfinder Class|Pathfinder]]
|-
|
|[[Reliant Class|Reliant]]
| colspan="2" |[[Prometheus Class|Prometheus]]
|-
| ||[[Saber Class|Saber]]|| colspan="2" |[[Rhode Island Class|Rhode Island]]
|-
| ||[[Springfield Class|Springfield]]|| colspan="2" |[[Sutherland Class|Sutherland]]
|-
| ||[[Steamrunner Class|Steamrunner]]
|}
=3 - Squadrons=


#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.
==Design and Layout==
#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.
While a modern built starship, the latest starship to bear the name ''Atlantis'' maintains design elements and aesthetics of the trends popular during the ''Sovereign''-class's original design period. Her modern functionality exists just under a veneer of twenty-year-old design sensibilities, giving the ship a built-in classic feel.
##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
|}


== 3.1 - Starship Strength ==
''Atlantis'' was originally laid down in 2397 at the Beta Antares Shipyard with nothing more than a registry number to her when construction started on the vessel. By mid-2398 progress was ahead of schedule, however a handful of technological innovations, newer and smaller ship designs and resource limitations to meet other objectives delayed further construction work on hull number NCC-90562. While progress continued, it was of a much slower pace and limited to key infrastructure components of the ship that would not be changing.


# Ship classes are allocated a certain level of Strength depending on their size, power, modernity, and so forth.
The delays did mean that when work resumed newer computer systems, data transfer lines, and improved shield and weapons systems were eventually implemented into the starship, bringing her up to modern specifications that a handful of other ''Sovereigns'' only a few years old would be facing months in refit to receive, though operational pressures would mean these refits would be years down the road.
# 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 (As above in 2 - Primary Commands) may not directly correlate with a starship's squadron strength. This is intentional, reflecting how some ships may be more or less popular when they are a member's only command, but valued differently when part of a larger squadron.


{| class="wikitable" style="margin:auto"
Originally planned to be christened the USS ''T'Rhan'', named after an ancient Vulcan philosopher on the concept of 'minimal applied force for maximal gain', who advocated that the concept of martial strength in the mind of your enemy could be just as effective as possessing that martial strength. In early 2400, weeks prior to the ship's official commissioning, the vessel's name was formally changed by order of Starfleet Command to ''Atlantis'' to replace the [[Argonaut Class|''Argonaut''-class]] [[USS_Atlantis_(NCC-81424)|''Atlantis'']] that had been decommissioned due to its status as a relic of import to the Federation Science Council.
|+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.


== 3.2 - Starbase Strength ==
===Bridge===
[[File:AtlantisBridge1.jpg|left|thumb|Bridge of the USS ''Atlantis'']]Her primary bridge has taken lessons learned from the original [[Sovereign Class]] starships and made valuable improvements to remedy early teething issues with workspace and workflow design. In a throwback to another prior generation, the arch behind the command seats replaces separate free-floating consoles to the rear and either side of the centre seats that had been first introduced on the early ships of the class. This removal of obstacles and centralisation of the primary Tactical station opened up the bridge, giving it an easier flow and roomier feel.


# 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 {{year}}.
With further enhancements to key systems and movement of components elsewhere within the bridge module, space to the rear of the bridge has been made available to dedicate the volume to an expanded missions operations area. This multi-function space can be repurposed for any given task or situation, allowing for enhanced responsiveness and collaboration between on-duty department heads and command staff.
# 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.


{| class="wikitable" style="margin:auto"
Normally this space remains configured for systems oversight and damage control, with the primary monitor defaulting to a Multifunction System Display, but as with all large monitors aboard the ship, can be quickly reconfigured for a variety of tasks. It would not be uncommon during long transits for this space to be repurposed for survey work or control of the ship while the bridge itself might be used for simulation training of junior officers. Flight operations, crisis management, scientific research and many other pursuits can and will find themselves here at some point.
|+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]]||
|}


== 3.3 - Attached Ships ==
<div align="center"><ul>
<li style="display: inline-block;"> [[File:AtlantisBridge2.jpg|left|thumb|The Arch and expanded mission operations area]] </li>
<li style="display: inline-block;"> [[File:AtlantisBridge3.jpg|left|thumb|Missions Operations and MSD]] </li>
</ul></div>


# 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.
===The Captain's Mess===
# 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.
[[File:Captainsmess.png|thumb|right|The Captain's Mess]]Compartment Deck Five Forward was by original design set aside as the captain's mess aboard ''Atlantis''. Within quick succession, the compartment and two smaller adjacent ones were redesigned to give the senior officers of the ship a relaxed social space that wasn't the ship's main lounge. Never a terribly populated locale, as interaction with the crew as a whole is encouraged, it does serve as a nice retreat whenever needed.
# 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.


{| class="wikitable"
While typically the purview of the command staff, department heads and their assistants, from time to time junior officers and crew members are invited to The Captain's Mess as an informal recognition, extended by either the captain or their department head. This would coincide with the presence of whoever extended the invitation, so turning down a chance to sit with the captain or a senior officer for drinks in a lounge with restricted access is not an invitation lightly turned down.
|+Starbase Attached Ship Options
|[[Aerie Class|Aerie]]
|
|
|
|
|-
|[[Aquarius Class|Aquarius]]
|
|
|
|
|-
|[[Sydney Class|Sydney]]
|
|
|
|
|}


== 3.4 - Requesting Squadron Ships ==
===The Keys===
The Keys are ''Atlantis''' first new totem. Replicated as a joke by Commander MacIntyre prior to the ship's commissioning, they are a simple set of three keys, purpose yet to be clarified, accompanied by a Starfleet delta. They've been adopted by the crew as the unofficial symbol of the watch, changing hands each shift or whenever control of the conn changes.


# Members must use BFMS to request any Commands under the Squadron system, in the same manner as Command requests at the ranks of Lieutenant Commander or Commander.
It is commonly accepted that the keys should never leave the bridge proper, not even to the captain's ready room. Rumours and dire predictions have circulated around the ship about what would happen in such a situation, from the breakdown of the ship to a sudden warp core detonation. Luckily for the more rational members of the crew, nothing bad has come of the multiple situations wherein senior officers have discovered they'd left the bridge without handing over the keys.
# 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.
 
## 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.
==Operational History==
## 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.
Commissioned into service on March 3rd, 2400, USS ''Atlantis'' slipped her moorings to begin her shakedown cruise. Systems integration, weapons test and engine performance evaluations were expected plans for the ship's first few months in space to ensure that the vessel was performing as designed, constructed and expected. These operational goals were quickly superseded by developments within the Romulan Star Empire and ''Atlantis'' found herself deployed to assist in the matter despite her new and untested condition.
## 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.
===Sundered Wings===
=4 - Fictions=
<pre>
#Stories about alternative settings such as non-Starfleet ships or historic eras are called 'Fictions'. Like primary or squadron commands and RPGs, they have their own BFMS Command page and are held to the same standards in content and canon compliancy.
!!!Error!!!
#Fictions may only be written by one individual member. Stories with multiple writers count as role-playing games, which fall under the purview of the Operations Department.
Access to log summaries of ongoing events is not possible at this time. Please consult unabridged logs and recordings available at your access level.
#A member who has reached the rank of Commander may submit a fiction proposal to the Intelligence Office. This is not necessary for fiction based on their Primary Command.
If you are seeing this error message and believe it is in error, please consult with Starfleet Operations to confirm your security clearance and access permissions.
#The proposal should explain the premise of the story, a loose estimation of expected length, and what it contributes to Bravo Fleet canon, present or historic. It should include a broad activity commitment, such as '1 Story posted per month.' This is not a binding agreement, but helps the Intelligence Office identify inactive Fictions.
Thank you,
#Starfleet ships in the year {{year}} are not an appropriate setting for Fictions. Members should use their Primary or Squadron Commands for these.
Starfleet Operations
# Fictions do not draw from ships in the Bravo Fleet Registry, and so should discuss their ship, station, or concept needs with the Intelligence Office so an appropriate entry can be created.
</pre>
#Fictions not set in {{Year}} should ''not'' draw from ships in the Bravo Fleet Registry. Members are subject to the same rank-based restrictions of classes (for example, a Commander writing a fiction set in 2375 still cannot request a Sovereign-class), but of course can request era-appropriate ship classes not listed in the registry.
 
# A new fiction will have its own Command on BFMS, assigned to the member. This Command is for use solely within the bounds of the accepted fiction proposal, and must not be used as a Primary Command.
==Notable Crew==
# Bravo Fleet fiction supports and enriches Bravo Fleet Canon, present and historic. Proposals from non-Trek settings will be rejected. Proposals from alternate universes of Star Trek will need to demonstrate their relevance to Bravo Fleet Canon content, themes, or characters to be accepted.
{{For|article=[[User:McGig/Atlantis/Atlantis_Full_Crew|''Atlantis'' Full Roster]]}}
===Commanding Officers===
*[https://bravofleet.com/command/34883 2400 - Present] : [[bfms_char:26791|Captain Tikva Theodoras]]
 
==Support Craft==
[[File:Harpyflight.png|thumb|350px|right|'''Semper Potest''' - Always Able]]
====[[Personnel_Shuttles#Type_12_Shuttle|Type 12 Shuttles]]====
''Kos'', ''Icaria'', ''Kea'', ''Ithaca'', ''Salamis''
====[[Personnel_Shuttles#Type-11_Shuttle|Type 11 Shuttles]]====
''Waihou'', ''Lesbos''
====[[Runabouts#Danube-class_runabout|''Danube''-class Runabouts]]====
''Gondwana'', ''Laurentia'', ''Pangea'', ''Rodinia''
====[[Starfighters#Valkyrie-class_fighter|''Valkyrie''-class Starfighters]]====
While the ''Valkyrie''-class fighters assigned to ''Atlantis'' have all been named, they conform to the Harpy flight callsigns on duty.
 
*''Samos''
**Harpy 1
*''Corfu''
**Harpy 3
*''Karpathos''
**Harpy 3
 
Harpy 2, ''Corfu'', has been modified from a standard A variant to an attack/recon (A/R) model. While the attack variant carried multiple micro-torpedoes aboard in small magazines, the A/R only carried 2, one per launcher. The magazine space is then given over to housing more specialised and sophisticated sensors and ECM hardware. These sensors are incredibly sensitive and capable in a very narrow observational window forward of the craft, allowing for superior long-range reconnaissance of known targets, but are incredibly poor at generalised scouting.
 
Equally the ECM hardware, while incredibly capable, has a limited field of effect and was ideally designed to cover the craft it is fitted on only. Skilled or reckless pilots are able to make use of the field to hide a few other fighters in close proximity, but exposure would put an entire flight at risk and is highly discouraged.
 
{{clear}}
 
==Hazard Team==
[[File:AtlantisHazard.png|thumb|350px|right|Fighting Myrmidons]]The Hazard team aboard ''Atlantis'' is a 15 entity operation split into three operational teams. Gold and Silver Teams are the primary fighting force for the Fighting Myrmidons, with Bronze Team acting as a combat support role. As such Gold and Silver are primarily security officers with an attached medic while Bronze is a composite Engineering, Science and Medical team with an attached security officer.
 
Inclusion in the Hazard team is not limited to Security personnel but is open to all aboard the ship who wish to apply and can meet the Chief of Security's rigorous combat proficiency requirements. In addition to existing duty requirements, training primarily revolves around extensive holodeck training and rotating training teams to allow for optimal flexibility based on crew availability at any given time. The stated goal is to attempt to develop the Myrmidons to be able to fight without needing to communicate between each other as much as possible.
 
{{clear}}

Revision as of 07:48, 11 April 2023

Sovereign1.png
USS Atlantis
General Information
Registry NCC-90562
Class & Type Sovereign-class explorer
Affiliation Starfleet
Status Active
Commissioned 2400
Assignment
Task Force Task Force 47
Task Group Task Group 13
Role Deterrence Explorer
Key Personnel
Commanding Officer Captain Tikva Theodoras
Executive Officer Commander Charles MacIntyre
Atlantisplaque.png
Template:Starship
"Ad iter te audacter committe."
    —Abandon yourself boldly to the journey. - Ship's Dedication Quote


USS Atlantis (NCC-90562) is one of the newest Sovereign-class starships constructed for Starfleet and assigned to the Fourth Fleet's Task Force 47 under the command of Captain Tikva Theodoras. A product of the Beta Antares Shipyard, she features the latest in technological innovations and systems that have been incorporated into the modern design specifications for ships of her class. With Task Force 47's remit of exploration in the Thomar Expanse, she is well suited to provide tactical support for elements of the task force when required in conjunction with her own exploration duties.

Design and Layout

While a modern built starship, the latest starship to bear the name Atlantis maintains design elements and aesthetics of the trends popular during the Sovereign-class's original design period. Her modern functionality exists just under a veneer of twenty-year-old design sensibilities, giving the ship a built-in classic feel.

Atlantis was originally laid down in 2397 at the Beta Antares Shipyard with nothing more than a registry number to her when construction started on the vessel. By mid-2398 progress was ahead of schedule, however a handful of technological innovations, newer and smaller ship designs and resource limitations to meet other objectives delayed further construction work on hull number NCC-90562. While progress continued, it was of a much slower pace and limited to key infrastructure components of the ship that would not be changing.

The delays did mean that when work resumed newer computer systems, data transfer lines, and improved shield and weapons systems were eventually implemented into the starship, bringing her up to modern specifications that a handful of other Sovereigns only a few years old would be facing months in refit to receive, though operational pressures would mean these refits would be years down the road.

Originally planned to be christened the USS T'Rhan, named after an ancient Vulcan philosopher on the concept of 'minimal applied force for maximal gain', who advocated that the concept of martial strength in the mind of your enemy could be just as effective as possessing that martial strength. In early 2400, weeks prior to the ship's official commissioning, the vessel's name was formally changed by order of Starfleet Command to Atlantis to replace the Argonaut-class Atlantis that had been decommissioned due to its status as a relic of import to the Federation Science Council.

Bridge

Bridge of the USS Atlantis

Her primary bridge has taken lessons learned from the original Sovereign Class starships and made valuable improvements to remedy early teething issues with workspace and workflow design. In a throwback to another prior generation, the arch behind the command seats replaces separate free-floating consoles to the rear and either side of the centre seats that had been first introduced on the early ships of the class. This removal of obstacles and centralisation of the primary Tactical station opened up the bridge, giving it an easier flow and roomier feel.

With further enhancements to key systems and movement of components elsewhere within the bridge module, space to the rear of the bridge has been made available to dedicate the volume to an expanded missions operations area. This multi-function space can be repurposed for any given task or situation, allowing for enhanced responsiveness and collaboration between on-duty department heads and command staff.

Normally this space remains configured for systems oversight and damage control, with the primary monitor defaulting to a Multifunction System Display, but as with all large monitors aboard the ship, can be quickly reconfigured for a variety of tasks. It would not be uncommon during long transits for this space to be repurposed for survey work or control of the ship while the bridge itself might be used for simulation training of junior officers. Flight operations, crisis management, scientific research and many other pursuits can and will find themselves here at some point.

  • The Arch and expanded mission operations area
  • Missions Operations and MSD

The Captain's Mess

The Captain's Mess

Compartment Deck Five Forward was by original design set aside as the captain's mess aboard Atlantis. Within quick succession, the compartment and two smaller adjacent ones were redesigned to give the senior officers of the ship a relaxed social space that wasn't the ship's main lounge. Never a terribly populated locale, as interaction with the crew as a whole is encouraged, it does serve as a nice retreat whenever needed.

While typically the purview of the command staff, department heads and their assistants, from time to time junior officers and crew members are invited to The Captain's Mess as an informal recognition, extended by either the captain or their department head. This would coincide with the presence of whoever extended the invitation, so turning down a chance to sit with the captain or a senior officer for drinks in a lounge with restricted access is not an invitation lightly turned down.

The Keys

The Keys are Atlantis' first new totem. Replicated as a joke by Commander MacIntyre prior to the ship's commissioning, they are a simple set of three keys, purpose yet to be clarified, accompanied by a Starfleet delta. They've been adopted by the crew as the unofficial symbol of the watch, changing hands each shift or whenever control of the conn changes.

It is commonly accepted that the keys should never leave the bridge proper, not even to the captain's ready room. Rumours and dire predictions have circulated around the ship about what would happen in such a situation, from the breakdown of the ship to a sudden warp core detonation. Luckily for the more rational members of the crew, nothing bad has come of the multiple situations wherein senior officers have discovered they'd left the bridge without handing over the keys.

Operational History

Commissioned into service on March 3rd, 2400, USS Atlantis slipped her moorings to begin her shakedown cruise. Systems integration, weapons test and engine performance evaluations were expected plans for the ship's first few months in space to ensure that the vessel was performing as designed, constructed and expected. These operational goals were quickly superseded by developments within the Romulan Star Empire and Atlantis found herself deployed to assist in the matter despite her new and untested condition.

Sundered Wings

!!!Error!!!
Access to log summaries of ongoing events is not possible at this time. Please consult unabridged logs and recordings available at your access level.
If you are seeing this error message and believe it is in error, please consult with Starfleet Operations to confirm your security clearance and access permissions.
Thank you,
Starfleet Operations

Notable Crew

Disambiguation.svgFor the article, see Atlantis Full Roster.

Commanding Officers

Support Craft

Semper Potest - Always Able

Type 12 Shuttles

Kos, Icaria, Kea, Ithaca, Salamis

Type 11 Shuttles

Waihou, Lesbos

Danube-class Runabouts

Gondwana, Laurentia, Pangea, Rodinia

Valkyrie-class Starfighters

While the Valkyrie-class fighters assigned to Atlantis have all been named, they conform to the Harpy flight callsigns on duty.

  • Samos
    • Harpy 1
  • Corfu
    • Harpy 3
  • Karpathos
    • Harpy 3

Harpy 2, Corfu, has been modified from a standard A variant to an attack/recon (A/R) model. While the attack variant carried multiple micro-torpedoes aboard in small magazines, the A/R only carried 2, one per launcher. The magazine space is then given over to housing more specialised and sophisticated sensors and ECM hardware. These sensors are incredibly sensitive and capable in a very narrow observational window forward of the craft, allowing for superior long-range reconnaissance of known targets, but are incredibly poor at generalised scouting.

Equally the ECM hardware, while incredibly capable, has a limited field of effect and was ideally designed to cover the craft it is fitted on only. Skilled or reckless pilots are able to make use of the field to hide a few other fighters in close proximity, but exposure would put an entire flight at risk and is highly discouraged.


Hazard Team

Fighting Myrmidons

The Hazard team aboard Atlantis is a 15 entity operation split into three operational teams. Gold and Silver Teams are the primary fighting force for the Fighting Myrmidons, with Bronze Team acting as a combat support role. As such Gold and Silver are primarily security officers with an attached medic while Bronze is a composite Engineering, Science and Medical team with an attached security officer.

Inclusion in the Hazard team is not limited to Security personnel but is open to all aboard the ship who wish to apply and can meet the Chief of Security's rigorous combat proficiency requirements. In addition to existing duty requirements, training primarily revolves around extensive holodeck training and rotating training teams to allow for optimal flexibility based on crew availability at any given time. The stated goal is to attempt to develop the Myrmidons to be able to fight without needing to communicate between each other as much as possible.

Retrieved from "https://wiki.bravofleet.com/index.php?title=Command_Policy&oldid=9108"