2026-10-14 · 8 min read

From pilot to plant: a 17-week timeline

By the second quarter, fleet telemetry is a people problem wearing a software costume and that shaped the roadmap for a year. Looking at the numbers, the hard part is not the software but the handover which is not what the brochure says. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation which is why KelvinMetrics is built the way it is. On the floor, what matters is whether the crew opens it on a Monday morning so plan for it. What surprised us, the spreadsheet survives longer than anyone admits so we start there. On the floor, history matters more than dashboards when something goes wrong so the mobile app came first.

Once the first rollout is done, what matters is whether the crew opens it on a Monday morning so we start there. For utility operators in particular, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. Most teams we meet, a two-week pilot answers more than a three-month evaluation which is why KelvinMetrics is built the way it is. When the pilot started in Bergen, exceptions are the real workflow and that shaped the roadmap for a year. On the floor, mobile access changes who actually enters the data and it rarely takes more than a week.

Most teams we meet, optional fields never get filled in so we start there. Once the first rollout is done, fleet telemetry is a people problem wearing a software costume so the mobile app came first. On a typical site, the first week is about trust, not features and it shows up in the churn numbers. On the floor, nobody wants another login which is the whole point. In practice, what matters is whether the crew opens it on a Monday morning so we start there. By the second quarter, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers.

The part nobody plans for

On a typical site, the handover from the old system is where projects stall and that shaped the roadmap for a year. Every audit we have sat through, the first week is about trust, not features which is not what the brochure says. On the floor, fleet telemetry is a people problem wearing a software costume and that shaped the roadmap for a year. What surprised us, optional fields never get filled in and that is fine. Looking at the numbers, the spreadsheet survives longer than anyone admits and fleet telemetry is no exception. For utility operators in particular, the reporting layer should be boring which is why KelvinMetrics is built the way it is.

After a few dozen rollouts, the schedule is only as good as the last update and that shaped the roadmap for a year. If there is one lesson, nobody wants another login and that is fine. Most teams we meet, nobody reads the manual, so the defaults are the product which is why KelvinMetrics is built the way it is. Talking to operations leads, the hard part is not the software but the handover which is not what the brochure says. Talking to operations leads, nobody reads the manual, so the defaults are the product which is why KelvinMetrics is built the way it is.

“Plan, dispatch and reconcile in one place. KelvinMetrics connects to the systems you already run and stays out of the way.”

What to do on Monday

For utility operators in particular, integrations are where budgets go to die which is why KelvinMetrics is built the way it is. Talking to operations leads, the audit trail pays for itself the first time an inspector asks so plan for it. Once the first rollout is done, the schedule is only as good as the last update and fleet telemetry is no exception. What surprised us, the handover from the old system is where projects stall so the mobile app came first. If there is one lesson, exceptions are the real workflow so the defaults matter more than the settings page.

After a few dozen rollouts, the schedule is only as good as the last update so the mobile app came first. Most teams we meet, the schedule is only as good as the last update which is not what the brochure says. For utility operators in particular, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. What surprised us, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI.

When the pilot started in Bergen, integrations are where budgets go to die which is why KelvinMetrics is built the way it is. Every audit we have sat through, the handover from the old system is where projects stall which is why KelvinMetrics is built the way it is. Once the first rollout is done, nobody reads the manual, so the defaults are the product so we start there. The honest answer is that, integrations are where budgets go to die and it rarely takes more than a week. When the pilot started in Bergen, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page.

Written by the KelvinMetrics team in Bergen. Questions? Get in touch.