Interface ABB Bailey INFI 90 and NETWORK 90 DCS with OPC90 Server from RoviSys
Looking to interface ABB Bailey INFI 90 or NETWORK 90 systems to OPC-compatible systems in your operations? Man Machine Interface (MMI) solutions can only be as strong as their weakest link. The RoviSys OPC90 Server is designed to be one of the strongest links in that chain. OPC90 Server is an 
OPC 1.0a and 2.0 compliant server that easily enables data exchange between OPC clients and ABB Bailey Command Series / NETWORK 90 / INFI 90 systems. OPC90 Server runs in the Windows NT/2000/2000 Server/XP/Server 2003 environment.
OPC90 Server supports all the common exception report blocks, supervisory control of those blocks, system status monitoring including problem report collection, general block output polling, along with general purpose block configuration reading and tuning. All these features are incorporated in a fashion that is extremely easy to use, very intuitive and consistent with the ABB Bailey system.
Supported INFI 90 and NET 90 interfaces
Save Money By Sharing Existing CIU Hardware
OPC90 Server features include:
- Interfaces to Bailey Command Series, Network 90 and Infi 90 systems supporting communication with all CIU models.
- Three licenses are available:
Lite 250 blocks 2 clients,
Standard 5000 blocks 4 clients,
Unlimited supports all available CIU block indices and unlimited clients. - Compatible with all popular 3rd party MMI packages thus supporting replacement of Bailey OIU, MCS, OIS and PCView operator consoles.
- Use of the semAPI environment is not required.
- Automatic database shadowing for installations using redundant OPC90 servers.
- Save money by using the exclusive OPC90 MUXCIU block to allow a single Bailey interface to be safely shared between OPC90 and multiple Composer and CADEWS programming stations.
- Supports Windows NT/2000 Workstation/2000 Server/XP/Server 2003.
- Call for pricing on our cost-effective service that translates a Bailey MCS/OIS/PCView tag database to the OPC90 server format.
- Total freedom to install on any PC anytime using our parallel port or USB dongle (you are not tied to us with a software key activation system that is PC specific).
- Supports redundant interfaces or communication channels.
- Read and write access to all standard Bailey exception report types.
- Supports general configuration and tuning of any Bailey block specification including PID constants with automatic fast update of control output and process variable required by loop tuning software clients.
- System health monitoring includes both module status and module problem reports.
- General block output polling.
- System simulation makes client validation easy and convenient.
- Reading and writing of real time data values from within the OPC90 Server program window.
- Automatic support of different types of ABB Bailey interfaces.
- Automatic database recovery after an ABB Bailey interface reset.
- Simultaneous communication with multiple ABB Bailey interfaces.
- Adjustable driver communication parameters.
- ABB Bailey system time synchronization.
- Automatic blocking of illegal operator requests.
- Online tag additions and modifications.
- Alarm limit reading and writing as OPC tags.
- Can run as a service
Why Pick RoviSys:
- Excellent documentation.
- Extremely easy to install, setup and use.
- Very responsive lifetime technical support.
- Optional cost effective yearly software maintenance contract allowing anytime update to new releases. We don’t make you buy it if you don’t want it.
- In-house ABB Bailey system dedicated to ongoing software support and new feature development.
- Software developed by former ABB Bailey engineers involved with the original development of INFI 90, NETWORK 90 and Command Series.
Overview diagram of how OPC90 Server connects ABB Bailey systems
Replacement costs are lower than purchasing new Bailey consoles. Additional savings can be realized when replacing ABB Bailey 5000 tag OIU, MCS or OIS by re-using the CIU already built into these console types.
OPC90 Server supports the
following Bailey interfaces
| Interface | Max Number Of Bailey Blocks |
Exception Reporting | Control Operation |
| NSPM01 | 500 | No | No |
| IMSPM01 | 500 | No | No |
| IMCPM02 | 500 | No | No |
| IMCPM03 | 500 | Yes | Yes |
| NCIC01 | 500 | Yes | Yes |
| NCIU01 | 500 | Yes | Yes |
| NCIU02 | 2,500 | Yes | Yes |
| NCIU03 | 5,000 | Yes | Yes |
| NCIU04 | 10,000 | Yes | Yes |
| INPCI01 | 500 | Yes | Yes |
| INPCI02 | 5,000 | Yes | Yes |
| IIMCP02 | 10,000 | Yes | Yes |
| INICI01 | 10,000 | Yes | Yes |
| INICI12 | 10,000 | Yes | Yes |
| INICI03 | 30,000 | Yes | Yes |
| INICI13A | 30,000 | Yes | Yes |
Three OPC90 licenses are available:
Lite 250 blocks 2 clients,
Standard 5000 blocks 4 clients,
Unlimited supports all of the above listed CIU block indices and unlimited clients.
System Configuration for OPC90 Server
OPC90 Server is easily configured using its explorer like program window. No configuration changes are required within the ABB Bailey system. Devices are added which represent each ABB Bailey interface. Under each device point groups can be configured which provide data organization. Under each group, blocks are configured representing corresponding blocks within the ABB Bailey controller logic. These blocks contain the ABB Bailey address (ring, node, module, block) defining where the data is being sourced. This information is used by the OPC90 Server driver to efficiently establish the point values within the ABB Bailey interface and exchange the requested information.
The configuration information can be exported to a CSV file format for bulk editing and than re-imported. For large tag counts, the complete OPC90 Server database can be configured within a CSV file using a program such as Microsoft Excel or Access and than imported using the OPC90 Server import function. The format of the CSV file is simple and easily understood being fully documented within the OPC90 Server manual and help system. OPC90 Server supports the following Bailey block associations:
OPC90 |
ABB Bailey Block |
Function Code |
| AIL | Analog Output / Loop AOL | 30, 70, 158, 177 |
| AOL | Analog Input / Loop AIL | 26, 121 |
| BLK | General purpose |
ALL |
| DAANG | Data Acquisition Analog | 177 |
| DADIG | Data Acquisition Digital | 211 |
| DD | Device Driver | 123 |
| DIL | Digital Output / Loop DOL | 45 |
| DOL | Digital Input / Loop DIL | 42, 122 |
| DEVICE | Interface Definition and operational statistics | |
| HAI | Harmony Analog Input | 222 |
| HAO | Harmony Analog Output | 223 |
| HDI | Harmony Digital Input | 224 |
| HDO | Harmony Digital Output | 225 |
| MODSTAT | Any Bailey module | |
| MUXCIU | Allows OPC90 to safely share its CIU with DBDOC/WinCAD/Composer | ALL |
| MSDD | Multi-state Device Driver | 129 |
| ODD | Allows client to emulate operation of a device driver block (DD) |
(123) |
| OMSDD | Allows client to emulate operation of a multi-state device driver block (MSDD) | (129) |
| ORCM | Allows client to emulate operation of a remote control memory block (RCM) | (62) |
| ORMC | Allows client to emulate operation of a remote motor control block RMC | (136) |
| ORMSC | Allows client to emulate operation of a Remote Manual Set Constant block RMSC | (68) |
| OSTN | Allows client to emulate operation of a control station block STN | (21, 22, 23, 80) |
| POLL | Poll any block output | |
| RCM | Remote Control Memory | 62 |
| RMC | Remote Motor Control | 136 |
| RMSC | Remote Manual Set Constant | 68 |
| SOE | Sequence of Events | 99, 243 |
| SPEC | Predefined block specification reading and tuning | |
| STN | Station (PID Control loop) | 21, 22, 23, 80 |
| TXT | Text | 151 |
| TEXTSTR | ASCII String Block - TEXTSTR | 194 |
Try the free OPC90 Server Bailey interface demo Important! The demo version does not recognize a hardware key and therefore cannot be used to upgrade existing purchased software installations.
Download a training presentation on OPC90
Save Money By Sharing Existing CIU Hardware
OPC90 Server can be used to save substantial CIU hardware costs with its MUXCIU block. This block allows OPC90 to safely share its CIU with *DBDOC, WinCAD, or Composer software. It can be used with any software that does not need to establish points in the CIU database. The MUXCIU block makes any free COM port on the PC running OPC90 respond as if it's the actual CIU that OPC90 is communicating with. It supports COM port expansion cards and virtual COM port software. Setup is easy. Configure a MUXCIU block for each PC COM port you want to respond as a CIU. Attach the PC running DBDOC, WinCAD or Composer software to that port with a NULL modem serial cable. If your OPC client software does not already have OPC90 running, execute it manually or set it up to run as a service with the "Startup In Runtime" option enabled. Setup is complete and you have saved a ton of money by sharing existing CIU hardware!
* The GMCL company takes advantage of this great standard feature of OPC90 with their DBDOC software system. DBDOC allows safe view only real time access of ABB Bailey logic values by any plant personnel. RoviSys invites you to check out DBDOC at the GMCL website http://www.gmcl.com/index.jsp.