PART 1 GENERAL

11.1 SUMMARY
1A. This section includes the specifications for the major software packages that are required for this

project.
21. Human Machine Interface Software
3B. Programming packages that are not specifically addressed but are necessary to meet system
requirements must also be provided. A minimum of one licensed copy of all software is required.
4C. Related Sections
51. Programmable Logic Controllers
62. Industrial Computers
73. Programmable Logic Controller Software
84. Communication Software
95. Network Software
1.2 QUALIFICATIONS
10A. Manufacturer
111. Software manufacturer specializing in producing products specified in this section with a
minimum of twenty years experience.
122. Manufacturer must maintain service and engineering facilities within 100 miles of project.
133. Manufacturer shall have service personnel available (24) hours a day through a 1-800
phone number.
144. Manufacturer shall offer standard and customized training courses at a local facility.
15B. Supplier
161. The supplier of the software shall be an authorized distributor for the manufacturer with a
minimum of three years experience.
172. The supplier of the software shall maintain a support staff knowledgeable in the selection
and use of the software.

NOTICE: The specification guidelines shown in this document are intended to aid in the specification of products.
Specific installations have specific requirements, and Rockwell Automation does not recommend or intend any
specific application based solely upon the guidelines provided here. Because of the variety of uses for this
information, the user of, and those responsible for applying this information, are responsible for ensuring the
acceptability of each application and appropriate use of the guidelines. In no event will Rockwell Automation be
liable for misuse, misapplication or reliance on these guidelines in connection with any specific application.

Rockwell Automation also disclaims indirect or consequential damages resulting from the use or application of this
information.
PART 2 PRODUCTS

12.1 HUMAN MACHINE INTERFACE SOFTWARE

1A. Manufacturer
21. Rockwell Software Model RSView32
32. Substitutions: Not Permitted
4B. Selection
51. The Human Machine Interface (HMI) software shall be an integrated package for developing
and running automation applications.

62. To insure system compatibility, the HMI software shall be manufactured by the manufacturer
of the programmable logic controllers.

73. The HMI shall come with a tool that enables the user to add symbols or addresses created in
an Allen-Bradley PLC-5 or SLC 500 program to a project.
84. The HMI shall be selected to handle the system requirements while allowing for twenty-five
percent additional inputs and outputs.
95. The HMI shall be based on Microsoft user-interface standards.
106. The HMI shall provide a Project Manager for organizing and working with projects. It shall
contain all editors to create a project and shall display project files as you create them.
117. All Project files shall be in a directory structure that does not mix application files (user
developed project files) with system files for easy data backup.
128. The HMI shall provide the ability to design high-level graphics for complex applications
either by using its own drawing editor or by importing graphic display files from other
drawing packages such as AutoCAD, CorelDRAW and PhotoshopTM. The HMI shall
have the ability to animate graphic displays via control including, but not limited to
position, rotation, size, and visibility.
139. The HMI shall come with a large selection of commonly used graphic objects and symbols
that can be dragged and dropped into a graphic display.
14C. Software Compatibility
151. The HMI software shall be compatible with the specified network, communication and
programmable logic controller programming software.
162. The HMI shall be designed for use in Microsoft Windows 2000 and Microsoft Windows NT.
173. The HMI shall use OLE, ODBC, DDE, OPC, and ActiveX technologies for optimal
performance and integration with other software systems.
184. The HMI shall support object linking and embedding (OLE) for true application integration.
The HMI shall store its tag database and alarm information in a database format that is
ODBC compliant and all historical data shall be stored in .dbf (dBase IV) format. Support
of narrow format (single tag per time stamp) and wide format (multiple tag per time
stamp) shall be supported.
195. It shall be possible to log historical data directly to an ODBC Compliant database.
206. The HMI shall be able to act as a DDE server and client to allow for data exchange with a
wide range of devices and other Microsoft Windows applications.
217. The HMI shall be able to act as an OPC server and client to allow for data exchange with a
wide range of process devices.
228. The HMI shall integrate Microsoft Visual Basic for Applications, VBA as the users
programming language to customize or extend the application. The HMI must adopt the
Component Object Model, and implement COM technology as a means to expose open

