IAS Object Manager GNG Started Guide PDF
IAS Object Manager GNG Started Guide PDF
The text and screen shots in this document are compatible with Workbench Version 8.4.0 and subsequent releases. If you are running a previous
version, please contact Technical Support.
Object Manager Getting Started Guide 3
Contents
Section 1 – Introduction.....................................................................................................................................4
SCOPE ............................................................................................................................................................... 5
INTENDED READERS ........................................................................................................................................... 5
ACCESSING ADDITIONAL HELP ............................................................................................................................ 5
Section 2 – Installation.......................................................................................................................................6
PRE-INSTALLATION INFORMATION........................................................................................................................ 6
INSTALLING THE IAS OBJECT MANAGER .............................................................................................................. 7
POST-INSTALLATION ACTIVITIES ........................................................................................................................ 12
Configuring the Universal Server for IAS Communication ......................................................................... 12
Creating and Deploying a Galaxy Repository and Platform....................................................................... 14
Linking the IAS Configuration..................................................................................................................... 21
Section 3 – Tutorial ..........................................................................................................................................29
CREATING OBJECTS ......................................................................................................................................... 29
LINKING OBJECTS TO SMARTSYMBOLS .............................................................................................................. 37
Section 4 – Troubleshooting ...........................................................................................................................46
Section 5 – Conclusion ....................................................................................................................................47
Section 6 – Additional Information .................................................................................................................48
Glossary ............................................................................................................................................................49
Section 1 – Introduction
The PAC8000 Control System provides a fully integrated, open solution for process control strategy
development, discrete automation, SIL2 safety applications, and process visualization. The process engineer
is supplied with the tools to design, implement, document, and maintain a process control system using
advanced control strategies or the IEC 61131-3 programming languages. The safety engineer is similarly
supplied with the tools to design, implement, document, and maintain a safety shutdown or fire and gas
system using a subset of IEC61131-3 programming languages.
The PAC8000 Control System consists of a number of open system components including:
Workbench – an integrated project development environment that centralizes and coordinates project
engineering, including instrument index, control strategies (process and discrete), process
visualization (operating faceplates and SmartSymbols), history (alarming and trending), and project
management.
HMI - components for the Operator Interface (HMI), plant historian, and batch recipe management.
Control Platform – a rugged, field-mountable system consisting of controllers (with redundancy) and
both 800 Process IO and SafetyNet (SIL2) systems.
Data is entered in the Workbench and can then be used in the HMI, Historian, and the Batch Management
System. Entering the data in one place streamlines engineering efforts by eliminating duplication of manual
tasks.
The IAS Object Manager coordinates creating, modifying, deleting, and deploying objects between the
Workbench and Industrial Application Server. When an IO or strategy compilation is performed in the
Workbench, objects are automatically created or modified, as necessary, in Industrial Application Server.
Since historization is an attribute of the object, the mechanism also marks the data to be recorded in InSQL.
When the strategy is downloaded to the controller, the appropriate objects are deployed and objects that are
no longer needed are deleted. To speed graphical development, a set of SmartSymbols provides
visualization for the objects created by the IAS Object Manager Configuration tool.
Scope
The intent of this Getting Started Guide is to provide assistance for installing the IAS Object Manager, linking
the Object Manager to various system components (Galaxy Repository node, development node, and InSQL
Server node), and using the Object Manager to generate certain objects and display the data associated with
these objects using SmartSymbols.
This Getting Started Guide assumes familiarity with the Workbench, Industrial Application Server, InSQL
Server, and SmartSymbols.
Intended Readers
The Getting Started Guide is intended for those users who are:
• Installing the IAS Object Manager for the first time
• Upgrading an existing installation of the IAS Object Manager
• Learning how to use the IAS Object Manager
Section 2 – Installation
This section provides an overview for installing the IAS Object Manager.
Pre-Installation Information
Before installing the IAS Object Manager, please ensure the following:
• Wonderware’s Industrial Application Server Version 3.0 Patch 1 or later and its development
components are already installed.
• If Industrial SQL Server was installed as a standalone application, ensure that Mixed Mode
(Windows Authentication and SQL Server Authentication) was selected in the Authentication
Mode dialog box and that a password was specifed.
• The Workbench Version 7.4.2 SP2 or later is installed on the node.
• InTouch Version 9.5 or later is installed.
Note: If any of these prerequisites are not met, the installation program may abort.
3. The Options screen appears. Select the Additional Programs option and click Go.
Note: The text and screen shots in this document are compatible with
Workbench Version 8.3.0 and subsequent releases. Version x.x.x on the
screen shots refers to the current version number of the product that is being
installed.
4. The Additional Programs screen appears. Select the IAS Object Manager option and click Go.
5. The IAS Object Manager – InstallShield Wizard Welcome screen appears. Click Next to continue.
6. The License Agreement screen appears. Review the License Agreement and select the I accept the
terms in the license agreement option. Click Next to continue.
7. The Customer Information screen appears. Specify the User Name, Organization, and for whom this
application is installed. Click Next to continue.
8. The Setup Type screen appears. Select the appropriate installation type.
Complete – To install the IAS Object Manager on the C drive, select the Complete option and click Next
to continue. Proceed to step 9 in this section.
Custom – To install the IAS Object Manager to a location other than the C drive, select the Custom
option and click Next. Proceed to step a, below.
b. Select the desired location for installation from the Change Current Destination Folder screen
and click OK.
c. The Custom Setup screen appears again. Click Next to continue with the installation.
11. When the installation is complete, the IAS Object Manager InstallShield Wizard Completed screen
appears. Click Finish to complete the installation.
Note: The IAS Configurator must be run before IAS objects can be created by the Object
Generator. Ensure that the option to automatically launch the IAS Configurator is selected.
Post-Installation Activities
2. The Change Network Account dialog appears. Make a note of the User Name (in this example, it is
Administrator) and click Cancel to close the dialog.
3. Open the Universal Server (Start | Programs | Standard Automation Products | Universal Server
Configuration).
4. Start the Server and expand the Project Explorer tree. Right-click the Configuration folder and click
Edit Configuration. Select the Security Accounts tab.
5. If your user name from the previous step is not included in the list on the left, add it in the User Name
field. Select all permissions, click Add User and close the Universal Server.
Note: When a galaxy is created it maintains the locale ID of the machine it was created on. This affects the
Object Manager since some attributes are defined as International Strings. If the locale ID of the galaxy does
not match the locale ID of the machine you are working with you can do one of two things.
• You can change the locale of your machine to match
or
• You can specify the locale ID for the ObjectManager to use (recommended approach). To specify
the locale ID for the Object Manger:
1. Define a string value in HKEY_LOCAL_MACHINE\SOFTWARE\Proficy\8000\Control
Center\Utilities\IAS Object Manager and name the string value GalaxyLocaleID.
2. Enter the desired numeric locale ID in decimal form. For example, use 1033 for English -
United States or 2057 for English - United Kingdom. Please refer to the following table for a
complete list.
http://msdn2.microsoft.com/en-us/library/0h88fahh.aspx
1. From the Start menu, select Program Files | Wonderware | ArchestrA IDE to launch the ArchestrA
IDE.
2. The Connect to Galaxy screen appears. If you are creating a new Galaxy, click New Galaxy.
3. The New Galaxy screen appears. Specify the Galaxy name and select Default Galaxy from the Galaxy
type drop down list. Click Create.
4. The creation process takes several minutes. Once the Galaxy is successfully created, click Close on the
Create Galaxy screen.
5. Select the Galaxy to which you wish to connect from the Galaxy name drop down list and click Connect.
7. To create a platform, expand the System tree in the Template Toolbox pane and right-click the
WinPlatform item. Select the New | Instance menu item.
8. The instance is created under the Unassigned Area directory in the Model section.
9. Right-click the instance and select Rename. Enter the desired name.
10. To deploy, right-click the platform node in Application Views and select Deploy from the resulting menu.
12. The deployment begins; this operation takes several minutes. Once complete, click Close on the Deploy
screen.
13. The platform is now deployed and ready to be linked. Close the ArchestrA IDE interface.
3. The IAS Object Manager Configuration appears with the InSQL Select tab displayed.
• Enable IAS Object Generator - Select this option if you would like compiles (IO and Drawing) in
the Workbench to automatically create objects in IAS. If you wish to display object creation, leave
this option unchecked.
• Disable nonessential checks - Select this option to remove nonessential processing from the
Object Manager. Doing so allows the Object Manager to run more quickly with very large projects
(above 2000 tags).
• Prompt before running - This option is useful when you have a lot of I/O to compile, but you do
not want to update the HMI objects. A message box appears asking you to verify that you would
like to run the Object Generator.
5. From the File menu, select the Connect Galaxy menu option.
6. The Galaxy Info screen appears. Select the Domain, Galaxy Repository, and Galaxy then click OK.
7. On the Target Galaxy tab, select the desired projects and select the Host Platform. The icon will appear
green. Enter the appropriate Object Generation option.
8. Select the Galaxy Info tab. Specify the login information used to connect to the Galaxy database.
9. Click Validate Connection to ensure that you are able to connect to the Galaxy. A Connect Successful
message is displayed when the connection is successfully established. Click OK to continue.
10. If you are not using the Galaxy Security feature, in this section, leave the Username and Password
fields blank and click Validate Security. A Connect Successful message is displayed. Click OK to
continue.
11. If you are mapping multiple projects to the same galaxy and you want the prefixes, select the Mapped
Projects tab to associate the project with the Galaxy and click Save Project Info. Note that this step is
optional.
Note: Multiple projects can be mapped to a single galaxy, but a project can only be mapped to one
galaxy at a time. If a project and Galaxy are not associated via the map buttons, then no objects will be
created or deployed for the Workbench project when the project is compiled or downloaded.
Note: If you are using more than one project, you may wish to use project prefixes. The prefix is
appended to tagnames and controller names for objects created in the galaxy. This provides a way to
determine which project the tag is associated with and also ensures that tag names are not duplicated.
Although the prefix is applied to the controller name, you cannot duplicate controller names in different
projects since the scan group name is used as the access path for objects created from the
$mtlStacServer template. Prefixes can contain letters, numbers, or the underscore character.
12. Once the information is entered, click File | Save and then click Import Objects. The Import
Preferences screen appears. Select the appropriate settings.
13. The Object Generator appears and the base template objects are now imported into the Industrial
Application Server object library. Progress is recorded in a dialog. Once the import is complete, the
progress dialog automatically closes.
The objects created by the Object Generator are created from one of the templates located in the toolset. The
toolset is created and populated by the IAS Object Manager Configuration when the Import Objects button is
clicked.
$mtlAppEngine - Derived from $AppEngine and 1 AppEngine is created per controller with the name of the
object being the controller name plus "AppEngine.”
$mtlArea - Derived from the $Area template. An area is created for each area associated with the controller.
The default area for all objects generated from a particular controller is named controller name plus "Area.”
$mtlStacServer - Derived from $OPCClient. Two $mtlStacServer objects are created for each controller. The
objects are named controller name plus ".DI" plus ".Primary" or ".Secondary" depending if it is the primary or
secondary data source. These two objects are referenced by the $mtlRedundantDIObject.
$mtlRedundantDIObject - Derived from the $RedundantDIObject. A single $RedundantDIObject object is
created per controller with the name of controller name plus "Redundant.” All the input source and output
destinations reference the Redundant object for the objects created from the $mtlDiscrete, $mtlFloat, and
$mtlInteger objects.
$mtlDiscrete, $mtlInteger, $mtlFloat - Derived from the $UserDefined object. Contains a Field Attribute
called value of type Discrete, Integer, or Float, respectively. This Field Attribute is populated via the
$mtlStacServer. These templates also contain UDA(s) called MTL_ControllerName and MTL_ProjectName
that should not be modified by the user.
The $mtlStacServer, $mtlDiscrete, $mtlFloat, and $mtlInteger templates and objects created from these
templates have attribute lock flags. These flags are named as MTL_OHMI_ plus the attribute name. OHMI
(Override Human Machine Interface). These flags are defined as UDA booleans. Their meaning is quite
simple. When the flag is set to true the Object Generator populates the specified attribute during the compile
phase. If the value is false, the Object Generator does not populate that attribute with a value and the object
retains the last value set by the user. Additionally, the initial values of these MTL_OHMI_ flags in the
templates can be changed based upon your application.
Function Block Templates - Derived from $mtlTemplate. The templates derived from $mtlTemplate may
contain the 3 UDAs, LinkedDiscretes, LinkedFloats and LinkedIntegers. Each one is a string array which
specifies the CSV Tags that make up the function block. The UDAs may be changed, thereby adding extra
tags or removing tags that make up the function block. The function blocks do not have the attribute lock flags
defined by default since this would result in a very large number of UDAs that are probably not needed.
Therefore, if there is no attribute lock flag present, the attribute is written to (by default) by the Object
Manager. If you would like to lock an attribute for one of the UDAs specified in the Linked arrays, simply
create the UDA in the instance and set the flag to the desired value. The UDA should be created with the
Boolean data type and the writeable category of user. The UDA should be named slightly different than that in
the base templates $mtlIngeger, $mtlFloat and $mtlDiscrete. The name is the field attribute name_ + OHMI_ +
name from the $float, $int, or $discrete template table (the UDAs column). For example, the RST trend high is
RST_OHMI_TrendHigh. In addition, to the field attribute lock flags their are some top level attribute lock flags
for the overall function defined below:
UDAs Attribute Name
OHMI_AlarmComment AlarmComment
OHMI_ShortDesc ShortDesc
There is also an AlarmMaster UDA. This UDA specifies one of the field attribute names in the linked arrays.
The specified UDA determines the AlarmComment and ShortDesc attributes along with the area to which the
Function block belongs. This is necessary because the function block is made up of essentially many tags,
each potentially set to a different area, however the function block must reside in a single area and likewise
have a single AlarmComment.
$mtlDiscrete
MTL_OHMI_ActiveAlarmState Value.ActiveAlarmState
MTL_OHMI_AlarmComment MTL_AlarmComment
MTL_OHMI_AlarmMsgVal Value.DescAttrName
MTL_OHMI_AlarmPriority Value.Priority
MTL_OHMI_Desc Value.Desc
MTL_OHMI_EnableHistory Value.Historized
MTL_OHMI_EnableStateAlarm Value.Alarmed
MTL_OHMI_EnableStateLabels Value.UseOffOnMsg
MTL_OHMI_Invert Value.InvertValue
MTL_OHMI_ShortDesc ShortDesc
MTL_OHMI_StateLabelFalse Value.OffMsg
MTL_OHMI_StateLabelTrue Value.OnMsg
$mtlInteger
MTL_OHMI_AlarmComment MTL_AlarmComment
MTL_OHMI_AlarmDeadband Value.LevelAlarm.ValueDeadband
MTL_OHMI_ConversionMode Value.ConversionMode
MTL_OHMI_Desc Value.Desc
MTL_OHMI_EnableHiHiLimitAlarms Value.HiHi.Alarmed
MTL_OHMI_EnableHiLimitAlarms Value.Hi.Alarmed
MTL_OHMI_EnableHistory Value.Historized
MTL_OHMI_EnableLimitAlarms Value.LevelAlarmed
MTL_OHMI_EnableLoLimitAlarms Value.Lo.Alarmed
MTL_OHMI_EnableLoLoLimitAlarms Value.LoLo.Alarmed
MTL_OHMI_EnableScaling Value.Scaled
MTL_OHMI_EngineeringUnits Value.EngUnits
MTL_OHMI_HiAlarmLimit Value.Hi.Limit
MTL_OHMI_HiAlarmMsgVal Value.Hi.DescAttrName
MTL_OHMI_HiAlarmPriority Value.Hi.Priority
MTL_OHMI_HiHiAlarmLimit Value.HiHi.Limit
MTL_OHMI_HiHiAlarmMsgVal Value.HiHi.DescAttrName
MTL_OHMI_HiHiAlarmPriority Value.HiHi.Priority
MTL_OHMI_LoAlarmLimit Value.Lo.Limit
MTL_OHMI_LoAlarmMsgVal Value.Lo.DescAttrName
MTL_OHMI_LoAlarmPriority Value.Lo.Priority
MTL_OHMI_LoLoAlarmLimit Value.LoLo.Limit
MTL_OHMI_LoLoAlarmMsgVal Value.LoLo.DescAttrName
MTL_OHMI_LoLoAlarmPriority Value.LoLo.Priority
MTL_OHMI_MaxEU Value.EngUnitsMax
MTL_OHMI_MaxEURange Value.EngUnitsRangeMax
MTL_OHMI_MaxRaw Value.RawMax
MTL_OHMI_MinEU Value.EngUnitsMin
MTL_OHMI_MinEURange Value.EngUnitsRangeMin
MTL_OHMI_MinRaw Value.RawMin
MTL_OHMI_ShortDesc ShortDesc
MTL_OHMI_TrendHigh Value.TrendHi
MTL_OHMI_TrendLow Value.TrendLo
$mtlFloat
MTL_OHMI_AlarmComment MTL_AlarmComment
MTL_OHMI_AlarmDeadband Value.LevelAlarm.ValueDeadband
MTL_OHMI_ConversionMode Value.ConversionMode
MTL_OHMI_Desc Value.Desc
MTL_OHMI_EnableHiHiLimitAlarms Value.HiHi.Alarmed
MTL_OHMI_EnableHiLimitAlarms Value.Hi.Alarmed
MTL_OHMI_EnableHistory Value.Historized
MTL_OHMI_EnableLimitAlarms Value.LevelAlarmed
MTL_OHMI_EnableLoLimitAlarms Value.Lo.Alarmed
MTL_OHMI_EnableLoLoLimitAlarms Value.LoLo.Alarmed
MTL_OHMI_EnableScaling Value.Scaled
MTL_OHMI_EngineeringUnits Value.EngUnits
MTL_OHMI_HiAlarmLimit Value.Hi.Limit
MTL_OHMI_HiAlarmMsgVal Value.Hi.DescAttrName
MTL_OHMI_HiAlarmPriority Value.Hi.Priority
MTL_OHMI_HiHiAlarmLimit Value.HiHi.Limit
MTL_OHMI_HiHiAlarmMsgVal Value.HiHi.DescAttrName
MTL_OHMI_HiHiAlarmPriority Value.HiHi.Priority
MTL_OHMI_LoAlarmLimit Value.Lo.Limit
MTL_OHMI_LoAlarmMsgVal Value.Lo.DescAttrName
MTL_OHMI_LoAlarmPriority Value.Lo.Priority
MTL_OHMI_LoLoAlarmLimit Value.LoLo.Limit
MTL_OHMI_LoLoAlarmMsgVal Value.LoLo.DescAttrName
MTL_OHMI_LoLoAlarmPriority Value.LoLo.Priority
MTL_OHMI_MaxEU Value.EngUnitsMax
MTL_OHMI_MaxEURange Value.EngUnitsRangeMax
MTL_OHMI_MaxRaw Value.RawMax
MTL_OHMI_MinEU Value.EngUnitsMin
MTL_OHMI_MinEURange Value.EngUnitsRangeMin
MTL_OHMI_MinRaw Value.RawMin
MTL_OHMI_ShortDesc ShortDesc
MTL_OHMI_TrendHigh Value.TrendHi
MTL_OHMI_TrendLow Value.TrendLo
Section 3 – Tutorial
Now that the applications have been linked and the template objects imported into IAS, we can start building
objects and linking graphics.
This portion of the Getting Started Guide examines the process of creating objects for a PID loop and linking
those objects to SmartSymbols.
Creating Objects
1. Configure project tags in the Workbench. For the PID loop, the tags PT501 and PY501 are created and
defined as follows:
PT501:
Tagname: PT501 Signal Type: MA
Description 1: Pressure Transmitter 501 Signal Min: 4
Engr Min or DI 0 State: 0 Signal Max: 20
Engr Max or DI 1 State: 500
Engr Units: PCT
PY501:
Tagname: PY501 Signal Type: MAO
Description 1: Pressure valve 501 Signal Min: 4
Engr Min or DI 0 State: 0 Signal Max: 20
Engr Max or DI 1 State: 100
Engr Units: PCT
PY501:
6. Open the ArchestrA IDE and expand the tree to view the objects in the IDE.
7. Create a drawing called PIC501 and add the appropriate function blocks for the PID. The drawing appears
as follows:
8. Save and compile the drawing. When the compile is complete, the IAS Object Generator is launched to
create objects for the function blocks used on the drawing.
9. Open the ArchestrA IDE and expand the tree to view the objects in the IDE.
11. Once the download is complete, the IAS Object Generator is launched to deploy the function block and IO
tag objects.
Note: This only occurs if the Deploy IAS objects on download option is checked in the IAS Object
Manager Configuration.
12. Open the ArchestrA IDE and expand the tree. All objects are now deployed and ready for use.
If you only require base functionality from these objects, completion of the preceding steps is sufficient.
However, you may require additional functionality, such as security on the objects. More specifically, you may
only want users with certain access levels to have permission to change tuning constants on the PID object.
The objects support security so that this can be accomplished with simple modification of the object in the
ArchestrA IDE.
2. A set of SmartSymbols, providing graphics for the objects, was installed with the IAS Object Manager.
Before the symbols can be used in an application, they must first be imported. To import the symbols,
select Special | SmartSymbol | Manage SmartSymbol.
7. The SmartSymbols are imported. Once the import is complete, the InTouch SmartSymbol –
Management Mode screen appears.
9. The SmartSymbols can now be used on a window. Create a new window in WindowMaker.
11. The cursor changes to Wizard Placement ( ). Click on the screen at the desired placement position.
13. Select the Template Object for which graphics are desired and then select the desired graphic. For our
example, choose the MAAU directory and the Manual Auto Faceplate Ver2.
14. Click OK; the SmartSymbol Properties screen appears. Select the Show Text Strings option at the
bottom of the screen.
15. Click Replace to replace all instances of MAAU with the base tagname; in our example this is PIC501.
Enter MAAU in the Find What text box and enter PIC501 in the Replace With text box. Click Replace All
and click Cancel.
Note: Enter the name of the directory containing the appropriate symbol that you wish to replace in the
Find What field. For example, enter Matrix8521 for a symbol located in this directory.
16. The SmartSymbol Properties screen is populated with information from the object.
17. Click OK to close the SmartSymbol Properties screen. The SmartSymbol is now displayed on the
InTouch window.
18. To view the graphic with live data, click Runtime (located in the upper right-hand corner) to launch
WindowViewer.
19. The SmartSymbol graphic is now displayed with live data from the process.
Section 4 – Troubleshooting
• Exception on the Host Platform section of the Object Manager Configuration:
This may indicate an incorrect version of Archestra or an insufficient Archestra patch.
• The Target Galaxy tab of the Object Manger Configuration does not show any Domains/Computers:
Verify on Windows Explorer that the Domains/Computers are shown. If Windows Explorer cannot find
them, the Object Manager Configuration will be unable to as well.
Section 5 – Conclusion
The preceding steps provide an introduction to the functionality and capability of SmartSymbols. There are
many other symbols available to allow visualization of other complex function blocks built using Matrix,
including: controller overview and diagnostics, motor control, PID tuning, and process variable quality. The
procedure for using these faceplates is the same as discussed for the MAAU_V1 in the Tutorial section of this
manual: configure the block on a drawing, compile it, download the strategy, select the appropriate faceplate
in InTouch, and then link it to the object.
This Getting Started Guide has examined the process of installing the object manager, linking it to the various
system components, and then using it to automatically create the IAS objects and link graphics to those
objects. Due to the high-level nature of this Getting Started Guide, you will certainly require additional
information as you become more familiar with the system components. Some common functions for which you
may require additional resources include:
• Help Files - A full set of Help files is delivered and installed with the system. From any application,
you may select Help from the pull down Help menu item, click the Help option (if one is present on the
form), or press the F1 key on the keyboard to view the Help. Each Help file has a detailed index, table
of contents, and search function to expedite locating additional information for a particular topic.
• HMI Graphics, History, and Alarming - Please refer to the documentation that comes with your HMI
for a detailed discussion of these features. If your HMI is InTouch, IO and Controller tags are set up to
automatically alarm. A detailed discussion can be found in the External Application/HMI Interface
section of the online Help.
• Training - GE offers a comprehensive set of training classes. For more information about these
courses, please visit the website: www.ge-ip.com/support.
• Technical Support
Europe, the Middle East, and Africa (EMEA)
Online Technical Support: www.ge-ip.com/support
Phone: +800-1-433-2682
Technical Support Email: [email protected]
Customer Care Email: [email protected]
Primary languages of support: English, French, German, Italian, Czech
Support in the Americas (Americas)
Online Technical Support: www.ge-ip.com/support
Phone: 800-433-2682
Technical support email: [email protected]
Customer care email: [email protected]
Primary Languages of support: English
Glossary
8000 IO Configurator – Configures the system hardware (controllers and IO modules) for a controller.
8000 Process IO System – Control system comprised of a controller and IO modules.
.NET Framework – Microsoft technology used in some of the Workbench components.
Basic Input/Output System (BIOS) – Area of the PC that monitors and controls all system hardware.
Basic Support – Support program that provides responses to your product questions on the next business
day.
Coil – Basic discrete output element in IEC 61131-3 Ladder Diagram programming.
Consumer – Uses data from one or more producing controllers.
Contact – Basic discrete input element in IEC 61131-3 Ladder Diagram programming.
Control Platform – Controller hardware upon which control strategies execute.
Control Strategy – Logic that executes within a controller to perform a task, e.g. controlling a valve, starting
and stopping a motor, etc.
Controller – Processor that executes control strategies and process IO.
Controller Statistics – Workbench feature that displays scan time breakdown, system parameters, and event
logs.
Custom Reports – User-created reports with customized output to fit all documentation needs
Data Entry Panel – Right-hand pane of the Workbench. As specific tasks are selected in the Project Explorer,
the Data Entry Panel changes to facilitate data entry.
Database Maintenance Utility – Workbench utility that allows for maintenance tasks on the database, e.g.
reload, attach, de-attach, etc. This utility should only be used with assistance from technical support.
Demo mode – Workbench mode that executes when no license file has been obtained. In this mode,
downloads to the controller are disabled, but all other functions are available.
DesignerSim – Enables the control system designer to test control strategies in a single controller without the
need of physical hardware.
Dynamic Link Libraries (dll) – Programming unit that provides functions or information to other programs.
Ethernet BIM – Controller type that functions as a remote IO scanner, as no control strategies are supported.
Executable File (exe) – File that can run directly on a computer.
Floating Point – IEEE precision numbers that are represented in two consecutive registers.
Function Block – Unit of code that uses inputs to compute one or more output(s). Examples of function
blocks include PID and motor control.
HART – Communication protocol that places digital information on top of a 4-20mA signal, allowing a
transmitter to send up to four data values in addition to the normal 4-20mA signal.
Human Machine Interface (HMI) – Graphical view of the process normally presented to the operator,
consisting of items such as value displays, animation, and trends.
Hybrid Controller – Controller type that supports both Process (Advanced Function Blocks, such as PID and
Motor Control) and Logic (IEC 61131-3) control strategies.
Hybrid Workbench – Licensed version of the workbench that supports creating control strategies in both
Process (Advanced Function Blocks, such as PID and Motor Control) and Logic (IEC 61131-3) languages.
Hysteresis – Prevents alarms from recurring when the value is hovering close to the set point.
IEC 61131-3 – International standard that defines how certain programming languages and their attributes
should behave.
IEC languages – Ladder Diagram, Structured Text, Instruction List, Function Block Diagram, and Sequential
Function Chart.
InBatch – Invensys’s S88 compliant batch execution engine.
Industrial SQL Server (InSQL Server) – Invensys’s historian.
Integer – Number that can be represented in a single register.
InTouch – Invensys’s HMI product.
IP Address – An identifier for a computer or other device (printer, plotter, etc.) on a TCP/IP network.
Logic Controller – Controller type that executes only Discrete Logic.
Logic Workbench – IEC 61131-3 programming environment included in Hybrid and Logic Controllers.
Matrikon – OPC client that is installable from the Additional Programs section of the Product Installation CD.
Media Access Control Address (MAC Address) – Unique address that identifies each device on a network.
Microsoft Desktop Engine (MSDE) – Allows the Workbench to access MS-SQL type databases.
Modbus RTU – Serial communication protocol widely used in the industrial automation industry.
Modbus TCP/IP – Modbus over Ethernet.
Module – Physical IO device that provides data to the controller.
Module Channel – Portion of a module that is connected to the physical field device, i.e., transmitter,
positioner, etc.
8521 – Product number of the controller.
Network Configurator – Network management tool used to assign IP addresses to unconfigured controllers
and show network information for all controllers on a process network.
Node Number – Modbus address of the controller.
OPC – Object Linking and Embedding (OLE) for Process Control.
Peer to Peer – Mechanism that allows controllers to exchange data without the need for additional
programming.
PID Loop – Process control function block that drives an output based on the difference between the
measured process variable and the desired setpoint.
Premium Support – Support program that routes your calls, emails, or faxes to an engineer as soon as one
is available within normal business hours.
Process Controller – Controller type that supports Process control strategies (Advanced Function Blocks,
such as PID and Motor Control).
Process Workbench – Version of the Workbench that supports creating strategies in the Process language
(Advanced Function Blocks, such as PID and Motor Control).
Producer – Supplies data to one or more consuming controllers.
Project Explorer – Located in the left-hand pane of the Workbench; assists in adding controllers, drawings,
tags, modules, etc.
Project Tags – Names and attributes assigned to channels on IO modules.
Real Time – Viewing control strategies with data updating as soon as it is available from the controller or
simulator.
Redundant Controller – Two controllers running in lockstep. The standby controller continually monitors the
health of the master controller so it can take over within the same scan if the master controller fails.
Sequence of Events (SOE) – Sequence of Events data gives an accurate time for event occurrence, along
with the event value and other useful information. This data can then be used to help determine a specific
order of occurrence.
Simplex Controller – Single controller used to execute control strategies and process IO. Systems can be
made redundant by adding a second controller.
Simulator (DesignerSim) – Enables the control system designer to test control strategies in a single
controller, without the need of physical hardware.
SmartSymbols – Graphic templates that can be linked to an object and used for rapid development of
screens. When a change is made to such a template object, the change is automatically propagated to all
uses of the template.
StacServer – Application name for the Universal IO Server. The Modbus TCP/IP and OPC server that comes
with the Workbench.
Standard Reports – Reports that are shipped with the product and pertain to either a project or a controller.
Strategy Builder – Process control logic diagrams are developed here by selecting the appropriate function
blocks, assigning symbolic tags, and then connecting the blocks with analog or digital lines.
Strategy Viewer – Facilitates the animation of logic diagrams with either simulated or live real time process
data.
SuiteLink – Communication protocol used within InTouch to communicate with devices on either a local
machine or a remote node.
Universal IO Server – Modbus TCP/IP and OPC server that comes with the Workbench.
Wizard – Mechanism for gathering operator input to some of the more complex function blocks of Process
Control.
Wonderware – Suite of products that include Industrial Application Server, InTouch, InSQL, and InBatch.
Workbench – Application that provides the foundation for defining a project and all of its components: tags,
hardware configuration, tables, and control logic.