1. cl02_ccc

8/2/2019 1. cl02_ccc

http://slidepdf.com/reader/full/1-cl02ccc 1/29

Â Â

Â Â

Â

Â

CONTROBLOC

CENTRALOG

CL02TRAINING

8/2/2019 1. cl02_ccc


CENTRALOG TRAINING Cl02-A/08-98

Presentation of CCC function Folio 2

.

PRESENTATION OFCCC

FUNCTION

8/2/2019 1. cl02_ccc



Presentation of CCC function Sheet 1-i

.

Table of contents

1. INTRODUCTION FOLIO 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1. GENERAL DESCRIPTION FOLIO 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2. ABBREVIATIONS & NOTATION CONVENTIONS FOLIO 4. . . . . . . . . . . . . . . .

1.3. DESCRIPTION OF THE MAIN OPERATOR INTERFACE FOLIO 6. . . . . . . . .

2. UTILIZATION FOLIO 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1. LOGGING INTO THE CCC FOLIO 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.1. Logging out of the CCC Folio 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2. CONFIGURATION FOLIO 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2.1. Presentation Folio 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3. EXPLOITATION FOLIO 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.1. Starting and stopping the system Folio 14. . . . . . . . . . . . . . . . . . . . . . . . .

2.3.2. Installing a NEW VERSION Folio 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.4. MAINTENANCE FOLIO 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.1. General principles Folio 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.2. System views and variables Folio 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.3. System messages and the CCC function Folio 26. . . . . . . . . . . . . . . . . .

8/2/2019 1. cl02_ccc




.

1. Introduction

1.1. GENERAL DESCRIPTION

The CENTRALOG Configuration Center (CCC) is used for :

Configuration of the CENTRALOG system

Maintenance of the CENTRALOG system

Operation of the CENTRALOG system

Fig. 1 : Standard configuration of an Alspa 8000-P320 system Centralog

CVS

Â Â

CONTRONET

Dual S8000

CVS

CIS

Automation cells

8/2/2019 1. cl02_ccc




.

The CENTRALOG Configuration Center handles different sets of

functions that vary according to the context or phase :

D During the configuration phase :The CCC gives access to the CENTRALOG database andmimic configuration tools. These tools are used :

D to configure the database

D to configure the mimic views

D to change the database or mimic version

D to configure the PRISCA process application

D During the maintenance phase :The CCC gives access to system signaling messages.

D During the operational phase :

The CCC is used for administration of the CIS (start/stop,database loading) and the CVS (startup/stop, databaseand mimic loading, synchronization with the CIS).

8/2/2019 1. cl02_ccc




.

1.2. ABBREVIATIONS & NOTATION CONVENTIONS

The following conventions and abbreviations are employed in this

manual:

D DB : Database

D BVA : Application variable database

D BVI : Mimic variable database

D CCC : CENTRALOG Configuration Center

D CIS : CENTRALOG Interface Station

D CONTROCAD: Engineering tool used to writeproject controller programs and data

D CVS : CENTRALOG Video Station

D DAT : Digital Audio Tape

D DataViewsT: Set of tools developed to generatecomplex man/machine interfaceapplications.

8/2/2019 1. cl02_ccc




.

D Datasource : Source of DataViews dataor ds

D DV-Draw : Mimic configuration tool

D EXP : Operator station function in normaloperation (EXPloitation)

D

HDSR : Historical Data Storage andRetrieval

D MMI : Man-machine interface

D MICROETE : Database configuration tool

