ExaPlog TI

Technical Information
TI 36J06A40-01E
Exaplog Event Conversion Specifications for Process Control Systems of Other Companies
TI 36J06A40-01E 1st Edition Aug. 2005
Blank Page
Introduction
This Technical Information brochure (hereafter, TI) describes how to convert the event data of other companies process control systems (hereafter referred to as PCS) so as to display such event data, using the Exaplog Event Analysis Package. The information in this TI should be referred to in combination with online help.
Trademarks
Exaplog is a registered trademark of Yokogawa Electric Corporation. CENTUM is a registered trademark of Yokogawa Electric Corporation. CIEMAC is a registered trademark of Toshiba Corporation. MICREX is a registered trademark of Fuji Electric Co., Ltd. DeltaV is a registered trademark of Emerson, Ltd. Other company names and product names used in this TI are trademarks or registered trademarks of their respective holders.
All Rights Reserved. Copyright 2005, Yokogawa Electric Corporation
TI 36J06A40-01E Aug.15, 2005-00
Blank Page
Toc-1
Exaplog Event Conversion Specifications for Process Control Systems of Other Companies
TI 36J06A40-01E
CONTENTS
1. Overview ....................................................................................... 1-1
1.1 1.2 1.3 Target PCS Event Data............................................................................ 1-1 Overview of the Event Data Connections of the PCSs of Other Companies ............................................................................................... 1-1 Defining Event Data Connection for the PCSs of Other Companies..................................................................................... 1-2
2. 3.
Yokogawa PCS Event Map........................................................... 2-1 International Companies.............................................................. 3-1

3.1 Honeywell TDC3000 ................................................................................ 3-1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 3.2 3.2.1 3.2.2 3.2.3 3.2.4 Honeywell TDC3000 Events to be Analyzed ............................... 3-1 How to Output a Virtual Printer Application CSV File .................. 3-1 How to Operate the Virtual Printer Application File Conversion Tool............................................................................................... 3-2 Method for Loading a Honeywell TDC3000 CSV File using Exaplog ........................................................................................ 3-4 Specifications for Honeywell TDC3000 Event Conversion .......... 3-5 Emerson DeltaV Events to be Analyzed ...................................... 3-6 How to Output a DeltaV CSV File ................................................ 3-6 Method for Loading an Emerson DeltaV CSV File using Exaplog ........................................................................................ 3-7 Specifications of Emerson DeltaV Event Conversion .................. 3-8
Emerson DeltaV ....................................................................................... 3-6
4.
Japanese Companies................................................................... 4-1

4.1 Toshiba CIEMAC DS................................................................................ 4-1 4.1.1 4.1.2 4.1.3 4.1.4 4.2 4.2.1 4.2.2 4.2.3 Toshiba CIEMAC DS Events to be Analyzed............................... 4-1 How to Output OIS CSV Files...................................................... 4-1 Method for Loading a Toshiba CIEMAC DS CSV File using Exaplog ........................................................................................ 4-2 Specifications for Toshiba CIEMAC DS Event Conversion.......... 4-3 Yamatake TDCS3000 Events to be Analyzed.............................. 4-4 How to Output Journal Station PCs CSV File ............................. 4-4 How to Operate the Journal Station File Conversion Tool ........... 4-5
Yamatake TDCS3000 (via Journal Station) ........................................... 4-4
TI 36J06A40-01E Aug.15, 2005-00
Toc-2
4.2.4 4.2.5 4.3 4.3.1 4.3.2 4.3.3 4.3.4 4.3.5 4.4 4.4.1 4.4.2 4.4.3 4.4.4 4.4.5 Method for Loading a Yamatake TDCS3000 CSV File using Exaplog ........................................................................................ 4-7 Specifications for Yamatake TDCS3000 Event Conversion ........ 4-8 Fuji Electric MICREX Events to be Analyzed............................... 4-9 How to Obtain Data for Fuji Electric MICREX.............................. 4-9 How to Operate the MICREX File Conversion Tool ................... 4-10 Method for Loading a Fuji Electric MICREX CSV File using Exaplog ...................................................................................... 4-12 Specifications for Fuji Electric MICREX Event Conversion ....... 4-14 Hitachi EX6000/7000 Series PC Printer Events to be Analyzed .................................................................................... 4-15 How to Obtain Hitachi EX6000/7000 Series PC Printer Data.... 4-15 How to Operate the EX6000/7000 Series PC Printer File Conversion Tool ......................................................................... 4-16 Method for Loading a Hitachi EX6000/7000 Series CSV File using Exaplog............................................................................. 4-18 Specifications for Hitachi EX6000/7000 Event Conversion ....... 4-19
Fuji Electric MICREX PC Printer ............................................................ 4-9
Hitachi EX6000/7000 Series PC Printer ............................................... 4-15
TI 36J06A40-01E Aug.15, 2005-00
<1. Overview>
1-1
1.
Overview
A large number of PCS are us in a plant. When analyzing plant operations, it is necessary to conduct an operations analysis not just of part of a plant, but of the plant as a whole. Thus, Exaplog provides a function for analyzing not only Yokogawa PCS event data but also the event data of the PCSs of other companies.
1.1
Target PCS Event Data

The event data to be analyzed is event data that is provided in CSV format by each PCS of another company.
1.2
Overview of the Event Data Connections of the PCSs of Other Companies