interfaces of the application to external applications, such as Microsoft Visual Basic.

23D. Features
241. Project Manager
25a. The HMI software shall provide a Project Manager to organize and work with the
project.

26b. The Project Manager shall be divided into two windowpanes, one for the editors
and one for the objects under each editor.
27c. The Project Manager shall have two modes, edit and run.

11.) The edit mode is for creating or configuring project files.

22.) The run mode is for running the project.
33.) The Project Manager shall allow the user to run the HMI system in runmode while editing project components.

12. Communications
2a. Data Collection
11.) The HMI shall have several methods for collecting data from
programmable controllers.
22.) The methods shall be via DDE servers, via OPC servers or via a C-API
interface through direct device tags.
33.) The HMI shall allow the user to alter the method for collecting data,
switching between DDE, OPC and Direct.

1b. The HMI shall have the ability to dynamically reassign tags to a different
programmable controller, providing node level redundancy. This re-assignment
shall be performed while running the project with no noticeable interruption of
data.
2c. The HMI shall have the ability to assign any device tag a scan class defining the tags
foreground and background scanning period.
3d. The HMI shall provide full optimization of tag writes to contiguous data held in
devices, to allow quick and proficient communication on downloads. It will be
expected that any OPC/DDE servers will provide write optimization
4e. The HMI shall have the ability to switch to a pre-defined secondary network if the
primary network fails at runtime. This task shall be able to be performed either
manually or automatically.
5f. Client Capability

11.) The HMI shall also act as a DDE client. When connecting to a DDE server,
the HMI shall attempt to connect using the preferred Advanced DDE
first, if unsuccessful, then a CF-text connection shall be made.
22.) The HMI shall act as an OPC client
0
a.) The HMI shall support both Local and Remote OPC
connections.
1
b.) The client shall produce a list of all known OPC servers
that are registered, during configuration.

c.) When functioning as an OPC client the HMI must be able

to implement the Browse Namespace method of OPC.

1g. Server Capability

11.) The HMI shall have the ability to act as an OPC and/or DDE Server.
0
a.) As a DDE Server the HMI must serve all 3 formats of
1

DDE, CF-text, XL-table, and Advanced DDE.

b.) When serving DDE over a network, the HMI shall
automatically create the DDE Share.

1h. The HMI shall allow nodes to be disabled / enabled while running the project. When
a node is disabled all communications with the device shall be stopped until the
node is re-enabled.
2i. The HMI shall provide an Object Model Interface to the communication architecture.
This interface shall allow the communication channel or node to be modified
from another program such as Visual Basic, while the project is running.
33. Tag Database
4a. Definition
51.) The tag database shall define what data is to be monitored. Each entry in
the tag database shall be called a tag.
62.) The HMI tag database shall provide four types of tags: analog, digital,
string, and system.
73.) The tag database shall provide the ability to enter a description of the tag,
describe its minimum, maximum, scale, offset, and units (if analog), its
on and off labels (if digital), its initial value, a security access code, and
describe its alarming.
84.) The tag database shall provide the ability to generate tag names of up to 40
characters long. The tag names shall be able to contain the following
characteristics: A through Z, 0 through 9, underscore (_) and dash (-).
95.) The tag database shall be organized in a hierarchy, each level represented
by a folder that can be expanded or collapsed.
10b. Updating
111.) Each tag shall have the ability to receive its data via a device, from a DDE
server, OPC Server or from memory.
12a.) A tag with a device as its data source shall use the C-API of
RSLinx to receive its data.
13b.) A tag with OPC or DDE as its data source shall receive its data
through any respective OPC or DDE server or from another
computer using NetDDE.
14c.) A tag with memory as its data source shall receive its data from a
value table and can be used for local storage purposes.
152.) The HMI shall have the ability for the current value of a tag to be updated
from the device it is connected to and stored in RAM so it is
immediately accessible to all parts of the HMI.
16c. Importing Tags
171.) The tag database shall have the ability to selectively import tags from an
Allen-Bradley PLC database.
182.) Tags imported in this way shall be copied into the database and shall not

