The utility bill is a single number. This PoC breaks it down: metering at the machine or panel, consumption tied to work orders and output, idle draw exposed at night and between shifts, and power-quality problems that were costing money invisibly.
Measure my energy use caseTalk to a manufacturing engineerPrimary buyer: Energy Manager · Plant Manager · Sustainability Manager · Maintenance Manager · Finance Director
Durations are typical, not guaranteed. What extends a schedule: missing or incomplete data, security and network approvals, hardware lead times, sample collection, installation access, the production schedule, ERP test access, and the time your team needs to review results.
No unplanned shutdown is expected. Any installation window or controlled interruption is agreed with you in advance and scheduled around production.
| Metric | How it is defined | Where the number comes from | Type |
|---|---|---|---|
| kWh per product or work order | Metered consumption divided by confirmed output for the same period and machine. | Sensor, meter or device data | Operational |
| Idle energy | Consumption during periods with no production output, by machine and by time of day. | Sensor, meter or device data | Financial |
| Peak demand | Maximum demand in the measured period and the activity coinciding with it. | Sensor, meter or device data | Financial |
| Power factor and phase imbalance | Measured power factor and imbalance across phases, against the level your tariff penalises. | Sensor, meter or device data | Technical |
| Measurement coverage | Share of the scoped load actually metered, and what remains unmeasured. | Sensor, meter or device data | Technical |
| Data completeness | Share of expected measurement intervals received without gaps. | MSF platform data | Technical |
| Energy cost allocation | Share of the scoped energy cost that can now be attributed to a specific machine, product or order. | MSF platform data | Financial |
| Identified savings opportunities | Each opportunity with its measured basis, its estimated value and what implementing it would require. | Sensor, meter or device data | Financial |
Before implementation, MSF and your team agree how each metric is calculated, where the baseline comes from, what data is excluded, and what result supports a rollout decision. This page lists what gets measured; the actual targets belong in the written PoC scope, not in a marketing claim.
Commercial terms, hardware ownership, travel, integration scope and any rollout credit are defined in the written PoC proposal. They are not the same for every product, and this page does not promise them.
Savings are presented as measured opportunities and scenarios with their assumptions written next to them, never as a guaranteed percentage. What a PoC can prove is where the energy goes; what it saves depends on the actions you then take.
Typically 3 to 10 measurement points, chosen for share of consumption rather than convenience. One panel covering a whole area often answers the first question — where does it go — faster than ten individual machine meters.
Where they expose a usable protocol and measure what the question needs, yes, and reusing them is checked first. Where they only produce a monthly total, they cannot answer a per-product question and the gap is stated plainly.
No. Any supplier quoting a saving percentage before measuring your plant is quoting someone else’s plant. This PoC produces measured consumption, ranked losses and costed opportunities, and lets you decide which ones to act on.
Long enough to be representative — a full production cycle including changeovers, a weekend and at least one genuine idle period. Four weeks is typical; seasonal loads need longer and the report says so rather than extrapolating.
Tell us the scope you have in mind and we will come back with a written PoC plan: what gets connected, what you provide, how success is measured and what the decision at the end looks like.