Yokogawa ExaQuantum Usage Procedure Rev1

Vendor Doc. No.
YOKOGAWA EXAQUANTUM USAGE -

PROCEDURE
Revision:0 Doc. Status:-
Document type: Procedure Rev. Date: 13 June 2017 Page 1 of 8
DONGGI SENORO LNG
YOKOGAWA EXAQUANTUM USAGE PROCEDURE
YOKOGAWA EXAQUANTUM USAGE

PROCEDURE
0 13 Jun‘17 Issued For Comment AM
BY CHK APP APP DATE

REV. DATE DESCRIPTION
YOKOGAWA DSLNG
Vendor Doc. No.
PROCEDURE
Revision: 1 Doc. Status: -
Document type: Procedure Rev. Date: 23 January 2018 Page 2 of 8
SHEE REVISIONS SHEET REVISIONS

T A B 0 1 2 A B 0 1 2
1 x 51
2 x 52
3 x 53
4 x 54
5 x 55
6 x 56
7 x 57
8 x 58
9 x 59
10 x 60
11 x 61
12 x 62
13 x 63
14 x 64
15 x 65
16 x 66
17 x 67
18 x 68
19 x 69
20 x 70
21 x 71
22 72
23 73
24 74
25 75
26 76
27 77
28 78
29 79
30 80
31 81
32 82
33 83
34 84
35 85
36 86
37
ATTACHMENT APPENDIX
38
39 1
40 2
41 3
42 4
43 5
44 6
45 7
46 8
47 9
48 10
49 11
50 12
TABULATION OF REVISED PAGES
- Introduction:
Vendor Doc. No.
PROCEDURE
Exaquantum is a Plant Information Management System (PIMS) that provides business benefits to
users in various industries. The main function of Exaquantum is the acquisition of data from all facets
of a business and the subsequent transformation of that data into easily usable, high value, widely-
distributed information. The data then becomes an integral part of the set of tools used by the
business in vital decision-making processes.
Exaquantum is the business intelligent gateway between the operational Process Control System
(PCS) and the business Enterprise Resource Planning (ERP) system. Using the latest, proven,
Microsoft based open technology Exaquantum is designed to provide low administration costs, and be
robust to future IT trends.
ExaQuantum daily usage are :
1. Collect Historical Trend Data
2. Collect Historical Excel Format Data
3. Exaquantum Auto-Archive
4. Exaquantum Routine Database Backup
5. Exaquantum Database Restore
6. Exaquantum Merge Database
7. Adding Exaquantum Tag
8. Manual RDS Historical Catch Up
9. Exaquantum Regular Maintenance

Vendor Doc. No.
PROCEDURE
1. Collect Historical Trend Data

No Tasks Picture
.
1 As Data Historian, Exaquantum has Trend Analyze tool to collect historical data value of registered tags
for a specific time period
2 To start Trend Analyze:

From Windows START menu –
Trend Analyze
3 1. A trend analyzer window will

appear.
(1)
2. Press data selector button
(2)
3. A data selector tree window will

appear on the right
(3)
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
4 1. Click “+” from Root of data
selector window,
The folder will be expanded
2. Browse desired tag we want to

(1)
collect the history
3. Then highlight the desired item,

commonly PV is the item we want
to collect
(2) (3)
5 Drag highlighted PV item of
desired tag to the lower left
window. You can do this to more
than one tag, so you can compare
their values for a specific time.
(by default, value history will
automatically show last 1 day
data as trend graph)
6 To configure specific time range

period:
1. Select start date (left date box)
2. Start time (left time box)
3. End date (right date box)
4. End time (right time box)
5. Then click Apply button (with
the red check mark)
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
7 Tags value history for specified
time is displayed as trend.
You can also stretch vertically the
trend by adjusting display pointer
8 To capture this trend view data,

you can either use windows print
screen function, or you can right
click on the trend window – select
Copy Image to Clipboard.
(You can paste it to paint or
directly to Microsoft Office
application)
The other option is directly click

