Centum Cs 3000.pdf 3g5qm

Main memory (with ECC)

Non-volatile memory for storing application programs

U1


V net or Vnet/IP Interface

V net or Vnet/IP Interface

SEN Bus Interface

SEN Bus Interface

ESB Bus Interface

Comparator 2

U2

Comparator 1


Comparator 2

Comparator 1

U1

U2

Main memory (with ECC) Non-volatile memory for storing application programs

ESB Bus Interface

I/Obus (ESB) F070305.ai

Figure Configuration of Dual-redundant Processor Modules (SCS)

TI 33Q01B10-01E

Dec.14,2007-00

7. Safety Instrumented System (ProSafe-RS)

7-18

How an SCS is made dual-redundant is explained below.

U • Each processor module has two Us and two main memories. Each U module (U1 and U2) performs the same operation and the operation results are compared by two comparators for each operation cycle. If the operation results of both Us match, the operation is regarded as normal and the data is sent to the main memory and bus interface modules. The main memory modules are equipped with ECC (Error Correcting Code); these codes are used to correct temporary bit-reverse errors that occur in the main memories. The main memory modules with ECC are dual-redundant as well, and if their values are different, a matching error occurs and the control right is ed to the processor module on the standby side. • The operation results of U1 and U2 are compared by the two comparators. If either one of the comparators detect inconsistency, it is considered an “operation error” and the control right is ed to the processor module on the standby side. • Each processor module is equipped with a WDT (Watch Dog Timer) and monitors that the safety functions are operating normally. If it detects that the safety functions are not working normally, the control right is transferred to the standby side as well. • The processor module on the standby side synchronizes with the processor module on the control side to ensure that the same operations are performed. The control right can thus be switched without interrupting the operation. When the processor module obtains the control right, it immediately starts sending operation data to the bus interface modules. • A processor module conducts self-diagnosis if an operation error occurs. If there is no abnormality in U hardware as a result of diagnosis, it regards the error as a temporary operation error and recovers from the abnormal status to the standby status. • A processor module is equipped with communication interfaces that can dualredundancy on Us and V net or Vnet/IP interfaces are connected to dual-redundant control buses.

ESB Buses See Section 2.8.2 for the explanation of ESB buses.

TI 33Q01B10-01E

Dec.14,2007-00

7-19


7.3.3

States and Operations of SCS Depending on the operating mode and security level, SCS can be in one of several states. Operations of SCS include forcing, override, output enable operation and . The figure below shows a rough overview of the relations among these states and operations.

HIS

SENG Forcing Online-change

Offline

Override

Output enable operation

SCS (Operating mode:Running Mode)

security level SW 1 : (Level 1: For maintenance) 1 0 : (Level 0: For engineering)

0

2

2 : (Level 2: For safety operation)

Application logic execution function

SCS (Operating mode: Waiting mode) If all output channels are in “output enabled status,” the operating mode shifts from the waiting mode to running mode regardless of the security level.

Application logic Process data input/output function Inter-SCS safety communication function Diagnostic function

F070306.ai

Figure States and Operations of SCS

TI 33Q01B10-01E

Dec.14,2007-00

7-20


Operating Modes Operating modes indicate the different running states of an SCS. The operations carried out by the system program of an SCS are determined by the operating mode. There are five operating modes of an SCS: stop mode, loading mode, initial mode, waiting mode and running mode. Loading Mode Notification of completion of offline from the workbench

Request to start offline from the workbench

Stop Mode

SCS start request/SCS start

SCS power supply on

Completion of diagnosis/starting application logic execution function

Initial Mode

All output channels are in “output enabled status” Waiting Mode

Running Mode

At least one output channel is in “output disabled status”

The system can switch to this mode from all other modes

F070307.ai

Figure Transition of Operating Mode

Security Levels An SCS is equipped with a function to protect internal data from being overwritten by external devices. It always monitors attempts to write data from outside and judges whether operations should be enabled or disabled according to the security level of the SCS. The security level indicates to what degree the SCS memory is protected from data writing attempts from outside. There are two levels for the security level: a level (online level) used during constant operation of an SCS and a level (offline level) used when the SCS is not operating. Security level is protected by so that it cannot be changed. The status of the security level changes as shown below. SCS restart, offline , master database offline

Online Levels

Offline Level

SYS_SEC_CTL check (*1) Level 2

Level 1 check for level 1 and SYS_SEC_CTL check

check for level 0 and SYS_SEC_CTL check

Level 0

check for level 0 and SYS_SEC_CTL check F070308.ai

*1:

Regardless of the security level change permission status set by SYS_SEC_CTL, it is always possible to shift from security level 1 to security level 2 by entering an RST input in a SYS_SECURE block . Using SYS_SEC_CTL block, it can be decided whether security level is changeable or not by input of a foreign key switch.

Figure Transition of Security Level

TI 33Q01B10-01E

Dec.14,2007-00

7-21


Forcing and Override Overview of Forcing Function The forcing function provides a interface for fixing channel inputs and outputs of input/output modules and variables in application logic to constant values (variable lock), forcibly changing variable values (variable value setting) and so forth for the purpose of SCS maintenance and debugging I/O loop check applications. This function is used by an SENG to forcibly fix input/ output variables and internal variables of an SCS and allows fixing all input/output values of each input/output module at the same time as well. Additionally, it is possible to use SYS_FORCE function blocks to monitor the lock status within the application logic and forcibly cancel locking. The forcing function can also be used when performing maintenance tasks.

Overview of Override Override is a function used to temporarily overwrite values of variables of application logic in an SCS from an HIS in case of ProSafe-RS/CS 3000 integration structure. It is used for performing tasks in states where variable values of application logic are temporarily changed. The override function is used when performing system maintenance and similar.

Differences between Forcing and Override The table below shows differences between forcing and override. Table

Differences between Forcing and Override Item

Forcing

Override

Purpose

Maintenance of SCS and debugging applications from SENG

Maintenance of SCS from HIS in ProSafeRS/CS 3000 integration structure

SCS security level

Can be performed at level 1 or lower

Can be performed at level 2 as well

Necessity of programming

No need for programming

Necessary to use override FB to create application logic

Specification of output value

Possible to specify values to be output using the I/O Lock window and so forth

If override is performed while executing an application, pre-programmed values are output as override values.

Requirement for setting variable values

Whether or not forcing can be Possible to create application logic that performed depends on the security level allows switching override permission with a of SCS mechanical key switch, etc.

Grouping Override (*1) *1:

–

More than one override function block (hereinafter referred to as override FB) are managed as a logical group and a function to enable only one override FB to override can be selected in the group.

ed by ProSafe-RS R1.03.00 or later.

TI 33Q01B10-01E

Dec.14,2007-00

7-22


7.3.4

SOER SOER (Sequence of Events Recorder) is a function for acquiring and saving anaputs, discrete inputs, discrete outputs and variables of application logic as event information. This event information can be viewed using SOE Viewer. A time synchronization function is provided in order to maintain the accuracy of the time at which an event occurs.

Event Acquisition It is possible to acquire not only discrete inputs (DI) but also changes of discrete outputs (DO) and anaput values as event information. By creating function blocks for SOER, changes in application logic can be acquired as event information as well. This also allows ing changes in communication data with other SCSs.

Saving Events Event information is saved in an SCS, which eliminates the need to prepare a PC for storing events or keeping the power supply to an SENG turned on at all times. Event information before and after trip signals, which is particularly important, is saved in a different location. This information is notified to s without fail.

Viewing Events with SOE Viewer • Event logs (SOE event information and diagnostic information messages) saved in an SCS are ed to an SENG via V net / Vnet/IP and displayed as event messages by means of the SOE Viewer function of the SENG. • Event logs of up to eight SCSs can be displayed at the same time. • It is possible to filter event messages so that only desired messages are displayed. • Trip reports are generated. Generated trip reports can be exported to printers and CSV format files. • In the case of ProSafe-RS/CS 3000 integration structure, SCS process alarm messages can be displayed together by using the HIS historical information.

Time Synchronization Function An SCS has a function to synchronize time information among SCSs as well as between Us and DI modules in order to maintain a high accuracy of the event generation time records.

Time Synchronization Method of SCSs Connected to V net ProSafe-RS allows selecting from two synchronization methods: V net time master method (default), where all stations synchronize to the V net time, and GPS time master method (optional), where the time is acquired from an external source via the IRIG-B interface. V net Time Master Method (Default) The V net time is set by an SENG or HIS specified as time master. The time of each device connected via V net is synchronized according to the time information of the time master.

TI 33Q01B10-01E

Dec.14,2007-00

7-23


GPS Time Master Method (Optional) In this method, a commercially available GPS receiver is used to acquire time information of the IRIG-B format and use this in an SCS designated as the time master. The standard time (date, hour, minute, second) and the synchronization timing are delivered to each connected SCS. Synchronization among individual SCSs is achieved at this synchronization timing. Since GPS is used, it is possible to acquire events with high time accuracy.

Time Synchronization Method of SCSs Connected to Vnet/IP The time synchronization method of SCSs connected to Vnet/IP is fixed to the synchronization with Vnet/IP time. If an SNTP server is installed, it is possible to achieve highly accurate time synchronization with the standard time. The time synchronization status can be checked in the SCS State Management window of the SCS Maintenance Tool on the SENG, or in the SCS Status Display window on the CS 3000 HIS.

7.3.5

Subsystem Connection (Modbus) An SCS s a subsystem communication function that allows the SCS side to connect to other systems as the communication master, and a Modbus slave communication function that allows other systems to connect to the SCS as the Modbus communication master. In both functions, serial communication interface modules are mounted in SCS nodes in order to allow connections with other systems. Note that Modbus communication cannot be used for safety loops (they shall be used as interference-free modules). There are the following two types of subsystem communication modules. • RS-232C serial communication module (ALR111) • RS-422/RS-485 serial communication module (ALR121)

Subsystem Communication Function The subsystem communication function is used for reading and writing input/output data within subsystems from an SCS. SCSs the Modbus communication protocol. It is possible to connect to LED outputs and PLCs by accessing data of other systems via subsystem communication from SCSs.

Modbus Slave Communication Function With this function, an SCS is able to function as a Modbus slave device. The Modbus slave connection function of an SCS allows the Modbus master (external device) to read and write data in the SCS via the Modbus protocol. The Modbus master requests to access data in the SCS using the Modbus device name as the interface. Not only control stations of CS 3000, but also DCSs made by other manufacturers can connect to an SCS as the Modbus master.

TI 33Q01B10-01E

Dec.14,2007-00

7-24


7.3.6

Operation at SCS Errors There are three error levels for SCSs: fatal errors, major errors and minor errors. SCSs are able to recover from errors by conducting recovery tasks corresponding to each error level.

Operations at Fatal Error Occurrence At this error level, hardware and software are unable to function. U (both sides for redundancy) stops and output values of all output modules are set to fail-safe values.

Operations at Major Error Occurrence At this error level, some hardware is unable to function. Operations to be performed at abnormality, which are defined by s in advance, are performed for the failed areas. It is necessary to define such operations at occurrence of major errors individually for a given application.

Operations at Minor Error Occurrence At this error level, there is no impact on the application logic execution functions themselves. Such situations include when one side of dual-redundant hardware modules fails. If one hardware side in a dual-redundant configuration fails, the control right is switched to the standby side to continue processing. Such errors are treated as minor errors. The hardware continues to operate in the same way as if it were placed in a single configuration.

TI 33Q01B10-01E

Dec.14,2007-00


7.4

7-25

Test Functions

The test functions of ProSafe-RS are used for effective debugging of applications, and useful in debugging when you create or change applications. There are two types of tests, virtual tests and target tests.

7.4.1

Virtual Tests In a virtual test, an application is executed using an SCS simulator on an SENG, which allows debugging application logic of each SCS. In a virtual test, it is possible to execute test functions on the SCS simulator regardless of the security level. SENG SCS Manager(*1) Test operation

Result display

Execution environment (SCS simulator)

Application

F070401.ai

*1:

A function that controls system engineering and maintenance tasks of an SCS, such as definition of applications to be executed on the SCS, database generation test functions, etc.

Figure Virtual Test

7.4.2

Target Tests In a target test, an application is executed on an actual SCS. It is possible to execute tests in a status where inputs/outputs are disconnected, i.e., without any input/output modules connected, using the forcing function. In a target test, the tests that can be executed are limited by the security level of an actual SCS. SENG SCS Manager(*1)

Test operation

Result display V net or Vnet/IP Execution environment (SCS)

SCS Application

F070402.ai

*1:

A function that controls system engineering and maintenance tasks of an SCS, such as definition of applications to be executed on the SCS, database generation test functions, etc.

Figure Target Test

TI 33Q01B10-01E

Dec.14,2007-00

7-26


7.5

ProSafe-RS Related Packages

Various packages are provided in order to improve the integration with CS 3000 and systems made by other manufacturers as well as efficiency in operations/monitoring via integration.

SOE Viewer Package The SOE Viewer Package provides functions to display event logs (event information, diagnostic information) acquired in an SCS with the sequence of event recorder (SOER) function using a CS 3000 HIS or general PC (with V net or Vnet/IP interface card). SOE Viewer allows viewing event logs of a specified SCS. It also provides event log filtering, trip report generation and other functions.

