At 7:30 AM, the duty officer Zhou opens the energy consumption logbook as usual to record the power generation and charge-discharge data of the photovoltaic inverter and energy storage cabinet from the previous day. The dense numbers on the notebook take over twenty minutes to copy, and any errors require backtracking for verification. The core issue lies in the fact that data from photovoltaics, energy storage, and workshop electricity usage are isolated in separate tables, preventing them from communicating with each other.
For photovoltaic and energy storage energy management to function effectively, it relies not on installing more meters, but on enabling data flow between systems. The following sections explain the linkage relationships.
1. Linkage with Energy Consumption Acquisition Terminals: Collecting Accurate Bottom-Level Data
The starting point for photovoltaic and energy storage energy management is data completeness. Parameters such as inverter output power, energy storage battery SOC (State of Charge), grid connection point electricity, and workshop sub-item electricity usage cannot maintain timeliness or accuracy if collected manually. In this context, the test instrument data acquisition and control system assumes the role of "data collection": touch-screen data acquisition cards connect to meter terminals without requiring computers on the meter side. WiFi communication is deployed, and material models or equipment IDs are entered into the acquisition card. Test data is automatically uploaded to the server for storage, while a Kanban displays real-time information.
Suppose a hypothetical electronics factory installs a photovoltaic carport and a set of energy storage cabinets. By connecting the inverter, energy storage BMS (Battery Management System), and grid connection point meter to the acquisition system uniformly, the duty officer can query power generation curves and charge-discharge records for any time period via the Web interface using combined conditions. Failed items are marked in red, and hovering the mouse reveals test specifications. This solution estimates that the daily twenty-plus minutes spent on meter reading and verification can be eliminated, shifting data status from "post-event supplementation" to "real-time availability." Solidifying this step provides the necessary foundation for subsequent linkages.
2. Linkage with ESOP and Electronic Kanban: Integrating Energy Information into Workstations
Data stored only on servers has limited value. The linkage point between photovoltaic and energy storage energy management and ESOP (Electronic Standard Operating Procedure) electronic work instructions is that workstation screens display not only SOPs but also energy status relevant to the current shift. For example, when an SMT line starts its morning shift, the all-in-one terminal displays the work instruction corresponding to the current work order, while the sidebar shows the current power load of the line, the real-time photovoltaic power generation ratio, and the energy storage discharge status. Workshop supervisors can view plant-level energy consumption summaries on the electronic Kanban without needing to visit the distribution room.
This linkage follows a unidirectional data flow: the acquisition system stores data, while Kanbans and ESOP terminals retrieve and display it. The benefit is that information reaches the personnel directly. Suppose a production line schedules high-energy-consuming equipment during periods of low photovoltaic output. The team leader can view the power generation curve on the Kanban and communicate with planning to adjust the production sequence. Essentially, energy management is not about placing the burden solely on electricians; it is about making energy users aware of energy consumption activities.
3. Linkage with Andon Call System: Transforming Abnormal Energy Consumption into Respondable Events
There are scenarios in photovoltaic and energy storage energy management requiring human intervention, such as excessively low energy storage SOC, grid connection point power exceeding limits, or sudden spikes in line energy consumption. If these issues remain only in reports until month-end reviews, it will be too late. Linking with the Andon call system involves pushing threshold judgment results from the acquisition system into Andon events. When trigger conditions are met, the Andon terminal for the corresponding line lights up to signal a call. The responsible person receives a notification on their mobile phone, confirms completion on the terminal, and the event record is retained for traceability.
The test instrument data acquisition and control system itself possesses intelligent data warning capabilities. It can automatically send email notifications for anomalies such as yield rate deviations or CPK (Process Capability Index) falling below standards, for instance, triggering an email if CPK is less than 1.33. The energy scenario operates similarly by setting parameters like power and SOC as warning items, utilizing the same web-based historical review mechanism for warnings. Major anomalies can be reviewed post-incident. Consider a scenario where the energy storage cabinet SOC drops to the set lower limit one afternoon. The Andon light activates, the duty officer confirms within ten minutes, switches to grid power to supplement, and avoids passive power curtailment during peak evening hours. Once this chain functions, energy anomalies shift from "discovered at month-end" to "handled during the shift."
In the market, suppliers for energy consumption acquisition, ESOP, and Andon are often three different vendors. Linkages rely on interface integration, leading to disputes whenever interfaces change. Implementing photovoltaic and energy storage energy management alongside Andon, Kanban, and ESOP on a unified platform results in shorter data flow paths and eliminates additional upgrade fees, a capability difficult for agent-type vendors to provide.
To conclude, if a factory is already running ESOP or Andon and wishes to integrate photovoltaic and energy storage data, it is recommended to clarify three matters first: which meters need to be connected, who should receive anomaly alerts, and who needs to view the Kanban data. Once these points are clear, deployment discussions can proceed.