The floor that runs the business.
Workstations you shape, buttons that do what your process needs, every action recorded by default. Approved orders land here as jobs — and get made, step by step, down to the minute and the count.
What is Bulk Production Execution?
Bulk Production Execution is the shop-floor layer of Bulk's manufacturing operations software. Approved orders arrive as tracked jobs and get built step by step at workstations you configure — operators start and stop their own timers, every action is recorded by default, and that live time feeds OEE. No retyping, and no guessing what's running on the floor.
Shape it, run it, record it.
Each station is a canvas a shift lead arranges — not a fixed screen built by engineering. The buttons do what your process needs, and everything an operator touches is written down the moment it happens.
Drag-and-drop widgets
Timer, loaded jobs, job card, counters, forms, instructions — arranged per asset type. Workstation, fulfillment and invoicing stations each get sensible defaults you can rearrange.
Dynamic workflows
The routing is snapshotted onto the job at creation, then driven step by step — conditional branches, do-while loops and rework all play out as the operator completes each step.
Every click a record
Start a timer, tap a counter, log a defect, complete a step — each is an immutable transaction. The platform can reconstruct who did what, when, on which asset.
Run a job. Watch it record.
This is the heart of the floor. Start the timer, tap the counters to record good parts, inspections and scrap — every tap writes an immutable transaction, and the OEE readout moves as you work. It's a real interaction, not a screenshot.
Select a station. Complete the work.
An operator's whole shift is five moves — and the platform gates each one. Pre-use checks can block a station until they pass; queue stations even serve the next ready step with an ETA from historical timing.
Select asset
The floor's front door — pick your workstation, with live running and available counts.
Running · availablePass pre-use
Safety, quality and maintenance checks can block the station until passed — or overridden.
The gateLoad jobs
Multi-select up to capacity, or let a queue station serve the next ready step with an ETA.
Manual · queueOperate
Play the timer, tap counters, log materials and quality — each an immutable transaction.
Timer · countersComplete
Stop distributes time across the worked items; the routing decides what comes next.
Routing advancesBuilt for how the floor actually moves.
Routings branch. Steps loop. Parts come back for rework. Timers stop and start a dozen times a shift. Production is built so none of that becomes a spreadsheet someone has to reconcile later.
Routing snapshot
The routing is frozen onto the job at creation — robust against later template edits — and can be customised for a single job without touching the shared version.
compiled · versionedBranches & loops
Completing a step evaluates conditions and do-while loops, creating the next job items and persisting every routing decision for the record.
conditional · do-whileRework, tracked
Failed steps spawn rework items with their own iteration counter — so a part that comes back round is its own auditable pass, not an edit over the first.
iteration counterImmutable time
One running session per asset. Pause opens an OEE downtime event; stop distributes elapsed time across items as time entries. Corrections are new rows, never edits.
timer · OEE · adjustmentsEvent-sourced counts
Every counter tap stores an exact integer delta in a recording batch. Adjustments and voids append offsetting transactions — the total is always the sum of the truth.
output · quality · consumablesPre-use gating
Safety, quality and maintenance checklists can block a station until they pass — or a supervisor logs a revocable override. The operate screen enforces it with a redirect.
blocks · overrideJobs & transactions, under control.
Planners and supervisors work the desktop side: every job in one register, every routed step surfaced as a "transaction" they can monitor and correct in flight — singly or in compatible bulk, always with a reason on the record.
- Jobs register Search, filter and sort every job; saved table views per role; bulk edit with a per-job results report.
- Transactions Every routed step across all jobs, with hover breakdowns of output and time by source — timer, manual, adjustment, downtime.
- Correct & audit Complete or undo steps, adjust recorded values, and read the immutable status history — every change carries a required reason.
See the floor as it runs.
for each job
not guesses
Paused · Idle
numbered
The traceability backbone.
Everything the floor records feeds the rest of the platform — quality, OEE, costing and invoicing all read from the same immutable transactions, so nothing gets retyped.
Production writes it once.
Every module below reads from the same immutable transactions the floor records — nothing is retyped, nothing drifts.
Inbound & OCR
Approved documents become production orders and jobs.
Quality
A scrap tap auto-creates a lifecycle quality issue.
OEE & Reporting
Timer pauses and status feed OEE; stats power the KPIs.
Inventory
Consumable usage deducts straight from the stock ledger.
Invoicing
Finished work flows into priced, numbered invoices.
Search
Every job and transaction is searchable in seconds.
Questions, answered.
What is Bulk Production Execution?
It runs work on the floor: approved production orders become tracked jobs, made step by step at configurable workstations, with every start, stop, and count recorded automatically.
Do I have to replace my ERP to use it?
No. Bulk runs on the floor alongside your ERP — approved orders flow in as jobs and the live production record flows back out, so your system of record stays where it is.
How is time on a job tracked?
Operators start and stop their own work at the workstation, so each job's time reflects what actually happened — and those timers feed live OEE instead of an after-the-fact estimate.
Can workstations be tailored to different benches?
Yes. Each station is built from widgets, so production, fulfilment, and inspection each get the right buttons for their work — no code and no custom development.
Is every action traceable?
Every action is an immutable record by default, giving you an audit-ready history of who did what, when, and on which job — without anyone remembering to log it.
How do approved orders become jobs?
Approved paperwork turns into a tracked job on its own, so work starts without anyone retyping order details.
Bring us your messiest routing.
We'll build the workstations around how your floor actually works, then run a real job through them with you — timers, counters, the lot.