Your machines run all day. Nobody sees what they cost.

An hour is usually enough. The screens show what a supervisor already looks at: what is running, what stopped and why.

Kernopy picks up the stop as it happens and asks for a reason on a tablet or the line screen. One tap, not a form.

Typically days to weeks ahead, depending on the fault. Drift in power, heat or vibration shows up long before a trip.

No. It feeds it. Alerts can open a work order in the tool your team already uses.

Often not. We start with the meters you have and add clamp meters only where a machine has none.

Yes. Power is matched with production counts, so you get cost per part, per machine and per product.

Most sites find their first saving in the first month, usually a utility running when nothing needs it.

Yes. Each plant runs on its own and the numbers come together in one view for the group.

No. Kernopy reads from the controllers, meters and sensors you already have. Older machines without a controller get a small clip-on sensor. Nothing on the line changes how it runs.

Only if you want it to. By default it only reads. Any control action needs your sign-off and is logged.

Most plants see their first line on screen within two weeks. A full site usually follows in a few more, line by line, without stopping production.

That is the normal case. Kernopy speaks to the common machine and meter types out of the box and puts them all on the same screen.

Yes. Everything keeps running on site, and the readings are held and sent once the link is back. Nothing is lost.

You do. It can stay entirely inside your plant if you prefer, and you can export it whenever you like.

Yes. Every running batch is laid over your golden batch, so drift is visible while there is still time to correct it.

Yes. You see which unit is waiting on which, live, not at shift handover.

It watches heat transfer against load over time. When the same duty takes longer or more steam, it flags it.

It tells you how fast the drift is growing, so you can pick the cleaning window instead of having it picked for you.

Yes, using existing flow meters where you have them and a few added ones where you don't.

Yes. Figures come straight from the meters and are kept with a full history, ready for audit.

Yes, live, for every product and unit, instead of a formula at month end.

Pricing is per connected asset, so you start small and grow. We will give you a number after a short walkthrough of your site.

It sits beside it. Kernopy reads from your control system and historians without touching the control logic.

Yes. The connection is read-only by default and goes through a one-way path you approve. Your process safety systems are never part of it.

We use the instruments you already have in those areas. Where new sensors are needed, they are rated for the zone.

Usually within a few weeks of connecting the first unit, once a few batches have run through.

Yes. Kernopy can run fully inside your plant with nothing leaving the fence.

You do, always. Export it at any time in plain formats.

Yes. Each floor's temperature and the air handler behind it are on one view, with an alert when comfort starts slipping.

Yes. Alerts and the floor view work on any phone or tablet.

It measures power per ton of cooling for each one, side by side, so the one working harder stands out.

Yes. Pressure drop and run hours tell you when a filter is really due.

Yes, live, from the meters, not from an estimate.

Yes. You see the before and after for each schedule change.

Yes. Temperature and uptime per hall are recorded continuously and can be shared with customers.

Most buildings find one quick win in the first month, often cooling that runs harder than it needs to.

No. Kernopy reads from your existing BMS and meters and adds what the BMS does not show: efficiency, cost and comparison.

Only if you allow it. By default it advises and you decide.

A typical building is connected in one to two weeks with no downtime for tenants.

Yes. Every building, plant room and data hall can be compared on one screen.

Yes. Where a chiller has no data port, power and temperature sensors fill the gap.

You do. It can stay inside your building network if you prefer.

Yes, live, for each crusher, mill and belt, with every stop and its reason.

It shows which mill has room and which is struggling, so you can shift the load.

It tracks power and load patterns that change as liners wear, so relines can be planned weeks ahead.

Heat, vibration and power drift on bearings and pumps are flagged long before a failure.

Yes. Each block is compared with what the weather allowed, so underperforming panels stand out.

Yes, per machine and for the whole plant, live.

Yes. Generation, storage and diesel use are tracked together, day by day.

Yes. Each site runs on its own and reports into one group view.

Yes. Kernopy runs on site and keeps working through outages. Readings are stored and sent when the link returns.

Usually not many. We use what the plant already measures and add a few where something important is missing.

Yes. Load and generation sit on the same timeline, so you can run harder when the sun and wind are strong.

A first area is often live in two to three weeks, depending on access and travel.

Yes. It reads only, through a path your team approves, and never touches safety systems.

You do. It can stay fully on site.

Yes. Every unit's status is live, with an alert the moment one stops.

Yes. Visits can follow the condition of each unit instead of the calendar.

Yes. They see the fault, its history and the likely part before they leave.

Yes. Duty cycles, loads and run hours are recorded for every unit.

Yes. It is measured on every unit and can go in your reports to them.

Yes. Real usage across the fleet feeds the design of the next model.

Yes. Uptime is measured per unit, so the promise in the contract has data behind it.

It shows which customers run hard and would benefit from a service plan.

A small gateway goes with each unit or site. It can be fitted at the next service visit.

The gateway can use its own mobile link, so it never needs to join the customer's network.

Yes. Many builders fit it on the line so every unit ships connected.

If you want them to. You can give each customer a view of only their units.

From a pilot of ten to many thousands. You add units as you ship them.

You and your customers agree that. Kernopy keeps each customer's data separate.