Bravo Fleet
Difference between pages "Command Policy" and "Avalon Research & Design Group"

Difference between pages "Command Policy" and "Avalon Research & Design Group"

From Bravo Fleet
(Difference between pages)
 
 
Line 1: Line 1:
{{icons|bfo}}Last Update: 17 December 2022
{{Organisation
| name = Avalon Group
| image = [[File:AvalonRDGroupSeal.png]]
| founded =
| affiliation = *[[United Federation of Planets]]
*[[Starfleet]]
*[[Fourth Fleet]]
*[[Fourth Fleet Advanced Research & Design Bureau]]
| headquarters = [[Avalon Fleet Yards]]
| primary mission = Research & Development
| location = [[Avalon System]]
| leadership =
| flagship =
| motto = ''macte virtute sic itur ad astra''
| status = Active
}}The '''Avalon Group''' of the [[Fourth Fleet Advanced Research & Design Bureau]] encompasses dozens of different Institutes and hundreds of different projects taking place at [[Avalon Fleet Yards]] and across the [[Avalon System]]. Meant to be the tip of the spear in scientific, engineering, and medical research for the Fourth Fleet, this group’s interdisciplinary and highly collaborative nature brings the best and the brightest minds together to solve problems and develop innovations.


=1 - Registry Definition=
== Leadership ==
#The registry lists all starships, starbases, and other entities available to Bravo Fleet for use as Commands or Games.
The Avalon Group is led formally by the Commander of Avalon Fleet Yards, though their day-to-day oversight of the group is minimal. Day-to-day decisions are made by individual institute, project, and team leaders. The leaders of institutes and independent projects meet regularly as the Avalon Group Board to share status updates and make collective decisions about allocating space and resources to each of their projects. The Avalon Group Board is chaired by either the Commander or Deputy Commander of Avalon Fleet Yards. In turn the Avalon Group reports to the [[Fourth Fleet Advanced Research and Design Bureau]], with individual institutes and projects also reporting to the appropriate Starfleet Science, Starfleet Engineering, and/or Starfleet Medical Bureaus.
#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.
#Events involving registry ships prior to 2399 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. This restriction begins at 2399 as this is when the current fleet canon went live; members should not be dictating fleet or member canon for this period outside of their own characters and Command.
#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 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 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.
#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.
#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.
{| class="wikitable" style="margin:auto"
|+Ship classes by rank
|-
!Midshipman!!Lieutenant Commander!!Commander!!
|-
|[[Raven Class|Raven]]||[[California Class|California]]|| colspan="2" |[[Akira Class|Akira]]
|-
| ||[[Challenger Class|Challenger]]|| colspan="2" |[[Defiant Class|Defiant]]
|-
| ||[[Cheyenne Class|Cheyenne]]|| colspan="2" |[[Excelsior II Class|Excelsior II]]
|-
| ||[[Diligent Class|Diligent]]|| colspan="2" |[[Gagarin Class|Gagarin]]
|-
| ||[[Grissom Class|Grissom]]|| colspan="2" |[[Inquiry Class|Inquiry]]
|-
| ||[[Intrepid Class|Intrepid]]|| colspan="2" |[[Luna Class|Luna]]
|-
|
|[[New Orleans Class|New Orleans]]
| colspan="2" |[[Manticore Class|Manticore]]
|-
| ||[[Norway Class|Norway]]|| colspan="2" |[[Nebula Class|Nebula]]
|-
| ||[[Nova Class|Nova]]|| colspan="2" |[[Pathfinder Class|Pathfinder]]
|-
| ||[[Olympic Class|Olympic]]|| colspan="2" |[[Prometheus Class|Prometheus]]
|-
|
|[[Parliament Class|Parliament]]
| colspan="2" |[[Rhode Island Class|Rhode Island]]
|-
| ||[[Reliant Class|Reliant]]|| colspan="2" |[[Sutherland Class|Sutherland]]
|-
| ||[[Saber Class|Saber]]|| colspan="2" |
|-
| ||[[Springfield Class|Springfield]]
|-
| ||[[Steamrunner Class|Steamrunner]]
|}
=3 - Squadrons=