print button to get the trend
hardcopy
Vendor Doc. No.
PROCEDURE
2. Collect Historical Excel Format Data

No Tasks Picture
.
Caution:
Collecting excel raw data from Trend
Analyze application is not
recommended because the timestamps
are following data changes that
displayed in trend graphic, not actual
interval 1 second.
1 To collect historical data with

excel format, first open new sheet
of Microsoft Office Excel – then
open “Exaquantum” tab on menu
bar (or “Add Ins” from client PC)
2 Select “Data Selector” from menu

bar
Then a new window

“Exaquantum Excel Add-In Data
Selector” will appear
3 Before selecting the data, we

need to set time configuration of
the data we will gather.
Right click blank part of the Data

Selector window – Times
A new window “Set Data

Range/Update” will appear
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
4 Here you can choose “Live”/latest

actual data. But when you want
to collect data record, choose
“History” on Data Type
5 You can also choose data range

- Point : one item value from
history
- Trend : array of item values
from history
- Aggregation : aggregation data
from history (such as max, min,
mean, sum, etc)
6 Then choose the Start Time and
Stop Time
6a If you select Aggregation instead

of Trend for Data Range,
You will able to choose what

aggregation you need from
dropdown
7 Setting sampling interval for

desired data record.
Lowest interval is 1 second same

Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
with DCS scanning time
8 If you pick “Live” data from Data
Type, you can set Update Rate
here.
But if you have an excel form with

many “Live” data, you cannot see
actual 1 second update rate due
to internal data access load to
Exaquantum Server
9 Now, we pick the data we want to

gather.
Browse the tag by open “+” mark
from root
10 For example, we want to gather

data from 041FIC2430, browse to
Root.PID.041FIC2430
Select / highlight the PV item

(it is important to make sure the
item to be collected is selected /
highlighted. Otherwise, data to be
shown is still the same with
previous selected tag/item)
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
11 Drag the PV item and drop it to a
cell.
Press “Start Data Update” from

menu bar.
After a brief moment, you will get

an array of selected data from a
certain timestamp you configured
before
12 We also need to show the

timestamp in the table.
To do that, open ‘+’ on the PV

and get PV.Value.Timestamp.
Same move, drag it to the table
Drag other tags as you need to

make a table
Autosampler Data Collect
Regularly, laboratory personnel requests an auto sampler data record after loading or on other analyze
purpose. Basically to collect these data, the steps are same with Collect Historical Record Data above
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
1 But, since this auto sampler data
is often be requested
From \\dssvexa103, we only need

to use Template File “Auto
Sampler Data Template.xltx”, a
table is ready.
2 A previous Auto Sampler Data

gathering is displayed
3 Select top left cell of the table

(B2)
4 Open Add-Ins from menu bar
5 Select “Edit Query” button

Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
6 a. Displayed “Exaquantum Query
Wizard” button
b. b. Click “Next” twice until

reaches “Times Selection”
7 Specified date and time period
8 Click “Next” 4 times until reaches

summary window, then click
“Finish”.
9 Wait a brief moment, until all data

are displayed
10 a. Select “Save” button on the top left menu bar

b. Specify destination folder and file name
GTG Monthly Load
Related to “Pajak Penerangan Jalan” (PPJ) which need to be paid by DSLNG, on the beginning of every
month, DSLNG need to collect GTG monthly actual power total on KWH
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
1 Similar to Auto Sampler, Excel
file template to collect this data is
prepared.
Log on to \\dssvexa103
Open file “GTG Monthly Actual

Power.xltx”
2 To prevent data collecting before

you set the time range, you better
to Press “Stop Data Update” from
Menu bar – Exaquantum or Add-
Ins tab
3 With just using simple setting, set
the start date/time and stop
date/time of desired auto sampler
data time range to gather. Input it
manually
4 After time range is set, press
“Start Data Update” from Menu
bar – Exaquantum or Add-Ins
tab.
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
5 After a brief moment, data is
gathered.
After formatting, file save as and

