Work & Supply Network · a reference build
One repair, from warning to recovery.
A machine gives a warning. A part is needed, so someone has to find it, buy it, fit it and pay for it — and if it fails early, get the money back. In most organisations those steps sit in different systems that hand over to each other by email or by re-typing. This network connects them, and you can watch it work.
A network is a group of separate applications that cooperate.What is a network?
14 applications and an Orchestrator: Work Management, Inventory, Asset Register, Asset Lifecycle, Warranty, Assurance, Classification, Condition Monitoring, Maintenance Schedule, Workforce, Catalogue, Supplier, SAP AP, Purchasing.
Fictional scenario and synthetic data, on a DSLCore reference build. The finance system is a simulator, not a connection to SAP. Every replay is a real recorded run of the network; nothing on these pages is live.
The story: a repair in eight steps
Each step is its own recording, shown here in the order a repair meets them. They are separate runs of the network, not one continuous run.
A warning arrives
An engine-oil result comes back urgent. Condition Monitoring opens an alert and asks Work to raise a draft order. When that order is later closed, the alert is resolved.
See it happen →A service comes due
A meter reading is recorded on a truck whose service is due. Maintenance Schedule asks Work for the order, using the plan’s template, and closing the order feeds back into the schedule.
See it happen →The part is in stock
A work order needs two oil filters. Inventory has them and reserves them for the job, and Work is told.
See it happen →The part is not in stock
A work order needs a transmission and none is in stock. Inventory reports it unavailable, Work knows the job is held, and Purchasing raises a requirement to buy one.
See it happen →The part arrives
The transmission is shipped, arrives and is accepted. The reservation that was waiting for it is filled and the held work order can go ahead.
See it happen →The work is closed and costed
Reserved stock is issued to the order, the work is verified and closed, and Finance moves the order’s cost to the asset it was spent on — without anyone typing it in again.
See it happen →The supplier is paid
The supplier invoices the order. Finance matches the invoice against the order and the goods received, posts the liability and pays it.
See it happen →A failed part is recovered
The failed transmission has an eligible warranty claim. It is claimed, part-approved by the supplier, credited in Finance and recorded as recovered.
See it happen →
Who does what
Fourteen applications, grouped here by the job they do. Each is small and does one thing; they are connected, not combined, and an orchestrator carries the messages between them.
Watch and plan
Condition Monitoring reads oil and other results and raises alerts. Maintenance Schedule works out when each service is due, from meters, dates and plans.
Do the work
Work Management holds the work orders, the hours and the costs. Workforce holds the people and their trades.
Supply the parts
Inventory holds stock and receipts. Purchasing places orders. Supplier holds who the business buys from. Catalogue defines the items.
Know the assets
Asset Register holds the machines and their components. Asset Lifecycle tracks usage and life. Classification gives shared codes so parts and faults are named the same way everywhere.
Pay and cost
A simulated finance system (SAP AP) holds invoices, matches them, pays them and posts each job’s cost to the asset.
Recover under warranty
Warranty finds a claim when a part fails early, follows it through to the supplier’s decision, and records the recovery.
Keep it accountable
Assurance records an issue as an exception with an owner, so a problem does not just disappear.
Orchestrator
Carries every message between the applications, retries when one is down, and keeps a record of what was sent and received.
Why connect them
A warning becomes work
An urgent result in one application becomes an order in another, and closing the order resolves the original alert.
Services come from the plan
When a reading shows a service is due, the order is raised from the plan’s template, not from someone remembering.
A shortage reaches the right place
When stock runs out, Purchasing is told without Inventory needing to know how buying works.
Cost is posted once
Parts issued and hours booked flow from Inventory and Work to Finance and are posted to the asset, without re-keying.
Each system keeps its job
The owner of each kind of data keeps it and its rules. Systems cooperate by passing messages; none reaches into another’s database.
Every step leaves a record
Each message carries the references of the order or claim it belongs to, so a job can be followed from the need to the payment.
The recordings are separate runs on synthetic data, shown in the order a repair meets them rather than as one continuous run.
Watch it happen
Each recording is a real run of the network. Play it, pause it, step through it, and open any message to see who sent it and who received it.
Urgent oil result
An engine-oil result comes back urgent: Condition Monitoring raises an alert, Work is asked for a draft order, and closing the order resolves the alert.
A service order from the plan
A meter reading is recorded on a truck whose service is due: Maintenance Schedule asks Work for the order from the plan, and closing the order feeds back into the schedule.
In stock
A job needs two oil filters. Inventory has them and sets them aside for the job.
Out of stock
A job needs a transmission and none is in stock. Inventory says so, and Purchasing is asked to buy one.
Delivery
The ordered transmission is shipped, arrives and is accepted. The reservation that was waiting for it is filled, and the held job can go ahead.
Job cost
Stock reserved for a job is used, the job is checked and closed, and Finance posts its cost to the asset.
Invoice to payment
The supplier invoices the order. Finance checks it against the order and the goods received, records what is owed, and pays it.
Warranty recovery
A failed transmission has an eligible warranty claim. It is claimed, part-approved by the supplier, credited in Finance and recorded as recovered.
What this is, and is not
It is a working reference build showing how separate applications can be connected so that a repair is carried from warning to payment and recovery. The finance system is a simulator. It is built so far around heavy mobile plant such as haul trucks, and other kinds of asset are not yet covered. It is not presented as compliant with any named standard, and the examples use synthetic data on a single machine.