YANN L3 03 GoodPractices a 01

8/20/2019 YANN L3 03 GoodPractices a 01

1/16

> L3_33_Good_Practices_A_011 1

Good Practices


2/16

> L3_33_Good_Practices_A_01 2 2

1.1) Introduction

What is a Good Practices ?

What is NOT Good Practices ?


3/16


1.2) Introduction

What is a Good Practices ?

GOOD PRACTICE IS A METHOD

TO SOLVE ONESPECIAL PROBLEM

If there is no problem no Cooking Recipeno Good Practice

Question What are our Business Problems ?


4/16


2.1) Good Practice Problem (1)

A) Business Technical Problems by Stages

1. Design / Engineering

2. Configuration / Installation

3. Validation

4. Commissioning / Maintenance

⇒ Good Practices can be defined in any of these 4 Technical Stages(Nowadays Mainly Configuration / Installation)

B) Business Problem Severity1. Blocking

2. Major

3. Minor

4. … => define priority in Good Practice


5/16



Good Practice Violation :

=> Problem reappears

but can be Non ApplicableAcceptable for the business case

=> Problem Severity…

Good Practice Application Ratio :

% of obligation of the method

Not applicable in business casen.a.

Obsolete GP, still listed for previous reference0

Optional highly depending of business case30

Recommended common for most of the cases50

Mandatory, derogation has to be clearly accepted70

Fully mandatory, no derogation100


6/16



Good Practice Life Cycle:

Appears with specific trouble (when solved)

Depends of PACiS System (FR, evolution, business case)Evolutes/dies with new methods

Good Practice is World Wide Capitalize experience

Save time in “common/tricky errors”

Anybody can/should propose new practices Everybody must explain violation


7/16


Good Practices

On Design On Configuration

On Installation


8/16


3) GP1 Design / Engineering

A) Specific Functional Specification SCE Usage, starting DB

B) Data List

Policies Graph Tables (Color, Font, Stroke, Bitmaps)

Archives / Logging / AlarmNaming DP and states labels

Graphics SCE C264 LHMI

System Map Mimic (ordered, names, IP, LBUS..)

Help mimic (module/equipment animations)

Automation FBD ILK and PSL outlined with FBD editor

Isagraf outline

Policies Wiring (DI, DI/DO, AIU, TMU), SWR

SCS mapping (+empty), LBUS, TBUS

Module / IED definition


9/16


4.1) GP2 Configuration (1)

Classification of Configuration GP

A) Naming

B) Data Base

C) Profiles / Archive

D) Electric

E) Scs

F) Graphic


10/16



A) Naming

B) Data Base

DB

Graph Tables (Color, Font, Stroke, Bitmaps)

Profiles

SCS SBUS, Boards, LBUS, TBUS, IED

Graphics mimics, Groups, multistate

Electric Bays, module (ANSI)..

Automations UserFunction, input/output

Version comment and reference documents

Check no errors no warning (incremental)


11/16



C) Profiles / Archive (logging Alarm Klaxon)General Scs/Graphic, OI Server

MV transmission

Profile Split Electric/Scs

No toggling/FSS/log

Boolean (same for all, DPS motion, FSS)

logging => archive, archive one state => all states…

alarm is archived, audible if set…

NO alarm / logging unknown

for FAT C264=OI, all DP on State panel

for SAT optimizationSystem profiles DIAG

Klaxon one only with SPC DE Permanente…


12/16



D) ElectricBay/Module Typed object (link ANSI, IEC..)

GroupSPS Forbidden (because of limitations)

DP Typed, initial reset/open, no toggling/FSS/SBMC

xPC Permanents, Permanents until FB (xPS/xPC), arch

xPS/xPC no wiring/profile inversion

MV AI acquisition 20%

Synchrocheck Manual with default profile on

… (look in training)

PSL no loop, 3 blocks,

SPS output (arch) + Control on State change

Isagraf no relation Manage, In/out ruleUniqueness order running archived


13/16



E) Scs

F) Graphic

C264 toggling/transmission/acquisition

Systrap policy

LBUS 2,2,50, synchronization 1mn

Port only software management

T103 Acq GI period 20mn, same setting group param

Disturbance channel order

IED Disturbance file name, always setting group

TBUS SBO > 10s…

User rights no administration, no use of AllWin/mimic no resize…

ActiveX sorting, no auto-refresh, printer

Real time preconfigured

Use GIF


14/16


5) GP3 Install

A) Commissioning Forms

B) PC

C) Ethernet

D) Extern devices

Directories manual, tools, sharingsaving installation reg, dat, …

DCOM config

Remote OI VNC or equivalent

cable/wiring optical, RJ45… SWR contacts…

SWx jumpers, form, incremental test

C264 printer, modem

Hopf extern synchro, redundancy

RuggedCom …

PACiS devices C264 upgrade, OI

External devices


15/16


6) Conclusion

Good Practice Addressed to special problem Application Ratio

Process on GPCreated when facing problemEvolution with product and business

ongoing listing of the practices (tool)

COESpecification DCSR auditData Base audit

Manufacturing auditSite audit


16/16

YANN L3 03 GoodPractices a 01

Documents