the data is ready to be submitted
to PCE.
Vendor Doc. No.
PROCEDURE
3. Exaquantum Auto-Archive
No Tasks Picture
.
1 As a Data Historian, Exaquantum has a fix database allocation size in the hard disk space. DSLNG
Exaquantum (RTDB3 - Server in Admin building) using around 1TB database allocation size. This
means 1TB is the maximum capacity of online data historian record that can be accessed directly.
When database is full, Exaquantum can no longer record data (freeze). To prevent this, there is an auto
archive function to detach old data from database and free some space in database allocation
automatically with a certain interval.
Currently, RTDB3 – which regularly accessed by DSLNG personnel PC clients (Operation, PE, PCE,
etc.) – is maintained with 1 year online database.
2 To make archiving possible, we

need to create a backup device as
a container of archived database
First, Login to
DSSVEXA103\Quantumuser
Open Start Menu– SQL Server

Management Studio
3 Press “Connect”
From left panel, open

(MACHINE NAME) – Server
Object
Right Click “Backup Device” –

choose New Backup Device
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
4 Browse to a folder that dedicated
to store a backup device.
(F:\ArchiveDB\)
And then specify backup device

file name.
(Better refer to Archive Group to
be assigned to this backup device.
Example : RawFast.bak)
*Caution: make sure this folder is

exists all the time. If the folder is
renamed or moved, the auto
archive function will fail
Now, the backup device

destination is ready. But, the .bak
file not directly created. It will
generated on the next archiving
activity
5 Next thing we need to do is to use

this backup device, assign it to
related Archive Group:
Open Start Menu – Exaquantum –

Administration Tools
Browse to console Root –

Yokogawa Exaquantum –
Database Management –
Archiving
Select Archive Group

(Example: Raw Fast)
Now select related available

backup registered device
(Example: RawFast.bak)
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
6 Set the auto archive configuration:
Set Archive Period

(New database ID generated
every this period)
Open Group Advance :

- Enable automatic archiving
- Check Auto-Save
- Set retention period

(how long past data maintained
become Candidate – before saved
to backup)
- Set Automatic offline period

(how long past data maintained
become Online – archived, and
saved).
- Advance - Automatic un-restore

after save is enabled
Leave the other setting

7 Result : (example: Raw Fast case)
- This results Exaquantum have

total 360 days stored data that
available to be accessed for
Raw Fast Archived Group .
- Any newer archived data per .
day will shift the days and
361st online data will be
automatically become offline
(un-restored automatically)
.
.
Vendor Doc. No.
PROCEDURE

Vendor Doc. No.
PROCEDURE
4. Routine Database Backup

No Tasks Picture
.
After discussion, it will be use 1 year backup interval for routine Exaquantum RTDB3 database. This meant for
better effectiveness when a data for certain period need to be recalled.
Routine database backup planned will be performed in the beginning of every year starting 2018. Since the
database is set archived after 5 months / 150 days, the data content for routine database backup will shifts 5
months
So database backup should will be like following :
No Backup time Database Content
1 Early 2018 15 Nov’14 to xx Aug’17
2 Early 2019 xx Aug'17 to xx Aug'18
3 Early 2020 xx Aug'18 to xx Aug'19
4 . .
. . .
. . .
Caution:
Do not perform any backup/restore Exaquantum database through midnight. Since auto archive process
performed on midnight, this will interrupt the process and might result data corrupt.
1 First we need to note the data

content of database stored in
backup device:
Start Menu – Exaquantum –


Archiving
Choose “Raw Fast” archive group

(as representative of all group)
Verify backup device is using

RawFast.bak
Click Content
Note lowest and the highest ID

listed .
Note date on the description of .
that two ID
These dates should be the

