Difference between revisions of "Fleet Contact Management System (CMS)"
Scottsigler (Talk | contribs) (→Visual Display Conventions) |
Scottsigler (Talk | contribs) |
||
| Line 9: | Line 9: | ||
== Naming Protocol == | == Naming Protocol == | ||
| − | + | ||
| − | * | + | The Fleet Contact Management System (CMS) assigns alphanumeric codenames to detected contacts based on object type and origin (friendly or hostile). Initial unknowns are designated as "Master One," "Master Two," etc. Once classified, these designations are replaced with type-based codenames. Friendly units use class identifiers, while hostile contacts receive distinct, non-overlapping labels. |
| − | ** Torpedoes: ''Tiger-One, Tiger-Two'' | + | |
| − | ** Missiles: '' | + | === CMS Naming Conventions === |
| − | ** Fighters: ''Fang-One, Fang-Two'' | + | |
| − | ** | + | * '''Master One, Master Two, etc.''' |
| − | * | + | ** Temporary designators for unidentified contacts. |
| − | * | + | ** Once identified, reassigned with proper nomenclature. |
| + | |||
| + | * '''Enemy Ships:''' | ||
| + | ** Assigned codenames like ''Aardvark,'' ''Viper,'' etc. | ||
| + | ** Designations are persistent once confirmed. | ||
| + | |||
| + | * '''Enemy Torpedoes:''' | ||
| + | ** Designated as: '''Tiger-One, Tiger-Two,''' etc. | ||
| + | ** Numbered in order of detection regardless of launch platform. | ||
| + | |||
| + | * '''Enemy Missiles:''' | ||
| + | ** Designated as: '''Mallet-One, Mallet-Two,''' etc. | ||
| + | ** Used for short-range void missiles. | ||
| + | ** Ship-killer missiles specifically designated as '''Vampire-One, Vampire-Two,''' etc. | ||
| + | |||
| + | * '''Enemy Fighters:''' | ||
| + | ** Designated as: '''Fang-One, Fang-Two,''' etc. | ||
| + | |||
| + | * '''Enemy APCs:''' | ||
| + | ** Designated as: '''Tusk-One, Tusk-Two,''' etc. | ||
| + | |||
| + | * '''Friendly Torpedoes (Keeling-Launched):''' | ||
| + | ** Designated by class and launch order: '''Keeling Mark14-One, Keeling Mark15-One, Keeling Mark16-One''' | ||
| + | ** Codename used in display system: '''Tadpole''' | ||
| + | ** Always prefixed with ''Keeling'' for clarity in mixed engagements. | ||
| + | |||
| + | * '''Friendly Missiles:''' | ||
| + | ** Designated by class and launch order (if used by other ships): e.g., '''Union Mallet-One''' | ||
| + | |||
| + | * '''Friendly Fighters:''' | ||
| + | ** Designated by callsign or tail number (e.g., '''Salamander Echo-Five''') | ||
| + | |||
| + | * '''Friendly APCs:''' | ||
| + | ** Designated by craft name and unit (e.g., '''Ochthera Bravo-One''') | ||
== Visual Display Conventions == | == Visual Display Conventions == | ||
Revision as of 14:42, 15 April 2025
Fleet Contact Management System (CMS) is the contact tracking and designation protocol used by the Planetary Union Fleet in The Crypt series. It is a comprehensive naming and visualization system used to monitor ships, torpedoes, missiles, fighters, and unknowns within a combat environment, especially within the navigation orb (nav-orb) of the PUV James Keeling.
Contents
Overview
The CMS allows Fleet personnel to:
- Track unknown or hostile contacts in real-time
- Assign unique designators to new contacts (e.g., "Master One")
- Transition contact names as information becomes available
- Visually identify contacts on tactical displays, such as the nav-orb
Naming Protocol
The Fleet Contact Management System (CMS) assigns alphanumeric codenames to detected contacts based on object type and origin (friendly or hostile). Initial unknowns are designated as "Master One," "Master Two," etc. Once classified, these designations are replaced with type-based codenames. Friendly units use class identifiers, while hostile contacts receive distinct, non-overlapping labels.
CMS Naming Conventions
- Master One, Master Two, etc.
- Temporary designators for unidentified contacts.
- Once identified, reassigned with proper nomenclature.
- Enemy Ships:
- Assigned codenames like Aardvark, Viper, etc.
- Designations are persistent once confirmed.
- Enemy Torpedoes:
- Designated as: Tiger-One, Tiger-Two, etc.
- Numbered in order of detection regardless of launch platform.
- Enemy Missiles:
- Designated as: Mallet-One, Mallet-Two, etc.
- Used for short-range void missiles.
- Ship-killer missiles specifically designated as Vampire-One, Vampire-Two, etc.
- Enemy Fighters:
- Designated as: Fang-One, Fang-Two, etc.
- Enemy APCs:
- Designated as: Tusk-One, Tusk-Two, etc.
- Friendly Torpedoes (Keeling-Launched):
- Designated by class and launch order: Keeling Mark14-One, Keeling Mark15-One, Keeling Mark16-One
- Codename used in display system: Tadpole
- Always prefixed with Keeling for clarity in mixed engagements.
- Friendly Missiles:
- Designated by class and launch order (if used by other ships): e.g., Union Mallet-One
- Friendly Fighters:
- Designated by callsign or tail number (e.g., Salamander Echo-Five)
- Friendly APCs:
- Designated by craft name and unit (e.g., Ochthera Bravo-One)
Visual Display Conventions
Contacts are represented in the nav-orb using shape and fill conventions:
Visual Display Conventions
The nav-orb displays contacts using standardized shapes and colors for quick visual parsing under combat conditions. This table summarizes the conventions used aboard Planetary Union vessels, including the PUV James Keeling.
| Contact Type | Icon | Color | Notes |
|---|---|---|---|
| Friendly Ship | Circle (outline) | Blue | Includes Keeling |
| Enemy Ship | Circle (solid) | Red | Assigned codename upon ID |
| Friendly Fighter | Delta (outline) | Blue-Green | Salamanders |
| Enemy Fighter | Delta (solid) | Red-Orange | Labeled as Fang |
| Friendly Torpedo | Triangle (outline) | Purple | Mark14/15/16; labeled Tadpole |
| Enemy Torpedo | Triangle (solid) | Rust | Labeled as Tiger |
| Friendly Missile | Cross (outline) | Indigo | Rare use |
| Enemy Missile | Cross (solid) | Yellow | Labeled as Mallet or Vampire |
| Friendly APC | Square (outline) | Blue | Ochtheras |
| Enemy APC | Square (solid) | Rust | Labeled as Tusk |
| Unknown Contact | Hollow Hexagon | White | Labeled Master One, Master Two, etc. |
| Under STC Distortion | Any shape (fuzzy) | Gray static overlay | Tracking unreliable |
The nav-orb displays contacts using standardized shapes and colors for quick visual parsing under combat conditions. This table summarizes the conventions used aboard Planetary Union vessels, including the PUV James Keeling.
| Contact Type | Shape | Fill | Color Family | Notes |
|---|---|---|---|---|
| Friendly Ship | Circle | Outline | Blue | Confirmed friendly; fill remains outline even under STC |
| Enemy Ship | Circle | Solid | Red | Confirmed hostile |
| Friendly Fighter | Triangle | Outline | Blue-Green | SPAC or voidcraft under friendly control |
| Enemy Fighter | Triangle | Solid | Red-Orange | Small hostile craft |
| Friendly Torpedo | Diamond | Outline | Blue-Purple | Includes bat-brain–guided Mark 16s |
| Enemy Torpedo | Diamond | Solid | Rust | Rust is Fleet-standard for enemy torpedoes |
| Friendly Missile | Cross | Outline | Green-Blue | Typically ship-launched |
| Enemy Missile | Cross | Solid | Yellow-Orange | Ship- or fighter-launched |
| Unknown / Unconfirmed | Circle (fuzzy or blinking) | Variable | White / Gray | Indicates STC distortion or insufficient data |
| STC-Affected Contact | Any | "Fuzzy" | Distorted color | Visual representation shimmers or pulses |
Transition Examples
- A new blip appears in the nav-orb: it's assigned Master One.
- Once confirmed as a torpedo, the name changes to Tiger-One.
- Once trajectory, engine profile, or signal signature confirms it as a Mark16 torpedo, it is renamed Tiger-One (Fleet Mark16).
- If it is intercepted or destroyed, its designation is removed.
Use in STC Environments
Because of STC distortion, contacts often appear distorted, "fuzzy," or incomplete. CMS operators must use experience and limited signal data to update contact designations. Visual aids and callouts help the Conn and Weapons stations react under combat stress.
