Implementation
Live in about a month, at one site
The cost that matters in industrial software is rarely the licence. It is how much of your own people's time disappears into the rollout. Here is what we actually ask for.
| When | What we do | What you do |
|---|---|---|
| Week 1 Connect | Stand up your instance, connect to your control system, and start recording. Map your locations, lines and equipment. | Network access and someone who knows the control system for a few hours. |
| Weeks 2 to 3 Make it yours | Build the metrics that matter to your process, the dashboards your shifts will actually open, and the alarms worth waking someone for. | A supervisor or plant manager to say which numbers matter and what a real alarm looks like. |
| Weeks 3 to 4 Move the work | Load your asset register, spare parts and preventive schedules. Migrate an existing maintenance system with its history if there is one. | Your maintenance lead, and an export from whatever you use today. |
| Week 4 onward Run it | Train operators on the mobile app, watch the first weeks with you, and adjust what is noisy. | Shift teams for a short session each. The app is the part that has to survive contact with gloves and a dusty screen. |
What usually slows a rollout
- Network access. Getting a route from the control network to the outside takes longer than the integration itself at most sites. Start that conversation with your IT team early.
- An asset register that does not exist. Plenty of plants have never written one down. Building it is worth doing regardless, but budget for it.
- Alarms configured too eagerly. The fastest way to make people ignore the system is a noisy first fortnight. We start conservative and tighten.
More sites after the first
The first site carries the thinking: what to measure, what an alarm means, how maintenance is organised. Sites that resemble it come up considerably faster, because the templates already exist.
Sites that do not resemble it are closer to a first deployment again, which is worth knowing before you plan a group rollout on the back of one pilot.
Autonomous control follows separately and on its own timeline. See KoPilot.
Scope your first site
Tell us about the site, the control system and how maintenance runs today. We will come back with a plan in weeks rather than a methodology.
Talk to our team