<<Contents>> <<Index>>

General NTPS200
Exapilot Standard (for HIS)
Specications Exapilot for HIS
Operation Efciency Improvement Package
GS 36J06B20-01E

OVERVIEW PACKAGE OVERVIEW

The Exapilot Standard (for HIS), Exapilot for HIS;
Operation Efciency Improvement Package makes
it easy to create semi-automatic sequences that
incorporate the know-how of skilled operators, and
thus greatly reduce manual operation.
Exapilot was developed to be Easy to Use, and
to Realize Continuous Improvements in Operating
Efciency as follows:
- Reduce operating time while maintaining product
quality.
- Reduce labor while the plant is running safety.
- Prevent operator errors.
- Standardize operating procedure and operation
methods.
- Ensure that operator know-how is not lost.
The Human Interface Station (HIS) of CENTUM VP
or CENTUM CS 3000 or CENTUM CS 1000 supports
all the features of this software package. Versions for
HIS include:
- NTPS200-S21 Exapilot Standard (for HIS) (R1.03
and later), or
- NTPS200-S31 Exapilot for HIS (R1.03 and later).
It used to require a lot of control system resources and
engineering work to automate Process Control System
(PCS) manual operation procedures. And even after
procedures were established, changes in equipments
and products required expensive maintenance work.
To solve these problems, Exapilot builder functions
are designed to make it easy to represent operating
procedures, so that the maintenance is easy.
Exapilot builder functions include procedure
components such as Pump Start/Stop, Set Valve
Opening, Ramp Up/Down, Request Field Work, Pause,
Wait for Condition.
By linking these components on the screen, an
experienced operator can create a procedure that
operates as a semi-automatic sequence. A created
sequence can be used as an operating screen.
Note thatunlike Exapilot for HIS provides operating
guidance functions only, and does not output data to
PCS.

To run these packages requires the Exaopc OPC

Interface Package for HIS (HIS OPC), model LHS2411
or PHS2411.

F01E.ai

Figure: Exapilot Standard (for HIS) and Exapilot for HIS Operation Main Window

Yokogawa Electric Corporation GS 36J06B20-01E

2-9-32, Nakacho, Musashino-shi, Tokyo, 180-8750 Japan Copyright Sep. 15, 2000 (YK)
Tel.: 81-422-52-6375 Fax.: 81-422-52-5994 22nd Edition Sep. 16, 2010 (YK)
<<Contents>> <<Index>> 2

F03E.ai

Figure: Exapilot Standard (for HIS) and Exapilot for HIS Builder Main Window

FUNCTION OVERVIEW
Exapilot functions are based on an operational efciency improvement cycle which is repeated continuously to
maintain or improve operational efciency. Starting with Enhance to determine areas where efciency improvement
can be expected, Engineer (Build Procedures) and Operate steps are used to automate, and realize operating
efciency improvements. Evaluate and Identify steps are under development, and will be supported in the future.
Find areas to fine-tune,
to improve operating efficiency
Determine areas where efficiency
improvement can be more expected
Enhance Create procedures to
automate operation
Identify Engineer
Operating efficiency
improvement cycle

Evaluate Operate

Analyze operational log of Exapilot Use automated standard procedures during

evaluate improvement test operation / actual operation
F04E.ai

Figure: Operating Efciency Improvement Cycle

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B20-01E Dec. 7, 2009-00
<<Contents>> <<Index>> 3
FUNCTION OVERVIEW contd.
Exapilot Client Machine
(HIS (general-purpose PC), general-purpose PC, or Console HIS)

Builder functions Operating functions

Builder Operation XXXXXXX : Window
client client

Utility functions

Utility-related
window

Procedure execution and

management functions
(Procedure server)
Procedure
Procedure
database
execution
management
functions
functions
Procedure
database

Exapilot server machine

(HIS (general-purpose PC))

OPC server

PCS
F05E.ai