be shared with the source PLC database.

19d. Modifying Tag Database

201.) The tag database shall provide the ability to duplicate, edit, and delete any
individual tag, or folder of tags.

212.) The HMI shall have the ability to modify the tag database while the
project is running. It shall be possible to add a tag(s) in the run mode to
the database (Alarming, Datalogging, and Displays all active) without
stopping the project.
223.) The HMI shall provide an Object Model Interface to the tag database.
This interface shall allow all aspects of the tag database to be modified
from another program such as Visual Basic, while the project is
running. The Object Model interface will also generate events for
single tags and collections of tags.
234. Tag Monitor
24a. The HMI shall have the ability to create and save a list of tags and monitor their
values while the project is running.
25b. The HMI Tag monitor shall provide the configuration details of each tag in the list.
26c. The HMI Tag monitor shall report the communication status of each tag as Valid or
Error.
27d. The HMI Tag monitor shall annunciate those tags in alarm by changing the text
color.
28e. The HMI Tag monitor shall present a form view as well as a spreadsheet view.
295. Derived Tags
30a. The HMI shall have the ability to create a tag whose value is the result of an
expression.
311.) The expression can be made up of mathematical operations, tag values, ifthen-else logic, and other special functions.
322.) The current value of the derived tag shall be stored in an analog, digital,
or string tag in a value table.
333.) Multiple derived tags may reside in the same derived tag file or in up to
20 different derived tag files that run simultaneously.
34b. The HMI shall have the ability to specify the evaluation period of the derived tag.
35c. The HMI shall have the ability to edit derived tags during development or runtime.
36d. The HMI shall have the ability to start and stop derived tag processing while the
project is running.
376. Macro Capability
38a. The HMI shall provide a Macro capability that will execute system commands, user
defined commands and other macros.
39b. The HMI macros shall be securable. The HMI shall provide a mechanism to restrict
certain users from the execution of a given macro.
40c. The HMI macro capability shall permit parameter passing of up to 7 variables.
41d. The HMI macro capability shall permit macros to call macros.
42e. The HMI macro capability shall permit synchronous or asynchronous operation.
43f. The HMI macro editor shall be a simple text editor permitting other editors to create
macro files when necessary.
447. Alarming
45a. The HMI shall allow the user to set up a complete alarm system.
46b. The alarm system shall have the ability to monitor any analog or digital tag for
alarms, up to a maximum of 10,000 tags.
47c. The alarm system shall provide a means of displaying up to 1000 tags that are in

alarm. This alarm summary display shall be fully configurable, and support
blinking colors.
48d. The alarm system shall have the ability to define up to eight different severity
classes to visually and audibly distinguish alarms.
49e. The alarm system shall be able to generate alarms on an increasing threshold,
decreasing threshold or both. It must be possible to disable the generation of
alarms when approaching normal operation range.
50f. The alarm system shall allow user defined alarms to be generated via a command.
51g. The HMI shall provide an Object Model Interface to the Alarm system. This
interface shall allow the configuration for the full read and write of all tag
alarms of the Alarm system to be modified from another program such as Visual
Basic while the project is running.
52h. The alarm system shall have the ability to use system default messages or create
unique messages to describe an alarm; log messages to a file (dBase IV) to a
printer or to both; suppress alarms for maintenance and tuning purposes; and set
up global alarm monitoring.
53i. Corrective Actions

11.) The alarm system shall have the ability to identify alarm corrective action
to the operator.
22.) The alarm identification shall be configured during alarm configuration,
and must not require a unique button per alarm on a graphic to
implement.

1j. Custom Alarm Summary Objects

21.) Custom alarm summary objects shall be able to be embedded on any
display.

32.) Alarm summary objects shall be able to be sorted by date, or severity in

