West Delta

Control Center
By: Data Exchange Team
OAGTraining
This document is prepared by the Data Exchange Department
Personnel Eng.Alaa Abdallah Elghazaly, Eng. Nagwa Abd Elraaof
from WDRCC based on the training session presented by
Eng.Stevens Jouyex from AREVA staff in january 2009
Egyptian Electricity
Transmission Company
Training Session for OAG System Page 2 of 17

Prepared by Data Exchange Dept.
Contents
- Environment Variables
- ICCP Blocks
- Configuration Files
- How can we add a data set in the import file
- How to import the txt file to the GUI browser
- Max scan rate
- LINK ID and PATH ID
- How to extract the history log from database
- Creation and naming of output data sets
- Directory of all savecases
- How to upload a savecase to runtime
- Configuration Control
- Permit
- NETIO
- Data Semantics Conversions
- HABITAT shortcuts
- CONTROLS
- IMPORTANT NOTES


Training Session for OAG System Page 3 of 17

Prepared by Data Exchange Dept.
Environment Variables
Objective: To allow savecases to be valid for both servers without affecting the
addresses of each server.
Ex: When we change an environment variable name (i.e. LOCAL_AR_NAME) in the
browser we should also change it in windows setting as follows:
Right click on "My Computer" >> Properties >> Advanced >> Environmental Variables
And change the variable name to the same name in browser


Note: the first variable name refers to the IP of LANA and the 2nd for LANB.
Training Session for OAG System Page 4 of 17

Prepared by Data Exchange Dept.
Variable Name WDIC1 WDIC2
LOCAL_AR_NAME WDIC1A WDIC2A
LOCAL_AR_NAME2 WDIC1B WDIC2B
ICCP Blocks
For Bilateral table (AIEF):
Block 1, 2 only mean that we can only receive and observe data but no control can be
done, If Block 5 is mentioned: this means that we can do control functions which
already supported by the OAG system
Configuration Files
We have 3 important types of files that must be known to configure to update or add
an ICCP control center or data sets or data items to the system:
1- OSILL2.cfg file
2- IMPORT file
3- PERL script (PL file)
OSILL2 file
Configuration file Located at C:\Program Files\SISCO\osill2\OSILL2.CFG
It contains the configuration done for the control center on MMS-EASE layer like:
- AR_NAMEs
- IP addresses
- AP Title
- PSEL, SSEL, TSEL and other parameters
Training Session for OAG System Page 5 of 17

Prepared by Data Exchange Dept.

Note: rules for choosing AP Title and PSEL and other parameters are found in this document
"Inst_mmease_132095.pdf"
We can also configure all these parameters without editing the OSILL2 file by using
SISCO STACK Configuration application
From start choose >> Programs >> Sisco >> Osi Stack >> Stack Configuration

But first we have to configure a registry file to choose between editing cfg file (OSILL2)
or stack manager
From start choose run >> regedit >> HKEY_LOCAL_MACHINE >> SOFTWRAE >>
Sisco >> OSILL2 >> Current version >> Parameters then we will find value named
"usecfgfile" if set 1 it will use it and if set 0 we will use the stack manager

Training Session for OAG System Page 6 of 17

Prepared by Data Exchange Dept.
Note: from Stack Configuration application we can also generate an OSILL2 file with the settings we
did in the application File >> Generate Stack Configuration File
IMPORT TXT file
Text file Located in E:\AREVA\OAG\OAGCONF"file name.txt"
The main file that contains Number of total remotes and The Data sets and Data items
Names, sources, Types and other related parameters

- DS_IDENT=WDDSX
The identifier of the data set
Note: the name will appear like this "A_ WDDSX_WD_TO_OAG or P_ WDDSX_WD_TO_OAG"
according to the setting in the PERL (states that P=digital and A=analog and Source TO
Destination)
- DI_SOURCE=WD, ISD, 1
States the source remote of this data item and which protocol is used and what is the
index of this remote
- DI_TYPE=
1. DI_TYPE=POINTQ
Training Session for OAG System Page 7 of 17

Prepared by Data Exchange Dept.
Means that the type of the data items contained in this data set is Status with
Quality
2. DI_TYPE= ANALOGQ
Means that the type of the data items contained in this data set is Analogs with
Quality
- DI_SCOPE=GLOBAL
Means that the type of the data scope is the default value (which is VMD)
- DI_SCOPE=DOMAIN
Means that the type of the data scope is DOM
- DEVICE_TYPE=DO_DOMAIN
This is set for control type data items, stands for Direct Operation and means
that this will operate by just a click
- DEVICE_TYPE=SBO_DOMAIN
This is set for control type data items and means Select before operation and
means that we have to select first which device we wish to control
How can we add a data set in the import file?
Before any group of data items (those will be contained in this data set) we add
the data set identifier format DS_IDENT=ANY VALUE
Note: it is recommended to add data sets or data items directly in this txt file instead of using
the GUI browser because if any value has been added in GUI and later I imported this file, any
changes I made in GUI without adding it in the file will be lost.

