GIZ ONTOLOGY
One business model instead of a different rule in every department.
Define business objects such as items, inventory, orders and lots, with their relations, states and permitted actions, so screens, APIs and agents apply the same rules.

Architecture illustration
Every team calculates available inventory differently
Production and purchasing may mean different things by available inventory. Whether inspection-pending stock counts, or whether reserved quantities are subtracted, changes the answer from the same table. Collecting data in one place does not remove that difference.
Giz Ontology defines business objects such as items, inventory, orders, purchase orders, shipments and lots once, with their relations, states and permitted actions. Screens, APIs and agents all use that definition.
What it defines
| Definition | Example | Effect |
|---|---|---|
| Objects and relations | Item–BOM–supplier, PO–shipment–receipt | Queries and calculations follow the same relations |
| States and transitions | Confirmed, shipped, received, on hold | State changes only in the permitted order |
| Business commands | Receive goods, place on hold, confirm a plan | Screens and agents run with the same permissions and checks |
| Rules | Reject negative stock and duplicate receipts | Invalid records never reach the ledger |
The standard model covers objects across 16 business domains. Not every object has a ready-made screen; the parts a workflow needs are configured during implementation.
What can be demonstrated today
The import supply flow runs on real screens: demand spreadsheet, purchase order, shipment, delay alert, receipt and inventory. The inventory ledger is append-only, and negative stock and duplicate receipts are rejected. Production execution, quality and sales and demand planning have models and tests and are validated on customer data during implementation.
Your existing systems stay in charge
ERP, MES and QMS remain the systems of record. Giz Ontology connects their records and takes over the work that currently happens between them in spreadsheets and email.
Supply-chain planning · Quality hold and 8D closure · Business applications
YOUR NEXT STEP
Bring us the workflow that needs to work.
Start with the files and systems you use today, and the work you want to change.