IEEE 1547-2018 requires a distributed energy resource to offer a standard communication interface, and the accepted protocols are SunSpec Modbus, IEEE 2030.5 and IEEE 1815 (DNP3). The standard does not choose one for you. The utility picks the protocol that fits its head-end system and decides which data it reads or writes.
A DER that cannot be read or configured remotely is hard to operate at scale. IEEE 1547-2018 added a requirement for a standard communication interface. The background is in the IEEE 1547-2018 guide and the US electrical codes and grid interconnection guide.
This guide is based on IEEE 1547-2018 (active, amended by 1547a-2020). IEEE has a revision in development.
Short answer
IEEE 1547-2018 requires a DER to include a communication interface that supports at least one of three protocols: SunSpec Modbus, IEEE 2030.5 or IEEE 1815 (DNP3). Through it, the utility or an aggregator can read status and measurements, and write settings and commands, according to the standard’s information model. Test conformance to IEEE 1547.1-2020 can be shown with one protocol. The standard does not itself include normative cyber security requirements.
What each protocol is used for
Typical roles, which are common practice rather than rules:
- SunSpec Modbus: a Modbus register map defined by the SunSpec Alliance. It is often used on the local side, between a gateway or controller and the inverter. See inverter integration to SCADA with Modbus and SunSpec.
- IEEE 1815 (DNP3): common for larger resources operated from a control center. See the guide on DNP3.
- IEEE 2030.5: an internet-based protocol suited to many small resources behind the meter, often managed by an aggregator or the utility head end.
Many products carry a gateway that converts one protocol to another. In that case the certified interface is the gateway’s, and its firmware belongs in the configuration record.
Interoperability, not only connectivity
Interoperability means that two products from different vendors exchange the same information with the same meaning. Without a shared model, a utility with thousands of devices would need a custom interface for each vendor and each firmware version. The standard fixes the information model so that “set the volt-var curve” means the same thing on any compliant inverter, whichever protocol carries it.
How the utility chooses
The utility picks the protocol that fits its head-end system. A utility with a mature SCADA that already speaks DNP3 will ask larger plants for IEEE 1815. A program that manages thousands of small residential units will ask for IEEE 2030.5, because it works over the internet and scales to many devices. An installer working locally with a controller will often meet SunSpec Modbus first. If your inverter supports only one protocol and the utility wants another, a certified gateway is the usual answer.
Data to agree before design
The information model covers status, measurements, settings and commands. In the interconnection process, agree which of these the utility will use:
- Monitoring only: output power, voltage, status and alarms.
- Settings: the ride-through, voltage-support and trip values, which the utility may update.
- Commands: output limits or connect and disconnect.
The more the utility can write, the more the access control matters. A write path into an inverter is also a way to change how much power the grid receives, so it needs the same care as a relay setting.
Security
The interface is a way into a device that can move power. Treat it like any other remote path into the plant. The companion document is covered in IEEE 1547.3 on cyber security of distributed resources. For the protocol layer, see secure IEC 104 and DNP3, and for the inverter specifically, NIST IR 8498 and solar plant cybersecurity.
Worked example: size of a polling link
This is illustrative, with our own data. A site controller reads 50 SunSpec Modbus holding registers from each of 20 inverters every 4 seconds, over Modbus TCP.
- Payload per read: 50 registers × 2 bytes = 100 bytes.
- Request frame: 12 bytes (7-byte header plus a 5-byte read request).
- Response frame: 7 + 2 + 100 = 109 bytes.
- Per inverter per poll: 12 + 109 = 121 bytes.
- For 20 inverters every 4 s: 20 × 121 / 4 = 605 bytes per second, or 4.84 kbit/s.
This ignores the TCP and IP headers and acknowledgements, which roughly double the traffic for such small messages. Even then the link is small. The design question is rarely bandwidth. It is who may write to the registers, and how those writes are logged.
Questions to put to the utility
- Which protocol and which version of the information model will be used?
- Does the utility connect directly, or through an aggregator or a head-end system?
- Who owns the certificates or credentials for the link, and how are they renewed?
- Which points are mandatory and which optional?
- How will a failed link be handled: does the DER keep its last settings or revert to defaults?
Checklist for the engineer
- Ask the utility which protocol it will use, and which points it will read and write.
- Confirm the inverter or its gateway supports that protocol, in the certified firmware.
- Define the network path, the firewall rules and the access control for writes.
- Keep the register or point list as part of the project record.
- Test reading and writing during commissioning; see on-site PV inverter tests.
- Plan how firmware updates will be applied without breaking the interface.
Who signs and seals
In the United States, drawings and studies are normally signed and sealed by a professional engineer licensed in the state of the project. Our work is delivered ready for your engineer of record to review and stamp. Tiza does not sign, seal or certify work in the United States.
Our remote relay and inverter configuration service sets up the communication points and the settings plan for the protocol your utility requires. Your engineer of record can then review the result. Contact us with the inverter model and the utility’s protocol.
Frequently asked questions
Which communication protocols does IEEE 1547 accept?
IEEE 1547-2018 requires the DER to support at least one of three: SunSpec Modbus, IEEE 2030.5 (also called Smart Energy Profile 2.0) or IEEE 1815, which is DNP3. The utility tells you which one it will use for your project.
Does IEEE 1547 require the DER to be connected to the utility?
The standard requires the interface to exist. Whether the utility connects to it, and which data it reads or writes, is decided by the interconnection agreement. Some projects use it only for monitoring and some for remote settings.
Does the standard cover cyber security?
Not as a normative requirement in IEEE 1547-2018. Cyber security guidance is in the companion document IEEE 1547.3, which has its own guide on this site.