Use this playbook for strategic coordination through an ASTM F3548-21 ecosystem. Pin the interface version, DSS environment, credentials, and local participation rules before the exercise.
Establish participant identity and time
Verify the service identity, certificate chain, clock synchronization, and tenant-to-participant mapping. Confirm which environment is being used; test and production data must never cross. Record the DSS endpoints and trust material by fingerprint, not by an unversioned screenshot.
Exercise token expiry and clock-skew behavior before sharing a real intent. A retry that silently changes the operation identifier is a defect, not recovery.
Build reviewable 4D volumes
Represent the operation as time-bounded horizontal and vertical volumes that cover the nominal flight and the required contingency space. Validate geometry, altitude references, and start/end boundaries before publication.
Keep the business operation identifier separate from every interoperability entity identifier. The audit record should make the mapping clear without exposing another participant’s protected details to unauthorized users.
Share intent and subscribe
Create or update the operational intent with optimistic concurrency. Establish subscriptions for the area and period needed to maintain the constraint picture. Record request and response correlation identifiers and preserve the last confirmed DSS version.
Treat notifications as prompts to fetch authoritative state, not as the state itself. Processing must be idempotent because delivery may be repeated or arrive after a retry.
Interpret strategic conflicts
A geometric and temporal overlap is a constraint requiring resolution; it is not automatically evidence that another operator acted improperly. Show the overlapping volumes, time interval, data freshness, and source without leaking fields the participant is not entitled to see.
Resolve the conflict by changing the plan, negotiating through the accepted process, or recording why a local rule allows the proposed relationship. Then rerun deconfliction against a fresh constraint snapshot.
Manage activated and off-nominal states
Define who may activate an intent and what preconditions are checked. When telemetry or operational judgement moves an operation to Nonconforming or Contingent, publish the required state change promptly and preserve the trigger, actor, and timestamps.
Rehearse loss of DSS connectivity, rejected updates, partial local failure, stale subscriptions, and recovery after the aircraft has landed. Do not fabricate a successful federation state while disconnected; show the last confirmed time and degraded operating rule.
Reconcile and close
At completion, transition or close the interoperability records according to the selected interface behavior. Reconcile the local event stream with DSS acknowledgements and investigate missing or out-of-order transitions.
Retain enough evidence to reproduce what the participant knew at each decision point without storing data beyond the agreed retention purpose.
Run the qualifier evidence
Execute the pinned InterUSS qualifier suite against the same release and configuration intended for deployment. Archive the suite version, environment, start/end time, raw results, and signed summary. Findings are triaged and linked to fixes; a rerun supersedes rather than erases the earlier result.
Qualification results support a claim about tested behavior at a point in time. They do not certify the deployment, the operator, or a flight.