Figure: Function Overview

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B20-01E Jul. 15, 2008-00
<<Contents>> <<Index>> 4
Builder Functions Procedure Execution and Management
Easy to understand (easy to describe and congure an Functions
operation procedure). Executes and manages procedures dened by builder
functions.
Procedure Builder Functions
- Procedure Flow Builder Functions Procedure Execution Functions
- Procedure Flow Documentation Functions - Controls procedure ow.
Setting the header/footer - Client/server functions
Additional print out - Multiple-procedures execution functions
- Character variable functions - Ofine functions
- PCS tag existence-checking functions - Test run functions
- Parameter (variable) declaration check functions - PCS output conrmation functions
Operating Procedure Parts Procedure Database Management Functions
- Procedure modules - Procedure ow display functions (display data
- Intrinsic user functions (created using Visual C processing, database editing, syntax check)
language) supported
Utility Functions
Operating Functions These provide necessary functions for package
The procedure ow window displays procedure management.
operating status detail, for operation and monitoring.
Utility functions
Operation Monitoring Functions - Installer functions
- Operating procedure display - System parameter setting functions
- Operating data display - Procedure maintenance functions
- Output history display - Multiple OPC servers connecting functions
Operating Functions - Security functions
- Operation start/stop commands - Historical Report (Message) functions
- Detailed operating commands (skip, break, pause) - Historical Report (PCS output history) functions
- Operation message display - Watchdog Notication and Operation Status
Monitoring
- Event Record Management functions

Tool
- Save/Restore Procedures functions
- Prepare to Main Procedures functions
- Variable display functions

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B20-01E Dec. 7, 2009-00
<<Contents>> <<Index>> 5
PROCEDURE CONFIGURATION
On Exapilot the series of operation and monitoring Procedure Conguration
sequence are described on ow chart style or logic Main Procedure: Individual operating procedure
chart style, called Procedure. units, each with individual names
(Example: Boiler start-up).
Procedure Configuration Subprocedure: Units which are part of the hierarchy
below the main procedure and have
Main Procedure individual names (Example: Heating
Subprocedure process).
Subprocedure for advanced alarm: Advanced alarm
Subprocedure for advanced alarm units which are part of the hierarchy
Procedure Elements below the main procedure and have
individual names (Example: Valve failure
Procedure Flow monitoring).
Unit Procedure Procedure Elements
Procedure Flow: Individually-dened operating
Subprocedure procedures
Subprocedure for advanced alarm Unit Procedure: A process associated with a single
procedure ow.
Procedure Group Subprocedure: Special unit procedure representing a
Procedure Module process hierarchy
Subprocedure for advanced alarm: Special unit
Standard Procedure module procedure used to represent the hierarchy
User Procedure module of the procedure for advanced alarm.
Procedure Group: Special subprocedure
Procedure templates representing a group of unit procedures.
for advanced alarm
Procedure Module: Special unit procedure used to
Standard procedure modules represent a subprocedure part registered
for advanced alarm in a library.
Standard Procedure Module: Module provided as
User procedure templates
standard by Yokogawa.
for advanced alarm
User Procedure Module: Module created by user
Other types of unit procedure (and registered in a library).
Procedure templates for advanced alarm:
Process parts for advanced alarm
Special unit procedure equivalent to
Flow arrow a subprocedure for advanced alarm
designed as a component (and registered
Standard flow arrow
in a library).
Repetition flow arrow Standard procedure modules for advanced alarm:
"Yes" judgment flow arrow Procedure templates for advanced alarm
provided as standard by Yokogawa
"No" judgment flow arrow User procedure templates for advanced alarm:
Component subprocedure for advanced
Picture
alarm created by user (and registered in a
Graphics library).
Images Other types of unit procedure: The minimum
elements conguring the Procedure ow
Character string Process parts for advanced alarm: The unit
Text procedures which can be used in a
procedure for advanced alarm.
Rich text
Variables
PCS variables
Global variables
Global parameters
Local variables
Local parameters
Procedure information variables
Procedure server variables
Matrix local variables
Matrix global variables
F01-1E.ai

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B20-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 6
Flow arrow: Structural element used to represent a
procedure and connect subprocedures in
a ow chart.
Standard ow arrow: Starts from one subprocedure
(other than a decision subprocedure) and
connects to another, dening the order in
which they are processed.
Repetition ow arrow: Loops back to previous
processing (used to perform repeated
processing).
Yes judgment ow arrow: Branches to process
corresponding to Yes decision.
No judgment ow arrow: Branches to process
corresponding to No decision.
Picture: Graphics (JPEG or bitmap) to be pasted
on the work space and gure (circle or
line).
Character string: Program element for which a string
of characters, a rich text or a hyperlink
can be specied.
Variables: Data used in Exapilot.
PCS variables: Variables used to transmit data
between Exapilot and PCS.
Global variables: Variables declared as global (main-
procedure-level) variables
Global parameters: Variables declared as global
(main-procedure-level) parameters; can
be modied by user.
Local variables: Variables declared as local
(subprocedure-level) variables
Local parameters: Variables declared as local
(subprocedure-level) parameters; can be
modied by user.
Procedure information variables: Variables in which
main procedure specic inforemation is
stored.
Procedure server variables: Variables the procedure
server manages.
Matrix local variables: Local variables with one-
dimensional array or two-dimensional
aray
Matrix global variables: Global variables with one-
dimensional array or two-dimensional
aray

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B20-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 7
PROCEDURE FLOW
Procedure Flow created in Exapilot represent user procedures as owcharts.
The Unit Procedures are connected between the start and end terminals. In general, major procedures are created as
part of the top-level Main Procedure, with the second and lower levels used to represent smaller Subprocedures and
unit operations. Application programs may contain a hierarchy of up to 300 levels.

