Water and beverages · WB-06 · Production lines during internet and power outages
The line must keep running, even without connectivity.
Marking has made the line dependent on internet and power supply. Manufacturers and an industry association say outages can stop production.
Platform: Plant Pulse, Goods Flow
Record summer daily electricity consumption, million kWh, July 2026.1
According to a representative of a major manufacturer, a minor code-reading fault or an internet outage stops the line this quickly.2
Hours when, according to a Ministry of Energy warning, temporary outages may occur in some regions.1
Outages cannot be prevented. Their impact on the line can be planned for in advance.
Who it is for
- Production Director
- Does the line keep running during an outage?
- Chief Power Engineer
- Power supply, UPS, outage log.
- Head of IT
- Internet link, local server.
- Plant Owner
- Cost of outages per month.
Where the problem lies
Not enough codes held at the plant
If codes are requested only when needed, the line cannot run when the internet is down.
Server and camera without backup power
Even after a short power outage, the server and camera take time to restart.
Report submission holds up the line
If the next step cannot proceed until data is sent, a connection loss carries over to the line.
Outages are not logged
How much time and how much product were lost remains unknown.
How the loss is calculated
| Outage loss | outage minutes × units/minute × margin per unit |
|---|---|
| Restart | restart minutes × units/minute × margin per unit |
| Scrap | units rendered unusable during the outage × unit cost |
| Codes | codes lost during the outage × cost per code |
Calculate with your data
Lost contribution margin from line stops during internet and power outages
This calculator estimates the contribution margin on units not produced while the marking line was stopped or restarting because of internet or power outages over one month.
Use spaces for thousands and a dot or comma for decimals. Use the same currency throughout.
Values stay in this page and are not sent to the server.
Scenario estimate
0 / 8 values entered
Enter your operating figures to see the estimate.
The margin loss is real only if output lost during stops cannot be recovered later, for example through extra shifts or from stock. The scenario minutes are your own target and are not guaranteed to be achievable. They should be confirmed by an audit and measurement. The calculator does not predict the quality of the power grid or of the internet provider. Changes to line software require the equipment supplier's approval. Buffer operation must comply with the rules of the national marking system (Asl belgisi). Assess scrap and lost codes separately, at cost and at code price respectively.
Formulas and assumptions
This calculator estimates the contribution margin on units not produced while the marking line was stopped or restarting because of internet or power outages over one month. It uses your logged observations. It compares this baseline with a target scenario you define, such as running with a prepared local code buffer. It also shows how many hours of production the code stock on the local server would cover. Only contribution margin counts here, meaning price minus variable costs, never revenue. Scrap, lost code costs, fines and the cost of implementing a buffer are excluded and not added to this figure. Results are estimates, not guaranteed savings.
- Current state: margin lost due to outages
- Outages per month × (stop minutes + restart minutes) × units/min × margin in UZS/unit, giving UZS/month. It applies only if the lost output cannot be recovered later.
- Scenario: margin lost due to outages
- Uses the same number of outages, but with your target stop and restart minutes, in UZS/month. The target is not guaranteed to be reached.
- Difference between current state and scenario
- Current margin loss minus scenario margin loss, in UZS/month. A negative result is shown as 0. This is an estimated range of exposure, not a guaranteed saving. Buffer implementation costs are not deducted.
- Production time covered by the local code stock
- Codes on the local server ÷ (units/min × 60), in hours. Assumes one code per unit. Codes consumed by scrap or reprinting are not included.
Facts and global practice
UzBev Association
Regular internet and power outages can stop production.3
Representative of a major manufacturer
A minor fault in reading a code or an internet outage stops the line immediately.2
Ministry of Energy, 16.07.2026
Summer daily consumption reached a new record of 288.1 million kWh.1
Ministry of Energy, 16.07.2026
During peak hours, technical faults in the grid may cause temporary outages in some regions.1
Outage frequency and duration depend on the region and the plant. Measuring them is the first step at the plant.
Local buffer and outage log
The data and power the line needs are kept within the plant. Once the connection is restored, data is sent from a queue.
- 01Codes
- Advance ordering
- Reserve on the local server
- Stock level control
- 02Power
- UPS: server, camera
- Voltage measurement
- Automatic restart
- 03Connectivity
- Backup link
- Report queue
- Send once restored
- 04Log
- Outage time
- Cause
- Impact on the line
Modules
The current maturity level is shown next to each module.
| Local code server | Storing codes at the plant and supplying them to the line | Engineering capability |
|---|---|---|
| Report queue | Sending to Asl belgisi once the connection is restored | Engineering capability |
| Outage log | Power and internet outages and their impact on the line | Engineering capability |
| Energy monitoring | Voltage and consumption measurement | In development |
How we start
- 01
Outage audit
Outages and their impact on the line are recorded for one month.
Outcome: outage map.
- 02
Buffer design
Code reserve, UPS and queue are designed.
Outcome: design and budget.
- 03
Pilot on one line
An outage is simulated for testing.
Outcome: the line runs without connectivity.
- 04
Scale-up
The remaining lines are connected.
Outcome: monthly report.
What is measured
| Outages | Number and duration, by type | Outage log |
|---|---|---|
| Downtime due to outages | Minutes of line stoppage | Operator panel |
| Restart time | From restoration of supply to line restart | Log |
| Code reserve | Codes on the local server relative to hourly output | Local server |
What is needed to start
- Responsible persons for power and IT
- Power and internet layout diagram
- Line and server locations
- Line time window for testing
What we do not promise
- Firm timeline and price without an audit
- Government decisions and deadlines
- Changes to line software without the equipment supplier's approval
- Unmeasured results or savings
- Quality of service of the power grid or internet provider
- Operating procedures outside Asl belgisi system rules
Self-check
- Are power and internet outages recorded in a log?
- Are the minutes of downtime caused by outages known?
- Are codes reserved in advance at the plant?
- Are the server and camera connected to a UPS?
- Is UPS status checked regularly?
- Is there a backup internet link?
- Are reports queued when the connection is lost?
- Is the time the line takes to restart after an outage measured?
- Has an outage test been carried out?
- Is there a person responsible for this area?
Outage audit
We measure how outages affect the lines at your plant and propose a local buffer design.
- Outage map
- Buffer design
- Plan and budget
Other solutions in this industry
Sources
- Ministry of Energy announcement. gov.uz/ru/minenergy, 16.07.2026.
- Statement by a representative of a major manufacturer. gazeta.uz, 30.03.2026.
- UzBev Association statement. gazeta.uz, 15.04.2026.