How to Separate Reclosers and FTUs in Feeder Automation

Feeder automation architecture assigns protection, sensing, and communications roles across reclosers, FTUs, and the control system; buyers should lock those role boundaries and data interfaces before comparing device quotations. Use this page to separate recloser, FTU, and SCADA roles before device shopping.

Part 1. How should feeder automation roles be mapped?

It is the role map for sensing, protection decisions, switching, and SCADA visibility along a feeder. Devices implement roles; they do not invent the map.

Readers searching for feeder automation architecture usually need a project checklist, not a catalog slogan.

Part 2. How do reclosers differ from sectionalizers?

A recloser typically interrupts fault current under its protection logic. A sectionalizer usually isolates after counting operations coordinated with upstream protection. Confirm project definitions before buying.

Part 3. Where does an FTU sit relative to protection?

An FTU often concentrates measurements, status, and telecontrol for a field unit. It does not automatically own protection settings unless the architecture assigns that role.

Important: Do not treat feeder automation architecture as a shopping list of reclosers and FTUs without a role map and protection ownership statement. (Source: IEC telecontrol / IEEE distribution protection resources / project architecture notes.)

Part 4. Why do protection settings stay outside device shopping?

No. Protection settings belong to the protection study and approved setting files. An FTU may transport or host functions only as designed.

Part 5. Which data interfaces belong in the architecture?

List points, protocols, time sync expectations, and cybersecurity boundaries at a requirements level without inventing setpoint values here.

Part 6. Which attachments close a feeder automation RFQ?

Attach the role map, device list, interface list, and document expectations, then discuss JUBANG switching device routes that fit the architecture.

• ZW32-40.5 Outdoor Pole Mounted VCB — switching device discussion inside a documented automation architecture.

Related articles:
– pole-mounted recloser checklist
– primary-secondary fusion breaker checks
– RMU expansion planning

Keep the role map with the JUBANG medium-voltage pole-mounted circuit breaker range inquiry, or contact JUBANG when device boundaries are still open.

Why not: Do not treat an FTU quotation as a substitute for a recloser protection study.

Part 7. What are the fit boundaries?

This article explains architecture vocabulary. It does not design protection, certify protocols, or approve a SCADA configuration.

FAQ

How should feeder automation architecture be described?

Describe it as the assignment of sensing, protection, switching, and communications roles along a feeder.

How do reclosers differ from sectionalizers on a feeder?

A recloser typically interrupts faults; a sectionalizer usually isolates after coordinated counts. Confirm project definitions.

Where does an FTU sit in feeder automation?

An FTU often concentrates field measurements and telecontrol; protection ownership must be stated separately.

May an FTU invent protection settings alone?

No. Settings come from the approved protection study.

Which interface items belong on the architecture sheet?

Points, protocols, time sync expectations, and security boundaries at requirements level.

Which attachments belong in a feeder automation RFQ?

Role map, device schedule, interfaces, documents, and destination.

Who approves the automation design for a feeder?

Design approval belongs to the project authority, not this article.

References

• IEC telecontrol publications
• IEEE Power and Energy Society
• Electrical Engineering Portal