database content period
(following is example content

(15 Nov 2014 – 7 June 2017)
period from first yearly backup
schedule)
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
2 Then from windows explorer, we
locate the dedicated folder to
store the backup devices.
(F:\ArchiveDB\)
3 Select all content of the folder
(Move the files)

“Cut” those files
This will not stop the auto archive

routine. A new file will be
automatically generated on the
next archiving activity.
Caution: Do not rename, move,

or cut the folder. Just do the files.
4 Paste those files to Database

Backup destination
(Could be cassette / external
storage / network storage)
5 Make sure to label the Database

backup with representative Example:
content refer to step 1 (15 Nov 2014 – 7 June 2017)
Vendor Doc. No.
PROCEDURE
5. Database Restore
No Tasks Picture
.
As we know that Exaquantum is using backup devices to store archived data dedicated for each Archive
Group. To restore a data (from an old archived database - .bak file), we need to register this old .bak file to
another new backup devices.
1 First we need to locate the old
.bak file which contains data of
what we want to restore.
This file is must be in localhost /

physical external storage.
If it is not, copy it to available
storage
(Example: E:\Restore\)
2 Then temporarily create a new

backup device:

Management Studio
Press “Connect”

Object
Right Click “Backup Device” –

choose New Backup Device
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
3 Browse to a the file we located in

step 1
And then specify backup device

file name.
(Better refer to related Archive
Group. Example :
RawFast_temp.bak)
4 Now we go to :
Start Menu – Exaquantum –

Vendor Doc. No.
PROCEDURE
No Tasks Picture
.

Archiving
Choose “Raw Fast” archive group
5 By original setting, you can see

backup device shown here is
“RawFast.bak”
Because we want to restore from

other backup device, we need to
change this backup device into
“RawFast_temp.bak”
Press “Content” to see the

database period that available in
this backup device.
You should see a time range that

you want to restore, just to verify.
Then OK.
6 From this Raw Fast archiving

window, browse ID(s) that related
to a time range that you want to
restore.
Select the ID, and press the

“Restore” button on below. Wait a
moment until the process is
completed
Notice that archived files status

changes from Offline to Online
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
Now the data on this time range

could be accessed
7 Do step 6 to every ID you need to

restore.
After that you can collect the data

you need.
Caution:
This restoring database activity is consuming database allocation size.
Bigger database could lead to slower data access from Exaquantum server by clients.
It is recommended not to restore more than 90 ID(s)
7 Now the data on this time range

could be accessed
Caution : any time before leaving

this window, make sure you
change again the backup device
to the original (RawFast.bak).
This is important, because it
related to which backup device
the next auto archive will append
the data to.
8 Now back to un-register this

temporary backup devices:

Management Studio – Connect

Object – Backup Device – Right
Click “RawFast_temp” - choose
delete.
*on this step, optionally, you can

do database merge refer to
procedure 6
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
9 You need to un-restore these

ID(s) after usage to maintain
online database size. You may
give some couple days before
you un-restore again those ID(s).
Vendor Doc. No.
PROCEDURE
6. Database Merge
No Tasks Picture
.
To merging database to existing active archive device, first we need to restore the additional/old archive file
content refer to procedure no. 5. This merging database activity have purpose to merge add database archive
content (ID) to existing active archive device.
In this example, we merge the restored IDs from procedure 5 to existing archive database.
1 Before Un-restoring IDs
(Procedure 5,9), we need to
merge these restored ID to
RawFast.bak
So ensure the device is already

back to RawFast
2 From this Raw Fast archiving
window, browse ID(s) that related
to a time range that you want to
merge to existing archive device.
The target ID status should be

Online
3 Now press Save button below
Verify target device is RawFast

And on Overwrite section:
Append to media.
Then press OK
Wait until progress is complete
4 Do step 2 and 3 to every ID you

need to merge. Confirm the IDs is
added to RawFast device content
5 You may need to un-restore

