7. One-Consul Unified Console Architecture
Back to this item in New Technology Catalog
One compact console, one operator position: the lower touchscreen is integrated into the worktable, the primary monitor is directly ahead, and the third monitor is mounted above it. Authorized Bridge, CIC, ATC, DMC, engineering, electrical, and damage-control roles load onto this common physical station while their underlying ship systems remain separated behind controlled interfaces.
How ONE Works
- Subsystems remain independent: combat, navigation, engineering, electrical, aviation, DMC, and damage-control systems retain their own certified functions and safety boundaries.
- Government-owned interfaces connect them: controlled APIs and data services expose authorized status, alerts, and operator actions to the common ONE environment.
- The watch role loads at login: a qualified operator receives the Bridge, CIC, ATC, DMC, engineering, electrical, or damage-control layout assigned to that station and watchbill.
- Controls follow the role: touch displays provide adaptable layouts while programmable rotary controls, backlit keys, trackballs, and guarded switches preserve tactile operation for critical actions.
- Roles can move when required: an authorized layout can be restored on another qualified ONE station after equipment loss, watch-station reconfiguration, or compartment damage.
Architecture boundary: ONE is not one computer operating the entire ship. It is the common operator-facing environment above separated ship systems, with access control, safety interlocks, local fallback controls, and degraded-mode procedures retained where required.
Comparison With Existing Options
| Decision Area | Dedicated Legacy Console | CDS/TSCE-Style Current Bridge | Proposed ONE Baseline |
|---|---|---|---|
| Primary model | One equipment set and one fixed watch function. | Standardized digital consoles integrated into a ship or mission-system family. | One fleet-wide operator environment with role-based layouts across FFG, DDG, and CAG. |
| Controls | Fixed switches, indicators, and equipment-specific panels. | Digital displays with keyboard, trackball, and vendor-integrated controls. | Touch displays plus programmable tactile controls and guarded critical-function switches. |
| Baseline control | Driven largely by the individual equipment supplier. | Navy requirements and standards with substantial contractor implementation and integration. | Government-owned HMI, interfaces, configuration model, and software baseline; competed hardware and integration. |
| Cross-class commonality | Low; retraining follows each equipment or ship change. | Improved, but commonly bounded by platform and integration baseline. | FFG, DDG, and CAG use the same core interaction rules, widgets, alerts, and control conventions. |
| Role reassignment | Normally requires a different physical station. | Possible where the installed mission system and permissions support it. | Designed so authorized roles can move among qualified stations without changing the underlying subsystem certification. |
| Technology insertion | Equipment-specific redesign and replacement. | Contracted hardware, software, and ship-integration update. | New systems enter through controlled services and reusable HMI components under a government configuration baseline. |
| Fallback | Local fixed controls are inherent to the station. | Current CDS-style hardware and mission-system procedures remain available during transition. | Protected local controls, degraded-mode layouts, and CDS-style fallback remain until ONE completes certification. |
| Maturity | Fielded and proven, but inflexible. | Fielded and the practical near-term baseline. | Proposed development requiring human-factors testing, cyber qualification, safety certification, and shipboard trials. |
What It Is
- Acronym meaning: ONE = Operational Networked Environment.
- Core function: one government-owned console environment and watch-station baseline across FFG, DDG, and CAG.
- Node coverage: Bridge, CIC, ATC, DMC, engineering, electrical, and other key watch stations.
- Physical concept: touchscreen displays combined with programmable knobs, switches, and guarded controls for critical functions.
- Design goal: crews should move between classes with the same core human-machine interface instead of relearning ship-unique consoles.
Why We Are Doing It
- Give the fleet one common operating environment across FFG, DDG, and CAG.
- Cut training time, improve watch-team transferability, and preserve command continuity under damage or degraded operations.
- Prevent vendor lock-in by keeping the software baseline, interface rules, and HMI standards under government control.
Used Today / What It Counters
- Used today: Zumwalt and Ford families already use integrated console and mission-system environments, but they are still heavily contractor-integrated in practice.
- Zumwalt example: TSCE-style integrated mission environment ties together combat, C4I, machinery, damage control, and support systems.
- Console example: CDS gives the fleet a standardized console family, but the hardware and much of the integration are still delivered through vendors.
- Counters: fragmented class-specific consoles, contractor-defined implementations, and the difficulty of changing workflows without reopening a vendor-owned ecosystem.
Current Stop Gap
- Current stopgap: CDS-style console families and TSCE-like integrated mission environments remain the practical bridge until ONE is approved and fielded.
Next Flight Implementation Steps
- Lock ONE user-interface standards, control logic, and role-based layouts across Bridge, CIC, ATC, DMC, and engineering.
- Define the government-owned interface model so combat, machinery, aviation, and support systems plug into ONE through common APIs and service rules.
- Deploy via next-flight installs and scheduled refit backfits with one common training pipeline.
Options and Styles
- Console Styles: Bridge, CIC, ATC, DMC, engineering, and electrical profiles all run on the same baseline architecture.
- System Position: ONE sits above ship subsystems as the common console runtime and below fleet mission systems as the operator-facing layer.
- Training Style: one cross-class operator framework with role-based overlays instead of ship-unique consoles.
Mounting and Integration Particulars
- Installed as standardized console/workstation hardware with government-owned software and interface definitions across command spaces.
- Integrated into Bridge, CIC, ATC, DMC, engineering, and support nodes through one common data and control architecture.
- Contractors still build hardware and help integrate systems, but the fleet owns the baseline and can compete future upgrades without being trapped in one vendor stack.