Data Producer
A data producer is a persona that ingests data into OSDU on behalf of the Data Owner. Before getting write access, they must be approved by the Data Office. They are responsible for the data they bring in — its quality, its access controls, and keeping it up to date.
What data producers do
- Prepare, validate, and ingest data into ADME in accordance with defined data standards
- Define schemas or map source data to existing OSDU Well-Known Schemas (WKS)
- Ensure metadata and entitlements are correctly applied during ingestion
- Perform quality checks before and after ingestion to ensure data integrity
- Use owner groups (
data.***.owners) granted by the Data Owner / Data Office for write access - Support troubleshooting and correction of data ingestion issues
Relationship to Data Owner and Data Office
The Data Producer ingests data on behalf of the Data Owner — the organisational unit accountable for a data domain. Before getting write access, the Data Producer must be approved by the Data Office, which operationally manages who can write data. For example, the Data Owner for Master Data is the organisational unit accountable for that domain, while SMDA is the Data Producer that actually ingests master data into ADME.
The Data Office governs who can see data through viewer groups, and grants write access by assigning Data Producers to the appropriate data.***.owners groups. See Data Owner vs Data Producer vs owner groups for the full distinction.
Data producers must adhere to the guidelines established by the Data Governance Forum and obtain approval from the relevant data office before being granted write access to the production environment.
Data producers are also expected to follow Equinor's Continuous Enrichment approach — ingest early, improve over time.
Further reading
- Data Producer Groups (reference) — write access group names
- Record Tags (reference) — required tags on every ingested record
- Data Office — how read access is governed, the Data Governance Forum, and data classification
- Ingesting Data — entitlements, legal tags, LRA, and technical assurance
- Data Architecture — Continuous Enrichment and ELT strategy