PCS event data is converted using the following procedure to obtain CSV files for analyses that can be read by Exaplog. Note that steps 3 and 4 may not be necessary, depending on the PCS. 1. Define each companys PCS adapter using Exaplogs PLAdmin. 2. Store PCS event data to be analyzed to any specified folder. 3. Convert the format of the PCS event data. (This step may not be necessary, depending on the PCS.) 4. The general-purpose data conversion tool (*2) converts event data that is converted by the conversion table for the other companys PCS (*1) into data (a comma- or tab-delimited text file) that can be automatically or manually displayed on the PLView window (event analysis tool). (This step may not be necessary, depending on the PCS.) 5. PCS event data or PCS event data format which has been converted, is automatically loaded into a PC running Exaplog, using the conversion table for the other companys PCS (*1) that corresponds to the defined PCS adapter. 6. The conversion table for the other companys PCS (*1) categorizes event types and reconfigures the content of event messages.
*1: *2: The conversion table for the other companys PCS is a standard function of Exaplog. The general-purpose data conversion tool is a standard function of Exaplog.
TI 36J06A40-01E Aug.15,2005-00
<1. Overview>
1-2
Conversion table for the other companys PCS
PLView PLAdmin
File conversion Tool
Company-A specific event file
Converts the file format
Exaplog text file (comma- or tabdelimited)
Categorizes events
CSV file for Exaplog
Exaplog event databese
Figure Overview of the Event Data Conversion for the PCSs of Other Companies
1.3
Defining Event Data Connection for the PCSs of Other Companies

Follow the procedure below to define PCS event data connection. 1. Display the PLAdmin window to check that Explog is running. 2. Click the Add button at the right of the window to display a new adapter window. 3. Enter the following items: Adapter Name: any name (e.g., a computer name) Type: Company-X PCS connection adapter name (e.g., CIEMAC DS) Acquisition Period: Select this from the pull-down menu. No Periodic Scan --- Manual acquisition only Hourly Every 3 Hours Every 5 Hours Every 8 Hours Every 12 Hours Daily --- Every 24 hours Periodic Acquisition On: Check this checkbox if a periodic scan is performed. Event File Name: Specify the network directory of another companys event file. (See the event data connection procedure described in Chapter 3 on for the PCSs of other companies.)
TI 36J06A40-01E Aug.15,2005-00
<2. Yokogawa PCS Event Map>
2-1
2.
Yokogawa PCS Event Map

The Yokogawa PCS event type/subtype map is defined as shown below. The events of the PCSs of other companies are assigned to this event map.
Table Yokogawa PCS Event Map
Type SubType SysAlarm CS/CS 1000/CS 3000 msgno. Point ID Detail Balance Factor (*1)
Alarm Notify
1-999 (odd no.) 1101, 1103, 1107, 1111 1201, 1207, 1211 1151 1701 1711-1714 1601, 1607, 1608, 1611, 1643, 1651 1603-1606, 1609 1641, 1642, 2601-2603 1602, 1612 1613, 1615, 1617
StationID TagName TagName StationID StationID StationID TagName TagName TagName TagName UnitTagName Alarm Code message (*2) Message (*2) message (*2) message (*2) ItemId Mode OpMKNo. ItemID
+1 +1 +1 +1 +1 +1 -1 -1 -1 -1 -1 -1 message (*2) -1 -1 0 0 0 0 0 0 0 0 0 Message (*2) Message (*2) 0 0 0 0 Message (*2) Alarm Code message (*2) Message (*2) 0 0 0 0 0
TagAlarm Annunciator CustomAlarm Guidance Opeguide DialogMsg Operation Record TagDataEntry TagModeChange OpeMark Ack BatchUnitOpe RecipeOpe OperatorDefine Security Process Record BlockStatus DataItemChange UnitStatus BatchStatus BatchMessage RecipeStatus Sequence AlarmOnOff Voice Custom/ECMP/BASIC Program ComputerMsg MessageReq TrendRecord Fieldbus Alarm Recovery SysAlarmRecovery TagAlarmRecovery AnnRecovery
1619, 1621, 1623, 1625, RecipeName 1627, 1633 2611-2681 641,642 1401, 1405 1407 1411, 1413 1331-1335, 1371, 14311437 1361, 1363 1311-1335, 1341, 1351, 1421-1426, 1428 1301, 1303, 1305 1403,1404 1501 RecipeName StationID TagName StationID StationID TagName TagName UnitTagName UnitTagName UserName Mode ItemID Status Status message (*2) Status message (*2) On/Off
1162, 1901, 1902, 7000StationID 7999 1903, 8000-8999 1801, 1803 1691-1695 3000-3999 2-998 (even no.) 1102, 1104, 1106, 1112 1206, 1216 TagName TagName StationID StationID StationID StationID StationID
CustomAlarmRecovery 1152
*1: *2:
Balance factor is the key for EBT (Event Balance Trend) graph. Message character string
TI 36J06A40-01E Aug.15,2005-00
<3. International Companies>
3-1
3.
3.1
3.1.1
International Companies
Honeywell TDC3000
Honeywell TDC3000 Events to be Analyzed
Honeywell TDC3000 event data is gathered from Universal Station (US) via virtual printer application. For Honeywell TDC3000 event data, events gathered as described below and provided in CSV format are taken as objects to be analyzed.
3.1.2
How to Output a Virtual Printer Application CSV File

The following is an example of how to obtain a CSV file using a floppy disk. In this example, CSV files saved by Virtual Printer application are taken as objects to be analyzed. The following shows an event data sample. Save this CSV file in a floppy disk.
Figure Example of TDC3000 Event File
TI 36J06A40-01E Aug.15,2005-00
3-2
3.1.3
How to Operate the Virtual Printer Application File Conversion Tool

Event files output as CSV files by the Virtual Printer application have the same format as information printed out. Thus, loading a CSV file using Exaplog requires conversion of its format. Using the following tool allows the format of a CSV file to be converted to an Exaplogcompatible format.
Conversion Procedure
1. Reading the CSV File Stored in the Virtual Printer Application PC
Store the CSV file saved in the floppy disk in section 3.1.2 to any directory.
2. Starting the Conversion Tool

