Start with the operating questions
An intelligent motor control center (MCC) is most useful when its data answers specific operating and maintenance questions. Before selecting communications options, identify what operators need to know: whether a motor is running, why it stopped, whether a protective device has tripped, or whether a process condition is approaching an alarm threshold. Maintenance teams may also need fault history, starts-per-hour information, runtime, or device health indicators. These needs vary by process and by motor, so begin with a motor list and mark each load’s operational importance, control method, and consequences of losing visibility. Separate information needed for immediate response from data intended for trending or maintenance planning. This prevents a design from collecting signals with no clear use while overlooking important status. The resulting requirements give the MCC builder and controls team a practical basis for selecting devices, defining data points, and coordinating interfaces.
Choose communications by architecture
Communications choices should follow the plant’s control architecture rather than dictate it. Document the intended connection between MCC devices, controllers, supervisory systems, and any asset-management or historian platforms. Identify the control-system vendor and model where known, network protocol requirements, addressing conventions, and who owns switches, cabling, gateways, and configuration. A networked device may reduce individual hardwired status connections, but it also introduces requirements for network design, device mapping, and troubleshooting. Hardwired signals can remain appropriate for selected interlocks or critical indications; the project team should determine which functions require them under the control philosophy and applicable safety design. Confirm available ports, media, segmentation, and cybersecurity policies with the plant’s IT and controls representatives. Protocol support and device compatibility are project-specific details to verify, not assumptions to make from a generic description. Early agreement on these boundaries helps avoid late changes to drawings, programming, or commissioning plans.
| System | Voltage, phase, current and available fault current |
|---|---|
| Configuration | Lineup, protection, controls and enclosure as specified |
| Compliance | Applicable standards and listing confirmed for the assembly |
| Delivery | California and nationwide; schedule confirmed by quote |
Define useful monitoring points
Build a point schedule that states both the data and its purpose. Common candidates include run and stop state, local or remote mode, overload trip, control power status, and communication health. Depending on the selected motor starter, protective device, and process need, additional information might include current, thermal capacity, trip cause, or accumulated operating hours. Specify whether each value is a discrete state, measured quantity, alarm, or event, and identify the expected source and destination. Establish naming, units, scaling, normal states, alarm thresholds, and whether a point must be time-stamped or retained for trends. Avoid requesting every available parameter by default: excess data can burden controller programming and operator displays without improving decisions. Conversely, a point that supports diagnosis may be worth including for a critical load even if it is not needed for routine operation. Controls and operations personnel should review the schedule together before device selection is finalized.
Coordinate control and protection boundaries
Integration planning must distinguish commands, permissives, interlocks, protective trips, and indications. The plant control narrative should define which system initiates a start or stop, how local control is handled, what conditions inhibit operation, and how an operator recognizes a trip and restores service. Protective functions and equipment ratings require review by qualified professionals for the specific motor, feeder, fault conditions, and applicable codes; communications should not be treated as a substitute for required protection. Determine what happens if network communication is lost, a controller is unavailable, or an MCC device reports invalid data. Define whether the affected load stops, remains in its last state, or can be operated locally, consistent with the process hazard analysis and control design. These decisions affect device selection, wiring, programming, and testing. Capture them in project documents so the MCC design, control logic, and operator procedures agree.
Prepare for design review and commissioning
Useful project inputs include a one-line diagram, motor and load schedule, control narrative, network architecture, preferred protocol, point list, and plant standards for naming and alarms. Identify enclosure and environmental conditions, available control power, cable-entry preferences, and space or access constraints that influence the assembly and field connections. Provide the intended controller interface and clarify which party supplies, configures, and tests each communication component. During submittal review, compare the proposed device data and connection scheme against the point schedule, then resolve gaps before release for manufacture. Commissioning plans should cover device addressing, communication-loss behavior, point-to-point verification, alarm handling, and representative start, stop, and fault scenarios. Record final settings and network information for operations and maintenance staff. Switchgear Builder California builds new equipment in the USA with American components and can review project requirements with customers in California and nationwide. Any schedule-sensitive approach is subject to project review and confirmation.
