Skip to content
Novus Examples

Manufacturing · Synthetic business data

Pine Assembly Workshop

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

ZIP with instructions and SHA-256 checksums. Files stay in your browser.

Create from this data

Choose a starting template, then follow its table and field mapping. Studio imports add a table to your project; they do not automatically replace the template’s sample content.

Guided source import

Inspect and edit the source data

Source table: shipments in the linked operating model.

shipment_id
shipment_id
part_id
part_id
parcels
parcels
delivered_parcels
delivered_parcels
status
status
  1. Open the linked operating model in the text and data editor. Find tables.shipments.rows to inspect the records and exact field names.
  2. Keep identifiers as quoted text, retain the other tables and compare edits with the linked schema and expected results. Save a local copy before changing records.

Guided source import

Shipment report

Source table: shipments in the linked operating model.

shipment_id
shipment_id
part_id
part_id
parcels
parcels
delivered_parcels
delivered_parcels
status
status
  1. Download operating-model.json, then open this Document Studio template. Choose Import business data, select the JSON file, choose shipments in Business data table and click Use table.
  2. The import appends a new typed table with all source columns. Use the listed fields for your report, edit its heading and remove unrelated sample blocks. Transfer any values needed by the original template into its fields explicitly; imported records do not replace or bind its sample line items.
  3. Save editable source to preserve the document project. Use the kit workbook in a spreadsheet application when you need its existing formulas, worksheets and chart layout.

Start with blank input tables

The ZIP contains a header-only CSV for every source table. Fill the fields using the kit schema, then open the CSV in the text and data editor or import it into a Studio. Open the completed operating workbook in a spreadsheet application to retain its native worksheets, formulas and chart layout.

Download blank CSV templates

Start with the expected results

Read the kit guide, follow each input’s import order, then compare your output with the reconciliation checks. Planning datasets do not imply that a platform can import them.

Platform compatibility

Example data

Generic business records

Profile 2026-09-08.1 · reviewed 2026-09-08

  1. Map fields to your application schema and retain stable relationships.

Generic records are not native imports for unnamed platforms.

Inputs, templates and references

Input · 22.7 KB · Valid

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.

Schema · 24.7 KB · Reference

Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

Expected Results · 2.3 KB · Reference

Exact table counts, metric formulas, 6 chart points and three negative-test outcomes. Units received=96.00 units; Units issued=72.00 units; Assembly relationships=6.00 records.

Reference · 49.7 KB · Valid

Three readable pages summarize the same model, chart, source tables and usage instructions. Units received=96.00 units; Units issued=72.00 units; Assembly relationships=6.00 records.

Template · 26.5 KB · Valid

Native sheets preserve 89 source records, 3 calculated headline metrics and one editable chart. Units received=96.00 units; Units issued=72.00 units; Assembly relationships=6.00 records.

Deliberately invalid tests