Structure Sample

Main Procedure

Procedure Group Procedure Group

Subprocedure Subprocedure

Start End
Unit
Subprocedure Subprocedure
Procedure

Subprocedure
Procedure Group Procedure Group

Subprocedure
Unit Operating procedure
Start Subprocedure End
Procedure can be hierarchy with
Unit up to 300 levels.
Procedure

Subprocedure
Repeat Unit Procedures represent
No - Pump start/stop
Unit Unit - Control valve opening setting
Start Procedure Procedure End
Yes - MV ramping
- SV ramping, etc.
F02E.ai

Unit Procedures

Unit Procedures Function / Unit Procedure Name

A unit procedure used to represent a procedure in a owchart format
Procedure ow symbols START terminal, END terminal, Subprocedure, Parallel 1, Parallel 2, AND, OR, Branch 1, Branch 2,
Output connector, Input connector
Input processing, Output processing, Unit procedures with message processing functions
Output to PCS (*1), Block mode Setting (*1), Input from other main procedures variables, Output to
I/O Messages other main procedures variables, Conrmation Messages, Guidance Messages, Alarm Messages,
Calculations, Substitution, HIS Operator Guide Messages, HIS Alarm Messages, HIS Window, Event
Wait, User Event Wait, String Operation, Statistic Processing, User Event Transmission, Start of User
Event Driven, End of User Event Driven, Reset of User Event, Matrix Calculation
Time processing, Unit procedures with time-series processing functions
Timer block
Timer, Clock, Start Timer, Stop Timer, Check elapsed time, Pause Timer, Restart Timer
In addition, unit procedures required to create various procedure ows
Parameter declaration, Pause, Start subprocedure command, Initialize subprocedure command, Judge
subprocedure status, End subprocedure command, Pause subprocedure command, End main procedure
Utilities command, Pause main procedure command, Start other main procedure command, Judge other main
procedure status, End other main procedure command, User function, Procedure group label, Comment,
Generic name declaration, Dynamical generic name, Event Record Search, Search, Matrix Search, User
Application, End, Matrix Declaration

