Difference between revisions of "Fleet Contact Management System (CMS)"
From Siglerpedia
Scottsigler (Talk | contribs) (→CMS Naming Conventions) |
Scottsigler (Talk | contribs) (→CMS Naming Conventions) |
||
| Line 14: | Line 14: | ||
== CMS Naming Conventions == | == CMS Naming Conventions == | ||
| + | === Hostile Contacts === | ||
{| class="wikitable" | {| class="wikitable" | ||
| − | ! Contact Type !! Designation Format !! Notes | + | ! Contact Type !! Designation Format !! Notes !! Nav-Orb Icon |
|- | |- | ||
| − | | '''Unknown Contacts''' || Master One, Master Two, etc. || Temporary | + | | '''Unknown Contacts''' || Master One, Master Two, etc. || Temporary designators until confirmed. || '''Solid circle (fuzzy if under STC)''' |
|- | |- | ||
| − | | '''Enemy Ships''' || Aardvark, Viper, etc. || Assigned | + | | '''Enemy Ships''' || Aardvark, Viper, etc. || Assigned persistent codenames once confirmed. || '''Solid arrow''' |
|- | |- | ||
| − | | '''Enemy Torpedoes''' || Tiger-One, Tiger-Two, etc. || Numbered in order of detection | + | | '''Enemy Torpedoes''' || Tiger-One, Tiger-Two, etc. || Numbered in order of detection, not by launch ship. || '''Solid triangle''' |
|- | |- | ||
| − | | '''Enemy Missiles''' || Mallet-One, Mallet-Two, etc. || | + | | '''Enemy Missiles''' || Mallet-One, Mallet-Two, etc. || Short-range void-to-void missiles. || '''Solid cross''' |
|- | |- | ||
| − | | '''Enemy Ship-Killer Missiles''' || Vampire-One, Vampire-Two, etc. || | + | | '''Enemy Ship-Killer Missiles''' || Vampire-One, Vampire-Two, etc. || Long-range capital-killers. High priority. || '''Solid cross (highlighted or red)''' |
|- | |- | ||
| − | | '''Enemy Fighters''' || Fang-One, Fang-Two, etc. || | + | | '''Enemy Fighters''' || Fang-One, Fang-Two, etc. || Single-pilot voidcraft. || '''Solid chevron''' |
|- | |- | ||
| − | | '''Enemy APCs''' || Tusk-One, Tusk-Two, etc. || Assault | + | | '''Enemy APCs''' || Tusk-One, Tusk-Two, etc. || Assault boarding transports. || '''Solid diamond''' |
| + | |} | ||
| + | |||
| + | === Friendly Contacts === | ||
| + | {| class="wikitable" | ||
| + | ! Contact Type !! Designation Format !! Notes !! Nav-Orb Icon | ||
| + | |- | ||
| + | | '''Friendly Ships''' || Keeling, Union-class identifiers || Known vessels shown by name or class. || '''Outlined arrow''' | ||
|- | |- | ||
| − | | '''Friendly Torpedoes | + | | '''Friendly Torpedoes''' || Keeling Mark14-One, Mark15-One, Mark16-One || Display codename: ''Tadpole''. Track by type and launch order. || '''Outlined triangle''' |
|- | |- | ||
| − | | '''Friendly Missiles''' || Union Mallet-One, etc. || | + | | '''Friendly Missiles''' || Union Mallet-One, etc. || Used by other Fleet ships only. || '''Outlined cross''' |
|- | |- | ||
| − | | '''Friendly Fighters''' || Salamander Echo-Five, etc. || | + | | '''Friendly Fighters''' || Salamander Echo-Five, etc. || Designated by callsign or tail number. || '''Outlined chevron''' |
|- | |- | ||
| − | | '''Friendly APCs''' || Ochthera Bravo-One, etc. || | + | | '''Friendly APCs''' || Ochthera Bravo-One, etc. || Denoted by craft and unit name. || '''Outlined diamond''' |
|} | |} | ||
| + | |||
| + | === Nav-Orb Icon Key === | ||
| + | * '''Arrow''' — Ship | ||
| + | * '''Triangle''' — Torpedo | ||
| + | * '''Cross''' — Missile | ||
| + | * '''Chevron''' — Fighter | ||
| + | * '''Diamond''' — APC | ||
| + | * '''Fuzzy''' — Object under STC distortion | ||
| + | * '''Solid shapes''' — Hostile contacts | ||
| + | * '''Outlined shapes''' — Friendly contacts | ||
== Visual Display Conventions == | == Visual Display Conventions == | ||
Revision as of 14:47, 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
Hostile Contacts
| Contact Type | Designation Format | Notes | Nav-Orb Icon |
|---|---|---|---|
| Unknown Contacts | Master One, Master Two, etc. | Temporary designators until confirmed. | Solid circle (fuzzy if under STC) |
| Enemy Ships | Aardvark, Viper, etc. | Assigned persistent codenames once confirmed. | Solid arrow |
| Enemy Torpedoes | Tiger-One, Tiger-Two, etc. | Numbered in order of detection, not by launch ship. | Solid triangle |
| Enemy Missiles | Mallet-One, Mallet-Two, etc. | Short-range void-to-void missiles. | Solid cross |
| Enemy Ship-Killer Missiles | Vampire-One, Vampire-Two, etc. | Long-range capital-killers. High priority. | Solid cross (highlighted or red) |
| Enemy Fighters | Fang-One, Fang-Two, etc. | Single-pilot voidcraft. | Solid chevron |
| Enemy APCs | Tusk-One, Tusk-Two, etc. | Assault boarding transports. | Solid diamond |
Friendly Contacts
| Contact Type | Designation Format | Notes | Nav-Orb Icon |
|---|---|---|---|
| Friendly Ships | Keeling, Union-class identifiers | Known vessels shown by name or class. | Outlined arrow |
| Friendly Torpedoes | Keeling Mark14-One, Mark15-One, Mark16-One | Display codename: Tadpole. Track by type and launch order. | Outlined triangle |
| Friendly Missiles | Union Mallet-One, etc. | Used by other Fleet ships only. | Outlined cross |
| Friendly Fighters | Salamander Echo-Five, etc. | Designated by callsign or tail number. | Outlined chevron |
| Friendly APCs | Ochthera Bravo-One, etc. | Denoted by craft and unit name. | Outlined diamond |
- Arrow — Ship
- Triangle — Torpedo
- Cross — Missile
- Chevron — Fighter
- Diamond — APC
- Fuzzy — Object under STC distortion
- Solid shapes — Hostile contacts
- Outlined shapes — Friendly contacts
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 |
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.
