Integration Timeline

Device Type	Common Devices	Integration Protocol	Integration Timeline	Remarks
Power Conversion System (PCS)	Mainstream PCS Brands (Standard Protocol)	Modbus RTU/TCP CAN	3 days	1. Requires register debugging and control logic verification
	Mainstream PCS Brands (Non-standard Protocol)	IEC 61850	10–20 days	Requires modeling, ICD import, and system integration testing New protocol stack development is relatively complex and takes longer for the first migration The timeline can be reduced by 50% for subsequent projects
	Niche / New PCS Brands (Non-standard Protocol)	Proprietary Custom Protocol	10–15 days	Requires register debugging and control logic verification Protocols from niche brands may be less mature, resulting in longer debugging time
Battery Management System (BMS)	Mainstream BMS	Modbus RTU/TCP CAN	3 days	1. Standard data integration
	Customized BMS	Proprietary Protocol	3–5 days	1. Requires custom integration development
PV Inverter	String / Central Inverter	Modbus RTU/TCP	2 days	1. Standard data integration
Energy Meter	Multi-function Energy Meter	Modbus RTU/TCP DL/T645	1 day	1. Standard data integration
Temperature Control System	Liquid Cooling Unit	Modbus RTU/TCP	2 days	1. Standard data integration
	Air Conditioner	Modbus RTU/TCP	2 days	1. Standard data integration
EV Charger	Mainstream EV Chargers / Charging Stations	Modbus RTU/TCP	4 days	1. Standard data integration and power scheduling
	Niche / New Brands EV Chargers	Modbus RTU/TCP	6–8 days	1. Standard data integration and power scheduling
Microgrid / Off-grid Applications	Pure Microgrid (VF/VSG)	Modbus RTU/TCP	10 days	1. Includes microgrid forming, islanding, frequency and voltage regulation logic
	Grid-connected / Off-grid Switching Circuit Breaker / ATS / STS	Modbus / Dry Contact	10 days	1. Includes interlocking and mode switching logic; high control complexity and mostly customized requirements
Diesel Generator	Generator Set	Modbus RTU	10 days	1. Includes start/stop control and power matching
Grid Dispatch	Industrial Park / Grid Control Center	IEC 104	20–30 days	Upstream integration with station-level control systems First protocol migration requires longer development time The timeline can be reduced by 50% for subsequent projects
Third-party Platform	Cloud Platform, Energy Management System	MQTT / HTTP	20–30 days	Direct cloud integration is not recommended due to difficulties in after-sales support and upgrades Cloud-to-cloud integration is recommended
Strategy Algorithms	Custom Charge/Discharge Strategy	/	/	1. Existing standard algorithms generally do not require additional development
	Peak-Valley Arbitrage	/	/
	Demand Management	/	/
	Reverse Power Protection	/	/
	Renewable Energy Utilization	/	/
	Dynamic Transformer Capacity Expansion	/	/
	Custom Strategy	/	/	1. Custom algorithms or other complex non-standard applications require separate evaluation and discussion