ascending or descending order on the fly.
43.) It shall be possible to include/exclude any tag in a summary by the use of
intelligent filters. Filters shall be of the following types.
5a.) Wildcard (* or ?) constructs
6b.) Tag Types (Analog, Digital)
7c.) Alarm States (Faults, Out of Alarm and Only show current
tags in alarm)
8d.) Severitys (1-8)

1k. The alarm system shall allow the operator to write a custom message to the alarm
history.
2l. The alarm system shall implement a handshake mechanism between the HMI and the

PLC ladder logic that guarantees short duration alarms are recorded in the alarm
history file. The alarm system must be flexible in this implementation to allow
the PLC ladder logic to reset the bit, or to manage the resetting of the bit in the
HMI.
3m. The alarm system shall allow the operator to call a Command, Macro or a VBA
routine when an alarm in the summary is selected. This functionality must pass
the following information of the alarm as comma separated parameters: Tag
Name, Alarm Type, Severity, Value, Date, Time, and Tag Type
4n. Alarm Logging

11.) The alarm system shall have the ability to create alarm log files (dBase IV)
periodically, at specified times and on event. This alarm log system
shall have the ability to automatically purge old files after a specified
time.
22.) The alarm system shall allow online export of an alarm log file to the
following ODBC format databases: MS Access, Sybase SQL Server,
Oracle, and MS SQL Server

18. Data Logging

2a. The HMI shall have the ability to record specific tag values under certain conditions.
Several models shall define these conditions.
31.) The data that is collected shall be stored in .dbf (dBase IV) format for
displaying in trends, archiving for future processing or analysis, and/or
using with third-party software, such as FoxPro, Crystal Reports, and
Microsoft Excel, for display or analysis.
42.) It shall be possible to log historical data directly to an ODBC Compliant
database.
53.) The HMI shall have the ability to start and stop data logging while the
project is running.
6b. Data Log Models
71.) The HMI shall be able to run 20 different datalog models simultaneously.
82.) There shall be no limit to the number of configured models.
93.) Models shall be capable of being stopped and started at any time.
104.) Datalog models must support 3 different data collection modes.
11a.) Periodic polling, on change, and on demand.
12b.) The periodic polling rate must have configurable, time units of
hundredths, tenths, seconds, minutes, hours or days. The
default time unit will be seconds.
13c. The data log system shall have the ability to create data log files periodically, at
specified times, on event and never. This data log system shall have the ability to
automatically purge old files or records after a specified time.
14d. The HMI shall be able to switch to an alternate path if a problem is encountered
logging to the primary.
151.) Errors such as low disk space, or dropped network connections must
be handled automatically.
162.) The HMI shall provide a way to automatically merge data logged to an
alternate location back to the primary location when the problem is
corrected.
17e. The HMI shall provide a mechanism for renaming the historical data set. It must be
possible to link the historical data with a batch or lot id.

18f. The HMI shall provide an Object Model Interface to the Datalog system. This
interface shall allow all the following aspects of the Datalog system to be
modified from another program such as Visual Basic, while the project is
running.
191.) Read data from and write it to a specified datalog model, to facilitate
easier report generation and manipulation of data.
202.) Access a specified model's configuration.
213.) The enumeration of available ODBC data sources and the creation of
tables within an existing, data source.
229. Activity Logging
23a. The HMI shall have the ability to record information about various types of system
activity.
24b. The HMI shall present the activity information in a dock-able window that can be
dynamically resized, and scrolled. This activity bar can be re-docked, or
disabled during runtime.
25c. Information that is collected shall be stored in .dbf (dBase IV) format, for archiving
for future processing or analysis, and/or for using with third-party software, such
as FoxPro, Crystal Reports, and Microsoft Excel, for display or analysis.

1d. Activity Logger

