Operational Data Flows
Operational Data Flows
| Field | Value |
|---|---|
| Distribution | WCT English — OpenC5ISR |
| Product | OpenC5ISR |
| Release | 0.15.1 |
| Deployment | openc5isr-en.wallacecorptech.com |
| Source | /srv/wct/releases/OpenC5ISR-v0.15.0 |
| Evidence | Reference architecture |
| Source fingerprint | 63d2b1097707e25d666401cdc6362e395968600a40a08690210cd8c0b75fbf50 |
| Status | Generated baseline — human review required |
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.
Reference flow
| Producer | Information product | Primary consumer/store |
|---|---|---|
| Sensor/device | Raw signal, frame, telemetry or observation | Edge adapter / domain module |
| Domain module | Typed observation, track, product or alert | OpenBus / OpenData / OpenFiles |
| OpenKnowledge | Type, relationship and policy context | Analytics, automation and operator applications |
| Operator/analytic | Decision, annotation, correlation or recommendation | OpenTask / OpenCOP / OpenIIA |
| OpenTask | Assigned action and state transition | Human, robot, service or external system |
| All stages | Provenance, timestamps, audit and retained artifacts | OpenFiles / OpenData / OpenAAR-MR |
Control points
- Validate schema and semantic type at ingestion.
- Preserve source time separately from processing and receipt time.
- Carry handling and release policy with the object, not only in the user interface.
- Reference large imagery/video/files rather than embedding them in high-rate event messages.
- Make task and effect transitions explicit, acknowledged and auditable.
Maintainer Notes
Add human-reviewed deployment notes, corrections, decisions, screenshots, and links here. Content outside the generated block is preserved on future runs.