*1: Output to PCS and Block mode Setting do not function with Exapilot for HIS.

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B20-01E Jul. 15, 2008-00
<<Contents>> <<Index>>
FEATURES AND FUNCTIONS
Builder and Operation: Client/Server
Functions
The Exapilot server PC can be accessed by a client
PC, for remote engineering and remote operation.
Builder: Intuitive GUI
Exapilot represents an operation procedure in owchart
format. No special programming language needs to
be learnt, and the user can easily perform buildering,
debugging, operation and maintenance.
Builder: Sharing and reusing of operator
know-how
Exapilot procedure ow engineering parts (unit:
subprocedure) can be stored in a library. Reusable
subprocedures can be used in user templates, and a
set of general-purpose standard templates is provided
with Exapilot.
Operation: Integrated man-machine
interface
By installing this application in an Human Interface
Station (HIS), a single man-machine performs both
process control monitoring and operation monitoring.
Operation: Operation procedure guidance
The main feature of Exapilot for HIS is to show each
procedure for mainly manual plant operation and
outputs guidance as the procedure.
Operation: Preserving operator know-how
The operating know-how of experienced operators can
be preserved as Procedure in owchart, as standard
operating procedures. Creating semi-automatic
Standard Operating Procedures can help prevent
operator errors.
Operation: Workow self-documentation
You can display a created workow on the
operating screen, and print out the workow as self-
documentation for the Standard Operating Procedure.
Operating know-how is shared among operators. This
function is helpful for operation training.
Operation: Debug functions
You can debug procedures either in ofine mode or in
trial mode.
- Ofine mode
This allows debugging without an PCS. Input values
that have been previously set in Exapilot are used.
Output values are not sent to the PCS, but those are
used within Exapilot.
- Trial mode
Data is input from PCS or from other procedures;
output values are not sent to the PCS, but those are
used within Exapilot.
All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation
8
Evaluation: Evaluation of operating
efciency
After actual operation, the operation history is displayed
in a chronological order, and the improvement due to
Exapilot will be evaluated. (Under development).
Identication: Finding operating procedure
enhancements
Displaying operating dead time, and the volume of
process requests and operator actions, suggests
where further improvements can be made. (Under
development).
Utility: Multiple OPC servers connecting
functions
This function enables users to dene the OPC server to
be connected separately for each procedure.
(Supported by R1.10 or later)
Builder: Character variable functions
This function allows users to describe other vendors
PCS tag name or data item.
(Supported by R1.10 or later)
Builder: PCS tag existence-checking
functions
This function checks the PCS tag existence and tag
type during the preparation to run procedures.
(Supported by R1.10 or later)
Utility: Security Functions
This function allows users to restrict operation to
authorized personnel and restrict operating procedures.
Users can qualify the scope of operations for each
operator.
(Supported by R1.10 or later)
Builder: Procedure Flow Printing Functions
- This function enables users to set header/footer
- This function enables users to specify optional
printing of exceptional ow, procedure modules, and
delete spare subprocedures.
(Supported by R1.10 or later)
Utility: Historical Report Functions
- Message Report
This function outputs Conrm, Alarm, Guidance, Error
messages to CSV type le.
- Output History Report
This function outputs the history that process
components have outputted, to CSV type le.
(Supported by R1.10 or later)
Builder: Graphics Drawing Function
This function allows users to draw lines, circles,
rectangles, and arrows on the workspace of Exapilot,
facilitating the creation of effective SOP (Standard
Operation Procedures).
(Supported by R2.10 or later)
GS 36J06B20-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 9
Operation: Procedure Operation Function Utility: Audit trail Function (Supporting 21
This function allows users to start and stop other CFR Part11)
procedures from a unit procedure. This function enables users to save the operation
(Supported by R2.10 or later) history such as procedure start/stop, the output
history, and the operating messages of Exapilot for
Operation: Message Window Component the specied period. Users can analyze, for example,
operation process from this history information.
This function allows users to copy a message window
and display it as a CENTUM VP/CS 3000/CS 1000 (Supported by R3.20 or later)
graphic for display.
(Supported by R2.10 or later)
Utility: Duplicate Exaopc Compliant
This feature enables Exapilot to support Exaopc OPC
Operation: Event Wait Unit Procedure server redundancy function version (Exaopc-RD).
This function allows reception of process alarm (Supported by R3.20 or later)
messages, sequence messages, and others from the
CENTUM. Utility: Save/Restore Procedures functions
(Supported by R2.10 or later) This function enables users to move the procedures
from other PCs and back up the procedures.
Operation: Automatic Update of Current (Supported by R3.30 or later)
Executed Unit Procedure
This function allows display of unit procedures of a Utility: Prepare to Main Procedures
hierarchical procedure that is being executed on the functions
Operation window. This function enables users to collectively prepare to
(Supported by R2.10 or later) Run Main Procedure on the Exapilot server.
(Supported by R3.30 or later)
Operation: Dynamical Generic Name
This feature facilitates swapping the existing tag name Builder: Hierarchically Arranged Procedure
with an arbitrary tag name. Module
(Supported by R2.20 or later) This function enables users to arrange procedure
modules hierarchically.
Operation: Dynamic Message Function (Supported by R3.40 or later)
This function facilitates changing the current message
and displaying a new message during system Procedure Execution: OPC Cache Read
operation. This function enables users to read data by Cache
(Supported by R2.20 or later) Read. (Supported by R3.40 or later)

