Technical Record

Standardized Ship Specification Format

STF Technical Manual Engineering Department Guides Updated 29 May 2022
TM RECORD

The SSSF is the approved format for all ship specifications in use in Starfleet. In conjunction with other Engineering Department documents, it provides guidelines for ship specification creation. The Engineering Department requires specification designers to follow the current Ship Submission Policy as present in the Technical Manual in order for a specification to receive review and potential approval for entry into the Technical Manual. A history of the SSSF is at the end of this page.

All specifications are required to conform strictly to the format below when posted in the ED. Unless otherwise stated, all sections and information are mandatory. The Engineering Department is to maintain a Markdown-formatted version of all approved specifications on the STF server as part of the Technical Manual section of the Library, and to move retired specifications to the Ship Museum section of the Library, including all pertinent revision history. The resultant web page will serve as the normative version of the specification.

The Category and Variant in the specification header are based on the Milwaukee Plan, the ED’s Ship Specification Categorization System (SSCS).

The SSSF also serves as a Designers’ Guide, and includes vast amounts of information intended to help designers improve their specs and keep them within ED bounds. Side comments are listed in [brackets] and are not part of the design proper. Note that only the designers’ real names are used, without rank. Additionally, the formatting used below serves as a way for the Engineering Department to port approved specifications into the Technical Manual with limited adjustments.

Format Outline and Details

GENERIC-CLASS
CATEGORY: CRUISER
VARIANT: MEDIUM
DESIGNER: Author Name
Mark I [Revision of an approved spec is Mark II, next is Mark III, etc.]
Draft 1 [Increments with each review posting of this Mark version.]
DATE: DD Month YYYY
REFERENCED URLs: [Links to images for this spec.]

## History And Mission Overview
This section covers the IC background and history of the project. It serves mostly for the designer's ego, but also includes the ship's mission profile, purpose, and so on. The question "So why do we need this ship anyway?" should be answered in this section. A bulleted list of mission profiles is recommended. (Some designs currently have this already.)

### Mission Profiles
* Mission 1
* Mission 2
* Mission 3

## Structure And Construction
This section should create an accurate, detailed picture of the ship in the reader's mind. From this section the reader should be able to close his eyes and visualize the ship almost exactly the same way as the designer. External view images of the design should be included in this section, if present, and are encouraged. URLs from above can be listed here for clarity. In the final normalized copies, they will be linked from here using thumbnails.

