Marshalling Cabinet.
A marshalling cabinet is the physical interface between the field cabling and the control-system I/O cards. Field cables terminate on terminal blocks in the marshalling cabinet, and short cross-wires, marshalling wires connect those terminals to the system-side terminals that lead to the I/O cards. The cabinet is where the project-specific wiring schema gets imposed on the standardized I/O hardware.
Three drawings included on a new account.
What Marshalling Cabinet means.
A marshalling cabinet is the deliberate seam between two things that change on different schedules. The field cabling, which arrives in whatever order the cable schedule dictates, and the controller I/O cards, which have a fixed channel layout. Field cables land on terminal blocks on one side of the cabinet, short cross-wires carry each one across to the system-side terminal that leads to its I/O channel, and that cross-wired layer is where the project's specific tag-to-channel assignment is imposed. Without it the field wiring would have to match the card layout perfectly from the first day, and any later change, swapping a card type, moving a tag to a different signal class, adding a spare would mean re-pulling cable in the field instead of re-landing a cross-wire in a cabinet. The cabinet is sized from the I/O list. The channel count by signal class, plus the spare allocation a project carries, commonly around twenty percent, plus any segregation rule that keeps SIS apart from BPCS, together set the terminal count, the rack space, and ultimately the number of cabinets. Smart-marshalling systems change the economics by making each channel software-configurable as any signal class rather than fixed by card, which collapses the cabinet count and absorbs late I/O changes without rewiring, at a higher cost per channel that large projects justify on schedule and change-management grounds. Either way the starting point is a complete, signal-classified count of what the drawings carry.
Why a marshalling layer exists
Field cables arrive in whatever order the field-cable schedule specifies. PLC and DCS I/O cards have a fixed channel layout. Without a marshalling cabinet, the field cabling would have to perfectly match the I/O channel layout from day one, and any change, replacing a card, moving a tag to a different signal class, adding a spare would mean re-pulling field cable. The marshalling cabinet decouples the field-side wiring from the system-side wiring, so changes happen as cross-wire modifications inside the cabinet rather than as field excavation.
Smart vs traditional marshalling
Traditional marshalling. Terminal blocks on both sides, manual cross-wires, fixed channel assignment per card. Smart marshalling, Emerson CHARMS, Honeywell Universal IO, Yokogawa N-IO, ABB Select I/O, Rockwell EtherNet/IP universal I/O. Each channel is software-configurable as AI, AO, DI, DO via configuration rather than card swap. Smart marshalling collapses the physical cabinet count, simplifies the cable schedule, and accommodates late-stage I/O changes without rewiring. The capex per channel is higher. The project-schedule and change-management benefits are large enough on big projects to swing the case.
Where a signal terminates on its way from the field to the controller
Each hand-off is a place a wire can be wrong, and each one is defined by a different document. That is exactly why the loop diagram exists.
| Layer | Hardware | What arrives | What leaves | Document that defines it |
|---|---|---|---|---|
| Field device | Transmitter, switch, solenoid or actuator | The process condition | The device cable tails | Instrument datasheet and the hook-up detail |
| Field junction box | Terminal strip and gland plate | Individual instrument cables | One multipair home run | Junction box schedule |
| Marshalling cabinet, field side | Terminal blocks, fused and disconnect terminals, surge protection, earth bar | The multipair home runs | Cross wires | Cable schedule and loop diagram |
| Marshalling cabinet, system side | Terminal blocks facing the system cabinet | Cross wires | Prefabricated system cable | Loop diagram and the panel general arrangement |
| System cabinet | I/O cards in racks, with their power supplies | System cable | The backplane to the controller | I/O list and the panel layout |
| Controller | Processor and communications modules | The backplane | The control network | Control system configuration |
Terminal types in a marshalling cabinet
The terminal type is what makes a loop testable without cutting a wire. It is specified per signal class on the panel specification.
| Terminal type | What it is for |
|---|---|
| Feed through | A plain connection between two conductors |
| Fused | Protects and isolates one loop, usually with a blown fuse indicator |
| Disconnect or knife | Lets a loop be broken for testing without removing any wire |
| Test or measuring | Allows a meter or a loop calibrator to be inserted into the circuit |
| Earth | Bonds cable screens and armour to the cabinet earth bar |
| Surge protection | Diverts induced transients to earth before they reach the card |
| Intrinsically safe, coloured blue | Segregated terminals for intrinsically safe circuits, physically separated from the rest |
| Relay or isolator base | Carries a signal isolator, a relay or a barrier on the same rail |
Common questions
Where does the marshalling cabinet sit relative to the PLC cabinet.
How is the marshalling cabinet sized from the I/O list.
What is the difference between marshalling and system I/O cabinets.
Get the junction box schedule template.
Box by box, every gland, pair and spare accounted for, with the home run to the marshalling side. Plain .xlsx.