21.) The activity logger shall have the ability to log any of the following:
command and macro usage, operator comments, system messages, and
errors, errors from the communication network, and tag read and write
activity, and custom messages.
32.) The activity logger shall allow the user to designate where to store activity
log files, when to create and delete log files, and what activities to log.
43.) The HMI shall have the ability to edit activity logging during development
or runtime.
54.) The HMI shall have the ability to start and stop activity logging while the
project is running.
65.) The HMI shall have the ability to conditionally log information to the hard
disk and to a status bar by category

710. Events
8a. The HMI shall have the ability to trigger actions based on an event that has an
expression applied to it.
91.) An expression is an equation that contains tag values, mathematical
operations, if-then-else logic, or other functions.
102.) An action shall have the ability to produce a variety of functions
including, but not limited to, initiating a snapshot of tag values,
displaying an error screen, and changing a tag value.
11b. The HMI shall have the ability to specify the evaluation period of events.
12c. The HMI shall have the ability to edit events during development or runtime.
13d. The HMI shall have the ability to start and stop event processing while the project is
running.
14e. The HMI shall have the ability to run 20 event files simultaneously.
1511. Security

16a. The HMI shall have a security system allows certain users or groups of users to
access only certain parts of the system.
17b. The HMI shall have the ability to have security set up by inclusion or exclusion.
18c. Security Codes
191.) The security shall be based on a series of codes.
202.) The HMI shall have a minimum of 17 different security codes.
213.) Each code shall allow the users, or groups of users, with security
privileges for that code to access the HMI commands, macros, graphic
displays, OLE verb controls and tags allowed by that code.
224.) The security system shall be capable of assigning users combinations of
security codes, allowing for each user to access a different set of
features.
23d. User Account
241.) The security system shall assign each person a user account with the
following features.
25a.) Login name
26b.) Password.
27c.) Macros to be executed on login and logout.
282.) The HMI shall provide a means for operators to change the passwords
while the project is running.
29e. Strict Security Option
301.) The HMI shall have a strict security option.
312.) When strict security is on, the system shall check the security codes of
commands and macros no matter from where they are issued.
323.) When strict security off, the system shall check the security codes of
commands and macros only when they are issued from a command
within the graphics.
33f. The security system shall provide an option of synchronization with the Windows
NT security system. This will provide for a close integration of the overall
system security model.
34g. The HMI shall provide an Object Model Interface to the Security system. This
interface shall allow all the following aspects of the Security system to be
modified from another program such as Visual Basic, while the project is
running:
351.) The notification of a User login/logout.
362.) The ability to Login/Logout a specified User.
373.) The ability to change a Users password
384.) The ability to check a Users security privileges
3912. Graphic Displays
40a. The HMI shall provide a graphics display editor for creating displays using graphic
objects.
41b. The graphic display editor shall have the ability to generate graphics without the
need for a compilation process.
42c. Object Creation
431.) The graphics display editor shall have the ability to drag and drop objects
from a pre-configured graphics library.
442.) The graphic display editor shall allow the user to create libraries of
graphic objects.
453.) The graphics display editor shall have the ability to paste objects that are
copied to the clipboard from another Windows application.

464.) The graphics display editor shall have the ability to insert objects created
by another Windows application using OLE. True OLE support is
required in that it shall be possible to call up the native application that
created the object being inserted and to use the native object editing
tools from within the HMI.