#The 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.  
== Organization ==
#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.
The Avalon Group is divided into institutes, projects, and teams, all of which are interdisciplinary research and development units. Institutes are multi-project teams that occupy a dedicated shore facility or several full levels aboard a station or research module. Projects are either sub-units of institutes or smaller independent research teams, which have several interconnected lab facilities. Teams are either sub-units of projects or institutes or are new initiatives in their early stages of formation under the Avalon Group, typically having just one lab or similar facility. The leaders of institutes, projects, and teams must regularly meet with one another to share ideas and resources, as well as status updates.
##Members with multiple ships should designate one as their Primary Command on BFMS.
##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 ==
===Institutes===
Institutes are large, multi-project teams that encompass either their own planetary facilities or a major research module on one of Avalon’s many space stations. Institutes are led by fleet captains and above and often consist of a half-dozen or more projects with hundreds of scientists, engineers, and/or doctors.


# Ship classes are allocated a certain level of Strength depending on their size, power, modernity, and so forth.
====Institute for Experimental Rehabilitative Medicine (IERM)====
# 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 Institute for Experimental Rehabilitative Medicine (IERM) is a medical research agency. Led by Admiral Linda Knox-Stanton, this institute was founded to explore new therapies to help patients recover physically, emotionally, and spiritually from traumatic injuries. Occupying a complex within [[Sato City]] on [[Avalon System#Avalon III|Avalon III]], the Institute has in-patient facilities for forty patients who are participating in about a dozen different research projects.


