json2.3 KB

Pine Assembly Workshop: Manufacturing and quality reconciliation identities

Manufacturing and quality reconciliation identities for Pine Assembly Workshop. 6 named identities covering the explosion, the cost roll-up, the work order that closes to standard, the routing, the inspection rule including the unilateral tolerance, and the difference between component scrap and finished-goods yield. The deliberate defect and its 4 unit, 0.40 USD shortfall are listed separately.

Data import JSON parsing

Preview, first 50 linesjson

{
  "schemaVersion": 1,
  "generatedAt": "2026-09-08",
  "sourceKit": "inventory-manufacturing",
  "currency": "USD",
  "identities": [
    {
      "id": "explosion",
      "statement": "Extended quantity is quantity per parent times parent quantity, and the leaf totals equal the model material requirements.",
      "productionOrder": "BUILD-1",
      "orderQuantity": 2,
      "leafTotals": {
        "LEG": 8,
        "SCREW": 24,
        "PANEL": 2
      },
      "modelRequirements": {
        "LEG": 8,
        "PANEL": 2,
        "SCREW": 24
      }
    },
    {
      "id": "cost-roll-up",
      "statement": "Leaf material plus added value is the standard cost of a finished unit.",
      "leafMaterial": "25.20",
      "addedValue": "14.80",
      "standardCost": "40.00"
    },
    {
      "id": "work-order-cost",
      "statement": "Material plus labour plus absorbed overhead equals the standard cost of the output, so the variance is zero.",
      "material": "50.40",
      "labour": "18.50",
      "overhead": "11.10",
      "orderCost": "80.00",
      "standardCost": "80.00",
      "variance": "0.00"
    },
    {
      "id": "routing",
      "statement": "Setup is charged once per order and run time per unit, so total minutes are setup plus run times quantity.",
      "setupMinutes": 10,
      "runMinutesPerUnit": 10,
      "orderQuantity": 2,
      "totalMinutes": 30
    },
    {
      "id": "inspection",
      "statement": "A reading passes only when it lies between both limits inclusive, and one characteristic has a unilateral tolerance whose lower limit is its nominal.",

… 77 lines total: download for the full file.

Specifications

Document Set: manufacturing
Industry: manufacturing
Source Kit: inventory-manufacturing
Entity: Pine Assembly Workshop
Synthetic: true
As Of: 2026-09-08
Identities: 6
Defects Listed: 1

Testing contract

Reference control

Scenario: Use this file as the expected-value table when testing a reader against the rest of the set.
Expected result: Every figure here is reproduced by at least two other files in the directory, and the deliberateDefects array names the single invalid file, the row it mutated and the exact size of the shortfall.

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: Manufacturing and quality reconciliation identities” is a deterministic Testaroo fixture for Data import, JSON parsing. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: JSON · 2,387 bytes. 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("quality-reconciliation.json") as f:
    data = json.load(f)
print(type(data), len(data))

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