Bravo Fleet
Difference between pages "Intelligence Office Policy" and "USS Thyanis"

Difference between pages "Intelligence Office Policy" and "USS Thyanis"

From Bravo Fleet
(Difference between pages)
 
 
Line 1: Line 1:
{{icons|bfo}}
{{Starship
== Canon Policy ==
| name = Thyanis
Last Update: February 22 2022
| prefix = USS
| image = [[File:AerieClass.jpg]]
| registry = NCC-88019
| class = Raven
| type = Corvette
| affiliation = [[Starfleet]]
| status = Active
| commission = 2389
| decommission =
| destroyed =
| taskforce = Task Force 93
| taskgroup = Task Group 44
| role = Multi-Role
| co = [[bfms char:77255|Lieutenant Commander Wallace Jones]]
| xo = [[bfms char:77347|Lieutenant Commander Harris Tan]]
}}
The '''USS ''Thyanis''''' is a [[Raven Class|''Raven''-class]] corvette assigned to [[Fourth Fleet]].


=== Section 1 - Fleet Canon ===
===Mission History===
====Early Encounters (2400-2400)====
The earliest encounters of the ''Thyanis'' in the former Romulan Neutral Zone were mostly involving dealing with folks affected by the disruption caused following the fall of the [[Romulan Star Empire]]. As captain of the ship, Kurios and his XO engaged in establishing trade, and helped to resolve issues of malnutrition and disease among several colonies throughout the region. As a part of [[Task Force 93]], this fell well within both the skills of the [[Starfleet]] doctor and within the parameters set by the [[Fourth Fleet]]'s chain of command.


==== Section 1.1 - Defining Fleet Canon ====
==== Refit (2400-2401) ====
Following the departure of Commander Thevius; ''Thyanis'' was returned to Starbase Bravo for minor re-fit. Being a small vessel with little tactical significance, she remained berthed as a reserve ship for nearly a year until she was assigned a new crew and captain at the start of March 2401.


