Skip to content
Novus Examples
json22.7 KB

Pine Assembly Workshop — Linked operating model

Linked operating model for Pine Assembly Workshop. 89 records across 11 linked tables; no duplicate primary keys or missing references. Units received=96.00 units; Units issued=72.00 units; Assembly relationships=6.00 records.

Data import
Preview, first 50 linesjson
{
  "id": "business-inventory-manufacturing",
  "slug": "inventory-manufacturing",
  "title": "Pine Assembly Workshop",
  "industry": "manufacturing",
  "description": "A two-level assembly with shared screw consumption, purchase/issue movements and reconciled stock balances.",
  "workflows": [
    "bill-of-materials",
    "stock-movements",
    "reorder-planning",
    "procurement",
    "production-planning",
    "shipments",
    "delivery-exceptions"
  ],
  "asOf": "2026-09-08",
  "source": "deterministic-synthetic",
  "tables": {
    "parts": {
      "primaryKey": "part_id",
      "foreignKeys": [],
      "rows": [
        {
          "part_id": "DESK",
          "description": "Desktop kit",
          "unit_cost": 40,
          "opening": 20,
          "reorder_point": 8
        },
        {
          "part_id": "BASE",
          "description": "Base assembly",
          "unit_cost": 15,
          "opening": 30,
          "reorder_point": 10
        },
        {
          "part_id": "TOP",
          "description": "Top assembly",
          "unit_cost": 20,
          "opening": 25,
          "reorder_point": 10
        },
        {
          "part_id": "LEG",
          "description": "Leg",
          "unit_cost": 3,
          "opening": 100,
          "reorder_point": 24
        },
… 947 lines total: download for the full file.

Specifications

Kit
inventory-manufacturing
Industry
manufacturing
Schema Version
1
Synthetic
true
As Of
2026-09-08
Records
89
Tables
11

Testing contract

Expected to pass
Scenario
Use linked operating model in the Pine Assembly Workshop bill-of-materials, stock-movements, reorder-planning, procurement, production-planning, shipments, delivery-exceptions workflow.
Expected result
89 records across 11 linked tables; no duplicate primary keys or missing references. Units received=96.00 units; Units issued=72.00 units; Assembly relationships=6.00 records.

What is a .json file?

JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.

How to use this file

Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.

How to use this file for testing

“Pine Assembly Workshop — Linked operating model” is a deterministic Novus Examples fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: 89 records. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

Code examples

import json

with open("operating-model.json") as f:
    data = json.load(f)
print(type(data), len(data))

Related files

Generated by generation/business_fixtures.py. Free for any use, no attribution required, license.