Difference between revisions of "Fleet Contact Management System (CMS)"
From Siglerpedia
Scottsigler (Talk | contribs) (→Use in STC Environments) |
Scottsigler (Talk | contribs) (→CMS Naming Conventions) |
||
| Line 12: | Line 12: | ||
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. | 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 == | |
| − | + | {| class="wikitable" | |
| − | + | ! Contact Type !! Designation Format !! Notes | |
| − | + | |- | |
| − | + | | '''Unknown Contacts''' || Master One, Master Two, etc. || Temporary designation until identification is confirmed. | |
| − | + | |- | |
| − | + | | '''Enemy Ships''' || Aardvark, Viper, etc. || Assigned unique codenames upon identification; persistent through engagement. | |
| − | + | |- | |
| − | + | | '''Enemy Torpedoes''' || Tiger-One, Tiger-Two, etc. || Numbered in order of detection regardless of launch platform. | |
| − | + | |- | |
| − | + | | '''Enemy Missiles''' || Mallet-One, Mallet-Two, etc. || Used for short-range void missiles. | |
| − | + | |- | |
| − | + | | '''Enemy Ship-Killer Missiles''' || Vampire-One, Vampire-Two, etc. || Identifies high-threat long-range missiles. | |
| − | + | |- | |
| − | + | | '''Enemy Fighters''' || Fang-One, Fang-Two, etc. || Covers single-pilot voidcraft of enemy origin. | |
| − | + | |- | |
| − | + | | '''Enemy APCs''' || Tusk-One, Tusk-Two, etc. || Assault transport craft; tracked similarly to fighters. | |
| − | + | |- | |
| − | + | | '''Friendly Torpedoes (Keeling-Launched)''' || Keeling Mark14-One, Mark15-One, Mark16-One || Display codename: ''Tadpole''; class and launch order used for precision tracking. | |
| − | + | |- | |
| − | + | | '''Friendly Missiles''' || Union Mallet-One, etc. || If used by other Union ships; class/launch order standard. | |
| − | + | |- | |
| − | + | | '''Friendly Fighters''' || Salamander Echo-Five, etc. || Identified by callsign or tail number. | |
| − | + | |- | |
| − | + | | '''Friendly APCs''' || Ochthera Bravo-One, etc. || Unit and craft name included in designation. | |
| − | + | |} | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
== Visual Display Conventions == | == Visual Display Conventions == | ||
Revision as of 14:45, 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
| Contact Type | Designation Format | Notes |
|---|---|---|
| Unknown Contacts | Master One, Master Two, etc. | Temporary designation until identification is confirmed. |
| Enemy Ships | Aardvark, Viper, etc. | Assigned unique codenames upon identification; persistent through engagement. |
| Enemy Torpedoes | Tiger-One, Tiger-Two, etc. | Numbered in order of detection regardless of launch platform. |
| Enemy Missiles | Mallet-One, Mallet-Two, etc. | Used for short-range void missiles. |
| Enemy Ship-Killer Missiles | Vampire-One, Vampire-Two, etc. | Identifies high-threat long-range missiles. |
| Enemy Fighters | Fang-One, Fang-Two, etc. | Covers single-pilot voidcraft of enemy origin. |
| Enemy APCs | Tusk-One, Tusk-Two, etc. | Assault transport craft; tracked similarly to fighters. |
| Friendly Torpedoes (Keeling-Launched) | Keeling Mark14-One, Mark15-One, Mark16-One | Display codename: Tadpole; class and launch order used for precision tracking. |
| Friendly Missiles | Union Mallet-One, etc. | If used by other Union ships; class/launch order standard. |
| Friendly Fighters | Salamander Echo-Five, etc. | Identified by callsign or tail number. |
| Friendly APCs | Ochthera Bravo-One, etc. | Unit and craft name included in designation. |
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.