Engineering Function for CENTUM CS 3000 Integration This package runs on an SENG and is used to integrate ProSafe-RS and CENTUM CS 3000. In a system integrating ProSafe-RS and CS 3000, it is possible to perform the following tasks on an SCS from an HIS and FCS. • It is possible to use tag names to operate and monitor data of an SCS from an HIS using the same interface as for FCSs. It is also possible to read data of an SCS from CS 3000 FCS. • It is possible to manage generation/recovery of process alarms and alarms from the annunciator detected by an SCS in the process alarm window of an HIS. • It is possible to monitor system alarms generated on an SCS in the system alarm window of an HIS. • It is possible to display the status of an SCS in the SCS status display window of an HIS.

SOE OPC Interface Package This package provides functions for installing an OPC server on an HIS of CENTUM CS 3000 or SENG and notifying event logs (event information and diagnostic information) acquired by the SOER function of the SCS to OPC clients via the OPC interface.

Modbus Communication Package This is the Modbus communication package used for SCSs to communicate with subsystems. With this package, an SCS is able to communicate with subsystems such as PLCs via interference-free serial communication modules (ALR111, ALR121) mounted on a safety control unit or safety node unit using the Modbus protocol. This package allows reading and writing subsystem data from application logic of an SCS.

TI 33Q01B10-01E

Dec.14,2007-00


7.6

7-27

Comparison of HIS Operation and Monitoring

The table below shows a comparison between CS 3000 and ProSafe-RS in of HIS operation and monitoring features. Table

Comparison of HIS Operation and Monitoring between CS 3000 and ProSafe-RS

Classification

CS 3000

ProSafe-RS

Window Call-up

HIS function

X

X

Operating Screen Mode

X

X

System Message Window

X

X

Window Sizing

X

X

X

X

X

X

X

X

Dynamic Window Set

X

X

Circulate Functions

X

X

Alarm Processing Functions

X

X

Print Screen Functions

X

X

Graphic Windows

X

X

Tuning Window

X

X

X

X

X

X

Process Alarm Window

X

X

Operator Guide Window

X

–

SCSs do not generate operation guide messages. (*1)

Message Monitoring Window

X

X

SCSs do not generate sequence messages. (*1)

Common Window Hierarchy Operation and Navigator Window Monitoring Set Functions

Operation and Trend Window Monitoring Trend Point Window Windows

Operation and Monitoring Functions

System Maintenance Functions

Process Reports

X

X

Historical Message Reports

X

X

Security Functions

X

X

Report Functions(Option)

X

X

Connecting an ITV Camera

X

X

CENTUM Desktop Environment Customization

X

X

Voice Messaging Functions

X

–

Multi-monitor Functions

X

X

Advanced Alarm Filter Function

X

X

Remote Desktop Function

X

System Status Overview Window

X

X

System Alarm Window

X

X

FCS Status Display Window

X

–

SCS Status Display Window

–

X

HIS Setting Window

X

X

Time Setting Dialog Box

X

X

Help Dialog Box

X

X

Control Drawing Window (Option)

X

–

X

–

X

–

X

–

Control Status Sequence Table Window Logic Chart Window (Option) Display Window SEBOL Window

Trend Functions

Individual package

X: *1: *2:

Remarks for ProSafe-RS

See “Table Mapping Blocks and Elements” for the assigned tags. 1second trends cannot be created.

SCSs do not %VM (voice messages). (*1)

Inhibited for safety reasons.

SENGs this function with a multi-language editor of Workbench.

SFC Window

X

–

Trends

X

X

Tuning Trend

X

X

Displaying Trends from Other Stations

X

X

Long-term Data Archive Functions (Option)

X

X

External Recorder Output Functions (Option)

X

X

Expert Trend Viewer Function (Option)

X

X

Open Interfaces (Option)

X

–

ed by the SOE OPC interface package.

FCS Data Setting/Acquisition Functions (PICOT) (Option)

X

X

Only data settings from external devices (elements) can be used. (*2)

Server for Remote Operation and Monitoring Function (Option)

X

X

Web Monitoring Functions (Option)

X

X

Configured Information Reference Function (Option)

X

–

Consolidated Historical Message Viewer Meeting FDA Regulations (Option) System Integration OPC Station (SIOS) (Option)

X

X

X

X

Only data settings (elements) from external devices can be used. (*2)

SOE package

X

X

Can be ed by SOE Viewer.

Generic Subsystem Gateway Package (Option)

X

X

Only data settings (elements) from external devices can be used. (*2)

Plant Resource Manager (PRM)

X

–

1-second trends cannot be created. See “Table Mapping Blocks and Elements” for the assignable tags.

Can be operated Blank: Cannot be operated –: No function See “Table Software Inputs and Outputs that can be used with SCSs” listed later. See “Table Mapping Blocks and Elements” listed later.

TI 33Q01B10-01E

Dec.14,2007-00

7-28


The table below shows a list of mapping blocks and elements. Table

Mapping Blocks and Elements

Classification

Description

Application Logic Definition Classification

Type name

Mapping block/element Type name/ Type element name

BOOL type

Internal variable BOOL

Mapping element %WB

Integer-type (32-bit)

Internal variable DINT

Mapping element %WB

Real number-type(32-bit)

Internal variable REAL

Mapping element %WB

Discrete

I/O structure

IO_BOOL

Mapping element %Z

Analog

I/O structure

IO_REAL

Mapping element %WB

Data settingn (BOOL)

FB

ECW_B

Mapping element %WB

Data settingn (integer)

FB

ECW_I

Mapping element %WB

Data settingn (real number)

FB

FB

Mapping element %WB

Anaput FB with data status

FB

ANLG_S

Mapping block

S_ANLG_S

Anaput indication

Anaput

FB

ANLG_S

Mapping block

S_ANLG_S

Velocity limit alarm

FB

ANLGI

Mapping block

S_ANLGI

Velocity limit

Velocity limit alarm

FB

VEL

Mapping block

S_VEL

Annunciator

Annunciator

FB

ANN

Mapping element %AN

BOOL-Type Data Override

FB

OVR_B

Mapping block

S_OVR_B

INTEGER-Type Data Override

FB

OVR_I

Mapping block

S_OVR_I

REAL-Type Data Override

FB

OVR_R

Mapping block

S_OVR_R

IO_BOOL-Type Data Override

FB

OVR_IB

Mapping block

S_OVR_IB

IO_REAL-Type Data Override

FB

OVR_IR

Mapping block

S_OVR_IR

FB

GOV_B

Mapping block

S_OVR_B

FB

GOV_IB

Mapping block

S_GOV_IB

FB

MOB_11

Mapping block

S_MOB_11

FB

MOB_21

Mapping block

S_MOB_21

FB

MOB_RS

Mapping block

S_MOB_RS

FB

MOA

Mapping block

S_MOA

FB

WD

Mapping block

S_WD

FB

SCI_B

Mapping element %WB

FB

SCI_I

Mapping element %WB

FB

SCI_R

Mapping element %WB

FB

SCO_B

Mapping element %WB

FB

SCO_I

Mapping element %WB

FB

SCO_R

Mapping element %WB

Internal variable Input/output variable Data setting from external device Anaput indication

Override from HIS

BOOL-Type Data Grouping Override (*1) IO_BOOL-Type Data Grouping Override (*1) BOOL-Type data manual operation FB with two-position answerback BOOL-Type data manual operation FB with three-position Manual operation answerback Auto-reset BOOL-Type data manual operation Analog-Type data manual operation

entry

Subsystem communication I/O

Subsystem communication input (BOOL) Subsystem communication input (integer) Subsystem communication input (real number) Subsystem communication output (BOOL) Subsystem communication output (integer) Subsystem communication output (real number)

*1:

ed by ProSafe-RS R1.03.00 or later.

TI 33Q01B10-01E

Dec.14,2007-00

7-29


The table below shows software inputs and outputs that can be used with SCSs. Table

Software Inputs and Outputs that can be Used with SCSs Name

by SCS

Element

Common switches

x

&SW

Global switch

x (*1)

%GS

Annunciator

x

%AN

Printout message (both printed and historical message)

%PR

Printout message (no printed message, historical messages only)

%PR

Operation guide message

%OG

Multimedia start message

%VM

Sequence message request

%RQ

Supervisory computer event message

%

Supervisory computer message output for PICOT

%M3

Signal event message

%EV

SFC/SEBOL retum event message output

%RE

x: ed Blank: Not ed *1: ed by ProSafe-RS R1.03.00 or later. FCS can refer to data of SCS global switch only from %GS001 to %GS128. Data after %GS129 is counted as invalid. Special function block is used for SCS transmission and reception.

TI 33Q01B10-01E

Dec.14,2007-00

8. Advanced Control Functions

8.

8-1

Advanced Control Functions The CENTUM CS 3000 is lined up with the Advanced Process Control Station (APCS) for advanced process control. This station is designed to periodically perform advanced process control and efficiencyimproving computations when incorporated in a plant operated highly reliably by CENTUM FCS. The CENTUM CS 3000 system can take advantage of advanced control functions of the APCS, which is also connectable to an existing CENTUM CS or CENTUM-XL system.

TI 33Q01B10-01E

June 30,2006-00

8-2


8.1

APCS Overview

The APCS (Advanced Process Control Station) performs advanced control and computations to improve the plant efficiency. The FCS executes set-point control, in which set-point is changed only a little, in one-second cycle. In the long control scan period, the APCS is used mainly in the following examples of control applications: • Control applications in which many computations are required. • Sophisticated control applications in which many additional and corrective actions are needed according to the change of the seasons or the plant conditions. However the APCS has same function blocks as the FCS, it does not take the place of the FCS. It s process control which the FCS performs, and it executes efficiency improvement. Ethernet HIS (for engineering)

HIS

V net

APCS

FCS F080101.ai

Figure Example of APCS System Configuration

TI 33Q01B10-01E

June 30,2006-00

8-3


8.2

Features of the APCS

The APCS has the following features:

A General Purpose Server Platform A general purpose server PC (personal computer) is employed, utilizing its high speed and large capacity for highly flexible control computations.

Wide-ranging Standard Function Blocks A wide range of control, monitoring, and other function blocks, which are used by the FCS, are available.

Unified Operation Procedures The APCS can be operated and monitored at the HIS, and its advanced control functions and computations can be managed as tags similar to FCS function blocks, so that alarms, which are occurred according to the advanced computations, can be operated and monitored at the same display of the FCS.

Close Connection with FCS The APCS is connected to the V net, enabling to share FCS function block data – in other words, APCS and FCS function blocks can be cascade-connected. The APCS inherits the bumpless and limit-check functions of the FCS and that ensures safer FCS connection compared to datasetting executed by a supervisory computer.

Online Maintenance Advanced computations (function blocks) of the APCS can be added, deleted and changed at online, so that system maintenance can be performed without changing algorithms of the FCS.

Unique Testing Environment The APCS action can be simulated for testing by APCS simulator, similar to the FCS. Also, a combined application of APCS and FCS simulators enables to simulate a plant environment using only the engineering HIS (ENG).

TI 33Q01B10-01E

June 30,2006-00


8.3

8-4

APCS Control Functions

APCS Function Specifications SEE

ALSO

8.3.1

For APCS function specifications, refer to GS 33Q03M10-31E.

Scan Period The APCS performs PID and other standard function blocks periodically. The FCS acts in onesecond cycle and the APCS executes advanced control in long scan period. For APCS scan period, see below. For standard block: Basic scan period: selected from 4, 8, or 16 seconds. High-speed scan period: 1 second

8.3.2

Function Blocks

Standard Blocks A wide variety of control, monitoring, and other standard function blocks available with the CS 3000 FCS can be used with the APCS. That permits control computation using General-Purpose Calculation (CALCU) blocks and SEBOL.

SEE

ALSO

For details on standard function blocks, refer to 4.1 Configuration of FCS Control Functions.

TI 33Q01B10-01E

June 30,2006-00

8-5


8.3.3

Input and Output of APCS The APCS uses a personal computer as its hardware and it can not access directly process I/O data, nor communicate with subsystems. Via communication, it acquires input data from the FCS and sends output data to the FCS. It thus can easily perform the advanced control computations for the set-point control executed by the FCS. The APCS provides an I/O capability that permits inputting the FCS function block data required for advanced control, performing advanced computation using the data as parameters, and outputting the results to the FCS function blocks.

Interface with FCS Data items and I/O terminals of FCS function blocks can be easily connected to the I/O terminals of APCS function blocks.

Software Input and Output Common switch and other software I/O are applicable to the APCS similar to the FCS. The software I/O configuration is shown below. Software input/output Internal status switch Common switch (%SW) Global switch (%GS) Message output Annunciator message output (%AN) Message for sequence control Print message output (%PR) Operator guide message output (%OG) Multimedia function start message output (%VM) Sequence message request (%RQ) Supervisory computer event message output (%) PICOT supervisory computer event message output (%M3) Signal event message output (%EV) SFC/SEBOL return event message output (%RE) F080301.ai

Figure Software Input/Output Configuration

8.4

APCS Operation and Monitoring

The HIS operation and monitoring function permits to the operation and monitoring of the APCS using the same interface as the FCS. From the standpoint of the operation and monitoring function, the APCS is a station executing the control function in accordance with the function blocks connected in the V net similar to the FCS. The APCS status can also be monitored on the system status overview window.

TI 33Q01B10-01E

June 30,2006-00


8.5

8-6

APCS Engineering

The APCS can be engineered using the system generation function in the same procedure as the FCS. APCS applications can be created in accordance with the function blocks similar to the FCS. Defining FCS common items

Defining APCS common items

Defining I/O modules

Defining function blocks

Defining function blocks

Virtual testing

Virtual testing

Target testing

Target testing

FCS procedure

APCS procedure

Engineering with CS 3000 engineering functions F080501.ai

Figure FCS & APCS Engineering Procedures

TI 33Q01B10-01E