Start ConvertTool.exe contained in the following folder C:\EXA\Exaplog\DCSType\YOKOGAWA\TDC3000\ConvertTool.exe
TI 36J06A40-01E Aug.15,2005-00
3-3
3. Specifying the DCS Type and Conversion Source File Name

Select TDC3000 for the DCS Type area. Specify the file name for File Name Before Conversion box that includes the network directory of the storage destination of the CSV file output from the Virtual Printer application PC.
4. Specifying a File Name after its Conversion

Specify a file name to be used after conversion for the File Name After Conversion box. Specify .csv for the extension. TIP
Checking the Merge With The Existing File checkbox causes converted information to be added to the existing file.
5. Starting a Convert
Click the [Start] button of the Convert Tool window.
TI 36J06A40-01E Aug.15,2005-00
3-4
3.1.4
Method for Loading a Honeywell TDC3000 CSV File using Exaplog

1. Starting PLAdmin
1. From the Windows [Start] menu, select [Program] - [YOKOGAWA EXA] [Exaplog] - [PLAdmin (Exaplog Administrator)] in that order. 2. The PLAdmin window appears. 3. Click the [Run Exaplog] button. This causes the Run Exaplog indication to switch to Stop Exaplog. 4. Click on the [Add] button, then the Adapter Add window displays.
2. Setting up the Adapter

Referring to section 1.3, Defining Event Data Connection for the PCSs of Other Companies, defines TDC3000 event data connection. The information in item in section 1.3, Defining Event Data Connection for the PCSs of Other Companies, is as shown below: Adapter: Any name the user sets Type: Scan: Event Source: TDC3000 No Periodic Scan Network directory of the event file storage destination after conversion of a Journal Station file
When the above setting is completed, click the [OK] button.
3. Loading Event Data into an Exaplog-installed PC

1. Click the [Demand Scan] button. 2. The Demand Scan window appears. 3. Click [Yes] to overwrite the existing event database with the loaded events. (All events at the data acquisition destination are reloaded.)
TI 36J06A40-01E Aug.15,2005-00
3-5
3.1.5
Specifications for Honeywell TDC3000 Event Conversion

Exaplog assigns Honeywell TDC3000 event data provided in CSV format to Yokogawa PCS message numbers.
Table Correspondence between TDC3000 Events and Yokogawas PCS Message Numbers
CIMAC DS CENTUM TDC3000 Message Number 99 1 16 19 21 21 23 26 26 28 28 31 32 38 41 42 52 76 *1:
TDC3000 Event Categories System Alarm System Alarm System Alarm System Error Process Alarm Process Alarm RTN Process Change (Guidance) Process Change (Mode Set) Process Change (Data Set) Process Change (AOF) Process Change (AON) Process Alarm (Ack) Process Alarm (Operation Ack (Guidance)) System Stats (System Alarm) System Stats (System Alarm) System Stats (System Alarm) System Maintenance (System Alarm) System Stats (Security) Other
Type AlarmNotify AlarmNotify AlarmNotify AlarmNotify AlarmNotify AlarmRecovery Guidance
SubType SysAlarm SysAlarm SysAlarm SysAlarm TagAlarm TagAlarmRecovery Opeguide
YOKOGAWA Message Point ID Number 0001 0001 0001 0001 1101 1102 1701 1603 1601 1403 1404 1602 1612 0001 0001 0001 0001 641 3999 StationID StationID StationID StationID -
Detail
Balance Factor (*1) 1 1 1 1 1 0 1 -1 -1 0 0 -1 -1 1 1 1 1 -1 0
TagName Alarm Code TagName Alarm Code StationID Message TagName ItemID TagName ItemID TagName On/Off TagName On/Off TagName TagName StationID StationID StationID StationID StationID UserName StationID Message
OperationRecord TagModeChange OperationRecord TagDataEntry ProcessRecord ProcessRecord AlarmOnOff AlarmOnOff
OperationRecord Ack OperationRecord Ack AlarmNotify AlarmNotify AlarmNotify AlarmNotify SysAlarm SysAlarm SysAlarm SysAlarm
OperationRecord Security ProcessRecord Fieldbus
Balance factor is the key for EBT (Event Balance Trend) graph.
TI 36J06A40-01E Aug.15,2005-00
3-6
3.2
3.2.1
Emerson DeltaV
Emerson DeltaV Events to be Analyzed
Emerson DeltaV event data is displayed by Process History View. This event data is saved in the following CSV format and is taken as an object to be analyzed.
3.2.2
How to Output a DeltaV CSV File

The method for saving CSV-format event data is under investigation. CSV files saved in the following format are taken as objects to be analyzed.
Figure Example of a DeltaV Event File
TI 36J06A40-01E Aug.15,2005-00
3-7
3.2.3
Method for Loading an Emerson DeltaV CSV File using Exaplog

1. Starting PLAdmin
1. From the Windows [Start] menu, select [Program] - [YOKOGAWA EXA] [Exaplog] - [PLAdmin (Exaplog Administrator)] in this order. 2. The PLAdmin window appears. 3. Click the [Run Exaplog] button. This causes the Run Exaplog indication to switch to Stop Exaplog. 4. Click on the [Add] button, then the Adapter Add window displays.

Referring to section 1.3, Defining Event Data Connection for the PCSs of Other Companies, defines DeltaV event data connection. The information in item in section 1.3, Defining Event Data Connection for the PCSs of Other Companies, is as shown below: Adapter: Any name the user sets Type: Scan: Event Source: DeltaV No Periodic Scan Network directory of the event file storage destination after conversion of a Journal Station file

TI 36J06A40-01E Aug.15,2005-00
3-8
3.2.4
Specifications of Emerson DeltaV Event Conversion

