Summary: How authorised data can be combined into a coherent, role-controlled view that supports situational awareness and coordinated decision-making.
A common operating picture, often called a COP, is a shared and controlled view of information relevant to an operation.
The purpose is not to put every available data source on one screen. It is to give authorised users a coherent picture of what is happening, where it is happening, what has changed and what actions are underway.
This article stays at a high level and focuses on information architecture and operational control.
The problem is fragmentation
Operational information may exist in reports, maps, sensor systems, incident logs, messages and separate databases.
When each source is viewed independently, users must mentally combine the picture. Different teams may also work from different versions of the same information.
A COP creates a shared information layer while preserving appropriate access controls.
Normalise before you visualise
Different sources describe information differently.
One system may use coordinates, another place names and another grid references. Time formats, status labels and identifiers can also differ.
The information-fusion layer should normalise these differences so that the display is coherent.
Putting inconsistent data on a map does not make it integrated.
Location provides context
Geospatial presentation helps users understand relationships between events, assets and areas.
A map can show position, movement, boundaries, routes or areas of interest where the data and permissions support it.
The map should remain an operational tool, not a decorative background. Layers need clear purpose and sensible defaults.
Time matters as much as location
A common picture needs to distinguish current information from historical information.
Each record should carry a meaningful timestamp and, where relevant, a status indicating freshness or confidence.
Users should not mistake an old position or unresolved report for a current fact.
Roles need different views
Commanders, analysts, operators and administrators may require different information.
Role-based views reduce clutter and help protect sensitive data. Access can also be constrained by mission, geography, organisation or information classification where appropriate.
A "common" picture does not mean identical access for everyone.
Alerts should represent defined conditions
The platform may generate alerts when a rule is met or an authorised source reports a relevant event.
Every alert needs a lifecycle: created, acknowledged, assigned, acted upon and closed.
Without workflow, alerts become another stream of noise.
Preserve source and confidence
Fused information should remain traceable to its authorised source where appropriate.
If a record has uncertainty, that should be represented rather than hidden.
Decision support becomes more trustworthy when users can distinguish observation, report, inference and confirmed status.
Build audit and dissemination control
Sensitive information environments need records of important access, edits and distribution.
The platform can support controlled dissemination so that users receive information consistent with their role and need.
Audit design should be defined alongside permissions, not added later.
Design for graceful degradation
Operational systems should define what happens when a source becomes unavailable, connectivity is reduced or data becomes stale.
The interface should surface the degradation rather than silently presenting an incomplete picture as normal.
Measure the information workflow
Useful measures can include data-source availability, alert acknowledgement, incident age, unresolved tasks and time from report to verified operational visibility.
The goal is faster, more coherent decision support.
COP design questions
Which operational questions must the picture answer? Which sources are authorised? How will time, confidence and data freshness be represented? Which roles need which layers? What happens when a source becomes unavailable? How does an alert become an assigned action?
What good looks like
Users can distinguish current information from stale information, trace significant records to their source and act from the same controlled environment. The interface reduces cognitive work instead of simply displaying more data.
REVTEK perspective
A common operating picture is an information architecture before it is a map interface. Source control, normalisation, permissions, workflow and audit determine whether the visual picture can be trusted.