June 30,2006-00

8-7


8.5.1

APCS Simulation Testing Similar to the FCS, the APCS operation can be simulated for testing. Additionally, APCS and FCS simulators can be used in combination to simulate a plant environment using only the engineering HIS (ENG). In the simulation test, FCS process data are acquired, the data are computed using them as parameters, the computed results are set at the FCS, and the set data are applied to the simulated operation in the simulated plant environment. Actual plant

APCS

Test function HIS memory ENG APCS simulator

FCS FCS simulator

Actual plant

Simulated plant

ENG F080502.ai

Figure APCS Testing

TI 33Q01B10-01E

June 30,2006-00

9-1

9. Batch Management Functions (Option)

9.

Batch Management Functions (Option) The powerful CS Batch 3000 batch process control package design considerations were ease of use, maintainability, and reusability.

9.1

Requirements for a DCS for Batch Processes

General requirements for a DCS for batch processes.

for Multiple Products To make multiple products in one process unit, the DCS must store multiple recipes internally. Recipes mainly consist of both procedures to manufacture products (phase control of process), and data (such as charge and temperature setting). A DCS must handle multiple recipes, and particularly multiple different procedures, flexibly, and make it easy to add new recipes. The design concept is based on the ISA S88.01 standard that requires the separation of the product-related information and the equipment control-related information.

Easy Operation It may be tempting to create custom operating screens for different recipes involving different procedures, but it is preferable – from the viewpoint of consistent operator interface – to use standard operation screens. Since each batch process typically corresponds to a dedicated control unit, for unit instrument views of batch process is desirable.

Open Environment It must be easy to recipes and schedules from a supervisory computer, and to batch production data to the computer.

for International Standards The standardization of batch processes is now in progress in the United States (ISA SP88) and Europe (NAMUR). For the internationalization of production, makers must international batch process control standards.

Higher Engineering Efficiency It is said that no two batch processes are the same, and that it takes at least four times as long to program a batch process as it does to program a continuous process. In fact, considerable man power is required to maintain, modify, and expand conventional batch programs. s now demand greater efficiency in programming and maintenance of batch programs using hierarchical programs, shared libraries, and reusable parts. The CS Batch 3000 Management Packages are designed to automate and systemize batch processes to fulfill these demands.

TI 33Q01B10-01E

June 30,2006-00


9.2

9-2

Main Functions of CS Batch 3000 Package

The functions of this package correspond to the Control Activity Model of ISA S88.01 as follows:

Recipe management *1

Information management

Scheduling management

Process management

: Covered by the CS Batch 3000 software

Unit supervision *2 *1: Process control (function block)

*2:

The ISA S88.01 Recipe Management covers general, site, master, and control recipes, but the CS Batch 3000 software s master and control recipes. Unit Supervision is a standard FCS function. It can be used without the CS Batch 3000 Recipe Management and Process Management package. F090201.ai

Figure ISA S88.01 Control Activity Model & CS Batch 3000

SEE

ALSO

For detail information of CS Batch 3000, refer to “Batch Management Package CS Batch 3000.” (TI 33Q01B3031E)

A recipe is created and managed by the recipe management function. The created recipe is called a master recipe. When the master recipe is used in an actual process, the master recipe is converted into a form usable in an actual process (Recipe setup). The “set up” recipe , called a “control recipe” is ed to the FCS and then it’s ready for use. Batch process status can be observed in the special batch management monitoring window. After a recipe is executed, results data are acquired and can be output as batch reports. As described above, the product-related information (recipe procedures, formulas, etc) and the equipment-related information (sequence control, etc) can be managed separately, so that the practical batch plants can be realized, permitting production for multi-product/variable volumes and frequent recipe changing.

TI 33Q01B10-01E

June 30,2006-00


9-3

HIS 1. Recipe creation(*1) Basic recipe 2. Recipe set up 6. Batch report printout Control recipe

Batch results 5. Batch results acquisition

3.

4. Recipe executed

*1: The master recipe can be created using not only HIS but also a network -connected general purpose PC.

Control recipe FCS

• Unit instrument blocks • Common blocks

F090202.ai

Figure Flow of CS Batch 3000

Recipe Management Functions Recipes can be organized into recipe groups, and up to one thousand recipes can be created in a group. Up to 16 recipe groups per project can be created. A recipe consists of the following four elements: • Recipe header (management information) • Procedure (manufacturing procedure) Described by SFC First use standard builder to create a unit sequence to be called from SFC. • Formula (recipe data) This consists of parameters such as charge and temperature setting. Common block (-definable variable block) is used. • Equipment requirement Choose generic process units corresponding to the requirement. At set-up time, assign actual units to be used. As described above, not only parameters but also sequence procedures in FCS are defined and managed on a per-recipe basis.

TI 33Q01B10-01E

June 30,2006-00


9-4

Process Management Functions (1) Recipe setup Set up a recipe using process management functions after completing the corresponding master recipe. Set Batch ID (ID to add a control recipe) and assign a unit that meets requirements (Unit assignment). Then, execute recipe setup and create control recipe. (2) control recipe to FCS. Use standard builder to create unit instrument block in FCS as target beforehand. There are two methods for ing: manual either manually from the process management window, or using SEBOL, or use automatic after recipe setup. (3) Recipe execution As for ing, there are two methods: manual start from the special batch management window or automatic start after . You can monitor and control batch process status using the special batch management window. (4) Batch results acquisition Batch results are acquired after recipe execution. Batch results consist of the formula used for execution and a log of messages generated. These batch results can be printed out as batch reports. These batch result data are acquired in relation to the batch ID.

TI 33Q01B10-01E

June 30,2006-00

10-1

10. Plant of Maintenance Inspection Works

10.

Plant Resource Manager (PRM) PRM (Plant Resource Manager), which contributes to enhance the efficiency of maintenance management of field devices, has the features, such as the capability of the preventive maintenance management and so on, corresponding to the bi-directional digital field networks represented by Foundation Fieldbus. It classifies and manages the device maintenance information, such as inspection schedules, inspection memos, and configuration information of devices, in various aspects, so that it is available for the versatile maintenance ways. It can also acquire the operation information of field devices from a remote area via the remote bus, so that utilizing above information as the field device maintenance information is easy. Furthermore, It contributes to saving of maintenance cost and reduction of TCO (Total Cost of Ownership) by the utilization of field device information.

• Inspection memo • Inspection schedule • Audit trail of device parameters

PRM client (instrumentation and control)

Parameter setting performed by operator

• Device master PRM server • Maintenance information • Parts list • Related information • Historical information • Device setting information

PRM client (maintenance)

Input of inspection and control data

4 to 20 mA analog devices

Field communication server

Online setting and acquisition of various parameters

Foundation Fieldbus Devices HART Devices F100001.ai

Figure Plant Resource Manager (PRM) Overview

SEE

ALSO

For details on Plant Resource Manager (PRM), refer to GS 33Y05Q10-31E.

TI 33Q01E10-01E

June 30,2006-00


10.1

10-2

Maintenance Information Managed by PRM

The maintenance information items managed by PRM are shown below. Table

Maintenance Information Items

Information Managed by PRM

Contents

Device master

Device tag names, device types, manufacturer names, revisions and so forth

Maintenance information

Inspection schedules, inspection memos

Parts list

Parts list including spare parts information, and so forth

Related information

Device specification sheets, parts composition

Historical information

Events of device, operation history of setting, calibrations, diagnoses and so forth

Device setting information

Setting data to devices

These information items are identified and related with each other, by the device ID assigned to device, so that you can call the information items easily. The historical information reserves the history of the items affecting to device, such as operation history of setting /calibration and so forth, events from device, and maintenance work records into the database. In addition to the data, it can record together who operated and what was the purpose. Especially, besides record reservation, data restoration ability, which can easily and safely restore the past operation parameters by the parameter comparison function, is also available.

TI 33Q01E10-01E

June 30,2006-00

10-3


10.2

Device Navigation Function

To get the necessary information form many devices in understandable way, PRM use the Device Navigation Function shown in below table. Table

Device Navigation Function

Kind of view

Function

Plant view

Display according to the logical position (plant hierarchy). In accordance with the use status, display in the categories of running devices at the plant, spare devices, devices under repair and so forth.

Network view

In accordance with field network configuration, display devices with the wiring conditions.

Class view

Display devices in the each type, such as vender, device type, revision and so forth.

In the plant according to its size, there are from tens to thousands of devices, and the spare devices, devices under calibration and broken-down devices, as well as running devices. By using this function, you can easily identify the status and type of devices.

TI 33Q01E10-01E

June 30,2006-00

10-4


10.3

of Maintenance Inspection Works

Device Status Monitoring By using the device status monitoring function from a remote place, you can confirm the device status immediately when abnormality occurred, and save the monitoring works at the plant-floor. • Can confirm the device parameters under abnormality, as well as the device status (normal or abnormal). • Can confirm the contents of abnormality by the alarm event notice corresponding to abnormal condition of device. These functions enable the system to present the information regarding the influence degree for plant operation when the device abnormality occurred, countermeasures, parts replaced for broken-down device, and availability of the spare device.

Calibration of Device For the field devices compliant with Foundation Fieldbus and HART, the following functions are available as the remote calibration function. • The parameter setting function (display, comparison and setting of parameter) • The method execution function (execution of specific calibration procedure of field device) • The PLUG-IN application function (execution of specific tool of field device)

Valve Diagnosis Among the field devices, a valve manipulates directly process, so that the diagnosis of the valve is important. By the enhanced function of valve positioner, the high accuracy diagnosis of valve has become available. PRM provides the execution environment of diagnosis program by the tool prepared in each device, as the specific PLUG-IN application of device. By the environment, the most suitable diagnosis to device is executed, and the history of start and finish is also managed and unified. By acquisition and store of the valve information, the statistical preventive maintenance of valve is available. The preventive maintenance enhances not only the efficiency of maintenance works but also the availability of plant operation by the prolongation of inspection period. Furthermore, the appropriate tuning based on storing information enhances the valve accuracy. The improvement of valve accuracy contributes to improve the quality and output-rate.

of Record and Report of Maintenance Inspection Result The management of the maintenance inspection result as work records is the effective information source of next inspection. The device information acquired online is effective for making inspection records of device. PRM provides following functions as of record and report of maintenance inspection result. • Make the inspection records according to inspection schedule. • Display explicitly the work status by the approval function for completion of inspection work. • Print the device information and maintenance inspection records in the unified format (self documentation function).

TI 33Q01E10-01E

June 30,2006-00

11. FDA: 21 CFR Part 11 Compllant Function (including option)

11.

11-1

FDA: 21 CFR Part 11 Compliant Function (including option) This function is compliant with 21 CFR Part 11 (Electronic Records; Electronic Signatures, hereinafter referred to as Part 11), issued by the Food and Drug istration (FDA), for providing criteria of acceptance by FDA that electronic records and electronic signatures are equivalent to paper records and handwritten signatures executed on paper. Part 11 specifically describes the “Security” and “Integrity” of electronic record. CENTUM CS 3000 provides Access Control Function and Audit Trail Management Function to be compliant with its requirements. Access Control Function (Personnel Authentication) • To protect systems and data from any break-ins • To control individual operations by authenticating an operator, an instrumentation engineer, and a recipe engineer Audit Trail Management Function • Automatically record the history of Operation, Recipe Creation, and System Maintenance (When, Who, What, Where, Why, How?) s are classified into HIS group operators, and engineering group engineers (instrumentation engineers, recipe engineers and operators with rights of reporting). Access control and the realization of audit trails, as well as setting locations, vary according to each . FDA-related packages and responses in those package functions are shown in the table below: Table

Optional Packages and Responses in Individual Group Functions HIS group, access control/audit trail

Engineering group (system builder, recipe builder,report builder) access control/audit trail

Access Package (FDA: 21 CFR Part 11 compliant)

-(*1)

x

Consolidated Historical Message Package (meeting FDA) (*3)

x(*2)

-

Optional package

*1: *2: *3:

SEE

ALSO

If access control is realized in an HIS, no optional package is required because access control is included in the standard security function. If an Exaquantum/Batch is installed as a historical message management server for HIS audit trail management, this package is not required. The LHS6510 Long-term Data Archive Package stores trend data, closing data, and historical messages over a long term on the HIS in which the package is installed. However, the LHS6510 does not cover such functions as the creation of reports retrieved from archived files and output as PDF files.

For details on FDA: 21 CFR Part 11, refer to TI 33Q01A61-01E.

TI 33Q01B10-01E

Dec 14,2007-00

11-2


The example of system configuration is provided in the below. The summarized and excerpted regulations from Part 11 regarding Data “Security” and “Integrity”; individual solution in CENTUM CS 3000 system are provided in the following pages. A: Audit Operator Events (Operation Events)

B: Audit Operator Events (Report and Print Events) (*1)

HIS Access Control Audit Trail

Access Control Audit Trail

Audit Trails of the Whole System and All Events System Audit Trail Database of groups (A to D) Audit Trail data server

•Save Data •Search Data •Report Search Result

Report

Site HIS

Ethernet


V net

C: Audit Instrumentation Engineer Events

FCS

PC

D: Audit Recipe Engineer Events

System Builders

Recipe Builders



HIS : Human Interface Station FCS : Field Control Station Note: Do not install engineering builder to HIS. F110001.ai

Figure Example of a System Configuration

TI 33Q01B10-01E

June 30,2006-00

11-3


11.1

Data Security

