Product Core Brief
- Model: INNIS01
- Brand: ABB Bailey
- Series: INFI 90 / Symphony / Symphony Harmony
- Core Function: Network Interface Slave (NIS) module that provides a Process Control Unit interface to the INFI-NET communication loop.
- Product Type: Network Interface Slave Module
- Key Specs: INFI-NET communication interface | paired with INNPM11 | supports hardware redundancy
- Condition: New Original / New Surplus (depending on stock)
Key Technical Specifications
- Manufacturer: ABB (Bailey INFI 90 / Symphony product line)
- Part Number:
- Product Type: Network Interface Slave Module (NIS)
- System Compatibility: ABB INFI 90 OPEN, Symphony, Symphony Harmony DCS
- Primary Function: Works with the INNPM11 Network Processing Module to provide a Process Control Unit interface to the INFI-NET communication system
- Paired Module: INNPM11 (Network Processing Module)
- Communication Network: INFI-NET high-speed serial data highway
- Controlway Interface: Communicates with control modules via Controlway through the paired NPM
- Redundancy Support: Supports hardware redundancy with dual NIS + dual NPM configuration
- Status Indicators: 16 LEDs (two groups: Group A for fault codes, Group B for event counters such as packets sent, retransmissions, and losses)
- Power Requirement: +5 VDC from the Bailey MMU backplane
- Mounting Style: Single-slot Bailey Module Mounting Unit (MMU) installation
- ESD Handling: Requires Bailey field static kit during maintenance
- HS Code: 853710 (electrical control panels / assemblies)
Product Introduction (No Fluff)
The ABB INNIS01 is a Network Interface Slave module used in Bailey INFI 90, Symphony, and Symphony Harmony DCS systems. It operates as part of a two-module Process Control Unit interface, working together with the INNPM11 Network Processing Module to connect a controller node to the INFI-NET communication loop.
The INNIS01 handles the physical and protocol-level interface to INFI-NET, while the paired INNPM11 manages Controlway communication and database functions. This module is commonly found in legacy HCU and controller interface assemblies. Because it always operates as part of a NIS/NPM pair, replacement planning should consider both modules—especially in redundant configurations where primary and standby pairs must match.
QA & Testing SOP (Dynamic & Transparent)
This is a network interface slave module, so testing focuses on INFI-NET registration, NPM pairing, and loop communication integrity.
- Incoming visual inspection: Check the module housing, edge connector, faceplate LEDs, and PCB for corrosion, burnt components, or prior repair marks.
- Pairing verification: Confirm the INNIS01 is correctly paired with an INNPM11 Network Processing Module. A mismatched or faulty NPM will prevent the interface from functioning even if the NIS module is healthy.
- Backplane communication test: Seat the module pair in a known-good Bailey MMU and verify power-up without fault indicators.
- INFI-NET registration test: Verify the node registers on the INFI-NET loop and that LED Group A shows no fault codes.
- Redundancy test (if applicable): In dual NIS/NPM configurations, verify primary/standby failover behavior to confirm seamless transfer.
- ESD-safe handling and packing: Store and ship in anti-static packaging; handle by the module frame and avoid contact with the edge connector.
Installation Pitfalls & Guide (Engineer to Engineer)
❗ INNIS01 cannot operate alone. It must be paired with an INNPM11 Network Processing Module. Installing the NIS module without a valid NPM will not restore INFI-NET communication.
❗ Do not confuse INNIS01 with other NIS variants. Later generations such as INNIS11 and INNIS21 serve different network interface roles and are not direct drop-in replacements for the INNIS01/INNPM11 pair.
❗ Verify redundancy pairing before removal. In redundant configurations, both NIS and NPM modules exist in primary and standby pairs. Removing or mismatching one side can disable the failover path.
❗ Check INFI-NET loop termination. Communication faults attributed to the INNIS01 may actually be caused by missing or failed loop termination modules such as NTCL01 at the INFI-NET endpoints.
Replacement steps:
- Pre-install: Document current node address, record active alarms, and notify operations.
- Removal: If redundant, confirm the standby pair is active before removing the failed primary pair.
- Install: Seat the new INNIS01 with the correct INNPM11, verify retention, and confirm slot alignment.
- Power-on test: Verify LED status, confirm INFI-NET registration, and validate node communication with the controller.
Technical FAQ
1. Is the INNIS01 still available? Yes, but it is a legacy Bailey module. Availability depends on inventory condition. We carry new original and new surplus stock.
2. Can INNIS01 work without INNPM11? No. The INNIS01 is a slave interface module that requires the INNPM11 Network Processing Module to form a complete Process Control Unit interface to INFI-NET.
3. Can INNIS11 or INNIS21 replace INNIS01? Not directly. INNIS11 and INNIS21 are later-generation network interface slave modules with different pairing requirements and network roles. Substitution should only be considered after confirming system compatibility.
4. Does this module need firmware loading? The INNIS01 operates as part of the Bailey INFI-NET interface assembly. It does not require user firmware loading like a controller, but correct node addressing, loop configuration, and NPM pairing must be verified after installation.
5. What happens if the INNIS01 fails? The associated controller node may lose INFI-NET communication. In non-redundant configurations, this can interrupt data exchange between the controller and the rest of the DCS network.
6. What warranty do you offer? Standard warranty is 12 months unless otherwise stated. For surplus stock, warranty terms are confirmed at quotation.