Also included in this section is a discussion of the spacecraft construction. Hull type, armor (if applicable), hull materials, and back-story discussion (literary embellishment on the part of the designer, always encouraged) are included here. If the ship is capable of separating into multiple sections (saucer separation, the Columbus' Sffina Kitana, etc.), a description of same would be included here. If the ship is capable of landing on a planetary surface and taking off again, it must be stated here. If not stated, it is assumed that it cannot.

Additionally, if the ship supports swappable mission modules, that fact must be stated here. The location of the modules, whether they require dry-docking the vessel or if modules can be swapped at your local corner starbase, and a list of usable modules must be included. The list should include any and all modules that a crew may use for that design, and should be assumed to be exhaustive. (GMs are given more flexibility with regards to the list, but a list must still be provided.)

## Science And Remote Sensing Systems
This section details any scientific and sensory equipment the ship carries, above and beyond "standard" sensors present on every ship. The ship's computer system, if applicable, should also be described here.

References to external Tech Submissions are permitted if applicable, in which case a URL must be provided. Unless stated otherwise, the computer system is assumed to be an isolinear computer core using the standard Starfleet LCARS OS and interface (same as Galaxy-class). This data is primarily characterization and literary embellishment, but not always. Any non-standard computer systems are expected to be compatible with canonical descriptions as cited in the Designers Guide, most notably the relationship between isolinear and bioneural circuitry.

If the ship carries any holo-crew, they are included and discussed here. Unless explicitly stated, a design is assumed to not carry any holographic crew of any kind.

This section also includes a discussion of the sensor systems on the ship. This section will likely be relatively short, as the main question of sensors is their range, which is listed in the Tech Spec section below.

If the ship possesses any digital weaponry (e.g. electronic warfare systems), those would be included in this section.

## Warp Propulsion System
This section includes a discussion of the warp system. Information that must be included here includes the number of nacelles, location of nacelles and warp core, maximum 12-hour warp speed, maximum sustainable warp speed, standard cruising speed (recommended to be no higher than warp 6, remember this is the ship's "strolling along the sidewalk" speed), and optionally the warp core's cochrane rating. The Modern Navy Plan has the numbers for the warp core types specifically available for the design, but a vessel can use a more powerful or a weaker warp core than in the typical range if it is appropriately explained. Also to be discussed is whether the ship is capable of warp flight while in separated mode, if applicable, and which sections are capable of the same.

This section should also state whether the ship uses traditional ("fixed-wing") or variable-geometry ("swing-wing") nacelles. Unless otherwise stated, a ship is assumed to have traditional fixed nacelles. As it is apparently possible, through unexplained means, to have both traditional and variable-geometry configurations be non-damaging to subspace, all designs are assumed to be subspace-safe unless otherwise specified. (A designer can specify that the ship is not subspace-safe, if for some bizarre reason they really want to.)

It is recommended that designs do not exceed warp 9.9 as their maximum warp factor unless allowed by the Modern Navy Plan. After warp 9.6 or so the warp scale increases exponentially, so every 0.1 increase is an extra several thousand light-years per hour.

## Impulse Propulsion System
A discussion of the impulse system should be included here, including the location of impulse engines, literary embellishments, and maximum impulse as a multiple of c. The maximum impulse of all ships must be less than 0.35c and 0.30c is recommended for most larger vessels. Smaller craft may have a speed up to and including 0.35c. (This sublight speed limit is intended to avoid relativistic considerations, and is based on a cruising impulse speed of 0.25c for the Galaxy-class. A deal signed with the GM department over a bottle of Romulan ale restricts threat vessels to this same speed limit.)

**NOTE:** Additional propulsion systems are allowed as a main section here (e.g. the Pump-Jet Propulsion System in the *Balao-class* or the Flea’tan Compression Relay Jump Core) if they are permanent fixtures in the vessel instead of modular additions.

## Tactical Systems
This section must include, in the following order, defensive shields, phaser systems, torpedo systems, and other weaponry. If any item is omitted the ship is assumed to be lacking that featured. (Vis, if the design doesn't mention torpedoes, then the ship explicitly does not carry torpedoes of any kind.) Due to the typically technical nature of the equipment descriptions, subsections for each are required as listed below.

### Defensive Shields
Defensive shielding is generated in sections by shield generator layers on the exterior of the hull (the main navigational deflector is not responsible for defensive shielding against hostiles, only interstellar hydrogen while the ship is in motion). This section may include the shield strength, using the following system: Maximum Graviton Load (Continuous) in megawatts (MW) and Maximum Primary Energy Dissipation Rate in kilowatts (kW). Shields should NOT be listed relative to any other design. The Modern Navy Plan has the numbers for the shield types available for the design.

### Phaser Systems
The discussion of phasers systems must include type, location, strength, and number, and optionally range. The Modern Navy Plan has the numbers for the phaser types available for the design. Phasers come in two varieties; strips of linked phaser emitters and pulse phaser cannons (formerly known as "Defiant-style"). Phaser strips are the type used by the Galaxy and Intrepid classes, and may be aimed at any target within an appropriate degree range from the location of the strip, by channeling all phaser energy from the emitters down the strip to a single point where it is directed at the target. For reference, the Galaxy-class has 200 emitters per strip on the saucer section. Pulse Phaser Cannons contain a single emitter which is mono-directional. It is aimed by moving the ship, or a turret to which the Cannon is affixed. If designing a historic design, only phaser banks are allowed. They are fixed-point phaser cannons with a small number of emitters (typically 3), such as those seen in *The Original Series* and the first six *Star Trek* films.

### Torpedo Systems
According to the DS9 Technical Manual, photon torpedoes, quantum torpedoes, and probes all use the same launching tube. Therefore a design should not differentiate between them. The primary data to list for torpedo tubes is number and location. The Galaxy-class has two torpedo tubes, on in the forward dorsal ("neck") section and one tail launcher. Torpedo systems generally have fire-and-forget programming allowing for 360-degree coverage from just two tubes. Designers should take care to not overpower their designs by bearing in mind that the Galaxy needed only two tubes total. Most vessels are stocked with a complement of photon torpedoes rather than quantum torpedoes, due to the high cost and limited availability of the materials necessary for quantum torpedo construction (DS9 TM). The Modern Navy Plan has the numbers for the torpedo tube types and torpedo types available for the design, as well as acceptable combat-to-probe ratios.

### [Additional Weaponry]
Any additional weaponry or defensive systems should be listed in this section as well.

## Command And Support Systems
This section covers all traditional and non-traditional “on duty” locations used by the whole crew or one of the main departments besides Medical. Examples of traditional areas include the Bridge, Brig, Main Engineering, and Science Laboratories. In-depth descriptions of these areas should be included here as subsections; any mission critical area on the Deck Plans not described here is assumed to have a similar layout, if not similar technology, to a *TNG*/*DS9*-era vessel (e.g. *Galaxy*-class or *Sovereign*-class for large vessels, *Intrepid*-class or *Nebula*-class for mid-size vessels, *Defiant*-class or *Nova*-class for small vessels). Given the current club year, use of Paramount+ exclusive sources set in the club year’s time frame (e.g. Picard, Lower Decks) for indirect reference is acceptable, but not mandatory.

### Bridge
The layout should include, at minimum, a central chair, a navigation station, a science station, a tactical station, an engineering station, an internal security station, an operations station, and a view screen. Additional stations are allowed, but if not listed, they are assumed to not be present. Stations may be combined if the combinations are logical. Typically, at least the navigation/helm station is at the fore central section of the bridge, but the specific arrangement of other stations varies between vessel types.

### Main Engineering
This section should include, at minimum, the orientation of the warp core in the room, where the core is located in the room, and any applicable side chambers (e.g. a Chief Engineer’s office). Any additional operationally-related locations which require further information (e.g. Cetacean Ops) should be in their own subsection.

### Science Labs
This section should include the functions (albeit not necessarily an exhaustive list) which the general laboratory areas on the ship are capable of performing, as well as whether there are specific offices or functions in the general labs which are of note. Any specialized labs which require further detail beyond simply being named and listed (e.g. Astrometrics, Stellar Cartography, Cybernetics, if they deviate from those seen in canon sources) should be in their own subsection.

### Brig
This section should include a description of the number, capacity, and type of holding cells aboard the starship. Given the brigs seen in various canon sources, a typical cell count is a minimum of two, with roughly 1 per 200 crew. Any additional Security facilities (e.g. Armory, Training Facilities, Security Offices) should be in their own subsection.

### [Additional Locations]
Other sections that may be included in Command And Support Systems include official meeting areas (e.g. a Briefing Room, a Conference Room, Diplomatic Reception Hall), offices (e.g. the Captain’s Ready Room), and any locations for supporting non-standard departments (e.g. Marines, Intelligence). The subsection should include, at minimum, the area’s location aboard the ship, its general purpose, layout, and technological capabilities (if outside of the regular setup in a comparable standard location). Additionally, if the specification, for whatever reason, prohibits the presence of certain non-standard crew, this should be noted in a separate subsection.

## Utility Systems
This section deals with all systems and areas of a ship that support and aid in the maintenance of the ship and crew. These systems include Cargo Bays, Tractor Beams, Transporter Pads, and Turbolifts, but other areas may be included here if the designer can reasonably display that they do not fit elsewhere in the specification. The sections detailed below are required for all specifications, and a Turbolift system may be detailed without objection to its presence.

### Cargo Bay
At minimum, a ship should have one cargo holding location, although this number should increase with the size of the ship. The description of locations, general size, and how to access the cargo bays must be included. Cargo transporters, if not mentioned, are assumed to not be present; if they are present, the description must include, at minimum, quantity, location, and range, and may only be used to transport nonliving matter. [Cargo transporters are assumed to be able to transport anything which the bay itself can hold, but a designer can include mass or volume limits if so desired.]

### Transporters
At minimum, transporter rooms must state their location and the number of pads. Transporter pads typically are multiples of two. Similarly, if a ship has multiple transporter rooms, the transporter rooms are to be multiples of two. Unless otherwise stated, a transporter room has six pads and the transporter’s range is 40,000 kilometers (i.e. low orbit for an Earth-sized planet). Emergency transporters must be mentioned if they are onboard. They are outbound-only, and are limited to 15,000 kilometers (typically close enough to reach another vessel, or to escape an otherwise fatal crash-landing).

### Tractor Beam
Tractor beam systems with location and range should also be included here. Range and capacity of the tractor system is dependent on payload mass and delta-v (acceleration, vis, change in velocity). At a nominal delta-v of 5 m/sec^2, the main tractor beam emitters are capable of handling a mass of 7,500,000 metric tonnes at less than 1,000 meters. For a mass of one metric ton at the same delta-v, the effective range is 20,000 kilometers. The main tractor emitters use a pair of 16 Megawatt graviton polarity sources, for a total of 32 Megawatt graviton displacement power. (The above numbers are taken from the TNG Technical Manual.)

## Crew Support Systems
This section includes all “on duty” locations for the Medical department, as well as “off duty” locations for the entire crew. Descriptions of Sickbay, Crew Quarters, Lounges, and Recreational Facilities must be given. In-depth descriptions of these areas should be included here as subsections; any mission critical area on the Deck Plans not described here is assumed to have a similar layout, if not similar technology, to a *TNG*/*DS9*-era vessel (e.g. *Galaxy*-class or *Sovereign*-class for large vessels, *Intrepid*-class or *Nebula*-class for mid-size vessels, *Defiant*-class or *Nova*-class for small vessels). Given the current club year, use of Paramount+ exclusive sources set in the club year’s time frame (e.g. Picard, Lower Decks) for indirect reference is acceptable, but not mandatory.

### Sickbay
This section describes the central location for the ship’s Medical department. The location, number of biobeds, other treatment areas and equipment, and a basic description of the Chief Medical Officer’s Office are required. Further embellishment is allowed. Additionally, the design should treat any treatment areas directly connected to Sickbay as part of Sickbay. If the specification has multiple sickbay areas, each is to be mentioned (if all Sickbay locations are practically identical) or detailed (if they differ substantively), but do not require individual subsections. Given their specialized nature, all additional separate Medical facilities on the ship are to have their own subsection.

### Quarters
Crew quarters can either be fully detailed in a single section, or divided into separate subsections dependent upon their intended residents. In a typical vessel design, senior officers and command officers typically have better quarters than junior officers and non-commissioned officers, with quarters for guests having similar accommodations as those of senior officers. Provisions for sleeping, seating, and personal hygiene are required in all quarters, while dining and relaxation or hosting areas are optional but recommended for senior officers, guest quarters, and command staff. Replicatiors are typically not present for non-commissioned officers.

### Lounge Facilities
Areas for social gathering and food consumption (e.g. a Mess Hall, the *Galaxy*-class Ten-Forward Lounge, Observation Lounges) may be detailed here if the designer chooses. At minimum, a Mess Hall or similar must be mentioned in the Deck Layout. If an area is detailed, the description must include its purpose, seating spaces, crew provisions, and any relevant structural details (e.g. windows, pillars, or dividing walls). Each detailed area must have its own separate subsection. Generally, areas such as this should be able to provide space for, at minimum, one fifth of the assigned crew at any given time, albeit they can be smaller or larger depending upon their intent.

### Recreational Facilities
This section details places for the crew to engage in physical activity, or in various activities not available in or intended for the lounge areas. This can include gymnasiums, exercise facilities, gaming areas, concert halls, holosuites, and holodecks. This list is in no way exhaustive; if a designer includes a recreational facility the presence of which can be defended (e.g. the casinos on the Expanded Entertainment Module of the Mythology-class), the Engineering Department will typically allow it. A ship is assumed not to have a recreational facility unless it is described in a subsection or, at minimum, present on the Deck Layout.

Holosuites are one deck tall but have a limit on the types of objects and scenes they can display and the number of occupants, due to their size. Holodecks are two decks tall and have a wider range of programming options as well as a larger capacity. Unless explicitly stated, a ship is assumed to not have any holo-facilities.

Any sections of the ship which can be configured for environments other than Class M with approximately 1.0g gravity should be listed here as well. If no such areas are specified it is assumed that the ship is incapable of any significant environmental variation.

## Auxiliary Spacecraft Systems
This section details the location of any shuttlebays, runabout pads, etc., as well as the ship's complement of auxiliary craft. Unless otherwise stated, a ship is assumed to not possess any auxiliary or support craft facilities. Auxiliary craft includes shuttlepods (sublight only), shuttlecraft (very limited warp, less than warp 2 in most cases), runabouts, fighters, bombers, and the captain's yacht, if applicable. Additional craft, such as the Maverick’s Evacuation Section, would also be listed here, in addition to their mention in the Structure section above. Specific auxiliary vessel designs available for use are present in the Technical Manual.

For reference, the Galaxy-class carries a complement of 10 standard personal shuttles (the limited warp kind), and the Captain’s Yacht is at the lowest point on its primary hull.

## Technical Specifications
[This is perhaps the most important section, and the one with the strictest layout. It is a series of nested headers. Unless otherwise specified, all entries are mandatory and must use the given numerical system and formatted layout.]

### Dimensions & Structure
#### Length
X meters
#### Beam (Width)
X meters
#### Height
X meters
#### Decks
X

[Height divided by deck count should be between 4.2 and 4.8 meters per deck except in unusual circumstances, such as a freighter in which there will be many decks that are just cargo holds, and therefore don't really exist.]

### Crew Complement:
#### Officers and Crew
X
##### Command
XX [OPTIONAL]
##### Engineering
XX [OPTIONAL]
##### Medical
XX [OPTIONAL]
##### Science
[OPTIONAL]
##### Security
XX [OPTIONAL]
##### Other Departments
XX [OPTIONAL]
#### Visiting Personnel
X
#### Maximum Evacuation Limit
X

### Computer Systems:
#### Core
Data storage and operation as described
#### Software
Starfleet Library Computer Access and Retrieval System (LCARS) unless otherwise specified
#### Interface
MAJEL unless otherwise specified

[The above may be expanded to include chipset, OS and UI modules, etc. at the discretion of the designer. This is intended primarily to allow for systems such as ENINTADI, GALEN, Linnux, etc., and are mostly literary embellishment.]

### Warp Systems:
#### Power Plant
One X+ Cochrane Class X M/ARA core feeding X nacelles
#### Cruising Velocity
Warp X
#### Maximum Warp
Warp X
#### Max. Sustainable Velocity (12 Hours)
Warp X
#### Emergency Speed
Warp X

### Impulse Systems:
#### Full Impulse
0.Xc
#### Zero-0.Xc
Blank seconds
#### 0.Xc-Zero
Blank seconds

### Defensive Systems
#### Shield Maximum Graviton Load (Continuous)
Blank MW
#### Shield Maximum Energy Dissipation Rate
Blank x 10^5 kW

### Offensive Systems:
#### Torpedoes
##### Tubes
2x Type-X Launcher
##### Standard Payload
X Standard Photon Torpedo Casings
#### Phaser system
X Type-Whatever phaser arrays

## Deck Layout
### Deck 1
Insert Location Here
Insert Other Locations
### Deck 2
Insert Location Here
Insert Other Locations
### Deck Etc.
Go on to the rest of the ship

## Ships Of Class
The naming convention of the vessel may be described here, but is not required. At minimum, the names of five (for NPC/Support specifications) or ten (for PC/Primary specifications) vessels are to be listed here. Given the time frame of the club at large, registry numbers for main sim vessels should be above 80000 unless the designer gives an acceptable explanation. Any PC/Primary specifications can have up to one fifth of listed vessels designated for NPC use.

*USS X*, __NCC-Y (Class Ship)__
*USS X1*, __NCC-Y+1__

Etc.

## Conclusion
Provide a summary of the specification, potentially using information derived from the History and Mission Overview, to establish a final statement on the intention and potential for the design. Limit this section to a single paragraph.

Submitted on DD Month YYYY by Author Name

History

It was an idea long in coming. For years, ED regulars had debated the idea of a standardized format for ship specs to make it easier to compare and review spec proposals and to make it easier for STFers to look up the information they wanted. The first idea, an internal plan by Mike Ballway and Larry Garfield known as “ZMP Format”, never saw the light of day.

Colin Wyers revived the idea with a massive proposal and argument in favor of the concept in September of 1999, but it was not until he had left STF that the SSSF would finally become a reality. Under pressure from Engineering Director Owen Townes, Larry Garfield compiled the first draft of what would later become the SSSF in September of 2000. It was finally approved by Engineering Director Townes in October of 2000, and on 15 October Townes decreed that all specs were required to conform to the SSSF by 15 April 2000, Insurance Day. A minor upgrade, SSSF 2.0, was released on 19 February. SSSF 2.1, including clarifications on where certain ship systems should go, was finalized in August 2001.

The migration of the Technical Manual from the XML-based DocBooks coding format to the Markdown WYSIWYG coding format, as well as changing from GitHub to the site itself for hosting the original documents, required an additional update. Nicholas Villarreal, as part of the Engineering Department, upgraded this style guide into what would become SSSF Exodus. Engineering Director Robert Archer approved the SSSF, Exodus Edition on July 23, 2024.