47d. Tools
481.) The graphics display editor shall have tear-away toolbar.
492.) Color Palettes
50a.) The graphics display editor shall have color palettes.
51b.) It shall be possible to customize the color pallet.
52c.) Graphics drawn with a customized color pallet shall not require
the customized color pallet to be present on all runtime
computers.
53d.) Colors must be stored internal to the graphic files as Red, Green,
Blue numbers, not pallet indexes.
543.) The graphics display editor shall have context sensitive right-mouse
support on all objects.
554.) Drawing Tools
56a.) The graphics display editor shall have a minimum set of drawing
tools.
57b.) The set shall include snap, grid, rectangle, rounded rectangle,
line, polyline, polygon, freehand line, ellipse, arc, wedge, and
text.
585.) Editing Tools
59a.) The graphics display editor shall a minimum set of editing tools.
60b.) The set shall include tag substitute, flip, rotate, resize, reshape,
align, cut, paste, copy, duplicate, group, ungroup, bring to
front, send to back, space, fill, undo, redo, line, and color.
61c.) The graphic display editor shall provide a text search and replace
capability on an object or group of objects. This capability
shall allow whole tags or parts of tags to be replaced on an
individual confirmation or replace all basis.
62d.) The graphic display editor shall permit 1000 editing operations
to be undone and redone.
636.) Viewing Tools
64a.) The graphics display editor shall have a minimum set of viewing
tools.
65b.) The set shall include zoom in, zoom out, pan, and view entire
graphic.
667.) Additional Tools
67a.) The graphic display editor shall provide additional tools.
68b.) The tools shall include numeric input, numeric display, string
input, string display, label, arrow, recipe, alarm summary, tag
monitor, input command line, trend, button, OLE object, and
ActiveX objects.
69e. The graphic display editor shall have the ability to use tag placeholders to provide a
way to use one graphic display to represent a number of similar operations.
70f. The graphic display editor shall have the ability to create a screen background by
converting objects to wallpaper. These wallpaper objects cannot be selected or
edited.
71g. Object Control

721.) The graphic display editor shall allow the user to assign control to any
object or grouping of objects.
732.) The graphic display editor will provide a Command Wizard to aid the
user to formulate HMI commands when attaching control to graphic
objects.
743.) It shall allow the user to drill down in a group to modify any object or
object attribute without losing any object control property.
754.) The graphic display editor shall allow control to be copied from any
object to another object.
765.) The graphic display editor shall have the ability to attach, as a minimum,
the following control to objects: blinking colors, visibility, rotation,
horizontal and vertical movement, resizing (width and height), fill, and
touch.
776.) The graphic display editor shall use OSPTM (Object Smart Path) to
visually set the range of motion for an object.
787.) The graphic display editor shall have the ability to attach OLE verb
control to an OLE object.
798.) The graphic display editor shall have the ability to attach control that links
an object or display to a key or mouse button so operators can perform
an action by pressing a key or mouse button.
809.) The graphic display editor shall have the ability to quickly test control of
displays without changing to runtime.
8110.) The graphic when hosting an ActiveX control will allow the properties,
events and methods of the ActiveX to be invoked.
82h. Screen Control
831.) The graphic display shall permit the user to specify screen placement
anywhere on the display
842.) The graphic display shall permit the user to specify screen size. The
graphic display editor shall enable automatic scaling of displays to
different display resolutions to make the porting of applications easier
between systems having different display resolutions.
853.) The graphic display shall provide at least three (3) different display types,
86a.) Replace automatically closes all intersecting windows.
87b.) Overlay allows multiple intersecting windows to remain running.
88c.) Pop-up allows the graphic to remain on top at all times.
894.) The graphic display editor shall provide the option to load a screen into
memory but not display to the operator. This feature allows embedded
ActiveX controls to process logic without being seen.
905.) The graphic display shall allow a configurable title and system menu bar.
916.) The graphic display editor shall provide functionality to execute a macro
or script on display shutdown assigned on an individual display basis.
927.) The graphic display editor shall provide functionality to execute a macro
or script on display startup assigned on an individual display basis
93i. The graphic display shall provide an onscreen keyboard for data entry on systems
that do not have a keyboard.
94j. The graphic display shall provide input fields that continuously update showing the
user the results of the download
95k. The graphic display shall allow all objects within the graphic to use the last
acquired value of a tag.
96l. The graphic display shall allow the selection of a color for the following items:
971.) Background

982.) Input Background/Text

993.) Interactive objects highlight
1004.) Object with input focus
101m. The graphic display shall provide for the inclusion of security, inherited from the
HMI security system.

