TempoOrder fulfillment agent Ten hours to minutes
Planning the day's orders used to take ten hours of stitching exports, and now it takes minutes.
The ask
Sense Asia runs supply chain operations. Synchronizing order fulfillment meant reading exports from the ERP and legacy systems by hand, about ten hours of planning a day, with each planner keeping a private file and a private version.
The plan lived in separate files, and in each planner's head.
The inputs
The ERP and legacy exports, the orders, inventory, purchase orders and production schedules each sat in a separate place.
The decision
Each order is a constraint check across three moving quantities: its target date against stock, material arrival and capacity.
The miss
Orders heading for a late date were not flagged before the date slipped.
The agent proposes. The planner signs.
The plan
It reads the ERP and legacy exports and builds one fulfillment plan, with a visual view and a suggested action for each order at risk.
The signature
The planner approves every plan that goes out. The agent does not release one alone, and the client is not ready to remove that step.
The blocker was habit, not code.
Adoption
Planners kept opening their old spreadsheet first, even when the agent was right. Seminars and one-to-one sessions fixed that, not a change to the agent.
Of planning every day, across the ERP and legacy exports.
Ten hours of stitching exports together each day is now one plan the whole floor shares. Every order heading for a late date is flagged while there is still time to move it, instead of found after it slips.
Book a callTirion
The Financial Operating System for Construction
Next file