Skip to content
Testaroo
md6.5 KB

Pine Assembly Workshop: manufacturing document set README

Document set README for Pine Assembly Workshop. 31 files, 1 of them intentionally invalid, with the reconciliation identities, the declared parameters and the measured size of each deliberate defect named in full.

Preview, first 50 linesmd
# Pine Assembly Workshop: bill of materials, work order, conformance certificate and inspection documents

The shop and quality paperwork around one production order: a multi-level bill of materials in four formats, the order exploded against it, a routing and cost build-up that closes exactly to standard, an inspection report with real measured deviations against bilateral and unilateral tolerances, the nonconformances that follow, and the certificate of conformance that discloses them rather than hiding them.

All parties, amounts and identifiers are fictional. Fixed snapshot: 2026-09-08. Records are derived from the shared operating model `inventory-manufacturing`, so identifiers join across this set, across the other commercial document sets, and across every fixture built on the same model.

## Reconciliation identities this set asserts

- Extended quantity is quantity per parent times parent quantity on every explosion row, and the leaf totals of 8 LEG, 2 PANEL and 24 SCREW equal the material requirements the model holds for BUILD-1.
- Leaf material of 25.20 USD plus added value of 14.80 is the 40.00 USD standard cost of a finished unit.
- The work order costs 50.40 of material, 18.50 of labour and 11.10 of overhead, which is 80.00 USD and exactly the standard cost of the output, so the variance is zero.
- Total routing time is 10 setup minutes plus 10 run minutes per unit times 2 units, which is 30 minutes.
- A reading passes only when it lies between both limits inclusive; 23 of 25 do, and the 2 that do not each raise one nonconformance.
- Every gauge is in calibration on the inspection date and every characteristic is measured by exactly one gauge.
- Every evidence reference in the certificate of conformance and the lot genealogy names a file that exists in this directory.

## Parameters this set introduces

These are properties of the document class, not of the operating model. They are declared once and every file in the set agrees with them.

- The routing: 5 operations with setup and run times, a labour rate of 37.00 USD an hour and overhead absorbed at 60 percent of labour. The model carries parts, a bill of materials and production orders and nothing about how the work is done.
- The drawing DRW-LEG-002 revision C, its 5 characteristics and their tolerances, four bilateral and one unilateral.
- The measured readings, the gauges and their calibration dates, the sampling table and the lot number LOT-2026-0912.
- The material certificate properties, which are invented values in a plausible shape, and the fictional test methods they name.

## Files

| File | Format | Validity | What it is |
| --- | --- | --- | --- |
| `bill-of-materials-indented.csv` | csv | valid | Indented bill of materials |
| `bill-of-materials-explosion.csv` | csv | valid | Bill of materials exploded for a production order |
| `bill-of-materials-explosion-rollup-mismatch.csv` | csv | invalid | Exploded bill of materials whose sub-assembly quantities do not roll up |
| `bill-of-materials.json` | json | valid | Bill of materials JSON |
| `bill-of-materials.xml` | xml | valid | Bill of materials XML |
| `standard-cost-rollup.csv` | csv | valid | Standard cost roll-up |
| `bill-of-materials.xlsx` | xlsx | valid | Bill of materials workbook |
| `work-order-operations.csv` | csv | valid | Work order routing |
| `work-order-cost.csv` | csv | valid | Work order cost build-up |
| `work-order-register.csv` | csv | valid | Work order register |
| `material-issue-list.csv` | csv | valid | Material issue list |
| `work-order-BUILD-1.pdf` | pdf | valid | Work order (PDF) |
| `work-order-BUILD-1.docx` | docx | valid | Work order (DOCX) |
| `inspection-characteristics.csv` | csv | valid | Inspection characteristics and tolerances |
| `inspection-measurements.csv` | csv | valid | Inspection measurements with tolerances |
| `inspection-measurements.xlsx` | xlsx | valid | Inspection measurement workbook |
| `inspection-summary.csv` | csv | valid | Inspection summary |
| `inspection-report-INS-2026-0001.pdf` | pdf | valid | Inspection report with measured tolerances |
| `nonconformance-register.csv` | csv | valid | Nonconformance register |
| `nonconformance-report-NCR-2026-0001.pdf` | pdf | valid | Nonconformance report |
| `gauge-calibration-register.csv` | csv | valid | Gauge calibration register |
… 75 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
Documented Files
31
Documented Defects
1

Testing contract

Reference control
Scenario
Read the README before using the set, then check that every filename it lists exists in the same directory and that the defect list matches the files marked invalid.
Expected result
The file table lists 31 entries including this README, and the deliberate-defect section names 1 file(s) with the measured size of each discrepancy.

What is a .md file?

Markdown (MD) is a lightweight plain-text markup language that uses simple punctuation conventions to denote headings, lists, links, emphasis, and code. It is designed to be readable as-is and to convert cleanly to HTML. It is widely used for documentation, READMEs, and content authoring.

How to use this file

Use an example Markdown file to test parsers and renderers, verify GitHub-Flavored Markdown extensions like tables and fenced code, and exercise HTML-conversion pipelines.

How to use this file for testing

“Pine Assembly Workshop: manufacturing document set README” is a deterministic Testaroo fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: MD · 6,639 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.

Document fixtures list their internal structure (pages, fields, tracked changes, embedded objects) in the spec table. Test extractors, converters, and OCR against that known structure, and compare searchable↔scanned or format-twin companions when present.

Code examples

import markdown  # pip install markdown

html = markdown.markdown(open("README.md").read())
print(html[:200])

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