Platform
One plant model. Every module reads it.
You describe the plant once: site, area, line, section, unit. Production, quality, maintenance, safety and people all hang off that description, and every record names who did what and when.
Why it holds together
Three things that are true of every module
Two people must agree.
One person records the work. A second person approves it, and the system refuses self-approval even when one user holds both roles. Quality, Calibration, HSE, Permit to Work and Documents all follow that rule, because it sits in the platform rather than in five separate features.
The plant is entered once.
Master Data holds the hierarchy: site, area, line, section, unit. Maintenance, Calibration, HSE, Permit to Work, Quality, Shifts, Production and Utilities read that one description. There is no second equipment list to keep in step.
OEE from what actually happened.
Production records the counts, the stops and the scrap. Shifts supplies the window the line was staffed, and the server computes Overall Equipment Effectiveness (OEE) from those two. When it cannot be computed the score is blank, never a fake zero.
How it fits together
One plant model, five areas, and the joins between them
Master Data holds the plant. Every area reads it. The value shows up where two areas meet, because the check happens on its own without anyone remembering to make it.
Master Data
One plant model: site, area, line, section, unit. Every module reads it.
-
Operations
Production, Scheduling, Capacity Planning
-
Assets & Energy
Maintenance, Spare Parts, Calibration
-
Quality & Compliance
Quality, In-Process & SPC, Validation
-
Safety
HSE, Permit to Work
-
People & Improvement
Skills & Training, Shift Handover
Master Data → Maintenance
Add a line to the plant model and its asset record appears in Maintenance as a draft. Nobody describes the same machine twice.
Production → Tools & Fixtures
Output counts tool life. A mold comes off the machine on shot count, not on a date somebody wrote in a spreadsheet.
Calibration → In-Process & SPC
A reading taken with a gauge that is out of calibration is refused at entry. The control chart only holds measurements you can defend.
Skills & Training → Permit to Work
The permit checks that the worker holds the competency the job needs, and that the certificate behind it has not expired.
The modules
Five areas of the plant, on one foundation
Each area is a page of its own. Every module inside it is licensed on its own, so a plant starts with what hurts most and turns on the next module later.
Operations
The factory day, planned and recorded.
- Production
- Scheduling
- Capacity Planning
- Shifts & Labor
- Traceability In design
- Inventory Planned
Quality & Compliance
Catch the drift, record the defect, prove the fix.
- Quality
- In-Process & SPC
- Validation
- Batch Records Planned
Assets & Energy
Every machine, gauge, tool and meter in one register.
- Maintenance
- Spare Parts
- Calibration
- Tools & Fixtures
- Utilities & Energy
Safety
Nobody works on a machine until it is safe.
- HSE
- Permit to Work
People & Improvement
Who can do the job, and what the last shift left behind.
- Skills & Training
- Shift Handover
- Kaizen Planned
Foundation
One plant model under every module.
These are not license lines. They apply to every module. You describe the plant once and Maintenance, Calibration, HSE, Permit to Work, Quality, Shifts, Production and Utilities all read the same description. The same login, the same permission check, the same audit trail and the same signature rule run underneath all of them.
Status
What is finished today
Built and running
Every live module shares one plant model, one login, one permission check and one audit trail. Electronic signature is a switch you turn on per action, on the approvals that matter to you. You buy modules one at a time, and a module that is off is absent from the system until the day you turn it on.
Not built yet
Traceability has a full specification and no build behind it. We can show you the design. Inventory, Batch Records and Kaizen are names in the menu and nothing more, which is why they carry a label everywhere they appear on this site. Operator tablet apps are not built either.
The system runs on hardware set aside for your plant, at your site or on a European cloud host, and an update reaches it when you choose to install it. Ask us what a module does today and you get the built answer, not the roadmap answer.
See it on your own plant.
Thirty minutes with an engineer. We walk the modules you care about against your own lines and shifts.