Operation: Hyperlink Function Supporting CENTUM VP (R4.01)

This function facilitates opening a specied document Exapilot (R3.60 or later) supports the operation on
or starting other programs in a message window. CENTUM VP HIS.
(Supported by R2.01 or later)
This function also allows for opening a specied
Operation: Online Maintenance
document or starting other programs through text Online Maintenance enables the revision per
pasted to a workspace. Subprocedure without interrupting Main procedure
operation. This function enables the maintenance
(Supported by R2.20 or later)
without affecting Subprocedure which is not revised.
Operation: Subprocedure Expansion (Supported by R3.60.10 or later)
Function
Builder: Parameter (variable) declaration
This function facilitates executing subprocedures that
are not wired.
Check functions
This function helps operators conrm if the Parameter
(Supported by R2.20 or later)
(variable) used in the program are identical with the
declared parameters (variables).
Operation: Procedure Display Mode (Supported by R3.70 or later)
This mode only displays the procedure without
executing it. Utility: Support for IT Security
(Supported by R2.20 or later) Several security models (legacy, standard, and
strengthened types) will be available, so that users
will be able to select the security level to match their
requirements.
(Supported by R3.70 or later)

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B20-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 10
Exapilot OPTION
Procedures Expansion
This option increases the number of main procedures that can be executed concurrently with the Exapilot Standard,
as well as the number of main procedures that can be built and number of Exapilot clients.

Additional Advanced Alarm Function

This advanced alarm component allows monitoring of equipment module failure monitoring, process failure
monitoring, or operator misoperation monitoring during stead-state operation.

APPLICATION CAPACITY
Exapilot Basic Exapilot Option (*8)
Procedure
Additional
Item Expansion
Advanced
Standard for HIS (Adding is
Alarm
possible to
Function (*6)
Standard)
Max. of 2
No. of installation 1/PC 1/PC
options/PC
Installation Installed HIS (*1) X X (*9) X X
distination Exaopc-installed PC or
PC X X X
general-purpose PC
No. of built main procedures 5 +5/option (*2)
No. of procedures concurrently executable 1 +1/option (*3)
No. of Exapilot client (*4) 2 +2/option (*5)
10000/ 1000/ 10000/ 10000/
No. of unit procedures
main procedure main procedure main procedure main procedure
Procedure Max. No. No. of unit procedures 1000/subprocedure
Capacity and of unit No. of unit subprocedures 300/main procedure
Restrictions procedures No. of unit procedure modules 1000/main procedure
No. of registered procedure
1000/PC
modules
No. of PCS variables 5000/main procedure (*7)
Max. No. of
No. of Global variables 5000/main procedure
variables
No. of Local variables 1000/subprocedure
PCS Commu- Data read from PCS X
nication Data write to PCS X X
Exaopc Exaopc OPC Interface Package X
Connection Exaopc OPC Interface Package (for HIS) X X