102n. The graphic display editor shall provide the ability to print any graphic whether
running or not. If the graphic is not running, the command will wait for the
graphic to collect all runtime data and then send the results to the printer. It
must be possible to print a graphic in the background, never disturbing the view
of the currently running screen.
103o. The graphic display editor shall provide real-time trends that always have a
minimum of 15 minutes of data.
10413. Trends
105a. The HMI shall have real-time and historical trending capabilities.
1061.) It shall also have the capability to display in trend layers, both real-time
and historical, at the same time.
1072.) The trends shall be created as reusable objects.
1083.) The trends shall have the ability to display data logged by another
computer. This feature is referred to as remote trending.
1094.) The trends shall have the ability to display data logged to a file server.
1105.) The trends shall have the ability to display data logged to either the
primary or alternate server.
111b. The HMI shall have the ability to create a trend that is part of a graphic display or
act as the entire graphic display.
112c. Trend Properties
1131.) The trends shall be able to plot data for as many as sixteen tags on one
trend.
1142.) The trends shall have the ability to display, as a minimum, the following
plot symbols: hollow square, filled square, up hollow triangle, up filled
triangle, down hollow triangle, down filled triangle, hollow diamond,
filled diamond, hollow circle, filled circle, dot, cross, and star.
1153.) The trends shall have the ability to interpolate a line via, as a minimum,
the following: automatic interpolation, linear line, digital line, and fullwidth representation.
1164.) Shading
117a.) The trends shall have the ability to use shading to emphasize
when a particular tag crosses a reference value.
118b.) a. The trends shall have the ability to be shaded to compare two
or more different trends.
119d. Trend Control
1201.) The trends shall have a marker, so that when the marker is over a point
on the trend, the pens date, time, and value at the markers location are
displayed in the legend.
1212.) The trends shall have the ability to be controlled by VCR style buttons
1223.) The trends shall have the ability to make invisible selected pens to
reduce screen clutter.
1234.) The trends shall have the ability to pause and resume
1245.) The trends shall have the ability to automatically pause when scrolling
back in time
12514. Expressions

126a. The HMI shall have the ability to create expressions to compare data to other
values, combine data with other data, and create cause-effect relationships with
other data.
127b. A command wizard shall be available to facilitate the creation of actions that
trigger when the expression evaluates true.
128c. Expressions shall have the ability to be built from, as a minimum, the following:
tag values; constants; mathematical, relational, logical and bit-wise operators;
built-in functions; and if-then-else logic.
129d. Expressions shall have the ability to be used, as a minimum, in any one of the
following: a graphic display, a derived tag, an event, an activity log, a data log,
and any alarm.
130e. The expression editor shall have the ability to use efficiency tools like cut, paste,
and copy in producing like expressions.
131f. Operators
1321.) The expression editor shall be able to use arithmetic operators, relational
operators, logical operators and bit-wise operators.
1332.) Arithmetic operators shall include addition, subtraction, multiplication,
division, modulus, and exponent.
1343.) Relational operators shall include equal, not equal, less than, greater
than, less than or equal to, and greater than or equal to.
1354.) Logical operators shall include AND, OR, and negation.
1365.) Bit-wise operators shall include AND, inclusive OR, exclusive OR, right
shift, left shift, and complement.
13715. Interoperability
138a. The HMI shall be based on standards that allow the HMIs data to be accessed and
shared among Windows applications and be fully interoperable with those
Windows applications.
139b. The HMIs graphic displays shall be containers for ActiveX controls, and be able
to invoke Methods and Properties of the ActiveX
140c. The HMI shall log all data in files in dBase IV format for easy retrieval in other
programs such as Microsoft Excel and Microsoft Query. It shall be possible to
log historical data directly to an ODBC Compliant database.
141d. The HMIs database editor shall provide a capability to browse the ladder/control
scheme documentation for direct tag import. This capability shall consist of a
wizard that enables on the fly tag creation without recompilation.
142e. The HMI shall provide an object model interface that provides the minimum
following HMI systems: The Application, Tag creation and values, Commands,
Activities, Security, Communications, and Alarm configuration.
14316. Networks
144a. The HMI shall have the ability to, while on a network, share project components
among multiple workstations during development and runtime, share data
logged by one workstation, and use NetDDE/OPC to share tag values among
multiple workstations.
145b. The HMI shall have the ability to store the following components on a central file
server: security, graphic displays, activity logs, alarm logs, and data logs.
14617. Client-Server Operations
147a. The HMI shall permit Client/Server operation whereby graphics functionality (full
operations) shall be provided at a client station.
148b. HMI Client/Server operation shall utilize Microsoft Active X technology and
standard Microsoft NT Peer Web (Windows NT 4.0 Workstation) or Internet
Information Services (Windows NT 4.0 Sever).

