Open Footprint — DDMS within OSDU

OFP as an OSDU Domain Data Management Service (DDMS) in the Generic.Environment domain. Mapping 13 OFP entities to OSDU kinds with full platform integration.

Generic.Environment Domain

The OSDU Data Platform defines a Generic.Environment subdomain with no entity types defined yet. OFP fills this gap as an Environment DDMS, bringing 120+ entities across 11 domains covering GHG emissions, sustainability reporting, product carbon footprints, and data verification. OSDU provides the governance layer (Storage, Schema, Register, Legal, Entitlements); OFP provides the domain expertise.

Integration Roadmap

Phase 1: Data Definitions
active
Phase 2: API Contract
planned
Phase 3: Schema & Shadow Records
future

Phase 1: Data Definitions

Active

Map OFP entities to OSDU kinds within the Generic.Environment domain. Each entity follows the kind format: ofp:wks:groupType--EntityName:version where ofp is the authority (OFP-owned, registered into OSDU via the Register service).

13 entities across 4 priority tiers, organized by OSDU GroupType.

Priority 1 — Reference Data

reference-data

Read-only lookup and classification types. Foundation for all other entity definitions. No inheritance from OSDU abstract fragments.

EmissionScopeTypeCommon Entities
ofp:wks:reference-data--EmissionScopeType:1.0.0

Scope 1, Scope 2 (location/market-based), Scope 3 upstream/downstream classification.

Source: reference_data.emission_scope_type
EmissionComponentCommon Entities
ofp:wks:reference-data--EmissionComponent:1.0.0

GHG gas components: CO2, CH4, N2O, HFCs, PFCs, SF6, NF3, and CO2e aggregates.

Source: reference_data.emission_component
EmissionRecordingMethodTypeCommon Entities
ofp:wks:reference-data--EmissionRecordingMethodType:1.0.0

How emission data was obtained: measured, calculated, estimated, or modeled.

Source: reference_data.emission_recording_method_type
UnitOfMeasureCommon Entities
ofp:wks:reference-data--UnitOfMeasure:1.0.0

Units for emission quantities and activity data: kg, tonne, kWh, MJ, m3, etc.

Source: reference_data.unit_of_measure

Priority 2 — Master Data

master-data

Core business entities with independent lifecycles. Inherit from OSDU abstract fragments (AbstractMaster, AbstractFacility) for cross-domain interoperability.

EmissionActivityRecording
ofp:wks:master-data--EmissionActivity:1.0.0

Specific emission-producing activities linked to scope, category, and facility.

Source: master_data.emission_activityInherits: AbstractMaster
EmissionInventoryRecording
ofp:wks:master-data--EmissionInventory:1.0.0

Collections of emission sources grouped by organization, facility, or reporting boundary.

Source: master_data.emission_inventoryInherits: AbstractMaster
EmissionFactorRecording
ofp:wks:master-data--EmissionFactor:1.0.0

Emission factors by activity type with provenance (IPCC, EPA, DEFRA, custom).

Source: master_data.emission_factorInherits: AbstractMaster
EnvironmentalFacilityFacility Structure
ofp:wks:master-data--EnvironmentalFacility:1.0.0

Extends OSDU AbstractFacility with emission inventories, GHG reporting boundaries, and regulatory frameworks. Joinable with all other OSDU facility records.

Source: master_data.facilityInherits: AbstractFacility

Priority 3 — Work Products (Core)

work-product-component

Primary recording and calculation entities. These are the bulk data objects that the DDMS manages and that OSDU Storage holds shadow records for.

EmissionStatementRecording
ofp:wks:work-product-component--EmissionStatement:1.0.0

Primary emission record: CO2e quantity, activity link, calculation model, recording method, and temporal validity.

Source: transactional_data.emission_statement
EmissionCalculationModelRecording
ofp:wks:work-product-component--EmissionCalculationModel:1.0.0

Calculation models and formulas used to derive emission quantities from activity data and factors.

Source: master_data.emission_calculation_model

Priority 4 — Work Products (Reporting)

work-product-component

Reporting, footprint, and verification entities. Depend on Priority 1-3 entities being in place first.

ProductFootprintProduct Life Cycle
ofp:wks:work-product-component--ProductFootprint:1.0.0

Product carbon footprint (PCF) aligned with PACT/Pathfinder, covering cradle-to-gate lifecycle stages.

Source: transactional_data.product_carbon_footprint
DisclosureReportReporting
ofp:wks:work-product-component--DisclosureReport:1.0.0

Disclosure reports for CSRD/ESRS, SEC Climate, CDP, and GHG Protocol frameworks.

Source: transactional_data.emission_report
VerificationSessionData Verification
ofp:wks:work-product-component--VerificationSession:1.0.0

Data verification sessions: quality rules, assessment methods, confidence scoring, and audit trails.

Source: transactional_data.data_quality

Phase 2: DDMS API Contract

Planned

Define the DDMS API contract: register with the OSDU Register service, expose bulk data endpoints with x-ddms-retrieve-entity tagging, and accept OSDU metadata on ingestion.

DDMS Registration

POST/api/register/v1/ddms

Register OFP Environment DDMS with the OSDU Register service. Includes OpenAPI spec with x-ddms-retrieve-entity tagging.

Environment DDMS Endpoints

GET
/ddms/environment/v1/emissions/{id}

Retrieve a single emission statement by ID (bulk data retrieval).

x-ddms-retrieve-entity
POST
/ddms/environment/v1/emissions

Bulk ingestion of emission statements with OSDU metadata (acl, legal).

GET
/ddms/environment/v1/facilities/{id}

Retrieve environmental facility data including emission inventories.

x-ddms-retrieve-entity
POST
/ddms/environment/v1/calculations

Execute GHG calculations using emission factors and activity data.

GET
/ddms/environment/v1/footprints/{id}

Retrieve product carbon footprint (PCF) data.

x-ddms-retrieve-entity
POST
/ddms/environment/v1/reports/generate

Generate disclosure reports for CSRD, SEC, CDP, or GHG Protocol frameworks.

GET
/ddms/environment/v1/verification/{sessionId}

Retrieve verification session status and quality assessment results.

x-ddms-retrieve-entity

Required OSDU Metadata

The DDMS must accept and forward these fields on all ingestion requests.

acl

Access control lists (owners, viewers) governing who can read/write the record.

legal

Legal tags, data countries, and compliance status required by OSDU governance.

data-partition-id

OSDU partition identifier for multi-tenant isolation.

Authorization

Bearer JWT token forwarded to OSDU Storage for entitlement delegation.

Phase 3: Schema & Shadow Records

Future

Register entity schemas with the OSDU Schema service and maintain 1:1 shadow records in OSDU Storage for cross-platform discoverability and governance.

Integration Flow

Schema DefinitionSchema ServiceOSDU StorageSearch Discovery

Each OFP entity type is registered as a schema once. Every data instance gets a shadow record in Storage, making it discoverable via OSDU Search across the entire platform.

Shadow Record Properties

Every bulk data instance in the OFP DDMS has a 1:1 shadow record in OSDU Storage containing these required properties. Authorization is delegated to the Storage service: if Storage returns the shadow record, the client is authorized.

ddmsId

Registered DDMS identifier linking the shadow record to the OFP Environment DDMS.

entityType

The domain object type (e.g., EmissionStatement, EnvironmentalFacility).

localId

The primary key within the OFP DDMS used to fetch the bulk data (e.g., emission_statement_pk).

View the standalone OFP data model

11 domains, 120+ entities, carbon measures, and database targets.

Standalone Data Model