Exaplog assigns Emerson DeltaV event data provided in CSV format to Yokogawa PCS message numbers.
Table Correspondence between DeltaV Events and Yokogawas PCS Message Numbers (1/2)
DeltaV CENTUM State
* * * * * * * * * *
Event
CHANGE CHANGE CHANGE CHANGE CHANGE
Type
USER USER USER USER USER
Comment 1
.MACK .NALM .CV .TARGET .ENAB
Comment 2
Comment 3
* * * * NEW VALUE = 1 NEW VALUE = 0 * * *
Type
OperationRecord OperationRecord OperationRecord OperationRecord OperationRecord Ack Ack
SubType
YOKOGAWA Message Point ID Number

1602 1602 1601 1603 1606 TagName TagName -
Detail
Balance Factor (*1)

0 1 -1 -1 -1
TagDataEntry TagModeChange TagModeChange
TagName ItemID TagName Mode TagName Mode
CHANGE CHANGE CHANGE CHANGE
USER USER USER USER
.ENAB * * *
* LOGON LOGOFF REMOTE LOGON
* * * *
OperationRecord OperationRecord OperationRecord OperationRecord
TagModeChange Security Security Security
1605 641 642 641
TagName Mode StationID StationID StationID UserName UserName UserName
-1 -1 -1 -1
CHANGE CHANGE DOWNLOAD DOWNLOAD * EVENT EVENT EVENT EVENT EVENT ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM EVENT EVENT EVENT ALARM ALARM ALARM ALARM ALARM ALARM
USER USER USER USER USER PROCESS PROCESS PROCESS PROCESS PROCESS PROCESS PROCESS PROCESS PROCESS PROCESS PROCESS PROCESS INSTRUMENT INSTRUMENT INSTRUMENT INSTRUMENT INSTRUMENT INSTRUMENT INSTRUMENT HIMA HIMA HIMA SYSTEM SYSTEM SYSTEM SYSTEM SYSTEM SYSTEM
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
REMOTE LOGOFF * UPDATE ACTIVE * ACTIVE ACTIVE INACT/ACK ACT/ACK * ACT/ACK ACT/UNACK INACT/ACK INACT/UNACK SUPPRESSED DISABLED * ACT/ACK ACT/UNACK INACT/ACK INACT/UNACK SUPPRESSED DISABLED * ACT/ACK INACT/ACK * ACT/ACK ACT/UNACK INACT/ACK INACT/UNACK SUPPRESSED DISABLED
* * * * * Error Cleared * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
OperationRecord ProcessRecord OperationRecord OperationRecord ProcessRecord AlarmRecovery AlarmNotify AlarmRecovery AlarmNotify ProcessRecord AlarmNotify AlarmNotify AlarmRecovery AlarmRecovery AlarmNotify AlarmNotify ProcessRecord AlarmNotify AlarmNotify AlarmRecovery AlarmRecovery AlarmNotify AlarmNotify ProcessRecord ProcessRecord ProcessRecord ProcessRecord AlarmNotify AlarmNotify AlarmRecovery AlarmRecovery AlarmNotify AlarmNotify
Security Fieldbus TagModeChange TagModeChange Fieldbus TagAlarmRecovery TagAlarm TagAlarmRecovery TagAlarm Fieldbus TagAlarm TagAlarm TagAlarmRecovery TagAlarmRecovery TagAlarm TagAlarm Fieldbus SysAlarm SysAlarm SysAlarmRecovery SysAlarmRecovery SysAlarm SysAlarm Fieldbus ComputerMsg ComputerMsg Fieldbus SysAlarm SysAlarm SysAlarmRecovery SysAlarmRecovery SysAlarm SysAlarm
642 3999 1606 1606 3999 1102 1101 1102 1101 3999 1101 1101 1102 1102 1101 1101 3999 0001 0001 0002 0002 0001 0001 3999 1903 1903 3999 0001 0001 0002 0002 0001 0001
StationID StationID
UserName Message
-1 0 -1 -1 0 0 1 0 1 0 1 1 0 0 1 1 0 1 1 0 0 1 1 0 0 0 0 1 1 0 0 1 1
TagName Mode TagName Mode StationID Message
TagName Alarm Code TagName Alarm Code TagName Alarm Code TagName Alarm Code StationID Message
TagName Alarm Code TagName Alarm Code TagName Alarm Code TagName Alarm Code TagName Alarm Code TagName Alarm Code StationID StationID StationID StationID StationID StationID StationID StationID StationID StationID StationID StationID StationID Message Message Message Message Message -
*1:
TI 36J06A40-01E Aug.15,2005-00
3-9
Table Correspondence between DeltaV Events and Yokogawas PCS Message Numbers (2/2)
DeltaV Event
STATUS STATUS ALARM ALARM ALARM STATUS STATUS STATUS STATUS STATUS EVENT *
CENTUM Comment Comment 2 3

* * * * * * * * * * * * * * * * * * * * * * * *
Type
SYSTEM SYSTEM SYSTEM SYSTEM SYSTEM SYSTEM SYSTEM SYSTEM SYSTEM SYSTEM SYSTEM * * *
Comment 1
State
BAD INTEGRITY NO CONFIGURATION SUPPRESSED DISABLED * BAD INTEGRITY NO CONFIGURATION NOT COMMUNICATING OK * * *
Type
AlarmNotify AlarmNotify AlarmNotify AlarmNotify ProcessRecord AlarmNotify AlarmNotify AlarmNotify AlarmNotify ProcessRecord AlarmNotify ProcessRecord
SubType
SysAlarm SysAlarm SysAlarm SysAlarm Fieldbus SysAlarm SysAlarm SysAlarm SysAlarm Fieldbus SysAlarm Fieldbus
YOKOGAWA Message Number