* Bravo Fleet Canon comes from two sources: on-screen Star Trek (defined as official Star Trek films and television programs) storytelling and original canon developed within Bravo Fleet.
The nature of her refit was only minor, involving updating many of the standard systems aboard the vessel and returning her to a standard configuration for a multi-role mission profile.
* Everything in Star Trek on-screen canon is considered canon to Bravo Fleet. If on-screen sources directly contradict each other, the more recent source, measured by air date, takes precedence.
* Original Bravo Fleet Canon consists of material created specifically for Bravo Fleet. This content has been explicitly created or ratified by the Lore Office. Bravo Fleet Canon will be recorded on the wiki in '''articles containing the Bravo Fleet Canon icon''' (usually in the top-right of the page). Articles that do not contain that icon are Member Canon (see Section 1.3) and should be used accordingly. The icon is a miniaturised version of the Bravo Fleet logo, as below (other icons refer solely to categorisation, and have no bearing on an article's status in Fleet Canon):[[File:Canonicon.png|center|frameless|alt=]]


* Sources other than on-screen canon and original Bravo Fleet Canon are not considered canon within Bravo Fleet, though they can be used as inspiration. Novels, production notes, published technical manuals, video games, and all other non-screen Star Trek content are not canon to Bravo Fleet.
=== Deneb Sector Crisis (2401) ===
* If new on-screen canon contradicts established Bravo Fleet Canon, the Bravo Fleet Canon will be re-written or retconned to comply.
In March 2401 Lieutenant Commander Wallace Jones assumed command of the ''USS Thyanis'' immediately following the outbreak of the Dominion crisis in the [[Deneb Sector|Deneb sector]].
* Individual games and fictions are required to follow Bravo Fleet Canon; their stories may involve new additions but must not contradict or deviate from Bravo Fleet Canon. Bravo Fleet is a cooperative writing group, and its strength comes from bringing people together to tell stories.
* The canon and Canon Policy apply to historical games and fictions. They are part of the shared universe of the Bravo Fleet Canon, set in different eras.
* Games and fictions set in alternate realities or non-Trek settings have no relation to the Bravo Fleet Canon, and each exists within a unique setting in adherence to their original game or fiction proposal.


==== Section 1.2 - Creating Fleet Canon ====
===== Oppenheimer Station =====
''Thyanis'' first assignment was to investigate [[Oppenheimer Station|Oppenheimer Research Outpost]] in the Gamma Cronae Borealis system. The station failed to respond to the evacuation order and Starfleet Intelligence requested that a vessel be immediately dispatched.


* All additions to Fleet Canon must be ratified by the Lore Office. Until that point, content should be considered Member Canon (see Section 1.3).
With most of the 4th fleet engaged on the front line, ''Thyanis'' was assigned this mission out of operational necessity
* Significant changes to Task Force stories must be approved by the Loremaster.
* New non-canon Federation member species must be approved by the Loremaster.
* New minor foreign powers with regional influence must be approved by the Loremaster.
* Significant development to on-screen species or cultures (ie, facts which anyone writing them would likely need to know) must be approved by the Loremaster.
* New Starfleet starship, space station, and small craft classes and specifications must be approved by the Loremaster. Likewise new Klingon, Romulan, or Cardassian starships.
* No addition to Bravo Fleet canon is considered official until it has completed all approval requirements and been added to the Bravo Fleet wiki in a format that provides complete, usable information that others may build on. These articles will be clearly identified as Bravo Fleet canon as per Section 1.1.


==== Section 1.3 - Member Canon ====
===== Voyage to Deneb Sector =====
During her voyage to the Deneb Sector the ''USS'' ''Thyanis'' was attacked by a Breen Plesh Tral Raider near the galactic Northern border of the Ferengi Alliance A short skirmish ensued which resulted in the death of one crewmember and life changing injuries to another, ''Thyanis also'' received significant damage.


* Content that has not been explicitly ratified by the Lore Office is considered Member Canon. This includes character biographies and the events of fiction plots and game missions unless they meet the above criteria.
Here ''Thyanis'' first encountered a Ferengi vessel commanded by Daimon Tal. The Daimon approached the ''Thyanis'' crew with a proposition as a front to covertly gather data and information on the ''Thyanis's'' destination.
* Member Canon is binding only to the stories and games in which it appears. Storytellers, Game Masters, and writers of other fictions and games are not obligated to adhere to these details, worldbuilding, or plot developments.
* The status of Member Canon is not a value judgement or reflection of quality. With so many stories and games over many years, it is not realistic for all their details to be known to all members, or to have been reviewed by the Lore Office. Likewise, with many distinct personal tastes and creative preferences, the existence of Member Canon allows writers with diverging interests to co-exist within the Fleet.
* Member Canon may be added to the wiki, particularly on a starship’s article or, for example, adding worlds or locations to a region other creators may choose to draw on for their own writing. Such articles will not include the Bravo Fleet Canon icon and should be treated as optional content to draw on.
* The nature of Member Canon necessitates limitations to its scope. Section 1.2 provides guidelines on the level at which the Lore Office’s ratification is needed, and Member Canon should not meet or exceed that level. Member Canon should be considered equivalent to the details of a standalone episode of The Next Generation, while Fleet Canon is comparable to a major story arc episode of Deep Space Nine with galactic ramifications. Some examples of the acceptable scale of Member Canon include:
** A colony world of a canonical Federation member, such as humans or Andorians.
** A starship captain of another major power, be they ally or enemy.
** A stellar phenomenon with local effect.
** If you are unsure of the scope of your story detail, please contact the Lore Office for advice. A rule of thumb is, ‘Is this essential knowledge for any Bravo Fleet creator writing in this topic/location?’ and remember that the galaxy is a big place.
* Member Canon should not include characters or ships from Star Trek Canon, such as the USS Enterprise or Admiral Kathryn Janeway. References to them should use recent Star Trek Canon (such as Star Trek: Picard) or, where extant, Fleet Canon. For example:
** We do not know the present status of Benjamin Sisko. Avoid mentioning his current circumstances at all.
** We do not know the specific status of Deep Space Nine; its design, its crew, its captain. It is reasonable to mention the existence of DS9, with its key position at the mouth of the wormhole, but do not go into details.
** Characters should not be an old friend, protégé, relative, etc, of any character in Star Trek Canon.
** Characters should not share a full name (or name they are known by) with canonical characters (for example: ‘John Reed’ would be an acceptable character name, but ‘Willard “Will” Riker’ would not be).
* Contradictions in Member Canon are expected, and tolerance is encouraged, especially if they occur within separate stories. If this is impossible, such as within a collaborative fiction, it is best to justify the co-existence of such details or reach a compromise. Should such again be impossible, contact the Lore Office for a judgement.
* Strong and interesting ideas that flesh out the setting may be adopted by the Lore Office into Fleet Canon. This will occur at the Lore Office’s discretion.


=== Section 2 - Timeline ===
After returning to Farpoint Station for repairs, ''Thyanis'' continued her journey to her destination without incident.
The Bravo Fleet timeline advances one year for every two years that pass. The in-character year will advance on January 1 of each even-numbered year. The timeline may be advanced immediately by the Bravo Fleet Loremaster.


=== Section 3 - Bravo Fleet Wiki ===
===== '''Arrival at Oppenheimer Station''' =====
On arrival at Oppenheimer Research outpost, ''Thyanis'' attempted to beam a small away team onto the station. The transport was aborted when it was discovered that the station was housing a Quantum singularity that had the potential to interfere with the transporter process and nearly cost the lives of the away team.


* The wiki will be maintained by the Lore Office.
A follow up away mission was carried out with the aid of a shuttle, led by the ''Thyanis'' X.O. Lt Commander Harris Tan
* All members may contribute to the Bravo Fleet Wiki, making additions in adherence to the definitions of Fleet canon in Section 1.
* Articles that are part of Bravo Fleet Canon will be clearly labeled confirming their content has been approved by the Lore Office.
* Articles not labeled should refer to a game or fiction’s personal canon and must remain small-scale story elements in adherence to Section 1. Bravo Fleet members may choose but are not bound to adhere to this content.
* Content on the wiki is In Character unless specified otherwise.


=== Section 4 - Fiction ===
At about the same time, the Ferengi Vessel commanded by Daimon Tal approached the station. ''Thyanis'' attempted to warn them of the danger but their actions were seen as aggressive and ''Thyanis'' took significant damage when the Ferengi retaliated.


==== Section 4.1 - Defining Fictions ====
Meanwhile on the station, the away team discovered bodies of the Jem'Hadar in advanced stages of decomposition. After shutting down and examining the energy device containing the Quantum Singularity, it was determined that the Jem'Hadar had died as a result of the relativistic effects from the unstable singularity.


* Fictions are stories written by individual members that take place within Fleet canon. Stories with multiple writers count as role-playing games, which fall under the purview of the Operations Department.
As the singularity was shut down, Daimon Tal boarded the station, killed a ''Thyanis'' crew member and kidnapped Dr Molly Xan and - the ''Thyanis'' Chief Medical officer and Dr Sutherland - Chief scientist aboard the station; all whilst stealing the energy device itself.
* Fiction is written on BFMS or linked to from a Command’s page on BFMS.
** Each Task Force’s Headquarters is a Command on BFMS. While any Task Force member may write a Story there, its major purpose is for members under the rank of Lieutenant Commander to write in accordance with the guidelines on the Command page. This writing is free-form and offers members a venue to express themselves and participate in fleet canon before they have their own ship.
** A member who has reached the rank of Lieutenant Commander with an Primary Command of their own (as per Section 5.2 below) may write fiction set within fleet canon based around this starship.
** Other fiction may be written after a submitted proposal is accepted by the Lore Office.


==== Section 4.2 - Fiction Proposals ====
==== '''Ferengi Pursuit''' ====
The ''Thyanis'' crew worked desperately to push the ship to its absolute limit in pursuit of the Ferengi Vessel, that was heading for a region of space plagued by subspace instability and a nebula like phenomena. After nearly tearing the ship apart flying well beyond her maximum rated warp speed; ''Thyanis'' successfully kept pace with the Ferengi and were able to maintain pursuit.


* A member who has reached the rank of Commander may submit a fiction proposal to the Lore Office. This is not necessary for fiction based on their Primary Command.
===== '''Battle with the Dominion''' =====
* 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 Lore Office identify inactive fictions.
The disruption to sensors, shields and energy weapons caused by the anomalous region forced the ''Thyanis'' to adopt 20th century tactics to navigate the anomaly and locate Daimon Tal's ship. Using a modified deflector pulse designed to emit Tachyons, ''Thyanis'' soon caught up with the Ferengi, only to encounter a Jem'Hadar Battleship in the process.
* Proposals for fictions set on Starfleet ships in {{Year}} must be sufficiently original or distinctive to justify why the story cannot be written on a member's Primary Command which, as above, do not require a proposal submission.
* Fictions set in {{Year}} must draw from ships in the Bravo Fleet Registry (see Section 5) and are subject to the same rank-based restrictions of ship classes. Fictions not using Starfleet ships should discuss their ship, station, or concept needs with the Lore Office so an appropriate registry entry can be created.
* 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 Lieutenant 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 (see 5.2 below).
* 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.


=== Section 5 - Registry ===
Meanwhile, During a showdown between the ''Thyanis'' C.O. - Wallace Jones and Daimon Tal - it was revealed that Tal had been replaced by a Changeling, who was plotting to re-engineer the stolen energy device as a devastating weapon - a Black hole Bomb. The changeling was defeated (but not killed) with the combined effort of the ''Thyanis'' away team however the energy device had already been delivered to the Dominion ship.


==== Section 5.1 - Registry Definition ====
At the same time ''Thyanis'' became locked in a deadly battle with the Dominion vessel. Completely out-classed and out gunned, the ''Thyanis'' X.O. Harris Tan devised a tactic that would later become known as '''The Tan Manoeuvre''<nowiki/>' to cripple the Dominion vessel. Taking inspiration from 20th century fighter weapons tactics, the crew modified several Photon torpedo's to act with delayed autonomous guidance on the same principle as the Tachyon pulse the ship had been using to find the Ferengi.


* The registry lists all starships, starbases, and other entities available to Bravo Fleet for use as Commands or Games.
The resulting damage caused to the Dominion vessel detonated the energy device on board, which was in the process of powering up for a test fire. This detonation allowed the singularity contained within to become self sustaining and this then evolved into a stellar mass black hole.
* 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 Lore 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. Events involving registry ships prior to {{Year}} may be referenced in circumstances such as character service records and backstory. 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.


==== Section 5.2 - Primary Commands (Starships and Auxiliary Craft) ====
As the Black hole began consuming the surrounding matter in the region, ''Thyanis'' rescued the survivors on board the Ferengi ship and her away team before departing for Farpoint station to conclude her mission.


* 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}}.
===Crew Complement===
* Members can write on their Primary Command 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 Lore 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.
The maximum crew of the ''Thyanis'' is only 20 strong, and as such the needs and the abilities of the crew are both affected. The crew has a greater focus on the medical and engineering careers, with only a handful of Starfleet officers specializing in particular fields. Many of the crew are of lower ranks to the point that a former captain, Ensign Kurios, once called it a "can of Ensigns". This quip was a mild misnomer however, as at least a quarter of the crew were cadets or crewman.
* When a member reaches the rank of Ensign they may request a ship on the registry for use as their Primary Command. Ship classes available are restricted by rank:
** At Ensign, a member shall have access to the following auxiliary craft classes: Raven.
** At Lieutenant Commander, a member shall have access to the following starship classes: Ambassador, Aquarius, Argonaut, California, Centaur, Challenger, Cheyenne, Diligent, Excelsior, Freedom, Grissom, New Orleans, Norway, Nova, Parliament, Reliant, Saber, Springfield, Steamrunner.
** At Commander, a member shall have access to all classes available at Lieutenant Commander as well as the following: Akira, Defiant, Elysion, Inquiry, Intrepid, Luna, Nebula, Olympic, Resolute, Rhode Island.
** At Captain, a member shall have access to all classes available at Lieutenant Commander and Commander, as well as the following: Century, Galaxy, Manticore, Obena, Odyssey, Prometheus, Sovereign, Typhon, Vesta.
* Members 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. This includes any member 'upgrading' from a Raven-class to a starship command at Lieutenant Commander.
* Primary Commands will be removed from a member's dossier upon transfer to the Reserves.


==== Section 5.3 - Primary Commands (Starbases) ====
Interestingly, despite being a ship providing humanitarian support to the former Romulan Neutral Zone, the crew itself could easily find itself in the care of only a old [https://memory-alpha.fandom.com/wiki/Emergency_Medical_Holographic_programs#EMH_Mark_I first generation EMH]. This was considered a bit grim, given the antiquated unit was already being phased out back in [https://memory-alpha.fandom.com/wiki/2374 2374]. As such, it was taken as a bit of black humour among some of the crew that nobody should get injured unless they wanted to be 'walking dead'. The attitude was not helped with the tendency of her captain to be involved in away missions or otherwise be indisposed.


* Starbases as an Primary Command work the same as starships, but are subject to different requirements. They represent starbases assigned In Character to the member’s Task Force in the Fourth Fleet in {{Year}}.
===Vessel Configuration===
* When a member reaches the rank of Commander they may request a starbase from the registry for use as their Primary Command. This is instead of a starship, not in addition to.
The current configuration of the ''Thyanis'' is standard for its class. In the past she had been fitted with a slightly more well equipped sick bay to assist her mission profile but this was replaced by its standard configuration to allow the vessel to align to its multi-role profile in 2401. No particular compartment is favoured over another and while she is equipped with two generalist science labs, these facilities can be used simultaneously for different purposes. For example: Science lab 1 can be configured for astronomical survey's where as Science lab 2 can be configured for medical research.
* Registry Starbases are created by the Lore Office, and will have their own wiki article explaining the location and setting material relevant to that starbase that has been ratified by the Lore Office. This is Fleet Canon that cannot be altered without permission of the Lore 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 Lore Office.
* Starbase classes available are restricted by rank.
** At Commander, a member shall have access to the following starbase classes: Jupiter, K-Type, Regula, Vision.
** At Captain, a member shall have access to all starbase classes available at Commander, as well as the following: Anchorage, Copernicus, Presidium, Watchtower.
** At Fleet Captain, a member shall have access to all starbase classes available at Commander and Captain, as well as the following: Canopus, Unity.
* As a Starbase Command is attached to a member’s dossier instead of a starship, the starbase as-standard has no attached starships and must make use of runabouts and shuttles on away missions.
** At the rank of Captain, a member may request a starship from the registry to be attached to their dossier as their starbase’s attached ship. This is a more restricted selection of starship classes: Aquarius, Centaur, Defiant, Diligent, Nova, Rhode Island, Sabre.


=== Section 6 - Content and Ratings ===
Each science lab is configurable by the crew without the need for return to space dock; being stocked and equipped to perform a wide range of experiments and research. Preparing the science lab for a new field of study may require several hours to several days of setting up and calibrating the on-board equipment, but it is most certainly 'user serviceable'.
* Bravo Fleet uses the [https://rpgrating.com/ RPG Rating System] to define appropriate content based on three metrics: Language, Sex, and Violence. RPGs and Fictions should not use the MPAA rating system (G, PG, etc.)
 
* The default rating for Bravo Fleet content is 1-1-1. All official fiction from Task Force Staff and the Lore Office must remain rated 1-1-1.
==== '''Warp Drive System''' ====
* Members may write stories of a higher rating, but this must be listed on their Command page on BFMS. They may freely designate their rating up to Language: 2, Sex: 2, and Violence: 2 (16+ age rating).
''Thyanis'' is equipped with a standard Matter/Anti-Matter reactor for her size, capable of an unrestricted sustained velocity of Warp 8. Her maximum (safe) obtainable speed is Warp 8.85 for 12 hours.
* No content may inappropriately depict acts of sex, assault, or violence. Appropriate content is determined by Bravo Fleet Command. We appreciate ratings are not absolute in their guidelines; please consult the Loremaster if you are unsure.
 
* Sexual violence should be addressed, if at all, with particular care. It should never be depicted directly in a scene, or be discussed by characters in any detail. Reference to sexual violence of any sort should never happen without the explicit OOC permission of every member involved in the story and, in RPGs, the GM. Stories may be removed at the Loremaster's discretion, as per the above on appropriate content.
In 2401, during her mission to the Deneb sector; ''Thyanis'' was forced to exceed this speed and managed to obtain a maximum velocity of warp 8.94. This was obtained without significant modification but caused severe stress damage to her hull and warp drive systems. This was also at the expense of having to override a number of failsafe's and safety protocols.
 
It is worth noting that this operation was only performed due to an unprecedented operational necessity and many of the failsafe's that were overridden at the time have now been re-designed to require dry-dock engineering equipment to bypass.
 
The intense heat generated from the warp matter reaction at these speeds was sufficient to weld her anti-matter injectors shut as they began to cool following an immediate warp core shut down. This made restarting the core impossible and required several injectors to be replaced in order to reinitialise a reaction.
 
While the Matter/Antimatter reaction could remain sustained after securing from such a high warp speed, it is highly likely that the injectors would have suffered heat stress beyond acceptable tolerance and for safety reasons, the injectors would have had to have been replaced before engaging the warp drive again regardless of whether the reaction was terminated immediately or gradually to allow time for adequate cooling and tempering of the alloys used in their construction.
 
Following her return to space-dock, the damage caused by this operation required a complete replacement of the Warp drive system, including all Matter/Anti-matter reaction components and a complete refurbishment of her warp coils, as many of them sustained micro fractures due to the stress of high warp flight.
 
==== Crew Transportation System ====
One rather unique design choice employed on the ''Thyanis'' is the complete lack of Turbo Lifts which are an over-complicated mechanism that would take up vast amounts of internal space. Instead ''Thyanis'' is equipped with 'Ladders' in various locations around the ship, these resemble very steep sets of stairs that were typical on contemporary Navy Warships of the 20th & 21st century. They are a simple and effective solution to allow access to all decks of the ship whilst maximising the internal space available for internal compartments and living quarters.
 
=== Deck plan (overview) ===
 
==== Deck 1 ''(From Bow to Stern)'' ====
'''''Bold''''' Denote Area only accessible via crawlspace & Jeffries tube
 
* Escape Pods
* Science Lab 1
* Escape Pods
* Science Lab 2
* Escape Pods
* '''''Aft Sensor Suite'''''
 
==== Deck 2 ''(From Bow to Stern)'' ====
'''''Bold''''' Denote Area only accessible via crawlspace & Jeffries tube
 
* C.O. Ready Room
* Main Bridge
* Environmental Control
* Portside Mess
* Starboard Galley
* X.O Quarters
* Equipment Storage
* '''''Life Support Consumable Storage Tanks'''''
 
==== Deck 3 ''(From Bow to Stern)'' ====
'''''Bold''''' Denote Area only accessible via crawlspace & Jeffries tube
 
* C.O. Quarters
* Sickbay
* Hollo Suite
* '''''Anti Matter Storage'''''
* '''''Warp Core (upper Level)'''''
* '''''Deuterium Storage'''''
* '''''Computer Core (upper Level)'''''
* Cargo Loading Dock
* Shuttle Bay
 
==== Deck 4 ''(From Bow to Stern)'' ====
'''''Bold''''' Denote Area only accessible via crawlspace & Jeffries tube
 
* '''''Deflector Control'''''
* Torpedo Magazine & '''''Launcher Tube'''''
* Brig
* Crew Quarters
* Forward Cargo Bay
* Main Engineering
* Computer Core
* Transporter Room
* Aft Cargo Bay
* Crew Quarters
 
==== Deck 5 ''(From Bow to Stern)'' ====
'''Note: Deck 5 Is only accessible via Crawlspace and not all areas are routinely pressurised'''
 
* '''EPS Power Buffers'''
* '''Forward Sensor array'''
* '''Subspace Transceiver'''
* '''Forward Landing Gear'''
* '''Forward Cargo Bay Doors & Elevator'''
* '''Warp Core (Lower Deck)'''
* '''Rear Cargo Bay Doors & Elevator'''
* '''Aft Landing Gear'''
 
===Notable Crew===
====Commanding Officers====
*[https://bravofleet.com/command/60986/ 2400 - 2400]: [[bfms char:59211|Ensign Cimozjen Kurios]]
*[https://bravofleet.com/command/52947/ 2400 - 2400]: [[bfms char:53381|Commander Thevius]]
*[https://bravofleet.com/command/77256/ 2401 - Present]: [[bfms char:77255|Lieutenant Commander Wallace Jones]]
 
{{clear}}

Revision as of 18:23, 18 June 2023

AerieClass.jpg
USS Thyanis
General Information
Registry NCC-88019
Class & Type Raven-class Corvette
Affiliation Starfleet
Status Active
Commissioned 2389
Assignment
Task Force Task Force 93
Task Group Task Group 44
Role Multi-Role
Key Personnel
Commanding Officer Lieutenant Commander Wallace Jones
Executive Officer Lieutenant Commander Harris Tan
Template:Starship

The USS Thyanis is a Raven-class corvette assigned to Fourth Fleet.

Mission History

Early Encounters (2400-2400)

The earliest encounters of the Thyanis in the former Romulan Neutral Zone were mostly involving dealing with folks affected by the disruption caused following the fall of the Romulan Star Empire. As captain of the ship, Kurios and his XO engaged in establishing trade, and helped to resolve issues of malnutrition and disease among several colonies throughout the region. As a part of Task Force 93, this fell well within both the skills of the Starfleet doctor and within the parameters set by the Fourth Fleet's chain of command.

Refit (2400-2401)

Following the departure of Commander Thevius; Thyanis was returned to Starbase Bravo for minor re-fit. Being a small vessel with little tactical significance, she remained berthed as a reserve ship for nearly a year until she was assigned a new crew and captain at the start of March 2401.

The nature of her refit was only minor, involving updating many of the standard systems aboard the vessel and returning her to a standard configuration for a multi-role mission profile.

Deneb Sector Crisis (2401)

In March 2401 Lieutenant Commander Wallace Jones assumed command of the USS Thyanis immediately following the outbreak of the Dominion crisis in the Deneb sector.

Oppenheimer Station

Thyanis first assignment was to investigate Oppenheimer Research Outpost in the Gamma Cronae Borealis system. The station failed to respond to the evacuation order and Starfleet Intelligence requested that a vessel be immediately dispatched.

With most of the 4th fleet engaged on the front line, Thyanis was assigned this mission out of operational necessity

Voyage to Deneb Sector

During her voyage to the Deneb Sector the USS Thyanis was attacked by a Breen Plesh Tral Raider near the galactic Northern border of the Ferengi Alliance A short skirmish ensued which resulted in the death of one crewmember and life changing injuries to another, Thyanis also received significant damage.

Here Thyanis first encountered a Ferengi vessel commanded by Daimon Tal. The Daimon approached the Thyanis crew with a proposition as a front to covertly gather data and information on the Thyanis's destination.

After returning to Farpoint Station for repairs, Thyanis continued her journey to her destination without incident.

Arrival at Oppenheimer Station

On arrival at Oppenheimer Research outpost, Thyanis attempted to beam a small away team onto the station. The transport was aborted when it was discovered that the station was housing a Quantum singularity that had the potential to interfere with the transporter process and nearly cost the lives of the away team.

A follow up away mission was carried out with the aid of a shuttle, led by the Thyanis X.O. Lt Commander Harris Tan

At about the same time, the Ferengi Vessel commanded by Daimon Tal approached the station. Thyanis attempted to warn them of the danger but their actions were seen as aggressive and Thyanis took significant damage when the Ferengi retaliated.

Meanwhile on the station, the away team discovered bodies of the Jem'Hadar in advanced stages of decomposition. After shutting down and examining the energy device containing the Quantum Singularity, it was determined that the Jem'Hadar had died as a result of the relativistic effects from the unstable singularity.

As the singularity was shut down, Daimon Tal boarded the station, killed a Thyanis crew member and kidnapped Dr Molly Xan and - the Thyanis Chief Medical officer and Dr Sutherland - Chief scientist aboard the station; all whilst stealing the energy device itself.

Ferengi Pursuit

The Thyanis crew worked desperately to push the ship to its absolute limit in pursuit of the Ferengi Vessel, that was heading for a region of space plagued by subspace instability and a nebula like phenomena. After nearly tearing the ship apart flying well beyond her maximum rated warp speed; Thyanis successfully kept pace with the Ferengi and were able to maintain pursuit.

Battle with the Dominion

The disruption to sensors, shields and energy weapons caused by the anomalous region forced the Thyanis to adopt 20th century tactics to navigate the anomaly and locate Daimon Tal's ship. Using a modified deflector pulse designed to emit Tachyons, Thyanis soon caught up with the Ferengi, only to encounter a Jem'Hadar Battleship in the process.

Meanwhile, During a showdown between the Thyanis C.O. - Wallace Jones and Daimon Tal - it was revealed that Tal had been replaced by a Changeling, who was plotting to re-engineer the stolen energy device as a devastating weapon - a Black hole Bomb. The changeling was defeated (but not killed) with the combined effort of the Thyanis away team however the energy device had already been delivered to the Dominion ship.

At the same time Thyanis became locked in a deadly battle with the Dominion vessel. Completely out-classed and out gunned, the Thyanis X.O. Harris Tan devised a tactic that would later become known as 'The Tan Manoeuvre' to cripple the Dominion vessel. Taking inspiration from 20th century fighter weapons tactics, the crew modified several Photon torpedo's to act with delayed autonomous guidance on the same principle as the Tachyon pulse the ship had been using to find the Ferengi.

The resulting damage caused to the Dominion vessel detonated the energy device on board, which was in the process of powering up for a test fire. This detonation allowed the singularity contained within to become self sustaining and this then evolved into a stellar mass black hole.

As the Black hole began consuming the surrounding matter in the region, Thyanis rescued the survivors on board the Ferengi ship and her away team before departing for Farpoint station to conclude her mission.

Crew Complement

The maximum crew of the Thyanis is only 20 strong, and as such the needs and the abilities of the crew are both affected. The crew has a greater focus on the medical and engineering careers, with only a handful of Starfleet officers specializing in particular fields. Many of the crew are of lower ranks to the point that a former captain, Ensign Kurios, once called it a "can of Ensigns". This quip was a mild misnomer however, as at least a quarter of the crew were cadets or crewman.

Interestingly, despite being a ship providing humanitarian support to the former Romulan Neutral Zone, the crew itself could easily find itself in the care of only a old first generation EMH. This was considered a bit grim, given the antiquated unit was already being phased out back in 2374. As such, it was taken as a bit of black humour among some of the crew that nobody should get injured unless they wanted to be 'walking dead'. The attitude was not helped with the tendency of her captain to be involved in away missions or otherwise be indisposed.

Vessel Configuration

The current configuration of the Thyanis is standard for its class. In the past she had been fitted with a slightly more well equipped sick bay to assist her mission profile but this was replaced by its standard configuration to allow the vessel to align to its multi-role profile in 2401. No particular compartment is favoured over another and while she is equipped with two generalist science labs, these facilities can be used simultaneously for different purposes. For example: Science lab 1 can be configured for astronomical survey's where as Science lab 2 can be configured for medical research.

Each science lab is configurable by the crew without the need for return to space dock; being stocked and equipped to perform a wide range of experiments and research. Preparing the science lab for a new field of study may require several hours to several days of setting up and calibrating the on-board equipment, but it is most certainly 'user serviceable'.

Warp Drive System

Thyanis is equipped with a standard Matter/Anti-Matter reactor for her size, capable of an unrestricted sustained velocity of Warp 8. Her maximum (safe) obtainable speed is Warp 8.85 for 12 hours.

In 2401, during her mission to the Deneb sector; Thyanis was forced to exceed this speed and managed to obtain a maximum velocity of warp 8.94. This was obtained without significant modification but caused severe stress damage to her hull and warp drive systems. This was also at the expense of having to override a number of failsafe's and safety protocols.

It is worth noting that this operation was only performed due to an unprecedented operational necessity and many of the failsafe's that were overridden at the time have now been re-designed to require dry-dock engineering equipment to bypass.

The intense heat generated from the warp matter reaction at these speeds was sufficient to weld her anti-matter injectors shut as they began to cool following an immediate warp core shut down. This made restarting the core impossible and required several injectors to be replaced in order to reinitialise a reaction.

While the Matter/Antimatter reaction could remain sustained after securing from such a high warp speed, it is highly likely that the injectors would have suffered heat stress beyond acceptable tolerance and for safety reasons, the injectors would have had to have been replaced before engaging the warp drive again regardless of whether the reaction was terminated immediately or gradually to allow time for adequate cooling and tempering of the alloys used in their construction.

Following her return to space-dock, the damage caused by this operation required a complete replacement of the Warp drive system, including all Matter/Anti-matter reaction components and a complete refurbishment of her warp coils, as many of them sustained micro fractures due to the stress of high warp flight.

Crew Transportation System

One rather unique design choice employed on the Thyanis is the complete lack of Turbo Lifts which are an over-complicated mechanism that would take up vast amounts of internal space. Instead Thyanis is equipped with 'Ladders' in various locations around the ship, these resemble very steep sets of stairs that were typical on contemporary Navy Warships of the 20th & 21st century. They are a simple and effective solution to allow access to all decks of the ship whilst maximising the internal space available for internal compartments and living quarters.

Deck plan (overview)

Deck 1 (From Bow to Stern)

Bold Denote Area only accessible via crawlspace & Jeffries tube

  • Escape Pods
  • Science Lab 1
  • Escape Pods
  • Science Lab 2
  • Escape Pods
  • Aft Sensor Suite

Deck 2 (From Bow to Stern)

Bold Denote Area only accessible via crawlspace & Jeffries tube

  • C.O. Ready Room
  • Main Bridge
  • Environmental Control
  • Portside Mess
  • Starboard Galley
  • X.O Quarters
  • Equipment Storage
  • Life Support Consumable Storage Tanks

Deck 3 (From Bow to Stern)

Bold Denote Area only accessible via crawlspace & Jeffries tube

  • C.O. Quarters
  • Sickbay
  • Hollo Suite
  • Anti Matter Storage
  • Warp Core (upper Level)
  • Deuterium Storage
  • Computer Core (upper Level)
  • Cargo Loading Dock
  • Shuttle Bay

Deck 4 (From Bow to Stern)

Bold Denote Area only accessible via crawlspace & Jeffries tube

  • Deflector Control
  • Torpedo Magazine & Launcher Tube
  • Brig
  • Crew Quarters
  • Forward Cargo Bay
  • Main Engineering
  • Computer Core
  • Transporter Room
  • Aft Cargo Bay
  • Crew Quarters

Deck 5 (From Bow to Stern)

Note: Deck 5 Is only accessible via Crawlspace and not all areas are routinely pressurised

  • EPS Power Buffers
  • Forward Sensor array
  • Subspace Transceiver
  • Forward Landing Gear
  • Forward Cargo Bay Doors & Elevator
  • Warp Core (Lower Deck)
  • Rear Cargo Bay Doors & Elevator
  • Aft Landing Gear

Notable Crew

Commanding Officers

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