What Is a Motor Control Center (MCC)?
A motor control center is the central enclosure that houses and protects the starters, breakers, and controls for a group of electric motors. In an oil and gas facility, one MCC lineup can feed dozens of pumps, compressors, and fans from a single organized assembly. This guide explains what an MCC is, how it is built, and how it ties into a SCADA system.
Motor Control Center (MCC) in one line: A motor control center (MCC) is a floor-standing assembly of vertical sections that houses the combination starters, circuit protection, and control devices for multiple electric motors, distributing power to them from a common bus.
What an MCC Is and How It Is Built
A motor control center is a modular lineup of steel vertical sections bolted side by side, each divided into compartments. A horizontal power bus runs across the top of the lineup and vertical buses drop into each section, so every compartment can tap the same incoming supply. This lets one central assembly power and control an entire area's motors instead of scattering individual starters around the plant.
Each motor gets its own removable compartment, commonly called a bucket. A typical bucket contains a circuit breaker or fused disconnect for short-circuit protection, a contactor to switch the motor on and off, and an overload relay to protect against sustained overcurrent. Buckets are drawer-style and interlocked so a technician cannot open a live compartment, and a faulted bucket can be swapped without de-energizing the whole lineup. Low-voltage MCCs (up to 600 V) are the norm for most oilfield process motors; medium-voltage lineups exist for large compressors.
Where MCCs Fit in Oil and Gas and SCADA
On a gas plant, compressor station, or saltwater disposal facility, the MCC is the electrical heart of the process area. It feeds the motors that drive injection pumps, transfer pumps, cooling fans, and compressor auxiliaries. Consolidating this gear into one lineup simplifies maintenance, arc-flash management, and the wiring back to the control system.
Modern MCC buckets increasingly include intelligent overload relays and soft starters or variable frequency drives (VFDs) that publish motor current, run status, and fault codes over a fieldbus such as Modbus, EtherNet/IP, or PROFIBUS. A SCADA platform reads those values so operators can see, from a dashboard, which pumps are running, their amperage, and any trip conditions. Merobix ingests MCC and drive data over Modbus or EtherNet/IP where the devices expose it, giving remote visibility into motor health without adding hardware to the lineup.
Specifying an MCC Lineup
The ratings that matter most are the ones set by the electrical system, not the motor list. Bus bracing and the interrupting ratings of the protective devices must meet the available fault current at the installation point, a site-specific figure that comes from the short-circuit study - an undersized bus is not a paperwork problem, it is shrapnel under fault. Alongside that: the incoming main arrangement, the enclosure type matched to the environment using the NEMA enclosure designations, and physical space. Order spare buckets and blank sections up front, because adding a vertical section to an energized lineup years later is a shutdown-scale job while an empty space is a bolt-in.
Starter philosophy is the other early decision, since NEMA vs IEC motor starters trade robustness and habit against footprint and cost, and the choice ripples through every bucket in the lineup. Specify the details that make the lineup serviceable for decades: consistent bucket space factors so units interchange, generous wireways, terminal provisions for control wiring, and network drops in each section if intelligent overloads or drives are in the plan - pulling communications cable through a finished lineup is miserable work.
The Signals Worth Bringing Back to SCADA
A bare minimum point list per bucket answers three questions remotely: is the motor running, has it tripped, and why will it not start.
| Signal | Source | What it answers |
|---|---|---|
| Run status | Starter auxiliary contact or device comms | Is the motor actually running, versus merely commanded |
| Trip / fault | Overload relay contact or fault register | Did it stop, or was it stopped |
| Motor current | Smart overload relay or drive | Load trend and early mechanical warning |
| HOA position | Selector switch contacts | Why a remote start command is being ignored |
| Speed reference and feedback | VFD comms | Is the process getting what the loop asked for |
Networked devices deliver far richer data than hardwired contacts - full fault codes, thermal state, energy figures - but the communications link is a shared failure point, so safety interlocks and critical shutdowns stay hardwired regardless of how good the fieldbus data is. The HOA point deserves its place on the list: the difference between local and remote command authority, laid out in local HOA vs SCADA remote motor control, is the single most common answer to why a motor will not start from the dashboard. Map and verify every fault register during commissioning, while tripping things on purpose is still cheap.
Working Safely Around an Energized Lineup
An MCC concentrates fault energy, and the highest-exposure routine task is racking a bucket in or out against a live vertical bus. The incident energy at the lineup, and therefore the PPE and boundaries, comes from an arc-flash study, and the labels on the gear reflect that study - not a generic table. Features like closed-door racking and remote racking exist precisely to move the worker out of the blast zone during the worst task. None of this substitutes for the site's energized-work procedures and qualified electrical workers; treat every decision at the lineup as governed by them.
Remote monitoring earns a safety justification here that has nothing to do with convenience: every current reading, fault code, and run status that arrives over the network is a panel-front visit that did not happen, a door that stayed closed, and a person who was never standing in front of the bus. Fewer trips to the lineup is a legitimate line item in the arc-flash exposure reduction plan.
Where MCC Lineups Fail
The characteristic wear points are the stabs - the spring clips on the back of each bucket that grip the vertical bus. Repeated racking cycles fatigue them, and a stab that has lost clamping force heats under load, discolors, and eventually arcs. Bus splice joints between sections loosen with thermal cycling the same way. Both show up beautifully in infrared thermography done under the site's maintenance program, which is why periodic IR scans of an MCC are standard practice. Inside the bucket, contactor contacts erode with every operation and coils age, so high-cycle motors get their contactors inspected on a schedule the duty justifies.
The environment does the rest: dust and corrosive gas drawn in by ventilation, condensation in unheated buildings attacking the bus, rodents in remote structures. Space heaters and sealed conduit entries are cheap insurance. And the trend data the MCC itself provides closes the loop - a motor whose running current creeps up month over month is telling you about the driven pump or the process long before the overload relay has anything to say.
Frequently Asked Questions
What is the difference between an MCC and a switchgear?
Switchgear is built to distribute and protect main power circuits at higher fault ratings and typically feeds large loads, transformers, and other panels. An MCC is optimized for controlling many individual motors, packing dozens of starters into compartmentalized buckets. Switchgear distributes power upstream; the MCC controls motors downstream.
What is inside a typical MCC bucket?
A standard combination starter bucket contains a disconnect (circuit breaker or fused switch), a contactor that opens and closes the motor circuit, and an overload relay that trips on sustained overcurrent. Buckets may also hold control transformers, VFDs, soft starters, and terminal blocks for control wiring.
Can a SCADA system read data from an MCC?
Yes, if the MCC uses intelligent starters, smart overload relays, or drives with communication ports. These devices publish current, run state, and fault data over Modbus, EtherNet/IP, or PROFIBUS, which SCADA can poll. Older electromechanical buckets provide only hardwired run and trip contacts that must be brought into a PLC or RTU.
Why does a motor start locally at the MCC but not from SCADA?
Start with the HOA switch: in Hand, the remote command path is deliberately bypassed, and in Off it is blocked entirely - which is why HOA position belongs on the SCADA point list. If the selector is in Auto, work through the remote chain: a process permissive or interlock not satisfied, the command not reaching the bucket, or a fault that local operation happens to mask.
What does arc-resistant MCC construction actually do?
It contains and redirects the blast of an internal arcing fault, venting the plasma and pressure through ducts and flaps away from where an operator stands, so a fault with the doors closed is survivable at the front of the gear. It does not reduce the fault energy itself, and it does not replace the arc-flash study, labeling, PPE, or the site's energized-work procedures.
Sources and verification
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
- Modbus Application Protocol Specification - Modbus Organization
Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.