0001 0001 0001 0001 3999 0001 0001 0001 0001 3999 0001 3999
Point ID
StationID StationID StationID StationID StationID StationID StationID StationID StationID StationID StationID StationID -
Detail
Balance Factor (*1)

1 1 1 1 0 1 1 1 1 0 1 0
* * * * * * * * * *
Message Message Message
*1:
TI 36J06A40-01E Aug.15,2005-00
<4. Japanese Companies>
4-1
4.
4.1
4.1.1
Japanese Companies
Toshiba CIEMAC DS
Toshiba CIEMAC DS Events to be Analyzed
Toshiba CIEMAC DS event data is event data stored in the OIS (operator station). For Toshiba CIEMAC DS event data, events gathered by the following procedure and provided in CSV format are taken as objects to be analyzed.
4.1.2
How to Output OIS CSV Files

1. Opening the OIS history window Open the Display History window on OIS. 2. Gathering events Click the [Save CSV] button to save event data in a desired folder.
IMPORTANT
About comment description content of CIEMAC DS event data Pay attention to the following point in regard to event data (CSV files) stored from OIS. If an event message contains , (comma), event data cannot be properly displayed by Exaplog. Thus, if event comments contain , (comma), organize comments separated by the , (comma) delimiter into a single comment using . (period), _ (under bar), or any delimiter other than , (comma). Example: (Incorrect) CIEMAC DS message Pay attention to the rotational speed of the agitators of equipment 1, 2, and 3.
Pay attention to the rotational speed of the agitators of equipment 1 2 and 3.
(Correct) CIEMAC DS message Pay attention to the rotational speed of the agitators of equipment 1_2_and 3.
Pay attention to the rotational speed of the agitators of equipment 1_2_and 3.
TI 36J06A40-01E Aug.15,2005-00
4-2
4.1.3
Method for Loading a Toshiba CIEMAC DS CSV File using Exaplog

1. Starting PLAdmin
1 2 3 From the Windows [Start] menu, select [Program] - [YOKOGAWA EXA] [Exaplog, and PLAdmin (Exaplog Administrator)] in that order. The PLAdmin window appears.
Click the [Run Exaplog] button. This causes the Run Exaplog indication to switch to Stop Exaplog. 4. Click on the [Add] button, then the Adapter Add window displays.

Referring to section 1.3, Defining Event Data Connection for the PCSs of Other Companies, defines CIEMAC DS event data connection. The information in item in section 1.3, Defining Event Data Connection for the PCSs of Other Companies, is as shown below: Adapter: Any name the user sets Type: Scan: Event Source: CIEMAC DS No Periodic Scan Network directory of the event file storage destination after conversion of a Journal Station file

TI 36J06A40-01E Aug.15,2005-00
4-3
4.1.4
Specifications for Toshiba CIEMAC DS Event Conversion

Exaplog assigns Toshiba CIEMAC DS event data provided in CSV format to Yokogawa PCS message numbers.
Table Correspondence between CIEMAC DS Events and Yokogawas PCS Message Numbers
CIEMAC DS CENTUM Type Subtype Yokogawa Message No. 0001 0001 1101 1701 1701 1601 1601 1601 1601 1601 1603 ID Name Station name Station name Tag name Time-ofday sync Alarm code 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 0 0 0 0 0 Parameter Balance Factor (*1) 1
CIEMAC Event Category System alarm generation Time-of-day change Process alarm generation Guidance provision Guidance recovery MV operation SV operation Tag parameter change Parameter change Operation execution Tag parameter change Flicker stop Flicker stop (guidance) Operation record Sequence operation System alarm recovery Process alarm recovery Other -
CIEMAC Message No.
Alarm System alarm notification System alarm Process alarm Guidance Operator guide Operator guide Operation record Tag data change Tag data change Tag data change Tag data change Tag data change Block mode change
10, 20, 21, 22, 31, 33, 34, 35, 40 20, 21, 22 20, 25 10, 20, 25, 61 30, 31, 32, 33, 34, 35 10, 20, 21, 22, 23, 30, 31, 32, 33, 40 10, 20, 21, 22, 30, 31, 32, 33, 34, 35, 40 30, 33, 34, 35 40 10, 20, 21, 22, 30, 31, 32, 33, 34, 35, 40 Other Alarm recovery Process record
Station name Message Station name Message Tag name Tag name Tag name Tag name Tag name Tag name Tag name Tag name Tag name Item name Item name Item name Item name Item name Control mode Item name Item name Item name
Acknowledgement 1602 Acknowledgement 1602 Data change notification Sequence System alarm recovery Process alarm recovery 1407 1301 0002 1102 7001
Station name Message Station name Message Tag name Alarm code -
*1: Balance factor is the key for EBT (Event Balance Trend) graph.
TI 36J06A40-01E Aug.15,2005-00
4-4
4.2
4.2.1
Yamatake TDCS3000 (via Journal Station)

Yamatake TDCS3000 Events to be Analyzed
Yamatake TDCS3000 event data is gathered from Universal Station (US) via Journal Station. For Yamatake TDCS3000 event data, events gathered by the following procedure and provided in CSV format are taken as objects to be analyzed.
4.2.2
How to Output Journal Station PCs CSV File

The following is an example of how to obtain a CSV file using a floppy disk. It describes the procedure for saving a CSV file stored using Journal Station to a floppy disk. 1. Saving RTJ search files Output the results of a search made by Journal Station in CSV file format. By default, the CSV files will be saved in a specified folder in drive D. Default-specified folder D:\UsdcWNT\J-Data\Rtj 2. Starting Explore Start Explore to save a CSV file stored to the default-specified folder in a floppy disk. 3. Open the folder (default-specified folder) containing the CSV files. 4. Choose the CSV file (XXXXX.csv) you wish to copy. 5. Right click the mouse and select "Send/3.5-inch FD (A)" to copy the selected CSV file to Drive A (floppy disk).
TI 36J06A40-01E Aug.15,2005-00
4-5
4.2.3
How to Operate the Journal Station File Conversion Tool

