Where I&C Meets Electrical: Interface Discipline for ICS Safety Systems and GE Drive Packages

A detail design coordination review, based on the instrumentationtools.com article “Instrumentation and Electrical Teams Interactions (Detail Design Engineering)”.

The Duty Split Everyone Must Respect

The instrumentationtools.com article fixes the baseline. The I&C team owns control and safety systems, instruments, automation functions, and their facilities. The electrical team owns power feeders, distribution, drives, consumers, motors, and lighting. Many companies merge both into one E&I team for small projects or plant maintenance. However, large EPC work still splits them. Therefore, every interface between the two scopes needs a written owner.

First, respect the gray zones. The article names communications, radio, telephone, paging, and LAN/WAN as subjects assigned differently across companies. Second, remember that both teams co-produce key documents. Hazardous area classification is shared with HSE. Cable routing is shared with piping. Package design is shared with vendors. In each case, one team must hold the pen.

Five Interaction Types That Shape the Schedule

The article's interaction model groups cooperation into five types. Both teams work separately with other disciplines. Both teams interact directly with each other. Both teams jointly coordinate with piping on layout and routing. Both teams jointly support package design and procurement. Finally, both teams receive special assignments that vary by company. This classification sounds academic. However, it drives the schedule.

Moreover, direct interactions dominate the interface register. Instrument power supplies, UPS coverage, motor-start signals, and earthing references all cross the boundary. Consider a safety system built on ICS Triplex hardware. Its tripping outputs stop GE motors through breaker auxiliary contacts. The I&C team owns the trip logic. The electrical team owns the breaker and the wiring to its coil. The interface drawing must define contact type, voltage, fail state, and test access. I have seen that single sheet prevent a two-week startup delay.

Cable Routing: The Real Battleground

The article stresses simultaneous coordination with piping on above-ground and underground routes. This is where projects bleed money. Instrument signal trays must separate from power trays to protect analog signals. Power cables need heat-rise clearances. Both need access space for pulling and maintenance.

Therefore, run joint routing reviews at defined milestones. First, review before 3D model freeze. Second, review after piping stress releases its final routes. Third, review bulk material take-off together. One GE compressor package taught me the cost of skipping this. Its local drive cabinet needed a power feed on one side. The layout had reserved that side for instrument junction boxes. The move cost new tray runs and three weeks. A joint routing review would have caught it for free.

An Interface Matrix Procedure That Works

1. Build the matrix early. List every document and deliverable that needs both I&C and electrical input.
2. Assign one pen-holder per deliverable. The other party becomes mandatory reviewer, not co-author.
3. Resolve gray-zone scopes in writing. Communications and LAN ownership must appear in the project execution plan.
4. Freeze interface drawings for safety trips. Define contact duties, voltages, and fail states between ICS Triplex outputs and motor breakers.
5. Schedule joint reviews with piping on routing at each model milestone, and log closures.
6. Reconcile bulk take-offs together before procurement. Tray, gland, and cable surpluses reveal scope confusion early.

Packages, Vendors, and Late Surprises

Package units concentrate interface risk. The article describes the shared duty clearly. Both teams produce design criteria, requisitions, vendor document reviews, and startup support. Therefore, split the vendor document list explicitly. The GE drive package data sheets go to electrical. The package instrument list and its safety trip logic go to I&C. However, the interface terminals, power quality requirements, and earthing scheme belong to both.

Moreover, watch vendor control system integration. A skid PLC that speaks only proprietary protocols creates work nobody budgeted. Therefore, specify standard interfaces in the requisition. Modbus TCP or OPC at minimum. Hardwired trips for anything safety-related. Finally, hold a pre-FAT alignment meeting with the vendor, both discipline leads, and the operator. One hour there saves weeks of punch list.

Conclusion & Action Advice

Successful plants are designed at the boundaries between disciplines. Respect the I&C and electrical duty split, classify your interactions, and put every gray-zone scope in writing. Build the interface matrix, freeze safety trip interfaces, and review cable routing jointly. Your safety layer may run on ICS Triplex. Your drives may come from GE. Disciplined interfaces still turn two teams into one design.

Author: Deng Zhiqiang is an industrial automation engineer with over 10 years of experience in PLC, DCS, and control systems.