Data security is assured with tight restrictions for access rights. The contents of “Data Security” in Part 11 is classified into three major parts as below: • Making sure s only have authorized access into the system • Making sure s have accessed are authorized to carry out their roles • Making sure only the actual person has authorized performs operation Excerpted clauses from Part 11 regarding Data Security are listed below. Also, CENTUM CS 3000 provides following functions to meet the regulations. Table

Clauses Regarding Data Security and Solution in CENTUM CS 3000

Clauses Excerpted from Part 11 §11.10 (d)

Limiting system access (personnel authentication)

Solution in CENTUM CS 3000 Control by ID and . Control by ID and fingerprint. (*1), (*2) Identify by ID, , and/or fingerprint at operation (*1)

§11.10 (g)

Authority checks

Add classification of roles to s Add functional limitation to the object to be operated (Instrument, Window)

Manifestation of Electronic Security builder and its print. Signature and Electronic Records

§11.50

Electronic signatures that are not §11.200 (a) based upon biometrics §11.200 (b)

Automatic recording of Audit trail. Identify by ID and . Only entry is required from second

Electronic signatures based upon Identify by ID and fingerprint. (*1), (*2) biometrics

Uniqueness of each combined §11.300 (a) identification code and

Double registration check when ID is ed Privilege is required for the registration of ID Audit trail records automatically when ID is ed. (*2)

§11.300 (b)

Periodically check of identification Setting the validity of . code and issuance

§11.300 (d)

Detection and report function for unauthorized access

*1: *2:

Alerting system alarm when wrong operations are performed continuously more than the number of times set previously. (*2) Automatically record audit trail of alarm

For the fingerprint authentication device, we utilize 3rd party product. Only the solution for operators is available. The solution for engineers is in phased-plan.

TI 33Q01B10-01E

June 30,2006-00


11.2

11-4

Data Integrity

To assure the data integrity, an appropriate measure must be prepared. The data integrity verification includes providing log of not only the intentional data falsification and deletions but also accidental operations. In CENTUM CS 3000 systems, electronic records include operational record and meta-data. Meta-data includes raw data, file translation information, and audit trail that are used for assuring its operational records. Audit trail automatically records log whenever a changes electric records in the system. Moreover, audit trail does not allow any changes, fixes, and deletions after the log is recorded. Another integral part of data integrity verification by audit trial is accurate time data. To the operation result data has not been changed, meta-data such as the audit trial with time-stamps or system-configuration modified record is demanded. Electronic Records Operation records • Operation result data • Alarm data • Trend data • Recipe data Meta-data • Raw data • Audit trail of operation • Audit trail of system maintenance Audit trail regarding system configuration file (application file) after validation • Audit trail of recipe management Excerpted clauses from Part 11 regarding Data Integrity are listed below. Also, CENTUM CS 3000 provides following functions to meet the regulations. Table

Clauses Regarding Data Integrity and Solution in CENTUM CS 3000

Clauses Excerpted from Part 11

Solution in CENTUM CS 3000

§11.10 (b)

Records in both human readable Retrieval function of historical message and electronic form Output in general file formats (CSV, PDF, XML)

§11.10 (c)

• Retrieval of date and time, personnel, batch ID, systems, messages, and the like, according to specific retrieval conditions • Output retrieval results and retrieval conditions together as PDF files Archive and protection of records • Check functions of disk spare memory capacity in data archive function • Check functions of U load, communication capacity, and memory capacity used in a DCS system

§11.10 (e)

Audit trail

§11.10 (h)

Device checks

§11.10 (k-1) Audit trail over system §11.10 (k-2)

Controls over system documentation for maintenance

Audit trail (when, who, what, where, why, how) records automatically, when following operation is performed. • Plant operation performed by operators • System maintenance performed by system engineers • Recipe creation performed by recipe engineers • Report creation by operators with rights of reporting

TI 33Q01B10-01E

June 30,2006-00

12. Online Manual

12.

12-1

Online Manual All manuals are provided as electronic documents on CD-ROM. Adobe PDF file format, the de facto standard for distributing electronic documents on the Internet, is used. The manual may be displayed and printed on demand. You can jump to related documents from the document map. Using whole-text search functions, it is easier to find information in electronic documents than in paper documents - and electronic document save storage space.

12.1

Running Online Manual Viewer

From Windows Start Menu You can select the online manual and start the PDF viewer from the Windows Start Menu. You can select (start from) “Read me”, “Document Map”, “Reference Index” or “Using Online Manual”.

From Help Menu of Builder You can select an online manual from the Help Menu of any of the builder component programs. You can select (start from) “Using Online Manual”, “Engineering Basic Operation”, “Builder Definition Items List”, or “Reference Index”.

TI 33Q01B10-01E

June 30,2006-00

12-2

12. Online Manual

12.2

Convenient Ways to Use Online Manual

Here we explain some convenient (PDF-specific) ways of using the online manual.

Using Table of Contents and Index The table of contents and index contain clickable links that allow you to jump to the corresponding page.

List of Builder Definition Items If you select “List of Builder Definition Items” from the help menu of any builder program, then a list of builder definition items for the current builder is displayed. Click any item to jump to the corresponding page in the reference manual.

Search Functions The manual provides the following search functions available on its search window: Find all:

Search is made in the entire online manual.

Definition item search: Search is made for a builder definition item. Page search:

Search is made in the page displayed.

Additional Search Functions Retrieval search:

Search is made in the previously searched results.

Search history:

Up to 20 latest searched results are saved.

Favorites Frequently accessed pages can be ed for easy later retrieval. ed pages can be rearranged or de-ed as favorites in web browser.

TI 33Q01B10-01E

June 30,2006-00

13. Sequence of Events Manager (SEM) Function (Option)

13.

13-1

Sequence of Events Manager (SEM) Function (Option) The Sequence of Events Manager (SEM) provides the Sequence of Events (SOE) recording feature, which captures the events at the fast speed of 1ms potentially resulting in a plant trip and allows the acquired event data to be stored, displayed, and managed. The SEM applies trip signals from a device, such as a turbine, compressor, fan, or pump, that has serious impact on the plant operation to the sequence of events (SOE) input modules, thereby allowing SOE data to be acquired automatically at the specified trigger signal. A time-stamp synchronizing with an external master clock is added to SOE data acquired by the SOE input module, and the SOE data is displayed on the SOE Viewer in chronological order. The SOE data is output as a trip report or can be output to an external historian through an OPC. This feature will be effective for analysis of trip causes and data management.

TI 33Q01B10-01E

June 30,2006-00

13-2


13.1

System Configuration

The basic system configuration of SEM is shown in the figure below. SOE Viewer Screen OPC Client (Exaquantum)

Ethernet

SOE Server & OPC Server

SOE Viewer & HIS

SOE Server Configurator & ENG

SOE Viewer & HIS

V net GPS Antenna Master Clock

FCS

FCS

FCS

FCS

Ethernet

IRIG-B pulse-width coded signal

Process inputs/outputs (including SOE signals)

F130101.ai

Figure SEM Basic System Configuration

TI 33Q01B10-01E

June 30,2006-00

13-3


13.2

Functional Configuration

The SEM consists basically of a sequence of events (SOE) input module that captures plant event signals, an FCS with an SOE interface module (SB311), an SOE server that acquires SOE data from the FCS via Ethernet and stores them, the SOE viewers that display stored data under specified conditions, and an SOE server configurator that defines SOE server system configuration. The SOE data is time-stamped in the SOE input module and sent to the SOE server via the SOE interface module (SB311) in the FCS. The FCS performs a time synchronization with an external master clock using an IRIG-B time code format through an RS-422 signal. The acquired SOE data can be displayed and output for any purpose in accordance with the event message display function, trip detail display function, and trip report function ed by the SOE viewer. In addition, The SOE data can be output to an external OPC client, such as the Exaquantum historian. This feature allows the integrated management of SOE data by the Plant Information Management System (PIMS). SOE Server Configurator

SOE Viewer

entry

Viewer Function

Setting Function

Trip report

Event readout Definition information settings

Message readout Supervisory Computer

Microsoft SQL Server Definition information file

Viewer

SEM OPC Interface

Gathering file

Monitoring SOE Database Size

SOE Server Gathering Function

Time settings

IRIG-B

Historical message file SOE Server alarm display Operating status display

Event readout ENG

FCS

Time synchronization

HIS

SB311 & ADV151-E Card s Time Stamp

Definition information ing

FCS Properties SB311 Card Definitions IOM Builder Status Input (SOE)

SOE signal F130201.ai

Figure Functional configuration of the sequence of events manager (SEM)

TI 33Q01B10-01E

June 30,2006-00

13-4


13.3

Basic SEM Configuration Equipment and Software Packages

The SEM is comprised of the following basic equipment and software packages.

SOE Server The SOE server acquires and stores time-stamped SOE data from FCSs, and has a server function that transfers the stored SOE data to multiple SOE viewers upon request. The SOE server runs on Microsoft Windows 2000 Server or Windows Server 2003. The SOE server operates when an SOE server package (LPC6900) is installed in an SQL server PC on which Microsoft SQL Server 2000 is running. The SOE server uses two independent Ethernet networks: one for SOE data acquisition from FCSs, and the other for SOE data transmission to SOE viewers. Up to 2000 SOE inputs can be acquired by one SOE server. The number of SOE viewer clients that can be connected to one SOE server is determined by the number of Windows and SQL server client licenses. Configure the system with the number of client licenses needed for SOE viewers.

SOE Viewer The SOE viewers display SOE data stored by the SOE server in chronological order according to preset retrieval conditions. The SOE viewers operate when the SOE Viewer Package (LPC6920) is installed on a PC running Windows 2000 or Windows XP, connected to the SOE server via Ethernet. The SOE viewers provide the functions listed below: • Event mode display: Lists data source parameters set by the SOE viewer property and all messages matched with the date and time. • Trip trigger mode display: Lists trip trigger events in the range of dates set by the SOE viewer property. • Trip detail display: Displays all trip detail records relating to trigger events selected on the trip trigger mode display screen. • Automatic trip report mode display: Automatically acquires newly generated trip triggers. • Trip report output: Outputs the trip reports acquired by trip triggers to a csv type file and/or a printer.

TI 33Q01B10-01E

June 30,2006-00

13-5

13. Sequence of Events Manager (SEM) Function (Option) S

SOE Viewer - D:\CS 3000\his\s\Soe\Viewer\SoeViewerProp.soe

File

Action

E T Event Trip

View

Help

Query Filter No Filt Clear

Timestamp Quality 07/10/03 14:47:47.798 07/10/03 14:47:47.798 07/10/03 14:47:47.798 07/10/03 14:47:47.798 07/10/03 14:47:47.798 07/10/03 14:47:47.798 07/10/03 14:47:47.798 T 07/10/03 14:47:48.799 H 07/10/03 14:47:48.799 07/10/03 14:47:48.799 H 07/10/03 14:47:48.799 07/10/03 14:47:48.799 H 07/10/03 14:47:48.799 07/10/03 14:47:48.799 H 07/10/03 14:47:48.799 Events 282 to 297 of 9520

Prev

Next

Type SOE-H SOE SOE-H SOE SOE-H SOE SOE-H SOE SOE-H SOE SOE-H SOE SOE-H SOE SOE-H

Up

Trip

ID SOE_RTN SOE_RTN SOE_RTN SOE_RTN SOE_RTN SOE_RTN SOE_RTN SOE_ALM SOE_ALM SOE_ALM SOE_ALM SOE_ALM SOE_ALM SOE_ALM SOE_ALM

Sorted by Timestamp

Trip

Setup

Resource SOECARD SOECARD SOECARD SOECARD SOECARD SOECARD SOECARD SOECARD SOECARD SOECARD SOECARD SOECARD SOECARD SOECARD SOECARD

Print Export

Reference SOEDI0026 SOEDI0027 SOEDI0028 SOEDI0029 SOEDI0030 SOEDI0031 SOEDI0032 SOEDI0001 SOEDI0002 SOEDI0003 SOEDI0004 SOEDI0005 SOEDI0006 SOEDI0007 SOEDI0008

Query at 07/10/03 14:52:25

Message Plant DI0026 SOE Input Recover Plant DI0027 SOE Input Recover Plant DI0028 SOE Input Recover Plant DI0029 SOE Input Recover Plant DI0030 SOE Input Recover Plant DI0031 SOE Input Recover Plant DI0032 SOE Input Recover Plant DI0001 SOE Input Plant DI0002 SOE Input Plant DI0003 SOE Input Plant DI0004 SOE Input Plant DI0005 SOE Input Plant DI0006 SOE Input Plant DI0007 SOE Input Plant DI0008 SOE Input Tip Detail [SOEDI0006] F130301.ai

Figure Trip detail display

The SOE viewer displays SOE data stored by the SOE server and can also access HIS message databases and Unified Operator Interface (UOI) servers to allow an integrated data display of SOE and other message data. Up to eight message data sources can be assigned.

Field Control Station (FCS) with SOE Interface Module The SEM provides the following four FCS models. These models incorporate two SOE interface modules (SB311) and one IRIG-B branch unit per FCS. • Models AFS30D-HE and AFG30D-HE 19-inch Rack Mountable, Duplexed Field Control Units for FIO and 19-inch rack mountable • Models AFS40D-HE and AFG40D-HE Duplexed Field Control Units for FIO with Cabinet The SB311 module is installed in a dual-redundant configuration consisting of ESB-bus modules with an Ethernet port (for SOE server) and an RS-422 port (for time synchronization). An Ethernet port is connected to the SOE server via an Ethernet hub. An RS-422 port is connected to an external master clock via an IRIG-B branch unit inside the FCS. RS-422 cables are cascadeconnected to the IRIG-B branch units in each FCS, and an YCB128 RIO bus terminator is attached at the end of the FCS. Up to 16 FCS’s can be connected to an SOE server. The SOE viewer can display data sources for up to eight SOE servers. If 16 or more FCS’s are used, or 2000 or more SOE data items are used, use multiple SOE servers.

