Ask our team:
  • Phone: +86 181 0690 9650
  • E-Mail sales1@apterpower.com
  • Lifecycle status

    Active / Available from OEM
    Apter Power reviews controller identity, configuration scope, and condition before quotation.

IMMFC03

/ 4.9
1001 reviews | Need a Specific Revision?
ABB IMMFC03 is an INFI 90 multi-function controller for executing analog, digital, batch, and advanced control strategies with connected slave I/O.
In Stock
Ships by Wednesday, October 28
Fast Shipping Available
Get a quick price for IMMFC03
Quantity
*E-mail
Company
*Mobile
*Content
Upload (gif, jpg, jpeg, png, bmp, doc, docx, xls, xlsx, ppt, pdf, csv)

Technical specifications for IMMFC03

  • Manufacturer:
    ABB
  • Part Number:
    IMMFC03
  • Product Family:
    ABB Bailey
  • Product Type:
    Multi-Function Controller
  • Stock:
    1
  • Controller class:
    Multi-function controller
  • System family:
    INFI 90
  • Supported control types:
    Analog, digital, batch, and advanced
  • Maximum slave I/O modules:
    64
  • Referenced alarm-limit value:
    9998
  • Weight:
    0.92 kg
  • Estimated shipping dimensions:
    7.1x31.2x17.6cm
  • Tariff Code:
    8537101190
  • Country of origin:
    Sweden
  • Place of shipment:
    Xiamen,Fujian,China
By purchasing this item, you agree to the Terms & Conditions, ApterPower is not an authorized distributor for listed manufacturers or tradenames and therefore the manufacturer's warranty does not apply. All our products come with ApterPower's 1-year warranty.

More Information

Overview Manuals Control Execution Slave I/O Scope Configuration Recovery Product Applications

Features:

  • Application continuity: preserves the running strategy as the primary asset during a controller exchange.
  • Node-impact visibility: makes the connected slave set part of outage planning instead of treating the controller as an isolated board.
  • Evidence-based release: uses communication, I/O visibility, and representative control behavior as the acceptance basis.
This controller matters when a fault affects coordinated control execution across a node rather than one field channel or one termination point.

Hardware identity alone is insufficient for selection because the plant result is defined by the saved application, node assignment, and connected slave map; those records determine whether a spare can restore the same duty.

A controlled exchange combines a verified backup, a staged restart sequence, and an agreed functional test so the team can recover the node without rebuilding its control intent from memory.

Apter Power supports application-scope review and quotation for the ABB IMMFC03 Multi-Function Controller, with attention to the installed node and recovery records.
ABB IMMFC03 Multi-Function Controller Manuals,Datasheets,Link Important Notice: No qualified exact-model English PDF is attached. Use the complete product model in every document request.
  • Analog strategies: handles continuous-control functions in the loaded application.
  • Digital logic: executes discrete control sequences assigned to the node.
  • Batch functions: supports staged control within the configured strategy.
  • Advanced control: hosts higher-level functions defined for the controller.
  • Module capacity: coordinates up to 64 slave I/O modules.
  • Address map: the connected slave identities must remain aligned with the application.
  • Failure impact: one controller exchange can affect a broad set of field signals.
  • Commissioning order: restore communication and I/O visibility before releasing control.
  • Application image: preserve the running function-code configuration.
  • Node assignment: record communication addresses and controller role.
  • Baseline evidence: retain active alarms, status, and control-mode information.
  • Rollback: keep a validated recovery path before loading or exchanging hardware.
  • Process control: execution of mixed analog and digital control strategies.
  • Batch units: controller service where batch functions are assigned to the node.
  • Legacy I/O coordination: management of the documented INFI 90 slave set.
  • Controller repair: restoration of an existing IMMFC03 application and node role.
Description
The IMMFC03 is an ABB Bailey INFI 90 multi-function controller. Its controller role spans analog, digital, batch, and advanced control functions, making the installed configuration—not the faceplate alone—the decisive part of a replacement.

Within the node, IMMFC03 can coordinate as many as 64 slave I/O modules. This capacity lets one controller supervise a substantial I/O set, but it also means a poorly documented exchange can affect many field loops at once.

A sound IMMFC03 service plan therefore captures the function-code configuration, connected slave set, communication assignment, and restart sequence before removal. Those records support a controlled restoration instead of rebuilding the application from assumptions.
Alternative Names
IMMFC 03 Bailey IMMFC03
Technical notes
The IMMFC03 can execute multiple control classes and coordinate up to 64 slave I/O modules, so its operational value resides in the loaded application and node assignment. Back up the function-code configuration and slave map before removal; stop the exchange if those records cannot be recovered or reconciled.
Exceptional Service

Our Mission

  • 100% Satisfaction

    We believe expertise is priceless. With over 20 years of experience, and top engineers on staff, we can help you solve or avoid problems that threaten your business.
  • Trust Guaranteed

    Not only do we have a vast inventory, our team makes sure every piece of equipment is in working condition. Your purchases are also backed by our Warranty.
  • Expertise

    Time is money, especially when your equipment is down. We work quickly to get your equipment on its way so you can get it back up and running.

FAQS

The following is a list of questions commonly asked by our customers. Please contact us if you have a question about our process that is not answered below.
What must be recovered before IMMFC03 is removed from a live INFI 90 node?
Recover the running application, function-code configuration, node address, connected slave map, alarm state, and restart procedure before isolation.
How does the connected I/O set change an IMMFC03 replacement decision?
The controller may coordinate up to 64 slave modules, so every slave identity and address must match the saved application before the replacement is released.
What is the first diagnostic step when IMMFC03 restarts but field loops remain unavailable?
Check node communication and slave-I/O visibility before altering control logic; a broken address map can make a correct application appear inactive.
Can IMMFC03 be substituted only because another controller supports similar function codes?
No. Confirm hardware identity, node role, application compatibility, slave capacity, and the approved migration method before considering a different controller.
What should procurement request when sourcing a repaired IMMFC03 for an outage spare?
Request exact identity, repair traceability, board-condition evidence, connector inspection, and a clear statement of the supplied hardware condition.
Which acceptance test gives the strongest evidence that IMMFC03 returned to service correctly?
Demonstrate node communication, expected slave visibility, representative analog and digital execution, alarm handling, and stable operation against the pre-outage baseline.