these ID(s) after merging to
maintain online database size.
Vendor Doc. No.
PROCEDURE
7. Adding Tag
No Tasks Picture
.
Above picture of Exaquantum data flow in DSLNG site. PC clients are some appointed PC machine that could
access Exaquantum data. But to access it, only registered accounts that have right to access or input manual
data.
Based on that picture when adding a new tags to be available to access in PC clients:
1. The tags should be available first in DCS
2. Equalize tag to ExaOPC
3. Register tag in RTDB1
4. Mapping tag to RTDB3
5. Register tag in RTDB3
1 Most tags registered in

Exaquantum are indicator (PVI)
or controller (PID) either
hardwire, Modbus, Fieldbus, etc.
After Regulatory blocks are

created, perform ExaOPC from :
a. Menu – Load –
Download Project
Common section
Wait until process
completed
b. Menu – Load –
Download tag list – pick
related controller on the
left, STN0155 on the
right. Equalize, OK
2 Log on to RTDB1
(\\dssvexa101\Quantumuser)
Open Administration Tools

Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
3 From left panel : Console Root –
Tag Editor
4 From right panel, browse to

related hierarchy of your new tag.
(PVI for indication, PID for
controller)
Example:
Root.All Tag.PVI.UNIT-071
Right Click the folder – Add

Select Function Block
5 Select related FB Tag template

(PVI-ALL for indication, PID-ALL
for controller)
Type the tag name
6 Click the button on Settings cell

of each Tag Name item.
Set with correspondence OPC

item
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
7 Wait a moment, confirm
timestamp, range, and values of
tag item are updating
8 Now perform tag mapping:
Open Publisher Management

Console.
On left panel, right click New
Publisher 1 – View /Edit
Configuration
9 Go to Tag Mapping tab.

Press Export.
Point to following folder:

\\Share_STN155\From RTDB1\
Tag Mapping
Rename the file. Press Save

Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
10 Open File Explorer, open the
exported file
11 Follow existing pattern, add lines

to map related tag items of newly
added tag. Save & Close
12 Perform step 8 to 11 for Aggregation Instance
13 To apply the mapping :
From Publisher Management

Console main window, right click
New Publisher 1 - select disable
Right Click again – Edit/View

Setting
14 Go to Mapping tab
Import the related modified tag
mapping excel file – Open
Press Exit
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
15 Right click New Publisher 1 –
select enable
16 Perform step 13 - 15 for Aggregation Instance
17 Now move, log on to RTDB3:

Open Administration Tools

18 From right panel, browse to
related hierarchy of your new tag.
(PVI for indication, PID for
controller)
Example:
Root.All Tag.PVI.UNIT-071
Right Click the folder – Add

Select Function Block
19 Select related Tag template

(PVI-ALL for indication, PID-ALL
for controller)
Type the tag name
And assign related data item
Then OK
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
20 Wait a moment, confirm
timestamp, and values are should
be updating (5 min period)
21 If the data are still not updating,

please check Application Event
viewer errors on either RTDB1 or
RTDB3 of any tag destination
mismatch or mistyped.
22 When no more errors, the data should be now available in the clients.
Vendor Doc. No.
PROCEDURE
8. Manual RDS History Catch Up

No Tasks Picture
.
DSLNG has 2 Exaquantum servers. RTDB1 as a server that directly collect data from the DCS. With RDS
function, RTDB3 mirrors data from RTDB1 and distribute it to Exaquantum clients/users. When connection
loss appear between these two servers for a short time, a historical catch up function can recover the data.
But if the connection loss is longer than 20 minutes, this history catch up function cannot fix the damage.
Thus, it will be require additional procedure for manually equalize to recover these data.
1 Before we go to history catch up,
we need to confirm first the
connection is already re-
established
To test this, you may perform

procedure 1 or 2 on RTDB1 and
RTDB3. Or also check the
timestamps on Administration
Tools – Tag Editor
You can also check the event

viewer
When the data only bad on

RTDB3, an RTDB3 restart mostly
do the fix
2 When the latest data is update,
we can recover the loss data on
the down time.
You can note this down time with

