Skip to the app
Search
The operating system for desk work that lives in files
Try a sample
Supply Chain & Retail EDI · Systems talking · Hours back · sample run · 29 ms

Baan Production Extractor

5 production orders parsed into 25 routing operations and 22 material lines, loading 342.95 planned hours on 9 work centers; 6 exceptions on 3 orders to fix before loading (25.25 hours have no work center).

Evidence · Order 26000419, header
30 DRL01 Drill and tap terminal box WC-CNC1 MAZ-QT-01 0.75 0.0000 0.25 2.00
Working

The run time per unit is 0 h, so 0.75 h setup + 0 h run per unit x 250 pcs = 0.75 planned hours: only the setup is loaded on WC-CNC1, none of the per-unit time.

Method

1Page headers are recognised from page 1 (every line above the first order header) and skipped on later pages; order header fields are read from 'Label : value' pairs.

2Routing and Estimated Materials columns come from the dashed ruler under each section's titles and are matched by title (Work Center or Work Centre, Run Time/Unit or Cycle Time, Qty per, Total Qty...).

6
Exceptions · 4 error(s)
SeverityProduction orderReference
Warning26000419Op 30
Error26000419Pos 30
Error26000420
1 to 3 of 6
Reads

Baan production order report text

Produces

Routing and BOM tables (CSV and JSON) (Routing (CSV), Bill of materials (CSV), Orders, routing and BOM (JSON))

Price

$3,000 / month, 30% to the referring partner

Your files

Read in memory for the session, never stored, never used to train a model.

Outputs are computed from your inputs and the tool's rules. Check them before you rely on them.