Event files output as CSV files using Journal Station have the same format as information printed out. Loading a CSV file using Exaplog requires conversion of its format. Using the following tool allows the format of a CSV file to be converted to the Exaplog-compatible format.
1. Reading the CSV File Stored in the Journal Station PC
Save the CSV file saved in the floppy disk in section 4.2.2 in any directory.
2. Starting the File Conversion Tool

Start ConvertTool.exe contained in the following folder. C:\EXA\Exaplog\DCSType\YOKOGAWA\TDCS (JS)\ConvertTool.exe
TI 36J06A40-01E Aug.15,2005-00
4-6
3. Specifying the DCS Type and Conversion Source File Name

Select TDCS (PJ) for the DCS Type area. Specify the file name for File Name Before Conversion box that includes the network directory of the storage destination of the CSV file output from the Journal Station PC.

Specify a file name to be used after conversion for the File Name After Conversion box. Specify .csv for the extension. TIP
TI 36J06A40-01E Aug.15,2005-00
4-7
4.2.4
Method for Loading a Yamatake TDCS3000 CSV File using Exaplog

1. Starting PLAdmin
1. From the Windows [Start] menu, select [Program] - [YOKOGAWA EXA] [Exaplog] - [PLAdmin (Exaplog Administrator)] in that order. 2. The PLAdmin window appears. 3. Click the [Run Exaplog] button. This causes the Run Exaplog indication to switch to Stop Exaplog. 4. Click on the [Add] button, then the Adapter Add window displays.

Referring to section 1.3, Defining Event Data Connection for the PCSs of Other Companies, defines TDCS3000 (JS) event data connection. The information in section 1.3, Defining Event Data Connection for the PCSs of Other Companies, is as shown below: Adapter: Any name the user sets Type: Scan: Event Source: TDCS(JS) No Periodic Scan Network directory of the event file storage destination after conversion of a Journal Station file

1. Click the Demand Scan button. 2. The Demand Scan window appears. 3. Click Yes to overwrite the existing event database with the loaded events. (All events at the data acquisition destination are reloaded.)
TI 36J06A40-01E Aug.15,2005-00
4-8
4.2.5
Specifications for Yamatake TDCS3000 Event Conversion

Exaplog assigns Yamatake TDCS3000 event data provided in CSV format to Yokogawa PCS message numbers.
Table Correspondence between TDCS3000 Events and Yokogawas PCS Message Numbers
TDCS3000 CENTUM Type Alarm notification Subtype System alarm Process alarm Process alarm Guidance Operation record Operator guide Tag data change Acknowledgement Acknowledgement Security AON/AOF Process alarm recovery Other Yokogawa Message No. 0001 1101 1101 1701 1601 1602 1602 641 1403 1102 3000 ID Name Station name Tag name Tag name Station name Tag name Tag name Tag name Station name Tag name Tag name Alarm code Alarm code Message Item name Item name Item name User name On/Off Alarm code Parameter Balance Factor (*1) 1 1 1 1 -1 -1 -1 -1 0 0 0
TDCS3000 Event Category System alarm Process alarm Process alarm Guidance Operation Operation ack Operation ack Operation key Operation aof Process alarm RTN Other
TDCS3000 Message No. 99 21 21 23 26 31 32 76 28 21

*1:
TI 36J06A40-01E Aug.15,2005-00
4-9
4.3
4.3.1
Fuji Electric MICREX PC Printer

Fuji Electric MICREX Events to be Analyzed
For Fuji Electric MICREX event data, events provided in CSV format are taken as objects to be analyzed.
4.3.2
How to Obtain Data for Fuji Electric MICREX

Data in the following MICREX directory is regarded as event data to be analyzed.
Event Data Acquisition Folder

\C\ \YYYY-MM-DD.LOG YYYY: year MM: month DD: day
TI 36J06A40-01E Aug.15,2005-00
4-10
4.3.3
How to Operate the MICREX File Conversion Tool

MICREX event files require file format conversion for being loaded by Exaplog. Using the following tool allows the format of a CSV file to be converted to the Exaplogcompatible format.
1. Checking MICREX CSV Files
Check that MICREX event files have been stored in the Event Data Acquisition folder shown in section 4.3.2.

Start ConvertTool.exe contained in the following folder. C:\EXA\Exaplog\DCSType\YOKOGAWA\MICREX\ConvertTool.exe
3. Specifying the Conversion Source Event Data Storage Folder Destination

Enter the event data storage destination path name of a PC printer to the Folder Name box in the Source area. All files in the specified folder will be objects to be converted.
4. Specifying the Conversion Period

All files falling within the period of Start Date to End Date among event data files in the folder specified by Folder Name will be converted. If you wish to convert all the event data files stored in the folder of the Folder Name, check the All checkbox. To specify the period to which file conversion is applied, uncheck the All checkbox and specify the start date of the conversion period for Start Date and the end date of the period for End Date.
TI 36J06A40-01E Aug.15,2005-00
4-11
IMPORTANT
If the total size of files that fall within the conversion period exceeds 100 MB, the following error message appears during conversion and no files can be converted. In this case, specify the period such that the total size of files is 100 MB or below.
Figure
Error Message

Specify a file name to be used after conversion for the File Name box (file name after conversion) in the Destination area. Specify .csv or .txt for the extension. TIP
TI 36J06A40-01E Aug.15,2005-00
4-12
4.3.4
Method for Loading a Fuji Electric MICREX CSV File using Exaplog
1. Starting PLAdmin
1. From the Windows [Start] menu, select [Program] - [YOKOGAWA EXA] [Exaplog] - [PLAdmin (Exaplog Administrator)] in that order. 2. The PLAdmin window appears. 3. Click the [Start Exaplog] button. This causes the Run Exaplog indication to switch to Stop Exaplog. 4. Click on the [Add] button, then the Adapter Add window displays.