Procedure 1 Trend View.
3 Now move, log on to RTDB3:

Open Publisher Management

Console
Right Click New Publihser 1 –

View/Edit Configuration
Vendor Doc. No.
PROCEDURE
No Tasks Picture
.
4 Go to Data Export Tab, and input
down time that you note on step
2. Better to extend more hour
before and after the down time.
Press Export Tag Data
Safe the file to

\\Share_STN155\From
RTDB1\History Catch Up
5 Name it with representative time range - Save

Wait until the process is completed. Could take several minutes.
6 Repeat Step 3 to 5 for Aggregations Instance
7 Copy those .rds exported files to

RTDB3 via a dedicated external
hard disk.
Better place it to
\\dssvexa103\Desktop\.Problems
and Activity\ [date of data loss
event]
8 Open Consumer Management
Console
Go to Import Data tab
Import Tag list – Browse file to

newly exported file
OK – Wait until the process

completed
This may take several hours
9 Perform step 7 for Aggregations exported file
10 Now, the data on RTDB3 should

be equalized from RTDB1.
You may confirm it with access

the data similar with step 1

Yokogawa ExaQuantum Usage Procedure Rev1

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Yokogawa ExaQuantum Usage Procedure Rev1

Hochgeladen von

Copyright:

Verfügbare Formate

Vendor Doc. No.

YOKOGAWA EXAQUANTUM USAGE -

DONGGI SENORO LNG

YOKOGAWA EXAQUANTUM USAGE PROCEDURE

YOKOGAWA EXAQUANTUM USAGE

0 13 Jun‘17 Issued For Comment AM

BY CHK APP APP DATE

Document type: Procedure Rev. Date: 23 January 2018 Page 2 of 8

SHEE REVISIONS SHEET REVISIONS

Document type: Procedure Rev. Date: 23 January 2018 Page 3 of 8

ExaQuantum daily usage are :

1. Collect Historical Trend Data

2. Collect Historical Excel Format Data

4. Exaquantum Routine Database Backup

5. Exaquantum Database Restore

6. Exaquantum Merge Database

7. Adding Exaquantum Tag

8. Manual RDS Historical Catch Up

9. Exaquantum Regular Maintenance

Document type: Procedure Rev. Date: 23 January 2018 Page 4 of 8

1. Collect Historical Trend Data

2 To start Trend Analyze:

3 1. A trend analyzer window will

2. Press data selector button

3. A data selector tree window will

Document type: Procedure Rev. Date: 23 January 2018 Page 5 of 8

2. Browse desired tag we want to

3. Then highlight the desired item,

6 To configure specific time range

Document type: Procedure Rev. Date: 23 January 2018 Page 6 of 8

8 To capture this trend view data,

The other option is directly click

Document type: Procedure Rev. Date: 23 January 2018 Page 7 of 8

2. Collect Historical Excel Format Data

1 To collect historical data with

2 Select “Data Selector” from menu

Then a new window

3 Before selecting the data, we

Right click blank part of the Data

A new window “Set Data

Document type: Procedure Rev. Date: 23 January 2018 Page 8 of 8

4 Here you can choose “Live”/latest

5 You can also choose data range

6a If you select Aggregation instead

You will able to choose what

7 Setting sampling interval for

Lowest interval is 1 second same

Document type: Procedure Rev. Date: 23 January 2018 Page 9 of 8

But if you have an excel form with

9 Now, we pick the data we want to

10 For example, we want to gather

Select / highlight the PV item

Document type: Procedure Rev. Date: 23 January 2018 Page 10 of 8

Press “Start Data Update” from

After a brief moment, you will get

12 We also need to show the

To do that, open ‘+’ on the PV

Same move, drag it to the table

Drag other tags as you need to

Autosampler Data Collect

Document type: Procedure Rev. Date: 23 January 2018 Page 11 of 8

From \\dssvexa103, we only need