In maritime command-and-control, what is the primary difference between platform-centric and sensor-centric approaches?

• A. Platform-centric focuses on weather data; sensor-centric focuses on communications
• B. Platform-centric organizes data around units; sensor-centric around data streams
• C. Platform-centric uses satellite links; sensor-centric uses line-of-sight
• D. Platform-centric is slower; sensor-centric is faster due to encryption

Answer: (B)

The main idea is how information is organized and accessed in the battle picture. In a platform-centric approach, the system is structured around the assets themselves—each ship, aircraft, or unit carries its own data and the command picture is built from that platform’s status, sensors, and reports. It tends to tie data and decisions to the individual platforms, making it straightforward to manage asset-level tasks but harder to fuse multiple sensors across platforms.

In a sensor-centric approach, the emphasis is on the data streams from sensors. Sensor data from any platform is aggregated, fused, and made interoperable, so the situational picture is built from streams rather than from the identity of a single platform. This enables cross-platform sensor fusion, flexible re-tasking of sensors, and a more networked view of the battlespace, where data is the primary element and platforms are just sources of that data.

So, organizing around units versus organizing around data streams captures the fundamental distinction: platform-centric centers on the asset as the data hub; sensor-centric centers on the data flows from sensors and how they can be combined across platforms. The other options describe unrelated aspects (weather vs comms, satellite vs line-of-sight, or encryption-related speed) and don’t define the core difference between these two approaches.