Referring to section 1.3, Defining Event Data Connection for the PCSs of Other Companies, defines MICREX event data connection. The information in section 1.3, Defining Event Data Connection for the PCSs of Other Companies, is as shown below: Adapter: Any name the user sets Type: Scan: MICREX No Periodic Scan
Event Source: file name created using the event conversion tool When the above setting is completed, click the [OK] button.
TIP
To specify a network directory for the Event File Name box, an Exaplog user must be specified in the PC in which that file exists.
TI 36J06A40-01E Aug.15,2005-00
4-13
Adding a user
1. Log on to the system as a user with the administrators rights 2. From the Windows [Start] menu, select [Setting] - [Control Panel] - [Management Tool] - [Computer Management]. 3. In the Computer Management window, select the Local User and Group. 4. Register the following new user. User Name exaplog Password exaplog1 Check the Apply the Password Indefinitely checkbox. If the User is requested to change the password at next log-on checkbox is checked, uncheck it.

TI 36J06A40-01E Aug.15,2005-00
4-14
4.3.5
Specifications for Fuji Electric MICREX Event Conversion

Exaplog assigns Fuji Electric MICREX event data provided in CSV format to Yokogawa PCS message numbers.
Table Correspondence between MICREX Events and Yokogawas DCS Message Numbers
MICREX CENTUM MICREX Event Content Alarm setpoint change Upper and lower operation limit setpoint change Type Subtype Setting change Setting change Control mode Setting change Operation output Operation output Block mode change Block mode change Yokogawa Balance Message ID Name Parameter Factor No. (*1) 1601 1601 1603 1601 1601 1401 1401 1101 1101 1101 1101 1101 1101 1101 1101 1102 4000 4001 Tag name Item name Tag name Item name Tag name Control mode -1 -1 -1 -1 -1 -1 1 1 1 1 1 1 1 1 1 0 0 0
MICREX Event Category
MICREX Message No.
Operation record
HG
Mode change Scale change Counter or timer change Run or stop, open or close, and on or off
Operation record
Tag name Item name Tag name Item name Tag name Item name Tag name Message Tag name Message Tag name Control mode
Status change
Status definition HK Message Module HH and LL Status definition ANN Module PH and PL Status definition Module PH and PL Status definition PG
Process record
Major failure occurrence
PM
Process alarm Alarm notification Process alarm Process alarm Alarm Process alarm notification Process alarm Process alarm Alarm notification Process alarm Alarm recovery Process alarm recovery
Tag name Item name Tag name Item name Tag name Item name Tag name Item name Tag name Item name Tag name Item name Tag name Recovery Tag name Message Tag name Message
Intermediate failure occurrence
PB
Minor failure occurrence Recovery from failure
PR
System alarm SM System alarm SG recovery

*1:
Alarm System alarm notification Alarm recovery System alarm recovery
TI 36J06A40-01E Aug.15,2005-00
4-15
4.4
4.4.1
Hitachi EX6000/7000 Series PC Printer

Hitachi EX6000/7000 Series PC Printer Events to be Analyzed
Hitachi EX7000 event data is event data stored in the operator station. For Hitachi EX7000 event data, events gathered via the EX6000/7000 series PC printer and provided in CSV format are taken as objects to be analyzed.
4.4.2
How to Obtain Hitachi EX6000/7000 Series PC Printer Data

Data in the following EX6000/7000 Series PC printer directory is regarded as event data to be analyzed.
Event Data Acquisition Folder

\C\ \YYYY\MM\YYYY-MM-DD_HH.mrd YYYY: year MM: month DD: day HH: 00 to 23 (No HH file exists in a time period during which no event has occurred)
TI 36J06A40-01E Aug.15,2005-00
4-16
4.4.3
How to Operate the EX6000/7000 Series PC Printer File Conversion Tool

EX6000/7000 Series PC printer event files require format conversion for being loaded by Exaplog. Using the following tool allows the format of a CSV file to be converted to an Exaplogcompatible format.
1. Checking EX6000/7000 Series PC Printer CSV Files
Check that EX6000/7000 Series PC printer CSV files have been stored in the Event Data Acquisition folder shown in section 4.4.2.

Start ConvertTool.exe contained in the following folder. C:\EXA\Exaplog\DCSType\YOKOGAWA\EX7000 (PCPrinter)\ConvertTool.exe
3. Specifying the Conversion Source Event Data Storage Folder Destination

Enter the PC printer event data storage destination path name to the Folder Name box in the Source area. All files stored in the specified folder will be objects to be converted.
TI 36J06A40-01E Aug.15,2005-00
4-17
4. Specifying the Conversion Period

All files falling within the period of Start Date to End Date among event data files in the folder specified by Folder Name will be converted. If you wish to convert all the event data files stored in the folder of the Folder Name, check the All checkbox.

Specify a file name to be used after conversion for the File Name box (file name after conversion) in the Destination area. Specify .csv or .txt for the extension. TIP
TI 36J06A40-01E Aug.15,2005-00
4-18
4.4.4
Method for Loading a Hitachi EX6000/7000 Series CSV File using Exaplog
1. Starting PLAdmin
1 2 From the Windows [Start] menu, select [Program] - [YOKOGAWA EXA] [Exaplog] - [PLAdmin (Exaplog Administrator)] in that order. The PLAdmin window appears.
3. Click the Run Exaplog button. This causes the Run Exaplog indication to switch to Stop Exaplog. 4. Click on the [Add] button, then the Adapter Add window displays.

