Ce document proprit d ALSTOM ne doit pas tre utilis, copi ou communiqu des tiers sans son autorisation

This document is the exclusive property of ALSTOM and shall not be used, copied or communicated to third parties without their prior authorization

P320 System
Site Anomaly Management Procedure

DIFFUSION :

CONFIDENTIELLE o

RESTREINTE o

CONTROLEE o

LIBRE x

ACCESSIBILITY

CONFIDENTIAL

RESTRICTED

CONTROLLED

FREE

DATE

NOM

24/07/02

NAME

ETABLI
ESTABLISHED

VERIFIE

CHECKED

APPROUVE
APPROVED

SIGNATURE

B.DURAND
M.MATHYS

Power

Electrical and Control Systems

D.CANTERO

PA 400 D

REV

P T P 0 9 A 4 2 6 0 3 - E C
4 -

STAT.

F/F FIN

Nb F

SH/SH END N of SH

A 4

GFE

1/11

TABLE DES MODIFICATIONS / MODIFICATIONS TABLE

ETABLI

VERIFIE

APPROUVE

ESTABLISHED

CHECKED

APPROVED

J.RAYMOND

P.CHERDO

D.CANTERO

29/06/00

First version

GFE

B.DURAND

M.MATHYS

D.CANTERO

24/07/02

Update, site operation

GFE

PA 401 C

REV

P320 System
Site Anomaly Management Procedure

DATE

MODIFICATIONS

STAT.

PTP09A42603-EC.2/11

Table of Contents
1.

INTRODUCTION

1.1.

PURPOSE OF THIS DOCUMENT

1.2.

USERS

1.3.

CONVENTIONS & DEFINITIONS

1.4.

QUESTIONS & SUGGESTIONS

2.

SITE ANOMALY PROCESSING CYCLE

3.

ANOMALY REPORT FORM

4.

EXPLANATIONS FOR ESTABLISHING AN ANOMALY REPORT

4.1.

ISSUED BOX

4.2.

ANOMALY DESCRIPTION BOX

P320 System
Site Anomaly Management Procedure

11

PTP09A42603-EC.3/11

1.

Introduction

1.1.

PURPOSE OF THIS DOCUMENT

This document presents the management of anomalies for the P320 system. It specifies
the different anomaly processing stages, presents an anomaly report and gives a
description of the different parts of this form to be filled in.

1.2.

USERS
This document is intended for all P320 system users, particularly after the installation on
site.

1.3.

CONVENTIONS & DEFINITIONS

In this document:

1.4.

P320 user can designate a customer in a general manner, an operator, etc.

Software configuration manager :

ALSTOM side : designates the person who records the anomalies and manages
their status,

P320 user side: designates the person who ensures the interface with CS-C1
SMS and assigns each discovered anomaly its proper number.

QUESTIONS & SUGGESTIONS

If you have any questions or suggestions with regard to this document, please contact:
ALSTOM Power
CS C1 SMS
9 rue Ampre
91345 MASSY cedex FRANCE
FAX : +33 (0)1.60. 13. 41. 28

P320 System
Site Anomaly Management Procedure

PTP09A42603-EC.4/11

2.

Site Anomaly Processing Cycle

On the ALSTOM side, the CS-C1/SMS structure is both destination for and transmitter of
the documents exchanged between P320 users and ALSTOM for anomaly processing.
Anomaly processing follows the stages below (see Figure 1) :

the P320 user discovers an anomaly : he transmits the information to CS-C1,

preferably using an Anomaly Report form (see Chapter 3),

CS-C1 records the anomaly report and begins anomaly processing by calling up the
competent services,

the anomaly report is processed by CS-T1/T3 (or other concerned departments). It

will materialize by a new version or a new revision of the P320 system described in a
version sheet or a Service Pack,

Remark :

generally speaking, a new P320 system version or revision does

not correct only one single anomaly, but for reasons of efficiency,
groups together the correction of several anomalies.

A P320 system new version is announced in a shipment availability message sent by

CS-T2 to CS-C1 project managers

Remark :

the shipment availability details the cases where a new version

has to be installed. With this information, the project manager can
decide to install this version.