149c. The Client/Server shall implement security via Microsofts NT security model;
consequently, a Windows Primary Domain Controller will be required.
150d. Server
1511.) The HMI Server shall leverage NT 4.0 Workstation or Server
technology.
1522.) The HMI sever shall permit up to 20 client connections at any one time.
1533.) The Server will support the use of occasional browsing via the use of
Microsofts Internet Explorer Version 4 or 5.
154e. Client
1551.) The Client shall support the use Windows 95, Windows 98, and
Windows NT 4.0 Workstation/server.
1562.) Client stations are desired to be thin clients. Performance shall not
degrade at the thin client in terms of display refresh or display call-up.
(E.g. displays on the client refresh at a rate equal to or better to the rate
possible on the server).
1573.) The Client software will utilize a setup Wizard for initial configuration.
The setup wizard will allow the user to decide if the client will have
full access or View Only operation.
1584.) Two forms of client licensing schemes shall be available.
159a.) Dedicated Clients shall require a license file on the client.
160b.) Floating Clients shall require a license file on the graphic server
computer.
1615.) The client machines must cache copies of the MMI project graphics
locally and be able to automatically copy the latest graphic from the
server as required.
1626.) The client configuration must allow for the specification of an Alternate
Server should the connection with the primary server be lost.
1637.) A client-side command server shall be provided via an Automation
Interface, that allows commands to be issued from a Visual Basic
program running on an a client machine. Commands will be processed
in the same way that commands issued from a Client are processed.

PART 3 EXECUTION

13.1 INSTALLATION
1A. For industrial rated computers, the engineering division of the software manufacturer shall load and

0
1

test all software prior to shipment. The Contractor shall provide certification from the
manufacturer as part of Close-out Documentation.
2B. For desktop and notebook computers, the engineering division of the software manufacturer shall load
and test the software. The Contractor shall provide certification from the manufacturer as part of
the Close-out documentation.
3C. The Contractor shall be responsible for developing, loading and testing all program code that is
specific to this project.
3.2 SOFTWARE LICENSE
3.3 TRAINING
4A. Licensed copies of the software utilized on the project shall be signed over to the Owner at the
completion of the project.
5B. Human Machine Interface Software
61. Provide one licensed copy of the Development / Runtime package of the Human Machine
Interface Software.
72. Provide Runtime versions of the Human Machine Interface Software for each computer
requiring access.
83. Where client-server functionality has been specified provide the appropriate number of clientserver licenses.
9A. The manufacturer of the software shall provide a standard training course for the following software
packages.
101. Human Machine Interface Software
11a. The course shall provide the student with the skills needed to maintain and modify
the Human Machine Interface software. At a minimum the course shall cover
the following.
121.) Configuring Communication Parameters
132.) Modifying a Tag Database and Tag Monitor
143.) Configuring the Activity Log
154.) Modifying Graphic Displays
165.) Creating Macros, Symbols, Parameter Files and Key Definitions
176.) Modifying Derived Tag Files, Event Files, Recipe Files and Data Logging

Files

187.) Configuring Alarms, Trends and Security

198.) Running a project
20b. The course shall be for a minimum of four days.
21c. The course shall be provided for _____ representatives of the Owner.
22B. This training shall be provided in addition to project specific training that has been specified
elsewhere in the specification.

23C. The training shall be provided at a location provided by the manufacturer of the software within 100
miles of the facility.
24D. The manufacturer shall provide training coupons that are valid for usage within one year of the issue
date.