D MSNV : (Mise en Service d'une Nouvelle Versionde Logiciel) Installation of a new data baseor software version without stoppingthe system

D OU : Operative Unit : Unit of application dataformed by a coherent set of variablesfrom the standpoint of the process.

D OSF/MOTIFTor MOTIF: Window and library manager

D S8000 : Unit network (F900 profile) linking the

controllers with the Centralog

8/2/2019 1. cl02_ccc




.

1.3. Description of the Main Operator Interface

The operator interface of the CENTRALOG Configuration Center is

composed of a main view from which the different functions can beactivated.

Fig. 2 : Description of the operator interface

Access to configuration functions

Access to CCC

Signaling messagedisplay zone

Blocking messageindicator

Edit/consultsignaling messages

Access to operational functions

Site reference

Control roomview

ACCESS CONTROL

CEGELEC POWER PLANT

CENTRALOG

CONFIGURATION CENTER

Centralog Messages From: 5hs station: 1 Date 26/10/98 10:13:44:070

Card: 5hsb Process: Phti_tri Sender: rphts_acquisit

Lib: 01KITUS002 Printer 2 E: NORMA

EXPLOITATIONCONFIGURATION

!

System type

8/2/2019 1. cl02_ccc




.

2. Utilization

Presentation

This chapter describes the different functions accessible from the

CENTRALOG Configuration Center view.

CCC

Maintenance

Signalization

Data Base

HDSRMMIHDSR

MimicsÇ Ç Ç Ç

CVS

Configuration

Exploitation

8/2/2019 1. cl02_ccc




.

2.1. LOGGING INTO THE CCC

When no user is logged into the CCC or immediately after starting

the station the view below is displayed :

ACCESS CONTROL

CEGELEC POWER PLANT

CENTRALOG

CONFIGURATION CENTER

Centralog Messages From: 5hs station: 1 Date 26/10/98 10:13:44:070



EXPLOITATIONCONFIGURATION

Only the Login and Logout are sensitive to the mouse clicks.

Logging in

Click on the Login button.

Enter the user name and password.

Please enter login

Username: Raymond

Password: ******

8/2/2019 1. cl02_ccc




.

2.1.1. Logging out of the CCC

Logging out

Click on the Logout button.

The buttons are no more sensitive to the mouse clicks and

the CCC

displays a message confirming the log out associated with

a request for

acknowledgement :

User Raymond LOGGED OUT at Mon Nov 8 10:11:49 1998

Acknowledge

Confirm by clicking on the button.

8/2/2019 1. cl02_ccc




.

2.2. CONFIGURATION

2.2.1. Presentation

The subject of this chapter is database and mimic configuration. The

chapter describes the actions to be performed and the sequencing

required to preserve consistency between the CENTRALOG

database and mimics.

The CENTRALOG database

The CENTRALOG real time database is created in two phases :

Database configuration consisting in the creation of filesdescribing the database (OU files) and in managing thearchives of these files and those of the data input tool,

Database administration enabling the real time databaseto be managed from these OU descriptor files.

8/2/2019 1. cl02_ccc




.

CENTRALOG mimics

The mimic views are closely linked to the database by virtue of themimic animation requirement. The mimic database (BVI) is

constructed from the database descriptor files, known as the

application variable database (BVA), in two phases :

Mimic configuration grouping the operations necessaryfor the creation of a version of the mimics which are beingdeveloped,

Mimic administration consisting in the management of mimic view versions and the loading of these views on theoperator stations.

Each of these four phases is associated to a button in the

Configuration zone on the VDU screen.

8/2/2019 1. cl02_ccc




.

GenerateBVI

OU

Verify coherency

BVI

Selectversion

Updatea EXP

Errorfiles

Currentversion

Previousversion

Nextversion

Backup Mimic

RestoreMimic

Remove Views

Newversion

-----------DV-Draw

MICROETE

DISK

OU

GenerateDB

View OU

GetOU

Backupstatus

Backup DB

Microete

OU

BD

Status of version

MMI EXP

Ç Ç Ç Ç Ç

Centralog

nn-1

n+1

Select DB tobe loaded

MimicConfig.

Database Admin.

DatabaseConfig.

Mimic Admin.

Each of the actions above is accessible via a menu from the relevant

button

Restore DB

Menu option

Fig. 3 : Database and mimic management

8/2/2019 1. cl02_ccc




.

vue_be

bd

ccc_m base dos hdsr

/local

Host space

mod.attente mod.courant

Host space

Data

Microete

CCC/CVS directories

microete

c10 c30 c50

ctx (1 to 9)

dvt

ete

vp vc vs rep_bvi rep_bva

Design office views

Data generated

Host space

Operational views

Host space

ETAT.CCC

DVconfig rep_syn bib_ref cvs_ref

etat_base BCBA BR1 BR2 trace

dico_base xxxx.A xxxx.Byyyy.B zzzz.A zzzz.B

MF e MF b

dicoDonnées

Données

fic_vers

fic_vers

ccc

af

* depending on the installation

clg exe

dc ic oc sc dc ic oc sc

dc ic oc sc

vpm *

8/2/2019 1. cl02_ccc




.

2.3. EXPLOITATION

2.3.1. Starting and stopping the system

Normally, system start-up is global, ie. all of the stations on the

system (CIS and operator stations) are started. However it is also

possible to start a station individually, for example after a

maintenance operation.

2.3.1.1. Starting and stopping the CIS

The CIS is started and stopped by means of dialogue from the CCCfunction.

Starting the CIS alone (without restarting the operator stations)

causes the views that were visible on the operator station CRTs

before the CIS was stopped to be re-displayed.

As a Centralog 10 configuration includes only one station

(CIS/operator station), the operational mode is the same as the one

described below for the CIS.

8/2/2019 1. cl02_ccc




.

2.3.1.2. CIS Start-up Modes

Depending on the choice of the operator, the CIS is started with

either total orpartial re-initialization of data. This choice is selected

from the CCC "Stations Admin" menu:

ExploitationStop CCC

Stations Admin

MSNV

FacilitiesCentralog Admin.Miscella

In the event of start-up with total initialization, any modifications

made by the operator are canceled and historical records (curves

etc.) are erased.

In the event of start-up with partial initialization, this data is

conserved.

8/2/2019 1. cl02_ccc




.

t

process

CIS stopped

t

process

start-up with partial initialization

t

start-up with total initialization

process

Example of start-up in each modewith y=f(t) curve data :

duration of stoppage

8/2/2019 1. cl02_ccc




.

2.3.1.3. CIS start-up with Total Initialization

This type of start-up is used when the CENTRALOG system is put

into service for the first time or after changing the real-time database

(RTDB) version.

The start-up procedure involves:

D downloading the software,

D downloading the entire RTDB,

D the full initialization of all data.

The database is thus loaded from the CCC disk onto the CIS exactly

as it has been generated.

D The status of all the variables and Operative Units isre-initialized as ''on-monitoring",

D Assignment of the direct call keys is also re-initialized.

D etc.

Only files containing logs archived before the shut-down are

conserved.

8/2/2019 1. cl02_ccc




.

2.3.1.4. CIS start-up with Partial Initialization

The start-up procedure is similar to that described above. However

certain data produced before the CIS was stopped is conserved.

This type of start-up can only be used if the RTDB version has not

been changed since the CIS was stopped.

In this type of start-up, the RTDB cannot be wholly reloaded, and

certain data may not be re-initialized.

The following data stored on disk is recovered after a partialinitialization:

D operator modifications regarding the status of variables(setting on/off monitoring, replacement of value,inhibition) or their thresholds,

D operator modifications regarding the status of OperativeUnits,

D operator modifications regarding the status ofdisturbance groups (setting on/off monitoring),

D operator modifications regarding the status of SOEgroups (setting on/off monitoring),

D the value attributed by the operator to analysis variables(TMO),

8/2/2019 1. cl02_ccc




.

D operator actions on the composition of variable groups(curve groups, operator groups).

D historical curve groups records,

D historical records of the shift, daily and monthly logs (inparticular the monthly log counters) at hourly intervals,

D

hourly values of long term TMIs, (these variables aresaved every hour),

D files containing archived logs,

D assignment of the direct call keys.

D table of values of schedules and associated curves

The shift, daily, weekly and monthly maintenance logs

corresponding to the period prior to shut-down are closed and

archived when the system restarts (if they have been declared as

archivable during configuration). They can therefore be printed out

on request by the operator. The subsequent printout of the shift, dailyand weekly logs will contain data recorded from the time the system

was restarted.

8/2/2019 1. cl02_ccc




.

2.3.1.5. Stopping the CIS

The CIS is stopped from the CCC "Stations Admin" menu:

ExploitationStop CCC

Stations Admin

MSNV

FacilitiesCentralog Admin.

Miscella

8/2/2019 1. cl02_ccc




.

2.3.2. Installing a NEW VERSION

CENTRALOG 30 or 50 with a dual CIS configuration offers the

possibility of changing the software or the database version withoutstopping the operation.

With one CENTRALOG version in normal operation, the procedure

for installing the new version (MSNV) is performed in three steps (the

procedure is entirely controlled from the CCC) :

STEP 1 : SWITCH TO SHARED MODE

During the system configuration phase, the stations are divided into

two groups forming two separate architectures capable of

functioning independently of each other. Such a separation

obviously requires a redundant architecture.

When the new software or database version is available on the CCC,

one of the two groups is stopped. The new version is loaded onto thegroup which is stopped and the group is then restarted.

8/2/2019 1. cl02_ccc




.

STEP 2 : OPERATION IN SHARED MODE

É É É É É

É É É É É

É É É É É

É É É É É

É É É É É

É É É É É

É É É É É É É É É É É É







Dual CONTRONET

Dual F900

Stations operating with current version

Stations operating with test version

É É É É É É É







P320CONTROBLOC

CVS 1 CVS 3CVS 2

CIS

P320CONTROBLOC

CIS

Process operations proceed without interruption using the current

version on the group which has not been stopped.

Simultaneously, the new version is tested and validated on the other

group.

8/2/2019 1. cl02_ccc




.

STEP 3 : RETURN TO NORMAL MODE

The operator can return to normal mode in one of two ways,

depending on whether the new version is satisfactory or not:

D either the new version is extended to the whole

CENTRALOG system, in order to continue operation withthe new version (the CIS and operator stations on thegroup running the old version are stopped and restarted),

D the group running the new version return to the old version(the CIS and operator stations on the group running thenew version are stopped and restarted).

Return to normal mode is performed without interrupting

operation of the system.

8/2/2019 1. cl02_ccc




.

2.4. MAINTENANCE

2.4.1. General principles

Information relative to the state of the system is transmitted on two

levels ;

D to the operator stations in the control room, enabling theoperators to call in maintenance teams.

D to the CCC function, in order to assist the maintenancestaff in diagnosing the origin of the fault.

8/2/2019 1. cl02_ccc




.

2.4.2. System views and variables

The CENTRALOG system functions which monitor hardware and

software components automatically produce state changes in the

logical variables associated to faults.

These TSS logical variables (System Telesignals described in the

Volume "Data Description and Management") are processed like the

other logical variables and can therefore, depending on

customization, trigger alarms and/or be recorded in the various logs.

These variables are also used to animate a mimic view representing

the different components of the system and their respective states.

This view can be consulted on the operator stations in the same way

as the process supervision mimics (refer to the Volume "Supervision

Functions").

8/2/2019 1. cl02_ccc




.

2.4.3. System messages and the CCC function

Signaling messages are transmitted to the CCC function from the

CIS and the operator stations.

These signaling messages are of two types:

D information messages intended for the operators; thesemessages correspond to system messages and aredefined in the Volume "Operator Station"

D manufacturer's messages reserved exclusively forCEGELEC service personnel.

CCC

Transmissionof message

Circularstorage

file(1024 messages)

CIS

MESSAGESDISPLAYED

ON ARRIVAL

OFF-LINECONSULTATION &PRINT-OUT OF

MESSAGES

8/2/2019 1. cl02_ccc


Signaling messages are stored in order of arrival at the station

dedicated to the CCC function in a circular file, containing up to

1024 messages). Messages are displayed one-by-one on arrivalin one of the windows of the CCC.

Printer output and consultation functions (order of arrival display of

each message), enable messages received by the circular file to be

sorted chronologically or by criteria (filters).

These functions are implemented by interactive dialogue on the

CCC station:

Message consultation/print-outwindow

Order-of-arrival messagedisplay window

Blocking messageindicator

Centralog Messages

Printer Log

From: 5hs station: 1 Date 26/10/96 10:13:44:070



Consultation Sorting Disabled

Filters

Source

Time slice

Block :z Station : Card Name :

From : Until :

Date [DD/MM/YYYY] : 03/9/1996 Date [DD/MM/YYYY] : 03/9/1996

Hour [hh:mm] : Hour [hh:mm] :

Sender : Name : Process : Name :

Message Display

Stack Analysis

Done QuitPrev Next Message : 581 MaxMin

From : 5hs Station : 1 card : 5 hsb process : phti_tu

Date : 03/09/1996 13 : 37 : 28 : 930

Mode

Sender : rphts_acquisit

01KITUS064 WORKSTATION 1 BD2 ACCESS CONNECT E : IN_SV

1. cl02_ccc

Documents