<<Contents>> <<Index>>

General NTPS200
Exapilot Professional,
Specications Exapilot Standard, Exapilot Ofce
Operation Efciency Improvement Package
GS 36J06B10-01E

OVERVIEW PACKAGE OVERVIEW

This GS provides an overview of the Exapilot
Operation Efciency Improvement Package. Reducing
operating costs (increasing prot) is a major issue for
plant operators. To enhance operating efciency and
increase prot, manual operations such as startup,
shutdown, load changes and grade changes need
to be automated.
The Exapilot; Operation Efciency Improvement
Package makes it easy for knowledgeable operators
to create semi-automatic sequences that replace
manual operation
Exapilot was developed to be Easy to Use, and
to Realize Continuous Improvements in Operating
Efciency, and it supports the following improvements
in operating efciency:
- 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.
It used to require a lot of control system resources
and engineering work to automate process control
system 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.

Exapilot runs on Windows OS. Using Exaopc (OPC

interface package), Exapilot can communicate with a
process control system (PCS), and access process
data.

F01E.ai

Figure: Exapilot Operation Main Window

Yokogawa Electric Corporation GS 36J06B10-01E

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

F03E.ai

Figure: Exapilot 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 36J06B10-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) or general purpose PC)

OPC server

PCS

F05E.ai

