Overview#
Submit, track, and report on Joint Intelligence Surveillance Reconnaissance collection tasking requests through one authenticated interface aligned with NATO AJP-27, without building a bespoke tasking system.
Coalition operations depend on getting the right sensor onto the right area of interest at the right time. Joint Intelligence, Surveillance and Reconnaissance (JISR) collection tasking is the discipline that turns an information requirement into a structured request that a collection manager can prioritise, assign to a provider, and follow through its lifecycle. The platform accepts those requests directly, captures every field of each one, and makes the whole task set available to operators and software integrators through a single, consistent, organisation-scoped interface.
Each request preserves the full tasking context: a request type, a priority from ROUTINE through FLASH, a collection type, an area of interest expressed as a GeoJSON geometry, requester and provider identifiers, a status through its lifecycle, and a secrecy level. Clearance-based filtering is applied at read time so operators only ever see requests their accreditation permits, every submission is written to the audit trail for coalition information assurance, and each task is emitted automatically into the shared operational view so command-and-control dashboards can surface pending and active collection tasking alongside other mission data in real time.
Key Features#
-
AJP-27 Aligned Tasking. Submit a JISR collection request and have every field captured in one operation. The record preserves request type, priority, collection type, area of interest, requester, provider, status, and secrecy level, keeping each task aligned with the NATO Allied Joint Publication for Joint Intelligence, Surveillance and Reconnaissance.
-
Priority From Routine To Flash. Each request carries a precedence drawn from the recognised ROUTINE through FLASH scale, so collection managers can express urgency in terms that any participating staff understands and downstream consumers can sort and escalate accordingly.
-
Geospatial Area Of Interest. The area to be collected against is carried as a GeoJSON geometry, the open geospatial format for points, lines, and polygons. A request can therefore describe a precise box, corridor, or named region that mapping tools and command dashboards can render without translation.
-
Lifecycle Status Tracking. Every request moves through a status lifecycle from pending onward, and a dedicated statistics path summarises the task set grouped by status. Watch staff see at a glance how many tasks are pending, active, or complete without trawling individual records.
-
Clearance-Based Record Filtering. Each request carries a secrecy level, and a shared interoperability bridge filters the returned task set against the requesting operator's clearance at read time. Requests above an operator's level are withheld rather than redacted, enforcing correct handling in multi-level secure coalition environments.
-
Automatic Audit Capture. Every submission writes an interoperability ingest audit record tagged with its NATO JISR source standard, carrying the record identifier, secrecy level, request type, collection type, and the acting operator and organisation. Nothing enters the task store without an immutable trail behind it.
-
Coalition Fusion Emission. On submission, each request emits an operational entity of type mission context into the coalition fusion layer, tagged with its source standard and secrecy level. Collection tasking therefore contributes to the same shared operational view as other allied data sources rather than living in isolation.
-
Organisation Data Sovereignty. All storage, reads, and statistics are scoped to the authenticated organisation, so coalition partners on the same platform never see one another's tasking traffic.
Use Cases#
Joint Task Force Collection Management#
A combined joint task force collection management cell receives information requirements from multiple component commands. Operators raise each requirement as a structured JISR request, set its priority and area of interest, and follow it through its lifecycle on one authenticated path, giving the cell a single, consistent view of all collection tasking without standing up a separate tasking system.
Intelligence Fusion Centre Tasking#
An intelligence fusion centre coordinating sensors across partner nations uses the read path to monitor every outstanding and active collection task in one place. Because each request is emitted into the shared operational view, analysts correlate pending tasking with incoming reporting and other mission data on the same dashboard.
Tasking Tempo Monitoring#
Watch officers use the status statistics to track collection tempo across an operation. A rising count of pending or flash-priority requests can signal a surge in demand, and the summarised view surfaces that shift far faster than reading individual tasks would allow.
Multi-Level Secure Tasking#
In an environment mixing clearances, the same task store serves operators at different accreditation levels safely. Clearance-based filtering ensures each operator sees only the requests permitted by their accreditation, so a single shared tasking picture can support staff across multiple security levels.
Compliance and After-Action Review#
Because every submission is captured in the audit trail with its source standard, request metadata, and acting operator, the tasking record provides a complete history for coalition information assurance and after-action review. Analysts can reconstruct exactly which collection tasks were raised, by whom, against which area, and when.
Software Integrator Onboarding#
A software integrator connecting an allied tasking tool to the platform raises JISR requests through a documented interface and reads them back through one consistent path, rather than reverse-engineering a bespoke schema. This shortens onboarding timelines for partner systems feeding collection tasking into a shared picture.
Integration#
The capability is provided through a GraphQL API. One read path returns stored JISR requests for the authenticated organisation with optional request-type filtering and pagination, a second read path returns request counts grouped by status, and a write path raises a single collection request. All access is authenticated with OAuth 2.0 bearer tokens in JSON Web Token (JWT) format and scoped to the authenticated organisation, consistent with the platform's identity and authorisation layer. The same model is reachable wherever the platform's REST and webhook connectors are deployed, so partner systems can plug in through whichever channel suits them.
Requests are raised as a structured input carrying request type, priority, collection type, area of interest as a GeoJSON geometry, requester, provider, status, and secrecy level. The response confirms the new record identifier, the request identifier, and success, so a calling system can immediately reconcile what it sent and begin polling for status changes.
Stored requests are held on the platform's normalised operational model and emitted into the coalition fusion layer as mission-context entities tagged with their NATO JISR source standard. Downstream consumers, including the shared operational view, reporting modules, and alerting rules, work with collection tasking in the same way they work with other coalition and allied data sources. The benefit to a customer is direct: connect a tasking feed once, and that traffic becomes part of the same picture, audit trail, and clearance model as everything else on the platform, with no custom store or workflow engine to build or maintain.
Open Standards#
- NATO AJP-27 (Allied Joint Publication for Joint Intelligence, Surveillance and Reconnaissance). The allied doctrine governing JISR collection tasking. Every request the platform accepts carries the request type, precedence, collection type, and lifecycle status aligned with AJP-27, and each submission is audited and emitted under a NATO JISR source standard tag.
- GeoJSON (RFC 7946). The open format for encoding geographic data structures. Each request carries its area of interest as a GeoJSON geometry, so points, corridors, and polygons can be rendered and reasoned over by mapping tools and command dashboards without translation.
- NATO STANAG (Standardisation Agreements). Referenced through AJP-27; the tasking precedence and collection vocabulary the platform captures derive from the NATO standardisation agreements that AJP-27 draws on, keeping raised requests aligned with allied conventions.
- OAuth 2.0 / JWT (RFC 6749 / RFC 7519). All API access is authenticated using OAuth 2.0 bearer tokens in JSON Web Token format, consistent with the platform's identity and authorisation layer.
Security and Compliance#
Every request carries a secrecy level. Record-level filtering checks the requesting operator's clearance before any request is returned, so operators in a multi-classification environment cannot read tasking above their permitted level, and requests the operator is not cleared for are withheld rather than redacted. All storage, reads, and statistics are organisation-scoped, preventing one coalition partner from seeing another's tasking on a shared platform.
Every submission is written to the audit trail with its source standard, record identifier, secrecy level, request metadata, and the acting operator and organisation, providing a complete and reviewable history for coalition information assurance and after-action purposes. Network separation between classified and unclassified sources remains the responsibility of the operator: classified tasking should reach the platform over networks physically or cryptographically separated from unclassified infrastructure. The platform enforces classification and clearance policy on stored and queried data; it does not substitute for network-layer separation.
Last Reviewed: 2026-05-26 / Last Updated: 2026-05-26