SOE Digital Input Module (ADV151-E) The SOE signals are connected to the SOE Digital Input Module (ADV151-E) installed on a local node in the FCS. Up to 32-point SOE signals can be applied to one ADV151-E module. For each input terminal, the SOE signal input specifications can be set. The status of SOE signal can be used as FCS control and monitoring signals. The ADV151-E module specifications are the same as those of the ADV151-P module except for the SOE-specific functions.

TI 33Q01B10-01E

June 30,2006-00


13-6

SOE Server Configurator The SOE Server Configurator is a builder for the SOE server to define the configuration required for acquiring SOE data from the FCS. The SOE Server Configurator (LPC6910) operates when installed on a PC running Windows 2000 or Windows XP connected to the SOE server via Ethernet.

SEM OPC Interface The SEM provides an OPC interface function for transferring SOE data stored in the SOE server, to an OPC client, such as Exaquantum, connected via Ethernet as an OPC alarm and events (A&E) server. The SEM OPC interface function works when installing the SEM OPC Interface Package (LPC6930) on a PC running as an SOE server.

External Master Clock The FCS, to assure 1-ms SOE data resolution and time, performs time synchronization by a pulse-width modulated IRIG-B code signal using an external master clock that incorporates GPS and through an RS422-interface. In addition, time synchronization by the SOE server is executed periodically with an FCS via Ethernet for SOE data acquisition. Time synchronization for SOE viewers, human interface stations (HIS’s), and network equipment, such as an engineering PC, depends on the system configuration. So, use a network time protocol (NTP) to separately set the SOE server.

13.4

System Monitoring and Maintenance Functions

The SEM provides the following functions for system monitoring and maintenance. • Monitor the SOE server • Display operating status of the SB311 and ADV151-E • Monitor free disk space capacity of the SOE server • Backup and restore the SOE server database

TI 33Q01B10-01E

June 30,2006-00

14-1

14. Event Viewer Package

14.

Event Viewer Package Event Viewer Package can search and analyze by filtering historical message from various viewpoints.This package enables plant analysis for the purpose of improving operation efficiency by achieving upgraded controllability and further automation as well as reduce operator’s workload. Event Viewer Package allows visual analysis of historical messages with an event viewer window collaborating with the Standard Operation and Monitoring Function on HIS. The HIS includes a historical message report window, which provides an overview display of various historical messages as alarm message records, operator work records, and the like. Main objectives of the historical message report window are to display, find and print process alarms, operation records, and system and process related events. In addition, Event Viewer Package provides graphs as bellow. • Message Summary Window (lower left) Display all messages of daily (0:00 to 23:59) historical messages • Event Balance Trend (EBT) graph window (left top) Display the rate of event occurrences per minute. There are number of events that action required to operator (on the positive axis) and action by operator (on the negative axis). • Category Sort Window (right top) Display sorted events with various conditions. (Alarm occur/recover, Event type, etc.) • Point ID Window (lower right) Display event IDs such as tag names with sorted by frequency, tag name order, etc. These windows are allowing an intuitive and quantitative analysis of historical messages through mouse operations. Upon the occurrence of the most recent event, the data storage period is the past seven days, inclusive of the date upon which the event occurred. However, days when no events occur are not included in this period. EBT (event balance trend) Graph Window

Message Summary Window

Category Sort Window

Point ID Window F140001.ai

Figure Event Viewer Window

TI 33Q01B10-01E

June 30,2006-00

15. Long-term Trend Historian Package (LTTH)

15.

15-1

Long-term Trend Historian Package (LTTH) Long Term Trend Historian (LTTH) acquires process data and alarm messages, stores them over a long term, and displays them with a specific viewer function, providing plant analysis features. LTTH consists of an LTTH server and LTTH clients. An Exaopc OPC Interface Package (for HIS) is required to acquire process data and alarm messages. LTTH Server Ethernet LTTH Client ENG

HIS

HIS

HIS

HIS

OPC

V net

SFCS

LFCS

KFCS

FFCS

F150001.ai

LTTH Server Function • Acquires tag items defined by the CENTUM CS 3000 trend acquisition pen assignment builder and event messages and stores them over a long term. • Runs on a PC separate from a human interface station (HIS) and acquires data via an OPC interface package incorporated in the HIS.

TI 33Q01B10-01E

June 30,2006-00

15. Long-term Trend Historian Package (LTTH)

15-2

LTTH Client Function • Runs on the HIS and displays trend data and event messages saved on an LTTH server. • Allows a simple analysis of alarms and event messages that occur during a specified period. The following screens are provided:

Trend and alarm analysis screens Trend data, alarms and event messages, and screen displaying tag names that most frequent of alarm occurrences within a specified period are displayed together; these data, alarms and messages can linked to each other screens for display.

Trend compare screen Two trend graphs are displayed side-by-side to compare current trend data with former trend data.

Data to Be Saved Data Save Period

Data Type

Amount of Data Saved

Trend data

On a per-acquired-data basis

For one year

Message

All messages at a time

For one year

Data Acquisition Period Data to be acquired are specified by Trend Acquisition Pen Assignment on the HIS. The LTTH data acquisition period is automatically determined in accordance with the data acquisition period specified by the HIS as given below: Data acquisition period specified on HIS

LTTH data acquisition period

One second

Ten seconds

Ten seconds

One minute

One minute

One minute

Two minutes

Two minutes

Five minutes

Five minutes

Ten minutes

Ten minutes

TI 33Q01B10-01E

June 30,2006-00

16-1

16. CENTUM CS 3000 Related Software Packages

16.

CENTUM CS 3000 Related Software Packages Yokogawa’s Exa-series software packages eliminate the information gap between business and control domains and allow Manufacturing Execution System (MES) technology to be applied to increasing plant safety and plant efficiency, reducing manpower, and increasing product quality.

16.1

Exapilot: Operation Efficiency Increase Package

For non-steady-state operation – such as startup and shutdown, emergency operation in response to process or device abnormalities, or manual intervention during normal operation – variation in operator skills can cause process irregularities or product quality problems, and affect operational efficiency. With the Exapilot package, an experienced operator can incorporate his skills to automate operation and monitoring, and maintain quality of operation at a consistently high level. Each function of Exapilot is provided based on the operational efficiency improvement cycle, “Plan, Define, Operate, Study, Improve”, so that can add for plant changes or new operating methods – and improve operational efficiency – by repeating the Exapilot cycle to create new Exapilot applications. Exapilot applications use Standard Operation Procedures (SOP) to display operation know-how in an intuitive format. Exapilot Operation - Plant A Reactor Phase

File Operation Change View View Window Message Tools Help 100%

Plant A Reactor Phase

Heating Time

Message

10:50:15 Start Heating Phase Loading

START

10:10:20 Start Loading Ingredients

Heating

10:02:13 Check Recipe Ingredients 09:23:10 Start Loading Solvent 09:03:33 Check Solvent Recipe 08:50:09 Start Plant A Reactor Phase

Cure

Drain

Condense

08:37:47 Check Phase

Crystallize

Confirm Message

Generated Message

99/06/30 10:50:15

Confirmed

Where START

TIC00. SV Set to 50 DEGC

If Heating doesn't complete in Set Time Phase switches to Pause Mode

TIC001. MODE Changed to AUT

99/06/30 10:50:27

Start Heating Phase

AND

Heating Complete

Heating Time Monitoring Timer

OK

Cancel Heating Phase End

Loading Time Over

F160101.ai

Figure Exapilot Operation Efficiency Increase Package display example

TI 33Q01B10-01E

June 30,2006-00

16-2

16. CENTUM CS 3000 Related Software Packages

16.2

Exaopc: OPC Interface Package

Recently there has been progress in sharing data between DCS and Manufacturing Execution System (MES) computer systems; plant information is useful at the top level of the business, and s are demanding information systems which provide timely information to business activity. In the process industries, data sources range from instruments in the factory to the control room database. Until now, accessing DCS operating data from a supervisory computer has been rather difficult, so MES computer access to operating data was not easy. Yokogawa, with its Exaopc OPC (OLE for Process Control) interface package, offers an OPC Foundation (*1) standard interface which solves these problems. Yokogawa also offers proprietary functions which enhance this interface. *1:

The OPC foundation is a non-profit foundation with over 300 corporate .

MES Application Exaplog

Exaquantum

Exapilot

Features of Exaopc

Exasmoc

OPC interface

• Uses OPC standard interface • Can connect to many types of system • Can act as process data server for MES applications

• Process data historian

Process data

CENTUM CS, CS 1000, CS 3000 CENTUM-XL, µXL

Other company PLCs

Exarqe

Application

In addition Yokogawa-specific functions

• DCS message historian • Message output to HIS*2 • Notify taglist equalization • Security management functions*2 Other company DCSes

PCS *2: Applies to CENTUM CS 1000/CS 3000 only. F160201.ai

Figure Exaopc OPC Interface Package

TI 33Q01B10-01E

June 30,2006-00

App.-1

Appendix Correspondence of Abbreviations and Product Models

Appendix Table

Correspondence of Abbreviations and Product Models

Correspondence of Abbreviations and Product Models

Category

Field Control Stations

Abbreviation

Product Name

Product Model

KFCS

Standard Type Field Control Station for FIO

AFS30 AFS40

KFCS2

Enhanced Type Field Control Station for FIO

AFG30 AFG40

LFCS

Standard Type Field Control Station for RIO

AFS10 AFS20

LFCS2

Enhanced Type Field Control Station for RIO

AFG10 AFG20

FFCS

Compact Field Control Station for FIO

AFF50

SFCS

Compact Field Control Station for RIO

PFC-H

Safety Control Units (Rack Mountable Type)

SSC10 SSC50

Enclosed Display Style Console Type HIS

LPCKIT

Open Display Style Console Type HIS

YPCKIT

Desktop Type HIS

Common PC

Safety Control Station

SCS

Human Interface Stations

HIS

Bus Converter

BCV

Bus Converter

ABC11-

Communication Gateway

CGW

Communication Gateway

ACG10S

TI 33Q01B10-01E

Dec.27,2006-00

Blank Page

Ind-1

CENTUM CS 3000 Production Control System System Overview TI 33Q01B10-01E 12th Edition

INDEX A Access to Relevant Builders ...............................3-63 Achievement of both Safety and High Availability ....1-8 Achievement of High Availability by Redundancy ...7-4 Achievement of Safety Rating SIL3 with Single Configuration ................................................. 7-4 Acquire a Wide Variety of Alarms and Events ....3-69 Acquisition of Certification Conforming to International Standard ................................... 1-8 Additional Search Functions ...............................12-2 Advanced Alarm Filter Function ..........................3-40 Advanced Control Functions ................................ 8-1 Advanced Process Control Station (APCS) ......... 2-4 Alarms & Events (A&E) Server Function ............3-57 Alarm & Event Information ..................................3-57 Alarm Priority Levels ...........................................3-15 Alarm Processing Functions ...............................3-15 Alarm Status Transfer up Window Hierarchy ....... 3-9 Analog Calculation Blocks ..................................4-10 Analog Faceplate Block ......................................4-10 Analog I/O Module ..............................................2-34 An Example of Window Hierarchies ..................... 3-8 APCS Control Functions ....................................... 8-4 APCS Engineering ................................................ 8-6 APCS Function Specifications .............................. 8-4 APCS Operation and Monitoring .......................... 8-5 APCS Overview .................................................... 8-2 APCS Simulation Testing ...................................... 8-7 Applicable Data for Data Exchange ....................6-20 Application Capacity of Compact FCS for RIO ...2-25 Application Standards .........................................2-50 Arithmetic Calculation Blocks .............................4-10 Auxiliary Blocks ...................................................4-10 Auxiliary Windows ................................................. 3-4 A General Purpose Server Platform ..................... 8-3

B Basic SEM Configuration Equipment and Software Packages .....................................................13-4 Batch Management Functions (Option)................ 9-1 BCV Settings .......................................................2-55 Benefits ...............................................................3-41 “BEST2” Maintenance System .............................. 1-6 Breakpoint Functions .................................6-10, 6-12 Builder ................................................................... 6-8 Business Information PCs and Supervisory Computers ..................................................... 2-4 Bus Converter (BCV) ............................................ 2-3

C C-Tick Mark Compliance (Electrical and electronic equipment without C-Tick mark can’t be sold in Australia and New Zealand) ........................2-50 Calculation Blocks...............................................4-17 Calculation Functions .........................................4-10 Calibration of Device ...........................................10-4 Cautions ..............................................................2-53 CENTUM CS 3000 Related Software Packages ..16-1 CENTUM Data Access Library ...........................3-57 CENTUM Desktop Environment Customization ...3-38 CENTUM V and CENTUM-XL Migration to CENTUM CS 3000 ........................................ 1-6 CE Mark Compliance (Electrical and electronic equipment without CE mark approval can’t be sold in Europe) ............................................2-50 Choose the Type of Control Station Based on Plant Scale .............................................................. 1-5 Circulate Functions .............................................3-14 Close Connection with FCS .................................. 8-3 Closing Data Information ....................................3-58 Combination of I/O Modules and Terminal Blocks ...........................................2-30 Common Block Information ................................3-58 Common Operation and Monitoring Functions .... 3-3 Communications Gateway Unit (CGW) ................ 2-4 Communications Input/Output ............................4-21 TI 33Q01B10-01E

