How to specify recloser communication for SCADA projects

Recloser communication protocols define how a controller exchanges status, measurements, and commands with SCADA; buyers should lock roles, points, time sync, and security boundaries before comparing protocol labels. Use this page to separate protocol labels from role maps, point lists, and acceptance tests.

Part 1. What a recloser communication interface actually connects

A recloser communication interface links the controller to SCADA or a telecontrol gateway. It carries status, measurements, and commands only as the architecture assigns those roles.

Readers searching for recloser communication protocols usually need a project checklist, not a catalog slogan.

Part 2. Protocol choices that belong in the project specification

Name candidate protocols as requirements, not as brand defaults. Record which device speaks which profile and who owns gateway translation.

Part 3. How SCADA points and controller functions should be separated

A point list is not the same as protection logic. Keep measurement and status exposure separate from curve ownership in the RFQ.

Important: Do not accept a recloser communication offer that is silent on roles, points, and time sync. A protocol label alone is incomplete. (Source: IEC telecontrol / IEC 61850 overviews / project architecture notes.)

Part 4. Why event records and time synchronisation matter

Event order and SOE usefulness depend on a stated time-sync method. Ask for the project expectation without inventing accuracy claims here.

Part 5. Security and network boundaries the RFQ should state

State network zones, remote access rules, and document expectations at requirements level. Do not copy another utility’s hardening checklist blindly.

Part 6. Supplier inputs that make controller integration testable

Ask for interface documents, point list drafts, and test scope when discussing JUBANG pole-mounted switching routes.

• ZW32-40.5 Outdoor Pole Mounted VCB — switching device discussion once communication roles are documented.

Related articles:
– pole-mounted recloser checklist
– feeder automation architecture
– primary-secondary fusion breaker checks

Bring the role map to the JUBANG medium-voltage pole-mounted circuit breaker range discussion, or contact JUBANG with the point-list draft.

Why not: Do not treat a protocol name as proof that SCADA integration is complete.

Part 7. Fit boundaries for this communication guide

This page supports RFQ language. It does not certify protocols or approve a SCADA configuration.

FAQ

Which protocol profiles commonly appear in recloser SCADA RFQs?

Common candidates include telecontrol and utility automation profiles named by the project; the architecture decides which one applies.

Does every recloser controller need a separate RTU?

Only when the design assigns that role. Some controllers expose telecontrol directly.

Which SCADA points should a recloser expose?

Expose the status, measurements, and commands listed in the approved point list – not an unbounded catalog dump.

Why does time synchronisation matter for recloser events?

Without a stated sync method, event order and SOE review become unreliable across devices.

Can one protocol choice prove interoperability by itself?

No. Interoperability needs profiles, points, tests, and gateway scope documented together.

What should be tested before recloser communications acceptance?

Interface connectivity, point mapping, command paths, and time-sync behavior under the approved procedure.

Does this page approve a SCADA design?

No. Design approval belongs to the project authority.

References

• IEC telecontrol publications
• IEC 61850 overview
• DNP Users Group