I/A Series® System

I/A Series®
Configuration
Component (IACC)
User’s Guide

B0700FE

Rev A
August 30, 2012
Invensys, AIM*Historian, Foxboro, FoxDraw, FoxView, I/A Series, INTERSPEC, the Invensys logo, and
Micro-I/A are trademarks of Invensys plc, its subsidiaries, and affiliates.
All other brand names may be trademarks of their respective owners.

Copyright 2012 Invensys Systems, Inc.

All rights reserved

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Invensys Systems, Inc. supplied software supported by this documentation, you
should read and understand the following information concerning copyrighted software.
1. The license provisions in the software license for your system govern your obligations
and usage rights to the software described in this documentation. If any portion of
those license provisions is violated, Invensys Systems, Inc. will no longer provide you
with support services and assumes no further responsibilities for your system or its
operation.
2. All software issued by Invensys Systems, Inc. and copies of the software that you are
specifically permitted to make, are protected in accordance with Federal copyright
laws. It is illegal to make copies of any software media provided to you by
Invensys Systems, Inc. for any purpose other than those purposes mentioned in the
software license.
Contents
Figures................................................................................................................................... xv

Tables................................................................................................................................. xxiii

Preface................................................................................................................................. xxv
Audience ................................................................................................................................ xxv
What You Should Know ........................................................................................................ xxv
Revision Information ............................................................................................................. xxv
Foundation fieldbus Support .................................................................................................. xxv
Reference Documents ........................................................................................................... xxvi
Document Overview ............................................................................................................. xxvi
Request for Comments ........................................................................................................ xxviii

1. Overview ........................................................................................................................... 1
IACC and Legacy Configurators ............................................................................................... 5
Control Strategy Engineering .................................................................................................... 6
Compounds ......................................................................................................................... 6
Control Strategy Diagrams ................................................................................................... 7
Control Blocks ..................................................................................................................... 7
Block Connections ............................................................................................................... 8
Naming Conventions ........................................................................................................... 8
Assigning or Unassigning Blocks and Compounds ............................................................... 9
Deleting and Unassigning IACC Objects ............................................................................. 9
Control Language ............................................................................................................... 10
Structured Text Code .................................................................................................... 10
Structured Text Templates ............................................................................................ 10
Ladder Logic Editor ....................................................................................................... 10
Downloading Blocks and Compounds ............................................................................... 10
Documentation and Printing .................................................................................................. 11
Utilities ................................................................................................................................... 11
Properties ........................................................................................................................... 11
ListViews ............................................................................................................................ 11
Palettes ............................................................................................................................... 11
Find in Database and Where Used ..................................................................................... 12
Import and Export Databases ............................................................................................. 12
Database Backup and Restoration ...................................................................................... 12
Software Packages ................................................................................................................... 12

iii
B0700FE – Rev A Contents

2. IACC Window ................................................................................................................ 13

Starting IACC ......................................................................................................................... 13
IACC Window Overview ........................................................................................................ 16
Title Bar, Menus and Toolbar ............................................................................................ 18
Project Navigator ............................................................................................................... 18
System Tab .................................................................................................................... 19
Network Tab ................................................................................................................. 20
Plant Tab ...................................................................................................................... 21
Selecting a Menu ................................................................................................................ 21
Dialog Boxes ...................................................................................................................... 22
Messages and Warnings ...................................................................................................... 22
The IACC Editors ................................................................................................................... 23
Process Control Editors/Dialog Boxes ................................................................................ 23
CSD Editor ................................................................................................................... 24
CSD Templates ............................................................................................................. 26
TagList Editor ............................................................................................................... 26
Configuring Sequential Control .................................................................................... 27
SFC Editor .................................................................................................................... 27
Structured Text Code Editor ......................................................................................... 27
ST Template Editor ....................................................................................................... 28
Ladder Logic Editor ....................................................................................................... 30
Execution Editor ........................................................................................................... 31
Control Station Loading ................................................................................................ 32
Control Hierarchy Validation and Download ................................................................ 33
Compare to a CP ........................................................................................................... 33
Synch Utility ................................................................................................................. 35
Properties Dialog Box .................................................................................................... 36
System Configuration Editors ............................................................................................ 36
Hardware Editor ............................................................................................................ 36
Software Editor .............................................................................................................. 37
Parameter Editor ........................................................................................................... 38
ListView Editor .................................................................................................................. 38
Customization Editors/Dialog Boxes .................................................................................. 40
Definition Editor ........................................................................................................... 40
Connection Dialog Box ................................................................................................. 42
Appearance Object Editor ............................................................................................. 43
Report Template Editor ................................................................................................ 43
Sheet Editor ................................................................................................................... 45
Toolbars Dialog Box ...................................................................................................... 46
Security Editors ............................................................................................................. 46
FoxDraw Software and Custom Display Files ..................................................................... 48
Utilities and Compilers ........................................................................................................... 49
Using On-Line Help ............................................................................................................... 50
Setting IACC Options ............................................................................................................ 50
Enable System-Wide Security ............................................................................................. 52
Configure Security Audit Trail ........................................................................................... 52

iv
Contents B0700FE – Rev A

Disable Checkpointing for Control Downloads ................................................................. 53

Track Configuration Changes for 21 CFR Part 11 ............................................................. 54
FSIM (Foxboro Simulation) Support ................................................................................. 54
Configure Error Reporting ................................................................................................. 54
Change Project Navigator Display Characteristics .............................................................. 57
Set the Where Used Display Option .................................................................................. 59
Property Page Settings ........................................................................................................ 59
Live Data Settings .............................................................................................................. 60

3. Using IACC .................................................................................................................... 63

Getting Started Sequence ........................................................................................................ 63
Control and System Configuration ......................................................................................... 64
Defining Plant Areas .......................................................................................................... 64
Creating a Compound for Blocks ....................................................................................... 65
Creating a CSD for Blocks ................................................................................................. 66
Creating I/A Series Control Blocks ..................................................................................... 66
Connecting Blocks ............................................................................................................. 68
Creating Hardware and Software Objects ........................................................................... 70
Creating a Station and Control Processor ...................................................................... 70
Creating Peripherals ...................................................................................................... 72
Creating Software .......................................................................................................... 72
Checking and Adding Parameters .................................................................................. 73
Selecting FBMs .............................................................................................................. 75
Validating the System Configuration .................................................................................. 76
Creating a Commit Diskette .............................................................................................. 77
Assigning CSDs and Compounds ....................................................................................... 77
Assigning ECBs to a CSD .................................................................................................. 79
Adding ECBs to a CSD ................................................................................................. 79
Associating FBM Points with CSD Blocks .................................................................... 80
Building Displays ............................................................................................................... 81
Block and Compound Execution ....................................................................................... 81
Block Sequencing .......................................................................................................... 81
Compound Sequencing ................................................................................................. 82
Downloading the Database ..................................................................................................... 82
Downloading an Entire Database to a Control Processor ................................................... 82
Checkpointing the CP ........................................................................................................ 83
Comparing Blocks in the CP to the IACC Database .......................................................... 83
Printing and Documentation .................................................................................................. 84
Importing/Exporting the Configuration Database ................................................................... 84
Protecting the Database ........................................................................................................... 85
Backing Up the Database ................................................................................................... 85

4. System Configuration...................................................................................................... 87
Planning .................................................................................................................................. 88
Security Configuration ....................................................................................................... 88
System and Control Configuration ..................................................................................... 88

v
B0700FE – Rev A Contents

Overview of System Configuration ..................................................................................... 89

Importing System Definition Data .......................................................................................... 91
Creating an I/A Series V8.x System ......................................................................................... 95
Adding Stations to The Mesh ............................................................................................. 97
Adding Fieldbus Modules to an I/A Series V8.x System ..................................................... 99
Creating a Network/LAN ..................................................................................................... 100
Procedures for Creating Networks .................................................................................... 100
Network Equipment ............................................................................................................. 101
Creating Network Components ....................................................................................... 101
Creating a Node from a Network Component ............................................................ 102
Creating a Node Without a LAN ................................................................................ 102
Creating an Ethernet Nodebus .................................................................................... 103
Configuring an ATS .............................................................................................................. 103
LI Replacement Mode ...................................................................................................... 103
Nodebus Extender Mode .................................................................................................. 104
Creating Stations and Processors ........................................................................................... 104
Procedures for Creating Stations ...................................................................................... 105
Creating a Station and CP from the Configuration Branch ......................................... 105
Creating a Station and Control Processor from a Nodebus .......................................... 107
Selecting Peripherals .............................................................................................................. 107
Configuring Communications Interface Devices ................................................................... 109
Creating Unassigned Comm Devices ............................................................................... 111
Creating FBIs from the CP40B ........................................................................................ 111
Creating FBI10s and FCM10s from a CP60 .................................................................... 111
Creating FCM2s from a Fieldbus Communications Module ............................................ 113
Adding Fieldbus Modules ..................................................................................................... 113
268Kbps Fieldbus Modules .............................................................................................. 114
Creating 268Kbps FBMs from the Configuration Branch ........................................... 115
Adding FBMs to a CP40B ........................................................................................... 116
Creating FBMs from the Fieldbus Isolator ................................................................... 116
Creating 268Kbps FBMs for a CP60 ........................................................................... 117
Expansion FBMs .............................................................................................................. 117
2Mbps Fieldbus Modules ................................................................................................. 119
DIN Rail Mounted FBMs ........................................................................................... 120
Adding DIN Rail Mounted FBMs for a CP60 or ZCP270 .......................................... 121
Adding DIN Rail Mounted FBMs for an FCP270 ...................................................... 122
Configuring Field Devices ........................................................................................... 122
Adding Migration FBMs ............................................................................................. 124
Creating Software Objects ..................................................................................................... 125
Changing FBM Software .................................................................................................. 127
Assigning Hardware Objects ................................................................................................. 127
Considerations for Assigning Hardware Objects ............................................................... 127
Assigning Hardware Objects ............................................................................................. 128
Assigning a Network Component ................................................................................ 128
Assigning Peripherals ................................................................................................... 129

vi
Contents B0700FE – Rev A

Assigning FBMs and Interface Modules ....................................................................... 129

Assigning Software Hosts from the Hardware Editor ............................................................ 131
Assigning Hosts from the Project Navigator ..................................................................... 131
Committing the Configuration ............................................................................................. 132
Validating a Configuration ............................................................................................... 133
Creating a Commit Diskette ............................................................................................ 134
System Installation and Reconciliation .................................................................................. 138
Updating Installation Status in IACC .............................................................................. 138
Reviewing the Software .................................................................................................... 139
Floppy Dependency Removal ........................................................................................... 140

5. Control Configuration .................................................................................................. 143

Compounds, Parameters, and Blocks .................................................................................... 144
Compounds ..................................................................................................................... 144
Parameters ........................................................................................................................ 145
Blocks ............................................................................................................................... 145
Block Parameters ......................................................................................................... 145
Editing Parameters ...................................................................................................... 145
Block Function Types .................................................................................................. 145
Setting Up CSDs .................................................................................................................. 146
Plant Areas ....................................................................................................................... 147
Creating a Simple CSD .................................................................................................... 148
Creating a CSD from a Template ..................................................................................... 149
Converting a CSD Instance ......................................................................................... 151
Converting a CSD Template to a Simple CSD ................................................................ 152
Renaming a CSD ............................................................................................................. 153
Deleting a CSD ................................................................................................................ 154
Setting Up CSD Templates ................................................................................................... 155
Creating a CSD Template ................................................................................................ 155
Converting a CSD to a Template ..................................................................................... 155
Editing CSDs and CSD Templates ....................................................................................... 158
Editing a CSD .................................................................................................................. 158
Opening the CSD Editor ................................................................................................. 159
Adding Blocks to a CSD .................................................................................................. 159
Deleting Blocks from a CSD ............................................................................................ 159
Moving and Placing Blocks on a CSD .............................................................................. 160
Resizing Areas on the Block Appearance Object ............................................................... 161
Assigning Blocks to Compounds ...................................................................................... 161
Creating a Compound ................................................................................................. 161
Assigning Individual Blocks ......................................................................................... 162
Assigning CSDs ........................................................................................................... 163
Bulk Assignments from a ListView .............................................................................. 163
Unassigning Blocks from Compounds ......................................................................... 163
Assigning Compounds to a CP ......................................................................................... 164
Assigning CSDs to a Plant Area ........................................................................................ 165
Making Connections ........................................................................................................ 165

vii
B0700FE – Rev A Contents

Making Off-Sheet Connections ................................................................................... 167

Showing Parameters .................................................................................................... 170
Removing Parameters .................................................................................................. 171
Deleting Connections .................................................................................................. 171
Hiding and Showing Connections ............................................................................... 171
Modifying Connection Lines ....................................................................................... 171
Adding Graphical Objects to a CSD ............................................................................ 174
Connecting I/O Blocks to the Field .................................................................................. 174
Adding ECBs to a CSD ............................................................................................... 174
Adding ECB Placeholders to a CSD Template ............................................................ 176

6. Modifying Compounds and Blocks ............................................................................... 177

Properties Dialog Box ........................................................................................................... 178
Adding a Formula to a Parameter Value Attribute ............................................................ 180
Editing Logic Block Properties ......................................................................................... 181
Derived Block Definitions ..................................................................................................... 183
Execution Editor ................................................................................................................... 186
Block and Compound Processing .......................................................................................... 188
Block Phasing ........................................................................................................................ 190
Relationship Between Block Period and Phase .................................................................. 190
Overruns .......................................................................................................................... 192
Block Phasing: Cautions and Guidelines .......................................................................... 192
Compound Phasing ..................................................................................................... 192
Control Block Phasing ................................................................................................. 193
Block Execution Order .......................................................................................................... 193
Modifiers .............................................................................................................................. 194
Creating an IA Modifier ................................................................................................... 196
Applying an IA Modifier .................................................................................................. 199
IA Mod Traverse Blocks ................................................................................................... 201
IA Mod Traverse CSDs and Blocks .................................................................................. 202

7. Sequence Blocks ............................................................................................................ 203

Creating a Sequence Block Instance ...................................................................................... 204
Using FoxSFC ....................................................................................................................... 204
Creating HLBL Code ............................................................................................................ 205
Opening the ST Code Editor for a Sequence Block .......................................................... 206
Inserting an ST Template Using the Instance Wizard ...................................................... 207
Modifying a Template Reference ...................................................................................... 209
Expanding and Collapsing an ST Template Reference ..................................................... 209
Converting an ST Template Reference to HLBL Code .................................................... 210
Deleting ST Template Reference ...................................................................................... 210
Creating and Editing Text Objects ........................................................................................ 210
Creating Text Objects ...................................................................................................... 210
ST Templates ........................................................................................................................ 211

viii
Contents B0700FE – Rev A

Creating an ST Template ................................................................................................. 212

Modifying an ST Template .............................................................................................. 213
Setting the ST Template Properties ............................................................................. 213
Creating ST Code Items .............................................................................................. 214
Creating ST Decisions ................................................................................................. 215
Connecting Objects in the ST Template Editor .......................................................... 219
Validating the Template .............................................................................................. 223
Deleting an ST Template ................................................................................................. 224
Locating an ST Code Item or Decision Point ................................................................... 224
ST Code Items ...................................................................................................................... 225
Opening the ST Code Editor for an ST Code Item .......................................................... 225
Inserting Substitution Questions ...................................................................................... 225
Saving and Re-Using HLBL Code ........................................................................................ 229
Compiling the HLBL Code .................................................................................................. 229
Bulk HLBL Compiler ...................................................................................................... 230

8. Ladder Logic.................................................................................................................. 233

Creating a Simple Ladder ...................................................................................................... 233
Editing a Ladder Program ..................................................................................................... 234
Rungs and Rows ................................................................................................................... 235
Rung Comments .............................................................................................................. 236
Logic Elements ...................................................................................................................... 237
Adding Elements .............................................................................................................. 237
Assigning Technical Identifiers ......................................................................................... 237
Adding and Deleting Connections ................................................................................... 238
Importing an I/A Series Ladder Configuration ................................................................. 240
Assigning a Ladder to a PLB .................................................................................................. 241
Implementation .................................................................................................................... 242
Validating the Ladder ....................................................................................................... 242
Compiling the Ladder ...................................................................................................... 244
Downloading the Ladder .................................................................................................. 244

9. TagLists and Bulk Generation....................................................................................... 245

Custom Tag Types ........................................................................................................... 247
Bulk Generation ............................................................................................................... 247
TagLists ................................................................................................................................ 247
Creating a TagList ............................................................................................................ 247
Deleting a TagList ............................................................................................................ 248
Editing a TagList .............................................................................................................. 248
Colors and Symbols Appearing in TagList Editor ........................................................ 249
Menus and Toolbars .................................................................................................... 249
TagList Editor Pop-Up Menus .................................................................................... 251
Tags ...................................................................................................................................... 252
Creating a New Tag ......................................................................................................... 252

ix
B0700FE – Rev A Contents

Deleting a Tag .................................................................................................................. 253

Editing a Tag ................................................................................................................... 253
Creating a Custom Tag Type ................................................................................................ 256
Importing TagLists ............................................................................................................... 258
Defining Tags .................................................................................................................. 260
Mapping Fields ................................................................................................................ 262
Selecting Tags ................................................................................................................... 264
Exporting TagLists ................................................................................................................ 267
Bulk Generation of CSDs ..................................................................................................... 272
Block Parameter Propagation ................................................................................................ 276
Showing Parameters for Tag Propagation ......................................................................... 278

10. Creating Displays ........................................................................................................ 281

FoxDraw Displays ............................................................................................................ 281
Library Objects ................................................................................................................. 281
Interface with the FoxDraw Application ............................................................................... 282
Displays ................................................................................................................................ 283
Display Templates ................................................................................................................. 284
Synchronizing Displays and IACC ........................................................................................ 284
Synchronizing Changes Done Within Display Files ......................................................... 284
Synchronizing Changes Done Within IACC .................................................................... 284
Creating a Display ................................................................................................................. 285
Adding a Display File to a Plant Area ............................................................................... 285
Adding a Display File from the System Tab ..................................................................... 285
Renaming a Display File Object ....................................................................................... 286
Assigning a Display File to a Plant Area ............................................................................ 286
Creating a Drawing ............................................................................................................... 287
Dragging Blocks to a FoxDraw Display ............................................................................ 287
Selecting Default Objects ................................................................................................. 289
Creating a Drawing File for a CSD .................................................................................. 291
Resolving FoxDraw Symbol Aliases ............................................................................. 294
Saving the Drawing File ................................................................................................... 295
Managing Display Files ......................................................................................................... 296
Deleting a Display File ..................................................................................................... 296
Assigning Displays to Workstations .................................................................................. 296
Validating Displays .......................................................................................................... 297
Downloading Displays ..................................................................................................... 298
Importing Displays ........................................................................................................... 300
ListViews, Properties, and Where Used ............................................................................ 303

11. Downloading Control Blocks ...................................................................................... 305

Enabling IACC Downloads to a Control Station .................................................................. 307
Control Hierarchy Validation ............................................................................................... 310

x
Contents B0700FE – Rev A

What Validation Checks are Performed ............................................................................ 310

Results of a Validation ...................................................................................................... 311
Summary of Checks Performed at Each Object Level ....................................................... 311
Downloading Compounds and Blocks .................................................................................. 312
Control Hierarchy Validation ........................................................................................... 314
Performing a Download ................................................................................................... 316
Downloading a Compound ......................................................................................... 316
Downloading from a Plant Area .................................................................................. 317
Downloading from a CSD or CSD Template .................................................................. 322
FoxCTS Change Tracking .................................................................................................... 322
Directory for Download Event Files ................................................................................. 323
Verifying the System Monitor Configuration ................................................................... 323
Enabling FoxCTS Integration .......................................................................................... 324
Authorizing User Access ................................................................................................... 324
Starting FoxCTS .............................................................................................................. 325
Shrink Command ................................................................................................................. 325
CP Checkpointing ................................................................................................................ 325
Quick View ........................................................................................................................... 327
Animated Loop Drawings ..................................................................................................... 329
FoxAPI/AIM*API Server Setup ........................................................................................ 331
Setting ALD Options ....................................................................................................... 333
ALD Sessions ............................................................................................................... 334
Viewing Block Status ............................................................................................................ 337
Remove from CP .................................................................................................................. 339
Synch Utility ......................................................................................................................... 340
Comparing to CP .................................................................................................................. 343
Upload and Compare ....................................................................................................... 343
Comparing Parameters ..................................................................................................... 343
DB and CP .................................................................................................................. 345
CP ONLY ................................................................................................................... 345
DB ONLY ................................................................................................................... 345
Bulk Upload ..................................................................................................................... 346
Initialize CP .......................................................................................................................... 347

12. Security ....................................................................................................................... 349

Configuring Security ............................................................................................................. 350
Initial Security Configuration ........................................................................................... 350
Limiting Access ................................................................................................................ 351
User Editor ........................................................................................................................... 351
Menus and Toolbars ......................................................................................................... 352
Configuring Users ............................................................................................................ 352
Adding and Naming a User ......................................................................................... 352
Removing a User ......................................................................................................... 353
Configuring a User ...................................................................................................... 353

xi
B0700FE – Rev A Contents

Group Editor ........................................................................................................................ 354

Adding and Naming a Group ........................................................................................... 355
Deleting a Group ............................................................................................................. 356
Configuring a Group ........................................................................................................ 356
Permitting Access to System-Wide Functions .............................................................. 356
Assigning IACC Object-Type Permissions .................................................................. 357
Enabling Security .................................................................................................................. 359
Security-Related ListViews .................................................................................................... 360
Security Audit Trail ............................................................................................................... 360

13. Printing and Reports ................................................................................................... 363

Printing ................................................................................................................................. 363
Printing an Object Report ................................................................................................ 363
Printing Editor Contents .................................................................................................. 365
Printing to a File .............................................................................................................. 365
Print Preview Mode .......................................................................................................... 365
Sheet Templates .................................................................................................................... 366
Basic Sheet Template Specifications ................................................................................. 366
Default Sheet Templates .............................................................................................. 366
Sheet Template Macros ............................................................................................... 366
Creating a Sheet Template ............................................................................................... 366
Editing the Sheet Template .............................................................................................. 367
Inserting a Macro ........................................................................................................ 369
Reports .................................................................................................................................. 370
Reports for One Object .................................................................................................... 370
Reports for More than One Object .................................................................................. 370
Report Templates ............................................................................................................. 371
Report Template Classes .............................................................................................. 371
Report Template Definitions ....................................................................................... 373
Report Template Instances .......................................................................................... 373
Creating a Report Template ............................................................................................. 373
Adding Scope Nodes ................................................................................................... 374
Adding a Plant Area Scope Node ................................................................................. 375
Removing a Scope Node .............................................................................................. 375
Report Template Object List Dialog Box .................................................................... 375
Using Filters ................................................................................................................ 376
Building a Filter Expression ......................................................................................... 378
State Tab ..................................................................................................................... 380
Type Tab ..................................................................................................................... 381
Category Tab ............................................................................................................... 382
Parenthesis Tab ........................................................................................................... 383

14. 100 Series Migration ................................................................................................... 385

Before You Begin ............................................................................................................. 385
FBM Level Migration ....................................................................................................... 386
CP270 (FCP/ZCP) Level Migration ................................................................................ 387

xii
Contents B0700FE – Rev A

FCM Level Migration ...................................................................................................... 391

Migration Tab .................................................................................................................. 393

15. Managing IACC Databases ......................................................................................... 395

Guidelines for Managing IACC Databases ....................................................................... 396
Setting Up Multiple Databases .............................................................................................. 396
Protecting Multiple Databases .......................................................................................... 400
Export Functions .................................................................................................................. 401
Exporting to an IACC Format File ................................................................................... 401
Exporting Save/SaveAll Data ............................................................................................ 403
ArchExport.exe IACC Utility for IEE Import Support ..................................................... 405
Import Functions .................................................................................................................. 405
Import Formats ................................................................................................................ 405
IACC Import ................................................................................................................... 406
Importing Save/SaveAll Data ............................................................................................ 412
After Importing from a SaveAll ........................................................................................ 417
Dealing with Compounds and Blocks Already in the CP ............................................. 417
Dealing with the Imported Compounds and CSDs ..................................................... 418
Backing Up and Restoring the Database ............................................................................... 419
Backing Up a Database ..................................................................................................... 419
Restoring a Database ........................................................................................................ 421
Verifying a Database ......................................................................................................... 424

Appendix A. Glossary ........................................................................................................ 427

Appendix B. Flow chart for Converting ICC SaveAll Diskette to IACC Database Format 435

Appendix C. Executing the IACC Utility ArchExport.exe ................................................. 437

Appendix D. 100 Series Migration Support ...................................................................... 439

Equipment Control Block Migration Supported By IACC ............................................... 439
Legacy CP/CP270 Configuration Migration (Import) ..................................................... 440
..............................Multiple Legacy CP30/40/60 Combined into CP270 (FCP/ZCP) 440
Single Legacy CP's 30AB/40AB/60 to FCP270/ZCP270 ............................................ 440
100 Series FBMs in FCP270 to 200 Series FBMs in CP270 ........................................ 441
100 Series FBMs in ZCP270 to 200 Series FBMs in ZCP270 ..................................... 441

Appendix E. IACC 2.5 Enhancements............................................................................... 443

Configuration and New Station Types supported by IACC 2.5 ............................................ 443
Packages Supported by IACC 2.5 ..................................................................................... 443
Support for Serial or Parallel port peripherals .............................................................. 444
Support for Network Printers ...................................................................................... 444
Support for USB Printers ............................................................................................ 445

xiii
B0700FE – Rev A Contents

Index .................................................................................................................................. 447

xiv
Figures
1-1. Building an IACC Control Strategy Diagram ............................................................... 1
1-2. Components Configured in IACC ................................................................................ 3
1-3. Configuration Options for IACC in a Mixed I/A Series Network ................................. 4
1-4. IACC Implementation on The Mesh Control Network ................................................ 4
1-5. Compound and Block Relationships ............................................................................. 6
1-6. IACC Control Strategy Diagram ................................................................................... 7
2-1. Windows Start Menu with IACC ............................................................................... 13
2-2. IACC Databases Dialog Box ....................................................................................... 14
2-3. Logon Dialog Box ....................................................................................................... 14
2-4. IACC Windows and Menu Bars ................................................................................. 16
2-5. Network Tab .............................................................................................................. 20
2-6. Plant Tab .................................................................................................................... 21
2-7. Plant Tab Pop-Up Menus ........................................................................................... 22
2-8. Control Strategy Diagram Editor ................................................................................ 24
2-9. Live Values Displayed in a CSD .................................................................................. 25
2-10. TagList Editor ............................................................................................................. 26
2-11. ST Code Editor ........................................................................................................... 28
2-12. ST Template Editor .................................................................................................... 29
2-13. IACC Ladder Logic ..................................................................................................... 30
2-14. Execution Editor Opened for a Compound ................................................................ 31
2-15. Control Station Loading Dialog Box ........................................................................... 32
2-16. Comparison Utility Page ............................................................................................. 34
2-17. Bulk Upload Page ....................................................................................................... 34
2-18. Synch Status Page ....................................................................................................... 35
2-19. Properties Dialog Box for an AIN Block ..................................................................... 36
2-20. Hardware Editor ......................................................................................................... 37
2-21. Software Editor ........................................................................................................... 37
2-22. Parameter Editor ......................................................................................................... 38
2-23. ListView Editor ........................................................................................................... 39
2-24. Definition Editor ........................................................................................................ 41
2-25. Connection Dialog Box .............................................................................................. 42
2-26. Appearance Object Editor and Select Parameters Dialog Box ...................................... 43
2-27. Report Template Editor Window ............................................................................... 44
2-28. Sheet Editor ................................................................................................................ 45
2-29. Typical Toolbar Dialog Box ........................................................................................ 46
2-30. User Editor ................................................................................................................. 46
2-31. Group Editor .............................................................................................................. 47
2-32. Permissions Window ................................................................................................... 47
2-33. IACC Options Dialog Box .......................................................................................... 51
2-34. IACC Options Dialog Box: Error Reporting Tab ........................................................ 55
2-35. IACC Options Dialog Box: Miscellaneous Tab ........................................................... 57
2-36. Object Type Displayed (left) and Object Description Displayed (right) ...................... 58
2-37. Plant Tab with Sorting Enabled (left) and Sorting Disabled (right) ............................. 59
2-38. Descriptive Text Added to Properties Dialog Box ....................................................... 60

xv
B0700FE – Rev A Figures

2-39. Confirming a Live Data Connection ........................................................................... 61

3-1. Plant Area Objects ...................................................................................................... 65
3-2. Compound and CSD added to a Plant Area Object .................................................... 66
3-3. Blocks Added to Simple CSD1 ................................................................................... 67
3-4. PIDA Appearance Object ............................................................................................ 67
3-5. Sample CSD with Three Connected Blocks ................................................................ 68
3-6. Select Parameters Dialog Box ...................................................................................... 69
3-7. Configuration Object in the Network Tab .................................................................. 70
3-8. Software for the Configured Workstation and the CP ................................................. 71
3-9. Parameter Editor Opened for AW70AA ...................................................................... 73
3-10. References Tab in the Parameter Editor for AW70AA ................................................. 74
3-11. Network Tree .............................................................................................................. 75
3-12. Validation Dialog Box and Output Window with Related Tab ................................... 76
3-13. Display of CSD and Compound Assignments in the Project Navigator ...................... 78
3-14. Adding ECBs to a CSD ............................................................................................... 79
3-15. Simple CSD Showing ECB Input/Output Points Connected to Blocks ...................... 80
3-16. Block Level Execution Editor ...................................................................................... 81
3-17. IACC Database Administration Dialog Box ................................................................ 85
4-1. Hardware in a Sample I/A Series System ..................................................................... 90
4-2. Selecting a SysDEF Diskette in the Available Formats Dialog Box .............................. 92
4-3. Select Drive Dialog Box for a SysDEF Export File ...................................................... 93
4-4. Verify Dialog Box ....................................................................................................... 93
4-5. SysDEF Import Log Tab in the Output Window ....................................................... 94
4-6. Create Networks Dialog Box Selected from the Configuration Object ........................ 95
4-7. Adding Switches to the Network ................................................................................. 96
4-8. Create Stations Dialog Box Selected from a Switch ..................................................... 97
4-9. Stations Added to an 8-Port Switch ............................................................................. 99
4-10. Create Networks Dialog Box ..................................................................................... 101
4-11. Create Switches/Hubs Dialog Box ............................................................................. 102
4-12. Configurable Stations and Processors ........................................................................ 105
4-13. Stations, Peripherals and Software for AW70 and CP40B - From Configuration ...... 106
4-14. Stations and Software for a CP40B ........................................................................... 107
4-15. Peripherals ListView and Create Peripherals Dialog Box ........................................... 108
4-16. Additional Peripherals ............................................................................................... 108
4-17. Create FB Comm/Isolators Dialog Box ..................................................................... 110
4-18. Adding Communication Interface Devices for a CP60 .............................................. 112
4-19. FCM10 Attached to a CP60 ..................................................................................... 113
4-20. Create 268Kbps Fieldbus Modules Dialog Box ......................................................... 116
4-21. Create Expansion Modules Dialog Box ..................................................................... 118
4-22. Project Navigator Display of an FBM with Expansion Module ................................. 119
4-23. Create 2Mbps Fieldbus Modules Dialog Box ............................................................ 120
4-24. Dialog Boxes for Selecting Device Types ................................................................... 123
4-25. Selecting FBMs for a WPDF Replacement I/O Module ............................................ 124
4-26. FBMs Configured for a WPDF Replacement Module ............................................... 125
4-27. Create Software Dialog Boxes for an AW70 .............................................................. 126
4-28. Optional Software Packages ...................................................................................... 126
4-29. Optional Software for an FBM217 ............................................................................ 127
4-30. Parented Nodebus ..................................................................................................... 128

xvi
Figures B0700FE – Rev A

4-31. Typical Hardware Editor for Field Devices - Parent Assignment for an FBM ............ 130
4-32. Typical Hardware Editor for an Entire System - Parent Assignment for Stations ....... 130
4-33. Assigning a Software Host Using the Hardware Editor ............................................. 131
4-34. Assign Host Dialog Box ............................................................................................ 132
4-35. Validate Hardware/Software Configuration Dialog Box ............................................ 133
4-36. Typical Output Window for Validation .................................................................... 134
4-37. Commit Hardware/Software Configuration Dialog Box ........................................... 135
4-38. Validation Checks Dialog Box .................................................................................. 135
4-39. Hardware/Software Commit Dialog Box .................................................................. 136
4-40. Package Distribution/Media Distribution Dialog Box ............................................... 136
4-41. Prompt to Insert Disk ............................................................................................... 137
4-42. Prompt for Another Diskette .................................................................................... 138
4-43. Insert Reconcile Diskette ........................................................................................... 138
4-44. Software Editor Selected for an AW70 ...................................................................... 139
4-45. Floppy Dependency Removal .................................................................................... 141
5-1. Creating a Plant Area from an Existing Plant Area .................................................... 147
5-2. Creating a Simple CSD ............................................................................................. 148
5-3. Bulk Generating CSDs from a Plant Area ................................................................. 149
5-4. Bulk Generate Dialog Box for Assigning Field Signals ............................................... 150
5-5. Confirming a CSD Conversion ................................................................................. 151
5-6. List of Instances for a CSD Template ........................................................................ 152
5-7. Delete Request Dialog Box ........................................................................................ 154
5-8. Converting a CSD to a Template .............................................................................. 156
5-9. Converting a CSD to a Template .............................................................................. 157
5-10. IACC CSD Editor .................................................................................................... 158
5-11. Block Appearance Object Selected for Relocation ..................................................... 160
5-12. Nudge Buttons in the CSD Editor Toolbar .............................................................. 160
5-13. Resizable Block Appearance Object Areas .................................................................. 161
5-14. AIN Block Before and After Assignment to a Compound ......................................... 162
5-15. Assign Compound To Control Station Dialog Box with Filtering Tool .................... 164
5-16. Address Versus Value Propagation Connection ......................................................... 166
5-17. Connection Dialog Box for an AOUT Block ............................................................ 166
5-18. Add Connection Dialog Box ..................................................................................... 167
5-19. Select Connection Parameter Dialog Box: Sink Parameter ........................................ 168
5-20. Select Object Dialog Box: Source Object .................................................................. 169
5-21. Select Object Parameter Dialog Box: Source Parameter ............................................. 169
5-22. Select Parameters Dialog Box .................................................................................... 170
5-23. Default Block Connections Lines .............................................................................. 172
5-24. Default Block Connections Lines .............................................................................. 172
5-25. Properties Dialog Box for a Connection Line ............................................................ 173
5-26. Reshaping an Orthogonal Line .................................................................................. 173
5-27. Adding an ECB to a CSD ......................................................................................... 175
5-28. Adding and Connecting an ECB Placeholder ............................................................ 176
6-1. Example of Properties Dialog Box ............................................................................. 178
6-2. Entering a Formula ................................................................................................... 180
6-3. Editing Math Block Programming Steps ................................................................... 181
6-4. Warning When Paste or Insert Exceeds Available Steps. ............................................ 182
6-5. Block Definition Derived from the ACCUM Block .................................................. 183

xvii
B0700FE – Rev A Figures

6-6. Derived Block Definition Opened in the Definition Editor ...................................... 185
6-7. Execution Editor Opened for a Compound .............................................................. 186
6-8. The Basic Processing Cycle ....................................................................................... 188
6-9. Result of Sample Period and Phase Settings ............................................................... 190
6-10. Location of the Modifier Types ................................................................................. 195
6-11. Adding a Parameter to an IA Modifier ...................................................................... 196
6-12. Assigning the MA Parameter to the Modify Group ................................................... 197
6-13. AutoMan Modifier Appearance Object and Modifiers Palette ................................... 198
6-14. Modifier Attached to Two I/O Blocks ...................................................................... 199
6-15. Changing the MA Parameter in Attached Blocks ...................................................... 200
6-16. Modifier Attached to a CSD ..................................................................................... 201
6-17. Parameters Added to a CSD and Its Blocks ............................................................... 202
7-1. Opening the ST Editor ............................................................................................. 206
7-2. Instance Wizard Menu .............................................................................................. 207
7-3. Instance Wizard Dialog Box ...................................................................................... 208
7-4. Typical ST Template with ST Decision and ST Code Items ..................................... 211
7-5. Code Properties Dialog Box ...................................................................................... 214
7-6. Decision Point Properties Dialog Box ....................................................................... 215
7-7. Control Question Properties Dialog Box ................................................................... 216
7-8. Control Question Properties Dialog Box for Multiple Choice ................................... 216
7-9. Decision Point Properties Dialog Box ....................................................................... 217
7-10. Control Question Dialog Box ................................................................................... 218
7-11. ST Template Example ............................................................................................... 219
7-12. Branch Choice Dialog Box ........................................................................................ 220
7-13. Multiple Choice Decision Point Linked to Five Code Items ..................................... 221
7-14. Example of a Replicate Decision Point ...................................................................... 222
7-15. Connecting a Replicate Decision Point ..................................................................... 223
7-16. Substitution Question Selection ................................................................................ 226
7-17. Substitution Properties Dialog Box ........................................................................... 226
7-18. Substitution Question Manager ................................................................................ 227
7-19. Substitution Properties Dialog Box ........................................................................... 228
7-20. Bulk Compile Dialog Box ......................................................................................... 230
8-1. Ladder Editor with Newly Created Ladder Object .................................................... 234
8-2. Rung Elements .......................................................................................................... 235
8-3. Ladder Rung Comments Dialog Box ........................................................................ 236
8-4. Logic Element Parameters Dialog Box ...................................................................... 237
8-5. Connecting Elements ................................................................................................ 239
8-6. Open Dialog Box for Importing a Ladder Configuration .......................................... 240
8-7. New PLB in a CSD ................................................................................................... 241
8-8. Assign Ladder to PLB Dialog Box ............................................................................. 242
8-9. Compile Tab in the Output Window ....................................................................... 244
9-1. Sample Process and Tags ........................................................................................... 245
9-2. Example IACC TagList ............................................................................................. 246
9-3. IACC TagList Editor Window .................................................................................. 248
9-4. TagList Editor Toolbar ............................................................................................. 249
9-5. Taglist Editor Pop-Up Menu Contexts ..................................................................... 251
9-6. Insert New Tag Dialog Box ....................................................................................... 252
9-7. FBM Combo Box ..................................................................................................... 254

xviii
Figures B0700FE – Rev A

9-8. Editing a New Parameter in a Custom Tag Type Definition ..................................... 257
9-9. Available Formats Dialog Box for TagList Export ..................................................... 258
9-10. Import Taglist - Information Dialog Box .................................................................. 259
9-11. Import Taglist - Tag Type Mapping Dialog Box ....................................................... 261
9-12. Import Taglist - Field Mapping Dialog Box .............................................................. 262
9-13. Import Taglist - Select Tags Dialog Box .................................................................... 264
9-14. Verify Dialog Box for TagList Agent Import ............................................................. 265
9-15. Imported Tags and Output Window with Import-Related Tabs ............................... 266
9-16. Available Formats Dialog Box for TagList Export ..................................................... 267
9-17. Export Taglist Information Dialog Box ..................................................................... 268
9-18. Taglist Export - Field Mapping Dialog Box .............................................................. 270
9-19. Delete Mappings Dialog Box .................................................................................... 271
9-20. Verify Dialog Box for a TagList Agent Export ........................................................... 271
9-21. Fields Used in Bulk Generation ................................................................................ 273
9-22. Select CSDs Dialog Box ............................................................................................ 274
9-23. Bulk Generation Preview Dialog Box ........................................................................ 275
9-24. CSD Created with Bulk Generation .......................................................................... 276
9-25. Tag Definition Selection Dialog Box ......................................................................... 277
9-26. Tag to Block Data Propagation Dialog Box .............................................................. 277
9-27. Adding Parameters to the Data Propagate Group ...................................................... 279
10-1. Reference Object Parameters ..................................................................................... 282
10-2. Creating Display Files ............................................................................................... 285
10-3. IACC FoxDraw Editor Option from a Display File Instance .................................... 287
10-4. Default Faceplates Added to a Drawing .................................................................... 288
10-5. Select FoxDraw Symbol Dialog Box .......................................................................... 289
10-6. Configure FoxView Options Dialog Box ................................................................... 289
10-7. FoxDraw Configure Objects Dialog Box ................................................................... 291
10-8. Assigning a CSD to a Compound ............................................................................. 292
10-9. Setting FoxView Options for a CSD Template ......................................................... 293
10-10. Adding a Symbol to a Drawing a CSD ...................................................................... 294
10-11. Configure FoxView Options Dialog Box ................................................................... 295
10-12. Assign Workstation(s) Dialog Box ............................................................................. 296
10-13. Display Validation Dialog Box .................................................................................. 297
10-14. Display Download Dialog Box .................................................................................. 299
10-15. Download Stations Dialog Box ................................................................................. 299
10-16. Downloading Dialog Box for Displays ...................................................................... 300
10-17. Available Formats Dialog Box ................................................................................... 301
10-18. Import File Name Dialog Box ................................................................................... 301
10-19. Selecting Display Files in the Open Box .................................................................... 302
10-20. Selecting All Display Files in a Folder ........................................................................ 302
10-21. Select File Location Dialog Box ................................................................................. 303
11-1. Control Database Locations ...................................................................................... 305
11-2. Entering Control Stations in the IACC-CP File ........................................................ 308
11-3. IACC Safeguard Program Settings ............................................................................ 308
11-4. Selecting Start Time in the Schedule Wizard ............................................................. 309
11-5. Entering User Name and Password in the Scheduled Task Wizard ............................ 309
11-6. Hierarchy Validation Dialog Box .............................................................................. 314
11-7. Validating Dialog Box and Download-Related Tabs in the Output Window ............ 315

xix
B0700FE – Rev A Figures

11-8. FoxCTS Change Tracking Dialog Box ...................................................................... 316

11-9. Download Control Station Dialog Box ..................................................................... 317
11-10. Downloadable Compounds ....................................................................................... 318
11-11. Display Download Dialog Box .................................................................................. 319
11-12. Download Stations Dialog Box for Display Files ....................................................... 320
11-13. Download Control Station Dialog Box ..................................................................... 321
11-14. Download Complete ................................................................................................. 321
11-15. Verifying System Monitor Configuration .................................................................. 323
11-16. IACC Options Dialog Box ........................................................................................ 324
11-17. IACC Options Dialog Box ........................................................................................ 326
11-18. Quick View Display .................................................................................................. 327
11-19. Configure FoxView Options Dialog Box ................................................................... 328
11-20. Live Values Displayed in a CSD ................................................................................ 329
11-21. FoxAPI Connect Utility Dialog Box ......................................................................... 331
11-22. Sample Client Initialization File ................................................................................ 333
11-23. Animated Live Diagram Options Dialog Box ............................................................ 334
11-24. ALD Update Dialog Box ........................................................................................... 335
11-25. Trending a Visible Parameter .................................................................................... 336
11-26. Compound Blocks ListView ...................................................................................... 337
11-27. Transition Between Validation and Download States ................................................ 339
11-28. Synch Status Page ..................................................................................................... 341
11-29. Upload and Compare to CP Warning ....................................................................... 343
11-30. Comparison Utility Dialog Box ................................................................................ 344
11-31. Bulk Upload Page ..................................................................................................... 346
11-32. Initialize Information Dialog Box .............................................................................. 348
12-1. IACC User Editor ..................................................................................................... 351
12-2. Delete Request Dialog Box ........................................................................................ 353
12-3. Confirm New Password Dialog Box .......................................................................... 354
12-4. IACC Group Editor .................................................................................................. 354
12-5. IACC Permissions Tab in the Group Editor ............................................................. 355
12-6. IACC Options Dialog Box ........................................................................................ 359
12-7. IACC Options Dialog Box and Audit Trail ListView ................................................ 361
13-1. Print Preview of a Tabular Report ............................................................................. 363
13-2. Graphical Report Preview ......................................................................................... 364
13-3. Print Preview Buttons ............................................................................................... 365
13-4. Sheet Editor .............................................................................................................. 367
13-5. Page Setup Dialog Box .............................................................................................. 368
13-6. Setting the Paper Orientation for the Sheet Template ............................................... 368
13-7. Report Template Definitions and Report Template Instances ................................... 372
13-8. Report Template Object List Opened for a Report Template Instance ...................... 374
13-9. Example Showing the Parameter Element ................................................................. 376
13-10. Example Showing the State Element ......................................................................... 377
13-11. Example Showing the Category Element ................................................................... 377
13-12. Report Template Editor ............................................................................................ 378
13-13. State Tab of the Report Template Editor .................................................................. 380
13-14. Type Tab of the Report Template Editor .................................................................. 381
13-15. Category Tab of the Report Template Editor ............................................................ 382
13-16. Parenthesis Tab of the Report Template Editor ......................................................... 383

xx
Figures B0700FE – Rev A

14-1. Context menu Selection ............................................................................................ 386

14-2. Create 200 Series FBM Dialog Box ........................................................................... 386
14-3. FCM/CP270 Migrate Window ................................................................................ 388
14-4. Print Messages ........................................................................................................... 389
14-5. Warning Message Box ............................................................................................... 390
14-6. Verification Dialog Box ............................................................................................. 390
14-7. Migration Dialog Box ............................................................................................... 391
14-8. FCM/CP270 Migrate Window ................................................................................. 392
14-9. Messages Dialog Box ................................................................................................. 393
15-1. IACC Database Directory Structure .......................................................................... 395
15-2. Files Copied from EmptyDB to a New IACC Database ............................................ 397
15-3. Sample IACC Settings File ........................................................................................ 398
15-4. Changing the IACC_DBNAME Variable ................................................................. 399
15-5. IACC Databases Dialog Box ..................................................................................... 400
15-6. Available Formats Dialog Box ................................................................................... 402
15-7. IACC Export File Name Dialog Box ......................................................................... 402
15-8. Export Information Dialog Box ................................................................................ 403
15-9. Select Compounds to Export Dialog Box .................................................................. 404
15-10. Verify Dialog Box for a Save/SaveAll Export ............................................................. 404
15-11. Available Formats Dialog Box ................................................................................... 406
15-12. Import File Name and Open Dialog Boxes ............................................................... 407
15-13. Import Dialog Box Showing Objects with Matching Types ...................................... 408
15-14. Preview of Objects to be Merged ............................................................................... 409
15-15. Preview of Objects to Copied from the Import File ................................................... 410
15-16. Verify Dialog Box for IACC Import ......................................................................... 411
15-17. Output Window with Import-Related Tabs .............................................................. 411
15-18. Import Information Dialog Box for a Save/SaveAll Import ....................................... 413
15-19. Select Block Dialog Box in a Save/SaveAll Import ..................................................... 415
15-20. FBMs to be Created with a Save/SaveAll Import ....................................................... 416
15-21. Results of a Save/SaveAll Import Displayed in the Project Navigator ........................ 417
15-22. IACC Database Administration Window .................................................................. 419
15-23. Warning: Backup Closes All Editors .......................................................................... 420
15-24. Enter Backup File Dialog Box ................................................................................... 420
15-25. Backup Complete ...................................................................................................... 421
15-26. Selecting the Backup File .......................................................................................... 422
15-27. Select Destination Directory Dialog Box ................................................................... 422
15-28. Information Message: Users Are Connected .............................................................. 423
15-29. Option to Back Up Files Currently in the Target Directory ...................................... 423
15-30. Restore Complete ...................................................................................................... 424
15-31. Select Central Database Dialog Box .......................................................................... 424
15-32. Verification Complete ............................................................................................... 425
15-33. Flow chart for converting ICC SaveAll diskette to IACC Database format ................ 435
E-1. Software Package Availability for AW ....................................................................... 444
E-2. Software Package Availability for WP ........................................................................ 444

xxi
B0700FE – Rev A Figures

xxii
Tables
2-1. Parts of the IACC Window ......................................................................................... 17
2-2. System Tab Branches .................................................................................................. 19
2-3. Network Tab Branches in the Project Navigator ......................................................... 20
2-4. IACC Independent Utilities ........................................................................................ 49
4-1. 268Kbps FBMs and Interfaces .................................................................................. 114
4-2. Expandable Main Modules and Their Expansion Modules ....................................... 117
4-3. DIN Rail Mounted 2Mbps FBMs ............................................................................. 120
4-4. User Guides for Field Device FBMs .......................................................................... 122
4-5. Validation Options ................................................................................................... 133
4-6. Package Distribution/Media Distribution Dialog Box Options ................................. 137
4-7. Columns in Software Section in Software Editor ....................................................... 139
5-1. IACC Block Function Types ..................................................................................... 145
6-1. Parameter Change Indicators .................................................................................... 179
6-2. Allowable Scan Periods .............................................................................................. 189
6-3. Valid Phase Values for a BPC of 0.5 Seconds ............................................................ 191
9-1. Colors and Symbols in TagList Editor ....................................................................... 249
9-2. Menu Commands Added for the TagList Editor ....................................................... 250
9-3. TagList Editor Cell Pop-Up Menu Commands ......................................................... 251
9-4. Parameters of the Foxboro IA Tag Type .................................................................... 253
9-5. Device Address Field Usage for H1 Device Block Connections ................................. 255
11-1. Download Actions .................................................................................................... 313
11-2. FoxView Toolbar Buttons ......................................................................................... 328
11-3. ALD Toolbar and Menu Selections ........................................................................... 330
11-4. Validation and Download States of IACC Objects .................................................... 338
12-1. Object-Type Actions ................................................................................................. 357
12-2. Symbols Appearing in Object-Type Action Configuration ........................................ 358
12-3. User and Group ListViews ........................................................................................ 360
12-4. Security Audit Trail Columns ................................................................................... 362
13-1. Sheet Template Macros ............................................................................................. 369
13-2. Type and Definition Objects List Box ....................................................................... 382
13-3. Fields and Buttons Unique to the Parenthesis Tab .................................................... 383
14-1. Checkbox Functionality ............................................................................................ 387
14-2. Parent Resolution ...................................................................................................... 389
D-1. ECB Conversion Mappings ....................................................................................... 439
E-1. Software Packages Assignable to WSTA70/WSVR70 ................................................ 443

xxiii
B0700FE – Rev A Tables

xxiv
Preface
This document describes how to use I/A Series Configuration Component (IACC) software to
develop control strategies for an I/A Series system. The document covers the basic features of
IACC for defining hardware and software, configuring control blocks and displays, and down-
loading the configurations to workstations and control processors. Additional information about
the IACC interface is available on-line in the IACC Help.
Refer to the release notes that accompanied the software for information on installing, configur-
ing, and maintaining the IACC software.
IACC is a direct replacement for the I/A Series Integrated Control Configurator. The application
supports import of configuration information from Save and SaveAll diskettes.

Audience
This document is intended for control and process engineering professionals who are responsible
for developing a process control system using the I/A Series system.

What You Should Know

This document assumes that the reader has a general knowledge of process control concepts and
practices, as well as familiarity with Microsoft® Windows® application. Specific knowledge of
I/A Series control software is helpful, but not absolutely necessary if there is ready access to
I/A Series documentation.

Revision Information
This is the initial release of this document.

FOUNDATION fieldbus Support

If you are using Version 2.2 to configure FOUNDATION fieldbus H1 devices on an I/A Series sys-
tem, you must also install Field Device Manager software. This FDT editor is opened from within
IACC and provides comprehensive management of field devices including configuration, com-
missioning and calibration, maintenance and troubleshooting. For additional information about
Field Device Manager, refer to Implementing FOUNDATION fieldbus on the I/A Series System
(B0700BA).

xxv
B0700FE – Rev A Preface

Reference Documents
The following Foxboro documents provide information related to IACC operation and the
I/A Series system:
 Address Translation Station User’s Guide (B0700BP)
 AIM*Historian User’s Guide (B0193YL)
 DCS Fieldbus Modules for Moore APACS+ Systems (B0700BK)
 DCS Fieldbus Modules for Westinghouse WPDF Systems User’s Guide (B0400BA)
 DIN Rail Mounted FBM Subsystem User’s Guide (B0400FA)
 FOUNDATION fieldbus H1 Communication Interface Modules (FBM220/FBM221)
User’s Guide (B0400FD)
 Implementing FOUNDATION fieldbus on the I/A Series System (B0700BA)
 FoxCTS Change Tracking Software (B0193VV)
 FoxDraw Software (B0193WG)
 High Level Batch Language (HLBL) User’s Guide (B0400DF)
 I/A Series Configuration Component (IACC) Release Notes (B0400BR)
 I/A Series Configuration Component (PSS 21S-2B5 B4).
 Integrated Control Block Descriptions (B0193AX)
 Integrated Control Software Concepts (B0193AW)
 Intelligent Design Studio (IDS) Library for IACC (B0400BQ)
 Learning to Use IACC (B0400BT)
 Software Installation (Solaris Platform) (B0193JG)
 Software Installation (Windows NT Operating System) (B0400JG)
 System Network Architecture Guide (B0700AZ)
 System Planning and Sizing (B0700AX)
 System Pocket Module Configurator User’s Guide (B0700AY)

Document Overview
The document is structured as follows:

Chapter 1 “Overview”
Discusses key concepts and features of IACC.

Chapter 2 “IACC Window”

Provides a quick tour of the IACC main window, describing the windows,
editors, and dialog boxes used to build a process control system.

Chapter 3 “Using IACC”

Outlines a procedure for quickly learning how to use the IACC configura-
tor tools to configure a control strategy for your application.

xxvi
Preface B0700FE – Rev A

Chapter 4 “System Configuration”

Describes how to configure hardware and software for installation of the
equipment.

Chapter 5 “Control Configuration”

Covers configuration of control blocks using the CSD Editor and the
Connections dialog box.

Chapter 6 “Modifying Compounds and Blocks”

Describes other tools for configuring compounds and blocks: the Proper-
ties dialog box, the Execution Editor, the Definition Editor, and modifier
type blocks.

Chapter 6 “Modifying Compounds and Blocks”

Discusses how to change compound and block parameters using the
Properties dialog box, Definition Editor, Execution Editor, and modifiers.

Chapter 7 “Sequence Blocks”

Describes the use of the ST Editor and ST Template Editor to create
structured text for Sequence blocks.

Chapter 8 “Ladder Logic”

Describes how to configure programmable logic blocks using the IACC
Ladder Editor.

Chapter 9 “TagLists and Bulk Generation”

Describes how to use the TagList Editor to identify I/O points, import
and export TagLists, and generate CSDs from a TagList and CSD
Templates.

Chapter 10 “Creating Displays”

Describes how to create and apply displays using the integrated FoxDraw
application.

Chapter 11 “Downloading Control Blocks”

Describes validation and download of a control database to the control
processor.

Chapter 15 “Managing IACC Databases”

Describes the tools available with IACC for managing the database.
Chapter 12 “Security”
Discusses the concepts and procedures required to manage security prefer-
ences, including configuring security with the User and Group Editors,
enabling system-wide security, and using security audit trails.

xxvii
B0700FE – Rev A Preface

Chapter 13 “Printing and Reports”

Describes printing and reports for the IACC application and the setup of
Report Templates and Sheets.

Chapter 14 “100 Series Migration”

Provides an overview of 100 Series migration. It also describes the process
and the sequence of procedure required for the 100 Series migration.

Appendix A “Glossary”
Provides a glossary of terms as they pertain to the use of IACC.

Appendix B “Flow chart for Converting ICC SaveAll Diskette to IACC Database Format”
Describes a flow chart that provides as a guide for the preparation work
that is required before importing an ICC SaveAll to IACC.

Appendix C “Executing the IACC Utility ArchExport.exe”

Provides information for executing the IACC Utility ArchExport.exe.

Appendix D “100 Series Migration Support”

Provides the types of migrations which IACC supports and the list of
migrations mappings supported by IACC.

Appendix E “IACC 2.5 Enhancements”

Provides information on the IACC 2.5 enhancements.

Request for Comments

Please direct your comments and suggestions concerning IACC software to:
Global Customer Support Center B52-AA
Invensys Systems, Inc.
33 Commercial Street
Foxboro, MA 02035
Telephone (within the US): 1-866-746-6477
Telephone (outside the US): 508-549-2424
Fax: 1-508-549-4999

xxviii
1. Overview
This chapter provides an overview of the concepts and features of IACC.
The IACC software package provides powerful tools to accomplish I/A Series process control
life-cycle design and engineering from a common engineering environment, significantly reduc-
ing configuration costs. IACC reduces engineering time and project costs by employing templates
such as control strategy templates, I/A Series process control blocks, and predefined block config-
urations. At the same time, the software performs many routine tasks allowing you to concentrate
on planning and engineering, while reducing errors and improving technical quality.
The program’s easy-to-learn operation allows you to extend these productivity benefits to projects
assigned to plant personnel and contract engineers. IACC’s graphical editors allow you to config-
ure complex control schemes by simply dragging an object from a palette of predefined objects to
a drawing in the Editor window (Figure 1-1).

Figure 1-1. Building an IACC Control Strategy Diagram

1
B0700FE – Rev A 1. Overview

The IACC engineering software package provides the following features:

 Re-usable engineering reduces engineering time, implementation time, and project
cost through Control Strategy Diagram (CSD) Templates, Structured Text (ST)
Templates, print templates for reports, and other libraries.
 The Intelligent Design Studio library includes CSD Templates and display objects for
frequently used loops that can be applied to your control strategy with minimal
modification.
 Integration of FoxDraw display templates with CSD Templates saves configuration
time and promotes standardization.
 Modifiers that quickly change the operational characteristics of blocks and
compounds.
 Quick construction of control strategies saves process control configuration time.
 System security allows individualized control of multiple concurrent users as they
access IACC editors, functions, and object types.
 The CSD Editor uses graphics with automatic drawing generation, ensuring consis-
tent documentation layout.
 CAD or other graphic utilities are not required to print or modify reports.
 You can customize control strategies by creating your own application libraries.
 You can customize the default parameter attribute values, add new parameters, and
delete parameters of control blocks, templates, and other library functions to create
new child objects of the parent object.
 Plant View enables you to group control objects by their location in the plant or
similar criteria and modify any objects in the IACC database.
 Database management tools enable you to merge re-usable components.
 Blocks can be downloaded to the I/A Series system individually or with other blocks
associated with the same compound, CSD or CSD Template, processor, or Plant
Area.
 The Bulk Generation feature automatically creates CSDs using TagList data and CSD
Templates.
 A consistent menu structure, a detailed Help system, and standard Microsoft™
Windows graphical user interface provide easy-to-learn operations.
 Intuitive icons facilitate fast access to operations and program areas.
 Selection lists eliminate typing errors.

2
1. Overview B0700FE – Rev A

A common database stores all configuration information making the data available to all other
IACC processes, eliminating the need to re-enter the same information in various applications
and minimizing data entry errors.
The implementation of a process control strategy begins by developing process and instrumenta-
tion (P&I) drawings for the process to be controlled. The information from these drawings
defines the equipment requirements and the type of control required to manage the process. You
use this information in IACC to build a control strategy for the process. IACC also allows you to
perform configuration tasks such as creating a TagList for instrumentation I/O, and building pro-
cess displays. With these features, IACC functions as the complete configuration tool for process
control engineering. Figure 1-2 depicts the components configured with IACC.

Ladder Logic Structured Text Continuous Process Process

Control Control Control Displays Templates

IACC Database

Reports Security System

TagList
Configuration
Figure 1-2. Components Configured in IACC

The engineering is performed on a stand-alone or networked IACC database server running the
Windows® XP operating system (Figure 1-3 and Figure 1-4). The server manages one or more
IACC databases, which users can access from different networked workstations; however, only
one client at a time can access a particular database. The workstation supports the tools for
building a control strategy of compounds and blocks. The compounds and control blocks are
downloaded to a control station to control the process independently.
Figure 1-3 shows an IACC implementation involving two servers, one on an I/A Series
workstation and the other installed off-platform on a Windows 7 machine. The setup
includes five clients: a local client on each of the two servers, one remote client on an I/A Series
workstation, and two remote clients on off-platform Windows 7 machines. This setup is used for
configuring an I/A Series environment that includes a 100 Mbps switched control network and a
legacy 10 Mbps Nodebus. In this mixed network environment, IACC uses a second ethernet net-
work for the following tasks:
 Communication between clients and servers.
 Delivery of control compounds to the download host I/A Series workstations.
The compounds are then downloaded to the control stations via the 100 Mbps
switched control network and the legacy 10 Mbps Nodebus.
 Interaction with the download host workstations for checkpointing, uploading CP
files, and variety of other tasks related to implementing a control strategy.
 Distribution of display files to I/A Series workstations.

3
B0700FE – Rev A 1. Overview

Enterprise Domain IACC server and IACC client IACC client

local client on
an off-platform
Windows XP
system with
multiple databases

2nd Ethernet I/A Series V6.4

Windows NT IACC server IACC client
I/A Series V8.8 I/A Series V8.8
Windows 7 Windows 7

IS3B01 CP4B01 MG3B01 OMC001

RCNI RCNI
DNBT DNBT
NCNI
Legacy A 100 Mbps Switch Control
Nodebus Network
10 Mbps Nodebus B 100 Mbps Switch
NCNI
DNBT
RCNI RCNI
AB3B01 FD3B01 CP6001 TACM01 I/A Series V6.4
(Hosted by Solaris I/A Series V7.0
AW51F1) Solaris
(AP51F)
- Only one client at a time can access a database.
- IACC clients can only download to hosts/ (WP51D)
workstations with 2nd Ethernet. (WP51F)

2nd Ethernet
Figure 1-3. Configuration Options for IACC in a Mixed I/A Series Network

When IACC is used for configuration of an I/A Series Version 8.x system, the IACC server and
clients can be implemented on I/A Series workstations and communicate with the download
hosts directly over The Mesh Control Network (Figure 1-4).

IACC Server
and local client

Workstation
Remote
(Windows 7)
IACC client
The Mesh Configuration Data
Control Network Workstation
Switch Switch Switch (Windows XP)

Download Control, Displays

Switch Switch Control Station

Workstation ZCP270
(Windows 7)

Download Host Workstation

Control Station (Solaris)
Workstation
ZCP270 (Windows 7)

Download Host

Figure 1-4. IACC Implementation on The Mesh Control Network

4
1. Overview B0700FE – Rev A

IACC and Legacy Configurators

IACC provides both system configuration and control configuration for I/A Series systems, and
includes import function to move control databases from configurators such as System Definition
(SysDef ) and the Integrated Control Configuration (ICC) using SaveAll diskettes.
While IACC is designed to replace the earlier tools, the software supports co-existence with Sys-
Def, ICC and FoxCAE as follows:
 System configuration for a control station including creation of the Commit diskettes
can be accomplished with either IACC or SysDef, provided the configuration tool
supports the specific hardware.
 If system configuration for a control station has been performed with SysDef, you can
develop and maintain the control configuration with IACC, provided the hardware is
supported by IACC. Refer to I/A Series Configuration Component (IACC) Release Notes
(B0400BR) for a list of supported hardware. A minimal amount of system configura-
tion data must be entered into IACC to identify the CP and its download host. The
information can be entered directly or imported from a SysDef Export diskette as
described in “Importing System Definition Data” on page 91.
 IACC and ICC can exist in the same workstation and can communicate with the
same download hosts.
 Control configuration for a specific control station can be maintained with either
IACC or ICC, but not by both. You must designate which control stations receive
downloads from IACC. Refer to “Enabling IACC Downloads to a Control Station”
on page 307 for instructions on making the designation.
 The I/A Series system prevents downloads to IACC designated control stations from
ICC, and vice versa.
 FoxCAE cannot download to an IACC designated control station.

5
B0700FE – Rev A 1. Overview

Control Strategy Engineering

Process control for I/A Series systems is based on the concepts of compounds and blocks. A block
is a member of a set of algorithms that performs a certain control task within the compound
structure. A compound is a logical collection of blocks that perform a control strategy. Figure 1-5
shows the compound and block relationship.

Compound 1
Control
Strategy Loop 1
I/O Block Process

Control Block

Control Block

Compound 2

I/O Block Process

Control Block

Control Block

I/O Block Process

Loop 2 Compound 3

I/O Block Process

Control Block

I/O Block Process

Figure 1-5. Compound and Block Relationships

Compounds
The compound provides the basis for the integration of:
 Continuous control such as pressure, temperature, level and flow, or valve and motor
control, including device interlocking.
 Sequential control such as a mixing phase in a batch reactor.
Within this structure, any block in any compound can be connected to any other block in any
other compound in the system. Each compound can contain one or more control loops or
individual control blocks for another control loop.

6
1. Overview B0700FE – Rev A

Control Strategy Diagrams

In IACC, the graphic CSD Editor is used to create a control strategy. A CSD contains graphical
appearance objects (Figure 1-6) of control blocks. These control blocks represent control loops as
organized on the CSD. Control loops can be graphically created by dragging block definitions
into the CSD drawing and then connecting the appropriate block parameters.

Figure 1-6. IACC Control Strategy Diagram

Control Blocks
You create blocks only by adding them from a library or a palette to a CSD. Control blocks on a
CSD can be assigned to the same compound or different compounds. This allows a logical pro-
cess grouping of connected blocks in the same CSD regardless of which compound or control
processor hosts the blocks.
Blocks have three essential parameter types:
 Inputs to the algorithm
 Outputs from the algorithm
 Configuration parameters to invoke different options to algorithm processing.
A block can contain parameters that have real, Boolean, packed Boolean, integer, string,
character, and other types of values.
For re-usable engineering, control blocks and CSDs can be saved in a palette or template, and
recalled as necessary. The appearance on a CSD of a control block can be customized.

7
B0700FE – Rev A 1. Overview

Block Connections
The connections between control blocks are defined within the CSD. You can connect parameters
of blocks graphically in a CSD. When you connect two block parameters, the CSD automatically
draws a line with an arrow symbol indicating the data flow. All connections are established by
connecting a source block’s parameter to a sink block’s parameter. When you make a single
address connection between two blocks, multiple elements can be connected as well, depending
on the parameters connected. When a single connection is made, IACC propagates other connec-
tions between the blocks based on the block definitions.
Within IACC, connections can be address connections or value propagation connections:
 Address Connections
The values of the parameters represent the physical and logical connections from one
block to another. Address connections contain the compound, block, and parameter
name to which the control block parameter is connected. The connections you make
using the graphical editor in IACC are converted by IACC to the block parameter
address required by the I/A Series system.
The I/A Series system uses these parameter connections to resolve the full pathnames
for block-to-block control connections during downloads to the CP. The standard
method of accessing a block parameter value is the syntax:
<Compound>:<Block>.<Parameter>
For example, FLOWRATE:CALC05.R101 is the real input parameter RI01 in the
Calculation block CALC05 in the compound FLOWRATE.
 Value Propagation Connections
Value propagation connections pass values such as scale and range among one or more
control blocks. Data values and block attributes for the elements of connected
parameters flow from one block (source) to another (sink).
The Value propagation connections are maintained only in the IACC database, and
changes to a source parameter in one block update the sink parameter in the same or
other blocks. When the block is downloaded to the I/A Series system, the last
propagated value is downloaded, not the connection.

Naming Conventions
In an I/A Series system, you must use unique names for:
 Blocks within the same compound
 Each compound.
You can use the same name for blocks that are assigned to different compounds. Names of
compounds and blocks can be up to 12 alphanumeric characters. Compound, block, and CP
names must comply with I/A Series system rules. IACC enforces additional naming rules for
objects such as CSDs, CSD Templates, and ST Templates.
When you add an object to a database, IACC assigns a default name. You can rename the object
at any time, and IACC automatically makes the appropriate addressing and other configuration
changes in the database.

8
1. Overview B0700FE – Rev A

Assigning or Unassigning Blocks and Compounds

A CSD shows blocks in a logical control flow. The blocks must be assigned to the appropriate CP.
During the control strategy engineering process, you assign blocks to a compound, and com-
pounds to a CP. You can assign or unassign individual blocks, entire CSDs to/from compounds,
and compounds to/from CPs. The compound rules are:
 Multiple compounds can be executed within the same CP.
 A single compound must be assigned to a single CP.
 Every compound must have a unique name.
For each compound, you can view the sequence in which compounds and blocks are executed in
the CP. The sequence of the blocks within a compound sets the sequence of operation. Single
blocks and compounds can be reordered to balance the block processing load.
The block rules are:
 Blocks must be uniquely named within a compound.
There can be several blocks called “AIN1”, but they must be in different compounds.
 The execution sequence of blocks may be reordered within a compound.
 A block can belong to only one compound, but it can belong to multiple loops at the
same time.

Deleting and Unassigning IACC Objects

IACC objects, such as blocks and compounds, appear in multiple places within the Project
Navigator. For example, compounds appear under Plant Areas and under CPs in the Project Nav-
igator, while blocks appear under compounds and under CSDs. Therefore, when you delete or
unassign these objects, one of the following actions occurs:
 Unassigning a compound from a CP leaves the compound under the Plant tree but
removes the compound under the CP.
 Deleting a compound removes the compound from the IACC database, but does not
delete the blocks from the CSD (blocks still appear in CSD); the blocks are unas-
signed from the compound.
 Unassigning a block from a compound removes the block from that compound, but
leaves the block assigned to the loop(s) to which it was previously assigned.
 Cutting a block from a loop removes the block from that CSD.
If that was the last loop to which the block was assigned, the block is also removed
from the IACC database.
 Deleting a block deletes the block from the compound and from the CSD.

! WARNING
Using the Delete command permanently removes the object from the IACC data-
base. There is no Undo capability in IACC.

9
B0700FE – Rev A 1. Overview

Control Language
IACC supports configuration of three types of process control: continuous, sequential, and ladder
logic, and provides special tools for configuring Sequence and Programmable Logic Blocks
(PLBs).

Structured Text Code

Structured Text (ST) code is written using a High Level Batch Language (HLBL). HLBL
provides a unified set of language elements for configuring continuous, semi-continuous and
batch control applications. Refer to High Level Batch Language User’s Guide (B0400DF).
The built-in ST Code Editor is used to write and compile the ST code.
For re-usable engineering, ST code written can be saved in a file or template and recalled as
necessary.

Structured Text Templates

IACC allows you to build templates of re-usable code. These ST Templates can contain
preconfigured control blocks, segments of HLBL code, or code comments. The ST Template tool
prompts you in a question and answer format to insert code segments and substitute values for
addresses, parameter names, strings and numeric constants in placeholders in the code segments.
The HLBL code contained in a template is inserted into and compiled from a sequence block.
You can embed templates within the code items of a template contained in a sequence block. For
re-usable engineering, ST Templates can be recalled when needed.

Ladder Logic Editor

With the IACC Ladder Logic Editor, you can design logical control strategies using relay contact
and coil symbols. You can save and retrieve segments of ladder logic that are commonly re-used.
The ladder logic program generated by the editor is compiled, and then downloaded to a digital
FBM for execution. A programmable logic block (PLB) is the interface between the FBM and the
tasks that set and get information from the ladder. These tasks can be other control blocks or
displays.

Downloading Blocks and Compounds

The IACC Download function installs the control block into the specified CP.
You can download the following:
 Individual blocks
 Individual compounds and their blocks
 All compounds
 All blocks or selected blocks in a CSD
 The blocks in all CSDs that were derived from the same CSD Template
 All or selected CSDs, compounds, and blocks assigned to a Plant Area.

10
1. Overview B0700FE – Rev A

Documentation and Printing

IACC has its own unique way of displaying and printing objects within the configuration. You
can print control strategies built within the CSD Editor or data from IACC to the local printer.
Tabular editors display objects typically as rows of data in a spreadsheet-like format printed in a
row/column print format. All reports are printed using a what-you-see-is-what-you-get
(WYSIWYG) format, which you can preview in IACC.
IACC enables you to create Sheet Templates for both graphical and tabular reports to include pre-
defined borders and annotations. The Sheet Templates can include macros for specifying time and
date of report, report name, and name of the user generating the report. You can build your own
templates from scratch or copy the existing Sheet Template into a new one.
You can print reports using predefined print specifications such as paper size, orientation, and
type of printer, or you can change the printer properties at the time of printing.

Utilities
Properties
Use the Properties dialog box to view and modify the parameter values for a displayed object in
the Project Navigator, or an appearance object displayed in an editor window for one of the
graphics-based editors.

ListViews
A ListView is a report of associations to a specific class of IACC objects, or a list of parameters.
It defines which types of collections and object attributes apply to a given primary object. Every
IACC object in the same class uses the same ListView to derive the contents shown in the Editor
window.
A collection is a list of similar IACC objects that meet one of the following criteria:
 The objects are derived from a single parent object, such as all CSDs created from the
same CSD Template
 The objects belong to the same object class, such as all I/O block definitions
 The objects are assigned to the same object, such as all CSDs, compounds, display
files, and Plant Areas that are assigned to the same Plant Area.
Each object class has a set of ListViews available to it.

Palettes
IACC palettes enable you to quickly configure a control strategy by dragging re-usable objects to
an editor window. Palettes provided with IACC include standard I/A Series control block, alarm
configurations, and ST code. You can create your own palettes to save certain configurations for
re-usable engineering.

11
B0700FE – Rev A 1. Overview

Find in Database and Where Used

The Find in Database search command enables you to locate any IACC object with certain
specified attributes. The search is performed only for objects in the IACC database. You can then
select the results of the search and apply the Where Used command to locate all objects derived
from or associated directly with a selected IACC object. For example, you can use a Where Used
search:
 For a CSD to list the blocks contained in the CSD and the compound associated with
the CSD
 For a sequence block definition to view the object definitions and object instances
derived from the block, the compounds or CSDs to which the block is assigned, and
other blocks to which the block has a parameter connection.
This search can be performed for objects in most windows and editors.

Import and Export Databases

An Import dialog box provides a direct interface for importing data from other IACC databases.
Export uses a standard Windows Save As dialog box and allows you to save specific portions of the
database to a file or to an external device. The import/export mechanism is in an IACC proprie-
tary format that cannot be read by applications outside IACC.

Database Backup and Restoration

The IACC Database Administrator utility is an independent facility that allows you to back up,
verify, and restore the entire IACC database. Each time you download configuration information
to the I/A Series system, IACC makes a separate backup of the entire database with the filename
LastDownload.bdb. The IACC Database Administrator backup function can be invoked from
the IACC menu bar. Regular backups of all or part of the IACC database is recommended. This
allows quick recovery in case of a catastrophic failure such as a disk crash.

Software Packages
For I/A Series software v8.8 and later, the software packages used by IACC have been modified
from previous releases, along with their installation locations. Some packages which were
previously installed on Control Processors are now installed on workstations or servers. Refer to
I/A Series V8.8 Release Notes (B0700SG) for a description of the current software packages
installed on the stations and Control Processors.

12
2. IACC Window
This chapter provides a quick tour of the IACC main window, describing the windows, editors,
and dialog boxes used to build your process control system. The chapter also describes how to set
system options.
This chapter includes the following topics:
 “Starting IACC” on page 13
 “IACC Window Overview” on page 16
 “The IACC Editors” on page 23
 “Utilities and Compilers” on page 49
 “Using On-Line Help” on page 50
 “Setting IACC Options” on page 50.

Starting IACC
To start an IACC session:
1. Do one of the following:
 Click Start and select the IACC icon if it is included in the list of most recently
used files.
 Choose Start > All Programs > IACC > IACC Studio as shown in Figure 2-1.

IACC
Icon in
Most
Recently
Used

Figure 2-1. Windows Start Menu with IACC

13
B0700FE – Rev A 2. IACC Window

An IACC client can be configured for access to multiple databases on one or more
servers (see Chapter 15 “Managing IACC Databases”). When multiple databases have
been enabled, the IACC Databases dialog box lists the available databases
(Figure 2-2).

Figure 2-2. IACC Databases Dialog Box

2. Select a database and click OK.

IACC displays the Logon dialog box (Figure 2-3) that provides security access to the
IACC editors and functions.

Figure 2-3. Logon Dialog Box

14
2. IACC Window B0700FE – Rev A

3. Enter the user name and password and click OK.

The password is case-sensitive; the user name is not.
The main IACC window is displayed (Figure 2-4).

15
B0700FE – Rev A 2. IACC Window

IACC Window Overview

IACC allows easy access to the editors, dialog boxes, tools, and objects you require to set up your
control strategy. As shown in Figure 2-4, the main IACC window is divided into four separate
elements. Multiple editors can be open at the same time. The editor tabs at the bottom of the
Editor window allow you to select among the active editors. Windows can be resized, moved to
another screen location, or hidden (via the toolbar menu). Each window and menu bar appears as
shown in Figure 2-4 when IACC is initiated for the first time, with the Welcome window in the
Editor window.
If another IACC editor is invoked, the editor replaces the Welcome window. The Welcome
window and any open editors are selectable from the tabs located under the Editor window. In
general, you select an editor by right-clicking on an object in the Project Navigator and selecting
the editor from the pop-up menu. When you select an editor, it adds its editor tab to the existing
set of editor tabs.

Menu Bar Toolbar

Title Bar

Status
Bar
Project Editor Output Editor Palette
Navigator Tabs Window Window
Figure 2-4. IACC Windows and Menu Bars

The IACC main window components are described in Table 2-1.

16
2. IACC Window B0700FE – Rev A

Table 2-1. Parts of the IACC Window

Function Description
Title Bar Displays IACC, the name of the IACC editor currently open in the Editor
window, and the name of the object being edited.
Menu Bar Provides access to a number of useful functions (picks). The contents of the
menus vary depending on whether the Project Navigator or an editor is active.
Menus also vary between editors.
Toolbar Provides immediate access to a host of functions via a set of buttons. The
buttons that are displayed vary depending on whether the Project Navigator
or an editor is active. Buttons also vary between editors. Each set of buttons
can be hidden. All toolbar picks are also menu picks.
Project Navigator Displays all the IACC objects currently available in the configuration
database. Double-click an object to start its associated editor. Right-click the
object to invoke a list of operations that you can perform on the object.
Invoking a specific editor loads a corresponding set of menu/tool selections in
the menu bar and toolbar. Project Navigator can be hidden from the IACC
window.
Editor Window Main window in which each IACC editor displays its contents. Most
configuration procedures take place within this window. Multiple IACC
editors can be open at once, but only one editor is viewable in this window at
a time. This window cannot be hidden. Tabs at the bottom of the Editor win-
dow allow you to select among the active windows.
Palette Displays commonly used objects for quick access during a configuration
session. This pane can be hidden or undocked from the IACC window.
Editor Tabs When an IACC editor is open in the Editor window, it has a corresponding
tab which allows you to bring the editor to the foreground. These tabs have a
different icon for each editor. When you hold the cursor over each tab, a
tooltip pops up with the name of the editor and the primary object for that
editor.
Output Window Displays the results of object requests, searches, and diagnostic runs, as well as
status messages of various editor activity and other IACC status reports. It can
be converted to a floating window separate from the IACC window, it can be
hidden, or it can be undocked from the IACC window. The contents of the
Output window can be printed or copied to a file. When an object is
displayed in the Output window, such as the results of a where-used or find
search, you can right-click on the line to display the menu options available
for that object. You can also double-click on the line and display that object’s
properties, such as a list of parameters.
Status Bar Displays a description of a selected menu or toolbar buttons and displays
status messages of various windows activities.

17
B0700FE – Rev A 2. IACC Window

Title Bar, Menus and Toolbar

The title bar (Figure 2-4) at the top of the IACC window, displays IACC, the name of the IACC
editor currently open and selected in the Editor window, and the name of the object being edited.
The title bar also provides standard window functions for moving and modifying the size of the
IACC window.
The menu bar is where you select commands for operating IACC and any open IACC editors.
The available commands vary depending on which editor is selected, or whether an IACC object
in the Project Navigator is selected.
The toolbar (Figure 2-4) contains groups of buttons which are shortcuts to selected commands
and functions. The buttons vary depending on the IACC editor selected and whether an IACC
object in the Project Navigator is selected.
When you right-click within an Editor window, a pop-up menu lists the editor-specific
operations.
Shortcut keys are available for frequently used menu options. For example, the key combination
Ctrl+F starts a Find operation to locate an object in the database.
Refer to the IACC Help for a complete catalog of menus, toolbars, and shortcuts.

Project Navigator
The Project Navigator (Figure 2-4), on the left side of the IACC window, is your view into the
project database, using a tree structure similar to the folders display in Windows Explorer. The
Project Navigator has three tab selections, each providing a different viewpoint:

System Provides access to objects and definitions used in configuring your process
control network. These resources include CSD Templates, TagLists, and
libraries of standard I/A Series block definitions. The tab also provides
access to report templates and security functions.

Network Defines the network hardware and software used in the system. With this
tab, you can view the hardware hierarchy, and you can create and modify
both hardware and software objects. Pop-up menus enable you to specify
options (parameter, hardware, and software) for hardware and software.
The Network tab also provides access to compounds and their blocks once
the compounds are assigned to a control station.

Plant Groups configuration components by physical location, projects, plant

equipment, processes, or whatever organizational method you choose.
In the Plant tab, you define a hierarchy of Plant Area objects. Each Plant
Area object allows you to create CSDs, compounds, and display files. You
can also perform a variety of other control configuration tasks.
The Project Navigator lists objects within each node alphabetically. You
can set the Project Navigator to display the objects in the order they were
created. It can also be configured to show the object type and a description
in parentheses after the object name. The Project Navigator display
properties are set with the Options dialog box as described in “Setting
IACC Options” on page 50.

18
2. IACC Window B0700FE – Rev A

System Tab
The System tab organizes the IACC objects in the system hierarchy into five main branches
(Table 2-2).
Table 2-2. System Tab Branches

Branch Icon Description

Components Where you define and store the following resources that
are used in the creation of CSDs:
 CSD Templates
 Display Files
 PLB Ladders
 ST Templates
 TagLists.
IACC Settings Reserved for Invensys use.

Library Where you create and define the definitions for the objects
in the Components branch.
Report Manager Contains Report Template and Sheet Templates used in
setting up reports for other objects in IACC.
Security Controls the individual user’s or group’s access to IACC or
to each functional editor.
Workspaces Contains custom palettes created for all users or for the
individual user who created the palette.

19
B0700FE – Rev A 2. IACC Window

Network Tab
The Network tab in the Project Navigator is used to configure the hardware and software to be
used in the control system. As shown in Figure 2-5, this tab contains two tree branches:
 Configuration
 Sheets.
These branches are unique to the Network tab.

Figure 2-5. Network Tab

The contents of the Configuration and Sheets branches are described in Table 2-3.

Table 2-3. Network Tab Branches in the Project Navigator

Branch Icon Description

Configuration Used to configure the application and control domains
(networks) for your I/A Series system. This is the location in
which you select the control hardware and software, and
configure the network.
Sheets Reserved

20
2. IACC Window B0700FE – Rev A

Plant Tab
In the Plant tab (Figure 2-6), you create a hierarchy of Plant Area objects to organize configura-
tion objects into logical groupings that reflect the layout of the plant, the needs of an engineering
project, or whatever scheme makes it easier for you to locate and re-use IACC objects. There are
no rules regarding how Plant Areas are used. You can use them to group control objects by where
they are, what they do, or who owns them. The Plant Areas can be nested in any combination.
Each Plant Area can contain other IACC objects such as CSDs, compounds, and display files. You
can create these objects from the Plant tab, or assign existing objects to Plant Areas using menu
picks in the System tab.

Figure 2-6. Plant Tab

Selecting a Menu
Menus can be selected by any of these methods:
 Clicking in the main menu
 Right-clicking on an IACC object in the Project Navigator
 Right-clicking on a blank space in a window
 Right-clicking on an object in a window.
Each of these actions brings up a different menu as each is context-sensitive and object-specific.
Figure 2-7 compares pop-up menus selected from a Plant Area with one from a display file.

21
B0700FE – Rev A 2. IACC Window

Figure 2-7. Plant Tab Pop-Up Menus

Dialog Boxes
In most cases, the IACC software provides special dialog boxes when user data entry is required.
These dialog boxes allow selections or assignments via lists and toggle options. Rather than typing
items, you can select them from lists. The risk of error is minimized since you can select only the
items that are suitable for the operation.

Messages and Warnings

All messages and warnings are displayed in the Output window, which gives information about
what the program is presently working on and tells you what must be done. When the Output
window displays an error, you can display information about the object causing the error by
selecting the object in the Output window and choosing Edit > Where Used from the menu bar.
The Where Used tab indicates where you can access the object.

22
2. IACC Window B0700FE – Rev A

The IACC Editors

IACC uses editors to help you efficiently configure loops for a process control application. Each
of these editors appears in the Editor window.
Editors within IACC have four predominant forms:
 Tabular Presents object data in a spreadsheet-like format with rows and columns of
information.
 Textual Displays data in a textual format, typically with line numbers preceding each
line of data.
 Graphical Displays data as a graphical display allowing objects to be dragged from one
place to another and allowing data to be inserted into the object as text or
graphical objects such as squares, circles, and bitmaps, each with their own
graphical properties. All graphics-based editors share a common set of
graphics tools.
 Dialog Box Provides data access via conventional windows and controls typically found on
dialog boxes.

Each editor has a specific string (or field) which it displays in the title bar. Also, each editor
displays a different icon on its respective tab in the Editor window.

Process Control Editors/Dialog Boxes

The process control editors/dialog boxes in IACC are:
 Control Strategy Diagram (CSD) Editor  TagList Editor
 ST Code Editor  ST Template Editor
 Ladder Editor  Execution Editor
 Control Station Loading dialog box  Synch Utility dialog box
 Control Validation and Download dialog  Compare to CP dialog box
box

23
B0700FE – Rev A 2. IACC Window

CSD Editor
The CSD Editor is a graphics-based editor that sets up CSDs. CSDs are used to create the
following:
 Continuous regulatory control  Sequential control
 Plant startup and shutdown sequences  Inter-unit coordination
 Device interlocking  New and modified CSD Templates.

CSDs typically consist of multiple, interconnected blocks grouped to perform a specific set of
functions. Each block contains an algorithm with one or more input/output parameters. Input
parameters bring real-time process data to the block algorithm. Output parameters make
block-calculated values available outside the block. These parameters are connected to the input
and output parameters of other blocks to create a continuous data flow.
Figure 2-8 displays a typical Simple CSD in the CSD Editor.

Figure 2-8. Control Strategy Diagram Editor

24
2. IACC Window B0700FE – Rev A

When viewed in the CSD Editor, all blocks in IACC have a graphical representation, which
displays certain input/output parameters. When you use the CSD Editor, connecting blocks is as
easy as dragging a line between an output parameter on one block to the input parameter of
another block. The connections define how data is transferred in real time between the blocks.
You can connect an output (source) parameter of one block to an input (sink) parameter of
another block. Using the Connection dialog box is further described on page 42. You can also
connect an output parameter of a block in one CSD to an input parameter of a block in a
different CSD. You can add drawing components such as lines, ellipses, and text to provide
annotations to your CSD.
After the control blocks of a CSD are downloaded to the I/A Series system, there are two ways you
can quickly access displays of live block data:
 Quick Views For IACC clients running on I/A Series workstations, a FoxView group
display can be accessed with each block represented by an I/A Series
faceplate. The faceplates are arranged in the group in the same way that
the blocks are shown in the CSD.
 Animated Loop Available for both on-platform and off-platforms clients, ALDs
Drawings (ALDs) connect with the CP and display the dynamically updated block param-
eter values in the CSD Editor window (Figure 2-9). ALDs also enable
you to set block parameters in the CP and to update the IACC database
with values from the CP.

Figure 2-9. Live Values Displayed in a CSD

25
B0700FE – Rev A 2. IACC Window

CSD Templates
You can also convert any CSD into a CSD Template or use the CSD Editor to build templates
from scratch. CSD Templates, which consist of control loops with connected control blocks and
ECB placeholders, enable re-use of control configurations. With a single command you can create
multiple CSDs that have the same blocks and block connections. You can then connect the
individual CSDs to the process I/O, and make other configuration changes appropriate for the
individual instances. When you update a CSD Template, the changes are automatically applied to
each CSD instance created from the template. CSD Templates can also be used with a TagList to
bulk generate CSDs and update existing CSD Template instances.

TagList Editor
The TagList Editor (Figure 2-10) allows you to create and modify lists of I/O points in your con-
trol system. The IACC TagList identifies the instrument tag and its input/output signal level with
its FBM, FBM point number, and CSD. All the tags for a process or system can be contained in
one or more TagList instances. For example, you may want to maintain a TagList for each major
area of your plant. IACC also allows you to export and import I/O tags to and from external
TagList files.
You can define any number of tag definitions, or types, which are used to describe the structure of
a specific tag. For example, you may want to describe tags representing an AIN block differently
than you would describe tags representing an AOUT block. Multiple tag types can exist in the
same TagList.

Figure 2-10. TagList Editor

26
2. IACC Window B0700FE – Rev A

A principal use of a TagList is to provide signal information for bulk generation of CSDs from
one or more CSD Templates. Tag attributes map each tag to an I/O block in a CSD Template
and name the target CSD. When bulk generation is invoked from the TagList Editor, IACC
creates new CSDs from the referenced templates and uses the tag values to configure the equip-
ment control block (ECBs) and I/O blocks in the new CSDs. If a CSD already exists in the IACC
database with a name matching a name used in the bulk generation, IACC replaces the existing
CSD using the selected template and TagList values. You can also specify other tag to block prop-
agation steps in addition to configuring the ECBs and I/O blocks.

Configuring Sequential Control

You can configure sequential code for batch and other applications using either Sequential Func-
tion Charts (SFC) or High Level Batch Language (HLBL). Once either SFC or HLBL has been
selected for a block, only that language can be used for the block.
The FoxSFC Editor is used for SFC. The Structured Text (ST) Code Editor and the ST Template
Editor are used for HLBL.

SFC Editor
You can access the I/A Series Sequential Function Chart/Structured Text Configurator
(FoxSFC Editor) from within IACC to create and compile code for a specific block instance. The
FoxSFC Editor application must be installed on the same computer as the IACC client.
Once you have selected the SFC Editor for a block, you can update the code only with the
SFC Editor.

Structured Text Code Editor

The Structured Text (ST) Code Editor (Figure 2-11) is a text editor built into IACC for
inputting HLBL code for sequence blocks (MON, IND, EXC and DEP).
The following IACC objects are used with the ST Code Editor:
 Sequence blocks
 ST Code items
 Text objects.
You can compile HLBL using the ST Code Editor for individual blocks, or you can compile
ST code in sequence blocks using the bulk HLBL block compiler (see “Compiling the HLBL
Code” on page 229).

27
B0700FE – Rev A 2. IACC Window

Figure 2-11. ST Code Editor

ST Template Editor
The ST Template Editor is a graphics-based editor that creates Structured Text Templates using
decisions and code blocks, code substitution, and code items (Figure 2-12).

28
2. IACC Window B0700FE – Rev A

Figure 2-12. ST Template Editor

ST Templates provide questions and responses for inserting ST code segments. The tool provides
questions and responses for value substitution in addresses, parameter names, strings, and
numeric constants. You can choose how to insert the template code into the program by copying
or linking the template by reference within the ST code itself.

29
B0700FE – Rev A 2. IACC Window

Ladder Logic Editor

Use the IACC Ladder Logic Editor to design logical control strategies using relay contact and coil
symbols (Figure 2-13). You can save and retrieve segments of ladder logic that are commonly
re-used. The ladder logic program generated by the editor is compiled, and then downloaded to a
digital FBM for execution. A programmable logic block (PLB) is the interface between the FBM
and the tasks that set and get information from the ladder. These tasks can be other control blocks
or displays.

Figure 2-13. IACC Ladder Logic

30
2. IACC Window B0700FE – Rev A

Execution Editor
The Execution Editor is a grid-based editor for viewing and editing the sequence in which
compounds and blocks are processed in a control station (Figure 2-14). The editor can be
accessed from a compound or CSD to order the execution of blocks within the CSD or within the
compound, or from a CP to order the execution of compounds that are assigned to the CP. This
editor performs a validation of the execution order, memory, and processor loading when you save
your work. Any applicable changes made to the IACC database are dynamically reflected in the
editor, ensuring you are always working with the latest information.

Figure 2-14. Execution Editor Opened for a Compound

31
B0700FE – Rev A 2. IACC Window

Control Station Loading

Control Station Loading performs predicted station loading calculations (Figure 2-15). Station
load is the total control block load for processing continuous blocks, sequence blocks, and I/O.

Figure 2-15. Control Station Loading Dialog Box

Control Station Loading provides information about station resources. The Control Station
Loading dialog boxes are identical for all stations: control processors, integrators and gateways,
and control stations. You can use Control Station Loading dialog boxes (Figure 2-15) to predict:
 Percentage of the station processor’s time being used to process control objects
and I/O
 Loading summary (% of BPC)
 Memory used in the station
 Cumulative block processor overruns.

32
2. IACC Window B0700FE – Rev A

Control Hierarchy Validation and Download

Control Hierarchy Validation
When you initiate a download operation to a control processor, IACC performs a hierarchy
validation operation to ensure the validity of the block and compound connections and
assignment to a control processor. You can perform this validity check without initiating the
download function.
Control hierarchy validation performs a series of checks on a compound hierarchy in an efficient
progression. Control validation is done prior to the download, separately or as part of the down-
load process.

Download Function
The Download function enables IACC objects to be downloaded to a control station. Object
classes that are downloaded to control stations include compounds and blocks. Typically, down-
loading the database objects to a control station is the last activity in the Control Configuration
sequence.
You can download control objects from the Plant and Network tabs in the Project Navigator. For
example, you can select a Plant Area object in the Plant tab to download all IACC objects assigned
to the area and all IACC objects assigned to the Plant Area objects nested within the selected
object.

Compare to a CP
Changes to the values of the compounds and blocks in a CP can be made by the operator or by
other applications. With the Comparison utility, you can upload the values from the CP to ensure
that the IACC configuration database matches the control database. The IACC Comparison util-
ity compares the IACC database with the CP database in the CP’s work file in its download host.
The Upload and Compare to CP command uploads the selected object configuration from the
CP to the work file prior to launching the Comparison utility.
The Comparison Utility displays a dialog box that includes two tabbed pages:
 The Comparison Utility page (Figure 2-16) compares parameter values in the two
databases and enables you to compare changes in the configuration database not yet
downloaded with the control database.
 The Bulk Upload page (Figure 2-17) displays block parameters for which the CP
database and the IACC database have different values. You can then select one or
more of these parameters and upload the CP value to the IACC database.

33
B0700FE – Rev A 2. IACC Window

Figure 2-16. Comparison Utility Page

Figure 2-17. Bulk Upload Page

34
2. IACC Window B0700FE – Rev A

Synch Utility
The Synch Utility (Figure 2-18) deals with the execution order and download states of objects in
IACC and CP. The utility identifies steps required to synchronize one database with the other.
Some steps can be accomplished automatically; others require that you make configuration
changes using other IACC functions.

Figure 2-18. Synch Status Page

35
B0700FE – Rev A 2. IACC Window

Properties Dialog Box

Properties is a grid-based dialog box (Figure 2-19) that lists parameters and their current values
for blocks and all other IACC objects. It allows you to quickly check or assign a value for a
visible parameter in the selected object. Changes in values, when applied, are indicated with
different colors and bullets in the Properties dialog box.

Figure 2-19. Properties Dialog Box for an AIN Block

System Configuration Editors

The System Configuration Editors are:
 Hardware Editor
 Software Editor
 Parameter Editor.
Use these editors to modify parameters of the hardware and software packages you have selected
for the system.

Hardware Editor
The Hardware Editor (Figure 2-20) shows all the hardware assigned to a network, node, station,
or communications interface. The Hardware Editor allows you to manipulate/configure any
hardware attributes, such as redundancy and IP addresses, and to change associations, such as
setting the host of a control processor. Most of the attributes configured in the Hardware Editor
are available in the Properties dialog box; however, the Hardware Editor allows you to change
attributes for many objects all at once, while the Properties dialog box sets attributes for one
object at a time.

36
2. IACC Window B0700FE – Rev A

Figure 2-20. Hardware Editor

Software Editor
The Software Editor (Figure 2-21) allows you to:
 Add optional software packages for each station and field module
 View the installation state of the software on the host station.
As you select hardware, the required software is automatically saved and assigned by IACC.
Depending on the station type, you can also assign optional software packages to that station.
Invoking the Software Editor displays a spreadsheet listing of all the software packages (required
and optional packages that have been assigned) for the specified piece of hardware, and, if the
hardware is a host processor, all the software for the equipment the processor is hosting.

Figure 2-21. Software Editor

37
B0700FE – Rev A 2. IACC Window

Parameter Editor
The Parameter Editor presents parameters which require the assignment of names or values
that are dependent upon your system requirements. The Parameter Editor allows you to
change/configure all the parameters in the hardware and software required for operation and
installation. These parameters include items such as hardware and software logical names, library
work volumes, names of stations for the System Monitor to watch, and baud rates for stations.
Invoking the Parameter Editor displays a spreadsheet (Figure 2-22) listing all the parameters for
the selected object. Parameters are initialized with system-wide default values that appear in the
pull-down lists in the Value column.
Most of the attributes configured in the Parameter Editor are available in the Properties dialog
box; however, the Parameter Editor allows you to change attributes all at once, while the
Properties dialog box sets attributes for one object at a time.

Figure 2-22. Parameter Editor

ListView Editor
The ListView Editor displays a spreadsheet of IACC objects associated with a given object
(Figure 2-23). When the ListView Editor is invoked for a particular IACC object (called the
primary object), the editor searches the database for any objects with the type of associations
specified by the ListView for the primary object. For example, invoking the ListView Editor for a
CSD displays all the blocks that the CSD contains.
The ListView Editor is primarily a read-only tool; however, you can perform some basic drag
operations with the objects it displays. You can also delete objects and open the Properties dialog
box.

38
2. IACC Window B0700FE – Rev A

Depending on the ListView, the following types of objects are displayed in the rows of the Editor
window, along with pertinent information about the objects:
 Object definitions and instances derived from the primary object
 Objects with parameters associated with the primary object
 Primary object itself
 Specific group of objects directly associated with the primary object, known as
collections.
The ListView Editor displays one or more of the following attributes for each object in the Editor
window:
 Names of other IACC objects to which the associated object is assigned, such as
CSDs, compounds, or control processors
 Key descriptive parameters (such as NAME, TYPE, or DESCRP), specific to the
displayed object
 Confirmation if the objects have been modified recently
 Current value of any parameter belonging to the object
 Information about the ordering of objects within a collection.
The primary object’s ListView defines which associated objects and attributes are displayed in the
ListView Editor (Figure 2-23).

Figure 2-23. ListView Editor

Additional information on ListView functions and contents can be found in IACC Help under
the ListViews topic.

39
B0700FE – Rev A 2. IACC Window

Customization Editors/Dialog Boxes

The following editors/dialog boxes are used for customizing tasks within IACC:
 Definition Editor
 Connection dialog box
 Appearance Object Editor
 FoxDraw and custom display files
 Report Template Editor
 Sheet Editor
 Toolbars dialog box.

Definition Editor
The Definition Editor (Figure 2-24) displays, in a spreadsheet format, the parameters and associ-
ated attributes of an object and allows editing of the displayed parameters. You can invoke the
Definition Editor from an object definition such as a derived block definition or a derived tem-
plate in the Library tree of the Project Navigator.
The IACC software is delivered with predefined object definitions. You cannot modify the default
values of definitions supplied with IACC; you must create a derived definition first, then override
the default values. The columns such as Data Type, Label, and Value in the spreadsheet contain
the parameter attribute values, which you can edit in a derived definition.
Figure 2-24 displays a partial view of the Definition Editor showing the tabbed parameters for a
block derived from the CALCA block definition and the object attribute columns in the defini-
tion.

40
2. IACC Window B0700FE – Rev A

Figure 2-24. Definition Editor

41
B0700FE – Rev A 2. IACC Window

Connection Dialog Box

The Connection dialog box (Figure 2-25) displays IACC block connections in a spreadsheet
format, thus allowing you to edit and delete existing IACC connections and add new connections
to objects.
Use the Connection dialog box to add or delete block connections for the following object
instances:
 Control block connections
 Equipment control block (ECB) connections
 Compound connections
 Station block connections.
IACC connections allow you to form relationships among compounds, blocks, and ECBs. Many,
but not all, IACC connections are also downloaded to the running control system, where they
become control connections. Figure 2-25 is a Connection dialog box showing the parameters for
an AIN block.
For a single parameter connection made on a CSD, IACC automatically makes other logical
connections. You can see these connections using the Connection dialog box. You can also specify
remote connections between CSDs and remote connections between compounds.

Figure 2-25. Connection Dialog Box

42
2. IACC Window B0700FE – Rev A

Appearance Object Editor

Use the Appearance Object Editor (Figure 2-26) to create and edit the appearance objects used in
graphical editors such as the CSD Editor. These appearance objects are associated with other
objects to give them a specific appearance within the editor. This generic editor also provides basic
drawing capability, allowing you to enhance the object’s various annotations such as text blocks,
text fonts, shapes with varying fill and colors, and bitmaps. You cannot modify the appearance
object for a Foxboro definition, but you can change the appearance object for a derived definition.

Figure 2-26. Appearance Object Editor and Select Parameters Dialog Box

Report Template Editor

The Report Template Editor window is used for developing a filter which determines which
IACC objects are included in an IACC report. The filter contains an expression consisting of a
series of user-defined criteria which an object must meet to be included in the associated report.
The Report Template Editor window contains five tabs, one tab for each of the four types of
criteria with which a filter expression is associated, and a tab for adding parentheses to the filter
expression. Figure 2-27 displays the Report Template Editor window.

43
B0700FE – Rev A 2. IACC Window

Figure 2-27. Report Template Editor Window

44
2. IACC Window B0700FE – Rev A

Sheet Editor
Use the Sheet Editor (Figure 2-28) to create the graphical templates, called Sheet Templates,
which are used as the backgrounds for IACC reports. You can add graphics, corporate logos,
macros, and other user-defined text to the Sheet Template using this editor. You can resize the
margins to increase or decrease the amount of space in which the report data is displayed when a
report is printed.

Figure 2-28. Sheet Editor

45
B0700FE – Rev A 2. IACC Window

Toolbars Dialog Box

The Toolbars dialog box (Figure 2-29) allows you to customize toolbars for any of the IACC
editors. You can change the appearance and size of the toolbar buttons, add or delete buttons
from a toolbar, and create your own toolbar from the set of buttons available to a specific editor.
Toolbars that you create for an editor are saved when you close the editor. Changes that you make
to the supplied toolbars do not persist after you close the editor. Refer to the Customizing Tool-
bars topic in IACC Help for additional information on creating and modifying toolbars.

Figure 2-29. Typical Toolbar Dialog Box

Security Editors
IACC provides security services that control what the current IACC user can and cannot access.
Users are required to log into IACC, at which point their access rights to the various objects,
including editors, are determined by virtue of their membership in groups. Users are organized
into groups (Figure 2-30), and a user can belong to any number of groups.

Figure 2-30. User Editor

46
2. IACC Window B0700FE – Rev A

A group is a collection of IACC users with a certain set of permissions to various aspects of IACC,
and thus to different elements of your process. You can use groups (Figure 2-31) to control each
user’s access to IACC object types, editors, and functions. You can use as many or as few groups as
you wish to control personnel access to your system, ranging from having all users be members of
a single group to having each user be the sole member of a group.

Figure 2-31. Group Editor

The Group Editor grants or denies object permissions to an object (Figure 2-32). Permissions are
associated with IACC editors and actions such as read, write, and download. If permission is
denied to a group for one of the editors, a member of that group is not able to access that editor.
Menu selections leading to that editor are grayed out in the Project Navigator for that user. If per-
mission is denied to a group for one of the functions, a member of that group is not able to per-
form that function. Picks invoking those functions are grayed out in the Project Navigator for that
user.

Figure 2-32. Permissions Window

47
B0700FE – Rev A 2. IACC Window

FoxDraw Software and Custom Display Files

IACC invokes the I/A Series FoxDraw software package that allows you to draw custom displays
for your process control system. Standard default displays for all control blocks are supplied with
I/A Series systems. Custom process displays can easily be built using the FoxDraw application and
the IACC database for process point information retrieval. The FoxDraw product must be pur-
chased and installed separately.
A display is a file that is constructed and configured to be viewed from a FoxView window. A
display can represent a plant, a process area, or a detailed portion of a process. A display can
be configured to allow operator interaction with the process by moving objects or typing
inputs. A display is composed of objects, each of which can be configured with attributes.
Using IACC and the FoxDraw application, you can create, modify, and save display files in the
IACC database. You can add a faceplate, trend, or symbol associated with a block by dragging the
object from the Project Navigator to the Editor window. You can assign and download the dis-
plays to the appropriate workstation on the network. You can assign the same display to more
than one workstation, in which case the display can be downloaded to all the stations in a single
download operation.

48
2. IACC Window B0700FE – Rev A

Utilities and Compilers

Table 2-4 describes the IACC utilities that are independent of IACC editors and can be invoked
at any time.

Table 2-4. IACC Independent Utilities

Utility Description Menu Pick

Import Imports a set of objects saved to an external file into File > Import
the IACC database associated with the open IACC
application. There are several different imports avail-
able from the Import menu in addition to the IACC
proprietary import.
Export Saves a copy of the specified objects to an external file File > Export
to create a backup file or to transfer the objects to
another IACC database. There are several different
exports available from the Export menu in addition to
the IACC proprietary export.
Find in Database Allows you to search the IACC database for objects Edit > Find in
conforming to a set of user-specified criteria. This is Database
performed in the Find IACC Object dialog box.
Where Used Allows you to locate all objects derived from or Edit > Where Used
associated directly with a selected IACC object. The or
results of a Where Used search are displayed in the Output window con-
Where Used tab in the Output window. text menu
System Options Sets checkpointing and security options, described in Tools > Options >
Chapter 12 “Security”. System Options
Error Reporting Sets the criteria and destination by which errors are Tools > Options >
reported in IACC. This is performed in the IACC Error Reporting
Options dialog box.
Backup Creates a backup file of the entire IACC database. The Tools > Backup
file can be restored using the IACC Database Admin-
istrator utility, which is accessed from outside the
IACC main window.
Audit Trail Tracks changes made to enabling and disabling Project Navigator,
security settings, adding users and groups, and System tab
modifying user permissions. Audit Trail options are set
with the System Options tab of the IACC Options
dialog box.

49
B0700FE – Rev A 2. IACC Window

Using On-Line Help

The IACC Help system uses standard Microsoft Windows Help functions.
IACC provides a main menu pick for Help topics. The Help text includes descriptions of each
IACC editor, menu selections, and the procedures to use an editor or function. The pull-down
menus and the command buttons at the top of the window are standard Windows Help system
features.

Setting IACC Options

This section describes how to use the IACC Options dialog box to enable system security, specify
error reporting levels, and set other system options. Use the IACC Options dialog box to
configure system options for the following tasks:
 “Enable System-Wide Security” on page 52
 “Configure Security Audit Trail” on page 52
 “Disable Checkpointing for Control Downloads” on page 53
 “Track Configuration Changes for 21 CFR Part 11” on page 54
 “Configure Error Reporting” on page 54
 “Change Project Navigator Display Characteristics” on page 57
 “Set the Where Used Display Option” on page 59
 “FSIM (Foxboro Simulation) Support” on page 54

NOTE
When system-wide security is enabled, only users with IACC Admin privileges can
set system options. When system-wide security is not enabled, any user can set
IACC options.

50
2. IACC Window B0700FE – Rev A

To set options:
1. Choose Tools > Options from the menu bar to open the dialog box (Figure 2-33).
The dialog box consists of three tabbed pages, each with groups of controls for various
options.

Figure 2-33. IACC Options Dialog Box

2. Set the controls as described in the following sections, and click OK.
The changes are implemented immediately.

51
B0700FE – Rev A 2. IACC Window

Enable System-Wide Security

Security in IACC is controlled by assigning users to one or more groups and then granting or
denying a group access to various editors and objects, as described in Chapter 12 “Security”.
For the security scheme currently implemented, system-wide security must be enabled from the
System Options tab.
To enable system-wide security:
1. Click the System Options tab if it is not already selected (Figure 2-33).
2. Click Enable security in the security group.
3. Click OK to set the option and close the dialog box, or click Apply to set the option
before making other changes in the dialog box.

Configure Security Audit Trail

Security Audit Trail records any changes made to the security scheme, as described in Chapter 12
“Security”.
To configure this option:
1. Click the System Options tab if it is not already selected (Figure 2-33).
2. Select one of the three options in the Security Audit Trail Level group.
None No audit trail is maintained.
Partial The following activities are logged in the audit trail:
 Modifications to system-wide security settings
 Creation of a new user or group instance
 Renaming of a user or group instance
 Deletion of a user or group instance
 All logins/logouts from IACC.
Full The following activities are logged in the audit trail in addition
to those that are logged when Partial is set:
 Addition of a user to a group
 Removal of a user from a group
 All modifications to group permissions.

3. Click OK to set the option and close the dialog box, or click Apply to set the option
before making other changes in the dialog box.

52
2. IACC Window B0700FE – Rev A

Disable Checkpointing for Control Downloads

Checkpointing saves the control station database in a checkpoint file on its host workstation. The
checkpoint file is the database saved in the form that is loaded from the host to the control station
when that station is rebooted. In the default IACC configuration, checkpointing is automatically
performed after every download procedure. However, the user Administrator can disable auto-
matic checkpointing as checkpointing can consume a significant amount of time. This feature is
intended for commissioning activities only.

! WARNING
It is not recommended that Checkpointing be disabled. If a control station is
rebooted before checkpointing is completed, the programs running in the station
do not match those in IACC. To correct the discrepancy, reload the station.

NOTE
All stations must be checkpointed before you uncheck this option.

Refer to Chapter 11 “Downloading Control Blocks” for additional information on downloading

and checkpointing.

53
B0700FE – Rev A 2. IACC Window

Track Configuration Changes for 21 CFR Part 11

IACC can be configured to update the FoxCTS application to record configuration changes for
21 CFR Part 11 compliance. In addition to the setup described in Chapter 11 “Downloading
Control Blocks”, the feature must be enabled from the System Options tab.
To enable recording of downloads by FoxCTS:
1. Click the System Options tab if it is not already selected (Figure 2-33).
2. Click the check box in the FoxCTS Integration group.
3. Use the warning interval field to specify how often a message is displayed to users
informing them that files have not yet been transferred to the FoxCTS application.
4. Click OK to set the option and close the dialog box, or click Apply to set the option
before making other changes in the dialog box.

FSIM (Foxboro Simulation) Support

FSIM (Foxboro Simulation) is a combination of an I/A control emulation package and a process-
modeling package. FSIM performs the functions that are available in the I/A Series Control Pro-
cessor. From this release, IACC can be configured to download the Compound and Blocks to the
FSIM Station.
The feature must be enabled from the System Options tab.
To enable the FSIM support:
1. Click the System Options tab if it is not already selected (Figure 2-33).
2. Click the check box in the FSIM Support Group.
3. Click OK to set the option and close the dialog box, or click Apply to set the option
before making other changes in the dialog box.
To configure the new parameter for compound/block download to FSIM station:
1. In properties of Control processor station, select the Yes option for FSIM Enable
parameter.
2. Enter the valid name in the FSIM Host available in the Hardware tab of the CP’s
Property Page.
3. FSIM_BaseOS property (Currently you can ignore this property).
When using IACC with FSIM Support, it is advisable to isolate the networks between the Simu-
lator and the main Plant Systems. If both the simulator and plant systems are on the same net-
work, it is possible to load simulator controls onto the plant system.

NOTE
Refer to the FSIM User’s Guide for details.

Configure Error Reporting

To Configure error reporting:
1. Click the Error Reporting tab (Figure 2-34).

54
2. IACC Window B0700FE – Rev A

Figure 2-34. IACC Options Dialog Box: Error Reporting Tab

As indicated by the Reporting Options group at the top of the tabbed page, you can
direct reports of system errors to three different locations:
 A text file in the C:\Temp directory with the filename listed in the Log File Name
dialog box (default is IACCError.log). You can change the name of the file, but
not its location.
 The Diagnostics tab in the Output window, even if the Output window is hidden
 A message box requiring your acknowledgement.
IACC generates four kinds of messages:
 Critical errors require your immediate attention as the error condition causes a
IACC or I/A Series system failure. Critical errors are shown in bold red type when
they are sent to an Output window tab.
 Warning is used to indicate a known bad condition that may cause a configura-
tion error. It is advisable to fix the condition before downloading the configura-
tion to the I/A Series system.
 Moderateis a seldom used level that indicates a minor problem.
 Informational messages report all system activity. Normally, Informational is
not selected for any reporting option as the output would be quite large.
The error records explain what happened to cause the error, why you were notified,
and suggest possible solutions or places to look to solve the problem.
2. Use the check boxes in the Error Types group to indicate the level of severity for errors
applied to each of the three options.

55
B0700FE – Rev A 2. IACC Window

NOTE
Error reporting is an individual user setting, not a system setting. You can change
any of these error reporting options at any time.

3. Change the name of the file, if needed, by editing the Log File Name field.
You cannot change the location of the file.
4. Specify a number in the Max. Diag. Window Errors field to limit the number of
error messages that are directed to the Diagnostic tab in the Output window.
The default is 100, but the number can be between 1 and 1000. When the maximum
number is reached, IACC discards the oldest message with each new error.
5. Specify the size of the error log file in Max. Log File Errors.
The default is 1000 messages, but the number can be between 1 and 10000. When
the maximum number of entries is reached, IACC overwrites older entries with newer
ones.
6. Click OK to set the option and close the dialog box, or click Apply to set the option
before making other changes in the dialog box.

56
2. IACC Window B0700FE – Rev A

Change Project Navigator Display Characteristics

By default, objects displayed in the Project Navigator are arranged within each node alphabetically
by object name, and each object is identified by its bitmap and object name. The IACC options
dialog box allows you to modify the display to arrange objects in the order they were created or,
downloaded objects, their order of execution. You can also specify that the display identify objects
by type and description.
To change the Project Navigator display characteristics:
1. Click the Miscellaneous tab if it is not already selected (Figure 2-35).

Figure 2-35. IACC Options Dialog Box: Miscellaneous Tab

57
B0700FE – Rev A 2. IACC Window

2. In the Tree Display Settings Group:

 Check Display object types to add type information in parentheses to the
object listings.
 Check Display object descriptions to include each object’s Descrp param-
eter in parentheses. In many instances the value of this parameter is the object
type.
Figure 2-36 shows examples of the Project Navigator with each option selected.

Figure 2-36. Object Type Displayed (left) and Object Description Displayed (right)

 Check Disable Sorting to display objects in the order they were added to the
IACC database.
Figure 2-37 shows examples of the Project Navigator with sorting enabled and
disabled.

58
2. IACC Window B0700FE – Rev A

Figure 2-37. Plant Tab with Sorting Enabled (left) and Sorting Disabled (right)

3. Click OK to set the option and close the dialog box, or click Apply to set the option
before making other changes in the dialog box.

Set the Where Used Display Option

To set the Where Used option:
1. Click the Miscellaneous tab if it is not already selected (Figure 2-35).
2. In the Where Used Option Settings group:
 Check Process Object displays to include connections to display objects
 Uncheck Process Object displays to exclude them.
3. Click OK to set the option and close the dialog box, or click Apply to set the option
before making other changes in the dialog box.
Including all block connections provides more information in Where Used displays, but it may
add to the time it takes IACC to complete a Where Used search.

Property Page Settings

The Show Descriptive Text option in the Property Page Settings enables descriptions of parame-
ters displayed in the Properties dialog boxes. Figure 2-38 shows the changes made to a Properties
dialog box for block when you select this options. Descriptive text has been added to the values in
the Period and Propt parameters.

59
B0700FE – Rev A 2. IACC Window

Figure 2-38. Descriptive Text Added to Properties Dialog Box

Live Data Settings

The Live Data Settings group is used for specifying an I/A Series workstation as a source for live
data. The function is used in ALDs as described in “Animated Loop Drawings” on page 329.
To select and specify a workstation for live data:
1. Click Options to open the Animated Live Diagram dialog box.
2. Use the Host pull-down list to select the workstation.
3. Click Test Host to test the connection between IACC and the workstation.
4. Close the dialog boxes when the connection has been confirmed (Figure 2-39).

60
2. IACC Window B0700FE – Rev A

Figure 2-39. Confirming a Live Data Connection

61
B0700FE – Rev A 2. IACC Window

62
3. Using IACC
This chapter describes an overview procedure for quickly learning how to use the IACC tools to
configure a control strategy for your application.
The instruction sequence in this chapter is designed to familiarize you with the major steps
required to configure a system. It covers the principal IACC functions, starting with defining
Plant Areas, and concluding with the documentation features of IACC. Because of the overall
capability and flexibility of IACC, the sequence presented is not the only sequence that can be
used. If you are not starting with a fresh database, the station, node, and other names (S00001
through S00003) are different than those listed in the text.
This chapter includes the following topics:
 “Getting Started Sequence” on page 63
 “Control and System Configuration” on page 64
 “Downloading the Database” on page 82
 “Printing and Documentation” on page 84
 “Importing/Exporting the Configuration Database” on page 84
 “Protecting the Database” on page 85.

Getting Started Sequence

The engineering sequence in this chapter configures an I/A Series system with control blocks.
These steps, defined by sections in this chapter, include:
 Defining Plant Areas
 Creating a compound
 Creating a CSD
 Creating and connecting I/A Series control blocks
This section does not describe the blocks that implement sequential control or
ladder logic. These are covered in Chapter 7 “Sequence Blocks” and Chapter 8
“Ladder Logic”, respectively.
 Creating hardware and software (system configuration)
System configuration can be performed at any time prior to assigning equipment
control blocks (ECBs) to the CSD.
 Validating the system configuration
 Creating a Commit diskette
 Assigning the I/A Series control blocks to a compound, the compounds to a control
processor, the CPs to a host, and the displays to a workstation
 Assigning ECBs to the CSD

63
B0700FE – Rev A 3. Using IACC

 Building and loading displays

 Scheduling block and compound execution periods
 Validating and downloading the control database to the control processor
 Checkpointing the CP
 Comparing the downloaded database.
You can print reports or configure security access functions at any time during the development of
or after completing the control configuration, but you should also save your configuration
database frequently.
To make a backup:
 Choose Tools > Backup from the menu bar.
Refer to Chapter 15 “Managing IACC Databases” for information on file backup and
restoration.
In I/A Series systems, you must use unique names for:
 All blocks within the same compound
 All compounds
 All letterbugs.
You may use the same name for blocks assigned to different compounds.
You can change the default name of any template, block, compound, or any IACC configurable
item, by right-clicking on the object and selecting Rename.

Control and System Configuration

Defining Plant Areas
The Plant Area tab allows you to organize configuration information in a way that makes sense for
your plant and is most convenient for you.
To define a Plant Area:
1. Click the Plant tab in the Project Navigator.
2. Right-click the Plant object at the top of the Project Navigator and choose New
Plant Area from the pop-up menu.
IACC inserts Plant Area1 under the Plant object. The object is enclosed in a rectangle
indicating that you can edit the name.

64
3. Using IACC B0700FE – Rev A

3. Type North over the highlighted object and press Enter.

4. Right-click North and choose New > Plant Area from the pop-up menu.
IACC creates Plant Area1 under Plant > North.
5. Rename the object Train01.
Figure 3-1 shows the new Plant Area objects in the Project Navigator.

Figure 3-1. Plant Area Objects

Note that you can also create CSDs, compounds and display files from the Plant tab. The objects
are automatically associated with the appropriate objects in the System tab, and assigned to the
selected Plant Area.

Creating a Compound for Blocks

To create a compound:
1. Right-click Train01 and choose New > Compound from the pop-up menu.
This creates a new compound with the default name COMPND1 in the Project
Navigator. The object is enclosed in a rectangle indicating that you can edit the name.
2. Press Enter to accept the default name.

65
B0700FE – Rev A 3. Using IACC

Creating a CSD for Blocks

The CSD Editor is a graphics-based editor from which you configure control loops for control
strategies.
To create a CSD:
1. Right-click Train01 and choose New > CSD > Simple CSD from the pop-up menu.
This creates a new CSD with the default name Simple CSD1 and assigns the CSD to
the Plant Area. The object is enclosed in a rectangle indicating that you can edit the
name.
2. Press Enter to accept the default name.
Figure 3-2 shows the compound and CSD added to Train01.

Figure 3-2. Compound and CSD added to a Plant Area Object

Creating I/A Series Control Blocks

You develop control loops in the CSD using I/A Series blocks.
To create I/A Series control blocks in the CSD:
1. Double-click Simple CSD1 to open the CSD Editor in the Editor window.
2. Use the pull-down list in the Palette window to select Input/Output
(Foxboro Palettes).
3. Drag the AIN block from the Palette into the left side of newly created Simple CSD1
in the Editor window.
4. Drag the AOUT block from the Palette into the right side of Simple CSD1.
5. Use the pull-down list in the Palette window to select Control (Foxboro Pal-
ettes).

66
3. Using IACC B0700FE – Rev A

6. Drag the PIDA block to the center of Simple CSD1 in the Editor window.
Figure 3-3 shows how the new blocks are displayed in the Project Navigator under
Simple CSD1 and in the CSD Editor.

Figure 3-3. Blocks Added to Simple CSD1

NOTE
You can also drag and drop blocks from the Project Navigator into the CSD Editor.
The block definitions are listed under Library in the System tab.

Figure 3-4 identifies the parts of the block appearance object using I/A Series control blocks.

Block Name

Port Area Port Area

Information Area

Text Area
Figure 3-4. PIDA Appearance Object

67
B0700FE – Rev A 3. Using IACC

Connecting Blocks
You connect input/output parameters of blocks in the CSD Editor.
To connect block parameters:
1. In the CSD Editor window, move the cursor over the PIDA1 block parameter Out.
The cursor changes to indicating the parameter is connectable.
2. Drag the cursor to the Meas parameter of the AOUT1 block.
 If the connection is valid, a line appears between the two parameters, with an
arrow indicating the direction in which data travels.
 If you move either of the blocks around, the line representing the connection
adjusts itself.
3. Move the cursor over the AIN1 block parameter named Pnt.
The cursor changes to .
4. Drag the cursor to the Meas parameter of the PIDA1 block.
5. Save the CSD by selecting File > Save.
Figure 3-5 shows an example of the CSD Editor window with the three selected I/A Series
control blocks.

Figure 3-5. Sample CSD with Three Connected Blocks

If the name of the parameter to which you want to connect does not appear on the appearance
object of the block in the CSD Editor window, you can use the Select Parameters dialog box
(Figure 3-6) to display the parameters.

68
3. Using IACC B0700FE – Rev A

To display block parameters:

1. Right-click anywhere within the PIDA block and choose Select Parameters from
the pop-up menu to display the Select Parameters dialog box (Figure 3-6).

Figure 3-6. Select Parameters Dialog Box

2. Check Configurable in the Parameter Attributes column to display only configu-

rable parameters.
3. Scroll the list of parameters to find the Hsco1 parameter.
4. Drag the Hsco1 parameter to the port section of the PIDA1 block in the CSD Editor
window.
The parameters that have been exposed are shown in the port portion of the block on
the CSD Editor. You can select and add parameters, as required, for each block shown
in a CSD.
5. Select Close.

69
B0700FE – Rev A 3. Using IACC

Creating Hardware and Software Objects

You must create and assign hardware and software objects so that the software install program
knows what software programs to install for each system module. You create hardware/software by
selecting items from the Project Navigator and related dialog boxes. This example configures a
single application workstation with a printer and a CP40 with two FBMs.

Creating a Station and Control Processor

To create a workstation and a control processor:
1. Click the Network tab in the Project Navigator window (Figure 3-7).

Figure 3-7. Configuration Object in the Network Tab

2. Right-click Configuration and choose New > Network from the pop-up menu.
3. Click NODE (Nodebus) in the Create Network dialog box and click OK.
A new Nodebus (N00001) is created under Configuration in the Project Navigator.
4. Press Enter to accept the default name.
5. Right-click N00001 and choose New > Station to open the Create Stations dialog
box.
6. Click the AW70 check box and the CP4B check box.
Leave the count on the right at one each.

70
3. Using IACC B0700FE – Rev A

7. Click OK.
A new AW70 station (S00001) and its required software and peripherals and a CP40B
(S00002) and its required software and any peripherals are created under the Node
object in the Project Navigator. Notice that software packages are named by the soft-
ware package name, followed by the name of the station to which they belong.
The software created for the CP40B includes two I/A Series compounds:
S00002_STA, which contains the Station block for monitoring the CP’s operation,
and S00002_ECB, which holds Equipment Control Blocks (ECBs) for Fieldbus
devices that are added to the CP.
S00002 is highlighted indicating that you can edit the name.
8. Type CP40AA over the highlighted name and press Enter.
9. Right-click S00001 and choose Rename from the pop-up menu so that the worksta-
tion name can be edited.
10. Type AW70AA over the highlighted name and press Enter.
Figure 3-8 shows the two stations and their software packages.

Figure 3-8. Software for the Configured Workstation and the CP

71
B0700FE – Rev A 3. Using IACC

Creating Peripherals
A monitor, keyboard, and mouse were created automatically for the workstation. This sequence
adds a printer to show how other peripherals are added:
1. Right-click AW70AA and choose New > Peripheral to open the Create Peripherals
dialog box.
2. Select P136P (Parallel Dot Matrix 136) and click OK.
The new peripheral (P00001) and associated software are created under the station
AW70AA in the Project Navigator.
3. Press Enter to accept the default name.

Creating Software
Every node must have the Compound Summary Access (CSA) application installed on one
station. Additionally, System Monitor software should be installed on at least one workstation on
every node.
To add these two software packages:
1. Right-click AW70AA and choose New > Software Package to open the Create Soft-
ware dialog box.
2. Click ASMON7 (System Monitor package for AW70s) and ACSA7 (Compound Sum-
mary Access package for AW70s), and click OK.

NOTE
There can only be one CSA instance on a node. There can be multiple workstations
with System Monitor.

The new software packages ACSA7_AW70AA and ASMON7_AW70AA are created under
the Station in the Project Navigator.

72
3. Using IACC B0700FE – Rev A

Checking and Adding Parameters

To review and modify installation parameters for the workstation:
1. Right-click AW70AA and choose Editors > Parameter Editor from the pop-up
menu to open the Parameter Editor (Figure 3-9).

Figure 3-9. Parameter Editor Opened for AW70AA

2. Click the Assignments tab at the bottom of the Editor window.

Values for some of the parameters on the Assignments page, such as AP Logical Name,
are automatically supplied by IACC, but can be changed. Other parameter values,
such as System Monitor Name, must be entered.
3. Make the necessary entries to set these parameter values:
 System Monitor Name: SYSMON1 (as shown in Figure 3-9)
 AP Logical Name: AW70AA
 WP Logical Name: WP70AA.

73
B0700FE – Rev A 3. Using IACC

4. Click the References tab at the bottom of the Editor window (Figure 3-10).

Figure 3-10. References Tab in the Parameter Editor for AW70AA

5. Use the pull-down list in the Value column to set these parameters:
 Priority 1 Printer 0: LP00
 Station to Monitor 0: AW70AA
When you enter a value for Station to Monitor 0, IACC inserts a line for Station
to Monitor 1. When you enter a value for that parameter, Station to Monitor 2 is
inserted, and so on.
 Station to Monitor 1: CP40AA
 Ctrl and IO Library Volume: volwrk
 Logical Host Letterbug: AW70AA
 Parallel Port Logical Name: LP00
6. Enter WP70BB for WP Message Backup.

74
3. Using IACC B0700FE – Rev A

Selecting FBMs
To add FBMs to the CP40B:
1. Right-click CP40AA and choose New > Fieldbus Module to open the Create Fieldbus
Modules dialog box.
2. Click the FBM01 (0-20 mA Input) and FBM04 (0-20mA Input/Output) check boxes,
and click OK.
Two new FBMs (F00001 and F00002) are created under the CP40AA. F00002 is
highlighted indicating that the name can be edited.
3. Type AOUT01 over the highlighted name and press Enter to rename the FBM04.
4. Right-click the F00001 and choose Rename from the pop-up menu.
5. Type AINP01 over the highlighted name and press Enter to rename the FBM01.
You can create additional equipment by repeating the appropriate steps in “Creating Hardware
and Software Objects” on page 70. The network tree you created in the Project Navigator should
appear as shown in Figure 3-11.

Workstation Software

Peripherals

FBMs
Compounds
CP Software

Figure 3-11. Network Tree

75
B0700FE – Rev A 3. Using IACC

Validating the System Configuration

Validating the system configuration verifies the installability of the hardware and software
contained in the configuration. If the configuration cannot pass the configuration check, you may
still be able to produce a Commit diskette for software installation, but you should fix all errors
before committing the configuration.
To validate the system configuration:
1. Change to the Network tab.
2. Right-click Configuration and choose Validate/Download > Validate from the
pop-up menu.
3. Check Installation Parameters in the Validate Hardware/Software Configura-
tion dialog box and click Next.
A Validating dialog box displays the message “All Validations Done”.
4. View any errors in the Output window (Figure 3-12).

Figure 3-12. Validation Dialog Box and Output Window with Related Tab

In normal operation, you return to the appropriate procedure to correct all errors and
then rerun the Validate procedure.
5. Click Done to exit the Validate Configuration.

76
3. Using IACC B0700FE – Rev A

Creating a Commit Diskette

To create a Commit diskette:
1. Right-click Configuration and choose Validate/Download > Download from the
pop-up menu.
2. Check Installation Parameters in the Validate Hardware/Software dialog box
and click Next.
3. Click Next in the Validating dialog box.
4. Check Commit Diskette in the dialog box and click Next.
If there are errors in the configuration, IACC displays the Validation Checks
dialog box.
 Click Ignore if you are following these instructions as a training exercise.
 Click Cancel and fix the errors if you are preparing a Commit diskette for an
actual installation.
5. Click Start in the Hardware/Software Commit dialog box.

NOTE
At this point, you can install the I/A Series system using the Commit diskette and
then reconcile the system configuration with the IACC database, as described in
“System Installation and Reconciliation” on page 138. If this is an actual installa-
tion, you must have a media distribution diskette #10091 to insert in the diskette
drive. If you are only following the tutorial, click Ignore in the information box
concerning the #10091 diskette.

6. Click Ignore in the information box.

7. In the Downloading dialog box, click Next.
8. In the Insert diskette dialog box, click OK.
9. Insert an empty diskette in the diskette drive, and click OK in the Hardware Software
Commit dialog box.
10. Click Done.
The next steps in an actual configuration sequence involve loading the software onto the
AW70 using the Commit diskette and the Software Install program. As part of the process, you
would create a Reconcile diskette, which you can use to update the installation status of the con-
figuration in the IACC database. These steps are discussed in Chapter 4 “System Configuration”.

Assigning CSDs and Compounds

Before downloading the control configuration to the I/A Series system, you must assign the blocks
in the CSDs to compounds, compounds to a CP, and displays to a workstation. Under its appro-
priate tree branch, the Project Navigator shows the CSDs and blocks assigned to the compound,
the compounds assigned to CPs, and the displays assigned to workstations.

77
B0700FE – Rev A 3. Using IACC

You can assign individual blocks or all blocks in a CSD to a compound from the CSD Editor
window using a menu function, from the Project Navigator tree structure using a menu function,
or you can use drag and drop techniques. The menu selections are described here.
To assign all control blocks in Simple CSD1 to a compound:
1. Right-click Simple CSD1 and choose Assign Default Compound from the pop-up
menu.
2. Select COMPND1 in the Assign Default Compound dialog box and click OK.
This assigns all the blocks in Simple CSD1 (and any new blocks added later) to
COMPND1.
To assign a compound to a CP:
1. Right-click COMPND1 and choose Assign to Control Station from the pop-up
menu.
2. Check CP40AA in the Assign Compound to Control Station dialog box and click OK.
This assigns COMPND1 and all its blocks to the CP40 CP40AA. You can also assign
a compound to a CP by dragging the compound to the CP in the Project Navigator.
Figure 3-13 shows the how the results of the CSD and compound assignments are
displayed in the Plant and Network tabs.

Figure 3-13. Display of CSD and Compound Assignments in the Project Navigator

78
3. Using IACC B0700FE – Rev A

Assigning ECBs to a CSD

Before FBMs can be used in the control scheme, their associated equipment control blocks
(ECBs) must be assigned to a CSD to identify field connections to the I/O blocks. In IACC, this
involves adding the ECBs to the CSD and then connecting the ECBs to I/O blocks.

Adding ECBs to a CSD

To add ECBs to a CSD:
1. Click the Plant tab at the bottom of the Project Navigator.
2. Double-click Simple CSD1 to open the CSD Editor window.
The CSD Editor shows the three existing blocks: AIN1, PIDA1 and AOUT1.
3. Click the Network tab and expand N00001 > CP40AA > CP40AA_ECB to display the
ECBs that represent the FBMs (AINP01 and AOUT01 in Figure 3-14).

Figure 3-14. Adding ECBs to a CSD

4. Drag AINP01 into the left side of the Simple CSD1 in the Editor window
(Figure 3-14).
5. Drag AOUT01 into the Simple CSD1 to the right side of the Simple CSD1 in the
Editor window (Figure 3-15).

79
B0700FE – Rev A 3. Using IACC

Associating FBM Points with CSD Blocks

To associate FBM points with the I/O blocks in the CSD:
1. Connect the Input_1 parameter from the AINP01 (ECB1) block to the From_Fld1
parameter in the AIN block, as described in “Connecting Blocks” on page 68.
This connects the signal from the FBM to the analog input signal.
2. Connect the To_Fld1 parameter of the AOUT block to the Outpt_5 parameter from
the AOUT01 (ECB2) block.
The channel number (PNT_NO), device ID (DEV_ID) and IOM_ID parameters on
the AOUT and AIN blocks were automatically updated with the proper information
when the connection to the ECB was made. The CSD should now look like
Figure 3-15 showing the I/O points of the ECB as they relate to blocks in the loop
drawing.

Figure 3-15. Simple CSD Showing ECB Input/Output Points Connected to Blocks

80
3. Using IACC B0700FE – Rev A

Building Displays
You can build custom displays using FoxDraw software at any time, but it is usually easier to build
the display files after you have completed creating your control loops in the CSDs because the
object attributes for connecting displays are available in the IACC database. After building your
custom displays, you need to assign and download the displays to a workstation.
To build displays using FoxDraw software:
1. Click the Plant tab in the Project Navigator.
2. Right-click Train 1 and choose New > Display File from the pop-up menu.
Display Files1 is added under Train 1.
3. Double-click Display Files1 to open to FoxDraw Editor.
To build, assign, download, and import displays, refer to Chapter 10 “Creating Displays”.
To assign the display to the AW70:
1. Right-click Display Files1 and choose Assign to Workstation from the pop-
up menu.
2. Select AW70AA in the Assign to Workstation dialog box, and click OK.

Block and Compound Execution

The sequence of the blocks, within the compound, sets the order of their operation in the CP.
Block processing can be reordered.

Block Sequencing
To check the sequence in which blocks are executed:
 Double-click COMPND1 to open the Execution Editor.
For this example, keep the default Period (1) and Phase (0). Figure 3-16 shows the
Block and Control Level Execution Editor. In normal operation, you can change a
block value or choose to remain with the assigned default values.

Figure 3-16. Block Level Execution Editor

81
B0700FE – Rev A 3. Using IACC

Compound Sequencing
To check the sequence in which compounds are executed:
1. Click the Network tab.
2. Right-click CP40AA and choose Editors > Execution Editor from the pop-up
menu to open the Execution Editor.
The Execution Editor shows COMPND1 and other compounds that have been assigned to the
CP. The compounds are executed in the order in which they appear in the editor, and according
to the Period and Phase parameters.

Downloading the Database

The Download function transfers the database control block configuration to the CP. The transfer
of the control blocks into a CP can be performed either on individual blocks or for all blocks in a
compound. Using the download function, you can:
 Download individual compounds or blocks to the CP
 Download all the blocks in a CSD to the CP
 Download the blocks in all CSDs created from the same CSD Template
 Download an entire database for a control processor
 Download a Plant Area and all configuration objects that have been assigned to
the area.
For simplicity, only the Download procedure for an entire database to a control processor is
shown. Refer to Chapter 11 “Downloading Control Blocks” for additional information about
downloading individual blocks, CSDs, compounds, or Plant Areas.

Downloading an Entire Database to a Control Processor

To download a database to a control processor:
1. Click the Network tab and expand the tree to display CP40AA.
2. Right-click CP40AA and choose Validate/Download > Download.
3. At the Validating dialog box, click Next.
Successful completion or error condition messages are displayed in the Output win-
dow. During normal operation, you correct the detected errors and repeat the valida-
tion/download procedure.
4. Click Cancel.

82
3. Using IACC B0700FE – Rev A

Checkpointing the CP
Checkpoint saves the station database in a checkpoint file on its host workstation. When the CP
is rebooted, the checkpoint file is downloaded to the CP. Normally, the Download process per-
forms a checkpoint upon completion. However, the CP Checkpoint command is available to
allow you to perform a checkpoint on demand.
To perform a CP checkpoint:
1. Click the Network tab and expand the tree to display CP40AA.
2. Right-click CP40AA and choose Validate/Download > CP Checkpoint.

Comparing Blocks in the CP to the IACC Database

Changes to the values of the compounds and blocks in a CP can be made by the operator or by
other applications. With the Comparison utility, you can upload the values from the CP to ensure
that the IACC configuration database matches the control database. The IACC Comparison util-
ity compares the IACC database with the CP database in the CP’s work file in its download host.
The Upload and Compare to CP command uploads the selected object configuration from the
CP to the work file prior to launching the Comparison utility.
To compare a control block in IACC to a block in the control database:
1. Do one of the following:
 Click the Network tab at the bottom of the Project Navigator, right-click CP40AA,
and choose Compare To CP from the pop-up menu to open the Compare Utility
window without updating the work file.
 Click the Network tab at the bottom of the Project Navigator, right-click CP40AA,
and choose Upload and Compare To CP.
2. In the Comparison tree, expand CMPND1.
3. Click on a control block to observe the value in the CP’s work file and the IACC value
for each parameter.
If the values are not the same, you can synchronize the two by doing one of the
following:
 Click Update IACC to upload the CP values to the control block in the IACC
configuration database.
 Download the block from IACC to the I/A Series system.
4. Compare other blocks.
5. At the Comparison Utility dialog box, click Close.

83
B0700FE – Rev A 3. Using IACC

Printing and Documentation

The IACC software can print drawings to any printer to which your workstation has network
access. Each editor has its own unique way of displaying and printing objects within the
configuration. Data from any editor can be immediately printed on a qualified Windows
compatible graphic printer.
Reports are printed in the following formats:
 All reports are printed using a what-you-see-is-what-you-get (WYSIWYG) format.
 Tabular editors typically display objects as rows of data in a spreadsheet format. Their
contents are printed in a row/column format.
 Sheet Templates for both graphical and tabular reports allow printouts to have
pre-defined borders and annotations (for example, company logos) including time
and date of report, report name and name of user generating the report. You can
create your own Sheet Templates by creating a new one from scratch, or copying the
contents of an existing Sheet Template into a new one.
You can print reports using predefined print specifications. Print specifications specify paper sizes,
orientation, type of printer, and the Sheet Template to be used during printing.
Print Preview is available for all forms of reports. Print Preview allows you to page through the
report and review its contents and layout prior to printing the actual report.

Importing/Exporting the Configuration Database

The import functions allow you to import: The export functions allow you to export:
 IACC format  IACC format
 Save/SaveAll  Save/SaveAll
 SysDEF Exports  TagList Agent
 TagList Agent
 Displays.

You can import any custom set of objects saved during an IACC export into the current IACC
configuration database. Refer to Chapter 15 “Managing IACC Databases” for additional
information.

84
3. Using IACC B0700FE – Rev A

Protecting the Database

To help you protect the integrity of the project database, IACC software includes a separate
utility that enables you to back up, restore, and verify IACC databases. The IACC Database
Administrator utility can be invoked from the IACC main window for backup, and from Explorer
for all three functions. See Chapter 15 “Managing IACC Databases” for details on using this
facility.
When the utility is started from the IACC window, only the backup option is active. Database
restoration and verification can be done only off-line; no user can be logged into target IACC
databases.

Backing Up the Database

To back up the currently open IACC database:
1. Choose Tools > Backup from the menu bar.
IACC opens the IACC Database Administrator dialog box with only the Backup and
Exit buttons active.
2. Click Backup.
3. Click OK when the utility displays a warning that all editors are closed before the
backup starts.
An Enter backup file dialog box prompts you to enter the location and name of the
backup file. The default backup filename uses the following format to indicate the
date and time the backup was made:
IACC_<mmddyyyy>_<hhmm>.bdb
4. Enter the name and location and click Save, or simply click Save to accept the
default name and location.
The utility displays an information box when the backup is finished (Figure 3-16).

Figure 3-17. IACC Database Administration Dialog Box

5. Click OK to close the information box and exit the utility.

85
B0700FE – Rev A 3. Using IACC

86
4. System Configuration
This chapter describes how to configure hardware and software for installation of the
equipment.
Configuration within IACC is the process by which you:
 Define hardware and software of a control strategy (system configuration)
 Develop control loops of the process (control configuration)
 Assign hardware, software, and control configuration database to a host
 Verify and download the configuration database to the CPs.
IACC is a flexible tool and can conform to your needs for configuring a process control system.
IACC does not require you to use a single rigid sequence when building this scheme. You can
begin by selecting whether or not you want to:
 Configure security
 Configure hardware and software
 Configure control.
Once security, system, and control have all been configured, you must validate and download the
database, as described in Chapter 11 “Downloading Control Blocks”.
This chapter deals with system configuration and covers the following topics:
“Planning” on page 88
“Importing System Definition Data” on page 91
“Creating an I/A Series V8.x System” on page 95
“Network Equipment” on page 101
“Creating Stations and Processors” on page 104
“Selecting Peripherals” on page 107
“Adding Fieldbus Modules” on page 113
“Creating Software Objects” on page 125
“Assigning Hardware Objects” on page 127
“Committing the Configuration” on page 132
“System Installation and Reconciliation” on page 138.

NOTE
If you are using IACC to configure FOUNDATION fieldbus H1 devices on the
I/A Series system, you must also install Field Device Manager software. This FDT
editor is opened from within IACC, and provides comprehensive management of
field devices including configuration, commissioning and calibration, maintenance
and troubleshooting. For additional information about Field Device Manager, refer
to Implementing FOUNDATION fieldbus on the I/A Series System (B0700BA).

87
B0700FE – Rev A 4. System Configuration

Planning
Before beginning system and control configuration using IACC, you should develop process and
instrumentation (P&I) drawings for your control strategy. From these drawings, you can deter-
mine the following:
 All the field inputs and outputs of your process and the types of signals they carry
 The types and quantity of equipment that supports your field I/O points and control
the entire strategy
 The point numbers on each Fieldbus Module (FBM) with which an I/O point is to be
associated
 The best method by which to execute the control portion of your strategy
 The compounds to which the control blocks of the process are assigned, and the name
of each compound
 The CP sizing for the control software.
Once you have developed the control strategy in your process and instrumentation drawings, you
can implement it in IACC.

! WARNING
Do not configure a CP and its compounds in more than one IACC database.

Security Configuration
You may choose to begin implementing your control strategy in IACC by configuring security.
IACC is shipped with one predefined user, “Administrator.” There is no password assigned to this
user by default. Administrator is a super-user with unlimited access to all the functions and edi-
tors of IACC. Unless a password is set for Administrator at this point, all personnel have full
access to the software through the Administrator identity.
You can continue to build your configuration using the Administrator identity and return to con-
figure security in the future. Security may be partially or completely configured at any time. If you
wish to configure security at this point, your first step should be to assign passwords or permis-
sions for each IACC user. See Chapter 12 “Security” for details on configuring security.

System and Control Configuration

Based on the information in your P&I drawings you may begin with either control configuration
or system configuration. In either case, you need not have your plant operational or physically
constructed to begin configuration with IACC. You can configure the system and its control
scheme before the I/A Series system is installed and operational in any process control
environment.
The following are some advantages of starting with system configuration:
 The hardware is defined and available for assigning compounds to host stations.
 The FBM definitions are available for connection in CSDs and to input into TagLists.
 The hardware is logically organized (network to station) in the Project Navigator
Network tab, reducing the need to later organize the system objects in the Network
tab.

88
4. System Configuration B0700FE – Rev A

The following are advantages of starting with control configuration:

 You develop a better understanding of the hardware needed to control the proposed
system.
 You can begin to build custom process control displays after your loops are built.

Overview of System Configuration

Prior to configuring the hardware and software, a preliminary plan should be drawn that shows all
required hardware devices and peripherals, their locations, and the distances between the devices
based on the requirements of the process environment. Figure 4-1 shows the interrelationships of
the configurable hardware items of a sample I/A Series system.
Only those hardware objects that require a letterbug assignment and the software that is loaded on
each such item during software installation are considered during system configuration. All other
items are ordered and specified during the system ordering process. When a hardware item is con-
figured, a standard software package is also automatically configured and assigned to that equip-
ment by IACC.
The overall architecture of the I/A Series system consists of a number of logical domains as
illustrated in Figure 4-1, as follows:
 Enterprise Domain — the interface to corporate networks
 Application Domain (or Application Network) — the top-level network through
which the operators and control software interface to the field-level equipment
 Control and I/O Domain (or Control Network) — the mid-level network which is
responsible for monitoring and directly operating the field-level I/O points.

89
B0700FE – Rev A 4. System Configuration

Enterprise Domain
(To Corporate Network)

To/From
Other Node(s)

WP70 Alarm Serial Printer AW70 Parallel Printer

LAN
Interface
Application
AW70 Network

Nodebus

To Other CPs
or Integrators
CP CP CP CP
30/ 30/ 60 60
Control 40 40
Y-Module
Network Or
FBMs

FCM10E

FCM10E
FBM0 xx
FBM0xx

FBM0xx

FBM0xx

FBM0xx

FBM0xx

Isolator
Y-Module
FBMs DIN Rail
Mounted FBMs
FBM1xx

FBM1xx

FBM1xx

FBM1xx

FBM1xx

FBM1xx

FBM2xx

FBM2xx

FBM2xx

FBM2xx

FBM2xx

FBM2xx
To field devices
(measurement instruments)

To field devices
(measurement instruments)

Figure 4-1. Hardware in a Sample I/A Series System

You can begin by creating the hardware and software objects that you are planning to use in your
I/A Series system. Hardware configuration in IACC is performed from the Network tab of the
Project Navigator. Control configuration can be performed before, after, or simultaneously with
system configuration, but the two must come together at some point.
System configuration can either begin at the network or workstation level and result in the cre-
ation of FBMs (“top-down” configuration), or it can begin at the FBM level and result in the
creation of workstations or a network (“bottom-up” configuration).
The following are some advantages of top-down configuration:
 Makes hardware assignments in the Network tree of the Project Navigator easier
 Allows you to concentrate on just the hardware and software before developing the
control configuration.
The following are some advantages of bottom-up configuration:
 Allows you to begin by specifying only the FBMs required in a system, allowing you
to then include the FBMs in CSDs and TagLists.
 Allows you to specify inputs and outputs based on loops you know you need for early
development of complete control strategies.
The procedures detailed in this chapter define both the hardware to be used in the control
strategy and the software to be installed. The sequence concludes with creating a Commit diskette

90
4. System Configuration B0700FE – Rev A

which is used to load the configuration on the I/A Series processors. Once this configuration has
been loaded, you can download control databases using a network connection.
The most expedient way to configure system is to start with Configuration in the Network tab
and perform the configuration from the top down. A network and hubs/switches are optional;
they are not required for stand-alone systems. Other items also may be optional. The recom-
mended sequence for object creation is as follows:
 Create a network
 Add network components (switches and hubs)
 Choose stations
 Select additional peripherals (if needed)
 Create processors
 Configure communications interface as needed for FBIs and FCMs
 Add FBMs
 Select software (if needed)
 Assign and link objects.
After you create the system objects, you must change their default names to the names
(letterbugs) configured on the hardware. Failure to do so results in problems during the attempt
to create a valid Commit diskette.
The procedures in this chapter include supplemental information to assist you in making the
most viable choices when defining hardware for your system. It includes material such as
descriptions, network requirements, and valid combinations. For more information, refer to:
 Site Planning (B0193AB)
 System Equipment Installation (B0193AC)
 PSSs listed in System Product Specifications Sheet (PSS) Hierarchy (PSS 21A-0A1-D1).
In IACC, available selections for system configuration vary according to the object for which they
are being created. For example, the Create Stations dialog box opened from the Configuration
object lists more than 30 different workstations, control stations and integration devices. When
the same dialog box is opened from a switch on The Mesh Control Network only three stations
are listed.

NOTE
For recovery purposes, back up your entire configuration database frequently.
See Chapter 15 “Managing IACC Databases”.

Importing System Definition Data

IACC allows you to import system configuration information from an I/A Series system using
SysDEF Export disks created with the System Definition configuration application.
You can only import a SysDEF Export file to an empty IACC database. If the database already has
system configuration information, the import function displays the following message:
Configuration is not empty - import cannot proceed.

91
B0700FE – Rev A 4. System Configuration

! CAUTION
Deleting all objects from a database does NOT create an empty database. Network
address assignment history survives the deletions and causes problems on the
SysDef import. Only import to an empty database.

If the target database is not a brand new, empty database:

1. Create another database as described in “Setting Up Multiple Databases” on page 396.
2. Import the SysDEF information to the new database.
3. Update the configuration as needed and export the configuration using the
IACC format.
4. Import the configuration to the target IACC database.
IACC does not support export of system configuration to a SysDEF Export disk.
To import from a SysDEF Export disk:
1. Insert the SysDEF Export disk in the diskette drive.
2. Choose File > Import from the menu bar to open the Available Formats dialog box
(Figure 4-2).

Figure 4-2. Selecting a SysDEF Diskette in the Available Formats Dialog Box

92
4. System Configuration B0700FE – Rev A

3. Select Import SysDEF Export and click Next to open the Select Drive dialog box
(Figure 4-3).

Figure 4-3. Select Drive Dialog Box for a SysDEF Export File

4. Use the pull-down list to select the diskette drive, and click Next.
The Verify dialog box displays the type of import and the location of the file
(Figure 4-4).

Figure 4-4. Verify Dialog Box

5. Click Next in the Verify dialog box.

The Import dialog box and the Output window display progress messages and errors
during the import.
6. Click Finish when the Import dialog box indicates that the import is complete.

93
B0700FE – Rev A 4. System Configuration

7. Review the SysDEF Import Log File in the Output window (Figure 4-5) for any
errors.

Figure 4-5. SysDEF Import Log Tab in the Output Window

94
4. System Configuration B0700FE – Rev A

Creating an I/A Series V8.x System

IACC supports the configuration of I/A Series V8.x equipment including The Mesh Control
Network, Windows 7 based workstations, and field control processors.
IACC also provides configuration support for interfacing The Mesh Control Network with I/A
Series V6.x and V7.x Control Networks using the Address Translation Station (ATS), as described
in “Configuring an ATS” on page 103.
This section describes creating an instance of The Mesh Control Network, configuring switches,
and adding workstations and field control processors. Other procedures for adding FBMs and
editing software are virtually the same for all I/A Series hardware and software, and are described
in the following sections:
 “Configuring Communications Interface Devices” on page 109
 “Adding Fieldbus Modules” on page 113
 “Selecting Peripherals” on page 107
 “Creating Software Objects” on page 125
 “Assigning Hardware Objects” on page 127
 “Committing the Configuration” on page 132.
To create an instance of The Mesh Control Network:
1. Right-click Configuration at the top of the Network tab and choose New > Net-
work from the pop-up menu to open the Create Networks dialog box (Figure 4-6).

Figure 4-6. Create Networks Dialog Box Selected from the Configuration Object

2. Click HPS Network, enter a value in the quantity field if you are creating more than
one, and click OK.
The network objects are displayed under Configuration in the Network tab with
default names such as HPS001. The last one to be created is highlighted indicating
that you can change the name now.
3. Press Enter to accept the default name, or type a new name over the object and press
Enter.
You can rename the network object at any time by selecting either Rename or
Properties from the object’s pop-up menu.

95
B0700FE – Rev A 4. System Configuration

To add switches to the network:

1. Right-click the network object and choose New > Network Component from the
pop-up menu to display the Create Switches/Hubs dialog box (Figure 4-7).

Figure 4-7. Adding Switches to the Network

2. For each switch type you want to add, click the check box to the left of the switch
name and enter a quantity to the right if you are adding more than one of the type.
3. Click OK.
The selected switches are displayed under the network object with default names such
as SW0001. The last one to be created is highlighted indicating that you can change
the name.
4. Press Enter to accept the default name, or type a new name over the object and press
Enter.
You can rename the network object at any time by selecting either Rename or
Properties from the object’s pop-up menu.
At this point, you can re-assign any switch to another network object or to another
switch by dragging the object in the Project Navigator to the new parent object.
The pop-up menu for a switch object includes a New function from which you add switches,
stations, or field communications modules.

96
4. System Configuration B0700FE – Rev A

Adding Stations to The Mesh

There are two ways to create workstations and field control processors:
 Choose New > Station from the Configuration object in the Network tab and select
equipment from the Create Stations dialog box.
The dialog box lists all station types, including those not supported on the The Mesh
Control Network.
After creating a station from the Configuration object, you can move object by drag-
ging the object and dropping it on a switch to connect it to the network
 Open the Create Stations dialog box from the switch to which the stations are to be
attached.
With this method (described below), the created stations are assigned to the switch
and thus to the network, and the dialog box only presents stations compatible with
The Mesh Control Network.
To add stations:
1. Right-click the appropriate switch in the Network tab and choose New > Station
from the pop-up menu to display the Create Stations dialog box (Figure 4-8).

Figure 4-8. Create Stations Dialog Box Selected from a Switch

97
B0700FE – Rev A 4. System Configuration

The dialog box lists four station types:

 AW70P Windows XP based application workstation. This station can serve as the
master timekeeper (or its backup) for the network. Optional software pack-
ages include Message Manager, Sequence of Events, Transient Data Analyst,
and Transient Data Recorder. See “Creating Software Objects” on page 125
for information on adding optional software packages.
 FCP270 Field-mounted control processor connects directly to DIN rail mounted
FBMs. Can be configured as a single processor or fault-tolerant pair.
 ZCP270 Z-form factor control processor installed in a central rack. Connects to
DIN rail mounted FBMs via an FCM100. Can be configured as a single
processor or fault-tolerant pair.
 AW51M0-M4 SolarisTM 10 based application workstation. These stations can serve as
master timekeeper (or its backup) for the network.

2. For each station type to be added, click the check box and enter a quantity if you are
adding more than one of the type.
3. Click OK.
The stations are displayed in the Network tab with default names such as S00001.
The last one to be created is highlighted indicating that you can change its name.
Before committing the configuration, you must rename the stations using letterbugs
that identifies the hardware on the I/A Series system. Default names can be used as
placeholders until you determine the letterbugs.
4. Press Enter to accept the default name for the last object, or type the new letterbug
name over the object and press Enter.
You can rename the network object at any time by selecting either Rename or
Properties from the object’s pop-up menu.
If you created more objects than ports available on the selected switch, messages in the
Diagnostics tab in the Output window list the objects that were not assigned to the
switch. The unassigned stations appear under the Configuration object.
Figure 4-9 shows an AW70P and an FCP270 created from an 8-port switch. The two
station objects have been expanded to show the peripherals and software that are auto-
matically configured for each object when it is created. The FCP270 is being assigned
to its workstation host.

98
4. System Configuration B0700FE – Rev A

Figure 4-9. Stations Added to an 8-Port Switch

Adding Fieldbus Modules to an I/A Series V8.x System

An I/A Series V8.x system communicates with field devices via FBMs on a 2Mbps module
fieldbus. There are three ways that these FBMs can be connected to the system:
 Connected directly to an FCP270
 Connected to a switch via an FCM100
 Connected to a ZCP270 via an FCM100.
The 2Mbps Fieldbus modules include DIN rail mounted FBMs and I/A Series Migration DCS
Fieldbus Modules. The DIN rail mounted FBMs are installed in the same baseplate as the host
FCP270/FCM100 or in an adjacent baseplate connected with a module fieldbus cable.
The Migration FBMs are installed in the legacy system equipment rack and connected to the host
FCP270/FCM100 via the legacy backplane and I/A Series module fieldbus cables.
For information on configuring an FCM100, see “Configuring Communications Interface
Devices” on page 109.
For information about adding FBMs, see “Adding Fieldbus Modules” on page 113.

99
B0700FE – Rev A 4. System Configuration

NOTE
Other types of I/A Series FBMs that communicate at 268Kbps and are normally
used with CP40s and CP60s can also be connected to an FCP270 or ZCP270.
IACC supports addition of these devices directly to the stations or through an
Ethernet Fieldbus Isolator (FBI10). Refer to FCP270 User’s Guide (B0700AR) and
ZCP270 and RCP270 User’s Guide (B0700AN) for information on using the older
style FBMs with V8.x control stations.

Creating a Network/LAN
Several topologies are available for structuring a network, such as star, tree, and bus topologies.
Refer to your site planning drawings to determine which network components are appropriate.
Small centralized networks that do not require signal amplification can use a passive star topology.
Larger centralized networks that require signal amplification can use either a star or a tree
topology. Non-centralized networks that spread out over long distances can use a bus topology.
If you are not building a stand-alone system, you must create a network. Primarily, a network
comprises a Token Passing Local Area Network (LAN) and its interfaces such as coaxial LAN
interface or fiber optic LAN interface. The I/A Series LAN provides redundant communication
among I/A Series system nodes. For versatility of applications, three basic LAN interface
configurations are possible:
 Coaxial (metallic) Carrierband LAN
 Passive Tap/Converter fiber optic LAN
 Direct fiber optic LAN.
Even if you do not require a network now, you may want to create one in anticipation of later
expansion. Additional information for these configurations is found in “Network Equipment” on
page 101.

NOTE
Unless otherwise noted, the procedures in this section start with the selection of an
object in the Project Navigator Network tab.

Procedures for Creating Networks

To create a network:
1. Right-click Configuration and choose New > Network from the pop-up menu to
display the Create Networks dialog box (Figure 4-10).
2. Type the number of LANs or click the LAN, and then click OK.

100
4. System Configuration B0700FE – Rev A

Type the number

Click the of networks
check box to desired.
select the item.

Figure 4-10. Create Networks Dialog Box

If you click the LAN, a new I/A Series LAN Network (L00001) is created in the
Configuration branch in the network hierarchy.
You can now proceed to creating network components (switches/hubs and nodes).

Network Equipment
There are a number of hardware items that either interface to the LAN, or themselves provide a
primary network service such as a Nodebus. The following sections contain a brief synopsis of the
network components listed in the Create Switches/Hubs dialog box.
When you create a network object from the Configuration branch, the item is not automatically
assigned to a parent. To have network components automatically parented, create the object from
the intended parent object (this is not the same as assigning a host). Otherwise, you must use
other methods to establish a parent relationship, such as dragging the object onto the intended
parent. For example, first create a LAN, then create its LAN interface, then create its Nodebus
from the expansions:
Configuration > New > Network To create the LAN with the default name L00001
L00001 > New > Network Component To attach a CLI LAN interface named S00001 to
LAN L00001
S00001 > New > Network Component To add the node to the CLI LAN interface
S00001.

Then create the remainder of the network components.

Note that fiber optic cabling and coaxial Carrierband LAN cabling can be combined.

Creating Network Components

There are two approaches to creating a network component:
 Use the pop-up menu for Configuration and later assign the component to the net-
work object.
 Create the components using the pop-up menu for the network object. IACC assigns
the components to the object.

101
B0700FE – Rev A 4. System Configuration

To create a network component from a LAN:

1. Right-click the network object (L00001, for example) and choose New > Network
Component from the pop-up menu to display the Create Switches/Hubs dialog box
(Figure 4-11).

Figure 4-11. Create Switches/Hubs Dialog Box

Note that a Nodebus/Node, Ethernet ThinNet, or splitter/combiner cannot be

created directly from a LAN. Each must be created directly from the expansion,
Configuration > New, or from a network component, as explained in the sections that
follow.
2. In the dialog box, scroll to the appropriate components and type the number of
components or click the component, for example, click CLI (coaxial LAN interface).
3. Click OK.
A new network component (S00001) is created in the network hierarchy. When
created this way, the network components are parented by the LAN.

Creating a Node from a Network Component

To create a node from a network component such as a coaxial LAN interface (CLI):
1. Right-click the network component (the CLI) S00001 and choose New > Network.
The Create Networks dialog box appears with Node as the only available selection.
2. Type the number of nodes, or click Node, and click OK.
A new node (N00001) is created under the network component in the network
hierarchy. When created this way, the node is parented by the LAN.

Creating a Node Without a LAN

To create a node without a LAN:
1. Right-click Configuration and choose New > Network from the pop-up menu to
open the Create Networks dialog box.
2. Check NODE and click OK.
A new Nodebus (N00001) is created directly under the Configuration branch in the
network hierarchy. When created this way, the node is unparented.

102
4. System Configuration B0700FE – Rev A

Creating an Ethernet Nodebus

The I/A Series system can accommodate an Ethernet-based node as a stand-alone entity
comprising application processors, application workstations, and workstation processors.
To create an Ethernet node:
1. Right-click Configuration and choose New > Network from the pop-up menu.
The Create Networks dialog box appears as shown in Figure 4-10.
2. Check IA EtherNet and click OK.
A new unparented I/A Series Ethernet Nodebus (L00001) is created directly under the
Configuration branch in the network hierarchy.

Configuring an ATS
The Address Translation Station (ATS) allows extension of I/A Series System V6.x and 7.x
Nodebus based control networks with I/A Series System Mesh Control network stations (V8.x).
The ATS operates in one of two modes:
 LI replacement: When there is no LAN Interface (LI) on the node, the ATS act as an
LI for the Node.
 Nodebus extender: When there is an LI on the Node, ATS makes The Mesh Control
Network an extension of that Node.
Procedures for configuring an ATS in IACC are described separately for each of these options.
Refer to Address Translation Station User’s Guide (B0700BP) for additional information on ATS
configuration, installation, and operating modes.

LI Replacement Mode
An ATS operates in LI replacement mode when there is not an LI on the same node. If there are
multiple Address Translation Stations on a network, only one can be in Nodebus extender mode,
and the rest are in LI replacement mode. In this mode, the ATS acts like an LI, but instead of con-
necting a node to the Carrierband LAN, it connects a node to The Mesh.
To configure an ATS in LI mode:
1. Expand the HPS network object to display the configured switches.
2. Right-click a switch and choose New > Network Component to open the Create
Switches/Hubs dialog box.
3. Check the box for ATS and click OK.
4. If the ATS is a redundant module, double-click the ATS to open the properties sheet
for the station, select FT on the Hardware tab and select a second switch using the
pull-down menu on the Switches tab.
5. Right-click the ATS station, choose New > Network from the pop-up menu, check
NODE in the Create Networks dialog box, and click OK.
Add hubs and stations to the Nodebus as described in “Creating Network Compo-
nents” on page 101 and “Creating Stations and Processors” on page 104, respectively.
If a Node has already been configured in IACC:
1. Select the Node in the Configuration tab and drag it to the ATS object.

103
B0700FE – Rev A 4. System Configuration

2. When all Nodes have been assigned to an ATS, delete their LI from the network.
To restore the node to the pre-V8.x network:
1. Create an LI station under the pre-V8.x LAN object.
2. Drag the node object from the ATS and drop it on the LI station.
3. Delete the ATS object.

Nodebus Extender Mode

The ATS operates as a Nodebus extender, or bridge, when there is an LI on the same node. Only
one bridging node can exist in a system. The ATS is added to a Node that is already connected to
an LI.
To configure a Nodebus extender:
1. Expand the LI in the Configuration tab, right-click the Node and choose New
Network Component from the pop-menu to open the Create Switches/Hubs dialog
box.
2. Check the box for ATS and click OK.
3. Right-click the newly created ATS and choose Properties from the pop-up menu.
4. Use the pull-down lists in Switch tab to configure the Switch 1 and Switch 2
parameters, and click OK.

Creating Stations and Processors

Stations, processors host system components, and support applications provide a means to per-
form configurations for process control and management strategies, supply an operator interface,
and execute process control tasks. Stations supported for I/A Series systems are listed in I/A Series
Configuration Component (IACC) V2.2 Release Notes (B0400BR).

104
4. System Configuration B0700FE – Rev A

The Create Stations dialog box for configurable stations is shown in Figure 4-12. This example
was invoked from the Configuration branch (Configuration > New > Station) in the Network tab.

Figure 4-12. Configurable Stations and Processors

Contents of dialog boxes for creating stations and processors vary according to the location in the
hierarchy, and the object from which they are invoked.

Procedures for Creating Stations

The following sections detail procedures for creating stations from a variety of locations in the
configuration hierarchy in the Network tab.

Creating a Station and CP from the Configuration Branch

To add stations to the Configuration object:
1. Right-click Configuration and choose New > Station to open the Create Stations
dialog box (Figure 4-12).
2. Select the station types, such as AW70 and CP40B, and enter the number of stations
to be added for each.
3. Click OK.
Figure 4-13 shows a new AW70 station (S00002) with its peripherals and software,
and a new CP40B (S00003) with its software. Because these objects were created from
the Configuration object, they are unparented.

105
B0700FE – Rev A 4. System Configuration

AW70 Operating System

Software

Peripherals

CP40B Operating System

Compounds

Figure 4-13. Stations, Peripherals and Software for AW70 and CP40B - From Configuration

106
4. System Configuration B0700FE – Rev A

Creating a Station and Control Processor from a Nodebus

To create the same station and control processor from a Nodebus:
1. Expand Configuration until the Nodebus appears in the network hierarchy.
2. Right-click the Nodebus (such as N00001 in Figure 4-14) and choose New > Station
to display the Create Stations dialog box (Figure 4-12).
3. Select a station type, such as AW70 or CP40B, and enter the number of stations you
want to create.
4. Click OK.
Figure 4-14 shows a new AW70 station (S00002) and a new CP40B (S00003) with its
software created under the Nodebus (N00001) in the network hierarchy. When
created this way, the objects are parented by the Nodebus.

Figure 4-14. Stations and Software for a CP40B

Selecting Peripherals
The I/A Series stations and processors require certain peripherals for operator interface, data
storage, or emergency shutdown. In most cases, peripherals for a station are automatically
included when you add the station. Figure 4-15 shows a ListView of peripherals already config-
ured for an AW70 and the Create Peripherals dialog box listing the equipment that can be added.

107
B0700FE – Rev A 4. System Configuration

Figure 4-15. Peripherals ListView and Create Peripherals Dialog Box

Figure 4-16 displays the other peripherals in the dialog box scrolled into view.

Figure 4-16. Additional Peripherals

To add peripherals:
1. Right-click the station, and choose New > Peripheral to open the Create Peripherals
dialog box (Figure 4-15).
2. Click the type of peripheral and enter the number you want to create.

108
4. System Configuration B0700FE – Rev A

For example, click CRTmonitor, Keyboard, Mouse, and PCL3P to configure one each
of the following peripherals for the station:
 Video monitor
 Alphanumeric keyboard
 Mouse
 HP DeskJet™ printer with a parallel interface.
3. Click OK.
The new peripherals (P00004 through P00007) are listed under the station selected in
Step 1.

Configuring Communications Interface Devices

Communications modules perform several basic functions such as providing an extender that
allows additional FBMs to be connected to the Fieldbus, and supplying galvanic isolation. The
following modules are supported:

DCM10 The DCM10 is an Ethernet Fieldbus Isolator that allows the CP60 to
communicate with 268Kbps FBMs, that is, Fieldbus modules designed for
the CP40 and earlier control processors. In the network hierarchy, the
DCM10 is created only from the CP60. The FBMs can be created from
the DCM10. Up to 24 FBMs are supported by the DCM10, which also
provides galvanic isolation between the Ethernet Fieldbus and the FBMs.
The DCM10 does not support 2Mbps FBMs.

FBI The Fieldbus Isolator (FBI) provides an extender that allows additional
FBMs to be connected to the Fieldbus, and also supplies galvanic isolation
between the extended Fieldbus and the remote Fieldbus. In the network
hierarchy, the FBI is created from the CP40B or a DCM10. 286Kbps
FBMs can be created from the FBI. Up to 30 FBMs can be added to the
FBI.

FBI10 The Ethernet Fieldbus Isolator (FBI10) allows CP60s, FCP270s and
ZCP270s to communicate with 268Kbps FBMs, that is, Fieldbus modules
designed for the CP40 and earlier control processors. In the network hier-
archy, the FBI10 is created from the Configuration object or from the sta-
tion. The FBMs can be created from the FBI10. Up to 30 (268Kbps)
FBMs are supported by the FBI10, which also provides galvanic isolation
between the Ethernet Fieldbus and the FBMs. The FBI10 does not sup-
port 2Mbps FBMs.

FCM10 The Fieldbus Communication Module (FCM10) is used to connect

2Mbps FBMs (including DIN rail mounted FBMs and WPDF Migration
DCS Fieldbus Modules) to a control processor via a high speed Ethernet
trunk Fieldbus. It also provides galvanic isolation between the Ethernet
trunk Fieldbus and the module Fieldbus.

109
B0700FE – Rev A 4. System Configuration

In the network hierarchy, the FCM10 is created only from the CP60.
2Mbps FBMs can be created from an FCM10, which supports a maxi-
mum of 30 DIN rail mounted FBMs.

FCM2 The Fieldbus Communication Module (FCM2) provides a

baseplate-to-baseplate fiber optic extension of the module Fieldbus
for DIN rail mounted 2Mbps FBMs. This allows the FBMs to be distrib-
uted either locally or remotely.
In the hierarchy, the FCM2 is created only from the FCM10, and must be
assigned to the FCM10. Note that no FBMs can be created from the
FCM2.
One FCM is needed for each bus (bus “A” and bus “B”). If you have a
redundant network, you require two FCMs for each redundant
connection.

FCM100 The FCM100 is a 100-megabit fieldbus communication module used in

I/A Series V8.x systems to connect 2Mbps FBMs to a Z-Form Factor
Control Processor 270 (ZCP270). In IACC, the FCM100 can be attached
to a ZCP270 or a network switch.
Additional criteria are described in the DIN Rail Mounted FBM Subsystem User’s Guide
(B0400FA).
You add these devices to the system configuration using the Create FB Comm/Isolators dialog
box. When the dialog box is opened from the Configuration object, it lists all six devices
(Figure 4-17).

Figure 4-17. Create FB Comm/Isolators Dialog Box

You can access the dialog box from the pop-up menu for any of the following objects in the
Network tab:
 Configuration node at the top of the tab
 CP object
 Network switch on The Mesh Control Network
 FCM10 (to configure an FCM2).

110
4. System Configuration B0700FE – Rev A

The following sections give examples of defining communications devices from several locations
in the Network tab. Contents of the Create FB Comm/Isolators dialog boxes vary depending on
the object from which you invoke the dialog box.

Creating Unassigned Comm Devices

To create communications devices directly from the Configuration object:
1. Right-click Configuration and choose New > FB Comm/Isolator to open the
Create FB Comm/Isolators dialog box (Figure 4-17).
2. Select the appropriate devices, enter a quantity for each, and click OK.
The new devices are created in the network hierarchy. When created this way, the
devices are unparented and must be assigned to the appropriate parent.

Creating FBIs from the CP40B

To create an FBI for a CP40B:
1. Expand Configuration to display the CP40B instance.
2. Right-click the CP and choose New > FB Comm/Isolator from the pop-up menu.
The Create FB Comm/Isolators dialog box displays FBI as the only choice for the CP
type.
3. Click FBI, enter a quantity if you are adding more than one, and click OK.
New Fieldbus Isolators are created under the CP. They are assigned default names
such as I00001. When created this way, the FBIs are parented by the CP40.

Creating FBI10s and FCM10s from a CP60

To create devices for a CP60:
1. Expand Configuration to the CP60 instance.
2. Right-click the CP and choose New > FB Comm/Isolators from the pop-up menu.
The Create FB Comm/Isolators dialog box displays DCM10, FBI10, and FCM10 as
the only choices for this CP type (Figure 4-18).

111
B0700FE – Rev A 4. System Configuration

Figure 4-18. Adding Communication Interface Devices for a CP60

3. Enter the number of Ethernet Fieldbus Isolators or Fieldbus Communications

Modules, and click OK.
The devices are created under the CP in the network hierarchy. When created this
way, the devices are parented by the CP60 (Figure 4-19). Note that the default name
for the FCM (such as E00100) ends in 00 to conform to the letterbug convention for
DIN rail mounted FBMs, in which the FCM letterbug ends in 00.

112
4. System Configuration B0700FE – Rev A

Figure 4-19. FCM10 Attached to a CP60

Creating FCM2s from a Fieldbus Communications Module

To create FCMs to be used with an FCM10:
1. Expand Configuration to the FCM10 instance under the CP60.
2. Right-click the FCM10 and choose New > FB Comm/Isolators from the pop-up
menu.
The Create FB Comm/Isolators dialog box displays FCM2 as the only selection that
can be created under an FCM10
3. Click FCM2, enter the number if you are creating more than one, and click OK.
The new FCM2s are created under the FCM in the network hierarchy. When created
this way, the FCMs are parented.

Adding Fieldbus Modules

Fieldbus Modules (FBMs) provide the interface between process sensors and actuators and the
control stations.
FBMs are organized into three groups in IACC:
 268Kbps Fieldbus Modules, which connect independently to a Fieldbus and provide
field I/O for older I/A Series control stations such as the CP40. The modules convert
electrical input/output signals used by field devices, permitting communication with
these devices via the Fieldbus. The modules can also be connected to later control sta-
tions such as the CP60 and the ZCP270 via Ethernet Fieldbus Isolators (FBI10).

113
B0700FE – Rev A 4. System Configuration

 Expansion Modules that can be added to certain 268Kbps FBMs to double the num-
ber of I/O channels, as described on “Expansion FBMs” on page 117.
 2Mbps Fieldbus Modules including DIN rail mounted FBMs (sometimes referred to
as 200 Series FBMs) and I/A Series Migration DCS Fieldbus Modules.
Several of the DIN rail mounted FBMs provide an interface with intelligent field
devices. These include the FBM246 FoxCom dual-baud rate intelligent device inter-
face and the Distributed Communication Interface (DCI) modules that support vari-
ous fieldbus standards such as HART™, PROFIBUS-DP™, and FOUNDATION™
fieldbus. The intelligent devices are configured in IACC through the addition of
device equipment control blocks (ECB201s), as described in “Configuring Field
Devices” on page 122.

NOTE
Before using IACC to configure FOUNDATION fieldbus H1 devices on an I/A Series
system, you must also install Field Device Manager software. This FDT editor is
opened from within IACC, and provides comprehensive management of field
devices including configuration, commissioning and calibration, maintenance and
troubleshooting. For additional information about Field Device Manager, refer to
Implementing FOUNDATION fieldbus on the I/A Series System (B0700BA).

268Kbps Fieldbus Modules

Table 4-1 lists the 268Kbps modules that can be added in IACC and assigned to a control station
or one of its attached communications modules. Typically these modules are added directly to a
CP40 or to a Fieldbus Isolator attached to a CP60. IACC also permits you to configure these
modules for use with newer control stations such as the FCP270 and the ZCP270.
Most FBM models have a fixed I/O capacity. However, nine modules have an expandable I/O
capacity as indicated in Table 4-1. The expandable main modules use expansion modules to
increase the capacity of field input/output channels and accommodate additional field signals of
the same or of a different kind.

Table 4-1. 268Kbps FBMs and Interfaces

FBM Description
CORINT Coriolis Interface
FBM01 0 to 20 mA Input
FBM02 Thermocouple/mV Input
FBM03 RTD Input (Platinum, Nickel)
FBM04 0 to 20 mA Input/Output
FBM05 Redundant 0 to 20 mA Input/Output
FBM06 Pulse Input, 0 to 20 mA Output
FBM07 Contact/dc Input; Expandable
FBM08 120 v ac Input; Expandable
FBM09 Contact/dc Input/Output; Expandable
FBM10 120 v ac Input/Output; Expandable

114
4. System Configuration B0700FE – Rev A

Table 4-1. 268Kbps FBMs and Interfaces (Continued)

FBM Description
FBM11 240 v ac Input/Output; Expandable
FBM17 Contact/0 to 10 v dc Input/Output
FBM18 Intelligent Transmitter
FBM20 240 v ac Input; Expandable
FBM22 4 to 20 mA I/O Auto/Manual
FBM24 Contact/125 v dc Input; Expandable
FBM26 Contact/125 v dc I/O; Expandable
FBM33 RTD Input (Copper)
FBM36 Thermocouple/mV Input
FBM37 0 to 20 mA Output
FBM39 Intelligent Transmitter, 0 to 20 mA Output
FBM41 High Power Contact/dc Input/Output; Expandable
FBM43 Dual Baud Rate Intelligent Transmitter
FBM44 Dual Baud rate Intelligent Transmitter, 0 to 20 mA Output
FBM46 Redundant Dual Baud Rate Intelligent Transmitter
FBP10 Fieldbus Processor
FBPI10R Redundant Fieldbus Processor
FBP11 UCM Spectrum Migration Interface
FBP11R Redundant UCM Spectrum Migration Interface
FBP12 FIO Spectrum Migration Interface
FBP13 UFM Spectrum Migration Interface
FBP14 UIO Spectrum Migration Interface
HIU Hydrostatic Interface Unit
PDSIP Panel Display Station
S2BM04 Spec200 0 to 10 v dc Input/Output
S2BM17 Spec200 0 to 10
S2MM09 Extended Control Integrator
S2MM17 Basic Control Integrator

The following sections provide procedures for adding FBMs from several locations in the Config-
uration hierarchy in the Network tab.

Creating 268Kbps FBMs from the Configuration Branch

To create 268Kbps FBMs directly from the Configuration branch:
1. Right-click Configuration and choose New > 268Kbps Fieldbus Module to open
the Create 268Kbps Fieldbus Modules dialog box (Figure 4-20).

115
B0700FE – Rev A 4. System Configuration

Figure 4-20. Create 268Kbps Fieldbus Modules Dialog Box

2. For each FBM type to be added, click the check box for the type and enter a quantity
if you are adding more than one.
3. Click OK.
The new FBMs are added to the network hierarchy with default names such as
F00001, F00002, and so on. When created this way, the FBMs are unparented. They
must be assigned to a control station or its FCM before you download a control strat-
egy that uses the FBMs.

Adding FBMs to a CP40B

The following procedures apply to expandable FBMs as well as non-expandable FBMs.
1. Expand Configuration until the appropriate CP appears in the network hierarchy.
2. Right-click the CP and choose New > 268Kbps Fieldbus Module from the pop-up
menu.
The Create Fieldbus Modules dialog box appears (Figure 4-20). Only modules
compatible with the CP are listed.
3. For each FBM type to be added, click the check box to the left of the model name and
enter a quantity on the right if you are adding more than one of the type.
4. Click OK.
The new FBMs are listed under the CP40 with default names such as F00001,
F00002, and so on. When created this way, the FBMs are assigned to the CP from
which they were created.

Creating FBMs from the Fieldbus Isolator

If you are using a Fieldbus Isolator (FBI) communications interface, you must create it prior to
adding FBMs.
To create 268Kbps FBMs from the FBI:
1. On the bottom of the Project Navigator window, click the Network tab.
2. In the Project Navigator window, expand Configuration until the appropriate FBI
appears in the network hierarchy.

116
4. System Configuration B0700FE – Rev A

3. Right-click the FBI and choose New > 268Kbps Fieldbus Module from the pop-up
menu.
The Create Fieldbus Modules dialog box appears (Figure 4-20).
4. For each FBM type to be added, click the check box to the left of the model name and
enter a quantity on the right if you are adding more than one of the type.
5. Click OK.
The new FBMs are listed under the FBI with default names such as F00001, F00002,
and so on. When created this way, the FBMs are assigned to the CP to which the FBI
is attached.

Creating 268Kbps FBMs for a CP60

A CP60 requires a DCM10 or FBI10 Ethernet Fieldbus Isolator to interface with 268Kbps
FBMs. The Create 268Kbpas Fieldbus Modules dialog box can be opened from either the config-
ured interface module or the CP60 itself. In the later case the FBMs must be dragged to the inter-
face module before the configuration is downloaded.
To configure 268Kbps FBMs for a CP60:
1. Expand Configuration until the appropriate DCM10 or FBI10 Ethernet Fieldbus
Isolator appears in the network hierarchy.
2. Right-click the DCM10 or FBI10 and choose New > 268Kbps Fieldbus Module
from the pop-up menu.
The Create Fieldbus Modules dialog box appears listing DIN rail mounted FBMs.
3. For each FBM type to be added, click the check box to the left of the model name and
enter a quantity on the right if you are adding more than one of the type.
4. Click OK.
The new FBMs are listed under the DCM10 or FBI10 with default names such as
F00001, F00002, and so on. When created this way, the FBMs are assigned to the CP
to which the DCM10 or FBI10 is attached.

Expansion FBMs
Nine 286Kbps FBMs support the optional use of an expansion module to increase the number of
I/O points with field signals of the same or a different kind. Each expandable main module can
support any one of nine expansion modules. More common expandable main module-expansion
module combinations are shown in Table 4-2.

Table 4-2. Expandable Main Modules and Their Expansion Modules

Main Module Expansion Module

FBM07 FBM12
FBM08 FBM13
FBM09 FBM14
FBM10 FBM15
FBM11 FBM16
FBM20 FBM21

117
B0700FE – Rev A 4. System Configuration

Table 4-2. Expandable Main Modules and Their Expansion Modules (Continued)

Main Module Expansion Module

FBM24 FBM25
FBM26 FBM27
FBM41 FBM42

The expansion module connects to the Fieldbus via the main module. Expansion modules are
functionally dependent on the supporting main module for performance of signal conversions
and other related operational executions. The main modules provide contact sensing, digital mon-
itoring only, or dc output switching. Expansion modules can be configured from the pop-up
menu for Configuration or the main module instance.
To create multiple expansion FBMs:
1. Right-click Configuration at the Project Navigator Network and choose New >
Expansion Module from the pop-up menu to open the Create Expansion Modules
dialog box (Figure 4-21).

Figure 4-21. Create Expansion Modules Dialog Box

2. For each type of expansion module to be configured, click the check box on the left
and enter a quantity if you are adding more than one of the type.
3. Click OK.
The modules are displayed in the Network tab under Configuration.
4. Drag each expansion module to a main FBM to assign it to the main module.
To add an expansion FBM to its main module:
1. Expand Configuration at the Project Navigator Network until the main module is
displayed.
2. Right-click the main module and choose New > Expansion Module from the pop-
up menu to open the Create Expansion Modules dialog box (Figure 4-21).
3. Select the FBM type and click OK.
Only one expansion module can be created for its associated main module. A new
FBM is created in the network hierarchy. When created this way, the FBM is parented
by the FBM from which it was created.

118
4. System Configuration B0700FE – Rev A

Figure 4-22 shows an FBM07 (the main module), which is connected to a CP60 via
an FBI10, and a newly added FBM12 (the expansion module).

Host CP60

Main Module

Expansion Module

Figure 4-22. Project Navigator Display of an FBM with Expansion Module

2Mbps Fieldbus Modules

This section covers configuration of 2Mbpas Fieldbus Modules including DIN Rail Mounted
FBMs and Migration DCS Fieldbus Modules. The modules can be added to an FCP270 directly,
to a ZCP270 via an FCM100, and to a CP60 via an FCM10. See “Configuring Communications
Interface Devices” on page 109.
All 2Mbps FBMs can be created from the Configuration branch, in which case they are unas-
signed and must be assigned to the appropriate control station or FCM before the control strate-
gies that use them can be downloaded.
To create unassigned 2Mbps FBMs:
1. Right-click Configuration and choose New > 2Mbps Fieldbus Module from the
pop-up menu to open an dialog box for selecting the modules (Figure 4-23).

119
B0700FE – Rev A 4. System Configuration

Figure 4-23. Create 2Mbps Fieldbus Modules Dialog Box

2. For each type to be configured, click the check box on the left of the model name and
enter a quantity on the right if you are adding more than one of the type.
3. Click OK to close the dialog box.
The new modules are listed under Configuration with default names such as
F000001, F00002, and so on.

DIN Rail Mounted FBMs

DIN rail mounted 2Mbps Fieldbus Modules allow you to distribute process input/output mod-
ules by mounting the modules more conveniently on a horizontal or vertical baseplate. They can
mount either inside or outside an enclosure, and in small, distributed cabinets. Also, there is inte-
grated use of fiber optic and coaxial cable for communication between modules. There is a wide
variety of baseplate mounting options, including the use of address switches to create a virtual
baseplate from multiple physical baseplates. Review DIN Rail Mounted FBM Subsystem User’s
Guide (B0400FA) for information on hardware installation and module identity. There is no rep-
resentation of the baseplate in IACC.

Table 4-3. DIN Rail Mounted 2Mbps FBMs

FBM Description
FBM201 0 to 20 mA Input (8 AI)
FBM202 Thermocouple/mV Input (8 AI)
FBM203 RTD Input (Platinum, Nickel and Copper) (8 AI)
FBM204 0 to 20 mA Input/Output (4 AI/4 AO) (can have redundant outputs)
FBM205 0 to 20 mA Input/Output Interface (4 AI/4 AO) (Redundant I/O)
FBM206 Pulse Input, 0 to 20 mA Output (8 PI)
FBM207 Contact/dc Input (16 DI)
FBM208 0 to 20 mA (4AI/4AO)
FBM211 0 to 20 mA (16 AI)
FBM212 Thermocouple/mV (14AI)
FBM213 RTD (Platinum and Nickel) (8 AI)

120
4. System Configuration B0700FE – Rev A

Table 4-3. DIN Rail Mounted 2Mbps FBMs

FBM Description
FBM214 HART (8 Input)
FBM215 HART (8 Output)
FBM216 HART (8 Input)
FBM217 Contact (32DI)
FBM218 HART (8 Output)
FBM219 Switch (24 DI/8 DO)
FBM220 FOUNDATION fieldbus H1 (one segment)
FBM221 FOUNDATION fieldbus H1 (four segments)
FBM223 2-channel Profibus-DP
FBM224 Modbus Communication Interface Module
FBM228 Redundant FOUNDATION fieldbus interface
FBM230 RS-232, RS-422 and/or R-485 Field Device System Integrators
FBM231
FBM232 Ethernet Field Device System Integrators
FBM233
FBM237 0 to 20 mA Output (8 AO)
FBM240 120V ac/125 V dc Switch (8 DO)
FBM241 Contact 24 V dc Input/0 to 240 V ac Output (8 DI/8 DO)
FBM242 0 to 60 V dc Externally Sourced Output (8DO)
FBM243 FoxCom Dual Baud Rate, 8 channel, Intelligent Device Interface
FBM246 FoxCom Dual Baud Rate, 8 channel, Intelligent Device Interface

Adding DIN Rail Mounted FBMs for a CP60 or ZCP270

To assign DIN Rail Mounted FBMs to a CP60, you must first configure an FCM10 that provide
interface FBMs. If you are using more than one baseplate, you must create an FCM2 interface.
Likewise, before assigning DIN Rail Mounted FBMs to a ZCP270, you must first configure an
FCM100 that provides the interface to the control station.
If the FBMs have already been created from Configuration, you can assign the FBMs by dragging
them to FCM in the Project Navigator. You can also create the FBMs from the FCM as described
in the following sequence. With this approach, the FBMs are automatically assigned to the host
control station/FCM.
To add DIN rail mounted FBMs to a CP60 or ZCP270:
1. Expand Configuration in the Network tab to display the appropriate control sta-
tion and its FCMs.
2. Right-click the FCM and choose New > 2Mbps Fieldbus Module from the pop-up
menu to open the Create 2Mbps Fieldbus Modules dialog box (Figure 4-23).
3. For each FBM type to be added, check the box to the left of the FBM name and enter
a quantity on the right if you adding more than one of the type.
4. Click OK to close the dialog box and add the selected modules to the FCM.

121
B0700FE – Rev A 4. System Configuration

The modules are listed below the FCM with default names such as F00001, F00002
and so on.

Adding DIN Rail Mounted FBMs for an FCP270

DIN Rail Mounted FBMs can be added and assigned to an FCP270 using the control station’s
context menu in the Project Navigator.
If the FBMs have already been created from Configuration, you can assign the FBMs by dragging
them to FCP270 in the Project Navigator.
To add DIN rail mounted FBMs to an FCP270:
1. Expand Configuration in the Network tab to display the control station.
2. Right-click the FCP270 and choose New > 2Mbps Fieldbus Module from the pop-
up menu to open the Create 2Mbps Fieldbus Modules dialog box (Figure 4-23).
3. For each FBM type to be added, check the box to the left of the FBM name and enter
a quantity on the right if you adding more than one of the type.
4. Click OK to close the dialog box and add the selected modules to the FCP270.
The modules are listed below the FCP270 with default names such as F00001,
F00002 and so on.

Configuring Field Devices

The DIN Rail Mounted FBMs listed Table 4-4 provide a digital interface with intelligent field
devices using various protocols and fieldbus standards. The field devices attached to these FBMs
are represented in the I/A Series system by device equipment control blocks (ECB201s). In IACC,
a field device is added to the host FBM in IACC by adding an ECB201 or a user-defined device
type derived from the ECB201 to the FBM.

Table 4-4. User Guides for Field Device FBMs

FBM User Guide

FBM220 FOUNDATION fieldbus H1 Interface Module (FBM220/221)
FBM221 User Guide (B0400FD).
FBM223 PROFIBUS-DP Communication Interface Module (FBM223)
User’s Guide (B0400FE)
FBM214 HART Communication Interface Module
FBM215 (FBM214/215/216/218) User’s Guide (B0400FF)
FBM216
FBM218
FBM224 Modbus Communication Interface Module (FBM224) User’s
Guide (B0400FK)
FBM230 I/A Series System Field Device System Integrators
FBM231 (FBM230/231/232/233) User’s Guide (B0700AH)
FBM232
FBM233
FBM228 Implementing FOUNDATION™ fieldbus User’s Guide on the
I/A Series® System (B0700BA).

122
4. System Configuration B0700FE – Rev A

Depending on the FBM, there are various rules for configuring the device and in some cases spe-
cialized editors that are plugged into IACC. The following sequence provides generalized instruc-
tions for adding field devices to an FBM. Refer to the user guide listed in Table 4-4 for detailed
instructions for setting device parameters and connecting the control strategy to the device via the
ECB201.
To add a field device to an FBM:
1. Expand the FBM object in the Project Navigator to display the module’s software and
its equipment control block, an ECB200 for a non-redundant FBM or an ECB202
for a redundant module.
2. Right-click the ECB200/202 and choose New Child ECB from the pop-up menu to
open a dialog box listing the available device ECBs for the FBM type.
Figure 4-24 show two dialog boxes:
 The Create Child ECB on the left was opened from an FBM224 Modbus Com-
munications Interface.
 The Create Device dialog box on the right was opened from an FBM228, which is
used to connect FOUNDATION fieldbus H1 devices to an FCP270 or ZCP270.
The dialog box lists four device definitions created by the user from device
descriptor files.
3. Click the check box to the left an ECB/device name and click OK.
For some FBMs, a single ECB201 is added for multiple devices; for others, there must
be an ECB201 for each device to be connected.
The new device is listed under the ECB200/201 for the host FBM. The context menu
for the device provides functions for configuring the device.
4. Refer to the specific FBM user guide (Table 4-4) for information on editing the device
instance.

Figure 4-24. Dialog Boxes for Selecting Device Types

123
B0700FE – Rev A 4. System Configuration

Adding Migration FBMs

The Invensys Plug-in Migration program enables users of legacy DCS systems that are no longer
supported to migrate to the I/A Series system. In this program, the legacy I/O modules are
replaced with I/A Series DCS Fieldbus Modules that plug into the existing I/O racks and use
existing field wiring. IACC includes support for two such programs: Siemens/Moore APACS and
Westinghouse WPDF. Migration modules for these legacy systems are included in the Create
2Mbps Fieldbus Modules dialog box and can be added to a FCP270 or to an FCM100 connected
to a ZCP270. The Westinghouse WPDF modules can also be added to an FCM10 to interface a
CP60 with the WPDF field wiring.
There are several instances in both migration programs where the legacy I/O module is replaced
by a single I/A Series module that is treated as two FBMs. These modules are represented in the
control database by two separate ECBs, and are configured as such in IACC. In the Create 2MBps
Fieldbus Modules dialog box, the modules requiring two ECBs are marked req 2. Figure 4-25
shows selection of a Westinghouse WPDF module that requires two ECBs.
To add migration FBMs:
1. Right-click the parent FCP270 or FCM, and choose New > 2Mbps Fieldbus Mod-
ule from the pop-up menu to display the Create 2Mbps Fieldbus Modules dialog
box.
2. Click the check boxes for the module types, enter the quantity for each, and click OK.
For modules marked req 2, add two FBMs for each replacement module
(Figure 4-20).

Figure 4-25. Selecting FBMs for a WPDF Replacement I/O Module

3. Rename the FBMs using the naming convention specified in the migration product
documentation, DCS Fieldbus Modules for Moore APACS+ Systems (B0700BK) or
DCS Fieldbus Modules for Westinghouse WPDF Systems User’s Guide (B0400BA).
For these products, generally the letterbug of the parent FCP270 or FCM ends in 00,
and the letterbug for the replacement modules consist of the first four characters of
the parent object plus two numbers or letters. The final two-character combination
must be unique among the FBMs connected to the CP. Dual modules must have con-
secutive numbers or letters. The letterbugs for the APACS AHF216 must end in A, B,
C, or D. Figure 4-26 shows an FCP270 that has been named WPDF00 and two

124
4. System Configuration B0700FE – Rev A

FBMs configured for a WAX01 replacement module. Following the naming conven-
tion, the FBMs are named WPDF01 and WPDF02.

Figure 4-26. FBMs Configured for a WPDF Replacement Module

Creating Software Objects

As you create hardware, most of the required software including the operating system is
automatically created by IACC. Once hardware is created, you define required packages and
optional software for the application processors, application workstations, workstation processors,
and for certain FBMs, the alternate software. For example, for each node you configure, you
must install the Compound Summary Access (CSA) package on one (and only one) application
workstation, and you should have at least one instance of the System Monitor (SysMon) package
configured on an application workstation. Other applications, such as AIM*Historian, are
optional. Each software object is created from its parent definition and should have its parameters
edited, as applicable.
The software is selected from the Create Software dialog box selected from the pop-up menu for
the processor or FBM. The contents of the Create Software dialog box vary depending on the
object selected in Project Navigator. Figure 4-27 is the Create Software dialog box opened from
the pop-up menu for an AW70.
Use the procedures shown in the following example to create software objects.
To add a System Monitor and the AIM*Historian™ software for the AW70 station S00001:
1. Right-click S00001 and choose New > Software Package to open the Create Soft-
ware dialog box (Figure 4-27).

125
B0700FE – Rev A 4. System Configuration

Figure 4-27. Create Software Dialog Boxes for an AW70

2. Select ASMON7 and AHIST7, and click OK.

The new software packages ASMON7_S00001 and AHIST7_S00001 are created
under the station in the Project Navigator (Figure 4-28).

Figure 4-28. Optional Software Packages

3. Use the System Editors or Properties dialog box to change software parameters as
needed.

126
4. System Configuration B0700FE – Rev A

Changing FBM Software

For many FBMs, there are alternate software packages that you can configure to meet specific
application requirements. For example, when you add an FBM217, IACC creates a default digital
I/O software package (iom05) for the module. However, you can change the package to support
one of the following applications:
 Sequence of Events (iom06)
 Pulse Count (iom07)
 Ladder Logic (iom08).
To change FBM software:
1. Right-click on the FBM object in the Network tab and select New > Software
Package to open the Create Software dialog box.
The dialog box lists the other software packages that can be configured for the FBM.
Figure 4-28 is a Create Software dialog box for an FBM217. Note that iom05 is not
listed because it is the currently selected software for the FBM.

Figure 4-29. Optional Software for an FBM217

2. Click the check box for the package you want and click OK.
IACC replaces the previously configured software with the selected package. Only one
such package can run on the FBM. If you select multiple copies of a package or more
than one package, IACC creates each one in turn and then replaces it with the next
package it creates.

Assigning Hardware Objects

Considerations for Assigning Hardware Objects
Creating associations among objects is referred to as assigning or linking those objects. When you
have finished creating hardware objects, you must assign them to a parent object. Objects are
assigned by dragging them within the Project Navigator hierarchy or by using the Hardware Edi-
tor.
All hardware objects, other than a LAN, node, or stand-alone processor must have a parent object
so that the system/network hierarchy is properly structured, and so that software is associated with

127
B0700FE – Rev A 4. System Configuration

its related hardware. You must assign the hardware objects individually after creating them under
Configuration. Objects are automatically assigned when you create them from their intended
parent object.
Figure 4-30 shows three Nodebus objects:
 N00001 is created from the Configuration object and is thus unparented
 N00002 and N00003 are assigned to and parented by CLIs S00002 and S00005,
respectively.

Figure 4-30. Parented Nodebus

You can change the assignment of an object by dragging it in the Project Navigator from its
location to a new parent object or Configuration. IACC does not allow you to drag and drop the
object when the re-assignment results in an invalid I/A Series configuration.

Assigning Hardware Objects

Assigning a Network Component
To assign a network component, you can either expand Configuration to the component to be
parented and drag the component to its intended parent, or you can use the Hardware Editor.
To use the Hardware Editor:
1. Right-click the component and choose Editors > Hardware Editor from the pop-
up menu to open the Hardware Editor for the component.
2. Use the pull-down list in the Parent column to assign the component to the parent
object.

128
4. System Configuration B0700FE – Rev A

Assigning Peripherals
If you create an additional peripheral for a workstation, you can assign the peripheral to another
compatible workstation. For example, you can move an annunciator from one AW70 to another
I/A Series workstation, but you cannot move peripherals that were automatically configured when
you created the station.
You can change the assignment by dragging and dropping the object in the Project Navigator or
you can change the assignment by invoking the Hardware Editor from the parent object. The
editor cannot be invoked from the peripheral itself.
To assign peripherals:
1. Expand Configuration to find the parent workstation.
2. Right-click the station and choose Editors > Hardware Editor from the pop-up
menu.
3. Click the Peripherals tab, scroll to the Parent column, and click the peripheral to
be assigned.
4. Pull-down the list of stations in the field and click the appropriate peripheral parent
name.
The peripheral is assigned to the new parent, and appears below it in the hierarchy.

Assigning FBMs and Interface Modules

You can use the drop-and-drag method to reassign FBMs and interface modules. IACC prevents
you from assigning a module to an object that is incompatible. For example, you cannot drop a
2Mbps FBM on a DCM10, as only 268Kbps modules can be connected to a DCM10.
The Hardware Editor is not directly available for assigning FBMs, unless the FBMs are
expandable main modules. In such cases, both the main module and its expansion are shown in
the Field Devices spreadsheet of the Hardware Editor. Instead, you must invoke the editor from
the parent object or Configuration.
To use the Hardware Editor:
1. Expand Configuration to display the CP, interface module, or expandable main
FBM from which assignments are to be made.
2. Right-click the object and choose Editors > Hardware Editor.
3. Click the Field Devices tab and select the row for the FBM or interface module to
be re-assigned.
4. Use the pull-down list in the Parent column to select the parent name, and click OK.
The FBM or interface module is assigned to its parent, and appears below it in the
hierarchy.
Figure 4-31 shows a typical Hardware Editor spreadsheet for assigning FBMs or interface
modules.

129
B0700FE – Rev A 4. System Configuration

Figure 4-31. Typical Hardware Editor for Field Devices - Parent Assignment for an FBM

Because FBM08 was created from CP40B, the ID for that CP (S00004) appears as the parent.
However, the pull-down list allows you to select I00001, an FBI10. Selecting this module as a par-
ent causes FBM08 to appear under the FBI10 in the hierarchy. It also changes the CP for FBM08
from CP40B to CP60 because the FBI10 is associated with that CP.

Figure 4-32. Typical Hardware Editor for an Entire System - Parent Assignment for Stations

130
4. System Configuration B0700FE – Rev A

Assigning Software Hosts from the Hardware Editor

Assigning the software host with the Hardware Editor defines where the software for a hardware
module resides.
To assign a software host via the Hardware Editor:
1. Right-click the appropriate station, and choose Editors > Hardware Editor to
open the Hardware Editor for the object (Figure 4-33).
2. Scroll to the SW Host column, use the pull-down list to select the host AP/AW, and
click OK.
The software associated with the station is assigned to the specified host.

Figure 4-33. Assigning a Software Host Using the Hardware Editor

Assigning Hosts from the Project Navigator

To assign a software host via the Project Navigator:
1. Right-click the station in the Project Navigator, and choose Assign > Host from the
pop-up menu.
The Assign Host dialog box lists the available stations (Figure 4-34). If the station is
already assigned, its host is checked in the dialog box.

131
B0700FE – Rev A 4. System Configuration

Figure 4-34. Assign Host Dialog Box

2. Click the check box for the AP/AW that is to be the host and click OK.
The station is assigned to the selected host.
To unassign a station:
 Uncheck the check box and click OK.

Committing the Configuration

Once you have completed configuring and assigning all your hardware and software, you are
ready to create a Commit diskette.
When you invoke the download procedure, IACC checks your entire network configuration for
errors and displays errors in the Hardware/Software Commit tab in the Output window. If Hard-
ware Validation finds no errors, you can proceed to produce a valid Commit diskette. IACC pre-
pares to generate a Commit diskette even when there are errors; however, this diskette is invalid.
You can select this Validation function without downloading, as described in this chapter.
The basic Commit diskette creation procedure consists of three main steps:
1. Performing a Hardware Validation operation to confirm that the network
configuration in the IACC database is valid
2. Generating the file for installation on the Commit diskette
3. Loading the file to the Commit diskette.
When installation is complete, the installation status is saved to one or more Reconcile diskettes
that allow you to update the configuration in the IACC database to reflect the installed version of
the configured system.

132
4. System Configuration B0700FE – Rev A

Validating a Configuration
You can run a validation at any time before downloading the configuration to a Commit diskette.
The following sequence is a stand-alone validation of the entire Configuration object.
To validate the configuration:
1. Switch to the Network tab in the Project Navigator, if it is not already displayed.
2. Right-click Configuration and choose Validate/Download > Validate from the
pop-up menu.
The Validate Hardware/Software Configuration (Figure 4-35) lists the validation
options. These are described in Table 4-5.

Figure 4-35. Validate Hardware/Software Configuration Dialog Box

Table 4-5. Validation Options

Option Description
Hardware Connectivity Verifies the connections between hardware in your control strategy.
Any problems found during this check may be rectified using the
Hardware Editor.
Software Requirements Checks to ensure all the hardware in your network configuration is
assigned the default software requirements. Any problems found
during this check may be rectified using the Hardware Editor or Proj-
ect Navigator.
Installation Parameters Checks for the installation parameters for your software. Any
problems found during this check may be rectified using the
Parameter Editor.

133
B0700FE – Rev A 4. System Configuration

3. Check the items to be validated and click Next.

As IACC performs the selected validations, it displays errors in the Hardware/
Software Commit tab in the Output window (Figure 4-36).

Figure 4-36. Typical Output Window for Validation

4. Click Done when the validation is complete.

5. Right-click in the Output window and choose Save Tab Contents or Print Tab
Contents for a list of errors to be fixed.
6. Adjust the configuration using the System Editors for the objects identified and rerun
the Validation to ensure that the configuration is error free.

Creating a Commit Diskette

The following sequence creates a Commit diskette for all items under the Configuration object.
To create a Commit diskette for a system configuration:
1. Right-click Configuration and choose Validate/Download > Download.
The Validate Hardware/Software Configuration dialog box (Figure 4-35) appears even
if you have previously done a validation.
2. Follow the sequence described for a stand-alone validation in “Validating
a Configuration” on page 133.

134
4. System Configuration B0700FE – Rev A

NOTE
If any errors are found, it is strongly recommended that you correct them before
continuing with creating the Commit diskette.

After the validation, the Commit Hardware/Software Configuration dialog box

appears (Figure 4-37).

Figure 4-37. Commit Hardware/Software Configuration Dialog Box

3. Select Commit Diskette and click Next.

The Validation Checks dialog box (Figure 4-38) appears if you have any unresolved
problems found during the Hardware Validation. Ignore allows you to continue
creating a Commit diskette.

Figure 4-38. Validation Checks Dialog Box

! CAUTION
Be aware that the files generated after you click Ignore may not load your network
configuration properly.

135
B0700FE – Rev A 4. System Configuration

4. Click Start in the Hardware/Software Commit dialog box (Figure 4-39) to begin the
generation of the Commit files.

Figure 4-39. Hardware/Software Commit Dialog Box

The Media Distribution dialog box prompts you to place the Package Distribution
diskette in the diskette drive (Figure 4-40).

! WARNING
If you do not have a Package Distribution diskette, click Ignore only if you are using
IACC as a training exercise. Do not attempt an actual installation without the
required Package Distribution diskette.

Figure 4-40. Package Distribution/Media Distribution Dialog Box

Table 4-6 describes the Package Distribution/Media Distribution dialog box options.

136
4. System Configuration B0700FE – Rev A

Table 4-6. Package Distribution/Media Distribution Dialog Box Options

Option Description
OK Processes the Commit diskette using the media ID from the Media Distribution
diskette, or media package IDs from the database.
If you have the Media Distribution diskette, replace the current diskette with that
diskette and click OK (Figure 4-43).
Ignore Proceeds to the download process.
Cancel Displays the message shown in Figure 4-42 and displays the Downloading dialog
box when you click OK. It displays the message “No download to perform.” The
Commit process is terminated.

5. Click OK in the Package Distribution/Media Distribution dialog box.

The Hardware/Software Commit dialog box prompts you to insert the diskette in the
drive (Figure 4-41).
6. Click OK in the Hardware/Software Commit dialog box.

Figure 4-41. Prompt to Insert Disk

7. Click Start in the Downloading dialog box.

137
B0700FE – Rev A 4. System Configuration

When the files are loaded on the diskette, a dialog box prompts you to make another
copy of the diskette (Figure 4-42).

Figure 4-42. Prompt for Another Diskette

8. Click Yes to create another diskette, or No to end the session.

9. Click Done when you have finished creating the Commit diskettes.

System Installation and Reconciliation

Use the Commit diskettes to install/load software to the applicable hardware in your configura-
tion, as described in Software Installation (Solaris Platform) (B0193JG) or Software Installation
(Windows NT Operating System) (B0400JG).
Following the installation, create a Reconcile diskette following the instructions in the relevant
I/A Series documentation. The installation process generates one or more Reconcile diskettes that
indicate the actual state of installed software packages, and contain a list of what software was
successfully installed, and what was not. You can process Reconcile diskettes into IACC to update
the software. When further changes are made to the system, you can modify your configuration in
IACC and create another Commit diskette.

Updating Installation Status in IACC

To reconcile the IACC database with the install configuration:
1. Right-click Configuration and choose Editors > Software Editor.
2. Choose Reconcile > Using Diskettes from the menu bar.
A dialog box prompts you to insert a Reconcile diskette in the diskette drive
(Figure 4-43).

Figure 4-43. Insert Reconcile Diskette

3. Insert a diskette and click OK to continue the reconcile process.

The progress bar in the middle of the dialog box keeps you informed of the progress
being made while loading the Reconcile diskette. Once the reconcile process has been
started, the Cancel button has no effect.
4. From the dialog box, click Yes if you have additional diskettes to reconcile, or click No
if you do not have additional Reconcile diskettes.

138
4. System Configuration B0700FE – Rev A

5. When all the diskettes have been processed, click OK to end the session.

Reviewing the Software

To review the Software Editor to determine the status of the software:
1. Right-click the station object in the Network tab and choose Editors > Software
Editor.
The Software Editor (Figure 4-44) allows you to view and configure the attributes
(software installation state and description) listed in Table 4-7 for the software
associated with the selected hardware object. This is an example of a typical Software
Editor section.

Figure 4-44. Software Editor Selected for an AW70

Table 4-7. Columns in Software Section in Software Editor

Column Name Description Configurable

Host For control processors, network components, No
Allen-Bradley stations, COMM10, and FBMs. Lists the
host processor to which this hardware object is assigned.
ID Letterbug identifier for selected hardware associated with No
the software package. Name must be unique and have
6 characters.
Package Type of software, such as OS1C4B for a CP40B. No
Description Brief description of software package. Yes

139
B0700FE – Rev A 4. System Configuration

Table 4-7. Columns in Software Section in Software Editor (Continued)

Column Name Description Configurable

Install State Indicates one of the following (fields are updated after Yes
reconciliation):
 Not Yet Installed — Software has not been installed yet
 Failed Installation — Installer attempted to load
software, but failed
 Reinstall Required — Installer must reinstall the
software before the software functions properly
 Failed Reinstall — Installer attempted a reinstallation
of the software, but failed
 Data Update Required — Software parameters require
an update (does not need to be reinstalled)
 Software Installed — Software has been successfully
installed.

Once the equipment and control strategy have been loaded successfully, you can download new
software configurations directly to the required hardware. For example, if you want to add a new
Fieldbus Module to your strategy, you can make the necessary additions to the control strategy in
the IACC database, and then download the contents to the applicable control processor.

Floppy Dependency Removal

To support the workstations that do not have floppy disk drives, IACC 2.5 allows reading files
from and writing them to locations other than stamped 3½” floppy disks. A stamped location is
one which represents a collection of files with a unique stamp identity. Valid stamped locations
include USB drives, the local file system, and network shares. Writing to optical media, tape
drives, and 5¼” floppy disks is not supported.
IACC 2.5 allows you to perform the following:
 Create configuration files to a stamped location
 Import Reconcile files and SysDef export files from a stamped location
During Commit, Reconcile, or SysDef import process, you are prompted to select a valid stamped
media using the Browse dialog box, as shown in the Figure 4-45.

140
4. System Configuration B0700FE – Rev A

Figure 4-45. Floppy Dependency Removal

If the selected media is not a valid stamped media, you are prompted to retry. To support back-
ward compatibility, the Use Diskette button (Figure 4-45) allows you to continue to read from
and write to floppy diskettes.
The following table lists the folder paths that can be selected by IACC 2.5 to read from or write to
a stamped location:

Location selected using

Folder Selection Dialog Box Actions
A: Treat as diskette
A:\ Treat as folder
A:\subfolder
F: Treat as folder
F:\ Treat as folder
F:\ subfolder Treat as folder

141
B0700FE – Rev A 4. System Configuration

NOTE
In addition to security constraints, reading from or writing to folders is limited by
the physical properties of the underlying media. Commit files that are written in to
stamped locations are not compatible with older version of I/A.

142
5. Control Configuration
This chapter describes how to configure control blocks using the CSD Editor.
CSDs are graphical representations of specific portions of your control strategy, containing blocks
and their connections. With the CSD Editor, you assemble a CSD using any of the block types
listed under the Library branch or contained in a palette. You drag the block definition from the
Project Navigator or Palette window into the CSD Editor creating an instance of the definition.
You then use the graphical tools and pop-up menu available with the editor to make connections
between the blocks.
Each block has an appearance object which can be displayed in the CSD Editor. Connections can
then be made in the editor between parameters on appearance objects of the blocks, which corre-
spond to the actual process connections. Connections can also be made between blocks, including
blocks on different CSDs, through the Connection dialog box. IACC uses these parameter
connections to resolve the full pathnames for block-to-block parameter connections during
downloads to control processors.
The CSD Editor is used to construct the following three control tools:
 Simple CSD — a CSD built in the CSD Editor without the use of a template.
A Simple CSD is set up for a specific control process. A Simple CSD is best for a
control strategy that is used only once.
 CSD Template — a framework that displays a process or a part of a process that is
used repeatedly to configure your control strategy.
A CSD Template contains a general block and connection strategy which can be used
to produce multiple CSD instances. Information from a TagList may be applied to a
CSD Template during bulk generation to produce a unique CSD instance. You can
build a CSD Template using the Project Navigator and the CSD Editor, or you can
convert a CSD to a CSD Template.
 CSD Instance — a CSD generated from a CSD Template.
As stated above, information may be applied to a CSD Template to produce a unique
CSD instance either through bulk generation or by changes made in the CSD Editor.

143
B0700FE – Rev A 5. Control Configuration

Before you can download the blocks in a CSD to the I/A Series system, you must assign the blocks
to a compound and assign the compound to a CP. These functions are performed using pop-up
menus from the Plant tab of the Project Navigator.
IACC includes several tools for making changes to the blocks you configure in a CSD, including:
 Properties dialog box for individual blocks as described in Chapter 6
“Modifying Compounds and Blocks”
 Definition Editor, which can be used to modify blocks derived from standard
I/A Series blocks
Changes made to a derived definition are propagated to instances of the blocks that
have already been configured in a CSD. The Definition Editor is discussed in
“Derived Block Definitions” on page 183.
 Modifiers, for use only within IACC to make global changes to block parameters. See
“Modifiers” on page 194.
The next section offers background information on compounds, blocks, and parameters when
configuring processes in the CSD Editor. For more in-depth information on these topics, refer to
I/A Series Integrated Control Software Concepts (B0193AW).

! WARNING
Do not configure a CP and its compounds in more than one IACC database.

Compounds, Parameters, and Blocks

Process control for I/A Series systems is based on the concepts of compounds and blocks. A
compound is a logical collection of blocks that perform a control strategy. A block includes a set
of algorithms that perform a certain control task within the compound structure.

Compounds
The compound provides the basis for the integration of:
 Continuous control
 Ladder logic
 Sequential control.
Using the CSD Editor in conjunction with the Connection dialog box, any block in any
compound can be connected to any other block in any compound in the system. Blocks in a
single CSD need not all belong to the same compound.
A compound supports the following functions for its related blocks:
 Process alarm priority, alarm inhibiting, and alarm grouping
 Sequence status notification
 Phasing for the order of execution and load leveling at execution time.
The following rules apply to compounds:
 Multiple compounds can be executed within the same station
 A single compound cannot cross station boundaries

144
5. Control Configuration B0700FE – Rev A

 Blocks in different compounds can be interconnected across station boundaries

 Every compound must have a unique name.

Parameters
Blocks are connected to each other and to compounds by connecting their parameters. In
IACC, the connections between parameters are implemented in the CSD Editor and in the
Connection dialog box (see “Making Connections” on page 165). In the CSD Editor, block
parameters are connected graphically. When two exposed block parameters are connected, the
CSD Editor automatically draws a line with an arrow symbol indicating the data flow from block
to block. These connections are reflected in the Connection dialog box. Making a single connec-
tion between blocks may cause other parameters to be connected as well, depending upon the
parameters involved. Any such additional connections are also shown on the CSD, as long as all
the involved parameters are currently exposed (see “Showing Parameters” on page 170). Each con-
nection consists of a connectable source and a connectable sink.

Blocks
A block has one or more inputs/outputs and performs a predefined process function that has been
specified by an algorithm. There are continuous, sequence, and ladder logic block function types
that can be mixed and matched to satisfy your integrated control needs. This section briefly
defines the block set. However, detailed information can be found in the documents listed in
Table 5-1.

Block Parameters
Like compounds, each block contains select parameters that serve as the inputs and outputs of
their respective functions. These parameters follow the same conventions as compound
parameters regarding their value types and connectability/settability.

Editing Parameters
You may edit block parameters in IACC using the Definition Editor.

Block Function Types

Table 5-1 lists documents that provide detailed descriptions of all the block function types
currently supported in IACC. Each subsystem document describes the relevant equipment
control blocks (ECBs) and their associated control blocks.

Table 5-1. IACC Block Function Types

I/A Series Document

Block Type Document Name Number
Sequence Blocks Integrated Control Block Descriptions B0193AX
High Level Batch Language (HLBL) User’s Guide B0400DF
Alarm Blocks Integrated Control Block Descriptions B0193AX
Control Blocks Integrated Control Block Descriptions B0193AX
Data Blocks Integrated Control Block Descriptions B0193AX

145
B0700FE – Rev A 5. Control Configuration

Table 5-1. IACC Block Function Types (Continued)

I/A Series Document

Block Type Document Name Number
DCI Blocks Integrated Control Block Descriptions B0193AX
FOUNDATION fieldbus User’s Guide for the Redundant (B0700BA)
FBM228 Interface
FD Blocks Device Integrator 15 and Device Integrator 30 User’s Guide B0193RH
Input/Output Blocks Integrated Control Block Descriptions B0193AX
INTERSPEC Blocks Integrators for Allen-Bradley™ Controllers B0193RG
PLC Interface Blocks PLC Interface Block Descriptions B0193YQ
I/O Gate Blocks Device Integration Using I/O Gates B0193VG
Logic Blocks I/A Series Integrated Control Block Descriptions B0193AX
Misc Blocks
ABSCAN Integrators for Allen-Bradley Controllers B0193RG
MDSCAN Integrators for Modbus and Modbus Plus Devices B0193RL
TRISOE FoxGuard Manager Direct Connect Interface for B0193VK
Triconex Safety Systems User’s Guide
Motor Blocks I/A Series Integrated Control Block Descriptions B0193AX
RTU Blocks Application Workstation 70 with Bristol Babcock, Inc. B0400AZ
Remote Terminal Units (RTUs)
Redundant I/A Series SCADA Processor User’s Guide B0193WN

NOTE
Refer to Integrated Control Software Concepts (B0193AW) for detailed information
on block connections and the formats for addressing parameters.

Setting Up CSDs
There are three ways to create CSDs:
 Create a Simple CSD using a Plant Area pop-up menu.
With this method, you build the CSD from scratch using the CSD Editor,
Palette window, and other tools.
 Make multiple CSDs from one or more CSD Templates in a process called
Bulk Generation.
With this method, you create CSD instances which replicate the block structure and
connections contained in the template. You can initiate Bulk Generation from a Plant
Area pop-up menu, as described in “Creating a CSD from a Template” on page 149,
or, you can initiate the function from the TagList Editor to combine block informa-
tion in the templates with I/O data in a TagList, as described in Chapter 9 “TagLists
and Bulk Generation”.
 Convert a CSD Template to a Simple CSD.

146
5. Control Configuration B0700FE – Rev A

This method is useful when you no longer need the template to generate new
instances or update existing instances. This method is described in “Converting a
CSD Instance” on page 151.

Plant Areas
All three methods for setting up CSDs require a Plant Area to which you can assign the CSD.
To define a Plant Area:
1. Click the Plant tab if the Plant Area tree is not already displayed in the Project
Navigator.
2. Do one of the following:
 Right-click the Plant object at the top of the Project Navigator and choose New
Plant Area from the pop-up menu.
 Expand the Plant object, right-click an existing Plant area, and choose New >
Plant Area from the pop-up menu (Figure 5-1).

Figure 5-1. Creating a Plant Area from an Existing Plant Area

IACC inserts the new Plant Area under the selected object and identifies it with a
default name such as Plant Area1. A rectangle appears around the new Plant Area to
indicate that you can edit the name.
3. Type the new name and press Enter.
You can now create CSDs, compounds, display files, and other Plant Areas using the object’s
pop-up menu. The objects are automatically saved to the selected Plant Area.

147
B0700FE – Rev A 5. Control Configuration

You can also move a Plant Area to another location in the Plant Area tree, making it part of
another Plant Area or attaching it to the top-level object, Plant. Objects created under the Plant
Area move with it. You move a Plant Area by dragging it from its current location and dropping it
on the parent object.
When you delete a Plant Area, IACC deletes any Plant Area assigned to the deleted object. The
other objects in the Plant Area are unassigned and relocated to one of the following:
 Plant > Unassigned_CSDs
 Plant > Unassigned_Compounds
 Plant > Unassigned_Displays.
To delete a Plant Area:
1. Right-click the Plant Area and choose Delete from the pop-up menu.
IACC displays the Delete Request dialog box, which shows the other objects affected
by the delete.
2. Click OK in the dialog box to confirm the action.

Creating a Simple CSD

To create and name a Simple CSD:
1. Click the Plant tab and expand the tree in the Project Navigator to display the Plant
Area where you want to create the CSD.
2. Right-click the Plant Area, and choose New > CSD > Simple CSD from the pop-up
menu (Figure 5-2).

Figure 5-2. Creating a Simple CSD

148
5. Control Configuration B0700FE – Rev A

The new CSD appears under the selected Plant Area with a default name, such as
Simple CSD1. A rectangle appears around the new CSD to indicate that you can edit
the name.
3. Type the new name and press Enter.

Creating a CSD from a Template

You can create multiple CSD instances from one or more templates with a selection from the
Project Navigator. If the CSD Template includes Placeholder ECBs, IACC prompts you to
identify the channel.
When bulk generation is performed, CSD instances are automatically created in the database
(refer to Chapter 9 “TagLists and Bulk Generation”).
To create a CSD from a CSD Template:
1. Right-click the Plant Area where you want to create the CSDs and choose New > CSD
> Bulk Create CSDs from the pop-up menu to open the Create New CSD(s) dialog
box (Figure 5-3).

Figure 5-3. Bulk Generating CSDs from a Plant Area

2. Click each CSD Template you want to apply.

A check mark appears next to the name and the number field becomes active.
3. Enter the number of instances you want to create from each template.

149
B0700FE – Rev A 5. Control Configuration

4. Click OK.
If there are Placeholder ECBs in the CSD Template, the dialog box prompts you to
identify FBM and channel data to apply to the placeholder (Figure 5-4).

Figure 5-4. Bulk Generate Dialog Box for Assigning Field Signals

5. For each I/O block parameter listed in the Block Connection Points List, select an
ECB and ECB Point in the group to the right, and click Assign.
The connection is listed in the box below the Assign button.
6. Click OK when all the connections have been identified.
The specified number of instances for each template type are created with default
names under the selected Plant Area. The default names are based on the names of the
individual templates. If you created multiple CSDs, the last one to be created is
highlighted indicating that you can edit the name.
7. Press Enter to accept the default name, or type a new name and press Enter.
You can rename this object or any other CSD by choosing Rename or Properties
from the object’s pop-up menu.
All CSD instances, whether created through one of the above two procedures or through Bulk
Generation, may be further modified in the CSD Editor. See “Setting Up CSD Templates” on
page 155 and “Editing a CSD” on page 158.

150
5. Control Configuration B0700FE – Rev A

Converting a CSD Instance

When you modify a CSD Template, the changes are applied to each CSD created from the
template. For example, if you change the Period and Phase parameters of the I/O blocks in the
template, the new settings are propagated to each of the instances. For some cases, you may want
to break this inheritance after you have created the CSDs.
The link is broken:
 For a single parameter When you change that parameter in the CSD Instance
using the Properties dialog box as described in “Block and
Compound Processing” on page 188.
 For all blocks in the CSD When you add or delete a block.
When you change a block connection.
When you convert the CSD instance to a Simple CSD.

To convert a CSD instance:

1. Right-click the CSD in the Project Navigator and choose Convert to Simple CSD
from the pop-up menu.
A dialog box prompts you to confirm the action (Figure 5-5).

Figure 5-5. Confirming a CSD Conversion

2. Click Yes to continue.

The CSD is displayed in the Project Navigator with the Simple CSD icon.

151
B0700FE – Rev A 5. Control Configuration

Converting a CSD Template to a Simple CSD

When you no longer need a CSD Template, you can convert it to a Simple CSD to create blocks
that can be downloaded. Before you initiate the conversion, you must first convert all instances of
the template to Simple CSDs as described in the previous section and then delete any ECB
Placeholder and modifiers from the template.
To convert a CSD Template to a Simple CSD:
1. Click the System tab in the Project Navigator and expand System > Components >
CSD Templates to display the current set of templates.
Right-click the CSD Template, and choose ListViews > CSD Definition from the
pop-up menu to display the instances of the template (Figure 5-6).

Figure 5-6. List of Instances for a CSD Template

152
5. Control Configuration B0700FE – Rev A

2. Click the Plant tab and convert each CSD Instance in the ListView (as described in
“Converting a CSD Instance” on page 151).
3. Click the System tab and expand the CSD Template object to display the blocks in
the template.
4. Right-click each ECB Placeholder, select Delete from the pop-up menu, and click OK
in the Delete Request dialog box.
5. Right-click the CSD Template and choose Convert to Simple CSD from the pop-
up menu.
A dialog box prompts you to confirm the action.
6. Click Yes in the dialog box to continue.
IACC displays the Assign to Plant Area dialog box. When you select a Plant Area, the
OK button becomes active.
7. Select the Plant Area to which you are assigning the new CSD or select Unassigned
CSDs, and click OK.

Renaming a CSD
To rename an existing CSD:
1. Right-click the CSD in the Project Navigator and choose Rename from the pop-up
menu.
A blinking cursor at the end of the name indicates that it can be changed.
2. Type the new name and press Enter.
You can also rename the CSD branch by using its Properties dialog box:
1. Right-click the CSD in the Project Navigator and choose Properties from the pop-
up menu.
2. Click the Standard tab in the dialog box.
3. Type the new value in the Name field and press Enter.
4. Click OK to conclude editing.

153
B0700FE – Rev A 5. Control Configuration

Deleting a CSD
To delete a CSD or CSD Template:
1. Right-click the CSD or CSD Template and choose Delete in the pop-up menu.
The Delete Request dialog box (Figure 5-7) identifies other items that would be
affected by the deletion.

Figure 5-7. Delete Request Dialog Box

In Figure 5-7, a CSD Template, at least one CSD instance, and three blocks are being
deleted. In addition, connections to ECBs and other objects outside the CSD are
deleted, but the objects themselves remain.
To delete all listed items:
 Click OK.
To preserve the CSD instance in Figure 5-7:
a. Click Cancel in the Delete Request dialog box.
b. Right-click Cas Loop_02 in the Project Navigator and choose Convert to
Simple CSD from the pop-up menu.
This disconnects the CSD from the template but makes no changes to the CSD
and its blocks.
A dialog box appears prompting you to confirm the action.
c. Click Yes in the Confirmation dialog box.
d. Right-click the CSD Template again and choose Delete from the pop-up menu.
2. Make sure that the name of the CSD to be deleted is present in the Deleted Object
field of the dialog box and click OK.

154
5. Control Configuration B0700FE – Rev A

Setting Up CSD Templates

There are two ways to create a CSD Template:
 Create the template using a pop-up menu in the System tab.
With this method, you build the CSD Template from scratch using the CSD Editor,
Palette window, and other tools.
 Convert a CSD to a CSD Template.
With this method, you make the conversion using the CSD’s pop-up menu. Once
you convert the CSD, a control strategy configured in the CSD cannot be
downloaded until you create an instance of the template.

Creating a CSD Template

To create and name a CSD Template:
1. Click the System tab in the Project Navigator and expand System > Components to
display the CSD Templates branch.
2. Right-click CSD Templates, and choose New CSD Template from pop-up menu.
The new CSD Template appears under CSD Templates with a default name, such as
Simple CSD Template1. A rectangle appears around the new template to indicate that
you can edit the name.
3. Type the new name and press Enter.
You can now open the CSD Editor to add and connect blocks in the CSD Template. To apply the
template, you must initiate Bulk Generation from a Plant Area pop-up menu or from the TagList
Editor.

Converting a CSD to a Template

You can convert a CSD to a CSD Template if the CSD contains no ECBs or modifiers.
See “Compounds, Parameters, and Blocks” on page 144 for information on adding ECBs to the
CSDs and “Modifiers” on page 194 for information on modifier types. When you convert a
CSD, the control strategy can be replicated in multiple CSD instances, but the blocks as
originally configured can no longer be downloaded.

155
B0700FE – Rev A 5. Control Configuration

To convert a CSD to a CSD Template:

1. Click the Plant tab if the Plant Areas are not already displayed, and expand the tree
to display the CSD to be converted.
2. Expand the CSD to list its blocks.
3. Right-click each ECB in the CSD, and choose Cut from the pop-up menu
(Figure 5-8).

ECBs

Modifier

Figure 5-8. Converting a CSD to a Template

The ECBs are removed from the CSD and disconnected from the other blocks, but
they remain in the database and can be added to other CSDs.
4. Right-click any modifier and choose Delete from the pop-up menu.

156
5. Control Configuration B0700FE – Rev A

5. Right-click the CSD and choose Convert to CSD Template from the pop-up
menu.
If you have not cut the ECBs or deleted modifiers before initiating the conversion
(Figure 5-9), the command is not executed and error messages are displayed in the
Output window.

Figure 5-9. Converting a CSD to a Template

A dialog box prompts you to confirm the move.

6. Click Yes in the dialog box.
The CSD is removed from the Plant Area and the new CSD Template is created
under System > Components > CSD Templates.
7. Replace the cut ECBs with ECB Placeholders and connect them to appropriate
I/O blocks as described in “Adding ECB Placeholders to a CSD Template” on
page 176.

157
B0700FE – Rev A 5. Control Configuration

Editing CSDs and CSD Templates

Figure 5-10 shows the IACC main window with a view of the CSD Editor.

Figure 5-10. IACC CSD Editor

Editing a CSD
When using this editor, you should be aware of the following rules:
 You can define blocks, block parameters, and internal connections (links) that exist
within the CSD in the drawing area of the CSD Editor.
To set block execution order, however, you must use the Execution Editor. Refer to
“Execution Editor” on page 186.
 Some blocks have data which must be shared with blocks in other CSDs.
You can make connections between such blocks either through the Connection dialog
box, or using the method described in see “Making Off-Sheet Connections” on
page 167.
 When changes are made and saved to a CSD Template in the CSD Editor, these
changes automatically propagate to any existing CSD instances made from that
template.
The link between a template and the instance remains until:
 Blocks are added to or deleted from the instance, or
 Connections to or from input/output blocks are changed in the CSD Editor
for that instance.
Until either of these changes is made, the link between a template and its instance
remains, and any change made to the template is reflected in the instance.

158
5. Control Configuration B0700FE – Rev A

Opening the CSD Editor

You can invoke the CSD Editor from any created CSD appearing in the Project Navigator.
To open the CSD Editor for a CSD:
1. Click the Plant tab and expand the parent Plant Area to display the CSD.
2. Right-click the CSD and choose Editors > CSD Editor from the pop-up menu.
To open the CSD Editor for a CSD Template:
1. Click the System tab and expand System > Components > CSD Templates to dis-
play the template.
2. Right-click the CSD Template and choose Editors > CSD Editor from the pop-up
menu.

NOTE
The commands described in the following sections are applicable to both CSDs and
CSD Templates, except where noted otherwise. The instructions assume that the
object has been selected in the appropriate Project Navigator tab and that the CSD
or CSD Template has been opened in the CSD Editor.

Adding Blocks to a CSD

To add a block to a CSD:
1. Use the pull-down list at the top of the Palette window to select the appropriate
category of blocks.
2. Select the block from the list and drag the block to the CSD.
You can also drag blocks into the CSD from System > Library > IA Block Types branch in the
Project Navigator.

Deleting Blocks from a CSD

You delete a block using a pick from its context menu, which you can access either from the block
branch in the Project Navigator, or the block appearance object in the CSD Editor. IACC
enforces the following rules:
 Deleting a block deletes all connections to other blocks.
 When you delete a block from a CSD Template, the block is deleted from all the
instances of the template.
 When you delete a block from a CSD that was created from a CSD Template, you
sever the connection between the CSD and the template. The CSD is no longer an
instance of the template and updates to the template are not propagated to the CSD.
To delete a block from a CSD:
1. Right-click on the block and choose Delete in the pop-up menu.
The Delete Request dialog box appears and lists other objects affected by the delete
(Figure 5-7).
2. Make sure that the name of the block that you wish to delete is present in the
Deleted Object field of the dialog box and click OK.

159
B0700FE – Rev A 5. Control Configuration

Moving and Placing Blocks on a CSD

To move a block on a CSD:
1. Click and hold the block to be moved.
Grab handles appear around the perimeter of the block, indicating that it is selected
(Figure 5-11).

Grab Handles

Figure 5-11. Block Appearance Object Selected for Relocation

2. Drag the object to its new location on the CSD.

To place blocks exactly on a CSD:
1. Click and hold the block to be moved.
Grab handles appear around the perimeter of the block, indicating that it is selected.
2. Click the Nudge Up, Nudge Down, Nudge Right, and Nudge Left toolbar buttons
(Figure 5-12) until the block is in the proper location.

Figure 5-12. Nudge Buttons in the CSD Editor Toolbar

These commands may also be chosen from the Tools menu. Holding down the Shift
key while using the Nudge commands moves selected objects by five units at a time.

160
5. Control Configuration B0700FE – Rev A

Resizing Areas on the Block Appearance Object

The connectable port and information areas on a block’s appearance object are shown below in
Figure 5-13.

Port Area

Information Area

Figure 5-13. Resizable Block Appearance Object Areas

The height of these areas can be changed by specifying their allotted number of lines:
1. Right-click in the area on the appearance object that you wish to resize and choose
Size Graph Area in the pop-up menu.
The Number of lines dialog box displays the current number of lines in the area.
2. Enter the new number and click OK.

Assigning Blocks to Compounds

You can assign blocks to a compound individually or assign all the blocks in a CSD to the com-
pound. You can make the assignment at any time before downloading the blocks to a CP.

Creating a Compound
To create a compound:
1. Expand the Plant Area tree in the Project Navigator to display the Plant Area where
you plan to create the compound.
2. Right-click the Plant Area and choose New > Compound from the pop-up menu.
The new object appears in the Project Navigator below the selected Plant Area and is
identified by a default name such as COMPND1. A rectangle appears around the new
object to indicate that you can edit the name.
3. Type the new name and press Enter.

161
B0700FE – Rev A 5. Control Configuration

You can also create a compound from a CP object in the Network tab, in which case the
compound is automatically assigned to the CP, but not assigned to a Plant Area.
To create a compound from a CP object.
1. Click the Network tab and expand Configuration to display the target CP.
2. Right-click the CP object and choose New > Compound from the pop-up menu.
The new object appears in the Project Navigator below the selected CP and is
identified by a default name such as COMPND1. A rectangle appears around the new
object to indicate that you can edit the name.
3. Type the new name and press Enter.

Assigning Individual Blocks

To assign a single block to a compound:
1. Right-click on the block in the CSD and select Assign Compound from the pop-up
menu.
The Assign Block to Compound dialog box lists the compounds available.
2. Select the compound and click OK.
The name of the assigned compound appears on the appearance object of the block
wherever it occurs (Figure 5-14). The block appears beneath the assigned
compound’s branch in the Project Navigator.

Block Compound
Name Name

Block
Type

Figure 5-14. AIN Block Before and After Assignment to a Compound

162
5. Control Configuration B0700FE – Rev A

Assigning CSDs
To assign all blocks in a CSD to the same compound:
1. Right-click anywhere in the background space of the CSD and choose Assign
Default Compound from the pop-up menu.
The Assign Default Compound dialog box lists the compounds available.
2. Select the compound and click OK.
The name of the assigned compound appears on the appearance object of each block
in the CSD. In addition, each block appears beneath the branch of the assigned
compound in the Project Navigator.
You can also assign a CSD to a compound by selecting the CSD in the Project Navigator and
dragging it to the compound. When you drop the CSD on the compound, the compound name
is added to the appearance objects in the block. The CSD remains at its original location in the
Plant Area tree, even when the compound is in a different Plant Area, as assignments to a com-
pound and to a Plant Area are not directly related.

Bulk Assignments from a ListView

ListViews provide a convenient method for assigning, or re-assigning, multiple blocks or multiple
CSDs to a compound. For example, you can open a ListView of the CSDs in a Plant Area, select
the one or more CSDs in the ListView display and drag them to a compound object in the Project
Navigator. For detailed instructions on making bulk compound assignments from a ListView,
refer to IACC Help under the ListViews topic.

Unassigning Blocks from Compounds

To unassign a single block or CSD from its compound:
 Right-click on the object in the CSD Editor or Project Navigator and choose
Unassign from Compound in the pop-up menu.
The compound name is removed from the block’s appearance object and the block is
removed from beneath the compound branch in the Project Navigator. This indicates
that the block has been removed from the compound.
Unassigning a CSD unassigns only those blocks in the CSD that were not explicitly
assigned to a different compound.

163
B0700FE – Rev A 5. Control Configuration

Assigning Compounds to a CP
Before you download compounds and their blocks to an I/A Series system, the compounds must
be assigned to the CPs that executes the configured control strategy.
To assign a compound to a CP:
1. Right-click the compound in the Project Navigator and choose Assign to Control
Station.
The Assign Compound To Control Station dialog box lists the CPs available in the
database (Figure 5-15). If the compound is already assigned to a CP, the station name
is checked in the list box.

Figure 5-15. Assign Compound To Control Station Dialog Box with Filtering Tool

You can narrow the list of CPs displayed in the list by using the filtering option:
a. Click Enable in the Filtering group and click Edit to display the Filter Assign
Candidates dialog box.
b. Check one or more categories and enter the appropriate filter criteria in the
corresponding data fields.
In Figure 5-15, the filter selects all CPs of the type CP60. You can also filter for
names containing a text string (for example, enter CP0* to select all names
starting with CP0) or select CPs that do or do not have compounds assigned to
them.
c. Click OK to refresh the list in the Assign Compound to Control Station dialog
box.
2. Click the CP where the compound is executed and click OK.

164
5. Control Configuration B0700FE – Rev A

You can use the same procedure to change the compound assignment. The compound appears
under the CP in the Network tab and you can access the compound’s pop-up menu from that
location also.

Assigning CSDs to a Plant Area

When you create a CSD from the Plant tab, the CSD is automatically associated with the selected
Plant Area object. When you create CSDs using Bulk Generation in the TagList Editor, the CSDs
are assigned to Plant Areas based on information in the selected TagList.
To assign a CSD to a different Plant Area:
1. Right-click the CSD in the Project Navigator and choose Assign to Plant Area.
IACC displays a dialog box showing the Plant tree. The Plant Area to which the CSD
is assigned is highlighted in bold.
2. Select the new Plant Area and click OK.
You can also re-assign a CSD by dragging the object in the Project Navigator to a new Plant Area.
To detach the CSD from the Plant Area:
 Right-click the object and choose Unassign from <Plant Area>.
IACC relocates the CSD to Plant > Unassigned CSDs. The move does not affect the
assignment of blocks in the CSD to various compounds.

Making Connections
To make connections between blocks in a CSD:
1. In each block, identify the parameters to be connected.
2. Move the cursor over the source parameter until the cursor appears as .
3. Drag the cursor from the source parameter to the sink parameter.
When you release the cursor, a line appears between the two parameters with an arrow
showing the flow of the connection.
If the link is invalid, the cursor appears as . A link may be invalid because the sink
is not an input parameter, or because it is already connected to a source.
To check for existing connections:
 Right-click the block and choose Connect from the pop-up menu to open the
Connection dialog box (Figure 2-25).
Connections between blocks in a CSD or a CSD Template are of two types, address and value,
as illustrated in Figure 5-16. Address connections are the same as the source/sink connections
that are made between I/A Series blocks and persist after the blocks are downloaded. These con-
nections are made in the CSD Editor when you drag a line from a parameter in one block
(the source) to a parameter in another block (the sink). The sink parameter is configured with the
address of the source parameter (block.parameter).

165
B0700FE – Rev A 5. Control Configuration

AIN PID AIN PID

PNT MEAS = EO1 = “PSI” EI1 = “PSI”
“AIN.PNT”

Address Connection Value Propagation Connection

Figure 5-16. Address Versus Value Propagation Connection

When you make an address connection in a CSD, several other connections can be
automatically configured based on the definitions of the two blocks. For example, when the Out
parameter of a PID block is connected to the Meas in an AOUT block, the back-calculation out
(Bcalco) in the AOUT block is connected to the back-calculation and feedback parameters in the
PID block (Bcalci and Fbk). These additional address connections are displayed in the Connec-
tion dialog box (Figure 5-17).
To display the Connection dialog box:
 Right-click the block in the CSD Editor and choose Connections from the pop-up
menu.
The dialog box enables you to view and edit the existing connections and to add new
connections.

Figure 5-17. Connection Dialog Box for an AOUT Block

When you make an address connection, IACC also implements several value propagation
connections based on the definitions of the two blocks. In a value propagation connection, the
value in the source parameter is copied exactly to the target parameter. The right side of
Figure 5-16 shows a common use of value propagation in which the units of measure description
is copied from an input block to a block using the input. This connection is maintained in IACC
so that changes to the source parameter value are propagated to the target parameter. When the
blocks are downloaded to an I/A Series system, however, the last propagated value, and not the
link, is downloaded.
Figure 5-17 shows three value propagations from an AOUT block to a PID block involving a
units of measure description and scaling values. Three similar value propagations are made from
the AIN block to the PID.

166
5. Control Configuration B0700FE – Rev A

Making Off-Sheet Connections

The CSD Editor can be used to make connections between any two blocks, whether or not the
blocks reside in the same compound or on the same CSD. Connections between blocks on
different CSDs are known as off-sheet connections. Off-sheet connections may be made using the
Connection dialog box.

NOTE
To connect a block to an I/A Series shared variable, you must enter the shared
variable name in the block parameter using the block’s Properties dialog box. Refer
to “Properties Dialog Box” on page 178.

NOTE
To connect a block to a block in another IACC database, you must enter the source
block address (compound:block.parameter) in the sink parameter using the sink
block’s Properties dialog box. Refer to “Properties Dialog Box” on page 178.

When you add an off-sheet connection (or remote connection) on a CSD:

 The CSD shows the off-sheet connection in a reference box with the connection
number and address
 The connection appears in the Connection dialog box.
To add a connection:
1. Right-click the block and choose Connect from the pop-up menu to display the
Connection dialog box (Figure 5-17).
2. Click Add to display the Add Connection dialog box (Figure 5-18).

Figure 5-18. Add Connection Dialog Box

167
B0700FE – Rev A 5. Control Configuration

3. Select a connection type in the list box.

Note that for block-to-block connections, you can specify either an address
connection or a value propagation connection.
4. Select either the Parent/Source or Child/Sink option button, and click Next.
This choice is only made for block-to-block connections. The next three dialog boxes
prompt you to select parameters for the connection. The labels within the dialog
boxes vary depending on your selections in the Add Connection dialog box. The
examples starting with Figure 5-19 illustrate a child/sink type connection.

Figure 5-19. Select Connection Parameter Dialog Box: Sink Parameter

5. Select the parameter to be connected and click Next to display the Select Object
dialog box (Figure 5-20).

168
5. Control Configuration B0700FE – Rev A

Figure 5-20. Select Object Dialog Box: Source Object

6. Expand the data tree to locate the block (either under its parent compound or its
Plant Area), select the object, and click Next to open the Select Object Parameter
dialog box (Figure 5-21).

Figure 5-21. Select Object Parameter Dialog Box: Source Parameter

169
B0700FE – Rev A 5. Control Configuration

7. In the Select Object Parameter dialog box, highlight the Source or Sink parameter,
and click Next.
8. Click Close in the Connection dialog box.

Showing Parameters
Each block’s appearance object in a CSD has certain parameters visible by default. The block’s
other parameters are not visible unless they are placed in the appearance object. This holds true
even when multiple connections are automatically made by IACC when two parameters are
connected. The connections do not appear in the CSD unless the involved parameters are
displayed.

NOTE
Before showing additional parameters in a block appearance object, it may be neces-
sary to increase the number of lines in the Port and Information Display areas, as
described in “Resizing Areas on the Block Appearance Object” on page 161.

To show hidden parameters:

1. Right-click the block and choose Select Parameter from the pop-up menu to
display the Select Parameters dialog box (Figure 5-22).

Figure 5-22. Select Parameters Dialog Box

2. Click the check boxes in the Parameter Attributes group of the dialog box to filter the
list.
Only parameters that meet all the selected criteria appear in the Parameters list box of
the dialog box.

170
5. Control Configuration B0700FE – Rev A

3. Select a parameter from the list box drag it to the block appearance object.
The cursor becomes a plus sign when it is in an area of the appearance object that can
show the parameter.
4. Drop the parameter in one of the Port areas to show connections to the parameter, or
drop the parameter in the Information area to display the parameter value.
5. Add additional parameters to the Port or Information areas of the block, or select
another block to add parameters.
6. Click Close in the Select Parameters dialog box (Figure 5-22).

Removing Parameters
To remove a parameter from a block’s appearance object on a CSD:
 Right-click on the parameter on the CSD and select Remove Parameter.
Removing a parameter from the appearance object has no effect on any connections to
the parameter. Removing parameters does not delete block connections, nor does it
remove the parameter from the block definition.

Deleting Connections
To delete connections in the CSD Editor:
1. Move the cursor over the connection to be deleted until the cursor appears as a
double-headed vertical arrow.
2. Right-click on the connection and select Delete from the pop-up menu.

Hiding and Showing Connections

To hide connections in the CSD Editor:
1. Move the cursor over the connection to be hidden until the cursor appears as a
double-headed vertical arrow.
2. Right-click on the connection and select Hidden from the pop-up menu.
The connection is not shown in the CSD, but it still exists in the database. You can
see all connections for a block by right-clicking on the block and choosing Connect to
display the Connection dialog box (Figure 2-25).
To make every hidden connection on a CSD visible again:
 Choose Tools > Unhide All Connections.

Modifying Connection Lines

NOTE
The functions described in this section only affect the appearance of the CSD and
have no impact on the configuration of block connections.

When you make block connections in the CSD Editor, IACC draws the connections with solid
black orthogonal lines of the same thickness (1 point). If there are multiple connections between
two blocks, or the blocks are not adjacent to one another, it may be difficult to distinguish

171
B0700FE – Rev A 5. Control Configuration

between the connecting lines, as in the multiple connections between the MAIN and MATH
block in Figure 5-23.

Figure 5-23. Default Block Connections Lines

To modify a block connection line to make the connections more obvious:

1. Drag either the sink or source parameter to a new position in its block appearance
object. IACC redraws the lines accordingly.
2. Adjust the position of either block appearance object.
3. Right-click on a line and uncheck Orthogonal in the pop-up menu to redraw the
connection as a straight between the two parameters.
Figure 5-24 shows the CSD after two connections were changed to straight lines, and
the RI03 parameter in the MATH block appearance object was moved to the bottom
of the port area.

Figure 5-24. Default Block Connections Lines

There are additional changes you can make to line properties to further distinguish
between connections.
4. Right-click on a line and choose one of the following options from the pop-up menu:
 Check Hidden to hide the line from view to hide the line. (The connection can be
selected and brought back into view.)

172
5. Control Configuration B0700FE – Rev A

 Click Delete to remove line from the CSD drawing and eliminate the connec-
tion between the two blocks. The connection can be viewed in either block’s Con-
nection Dialog box (Figure 5-17).
 Choose one of the commands in the Order submenu to place line on top or
below behind intersecting connections or other graphics in the drawing.
 Open the Properties dialog box (Figure 5-25), specify a different line style,
thickness, or color, and click OK.

Figure 5-25. Properties Dialog Box for a Connection Line

The Transparent check box hides the line but not the arrow head at the sink
parameter. To hide both the line and the arrowhead choose Hidden from the pop-
up menu.
Changes made using the pop-up menu and the Properties dialog box are not reversed when the
drawing is refreshed and are saved with the CSD.
Note that when you select a line, two or more gray squares appear on the line indicating the verti-
ces or connections between the segments that make up the line. On an orthogonal line you can
grab a point between the two vertices and drag the segment either vertically or laterally as shown
in Figure 5-26.

Figure 5-26. Reshaping an Orthogonal Line

173
B0700FE – Rev A 5. Control Configuration

If you move either block appearance object or close and reopen the CSD, the orthogonal line
snaps back to its default routing. The Edit Vertices ( ) and the Lock Vertices ( ) buttons in
the CSD toolbar enable you to make more elaborate changes to block connection lines and to
lock in those changes so the lines do not snap back to the default appearance.
To redraw block connection lines:
1. Click the or choose Draw > Lock Vertices from the menu bar to make the
line reshaping permanent.
2. Click the or choose Draw > Edit Vertices from the menu bar to make the fol-
lowing functions available:
 Drag a line segment to reshape the line.
 Drag vertex to move it to a new position.
 Click on a line segment while holding down the Ctrl key to add a vertex to the
line.
 Click on a vertex while holding down the Ctrl key to delete the vertex.
Refer to IACC Help topic Graphics Tools for additional information on manipulating CSDs and
other drawings in IACC.

Adding Graphical Objects to a CSD

Additional objects such as shapes, text boxes, and images can be added to CSDs using standard
IACC drawing tools. For information and procedures pertaining to these tools refer to IACC
Help.

Connecting I/O Blocks to the Field

In the I/A Series system, Fieldbus Modules (FBMs) and other devices provide an interface
between sensors and other devices in the field and the Control Processor. The FBMs are
represented in the control software by Equipment Control Blocks (ECBs). You configure these
connections in IACC by adding ECBs to the CSD and connecting channels in the ECB to
parameters in the I/O type blocks. “Adding Fieldbus Modules” on page 113 describes how to add
FBMs to the configuration and create the ECBs. You add ECBs to individual CSDs or add ECB
Placeholders to a CSD Template, in which case IACC prompts you to identify specific channels
when you run Bulk Generation.

Adding ECBs to a CSD

To add an ECB to a CSD:
1. Right-click the CSD and choose Editors > CSD Editor from the pop-up menu.
2. Click the Network tab in the Project Navigator, locate the appropriate CP, and
expand its ECB compound (<Station Name>_ECB) as shown in Figure 5-27.
3. Select the ECB, drag it into the CSD Editor, and position it near the I/O block.
See “Adding Blocks to a CSD” on page 159.
4. Make the appropriate connections using the steps described in “Making Connections”
on page 165.

174
5. Control Configuration B0700FE – Rev A

For example:
 Connect Input_1 in the first ECB to From_Fld1 in the input block.
 Connect To_Fld1 in the output block to Outpt_1 in the second ECB.
Note that the connection sets multiple parameters in the I/O blocks such as DEV_ID
and PNT_NO (Figure 5-27).
To connect to other points on the ECB, place their corresponding parameters
(Input_x or Outpt_x) on the ECB appearance object, as described in “Showing
Parameters” on page 170.

Figure 5-27. Adding an ECB to a CSD

175
B0700FE – Rev A 5. Control Configuration

Adding ECB Placeholders to a CSD Template

When you create a CSD Template to be used in Bulk Generation from the TagList Editor, all
inputs from and outputs to the field must be represented by an ECB placeholder. These generic
ECBs are updated to specific ECBs during Bulk Generation.
Do one of the following to locate the ECB Placeholder definition:
 Click the System tab in the Project Navigator and expand System > Library >
IA Block Types > ECB Placeholders.
 Select the ECB Placeholder palette in the Palette window (Figure 5-28).

Figure 5-28. Adding and Connecting an ECB Placeholder

You add and connect the placeholder in the same way you configure an ECB in a CSD (“Adding
ECBs to a CSD” on page 174).

176
6. Modifying Compounds
and Blocks
This chapter describes additional editors and tools for configuring control compounds and
blocks.
In addition to the CSD Editor and the Connection dialog box described in the previous chapter,
IACC provides the following tools for modifying compound and block parameters:
 The Properties dialog box enables you change parameter values, as described in this
section.
 The Definition Editor enables you to change parameter labels and other attributes in
standard block definitions, and add parameters in derived block definitions, as
described in “Derived Block Definitions” on page 183.
 The Execution Editor allows you to arrange the order in which compounds and
blocks are executed and to alter the Phase and Period parameters, as described in “Exe-
cution Editor” on page 186.
 Global changes to blocks can be made with a specialized block type called
IA Modifier. Refer to “Modifiers” on page 194 for additional information.
After the compounds have been downloaded to the CP, IACC provides the following tools for
testing and updating the control strategy:
 Quick Views
 Animated Loop Drawings
 Compare to CP Utility
 Database Synchronization
 Bulk Upload.
These tools are described in Chapter 11 “Downloading Control Blocks”.

177
B0700FE – Rev A 6. Modifying Compounds and Blocks

Properties Dialog Box

You can use the Properties dialog box to view and edit the parameter values for any IACC object.
To display the dialog box for a block:
 Right-click the object in the Project Navigator or its appearance object in an Editor
window, and choose Properties from the pop-up menu.
Figure 6-1 shows an example of the Properties dialog box for an ECB.

Title Bar
Tabs
Click to revert to
Parameter Label saved value.

Click to revert to
Saved Change
definition value.

Unsaved Change

Tooltip for
Failsafe Delay
(when enabled) Resize
Button
Buttons

Figure 6-1. Example of Properties Dialog Box

178
6. Modifying Compounds and Blocks B0700FE – Rev A

The tabs across the top of the dialog box allow you to display the parameters in various groupings.
The dialog box uses color-coding and bitmaps to indicate when parameter value changes have
been made, as described in Table 6-1.

Table 6-1. Parameter Change Indicators

Item Description
Identifies parameter values that you have changed in the Properties dialog
box during a previous editing session. Displayed only if the dialog box
was invoked from an object ready for downloading.
Identifies parameter values that you have changed in the Properties dialog
box during the current editing session. Displayed if the dialog box was
invoked from an object ready for downloading.
Identifies parameter values that you have changed in the Properties dialog
box during the current editing session.
It is displayed if the dialog box was invoked for any other object, such as
an object which is not ready for downloading.
Parameter Colors  Green indicates that you have edited the parameter value.
 A yellow background indicates that you have entered an invalid
value. It may be invalid for many reasons, such as using a duplicate
name. You are responsible for fixing the invalid entry.
 Black indicates a default parameter value inherited from a parent
definition.
 Blue indicates a parameter value derived from a formula. Clicking a
blue-colored value displays the associated formula.
Error! Displayed in a value field to indicate that you have entered an invalid
formula for that parameter value via the Properties dialog box.
Resets the parameter value to the last applied value.

Resets the parameter value to the definition value.

179
B0700FE – Rev A 6. Modifying Compounds and Blocks

To view and edit properties for a block:

1. Right-click the block in the CSD or in the Project Navigator, and choose Proper-
ties from the pop-up menu.
2. Click a tab to view values for the parameters in that group.
The label and value of each parameter in the group are listed in the tabbed list box.
3. Click a parameter value field to edit the value.
4. Place the cursor over a parameter label to view a tooltip describing that parameter
(Figure 6-1).
 Choose View > Toolbars to open a dialog box for enabling or disabling Tooltips
and other toolbar options.
Parameter values that are grayed out are not configurable.
5. Use the reset and set buttons to the right of the parameter value fields as needed.
 Click to reset parameter values to the last saved value.
 Click to set parameter values to the definition (default template) value.
6. Click Apply to apply changes without closing the dialog box, or click OK to make the
change and close the dialog box.

Adding a Formula to a Parameter Value Attribute

You can add a formula to object properties to calculate the parameter Value attribute, which is dis-
played in blue. Formulas are predefined with some extensions provided by IACC. Formulas begin
with an equal sign (=).
The Properties dialog box uses an advanced formula engine, which supports most of the formula
expressions in Microsoft Excel™ software. Figure 6-2 shows the entry of the formula
= 0.9*(N(HSCO1)N(LSCO1)) to set the high alarm limit attribute (Hal) in the AIN block
TI02 to 90% of the difference between the values of parameters HSCO1 and LSCO1.

Figure 6-2. Entering a Formula

180
6. Modifying Compounds and Blocks B0700FE – Rev A

Editing Logic Block Properties

CALC, CALCA, LOGIC, and MATH blocks provide logical function and arithmetic and Bool-
ean computational capability. The blocks have number of step parameters, each representing one
programming step. Use the Properties dialog box for these blocks to enter programming steps.
Refer to Integrated Control Block Descriptions (B0193AX) for information on the programming
step syntax.
The Properties dialog box for Logic blocks offers additional editing features that enable you to cut
and paste steps, insert and delete steps, and copy programing to other Logic blocks.
To edit step parameters:
1. Open the Properties dialog box for the block and click the Program Steps tab.
2. Select the steps you want to edit by dragging the cursor over the value fields.
3. Right-click at the end of your selection to display a pop-up menu (Figure 6-3).

Figure 6-3. Editing Math Block Programming Steps

181
B0700FE – Rev A 6. Modifying Compounds and Blocks

4. Choose an editing function from the menu:

 Copy To copy the selected steps to the clipboard. If you are copying
steps to another block, you can close the dialog box, open
Properties for the destination block, and paste the values from the
clipboard into the new block.
 Paste Pastes steps from the clipboard starting from the active step.
Displays a dialog box (Figure 6-4) if there are more steps on the
clipboard than steps selected in the dialog box (Figure 6-4).
 Insert Inserts steps from the clipboard starting at the active step position,
moving down all steps below. Displays a warning message
(Figure 6-4) if the number of steps on the clipboard exceeds the
number of steps between the active step and the last step in the
block
 Insert Opens a dialog box for specifying the number of steps to be
Empty inserted, and adds the empty steps starting at the active step
Steps position. The dialog box states the maximum number of steps that
can be added.
 Reset Resets the selected steps to the definition values.
 Delete Deletes the selected steps and moves up the steps below the
selected steps. Empty steps are inserted at the end of the block.

A dialog box warns you when the number of steps being pasted or inserted is greater
than the available steps in the blocks (Figure 6-4).

Figure 6-4. Warning When Paste or Insert Exceeds Available Steps.

5. Select OK to continue with the function or Cancel to make another selection.

NOTE
Branch offsets are not adjusted automatically when you insert or delete steps. You
are responsible for making the appropriate adjustments.

182
6. Modifying Compounds and Blocks B0700FE – Rev A

Derived Block Definitions

IACC enables you to derive custom control blocks based on the library of blocks included with
the software. These derived blocks inherit the algorithm and parameter attributes of the parent
block, which you can modify using the Definition Editor.
Each instance of a derived block definition inherits changes made to the definition after the block
is created except in cases where a parameter in an individual block has been changed.
To create a derived block:
1. In the Project Navigator System tab, expand the System > Library > IA Block
Types branch.
2. Right-click on the block branch, and choose New Definition in the pop-up menu.
The new block appears under the selected block with a number appended to the block
name. The new block has the same parameters and values as its parent until it is
modified in the Definition Editor. The default name in the Project Navigator is boxed
in and highlighted in blue. A blinking cursor at the end of the name indicates that it
can be changed.
3. Type the new name and press Enter.
Figure 6-5 shows a newly created and renamed block derived from the ACCUM
block.

Derived
Block
Definition

Figure 6-5. Block Definition Derived from the ACCUM Block

183
B0700FE – Rev A 6. Modifying Compounds and Blocks

4. Double-click the block to open the Definition Editor (Figure 6-6) and modify the
parameters as needed.
The Definition Editor presents the attributes of each block parameter in a spreadsheet
and enables you to modify the attributes. Initially, the block parameters are the same
as those of the parent I/A Series block. Only limited editing is allowed for parameters
that are downloaded to I/A Series systems. As a rule, you can modify any cell in the
editor that has a white background. For example, in Figure 6-6 you can change the
Label and Value Attributes of the HHAIND parameter, but you cannot modify the
Data Type.
You can also add parameters to the definition for use within IACC. Figure 6-6 shows
the parameter Param1 being added to a derived definition. Note that you can change
any attribute in this parameter. The added parameters are not downloaded to the
I/A Series system, but are used to propagate values from a TagList and automatically
generate other values in block parameters that are downloaded. See Intelligent Design
Studio (IDS) Library for IACC (B0400BQ) for examples of derived definitions.
Once a new parameter is defined, you can change its value in the definition or an
instance of the block using the Properties dialog box. The parameters can be displayed
in CSDs and connected to other parameters.
Like the Properties dialog box, the Definition Editor organizes the parameters in
various folders that you can select by clicking a tab at the bottom of the Definition
Editor window. The editor opens with the Standard tab selected. You can also sort the
rows on any attribute (for example, ID or Data Type) by clicking the column label.
Refer to the Definition Editor topic in IACC Help for a complete description of the
tools available in the editor.

184
6. Modifying Compounds and Blocks B0700FE – Rev A

Figure 6-6. Derived Block Definition Opened in the Definition Editor

To delete a derived block:

1. Right-click on the block in the Project Navigator and choose Delete from the pop-
up menu.
IACC opens the Delete Request dialog box showing the object affected by the
deletion.
2. Verify that the correct block name is present in the Deleted Object field of the dia-
log box, and click OK.

185
B0700FE – Rev A 6. Modifying Compounds and Blocks

Execution Editor
The Execution Editor enables you to view, edit, and schedule the order in which compounds and
blocks execute in control stations, and to change the Period and Phase parameters of compounds
and blocks. The editor is available from the following object types in the Project Navigator:
 Control station
 Compound (in either the Network tab or the Plant tab)
 CSD
 CSD Template.
This editor does not dynamically alter the order of objects in the database; you must actively save
the database changes to apply them, and then download the compounds and blocks to implement
the changes in the I/A Series system. Figure 6-7 illustrates a typical example of the Execution Edi-
tor.

Figure 6-7. Execution Editor Opened for a Compound

The editor allows you to:

 Reorder both compounds and blocks
 Revert the execution order back to the last saved order
 Set all block phases and periods to their parent compound’s phase and period
 Change the phases and/or periods of compounds and blocks
 Check the predicted control processor loading.
The order in which compounds and blocks are stored in IACC defines the order in which the
compounds and blocks are executed in the control station. The Execution Editor manipulates this
list of database objects in order to define the scheduling order of blocks and compounds within a
control station.

186
6. Modifying Compounds and Blocks B0700FE – Rev A

The editor reflects:

 Assignment of new blocks to a compound
 Unassignment of blocks from a compound
 Assignment of compounds to a control station
 Unassignment of compounds from a control station
 Deletion of blocks from IACC
 Deletion of compounds from IACC
 Renaming of blocks
 Renaming of compounds
 Execution Processing Time
 Control Station Loading.
Control Station Loading and Execution Processing Time are calculated and updated when you
open the Phase Loading dialog box. Execution Processing Time is shown as percent of Basic
Processing Cycle (BPC) in phase and compound/block loading dialog boxes.
Control Station Loading performs predicted station loading calculations. Station load is the total
control block load, that is, the load value for processing ECBs, Continuous blocks, and sequence
blocks.
Control Station Loading provides information about the station’s resources. The Control Station
Loading dialog boxes, identical for all stations, are used for each of the following types of stations:
 Application Workstations (AWs) with Control
 Control Processors (CPs)
 Integrators and Gateways.
You can use the Control Station Loading dialog boxes to determine:
 Percent of the station processor time being used to process:
 All blocks
 The compound’s total and each of its assigned blocks.
 Loading summary (% of BPC)
 Memory used in the station
 Cumulative block processor overruns.
The loading calculation predicts, but probably does not reflect the same value as the dynamic run-
time update in the CP. Station load is the total control block load, that is, the load value for pro-
cessing continuous blocks, sequence blocks, and ECBs. Since the predicted calculation cannot
include peer-to-peer connections and other overhead that may be introduced by the use of
sequence blocks, you should keep the predicted station loading calculation in the 60 to 65 percent
range.

187
B0700FE – Rev A 6. Modifying Compounds and Blocks

Block and Compound Processing

In a control processor, the compounds and blocks are executed at their designated periods and
phases under the control of the compound processor, a task scheduled by the operating system to
run periodically. The frequency at which the compound processor executes is called the basic
processing cycle (BPC), which is configured through the Parameter Editor.
The BPC is the smallest resolution of time in which the compound processor can be scheduled to
run. The frequencies range from 0.05 seconds to 2 seconds. It defaults to 0.5 second for a CP and
1 second for an Integrator. Periods are resolved in multiples of the BPC.
Figure 6-8 illustrates the order of compound processing during a single BPC.

Compound Processing

Continuous Continuous
Inputs block Sequence block Outputs
from algorithms block algorithms to
FBMs (1st list) processing (2nd list) FBMs

System
Block Processing Tasks

One Basic Processing Cycle (BPC)

Figure 6-8. The Basic Processing Cycle

Within each BPC, the compound processor task processes the blocks in the following order:
1. The first list of continuous blocks
2. Sequence blocks in this order:
a. Monitor blocks and timer blocks
b. Exception blocks
c. Dependent and independent blocks
3. The second list of continuous blocks.
Compounds are processed in the sequence in which they have been configured to execute. The
compound processor looks at every configured compound each time it executes. When the com-
pound processor finds a compound that is on and whose period and phase have arrived, it looks at
each block in the compound, and those blocks whose period and phase have arrived are executed.
Note that a block cannot be turned off. A block is off if, and only if, the compound it is in is off.
As with compounds, blocks are processed (within each compound) in the sequence in which they
have been configured to execute.
A PLB is processed in order just like any other block, but its associated ladder logic processing
takes place in the FBM asynchronously.

188
6. Modifying Compounds and Blocks B0700FE – Rev A

Data blocks are not processed, as they simply serve as holding places for data.
After the first list of continuous blocks is processed, the sequence blocks are processed before the
second continuous list. The second continuous zone is only needed if sequence logic does some-
thing that must eventually be sent to the field. You can put output blocks in this zone so that out-
puts are written in the same BPC. Without this zone the outputs must wait until the next BPC.
If all blocks to be processed during a particular phase have not been processed by the end of the
BPC, a compound process overrun occurs. All block scheduled to run during that phase continue
to run until they have finished. The next phase is delayed for one BPC.
The dynamics of a particular process can be quite diverse. Therefore, it is not be necessary or
desirable to process every block each time the compound processor executes. For example, flow
rates, which can change instantaneously, should be monitored often, while temperatures, which
change relatively slowly, can normally be monitored less frequently. To provide the flexibility to
regulate the frequency and timing of execution on a per block basis, each compound and each
block has a PERIOD parameter and a PHASE parameter.
The PERIOD parameter is used to specify explicitly how often the compound processor is to exe-
cute the compound or block. The value configured for the PERIOD parameter is an index into
the period table used by the control station.
The allowable user-specified scan periods are shown in Table 6-2. Note that the period values for
control processors are not in order of length. The fastest period is 13 and the default period is 1.
Note also that Integrators and Gateways have a different set of scan periods.

Table 6-2. Allowable Scan Periods

Scan Period Control Processors Integrators and Gateways

0 0.1 second 0.1 second
1 0.5 second 0.5 second
2 1 second 1 second
3 2 seconds 2 seconds
4 10 seconds 4 seconds
5 30 seconds 8 seconds
6 1 minute 16 seconds
7 10 minutes 32 seconds
8 60 minutes 64 seconds
9 0.2 second 128 seconds
10 5 seconds 256 seconds
11 0.6 second * 512 seconds
12 6 seconds** 1024 seconds
13 0.05 second***
* Not directly configured; automatically used by the CP when the BPC is 0.5 seconds and
the Period is 1 (0.5 seconds), since 0.5 is not evenly divided by 0.2.
** Not directly configured; automatically used by the CP when the BPC is 2 seconds and
the Period is 10 (5 seconds), since 5 is not evenly divided by 2.
***CP40, CP60, FCP270, and ZCP270 only.

189
B0700FE – Rev A 6. Modifying Compounds and Blocks

Compounds process in the order in which you install them using IACC, subject to variations due
to differences in their periods and phases. You can rearrange the order using the Execution Editor
on the control station level. Within the compound, blocks also process in the order in which you
install them, create them, and rearrange them with the Block Execution Editor. As with com-
pounds, you can modify the execution sequence by means of the period and phase parameters.
If the configured period is less than the BPC, the compound or block is run at the BPC.
Phases and periods can be adjusted in individual blocks to alleviate potential overloading situa-
tions. An overrun occurs when a processor has more blocks than it can process within a single
Block Processing Cycle (BPC) as described in “Overruns” on page 192.

Block Phasing
Phasing is the distribution of the block processing over multiple BPCs. The object is to limit the
number of blocks scheduled for processing in any given BPC. When the block period is equal to
the BPC, the block is processed every cycle and there are no phasing options. However, when the
block period is greater than the BPC, the block can be phased to execute at some time other than
the very beginning of the period. This feature is useful in avoiding overruns. Overruns occur
when too many blocks are scheduled for execution at the same BPC.
The Execution Editor enables you to view, edit, manipulate and schedule the order in which com-
pounds and blocks execute in control stations.

Relationship Between Block Period and Phase

Block periods greater than the BPC are always equal to an integral number of BPCs. For example,
when the BPC is 0.5 second, a block period of 2.0 seconds equals four BPCs, and the block
executes every fourth cycle (Figure 6-9).
The Phase value determines whether block execution occurs at the 0 count, the 1 count, the 2
count, or the 3 count. A Phase value greater than three in this example exceeds the maximum and
the block is never executed. IACC generates a warning for invalid period and phase combinations.

2 seconds

Phase 0 1 2 3 0 1 2 3 0 1 2 3

Blocks with Period = 3 and Phase = 0 execute here.

Figure 6-9. Result of Sample Period and Phase Settings

190
6. Modifying Compounds and Blocks B0700FE – Rev A

Generally, the valid phase values are the integers from 0 to N-1, where N equals the number of
BPCs in the period. Table 6-3 lists the phase values for a CP that has a BPC of 0.5 seconds.

Table 6-3. Valid Phase Values for a BPC of 0.5 Seconds

Period Phase
Value Length Values
0 0.1 second [0] runs at BPC
1 0.5 second [0] default
2 1.0 second [0,1]
3 2.0 seconds [0,1,2,3]
4 10 seconds [0 - 19]
5 30 seconds [0 - 59]
6 1 minute [0 - 119]
7 10 minute [0 - 1199]
8 60 minute [0 - 7199]
9 0.2 seconds [0] runs at BPC
10 5.0 seconds [0 - 9]
11 0.6 seconds Not used
12 6.0 seconds Not used
13* 0.05 seconds [0] runs at BPC
* Available with CP40 and CP60 only

Thus, a block having a PERIOD/PHASE parameter assignment of 3/1 executes every 2.0 seconds
in the second BPC frame of the 2 second period.

NOTE
You cannot assign an invalid phase value in IACC. Assigning a phase value not
listed in Table 6-3 results in a warning, caught by download validation in IACC.

191
B0700FE – Rev A 6. Modifying Compounds and Blocks

Overruns
An overrun occurs when a processor has more blocks that it can process within a single scan cycle.
During a scan overrun, the compound processor continues to process blocks even after the allo-
cated period for the cycle is over, delaying the next phase by one BPC. When finished, the com-
pound processor waits until the beginning of the next scheduled BPC to begin the next
execution.
An overrun guarantees that the control operation goes to completion, but it also results in the loss
of a processing cycle and the skewing of succeeding cycles. An occasional overrun may not affect
control, but repeated occurrences must eventually degrade process control. Anything that must
run at a particular time or a specified number of times per minute can be adversely affected.
To alleviate a potential overrun situation, the block phasing should be adjusted for the extra
blocks causing the overrun. Configuring block phasing balances out the load on the CP database
by spreading block processing evenly throughout the BPCs.
Control Processor (CP) Loading dialog boxes assist you in preventing overruns by displaying:
 Each phase and each phase’s loading
 For each phase the breakdown of contributions from the compounds (all block contri-
butions for a compound summed)
 For each phase the individual block loading
 For each phase the percent of overrun.

NOTE
Often sequence logic is a large factor affecting control cycle loading. If you are
experiencing overruns, this is the first place to check.

Block Phasing: Cautions and Guidelines

Phase configuration should take into account a block’s position in the control scheme, its
workload, the number of active options, and so on.

NOTE
For compounds, it is recommended that you use the default period and phase set for
by IACC.

Compound Phasing
 The system defaults the compound period to the system BPC, and the compound
phase to 0.
 Compounds execute in the order in which they are set in the Execution Editor
(not the CSD or the compound in the Project Navigator).
 Phasing should be checked whenever the execution order of compounds is changed to
ensure the new order does not cause any scan overrun.

192
6. Modifying Compounds and Blocks B0700FE – Rev A

Control Block Phasing

 All block phasing is on a global basis. Phase 0 is common to all blocks, compounds
and ECBs.
 Block execution order and control processor loading are the major considerations
when any phasing is to be configured. Normally, block execution order in a control
loop should be set up so that the feedback measurement input blocks execute immedi-
ately before the control blocks, and the output blocks should immediately follow the
control blocks. If all blocks in a control loop are in the proper order and have the same
period and phase, then block initializations and bumpless transfers work properly.
 In cascade strategies, the primary blocks should execute before the secondary blocks.
Execution of feedforward blocks should be sequential in the data flow direction.
 If a phase value is configured outside of the legal phase values for the assigned period
value, the block, compound, or ECB is never processed. A warning message is dis-
played in IACC and the block, compound, or ECB object status is set not valid, or
undefined, and cannot be downloaded to the control processor. If you reduce the
period value, the existing Phase value is verified to ensure that it is within the legal
range for the new period value. IACC prevents you from downloading objects that
have incorrect phase values.

NOTE
To avoid situations in which changing the period or phase of a block or compound
results in a combination that cannot be downloaded, leave the compound period
and phase at default if there is no severe loading problem.

 If you change a compound period and phase, make sure that the blocks in the
compound run during the same phase as the compound.
For example, for a BPC of 0.5 seconds, a compound period at 2 seconds, and a
phase of 0, you cannot set the block period to 2 seconds and the phase to 1, 2, or 3.
However, in a compound with a period of 2 seconds, you can have a block with a
period of 10 seconds and a phase of 0, 4, 8, 12, or 16 because each one of these phases
aligns the 2-second compound running at phase 0.

Block Execution Order

Typically, control processors follow a specific block processing order by type:
 Equipment Control Blocks
 Pre-Sequence Continuous Blocks (Continuous 1)
 Sequence Blocks
 Post-Sequence Continuous Blocks (Continuous 2)
Blocks in the IACC database conform to this sequence. However, within a specific type you can
sort blocks in any order, and you can assign continuous blocks to pre- or post-sequence
processing.

193
B0700FE – Rev A 6. Modifying Compounds and Blocks

When the Execution Editor is initialized, the currently defined block order is validated. If the
block order does not adhere to the sequence described above, a default valid execution order is
created and saved to the database. A message notifies you that the blocks have been reordered in
the unlikely event that the order is incorrect before the Execution Editor is opened. If you make
changes to the order and decide to create a default order before saving the block, you are allowed
to, but no message is generated to that effect.

Modifiers
A modifier is a special block type used within IACC to make global changes to common
parameters in selected blocks or to all blocks in a CSD and to the CSD itself. Modifiers are not
downloaded to the I/A Series system.
Applications of this configuration tool include:
 Changing Period and Phase setting in all blocks in a CSD
 Switching all blocks from manual to automatic before downloading them to an
I/A Series system
 Adding labels to a CSD indicating revision levels or other important information
 Connecting I/O blocks to a simulation and then reconnecting the I/O to actual field
devices after testing.
Three modifier types are supplied with IACC and are located under System > Library in the Proj-
ect Navigator System tab (Figure 6-10):
 IA Modifiers Applied to individual blocks. For example, you can
create a modifier in this class that includes the MA
(manual/automatic) parameter and attach the definition to a
number of blocks in various CSDs. You can then change the
MA parameter of the selected blocks using the Properties
sheet of the modifier.
 IA Mod Traverse Attached to a CSD or a compound. Changes made to the
Blocks modifier are propagated to each block in the CSD or
compound. For example, you can create a modifier of this
type to change Period and Phase parameters of blocks in
multiple CSDs by making a single change in the Properties
sheet for the modifier definition, or to a CSD by changing
the modifier instance attached to the CSDs.
 IA Mod Traverse Attached to a CSD and its blocks to modify block parameters
CSDs and Blocks and CSD properties. For example, you can create a modifier
of this type to add a set of label parameters which are used
each time the CSD is displayed or printed.

194
6. Modifying Compounds and Blocks B0700FE – Rev A

Figure 6-10 shows the IA Modifiers Definition opened in the Definition Editor. The modifier
definition includes only 12 parameters. You cannot add parameters to this definition (or to
IA Mod Traverse Blocks or IA Mod Traverse CSDs and Blocks).
To use a modifier, you must derive a definition from one of the three, and add parameters and
modify parameters as you would for a custom block definition (as described in “Derived Block
Definitions” on page 183).
The parameters you add to a modifier can be included in one or more of the modifier definition’s
parameter groups:
 ADD Adds the parameter to the attached object when the modifier type is
attached.
 MODIFY Modifies the parameter in the attached object when the modifier
type is attached.
 DELETE Deletes the parameter in the attached object when the modifier type
is attached.

Figure 6-10. Location of the Modifier Types

195
B0700FE – Rev A 6. Modifying Compounds and Blocks

Creating an IA Modifier
To define a new IA Modifier:
1. Right-click IA Modifiers and choose New Definition from the pop-up menu.
The new modifier appears under IA Modifiers with a default name, such as
IA Modifiers1. A rectangle appears around the new definition to indicate that you can
edit the name.
2. Type the new name (such as AutoMan) and press Enter.
3. Double-click the new object to open it with the Definition Editor.
4. Choose Edit > Add New Parameter from the menu bar to insert Parm1 to the
definition.
You can edit any attribute in this parameter.
5. Change parameter name and data type to match those of the parameter you want to
control with the modifier.
For example, to change the MA parameter in the target blocks, enter MA in the
Parameter column and use the pull-down list in the Data Type column to select
Boolean (Figure 6-11).

Figure 6-11. Adding a Parameter to an IA Modifier

196
6. Modifying Compounds and Blocks B0700FE – Rev A

6. Assign the new parameter to the Modify group:

a. Click the Modify tab and choose Edit > Add Remove Parameter(s) To
Group from the menu bar.
b. Select the parameter (MA for example) in the Add Remove Parameter(s) To Group
dialog box and click OK (Figure 6-12).
If you add new parameters to the definition from the Modify tab, the new
definitions are automatically assigned to the Modify group.

Figure 6-12. Assigning the MA Parameter to the Modify Group

7. Choose File > Close from the menu bar to close the Definition Editor.
Once you have defined the modifier, you can update the parameter values using the
Properties dialog box, modify its appearance object and add the definition to All User
or IA User palettes.

197
B0700FE – Rev A 6. Modifying Compounds and Blocks

To add the Modifier palette:

1. Open the palette in the Palette window.
2. Select the modifier in the Project Navigator and drag it to the Palette window.
Figure 6-13 shows the AutoMan Modifier type opened in the Appearance Object
Editor and listed with two other modifiers in a user-created Modifier palette.

Figure 6-13. AutoMan Modifier Appearance Object and Modifiers Palette

198
6. Modifying Compounds and Blocks B0700FE – Rev A

Applying an IA Modifier
To apply an IA Modifier:
1. Select the Plant tab and expand the display to show the target blocks.
2. Click the System tab and expand System > Library > Modifiers > IA Modifiers
to display the modifier you want to apply.
3. Drag the definition down to the Plant tab to switch to the Plant view of the Project
Navigator.
4. Drop the definition on the target block.
The modifier is attached to the block and is displayed underneath the block in the
Project Navigator. When the block is opened in the CSD Editor, the modifier is
displayed in the CSD and a connection is drawn between the modifier and the target
block (Figure 6-14).

Figure 6-14. Modifier Attached to Two I/O Blocks

You can also attach a modifier by dragging the modifier from a palette and dropping it
on the block object in the Project Navigator or the CSD Editor.
5. Drag and drop the definition to other blocks you want to control with the modifier.

199
B0700FE – Rev A 6. Modifying Compounds and Blocks

6. Right-click the modifier definition in the Project Navigator, choose Properties

from the pop-up menu, and click the Modify tab in the Properties dialog box
(Figure 6-15).
7. Change the parameter value in the Modify tab and click OK.
The parameter value is changed in each of the blocks to which the modifier is
attached. Of course, there is no change if the target object does not have the
corresponding value. For example, the AutoMan modifier would have no affect if it
were attached to a compound, as the compound does not have an MA parameter.

Figure 6-15. Changing the MA Parameter in Attached Blocks

200
6. Modifying Compounds and Blocks B0700FE – Rev A

IA Mod Traverse Blocks

Modifiers derived from the IA Mod Traverse Blocks definition are used to make global changes to
all blocks in a CSD or all blocks in a compound. For example, you could create a modifier with
the Iomopt parameter in the Modify group and attach it to multiple CSDs to switch between
using signals from the field and using input from a simulation block. Figure 6-16 shows the
ChangeIO modifier attached to the Level Simulation CSD. Note that there is an instance of the
modifier (ChangeIO1) attached to each block in the CSD. The attached modifiers are also visible
in the TANK_SIM compound. When the CSD is opened in the CSD Editor, the modifier
appearance object is shown connected to the blocks affected by the object’s Modify group
parameters (the PID block in Figure 6-16).

Figure 6-16. Modifier Attached to a CSD

To change block parameters in one CSD:

1. Expand the CSD object display in the Plant tab, right-click the modifier instance
(ChangeIO1), and choose Properties from the pop-up menu.
2. Click the Modify tab, make the appropriate changes, and click OK.
To change block parameters in all CSDs to which the modifier is attached:
1. Click the System tab, and expand System > Library > Modifiers > IA Modifi-
ers > IA Mod Traverse Blocks to display the definition.
2. Right-click the modifier definition (ChangeIO), choose Properties from the pop-
up menu, change the parameter, and click OK.

201
B0700FE – Rev A 6. Modifying Compounds and Blocks

IA Mod Traverse CSDs and Blocks

Figure 6-17 illustrates a use of modifiers derived from the IA Mod Traverse CSDs and Blocks.
A modifier, Labels, was derived from IA Mod Traverse CSDs and Blocks and applied as follows:
 Two parameters, Project and Test Phase, were defined and included in the Add and
Modify groups.
 The modifier was attached to the Level Simulation CSD.
 A text box was added to the CSD and configured to display the parameter values
([.Project] - [.Test Phase]).
See the Graphics Tools topic in IACC Help for additional information on adding text
boxes to CSDs.
 The Project parameter was added to the information area of some of the blocks in the
CSD.
 The Properties sheet for Labels1 was used to change the Project and Test Phase param-
eters to Orion II and Beta Test, respectively.
 The labels appeared when the CSD display was refreshed (Figure 6-17).

Figure 6-17. Parameters Added to a CSD and Its Blocks

202
7. Sequence Blocks
This chapter describes the configuration of sequential control in IACC.
The I/A Series system provides five software blocks for configuring sequential control:
 DEP - Dependent sequence
 EXC - Exception
 IND - Independent sequence
 MON - Monitors
 TIM - Timers.
You can configure instances of these blocks, and of block definitions derived from standard
I/A Series blocks, applying the same techniques used to create and connect continuous control
blocks such as PID and PIDA. The TIM block definition includes sequence code as part of the
block definition. The other four blocks are containers for code that you develop with the Foxboro
High Level Batch Language (HLBL) using the ST Code Editor built into IACC.
For DEP, EXEC, and IND, you can alternatively use FoxSFC software to develop code using
sequential function charts. FoxSFC is a separate optional software package that operates on
I/A Series workstations. IACC interfaces with the application when IACC is installed on a
workstation that has FoxSFC 1.1 or later installed. You access the FoxSFC using a pop-up menu
from the DEP, EXEC, or IND object, develop and compile the code using the editor, and then
return to IACC when you close the editor. The compiled SFC code is stored in the IACC data-
base. You cannot access the SFC code without calling the editor from IACC.
The ST Code Editor and FoxSFC are mutually exclusive. You cannot access a block with the
ST Code Editor once you have opened the block with FoxSFC, and vice versa.
Which ever editor you select, you add the code to a sequence block instance, not to a standard or
derived sequence block definition.
For additional information about HLBL code, sequence function charts, and sequence blocks,
refer to:
 Integrated Control Block Descriptions (B0193AX)
 High Level Batch Language (HLBL) User’s Guide (B0400DF)
 Sequential Function Chart/Structured Text Configurator and Display Manager for
Sequence Blocks (B0193UZ).

203
B0700FE – Rev A 7. Sequence Blocks

Creating a Sequence Block Instance

The sequence blocks are located in the Project Navigator under System > Library > IA Block
Types > ST Blocks > SEQ Blocks and in the Sequence palette, one of the standard Foxboro
palettes. You can derive custom block definitions from any of the sequence block definitions,
include standard and derived definitions in any ALL User or IA User palette, and add instances of
the sequence blocks to CSDs and CSD Templates.
To create a sequence block instance:
1. Select the CSD in the Plant tab or the CSD Template in the System tab.
2. Open the Palette window, and use the pull-down list to select the Sequence palette.
3. Select one of the blocks (DEP, EXC, IND, or MON) and drag it into the CSD in the
Editor window.
4. Connect the block to other blocks in the CSD and assign the block to a compound as
you would for a continuous control block.
You now create HLBL code for DEP, EXEC, IND, and MON blocks using the ST Code Editor
as described in “Creating HLBL Code” on page 205. Or, for a DEP, EXEC, or IND block, you
can open FoxSFC Editor to develop code, as described in the next section.

Using FoxSFC
To develop code using FoxSFC:
1. Right-click the block instance in the Project Navigator and choose Editors >
SFC Editor from the pop-up menu.
IACC launches the FoxSFC Editor.
2. Develop and compile the code as described in the Sequential Function
Chart/Structured Text Configurator and Display Manager for Sequence Blocks
(B0193UZ).
IACC is locked while FoxSFC is open. When you close the editor, the compiled code
is stored in IACC. The next time you select the editor from the block’s pop-up menu,
the FoxSFC extracts the code from IACC.

NOTE
IACC does not store library items and #include files, so you must make sure that
these resources are included on the appropriate workstations.

3. Complete configuration of the CSD and download the control compound to the CP.

204
7. Sequence Blocks B0700FE – Rev A

Creating HLBL Code

The ST Code Editor is a specialized text editor that enables you to enter, check, and compile
HLBL text.
The editor contains an Instance Wizard that you use to insert and modify ST Templates. An ST
Template is a framework containing pieces of commonly used code that is assembled through the
use of a question/answer interface. You can insert ST Templates into HLBL programs to provide
re-usable code for similar process control applications. The templates are located under System >
Components > ST Templates > SEQ Template Types > SEQ_TMPL. You create the templates
using the ST Template Editor, graphical editor for creating code by inserting and connecting deci-
sion point and code objects.
You populate the template with two different types of objects:
 ST Decision Points, which provide question and answer sequences for selected code.
There are three types of questions that can be configured:
 Boolean
 Multiple Choice
 Replicate, which allow you to insert a loop with a specific number of iterations.
 ST Code Items, which are placeholders in an ST Template for code.
You can edit the contents of an ST code item using the ST Code Editor.
IACC also enables you to develop a library of Text Objects, which contain ST code snippets. You
can copy and paste the snippets into the sequence blocks to specify #include files and re-use text.
Texts objects are stored in System > Library > Text Objects.

205
B0700FE – Rev A 7. Sequence Blocks

Opening the ST Code Editor for a Sequence Block

To open the ST Code Editor:
 Right-click the sequence block instance in the Project Navigator and choose
Editors > STCodeEd Editor from the pop-up menu (Figure 7-1).

Figure 7-1. Opening the ST Editor

206
7. Sequence Blocks B0700FE – Rev A

The sequence block ST code is ready to be configured.

The code can contain:
 A heading
 A subroutine section
 A standard block exceptions section
 A main statement section.
While entering HLBL code, you can insert ST Templates using the Instance Wizard.
For sequence blocks, values outside the subroutine are transported by assigning the value to a user
parameter, a local variable, or an INOUT argument. Refer to the High Level Batch Language User’s
Guide (B0400DF) for details on the HLBL language.

Inserting an ST Template Using the Instance Wizard

The Instance Wizard allows insertion of the selected ST Template into the current ST Code
Editor window. The Instance Wizard is available only for sequence blocks and ST code items.

NOTE
An ST Template must be validated before it can be inserted into HLBL code.

To insert an ST Template into the code:

1. Right-click the point in the code where you want to instantiate the template and
choose Instance Wizard from the pop-up menu (Figure 7-2).

Figure 7-2. Instance Wizard Menu

207
B0700FE – Rev A 7. Sequence Blocks

The Instance Wizard dialog box appears (Figure 7-3).

Figure 7-3. Instance Wizard Dialog Box

2. Click Template to display the Open Template dialog box.

3. Select the ST Template you want to instantiate and click Open.
The Instance Wizard displays the ST Template name in the title bar, a default name in
the Reference Name field, and the template’s first question in the Text field in
Question Properties group.

NOTE
If the ST Template you want is listed as invalid, you must validate the ST Template
using the ST Template Editor, as described in “Validating the Template” on
page 223.

4. In the Reference Name text box, enter the name you want to assign to this
ST Template reference.
Each reference must have a unique name.

208
7. Sequence Blocks B0700FE – Rev A

5. Use the Reference Type pull-down list to choose one of the following:
 Copy to place native code directly into the block. Subsequent changes to the tem-
plate have no effect on this template reference.
 Link to place a template reference into the block. When the reference is
expanded, it uses the most recent validated version of the template. The template
reference also saves the answers to the questions so they can be modified later.
6. Use the pull-down list in the Answer field to select the appropriate answer for the
question, and click Next.
The current question and its answer appear in the spreadsheet in the middle of the
Instance Wizard dialog box. The next question in the selected ST Template is
displayed in the Question Properties field.
To change an answer, display the question in the Question Properties file, and press
the Back button. You must re-enter the answer for any question that you pass over as
you go backwards.
When all the questions in the template and nested template have been answered, the
Insert button becomes selectable.
7. Click Insert.
The ST Code Editor window reappears with the ST Template reference in place.

NOTE
If you linked to a template, the names of each question and its answers are displayed
in the ST Template reference.

Modifying a Template Reference

You can also use the Instance Wizard to modify ST Template references:
1. Click the reference in the ST Code Editor, so that the entire reference is highlighted.
2. Right-click inside the reference and choose Modify Template Reference from the
pop-up menu.
The editor opens the Instance Wizard; the Insert button changes to Modify.
3. Use the tools in the wizard to change the template or the answers, and click Modify.

Expanding and Collapsing an ST Template Reference

An ST Template reference is essentially a placeholder for a set of HLBL code. You can expand
an ST Template reference to list its complete HLBL code, and collapse this code back into a
reference. The complete HLBL code is treated as if it were a single character, similar to the
ST Template reference.
To expand or collapse an ST Template reference:
1. Click the ST Template reference in the ST Code Editor so that the entire reference is
highlighted.
2. Right-click inside the highlighted reference and choose Expand/Collapse Tem-
plate from the pop-up menu.
3. Repeat the procedure to switch back.

209
B0700FE – Rev A 7. Sequence Blocks

Converting an ST Template Reference to HLBL Code

An ST Template reference is essentially a placeholder for a set of HLBL code, which is inserted
into the code of the sequence block during compilation. You can convert any ST Template refer-
ence into the HLBL code that the template represents using the ST Code Editor. This allows you
to see how the complete code text appears for the sequence block; however, you cannot collapse it
back to a link.
To convert an ST Template reference to HLBL code:
1. Click the ST Template reference in the ST Code Editor so that the entire reference is
highlighted.
2. Right-click inside the highlighted reference and choose Convert Link to Code
from the pop-up menu.
The ST Template reference is converted to ASCII text.

Deleting ST Template Reference

You can delete an ST Template reference in the ST Code Editor.
To delete an ST Template reference:
1. Click the ST Template reference in the ST Code Editor so that the entire reference is
highlighted.
2. Press the Delete key.
The ST Template reference is deleted.

Creating and Editing Text Objects

Text objects are library objects that contain ST code and can be inserted into the sequence block
code. Text objects are stored in System > Library > Text Objects.
You create text objects using a pop-up menu in the Project Navigator and add code to the object
using the ST Code Editor.

Creating Text Objects

To create a text object:
1. In the Project Navigator, expand System > Libraries > Text Objects.
2. Right-click Text Objects and choose New Text Object from the pop-up menu.
A new object with a default name such as Text Object1 is added under the Text
Objects branch. The name is enclosed in a rectangle indicating that you can change
the name.
3. Type a new name and press the Enter key.
To add code to the text object:
1. Double-click the object to open the ST Code Editor.
2. Create program code for the code item using the techniques used for sequence blocks.
3. Verify, compile, and save the code in the text object.

210
7. Sequence Blocks B0700FE – Rev A

ST Templates
The ST Template Editor is a graphics-based editor in which you can create and verify Structured
Text (ST) Templates, which contain re-usable code segments. When you insert the template into
Sequence block program, the code is assembled through the use of a question and answer inter-
face. The template consists of ST decision points and code items (Figure 7-4).
ST Templates are built as a pipeline with a single starting point leading to multiple branches. An
ST decision point defines the branches that the template can take. When a specific piece of code
is required at a certain point, a user-configured ST code item contains it. Since a pipeline is best
described visually, ST Templates are modified using a graphics-based editor. When you change
the contents of an ST Template, all instances of the template automatically change.

Multiple Choice
ST Decision

Boolean
ST Decision

ST Code

Figure 7-4. Typical ST Template with ST Decision and ST Code Items

ST items are the elements from which a ST Template is built. ST items are not available in the
Project Navigator, but can be selected from the Palette window.
ST items are arranged in a flowchart formation when they are incorporated into an ST Template.

211
B0700FE – Rev A 7. Sequence Blocks

The following are available ST Template items:

 ST decision points – defines a certain point in a ST Template where a control
question is asked during instantiation. Based on the answer, the ST decision routes to
another ST Decision Point or to an ST code item.
 ST Code Item – contains user-specified code that may be invoked from an ST
decision point.
 Control Questions – questions used at decision points that lead to the inclusion or
exclusion of ST items within the ST Template. Control questions can be Boolean,
multiple choice, or replication (looping) type questions providing for value
substitution in addresses, parameter names, strings, and numeric constants.
 Substitution Questions – used for placing program parameter names or other types of
variable data at certain locations in the ST Template allowing them to be dynamically
substituted within ST code items.
The following example describes the use of a substitution and control question:
If you required a program to control three different pressures (0 to10 psi, 0 to 50 psi,
50 to 300 psi), you could write three separate programs, or you could write one
re-usable program. The one re-usable program can contain control questions that
allow you to substitute a template containing the program variables for the three
different pressures.
ST decision and ST code items are created by dragging them from the ST palette. Control
questions and substitution questions are created in the ST Template Editor. Each instance of
these ST items is configurable via dialog boxes in the ST Template Editor. You can insert the
template code into another program by copying or linking the template by reference. The ST
Template verification does not look at the code or code syntax allowing the template to contain a
variety of information.

NOTE
No control question can have the same name as a substitution question.

Creating an ST Template
To create an ST Template:
1. Expand System > Components > ST Templates > SEQ Template Types >
SEQ_TMPL in the Project Navigator.
2. Right-click SEQ_TMPL and choose New ST Template from the pop-up menu.
The new ST Template appears in the branch under the template definition from
which it was created. The name is enclosed in a rectangle indicating that you can
change the name.
3. Type a new name and press the Enter key.

212
7. Sequence Blocks B0700FE – Rev A

Modifying an ST Template
To modify an ST Template:
1. Double-click the template instance in the Project Navigator to open Template Editor.
2. Use the ST Template Editor to:
 Set the ST Template properties
 Create and edit ST code blocks (ST code items)
 Create and edit ST decisions
 Connect ST code and ST decisions
 Validate the ST Template.
You can create either an ST code item or a decision to act as the starting point of the ST Tem-
plate, depending on the requirements of the control strategy. ST code items are placeholders that
contain a segment of the program code. ST decisions contain a question whose answer varies
depending on the input.

Setting the ST Template Properties

Set the properties of the ST Template using the ST Template Properties dialog box.
The ST Template Editor must be open for the ST Template in order to perform this procedure.
To set the ST Template properties:
1. Choose View > Template Properties from the menu bar to open the Template
Properties dialog box.
2. In the Template Name text box, type the name of the ST Template.
3. In the Short Description text box, write a short description of the purpose of the
ST Template.
4. In the Help Info text box, describe the function of the ST Template in detail.
5. In the Template Instantiation Type box, check a box to indicate the types of
instantiation you want the ST Template to have:
 Copy Instantiation allows the HLBL code contained in the ST Template to
be inserted into a sequence block.
 Link Instantiation allows the HLBL code contained in the ST Template to
be inserted by reference into the sequence block.
When you link, the name of the question and the questions control answer is
contained in the code after the template is instantiated.
6. Click OK to apply your property changes, and close the Template Properties
dialog box.

213
B0700FE – Rev A 7. Sequence Blocks

Creating ST Code Items

To create an ST code item:
1. Use the pull-down list at the top of the Palette window to select the Structured
Text palette.
2. Drag an ST code object onto the ST Template Editor window.
To modify the properties of an ST code item using the Code Properties dialog box:
1. Right-click on the ST code item and select Code Properties from the pop-up
menu to display the Code Properties dialog box (Figure 7-5).

Figure 7-5. Code Properties Dialog Box

2. Enter a code name and description in the relevant text boxes in the dialog box.
The code name must be unique among blocks within the template.
3. Click OK.

214
7. Sequence Blocks B0700FE – Rev A

Creating ST Decisions
To add a decision point to the template:
1. Use the pull-down list at the top of the Palette window to select the Structured
Text palette.
2. Drag the Decision object into the ST Template Editor window.
To create and link decision properties:
1. Right-click on the ST code item and select Decision Properties from the pop-up
menu.
The Decision Point Properties dialog box appears (Figure 7-6).

Figure 7-6. Decision Point Properties Dialog Box

2. Enter the Decision Point Name and Description.

At this point, you can select an existing question using the Question Name pull-
down, in which case the other fields in the Question Configuration group are filled in
automatically based on your choice. Or, you can create a new question by completing
this sequence.

215
B0700FE – Rev A 7. Sequence Blocks

3. Click New Question.

The Control Question Properties dialog box appears (Figure 7-7).

Figure 7-7. Control Question Properties Dialog Box

4. Enter the Question Name, Question Text and Help Info into the appropriate
fields on the dialog box.

NOTE
All control question and substitution question names must be unique.

5. Select the Question Type: Boolean, Multiple Choice, or Replicate, and configure the
answers as follows:
 For Boolean there is no additional configuration required.
 For each Multiple Choice option, click Add, enter the choice in the selection
dialog box that is displayed (Figure 7-8), and press Enter key.

Figure 7-8. Control Question Properties Dialog Box for Multiple Choice

216
7. Sequence Blocks B0700FE – Rev A

 For Replicate, specify the minimum and maximum number of times to repli-
cate the referenced code object.
A replication question inserts a loop into the sequence block program back to the
previous code item. When the template is inserted into the code, the Instance
Wizard prompts you to specify the number of iterations. In the Control Question
Properties dialog box, you specify the minimum and maximum number of itera-
tions allowed by the Instance Wizard. The minimum iteration must be at least 1.
6. Use the Default Answer pull-down list to select a default answer to be presented by
the Instance Wizard:
 For Boolean, select True or False.
 For Multiple Choice option, select one of the answers in the Choice List list
box.
 For Replicate, select one of the values in the range you specified.
7. Click OK.
The Decision Point Properties dialog box reappears (Figure 7-9) and displays the
control question name, type, and text.

Figure 7-9. Decision Point Properties Dialog Box

217
B0700FE – Rev A 7. Sequence Blocks

8. Select Question Link.

The Control Question Selection dialog box appears (Figure 7-10) so you can add,
edit, or delete control questions that are not linked to any decision points.

Figure 7-10. Control Question Dialog Box

9. Click the Where is Question Used? button.

A list of decision point names where the question is used is displayed in the Output
window.
10. Select the question that you want to link to this decision and click Use Question.
The Decision Point Properties dialog box reappears (Figure 7-9).
11. Click OK.
The ST decision is now identified by the new name.

218
7. Sequence Blocks B0700FE – Rev A

Connecting Objects in the ST Template Editor

Figure 7-11 illustrates an ST Template with the ST code and decision items with their input/out-
put connections linked together. You must answer and complete the decision and code questions
prior to connecting blocks; otherwise, you are prevented from connecting the blocks.
When creating an ST Template, you make connections between blocks by creating a link between
the input and output connections. Connections are directional. Begin a connection on an output
point and end on an input point.
Objects must have an available connection. For example, a Boolean decision point allows only
two output connections.

Input/Output
Connection

Figure 7-11. ST Template Example

219
B0700FE – Rev A 7. Sequence Blocks

To link ST code items and decisions:

1. Move the cursor over one of the parameter ports that you want to connect.
Parameter ports for ST code items are two dots on the top and bottom of the code
item. Parameter ports for ST decisions are the four corners of the decision itself. The
cursor changes to .
2. Drag the cursor over the other parameter port to which you want to connect the first
parameter port until the same cursor symbol appears.
3. Release the left mouse button.
If the link is valid, a line appears between the two ports, with an arrow indicating the
direction in which data travels between the two ports. If you move either of the blocks
around, the line representing the link adjusts itself as well.
When you connect a decision point to another object, a Branch Choice dialog box
appears (Figure 7-12) listing the available answers to the control question assigned to
this ST decision point.
4. Select the answer for this link in the Select a choice field, and click OK.

Figure 7-12. Branch Choice Dialog Box

Boolean Decision Points

Figure 7-11 shows links for two decision points that are configured as Boolean questions, and
Figure 7-12 the Branch Choice dialog box for a Boolean question. For a Boolean decision point,
you connect each of the two available ports to a code item or another decision point.
When the template is inserted into the Sequence block code, the Instance Wizard prompts the
user to select either True or False, and includes the appropriate code item based on the answer. For
example, when you instantiate the template in Figure 7-11, you are first presented with the Tank
Choice question. If you select False, the Instance Wizard inserts the Initial Vars A code item and
then Valve Code. If you select True, the wizard inserts Initial Vars D, and then presents the Abort?
question. If you select False for this second question, the wizard inserts the Valve Code. If you
select True, the wizard inserts the Abort Code and then the Valve Code.

220
7. Sequence Blocks B0700FE – Rev A

Multiple Choice Decision Points

Figure 7-13 shows a multiple choice decision point connected to five different code items. As you
connect the decision point to a code item, the Branch Choice dialog box prompts you to enter the
answer that should lead to the code item.

Figure 7-13. Multiple Choice Decision Point Linked to Five Code Items

When the template is inserted into the sequence block program, the Instance Wizard prompts the
user to select one of the configured choices, and includes the appropriate code item based on the
answer. For example, with the template created in Figure 7-13, if the user selects NW_07, the
code in item D7 is inserted into the sequence block program.

221
B0700FE – Rev A 7. Sequence Blocks

Replicate Decision Points

Figure 7-14 shows the replicate decision point Pause Count connected to a previous code item
(Counter). The decision point is inserted into the template so the user can specify that the
sequence block program loop back to the code item for a specified number of iterations. When
the iterations are complete, the program executes the code in Reset.

Figure 7-14. Example of a Replicate Decision Point

To set up a loop:
1. Insert the replicate decision point after the code item you want to repeat.
2. Connect the code item to the top corner of the decision point.
3. Connect another corner of the decision point to the top of the code item.
The Branch Choice dialog box prompts you to identify the purpose of the connection
as Loop or Continue.
4. Select Loop and click OK in the Branch Choice dialog box.
5. Insert another code item or a decision point after the replicate decision point.

222
7. Sequence Blocks B0700FE – Rev A

6. Connect the bottom corner of the decision point with the top of the new item.
The Branch Choice dialog box prompts you to identify the purpose of the connection
as Loop or Continue.
7. Select Continue and click OK in the Branch Choice dialog box.
Figure 7-15 shows the sequence for inserting a loop into an ST Template.

Figure 7-15. Connecting a Replicate Decision Point

When the template is inserted into the sequence block program, the Instance Wizard prompts the
user to specify the number of iterations, and inserts the loop with the appropriate number of
iterations.

Validating the Template

The Template Validation tool verifies that all required configurations are provided and that there
are no infinite loops within the graphic configuration. Output messages are written to the Output
window. The template must be validated to be available for insertion by the Instance Wizard.
To validate a template:
1. Choose Tools > Validate Template from the menu bar.
Output messages are written to the Output window. Successful validation of the
template is indicated by the message “Validation successful” in the Output window.
2. Correct any indicated ST Template errors using the Control Question and Decision
Point question dialog boxes as previously described.
Double-click on each error message to highlight the invalid object in the Editor
window.
You can now add the program code to be executed to the ST code items in your ST Template.
Programs typically consist of user-configured HLBL code and substitution questions.

223
B0700FE – Rev A 7. Sequence Blocks

Deleting an ST Template
NOTE
You cannot delete an ST Template once it has been instantiated in a sequence block.
You must delete the instances of a template before you delete the template itself.

To delete an existing ST Template:

1. Right-click the template in the Project Navigator and choose Delete from the pop-
up menu.
The Delete Request dialog box lists other IACC objects affected by the deletion.
2. Click OK.

NOTE
IACC deletes the item from the database. If the screen fails to update with the
change, then collapse and expand the control tree branch.

Locating an ST Code Item or Decision Point

If you are unsure where a specific ST code item or decision point is in an ST Template (if the tem-
plate is very large or the text is hard to read), you can use the Find dialog box to locate the item.
Proceed as follows:
1. Choose Edit > Find from the menu bar.
2. Type the name of the ST code item or decision point in the Object Name text box.
If you have validated the template recently, a pull-down list provides the names of all
the ST code items which have passed validation (that contain valid HLBL code).
3. Select one of the following as an object type for your search:
 Code Objects Check this box to search only for ST code items
 Decision Points Check this box to search only for ST decision points
 Code Objects and Check this box to search for both ST code items and
Decision Points decision points.

4. Click Find.
IACC attempts to locate the object whose name you specified in the Object Name
text box.
 If the object is found, the Find dialog box closes and the object is selected in the
Editor window.
 If the object is not found, the following message appears: “Object not found in
template.”
 Click OK to continue.
 If the following message appears: “You must enter a name to search for!”
 Type an object name into the Object Name text box.

224
7. Sequence Blocks B0700FE – Rev A

ST Code Items
An ST code item is essentially a placeholder in an ST Template for a short program consisting of
user-configured HLBL code and substitution questions. This program is written using the
ST Code Editor. To create an ST Code item, refer to “Creating ST Code Items” on page 214.

Opening the ST Code Editor for an ST Code Item

To edit an ST code item:
1. Right-click on the object in the ST Template Editor and choose ST Code Editor
from the pop-up menu.
2. Build the code by using any or the following techniques:
 Type in the code using the HLBL code syntax and functions described in High
Level Batch Language User’s Guide (B0400DF)
 Insert substitution questions
 Import code from an ASCII file.

Inserting Substitution Questions

You can insert a substitution question while entering code:
To insert an existing substitution question:
 Place the cursor at the location in the HLBL code where you want to insert a
question, choose Substitution List from the pop-up menu and select a question
listed in the submenu.
The name of the substitution question is inserted into the code at the location of the
cursor.

225
B0700FE – Rev A 7. Sequence Blocks

To create a new substitution question:

1. Place the cursor at the location in the HLBL code where you want to insert a question
and choose Substitution Question from the pop-up menu.
The Substitution Question Selection dialog box appears (Figure 7-16).

Figure 7-16. Substitution Question Selection

You can also use this dialog box to select and modify existing questions.
2. Click New Question to open the Substitution Properties dialog box (Figure 7-17).

Figure 7-17. Substitution Properties Dialog Box

226
7. Sequence Blocks B0700FE – Rev A

3. Enter the name of the substitution question in the Substitution Name text box.

NOTE
All substitution question and control question names must be unique.

4. Type the description of the new substitution question in the Question Text text box.
5. Type a more complete description of the new substitution question in the Help Info
text box, for the use of the operator.
6. Type the default answer for this substitution question in the Default Answer text box.
The number of characters in the answer cannot exceed the number specified in the
Max Length text box.
7. Type the maximum length of the answers for this substitution question in the Max
Length text box.
The Substitution Question Selection dialog box reappears.
8. Highlight the new question and click OK.
The name of the substitution question is inserted into the code at the location of the
cursor.
To add, modify, or delete a substitution question while entering code:
1. Place the cursor at the location in the HLBL code where you want to insert a code
instance.
2. Select View and click Substitution Question Manager.
The Substitution Question Manager dialog box appears (Figure 7-18). The dialog box
allows you to add, edit, or delete substitution questions not linked to any code items.
From the Substitution Question Manager dialog box, you can add a question, edit a
question, or delete a question.

Figure 7-18. Substitution Question Manager

227
B0700FE – Rev A 7. Sequence Blocks

3. To delete a question, highlight the question and click Delete Question.

4. To add a question, click New Question to open the Control Question Properties dia-
log box and complete the fields in the dialog box as described on page 216.
5. To edit a question:
a. Highlight the question and click Edit Question to open the Substitution Prop-
erties dialog box (Figure 7-19).

Figure 7-19. Substitution Properties Dialog Box

b. Modify the fields as appropriate and click OK.

The Substitution Question Manager dialog box (Figure 7-18) reappears.
6. To locate an existing question, highlight the existing question and click Where is
Question Used.
The names of decision points where the question is used is shown in the Where Used
tab in the Output window. You cannot delete a question if a decision point references
the question.

228
7. Sequence Blocks B0700FE – Rev A

Saving and Re-Using HLBL Code

You can save code to an ASCII file for re-use in other sequence blocks.
To save code for re-use.
1. Highlight the code in the ST Code Editor.
To highlight all the code, choose Edit > Select All from the menu bar.
2. Choose File > Save as ASCII from the menu bar to display a Save As dialog box.
3. Specify the filename and location in the dialog box and click Save.
To re-use the saved code:
1. Select the text object or block where you want to use the code and open the ST Code
Editor.
2. Place the cursor where you want to use the code and choose File > Insert ASCII
file from the menu bar.
An Open dialog box appears so you can browse and select the file.
3. Specify the filename and location and click Open.
The text is inserted into the code at the cursor location.
4. Compile and save the code.

Compiling the HLBL Code

When you have finished writing code, the code must be compiled before it can be downloaded.
The block must be recompiled every time you change its code.
The bulk compile function ignores any blocks that contain code created with the SFC Editor
because that code must be complied in the SFC Editor.
A bulk compile function is available from the Project Navigator to compile multiple blocks
automatically, instead of compiling individual blocks separately via the ST Code Editor.
To compile code for a single HLBL block:
1. Place the cursor anywhere in the ST Editor window and choose Tools > Syntax
Check and Compile from the menu bar.
Syntax errors are displayed in the Output window.
2. Debug the syntax and repeat the syntax check as necessary.
3. Choose Tools > Syntax Check and Compile from the menu bar.
4. When the code has been successfully compiled, choose File > Save from the menu
bar.
The Output window contains error messages with line numbers relating to the most recent edit.
To display and fix ST code compiler errors:
 Double-click each error in the Output window to display the incorrect line of code in
the Editor window.

229
B0700FE – Rev A 7. Sequence Blocks

Bulk HLBL Compiler

The Bulk HLBL Compiler utility compiles sequence blocks in a batch mode without the need to
open the ST Code Editor for every block. Designed primarily to compile groups of sequence
blocks assigned to a CSD or compound, this function allows you recompile large numbers of
blocks if they are invalid. Blocks are invalid if they have never been compiled or if they have been
modified since their last compilation.
If any block selected for compilation has code developed with the SFC Editor, a message in the
Output window informs you that the block was not compiled. Other blocks are not affected.
To use the Bulk HLBL Compiler:
1. Right-click on the CSD or compound that holds the blocks you want to compile, and
choose Compile from the pop-up menu.
The Bulk Compile dialog box asks you whether you want to compile all the sequence
blocks, or only the invalid sequence blocks (Figure 7-20).

Figure 7-20. Bulk Compile Dialog Box

The Number of Blocks group at the top of the dialog box provides statistics on the
sequence blocks in the CSD or compound: total blocks, invalid blocks, and valid
blocks.
A sequence block is considered valid after it has been successfully compiled. If a
sequence block contains invalid ST Templates, the sequence block is considered
invalid after it is compiled. The Bulk Compiler can fix some of the problems which
cause sequence blocks to become invalid, but relies mostly on you to correct any of the
errors it locates.

230
7. Sequence Blocks B0700FE – Rev A

2. Select one of the options in the Blocks to Compile group: All Blocks or Only
Invalid.
The Bulk Compiler attempts to compile all selected blocks. The compiler displays its
compilation status in the Output window, displaying the following information:
 Pass being performed
 Block being compiled
 Status of the block compilation
 Status of each pass
 Number of blocks being compiled
 Final summary of the bulk compile.
Any fatal errors which occur during bulk compilation must be fixed in the sequence
block code, via the ST Code Editor.
Connections to the sequence block must be configured and resolved in the CSD
Editor.
3. Edit any compilation errors in the sequence block code by double-clicking the error in
the Output window to highlight the ST code items or decision points in which the
errors are located in the ST Template Editor.
You can also right-click the errors and choose STCodeEd Editor from the pop-up
menu to open the code in the editor and fix the errors.

231
B0700FE – Rev A 7. Sequence Blocks

232
8. Ladder Logic
This chapter describes how to configure programmable logic blocks using the IACC Ladder
Editor.
The IACC Ladder Editor is used to create ladder programs for programmable logic blocks (PLBs).
The process involves:
 Creating a ladder object using the Project Navigator
 Invoking the Ladder Editor to assign logic elements to the ladder and make
connections
 Assigning the ladder to a PLB
 Validating and compiling the ladder program
 Downloading the ladder program by downloading the block, its compound, or
its CSD.
IACC Help contains a configuration example complete with instructions for creating specific
ladder diagrams.

Creating a Simple Ladder

To create a ladder:
1. Click the System tab in the Project Navigator if the tab is not already selected.
2. Expand System > Components > PLB Ladders.
3. Right-click PLB Ladders and choose New > Simple Ladder from the pop-up menu.
The ladder object appears in the branch under PLB Ladders with a default name such
as Simple Ladder1. A box appears around the name to indicate that the name is
editable.
4. Type in the new name for the ladder and click anywhere outside the rectangle.
You can change the name either by right-clicking on the object and choosing Rename
from the pop-up menu, or by using the Properties dialog box, also available from the
pop-up menu. The pop-up menu for the ladder object includes other functions for
managing the ladder object such as Delete, Editors, ListViews, and Assign to PLB.

233
B0700FE – Rev A 8. Ladder Logic

Editing a Ladder Program

Once the object has been created, you can build the ladder program using the Ladder Editor win-
dow:
1. Double-click the ladder object in the Project Navigator.
The Ladder Editor appears in the Editor window with a single rung (Figure 8-1). Two
power rails run vertically on either side of the window. The left power rail is visible in
Figure 8-1.

Ladder Object Left Palette Window

Ladder Editor
Selected in the Power Rail with Ladder Logic
opened in the
Project Navigator Palette Selected
Editor Window
Figure 8-1. Ladder Editor with Newly Created Ladder Object

The Ladder Editor is displayed in the Editor window in the center of the screen.
Format and Draw menus are added to the menu bar, and Pan-Zoom and Ladder
toolbars are added to the IACC toolbar. Refer to IACC Help for additional
information on these features.
2. Choose View > Palette if the Palette window is not already displayed.
3. Use the pull-down list at the top of the Palette window to select Ladder Logic
{Foxboro Palettes}.
This palette provides logic elements which you can drag into the ladder drawing. You
can also insert logic elements into the ladder by dragging objects from the Ladder
Logic Elements library in the Project Navigator.

234
8. Ladder Logic B0700FE – Rev A

Rungs and Rows

When you open the Ladder Editor for a new ladder, the window displays a single unconfigured
ladder rung (Figure 8-1). A ladder consists of up to 98 rungs, with up to 8 logic elements per
rung. The logic elements are configured by dragging them from a palette and placing them on
one of the 8 rectangles, or drop cells, in the rung. Figure 8-2 shows a single rung in Simple
Ladder1.
You can add another row of drop cells to a rung, but the new row counts as another rung for
purposes of the 98-rung limit.

Drop Cell Power Rail

Figure 8-2. Rung Elements

You can insert rungs in the ladder by using the context menu or using keyboard shortcuts. The
instructions in this document use the context menus. Refer to IACC Help for a table listing the
keyboard shortcuts.
To insert a rung:
 Right-click the location for the rung and choose Insert Rung from the pop-up
menu.
You can move the rung in the drawing by simply dragging it to the new location. When a rung is
moved, all its logic elements and connections are moved with it.
Additional rows can be added to a rung allowing larger logical circuits to be built.
To add rows to a rung:
 Right-click the rung you want to expand and choose Rung > Insert Row from the
pop-up menu.
Rows can be deleted from a rung set. Only the last row in a rung set can be deleted.
To delete a row from a rung:
 Right-click the rung you want to delete and choose Rung > Delete Row from the
pop-up menu.

235
B0700FE – Rev A 8. Ladder Logic

Rung Comments
A rung has both operator and engineer comments that appear below the rung. The operator com-
ment is visible in the I/A Series system. Engineering comments are not part of the downloadable
image passed to an FBM; they are only visible through the PLB Ladder Editor in IACC.
To add operator and engineering comments:
1. Right-click the drop cell where you want the comment to be placed and choose
Rung > Rung Comments to display the Ladder Rung Comments dialog box
(Figure 8-3).

Figure 8-3. Ladder Rung Comments Dialog Box

Both comments are user-defined. Operator comments can be used to pass

information to an operator of a system.
2. Enter the comments and click OK.

236
8. Ladder Logic B0700FE – Rev A

Logic Elements
Adding Elements
Logic elements can be added to the ladder by dragging them from the Ladder Logic {Foxboro
Palette}, or by using keyboard shortcuts. Logic elements can be moved among valid locations
within the ladder by dragging them to different locations. Use of the palette is described in this
section. Refer to IACC Help for a table of keyboard shortcuts.
To insert a logic element:
1. Select Ladder Logic {Foxboro Palette} in the Palette window.
The palette (right side of Figure 8-1) lists all the possible elements.
2. Select and drag a logic element to a rung.
 Contacts can only be placed in the first seven columns of a ladder rung.
Contacts cannot be placed in the eighth column.
 Coils, counters, relays, and timers can only be placed in the eighth column of a
ladder rung.
To delete a logic element:
 Right-click the element to be deleted and choose Delete from the pop-up menu.

Assigning Technical Identifiers

Once a logic element is inserted into a ladder, you can assign a technical identifier based on the
element type.
To identify a logic element:
1. Right-click on an element and choose Logic Element Parameters to display the
Logic Element Parameters dialog box (Figure 8-4).

Figure 8-4. Logic Element Parameters Dialog Box

237
B0700FE – Rev A 8. Ladder Logic

2. Select the technical identifier type from the TechId Type list.
3. Select a technical identifier from the TechId list.
4. Enter or modify labels for TechId in the Description1 and Description2 fields.
The Description1 and Description2 fields are optional descriptors and can con-
tain up to seven characters. The Preset and Reset fields are enabled when the logic
element is a counter or timer.
5. Enter Preset and Reset values as appropriate.
 If the logic element is a timer, the minimum and maximum values for Preset and
Reset values are 0 and 6553.4, respectively.
 If the logic element is a counter, the minimum and maximum values for the
Preset and Reset values are 0 and 65534, respectively.
6. Click OK.

Adding and Deleting Connections

Connections are made between drop cells of a rung and drop cells of adjacent lines in a rung.
Each drop cell has an invisible port on its left side. These ports can be linked together to create
connections. The vertical connections can only be made from the lines in a rung not among
rungs.
To create a connection:
1. Place the cursor over a port on a drop cell.
The cursor changes to a link symbol to show that a connection can start.
2. Drag the cursor to another port on another drop cell within the same rung.
As you drag it, the cursor loses color to show that a connection cannot be made.
When the cursor changes back to a normal link symbol, a link can be created.
3. Release the mouse button.

238
8. Ladder Logic B0700FE – Rev A

Figure 8-5. Connecting Elements

To delete a connection:
1. Select the connections to be deleted.
For multiple connections it may be easier to drag a selection box around all
connections.
2. Right-click the selected connections and choose Delete from the pop-up menu.

NOTE
Multiple connections can be created at one time. Dragging the cursor to a valid port
on a drop cell that is not adjacent to the starting drop cell causes connections to be
created through intermediate drop cells. When creating multiple connections, the
path of the connections runs horizontally until it is blocked or must go vertically to
meet the end point.

239
B0700FE – Rev A 8. Ladder Logic

Importing an I/A Series Ladder Configuration

You can import existing ladder programs from the I/A Series system to define new ladder pro-
grams in IACC. Unlike other IACC import functions, this import is invoked from within the
Editor window and not the menu bar because the Ladder Editor must be running at the time of
import.
To import an I/A Series ladder configuration:
1. Right-click anywhere in the Ladder Editor and choose Import I/A Ladder
Configuration from the pop-up menu.
An Open dialog box (Figure 8-6) is displayed with the file extension set to filter for
the configuration files (*.p).

Figure 8-6. Open Dialog Box for Importing a Ladder Configuration

2. Browse and select the file, and then click OK.

An information box asks whether the imported file should overwrite the existing
ladder or be appended to the ladder.
3. Make your selection and click OK.

240
8. Ladder Logic B0700FE – Rev A

Assigning a Ladder to a PLB

Assigning a ladder to a PLB makes the ladder logic program part of the block, and enables you to
connect the program to other blocks and to a field device. To download the program, you must
assign the ladder to a PLB. Only one ladder can be assigned to a PLB. The PLB, in turn, can be
connected to only one FBM.
To assign the ladder to a PLB:
1. Create the PLB instance if it does not already exist:
a. Click the Plant tab and expand the tree to display the target CSD.
b. Double-click the CSD to open the CSD Editor.
c. Use the pull-down list in the Palette window to select Logic {Foxboro Pal-
ette}.
d. Drag the PLB into the CSD.
Figure 8-7 shows a CSD with a PLB added.

Figure 8-7. New PLB in a CSD

e. Assign the block to a compound.

241
B0700FE – Rev A 8. Ladder Logic

2. Right-click the ladder object in the Project Navigator, and choose Assign to PLB
from the pop-up menu to display the Assign Ladder to PLB dialog box (Figure 8-8).

Figure 8-8. Assign Ladder to PLB Dialog Box

3. Select the PLB and click OK.

4. Connect the PLB to an appropriate ECB.
Refer to “Assigning ECBs to a CSD” on page 79.
To unassign the ladder:
 Right-click the ladder object and choose Unassign from PLB.

Implementation
Validating the Ladder
The validation procedure performs a series of syntax checks to verify the installability of the
configuration.
The ladder must meet these criteria:
 The number of ladder lines does not exceed 98.
 The number of ladder rungs does not exceed 98.
 There are no more than 390 elements.
 Each logic element has a technical identifier.
 The ladder is assigned to only one PLB.
 The ladder’s PLB is assigned to an ECB and only one ECB.

242
8. Ladder Logic B0700FE – Rev A

To validate a ladder:
1. Right-click on the object in the Project Navigator (or anywhere in the Ladder Editor)
and choose Validate from the pop-up menu.
You can select Validate if the ladder:
 Has never been validated
 Has been modified since its last validation
 Failed the last validation.
If any validation check fails:
 An error message is displayed in the Output window.
 The Ladder Editor highlights the problem area in red.
 A message box displays the error.

NOTE
You can use the IACC Options dialog box to configure how these three error report-
ing features are used to report problems of various degrees of severity. Choose
Tools > Options to open the dialog box and select the Error Reporting tab.

2. Click OK to close the information boxes, review the messages in the Output window,
and fix the identified problems.
3. Run the validation again.
When all validation checks pass:
 The ladder is marked valid.
 The Validate command is greyed out.
 The Compile command becomes active.
A successfully compiled ladder is required before the ladder can be downloaded to a digital FBM
for execution.

243
B0700FE – Rev A 8. Ladder Logic

Compiling the Ladder

Before compiling, a ladder must be assigned to a PLB and the PLB must be assigned to a
compound.
To compile a ladder:
1. Right-click anywhere in the Ladder Editor and choose Compile from the pop-up
menu.
The Ladder Compiler Output tab in the Output window (Figure 8-9) displays the
status and any errors found during the compilation procedure. The tab remains open
until IACC is closed.

Figure 8-9. Compile Tab in the Output Window

2. Double-click on any error to open the compiler and highlight the lines of code which
caused the error.

Downloading the Ladder

A download cannot be performed from within the Ladder Editor. To download the ladder pro-
gram, you must download the assigned PLB, as described in Chapter 11 “Downloading Control
Blocks”.

244
9. TagLists and Bulk Generation
This chapter describes how to use the TagList Editor to identify I/O points, import and export
tag lists, and generate CSDs from CSD Templates.
The IACC TagList Editor allows you to create and modify input/output (I/O) tags. It also allows
you to export and import I/O tags to and from external TagList files. One of the main purposes of
this editor is to create TagLists that provide data for the construction or update of CSDs. It also
acts as a record-keeping device that enables you to organize and view the network connections of
your process control strategy in one place.

F00107
Mix CSD1
FBM241
TAG - Mix1 - 0-10 V F00101
Inputs On/Off CSD1
FBM201
TAG - Inputs1 - 0-10 mA
F00102
Gas FBM201 CSD2
TAG - Gas1 - 0-10 mA
CP6001
F00103
Gas CSD2
FBM201
TAG - Gas2 - 0-10 mA CP

F00104
Steam CSD2
FBM201
TAG - Steam1 - 0-10 mA

F00105
Return CSD2
TANK1 FBM204
TAG - Return1 - 0-20 mA

F00106
Drain CSD2
FBM204
TAG - Drain1- 0-20 mA

Figure 9-1. Sample Process and Tags

An IACC TagList appears in a spreadsheet format (Figure 9-2). Each row in the TagList
represents a single tag. Each column of the TagList contains a parameter that defines the tags
(see Table 9-4 for a description of the column headings/parameters of the Foxboro IA Tag type).
The tag type determines the columns applicable to that row. The minimum data necessary to
define a tag within a tag list is the tag name and tag type. The TagList Editor provides for both
manual entry of individual tags, as well as the import of TagLists from a variety of sources.

245
B0700FE – Rev A 9. TagLists and Bulk Generation

Figure 9-2. Example IACC TagList

A tag type, or a tag definition, is a predefined or user-defined category of tags that can be used in
a TagList. IACC is delivered with one predefined tag type, the Foxboro IA Tag. New tag types
may be derived from the Foxboro IA Tag definition. You can then add and modify parameters in
the derived tag type definition, as well as create new tag types from the derived definition. You
cannot delete or alter the Foxboro IA Tag.
Only one instance of the TagList Editor can be open for a particular TagList at a time. All the tags
for a process or system can be contained in one TagList instance; however, multiple instances can
be used as an organizational tool. For example, you may want to maintain a TagList for each
major area of your plant.

246
9. TagLists and Bulk Generation B0700FE – Rev A

Custom Tag Types

You can create user-defined tag types using a pop-up menu from a tag type object in the Project
Navigator. You can then open the newly created type using the Definition Editor to modify the
type as follows:
 Add and delete parameters
 Change parameter attributes
 Select parameters to be displayed as column headings in the TagList Editor
 Specify which parameters appear when configuring tag data propagation.

Bulk Generation
You use a TagList and CSD Templates to create multiple CSDs. This Bulk Generation feature is
invoked from the TagList Editor and generates ECBs in the CSD using TagList data. See “Bulk
Generation of CSDs” on page 272 for details.
In addition to identifying I/O points in a CSD, the TagList can be used to set parameters in other
blocks in CSDs created or updated during bulk generation. You can specify tag propagation steps
for any user-defined tag type. For example, you can map a description field in the TagList to the
DESCRP parameter of the I/O blocks in the CSD. See “Block Parameter Propagation” on
page 276 for additional information.
This chapter describes the various procedures you can use to operate the TagList Editor.
 Creating a TagList
 Adding tags using the TagList Editor
 Exporting TagLists
 Importing tags into an existing TagList
 Using TagList to bulk generate and update CSDs.

TagLists
Creating a TagList
To create a TagList:
1. Expand System > Components in the Project Navigator.
2. Right-click TagLists and choose New TagList from the pop-up menu.
The new TagList appears with a default name such as Tag List1 under the TagLists
branch. A rectangle appears around the name indicating that it is editable.
3. Enter a new name and click anywhere outside the rectangle.
You can also change the name by choosing Rename from the object’s pop-up menu or
using the Properties dialog box.

247
B0700FE – Rev A 9. TagLists and Bulk Generation

Deleting a TagList
To delete a TagList:
1. Right-click the TagList instance and choose Delete from the pop-up menu.
The Delete Request dialog box shows the other IACC objects affected by the delete so
you can review the action before confirming it.
2. Click OK.

Editing a TagList
To open the TagList Editor:
 Double-click the instance in the Project Navigator to open the TagList Editor
window.
Figure 9-3 shows the TagList Editor open for IDSTagList selected in the Project
Navigator. The tag data is displayed in a spreadsheet with each row representing a
different tag and each column a tag parameter. The tag parameters are defined in the
TagList type under System > Library > TagList Types.

Figure 9-3. IACC TagList Editor Window

The TagList Editor has a page for all tags in the list and a page for each tag type. For example, tags
in the Orion Taglist in Figure 9-3 use either the Foxboro IA Tag or the Orion tag type. The jump
buttons to the left of the tabs are active when there are tabs that are not currently visible, but can
be brought into view.

248
9. TagLists and Bulk Generation B0700FE – Rev A

Colors and Symbols Appearing in TagList Editor

Table 9-1 describe the colors and symbols that may appear in the TagList Editor.

Table 9-1. Colors and Symbols in TagList Editor

Color or Symbol Description

Blue Text Blue text is the default or original entry for that cell.
Green Text Green text indicates that the entry in the cell has been overridden. The text
may only turn green once the updated TagList has been saved.
Yellow A yellow background in a cell indicates that the cell is invalid. A common
Background example of this is a yellow background appearing in a Name cell, indicating
that at least one other tag with this name exists in IACC.
Beige or Grey Black text on a beige or grey background indicates that the cell cannot be
Background with edited, as the cell is read-only. For example, you cannot edit the Type
Black Text parameter.
The pencil symbol appearing at the far left of a tag row indicates that the tag
has been modified during the current editing session, and that the changes
have not yet been saved to the database.

Menus and Toolbars

When you open the TagList Editor, a set of commands specific to the editor are added to various
menus in the menu bar and the TagList Editor toolbar (Figure 9-4) appears next to the standard
IACC toolbar.

Remove Tags Bulk Generate

CSDs

Find

Add New Tag Tag Data

Propagation
Figure 9-4. TagList Editor Toolbar

249
B0700FE – Rev A 9. TagLists and Bulk Generation

Table 9-2 lists the commands added to the File, Edit, and Format menus, and shows the related
toolbar icons.

Table 9-2. Menu Commands Added for the TagList Editor

Command Icon Description

File Menu
Bulk Generate CSDs Invokes a series of dialog boxes for bulk generating CSDs
from the current TagList (see “Bulk Generation of CSDs”
on page 272).
Tag Data Propagation Invokes a series of dialog boxes for configuring propaga-
tion preferences for parameters of user-defined tags
(see “Block Parameter Propagation” on page 276).
Edit Menu
Fill Down Transfers a value from a cell to a group of selected cells.
Find Invokes a search utility to locate a specific text string in a
column.
Add New Tag Opens a dialog box for specifying the number of tags to be
added to the TagList.
Remove Tag(s) Removes the selected tags from the active TagList. Does
not delete the tag everywhere else it occurs.
Revert to Default Returns a cell entry to the value it held upon initiation of
the active editing session.
Format
Column > Hide Hides the selected TagList columns.
Column > Unhide Displays any hidden columns between the selected
columns in the displayed spreadsheet.
Column > Lock Locks all the columns to the left of the selected columns
on the displayed spreadsheet.
Column > Unlock Unlocks all the columns to the right of the selected locked
columns on the displayed spreadsheet.

250
9. TagLists and Bulk Generation B0700FE – Rev A

TagList Editor Pop-Up Menus

Pop-up menus are available from various contexts in the TagList Editor window (Figure 9-5) to
give you quick access to editing commands. Many of the picks on the pop-up menus are the same
as the TagList Editor menu choices described in Table 9-2.

Background Column
Space Context Context
Row Context

Cell
Context
Background
Space Context

Figure 9-5. Taglist Editor Pop-Up Menu Contexts

Table 9-3 lists the commands in these context menus and shows related toolbar icons.

Table 9-3. TagList Editor Cell Pop-Up Menu Commands

Command Icon Description

Cell Context
Revert to Default Returns a cell entry to the value it held upon initiation of the
current editing session.
Cut Removes the text selected in the cell and stores it on the
clipboard.
Copy Copies the text selected in the cell to the clipboard.

Paste Pastes a copy from the clipboard to the cell selected in the
Editor window, replacing the data in the selected cells.
Fill Down Transfers a value from a cell to a group of highlighted cells.
Column Context
Revert to Default Returns all entries in the column to the values they held upon
initiation of the current editing session.
Copy If available, makes a copy of the text selected in the column
and stores it on the clipboard.
Paste Not available in this menu for this release.

251
B0700FE – Rev A 9. TagLists and Bulk Generation

Table 9-3. TagList Editor Cell Pop-Up Menu Commands (Continued)

Command Icon Description

Row Context
Revert to Default Returns all entries in the row to the values they held upon
initiation of the current editing session.
Copy Copies the entire tag to the clipboard.

Paste Pastes a copy of the entire tag from the clipboard to the tag row
selected in the Editor window.
Delete Deletes the row selected.
Where Used Not available.
Background Space Context
Revert to Default Returns all TagList entries to the values they held upon
initiation of the current editing session.
Cut Removes the selected text from the cell and stores it on the
clipboard.
Copy Copies the selected object to the clipboard.

Paste Pastes a copy of the text from the clipboard to the selected cell
in the Editor window.

Tags
Creating a New Tag
To add tags to the currently open TagList:
1. Choose Edit > Add New Tag from the menu bar to display the Insert New Tag dia-
log box (Figure 9-6).

Figure 9-6. Insert New Tag Dialog Box

2. Use the Tag Type pull-down list to select a tag type.

The default type is Foxboro IA Tag.
3. Enter the number of tags you want to create in Number of Tags or use the spinner
buttons to increase or decrease the displayed value.
4. Click OK.

252
9. TagLists and Bulk Generation B0700FE – Rev A

The new tags of the type you specified appear in the TagList with default names such
Foxboro IA Tag-1 and Foxboro IA Tag-2.

Deleting a Tag
To delete a tag from the current TagList:
1. Select the tag by clicking the grey button at the far left of the tag row.
2. Click the Remove Tags icon ( ) in the toolbar.

Editing a Tag
Many of the values of the parameters that define a tag may be edited. Most of the parameter val-
ues can be edited selecting an entry from a pull-down list of possibilities. Table 9-4 describes each
parameter in the default Foxboro IA Tag type and indicates how the parameter can be edited. The
following sections provide more information for defining your tags by means of editing the
parameter values.

Table 9-4. Parameters of the Foxboro IA Tag Type

Parameter Description
Name Identifies the name of the tag instance. A default name is assigned to each tag
upon its creation.
Type The tag type or definition of the tag instance. The type is chosen when the
tag is first added to the TagList and cannot be changed.
Description Can be changed directly in the cell using the keyboard to reflect any
descriptive information as needed.
HighScale The upper limit of the signal range. Enter this limit into the cell by either
typing it in or by choosing it from the pull-down list.
LowScale The lower limit of the signal range. Enter this limit into the cell by either
typing it in or by choosing it from the pull-down list.
Units Engineering Units associated with this signal. Enter the units description into
the cell by either typing it in or by choosing it from the pull-down list.
CP The CP associated with the FBM of the tag. Choose the CP from the
pull-down list of CPs already configured in IACC. If the CP has not been
added yet, enter the letterbug directly.
FBM The Fieldbus Module (or connected field device) associated with the signal.
The value in this field is copied to the IOM_ID parameter (or equivalent) in
I/O type block. Choose the FBM from the pull-down list of modules already
configured in IACC. If the module has not been added, type in the FBM
name (see “Specifying the FBM Name, Point, Channel Group Index, and
Device Address of a Tag” on page 255).
FBM Point The FBM point to be associated with the tag. You can enter the FBM point
into the cell by either typing it in or by choosing it from the pull-down list
(see “Specifying the FBM Name, Point, Channel Group Index, and Device
Address of a Tag” on page 255).

253
B0700FE – Rev A 9. TagLists and Bulk Generation

Table 9-4. Parameters of the Foxboro IA Tag Type (Continued)

Parameter Description
Compound The compound where the block or CSD Template component associated
with the tag resides. You may use the combo box to enter the compound
name into the cell by either typing it in or by choosing it from the pull-down
list of available compounds.
Plant Area The name of the Plant Area to which CSDs are assigned during Bulk
Generation. You can assign a Plant Area by making a selection from the
combo box, or you can type in a Plant Area name. If the Plant Area specified
does not already exist in the database, Bulk Generation creates the object. If
the Plant Area field is blank, the CSD is assigned to the Unassigned CSDs
folder in the Plant tab.
CSD Name The name of the CSD where the tag is to be used when a bulk generation is
performed. Enter the name directly or select it from the pull-down list of
already created CSDs.
CST Name The name of the CSD Template to be used with the tag to bulk generate the
associated CSD. Enter the name directly or select it from the pull-down list
of already created CSD Templates (see “Specifying the CST Name and
Component of a Tag” on page 256).
CST Component The component that maps the tag to the block component in the associated
CSD Template when a bulk generation is performed. Enter the component
directly or select it from the pull-down list (see “Specifying the CST Name
and Component of a Tag” on page 256).
Channel Group The channel group index for MAIN, MCIN, and MCOUT blocks. Select it
Index from the pull-down list (see “Specifying the FBM Name, Point, Channel
Group Index, and Device Address of a Tag” on page 255).
Device Address This field supplies an address string that is used instead of FBM Point and
(Data Address) Channel Group Index to specify the connection in the I/O block, as
described in “Specifying the FBM Name, Point, Channel Group Index, and
Device Address of a Tag” on page 255.

Specifying Parameters Using Combo Boxes

Most of the values of the predefined Foxboro IA tag parameters are defined or edited through the
use of a combo box such as the one in Figure 9-7, which lists the ECBs for configured FBMs and
their parent compounds. You can either enter the data directly or select an item from the pull-
down list. Depending upon what stage you are at in defining your tags and your process using
IACC, a parameter may or may not have a pull-down list of possible choices available.

Figure 9-7. FBM Combo Box

254
9. TagLists and Bulk Generation B0700FE – Rev A

Specifying the FBM Name, Point, Channel Group Index, and Device Address of a Tag
The FBM and FBM Point parameters may be specified either before or after the actual piece of
hardware is defined in IACC, although it is recommended that you define your hardware first.
The FBM combo box contains a pull-down list of all the FBM instances that have been defined in
IACC thus far.

NOTE
Specifying the name of an FBM here does not automatically propagate the defini-
tion of this FBM elsewhere in IACC. You must manually create your hardware,
either before or after filling out your TagList. Hardware must be created prior to
performing bulk generation.

You may specify the point on the FBM associated with the signal defined by a particular tag by
choosing from the FBM Point pull-down list or by directly typing it into the box. IACC does not
let you assign the same FBM point to more than one tag, and thus only displays points that have
not been used.
For MAIN, MCOUT, and MCIN blocks you do not specify the FBM point, but rather designate
the Channel Group Index by choosing from that column’s pull-down list or by directly typing it
into the box.
For FBMs used to interface with FOUNDATION fieldbus H1, HART™, PROFIBUS™, and
Modbus® devices, enter the name of the child ECB (ECB201) that represents the connected field
device, and then enter any additional required addressing information in the Device Address
(Data Address) field.
Table 9-5 shows the Device Address field usage for connecting DCI and DCI Function blocks in
FOUNDATION fieldbus H1 applications.

Table 9-5. Device Address Field Usage for H1 Device Block Connections

FBM DCI Block Device Address/Data Address

FBM220/221 BIN/BINR, BOUT, Enter the tag of the function block in the connected
RIN/RINR, ROUT device to establish a publisher/subscriber connection
to the block’s primary variable.
FBM228 AI, AO, DI, DO Enter the CHANNEL to be used by the device func-
tion block. (The function block is specified by the
Name parameter of the DCI Function block.)
BIN/BINR, IIN, Enter the tag of the device block and the index.sub-
PAKIN, RIN/RINR, index of a specific parameter to specify a client/server
STRIN connection to the parameter. Use the following
syntax:
<device block tag>.<index>[.<subindex>]
RIN, ROUT Enter the tag of the function block in the connected
(legacy usage) device to establish a publisher/subscriber connection
to the block’s primary variable.

For details on configuring connections to H1 devices, see:

255
B0700FE – Rev A 9. TagLists and Bulk Generation

 FOUNDATION fieldbus H1 Communication Interface Modules (FBM220/FBM221)

User’s Guide (B0400FD)
 Implementing FOUNDATION fieldbus on the I/A Series System (B0700BA).

Specifying the CST Name and Component of a Tag

If you plan to perform a bulk generation using your TagList, you must specify the following
parameters of the relevant tags:
 CSD Name Names the resulting CSD.
 CST Name Identifies the CSD Template to be used.
 CST Component Maps the tag to an I/O block in CSD Template.

Creating a Custom Tag Type

IACC includes at least one tag type, Foxboro IA Tag. Using this tag type assures you
compatibility with the IACC application and with your I/A Series system. You can create new tag
types to track a variety of I/O items and to add tag propagation steps for use in bulk generation of
CSDs.
To create a custom tag type:
1. Expand System > Library > Tag Types in the Project Navigator to display the
existing tag types.
2. Right-click on Foxboro IA Tag (or another tag type in the directory) and choose
New Definition from the pop-up menu.
IACC creates a new tag type below the selected type with a default name such as
Foxboro_IA_Tag1. The new type inherits its definition from its parent object. The
object is surrounded by a rectangle indicating that the name can be changed.
3. Type the new name and click anywhere outside the rectangle.
To modify a custom tag type definition:
1. Right-click on the tag type and choose Editors > Definition Editor from the
pop-up menu.
IACC displays a multi-tab spreadsheet showing the definition of each tag type
parameter. You can edit any field of a parameter definition that has a white
background.
2. Use the tabs at the bottom of the Editor window to select among the various
parameter groups.
3. Use the Edit menu in the menu bar or the toolbar icons to add, remove, or modify
parameters.
Figure 9-8 shows editing of Param1, a parameter just added to the definition of a
custom TagList named Orion.

256
9. TagLists and Bulk Generation B0700FE – Rev A

Definition Editor Toolbar

for a Tag Type

Custom Tag New Editable

Type Definition Parameter Parameter Attributes
Figure 9-8. Editing a New Parameter in a Custom Tag Type Definition

257
B0700FE – Rev A 9. TagLists and Bulk Generation

Importing TagLists
To import a TagList to an IACC TagList from an external database or text formatted file:
1. Set up the IACC TagList instance as described in “TagLists” on page 247.
2. Place the cursor in the Project Navigator and choose File > Import from the menu
bar to open the Available Formats dialog box (Figure 9-9).

Figure 9-9. Available Formats Dialog Box for TagList Export

3. Select Import Taglist Agent and click Next.

The Import Taglist - Information dialog box appears (Figure 9-10).
4. Click the DBF or Text option button to identify the import file format.
5. If you chose Text, specify the delimiting character of the text file:
a. Click Edit to open the Edit Delimiting Character dialog box.
b. Select the Tab option button, or click the Text File Delimiting Character
button and type the appropriate character into the associated box.
c. Click OK.
6. If you are importing a text file, specify whether the first row of the file contains
column names or data.
7. Click the Select Taglist File Browse button and select the file from the Import From
dialog box.
8. Specify how the tags are to be defined by selecting one of the following options:
 If there is a column in the external TagList which indicates the type of each tag,
click the Get Tag Type from Column button, and choose the appropriate col-
umn name from the pull-down list.
 If you wish to import the tags as all the same type of tag, click the Import All
Tags as IACC Type option, and choose the tag type from the pull-down list.
9. Use the pull-down list in the Select IACC TagList box to specify the target IACC
TagList and click the Next.

258
9. TagLists and Bulk Generation B0700FE – Rev A

Figure 9-10. Import Taglist - Information Dialog Box

259
B0700FE – Rev A 9. TagLists and Bulk Generation

Defining Tags
If you chose Import All Tags as the IACC Type in Step 8 on page 258, the Import Taglist - Field
Mapping dialog box appears. Skip to “Mapping Fields” on page 262.
If you chose Get Tag Type from Column in Step 8 on page 258, the Import Taglist - Tag Type
Mapping dialog box (Figure 9-11) appears.
1. Indicate the IACC tag type to correspond to each of your external file tag types using
the Tag Types in TYPE column and IACC Tag Definitions boxes.
Each tag type in your external file is listed in the Tag Types in TYPE column box.
Each of the available IACC tag types is listed in the IACC Tag Definitions box.
a. For each external tag type, click its listing in the Tag Types in TYPE column box
and then click the tag type you wish to map it to in the IACC Tag Definitions
box. Both of the members of the selected pair are now highlighted.
b. Click the Add button.
A check appears in the box to the left of the external tag type selection. A text line
appears in the Mappings box which shows the tag type to be mapped followed by
the name of the corresponding tag type in the new file.
2. If you make a mistake choosing a type-to-type mapping pair:
a. Click the pair members so that they are both highlighted.
b. Click the Sub button.
The two entries are no longer linked as a pair.
3. Repeat these steps for each tag type in the file to be imported.
The complete list of type-to-type mappings appears in the Mappings box.
4. Click Next to display a dialog box for mapping the fields.
In addition to displaying the current pairings, the Mappings group enables you to:
 Save the current setup for use with other imports by opening the Save Mapping dialog
box and clicking Save Current Tag Type Mapping (Figure 9-11).
 Apply the previously saved pairings using the pull-down list in Select Mapping to Use.
 Delete saved mappings by opening the Delete Mappings dialog box and clicking
Edit Mappings.

260
9. TagLists and Bulk Generation B0700FE – Rev A

Figure 9-11. Import Taglist - Tag Type Mapping Dialog Box

261
B0700FE – Rev A 9. TagLists and Bulk Generation

Mapping Fields
The next step is to map the fields in the imported TagList to the appropriate fields in the IACC
TagList. IACC displays a dialog box with field mapping tools (Figure 9-12).

Figure 9-12. Import Taglist - Field Mapping Dialog Box

262
9. TagLists and Bulk Generation B0700FE – Rev A

To map the fields:

1. Select the TagList columns you wish to import using the External Taglist Column
Names and Tag Type Columns boxes.
Each parameter column in your external TagList is listed in the External Taglist
Column Names box. Each of those parameters has a corresponding potential column
in the new IACC TagList listed in the Tag Type Columns box. If you previously
indicated the external column that contains the type of each tag, this column does not
appear at this stage.
a. For each column you wish to import, click its listing in the External Taglist
Column Names box and then its corresponding entry in the Tag Type Columns
box.
Both members of your selected pair are now highlighted.
b. Click Add.
A check appears in the box to the left of each of your pair members. A text line
appears in the Mappings box which shows the parameter column to be mapped
followed by the name of the corresponding column in the new file.
2. Check for errors, and if you make a mistake choosing a pair:
a. Click the pair members so that both become highlighted.
b. Click the Sub button.
The two entries are no longer linked as a pair.
3. Repeat these steps for each parameter you wish to map to the new file.
The complete list of column-to-column mappings appears in the Mappings box.
4. Click Next to display the Import Taglist - Select Tags dialog box.
In addition to displaying the current pairings, the Mappings group enables you to:
 Save the current setup for use with other imports by opening the Save Mapping dialog
box and clicking Save Current Tag Type Mapping (Figure 9-11).
 Apply the previously saved pairings using the pull-down list in Select Mapping to Use.
 Delete saved mappings by opening the Delete Mappings dialog box and clicking
Edit Mappings.

263
B0700FE – Rev A 9. TagLists and Bulk Generation

Selecting Tags
The final specification is to select tags from the external file using the Import Taglist - Select Tags
dialog box (Figure 9-13).

Figure 9-13. Import Taglist - Select Tags Dialog Box

264
9. TagLists and Bulk Generation B0700FE – Rev A

To complete the import:

1. Select the tags you wish to import.
The New Tags group box displays all the names of the tags as they appear in the IACC
TagList once the import is performed. The A/M column indicates whether the item is
to be added or merged with an existing item. A check mark appears in the box to the
left of each tag entry you have chosen.
When you highlight a tag entry in the New Tags group box that is to be merged into
the IACC TagList, the New Tag Values group box displays the differences that exist
between the parameters of that tag in the current IACC TagList and in the TagList
once the import is performed. The New Tag Values box displays only those parame-
ters for which differences exist.
 To view all the parameters of the tag, regardless of whether differences exist for
that parameter, check the box to the left of Show All.
2. Use the check box in the lower left to remove all tags from the target TagList before
importing the tags.
3. Click Next.
The Verify dialog box displays information about the import (Figure 9-14).

Figure 9-14. Verify Dialog Box for TagList Agent Import

4. Verify that the information is correct and then click Start.

5. Click Finish when the Import dialog box indicates that the import is complete or
has been stopped because of errors.
6. Review the import-related tab messages in the Output window (Figure 9-15).

265
B0700FE – Rev A 9. TagLists and Bulk Generation

7. Display the imported objects by double-clicking the target TagList in the Project
Navigator.
Figure 9-15 show three tags imported from the file Orion.txt. Any tags that were in
the Orion TagList prior to the import were deleted when the Delete Existing Tags
option was checked (Figure 9-13).

Figure 9-15. Imported Tags and Output Window with Import-Related Tabs

266
9. TagLists and Bulk Generation B0700FE – Rev A

Exporting TagLists
There are two options for exporting a TagList:
 Export to IACC Format so that the TagList can be used in another IACC applica-
tion or re-used later in the same application.
 Export Taglist Agent to save the data in another file format for use in a spread-
sheet or similar application. The formats available are comma-separated values (.csv)
and other text files, and the database format (.dbf ) used by FoxCAE and other soft-
ware engineering applications.
To export an IACC TagList to a new external text or database-formatted file:
1. Select the TagList in the Project Navigator and choose File > Export from the
menu bar.
The Available Formats dialog box appears (Figure 9-16).

Figure 9-16. Available Formats Dialog Box for TagList Export

267
B0700FE – Rev A 9. TagLists and Bulk Generation

2. Select Export Taglist Agent and click Next to open the Export Taglist Informa-
tion dialog box (Figure 9-17).

Figure 9-17. Export Taglist Information Dialog Box

The External Taglist Information Group specifies the destination file.

268
9. TagLists and Bulk Generation B0700FE – Rev A

3. Select DBF or Text for the file type.

For Text type, define the delimiting character:
a. Click Edit to open the Delimiting Character dialog box.
b. Select Tab, or select Text File Delimiting Character and type the appro-
priate character into the associated box.
Do not use a character that is used in one of the data fields.
c. Click OK.
4. Click Browse next to the External Taglist File Name box and use the Export To dialog
box to specify name and path for the file.
The filename should have the appropriate .dbf, .txt, or .csv extension.

! CAUTION
Exporting an IACC TagList to an existing file overwrites the destination file.

5. Use the pull-down lists in the IACC TagList Information group to select the TagList
and types of tags to be exported.
6. Click Next.
The Taglist Export - Field Mapping dialog box appears (Figure 9-18).
7. For each TagList column you wish to export, map the column to a column in the
destination file:
a. Click the attribute in Tag Type Columns and select a corresponding attribute in
the External Taglist Columns list.
b. Click Add.
To use a previously saved mapping, pull down the list in the Select Mapping to Use
box (Figure 9-18) and select a name. The name of the chosen mapping appears in the
Select Mapping to Use box and the column-to-column mapping pairs appear in the
Mappings box.

269
B0700FE – Rev A 9. TagLists and Bulk Generation

8. To save a mapping for future exports:

a. Click Save Mapping to open the Save Mapping dialog box (Figure 9-18).
b. Enter a name for this mapping in the Mapping Name field and click OK.
The Save Mapping dialog box disappears and the name of your newly saved
mapping appears in the Select Mapping to Use box.

Figure 9-18. Taglist Export - Field Mapping Dialog Box

270
9. TagLists and Bulk Generation B0700FE – Rev A

9. To delete a saved mapping:

a. Click Edit Mappings to open the Delete Mappings dialog box (Figure 9-19).

Figure 9-19. Delete Mappings Dialog Box

b. Select the Mappings name using the pull-down list at the top of the dialog box,
click Delete Mappings, and click OK.
10. Click Next to display the Verify dialog box (Figure 9-20).

Figure 9-20. Verify Dialog Box for a TagList Agent Export

11. Verify that the information is correct and click Start.

12. Click Finish when the Export dialog box indicates that the export is complete or the
process was stopped because of an error.

271
B0700FE – Rev A 9. TagLists and Bulk Generation

Bulk Generation of CSDs

Bulk Generation creates CSDs and updates existing CSDs using CSD Templates and
information in the TagList. Bulk Generation is invoked when the TagList is opened in the TagList
Editor. The tags are mapped to I/O blocks and other components in the CSD Template.
Following are some Bulk Generation rules:
 You can generate multiple CSDs from the same template.
 The name of the new CSD is derived from the CSD Name field. If the name of an
existing CSD is used, the bulk generation overwrites the CSD. Thus, bulk generation
can be used to update signal information in CSDs you have already built.
 The CSD Template is identified in the CST name field.
 Every I/O block in the CSD Template must be mapped to a tag by having its name in
the tag’s CST Component field, the name of the CSD Template in the CST Name
field, and the name of the resulting CSD in the CSD Name field.
Figure 9-21 shows six tags in the IDSTaglist used to generate two CSDs from the CSD CAS Loop
Template. The template has three I/O blocks, two analog inputs and one analog output. These
blocks are identified in the CST Component column. For a CSD to be generated, a tag must be
mapped to each of the CSD Template components, that is, there must be a signal for each I/O
block.
The tags shown in Figure 9-21 result in two CSD - CSD Template pairings:
 CAS LOOP with CSD CAS LOOP
 CAS LOOP_1 with CSD CAS LOOP.
In this example, the two CSD instances are mapped to two different Plant Areas:
 Tank Farm does not yet exist in the database, so it is created at the top level of the
Plant tab by Bulk Generation.
 IDS Samples is already part of the database.
Bulk generation assigns the existing compound, CAS_LOOP, to the Tank Farm Plant Area.

272
9. TagLists and Bulk Generation B0700FE – Rev A

Figure 9-21. Fields Used in Bulk Generation

To bulk generate CSDs from a TagList:

1. Open the TagList in the TagList Editor and make sure the fields used in bulk
generation specify the correct CSDs, CSD Templates, and CSD Template
Components.
2. Choose File > Save from the menu bar.
You cannot invoke bulk generation with a TagList that has unsaved changes.

273
B0700FE – Rev A 9. TagLists and Bulk Generation

3. Choose File > Bulk Generate CSDs from the menu bar to open the Select CSDs
dialog box (Figure 9-22).

Figure 9-22. Select CSDs Dialog Box

The dialog box lists every CSD - CSD Template pairing in the TagList. The two
selected pairings in Figure 9-22 result from the tags shown in Figure 9-21.
You can generate all or some of the CSDs designated in your TagList at one time.
4. Click the CSD or CST column head to sort the list on that column.
5. Click the check box of each CSD you want to generate, or click Select All to select
all CSD - CSD Template pairs.

274
9. TagLists and Bulk Generation B0700FE – Rev A

6. Click Next.
The Bulk Generate Preview dialog box appears (Figure 9-23). Information on the
generation appears in this dialog box. If the generation cannot be completed, error
messages appear in this dialog box.

Figure 9-23. Bulk Generation Preview Dialog Box

The dialog box identifies any CSDs which do not have all their I/O blocks mapped to
a tag. If you are regenerating CSDs, the CSDs and the compound assignments are
overwritten by the information in the template and the TagList.

275
B0700FE – Rev A 9. TagLists and Bulk Generation

7. Click Finish.
Bulk generation runs, and when complete, the dialog box disappears. The newly
created CSDs appear in the Project Navigator. Figure 9-24 shows the newly created
CAS_LOOP_1 opened in the CSD Editor and the two Plant Areas expanded in the
Project Navigator. The updated CAS_LOOP CSD is displayed under IDS Samples
and the CAS_LOOP compound is expanded under Tank Farm.
8. Check the Output window for messages resulting from the bulk generation process
(Figure 9-24).

Figure 9-24. CSD Created with Bulk Generation

Block Parameter Propagation

You can add tag propagation steps to user-defined tag types for automatic configuration of
additional block parameters during bulk generation.
To configure tag data propagation:
1. Double-click the TagList in the Project Navigator if TagList is not already open in the
TagList Editor.
2. Choose File > Tag Data Propagation from the menu bar to display the Tag
Definition Selection dialog box (Figure 9-25).

276
9. TagLists and Bulk Generation B0700FE – Rev A

Figure 9-25. Tag Definition Selection Dialog Box

3. Choose the user-defined tag type from the Tag Type pull-down list for which you wish
to configure propagation and click OK.
The Tag to Block Data Propagation dialog box appears (Figure 9-26).

Figure 9-26. Tag to Block Data Propagation Dialog Box

4. Select an entry in the Tag Parameters field and a block in the I/O Block Types
field.
Both selections become highlighted in blue, and the parameters for the chosen block
appear in the Common Block Parameters field.
5. Select the target parameter in the Common Block Parameters field, and click Add.

277
B0700FE – Rev A 9. TagLists and Bulk Generation

The tag parameter - block.parameter pair appears in the Tag to I/O Block Data
Propagations field.
6. Repeat the procedure for any additional pairs you wish to configure.
7. To set up propagation to non I/O blocks, uncheck I/O Blocks Only below the
Block Types list.
Figure 9-26 shows the mapping of tag field to the BLK_DESCR parameter in
CALCA_IA, a custom block derived from the standard I/A Series CALCA block. The
value propagated can be used by formulas in other CALCA_IA parameters to name
and describe the block. The BLK_DESCR is only used within IACC and is not
downloaded to the CP.
Refer to Intelligent Design Studio (IDS) Library for IACC (B0400BQ) for additional
information on tag-to-block propagation and examples of naming formulas.
8. To remove a propagation step, select the mapping in the Tag to I/O Block Data
Propagations list box, and click Remove.
9. Click OK to conclude configuration.

Showing Parameters for Tag Propagation

Only selected TagList parameters are displayed in the Tag to Block Data Propagation dialog box
(Figure 9-26), as specified in the tag type definition. The parameters must be included in the
Data Propagate Group to be shown in the dialog box. You can view the group for any tag type
using the Definition Editor, but you can only modify custom tag types.
To make a TagList parameter available for tag to block propagation:
1. Expand System > Library > Tag Types in the Project Navigator to display existing
tag types.
2. Right-click on the custom tag type and choose Editors > Definition Editor
from the pop-up menu.
3. Click the Data Propagate tab to display the Data Propagate group.
4. Choose Edit > Add/Remove Parameter(s) to Group from the pop-up menu.
A dialog box displays all the tag type parameters with the group members highlighted
by a blue background (Figure 9-27).
5. Click individual parameters to add them or remove them.
The parameters to be included are highlighted with a blue background.

278
9. TagLists and Bulk Generation B0700FE – Rev A

Figure 9-27. Adding Parameters to the Data Propagate Group

6. Click OK.

279
B0700FE – Rev A 9. TagLists and Bulk Generation

280
10. Creating Displays
This chapter describes how to create and apply displays using the integrated FoxDraw
application.
The FoxDraw application is a graphical editor for building displays to view process control
dynamics. For complete information on the FoxDraw application, refer to FoxDraw (B0700BE)
and the associated on-line Help. This chapter describes the IACC interface with the FoxDraw
application only. The interface requires that FoxDraw 9.0 (or greater) be installed on the same
workstation as the IACC client.

FoxDraw Displays
A display is a file that is constructed and configured to be viewed from a FoxView screen. A dis-
play can represent a plant, a process area, or a detailed portion of a process and can be configured
to allow operator interaction with the process by moving objects or typing inputs. Displays are
composed of objects, each of which can be configured with attributes.
Object attributes determine the static and dynamic appearance of the object, and the actions you
can perform on an object. The term object includes primitive objects (such as lines, rectangles,
circles, and text), library objects, and bitmaps. Library objects include Invensys supplied and user-
built symbols, overlays, faceplates, and trends. The term symbols refers to a collection of objects
that you can copy to a display from Invensys supplied and user-built palettes.

Library Objects
Library objects include:
 Faceplates
 Trends
 Symbols
 Markers
 Buttons.
You can link a library object to a base display, overlay, or another library object that contains a
pointer to the library object, instead of a pasted copy. A display can have multiple references to
the same library object.

281
B0700FE – Rev A 10. Creating Displays

Interface with the FoxDraw Application

The FoxDraw application is integrated into IACC as an application that reads and writes com-
mon data to the IACC database. The IACC FoxDraw Editor supports all the functionality of a
stand-alone FoxDraw Editor.
The FoxDraw display file is represented by a reference object in the IACC database. The reference
object is created and maintained by IACC. Right-clicking the reference object displays a pop-up
menu, with the IACC FoxDraw Editor as one of the options available to create and edit the dis-
play file.
Whenever a FoxDraw display file is saved, IACC automatically creates lists of compounds and
blocks referenced in the display, which it stores with information about the linked object in the
display reference object.
Figure 10-1 shows the information stored in the object reference.

Object Reference

Display Files

Display File
Parameter

Station Reference
Parameter
Parameter
IACC Configured Workstations

Linked Object
Parameter

Display File Linked Object

Figure 10-1. Reference Object Parameters

282
10. Creating Displays B0700FE – Rev A

By integrating the FoxDraw application with IACC:

 The FoxDraw application joins the list of configurators that fall within the IACC
family of I/A Series configurators.
 Displays can be created using data obtained directly from the IACC database, which
contains all the control and reference information required for FoxDraw displays.
 Display-related information can be stored in the IACC database, enabling control
engineers to perform tasks such as:

Finding all the displays in which a block is referenced
 Displaying stations or workstations that contain a specific display
 Listing all the symbols in a display
 Listing all the variables in a display.
 You can assign displays to workstations and distribute them to workstations.

Displays
A display reference object represents a display in the IACC database. Display files are located
outside the IACC database, thus enabling the stand-alone version of the FoxDraw application as
well as the IACC version to edit them. The drawing is stored in a FoxDraw file (*.fdf ).
A reference object supports the following:
 A display associated with the reference object can be opened from the IACC FoxDraw
Editor utility.
 The display stays intact when the reference is deleted.
 A display can be edited from the stand-alone FoxDraw application.
 The name of a reference object can be different from the name of the display.
Display files can contain linked library objects that exist as independent, physically separate files.
A list of symbols, workstations, and compound:block.parameters that a display file uses are
available from its reference object and can be viewed using the ListView utility.
When you try to open a display that was manually deleted or renamed, the IACC version of the
FoxDraw application displays an appropriate warning message.

NOTE
If the FoxDraw file (.fdf ) is moved or renamed in the stand-alone FoxDraw
application, IACC is not able to find it. To access a renamed or moved file with
IACC, you must import it into the application, as described in “Importing Dis-
plays” on page 300.

283
B0700FE – Rev A 10. Creating Displays

Display Templates
A template is a display file that has specific compound and block references converted to macros.
When an instance of a template is created, the macro substitution process converts the macro
references back into instance-specific compound and block references (that reflect the actual
control strategy to which it is tied), and saves this information in the template reference object.
When an existing display is converted to a template, however, a reference object is not created,
because a template has its compound and block references composed of macros, and does not
refer to any actual instances of blocks and compounds.
Templates are located in the System tab under System > Components > Displays > Templates.

Synchronizing Displays and IACC

Synchronizing Changes Done Within Display Files
Changes can be made to display files outside the IACC version of FoxDraw software, in basically
one of the following three ways:
 The stand-alone version of the FoxDraw application can make changes to the display
file.
 DEdit can be used to find and replace parameter tag names in one or more display
files.
DEdit can be run via a command script.
 GEdit can add faceplates, trends, symbols, and buttons to existing displays.
GEdit, run via a command script, is a display engineering and maintenance utility
that supplements the capabilities of the FoxDraw application.
The above methods do not update the reference object contained in IACC. The reference object
is updated only when the IACC version of the FoxDraw application scans the display file, or
when a display is opened via the IACC FoxDraw Editor.
When the IACC FoxDraw application first opens a display file, the date/time it was created and
its file size is compared to the data stored in the associated IACC reference object. If either the
date/time stamp or the file size is different, the IACC FoxDraw application scans the display file,
removes any compound or block references in the reference object that no longer exist in the dis-
play, and adds new compound and block references for the valid compound:block:parameters
added to the display. While the display’s reference object is being updated, the FoxDraw applica-
tion updates any relationships that the referenced IACC blocks and compounds have with the ref-
erence object, keeping referential integrity intact. This prevents Where Used queries from
accidently reporting that a block or compound was referenced in a display file when it was not
actually referenced.

Synchronizing Changes Done Within IACC

You can delete or rename blocks and compounds from the IACC configuration, independent of
the IACC FoxDraw application, regardless of the number of displays in which the blocks and
compounds are referenced. When a block or compound has been deleted or renamed in an IACC
configuration, it is not removed from the reference object in which it resides.

284
10. Creating Displays B0700FE – Rev A

Creating a Display
The first step in creating a display involves creating a reference display file object in IACC. The
display associated with the reference object stores variable, symbol, and workstation assignments.

Adding a Display File to a Plant Area

To create a display file object from a Plant Area:
1. Click the Plant tab and expand the tree to display the Plant Area.
2. Right-click the Plant Area and choose New > Display File from the pop-up menu
(Figure 10-2, left side).

Figure 10-2. Creating Display Files

A new reference object with a default name such as Display Files1 is added under the
Plant Area. The object is assigned to the selected Plant Area.
The default name is highlighted in the Project Navigator indicating that name can
edited now.
3. Press Enter to accept the default name, or type a new name and press Enter.

Adding a Display File from the System Tab

To create a display file object from the System tab:
1. Click the System tab and expand System > Components > Displays.
2. Right-click Display Files and choose New Display File from the pop-up menu
(Figure 10-2, right side).

285
B0700FE – Rev A 10. Creating Displays

A new reference object with a default name such as Display Files1 is added under
Display Files. The object is not assigned to a Plant Area.
The default name is highlighted in the Project Navigator indicating that name can
edited now.
3. Press Enter to accept the default name, or type a new name and press Enter.

Renaming a Display File Object

To rename an object:
1. Right-click Display Files1 and choose Rename from the pop-up menu.
A box around the object name indicates that it is editable.
2. Type the new name and click outside the box.

Assigning a Display File to a Plant Area

Display files that are created from the Plant tab are automatically assigned to the selected Plant
Area object. These files and all the associated objects are downloaded when the parent Plant Area
object is selected for download.
To assign a display file created in the System tab to a Plant Area:
1. Right-click the Display File object and choose Assign to Plant Area from the
pop-up menu.
The Assign to Plant Area dialog box contains a tree view of the Plant Area.
2. Select the Plant Area and click OK.
The display file is assigned to the Plant Area and is downloaded when the object or its
parent is selected for download.
To unassign a display file from a Plant Area without assigning it to another Plant Area object:
1. Click the Plant tab and expand the tree to show the display file to be unassigned.
2. Right-click the display file object and choose Unassign from <Plant Area name>
from the pop-up menu.

286
10. Creating Displays B0700FE – Rev A

Creating a Drawing
To create a drawing:
1. Double-click the display file.
IACC opens the FoxDraw application in the Editor window and changes the menu
and toolbars to display the FoxDraw functions (Figure 10-3).

Figure 10-3. IACC FoxDraw Editor Option from a Display File Instance

2. For assistance using this editor, refer to FoxDraw (B0700BE), the FoxDraw Help, and
the tooltips.

Dragging Blocks to a FoxDraw Display

IACC automatically adds the default symbol or faceplate for a block when you drag the block
instance from the Project Navigator into a drawing in the FoxDraw Editor.

NOTE
This feature is only supported for blocks that are assigned to a compound.

To add a default symbol for a block:

1. Expand either the compound or the CSD in the Project Navigator to display the
block.

287
B0700FE – Rev A 10. Creating Displays

2. Do one of the following:

 Drag the block into the drawing to add the default symbol for the block type.
If there is no associated symbol, IACC adds the default faceplate.
 Press Ctrl while dragging the block to the drawing to add the default faceplate
for the block.
 Press Alt while dragging the block to the drawing to add a trend.
By default, IACC creates a group trend and configures the trend area’s
parameters, and trend and pen parameters.
Figure 10-4 shows a drawing where faceplates for two blocks have been added to the
drawing.

Figure 10-4. Default Faceplates Added to a Drawing

When you drop the block into the drawing, the bottom right corner of the display
object is positioned at the cursor location.
If more than one symbol is associated with the block, the Select FoxDraw Symbol
dialog box prompts you to select one from the list of symbols (Figure 10-5).

288
10. Creating Displays B0700FE – Rev A

Figure 10-5. Select FoxDraw Symbol Dialog Box

Selecting Default Objects

You can change the default drawing objects that are automatically added for a block when you
drag the block into a drawing. You can specify the default for an individual block instance, for a
block in a CSD Template, or for a derived block definition. (You can review the defaults for a
standard block definition, but you cannot change them.)
To select default drawing objects:
1. Right-click the block object in the Project Navigator and choose FoxView Options
from the pop-up menu to display the Configure FoxView Options dialog box
(Figure 10-6).

Add button opens

Specifies symbols the Enter Symbol dialog
for drag and drop box. Remove is active
into FoxDraw. when a symbol is selected.

Specifies a symbol for

Ctrl + drag and drop.
Specifies a symbol for
Alt + drag and drop.
Specifies an alias for use
with a CSD drawing. Not
needed when the symbol
involves only one block.

Figure 10-6. Configure FoxView Options Dialog Box

289
B0700FE – Rev A 10. Creating Displays

2. Add or remove the names of symbol objects in the Symbols list.

The objects you specify in the Symbols list are displayed in the Select FoxDraw
Symbol dialog box (Figure 10-5).
To add a symbol:
a. Click the Add button to the right of the Symbols list.
b. Type the symbol name (but not the .m1 extension) in the Enter Symbol dialog
box and click OK.
In Figure 10-6, two symbols are already listed, configuring the files AIN_Tank.m1
and AIN_Refill.m1, respectively. A third symbol AIN_A (.m1) is being added.
To remove a symbol:
a. Select the name in the Symbols list.
The Remove buttons becomes active.
b. Click Remove.
3. Check the Override box for Faceplate or Trend, and enter the object name, to
specify a different symbol file for the faceplate (Ctrl + drag and drop) or trend
(Alt + drag and drop).
The configuration in Figure 10-6 replaces the standard I/A Series PIDA faceplate with
PIDA_01, but keeps the default trend displays (group trend).
4. Click OK to close the dialog box and apply the changes.
If you rename a block or compound, the new name is not automatically propagated to objects in
the FoxDraw screen. The display object (faceplates, trends, and symbols) created before a name
change continues to use the old name. You must do one of the following:
 Delete these display objects and create them again.
 Manually change the configuration of the objects.
To manually change the names in a display object:
1. Double-click the display file in the Project Navigator if the symbol is not already
opened with FoxDraw in the Editor window.
2. Right-click the object and choose Configure Options from the pop-up menu.
FoxDraw displays the Configure Objects dialog box.
3. Click the Text Substitution tab (Figure 10-7), select the name, and click the Edit
button.

290
10. Creating Displays B0700FE – Rev A

Figure 10-7. FoxDraw Configure Objects Dialog Box

Creating a Drawing File for a CSD

IACC adds configured symbols to a drawing when you drag a CSD into the FoxDraw Editor win-
dow. This feature is only supported for the CSDs that meet the following criteria:
 The CSD is assigned to a compound.
 The CSD has at least one FoxDraw symbol associated with it.
 The block names are equated with the aliases described in the symbol.
If more than one symbol is associated with the CSD, the Select FoxDraw Symbol dialog box
(Figure 10-5) prompts you to select among the symbols associated with the block.
To create a drawing file for a CSD:
1. Assign the CSD to a compound if it is not already assigned.
a. Right-click the CSD object in the Project Navigator and choose Assign
Default Compound from the pop-menu.
b. Click the check box of a compound in the Assign Default Compound dialog box
and click OK (Figure 10-8).

291
B0700FE – Rev A 10. Creating Displays

Figure 10-8. Assigning a CSD to a Compound

2. Ensure that the symbol files (*.m1) to be used in the drawing are in the following
directory:
\opt\customer\displib\Symbols
In the following example, CAS_LOOP_1.m1 and CAS_LOOP_2.m1 have already
been copied to the folder.
3. Right-click the CSD object in the Project Navigator, choose FoxView Options from
the pop-up menu, and add the symbol names using the Configure FoxView Options
dialog box.
Figure 10-9 shows the FoxView Options dialog box opened for the CAS_LOOP CSD
Two symbols are already configured for this template: CAS_LOOP_1 and
CAS_LOOP_2.

NOTE
The FoxView Options can be configured for individual CSDs or for CSD Tem-
plates so that options are applied to each template instance. Additional symbols can
be added to an instance without breaking its link to the CSD Template.

4. Click the Add button, enter the name of the symbol (but not the file’s .m1 extension)
in the Enter Symbol dialog box, and click OK.
CASREV1 is being added in Figure 10-9.
5. Click Ok in the Configure Fox View Options dialog box.

292
10. Creating Displays B0700FE – Rev A

Figure 10-9. Setting FoxView Options for a CSD Template

6. Create and name the Display File as described on page 285, and double-click the
drawing file to open it in the FoxDraw Editor.
7. Select the CSD object in the Project Navigator and drag it into the drawing.
If only one symbol has been assigned in the FoxView Option dialog box, that symbol
is added to the drawing when you release the mouse button. If there are multiple sym-
bols assigned, the Select FoxDraw Symbol dialog box lists the options. Figure 10-10
shows a display file object (Display Files1) opened in the FoxDraw Editor window.
When the CSD object CAS_LOOP is dragged into the Editor window, the Select
FoxDraw Symbol dialog box lists the three symbols configured for the CSD. In
Figure 10-10, the symbol CAS_LOOP_2 has already been placed in the drawing.
8. Select the symbol and click OK to add the symbol to the drawing.
9. Complete the drawing, save the file, and exit the FoxDraw Editor.

293
B0700FE – Rev A 10. Creating Displays

Figure 10-10. Adding a Symbol to a Drawing a CSD

NOTE
The IDS Library contains multiple examples of FoxDraw symbols configured for
use with CSD Templates. Refer to Intelligent Design Studio (IDS) Library for IACC
(B0400BQ) for information on importing and using these examples.

Resolving FoxDraw Symbol Aliases

IACC only resolves aliases for compound names and block names. For IACC to be able to auto-
matically resolve symbol aliases, use the following:
 C to resolve the alias to the compound name
 B to resolve the alias to the block name
 CB to resolve the alias to the compound:block name.
A separate alias must be configured for each block represented in the drawing, using the form
alias name_C, alias name_B, or alias name_CB. For example, for a CSD with two analog
inputs that measure tank feeds, the following aliases can be configured to resolve the names of two
AIN blocks and their compounds, TANK01_CB and TANK02_CB.
To specify an Alias:
1. Expand the CSD object in the Project Navigator to display the individual blocks.

294
10. Creating Displays B0700FE – Rev A

2. Right-click the block and choose Configure FoxView Options from the pop menu
to open the dialog box (Figure 10-11):

Figure 10-11. Configure FoxView Options Dialog Box

3. Click the Override check box to the right of the Alias field in the lower half of the
dialog box.
4. Enter the name in the Alias field, and click OK.

Saving the Drawing File

The FoxDraw application does not automatically save the drawings. The application prompts you
to save the file when you close the FoxDraw Editor window.
To save a file:
 Choose File > Save from the menu bar.
When you save the display file, its reference object is updated with the following information:
 Workstations to which the display is assigned
 Library objects it contains.
The name and the location of the display file is specified when it is saved. You can save the file in
a directory under the \opt\fox\displib folder.

295
B0700FE – Rev A 10. Creating Displays

Managing Display Files

The pop-up menu for the Display File reference object in the Project Navigator provides options
for modifying the file as well as opening the FoxDraw Editor.

Deleting a Display File

When you delete a Display File reference object in IACC, the FoxDraw display file (*.fdf )
remains
unaffected.
To delete a Display File reference object:
1. Right-click the file and choose Delete from the pop-up menu.
The Delete Request dialog box allows you to review objects associated with the file
and confirm the delete action.
2. Click OK.

Assigning Displays to Workstations

A display file must be assigned to a valid workstation before being downloaded. You can assign the
same display to more than one workstation or to a single workstation in one download operation.
To assign a display file:
1. Right-click Display File and choose Assign To Workstation from the pop-up
menu.
The Assign Workstation(s) dialog box appears (Figure 10-12) listing the available
stations.

Figure 10-12. Assign Workstation(s) Dialog Box

2. Select the stations to which you want the files assigned and click OK.
You can also assign the file to an individual workstation by dragging the object to the
station object in the Project Navigator.

296
10. Creating Displays B0700FE – Rev A

Validating Displays
As part of the download of a display file and its associated symbols, faceplates and other library
objects, a validity check is run against the display file’s reference object. This validity check
ensures that the display file has been assigned to a valid workstation. A display file not assigned to
a valid workstation at the time of download is prevented from being downloaded.
To perform a display validation without initiating a download:
1. Right-click Display File in the Project Navigator (in either the Plant tab or the
System tab and choose Validate/Download > Validate from the pop-up menu.
The Display Validation dialog box appears as shown in Figure 10-13.

Figure 10-13. Display Validation Dialog Box

2. Click Next to continue the process.

The dialog box displays the progress of the validation. Errors are displayed in the
output window.

NOTE
Errors must be fixed before a download operation is done.

297
B0700FE – Rev A 10. Creating Displays

Downloading Displays
The Download command distributes the display files and their associated components to the
assigned I/A Series workstations. You can select the display file for download from one of three
object locations in the Project Navigator:
 The display file object in the System tab under System > Components > Display >
Display Files
 The display file object in the Plant tab under its parent Plant Area
 A parent Plant Area object in the Plant tab. This selection also causes a validation and
download of the objects under the Plant Area (see “Downloading from a Plant Area”
on page 317).
IACC copies the display files to the target station using the same directory structure used when
the files were saved on IACC. Thus if you save a file to c:\opt\fox\displib\symbols, it is placed in
/opt/fox/displib/symbols on Solaris based workstations and in d:\opt\fox\displib\symbols on
Windows based workstations. All display elements such as symbols, bitmaps, and trends are avail-
able within their corresponding directories.
The Foxboro user display location is:
 For Solaris workstations: /opt/customer/displib
 For Windows workstations: \opt\customer\displib.
To download displays:
1. Right-click Display File and choose Validate/Download > Download from the
pop-up menu.
IACC performs a validation of the files as described in “Validating Displays” on
page 297.
2. Click Next to proceed with the download operation.
The Display Download dialog box lists the selected drawing file (*.fdf ) and each com-
ponent listed in the drawing (Figure 10-14).

298
10. Creating Displays B0700FE – Rev A

Figure 10-14. Display Download Dialog Box

3. Select the drawing file and click the Download Stations button.
The Download stations dialog box lists the workstations to which you assigned the
displays (Figure 10-15).

Figure 10-15. Download Stations Dialog Box

When you select a station in the list box, its root directory is displayed in the lower left
corner. If the display has been assigned to more than one workstation, all the assigned
stations appear in the Download stations dialog box. The display can be distributed to
one or more stations in a single download operation.
4. Select the stations to which you want to download, and click OK.
The Download Stations dialog box closes.
5. Click Next in the Display Download dialog box (Figure 10-14).

299
B0700FE – Rev A 10. Creating Displays

The Downloading dialog box appears (Figure 10-16).

6. Click Start in the Downloading dialog box.

Figure 10-16. Downloading Dialog Box for Displays

7. Click Done to complete the download operation, if successful.

The results of the download process are displayed in the output window.

Importing Displays
IACC includes a facility for importing display files from the I/A Series system. The Import utility
scans the display file and builds an appropriate parallel reference object. When the import is com-
pleted, the reference object contains a pointer to the display file, and has established connections
to all the appropriate blocks and compounds within the IACC database. The displays can be
opened from their corresponding reference objects.
A display file being imported for the first time (no existing reference objects point to the display
file) does not have any connections established to any workstations until the specific display is
assigned.
If the display being imported already exists, the reference object gets modified to reflect the actual
compound and block references that are contained in the display file. Modifying a display outside
IACC and opening it through the IACC FoxDraw Editor also updates the information in the
reference object.

NOTE
The display file itself is not actually imported into IACC and remains external to
the IACC database. The display file must reside somewhere under IA share on the
IACC server.

You can import multiple display files, with a single import command invocation. For each display
file, an appropriate reference object is created.

300
10. Creating Displays B0700FE – Rev A

To import displays:
1. Choose File > Import from the menu bar to open the open the Available Formats
dialog box (Figure 10-17).

Figure 10-17. Available Formats Dialog Box

2. Select Import Display Agent and click Next.

The Import File Name dialog box appears (Figure 10-18).

Figure 10-18. Import File Name Dialog Box

3. Choose one of the following Selection type options:

 Select File(s) to import one of more display files in a specified directory.
In Figure 10-18 two files are being imported from the TEMP folder on the local
drive.
 Select Directory to import all the display files in a directory.
To import specific files:
a. Click Select Files(s) and click the Browse button to the right of the Dis-
play File Selection field to display the Open dialog box (Figure 10-19).

301
B0700FE – Rev A 10. Creating Displays

Figure 10-19. Selecting Display Files in the Open Box

b. Browse to the folder, select the files, and click the Open button.
Press Ctrl when selecting more than one file.
To import all files in a directory:
a. Click Select Directory and click the Browse button to the right of the
Import All Display Files... field to display the Select Import Directory dialog box
(Figure 10-19).

Figure 10-20. Selecting All Display Files in a Folder

b. Browse to the target directory and click Open when the directory is listed in the
Folder field.
The selection in Figure 10-19 imports a displays in the TEMP directory on the
local drive.

302
10. Creating Displays B0700FE – Rev A

4. Click Next to open the Select file location dialog box (Figure 10-21).

Figure 10-21. Select File Location Dialog Box

5. Select from the list provided to create a reference object under the appropriate branch
under Displays and click Next.
6. Click the Start button in the next dialog box to initiate the import.
After the import is done, you can observe a reference object created for the imported
display, under the appropriate branch in the display tree. In this case, a new reference
object is created under Display Files.

ListViews, Properties, and Where Used

Display File ListViews include:
 Display Symbols List of library objects linked in the display.
 Display Variables List of compounds, blocks, parameters used in the display and its
components.
 Workstations List of the workstations where the display has been downloaded.

The Properties dialog box is used to view and edit properties of a display from the corresponding
reference object.
The Where Used search utility provides a list of all the workstations associated with a selected
display. The results of a Where Used search are displayed in the output window. The Where Used
utility is also available from the IACC FoxDraw Editor. The Display Edit utility supports this
feature. For more information, refer to FoxDraw (B0700BE).

303
B0700FE – Rev A 10. Creating Displays

304
11. Downloading Control Blocks
This chapter describes validation and download of a control database to the control processor.
The control download function in IACC transmits the selected compounds and blocks to the
assigned CP via a network connection to the host workstation for the CP. The compound and
block parameters are sent to a work file in the host workstation. A download from the host to the
CP is then initiated (Figure 11-1).
Note that only compound and block data are downloaded to the host and the CP. The
download does not include objects used in the creation of the compounds and blocks such as
CSDs and CSD Templates (although you can initiate a download from these objects). CSDs and
CSD Templates only reside in the IACC database, its backup files, and any export you may have
created. The IACC database is automatically backed up each time you perform a download.
IACC also enables you to initiate a checkpoint of the CP and to upload the compound and block
information from the CP to compare the configuration with the IACC database.

Host Workstation
AW70AA Control Stations
Windows XP Client
Download
Download
Work File Upload
Compare to CP
IACC
Reboot CP4B01
Application
Download Checkpoint File Checkpoint

Backup Restore
Compare
to CP Download
Work File Upload
Reboot CP4B02
Backup Files Checkpoint File Checkpoint

Figure 11-1. Control Database Locations

Before beginning a download operation to a control processor, you must perform a Control
Hierarchy Validation operation to ensure the validity of all the software associations (control
processors, CSDs, compounds and blocks) to the control processor in the IACC database.
There are three validation types in IACC:
 Control Hierarchy Validation operation for objects (page 310)
 Hardware and Software Validation operation (Chapter 4 “System Configuration”)
 Display Validation for FoxDraw Displays (Chapter 10 “Creating Displays”)

305
B0700FE – Rev A 11. Downloading Control Blocks

A Control Hierarchy Validation can be invoked by itself; however, it is also performed at the
beginning of a download operation.
If you are tracking configuration changes with FoxCTS Change Tracking Software (FoxCTS) for
21 CFR Part 11 compliance, you can configure IACC to record the details of each download
event and pass the information to the FoxCTS application.
IACC offers two tools to test the control objects that you have downloaded to the CP:
 Quick View Available to IACC clients running on I/A Series
workstations. Automatically generates a
FoxView group display of the blocks in a
CSD with live data from the CP.
 Animated Loop Drawings (ALDs) Available to both on-platform and off-platform
IACC clients. Displays live data in the CSD
Editor, and enables you to set block parameters
in the CP and align the IACC database with the
CP database.

Two IACC utilities can be used to align the IACC databases with the objects in the CP databases:
 Synch to CP Verifies the download status and execution
order of the blocks and compounds in the IACC
database against the objects actually in the CP.
If the status and execution order are incorrect, the
utility displays recommendations on how to align
the IACC and CP databases.
 Compare to CP Enables you to identify differences between block
parameters in the work file of the CP’s host and
the same parameters in the IACC database. The
utility provides several methods of reconciling
the two databases, including selectively uploading
parameters from multiple blocks and compounds.
The Upload and Compare to CP command
updates the work file with values from the CP
prior to launching the Compare to CP utility.

This chapter covers the following topics relating to downloading control objects to the I/A Series
system:
 “Enabling IACC Downloads to a Control Station” on page 307
 “Control Hierarchy Validation” on page 310
 “Downloading Compounds and Blocks” on page 312
 “FoxCTS Change Tracking” on page 322
 “Shrink Command” on page 325
 “Quick View” on page 327
 “Animated Loop Drawings” on page 329
 “Initialize CP” on page 347
 “Viewing Block Status” on page 337

306
11. Downloading Control Blocks B0700FE – Rev A

 “Viewing Block Status” on page 337

 “Synch Utility” on page 340
 “Comparing to CP” on page 343.

Enabling IACC Downloads to a Control Station

While IACC was developed as a replacement for the Integrated Control Configurator (ICC), the
software supports co-existence with ICC and with FoxCAE, which uses the facilities of IACC to
perform control downloads. You can use either IACC or ICC to maintain the control configura-
tion in a specific control station, but you cannot use both for the same station.
The IACC Safeguard program runs in the background on an IACC server to prevent ICC down-
loads to IACC stations and IACC downloads to control stations that are being maintained with
ICC. The user-created IACC-CP file on the server specifies which CPs are to be configured with
IACC and lists the host workstation for each CP. The IACC Safeguard program sends the IACC-
CP file to the listed workstations. The workstations, in turn, check the file before allowing a
download from either IACC or ICC:
 If the target CP is listed in the IACC-CP file, the workstation allows downloads from
IACC, but not from ICC.
 If the CP is not designated in the file (or if there is no IACC-CP file on the worksta-
tion), the workstation permits downloads from ICC, but not from IACC.

NOTE
When there are multiple IACC servers, the IACC-CP file should be created on one
server and the IACC Safeguard program should run on that server for all CPs and
host workstations on the network.

To designate control stations as IACC CPs:

1. Open ..\IACC\CoExistence\IACC-CP using Notepad or a similar text editor.
2. Follow the template in file to list the IACC control stations.
For each station, insert a line with the control station name, and the name and IP
address of its download host.
You must use a tab to separate the three elements in the list.
Make sure that you specify the ethernet address used by IACC:
 The second Ethernet port when IACC is installed off-platform or when IACC is
being used in an I/A Series environment that includes a 100 Mbps switched con-
trol network and a legacy 10 Mbps Nodebus (see the configuration in Figure 1-3
on page 3).
 The main Ethernet port specified during system configuration of the download
host when IACC is being used to configure an I/A Series Version 8.x system, and
the IACC server and clients are implemented on I/A Series workstations and com-
municate with the download hosts directly over The Mesh Control Network (see
the configuration in Figure 1-4 on page 3).
Figure 11-2 shows the file with three FCP270s designated as IACC CPs.

307
B0700FE – Rev A 11. Downloading Control Blocks

Figure 11-2. Entering Control Stations in the IACC-CP File

3. Save the file.

4. Use Explorer to execute ..\IACC\bin\IACCSafeguards.exe.
The IACC Safeguards program sends the IACC-CP file to the host workstations listed
in the file.
For example, the file in Figure 11-2 is sent to two workstations, AW70A1 and
AW70A2. Each workstation references that file before allowing a configurator to
download to one of its CPs. Based on the last entry in Figure 11-2, workstation
AW70A2 allows IACC downloads for control station FCP004, and prevents updates
from ICC. Other CPs hosted by the workstation, but not listed in the IACC-CP file,
can be updated by ICC, but not by IACC.
Once executed, the IACC Safeguards program runs in the background according to
the parameters set in the file IACCSGSettings.dat in the ..\IACC\CoExistence folder
(Figure 11-3). You can change the program interval and log setting at any time.

Figure 11-3. IACC Safeguard Program Settings

5. Update the IACC-CP file each time you create a new control station.
6. Ensure that IACCSafeguards.exe is scheduled to start automatically when you start
the IACC workstation.
a. Choose Start > Settings > Control Panel, and double-click Scheduled
Tasks in the Control Panel to open the Scheduled Tasks window.

308
11. Downloading Control Blocks B0700FE – Rev A

b. If IACCSafeguard is not configured to Run at system startup, double-click

Add Scheduled Task to open the Schedule Task Wizard.
c. Click Next in the first wizard page, click Browse in the next page, and use the
Select Program to Schedule dialog box to select:
..\IACC\bin\IACCSafeguards.exe.
d. When the wizard lists IACCSafeguard as the program to schedule (Figure 11-4),
select When my computer starts and click Next.

Figure 11-4. Selecting Start Time in the Schedule Wizard

e. Enter the required user information on the next wizard page (Figure 11-4), and
click Next.

Figure 11-5. Entering User Name and Password in the Scheduled Task Wizard

309
B0700FE – Rev A 11. Downloading Control Blocks

Control Hierarchy Validation

Control hierarchy validation commences at the compound level for each of the four validation
object candidates: control processors, CSDs, compounds, and blocks. Control Hierarchy
Validation has no database objects which it uses exclusively.
 A compound list is built from the validation in each case, and each compound is a
starting point for hierarchy validation.
 If a control processor is selected, hierarchy validation is performed on each of the
compounds assigned to the CP.
 If a CSD is selected, the CSD’s block list is retrieved, and each block’s parent
compound is a starting point for hierarchy validation. The entire compound is
validated, even if the compound includes blocks from other CSDs.
 If a compound is selected, the compound is the starting point for validation.
 If a block is selected, the block’s parent compound is the starting point for the
hierarchy validation, and the compound is validated.
A separate block list is built for blocks not assigned to a compound. In this case, the block list is
the starting object for validation, and all block checks are executed against each block. However,
without assignment to a valid compound, a block object’s valid bit is not set even if all block-level
checks have been passed.
When an object is selected for validation, its parent and child objects are also validated. For
example, if a block is selected to be validated, it and its compound are validated, but not its
sibling blocks.

What Validation Checks are Performed

Validation checks are performed on an object if it is not valid or if it is valid but one or more
checks resulted in warnings.
All validation checks for that object are always executed on an object to extract as much
information as possible in a single pass; for example, multiple errors can be generated from a
single validation run on an object. However, in some contexts such as lack of assignment to a
compound or control station, the execution of certain checks are skipped to minimize the output
of redundant error or warning messages. In these cases, the checks are considered to have failed,
and the effect on validation is the same as if they were fully executed.
Out-of-range checking is done on all targetable object parameters. It is not restricted to the subset
of targetable and configurable parameters. The out-of-range attribute on a parameter is set or
cleared for compound and block period and phase, according to the results of the out-range-check
on the compound or block object.
The validation of block execution order enforces the correct relative order of block execution zone
values as specified by the control station. The order as checked, is the order in which the blocks
are processed by the control station after download. There is no checking that the execution zone
value for an individual block is correct for the block’s type.
Download granularity checks are made only on previously downloaded and then reassigned
compounds or blocks to minimize the number of objects on which this premium type of checking
is performed. Download granularity checking is not performed if the downloaded object is a
CSD, since there is no source context in that case. Download granularity checking does include
checking for possible compound or block reordering.

310
11. Downloading Control Blocks B0700FE – Rev A

Results of a Validation
The possible results of a Validation are:
 Success
 Failure
 Success with warnings
 For all checks
Valid bit for the object set, successful return from the
validation agents.
Valid bit for the object not set, unsuccessful return
from the validation agent.
Valid bit set, warning messages issued, successful return
from the validation agent.
A warning or error message is issued to the Control
Station Download tab of the output window if the
check fails.

NOTE
Some individual checks, if failed, issue an error message and fail the validation,
while other checks, if failed, do not fail the validation but issue a warning message.

Summary of Checks Performed at Each Object Level

Control hierarchy validation performs a series of checks on a compound hierarchy in an efficient
progression. The following lists summarize the functionality of the validation checks performed at
each object level:
CP checks include:
 Parameter values not out-of-range
 The CP is assigned to a host if the CP is not self-hosting
 The CP host is reachable
 Sufficient download granularity for compounds:
 Compounds that have been assigned to the CP
 Previously downloaded compounds that have been assigned to another CP.
CSD checks include:
 All blocks in the CSD are assigned to compounds (ECBs in the CSD can be assigned
to a CP or a compound).
Compound checks include:
 Assigned to a control station  The control station assigned to
 The CP host is reachable a host if it is not self-hosting
 Name is valid  All CP-level checks, if the
compound is assigned to a CP
 Compound is legal to execute on
the host control station  All parameter values in range
 Sufficient granularity of download  Valid period and phase
(if a block has been re-assigned,  Child block execution order
checks to see if a download of is valid
either the parent compound or the  All child block checks.
host CP is required)

311
B0700FE – Rev A 11. Downloading Control Blocks

Block checks include:

 All parameter values are in range.
 Block can be executed on the assigned CP
 Period and phase are valid
 Parent compound’s period is less than or equal to the block’s
 For PLBs, the ladder is compiled
 For Sequence blocks, the source code is compiled.

Downloading Compounds and Blocks

The Download function enables control database object instances to be downloaded to a control
station. You can download unmodified object instances and object instances that have been
modified in an editor, as long as these instances pass a Control Hierarchy Validation check.
You can select the download function from the following objects:
 Plant Areas
 Control processors (control stations)
 Compounds
 CSDs
 Blocks.
Typically, downloading the database objects to a control station is the last activity in the control
configuration sequence.
Downloading to a control station involves:
 Creating the new object instances assigned to the control station since the last
download in the control station
 Deleting objects unassigned or removed from the control station
 Writing the parameters associated with an object to the control station.

312
11. Downloading Control Blocks B0700FE – Rev A

The download actions performed depend on which object is selected when the downloaded
function is invoked (Table 11-1).

Table 11-1. Download Actions

Object Selected Download Actions

Control Station  Downloads all compounds assigned to the control processor
and all blocks assigned to the compounds.
CSD  For each block in the CSD, downloads the compound to
which the block is assigned, if not already downloaded.
 Downloads each block in the CSD to the control processor.
CSD Template  Downloads all CSD instances created with the template.
Plant Area  Downloads all compounds, CSDs, and display files assigned
to the Plant Area and its child Plant Areas.
Compound  Downloads the compound and its blocks to the control
processor.
Block  Downloads the block to the control processor.
 Downloads the parent compound if the compound has not
already been downloaded to the CP.
 Downloads only the selected block; other blocks in the
compound are not downloaded.

When you have completed configuration of the control strategy, you must download it to the
control processor via a network connection to the control processor’s host.
The instructions in this chapter assume that the processor’s configuration has already been loaded
via the Commit diskette, and that its host is available to the IACC application.
The control blocks are downloaded to the CP database when you select download from the
pop-up menu of any of the following objects:
 Plant Area
 System
 Compound
 Block
 Control Station
 CSD
 CSD Template.
The first step in the download process is validation of the objects. The validation can be invoked
independently from the download, as described in the next section.

313
B0700FE – Rev A 11. Downloading Control Blocks

Control Hierarchy Validation

You can validate the hierarchy of objects assigned to a specific hardware or software object in
IACC such as a CSD, compound, or control processor.
To perform a control hierarchy validation:
1. Right-click the object in the Project Navigator and choose Validate/Download >
Validate from the pop-up menu.
The Hierarchy Validation dialog box appears (Figure 11-6).

Figure 11-6. Hierarchy Validation Dialog Box

2. Click Next to initiate the process.

The progress of the validation process is displayed in the dialog box. Errors are
displayed in the Validating Dialog Box and the Output Window Download-Related
Tabs (Figure 11-7).

314
11. Downloading Control Blocks B0700FE – Rev A

Figure 11-7. Validating Dialog Box and Download-Related Tabs in the Output Window

Figure 11-7 includes the Control Station Download and Download Summary tabs
because the validation was performed on a control compound. Other tabs may be
displayed depending on the object selected for validation. For example, if you select
Validate/Download > Validate from a Plant Area that contains compounds and
displays, the Output window also includes the Display Download tab.
3. Click Done when the dialog box indicates that the object has been successfully
validated or that the process has been stopped because of errors in the object
configuration.
4. Review the messages in the download-related Output window tabs to identify and
correct any errors.

315
B0700FE – Rev A 11. Downloading Control Blocks

Performing a Download
This section describes various ways of downloading control compounds to a CP. If you are using
FoxCTS software to track configuration changes for 21 CFR Part 11 compliance, you can
configure IACC to record the particulars of each control download and pass the information to
the FoxCTS application. When FoxCTS tracking is enabled, IACC displays the FoxCTS Change
Tracking dialog box (Figure 11-8) each time one or more compounds are selected for download.

Figure 11-8. FoxCTS Change Tracking Dialog Box

IACC does not allow you to proceed with the download until you make an entry in the dialog
box. For information on setting up FoxCTS tracking, see “FoxCTS Change Tracking” on
page 322.

Downloading a Compound
To download a compound:
1. Locate the compound in the Project Navigator either under its Plant Area in the
Plant tab or under its CP in the Network tab.
2. Right-click the compound and choose Validate/Download > Download from the
pop-up menu.
IACC begins the download by validating the object, as described in
“Control Hierarchy Validation” on page 314.
3. Click Next in the Hierarchy Validation dialog box (Figure 11-6).

316
11. Downloading Control Blocks B0700FE – Rev A

4. When validation has been successfully completed, click Next to display the
Downloading dialog box (Figure 11-9), which lists the compound and the blocks to
be downloaded to the control processor.

Figure 11-9. Download Control Station Dialog Box

5. Click Start.
IACC begins the download process. Successful completion or an error condition is
shown in the Control Station Download tab of the Output window.
6. Click Done when the download is complete.

Downloading from a Plant Area

You can also download compounds and blocks by selecting objects to which they are assigned or
objects from which they were created. These download objects include Plant Areas, CSDs or CSD
Templates, control processors and the configuration object in the Network tab.
To download a compound from a Plant Area object:
1. Right-click the Plant Area object in the Project Navigator and choose
Validate/Download > Download from the pop-up menu.
IACC begins the download by validating all the compounds and displays which are
assigned to the object as described in “Control Hierarchy Validation” on page 314.
The validation includes the compounds, blocks in the CSDs, and displays assigned to
both the Plant Area and to its child Plant Areas.
2. Click Next in the Hierarchy Validation dialog box (Figure 11-6).
If there are validations errors, you cannot proceed with the download.
 Fix all the errors identified in Display Download, Control Station Download, and
the other tabs in the Output window, and restart the download process from the
object.

317
B0700FE – Rev A 11. Downloading Control Blocks

3. Click Next in the Validating dialog box (Figure 11-7).

The Control Station Download dialog box (Figure 11-10) lists the compounds associ-
ated with the Plant Area:
 Compounds assigned to the Plant Area
 Compounds assigned to the child Plant Areas
 Parent compounds of blocks in the Plant Area CSDs or those of a child
Plant Area.

Figure 11-10. Downloadable Compounds

318
11. Downloading Control Blocks B0700FE – Rev A

4. Select the items individually or click Select All, and click Next.
If you are downloading from a Plant Area that has Display Files assigned to it, the
Display Download dialog box (Figure 11-11) prompts you to select from among the
files.

Figure 11-11. Display Download Dialog Box

319
B0700FE – Rev A 11. Downloading Control Blocks

a. For each file you want to download, select the file in the list box and click
Download Stations.
Another dialog box (Figure 11-12) enables you to select among the stations
assigned to the Display File.

Figure 11-12. Download Stations Dialog Box for Display Files

b. Select the stations and click OK.

c. Click Next in the Display Download dialog box when you have finished selecting
files and stations.
The Downloading dialog box lists all the objects to be downloaded to the control
processor (Figure 11-13). The Action column indicates whether the object is to be
added to the CP or used to update a previously downloaded version of the object.

320
11. Downloading Control Blocks B0700FE – Rev A

Figure 11-13. Download Control Station Dialog Box

5. Click Start.
IACC begins the download process. A successful completion or an error condition is
displayed in the dialog box (Figure 11-14) and in the Download Summary tab in the
Output window. Errors involving compounds are also listed in the Control
Station Download tab, while errors involving displays are shown in the Display
Download tab.

Figure 11-14. Download Complete

6. Click Done to close the dialog box.

321
B0700FE – Rev A 11. Downloading Control Blocks

Downloading from a CSD or CSD Template

You can download compounds and blocks by selecting a CSD for download. After validation of
the downloadable objects, the Downloading dialog box prompts you to select from the parent
compounds of the blocks in the CSD. The process continues as if you had selected to download
individual compounds.
You can batch CSD downloads by selecting a CSD Template as the download object. After
validation of all the instances of the CSD Template in the database, the Downloading dialog box
prompts you to select which of these CSDs you want to download. This process selects the parent
compounds of all the blocks in the CSD Template instances.

FoxCTS Change Tracking

IACC provides a link to FoxCTS software so you can track control configuration changes for
21 CFR Part 11 compliance. When FoxCTS integration is configured, IACC creates an event file
with the following information each time a compound is downloaded:
 Affected CP and compounds
 New parameter values
 Originating IACC workstation
 Time and type of download
 IACC user initiating the download
 Reason for the download given by the user in the FoxCTS Change Tracking
dialog box (Figure 11-8).
The download event file is then sent to the FoxCTS application monitoring the affected CPs, as
configured in the I/A Series System Monitor instance. IACC maintains the file until the transfer
to FoxCTS has been verified. IACC issues a warning message if the transfer has not been verified
within a user-specified time.
For additional information on configuring and using FoxCTS, refer to FoxCTS Change Tracking
Software (B0193VV).
Setting up change tracking with IACC involves the following:
 Creating a directory on the FoxCTS server to receive the download event files
 Verifying that the System Monitor instance is properly configured for the
FoxCTS application
 Enabling the FoxCTS integration within IACC
 Authorizing user access
 Starting the FoxCTS application.

322
11. Downloading Control Blocks B0700FE – Rev A

Directory for Download Event Files

To configure the destination directory for the download event files:
 Create the following directory on the FoxCTS server:
\opt\foxind\cms\srvr\data\iacc

Verifying the System Monitor Configuration

To verify that the System Monitor application is properly configured for the FoxCTS application:
1. Select the host workstation in the Network tab and expand the object to display the
System Monitor software:
 ASMON6 for a Solaris workstation
 ASMON7 for a Windows workstation.
2. Right-click the software object and choose Properties from the pop-up menu
(Figure 11-15).

Figure 11-15. Verifying System Monitor Configuration

3. Click the Software tab and verify that the letterbug of the FoxCTS host workstation
is in the FoxCTS Server field.
4. Click the SMSTM tab and verify that the display lists all the CPs for which FoxCTS is
to monitor configuration changes, and the CPs’ host workstations.

323
B0700FE – Rev A 11. Downloading Control Blocks

Enabling FoxCTS Integration

To enable FoxCTS integration:
1. Choose Tools > Options from the menu bar to open the IACC Options dialog box
(Figure 11-16).

Figure 11-16. IACC Options Dialog Box

2. Check Enable 21 CFR Part 11 Change Tracking in the FoxCTS Integration

group.
3. Specify a warning period for verification of the file transfer to FoxCTS.
The warning period can be set from 10 to 120 minutes. The default is 30 minutes.
4. Click OK to apply the changes and close the dialog box, or click Apply and set other
IACC options.

Authorizing User Access

The use of login accounts is vital to the secure and traceable operation of both IACC and
FoxCTS.
When the FoxCTS link is enabled, FoxCTS accepts the information from any download and
associates that information with the IACC user name. If the IACC defined user is to be allowed
login access to the FoxCTS system, set up a login account in FoxCTS with the same user name
before that user performs any downloads.
The login accounts are separately managed by IACC and FoxCTS, and each application has its
own rules for defining login accounts. For example, FoxCTS supports periodic password expira-
tion and has a 12-character limit for the user name. Refer to FoxCTS Change Tracking Software
(B0193VV) for information on setting up user accounts.
If the IACC user name is not defined in FoxCTS at the time of the download, FoxCTS accepts
the download information but does not allow the IACC user to access the information.

324
11. Downloading Control Blocks B0700FE – Rev A

Starting FoxCTS
Refer to FoxCTS Change Tracking Software (B0193VV) for information on starting and using
FoxCTS.

Shrink Command
The Shrink command compresses the work files for the selected CP on the host workstation.
Shrinking recovers disk space on the workstation, and should be done after there have been
multiple updates to the CP databases.
To compress the work file for a CP:
 Right-click the control processor in the Project Navigator and choose
Validate/Download > Shrink from the pop-up menu.

CP Checkpointing
Checkpoint saves the control station database in a checkpoint file on its host workstation. The
checkpoint file is the database saved in the form that is loaded from the host to the control station
when that station is rebooted. In the default IACC configuration, checkpointing is automatically
performed after every download procedure. However, because checkpointing can consume a
significant amount of time, the user Administrator can disable the automatic checkpointing. This
feature is intended for commissioning activities only.

! WARNING
It is not recommended that Checkpointing be disabled. If a control station is
rebooted before checkpointing has been done, the programs running in the station
do not match those in IACC. To correct the discrepancy, reload the station.

NOTE
All stations must be checkpointed before the Download without checkpoint option
is enabled.

To set the checkpointing option:

1. Manually checkpoint the CPs to which you download before setting the option:
a. Click the Network tab and expand the tree to display the target CPs.
b. Right-click each CP object and choose Validate/Download > CP Checkpoint
from the pop-up menu.
2. Choose Tools > Options from the menu bar to display the IACC Options dialog
box (Figure 11-17).

325
B0700FE – Rev A 11. Downloading Control Blocks

Figure 11-17. IACC Options Dialog Box

3. Check Download without checkpoint to disable automatic checkpointing.

NOTE
When Download without checkpoint is enabled, there is no automatic backup of
the last download database after a download.

4. Use the Warning interval field to specify the time interval between
messages informing users the that control processors in the database are not being
checkpointed.
5. Uncheck the option when you have finished the downloads.
Although the Download process does perform a checkpoint, the CP Checkpoint command is
available so you can perform a checkpoint on demand. If your download is successful, you can
perform a CP Checkpoint function to make a backup of your database.

NOTE
One purpose of checkpointing is to resolve connections between blocks. If check-
pointing is disabled, these connections are not resolved until you perform a manual
checkpoint.

To perform a manual CP checkpoint:

 Right-click the control processor in the Project Navigator and choose
Validate/Download > CP Checkpoint from the pop-up menu.

326
11. Downloading Control Blocks B0700FE – Rev A

Quick View
Quick View is a commissioning tool available to on-platform IACC clients. Quick View, which is
accessed from the CSD Editor, automatically generates a FoxView group display with a faceplate
for each block in the CSD. The Quick View shows live data from the CP. The faceplates are
arranged in the same relative positions as the blocks in the CSD (Figure 11-18).

Figure 11-18. Quick View Display

To access Quick View:

1. Start the FoxView application if it is not already running.

327
B0700FE – Rev A 11. Downloading Control Blocks

2. Open the CSD in the CSD Editor, and click one of the three buttons in the
FoxView toolbar (Table 11-2).

Table 11-2. FoxView Toolbar Buttons

Toolbar Description
Shows faceplates for the blocks that are fully visible in the CSD
Editor window.
Shows faceplates for all blocks that are at least partially visible in
the CSD Editor window.
Shows faceplates for all the blocks that belong to the CSD.

The FoxView group display appears as shown in Figure 11-18. The drawing is saved
to the d:\opt\CSDs directory.
Quick View uses default faceplates for the I/A Series block type. You can, however,
configure alternatives for one or more blocks using the Configure FoxView Options dialog box.
To select an alternative Quick View faceplate:
1. Right-click the block instance in the CSD and choose FoxView Options to open the
Configure FoxView Options dialog box (Figure 11-19).

This field specifies

the graphic to be used
to represent the block
in a Quick View.

Figure 11-19. Configure FoxView Options Dialog Box

328
11. Downloading Control Blocks B0700FE – Rev A

2. Click the Override check box to the right of the Faceplate field.
3. Enter the name (but not the .m1 extension) of the symbol file.
In Figure 11-19, a custom faceplate symbol, AIN_Refill.m1, has been specified as the
faceplate. See “Creating Displays” on page 281 for additional information on the
FoxView options and drawings.

Animated Loop Drawings

After downloading a CSD, you can convert the CSD to an Animated Loop Drawing (ALD) to
test the control strategy, update the IACC database, set parameters in the CP database, and obtain
trend displays of selected parameters. Unlike Quick Views, ALDs can also be generated from
off-platform IACC clients.
An ALD is a CSD displaying live data from the CP for parameters visible in the port areas of the
block appearance objects. Figure 11-20 shows an ALD open for CSD2020. The current values
from the CP are displayed adjacent to the parameters just outside the block appearance objects.

Figure 11-20. Live Values Displayed in a CSD

An A or M in the upper left corner of each block indicates whether the block is running in
automatic or manual mode.

329
B0700FE – Rev A 11. Downloading Control Blocks

The ALD toolbar has been dragged into the CSD Editor and is visible in the upper left corner of
the CSD. The toolbar provides shortcuts to three ALD commands that are included in the Tools
menu when the CSD Editor is open (Table 11-3).

Table 11-3. ALD Toolbar and Menu Selections

Toolbar Menu Bar Description

Tools > ALD > Start Animation Starts live updates from the CP, displays
values for parameters visible in the port
areas, and locks the CSD.
Tools > ALD > Stop Animation Stops the animation.

Tools > ALD > ALD Options Opens a dialog box for selecting a server
and setting other ALD options.

NOTE
As indicated in the title bar, the CSD is locked in a read-only mode while the
animation is running so that no changes can be made to the blocks in the IACC
database except through update tools provided during the ALD. In fact, you cannot
perform any other IACC function including downloads.

There are four requirements that must be met before converting a CSD to an ALD:
 The blocks in the CSD must be downloaded to the CP.
 The blocks’ parent compounds must be on.
 The IACC client machine must be connected to a FoxAPI or AIM*API server on an
I/A Series workstation that is connected to the target CPs.
 The user must have permission to access ALDs. If security is enabled, the user must
belong to a group that has Animated CSD enabled in the System wide permissions.
Refer to Chapter 12 “Security” for information on controlling users access to IACC
features.

330
11. Downloading Control Blocks B0700FE – Rev A

FoxAPI/AIM*API Server Setup

IACC accesses the live values displayed in ALDs using a FoxAPI server or an AIM*API server on
an I/A Series workstation. You select this target server using the ALD Options dialog box.

NOTE
In this section the term server refers to the FoxAPI or AIM*API software operating
on an I/A Series workstation that enables a connection for live updates. This is not
the IACC server.

The dialog box lists available servers based on the FoxAPI or AIM*API client initialization file
(an_init.cfg) in the C:\Windows directory. You can add servers to a file as follows:
If IACC is installed on a machine that is already a FoxAPI client:
1. Configure an_init.cfg using the FoxAPI applet in the Control Panel
(Figure 11-21).

Figure 11-21. FoxAPI Connect Utility Dialog Box

2. Enter the FoxAPI server’s I/A Series letterbug in the AW Name field and the
IP address in the IP Address fields, then click Apply.
The AW Name is added to the list of AW stations in the dialog box, and can now be
selected for live updates.

331
B0700FE – Rev A 11. Downloading Control Blocks

If IACC is installed on a machine that is already an AIM*API client:

1. Start the Api Admin utility, and click Edit Server Connections in the Settings
tab.
2. Enter the letterbug of the target AIM*API server in the Path Alias field and its
IP address in the IP address fields, and click Apply.
The Path Alias is added to the list of Aliases in the dialog box, and can now be selected
for live updates.
3. Click Accept and exit Api Admin.
If the IACC machine is neither a FoxAPI client or an AIM*API client:
1. Use Notepad or a similar text editor to open the an_init.___ file in
\IACC\Examples\FoxAPI.
2. Follow the instructions in the file (Figure 11-22) to:
a. Add a line in the [TCPIP] section that maps a server name to an IP address and
port number.
The server name is the letterbug of the I/A Series workstation on which the
FoxAPI server or the AIM*API server is running.
For a FoxAPI server, use the following syntax:
<Server name> = "<IP address> 55555 /dev/tcp 1024"
For example: AW70AA = "64.9.34.88 55555 /dev/tcp 1024"
For an AIM*API server, use the following syntax:
<Server name> = "<IP address> 45678 /dev/tcp 1024"
For example: AW70BB = "64.9.34.88 45678 /dev/tcp 1024"
Note that FoxAPI and AIM*API servers use different port numbers.
b. Add a line under [IA Server Connections] that identifies the FoxAPI or
AIM*API server.
Use the following syntax:
SERVERNAME = <Server name> TCPIP 1 0 1 1 / 1
For example: SERVERNAME = AW70AA TCPIP 1 0 1 1 / 1

332
11. Downloading Control Blocks B0700FE – Rev A

Figure 11-22. Sample Client Initialization File

3. Save the file as an_init.cfg in the C:\Windows directory.

Setting ALD Options

Use the ALD Options dialog box to select the I/A Series workstation to supply live data from the
CPs and set other options. These settings are applied to all CSDs in the database.
To set ALD options:
1. Open any CSD in the CSD editor.
2. Click in the ALD toolbar or choose Tools > ALD > ALD Options from the
menu bar to open the Animated Live Diagram Options dialog box (Figure 11-23).

333
B0700FE – Rev A 11. Downloading Control Blocks

Figure 11-23. Animated Live Diagram Options Dialog Box

3. Use the Host pull-down list to select an I/A Series workstation to supply the live data
from the CPs (using a FoxAPI or AIM*API server on the workstation).
See “FoxAPI/AIM*API Server Setup” on page 331 if the pull-down list does not con-
tain the letterbug of the appropriate I/A Series workstation.
4. Click Test Host to verify that IACC can connect to the FoxAPI or AIM*API server
selected workstation.
5. Specify a scan rate in seconds and a change delta as a percentage of range.
If a parameter value does not change by at least the specified delta, the parameter’s
ALD display is not changed.
6. To record changes made during the ALD session using Operator Action Journal
(OAJ):
a. Check the Log Actions into OAJ option.
b. Use the pull-down list in the Host field to select OAJ and click Test Host to
verify access to the selected instance.
c. Optionally, use the pull-down list in the AIM*Historian field to select an
historian instance that collects OAJ messages, and click Test Historian to
confirm access to the instance. See the AIM*Historian User’s Guide (B0193YL) for
information on configuring the message collection option.
7. Click OK.

ALD Sessions
To use ALD:
1. Double-click the CSD in the Project Navigator to open it in the CSD Editor.

334
11. Downloading Control Blocks B0700FE – Rev A

2. Click in the ALD toolbar or choose Tools > ALD > Start Animation from the
menu bar.
IACC connects with the CP via the selected API server and displays the current values
adjacent to the parameter names.
3. Right-click on the A or M indicator in the top corner of the block and choose either
Automatic or Manual from the pop-up menu to change the block’s operating mode.
To update either the CP or IACC for a visible parameter:
1. Right-click the parameter and choose Update from the pop-up menu to open the
Update dialog box (Figure 11-24).

Figure 11-24. ALD Update Dialog Box

If the parameter is settable/configurable, the Value field in the Update group is active.
2. Enter a value, and click CP to download the value to the CP or click CP and IACC to
update both databases.
3. Use the Download/Upload group to synchronize the value in the two databases:
 Click Upload to synchronize on Value in CP.
 Click Download to synchronize on Value in IACC.
4. Click Close to return to the ALD display.
If the IACC client is on-platform, you can select four values for display in a FoxView Trend.

335
B0700FE – Rev A 11. Downloading Control Blocks

To trend a visible parameter:

1. Right-click a parameter value and choose Trending > Trend Pen n from the pop-up
menu to assign the parameter to the pen number.

Figure 11-25. Trending a Visible Parameter

2. Use the task bar button to switch to FoxView and view the Trend.
To update or trend parameters that are not visible in the ALD:
1. Right-click a block object and choose the appropriate Properties dialog box:
 Properties to view the parameters of the selected block in the IACC database
 Block Parameters to view all parameters values of the selected block in the CP
 Compound Parameters to view the parameters of the block’s parent compound.
2. Right click any parameter in the dialog box, and choose Update from the pop-up
menu to open the Update dialog box for the parameter (Figure 11-24).
3. Right-click any parameter and choose Trending > Trend Pen n to trend the
parameter.
To update a compound:
1. Right-click one of its blocks and choose Compound Parameters from the pop-up
menu to display the Compound Parameters dialog box.
2. Right click any parameter in the dialog box, and choose Update from the pop-up
menu to open the Update dialog box for the parameter (Figure 11-24).
To end the ALD session:
 Click in the ALD toolbar or choose Tools > ALD > Stop Animation from the
menu bar.

336
11. Downloading Control Blocks B0700FE – Rev A

Viewing Block Status

Use the ListViews for IACC objects to review whether they have been validated and downloaded
to the I/A Series system. Figure 11-26 shows a Compound Block ListView opened for
compound CAS_LOOP.

Figure 11-26. Compound Blocks ListView

337
B0700FE – Rev A 11. Downloading Control Blocks

The current state of each block is listed in the final column of the ListView. Table 11-4 describes
the possible states that can be displayed in this column. Figure 11-27 shows how an object
transitions from one state to another.

Table 11-4. Validation and Download States of IACC Objects

State Attributes Description

1 Added The object has just been created, or has been
downloaded after being unassigned from its tar-
get, effectively removing the object from the
target.
2 Added, Valid The object is new, and has passed validation by
the validation agent responsible for this context.
3 Valid, Downloaded The object has been downloaded. Downloading
an object from state (2) clears the “Added” bit.
Downloading an object from the state (6) clears
the “Modified” bit.
4 Downloaded An object that has been downloaded has failed
validation by the validation agent responsible
for this context. Failing validation clears the
“Valid” bit.
5 Downloaded, Modified An object which was in state (3) has been modi-
fied. Modifying an object clears the “Valid” bit.
6 Downloaded, Modified, Valid An object which was in state (5) has passed vali-
dation by the validation agent responsible for
this context. Passing validation leaves the “mod-
ified” bit intact.
7 Downloaded, Modified Results from unassigning an object in any
downloaded state from its target. The “Modi-
fied” bit is set because the object was changed
during the unassignment operation. Similar to
state (5) except that the object has no target.
Differs from state (5) by the fact that it can still
be downloaded. When downloaded, it reverts
back to state (1) “Added”. Leaves intact other
attribute bits which may have been set, such as
“Valid.”
8 Downloaded, Deleted Results from deleting an object in any down-
loaded state (that is, in states 3-6). Object must
remain in this state until it is downloaded again
in order to construct the “Delete” commands
necessary for the download itself.
9 Deleted The object is deleted, and has no targeted state.
10 Moved Downloaded object has been moved to a differ-
ent target.

338
11. Downloading Control Blocks B0700FE – Rev A

Converting from any downloaded state to states 7, 8, or 10 leaves intact any other attribute bits,
such as “Valid.”

9 1 7
Delete Download Downloaded
Deleted Added
Modified

Download Validate
Delete

8 2 10
Downloaded Valid Downloaded
Deleted Added Modified, Moved
Download
Delete (Clears Added
bit) Download Re-assign Unassign

Not yet downloaded

Actual downloaded state

3
Valid
Modify Downloaded Validate
(Clears Valid bit) (Fails, clears
Validate Valid bit)
5 (Passes) 4
Downloaded Validate
Modified Downloaded
6
Downloaded
Modified, Valid
Modify

Figure 11-27. Transition Between Validation and Download States

Remove from CP
The Remove from CP command can be selected from the context menu of any block, including
equipment control blocks (ECBs), to delete the block from the control station but not from the
IACC database. The block’s download state is changed to Not Downloaded as if the block had
been Added to the database (number 1 in Figure 11-27), but not yet validated and downloaded.
The block connections and compound assignment are maintained, and the connected objects are
updated when changes are made to removed block. The block can then be downloaded to the
same CP or a different station.
Use the Remove CP command to do any of the following tasks:
 Rename an FBM to a new letterbug.
 Move a FOUNDATION fieldbus H1 device from one segment to another either on the
same FBM228 or on a different FBM228.
 Remove blocks whose names must be changed in the IACC database as the result of
any import.
For example, to change the name of an FBM:
1. Expand Configuration in the Network tab to display the host control station, the
FBM, its software, and ECB.

339
B0700FE – Rev A 11. Downloading Control Blocks

2. Right-click the ECB and choose Validate/Download > Remove from CP from the
pop-up menu.
3. Right-click the ECB and choose Properties from the pop-up menu to open the
ECB in the Properties dialog box.
4. Change the Name field to the new letterbug, and click Apply at the bottom of the dia-
log box.
5. Click Download at the bottom of the dialog box and follow the instructions in the
succeeding dialog boxes to validate and then download the modified ECB.

Synch Utility
It is important that the block status in the IACC database, that is, whether or not the block
has been downloaded to the CP, accurately reflect what objects are actually in the CP. The status
determines the actions that IACC takes when you select the download command. For example, if
the status in IACC does not indicate that the block has been downloaded, IACC performs a full
download, creating a new block in the CP. If the status is incorrect, that is, the block already exist
in the CP, the download causes naming conflicts and other errors.
The Synch utility verifies the download state of blocks in IACC with the blocks that are present
in the CP and displays the execution order of the compounds and blocks in the CP. The Synch
utility identifies mismatches between the two databases and allows you to synchronize on either
the CP or IACC. The Synch Utility dialog box indicates which mismatches can be rectified auto-
matically by the utility and the actions you must take to synchronize the two databases. Actions
that require user intervention are marked with an asterisk.

NOTE
The Synch utility does not deal with compound and block parameters, only with
the presence of objects in the CP and their execution order. Use the Compare to CP
function (page 343) to view and reconcile differences in parameter values.

You should use the Synch utility in the following situations:

 A configuration is imported with the IACC format. The states of the imported
compounds and blocks may have been set to Added in the IACC database, even if the
objects were previously downloaded to a CP. Refer to “IACC Import” on page 406 for
information on preserving the download status of blocks already in the IACC
database.
 You have added a block to the IACC database and the block already exist in the CP.
Use the Synch utility to correct the download status and then use the Compare to CP
function to upload the parameters from the CP to IACC, as described in “Comparing
to CP” on page 343.
 There was a communication error or other failure during download, and the block
status in IACC may not have updated correctly.

340
11. Downloading Control Blocks B0700FE – Rev A

To verify the download states in IACC with blocks in the CP:

1. Right-click either the CP or one of its compounds in the Project Navigator, and
choose Synch To CP from the pop-up menu.
IACC compares the two databases and then displays the results in a dialog box
showing the download states and execution order (Figure 11-28).

Figure 11-28. Synch Status Page

A seven-column grid shows blocks that are in the two databases for the selected
compound or CP. An X in the IACC or CP column indicates that the object is in the
IACC database or the CP, respectively. State shows the object’s status in IACC as
either Downloaded or Not Downloaded. See “Viewing Block Status” on page 337 for
additional information on state information in IACC. Note that an object can be
marked as Downloaded in IACC, but not be present in the CP.

341
B0700FE – Rev A 11. Downloading Control Blocks

The objects are displayed in their order of execution in the CP. When the Synch to CP
function is selected from a CP, the un-indented numbers in the Order column show
the order of the compounds within the CP and the indented numbers indicate the
order of blocks within their compounds. You can sort the order of the display on any
column by clicking the column title. The display order has no effect on the block exe-
cution order in the CP or in IACC.
When there is a mismatch between the two objects, or an object is in only one
database, the object is highlighted in yellow. The column on the right indicates what
must be done to synchronize the two databases.
The option buttons in the lower left corner of the page specify the point of reference
in the synchronization. When you switch between Synch to IACC and Synch to CP,
the specified action is changed to reflect the new point of reference.
Actions that require your intervention are marked with an asterisk. Actions not
marked with an asterisk are performed by the Synch utility when you click the Synch
button in the lower right.
For example, in Figure 11-28 there are two types of mismatches:
 There is a mismatch in item 10, where the execution order for the TEST5
compound is different. With Synch to IACC checked in the Options group, the
action is to move the compound above TEST6 in the CP database. This action is
performed automatically when you click Synch.
 Items 19 through 26 are only in the CP database. The asterisk in each of
the actions for these items indicate that these items cannot be automatically
synchronized. The objects must be created in IACC. Then the download status
and execution order must be updated using the Synch utility. The compound and
block parameters can be reconciled with the Compare to CP function.
2. Set the synchronization option by clicking either Synch To IACC or Synch To CP.
3. Click the Synch button to initiate the tasks to be handled by the utility.
The Synch button can only be used once in each session. The button becomes
inactive after you execute the function.
4. Click Print to copy the page for a list of actions you must perform.
5. Exit the utility, make the required changes to the IACC database, and download the
CP or compound.
6. Start the Synch utility for the object and run synchronization again as required.

342
11. Downloading Control Blocks B0700FE – Rev A

Comparing to CP
Use the Compare to CP function to identify differences between the objects as they exist in the
CP and in the IACC database, and to ensure that parameter values in the IACC database are
identical to those in the CP.
With this function, IACC compares the work file (described on page 305) in the CP’s host work-
station with the IACC database. The Comparison Utility dialog box includes two tabbed pages:
 Comparison Utility Identifies differences between parameters in the two databases. You
can then select objects in the IACC database to be updated with val-
ues from the work file. The objects being compared can be all com-
pounds and blocks in the processor, a single compound and its blocks,
or an individual block.
 Bulk Upload Identifies differences in parameter values between the work file and
the IACC database, and allows you to update selected parameters in
the IACC database with values from the CP database.

Upload and Compare

The work file may or may not contain the values currently being used by the CP. For example, an
operator may have changed a setpoint since the last time the CP database was uploaded to the
work file. The Compare to CP function can be combined with an upload from the CP database
to ensure that the work file contains the current CP values. However, depending on the number
of objects being compared, the size of the CP database and the loading on the CP, the upload and
compare option may take hours, during which time IACC would not be available. For example,
uploading from a CP with numerous compounds may be unnecessarily time-consuming, espe-
cially if the CP values have been uploaded to the work file recently. On the other hand, the time
required to upload and compare a single CSD is minimal.

Comparing Parameters
To compare the IACC database to the control processor database:
1. Do one of the following to initiate the comparison:
 Right-click the object in the Project Navigator, and choose Compare To CP from
the pop-up menu.
 Right-click the object in the Project Navigator, and choose Upload and Com-
pare To CP from the pop-up menu.
An IACC warns of possible delays if you upload first (Figure 11-29).

Figure 11-29. Upload and Compare to CP Warning

 Click Yes to continue, or click No to stop the function and choose Compare
to CP only.

343
B0700FE – Rev A 11. Downloading Control Blocks

IACC compares the two databases and then displays the results in the Comparison
Utility dialog box (Figure 11-30).

Figure 11-30. Comparison Utility Dialog Box

The Comparison Tree on the left shows compounds and blocks and their locations as
one of the following:
 DB and CP when the object exists both in the IACC database and on the CP
 CP ONLY when the object exists only on the CP
 DB ONLY when the object exists only in the IACC database.
The procedure for reconciling the two databases depends on object location.

344
11. Downloading Control Blocks B0700FE – Rev A

DB and CP
To reconcile objects that exists both in the IACC database and on the CP:
1. Select the object in the location tree to display the parameter values in the pane to the
right of the tree.
Figure 11-30 compares versions of the block AIN in the compound PT7771 in the
CP and the IACC databases. Two parameters with differences are marked with a red
not-equal symbol ( ) on the left.
2. Do one of the following to resolve the differences:
 Click Update IACC to overwrite IACC parameters with those in the CP database.
 Click the Bulk Upload tab to update selected parameters in IACC with parame-
ters in the CP, and then exit the utility and download the object to the CP
to update the CP version with the updated values in the IACC database.
 Click Close to exit the utility and download the object to update the CP version
with the IACC values.

CP ONLY
You cannot upload blocks from the CP that do not already exist in IACC.
To reconcile IACC with the CP database for objects that are CP ONLY:
1. Click Close to exit the Compare utility.
2. Create the objects and make the appropriate compound and CP assignments.
Do not set any parameters; these can be uploaded from the object in the CP.
3. Use the Synch to CP to synchronize the object status and execution order in IACC
with the CP database.
The IACC block status must be changed from Added to Downloaded before you can
upload parameters from the CP.
4. Right-click the CP in the Project Navigator and choose Compare to CP from the
pop-up menu to return to the Comparison Utility dialog box.
The objects should now be listed as CP and DB.
5. Select the object and click Update IACC to copy the parameter values from the CP to
the IACC database.

DB ONLY
To reconcile the CP with IACC for a DB ONLY object:
1. Click Close to exit the Compare utility.
2. Make sure the object has the appropriate compound and CP assignments.
3. Use the Synch utility (page 340) to ensure that the object status is Not Downloaded.
The IACC block status must be correct for a download to create the block in the CP.
4. Right-click the object in the Project Navigator and choose Validate/Download >
Download to initiate the download to the CP as described in “Downloading Com-
pounds and Blocks” on page 312).

345
B0700FE – Rev A 11. Downloading Control Blocks

Bulk Upload
When you update the IACC database using the Comparison Utility tab, all parameters of the
selected object are updated with values from the CP database. The Bulk Upload tab allows you to
update selected parameters of one or more objects in the IACC database with current values from
a CP database.
To run Bulk Upload:
1. Right-click the CP, one of its compounds, or a specific block in the Project Navigator,
and choose Compare To CP from the pop-up menu.
IACC compares the two databases and then displays the results in the Comparison
Utility dialog box (Figure 11-30).
2. Click the Bulk Upload tab to display the page identifying differences in parameter
values.
Figure 11-31 shows the Bulk Upload page for a compound (PT7771). This page is
only displayed when the compounds and blocks are in synch, that is, when they exist
in both databases, the execution orders match, and the IACC download state does not
conflict with the CP database. IACC prompts you to select the Synchronization
Utility if the databases are not in synch.

Figure 11-31. Bulk Upload Page

The grid identifies the parameters by compound or compound and block name,
and parameter name and type. The Current value is the parameter value in the IACC
database, while New Value is the value in the CP database that can be uploaded to
update IACC. The column to the right of the values indicates how the value was set in
IACC:
 F for formula
 Pfor propagation from another parameter
 I for inheritance from the parameter in a parent object.
M in the Mod column indicates that the value has been modified in IACC, but not yet
downloaded to the CP.

346
11. Downloading Control Blocks B0700FE – Rev A

3. Select individual parameters for upload by clicking anywhere in their rows, or click
the Select All button at the bottom of the page.
4. Click the Upload button to update the selected parameters in the IACC database with
values from the CP database.

Initialize CP
It may be desirable at times to use the Initialize command to clear the control processor and start
from scratch.

! CAUTION
Consider the results of this action on the process application.

Initialize performs three actions on the host workstation for the selected CP:
 Removes all compound and block information from the work files for the
selected station
 Clears the Checkpoint file for the station
 Removes all entries about the CP from the Compound Summary Access (CSA)
application.
Thus, the database in the host for the selected CP is emptied.
The CP station must be rebooted after an initialize is performed for the CP database to be
emptied also. Nothing is touched in the CP until the reboot occurs.
The objects in the IACC database are kept exactly as they were except the state of previously
downloaded objects are reset to the state of Added (see Table 11-4 for a description of download
states). Therefore, following an Initialize, the CP database can be downloaded from whatever
object you choose.
To download an entire CP database:
 Select the Download function from the CP object in the Project Navigator.

NOTE
Methods to initialize the station outside of IACC are not sufficient and may be
harmful. Make sure the Initialize commands to the CP are done via IACC.

347
B0700FE – Rev A 11. Downloading Control Blocks

To initialize a control processor:

1. Right-click the control processor in Project Navigator, and choose Initialize from
the pop-up menu.
A dialog box warns you that the action requires restarting the CP (Figure 11-32).

Figure 11-32. Initialize Information Dialog Box

2. Click Yes to proceed or No to back out.

The Control Station Download tab in the Output window displays status and error
messages from the process.
3. Reboot the CP when the Initialize procedure is complete.
4. Download part or all of the existing control configuration, or create and download a
new configuration.

348
12. Security
This chapter discusses the concepts and procedures required to manage security preferences. This
includes configuring security with the User and Group Editors, enabling system-wide security,
and using security audit trails.
The security features of IACC enable you to control access to the various sections of the software,
and thus to the elements of your process.
Security in IACC can be managed on a number of different levels:
 Access to IACC is restricted to users with passwords
 Users may be assigned to various groups with permissions to different aspects of the
process (“Configuring a Group” on page 356)
 Security may be turned on or off for IACC system-wide (“Enabling Security” on
page 359)
 ListViews allow you to view and sort security information easily (“Security-Related
ListViews” on page 360)
 Security audit trails can track each change made to your security configuration (“Secu-
rity Audit Trail” on page 360).
Each person working in the IACC application can be assigned a user name and a password
through the User Editor (see “Configuring a User” on page 353). This assignment is made by a
member of the IACC Administrator group or by a member of another group with IACC Admin
permissions. Whether or not IACC security is enabled system-wide, only personnel with valid
user names are able to access the system. If the user is assigned a password, that password is
required in order to enter the system at all times. Setting up users with passwords is the first line of
security. Further, users may be assigned to one or more groups (“Configuring a Group” on
page 356) which serve to deny or grant access to the various editors, functions, and object types
within IACC.
IACC comes with one predefined user: Administrator. Initially there is no password set, so that
IACC may be accessed to configure security for the first time. Administrator is not a member of
any group by default. You may want to make Administrator a member of the IACC Administra-
tor Group (“Configuring a Group” on page 356) or you may wish to configure your own admin-
istrator group with more restrictions. Only one person may be logged onto IACC as
Administrator at any given time.
A group is a collection of IACC users with a certain set of permissions to various aspects of IACC,
and thus to different elements of the process. You can use groups to control the IACC object
types, editors, and functions to which each user has access. You can use as many or as few groups
as you wish to control personnel access to your system.

349
B0700FE – Rev A 12. Security

IACC comes with one predefined group, the IACC Administrator group. Initially this group has
no members, and is configured to give any future members full permissions to all parts of IACC.
You may want to make Administrator a member of this group.

! WARNING
If you make Administrator a member of any single group other than the IACC
Administrator group, you must make sure that the group or some other users have
the IACC Admin permission. If no user is assigned to a group with the IACC
Admin permission, you lose the ability to perform vital security configurations such
as modifying group memberships, IACC system-wide security settings, and IACC
security permissions.

You can make any number of users members of the IACC Administrator group, but keep in mind
that they all have administrative capabilities and full access to IACC. More than one member of
this group may be logged on at the same time.
A user can be a member of more than one group. A permission granted to a user as a member of
one group is not affected by membership in another group that does not have that permission.

Configuring Security
Initial Security Configuration
Immediately after loading IACC, Administrator is the only user defined to access the software
initially. System-wide security is disabled by default. It is thus highly recommended that the
IACC Administrator perform the following security configurations using the defined
Administrator identity:
 Make the Administrator a member of the IACC Administrator group as long as that
person is to have full permissions throughout IACC (“Configuring a Group” on
page 356).
 Set a new password for the user Administrator (“Configuring a User” on page 353).
Until this point Administrator has no password set, and anyone can access your
software using the Administrator identity.
 If more than one individual is to have administrative permissions, create and add the
users to the IACC Administrator group.
 Enable system-wide security (“Enabling Security” on page 359).
At this point, the administrator may also want to define a user with a password for each person
who needs access to IACC (“Configuring a User” on page 353). However, if users are defined at
this time without assigning them to groups, they have system-wide access to IACC, as their access
has not yet been limited by assigning them to one or more groups.

! CAUTION
A defined user who has not yet been assigned to any group has full access to any
part of IACC.

350
12. Security B0700FE – Rev A

Limiting Access
In IACC, users start as super-users with system-wide access. A user’s access only becomes limited
when the user becomes a member of one or more groups as permission in IACC is denied, not
granted. If permission or access has not been explicitly denied to a user or a group of users, then
that permission is granted to them. A user belonging to more than one group is granted
permission as long as at least one of the groups has that access.
If a user belongs to many groups, looking at the ListView for that user may be the easiest way of
telling what permissions that user has (“Security-Related ListViews” on page 360).

User Editor
Figure 12-1 shows the IACC window with a view of the User Editor on the right. Configurable
security objects are available in the System tab of the Project Navigator.

Figure 12-1. IACC User Editor

351
B0700FE – Rev A 12. Security

The window includes the following components:

User Name The name being configured in the User Editor. The user name is not case-
sensitive.
See“Authorizing User Access” on page 324 if the application is linked to
FoxCTS for compliance tracking.

Full Name Proper name of the user currently displayed in the User Editor.

Description Optional additional descriptive information about the user.

Password Password for the user currently displayed in the User Editor.
Each character of the password is displayed as an asterisk in this field. The
password is case-sensitive.

Groups Provides controls for assigning a user to groups. (See “Configuring a

Group” on page 356.)

Menus and Toolbars

The User Editor utilizes a standard menu set derived from the generic IACC Editor Template.
Right-clicking the mouse in any of the four text fields at the top of the User Editor window dis-
plays a pop-up menu with standard Windows editing features such as Copy and Paste.

Configuring Users
Use the System tab of the Project Navigator to create, name, and delete IACC users.

Adding and Naming a User

To add and name a user:
1. Expand System > Security > Users in the Project Navigator.
2. Right-click Users and choose New User from the pop-up menu.
A new user object with a default name such as User1 is placed under the Users branch.
3. Right-click the default name in the Project Navigator and choose Rename from the
pop-up menu.
The user name becomes outlined in black and highlighted, indicating that it may be
changed.
4. Enter the new name and click outside the user name box to conclude editing.

352
12. Security B0700FE – Rev A

Removing a User
To delete a user:
1. Right-click on the user name in the Project Navigator and choose Delete from the
pop-up menu.
The Delete Request dialog box (Figure 12-2) displays the other IACC objects affected
by the delete before you confirm the action.

Figure 12-2. Delete Request Dialog Box

2. Review the affected objects, and click OK.

Configuring a User
Once the user object is created, you can assign a password to the user and assign the user to one or
more groups.
To configure a user:
1. Double-click on the user name in the Project Navigator to open the User Editor
(Figure 12-1).
2. Use the Full Name and Description fields to identify the individual and his or her
role in the organization.
 To change the name, enter a new name in the User Name field
 Set a password if there is a single asterisk in the Password field.
This indicates that no password is set.

NOTE
Passwords are case-sensitive; user names are not.

3. Enter the password in the Password field.

Asterisks appear in the field as you enter the characters of the password.

353
B0700FE – Rev A 12. Security

4. Press the Enter key.

The Confirm New Password dialog box prompts you to re-enter the password
(Figure 12-3).

Figure 12-3. Confirm New Password Dialog Box

5. Repeat the entry and click OK.

If the two entries match, the new password is set. You can change the password later
using the same technique.
6. Assign the user to a group by selecting a group in the Not member of box and click-
ing Add.
You can assign the user to one or more groups. To remove a user from a group:
 Select the group name in the Member of box and click Remove.

Group Editor
Figure 12-4 shows the IACC main window with a view of the Group Editor. The editor has been
opened for a group in the Project Navigator under System > Security > Groups.

Figure 12-4. IACC Group Editor

354
12. Security B0700FE – Rev A

The Group Editor includes two tabs:

Members Provides controls for identifying the group and assigning users to it
(Figure 12-4).

IACC Permissions Allows you to assign system-wide and object-specific permission to the
group (Figure 12-5).

Figure 12-5. IACC Permissions Tab in the Group Editor

Adding and Naming a Group

Use the System tab of the Project Navigator to create, name, and delete groups.
To add and name a group:
1. Expand System > Security in the Project Navigator.
2. Right-click Groups and choose New Group from the pop-up menu.
A new user object with a default name such as Group1 is placed under the Groups
branch.
3. Right-click on the group name in the Project Navigator and choose Rename from the
pop-up menu.
The user name becomes outlined in black and highlighted, indicating that it may be
changed.
4. Enter the new name and click outside the group name box to conclude editing.

355
B0700FE – Rev A 12. Security

Deleting a Group
To delete a group:
1. Right-click on the user name in the Project Navigator and choose Delete from the
pop-up menu.
The Delete Request dialog box (Figure 12-2) displays the other IACC objects affected
by the delete before you confirm the action.
2. Click OK.

Configuring a Group
Once the user object is created, you can assign users to it and configure permissions to the group.
To configure a group:
1. Double-click on the group name in the Project Navigator to open the Group Editor
(Figure 12-4).
2. Use the optional Description field to identify the group’s purpose and its uses of
IACC.
At this point, you can also change the name of the group by modifying the entry in
the Name field.
3. Assign the users to the group by selecting names in the Not member of box and click
Add.
To remove a user from the group:
 Select the user in the Members box and click Remove.
4. Click the IACC Permissions tab and set permissions for the group using procedures
in the next two sections.

Permitting Access to System-Wide Functions

The check boxes at the top of the IACC Permissions tab (Figure 12-5) allow you to grant or deny
access to individual editors and to perform these other system-wide functions:
 IACC Admin - enables group members to perform system-wide administrative
functions
 Backup Database - permits the group member to create a complete backup of the
IACC database.
Restoring the database is accomplished outside the IACC application using the
Database Administrator utility described in Chapter 15 “Managing IACC
Databases”.
 Run Reports - allows a user to create IACC reports
 Import - permits a user to import into IACC
 Export - enables a group member to export from IACC.
Initially the group is permitted access to each function as indicated by the check marks in the box
to the left of each function.
If permission is denied to a group for one of the above editors, a member of that group cannot
access that editor or function unless the user is also a member of a group that has the permission.
Picks leading to that editor or function are grayed out in the Project Navigator for that user.

356
12. Security B0700FE – Rev A

To set these IACC editor and function permissions:

1. Click the check box for an IACC editor or function to clear the box and deny
permission.
2. Click again to check any box and grant permission.
Changes to these permissions are effective immediately.

Assigning IACC Object-Type Permissions

The tree view in the center of the tab is used to grant or deny access permission to write to,
validate, and download each IACC configurable object type, as described in Table 12-1. These
actions can only be controlled at the type level; permissions cannot be set for actions on individual
object instances.

Table 12-1. Object-Type Actions

Action Description
write (w) Permits a user to make configuration changes to the IACC object.
validate (v) Allows a user to perform the validate function for an IACC object.
download (d) Enables a user to download the object. If this action is enabled for a CP,
the user may download IACC objects to the CP.

The IACC configurable object types for which permissions for these actions can be controlled are
listed in a hierarchical tree format. You can view the hierarchy using the same expand and collapse
functions used in the Project Navigator.
To the right of the branches are three columns which display whether each of the three actions
described in Table 12-1 is granted or denied to the group for each object. Table 12-2 describes the
symbols which can appear in these columns.

357
B0700FE – Rev A 12. Security

Table 12-2. Symbols Appearing in Object-Type Action Configuration

Symbol Colors Description

Green The action has been explicitly granted to the group for the object type.

Red The action has been explicitly denied to the group for the object type.

Grey The action has been implicitly granted to the group for this child
object type through inheriting the permission from its parent. This is
also the default setting for all actions for all object types.
Grey The action has been implicitly denied to the group for this child object
type through inheriting the permission from its parent.
Green on grey The action has been explicitly granted to the group for the object type,
background and one or more children of this object type is denied this action.
Red on grey The action has been explicitly denied to the group for the object type,
background and one or more children of this object type is granted this action.
Grey on grey The action has been granted to the group for the object type because it
background was granted for a parent object, and the action has been denied for at
least one child of this object type.
Grey on grey The group has been denied the action for this object type because it
background has been explicitly denied for a parent object type. However, permis-
sion has been granted explicitly for at least one child of this object
type.

The default permissions for these actions for all IACC configurable object types are granted. Per-
missions are automatically passed onto each child object type from its parent. Every child object
type has the same permissions for these actions as does its parent, unless it is explicitly configured
otherwise by an administrator. These inherited permissions can be overridden on an individual
basis.
The two option buttons in the Filter field at the bottom of the tab provide two different ways of
viewing the object type hierarchy:

All Nodes Displays all nodes of the IACC Configurable Object Type hierarchy
regardless of permissions.

Explicit Nodes Displays only those branches of the hierarchy that have had permissions
Only explicitly set. Branches with only inherited permissions are not shown.
To assign IACC object-type permissions for the write, validate, and download actions for a group:
1. Locate the branch of the object type for which you wish to set action permissions in
the hierarchy by using standard expansion and collapse techniques on the tree.
2. Right-click on the row and column intersection which corresponds to the object type
and its action that you wish to configure to display a pop-up menu (Figure 12-5).
3. Choose the symbol which corresponds to the permission you wish to grant for this
action and object type (see Table 12-2).
The change occurs immediately.

358
12. Security B0700FE – Rev A

Enabling Security
In order for the security preferences you have chosen during configuration to take effect, IACC
security must be enabled at the system-wide level. A user with the IACC Admin permission may
enable or disable system-wide security at any time. However, be aware that any time security is
disabled on the system level, all users are able to access any part of IACC.

! CAUTION
Whenever IACC system-wide security is disabled, all defined users have access to all
parts of IACC.

In order to enable or disable security system-wide:

1. Choose Tools > Options from the menu bar to open the IACC Options dialog box
(Figure 12-6).

Figure 12-6. IACC Options Dialog Box

2. Click the Enable security.

3. Check box in the Security Group and click Apply.
4. Set other IACC options and click OK.

359
B0700FE – Rev A 12. Security

Security-Related ListViews
The ListView Editor is a tool that finds and displays objects associated with a given IACC object.
When the ListView Editor is invoked for a particular IACC object, it searches the IACC database
for objects linked to it in a specified fashion, and displays the results in the Editor window.
There are up to three ListViews associated with each IACC user instance and up to five ListViews
associated with each IACC group instance. These ListViews are accessed by right-clicking the user
or group instance branch in the Project Navigator and selecting ListViews from the resulting
pop-up menu. A menu of the available ListViews for that object appears. Table 12-3 lists and
describes these security ListViews.

Table 12-3. User and Group ListViews

ListView
User ListView
Group Members
Group Type Permissions
Group System Permissions
Security System Permissions
Security Type Permissions
Description
Invoked from any user instance branch, it displays the name and
description of each group to which the user belongs.
Invoked from any group instance branch, it displays the name and
description of each user belonging to the group.
Invoked from any group instance branch, it displays all object-type
permissions explicitly granted or denied to the group. For each
such permission, this ListView also indicates whether the write,
validate, and download actions are enabled or disabled.
Invoked from any group instance branch, it displays all system
permissions and whether each is enabled or disabled for the group.
Invoked from either a user or a group instance branch (but only
when system-wide security is enabled), it indicates whether each
system-wide security permission is enabled or disabled for each
created group.
Invoked from either a user or a group instance branch
(but only when system-wide security is enabled).

ListViews offer the most convenient method for observing at a glance the security assignments
and permissions associated with the users and groups.

Security Audit Trail

Changes to the IACC security configuration are recorded in an audit trail that is stored in the
IACC database.
To enable the audit trail:
1. Choose Tools > Options from the menu bar to open the IACC Options dialog box.

360
12. Security B0700FE – Rev A

2. Click one of the option buttons in Security Audit Trail Level group:
 Partial for:
 Any modifications to system-wide security settings
 The creation of a new user or group instance
 The renaming of a user or group instance
 The deletion of a user or group instance
 All logins/logouts from IACC.
 Full for:
 The addition of a user to a group
 The removal of a user from a group
 All modifications to group permissions.
To view the audit trail:
1. Expand System > Audit Trails > Security Audit Trail in the Project Naviga-
tor.
2. Right-click the Security Audit Trail branch and chose ListViews > Audit
Trail (Figure 12-7).

Figure 12-7. IACC Options Dialog Box and Audit Trail ListView

The security audit trail is updated immediately upon security configuration changes. Table 12-4
lists and describes the column headings in the Security Audit Trail ListView.

361
B0700FE – Rev A 12. Security

Table 12-4. Security Audit Trail Columns

Column Description
Date Indicates the date and time at which the security configuration change was made.
User Identifies the authenticated user that made the security configuration change.
System Indicates the workstation from which the changes were made.
Audit Info Provides a description of the action.

To clear records from the audit trail:

 Right-click in the ListView and choose Purge from the pop-up menu.

362
13. Printing and Reports
This chapter describes printing and reports for the IACC application and the setup of Report
Templates and sheets.

Printing
Printing in IACC allows you to create a hard copy of the attributes of one or more IACC objects.
You can print either of the following:
 A standardized report for one or more objects
 The contents of the editor currently open in the Editor window.
IACC uses standard Windows print commands and dialog boxes for page setup, printer selections
and other print related functions. Refer to IACC Help if you are not familiar with the Windows
commands. Details presented by the dialog boxes may vary from the descriptions in this docu-
ment and IACC Help depending on the printer drivers configured with your system.

Printing an Object Report

For most objects, reports provide a table of the object parameters and their associated values
(Figure 13-1).

Figure 13-1. Print Preview of a Tabular Report

363
B0700FE – Rev A 13. Printing and Reports

Reports for CSDs and graphical representations replicate the display in the Editor window
(Figure 13-2).

Figure 13-2. Graphical Report Preview

You can print reports for individual objects or set up Report Templates for printing multiple
objects.
To print a tabular report for a single object using the default setup:
1. Click the object in the Project Navigator.
2. Choose File > Print from the menu bar.
A Print dialog box appears allowing you to change default settings.
3. Click OK in the Print dialog box.

364
13. Printing and Reports B0700FE – Rev A

Printing Editor Contents

When you select the Print command from an open editor, IACC prints out the contents of the
Editor window. Depending on the size of the window, this may require more than one page.

NOTE
You must select the Editor window and then immediately select the Print command
to print the contents of the window. The Print command prints the most recently
selected item, which can be either an object in the Project Navigator or in the
Editor window.

As shown in Figure 13-1, IACC sets a background behind the contents of the Editor window
using a Sheet Template. A default Sheet Template is assigned to every printable object; however,
you can change a Sheet Template for the object.
To print the contents of the Editor window:
1. Click the Editor tab to make sure the editor is selected.
2. Choose File > Print from the menu bar.
A Print dialog box appears allowing you to change default settings.
3. Click OK in the Print dialog box.

Printing to a File
You can send a print job to a file so you can print at a later time on a printer with a higher resolu-
tion than is available on your desktop printer. When you print to a file, you must first select the
printer that ultimately prints the file. The file is saved in the appropriate printer language.
In addition to document data, a printer file contains information, such as line breaks, page breaks,
and font spacing necessary to reproduce the computer’s output to your printer. The computer
that prints the printer file need not have IACC installed.

Print Preview Mode

You can preview how your document appears when printed to check the document for potential
problems and determine if you want to edit the printing properties.
To access the Print Preview mode:
1. Click the Editor tab or the object in the Project Navigator that you wish to preview.
2. Choose File > Print Preview from the menu bar.
The print preview appears in place of the entire IACC display. A row of buttons, shown in
Figure 13-3, appears above the preview section to help you move around and focus on a particular
part of the drawing.

Figure 13-3. Print Preview Buttons

365
B0700FE – Rev A 13. Printing and Reports

Sheet Templates
A Sheet Template is a customized design of a sheet of paper, providing a graphical background for
reports. You can create and edit Sheet Templates using the Sheet Editor (see “Editing the
Sheet Template” on page 367). Sheet Templates can be customized by specifying the paper size
and the items printed, including borders, company logo, date, time, and user name.

Basic Sheet Template Specifications

A Sheet Template must:
 Have its margins set large enough to display the report data, and
 Be equal in size to one of the types of paper available for your printer (that is, have an
equivalent print specification).
Figure 13-1 and Figure 13-2 show the bottom-right corner portion of one of the IACC standard
templates named Sheet Letter – Landscape.

Default Sheet Templates

IACC is shipped with the following Sheet Templates that you can copy and customize:
 Sheet Letter – Landscape
 Sheet Letter – Portrait
 Sheet A4 – Landscape
 Sheet A4 – Portrait.

Sheet Template Macros

A macro is a text string that is replaced by some predefined text or graphic when the templates are
used to print an object from IACC. Macros are typed within brackets on a Sheet Template, and
then are evaluated by IACC when that sheet is used to print. For example, a user logged on as
JDoe may type the macro [USERNAME] onto a Sheet Template. When that template is used to
print an object, JDoe appears in place of the [USERNAME] macro on the printed page. See
“Inserting a Macro” on page 369 for instructions and for a list of supported macros.

Creating a Sheet Template

To create and name a Sheet Template:
1. Expand System > Report Manager in the Project Navigator.
2. Right-click on the Sheet Templates branch and choose New Sheet Template
from the pop-up menu.
A new Sheet Template appears at the bottom of the list of Sheet Templates in the
Project Navigator with a default name such as Sheet Template1.
3. Right-click the new Sheet Template and choose Rename from the pop-up menu.
A rectangle around the template indicates that the name is editable.
4. Type the new name and click anywhere outside the rectangle.

366
13. Printing and Reports B0700FE – Rev A

To delete a Sheet Template:

1. Right-click the Sheet Template and choose Delete from the pop-up menu.
The Delete Request dialog box lists other objects affected by the delete.
2. Click OK.

Editing the Sheet Template

To access the Sheet Editor:
1. Right-click on the Sheet Template branch and choose Editors > Sheet Editor
from the pop-up menu.
The Sheet Editor is displayed in the Editor window and graphics-oriented toolbars are
added to the IACC windows (Figure 13-4).

Figure 13-4. Sheet Editor

2. Use the drawing tools to add lines, bitmaps, and text to the sheet background.

367
B0700FE – Rev A 13. Printing and Reports

To set up the basic page for the Sheet Template:

1. Choose File > Page Setup from the menu bar to open the Page Setup dialog box
(Figure 13-5).

Figure 13-5. Page Setup Dialog Box

2. Use the pull-down lists in the Paper group to specify the paper size and source.
3. Click either Portrait or Landscape for the page orientation (Figure 13-6).

Figure 13-6. Setting the Paper Orientation for the Sheet Template

4. Adjust the four margins using the controls in the Margins (inches) group.
An image at the top of the Page Setup dialog box displays how the report data appears
on the Sheet Template with the specified margins and orientation.
5. Click OK to save and close the Page Setup dialog box.

368
13. Printing and Reports B0700FE – Rev A

Inserting a Macro
To add a macro to a Sheet Template:
1. Click the Text icon in the toolbar and click the location on the Sheet Template where
you wish the macro to appear.
A text box with grab handles is inserted onto the sheet.
2. Right-click anywhere within the text box and select Properties from the pop-up
menu to open the Component Properties dialog box.
3. Click the Text tab and enter one of the supported macros listed in Table 13-1.

Table 13-1. Sheet Template Macros

Macro Text Description

[USERNAME] Prints the user name of the user currently logged
on.
[MMDDYY] Prints the current date.
[PAGE] Prints the page number.
[RPTPL.<Param Example>] <Param Example> is replaced with a parameter
name maintained by the associated Report Tem-
plate. This macro is only used for Sheet Templates
that have an associated Report Template.
[SHEET.<Param Example>] <Param Example> is replaced with a parameter
name maintained by the Sheet Template on which
it is placed.
[.<Param Example>] <Param Example> is replaced with a parameter
name maintained by the object being printed.

The macro text, including brackets, appears in the text box. When the Sheet Template
is used to print an IACC object, the macro text is replaced with the predefined vari-
able data.
To remove a macro from a Sheet Template:
 Right-click the text box and choose Cut from the pop-up menu.

369
B0700FE – Rev A 13. Printing and Reports

Reports
Reports are generated whenever a request is given to print one or more IACC objects. Reports are
constructed using the following:
 Report data — All data associated with the object or objects involved, including
parameters and parameter values, object classes, types of connections permitted for
the object, and so forth
 Report Template — a template used to find one or more objects in the IACC database
which fit certain criteria, and to generate a standardized report for each of them using
a Sheet Template and a print specification
 Sheet Template — a graphical background onto which the report is set
 Print specification — an object which records configuration information for printing,
such as page size and orientation.
The Sheet Template and print specification are both set in the Page Setup dialog box. Reports are
invoked differently depending on whether you request a report for a single object or for more
than one object.

Reports for One Object

When you initiate a print request for an object in the Project Navigator, IACC automatically
builds a report for you. When the report is complete, IACC displays the Print dialog box, as is
standard in many Windows applications.
You can assign a specific Sheet Template to each object in the Project Navigator. IACC automati-
cally assigns a corresponding print specification for the object. You do not need to configure or
access a Report Template when printing a report for a single object.

Reports for More than One Object

Report Templates are used to build reports for multiple objects derived from the IACC database.
The scope of Report Templates, by default, is the set of all definitions and instances of real-world
objects. However, this scope can be limited to a specific object or objects. When you configure a
Report Template, you provide it with a number of criteria. The Report Template builds reports
for only those objects that fit with these criteria, from the objects contained in the scope of this
template.
Each Report Template is assigned a Sheet Template and print specification which are used for all
reports generated from that template. The Report Template overrides any other Sheet Templates
and print specifications assigned to the objects being printed.

370
13. Printing and Reports B0700FE – Rev A

Report Templates
Report Templates are objects designed to create a set of standardized reports for a set of
IACC objects which fit certain established criteria. Each Report Template is assigned a single
Sheet Template and print specification, which are applied to all reports generated by that Report
Template. Report Templates create reports only for objects assigned to their object list.
Report Templates use scope nodes and filters to derive this object list:

Scope Nodes When a scope node is added to a Report Template, all the objects under
the scope node in the System Hierarchy are added to the Report Tem-
plate’s object list, before the template uses its filters to narrow the list.
Unless otherwise specified, a Report Template’s object list includes all
user-created object instances in IACC.
You can drag individual objects into a Report Template. Each of these
objects then becomes a scope node for the Report Template.

Filters Report Templates contain filters that narrow the object list to include only
objects that match the criteria you specify. Each Report Template has two
types of filters:
 Inherent filters that are integral parts of the Report Template and
cannot be edited
 Filter expressions created in the Report Template Editor. Objects
that meet the criteria are included in the Report Template’s Print-
able Object Collection.

Report Template Classes

There are five classes of Report Templates, each associated with an IACC editor. Only those
objects that are editable in the editor associated with a given report can appear in that report:
 Rpt CSD, which prints the graphics-based representation of CSDs, similar to the
CSD Editor display. These Report Templates have inherent filters which allow them
to add only CSDs to their object lists.
 Rpt Definition, which prints spreadsheets similar to the Definition Editor display.
These Report Templates have inherent filters which allow them to add all definitions
and instances for real-world objects to their object lists.
 Rpt ListView, which prints spreadsheets similar to the ListView Editor display.
 Rpt ST Template, which prints the graphics-based representation of ST Templates,
similar to the ST Template Editor display. These Report Templates have inherent fil-
ters which allow them to add only ST Templates to their object lists.
 Rpt TagList, which prints the selected TagList in spreadsheet format similar to that
used in the TagList Editor.

371
B0700FE – Rev A 13. Printing and Reports

For each class, there are two types of Report Templates:

 Report Template definitions
 Report Template instances.
These objects are illustrated in the Figure 13-7.

Template Class

Default Template

Derived Template

Template Instance
Scope Node

Figure 13-7. Report Template Definitions and Report Template Instances

NOTE
The Configurable Object Types Scope Node is assigned to each Report Template by
default. If you add your own scope node to a Report Template, the Configurable
Object Types Scope Node is not assigned to your Report Template.

372
13. Printing and Reports B0700FE – Rev A

Report Template Definitions

Report Template definitions retain the basic filter expressions for graphical or tabular Report
Templates. You can edit their filter expressions with the Report Template Editor. Report Template
definitions, which can be printed as needed, have an object list of all definitions and instances for
real-world objects in IACC.

Report Template Instances

When you print Report Template definitions, you can save the object list generated for them.
When you save this list, a Report Template instance is created in a branch under the Report
Template definition to hold this list and the filter expression under which it was created.
Report Template instances are created from their parent Report Template definition. They retain
their parent’s filter expression, but unlike their parent, they can hold specific scope nodes in their
object list. Instances are assigned default names comprised of the parent’s name and followed by a
unique number. They cannot override their parent’s filter expression, and therefore, cannot be
edited with the Report Template Editor. You can add scope nodes to them and print them as
needed.
Report Template instances are updated as the IACC database is updated.

Creating a Report Template

To create and name a Report Template:
1. Expand System > Report Manager > Report Templates in the Project Navigator
to display the Report Template classes.
2. Right-click on the template class you want to use and choose New Report Template
from the pop-up menu.
The new template is listed under the template class with a default name consisting of
the class name and a number such as Rpt Definition1 in Figure 13-8.
3. Right-click the new object and choose Rename from the pop-up menu.
A rectangle around the name indicates that it is editable.
4. Type the new name and click outside the rectangle.

373
B0700FE – Rev A 13. Printing and Reports

Adding Scope Nodes

You can add scope nodes to a Report Template if you want a Report Template to have an object
list containing specific objects. Adding a scope node to a Report Template creates a Report
Template instance with an object list containing only the assigned scope node. Add additional
scope nodes to a Report Template instance to increase the size of its object list for each scope
node.
To add the first scope node to a Report Template:
1. Expand System > Report Manager > Report Templates and the template class to
display the template you want to use.
2. Select the object you want to use as a scope node and drag it to the Report Template.
3. Drop the object onto the template definition in the Project Navigator.
If the association is valid, the cursor changes to .
The Report Template Object List dialog box appears (Figure 13-8). In Figure 13-8,
the AIN definition has just been dragged to the IA Blocks Full Detail1 Report
Template to add a second scope node to the template. The first scope node is the
AOUT block definition added earlier, as shown in the Project Navigator.
The items in the Printable Objects List are all derived from either the AIN definition
or the AOUT definition.

Figure 13-8. Report Template Object List Opened for a Report Template Instance

374
13. Printing and Reports B0700FE – Rev A

4. Click Save and then click Close.

If the Report Template is a definition, a Report Template instance is created with one
scope node, the object you originally selected. The instance has a default name con-
sisting of the parent name followed by a unique number. The object is listed under the
template instance. The Project Navigator in Figure 13-8 shows the AOUT block
definition as the first scope node under IA Blocks Full Detail1.
To add other scope nodes:
 Drag the object to the instance.
Figure 13-8 shows a Report Template Object List dialog box after a second scope
node (the AIN block definition) has been added to a Report Template instance.

Adding a Plant Area Scope Node

To select a Plant Area as a scope node:
1. Expand Report Templates so that the target template definition of instance is visi-
ble in the Project Navigator.
2. Click the Plant tab and expand the tree to locate the Plant Area object you want to
use as a scope node.
3. Drag the object to the System tab to return to the Report Templates branch.
Drop the object on the target Report Template definition or instance.

Removing a Scope Node

To remove a scope node from a Report Template:
1. Select the scope node.
2. Click the Cut icon on the toolbar.

Report Template Object List Dialog Box

The Report Template Object List is a printable object collection (POC) dialog box. A POC lists
those objects to be printed based on current Report Template filters. The Report Template Object
List dialog box displays:
 In the Scope Nodes box, the object classes in which the Report Template is searching
for objects for which to generate reports, and
 In the Printable Object List box, all the objects for which reports are generated and
printed.
This dialog box appears when a request to print a Report Template is made.

375
B0700FE – Rev A 13. Printing and Reports

Using Filters
The Report Template Editor allows you to create and edit the filter used by Report Templates to
eliminate unwanted objects from their object lists. The filter is defined by its filter expression
displayed in the CurrentFilters list box in the Report Template Editor.
The filter expression is a series of criteria built into a functional expression using logical
connections (AND/OR) and parentheses. All objects for which the Report Template creates
reports must satisfy the criteria in the filter expression.
Each line in a filter expression defines an object or parameter attribute. The Report Template
eliminates all objects from its object list that do not possess this attribute. When multiple lines are
used, the Report Template organizes the attributes in each line using AND, OR, and
parentheses. The Report Template Editor does not support wildcards (*) in its filter expressions.
The Report Template Editor has four types of criteria for creating the filter expression:

Parameter As shown in the Definition Editor (Figure 13-9), all objects have a series
of parameters, each parameter has a standard series of attributes, and each
attribute has a value.

Figure 13-9. Example Showing the Parameter Element

The Parameter element directs the Report Template to search for all
objects containing a specific parameter with a specific value in a specific
attribute. The attributes available to this element are equivalent to any of
the columns in the Definition Editor, with the exception of the Attributes
column. For example, you can use this element to select all objects with a
parameter type of AIN.

376
13. Printing and Reports B0700FE – Rev A

State As shown in the ListView Editor (Figure 13-10), all objects are assigned a
download state, such as Added, Modified, or Locked.

Figure 13-10. Example Showing the State Element

The State element directs the Report Template to search for all objects
containing a download state with a specific type. All modification states
are available. For example, you can use this element to select all objects
which have been Added to the IACC database, but have not yet been
downloaded to a control processor.

Type The Type element directs the Report Template to search for all objects
from a specific class.All these classes are available; however, only defini-
tions and instances of real-world objects can exist in the Report Template’s
object list. For example, you can use this element to select all analog con-
trol block types.

Category As shown in the results of a Where Used search (Figure 13-11), all objects
have a category which defines whether they are Definitions, Elements,
Instances, or Undefined.

Category

Figure 13-11. Example Showing the Category Element

The Category element directs the Report Template to search for all objects
of a specified category. All categories in IACC are available. For example,
you can use this element to select all object instances in the IACC data-
base.

377
B0700FE – Rev A 13. Printing and Reports

Building a Filter Expression

To build a filter expression:
1. Right-click the Report Template in the Project Navigator and choose Report
Template Editor from the pop-up menu.
The Report Template Editor appears (Figure 13-12).

Figure 13-12. Report Template Editor

The editor consists of five tabbed pages, each with a New Filter box on the left and a
CurrentFilters list box on the right.
2. Click the tab for the type of criteria you want to set.
3. Build the element using the selections in the New Filter list box.
To add Parameter elements to the filter expression:
a. Use the pull-down list to select the parameter attribute and enter the parameter in
the Parameter Name box.
b. Use the Operator pull-down list to select whether the parameter values sought
should be equal to (=), greater than (>) or less than (<) the value in the Value box.
c. Enter the parameter value in the Value box.

378
13. Printing and Reports B0700FE – Rev A

d. Click AND or OR to specify the relationship between this element and the element
above it.
If this is the first or only element in the CurrentFilters list box, you can skip
this step.
e. Click Add.
The element is added with the following format:
Parm: [Parameter Attribute] [Parameter Name] [Operator (=,<,>)]
[Parameter Value]
To add State, Type, or Category elements to the filter expression:
a. Select the element from the list in the New Filter box.
b. Click AND or OR to specify the relationship between this element and the element
above.
If this is the first or only element in the CurrentFilters list box, you can skip this step.
c. Click Add.
The element is added with one of the following formats:
State: [Parameter State]
Type: [Object Class]
Cat: [Object Category]
4. Complete the filter expression:
 Add other elements to the expression.
 If you want to delete a line in CurrentFilters, select the line and click Delete.
 If you want to erase the entire filter expression, click Delete All.
5. Add parentheses to the elements in the filter expression to treat a group of elements as
one in the expression:
a. Click the Parenthesis tab.
b. Select the first line of the expression you wish to include in parentheses and click
Left Before or Left After to insert an open parenthesis before or after the
selected line in the filter expression.
c. Select the AND or OR to join the combined elements with the line above them and
click Add.
d. Select the last line of the expression you wish to include in parentheses, and click
Right Before or Right After to insert a closed parenthesis before or after the
selected line.
e. Select the AND or OR to join the combined elements with the line below them, and
click Add.

379
B0700FE – Rev A 13. Printing and Reports

6. Click Validate Filter to ensure that the Report Template can find one or more
objects from its object list.
The Report Template Editor uses the filter to count the number of objects that fulfill
the criteria in the filter expression in the Report Template’s object list. When the vali-
dation is finished, a message box displays, “Filter validation is successful.”
7. Click OK to close the message box and return to the Report Template Editor
dialog box.

State Tab
The State tab is shown in Figure 13-13.

Figure 13-13. State Tab of the Report Template Editor

380
13. Printing and Reports B0700FE – Rev A

Type Tab
The Type tab is shown in Figure 13-14.

Figure 13-14. Type Tab of the Report Template Editor

The tree view in the New Filter group contains all the object classes available in IACC.

381
B0700FE – Rev A 13. Printing and Reports

Category Tab
The Category tab is shown in Figure 13-15.

Figure 13-15. Category Tab of the Report Template Editor

Table 13-2 lists the meaning of each of the entries in the Object Categories list box in the
Category tab.

Table 13-2. Type and Definition Objects List Box

Category Description
Definition Filters for object definitions.
Instance Filters for object instances.
Type Filters for root definitions of object classes for real-world objects.

382
13. Printing and Reports B0700FE – Rev A

Parenthesis Tab
The Parenthesis tab is shown in Figure 13-16 and described in Table 13-3.

Figure 13-16. Parenthesis Tab of the Report Template Editor

Table 13-3. Fields and Buttons Unique to the Parenthesis Tab

Field/Button
Parenthesis Insertion Type
Description
Defines where the parenthesis is added in the filter expression in
relation to the selected element (line). When you select a line in the
CurrentFilters list box, only the option buttons which are valid are
available to you.
 Left Before and Left After create an opened parenthesis – (.
 Right Before and Right After create a closed parenthesis – ).

383
B0700FE – Rev A 13. Printing and Reports

384
14. 100 Series Migration
This chapter provides an overview of 100 Series migration. It also provides the process and the
sequence of procedure required for 100 Series migration.
The 100 Series Migration is a conversion of Save All database or replacement of 100 Series mod-
ules with 200 Series. To perform the migration, you must upgrade the I/A Series Configuration
Component (IACC) software to version 2.4 or later. The migration can be performed at the
CP270 (FCP/ZCP), FCM or FBM level as per the Table D-1.
IACC will automatically create all the replacement of 100 Series FBMs of CP270s and FCMs.
You must specify the letterbug of each 200 Series FBM which replaces each 100 Series FBM. ECB
names of 100 Series FBMs will remain same after migration depending on the user choice (pro-
vided option through a checkbox). The changed objects will automatically reflect in all the occur-
rences of database configuration. These control databases can be downloaded to their CPs as
discussed in “Overview of System Configuration” on page 89.
Refer to “Legacy CP/CP270 Configuration Migration (Import)” on page 440 for information on
how to migrate Legacy CPs (30, 40, 60...) Save all configurations. User can also use the existing
CP270 configuration which has 100 series FBMs that needs to be migrated. To perform the
Migration at various levels use the context menu "Migrate to 200 Series":
 FBM Level
 FCM Level
 CP270 (FCP/ZCP) Level
The menu item will be enabled when the 100 Series FBM Module is present under CP270
(FCP/ZCP) and FCM, else it will be disabled.

Before You Begin

1. All duplicates should be manually resolved before performing the Migration. User
should validate the configuration before Migration using IACC validation functional-
ity and ensure that each and every module should be in non-downloaded state. Refer
to “Validating a Configuration” on page 133.
2. If Migrating 100 Series FBMs to 200 Series FBMs on the same CP270, it is highly
recommended that you backup the IACC database, as it is not possible to reverse the
migration process. The IACC Database Administrator can back up the IACC data-
base. This procedure is provided in “Protecting the Database” on page 85.
3. Refer to “Legacy CP/CP270 Configuration Migration (Import)” on page 440 for
information on how to migrate Legacy CPs (30, 40, 60...) Save all configurations.

NOTE
Migration will support only the ECB/FBM combination mentioned in the
Table D-1.

385
B0700FE – Rev A 14. 100 Series Migration

FBM Level Migration

To migrate a 100 Series FBM control blocks from the FBM itself, proceed as follows:
1. Locate the 100 Series FBM in the Project Navigator under CP270.
2. Right-click the FBM and click Migrate to 200 Series in the context menu that
appears as shown in Figure 14-1.

Figure 14-1. Context menu Selection

The FBM Migration dialog box appears as shown in Figure 14-2. It lists the 200
Series migration FBMs to which this 100 Series FBM can be converted.

Figure 14-2. Create 200 Series FBM Dialog Box

3. Click the checkbox beside the appropriate 200 Series FBM to migrate.

386
14. 100 Series Migration B0700FE – Rev A

4. Select or unselect Persist ECB Name checkbox based on the requirement, this oper-
ates as per the Table 14-1.
5. Click OK. The new 200 Series migration FBM will be created.
All the references to the former 100 Series FBM are mapped to this new FBM. IACC
automatically assigns a new unique letterbug to this and the 100 Series FBM will be
deleted permanently. Update the letterbug for the new 200 Series migration FBM to
the letterbug assigned to this FBM in the planning stage.
If the migration fails, then the old 100 Series FBM will be restored.

Table 14-1. Checkbox Functionality

100 Series FBM Check Box 200 Series FBM

FBMName ECBName True - Check FBMName ECBName
False - Uncheck
F00001 F00001(Formula) True F00002 F00001(No Formula)
F00001 FBM01(No For- True F00002 FBM01(No Formula)
mula)
F00001 F00001(Formula) False F00002 F00002(Formula)
F00001 FBM01(No For- False F00002 FBM01(No Formula)
mula)

CP270 (FCP/ZCP) Level Migration

To migrate 100 Series FBM control blocks for all the 100 Series FBMs assigned to a CP270
(FCP/ZCP), proceed as follows:
1. Locate the CP270 (FCP/ZCP) in the Project Navigator.
2. Right-click the CP270 (FCP/ZCP) and click Migrate to 200 Series in the con-
text menu that appears as shown in Figure 14-1.
The Migrate to 200 Series dialog box appears as shown in Figure 14-3. It lists the 200
Series migration FBMs to which the 100 Series FBM can be converted.

387
B0700FE – Rev A 14. 100 Series Migration

Figure 14-3. FCM/CP270 Migrate Window

3. Click the checkboxes in the grid to select the FBMs required for Migration.

The description about the columns in the Migrate to 200 Series window before
migration:
 Compound - Compound name of FBM's ECB resides.
 ECB Name - ECB name of the FBM
 ECB Type - ECB type of FBM
 FBM Name - FBM letterbug
 FBM Type - FBM Type
 New FBM Type - Supported 200 Series FBM type for this 100 Series FBM as
per Table D-1.
 New FBM Name - The new FBM name. A unique and valid FBM name will
be provided by default. The user can edit the FBM name if required, but can-
not duplicate the FBM name.
 Parent - Parent Module (FCP270/FCM100) to which the New FBM will be
attached. The Parent name will be derived and created as per the Table 14-2.

388
14. 100 Series Migration B0700FE – Rev A

Table 14-2. Parent Resolution

CP270 FCM FBI 100 Series New 200 Series FBM

FBM
FCP270    FBM will be attached to FCP270
FCP270    FBM will be attached to FCP270
ZCP270    FCM Will be created and FBM will be
attached to new FCM
ZCP270    FBM will be attached to the existing one
of the (First) FCM if FBM is at CP Level
else it will be attached to its parent FCM.
ZCP270    FBM will be attached to FBI Parent i.e.,
FCM.

In all the above cases old FBM will be deleted after migration. If there are no FBMs
present in FBI after migration, the FBI does not have any modules.
 Module Selected - Displays the name of the module selected
(FCP270/ZCP270).
The following operations can be performed on this dialog:
a. Select or unselect Persist ECB Name checkbox based on the requirement. This
operates as per Table 14-1.
b. Click Select All to select all the rows of FBMs for migration.
c. Click Deselect All to de-Select all the rows of FBMs.
d. Click Print, the user selected mapped configurations will be populated in the
Migration Tab of the Output window as shown in Figure 14-4 (Existing contents
of Migration Tab will be cleared before the activity). If there no selected FBMs, a
warning messages pops-up as shown in Figure 14-5.
The Messages for Print are displayed in the "Migration" Tab of the Output win-
dow in the following format:
"Timestamp/Parent / FBM Name [FBM Type, Extension Type] will Migrate to New
Parent / FBM Name [FBM Type, 0]"

Figure 14-4. Print Messages

e. Click Cancel to cancel the migration operation.

389
B0700FE – Rev A 14. 100 Series Migration

f. Click Help for the online help.

4. Click Next to confirm the selection. If the user clicks on Next without selecting any
checkboxes in the grid a warning message pops-up as shown in Figure 14-5.

Figure 14-5. Warning Message Box

If the clicks on Next after selecting the checkboxes in the grid, the Verify dialog box
appears to re-verify before proceeding further as shown in Figure 14-6.

Figure 14-6. Verification Dialog Box

5. Click Start.
The migration process begins and all the selected modules will be migrated to 200
FBM modules as per user selections. The Migrate dialog box appears displaying the
progress messages as shown in Figure 14-7. All the Progress/Status messages will be
displayed in Migration tab of the Output window.
If the migration fails, the database configuration will be restored.

390
14. 100 Series Migration B0700FE – Rev A

Figure 14-7. Migration Dialog Box

6. Click Finish, completes the migration and reverts back to the main window.

FCM Level Migration

To migrate 100 Series FBM's control blocks for all the 100 Series FBMs assigned to a FCM, pro-
ceed as follows:
1. Locate the FCM in the Project Navigator.
2. Right-click the FCM and click Migrate to 200 Series in the context menu that
appears as shown in Figure 14-1.
The Migrate to 200 Series dialog box appears as shown in Figure 14-8. It lists the 200
Series migration FBMs to which the 100 Series FBM can be converted.

391
B0700FE – Rev A 14. 100 Series Migration

Figure 14-8. FCM/CP270 Migrate Window

3. Click the checkboxes in the grid to select the FBMs required for Migration.
The description of the columns in "Migrate to 200 Series" window before migration:
 Compound - Compound name of FBM ECB resides.
 ECB Name - ECB name of the FBM
 ECB Type - ECB type of FBM
 FBM Name - FBM letterbug
 FBM Type - FBM Type
 New FBM Type - Supported 200 Series FBM Type for this 100 Series FBM as
per Table D-1.
 New FBM Name - The new FBM name. A unique and valid FBM name will
be provided by default and the user can edit the FBM name if required, but
the FBM name cannot be duplicated.
 Parent - Parent Module (FCM100) to which the New FBM will be attached.
The Parent name will be derived and created as per the Table 14-2.
Module Selected - Displays the name of the selected module (FCM)
The following operations can be performed on the "Migration to 200 Series" dialog:
a. Select or unselect Persist ECB Name checkbox based on the requirement. This
operates as per Table 14-1.
b. Click Select All to select all the rows of FBMs for migration.
c. Click Deselect All to de-Select all the rows of FBMs.

392
14. 100 Series Migration B0700FE – Rev A

d. Click Print, the user selected mapped configurations will be populated in the
Migration Tab of the Output window as shown in Figure 14-4 (Existing contents
of Migration Tab will be cleared before the activity). If there no selected FBMs, a
warning messages pops-up as shown in Figure 14-5.
The Messages for Print are displayed in the Migration Tab of the Output window
in the following format:
"Timestamp Parent / FBM Name [FBM Type, Extension Type] will Migrate to New
Parent / FBM Name [FBM Type, 0]"
e. Click Cancel to cancel the migration operation.
f. Click Help for the online help.
4. Click Next to confirm the selection. If the user clicks on Next without selecting any
checkboxes in the grid a warning message pops-up as shown in Figure 14-5, else the
Verify dialog box appears to re-verify before proceeding further as shown in
Figure 14-6.
5. Click Start. The migration process begins and all the selected modules will be
migrated to 200 FBM modules as per user selections. The Migrate dialog box appears
displaying the progress messages as shown in Figure 14-7. All the Progress and Status
messages will be displayed in Migration tab of the Output window.
If the migration fails, the database configuration will be restored.
6. Click Finish, completes the migration and reverts back to the main window.

Migration Tab
The Migration progress and status messages are displayed in the "Migration" Tab of the Output
window as shown in Figure 14-9.

Figure 14-9. Messages Dialog Box

393
B0700FE – Rev A 14. 100 Series Migration

The log messages are categorized into Status and Progress messages:
 Status Messages: Displays the status of the migration
 Progress Messages: Displays the progress of migration
The Log Messages window enables you to do the following:
1. Right-click a message and select Print Tab Contents to print the tab messages.
2. Right-click a message and select Save Tab Contents to save the messages in .csv or .txt
format.
3. Right-click a message and select View Entire Message to view the messages in another
window.

394
15. Managing IACC Databases
This chapter describes procedures for setting multiple IACC databases and tools for
maintaining the databases.
As part of the server installation, the IACC setup program creates a Database folder in the shared
IACC directory, and loads nine files (with the extensions *.isd and *.icd) containing the defini-
tions and templates supplied with the software (Figure 15-1). This database is populated with
objects and new definitions as you develop a control strategy.
The Database folder contains two folders:
 Backup is the default directory for backup files created by IACC.
 EmptyDB contains the same files that are installed in the Database folder. You can
create a new database by copying the contents of this empty database to a new
location.
When a client logs onto IACC, environment variables locate the database in the
\IACC\Database folder on the server.

Figure 15-1. IACC Database Directory Structure

You can create additional databases on the same server, and selectively enable IACC clients to
access multiple databases on any server. These options are described in “Setting Up Multiple
Databases” on page 396.

395
B0700FE – Rev A 15. Managing IACC Databases

This chapter also covers the IACC tools for maintaining the integrity and availability of IACC
data:
 Export of IACC databases, tag data, and compounds, including exports to SaveAll
diskettes (page 401)
 Import functions that accept data in a variety of formats and include the ability to
merge data with existing objects (page 405)
 IACC Database Administrator, which provides Backup, Restore, and Verify functions
(page 419).

Guidelines for Managing IACC Databases

Before using any of the tools described in this chapter, it is important to note the different uses of
the Export/Import and Backup/Restore functions:
 The Backup function is applied to only one database at a time, the current database
when the function is initiated in IACC, or a selected database when Backup is initi-
ated from the Database Administrator window. If you have created multiple databases,
make sure that you back up each database regularly.
 Do not use Export/Import for backing up and restoring databases.
 The default backup location is a folder in the IACC directory. It is advisable to archive
that directory to a different location on the network, or to different media.
 Before installing a new version of IACC software, you should export all databases and
move the export files outside of the IACC directory structure. During installation of
the new software the Database directory is emptied. After installation of the new ver-
sion, you can then import the databases created in the earlier version.
Do not use the Backup and Restore functions to upgrade databases to new IACC soft-
ware. The backup files are version-dependent. Export files are not version-dependent.
 Use Export/Import to replicate a database, and not Backup/Restore. The Restore
function can copy the saved database only to the database’s original directory
structure.

Setting Up Multiple Databases

! WARNING
Do not configure a CP and its compounds in more than one IACC database.

To set up an IACC database:

1. On the IACC server, create a folder in the \IACC\Database directory and copy the
contents of \IACC\Database\EmptyDB to the new folder.
You cannot create the new database by restoring an IACC database to the new
location, as the Restore function can only copy the files to the directory where the
backup files were made.
2. In the new directory, rename the IACC.icd file using the form IACC_name.icd to
create the database name.

396
15. Managing IACC Databases B0700FE – Rev A

For example, in Figure 15-2 the file in the \IACC\Database\Training folder is

IACC_Tng.icd.

Figure 15-2. Files Copied from EmptyDB to a New IACC Database

3. Open \IACC\Database\IACCSettings.txt with a text editor such as Notepad

(Figure 15-3).

397
B0700FE – Rev A 15. Managing IACC Databases

4. Follow the syntax instructions above the [DATABASES] section to enter a line under
[DATABASES] containing the database name, path, and a description.
In Figure 15-3, there are five databases listed: the original IACC database and two
other local databases (on the server plen01), and two databases on another IACC
server (dws011).

Figure 15-3. Sample IACC Settings File

IACC selects a database using the IACC_DBNAME system environment variable.

When that variable has a null value or is missing, IACC uses IACCSetting.txt to
display a list of available databases when the user logs on. The next step is to edit the
IACC_DBNAME variable.
5. Choose Start > Settings > Control Panel and click the System icon in the
Control Panel.
6. Select the Advanced tab in the System Properties dialog box and click Environment
Variables at the bottom of the tab.
7. Select IACC_DBNAME in the System environment variables group and click Edit.

398
15. Managing IACC Databases B0700FE – Rev A

8. Delete Iacc from the Variable value field and click OK (Figure 15-4).

Figure 15-4. Changing the IACC_DBNAME Variable

NOTE
On Windows 7 and Windows Server 2008 stations, Environment Variables list with
blank values cannot exist, so the Environment Variable IACC_DBNAME should be
deleted from the list.

9. Close the System Properties dialog box and the Control Panel.
10. Make the same change to the IACC_DBNAME variable on each of the server’s IACC
clients.
Now when you log onto IACC, the IACC Databases dialog box (Figure 15-5)
presents a list of available databases.

399
B0700FE – Rev A 15. Managing IACC Databases

Figure 15-5. IACC Databases Dialog Box

11. Select a Database Name and click OK to display the IACC Log On window.
You can create multiple databases, and then use the Export/Import functions to replicate a control
strategy for multiple locations.

NOTE
If you create multiple databases, make sure that you regularly make backups of each
database. When you initiate Backup in IACC (Tools > Backup), only the currently
opened database is backup. When you use initiate Backup from the IACC Database
Administrator window, only the selected database is backed up.

Protecting Multiple Databases

The actions listed in this section provide maximum protection for your IACC databases if you
need to do any of the following:
 Rebuild the IACC application in the event of a catastrophic failure of an IACC server.
 Reinstall IACC.
 Upgrade to a new version of IACC.
To provide maximum protection for your IACC databases, take the following actions on a regular
basis:
1. Perform a complete export of each database using the Export to IACC Format
described in the next section.
Make sure you select the export command from the System object at the top of the
System tab in Project Navigator.
2. Archive the Export files to a different network drive or media.
3. Copy and archive \IACC\IACCSettings.txt.
4. Copy and archive \IACC\CoExistence\IACC-CP.
5. Print copies of the IACCSettings file and IACC-CP to create a record of database
locations, and IACC maintained CPs.

400
15. Managing IACC Databases B0700FE – Rev A

6. Perform a Backup of each database.

7. Copy the Backup files to another drive on the network or to other media.
8. Make copies of the display files (*.fdf ) created using the FoxDraw application in
IACC.
The files should be located in \opt\fox\displib and folders you added to the directory.
9. Copy any custom bitmaps or other elements referenced by the displays.
You do not need to copy the components supplied with FoxDraw and IACC.

Export Functions
The IACC export functions allow you to save IACC objects to one of three types of files:
Export to IACC Format
Export TagList Agent
Export Save/SaveAll Data
ArchExport Utility
Sends a group of custom IACC objects to an
import/export file (.ida). This is the format used
to share custom objects among multiple IACC
databases.
Exports a file containing TagList data to a .dbf,
.csv, or .txt file as described in “Exporting
TagLists” on page 267.
Exports compound and block information to a
backup file.
Exports IACC database information into XML
files for IEE imports.

Exporting to an IACC Format File

This export function saves a copy of selected IACC objects to a new import/export file (.ida).
The new file can either be imported into another IACC database or back into the original
database. Keep in mind that any set of objects exported to a new IACC import/export file for
transfer to another IACC database is copied, not moved, to this file. The objects in the IACC
database remain in their original forms.

NOTE
An IACC Format export can include drawing objects reference, but not the actual
drawing files. Copy to the files to the destination server before importing the object
references using the IACC Format Import. See “Importing Displays” on page 300.

To export an IACC object or the entire IACC database:

1. Click the System object at the top of the System tab if you are exporting the entire
database, or click the IACC object branch in the Project Navigator to export the
object (and its child objects and connected definitions).

NOTE
Select the System object if the export is part of an upgrade to a new version of IACC
software.

401
B0700FE – Rev A 15. Managing IACC Databases

2. Choose File > Export from the menu bar to open the Available Formats dialog box
(Figure 15-6).

Figure 15-6. Available Formats Dialog Box

3. Select Export to IACC Format, and click Next to display the IACC Export File
Name dialog box (Figure 15-7).

Figure 15-7. IACC Export File Name Dialog Box

4. To change the default destination file shown in the Save in field:

a. Click Browse to open a Save As dialog box.
b. Select the appropriate folder or network location in the Save in field.
c. Click Save.

NOTE
An IACC format file cannot be exported to diskettes unless it can fit on one dis-
kette. This export process does not prompt for insertion of multiple diskettes.

5. In the Enter Export File Name field, type the name for the import/export file.

402
15. Managing IACC Databases B0700FE – Rev A

Be sure the filename ends with .ida to ensure that IACC recognizes the file as valid for
importing.
6. Click Next and then Start in the Information dialog box.
7. Click the Finish button when the dialog box indicates that the export is complete.

Exporting Save/SaveAll Data

To export Save/SaveAll Data:
1. Select the object in the Project Navigator you want to export, and choose File >
Export from the menu bar.
The Available Formats dialog box appears.
2. Select Export Save/SaveAll Data and click Next to display the Export Informa-
tion dialog box (Figure 15-8).

Figure 15-8. Export Information Dialog Box

3. Click the browse button ( ) to open a dialog box for selecting a directory, and
click the appropriate folder in the data tree.
The destination for the exported data appears in the Enter IA Save/SaveAll
Export Directory field. Typically, you export Save/SaveAll data to a diskette in
your A: drive, which is the default entry in this field.

403
B0700FE – Rev A 15. Managing IACC Databases

4. Click Next to display the Select Compounds to Export dialog box (Figure 15-9).

Figure 15-9. Select Compounds to Export Dialog Box

5. Click the check box next to every object you want to export, or click Select All to
chose all objects in the field for export.
Deselect All clears all selections.
6. Click Next.
The Verify dialog box displays the blocks to be exported (Figure 15-10).

Figure 15-10. Verify Dialog Box for a Save/SaveAll Export

7. Click Start in the Verify dialog box, and Finish when the button appears at the
bottom of the dialog box.
8. Check the Export tab in the Output window for information on any errors.

404
15. Managing IACC Databases B0700FE – Rev A

ArchExport.exe IACC Utility for IEE Import Support

NOTE
The following information is for IEE Users only.

ArchExport.exe exports IACC database information into one or more XML files for the purpose
of import into Infusion Engineering Environment (IEE).
For more information on this refer to Appendix C “Executing the IACC Utility ArchExport.exe”.

Import Functions
The IACC Export and Import functions enable you to exchange the IACC database among
applications, save object configurations for re-use in other projects, and revert to earlier project
phases for selected objects.

Import Formats
The IACC import functions allow you to bring one of five types of files into the database
associated with your IACC application:

IACC Format To load a file that contains one or more IACC objects saved anywhere on
your network. These import/export files have the suffix .ida. This is the
format used to share custom objects among multiple IACC databases.

NOTE
An IACC Format import can include drawing objects reference, but not the actual
drawing files. Copy to the files to the destination server before importing the object
references using the IACC Format Import. See “Importing Displays” on page 300.

Save and SaveAll To import backup files from an I/A Series database containing
compounds and blocks configured with the Integrated Control Configu-
rator (ICC). IACC replaces the ICC, and the Save/SaveAll format enables
you to migrate to the new configurator.

NOTE
You should use Import Save/SaveAll Data and Export Save/SaveAll Data only for
transferring data between ICC and IACC. Save/SaveAll files are not appropriate for
backing up IACC databases, as the Save/SaveAll files exclude numerous objects such
as CSDs, custom block definitions, and TagList data.

SysDEF To load a backup file from a SysDEF Export disk containing hardware,
software, and parameter definitions. See “Importing System Definition
Data” on page 91.

TagList Agent To import text and database files containing TagList data. See
“Importing TagLists” on page 258.

405
B0700FE – Rev A 15. Managing IACC Databases

Display Agent To import a backup file containing FoxDraw display data as described in
“Importing Displays” on page 300.
You invoke the import functions from the Project Navigator. Imported data and objects are auto-
matically placed by IACC in the appropriate places in the database and in the Project Navigator
hierarchy.

NOTE
Use the Backup/Restore functions (see “Backing Up and Restoring the Database”
on page 419) rather than Export/Import to make regular backups of IACC data-
bases.

IACC Import
The IACC Import feature displays import file definitions and objects in a data tree similar to
those in the Project Navigator. You then select items for import and specify whether they are to be
imported as copies (and thus avoid overwriting objects you want to maintain), or as replacements
for items with matching names.
To import an IACC database:
1. Click anywhere in the Project Navigator, and choose File > Import from the menu
bar to open the Available Formats dialog box (Figure 15-11).

Figure 15-11. Available Formats Dialog Box

2. Select Import from IACC Format and click Next to open a dialog box for selecting
the database to be imported.
3. Click Browse to display a standard Windows Open dialog box for specifying the
filename and location (Figure 15-12).

406
15. Managing IACC Databases B0700FE – Rev A

Figure 15-12. Import File Name and Open Dialog Boxes

407
B0700FE – Rev A 15. Managing IACC Databases

4. Select the file to be imported and click Next.

The Import dialog box provides tools for specifying items to be imported
(Figure 15-13).

Compound and
CSDs contained
in the selected
Plant Area

CSD Templates
used to create
CSDs H003 and
H004

Derived block definition

used in CSD Template
Connected FBM

Figure 15-13. Import Dialog Box Showing Objects with Matching Types

The data tree in the box, Objects in File, displays the contents of the import database.
The tree in Figure 15-13 includes a Plant Area object that contains one compound
and three CSDs. Two of the CSDs were created from a template. When the Plant
Area object was exported, IACC included the CSD Template (Tank) and its blocks.
The block TANK1 in the template is an instance of a derived block definition, so the
definition was also included in the export file. Likewise, when the Plant Area object is
imported from the file, the template and the block definition are also imported
whether or not they are explicitly selected. Finally, the import file contains ECBs that
were connected to the CSDs when the CSDs were created from the template.
5. Select each object you want to import by clicking the check box to its left, or click
Select All.
An object is automatically selected when its parent is selected.

408
15. Managing IACC Databases B0700FE – Rev A

6. Click one of the options in the Import Options group:

 Use Copy All Objects if you do not want to overwrite objects in the IACC
database with matching items in the import file. When the import is complete,
the name of matching items are displayed in red, indicating the duplicate names.
 Check Replace Existing Objects, Copy Other Objects if you want to
update the database with objects selected from the import file.
7. Check Preserve Objects’ Download Status to maintain the download status of
objects in the import database.
This option is primarily used for migrating to a new version of IACC which involves
importing IACC Format files exported from the earlier version. If you do not select
this option, the status of the updated objects is Added.
8. Click Preview to open the Preview dialog box.
Figure 15-14 previews the import of a Plant Area object with the Replace option
selected.

Figure 15-14. Preview of Objects to be Merged

409
B0700FE – Rev A 15. Managing IACC Databases

The preview uses symbols and colors to indicate the various effects the import have on the IACC
database:
Object in the import files overwrites the object in the IACC database.
Object is copied from the import file to the IACC database. The
similarly named object in the IACC database is maintained. Duplicate
names are displayed in red italics.
Object is imported to the IACC and left unassigned.
Definition or object is imported because it is connected to another
object selected for import. IACC import automatically includes
derived definitions used by object selected for import and child objects
of the selected object.

Figure 15-15 is an import preview in which a Plant Area object has been selected for import and
the copy option has been selected.

Figure 15-15. Preview of Objects to Copied from the Import File

9. Click Close to return to the Import dialog box.

10. Click Next.
The Verify dialog box appears (Figure 15-16).

410
15. Managing IACC Databases B0700FE – Rev A

Figure 15-16. Verify Dialog Box for IACC Import

11. Click Next, and then Finish when the dialog box indicates the procedure is com-
plete.
12. Review the import-related tabs in the Output window (Figure 15-17).

Figure 15-17. Output Window with Import-Related Tabs

The following tabs are displayed in the Output window with an import:
 Import Log Displays all messages generated by the import procedures.

411
B0700FE – Rev A 15. Managing IACC Databases

 Import Unassigned Lists objects that were imported and are now unassigned.
 Import Failures Displays error messages.

Importing Save/SaveAll Data

! WARNING
Read this entire section before importing data from a SaveAll. You should also
review “Synch Utility” on page 340 for information on synchronizing the download
status of IACC objects with compounds and blocks in the CP.

NOTE
Make sure that you have an up-to-date ICC SaveAll for the CP, as a recovery option,
before beginning any SaveAll import. It is also recommended that you back up the
IACC database immediately before importing the data.

NOTE
If you intend to replace the entire database in an existing CP with the content of the
SaveAll, the CP should be initialized prior to a SaveAll import (after making a cur-
rent SaveAll for recovery). This eliminates the need to synchronize IACC with the
existing CP database.

! WARNING
Performing a SaveAll Import from a SaveAll that contains blocks in the current CP
database requires a manual synchronization of the content of the IACC database to
the database in the target CP. Failing to perform the synchronization may result in
one or more blocks that can no longer be downloaded by IACC.

The SaveAll import constructs compounds and matching CSDs using the compound and block
information contained in the SaveAll.
The compounds are named in accordance with the compound names in the SaveAll. The newly
created compounds are placed in the Unassigned_Compounds folder in the Plant tab. If an
imported compound has the same name as a compound already in the database, the compounds
are not merged; the duplicate compound names are displayed in red italics the Project Navigator.
Depending on the choices made during import, the CSDs are constructed and named based on
the content and name of each compound or on the LOOPID parameter of the blocks. The newly
created CSDs are placed in the Unassigned_CSDs folder in the Plant tab. If an imported CSD
has the same name as a CSD already in the database, the CSDs are not merged; the duplicate
CSD names are displayed in red italics the Project Navigator.
The new CSDs contain all the imported blocks and ECBs, and specify the linkage of each block
into one of the new compounds within the imported compound set. The status of the resulting
CSDs and compounds is Added, that is, they have not been downloaded to the CP. See “Viewing
Block Status” on page 337 for a description of object status and how each status affects how the
object is treated when it is downloaded.

412
15. Managing IACC Databases B0700FE – Rev A

! WARNING
Do not modify the new CSDs or compounds until you have synchronized the
objects with those resident in the CP.

Do the following before importing Save/SaveAll data:

1. Ensure that you have a current SaveAll of the CP for recovery, even if you are not
importing compounds and blocks that are currently in the CP.
2. Make a backup of the IACC database (as described in “Backing Up and Restoring the
Database” on page 419) if you do not have a recent backup.
3. Right-click Plant at the top of the Plant tab in the Project Navigator, choose
ListViews > Plant Compounds from the pop-up menu, and print the resulting list
of compounds that are already in the IACC database.
4. Right-click Plant at the top of the Plant tab in the Project Navigator, choose
ListViews > Plant CSDs from the pop-up menu, and print the resulting list of
CSDs that are already in the IACC database.
To import Save/SaveAll data:
1. Click anywhere in the Project Navigator and choose File > Import from the menu
bar to open the Available Formats dialog box (Figure 15-11).
2. Select Import Save/SaveAll Data, and click Next.
The Import Information dialog box (Figure 15-18) prompts you to specify the
location of the files to be imported.
3. Click the browse button ( ) to open a dialog box for selecting a directory, click the
appropriate folder in the data tree, and click Next.
Typically, you import Save/SaveAll data from one or more SaveAll diskettes in your
A: drive, which is the default entry in this field.

Figure 15-18. Import Information Dialog Box for a Save/SaveAll Import

413
B0700FE – Rev A 15. Managing IACC Databases

4. Click the check box next to the CP whose compounds you want to import.
You may only import to one CP at a time.
5. Select one of the two options for generating and naming CSDs:
 Choose Loop ID to create and name CSDs based on the LOOPID parameter of
the blocks in the SaveAll file. All blocks with the LOOPID parameter value are
placed in the same CSD.

! WARNING
The number of blocks “assigned “to the same CSD determines the ultimate look of
the CSD. The number of the block differs depending on the Appearance Object
assigned or modified for the specific Block as well on the format of the Sheet Tem-
plate chosen for the specific CSD (more blocks in the default appearance on 11x17
less blocks on 8.5x11). Use the print test of the CSDs to determine the outcome of
your final Strategy Diagram representation on selected print format. Refer “Flow
chart for Converting ICC SaveAll Diskette to IACC Database Format” on page 435

 Choose Compound Name to name each CSD using the compound associated
with the blocks in the CSD.

! WARNING
The number of blocks within the Compound determines the ultimate look of the
CSD. Having more then 20–25 Blocks in the Compound results in very unclear
and unmanageable look of the CSD. Use this option when Compounds have lim-
ited number of blocks. Use the print test of the CSDs to determine the outcome of
your final Strategy Diagram representation on selected print format. Refer “Flow
chart for Converting ICC SaveAll Diskette to IACC Database Format” on page 435

6. Click Next.
A message box prompts you to insert additional diskettes if applicable. Once all
necessary diskettes have been read, the Select Blocks to Import dialog box appears
(Figure 15-19).

414
15. Managing IACC Databases B0700FE – Rev A

Figure 15-19. Select Block Dialog Box in a Save/SaveAll Import

7. Compare the compounds names and the proposed CSD names in the dialog box with
the printed lists of compounds and CSDs already in the database.

NOTE
The import process does not merge data, but rather creates new compounds and
CSDs following its naming rules regardless of the names already in the IACC
database. Any resulting duplicate names - even though they are displayed in red
italics - can be a source of confusion and multiple errors. Be careful to avoid
creating duplicates.

To avoid duplicate names:

a. Cancel the import.
b. Rename the objects in the database.
c. Download the renamed compounds and CSDs if those objects have been
previously downloaded.
d. Restart the import.
8. Click the check box in the Select Blocks to Import field next to every object
you want to import.
 Click Select All to chose all objects in the field for import.
 Click Deselect All to clear your selections.

415
B0700FE – Rev A 15. Managing IACC Databases

! CAUTION
For IACC to make all the I/O connections properly, the FBM/ECBs should already
exist in the IACC database or be created as part of the SaveAll import. The SaveAll
import process creates the required FBM/ECBs based on data in the ECBs in the
import file if you check Create Nonexistent FBMs and ECBs (step 9) and follow the
instructions in step 10. Otherwise, you must cancel the import and add the
FBM/ECBs to the database first, in which case you should at least complete step 9
to identify required FBM/ECBs.

9. Check Create Nonexistent FBMs and ECBs and click Next to identify the FBM
and ECB objects that need to be created in IACC.
IACC displays a list of FBMs and ECBs that is created based on data in the ECBs in
the import file (Figure 15-20). In some instances, the import requires selection of
additional hardware. For example, in Figure 15-20, the five DIN rail mounted FBMs
to be created require a Fieldbus Communications Module to interface with the
selected CP. A drop-down list in the FBM type column allows you to select DCM10,
FCM10, or FBI10.

Figure 15-20. FBMs to be Created with a Save/SaveAll Import

10. Click the check box next to each FBM/ECB you want to create, make a selection for
module types that must be identified, and click Next.
If you do not want the FBM/ECBs to be automatically created by the import:
a. Note the required ECBs listed in the dialog box.
b. Cancel the import now.
c. Add the ECBs to the database using the procedures described in “Adding Fieldbus
Modules” on page 113.
d. Re-start the SaveAll import
11. Click Start in the Verify dialog box to start the import.

416
15. Managing IACC Databases B0700FE – Rev A

12. Click the Finish button when the dialog box indicates that the import is finished or
has been aborted because of errors.
The imported and newly created objects are displayed in the Network tab in the Proj-
ect Navigator (Figure 15-21).

ECBs created by a
Save/SaveAll Import

FBMs created by a
Save/SaveAll Import

Duplicate compound name

displayed in red italics

Figure 15-21. Results of a Save/SaveAll Import Displayed in the Project Navigator

The imported compounds and the created CSDs are displayed in the Plant tab in the
Unassigned Compounds and Unassigned CSDs folders, respectively.
13. Check the import-related tabs in the Output window for a log of the import actions.

After Importing from a SaveAll

Care must be exercised when the control database that was just imported from SaveAll format is
already resident in a CP. IACC does not automatically assume that the new database matches the
existing CP content. The status of the new CSDs, compounds and blocks is Added, that is, they
have not been downloaded. Thus, there is a mismatch in the download state of the newly
imported compounds and blocks.
There may also be compounds or blocks marked as duplicates, in red italics (Figure 15-21), of
those just imported. Validate the CP to flag any duplicate names.
When resolving name conflicts, be careful to rename the compounds and blocks that were in the
IACC database prior to the import and not those that were created by the SaveAll import. If the
renamed objects have been downloaded prior to the import, download them to update the CP
with the changed names.

Dealing with Compounds and Blocks Already in the CP

If any of the compounds and blocks you just imported are also in a CP under IACC control, you
must first synchronize the IACC database with the CP database to update IACC with the correct

417
B0700FE – Rev A 15. Managing IACC Databases

download status and parameters, as described in “Synch Utility” on page 340. Failure to establish
the correct downloaded state in IACC may make it difficult or impossible to perform changes and
download the blocks in the future.
Once the IACC database is completely synchronized to the existing CP, a download request
should result in no blocks or compounds being proposed for addition or deletion.

Dealing with the Imported Compounds and CSDs

You should not make changes to the newly constructed CSDs and compounds until the IACC
database has been synchronized to accurately reflect the current download state of the CP.
The SaveAll format contains far less connection information than IACC normally uses; it is possi-
ble that some connections automatically made during SaveAll import may not look entirely as
expected. IACC makes many of the block and ECB connections implied in the SaveAll data for
you. Some connections may be imported as block references only in the form of a C:B.P text
entry in the data sink parameter, without the formal IACC connection editor features. Be sure
that the CSDs are assigned to the correct compounds and that the compounds, in turn, are
assigned to the correct CP.
You are strongly advised to examine the content and relationships of the newly constructed CSDs
to the newly constructed compounds before making any changes. This is particularly important
when the imported compound contains ECBs. ECBs that have already been downloaded to the
CP have parameters that cannot be edited. Moving or reassigning these ECBs requires that they
be deleted from the CP and re-added, possibly disrupting on-line control strategy operation.

418
15. Managing IACC Databases B0700FE – Rev A

Backing Up and Restoring the Database

The IACC Database Administrator is a separate utility for backing up, verifying, and restoring
IACC databases. All three functions are selected from the IACC Database Administration win-
dow (Figure 15-22), which includes an Output window for monitoring the progress of the
selected operation.
When the IACC Database Administrator is initiated from Explorer, three command buttons are
active: Backup, Restore, and Verify.
When the IACC Database Administrator is initiated from the IACC window, only the backup
option is active, and the backup command is applied only to the currently open database.
Database restoration and verification can be executed only off-line; no user can be logged into the
target IACC database.

Figure 15-22. IACC Database Administration Window

Backing Up a Database
The backup procedure makes a copy of the complete IACC database and saves it to a user-speci-
fied location. You can save multiple backup copies and select from among them when you need to
restore the files. All changes made since the backup are eliminated.
Backups are automatically made each time you download.
To back up the currently open IACC database:
1. Choose Tools > Backup from the menu bar.
IACC opens the IACC Database Administrator dialog box, with only the Backup and
Exit buttons active.

419
B0700FE – Rev A 15. Managing IACC Databases

2. Click Backup.
The utility displays a warning that all editors are closed before the backup starts
(Figure 15-23).

Figure 15-23. Warning: Backup Closes All Editors

3. Click OK.
An Enter backup file dialog box (Figure 15-24) prompts you to enter the location and
name of the backup file. The default name for the backup file is the filename with the
current date and time, for example:
IACC_mmddyyyy_hhmm.bdb

Figure 15-24. Enter Backup File Dialog Box

420
15. Managing IACC Databases B0700FE – Rev A

4. Click Save to accept the default name and location, or use the controls in the dialog
box to enter a different name or location, and then click Save.
The Output window in the dialog box displays the backup functions as they are
performed, and error messages if there are problems. When the process is complete,
the utility displays a message box (Figure 15-25).

Figure 15-25. Backup Complete

5. Click OK to close the information box and exit the utility.

Restoring a Database
The Restore function overwrites the current database with a file that was created with the backup
function.
To restore a database:
1. Ensure that no one is logged into the target database.
If there is an active client, work is overwritten by the restore function.
2. Use Explorer to locate the utility in the executable folder:
...\IACC\bin\DbAdmin.exe
3. Double-click DbAdmin.exe to open the IACC Database Administrator window
(Figure 15-22).

421
B0700FE – Rev A 15. Managing IACC Databases

4. Click Restore.
The utility displays a dialog box in which you select the database to be restored
(Figure 15-26). The dialog box is similar to a standard Windows Open dialog box.

Figure 15-26. Selecting the Backup File

5. Use the dialog box controls to select the database to be restored, and click Open.
The utility displays the target directory, that is, the directory in which the original
IACC database files were located (Figure 15-27). If you select another location, the
Restore function does not work.

Figure 15-27. Select Destination Directory Dialog Box

422
15. Managing IACC Databases B0700FE – Rev A

6. Click Open.
If a user is connected to the target database, the utility displays a message box.
 Click No in the message box (Figure 15-28).
If you click Yes, IACC fails and data may be lost. Invoke Restore when there are
no clients connected or request that current users exit IACC before continuing.

Figure 15-28. Information Message: Users Are Connected

If the target directory already contains a valid database, Restore overwrites it with the
selected database. To prevent data loss, the utility prompts you to back up the
databases in the target directory (Figure 15-29).

Figure 15-29. Option to Back Up Files Currently in the Target Directory

7. Select Yes to back up the database using the default name and location, or click No to
skip the backup.
If you select Yes, the utility displays the Enter backup file dialog box (Figure 15-24) so
you can specify a filename and location.
The Output window displays the restore procedure, which includes both a verification
of the database to ensure that all pointers and references in that database are valid and
a database integrity check (Figure 15-30).

423
B0700FE – Rev A 15. Managing IACC Databases

Figure 15-30. Restore Complete

8. Click Exit when the Output window indicates that the target database volume has
been closed.

Verifying a Database
To verify any database independent of the Restore function:
1. Start the utility from Explorer and click Verify.
The utility displays a dialog box for you to select the database to be verified
(Figure 15-31).

Figure 15-31. Select Central Database Dialog Box

424
15. Managing IACC Databases B0700FE – Rev A

2. Use the dialog box controls to select the target and click Open.
The utility verifies that all pointers and references in the database are valid and runs
integrity checks on all the collections. The verification results are displayed in the
Output window (Figure 15-32).

Figure 15-32. Verification Complete

3. Click Exit when the output indicates that verification is complete.

425
B0700FE – Rev A 15. Managing IACC Databases

426
Appendix A. Glossary
Appearance Object Graphical representation of IACC objects used to configure process con-
trol hardware and software in graphical editors.

Attribute Category within a parameter to which a value is assigned.

Audit Trail Log file of security configuration changes providing a description of the
change along with the date, time, user, and system associated with the
change. Audit is enabled with the IACC Option dialog box and displayed
in its ListView.

Basic Coils Energize Coils, Write Not Coils, and Set (Latch) Coils.

Block Set of algorithms that perform a specific control task within the com-
pound structure. Blocks, structured text, and ladder logic are the basic
elements for building a control strategy. I/A Series control blocks are
predefined, however, you can program your own sequence blocks using
the High Level Batch Language.
Blocks are tailored for your specific process control application using sets
of variables and constants known as parameters.
To learn about the basic operation of blocks in your system, refer to
Integrated Control Blocks Concepts (B0193AW).

Branching Coils Master Control Relay Coils or Zone Control Logic Coils in ladder logic.

Bulk Generation Automatic generation of CSDs used to apply the parameter information
for inputs and outputs from a TagList to the format provided by one or
more CSTs.

Class Group of objects that are related in function and that have similar
parameters.

Code Block Holds segments of HLBL code in an ST Template.

Collection List of similar IACC objects that meet one of these criteria:
 Derived from a single parent object (such as parent or child object
definitions)
 Located under the same class of object in the system hierarchy
 Assigned to a single object (such as all blocks assigned to the same
CSD).

Combo Box Editable field that includes a pull-down list of predefined options. In some
combo boxes, you can specify one of the available options by typing the
name of the option in the box.

Compilation Converts a text input file into executable code.

427
B0700FE – Rev A Appendix A. Glossary

Compiler Software that converts a text input file into executable code.

Component Graphical primitive such as a line, text, or ellipse. A component is any

piece you can draw in a graphics-based editor. You can ascribe line color,
fill color, and position to a component.

Component Type The type is set for primitive components; for example, a rectangle compo-
nent is automatically assigned a type of “Rectangle.”

Composite A group of components that act as a single item showing all the character-
istics of the components with one exception: you cannot edit the vertices
of the individual shapes.

Compound Logical collection of blocks that perform a specific portion of the control
strategy in a control processor. Compounds can be used to represent Plant
Areas (all blocks used in a specific section of your plant), or simply a group
of blocks placed together for a specific purpose.

Control Points Points situated in the center and the perimeter of a graphic component for
a total of 8. Control points set the origin for spatial calculations such as
rotation and scaling.

Control Processor (CP) or Control Station

Processor that performs regulatory, logic, timing, sequential control, and
alarm detection and notification. The CP can be a single module or
fault-tolerant module. In IACC and this document, these terms often
refer to the range of products that can run control software, including
CPs, integrators, and workstations with control enabled.

Control Strategy Diagram (CSD)

Graphical representation of a specific portion of a control strategy that
shows the interconnections between blocks.

CSD Instance A CSD generated from a pre-existing CSD Template. Information may be
applied to a copy of a CSD Template to produce a unique CSD instance
either through bulk generation or by changes made in the CSD Editor.

CSD Template A CSD that displays a process or a part of a process that is used repeatedly
to configure your control strategy. A CSD Template contains a general
block and connection strategy which can be copied to produce multiple
CSD instances. Information from a TagList can be applied to a CSD Tem-
plate during bulk generation to produce a unique CSD instance. Alter-
nately, a CSD Template may be copied to form a CSD instance which is
then modified by you in the CSD Editor to produce a unique CSD
instance.

Counter Coils Up-Counter Coils or Down-Counter Coils.

Decision Point Point in an ST Template flowchart where a control question is asked.

428
Appendix A. Glossary B0700FE – Rev A

Drag and Drop Action performed when you select an object with the left mouse button
and then, keeping the left button pressed, you drag the object to a new
location on the screen. Once the object crosses over the top of a drop
target, the mouse cursor changes, alerting you that the object being
dragged can now be dropped by releasing the mouse button.

Drawing Collection of components, composites, appearance objects, and links that

show a complete system of graphical objects and their relationships.
Drawings are displayed in the Editor window for graphics-based editors.

Drawing Area Surface on which you can edit the diagram components, using the
graphics tools. Area contained in an Editor window.

Drop Cell Light gray rectangle, eight of which make up a ladder rung.

ECB Placeholder A generic ECB that represents input/output to the field in a CSD
Template. When the template is used in bulk generation to create or
modify CSDs, the ECB is updated with specific information from the
TagList.

Editor Permissions Access to specific IACC editors granted to user groups.

Filter Feature used by a Report Template along with scope nodes to narrow the
object list of the report. A Report Template filters select objects from
among those designated by its scope nodes.

Function Permissions
Access to a system-wide function such as importing and exporting granted
to a group of users.

Group Collection of IACC users with a certain set of permissions to various

aspects of IACC. Groups are used to control user access to IACC object
types, editors, and functions.

Handles Points in a component, represented by ( ) when the component is

selected. Handles allow you to identify which component is selected and
then scale or move the component.

High Level Batch Language (HLBL)

Structured text programming language used in I/A Series software.

IACC I/A Series Configuration Component.

Instance Wizard Utility for inserting HLBL code from an ST Template into the ST Code
Editor.

Instantiation Creates an instance of the object.

429
B0700FE – Rev A Appendix A. Glossary

Ladder Logic Symbolic representations of relay circuits. These symbols, consisting of

contacts, timers, counters, and coils, are used to build rungs. The rungs
are built into ladders. Ladder logic capability is a configurable option in
digital Fieldbus Modules, where the ladder diagrams are processed.

List Box Any type of box containing a list of options that you can select. The list
box has a specific size, however, if it contains more options than can be
shown at once, a scroll bar in the right side of the box allows you to
display the other options. You cannot type a selection in a list box.

ListView Tabular view designed to display a list of associations to a specific class or

collection of IACC objects.

Macro A text string in a Report Template that is replaced by some predefined text
or graphic when the template is used to print an object from IACC. Mac-
ros are typed within square brackets on a Sheet Template, and then are
evaluated by IACC when that sheet is used to print the object from IACC.

Menu Bar Provides access to common IACC functions, such as printing and specific
editor functions, such as compilation of code.

Modifier Block Block definition that overrides any exposed matching parameters in blocks
to which the Modifier block is attached.

Object Basic building block used by IACC to set up your control strategy.
Includes any item displayed in the Project Navigator, such as a control
block, compound, or control processor.

Object Definition IACC object from which other IACC objects derive their structure and
default parameters.

Object-type Permissions
Access granted to groups to modify specific IACC objects.

Off-Sheet Connection
Connection made between two blocks in two different CSDs.

Palette Group of IACC object instances that are used to create similar object
instances quickly in the configuration process.

Palette (Ladder) A list of all the available contacts and coils that can be inserted in a ladder.
It is not a modifiable palette.

Parameter Group Group of parameters assigned to a specific set of IACC objects. All objects
have the All, Standard, and Support parameter groups, but can have addi-
tional user-configured groups.

Parent Object IACC object to which the displayed object is assigned, or from which the
displayed object is derived.

430
Appendix A. Glossary B0700FE – Rev A

Plant Area A user-defined object that enables organization of control objects by plant
location, process, or other structure.

PLB Ladder Editor Graphic Editor used to construct a ladder diagram to be executed in a
digital Fieldbus Module (FBM). It provides basic graphical editing
capabilities in a structured environment necessary to complete the task.
Different logic elements (contacts, coils, timers, counters, and so forth) are
available to construct the ladder. Line connections can also be easily made
between logic elements to complete a diagram.

Power Rails Run vertically on either side of a ladder. The power rails expand
automatically as new rows or rungs are added to the ladder.

Preferences User-controlled settings that determine the specific behavior and

appearance of the editor.

Primary Object IACC object for which an editor is opened.

Print Specification Set of variables that specify the page size and orientation for Sheet
Templates in reports. A print specification is created every time you
specify a printing size that has not been used before with the template.

Pull-down List Menu associated with a specific field. Click the to view the list.

Report Format in which information about an IACC object is printed. For most
objects, reports provide a complete list of the object parameters and their
associated values in a spreadsheet form. A CSD report is a graphical
representation displaying the blocks and block connections configured for
the selected CSD, similar to the display in the CSD Editor. You can print
reports for individual objects or set up Report Templates for printing mul-
tiple objects.

Report Template Object designed to create a set of standardized reports for a set of IACC
objects that fit certain established criteria. Each Report Template has a sin-
gle Sheet Template and print specification assigned to it. All the reports
generated from the template keep a consistent format.

Re-usable Component
A component that includes standard and derived block definitions, code
items, and various templates from which you can create downloadable
control objects. You access reusable components in the System tab of the
Project Navigator or the Palette window. You create an instance of the
re-usable component by dragging the object into an editor or by invoking
a command for the object’s pop-up menu. You can also create a re-usable
component by dragging an object such a block instance into a palette.

Right-click Press the right mouse button while the cursor is on an object to display a
pop-up or context menu pertaining to the object.

431
B0700FE – Rev A Appendix A. Glossary

Scope Node Data item used by a Report Template along with filters to narrow the
object list of a report. When a scope node is added to a Report Template,
all the objects under the scope node in the System Hierarchy are added to
the Report Template object list, before the template uses its filters to nar-
row the list.

Security Configuration that controls access to the various sections of the IACC
software through the setting of editor, function, object-type, and system-
wide permissions for groups of users.

Sheet Template Specifications for the background of printouts of Editor window contents.
Includes borders, logo, background colors and markers for titles.

Simple CSD Control strategy diagram built in the CSD Editor, which is a graphical
representation of a specific portion of a control strategy that shows the
interconnections between blocks. A Simple CSD is not an instance of a
CSD Template and, therefore, does not inherit changes made to the
template.

Special Purpose Coils

Initialization, Communication Fail, Fail-Safe and Power Fail Coils.

Spinner Box Text box with up and down arrows that you select to move through a set
of fixed options. Also, you can type a valid option in the box to select it.

Structured Text (ST)

Group of languages with which user-created HBLB programs are written.

ST Template Pattern of code blocks that contain HLBL substitution and control
questions used to standardize HLBL coding methods.

Substitution Question
A fill-in-the-blank question in an ST Code block.

Syntax Structure of the input language. The syntax rules determine whether the
input is a valid subset of the compiler’s input language. Structured Text
has specific syntax.

System-wide Permissions
Security setups that control whether user groups have access to certain
system-wide functions, such as importing and exporting.

Tag Information about an I/O point of a process control system.

Tag Data Propagation

Series of dialog boxes for configuring propagation preferences for
parameters of user-defined tags.

TagList List of I/O points in a process control system and related data for con-
struction and update of CSDs.

432
Appendix A. Glossary B0700FE – Rev A

Tag Type Also called a tag definition. A predefined or user-defined category of tags
that can be used in a TagList. The purpose of tag types is to create tem-
plates that provide a set of parameters for a tag appropriate for working on
different projects or engineering environments.

Text Box Drawing component displays as a rectangular box in which you can type
text. If the box already contains text, you can select the default text, or
delete it and type new text.

Timer Coils Retentive On-delay Timer, Retentive Off-delay Timer, Non-retentive

On-delay Timer, and Non-retentive Off-delay Timer.

Title Bar Displays IACC, the name of the IACC editor currently open in the Editor
window, and the name of the primary object being edited.

Toolbar Customizable set of buttons that provide shortcuts to specific functions

available in the menu bar.

Type Name of the object class.

User Individual Assigned a username and password in IACC. Users are assigned
to groups which define the users’ access to areas of IACC.

433
B0700FE – Rev A Appendix A. Glossary

434
Appendix B. Flow chart for
Converting ICC SaveAll Diskette to
IACC Database Format
This appendix provides the flow chart for Converting ICC SaveAll Diskette to IACC Database
Format.

NOTE
The flow chart is only intended to provide a guide for the preparation work that is
required before importing an ICC SaveAll to IACC. The actual convert process
should follow the guidelines and steps as outlined in“Importing Save/SaveAll Data”
on page 412

Figure 15-33. Flow chart for converting ICC SaveAll diskette to IACC Database format

435
B0700FE – Rev A Appendix B. Flow chart for Converting ICC SaveAll Diskette

 Using the LOOPID method results in a CSD (loop drawing) per unique
LOOPID. All blocks containing that unique ID get assigned to the newly created
CSD.
 Using the COMPOUND method results in a CSD (loop drawing) per unique
COMPOUND. All blocks contained in the COMPOUND are in the newly cre-
ated CSD.

436
Appendix C. Executing the IACC
Utility ArchExport.exe
This appendix provides information for executing the IACC Utility ArchExport.exe.

NOTE
The following information is for IEE Users only.

ArchExport.exe exports IACC database information into one or more XML files for the purpose
of import into Infusion Engineering Environment (IEE).The ArchExport.exe is located in
<IACC_Install_Directory>/bin.
For example, to export information from an IACC system, invoke ArchExport with the com-
mand;
ArchExport <myExportName>.XML
For an IACC configuration containing no FF objects or sequence block text objects, a single file
named …\<myExportName>.XML is the only output. But if the IACC configuration contains
one or more FF objects, a new folder named …\<myExportName>_files\ is also created, located
in the same folder as the ‘top-level’ file ‘myExportName>.XML’. Then for every FF object <myF-
FObject> found (whether base template, derived template, or device instance), this new folder also
contains a file named ‘<myFFObject>’.XML. This ‘top-level’-file / folder pair should always be
kept together in the same folder, and if one is renamed, the other must also be renamed to retain
functionality.
Similarly, if any sequence blocks are found to have required text objects, a folder is created that is
named …\<myExportName>_TextObjs\ and any text object found is placed in this folder. IACC
Text objects are usually used as include files in IACC sequence blocks and are needed to recompile
the IEE strategy sequence source code.

437
B0700FE – Rev A Appendix C. Executing the IACC Utility ArchExport.exe

438
Appendix D. 100 Series Migration
Support
Equipment Control Block Migration Supported By IACC
Before performing the migration with IACC, you must be aware of the types of migrations which
IACC supports. Table D-1 lists the migration mappings supported by IACC. The ECBs of any
100 Series FBMs which do not have an equivalent 200 Series FBM will remain mapped to their
original 100 Series FBM during the migration process.

Table D-1. ECB Conversion Mappings

NEW NEW
OLD FBM OLD FBM & ECB &
& SWTY OLD HWTYP SWTY NEW
HWTYPE PE EXTYPE E PE EXTYPE CHILD
ECB ECBs
1 1 1 0 201 1 0
1 2/36 1 0 202 1 0
1 3/33 1 0 203 1 0
2 4 2 0 204 2 0
2 5 2 0 208 2 0
4 6 4 0 206 4 0
5 7/8/20/24 5 0/12/13/21/ 217 5 0
25
5 7/8/20/24 5 14/15/16/27 219 5 0
/42
5 9/10/11/26/ 5 0/14/15/16/ 239 5 0
41 27/42
5 9/10/11/26/ 5 12/13/21/25 238 5 0
41
6 7/8/20/24 6 0/12/13/21/ 217 6 0
25
7 7/8/20/24 7 0/12/13/21/ 217 7 0
25
8 7/8/20/24 8 0/12/13/21/ 217 8 0
25
8 7/8/20/24 8 14/15/16/27 219 8 0
/42
8 9/10/11/26/ 8 0/14/15/16/ 239 8 0
41 27/42

439
B0700FE – Rev A Appendix D. 100 Series Migration Support

Table D-1. ECB Conversion Mappings

NEW NEW
OLD FBM OLD FBM & ECB &
& SWTY OLD HWTYP SWTY NEW
HWTYPE PE EXTYPE E PE EXTYPE CHILD
ECB ECBs
8 9/10/11/26/ 8 12/13/21/25 238 8 0
41
9 17 9 0 227 9 0
12 18 12 0 243 12 0 ECB18
12 43 37 0 243 12 0 ECB18
23 39 23 0 243 23 0 ECB18
23 44 38 0 243 23 0 ECB18
34 17 34 0 227 34 0
36 17 36 0 227 36 0
38R FBM46- 49 0 246 ECB38 0 ECB18
HWT98 R-49
52 4 52 0 204 52 0
52 17 52 0 227 52 0
53 37 53 0 237 53 0
73 43 73 0 243 73 0 ECB18,
74

Legacy CP/CP270 Configuration Migration (Import)

Various types/combinations of CP Database Configurations can be migrated. The procedure for
importing and Migration of the CP Database Configurations is provided below:

Multiple Legacy CP30/40/60 Combined into CP270 (FCP/ZCP)

Proceed as follows:
1. Create a CP 270 Station
2. Export the First Legacy CP 30/40/60 Save-all to the CP270 created as in step 1.
3. Import the Second Legacy CP 30/40/60 Save-all to the same CP270 created as in step
1.
4. Resolve any duplicate FBM names.
5. It is recommended that you validate the database before performing Migration.
6. Perform CP270 level Migration.

Single Legacy CP's 30AB/40AB/60 to FCP270/ZCP270

1. Create a CP 270 Station
2. Import Legacy CP 30/40/60 Save-all to the CP270 created in step 1.
3. Resolve any duplicate FBM names.

440
Appendix D. 100 Series Migration Support B0700FE – Rev A

4. It is recommended that you validate the database before performing Migration (rec-
ommendation)
5. Perform CP270 level Migration.

100 Series FBMs in FCP270 to 200 Series FBMs in CP270

1. Import/use the existing FCP270 database.
2. Resolve any duplicate FBM names.
3. It is recommended that you validate the database before performing Migration
4. Perform CP270 level Migration.

100 Series FBMs in ZCP270 to 200 Series FBMs in ZCP270

1. Import/use the existing ZCP270 database.
2. Resolve any duplicate FBM names.
3. It is recommended that you validate the database before performing Migration.
4. Perform CP270 level Migration.

441
B0700FE – Rev A Appendix D. 100 Series Migration Support

442
Appendix E. IACC 2.5
Enhancements

Configuration and New Station Types supported by

IACC 2.5
IACC 2.5 supports configuration of new hardware station types of Windows 7 (P92) and Sever
2008 R2 (P91) as listed in Table E-1. WSTA70 and WSVR70 station types can be configured
only to Mesh network and will be able to host the CPs that are hosted by AW70P station type.

Packages Supported by IACC 2.5

In addition to the existing software packages ASCA7, AFSIM7, AICC7, AMSGM7, ANSOF7,
ASMDW7, and ASMON7, the new station types supports three new software packages, namely,
IAMESH, IASVCS, IACTRL, and ADDISP Table E-1 shows the software packages supported by
WSTA70 and WSVR70 station types and its default availability.

Table E-1. Software Packages Assignable to WSTA70/WSVR70

Package Name Description Default State

ACSA7 Com Sum Access Unassigned
ADDISP Default Displays Assigned
AICC7 Int Ctl Config Unassigned
AMSGM7 Message Manager Unassigned
ANSOF7 FoxPanels SW Annunciator Unassigned
ASMDW7 SMDH Assigned
ASMON7 System Monitor Unassigned
IACTRL Controller Support Unassigned
IAMESH Mesh Connectivity Assigned
IASVCS I/A Series and APIs Assigned

Workstation installations can be streamlined to load the necessary components. The distinction
between Application Workstations and Workstation Processors is now simply a matter of what
components are assigned. The Figure E-1 and Figure E-2 shows the configuration of WSTA70 or
WSVR70 as AW and WP.

443
B0700FE – Rev A Appendix E. IACC 2.5 Enhancements

Figure E-1. Software Package Availability for AW

Figure E-2. Software Package Availability for WP

Support for Serial or Parallel port peripherals

WSTA70 or WSVR70 does not support any serial or parallel port peripherals other than GCIO.
Instead, new peripherals such as USBANN (USB Annunciator Panel/Keyboard) and PRTUSB
(USB Printer) can be configured to these stations.

Support for Network Printers

IACC2.5 supports configuration of network printers on Mesh network. Network printers are
considered as a station type which can be hosted by WSTA70 or WSVR70 station types. Like any
other station type, Network printers can be configured to system monitor.

444
Appendix E. IACC 2.5 Enhancements B0700FE – Rev A

Support for USB Printers

IACC 2.5 supports configuration of USB printers as a peripheral to station types WSTA70 and
WSVR70. Maximum number of USB printers that can be attached to a station is restricted to 3.
Station types WSTA70 and WSVR70 will not support configuration of serial or parallel port
printer types.

445
B0700FE – Rev A Appendix E. IACC 2.5 Enhancements

446
Index

21 CFR Part 11
configuration change tracking 322
IACC support 54
268Kbps Fieldbus Modules 114
2Mbps Fieldbus Modules 119

A
Address connections 166
Address Translation Station. See “ATS.”
AIM*API
setup for ALDs 331
AIM*Historian
recording ALD actions 334
ALDs
connection to AIM*Historian 334
connection to Operator Action Journal (OAJ) 334
server setup 331
setting ALD options 333
setting values in the CP 335
toolbar and menu commands 329
trending 335
updating the IACC database 335
alpha-sorting objects in the Project Navigator 57
Animated Live Diagram Options dialog box
as used for sourcing live data 334
Animated Loop Drawings. See ALDs.
Appearance Object Editor 43
ArchExport 437
ArchExport.exe 437
assigning
CSDs to a Plant Area 164
field devices and interface modules 129
hardware objects 127
peripherals 129
software hosts 131
Assigning a CSD to a compound 292
ATS
configuring an ATS as a LAN Interface replacement 103
configuring an ATS to extend a Nodebus with The Mesh control network 104
audit trail for changes to the security settings 360
Available Formats dialog box 406

447
B0700FE – Rev A Index

B
backup 419
basic processing cycle (BPC)
defined 188
scan overload 192
block connections
changing the appearance of a connection line 171
blocks
adding a formula for a parameter value 180
and compounds 6
assigning to a compound 161
connecting two parameters in a CSD 68
connections 8, 165
CP processing load 9
definition 145
derived blocks and the Definition Editor 183
deriving new block definitions 183
editing logic blocks using the Properties dialog box 181
naming rules 8
phasing cautions and guidelines 192
phasing, defined 190
processing 188
Properties dialog box 178
sequencing 81
showing parameters in a CSD 170
tag to block propagation of parameter values 276
viewing block status 337
bulk generation
generating CSDs from a Plant Area 149
generating CSDs from a TagList 272
bus A and bus B 110
buttons 18

C
checkpointing
CP checkpointing 325
Disable Checkpointing in the IACC Options dialog box 53
code blocks
connections in an ST template 220
creating 214
coexistence with legacy configurators 5
combining fiber optic and LAN cabling 101
commissioning 327
Commit diskette 132
Comparison Utility
Comparison Utility tab 343
defined 343
with upload to the checkpoint file 343
compilation of HLBL code 229

448
Index B0700FE – Rev A

Components branch in the Project Navigator 19

compound processor 188
compounds
and blocks 6
assigning to a CP 9, 164
configuration rules 9
creating a compound 161
naming rules 8
processing 188
sequencing 82
structure 6
compressing work files on a host workstation 325
Configuration branch in the Project Navigator 20
Configure FoxView Options dialog box 292
connecting
I/O blocks to the field 79
inputs and outputs in an ST template 219
objects in an ST template 219
Connection Dialog box 42
connections 8
continuous control 6
control download 312
Control Question Properties dialog box 216
Control Question Selection dialog box 218
control strategy 6
CP
assigning compounds to a CP 164
block processing load 9
checkpointing 325
creating
268Kbps FBMs for the CP60 117
an I/A Series V8.x System 95
code blocks 214
communications devices 111
CSD Template instance 149
decision blocks 215
decision properties 215
DIN rail mounted FBMs for the CP60 or ZCP270 121
DIN rail mounted FBMs for the FCP270 122
FBMs from the Fieldbus Isolator (FBI) 116
I/A Series control blocks 66
loops in an ST template 222
network component directly from a Configuration 101
network component directly from an object 101
network component from a LAN 102
node without a LAN 102
The Mesh Control Network 95
CSD
assigning to a compound 292
CSD Templates 26

449
B0700FE – Rev A Index

adding ECB placeholders 176

and ECB placeholders 176
converting a CSD template to a simple CSD 148
converting a CSD to a CSD Template 155
converting a template to a simple CSD 152
creating a template 155
creating an instance 149
description 143
ECB placeholders 174
instances 143
CSDs
adding blocks 159
and compounds 144
and Plant Areas 147
assigning a CSD to a Plant Area 164
assigning CSDs to a Plant Area 165
converting a CSD template to a simple CSD 148
converting a CSD to a CSD Template 155
converting a template to a simple CSD 152
creating a simple CSD 148
creating an instance from a template 149
CSD Editor 8, 24, 158
definition of a simple CSD 143
deleting 154
deleting blocks 159
instance of a CSD Template 143
moving and placing blocks 160
off-sheet connections 167
renaming 153
showing parameters 170
custom blocks 183

D
database
Find in Database command 12
import/export 12
Decision point
description 215
name 215
properties 215
default names 64
Definition Editor 40
and modifiers 195
deriving new block definitions 183
formulas 180
dialog boxes
Animated Live Diagram Options 334
Assign Host 132

450
Index B0700FE – Rev A

Available Formats (Import) 406

Commit Hardware/Software Configuration 135
Create Comm Device 111
Create Fieldbus Modules 121, 122
Create Peripherals 108
Create Software 125
Create Stations 105, 107
Create Stations, variations 105
Create Switches/Hubs 101
FoxView Options 328
Hardware/Software Commit 136
Import File Name 407
Instance Wizard 208
Media Distribution 136
Properties dialog box 178
Validate Hardware/Software Configuration 133
Validation Checks 135, 136
DIN rail mounted FBMs 109, 120
displays 281, 283
creating 285
downloading 298
importing 300
validating 297
document overview xxvi
documentation 84
download function 33
download status
synchronizing CP and IACC databases 340
Downloading
enabling IACC downloads to a control station 307
downloading
compounds and blocks 312
database 82
from a CP object 82
from a CSD 82
individual compounds 82
dragging and dropping 25

E
ECB placeholders 174, 176
Edit Vertices button 171
Editor tabs 17
Editor window 17
editors
CSD Editor 143, 158
Execution Editor 186
Security Editor 46
ST Template Editor 211
error reporting 54

451
B0700FE – Rev A Index

Ethernet
Ethernet Fieldbus Isolators 112
Ethernet-based node 103
Execution Editor
description 31
modifying compound and block execution order 186
expansion FBMs 117
export
formats 401
IACC Format 401
Save/SaveAll 403
TagLists 267
Export TagList Agent 267
extended Fieldbus 109

F
FBI (Fieldbus Isolator) 109
FBI10 (Ethernet Fieldbus Isolator) 109
FBMs
268Kbps Fieldbus Modules 114
2Mbps Fieldbus Modules 119
adding FBMs for I/A Series replacement I/O modules 124
attaching field device to an FBM 122
expansion modules 117
module types 113
renaming modules that have been downloaded 339
FCM10 (Fieldbus Communication Module) 109
FCM2 (Fieldbus Communication Module) 110
FCP270
adding FBMs 122
field connections 79
Field Device System Integrators 122
filters
in report templates 371
Find in Database search 12
Formulas in Definition Editor 180
formulas in the Properties dialog box 180
Foundation fieldbus devices 122
FoxAPI
setup for ALDs 331
Foxboro IA tag type
parameters 253
FoxCAE
and IACC 5
FoxCTS
authorizing access to download information 324
IACC support 54
set up connection to IACC 322
FoxDraw 48, 281, 285, 297, 298, 300

452
Index B0700FE – Rev A

IACC interface 282

FoxSFC
sequential function charts 203
starting FoxSFC from IACC 204
FoxView options 292
FoxView Options dialog box 328
FoxView toolbar 328
FSIM(Foxboro Simulation) 54

G
galvanic isolation 109
Global Customer Support Center xxviii
group
Administrator group 349, 350
definition 349
Group Editor 354

H
Hardware Editor 36
HART devices 122
Help 50
High Level Batch Language (HLBL) 10
compilation 229

I
I/A Series V8.x System
system configuration 95
IA Mod Traverse Blocks. See modifiers.
IA Mod Traverse CSDs and Blocks. See modifiers.
IA Modifiers. See modifiers.
IACC 437
IACC and legacy configurators 5
IACC block function types 145
IACC Database Administrator 419
IACC Format
export 401
exporting TagLists 267
import 406
IACC Help 50
IACC Options dialog box 50
Error Reporting tab 54
Live Data Settings 60
IACC Safeguard program 307
IACC Settings
branch in the Project Navigator 19
IACC window 16
IACC-CP file 307
ICC and IACC 5

453
B0700FE – Rev A Index

ida file extension 401

IEE 405
import
displays 300
formats 405
IACC Format 406
Save/SaveAll Data 412
SysDEF 92
TagList 258
Import File Name dialog box 407
import functions 405
import/export database 12, 84
Infusion 405
initialize CP 347
input parameters 24
insert a substitution question 225
installation parameters 133
Instance Wizard 225
dialog box 208
inserting a template into code 207

L
ladder logic 10, 30
LAN interface configurations 100
LI replacement mode for an ATS 103
Library branch in the Project Navigator 19
linking decision properties 215
ListView
description 38
security-related ListViews 360
Live Data Settings in the IACC Options dialog box 60
loading calculations 32
Lock Vertices button 171
logic blocks 181

M
macros in a sheet template 366
maximum FBMs 109
media distribution diskette #10091 77
menu bar 17
Mesh
adding switches to The Mesh Control Network 96
creating an instance of the Mesh Control Network 95
Migration FBMs 124
Miscellaneous tab in the IACC Options dialog box 57
Modbus 122
modifiers
applying an IA Modifier 199
creating an IA Modifier 196

454
Index B0700FE – Rev A

modifier types defined 194

parameter groups 195
using the IA Mod Traverse Blocks modifier type 201
using the IA Mod Traverse CSDs and Blocks modifier type 202
Moore APACS replacement modules 124
moving H1 devices 339
multiple choice decision points in an ST template 221

N
names
default names in IACC 64
naming conventions 8
nested Plant Areas 21
Network
centralized networks 100
components 101
creating 100
token local area network 100
topologies 100
Network tab 20
node
creating a node from a network component 102
Nodebus
interfacing a V6.x and V7.x Nodebus with The Mesh control network (V8.x) 103
Nodebus extension for an ATS 104
Not Downloaded state 339

O
object-type permissions 357
off-sheet connections 167
optional hardware 91
output parameters 24
Output window 17, 132
Overrun 192
overview of system configuration 87

P
packages
software 12
Palette window 17
palettes
structured text 212
Parameter Editor 38
parameters
in a TagList 253
in blocks 145
input 24
output 24

455
B0700FE – Rev A Index

sink 25
source 25
parent object 127
passwords 349
period 190
PERIOD parameter 189
permissions
system-wide 359
phase 190
Plant Areas 21
and CSDs 147
assigning CSDs to a Plant Area 164, 165
creating a Plant Area 147
deleting 148
Plant tab 21
print preview 365
printing 84
printing reports 363
printing to a file 365
Process and instrumentation (P&I) drawings 88
processing
blocks 188
compounds 188
PROFIBUS 122
programmable logic block (PLB) 10, 30
Project Navigator 17, 18
display options 57
Properties dialog box 36, 178
adding a formula for a parameter value 180

Q
question type in an ST template
boolean 216
multiple choice 216
replicate 217
Quick View
FoxView toolbar 328
Quick View displays 327

R
reconcile diskette 132, 138
reconciling the installed configuration with the IACC database 138
Redrawing block connections lines 171
redundant connection
FCM 110
Remove from CP 339
renaming objects in IACC 64
Replicate 217
replicate decision points in an ST template 222

456
Index B0700FE – Rev A

Report Manager branch in the Project Navigator 19

Report Template Editor 43
Category tab 382
Parenthesis tab 383
State tab 380
Type tab 381
report templates
classes 371
definitions 373
instances 373
Object List dialog box 375
reports 363
overview 370
request for comments xxviii
resolving FoxDraw symbol aliases 294
restoring a database 421
revision information xxv
rung set 235

S
Save/SaveAll
export 403
import 412
scan overload 192
scan period 189
scope nodes 371
adding to Report Templates 373
configurable object types 372
search 12
security
audit trail 360
configuring security 350
group defined 349
Group Editor 354
IACC and FoxCTS log-in accounts 324
ListViews 360
object-type permissions 357
overview 349
passwords 349
permissions, system-wide 359
User Editor 349, 351
security audit trail
IACC Options dialog box 52
Security branch in the Project Navigator 19
Security Editors 46
sequence blocks
bulk compilation 230
IACC configuration tools 203
sequential control 6

457
B0700FE – Rev A Index

server setup for ALDs 331

Sheet Editor 45
sheet templates 45, 365
default sheet templates 366
macros 366
Sheets branch in the Project Navigator 20
Shrink command 325
simple CSDs 143
software
packages 12
Software Editor 37
description column 139
host column 139
ID column 139
install state column 140
package column 139
software packages 12
ST code
compiling 229
ST Code Editor description 27
ST code item definition 212
ST code item in an ST template 211
ST control questions 212
ST decision in an ST template 212
ST substitution questions 212
ST Template Editor 28, 211
ST templates
creating 212
inserting in a sequence block 207
Instance Wizard 207
modifying 213
validation 223
with reference in place 209
starting IACC 13
stations supported in IACC 104
status bar 17
structured text. See ST code.
Substitution Properties dialog box 228
Substitution question
add, edit, delete 227
substitution question 225
Substitution Question Manager dialog box 227
switches on the Mesh Control Network 96
Synch To CP 341
Synch Utility 340
SysDEF Export disk 92
system configuration 87, 89
System Definition (SysDEF)
and IACC 5
System Options tab in the IACC Options dialog box 52

458
Index B0700FE – Rev A

System tab 19
system-wide permissions 359
system-wide security
IACC Option dialog box 52

T
tag data propagation
procedure 276
tag types 246, 253
TagList Editor 26
colors and symbols 249
menus and toolbars 249
pop-up menus 251
tabbed sections 248
tag data propagation procedure 276
tag parameters 253
TagLists 245
and bulk generation of CSDs 272
exporting 267
tags 245
technical assistance xxviii
The Mesh Control Network
interfacing with a V6.x and 7.x Nodebus network 103
title bar 17
toolbars 17
overview 18
Toolbars dialog box 46
tracking changes made to IACC security settings 52
tracking configuration changes 54
trend displays from an ALD 335

U
unparented hardware objects 111
Upload and Compare to CP command 343
User Editor 349, 351
users
administrator 349
utilities 11
Audit Trail 49
Backup 49
error reporting 49
Export 49
Find in Database 49
Import 49
Synch to CP 340
Where Used 49

459
B0700FE – Rev A Index

V
validate 223
hardware connectivity 133
installation parameters 133
software requirements 133
ST template 223
validation 33
validation checks
for system configurations 136
value propagation connections 166
verifying a database 424

W
Westinghouse WPDF replacement modules 124
what’s new in Version 2.0 xxv
Where Used search 12
Workspaces branch in the Project Navigator 19

Y
Y-Module FBMs. See 268Kbps Fieldbus Modules

460
Index B0700FE – Rev A

461
Invensys Operations Management
5601 Granite Parkway Suite 1000
Plano, TX 75024
United States of America
http://www.iom.invensys.com

Global Customer Support

Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424 or contact your
local Invensys representative.
Website: http://support.ips.invensys.com