X: Available : Not Available

*1: The Exaopc OPC Interface package (for HIS) needs to be prepared separately.
*2: If one Exapilot Procedures Expansion is added onto Exapilot Standard, the number of procedures that can be created is
expanded to 10.
*3: Example: For Exapilot Standard + Procedures Expansion x 2, the number of main procedures that can be run concurrently
is 3.
*4: Total number of Operation windows and Builder windows that can be connected at the same time to the procedure server.
*5: Example: For Exapilot Standard + Procedures Expansion x 2
The number of main procedures that can be run concurrently is 2, and the total number of multiple runs with these two main
procedures amounts to 6.
*6: Exapilot for HIS includes the Additional Advanced Alarm Function.
Other Exapilot Options cannot be added to it. (excluding the Voice Message Output Option.)
*7: Exapilot Standard is connected to the Exaopc OPC Interface Package (for HIS) as an OPC client, in this case, the total
number of PCS variables is not 5,000 but 1,000 per main procedure at the maximum.
*8: For options added to Exapilot Standard, please refer also to GS36J06B10-01E.
*9: The server and client packages of the Exapilot for HIS cannot be installed on separate PCs.

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B20-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 11
SYSTEM CONFIGURATION
Exapilot Standard (for HIS) / Exapilot for HIS and HIS OPC installed in one PC

HIS / HIS ENG Exapilot Client

+
Exapilot Server
+
HIS OPC

VL net / V net

LFCS LFCS
SFCS SFCS

Process Data
Read / Write
F06E.ai

Exapilot Standard (for HIS) and HIS OPC installed in separate PCs
Ethernet

HIS / HIS ENG General-purpose PC / HIS

HIS OPC Client
+
HIS OPC
Exapilot Client
+
Exapilot Server
VL net / V net

LFCS LFCS
SFCS SFCS

Process Data
Read / Write F07E.ai

Exapilot Standard (for HIS) Client and HIS OPC installed in one PC
Ethernet

General-purpose
HIS / HIS ENG PC / HIS

Exapilot Server
+ Exapilot
HIS OPC Client

VL net / V net

LFCS LFCS
SFCS SFCS

Exapilot
Communications Data
Process Data
Read / Write
F08E.ai

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B20-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 12
OPERATING ENVIRONMENT
Package Operating Environment
Versions for HIS:
Exapilot Standard (for HIS) R1.03 and later
Exapilot for HIS R1.03 and later

Hardware Operating Environment