Dec.14,2007-00

Ind-2 Communications with Subsystems Through an FCS (Option) .......................................................... 5-1 Compact FCS for RIO (PFCh-H/-S/-E) ...............2-25 Comparison of HIS Operation and Monitoring ...7-27 Compatible with Other Yokogawa Systems.......... 1-6 Compliance with Various Standards ...................2-50 Concurrent Engineering .................................6-1, 6-5 Concurrent Engineering on a Network ................. 6-5 Configuration and Mounting of Compact FCS for RIO ..............................................................2-25 Configuration of Engineering Functions ............... 6-2 Configuration of FCS Control Functions ............... 4-2 Configuration of Operation and Monitoring Functions ....................................................... 3-2 Configuration of Safety Control Units .................7-14 Configuration of Safety Node Units (SNB10D)...7-16 Configured Information Reference Function (Option) ........................................................3-63 Connecting an ITV Camera ................................3-37 Connecting Subsystems ....................................... 5-1 Connection with Other Systems ........................... 7-4 Connector Type Digital I/O Module .....................2-36 Connector Type Multiplexer Module ...................2-38 Console Type HIS ................................................. 2-8 Consolidated Alarm Management Software for Human Interface Station (CAMS for HIS) (Option) ........................................................3-69 Consolidated Historical Message Viewer Meeting FDA Regulations (Option) ...........................3-64 Container Functions ............................................3-24 Continue to Use Existing Resources (Hardware, Software, Know-how) ................. 1-6 Control Drawings (Option) .................................... 4-3 Control Drawing Definitions ................................6-18 Control Drawing Examples ................................... 4-4 Control Drawing Window (Option) ......................3-48 Control Functions a Wide Range of Applications ................................................... 1-5 Control Objects ...................................................3-19 Control Status Display Window ..........................3-48 Convenient Ways to Use Online Manual ............12-2 Coordination with SmartPlant Instrumentation ...6-20 Correspondence of Abbreviations and Product Models ..................................................... App.-1 U.................................................. 2-45, 2-47, 7-18 U Failure.........................................................2-49

D Data Access (DA) Server Function .....................3-57 Data Acquisition Period .......................................15-2 Data Binding Functions .......................................3-24

Data Flow between Function Blocks and Subsystems ................................................... 5-4 Data Integrity ....................................................... 11-4 Data Reading ........................................................ 5-4 Data Security....................................................... 11-3 Data to Be Saved ................................................15-2 Data Transfer Unit ...............................................6-20 Data Writing .......................................................... 5-5 Dedicated Cabinets ............................................2-23 Dedicated Cable ................................................. 7-11 Define Alarms and Events Attribute ....................3-69 Desktop Type HIS ...............................................2-10 Device Functions .......................................6-21 Device Navigation Function ................................10-3 Device Status Monitoring ....................................10-4 Differences between Forcing and Override ........7-21 Disk Capacity ......................................................3-54 Displaying Trends from Other Stations ...............3-53 Distributed Engineering of FCS ..........................6-14 Domain .................................................................. 2-6 Drastically Synchronize ......................................2-53 Dual-redundant SCS and Reliability of SCS.......7-17 Dynamic Window Set ..........................................3-13

E Easy Function Configuration ................................ 1-7 Easy Links to Information Systems (ERP, MES systems) ..................................... 1-3 Easy Operation ..................................................... 9-1 Edit Headers, Footers .........................................6-15 Edit Table of Contents .........................................6-15 Enclosed Display Style Console Type HIS ........... 3-1 Engineering and Operation/Monitoring Functions on the same PC ............................................. 6-3 Engineering Data Exchange Function ................6-20 Engineering Environment ..................................... 6-3 Engineering Functions .......................................... 6-1 Engineering Functions on dedicated PC .............. 6-3 Engineering Function for CENTUM CS 3000 Integration....................................................7-26 Engineering PC (ENG) ......................................... 2-3 Engineering Procedure ......................................... 6-6 Enhanced MC/Switch Instrument Blocks ...........4-19 Enhance and Integrate Existing Systems ............. 1-6 Enterprise Technology Solutions .......................... 1-1 ER Bus Interface Module ....................................2-16 ESB Bus .....................................................2-45, 2-47 ESB Buses ..........................................................7-18 ESB Bus and ER Bus .........................................2-15

TI 33Q01B10-01E

Dec.14,2007-00

Ind-3 ESB Bus Slave Interface Module........................2-16 Ethernet........................................................2-5, 2-40 Event Acquisition.................................................7-22 Event Viewer Package ........................................14-1 Exaopc .................................................................. 2-4 Exaopc: OPC Interface Package ........................16-2 Exapilot: Operation Efficiency Increase Package.......................................................16-1 Expanded Test Functions ...................................6-13 Expert Trend Viewer Function (Option) ..............3-56 Export Function ...................................................6-20 Extending the V net .............................................2-40 External Master Clock .........................................13-6 External Recorder Output Functions (Option) ....3-55

F Faceplate Blocks.................................................4-18 Faceplate Block Functions..................................4-10 Favorites .............................................................12-2 FCS Data Setting/Acquisition Functions (PICOT) (Option) ........................................................3-59 FCS for FIO (KFCS, KFCS2, FFCS) ..................2-13 FCS for FIO Application Capacities ....................2-13 FCS for RIO (LFCS, LFCS2) ..............................2-19 FCS for RIO Application Capacity.......................2-19 FCS Status Display Window ...............................3-44 FCU Configuration in FFCS ................................2-14 FCU Configuration in KFCS and KFCS2 ............2-13 FDA: 21 CFR Part 11 Compliant Function (including option) ......................................... 11-1 Features ..............................................................3-59 Features of ProSafe-RS ....................................... 7-4 Features of the APCS ........................................... 8-3 Fieldbus........................................................2-5, 2-41 Fieldbus Connection (FCS for FIO) ....................2-42 Fieldbus Connection (FCS for RIO, Compact FCS for RIO) ........................................................2-43 Fieldnetwork I/O (FIO) ........................................2-27 Field Bus Input/Output ........................................4-21 Field Control Station (FCS) ..........................2-3, 2-12 Field Control Station (FCS) with SOE Interface Module .........................................................13-5 Field Control Station Control Functions ................ 4-1 Field Control Unit (FCU) .....................................2-13 Field Control Unit (FCU) for RIO .........................2-19 Field Wiring Using KS Cable Interface Adapter ..2-31 Field Wiring Using Pressure Clamp Terminals ...2-31 FIO Nodes ..................................................2-45, 2-47 Flexible, Durable System that can be Optimized for Your Plant ...................................................... 1-5

Flow of Process...................................................3-59 Forcing and Override ..........................................7-21 Four Types of FCS to Choose from, for Flexible System Configuration .................................... 4-1 Free Signal Flow between Control Drawings ....... 4-3 From Help Menu of Builder .................................12-1 From Windows Start Menu .................................12-1 Full-Screen Mode.................................................. 3-4 Functional Configuration .....................................13-3 Functional Safety Standards...............................2-50 Functions of CAMS for HIS .................................3-69 Functions of SIOS ...............................................3-66 Function Blocks..............................................4-3, 8-4 Function Block Lists ............................................6-16

G General-Purpose Calculation Blocks..................4-10 General of CAMS for HIS....................................3-69 General of VTSPortal ..........................................3-67 Generic Name .....................................................4-12 Generic Subsystem Gateway Package (GSGW)....2-4 Generic Subsystem Gateway Package (Option)....5-6 Graphic Definitions..............................................6-17 Graphic Objects ..................................................3-18 Graphic Windows ................................................3-18

H Hardware .............................................................. 1-6 Hardware Configuration ........................................ 5-5 Hardware Configuration Devices .......................... 7-9 Hardware Configuration of SCS .........................7-13 Hardware Implementation Requirements............. 7-8 Help Dialog Box ..................................................3-47 High-Reliability Controllers to Safeguard Your Plant............................................................... 1-5 High-speed Data Update ...................................... 3-1 Higher Engineering Efficiency .............................. 9-1 Historical Message Information ..........................3-58 Historical Message Reports ................................3-31 HIS Function Specifications .................................. 2-8 HIS Setting Window ............................................3-46 Human Interface Station (HIS).......................2-3, 2-8 Hybrid Faceplate Block .......................................4-10

I I/O Module...........................................................2-16 I/O Modules .........................................................2-33 I/O Module Nests ................................................2-32 I/O Module Nests and I/O Modules.....................2-27 TI 33Q01B10-01E

Dec.14,2007-00

Ind-4 I/O Reports ..........................................................3-31 I/O Units (IOU) ....................................................2-21 Implementation of Control System Technologies ...7-4 Import Function ...................................................6-20 Improved Security and Safety for Plants .............. 1-8 Improvement of Plant Safety ................................ 1-8 Individual Test ....................................................... 6-6 Input/Output Modules .........................................7-10 Input and Output of APCS..................................... 8-5 Instrument Faceplates ........................................3-19 Integrated Monitoring with CS 3000 ..................... 7-4 Integrated Safety Instrumented System for Processes ...................................................... 1-8 Integration with Control System ............................ 1-8 Inter-SCS Safety Communication ........................ 7-6 Interface with FCS ................................................ 8-5

L Links to Factory Automation (FA) Systems........... 1-3 List of Builder Definition Items ............................12-2 List of Function Blocks ........................................4-14 Logic Chart Blocks ................................................ 4-8 Logic Chart Window (Option)..............................3-50 Logic Operation Blocks .......................................4-10 Long-term Data Archive Functions (Option) .......3-54 Long-term Trend Historian Package (LTTH) ......15-1 LTTH Client Function ..........................................15-2 LTTH Server Function .........................................15-1

M Maintenance Information Managed by PRM ......10-2 Maintenance Service ............................................ 1-6 Main Functions of CS Batch 3000 Package ......... 9-2 Main Window ........................................................ 3-4 Management Cost Reduction ............................... 1-6 Marine Standards................................................2-51 Mechanism of Inter-SCS Safety Communication ...7-6 Merging of Engineering Data ................................ 6-5 Message Functions.............................................3-66 Message Monitoring Window .............................3-30 Methods of Representing Sequences .................. 4-6 Migrated Field Control Station (RFCS2) ............... 2-4 Migration from CENTUM CS 1000 to CS 3000 .... 2-7 Minimize Total Cost of Ownership, Increase Profits.............................................. 1-6 Modbus Communication Package......................7-26 Modbus Slave Communication Function ............7-23 Mounting of FCS for FIO .....................................2-17 Mounting of FFCS ...............................................2-18

Mounting of I/O Units ..........................................2-26 Mounting of KFCS and KFCS2 ...........................2-17 Mounting of LFCS FCUs and Nodes ..................2-23 Multi-function Graphics .......................................3-24 Multi-monitor Function .......................................... 3-1 Multi-monitor Functions ......................................3-39 Multi-window Display ............................................ 3-5 Multi-window Mode ............................................... 3-5 Multiple Project Connection Functions (Option) ....6-4 Multipoint Control Analog I/O Module .................2-37

N Navigator Function ..............................................3-10 Navigator Window ............................................... 3-11 Networks .............................................................2-39 Nodes ..................................................................2-21 Node Interface Units (NIU)..................................2-21 Node Units (NU) for FIO......................................2-16 Normalize/Standardize Alarms and Events ........3-69 Number of SCSs ................................................... 7-8 Number of SENGs ................................................ 7-8 Number of Stations ............................................... 7-8

O Offsite (Option) ....................................................4-20 Offsite Block Functions (Option) .........................4-13 One-shot Execution Functions ..................6-10, 6-12 One-touch Multi-window Display Functions ......... 3-1 Online Documentation .......................................... 1-7 Online Maintenance .............................................. 8-3 Online Maintenance Functions ...........................6-19 Online Manual .....................................................12-1 Opening Windows and Acknowledging Process Alarms..........................................................3-16 Opening Windows and Acknowledging System Alarms..........................................................3-17 Open Display Style Console Type HIS ................. 3-1 Open Environment ................................................ 9-1 Open Environment for Optimizing the Whole Enterprise ...................................................... 1-3 Open Interfaces (Option) ....................................3-57 Operating Modes ................................................7-20 Operating Same Virtual FCS from Multiple PCs...6-13 Operating Screen Mode........................................ 3-4 Operations ..........................................................4-12 Operations at Fatal Error Occurrence ................7-24 Operations at Major Error Occurrence ...............7-24 Operations at Minor Error Occurrence ...............7-24 Operation and Monitoring ...................................3-66 TI 33Q01B10-01E

Dec.14,2007-00

Ind-5 Operation and Monitoring Functions .................... 3-1 Operation and Monitoring Functions.....3-31 Operation and Monitoring Windows ...................3-18 Operation at SCS Errors .....................................7-24 Operation Environment Customizable to match Plant Configuration and Operating Procedures .................................................... 1-4 Operation Keyboard............................................2-10 Operator Guide Window .....................................3-29 Optimal Operating Environment, Hardware Upgradeable to the Latest Technology.......... 1-4 Overall Test ........................................................... 6-6 Overview Objects ................................................3-23 Overview of Forcing Function .............................7-21 Overview of Inter-SCS Safety Communication .... 7-6 Overview of Override ..........................................7-21 Overview of Security Functions ..........................3-32