Training Session for OAG System Page 8 of 17

Prepared by Data Exchange Dept.
Steps of how to import the txt file to the GUI browser:
1- Retrieve the empty savecase (Important so that no duplication of data sets
happening) so there will be no data sets except the automatically generated
ones (those are used to check the link status and provide it to the SCADA)
2- Go to the folder containing the IMPORT file E:\AREVA\oag\oagconf and
right click on it >> choose prompt
3- Type "perl pl_file_name txt_import_file_name" and press ENTER
Note: file names must not have spaces
4- If the previous steps done right it will create a .bat file (impot_OAG_wd.bat) in
the same folder if we execute it this will update our browser to the changes we
made in the txt IMPORT file
Max scan rate
It is the time before I can send output data (i.e. before this time I can't send data this
means that the triggering time in PER can't be less than max scan rate), it can be a
different value for each remote and different protocols
LINK ID and PATH ID
Note that these values doesn't matter at all because they are not read by any thing
(the automatically generated data sets use those names but if we change them the
OAG automatically rename them)

Training Session for OAG System Page 9 of 17

Prepared by Data Exchange Dept.
How to extract the history log file for certain application from database
Open the command prompt and type the following command:
"listmsg oaglog app=iccplink fam=oag output=anyname.log"
Note: the output file will contain the last 278 pages of the log from DB (whatever the date was), also
we can get the output in txt file and from any db and any application
The format is: "listmsg dbname app=application_name fam=family_name
output=logname.log" This will create a log file in the current folder containing the logs
for iccplink application
Note: in the log view in GUI browser we can go to a specific page by writing "page 245" (max of 278
pages) in the upper box and click ENTER, also we can search for a specific data item name by writing
"find di=EXACT_VALUE" and press Find DI or ENTER

Creation and naming of output data sets
It is important to understand that ICCP does not create output data set
For ex: NECC (remote) will send data sets and WDRCC (local) will receive data sets
- Before any communications is done with the remote the WDRCC will configure txt
import file or GUI to define the required (input) data sets (output for NECC)
Note: define means naming and triggering method and all other parameters
- After association is done WDRCC will send a request containing the pre-created data
sets to be sent from NECC at this moment they will be defined as output data set at
NECC
Training Session for OAG System Page 10 of 17

Prepared by Data Exchange Dept.
Directory of all savecases
The directory that contains all savecases that we have is located in:
E:\AREVA\habdata66\savecases
Note: for ISD and ICCP savecases are valid for both servers because the read of addressing (which is
the only thing that is changing between both servers) is read from OSILL2 file
How to upload a savecase to runtime
1- first make sure that you updated this savecase to the last changes you made
(right click on this savecase and click update)
2- stop all link application used by OAG (OAGSERVE, ISDLINK, ICCPLINK,
WSCC LINK)

3- from oag runtime >> oagserve master write the name of the save case you want
to upload in the upper text input box the press the bottom of screen click retrieve
oag model savecase
4- start OAGSERVE process then the rest of the processes
Training Session for OAG System Page 11 of 17

Prepared by Data Exchange Dept.
Configuration Control
From OAG choose HABITAT Applications >> Configuration Control >> CFGCTRL
Master to have the Analyst Displays menu appears then from it choose CFGCTRL
Model Definition >> CFGCTRL Definitaion

In this display we can change a lot of useful settings

Like for which disk space usage to make warning and failure and etc, it is also used to
register a device or path
Permit to be continued
We have 2 menus concerning with the permit
1- HABITAT Applications >> Permit
2- Permit Server Displays
Training Session for OAG System Page 12 of 17

Prepared by Data Exchange Dept.

Note: the menu Permit Server Displays contains all options in Habitat Applications >> Permit
NETIO to be continued
The ISD is an AREVA internal protocol and NETIO enables is to communicate with
different systems
NETIO has 2 applications: NETIO NIOCLERK and NETIO NIOSERVE as it defines 2
main roles: SERVER and CLERK
Data Semantics Conversions

We have 3 types of conversions:
1- STSMAP: Define representations of status, and conversions to alternate
representations
2- FLOWDIR: Conversions between different meanings of the sign bit on analog
values
Training Session for OAG System Page 13 of 17

Prepared by Data Exchange Dept.
3- SCALING: Conversions between different units of value
We also can make this applies to all Statuses or Reals or Integers of a certain remote
or we can make this for a specific data item
OAG Modeling >> Data Items >> Source then choose insert conversions for any DI we
choose

Then insert the index of the conversion record that we want to apply to this data item
HABITAT shortcuts to be continued
Here we will define some shortcut to use for OAG
CONTROLS
To have control criteria over data items we have to do the following:
- First we will need to create a DI of control type for the remote I want to control its
data items and another DI for my local site and model them both at my site
(define them as CTRLMSG) in OAG Modeling >> Data Items >> Type and also
choose the size in characters 20

Training Session for OAG System Page 14 of 17

Prepared by Data Exchange Dept.
Note: The Control DIs must be contained in datasets so we have to create 2 datasets for Input
and output at the local site and 2 datasets for Input and output at the remote site
- Then select which remote I want if for in OAG Modeling >> Data Items >>
Source

Now we will do the following steps for each DI I want to control
- Choose which DI you want to control
- Then insert a DI NAME for it if it has a different name in the EMS (i.e. Name for
ISD)
- Then in OAG Modeling >> Data Items >> Source choose to Insert Device for
this data item (we must create a device in remote with the same name) we have
different parameters for each type of DIs :
o STATUS: it will have CTRL0, CTRL1, ISD Site and Class

ICCP Name: ICCP Device name, it is an MMS identifier
ICCP SCOPE: Toggle button (VMD/DOM), it only applies to ICCP
ICCP protocol allows devices to be created with either "VMD
scope" or "Domain scope". When a device is created with
Training Session for OAG System Page 15 of 17

Prepared by Data Exchange Dept.
"Domain scope" then the number of MMS Named Variables
created for that device is equal to the number of remotes with
access to that device. Unauthorized requests for that device are
refused immediately by MMS. When a device is created with
"VMD scope", then only one MMS Named Variable is created for
that device, regardless of the number of remotes with access.
Unauthorized requests for that device are not refused until
ICCPLINK processes the request
Set a device's scope to "VMD scope" if more than one
remote has execute permission to it
Set its scope to "Domain scope" if only one remote has
execute permission to it.
CTRL0: define what 0 means (CLOSE or OPEN)
CTRL1: define what 1 means (CLOSE or OPEN)
Note: This ISD Name CTRL definition must be the same as the EMS in the local site
Remote Local
CTRLDI1 (input) >>>>>> CTRLDI1 (output)
CTRLDI2 (output) >>>>>> CTRLDI2 (input)
2 DIs contained in 4 DSs
ISD Site: any name it wont make a different
Class: select DO or SBO
o ANALOG: unlike status it will have a setpoint NAME instead of CTRLs
Training Session for OAG System Page 16 of 17

Prepared by Data Exchange Dept.
Twin: This option is only done for control data sets
To obtain it go to OAG Modeling >> Data Sets (Definition) >> Then click on
the triple arrow icon


Now in that field we have to insert for each data set the index of the one that
is opposite to it in the other remote
For example:
If we have 4 Data sets:
For WD: CTRL_IN (index 4) & CTRL_OUT (index 5)
For NECC: CTRL_IN_NECC (index 9) & CTRL_OUT_NECC (index 10)
The configuration for the twin field will be as the following:
Twin for CTRL_IN (index 4): 10 (IN for WD is OUT for NECC)
Twin for CTRL_OUT (index 5): 9 (OUT for WD is IN for NECC)
Twin for CTRL_IN_NECC (index 9): 5 (IN for NECC is OUT for WD)
Twin for CTRL_IN_NECC (index 10): 4 (OUT for NECC is IN for WD)

Training Session for OAG System Page 17 of 17

Prepared by Data Exchange Dept.
IMPORTANT NOTES
1- For the troubleshooting log we have to start from bottom alarms going to top
because bottom alarms may be responsible for the upcoming ones
2- Under the working path for ICCP (Status of topology) there is a Query button

The Query button on the path record allows the user to request the list of data
items available at a remote site
3- The osill2d.exe is a process in task manager for the MMS EASE it must be
started so that the system works
To start it again if not started from Start Menu >> Programs >> SISCO >> OSi
Stack >> Sisco Osi stack
4- We can find all the habitat logs (.out and .err) aka stdout files in this path:
E:\AREVA\habdata66\log
5- For data items permissions we cant have both write & execute permissions
together because write is only for the owner remote and execute is only for the
other remote