PC both Exapilot Client-Server and HIS OPC installed
Machine: HIS (general-purpose PC HIS)
CPU: Pentium III 600 MHz or faster required (Pentium III 1 GHz or faster recommended)
Windows Vista, Windows Server 2008; Core 2 Duo Processor 2.66 GHz or faster
RAM: At least 512 MB required (At least 1 GB recommended)
Windows Vista, Windows Server 2008; At least 1 GB required (At least 2 GB recommended)
Disk: HIS area use + 4 GB or more
VRAM (Video RAM): At least 128 MB
Color: At least 32,768 colors
Resolution:At least 1,024 x 768 recommended
Sound: Recommended (for message output)
PC for Exapilot Standard (for HIS) Client and Server without HIS OPC installed
Machine: IBM PC/AT (or DOS/V) compatible
CPU: Pentium III 600 MHz or faster required (Pentium III 1 GHz or faster recommended)
Windows Vista, Windows Server 2008; Core 2 Duo Processor 2.66 GHz or faster
RAM: At least 512 MB required (At least 1 GB recommended)
Windows Vista, Windows Server 2008; At least 1 GB required (At least 2 GB recommended)
Disk: At least 4 GB
VRAM (Video RAM): At least 128 MB
Color: At least 32,768 colors
Resolution:At least 1,024 x 768 recommended
Sound: Recommended (for message output)
PC for Exapilot Standard (for HIS) Client without HIS OPC installed
Machine: HIS (general-purpose PC HIS) or console HIS
CPU: Pentium III 500 MHz or faster required (Pentium III 1 GHz or faster recommended)
Windows Vista, Windows Server 2008; Core 2 Duo Processor 2.66 GHz or faster
RAM: At least 512 MB required (At least 1 GB recommended)
Windows Vista, Windows Server 2008; At least 1GB required (At least 2 GB recommended)
Disk: At least 2 GB
VRAM (Video RAM): At least 128 MB
Color: At least 32,768 colors
Resolution:At least 1,024 x 768 recommended
Sound: Recommended (for message output)

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B20-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 13
Software Operating Environment
Exapilot (Server / Client functions)
Exapilot Revision OS Windows Service Pack
R1.01, R1.02,
Windows NT Workstation 4.0 or Windows NT Server 4.0 Stand-alone Server Service Pack 6a (4, 5)
R1.03, R1.10
Windows NT Workstation 4.0 or Windows NT Server 4.0 Stand-alone Server Service Pack 6a (4, 5)
R2.01
Windows 2000 Professional or Windows 2000 Server Stand-alone Server Service Pack 1
Windows NT Workstation 4.0 or Windows NT Server 4.0 Stand-alone Server Service Pack 6a (4, 5)
R2.10
Windows 2000 Professional or Windows 2000 Server Stand-alone Server Service Pack 2 (1)
Windows NT Workstation 4.0 or Windows NT Server 4.0 Stand-alone Server Service Pack 6a (4, 5)
R2.20
Windows 2000 Professional or Windows 2000 Server Stand-alone Server Service Pack 3 (1, 2)
Windows NT Workstation 4.0 or Windows NT Server 4.0 Stand-alone Server Service Pack 6a (4, 5)
R3.01 Windows 2000 Professional or Windows 2000 Server Stand-alone Server Service Pack 3 (1, 2)
Windows XP Professional Service Pack 1
Windows 2000 Professional or Windows 2000 Server Stand-alone Server Service Pack 4 (1, 2, 3)
R3.20 Windows XP Professional Service Pack 1
Windows Server 2003 Standard Edition
Windows 2000 Professional or Windows 2000 Server Stand-alone Server Service Pack 4 (1, 2, 3)
R3.30 Windows XP Professional Service Pack 2 (1)
Windows Server 2003 Standard Edition
Windows 2000 Professional or Windows 2000 Server Stand-alone Server Service Pack 4 (1, 2, 3)
Windows XP Professional Service Pack 2 (1)
R3.40, R3.50
Windows Server 2003 Standard Edition Service Pack 1
Windows Server 2003 R2 Standard Edition Service Pack 2 (1)
Windows XP Professional Service Pack 3 (1, 2)
Windows Server 2003 Standard Edition Service Pack 2 (1)
R3.60
Windows Server 2003 R2 Standard Edition Service Pack 2 (1)
Windows Vista Business Edition Service Pack 1
Windows XP Professional Service Pack 3 (1, 2)
Windows Server 2003 Standard Edition Service Pack 2 (1)
R3.70, R3.80 Windows Server 2003 R2 Standard Edition Service Pack 2 (1)
Windows Vista Business Edition Service Pack 2 (1)
Windows Server 2008 Standard Edition Service Pack 2

Note: Develop user functions using VC++6.0 (Service Pack 6), Visual Studio 2005 (Service Pack 1), VC.NET and Visal
Studio2008 (Service Pack1).
Note: The numbers in parentheses shows installable Windows service pack numbers.
However, the latest Windows service pack might be required when the OS causes some trouble in Exapilot.
Documnet Brower
Adobe Reader 9.3 or later
Note: It is neccessary to install Adobe Reader to read document of Exapilot.

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B20-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 14
Coexistence and Connectivity between Exapilot and other Solution-based Software Packages
Coexistence and connectivity are dened as follows.
Coexistence: Exapilot and other Solution-based Software packages are installed on the same PC.
Connectivity: Exapilot is connected to an Exaopc or HIS OPC via a network.
Note: Solution-based Software packages refer to Exaopc, Exaquantum, Exaquantum/Batch, Exaplog, Exasmoc and Exarqe
packages.