P Set.............................................................3-12 Plant Resource Manager (PRM) ........................10-1 Potential Features of VTSPortal .........................3-67 Powerful Engineering Functions ........................... 1-7 Pressure Clamp Terminal Blocks ........................ 7-11 Printout of Individual Items..................................6-15 Print All Data........................................................6-15 Print Screen Functions........................................3-17 Process Alarm Window .......................................3-28 Process Data Access Function ...........................3-66 Process Data Information ...................................3-57 Process Input/Output ..........................................4-20 Process Input/Output and Software Input/Output .................................................4-20 Process Management Functions .......................... 9-4 Process Reports .................................................3-31 Products Related to Input/Output Modules ........ 7-11 Profiler Display Functions ...................................6-12 Programmable Controller Standards ..................2-50 Programming Language Standard .....................2-51 Projects ................................................................. 6-7 ProSafe-RS Related Packages ..........................7-26 Protection Layers of Plant and Safety Instrumented System ........................................................... 7-1

R Rack Mountable Node ........................................2-24 Re-classify Alarms and Events ...........................3-69 Receiving Communications from Other Stations ..6-10 Recipe Information ..............................................3-58 Recipe Management Functions ............................ 9-3

Redundancy and Reliability ................................2-44 Redundancy and Reliability of the Compact FCS for FIO ..........................................................2-46 Redundancy and Reliability of the Compact FCS for RIO .........................................................2-48 Redundancy and Reliability of the FCS for FIO, FCS for RIO .................................................2-44 Redundant Communication Functions ................. 5-4 Regulatory Control Blocks ...........................4-5, 4-14 Regulatory Control Functions ............................... 4-5 Relation to Other Functions ................................6-21 Relay Boards ...................................................... 7-11 Relay I/O Module ................................................2-38 Remote Desktop Function ..................................3-41 Remote I/O ............................................................ 1-6 Remote I/O (RIO) ................................................2-32 Remote Maintenance (Option) ...........................6-19 Repeating Alarms................................................3-15 Replacement System............................................ 1-6 Report Functions (Option) ..................................3-34 Report Printing from Other PC ............................3-36 Requirements for a DCS for Batch Processes ..... 9-1 Resource Usage Status Display .........................6-15 Reusable Engineering Data .................................. 6-1 RIO Bus...............................................................2-20 RIO Buses ...........................................................2-45 RIO Nodes ..........................................................2-45 Running Online Manual Viewer ..........................12-1 Run on General Purpose PC ................................ 6-1

S Safety Control Station (SCS) ............... 2-4, 7-9, 7-13 Safety Engineering PC (SENG).....................2-4, 7-9 Safety Instrumented System ................................ 1-8 Safety Instrumented System (ProSafe-RS) ... 2-4, 7-1 Safety Life Cycle ................................................... 7-2 Safety Standard Compliance ..............................2-50 Saving Events .....................................................7-22 Saving to other Media .........................................3-54 Scales of Safety Evaluation .................................. 7-3 Scan Period........................................................... 8-4 SCS Global Switch Communication ..................... 7-7 SCS Link Transmission......................................... 7-7 SCS Link Transmission Safety Communication ....7-7 SCS Status Display Window...............................3-45 Search Functions ................................................12-2 SEBOL Functions ................................................. 4-9 SEBOL Window ..................................................3-51 Security Functions ..............................................3-32 Security Levels ....................................................7-20 TI 33Q01B10-01E

Dec.14,2007-00

Ind-6 Security on a Per-Function-Block Basis .............3-33 Security on a Per-Window Basis ........................3-33 Self Documentation (Option) ..............................6-15 SEM OPC Interface ............................................13-6 Sequence Blocks ................................................4-16 Sequence Control Functions ................................ 4-6 Sequence Element Blocks .................................... 4-8 Sequence Faceplate Block .................................4-10 Sequence of Events Manager (SEM) Function (Option) ........................................................13-1 Sequence Table Block .......................................... 4-7 Sequence Table Window ....................................3-49 Server for Remote Operation and Monitoring Function (Option) .........................................3-61 SFC Block Functions ............................................ 4-9 SFC Window .......................................................3-51 Shortcut Functions ..............................................3-10 SIL3 Certification Acquired from TÜV .................2-51 Smoothly Synchronize ........................................2-53 Snapshot Functions ............................................6-10 SOER ..................................................................7-22 SOE Digital Input Module (ADV151-E) ...............13-5 SOE OPC Interface Package .............................7-26 SOE Server .........................................................13-4 SOE Server Configurator ....................................13-6 SOE Viewer.........................................................13-4 SOE Viewer Package .........................................7-26 Software Input/Output .........................................4-21 Software Input and Output .................................... 8-5 Solutions Incorporating CENTUM CS 3000 ......... 1-3 Special Size .......................................................... 3-7 Specify Type of Printing ......................................6-15 Standards for Hazardous Location Equipment ...2-51 Standard Blocks .................................................... 8-4 Standard Engineering Functions .......................... 6-7 Starting Printing...................................................3-36 States and Operations of SCS............................7-19 Station Information ..............................................3-57 Step Execution ...........................................6-10, 6-12 Subsystem Communication Function .................7-23 Subsystem Communication Functions ................. 5-1 Subsystem Connection (Modbus) ......................7-23 Subsystem Integration Functions ......................... 4-1 Summary of Communications with Subsystems ...5-7 Supervise Alarm and Event Messages ...............3-70 ed Subsystem Communication Packages ...5-2 for Intelligent Field Instruments ............... 1-5 for International Standards ...................... 9-1 for Latest PC Hardware........................... 3-1

for Multiple Products ............................... 9-1 for Next-generation Field Instruments with Open Fieldbus ............................................... 4-1 of Maintenance Inspection Works .........10-4 of Record and Report of Maintenance Inspection Result .........................................10-4 Suppress Unnecessary Alarms and Events Issuance ......................................................3-69 Switch Instrument Blocks...................................... 4-8 Synthesis of DCS and Personal Computers ........ 1-4 System Alarm Window ........................................3-43 System Clock and VEHICLE Clock ....................2-52 System Concepts .................................................. 1-2 System Configuration ................. 2-1, 3-65, 5-6, 13-2 System Configuration – CENTUM CS 3000 Equipment ..................................................... 2-3 System Configuration of ProSafe-RS ................... 7-5 System Configuration Using CAMS for HIS .......3-70 System Generation ............................................... 6-6 System Integration OPC Station (SIOS) (Option) ........................................................3-65 System Maintenance Functions .........................3-42 System Message Window ......................3-4, 3-5, 3-6 System Monitoring and Maintenance Functions ..13-6 System Overview ...........................................1-1, 7-5 System Scale .................................................2-6, 7-8 System Scale and Hardware Implementation Requireme ..................................................... 7-8 System Specifications........................................... 2-6 System Status Overview Window.......................3-42 System View ......................................................... 6-7

T Tag Name Search ...............................................6-15 Tag Report...........................................................3-31 Target Tests .........................................................7-25 Target Test Functions ..........................................6-12 Terminal Boards .................................................. 7-11 Terminal Type Digital I/O Module ........................2-35 Terminal Type Multiplexer Module ......................2-38 Test (EEMUA No.191 Compliant) .......................3-70 Test Functions .....................................................7-25 Test Functions (Option) .......................................6-10 Test Multiple Virtual FCSes from Multiple PCs ...6-13 The Operating Environment can incorporate the Latest Technology.......................................... 1-4 Time Adjustment .................................................2-53 Time Discrepancy ...............................................2-53 Time Management ..............................................2-52 Time Notification .................................................2-54 TI 33Q01B10-01E

Dec.14,2007-00

Ind-7 Time Setting Dialog Box......................................3-47 Time Synchronization Between Domains...........2-54 Time Synchronization Function ..........................7-22 Time Synchronization in Different Domains .......2-54 Time Synchronization Method of SCSs Connected to Vnet/IP ..................................7-23 Time Synchronization Method of SCSs Connected to V net ......................................7-22 Time Synchronization of the Stations Not Connected on V net .....................................2-54 Time Synchronization Scheme ...........................2-52 Trends .................................................................3-52 Trend and alarm analysis screens ......................15-2 Trend compare screen ........................................15-2 Trend Data Information .......................................3-58 Trend Functions ..................................................3-52 Trend Point Window ............................................3-27 Trend Window .....................................................3-26 Tuning Parameter Printout ..................................6-15 Tuning Parameter Save Functions ............6-10, 6-12 Tuning Trend .......................................................3-53 Tuning Window ...................................................3-25 Types of Sequence Control .................................. 4-6

Virtual Test Functions ..........................................6-10 Voice Messaging Functions ................................3-38 VTSPortal System Architecture ..........................3-68 V net .............................................................2-4, 2-40 V net Time Master Method (Default) ...................7-22

W Web Monitoring Functions (Option) ....................3-62 When GSGW and the OPC server are on the same PC ........................................................ 5-6 When GSGW is on a PC separate from the OPC server ............................................................. 5-6 Wide-ranging Standard Function Blocks .............. 8-3 Windows-Based Open Interface ........................... 3-1 Window Call-up ..................................................... 3-3 Window Hierarchy ................................................. 3-8 Window Sizing ...................................................... 3-7 Wiring check Adapters ........................................7-12

Y Yokogawa’s Enterprise Technology Solutions Concept ......................................................... 1-1 You can mix Continuous and Sequence Control ....4-3

U Unified Operation Procedures .............................. 8-3 Unique Testing Environment ................................. 8-3 Unit for Optical Bus Repeater Module (Rack Mountable Type) (SNT10D) ..............7-16 Unit Instruments ..................................................4-12 Unit Instruments and Operations ........................4-19 Unit Management Functions............................... 4-11 Groups ........................................................3-32 Name ..........................................................3-32 Permissions ................................................3-33 Using a Mouse or Similar Pointing Device to Call up Windows ............................................ 3-3 Using Operator Keyboard to Call up Windows ..... 3-3 Using Table of Contents and Index .....................12-2 Utility Functions ...................................................6-15

V Valve Diagnosis...................................................10-4 Valve Monitoring Blocks ........................................ 4-8 Valve Pattern Monitors (Option) .................4-13, 4-20 Versatile Terminal Service Application Portal (VTSPortal) ..................................................3-67 Viewing Events with SOE Viewer .......................7-22 Virtual Tests .........................................................7-25 “Virtual Test” Functions ......................................... 6-1 TI 33Q01B10-01E

Dec.14,2007-00

Blank Page

i

Revision Information ● Title ● Manual No.

: CENTUM CS 3000 Integrated Production Control System System Overview : TI 33Q01B10-01E

May 1998/1st Edition Newly published Nov.1998/2nd Edition 2.3 Console-type added 2.4.2 AMM12C, ACF11 added 2.6 Fieldbus added 3.9 Graphic Web Display Function added 4.1.4 Logic Chart Blocks added 6. Batch Management Functions added Oct.1999/3rd Edition 1.3 Revised “1.2 Overview of Function” to “1.3 Solutions Incorporating CENTUM CS 3000” 1.3.4 Added “CENTUM V and CENTUM-XL Migration to CENTUM CS 3000” 1.4 Added CENTUM CS 3000 Related Software Packages 2. Revised System Configuration Diagram 2.1 Added Engineering PC (ENG), Fieldbus, Unified Operation/Monitoring Station (UHMIS), Business Information PCs and Supervisory Computers, FCS-XL and FCS-V Control Station for Migration to CENTUM CS 3000, and Prosafe “Safety Instrumented System” Revised description of Communications Gateway Unit (CGW) 2.4.3 Separated “I/O Module Nests and I/O Modules” from item 2.4.2 Added AMN52 to I/O Module Nests, and AAM11B, AAM21J, AMM22C, AMM22TJ, AMM25C, AMM32C, AMM32TJ, AMM32CJ, ACM71 and A71 to I/O Modules 2.5.1 Revised description of V net cable and length 2.8 Added process I/O operation at U failure 2.9 Added C-Tick Mark description 3.1 Revised figure showing Configuration of Operation and Monitoring Functions 3.2 Revised order and contents of Common Operation and Monitoring Functions 3.2.3 Revised figure showing System Message Window 3.2.5 Revised Window Hierarchy explanation 3.2.10 Added explanation of Alarm Processing Functions Added notes to figures explaining “Opening Process Alarm Window to Acknowledge Alarm” and “Opening System Alarm Window to Acknowledge Alarm” 3.2.11 Added Hard Copy Functions 3.3.1 Added examples of Instrument Faceplates 3.3.7 Added Message Monitoring Window 3.4.5 Added Connecting ITV Camera 3.4.6 Added CENTUM Desktop Environment Customization 3.5.4 Revised HIS Setting Window Added External Recorder Tab Sheet and ITV Tab Sheet on HIS Setting Tab Sheet Items 3.5.6 Added Help Dialog 3.6.3 Added Logic Chart Window 3.6.4 SEBOL Window: Changed item no. due to addition of 3.6.3 Logic Chart Window 3.6.5 SFC Window: Changed item no. due to addition of 3.6.3 Logic Chart Window 3.7.5 Added External Recorder Output Functions 3.9 Added FCS Data Setting/Acquisition function (PICOT) 4.1.4 Revised Logic Chart Block Diagram 4.1.7 Added Generic Name 4.1.8 Added YS Instrument Blocks (SLCD, SLPC, SLMC, SMST-111, SMST-121, SMRT, SBSD, SLCC, SLBC, STLD) to Table of Regulatory Control Blocks In Table of Unit Instruments and Operations, added OPSFC1, OPSFC2, OPSFC3, OPSFC4, OPSFC5 4.2.1 Added ACM71 Ethernet Communication Module, YS Communication Package (for ACM12), MELSEC-A Communication Package (for ACM71) Revised description associated with Communicating with Other Subsystems, and figure showing “Communications I/O Data Flow”

TI 33Q01B10-01E

