What is a common operational picture?

The short definition

The term comes from military command and control, where a common operational picture — COP for short — is the one display that lets several commands see the same situation. Civil emergency management adopted it. The US incident-management doctrine NIMS describes it as a picture that “offers an overview of an incident thereby providing incident information enabling the Incident Commander/Unified Command and any supporting agencies and organizations to make effective, consistent, and timely decisions.”

In plain words: a common operational picture answers four questions for everyone at once — where is everything, what is happening, since when, and who is acting on it.

A picture is common when the control room, the patrol and the crisis team look at the same facts — not when each of them has a screen.

Europe already works this way — in places

• The Netherlands: the 25 safety regions work “network-centrically” in LCMS, the national crisis management system that crisis partners use “to maintain a current and shared picture” — text, documents and maps shared across organisations, from the National Crisis Centre and water boards to drinking-water companies and Defence. The Netherlands Institute for Public Safety (NIPV) manages it.
• Germany: the joint reporting and situation centre of the federal government and the states, the GMLZ, run by the BBK, builds a situation picture — a Lagebild — of civil-protection events in and around Germany “in near real time”.
• France: the civil protection service uses SYNAPSE, a digital decision-support system for crisis situations that shares event information with the zonal and national levels.

These systems serve crisis staffs. The operators of the infrastructure itself — the grid control room, the port security desk, the rail operations centre — mostly still work from their own screens. And that is where incidents start.

What happens without one

In July 2021 the flood in Germany’s Ahr valley killed 135 people. The Rhineland-Palatinate parliamentary inquiry later found that in the operations command of the Ahrweiler district “the devastating, actual extent of the disaster was underestimated deep into the night, in part until the next afternoon, and was not captured, or captured too late.”

Without a shared picture, the people in charge decide on the situation they can see — not the one that exists.

What goes into it

• Where: positions of your own units, assets, vehicles, drones and sensors — live.
• What: incidents, alarms and reports, each with a status: reported, confirmed, handled.
• When: the history behind every item, so the picture can be scrolled back.
• Who: which team owns which incident, and which task.
• Context: the fixed layers — sites, fences, cable routes, zones, plans.
• Source: where every item came from, and how reliable it is.

Often confused with

Why most organisations still don’t have one

• Every organisation has its own screens. Police, operator, fire service and security each see a part.
• Data projects come first. Many projects try to collect everything in one central store before anyone sees a picture — and the store runs minutes or days behind.
• Sharing is legally hard. Not everyone may see everything. Without layers by role and legal basis, sharing simply doesn’t happen.
• The field is offline. Patrols in dead zones drop out of the picture exactly when it matters.
• The phone fills the gap. Where systems don’t connect, people call — and calls leave no trace.

What a good one needs

1. 01

   Live, not refreshed

   Seconds, not the next situation report.

2. 02

   Shared, but in layers

   Each organisation sees what its role and legal basis allow — and every query is logged.

3. 03

   Time you can scroll back

   Replay any moment for the debrief, the evaluation or the investigation.

4. 04

   Traceable

   Every item shows its source; every decision is recorded as it is made.

5. 05

   Works when the network doesn’t

   On disconnected networks and in dead zones, synchronising when the connection returns.

6. 06

   Sources stay in charge

   Source systems remain the system of record; the picture keeps only what it needs, with a link back to the source.

7. 07

   Under your own jurisdiction

   A common operational picture concentrates your most sensitive information in one place. Who can be compelled to hand it over matters.

How to start

1. 01

   Pick one incident type that hurts

   An intrusion at a remote site, a drone over the perimeter, a cable fault that might be sabotage.

2. 02

   List what the room already uses

   Alarms, cameras, radio, vehicle tracking — and the spreadsheets and phone numbers nobody wrote down.

3. 03

   Connect, don’t migrate

   Connect the sources as they are, instead of starting with a migration project.

4. 04

   Agree who sees which layer

   Before the first incident, not during it.

5. 05

   Exercise it — then replay it

   Run an exercise, scroll back through it, and fix what the picture missed.

A common operational picture is not a screen. It is an agreement about what is true right now — and the software that keeps that agreement up to date.