Operating Environment in Combination of Exapilot and OPC Interface Packages

- Exapilot can be connected to Exaopc OPC Interface Package R3.10 or later.
- Exapilot can be connected to Exaopc OPC Interface Package (for HIS) R3.05 or later.
- Revision of Exaopc Client must be same as revision of Exaopc Server to be connected.
Note: As for detail, refer also to GS36J02A10-01E (NTPF100 Exaopc OPC Interface Package).

Limitation for coexistence of Exa packages

Other Exa Packages

Server Client
Exapilot
Server Case1 Case1
Client Case1 Case2

The combination of Exa packages that can coexist with Exapilot is as show below.

Case1:

Exaopc Exaquantum Exaquantum Exaplog

Exasmoc Exarqe
(R3.60 or later) (R2.50 or later) /Batch (R3.30 or later)
Exapilot
OK OK (*1) N/A OK N/A N/A
(R3.08)

Case2:

Exaquantum
Exaopc Exaquantum Exaplog Exasmoc Exarqe
/Batch
(R3.10 or later) (R2.50 or later) (R3.01 or later) (R4.01 or later) (R4.01 or later)
(R2.50 or later)
Exapilot
OK OK (*1) OK (*2) OK OK (*2) OK (*2)
(R3.08)
*1: Exapilot adopts Legacy model for its IT security.
*2: Please pay attention to the installation procedure in case of installing clients of Exasmoc or Exarqe with Exapilot client
simultaneously on the Standard or Strengthened model of IT security.
For more information, please contact Yokogawa.
Note: Please check not only the type and version of the package but also the operating system environment.

Limitation for coexistence with HIS

Exapilot (R3.08) CENTUM VP HIS CENTUM CS 3000 HIS

Server/Client R4.01 or later R3.08.50 or later Exapilot for HIS, Exapilot Standard
Only the client of Exapilot Standard or
Client only R4.01 or later R3.05 or later Exapilot Professional can be installed in
an HIS environment.
Note: Please check not only the model and version of the package but also the compatibility of operating system environment.

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B20-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 15
MODEL AND SUFFIX CODE
Exapilot Operation Efciency Improvement Package
Description
Model NTPS200 Exapilot Operation Efciency Improvement Package
-S Basic Software License (with media)
2 For Exapilot Standard (*1)
Sufx Codes
3 For Exapilot for HIS
1 English version

*1: For options added to Exapilot Standard, please refer to GS36J06B10-01E.

Note: The Exapilot Ofce can be upgraded to Exapilot for HIS, Exapilot Standard, or Exapilot Professional.
The Exapilot for HIS can be upgraded to Exapilot Standard or Exapilot Professional.
The Exapilot Standard can be upgraded to Exapilot Professional.
Exapilot Annual Support Contract
The product is supplied at prices not covering the manufacturers warranty costs. Therefore, users are required to
sign annual maintenance contracts to receive maintenance service from the rst year of purchase onward.

Description
Model NTMS200 Maintenance Service for Exapilot
-S Annual Contract
2 For Exapilot Standard
Sufx Codes
3 For Exapilot for HIS
1 Always 1

Note: Order to YMX customer service via FAX.

ORDERING INFORMATION
Specify model and sufx codes.

TRADEMARK
- Exapilot, Exaopc, Exaquantum, Exaplog, Exasmoc, Exarqe are registered trademark of Yokogawa Electric
Corporation.
- CENTUM is a registered trademark of Yokogawa Electric Corporation.
- Windows, Excel and Visual Studio are registered trademark of Microsoft Corporation in the United States and /or
other countries.
- Ethernet is a registered trademark of XEROX Corporation.
- Pentium, Core 2 Duo are registered trademark of Intel Corporation.
- Adobe Reader is either registered trademarks or trademarks of Adobe Systems Incorporated in the United States
and/or other countries.
- All other company and product names in this GS are registered trademarks or trademarks of respective companies.

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B20-01E Sep. 16, 2010-00
Subject to change without notice.