Scope
Two systems, one clear boundary
The first question most plant owners ask is whether new software means touching the plant. It does not.
What Linkoper does not do
- Control or read from batching systems, PLCs or SCADA
- Set, store or calculate mix designs
- Manage aggregate, bitumen or filler inventory
- Monitor burner performance, temperatures or tank levels
- Require any change to your plant automation
What Linkoper does do
- Take orders through a customer portal instead of by phone
- Handle recurring, multi-product and multi-date orders
- Plan the day's deliveries against the trucks you have
- Give drivers their assigned loads and customers live status
- Produce delivery notes, invoices and quotations from the order
How it works
Where the two systems meet
One handover point, in one direction.
- 01
The order is agreed in Linkoper
A customer orders through the portal, or your office enters it. Product, quantity, site and requested time are captured once, in writing.
- 02
The plant produces to that order
Your operator sees what is required and when, and runs the batching system exactly as today. Linkoper sends no setpoints and no recipes.
- 03
The delivery is recorded against the order
Loads, times and quantities are logged against the order, so dispatch, driver and customer all read the same record — and the paperwork follows from it.
Why it matters
Why the boundary is the point
No plant downtime to adopt it
Nothing is rewired, so there is no commissioning window and no automation risk.
No lock-in at the plant floor
You can change or upgrade your batching system without touching Linkoper, and the other way round.
A shorter implementation
The work is configuring products, plants, sites and users — not interfacing with hardware.
Common questions about plant integration
Direct answers, including where Linkoper stops.