Track-to-Task Workflow

Track-to-Task Workflow

Verification boundary: This page combines platform design guidance with static evidence from the release. It does not prove that every detected interface is enabled, reachable, secure, or operational in the deployed environment.

Objective

Demonstrate the operational chain from track ingestion through visualization, semantic association, collaboration and an acknowledged/completed task.

Prerequisites

• OpenTrack, OpenCOP, OpenTask and required OpenBus/knowledge services are healthy.
• A controlled track generator or recorded input is available.
• Two test users/roles are available for assignment and acknowledgement.

Procedure

1. Create or ingest a uniquely identified test track with known position, time, type and source.
2. Verify OpenTrack receives/updates it and OpenCOP displays it in the correct location/type.
3. Open the track details and confirm source time, provenance and semantic type.
4. Create an OBSERVE, INVESTIGATE, TRACK or other allowed task from the track.
5. Assign it to the second user/asset; acknowledge, execute and complete it.
6. Verify task state is visible in OpenTask/OpenCOP and correlated to the original track.
7. Capture messages/events/logs proving the state transitions.

Pass criteria

Track position/type/time are correct; task creation and authorization succeed; all state transitions are visible and correlated; duplicate updates do not create duplicate tasks; evidence is retained.

Cleanup

Delete or mark the test track/task complete according to the test-data policy and verify no generator continues publishing.

Maintainer Notes

Add human-reviewed deployment notes, corrections, decisions, screenshots, and links here. Content outside the generated block is preserved on future runs.