{| class="wikitable" style="margin:auto"
=====Genetronic Nanocybernetics Project=====
|+Ship classes by rank
The Genetronic Nanocybernetics Project (Codename: Hephaestus) is a project operating under the auspices of the Institute for Experimental Rehabilitative Medicine to study the combination of genetronic replication and nano-scale cybernetics to treat patients with severe spinal cord injuries. Started after his success with a procedure conducted on the Risian Lieutenant Zaos Sarcaryn, this project is being led by Captain Alenis Anjar.
|-
!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 ==
======Nanocybernetics Team======
The Nanocybernetics Team is one of the teams under Project Hephaestus, developing nano-scale cybernetics that can help regenerate or replace the connections between nerves. Primarily an engineering team rather than a medical team, this team has experts in cybernetics, nanotechnology, and microphysics.


# 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.
====Institute for Advanced Impulse Engine Design====
# 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.
The Institute for Advanced Impulse Engine Design (IAIED) is an engineering research agency studying advancements in sublight propulsion technologies. While the basic design of Federation impulse engines has remained fundamentally the same since the twenty-second century, this institute is focusing on small scale improvements to their general functioning. This institute occupies the entirety of Research Module A on [[Tucker Station]].
# 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"
=====Phase 7 Impulse Manifold Project=====
|+Starbase classes by Strength
One of the projects under the Institute for Advanced Impulse Engine Design, the Phase 7 Impulse Manifold Project is studying enhancements to the current standard of Starfleet impulse manifolds (so-called Phase 6), which are the component of an impulse engine assembly that direct energized drive plasma from multiple fusion reactors through to the subspace driver coils and ultimately the engine exhaust. This team includes engineers and physicists hoping to make this system more efficient. This project works out of the IAEID space on [[Tucker Station]].
|-
!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 ==
======Fusion Reactor Enhancement Team======
Working under the Phase 7 Impulse Manifold Project, the Fusion Reactor Enhancement Team is a team of engineers and physicists looking to improve the efficiency and power generation potential of Starfleet's fusion reactors. In particular, this team's focus is on the type of reactor currently in use on the fleet's [[Reliant Class|''Reliant''-class frigates]], many of which are built at Avalon Fleet Yards. This team works out of the IAEID space on [[Tucker Station]].


# 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.
====Institute for Observational Cosmology====
# 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.


{| class="wikitable"
=====New Deep Space Telescope Project=====
|+Starbase Attached Ship Options
![[Aquarius Class|Aquarius]]
!
!
!
!
|-
|[[Raven Class|Raven]]
|
|
|
|
|-
|[[Sydney Class|Sydney]]
|
|
|
|
|}


== 3.4 - Requesting Squadron Ships ==
======Deep Space Scanning Team======


# Members must use BFMS to request any Commands under the Squadron system, as was done with previous Command requests.
==== Institute of the History of Starfleet Warfare ====
# 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.
The Institute of the History of Starfleet Warfare (IHSW) is a historical research agency. This institute was founded to further research and analysis of the history of Starfleet conflicts, dating back to the period immediately before the Federation’s founding. The IHSW occupies a complex in Sato City, where it conducts and manages archival and archaeological research, historical analysis, and museology. Its projects each take an interdisciplinary approach to assigned eras of history, with teams providing expertise in their respective disciplines. The IHSW studies historical Starfleet conflicts to understand how to avoid potential future ones, considering strategy, tactics, and technology, but also the role of Starfleet's organisational policy, psychology, and culture.
## 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.
===== Dominion War Project =====
## 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.
The Dominion War Project is an historical research project operating under the Institute of the History of Starfleet Warfare to gather and maintain records and conduct analysis of the Dominion War of the 2370s. As this is a conflict that occurred within living memory even of humans, the project's work includes gathering records from multiple governments and organisations, as well as recording lived experiences of survivors. The Dominion War is considered the most catastrophic in Federation history, and a significant portion of the project's focus includes understanding how and why this inter-quadrant conflict became intra-quadrant, intending to shape future Federation foreign policy to avert similar events.
# 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.
 
===Independent Research Projects===
There are many research projects under the Avalon Group that do not report to an insitute, often because the project is still at an early stage and it will later mature into an institute once initial research has been completed. These independent projects may also have affiliations with more than one institute, thus making them better suited to remain independent. Projects are led by commanders and captains, and can consist of several dozen scientists, engineers, and/or doctors.
 
===Independent Research Teams===
As with independent research projects, some research teams under the Avalon Group are not part of any one project or institute, either because their work is still in its early stages or because their work is affiliated with more than one project. They may later mature into projects of their own. Teams are led by lieutenants and lieutenant commanders.
 
== The Avalon Group In-Play ==
 
* The Avalon Group was created as a way of allowing members to write higher ranking characters with important research assignments that might not fit into either [[Starbase Bravo]] or into their personal commands. Indeed, it's not particularly logical for characters higher than fleet captain to be regularly assigned to field operations, so these characters need a home for when those members are no longer on staff. The purpose of this component of Avalon Fleet Yards is thus to allow you to write content that deals with politics, bureaucracy, and higher-level concepts, rather than the slice-of-life theme on Starbase Bravo.
* As explained in the [[Guide:Avalon Fleet Yards|Avalon Fleet Yards Guide]], you are allowed to write up to your fleet rank in the Avalon Group, with larger teams becoming available to you at the ranks of lieutenant, commander, and fleet captain. For instance, as a fleet captain you can have your own "Institute" while at lieutenant you can have your own "team."
* Teams fit into projects which fit into Institutes, but Teams and Institutes can also be independent. You can grow your team into a project and then into an institute as you increase in rank. You can also speak to the members who have institutes to see if it would be OK with them to add your team or project to their institute. Many folks would be happy to have you!
* Most of the research facilities are located either on Avalon III or one of the Avalon Fleet Yards stations in orbit. Generally speaking, researchers will live either on Brahms Station or on Sato City and commute via shuttle or transporter, so members of the Avalon Group will have plenty of opportunities to socialize even if their workplaces are spread out.
* There are always reasons to work with researchers in other teams, projects, and institutes, as science is inherently collaborative. Maybe you have a friendly rivalry with someone else in a similar discipline and you're competing for resources. Maybe they have a piece of equipment that's hard for you to acquire and you need to convince them to share. Maybe they have expertise that you lack. The possibilities are many.

Revision as of 14:35, 5 July 2023

AvalonRDGroupSeal.png
Avalon Group
Affiliation
Headquarters

Avalon Fleet Yards

Primary Mission

Research & Development

Location

Avalon System

Motto

macte virtute sic itur ad astra

Status

Active

Template:Organisation

The Avalon Group of the Fourth Fleet Advanced Research & Design Bureau encompasses dozens of different Institutes and hundreds of different projects taking place at Avalon Fleet Yards and across the Avalon System. Meant to be the tip of the spear in scientific, engineering, and medical research for the Fourth Fleet, this group’s interdisciplinary and highly collaborative nature brings the best and the brightest minds together to solve problems and develop innovations.

Leadership

The Avalon Group is led formally by the Commander of Avalon Fleet Yards, though their day-to-day oversight of the group is minimal. Day-to-day decisions are made by individual institute, project, and team leaders. The leaders of institutes and independent projects meet regularly as the Avalon Group Board to share status updates and make collective decisions about allocating space and resources to each of their projects. The Avalon Group Board is chaired by either the Commander or Deputy Commander of Avalon Fleet Yards. In turn the Avalon Group reports to the Fourth Fleet Advanced Research and Design Bureau, with individual institutes and projects also reporting to the appropriate Starfleet Science, Starfleet Engineering, and/or Starfleet Medical Bureaus.

Organization

The Avalon Group is divided into institutes, projects, and teams, all of which are interdisciplinary research and development units. Institutes are multi-project teams that occupy a dedicated shore facility or several full levels aboard a station or research module. Projects are either sub-units of institutes or smaller independent research teams, which have several interconnected lab facilities. Teams are either sub-units of projects or institutes or are new initiatives in their early stages of formation under the Avalon Group, typically having just one lab or similar facility. The leaders of institutes, projects, and teams must regularly meet with one another to share ideas and resources, as well as status updates.

Institutes

Institutes are large, multi-project teams that encompass either their own planetary facilities or a major research module on one of Avalon’s many space stations. Institutes are led by fleet captains and above and often consist of a half-dozen or more projects with hundreds of scientists, engineers, and/or doctors.

Institute for Experimental Rehabilitative Medicine (IERM)

The Institute for Experimental Rehabilitative Medicine (IERM) is a medical research agency. Led by Admiral Linda Knox-Stanton, this institute was founded to explore new therapies to help patients recover physically, emotionally, and spiritually from traumatic injuries. Occupying a complex within Sato City on Avalon III, the Institute has in-patient facilities for forty patients who are participating in about a dozen different research projects.

Genetronic Nanocybernetics Project

The Genetronic Nanocybernetics Project (Codename: Hephaestus) is a project operating under the auspices of the Institute for Experimental Rehabilitative Medicine to study the combination of genetronic replication and nano-scale cybernetics to treat patients with severe spinal cord injuries. Started after his success with a procedure conducted on the Risian Lieutenant Zaos Sarcaryn, this project is being led by Captain Alenis Anjar.

Nanocybernetics Team

The Nanocybernetics Team is one of the teams under Project Hephaestus, developing nano-scale cybernetics that can help regenerate or replace the connections between nerves. Primarily an engineering team rather than a medical team, this team has experts in cybernetics, nanotechnology, and microphysics.

Institute for Advanced Impulse Engine Design

The Institute for Advanced Impulse Engine Design (IAIED) is an engineering research agency studying advancements in sublight propulsion technologies. While the basic design of Federation impulse engines has remained fundamentally the same since the twenty-second century, this institute is focusing on small scale improvements to their general functioning. This institute occupies the entirety of Research Module A on Tucker Station.

Phase 7 Impulse Manifold Project

One of the projects under the Institute for Advanced Impulse Engine Design, the Phase 7 Impulse Manifold Project is studying enhancements to the current standard of Starfleet impulse manifolds (so-called Phase 6), which are the component of an impulse engine assembly that direct energized drive plasma from multiple fusion reactors through to the subspace driver coils and ultimately the engine exhaust. This team includes engineers and physicists hoping to make this system more efficient. This project works out of the IAEID space on Tucker Station.

Fusion Reactor Enhancement Team

Working under the Phase 7 Impulse Manifold Project, the Fusion Reactor Enhancement Team is a team of engineers and physicists looking to improve the efficiency and power generation potential of Starfleet's fusion reactors. In particular, this team's focus is on the type of reactor currently in use on the fleet's Reliant-class frigates, many of which are built at Avalon Fleet Yards. This team works out of the IAEID space on Tucker Station.

Institute for Observational Cosmology

New Deep Space Telescope Project
Deep Space Scanning Team

Institute of the History of Starfleet Warfare

The Institute of the History of Starfleet Warfare (IHSW) is a historical research agency. This institute was founded to further research and analysis of the history of Starfleet conflicts, dating back to the period immediately before the Federation’s founding. The IHSW occupies a complex in Sato City, where it conducts and manages archival and archaeological research, historical analysis, and museology. Its projects each take an interdisciplinary approach to assigned eras of history, with teams providing expertise in their respective disciplines. The IHSW studies historical Starfleet conflicts to understand how to avoid potential future ones, considering strategy, tactics, and technology, but also the role of Starfleet's organisational policy, psychology, and culture.

Dominion War Project

The Dominion War Project is an historical research project operating under the Institute of the History of Starfleet Warfare to gather and maintain records and conduct analysis of the Dominion War of the 2370s. As this is a conflict that occurred within living memory even of humans, the project's work includes gathering records from multiple governments and organisations, as well as recording lived experiences of survivors. The Dominion War is considered the most catastrophic in Federation history, and a significant portion of the project's focus includes understanding how and why this inter-quadrant conflict became intra-quadrant, intending to shape future Federation foreign policy to avert similar events.

Independent Research Projects

There are many research projects under the Avalon Group that do not report to an insitute, often because the project is still at an early stage and it will later mature into an institute once initial research has been completed. These independent projects may also have affiliations with more than one institute, thus making them better suited to remain independent. Projects are led by commanders and captains, and can consist of several dozen scientists, engineers, and/or doctors.

Independent Research Teams

As with independent research projects, some research teams under the Avalon Group are not part of any one project or institute, either because their work is still in its early stages or because their work is affiliated with more than one project. They may later mature into projects of their own. Teams are led by lieutenants and lieutenant commanders.

The Avalon Group In-Play

  • The Avalon Group was created as a way of allowing members to write higher ranking characters with important research assignments that might not fit into either Starbase Bravo or into their personal commands. Indeed, it's not particularly logical for characters higher than fleet captain to be regularly assigned to field operations, so these characters need a home for when those members are no longer on staff. The purpose of this component of Avalon Fleet Yards is thus to allow you to write content that deals with politics, bureaucracy, and higher-level concepts, rather than the slice-of-life theme on Starbase Bravo.
  • As explained in the Avalon Fleet Yards Guide, you are allowed to write up to your fleet rank in the Avalon Group, with larger teams becoming available to you at the ranks of lieutenant, commander, and fleet captain. For instance, as a fleet captain you can have your own "Institute" while at lieutenant you can have your own "team."
  • Teams fit into projects which fit into Institutes, but Teams and Institutes can also be independent. You can grow your team into a project and then into an institute as you increase in rank. You can also speak to the members who have institutes to see if it would be OK with them to add your team or project to their institute. Many folks would be happy to have you!
  • Most of the research facilities are located either on Avalon III or one of the Avalon Fleet Yards stations in orbit. Generally speaking, researchers will live either on Brahms Station or on Sato City and commute via shuttle or transporter, so members of the Avalon Group will have plenty of opportunities to socialize even if their workplaces are spread out.
  • There are always reasons to work with researchers in other teams, projects, and institutes, as science is inherently collaborative. Maybe you have a friendly rivalry with someone else in a similar discipline and you're competing for resources. Maybe they have a piece of equipment that's hard for you to acquire and you need to convince them to share. Maybe they have expertise that you lack. The possibilities are many.
Retrieved from "https://wiki.bravofleet.com/index.php?title=Command_Policy&oldid=10442"