Referring to section 1.3, Defining Event Data Connection for the PCSs of Other Companies, defines Hitachi EX6000/7000 event data connection. The information in section 1.3, Defining Event Data Connection for the PCSs of Other Companies, is as shown below: Adapter: Any name the user sets Type: Scan: Event Source: EX7000 (PC Printer) No Periodic Scan Network directory of Exaplog text file storage destination after conversion of an event data file the PC printer has

TI 36J06A40-01E Aug.15,2005-00
4-19
4.4.5
Specifications for Hitachi EX6000/7000 Event Conversion

Exaplog assigns Hitachi EX6000/7000 event data provided in CSV format to Yokogawa PCS message numbers.
Table Correspondence between EX6000/7000 Events and Yokogawas DCS Message Numbers
EX6000/7000 CENTUM Type Subtype Yokogawa Message No. 0001 1101 1701 1601 1601 1601 641 1601 ID Name Station name Tag name Station name Station name Tag name Tag name Tag name Tag name Tag name Tag name Tag name Tag name Recipe name Tag name Recipe name Recipe name Tag name Tag name Item name Alarm code Operation mark no. Alarm code Message Item name Item name Item name Item name Item name Control mode Item name Item name Item name Parameter Balance Factor (*1) 1 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 0 0
EX6000/7000 Event Category System alarm Process alarm Operator guide SLC data setting Graphic operation data setting Sequence data setting System stoppage Switch operation Status switching Selector operation Valve motor operation Loop data setting Process switching Operation mark Recipe data change
EX6000/7000 Message No. r5S,r5PCS r0P r0O r0D r0D r0D r0D r0D r0D r0D r0D r0D r0D r0D r0D
Alarm System alarm notification Process alarm Guidance Operation record Operator guide Tag data change Tag data change Tag data change Security Tag data change
Block mode change 1603 Tag data change Tag data change Tag data change Recipe operation Operation mark control Recipe operation Recipe operation Tag data change Alarm recovery Other Process alarm recovery 1601 1601 1601 1619 1641 1619 1619 1601 1102 3999
Scheduled product r0D type setting Operation record (others) Process alarm recovery Other r0D r0P
*1: Balance factor is the key for EBT (Event Balance Trend) graph.
TI 36J06A40-01E Aug.15,2005-00
Blank Page
Revision Information
Title Manual No. : Exaplog Event Conversion Specifications for Process Control Systems of Other Companies : TI 36J06A40-01E
Aug. 2005/1st Edition Newly published
TI 36J06A40-01E Aug.15, 2005-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.

ExaPlog TI

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ExaPlog TI

Încărcat de

Drepturi de autor:

Formate disponibile

Technical Information

TI 36J06A40-01E 1st Edition Aug. 2005

All Rights Reserved. Copyright 2005, Yokogawa Electric Corporation

TI 36J06A40-01E Aug.15, 2005-00

Yokogawa PCS Event Map........................................................... 2-1 International Companies.............................................................. 3-1

Emerson DeltaV ....................................................................................... 3-6

Japanese Companies................................................................... 4-1

Yamatake TDCS3000 (via Journal Station) ........................................... 4-4

TI 36J06A40-01E Aug.15, 2005-00

Fuji Electric MICREX PC Printer ............................................................ 4-9

Hitachi EX6000/7000 Series PC Printer ............................................... 4-15

TI 36J06A40-01E Aug.15, 2005-00

Target PCS Event Data

Overview of the Event Data Connections of the PCSs of Other Companies

Conversion table for the other companys PCS

File conversion Tool

Company-A specific event file

Converts the file format

Exaplog text file (comma- or tabdelimited)

CSV file for Exaplog

Exaplog event databese

Defining Event Data Connection for the PCSs of Other Companies

<2. Yokogawa PCS Event Map>

Yokogawa PCS Event Map

<3. International Companies>

How to Output a Virtual Printer Application CSV File

Figure Example of TDC3000 Event File

<3. International Companies>

How to Operate the Virtual Printer Application File Conversion Tool

2. Starting the Conversion Tool

<3. International Companies>

3. Specifying the DCS Type and Conversion Source File Name

4. Specifying a File Name after its Conversion

<3. International Companies>

Method for Loading a Honeywell TDC3000 CSV File using Exaplog

2. Setting up the Adapter

When the above setting is completed, click the [OK] button.

3. Loading Event Data into an Exaplog-installed PC

<3. International Companies>

Specifications for Honeywell TDC3000 Event Conversion

Type AlarmNotify AlarmNotify AlarmNotify AlarmNotify AlarmNotify AlarmRecovery Guidance

SubType SysAlarm SysAlarm SysAlarm SysAlarm TagAlarm TagAlarmRecovery Opeguide

Balance Factor (*1) 1 1 1 1 1 0 1 -1 -1 0 0 -1 -1 1 1 1 1 -1 0

OperationRecord TagModeChange OperationRecord TagDataEntry ProcessRecord ProcessRecord AlarmOnOff AlarmOnOff

OperationRecord Security ProcessRecord Fieldbus

<3. International Companies>

How to Output a DeltaV CSV File

Figure Example of a DeltaV Event File

<3. International Companies>

Method for Loading an Emerson DeltaV CSV File using Exaplog

2. Setting up the Adapter

When the above setting is completed, click the [OK] button.

3. Loading Event Data into an Exaplog-installed PC

<3. International Companies>

Specifications of Emerson DeltaV Event Conversion

YOKOGAWA Message Point ID Number

Balance Factor (*1)

TagDataEntry TagModeChange TagModeChange

TagName ItemID TagName Mode TagName Mode

CHANGE CHANGE CHANGE CHANGE

USER USER USER USER

* LOGON LOGOFF REMOTE LOGON

OperationRecord OperationRecord OperationRecord OperationRecord