FluenBox now supports ODPS v1.1 and ODCS v3.2, fully integrated into the data maturity score

FluenBox now supports the latest versions of the two open standards for data products and data contracts: the Open Data Product Standard (ODPS) v1.1.0 and the Open Data Contract Standard (ODCS) v3.2.0. Both are fully integrated into the FluenBox data maturity score, so what a data product declares in these standards is checked and counted every time its data maturity is measured.

Two open standards, one data product

Both standards are maintained by Bitol, a Linux Foundation project under LF AI & Data, and are published under the Apache 2.0 licence. They were released together in September 2026 and are designed to work as a pair:

• ODPS describes the data product: what it is, its type, the team that owns it, how to get support, and the input and output ports it offers.
• ODCS describes the data contract: the schema, the quality rules, the service levels and the servers behind each output port.

An output port in ODPS points to its ODCS contract. Together they give every data product a complete, portable description that any team and any tool can read.

apiVersion: v1.1.0kind: DataProductname: Customer 360type: consumerAlignedteam: customer-domainoutputPorts:  - name: customers    contractId: c360-v2

apiVersion: v3.2.0kind: DataContractid: c360-v2schema: customersquality: 6 rulesslaProperties: dailycontext: for AI agents

What is new in these versions

The latest releases bring the two standards closer together and prepare them for AI:

• A type for every data product (ODPS): source-aligned, aggregate or consumer-aligned.
• Context for AI agents (ODCS): instructions, verified statements and constraints that tell an AI agent how to use the data correctly.
• Clearer meaning: synonyms, fixed lists of allowed values and semantic types that mark a field as a measure or a dimension.
• Retire without breaking: a deprecated flag for data products, ports and fields, so consumers are warned before anything is removed.
• Simpler, more consistent definitions: shared fields across both standards, stable identifiers and new server types such as Apache Iceberg, SAP HANA and Teradata.

How they feed the data maturity score

In FluenBox, data products and data contracts described in ODPS and ODCS are part of the measurement, not a document stored on the side. What they declare becomes evidence, and the data maturity score checks whether it is complete and whether it is honoured:

1. Ownership: the data product has a team and a support channel.
2. Contracts: every output port is linked to a data contract.
3. Quality and service levels: the contract defines its rules and service levels, and the results show they are met.
4. Change management: deprecated ports and fields are flagged before they are removed.
5. Ready for AI: the context for AI agents is defined where AI will use the data.

Each improvement is measured again, so teams can see their data maturity rise as their descriptions and contracts become complete, and executives see the result by data product, domain, country and organisation.

Why it matters for your organisation

• No lock-in: your data products and contracts are described in open standards that you own and can take anywhere.
• One language for every team: business, data and technical teams describe data products the same way in every domain and country.
• Ready for AI: AI agents get the context they need to use your data correctly.
• Measurable from day one: adopting the standards immediately shows up in your data maturity score.