Skip to content
Novus Examples
md2 KB

Pine Assembly Workshop — Workflow and import guide

Workflow and import guide for Pine Assembly Workshop. Documents 11 source tables, exact expected totals and supported versus manual workflows.

Preview, first 44 linesmd
# Pine Assembly Workshop

A two-level assembly with shared screw consumption, purchase/issue movements and reconciled stock balances.

All entities and transactions are fictional. Snapshot: 2026-09-08.

## Start with the linked model

1. Open operations.xlsx and review the Summary sheet. Source tables contain stable primary keys and declared references.
2. Change source values in the workbook to explore the calculated totals and editable chart.
3. Compare output values with expected-results.json. The JSON Schema checks types; primary-key uniqueness and joins also require the listed semantic checks.
4. Use invalid-records.json only in a local validation harness. Its three cases exercise duplicate keys, wrong types and an orphan reference.

## Included tables

| Table | Records | Primary key |
| --- | ---: | --- |
| parts | 6 | part_id |
| bom | 6 | bom_id |
| movements | 24 | movement_id |
| suppliers | 2 | supplier_id |
| procurement | 8 | purchase_order_id |
| production_orders | 4 | production_id |
| material_requirements | 12 | requirement_id |
| routes | 4 | route_id |
| shipments | 16 | shipment_id |
| vehicles | 4 | vehicle_id |
| shipment_exceptions | 3 | exception_id |

## Expected totals

- Units received: 96.00 units. Sum movements.received over the included records.
- Units issued: 72.00 units. Sum movements.issued over the included records.
- Assembly relationships: 6.00 records. Count unique bom_id values in bom.

## Platform mapping

primary-records.csv is a generic example table. It is not a native platform export. Where this kit includes a named profile, use that profile’s separate CSV and schema and review its compatibility level before uploading.

## Scope and assumptions

- Producing one DESK requires four LEG, one PANEL and twelve SCREW leaf units. Intermediate assembly counts must not be double-counted as raw parts.
- Production orders and shipment plans are future commitments. They do not silently deduct the historical stock ledger. Confirm available stock and planned material requirements before fulfillment.

Specifications

Kit
inventory-manufacturing
Industry
manufacturing
Schema Version
1
Synthetic
true
As Of
2026-09-08

Testing contract

Reference control
Scenario
Use workflow and import guide in the Pine Assembly Workshop bill-of-materials, stock-movements, reorder-planning, procurement, production-planning, shipments, delivery-exceptions workflow.
Expected result
Documents 11 source tables, exact expected totals and supported versus manual workflows.

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 — Workflow and import guide” 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: MD · 2,069 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("guide.md").read())
print(html[:200])

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