When the project manager has accepted it, CS-C1 transmits the new version or
revision and the associated version sheet to the P320 user. This version sheet gives
a summary listing of the anomaly reports which have been corrected in the new
version, and those which have not yet been corrected.

CS-C1 has to check with the P320 user that the new system version has been
installed on site. This return is the final approval of the anomaly (or anomalies)
correction.

P320 System
Site Anomaly Management Procedure

PTP09A42603-EC.5/11

P320 user
on site

Anomaly report

CS-C1/SMS

AR
AR recorded

CS-T1/T3
AR processed
Shipment availability
(sent by CS-T2)

Consultation
Project manager

P320 User
(on site)

CS-C1/SMS
Decision

New version/revision
delivered

Test of corrections
(when applicable)
New system version/revision
implementation

New version/revision
installation

Figure 1 : Anomaly Processing Cycle

P320 System
Site Anomaly Management Procedure

PTP09A42603-EC.6/11

3.

Anomaly Report Form

P320 System
Site Anomaly Management Procedure

PTP09A42603-EC.7/11

4.

Explanations for Establishing an Anomaly

Report

Only those parts of the form which are to be completed by the Centralog user are
mentioned here.
Remark:

4.1.

The anomaly report must be filled in using a ballpoint pen.

ISSUED BOX
Raised by:
Specify the authors name.
Date:
Specify the report date.
Address + Tel. :
Indicate the complete address and telephone number of the author or of the person to
contact if need be.
Software configuration managers signature:
Signature of the person who ensures the interface with CS-C1 and assigns each anomaly
its own proper number (see Project AR N. box).
Project / Site :
Specify site and project name.
Unit:
Indicate which site unit is concerned.
Project AR N.:
Indicate the number assigned to this AR as per Centralog user numbering.
The following is the recommended numbering: YEPRO-xxx
YE = year, example: 93,
PRO = three letter abbreviation of project name, or project code,
xxx = order number from 001 to 999.
Environment:
Specify the date and time of the anomaly appearance.
Context:
Indicate whether the anomaly appeared in normal operation, during hardware installation,
during testing, during a maintenance operation or during the installation of a new version.

P320 System
Site Anomaly Management Procedure

PTP09A42603-EC.9/11

Importance:
Specify whether the anomaly is:
. blocking (example: system shutdown),
. major (example: unsatisfactory operation),
. minor (example: documentation)
Anomaly reproduced:
Indicate whether or not the anomaly is reproducible, or if it is sporadic. In this case,
specify the frequency (example: once a day). For an anomaly which has only occurred
once, tick only the box marked No.
Presumed cause:
The presumed cause of the anomaly can be the following:

Software : in this case, specify the version (refer to the version sheet); in the case of
a tool, indicate its name and its version,

Application : in this case, specify the version of the part of the application in cause
(data base, views, application controllers),

Hardware: in this case, indicate the type of module in cause (example: MVME 147), if
possible its manufacturers serial number and its revision. If this module has PROM
or integrated software, specify their identification and version.

Operating system : (example : SunOS 4.1.3)

Documentation: in this case, specify the document number, its version and the pages
or chapters concerned, in the anomaly description.

P320 System
Site Anomaly Management Procedure

PTP09A42603-EC.10/11

4.2.

ANOMALY DESCRIPTION BOX

Anomaly description:
Indicate the following:

the system operation phase, for example: startup, shutdown, stable running regime,
surge peak, etc.

the concerned physical block : the rack, the station number

the views displayed on the CVS at the moment of the anomaly

the signalization message(s) displayed on the CCC at the moment of the anomaly

the operations performed by the operator immediately before the anomaly occurred:
views call up, remote control, logs editing, sequence monitoring, etc. The
phenomenon is to be described as faithfully as possible in being careful to respect
the chronological order of the events.

If surmountable, provisionary solution:

Describe the solutions implemented to prevent the anomaly from reproducing if this is the
case (for example: no more calling up of view XXX).
Documents attached:
Indicate all attached documents: printer listing, screen copy, trace of messages.
Remark:
n.

As many pages as necessary are to be used, in numbering them from 1 to

P320 System
Site Anomaly Management Procedure

PTP09A42603-EC.11/11