Overview#
Connect a NATO TIDE service endpoint and have allied ISR product metadata flow straight into the Argus coalition picture, filtered to each analyst's clearance, with no bespoke ETL to build or maintain.
In a combined joint task force, intelligence, surveillance, and reconnaissance products are generated by many nations across many sensors, and the metadata describing them needs to reach the right analysts on the right networks at the right classification. Argus implements the NATO TIDE (Theatre ISR Data Exchange) pattern so that operators can ingest ISR product metadata once and have it appear automatically on the coalition Common Operational Picture, scoped to their organisation and screened against multi-level security rules.
The result is faster shared situational awareness and a defensible audit position. Allied programme offices, national defence agencies, and commercial C4ISR integrators get a single normalised path for ISR product metadata, while accreditation teams get an evidence trail for every product handled. Analysts only ever see products they are cleared to access, which keeps combined operations compliant without slowing the people doing the work.
Last Reviewed: 2026-05-26 Last Updated: 2026-05-26
Key Features#
- TIDE Product Ingestion: Operators record ISR product metadata through the
ingestTideProductoperation, capturing product type, source sensor, collection time, geolocation, classification, quality score, and secrecy level in one normalised model. - Bidirectional TIDE Connectivity: The TIDE adapter can both push products to and pull products from an upstream TIDE service endpoint over REST, with optional bearer-token authentication, so allied metadata moves in either direction without custom plumbing.
- Clearance-Filtered Retrieval: The
tideProductsreader screens every result against the requesting user's secrecy level, removing any product whose classification exceeds their clearance before it is ever returned. - Automatic Coalition Picture Emission: Each ingested product is published as an operational mission-context entity into the coalition ISR-Fusion workspace of the Common Operational Picture, so newly arrived ISR metadata is immediately visible alongside other coalition data.
- Confidentiality-Label Alignment: Secrecy levels follow NATO confidentiality metadata label conventions, giving products a consistent, machine-readable classification marking across allied systems.
- Product Statistics: The
tideStatsreader returns per-type product counts for dashboard-level situational awareness, showing at a glance how the ISR product inventory is distributed. - Organisation Scoping: Every operation is bound to the authenticated organisation, so coalition partners share a standard while keeping their own holdings logically separated.
- Accreditation-Grade Audit Trail: Every ingest is written to the interop audit trail with the source standard, product identifiers, secrecy level, and the acting user and organisation, satisfying accreditation evidence requirements for ISR data handling.
Use Cases#
National Defence Agencies#
A NATO-aligned national agency connects its TIDE service endpoint and has allied ISR product metadata appear on the national coalition picture automatically. Analysts work from a single fused view rather than polling multiple allied catalogues, and the audit trail provides the evidence the national accreditor expects for cross-domain ISR handling.
Allied Programme Offices#
A multinational programme office operating a shared TIDE service uses Argus as the consuming picture for a combined joint task force. Clearance filtering means a single deployment can serve analysts at different classification levels, with each person seeing only the products they are authorised to access.
Commercial C4ISR Integrators#
A systems integrator delivering coalition C4ISR capability plugs a customer TIDE endpoint into Argus and reuses the normalised product model rather than writing bespoke transforms for each programme. The push and pull paths let the integrator both feed the coalition picture and republish curated holdings back to allied consumers.
Combined Joint Task Force Watch Floors#
- Intelligence watch staff monitor incoming ISR product metadata as it arrives from allied sensors, with new products surfacing on the ISR-Fusion workspace in near real time.
- Collection managers use per-type product counts to judge where collection is concentrated and where gaps are opening across the theatre.
- Security officers rely on per-user clearance filtering to keep higher-classification products off lower-clearance screens during combined operations.
Integration#
ISR product exchange is exposed over the same authenticated API surface as the rest of the platform. Operators record products through ingestTideProduct, read clearance-filtered holdings through tideProducts, and read per-type counts through tideStats. Authentication is required on every operation, and OAuth2 plus JWT bearer tokens secure access in the standard platform pattern.
The TIDE adapter is a REST connector: it submits products to the /products path on a configured TIDE service endpoint and fetches products from the same path, carrying an optional bearer token for the upstream service. Customers point the connector at their existing TIDE endpoint and gain a normalised product model, an automatic feed into the coalition picture, and a complete audit record, without building or operating any intermediary transform layer of their own.
Because every product is normalised into a common operational entity and emitted into the ISR-Fusion workspace, TIDE metadata fuses naturally with other coalition data already on the Common Operational Picture, giving analysts one place to assess allied ISR holdings.
Open Standards#
- NATO TIDE (Theatre ISR Data Exchange): The exchange pattern for intelligence, surveillance, and reconnaissance product metadata and tasking across allied nations, implemented end to end from ingest through coalition picture emission.
- STANAG 4774 (Confidentiality Metadata Label Syntax): The NATO standard for the syntax of confidentiality metadata labels, aligned to the secrecy level carried on every product so classification markings are consistent and machine-readable.
- STANAG 4778 (Metadata Binding Mechanism): The NATO standard for binding metadata, including confidentiality labels, to the data they describe, underpinning the classification markings applied across product exchange and the wider interoperability layer.
- OAuth2 and JWT: Token-based authentication and authorisation securing every read and ingest operation.
- REST over HTTP/JSON: The transport for the TIDE service connector, using standard
GETandPOSTrequests against the/productsresource withapplication/jsonpayloads.
Security & Compliance#
Multi-level security is enforced on retrieval: products carry a secrecy level, and the clearance filter removes any product whose classification exceeds the requesting user's clearance before results are returned, satisfying MLS requirements for combined joint task force environments. Every operation is scoped to the authenticated organisation, so coalition partners share a standard interface without commingling their holdings. Each ingest is written to the interop audit trail with source standard, product identifiers, secrecy level, and the acting user and organisation, providing the evidence record that NATO accreditation expects for ISR data handling.