Figure: Function Overview

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B10-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 36J06B10-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
for advanced alarm
standard by Yokogawa.
User Procedure Module: Module created by user
Other types of unit procedure (and registered in a library).
Process parts for advanced alarm
Procedure templates for advanced alarm:
Special unit procedure equivalent to
Flow arrow a subprocedure for advanced alarm
Standard flow arrow
designed as a component (and registered
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:
Picture
Component subprocedure for advanced
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 36J06B10-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 36J06B10-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, Block mode Setting, Input from other main procedures variables, Output to other main
I/O Messages 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

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B10-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: Seamless connection to PCS
When Exapilot is connected to PCS, a standard OPC
interface compliant to the OPC (OLE for Process
Control) standard interface specications can be used.
Connections with various PCSs, not only Yokogawas
DCS (CENTUM VP/CS3000/CS 1000/CS) but also
other companies DCS and PLC systems, have already
been established.
Note: When establishing the connection through a third
party OPC server, the interoperability of the OPC
server must be checked by each project.
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: 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 36J06B10-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
This function facilitates opening a specied document Supporting CENTUM VP (R4.01)
or starting other programs in a message window. The connection between Exapilot (R3.60 or later) and
(Supported by R2.01 or later) CENTUM VP is supported by Exaopc (R3.50 or later).
This function also allows for opening a specied Exapilot (R3.60 or later) supports the operation on
document or starting other programs through text CENTUM VP HIS.
pasted to a workspace.
(Supported by R2.20 or later) Operation: Online Maintenance
Online Maintenance enables the revision per
Operation: Subprocedure Expansion Subprocedure without interrupting Main procedure
Function operation. This function enables the maintenance
without affecting Subprocedure which is not revised.
This function facilitates executing subprocedures that
are not wired. (Supported by R3.60.10 or later)
(Supported by R2.20 or later)
Builder: Parameter (variable) declaration
Operation: Procedure Display Mode Check functions
This mode only displays the procedure without This function helps operators conrm if the Parameter
executing it. (variable) used in the program are identical with the
declared parameters (variables).
(Supported by R2.20 or later) (Supported by R3.70 or later)

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B10-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 10
Operation: PCS Output Conrmation User VB Script Unit Procedure
functions The VB script created by users can be executed from
This function enables to display a dialogue window to Exapilot.
let operators/engineers conrm the PCS output.
(Supported by R3.70 or later) MS-Excel Add-Inn
This is an option to use MS-Excel for an operating
Utility: Support for IT Security window.
Several security models (legacy, standard, and The Exapilot data can be displayed on the cell of MS-
strengthened types) will be available, so that users Excel in real time. Moreover, graphical display is also
will be able to select the security level to match their available.
requirements.
(Supported by R3.70 or later) Self-doumentation
All the setting details of the Exapilots main procedure
can be export into Microsoft Word les (to be printed
on paper). It will help debugging of the procedural
ow charts or the les can be used as a management
Exapilot OPTIONAL PRODUCTS document.
(Supported by R3.80 or later)
Procedures Expansion
This option increases the number of main procedures
that can be executed concurrently with the Exapilot
Professional and Exapilot Standard, as well as the
number of main procedures that can be built and
number of Exapilot clients.

Multi-run Procedures Expansion

This option allows identical main procedures to be
executed by assigning different operating ID when
Exapilot starts. This makes it possible to monitor
operating progress and automate half the manual
operations for simple batch processes that do not need
to be rearranged.

Additional Advanced Alarm Function

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

MS-Excel Link Unit Procedure

Data input and output with MS-Excel is supported.

Exaquantum Link Unit Procedure

Data input and output with Exaquantum is supported.

E-mail Communication Unit Procedure

This option allows users to send e-mails from Exapilot
to the mail server.

ActiveX Component
This option is composed of the following components.
Users can create the original operating screen on
the HIS Graphic Window, MS-Excel, Visual Basic, or
Exaquantum Explorer.
- Grid Control
- Button Indicator Control for Procedure/Subprocedure
run or stop
- Message Component
- Correlation Diagnosis Component
- Trend Component
- Chart Component

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B10-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 11
APPLICATION CAPACITY
Exapilot Basic

Exapilot Basic
Item
Standard Professional Ofce (*4)
No. of installation 1 / PC
Installation Installed distination HIS XX (*1) X XX
PC Exaopc-installed PC or general-purpose PC XX
No. of built main procedures 5 20 5
No. of procedures concurrently executable 1 4 1
No. of multiple runs of Multi-run main procedures
No. of Exapilot client (*2) 2 8 2
1000 / main
No. of unit procedures 10000 / main procedure
Procedure procedure
Capacity and Max. No. of unit No. of unit procedures 1000 / subprocedure
Restrictions procedures No. of unit subprocedures 300 / main procedure
No. of unit procedure modules 1000 / main procedure
No. of registered procedure modules 1000 / PC
No. of PCS variables 5000 / main procedure (*3)
Max. No. of variables No. of Global variables 5000 / main procedure
No. of Local variables 1000 / subprocedure
PCS Data read from PCS XX
Communication Data write to PCS XX
Exaopc Exaopc OPC Interface Package XX XX
Connection Exaopc OPC Interface Package for HIS XX

XX: Available X: Available, however, the client can only be installed. : Not Available

*1: The Exaopc OPC Interface package (for HIS) needs to be prepared separately.
*2: Total number of Operation windows and Builder windows that can be connected at the same time to the procedure server.
*3: 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.
*4: Exapilot Basic Options and Exapilot Options cannot be added to Exapilot Ofce.

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B10-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 12
Exapilot Option
Exapilot Options can be added to Exapilot Standard or Exapilot Professional.
Exapilot Options can not be added to Exapilot Ofce.

Exapilot Basic Option Exapilot Option

Procedure Expansion Additional of
Multi-run Advanced Alarm
Item
Procedures Function
Standard Professional Expansion Standard/
Professional
Max. of 2 options/ Max. of 3 options/ Max. of 3 options/
No.of installation 1/PC
PC PC PC
HIS XX (*1) X XX
Installation Installed
Exaopc-installed
distination
PC PC or general- XX
purpose PC
No. of built main procedures +5/option (*2) +1/option (*7)
No. of procedures concurrently
+1/option (*3) +2/option (*4)
executable
No. of multiple runs of Multi-
+3/option (*8)
run main procedures
No. of Exapilot client (*5) +2/option (*6) +3/option (*9)
No. of unit 5000/multi-run 10000/main
10000/main procedure
procedures main procedure procedure
No. of unit
1000 / subprocedure
procedures
Procedure No. of unit
Max. No. 300 / main procedure
Capacity and of unit subprocedures
Restrictions procedures No. of unit
procedure 1000 / main procedure
modules
No. of registered
procedure 1000 / PC
modules
No. of PCS
5000 / main procedure (*10)
variables
Max. No. of No. of Global
5000 / main procedure
variables variables
No. of Local
1000 / subprocedure
variables
PCS Commu- Data read from PCS XX
nication Data write to PCS XX

XX: Available X: Available, however, the client can only be installed. : 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.
If one Exapilot Procedures Expansion is added onto Exapilot Professional, the number of procedures that can be created is
expanded to 25.
*3: Example: For Exapilot Standard + Procedures Expansion x 2, the number of main procedures that can be run concurrently
is 3.
*4: Example: For Exapilot Professional + Procedures Expansion x 3, the number of main procedures that can be run
concurrently is 10.
*5: Total number of Operation windows and Builder windows that can be connected at the same time to the procedure server.
*6: Example: For Exapilot Professional + Procedures Expansion x 3, the number of the Exapilot client is 14.
*7: If the Exapilot Multi-run Procedures Expansion is added onto Exapilot Standard, the number of procedures that can be
created is expanded to 6, allowing all procedures to be created as multi-run main procedures.
If the Exapilot Multi-run Procedures Expansion is added onto Exapilot Professional, the number of procedures that can be
created is expanded to 21, allowing all procedures to be created as multi-run main procedures.
*8: Example: For Exapilot Standard + Multi-run Procedures Expansion x 2
The number of multi-run main procedures that can be run concurrently is 2, and the total number of multiple runs with these
two main procedures amounts to 6.
*9: Total number of Operation windows and Builder windows that can be connected at the same time to the procedure server.
Example: If one Exapilot Multi-run Procedures Expansion is added onto Exapilot Standard, the total number of Operation
windows and Builder windows that can be connected at the same time to the procedure server amounts to 5.
*10: 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.

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B10-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 13
CONFIGURATION OF Exapilot ENGINEERING/OPERATION CLIENT AND
SERVER
More than one Exapilot client can be connected at the same time to Exapilot server.
Both Builder window and Operation window are referred to as Exapilot client. In case the maximum number of clients
is four, it can execute three Operation windows and one Builder window at the same time.
Operation Operation Operation
Exapilot
client

Exapilot
client/server Connection

Builder
F07E.ai

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B10-01E Dec. 7, 2009-00
<<Contents>> <<Index>> 14
SYSTEM CONFIGURATION
Example of Connection to CENTUM VP/CS 3000
PC
Exapilot Builder / Operation
Client

Ethernet

HIS ENG PC

Exaopc (*1)
Exapilot Builder / Operation +
Client Exapilot Builder / Operation
Client / Server
V net

LFCS LFCS

Exapilot Communications Data

Process data Read / Write

F08E.ai

*1: At System Conguration (Engineering) time, refer to Exaopc (OPC interface package) GS 36J02A10-01E.

Example of Connection to CENTUM Integrated System

PC
Exapilot Builder / Operation
Client
Exapilot Engineering / Operation
Client

E net Ethernet

ICS EWS HIS ENG PC

Exaopc (*1)
+
Exapilot
Builder / Operation
Client / Server
V net

COPSV EOPS ENGS

FCS LFCS
ABC

HF bus
CFSD EFCD

Exapilot Communications Data

Proces Data Read / Write
F09E.ai

*1: At System Conguration (Engineering) time, refer to Exaopc (OPC interface package) GS 36J02A10-01E.
Note: R2.10 or later version is required for CENTUM CS3000 and CENTUM CS1000.
R2.09 or later version is required for CENTUM CS.

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B10-01E Dec. 7, 2009-00
<<Contents>> <<Index>> 15
OPERATING ENVIRONMENT
Hardware Operating Environment
PC for installing Exapilot Server and Client functions
OS (As for detail, refer to the Software Operating Environment.)
Specication Item
Windows XP, Windows Server 2003 Windows Vista, Windows Server 2008
Machine Compatible Machine for IBM PC and AT (DOS/V)
Pentium III 600 MHz or faster
Required
CPU (Client PC ; Pentium III 500 MHz or faster) Core 2 Duo Processor 2.66 GHz or faster
Recommended Pentium III 1 GHz or faster
Required At least 512 MB At least 1 GB
RAM
Recommended At least 1 GB At least 2 GB
Disk At least 4 GB
V RAM (Video RAM) At least 128 MB
Color At least 32,768 colors
Resolution At least 1,024768 recommended
Sound Recommended (For message output)

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, Visual Studio 2005 (Service Pack 1) and Visual Studio 2008 (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 36J06B10-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 16
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 modelfor 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 36J06B10-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 17
MODEL AND SUFFIX CODE
Exapilot Operation Efciency Improvement Package
Description
Model NTPS200 Exapilot Operation Efciency Improvement Package
-S Basic Software License (with media)
1 For Exapilot Professional
2 For Exapilot Standard
Sufx Codes
3 For Exapilot for HIS (*1)
4 For Exapilot Ofce (*2)
1 English version
/-A10 For Exapilot Procedures Expansion (: required quantity) (*3)
/-A20 For Exapilot Multi-run Procedures Expansion (: required quantity) (*4)
/1-A30 For Exapilot Additional Advanced Alarm Function (*5)
/1-B10 For Exapilot MS-Excel Link Unit Procedure (*6)
/1-B30 For Exapilot Exaquantum Link Unit Procedure (*7)
Option Codes
/1-B50 For Exapilot E-Mail Unit Procedure
/1-B60 For Exapilot ActiveX Component (*8)
/1-B70 For Exapilot User VB Script Unit Procedure (*9)
/1-B80 For Exapilot MS-Excel Add-In (*10)
/1-B91 For Exapilot Self-documentation Option (*11) (*12)

*1: NTPS200-S31 doesnt have a function to output data to FCS. And any option can not be added to NTPS200-S31.
*2: NTPS200-S41 doesnt have a function to communicate with external. And any option can not be added to NTPS200-S41.
*3: The Exapilot Procedures Expansion can be added to NTPS200-S11 and NTPS200-S21.
*4: The Exapilot Multi-run Procedures Expansion can be added to NTPS200-S11 and NTPS200-S21.
*5: The Exapilot Additional Advanced Alarm Function can be added to NTPS200-S11 and NTPS200-S21.
Unit Procedure for Advanced Alarm Function is added by this option but procedures are not expanded.
NTPS200-S31 includes the Exapilot Additional Advanced Alarm Function.
*6: Microsoft Excel is required. The version must be 2003 or 2007. You can dene an MS-Excel le in either format of
Microsoft Excel book (*.xls)or Comma Separate Values le (*.csv).
*7: To use this option, Exaquantum (R1.10.00 or later) is required.
*8: Only when Exapilot Active-X Component option is pasted in Microsoft Excel, Microsoft Excel is required.
The version must be the following.
Microsoft Excel 2003/2007
Microsoft Visual Studio 2005(SP1)/ Visual Studio 2008(SP1)
*9: Microsoft Visual Basic required. The version must be Visual Studio 2005(SP1) or Visual Studio 2008(SP1).
*10: The Exapilot Self-documentation Option can be added to NTPS200-S11 and NTPS200-S21.
*11: To use this option, Microsoft Word 2003 or 2007 is required.
In case of applying Word 2003, there are some restrictions. For details, please contact Yokogawa.
When the self-documentation function is running, the PCs CPU loading increases.

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
1 For Exapilot Professional
Sufx Codes
2 For Exapilot Standard
1 Always 1
/-A10 For Exapilot Procedures Expansion (: required quantity)
Option Codes /-A20 For Exapilot Multi-run Procedures Expansion (: required quantity)
/1-A30 For Exapilot Additional Advanced Alarm Function

Note: Order to YMX customer service via FAX.

Note: Although the Exapilot Ofce is not ofcially supported, inquiries will be accepted for 90 days from the delivery date via the
following URL:
http://www.yokogawa.com/sbs/sbs-index.htm

All Rights Reserved. Copyright 2000, Yokogawa Electric Corporation GS 36J06B10-01E Sep. 16, 2010-00
<<Contents>> <<Index>> 18
ORDERING INFORMATION
Specify model and sufx codes.

TRADEMARK
- Exapilot, Exaopc, Exaquantum, Exaplog, Exasmoc and Exarqe are registered trademark of Yokogawa Electric
Corporation.
- CENTUM is a registered trademark of Yokogawa Electric Corporation.
- Windows, Excel, Word, Visual Basic 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 36J06B10-01E Sep. 16, 2010-00
Subject to change without notice.