Standby and idle energy losses are the electricity a plant consumes while producing nothing: motors spinning between jobs, conveyors running empty, compressors loading against leaks, ovens and hydraulics held hot through breaks. It is among the cheapest energy to eliminate because, by definition, cutting it costs no production, and among the most overlooked because it hides inside the normal hum of a running factory.
None of it makes a unit of product, and much of it runs 24/7 regardless of the schedule.
A 55 kW compressor serves a line that runs two shifts, five days. Over nights and weekends the line is off, but the compressor keeps cycling to hold system pressure against leaks and to feed a few always-on actuators, drawing an average of, say, 18 kW during the roughly 112 non-production hours each week. That is about 2,000 kWh per week, over 100,000 kWh a year, spent making zero product, much of it feeding leaks. Isolating the air system out of hours (a valve and a schedule) and fixing the leaks (a leak survey) can reclaim the large majority of it. The intervention is a scheduling decision and some maintenance, not a capital project, and the saving repeats every week forever.
Idle energy shows up as a floor on the load profile, the power drawn when production is zero. Overlay energy against production and the gap between "power when running" and "power when idle but on" is the target. The diagnostic depends on knowing exactly when equipment was actually producing versus merely powered, which is the same run-state data that OEE monitoring captures. Without accurate production state, idle energy and running energy blur together and the waste stays invisible.
Every hour of availability loss where equipment sits powered but not producing is simultaneously an OEE loss and an energy loss. The two metrics point at the same events: the machine that idles through a 40-minute material wait wasted 40 minutes of capacity and 40 minutes of energy. Plants that measure OEE already know when equipment ran empty; connecting that to energy turns an operations metric into a costed energy-saving list, often with faster payback than efficiency upgrades because the fix is behavioral and maintenance-driven, not capital.
Fabrico is not an energy meter and does not measure power, but it holds the one thing that turns a load profile into an action list: precise, time-stamped machine run-state, when each asset was actually producing versus idle-but-powered. Overlay that on your energy data and idle waste becomes visible and costable; the maintenance side (leaks, isolation, standby procedures) then closes it as scheduled work. Fabrico tells you when the factory was making nothing; your energy data tells you what that cost. EU-built, with EU data residency.
It depends on restart cost, energy draw, and stop length. Many machines are safely and cheaply shut for stops beyond a threshold; the analysis needs accurate stop durations, which OEE data provides. The common error is assuming restart is expensive when it is not, and leaving equipment running through avoidable idle time.
Energy consumed by a machine running without doing useful work, a compressor cycling to hold pressure, a pump throttled against a closed valve, a motor spinning a disconnected load. It is a large, common, and often invisible slice of idle energy, addressed by controls, sequencing, and leak reduction.
Directly: availability losses where equipment is powered but not producing are simultaneously energy waste. The same run-state data that quantifies OEE availability quantifies idle energy, which is why the two programs share a data foundation and often share solutions.
Want to see exactly when your factory runs empty? Book a Fabrico demo to see real-time run-state data that turns idle time into costed energy savings.
Вход
Блог