OC4IDS
OC4IDS - the Open Contracting for Infrastructure Data Standard - structures the delivery half of Civil Memory: the infrastructure project record for work you’ve won and are delivering, or have delivered. Where OCDS covers the public, pre-award side of a job, OC4IDS picks up at the award seam and covers everything after.
What it covers in Demiton
Once you declare a win, your pursuit becomes a delivery project inside Projects and Memory - live operational data from your own ERP, field ops, and payroll systems. OC4IDS is the shape that data takes when it’s reported back out: project scope, cost, schedule, and outcome, structured the way government clients and the broader infrastructure sector can consume.
An emission, not an ambient state
OC4IDS output is never generated by default. It’s produced only through a contractor-initiated, consented, audited emission - you choose to report a specific project’s delivery data to a specific government client, and that action is what triggers the projection into OC4IDS shape. Your day-to-day operational memory - site diaries, allocations, payroll reconciliations - is never exposed as a side effect of simply existing in the platform.
This is the One-Way Valve: tenant operational memory never flows to the public platform hub except through this deliberate, consented path. A single enforcement point - the disclosure gate - is what every crossing goes through. See Conformance for how that’s enforced in practice.
Next steps
- OCDS - the pre-award standard that hands off to OC4IDS at the award seam
- Conformance - the One-Way Valve and the disclosure gate in detail
- Projects - where delivery data lives before it’s ever emitted