USE CASE

Shop-floor tracking

See what each workstation is doing now, from job cards the operators update.

The problem

The office learns what happened on the floor the next morning, from a register someone filled in from memory. Late operations and scrap surface only when an order is already late.

The flow in Sundial

1. Work orders create job cards. Each operation in the routing becomes a job card for its workstation, with the quantity to produce.

2. Operators start and stop the clock. On a desktop or phone at the station, the operator starts the job card, logs time, and records completed quantity. Several operators can log against one card.

3. Record material as it is used. Raw materials are transferred to work in progress against the work order, so consumption is recorded when it happens.

4. Capture scrap and rework. Rejected quantity is entered on the job card, keeping actual output honest.

5. Close the operation. Completing the last job card lets the work order finish and finished goods move into stock.

What the team sees

Supervisors see open job cards per workstation and how long each has run. Planners see work orders progress operation by operation. Costing reflects actual time and material, not the standard.

Why it holds up

Job cards are filled in at the station, not reconstructed later, so the record matches what happened. Time and quantity logged per operation feed the work order’s actual cost, which makes the difference between planned and actual production cost something you can see per order. The same screens work on a shared terminal or an operator’s phone.

With AI (coming to Sundial)

Coming to Sundial: ask “which work orders are behind schedule today?” in plain language, and get the answer from live job cards.

THE NEXT AGE OF ERP

Run the whole business
in one calm system.

Try the demoTalk to us