Feb.01,2001-00

ii 5.2

Revised “Multiple-project Configuration” to “Multiple Project Connection Functions”, and description of the functions 5.3 Added description of Engineering Procedure 5.4.2 In Table of “List of Builder Programs”, added Multiple project connection, Plant hierarchy, Engineering unit symbol, Switch position label, State transition matrix, Alarm processing table, Alarm priority level, -defined status character string, Status change command character string, BCV constants, CGW constants, and Train in batch functions 5.5 Added Expanded Test Functions 5.7 Revised “5.4 Online Maintenance Functions” to “5.7 Online Maintenance Functions,” and description of the functions 5.8 Added description of Remote Maintenance Functions Feb. 2001/4th Edition For all sections, Windows NT is changed to Windows 2000 KFCS and APCS are added, so that some chapter, section and item numbers of 3rd Edition are revised. 1.3.4 Added "Management Cost Reduction" 1.4.1 Revised description of Exaplog 1.4.2 Revised description of Exapilot 1.4.3 Revised description of Exaopc and figure showing Exaopc OPC Interface Package 2. Added console type HIS, KFCS and APCS to figure showing CENTUM CS 3000 System Configuration (Basic) Added console type HIS, KFCS and APCS, deleted CENTUM V and revised UHMIS to Exaopc in figure showing CENTUM CS 3000 System Configuration 2.1 Added console type HIS, KFCS and APCS, deleted Nodes and RIO Bus revised UHMIS to Exaopc 2.2 Added KFCS and CENTUM-XL system to figure showing Example of Large System Configuration 2.3.1 Added this item, revised description of Console-type HIS Added open style console type HIS 2.4 Added KFCS 2.4.1 Added KFCS 2.4.2 Revised standard FCS (LFCS) of 3rd Edition to standard FCS for RIO (LFCS) 2.5.1 Added KFCS I/O modules 2.5.2 Added description of I/O modules for LFCS and SFCS 2.6.2 Added "acquiring trend data for other stations" to description of Ethernet 2.7 Added KFCS system configuration with Fieldbus 2.8.1 Added description of KFCS, ESB bus and FIO Node 3. Deleted redundant description of "Easy Hardware Upgrades" Added Console Type HIS and Multi-monitor Functions 3.1 Added voice messaging functions, multi-monitor functions and expert trend viewer function to figure showing Configuration of Operation and Monitoring Functions 3.4.3 Added Security on Per-Window Basis 3.4.5 Revised description of Connecting ITV Camera 3.4.7 Added Voice Messaging Functions 3.4.8 Added Multi-monitor Functions 3.5.4 Revised figure showing HIS Setting Window Added OPC, Report, Multi-monitor and Process Management Tab Sheet to table showing HIS Setting Tab Sheet Items 3.7.4 Revised table of Typical Figures for Disk Capacity 3.7.6 Added Expert Trend Viewer Function (Option) 3.8 Revised description of this section, added CENTUM Data Access Library and deleted DDE (Dynamic Data Exchange) 3.10 Revised Graphic Web Display Function to Web Monitoring Functions Added trend window monitoring to Web Monitoring Functions 4.1.2 Deleted description of Increasing Engineering Productivity - Components and Models 4.1.8 Added new sequence table blocks to table "List of Sequence Blocks"

TI 33Q01B10-01E

Feb.01,2001-00

iii 4.2.1

Added ALR111 and ALR112 communication modules Added FA-M3 Communication Package (for ALR111, ALR112 and ACM71), Modbus Communication Package (for ALR111 and ALR112) and MELSEC Communication Package (for ALR111 and ALR112) 5. Added Advanced Control Functions 6.2 Deleted Exchanging Data with Windows Application (item 5.2.2 of 3rd Edition) and Reusable Engineering Data (item 5.2.3 of 3rd Edition) 6.4.2 Added system-specific status character string viewer, global switch, trend record, trend display pen assignment and unit common block to List of Builder Program 6.5 Added Snapshot Functions 6.6 Revised figure showing Self-Documentation for Function Block Detail Definitions 7.1 Added ISA S88.01 requirement to description of for Multiple Product 7.2 Added note 1 regarding master recipe creation to figure showing Flow of CS Batch 3000 Revised description of (4) Batch results acquisition of Process Management Functions 8.2 Added Search Functions and Favorites 9. Added Plant Resource Manager (PRM) Nov. 2001/5th Edition For all sections Corresponded to R3.02. 2. Added Enhanced FCS. 2.2 Added description that tags can be monitored up to 1,000,000. 2.5 Added AAP149 Pulse Input Module for Compatible PM1 and ALE111 Ethernet Communication Module. 3.3.5 Added display buttons for each alarm priority level. 3.4.9 Added Advanced alarm Filter Function. 4.2 Added subsystems ed by Ethernet communication; FA-M3, PLC-5, SLC 500 and MELSEC. 9. Revised description of Plant Resource Management. 10. Added FDA: 21 CFR Part 11 Compliant Function. Sep. 2002/6th Edition All sections Revised in line with system version R3.03. Descriptions for Windows XP added. Introduction “CRT” deleted. Trademark acknowledgments revised. 1.4.3 Number of OPC Foundation participants revised to 200. “Windows NT-version” deleted from “Exapilot Windows NT-version” in the figure of Exaopc. 2.2 “V net” in the figure of a large system configuration changed to “HF-bus.” 2.3.1 “18-inch LCD/” added to the figure of an enclosed display style console. 2.4 KFCS2 and LFCS2 added. 2.4.1 Description for the maximum number of node units per KFCS2 added. 2.5.1 AI143 and AAI543 field-to-system isolated, point-to-point non-isolated modules added. AST143, ASR133, ASD143, ASD533 modules with built-in barriers added. 2.5.2 “RTS” changed to “RTD” (resistance temperature detector). 2.10 Description for compliance to US standards deleted. 3 “LCD/” added to “CRT” for an enclosed display style console. 3.1 “Remote Desktop Function,” “Configured Information Reference Function,” and “Consolidated Historical Message Viewer” added to the figure of configuration of operation and monitoring functions. “Advanced Alarm Filter Functions” moved to a different position. 3.2 “Alarm handling” changed to “Alarm processing.” 3.2.10 “Alarm handling” changed to “Alarm processing.” 3.3.1 Instrument faceplate of a timer block changed. Figure of the graphic window showing overview objects changed. 3.4 Voice messaging functions, advanced alarm filter functions, and remote desktop function added to operation and monitoring functions. 3.4.10 Page for the remote desktop function added. 3.5.4 Figure of the HIS setting window revised. 3.11 Page for the configured information reference function added. 3.12 Page for Consolidated Historical Message Viewer added. 4.1.8 A list of enhanced motor control and switch instrument blocks added. 8.3 “Helper package” changed to “PLUG-IN application.”

TI 33Q01B10-01E

Oct.15,2003-00

iv Oct. 2003/7th Edition For all sections Corresponded to R3.04 1.4 Moved to Chapter 15 1.4.1 Descriptions on Exaplog deleted 2 Figure CENTUM CS 3000 System Configuration (Basic) and Figure CENTUM CS 3000 System Configuration revised 2.1 Compact FCS for FIO added Generic Subsystem Gateway Package added 2.2 Figure Example of Large System Configuration revised 2.3.1 Descriptions on Enclosed Display Style Console Type HIS with 21-inch CRT and Open Display Style Console Type HIS with 15-inch LCD deleted 2.4 Compact FCS for FIO added 2.4.1 FCU Configuration in FFCS added Mounting of FFCS added 2.5.1 AAV144, AAV544, and ALP111 added 2.6.1 Descriptions on V net revised 2.7 Notes on Fieldbus Connection (FCS for FIO) added 2.8.2 Redundancy and Reliability of the Compact FCS for FIO added 2.8.3 Moved from 2.8.2 2.9 Descriptions on U Failure revised 2.11 Time Management added 3.2.1 Figure Operation Keyboard revised 3.5.4 Figure HIS Setting Window revised 4.1 Figure Configuration of FCS Control Functions revised 4.1.8 Valve Pattern Monitors added 4.1.9 Offsite Block Functions added 4.1.10 Moved from 4.1.8 Function outline of List of Function Blocks added 4.1.11 Process Input/Output and Software Input/Output added 5 4.2 Subsystem Communication Functions revised and moved to Chapter 5 Generic Subsystem Gateway Package (GSGW) added 6.5 Descriptions on Receiving Communications from Other Stations revised 7 Moved from Chapter 5 8 Moved from Chapter 7 10 Table Optional Packages and Responses in Individual Group Functions added Figure Example of a System Configuration revised 10.2 Table Clauses Regarding Data Integrity and Solution in CENTUM CS 3000 revised 11 Moved from Chapter 8 12 Sequence of Events Manager (SEM) Function added 13 Event Viewer Package added 14 Long-term Trend Historian Package (LTTH) added Oct. 2004/8th Edition For all sections Corresponded to R3.05 2.3.1 Console Type HIS with 18-inch LCD changed to LCD 2.5.1 AAP849 Anaput/Output Module added 2.11.2 Accuracy of VEHICLE clock corrected 2.11.3 Time adjustment of a PC with ENG function deleted 3.1 Remote Operation and Monitoring Server Function added to configuration of Operation and Monitoring Functions 3.4.10 Benefits of Remote Desktop Function is Corrected 3.10 Remote Operation and Monitoring Server Function description added 4.1.10 Fieldbus simplified universal block added to faceplate blocks 6.8 Yokogawa Engineering Service replaced with our service section March.2005/9th Edition For all sections Corresponded to R3.06 i Trademark added 2 “ProSafe” changed to “ProSafe-RS” in description of Safety instrumented system. 2.2.3 Description on Migration from CENTUM CS 1000 to CS 3000 2.4 PFC-S/-E added to compact FCS for RIO 2.4.3 Compact FCS changed to compact FCS for RIO and PFC-S/-E added 3.1 System Integration OPC Station added 3.1.4 Description on System Integration OPC Station added TI 33Q01B10-01E

May 31,2005-00

v 6.9 Description on Coordination with SmartPlant Instrumentation added 6.10 Description on Device Functions added June 2006/10th Edition General “Safety Instrumented System (ProSafe-RS)” was added in Chapter 7. Cover Page The logo of ProSafe-RS was added under the logo of CS 3000 R3 in the upper right corner. Introduction Descriptions of ProSafe-RS and safety instrumented system were added. 1.3 Description of a safety instrument system was added. 1.3.6 Section 1.3.6, “Improved Security and Safety for Plants” was newly added. 2.1 The position of ProSafe-RS was unified. 2.10 Description of functional safety was added. 3.2.10 Description of the process alarm window of the alarm processing function was revised. 3.3.5 Description of the process alarm window was revised. 3.5.1 SCS and SENG were added to the system status list display window. 3.5.2 Description of the system alarm window was revised. 3.5.4 Description of the SCS status display window was added. 7 “Safety Instrumented System (ProSafe-RS)” was added in Chapter 7 and subsequent chapter numbers were changed. December 2006/11th Edition Descriptions for ProSafe-RS R1.02 was revised. For all sections corresponded to R3.08 1.3.6 “Improved Security and Safety for Plants” was revised. Description of “ProSafe-RS” was revised. 2.10 Description of functional safety was added. 3.15 “Versatile Terminal Service Application Portal(VTSPortal)” was newly added 3.16 “Consolidated Alarm Management Software for Human Interface Station (CAMS for HIS)” was newly added. 7 “Safety Instrumented System (ProSafe-RS)” 7.2.3 Model was added or changed. 7.3.1 Hardware Configuration of SCS. Figure “Hardware Configuration of SCS” was revised. ESB bys (SNB10D) was added. 7.3.3 Security Levels The explanation of “Security Levels” was added. 7.6 Comparison of HIS Operation and Monitoring Table “Mapping Blocks and Elements” was revised. Dec. 2007/12th Edition General for ProSafe-RS R1.03 2.10 Marine Standards added to various standards Error in Standards for Hazardous Location Equipment corrected 3.5.4 SCS Status Display Window Link Trans Lock added to the Figure in 3.16 SCS added and corrected in System Configuration of Consolidated Alarm Management 7.2.1 System Overview SCS Link Transmission added Description in Products Related to Input/Output Modules revised AKB651 added to Dedicated Cable SED2D description added to Terminal Boards Relay Boards description revised Figure in Wiring Check Adapters changed 7.2.3 States and Operations of SCS Forcing and Override Grouping Override added to Table Differences between Forcing and Override 7.6 Comparison of HIS Operation and Monitoring Table Mapping Blocks and Elements Data Grouping Override added to Override from HIS Table Software Input and Output That Can Be Used with SCS Global switch ed by SCS

TI 33Q01B10-01E

Dec.14,2007-00

Written by

Yokogawa Electric Corporation

Published by

Yokogawa Electric Corporation 2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, JAPAN

Printed by

KOHOKU PUBLISHING & PRINTING INC.

Subject to change without notice.

Centum Cs 3000.pdf 3g5qm

Overview 6h3y3j

More details h6z72

Related Documents 543cg

Centum Cs 3000.pdf 3g5qm

Yokogawa Centum Cs 3000 223l62

Cs 1mg24

Cs 1mg24

Cs 5140 Cs 5142 1c5n18

Yokogawa Centum Cs3000.pptx 2h6h3w

More Documents from "Brendan Stack" 6afy

Centum Cs 3000.pdf 3g5qm

11482j

11482j

Bs En10294 Part1 Hollow Bars 6e3t17

If I Could Tell Her 704u1n

258772629-wicked-dancing-through-life.pdf 175o46