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

    Active / Available from OEM
    Apter Power reviews INICT13 suffix, INNIS21 pairing, host connection, and migration evidence before sourcing.

INICT13

/ 4.9
1001 reviews | Need a Specific Revision?
ABB INICT13 is documented for an INICT13-based ICI03 communication path that uses INNIS21 without a separate MPI module.
In Stock
Ships by Wednesday, October 28
Fast Shipping Available
Get a quick price for INICT13
Quantity
*E-mail
Company
*Mobile
*Content
Upload (gif, jpg, jpeg, png, bmp, doc, docx, xls, xlsx, ppt, pdf, csv)

Technical specifications for INICT13

  • Manufacturer:
    ABB
  • Part Number:
    INICT13
  • Product Family:
    ABB Bailey
  • Product Type:
    ICI03 Communication Transfer Module
  • Stock:
    1
  • ICI architecture:
    INICT13-based ICI03
  • Required network interface:
    INNIS21
  • MPI requirement:
    Separate MPI not required
  • Configuration boundary:
    Confirm base code versus INICT13A before application
  • Tariff Code:
    Please confirm the destination before shipping
  • 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 Specifications ICI03 Evolution Required Pairing Migration Checks

Features:

  • Simplified ICI path: The INICT13-based interface does not require a separate MPI.
  • Defined network pairing: ABB specifies INNIS21 for this architecture.
  • Suffix-sensitive migration: Base and INICT13A records require exact identification.
ABB INICT13 is most useful to engineers evaluating the hardware boundary of an ICI03 communication migration.

Its documented architecture removes one legacy interface layer, but that change also makes the surrounding INNIS hardware part of the selection decision.

A successful project distinguishes installed and evolution part codes before cabinet hardware or host configuration is changed.

Apter Power will review ABB INICT13 requests against the installed suffix, INNIS interface and existing ICI03 hardware path.
ABB INICT13 ICI03 Communication Transfer Module Manuals, Datasheets, Link Important Notice: Other accessories, manuals, cables, calibration data, software, etc. are not included with this equipment unless listed in the above stock item description. All prices are shown in USD.
ABB INICT13 ICI03 Communication Transfer Module Specs

General

  • Manufacturer ABB
  • Model INICT13
  • Condition New Original ready stock
  • Product Family Symphony Harmony / INFI 90
Important Notice: Other accessories, manuals, cables, calibration data, software, etc. are not included with this equipment unless listed in the above stock item description. All prices are shown in USD.

Legacy Interface Change:

  • Earlier path: INICT03A used a separate IMMPI01.
  • INICT13 path: The separate MPI is not required.
  • Migration target: ABB documentation lists a suffixed evolution part that must be checked against the base code.

Network Interface Dependency:

  • Specified interface: INNIS21.
  • Cabinet evidence: Confirm the installed network-interface nameplate.
  • Design control: Do not assume an older INNIS version remains acceptable.

Before Commissioning:

  • Part identity: Resolve base code, suffix and revision.
  • Host path: Document existing communication and configuration.
  • Acceptance: Test node visibility and point access after the hardware change.
Description
ABB evolution guidance places ABB INICT13 in an INICT13-based ICI03 communication interface. The documented architecture requires an INNIS21 network interface and removes the separate MPI used with the earlier INICT03A and IMMPI01 arrangement.

A project involving ABB INICT13 should distinguish the base code from the separately documented INICT13A evolution part before purchase or commissioning. Confirm the installed suffix, host connection, network interface and migration scope from the nameplate and cabinet drawings instead of treating the two codes as automatically interchangeable.
Alternative Names
ABB INICT13 ICI03 Transfer Module Bailey ICT13 Communication Interface Symphony Harmony ICI Communication Board INFI-NET Host Interface Module
Technical notes
Plan ABB INICT13 around the documented ICI03 architecture: ABB specifies INNIS21 and states that an MPI is not required. Do not treat the base code as interchangeable with a suffixed evolution part; verify the installed suffix, network interface, host connection and migration scope before ordering or commissioning.
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.
Does an INICT13-based ICI03 require a separate MPI module?
ABB states that the INICT13-based arrangement does not require the MPI used by the earlier INICT03A and IMMPI01 interface.
Which network interface is required with INICT13?
ABB evolution guidance specifies INNIS21 for the INICT13-based ICI03 path; do not retain an older interface without an approved migration design.
Can INICT13 be ordered as a direct substitute for the suffixed evolution part?
Not without confirmation. ABB lists INICT13A as an evolution part, while the explanatory note uses the base code; verify the complete installed identification.
What changes when an older ICI03 is migrated to INICT13?
The documented path removes the separate MPI and requires INNIS21, so the migration scope must include interface hardware, host connectivity, configuration and acceptance testing.
Why is the cabinet drawing important for INICT13 selection?
It shows whether the interface is an INICT13-based ICI03, which network interface is installed and whether legacy MPI hardware remains in the path.
What should be validated after installing INICT13?
Confirm host communication, network-node visibility, configured point access, interface diagnostics and the absence of unintended dependency on the removed MPI layer.
What evidence should accompany an INICT13 quotation request?
Provide complete nameplates, suffix and revision, INNIS model, host-interface details, existing MPI status, cabinet photos, quantity and destination.

Product Browsing History