Good Practices

> L3_33_Good_Practices_A_01

1.1) Introduction
What is a Good Practices ?
What is NOT Good Practices ?

> L3_33_Good_Practices_A_01

1.2) Introduction
What is a Good Practices ?

GOOD PRACTICE IS A

METHOD
TO SOLVE ONE
SPECIAL PROBLEM

If there is no problem

no Cooking Recipe
no Good Practice

Question

What are our Business Problems ?

> L3_33_Good_Practices_A_01

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 Severity

1.
2.
3.
4.
4

Blocking
Major
Minor

> L3_33_Good_Practices_A_01

=> define priority in Good Practice

4

2.2) Good Practice Problem (2)

Good Practice Violation :
=> Problem reappears
but can be

Non Applicable
Acceptable

for the business case

=> Problem Severity

Good Practice Application Ratio :
% of obligation of the method
100

Fully mandatory,

no derogation

70

Mandatory,

derogation has to be clearly accepted

50

Recommended

common for most of the cases

30

Optional

highly depending of business case

Obsolete GP,

still listed for previous reference

Not applicable

in business case

0
n.a.
5

> L3_33_Good_Practices_A_01

2.3) Good Practice Problem (3)

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

> L3_33_Good_Practices_A_01

Good Practices
On Design
On Configuration
On Installation

> L3_33_Good_Practices_A_01

3) GP1 Design / Engineering

A) Specific Functional Specification
Policies

SCE Usage, starting DB

Graph Tables (Color, Font, Stroke, Bitmaps)

Archives / Logging / Alarm
Naming 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

B) Data List
Policies

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

SWR

SCS mapping (+empty), LBUS, TBUS

Module / IED definition
8

> L3_33_Good_Practices_A_01

4.1) GP2 Configuration (1)

Classification of Configuration GP
A) Naming
B) Data Base
C) Profiles / Archive
D) Electric
E) Scs
F) Graphic

> L3_33_Good_Practices_A_01

4.1) GP2 Configuration (1)

A) Naming
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

B) Data Base

10

Version

comment and reference documents

Check

no errors no warning (incremental)

> L3_33_Good_Practices_A_01

10

4.2) GP2 Configuration (2)

C) Profiles / Archive
General

(logging Alarm Klaxon)

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 optimization

System profiles DIAG

Klaxon

11

> L3_33_Good_Practices_A_01

one only with SPC DE Permanente

11

4.3) GP2 Configuration (3)

D) Electric
Bay/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

acquisition 20%

AI

Synchrocheck

Manual with default profile on

(look in training)

PSL

no loop, 3 blocks,
SPS output (arch) + Control on State change

12

Isagraf

no relation Manage, In/out rule

Uniqueness

order running archived

> L3_33_Good_Practices_A_01

12

4.4) GP2 Configuration (4)

E) Scs
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,

TBUS

SBO > 10s

always setting group

F) Graphic
User rights

no administration, no use of All

Win/mimic

no resize

ActiveX

sorting, no auto-refresh, printer

Real time preconfigured

Use GIF
13

> L3_33_Good_Practices_A_01

13

5) GP3 Install
A) Commissioning Forms
PACiS devices C264 upgrade, OI
External devices

B) PC
Directories manual, tools, sharing
saving installation

reg, dat,

DCOM config
Remote OI

VNC or equivalent

C) Ethernet
cable/wiring

optical, RJ45 SWR contacts

SWx

jumpers, form, incremental test

D) Extern devices
C264

printer, modem

Hopf

extern synchro, redundancy

RuggedCom
14

> L3_33_Good_Practices_A_01

14

6) Conclusion
Good Practice
Addressed to special problem
Application Ratio

Process on GP
Created when facing problem
Evolution with product and business
ongoing listing of the practices (tool)

COE
Specification DCSR audit
Data Base audit
Manufacturing audit
Site audit

15

> L3_33_Good_Practices_A_01

15