System Interdependency Matrix
UR E26 §3.2.1 Goal: The Identify functional element aims to identify the ship’s computer-based systems (CBS) and their interdependencies. Understanding how data flows between the Engine Room and the Bridge is mandatory for establishing the vessel’s resilience profile.
1. Defining Functional Connections
A vessel is a “system of systems.” The Interdependency Matrix documents the Critical Path of data. If a core system like the GPS or the Power Management System (PMS) is compromised, the matrix visualizes the “ripple effect” across the rest of the ship’s Computer Based Systems (CBS).
2. Core Dependency Model
Use the following logic to map your Category II and III systems:
| Primary System (Source) | Dependent System (Target) | Dependency Type | Impact of Failure |
|---|---|---|---|
| GPS / GNSS | ECDIS, AIS, Radar, VDR | Data (NMEA 0183/2k) | Loss of Positional Integrity |
| Power Management (PMS) | Main Engine Control, AMS | Control Logic / Power | Total Blackout / Loss of Propulsion |
| IAS / AMS | Remote Control Stations | Monitoring Data | Blindness to Engine Room Status |
| SATCOM | Chart Update Server, IT Network | External Connectivity | Loss of Remote Support/Updates |
Interdependencies Mapped?
Pillar B Complete. Now that the technical mapping is finished, you must define the human element: roles, responsibilities, and change management policies.