Difference between revisions of "Fleet Contact Management System (CMS)"

From Siglerpedia
Jump to: navigation, search
(→‎Nav-Orb Shape & Color Conventions (MASTER TABLE))
(→‎Nav-Orb Visual Display Conventions)
 
(20 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
The CMS allows Fleet personnel to:
 
The CMS allows Fleet personnel to:
 
* Track unknown or hostile contacts in real-time
 
* Track unknown or hostile contacts in real-time
−
* Assign unique designators to new contacts (e.g., "Master One")
+
* Assign unique designators to new contacts (e.g., ''Locus One'')
 
* Transition contact names as information becomes available
 
* Transition contact names as information becomes available
 
* Visually identify contacts on tactical displays, such as the nav-orb
 
* Visually identify contacts on tactical displays, such as the nav-orb
  
 
== Naming Protocol ==
 
== Naming Protocol ==
 +
The CMS assigns alphanumeric codenames to detected contacts based on object type and origin (friendly or hostile). Initial unknowns are designated as ''Locus One,'' ''Locus Two,'' etc. Once classified, these designations are replaced with type-based codenames. Friendly units use class identifiers; 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.
+
=== Locus Designation Rules ===
 +
* All new contacts are assigned a sequential ''Locus'' identifier (e.g., ''Locus One'', ''Locus Two'').
 +
* Once a contact's type is known (e.g., torpedo, ship, fighter), its name transitions to the appropriate codename (e.g., ''Tiger-One'').
 +
* If the ''type'' of ship is identified but not the individual vessel, it becomes ''[Ship Type] + Locus number'' (e.g., ''Destroyer Locus Five'').
 +
* If the ''individual ship'' is identified via grav-sig, its codename is replaced with the ship’s name (e.g., ''ISS Renegade'').
  
−
=== CMS Naming Conventions ===
+
== CMS Naming Conventions ==
  
−
* '''Master One, Master Two, etc.'''
+
=== Hostile Contacts ===
−
** Temporary designators for unidentified contacts.
+
{| class="wikitable"
−
** Once identified, reassigned with proper nomenclature.
+
! Contact Type !! Designation Format !! Notes
 +
|-
 +
| Unknown Contacts || Locus One, Locus Two, etc. || Temporary designators until confirmed
 +
|-
 +
| Enemy Ships || Aardvark, Viper, etc. || Assigned persistent codenames once confirmed
 +
|-
 +
| Enemy Torpedoes || Tiger-One, Tiger-Two, etc. || Numbered in order of detection, not by launch ship
 +
|-
 +
| Enemy Missiles || Mallet-One, Mallet-Two, etc. || Short-range void-to-void missiles
 +
|-
 +
| Enemy Ship-Killer Missiles || Vampire-One, Vampire-Two, etc. || Long-range capital-killers. High priority
 +
|-
 +
| Enemy Fighters || Fang-One, Fang-Two, etc. || Single-pilot voidcraft
 +
|-
 +
| Enemy APCs || Tusk-One, Tusk-Two, etc. || Assault boarding transports
 +
|}
  
−
* '''Enemy Ships:'''
+
=== Friendly Contacts ===
−
** Assigned codenames like ''Aardvark,'' ''Viper,'' etc.
+
A metal arrow at the center of a nav-orb represents the ship the nav-orb is in. The icons below appear in relation to the ship's orientation. The arrow is fixed, always pointing toward the prow. When the ship maneuvers, the icons below move in relation to their orientation to the ship.
−
** Designations are persistent once confirmed.
+
  
−
* '''Enemy Torpedoes:'''
+
{| class="wikitable"
−
** Designated as: '''Tiger-One, Tiger-Two,''' etc.
+
! Contact Type !! Designation Format !! Notes
−
** Numbered in order of detection regardless of launch platform.
+
|-
 +
| Friendly Ships || Keeling, Union-class identifiers || Known vessels shown by name or class
 +
|-
 +
| Friendly Torpedoes || Keeling Mark14-One, Mark15-One, Mark16-One || Display codename: ''Tadpole''. Track by type and launch order
 +
|-
 +
| Friendly Missiles || Union Mallet-One, etc. || Used by other Fleet ships only
 +
|-
 +
| Friendly Ship-Killer Missiles || Union Vampire-One, etc. || Long-range Fleet anti-capital munitions
 +
|-
 +
| Friendly Fighters || Salamander Echo-Five, etc. || Designated by callsign or tail number
 +
|-
 +
| Friendly APCs || Ochthera Bravo-One, etc. || Denoted by craft and unit name
 +
|}
  
−
* '''Enemy Missiles:'''
+
== Nav-Orb Visual Display Conventions ==
−
** Designated as: '''Mallet-One, Mallet-Two,''' etc.
+
A metal arrow at the center of a nav-orb represents the ship the nav-orb is in. The icons below appear in relation to the ship's orientation. The arrow is fixed, always pointing toward the prow. When the ship maneuvers, the icons below move in relation to their orientation to the ship.
−
** 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''.
 
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''.
  
Line 60: Line 65:
 
! Contact Type !! Icon !! Color !! Notes
 
! Contact Type !! Icon !! Color !! Notes
 
|-
 
|-
−
| Friendly Ship || Circle (outline) || Blue || Includes Keeling
+
| Organic Ship || Circle (dashed outline) || Purple || Keeling in Keeling station displays
 +
|-
 +
| Friendly Ship || Circle (outline) || Blue ||
 +
|-
 +
| Enemy Ship || Dot (solid) || Red ||
 +
|-
 +
| Organic Fighter || Triangle (dashed outline) || Purple ||
 +
|-
 +
| Friendly Fighter || Triangle (outline) || Blue ||
 +
|-
 +
| Enemy Fighter || Triangle (solid) || Red||
 +
|-
 +
| Organic APC || Square (dashed outline) || Purple ||
 +
|-
 +
| Friendly APC || Square (outline) || Blue ||
 
|-
 
|-
−
| Enemy Ship || Circle (solid) || Red || Assigned codename upon ID
+
| Enemy APC || Square (solid) || Red ||
 
|-
 
|-
−
| Friendly Fighter || Delta (outline) || Blue-Green || Salamanders
+
| Organic Torpedo || Chevron || Purple ||  
 
|-
 
|-
−
| Enemy Fighter || Delta (solid) || Red-Orange || Labeled as Fang
+
| Friendly Torpedo || Chevron (outline) || Blue ||  
 
|-
 
|-
−
| Friendly Torpedo || Triangle (outline) || Purple || Mark14/15/16; labeled Tadpole
+
| Enemy Torpedo || Chevron (solid) || Red ||
 
|-
 
|-
−
| Enemy Torpedo || Triangle (solid) || Rust || Labeled as Tiger
+
| Organic Missile || Diamond (dashed outline) || Purple ||
 +
|-
 +
| Friendly Missile || Diamond (outline) || Blue ||  
 
|-
 
|-
−
| Friendly Missile || Cross (outline) || Indigo || Rare use
+
| Enemy Missile || Diamond (solid ) || Red ||  
 
|-
 
|-
−
| Enemy Missile || Cross (solid) || Yellow || Labeled as Mallet or Vampire
+
| Organic Artillery || Cross (dashed outline) || Purple ||
 +
|-
 +
| Friendly Artillery || Cross (outline) || Blue ||  
 
|-
 
|-
−
| Friendly APC || Square (outline) || Blue || Ochtheras
+
| Enemy Artillery || Cross (solid ) || Red ||  
 
|-
 
|-
−
| Enemy APC || Square (solid) || Rust || Labeled as Tusk
+
| Unknown Contact || Solid Hexagon || White || Labeled ''Locus One'', ''Locus Two'', etc.
 
|-
 
|-
−
| Unknown Contact || Hollow Hexagon || White || Labeled Master One, Master Two, etc.
+
| Unidentified Contact || Hexagon (outline) || Yellow || Labeled ''Locus One'', ''Locus Two'', etc.
 
|-
 
|-
 
| Under STC Distortion || Any shape (fuzzy) || Gray static overlay || Tracking unreliable
 
| Under STC Distortion || Any shape (fuzzy) || Gray static overlay || Tracking unreliable
Line 86: Line 109:
  
 
== Transition Examples ==
 
== Transition Examples ==
−
* A new blip appears in the nav-orb: it's assigned ''Master One''.
+
* A new blip appears in the nav-orb: it's assigned ''Locus One''.
 
* Once confirmed as a torpedo, the name changes to ''Tiger-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 grav-sig confirms it as a Mark16 torpedo, it is renamed ''Tiger-One (Fleet Mark16)''.
 
* If it is intercepted or destroyed, its designation is removed.
 
* If it is intercepted or destroyed, its designation is removed.
  
 
== Use in STC Environments ==
 
== 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.
+
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.
  
 
== See Also ==
 
== See Also ==
Line 102: Line 125:
 
[[Category:The Crypt]]
 
[[Category:The Crypt]]
 
[[Category:Planetary Union Fleet]]
 
[[Category:Planetary Union Fleet]]
−
[[Category:Fleet Systems]]
 
−
[[Category:Technology]]
 

Latest revision as of 19:36, 25 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.

Overview

The CMS allows Fleet personnel to:

  • Track unknown or hostile contacts in real-time
  • Assign unique designators to new contacts (e.g., Locus One)
  • Transition contact names as information becomes available
  • Visually identify contacts on tactical displays, such as the nav-orb

Naming Protocol

The CMS assigns alphanumeric codenames to detected contacts based on object type and origin (friendly or hostile). Initial unknowns are designated as Locus One, Locus Two, etc. Once classified, these designations are replaced with type-based codenames. Friendly units use class identifiers; hostile contacts receive distinct, non-overlapping labels.

Locus Designation Rules

  • All new contacts are assigned a sequential Locus identifier (e.g., Locus One, Locus Two).
  • Once a contact's type is known (e.g., torpedo, ship, fighter), its name transitions to the appropriate codename (e.g., Tiger-One).
  • If the type of ship is identified but not the individual vessel, it becomes [Ship Type] + Locus number (e.g., Destroyer Locus Five).
  • If the individual ship is identified via grav-sig, its codename is replaced with the ship’s name (e.g., ISS Renegade).

CMS Naming Conventions

Hostile Contacts

Contact Type Designation Format Notes
Unknown Contacts Locus One, Locus Two, etc. Temporary designators until confirmed
Enemy Ships Aardvark, Viper, etc. Assigned persistent codenames once confirmed
Enemy Torpedoes Tiger-One, Tiger-Two, etc. Numbered in order of detection, not by launch ship
Enemy Missiles Mallet-One, Mallet-Two, etc. Short-range void-to-void missiles
Enemy Ship-Killer Missiles Vampire-One, Vampire-Two, etc. Long-range capital-killers. High priority
Enemy Fighters Fang-One, Fang-Two, etc. Single-pilot voidcraft
Enemy APCs Tusk-One, Tusk-Two, etc. Assault boarding transports

Friendly Contacts

A metal arrow at the center of a nav-orb represents the ship the nav-orb is in. The icons below appear in relation to the ship's orientation. The arrow is fixed, always pointing toward the prow. When the ship maneuvers, the icons below move in relation to their orientation to the ship.

Contact Type Designation Format Notes
Friendly Ships Keeling, Union-class identifiers Known vessels shown by name or class
Friendly Torpedoes Keeling Mark14-One, Mark15-One, Mark16-One Display codename: Tadpole. Track by type and launch order
Friendly Missiles Union Mallet-One, etc. Used by other Fleet ships only
Friendly Ship-Killer Missiles Union Vampire-One, etc. Long-range Fleet anti-capital munitions
Friendly Fighters Salamander Echo-Five, etc. Designated by callsign or tail number
Friendly APCs Ochthera Bravo-One, etc. Denoted by craft and unit name

Nav-Orb Visual Display Conventions

A metal arrow at the center of a nav-orb represents the ship the nav-orb is in. The icons below appear in relation to the ship's orientation. The arrow is fixed, always pointing toward the prow. When the ship maneuvers, the icons below move in relation to their orientation to the ship.

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
Organic Ship Circle (dashed outline) Purple Keeling in Keeling station displays
Friendly Ship Circle (outline) Blue
Enemy Ship Dot (solid) Red
Organic Fighter Triangle (dashed outline) Purple
Friendly Fighter Triangle (outline) Blue
Enemy Fighter Triangle (solid) Red
Organic APC Square (dashed outline) Purple
Friendly APC Square (outline) Blue
Enemy APC Square (solid) Red
Organic Torpedo Chevron Purple
Friendly Torpedo Chevron (outline) Blue
Enemy Torpedo Chevron (solid) Red
Organic Missile Diamond (dashed outline) Purple
Friendly Missile Diamond (outline) Blue
Enemy Missile Diamond (solid ) Red
Organic Artillery Cross (dashed outline) Purple
Friendly Artillery Cross (outline) Blue
Enemy Artillery Cross (solid ) Red
Unknown Contact Solid Hexagon White Labeled Locus One, Locus Two, etc.
Unidentified Contact Hexagon (outline) Yellow Labeled Locus One, Locus 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 Locus One.
  • Once confirmed as a torpedo, the name changes to Tiger-One.
  • If grav-sig 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.

See Also

Retrieved from "https://siglerpedia.scottsigler.com/index.php?title=Fleet_Contact_Management_System_(CMS)&oldid=7343"