Escolar Documentos
Profissional Documentos
Cultura Documentos
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
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
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
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.
1.2.
USERS
1.3.
1.4.
2.
3.
4.
4.1.
ISSUED BOX
4.2.
P320 System
Site Anomaly Management Procedure
11
PTP09A42603-EC.3/11
1.
Introduction
1.1.
1.2.
USERS
This document is intended for all P320 system users, particularly after the installation on
site.
1.3.
1.4.
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.
P320 System
Site Anomaly Management Procedure
PTP09A42603-EC.4/11
2.
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) :
CS-C1 records the anomaly report and begins anomaly processing by calling up the
competent services,
Remark :
Remark :
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
P320 System
Site Anomaly Management Procedure
PTP09A42603-EC.6/11
3.
P320 System
Site Anomaly Management Procedure
PTP09A42603-EC.7/11
4.
Only those parts of the form which are to be completed by the Centralog user are
mentioned here.
Remark:
4.1.
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.
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.
the system operation phase, for example: startup, shutdown, stable running regime,
surge peak, etc.
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.
P320 System
Site Anomaly Management Procedure
PTP09A42603-EC.11/11