DFA Codifications Rules OML 100 Project RevAA

7/21/2019 DFA Codifications Rules OML 100 Project RevAA

http://slidepdf.com/reader/full/dfa-codifications-rules-oml-100-project-revaa 1/12

DFA codifications rules OML 100 project revAA.docThis document is the property of TOTAL and shall not be disclosed to third parties or reproduced without permission of the COMPANY.

NIGERIA – OML 100

FCW Implementation on OML 100 ICSS

COMPANY ref: XXXXXXXX Revision: AA Status: Class: date: 05/10/2007 page: 1/12

CONTRACTOR ref: ??? -- -- -- -- --

No comments code 0

Approved code 1

Approved with minor comments code 2

Rejected code 3

Reviewed with comments code 4

date:

ASB final acceptance code 5

date:

The document is:

Reserved to COMPANY

Remarks:

AA 05/10/2007 Issue for comments B. THEVENET M. MEDIONI

REV DATE DESIGNATION Initiator Reviewed by Approved by

FCW Implementation on OML 100

DETAILED FUNCTIONAL ANALYSIS

CODIFICATIONS RULES




NIGERIA – OML 100



CONTRACTOR ref: ??? -- -- -- -- --

TABLE OF CONTENTS

1 GENERALITIES.....................................................................................................................................................................3

1.1 DOCUMENT PURPOSE ......................................................................................................................................... 3

2 CODIFICATION.....................................................................................................................................................................4

2.1 SEQUENCE / GRAPH SYMBOL CODIFICATION ......................................................................................................... 4

2.2 DATA CODIFICATION............................................................................................................................................5

2.3 SEQUENCE EXAMPLE ..........................................................................................................................................9

2.4 TIMERS MANAGEMENT ...................................................................................................................................... 11

2.5 LOGICS CODIFICATION....................................................................................................................................... 12




NIGERIA – OML 100



CONTRACTOR ref: ??? -- -- -- -- --

1 Generalities

1.1 Document purpose

The present document aims at establishing and gathering a general set of rules and conventions for the data andsequence symbols codification that are used to write OML 100 DFA.

Particularly, it provides the rules that are applied for timers’ management description.




NIGERIA – OML 100



CONTRACTOR ref: ??? -- -- -- -- --

101

100

2 Codification

2.1 Sequence / graph symbol codification

Symbol Function

^ Positive edge transition (Boolean expression true only once )

> One shoot action

Continuous action

Escape upon event

Initial step

Standard step

Sub sequence

S = (a > b)

higher than

S = (a < b)

lower than

S = (a - b)

Subtraction

= Test

:= Affectation

Not visible step on partial sequence view

Go to step (coming from a not visible step)

Go to step

Fromsteps > 1

a

- bs

a

< b

s

a

> bs

Step name

Step




NIGERIA – OML 100



CONTRACTOR ref: ??? -- -- -- -- --

2.2 Data codification

Data are codified according to the nomenclature: prefix.data_name.suffix

A non exhaustive list of the prefix and suffix is given on following pages.

Example Description

cv.PWV.Commandcv is the prefixPWV is the data name

Command is the suffix

For the exchanges inter FCW modules, the following nomenclature is also applied:

prefix[complementary data].data_name

Example Description

mcm[Well A].Start-up^The Multiwell Control Module (MCM) sends a START-UP order to the well A.

This order is a pulse one.

mcm[All Wells].PauseOrderThe Multiwell Control Module (MCM) sends a PAUSE order to all wells.

This order is a bistable one.




NIGERIA – OML 100



CONTRACTOR ref: ??? -- -- -- -- --

2.2.1 Prefix list

Prefix Description

Standard Functions

ai Analog Input

cv Control Valves

siv Shut In Valves

pid Proportional, Integral, Derivative (PID)

ICSS systems

pcs Process Control System

sss Safety Shutdown System

FCW control modules

mcm Multiwell Control Module

mfcm Multi-Field Control Module

wcm Well Control Module

Supervised data from the HMI

cmd Operator’s commands

par Parameters

set Individual settings

sta Status

war Warning & alarms

Local data

int Internal data




NIGERIA – OML 100



CONTRACTOR ref: ??? -- -- -- -- --

2.2.2 Suffix list

Suffix Description

Analog input

Value Concerned transmitter value

Validity

Concerned transmitter is valid

Explicit = YES / NO

InhibitionConcerned transmitter has been inhibited by maintenance

Explicit = YES / NO

Control valves

ModeConcerned valve control mode

Explicit = FREE / PILOTED

CommandConcerned valve command

Explicit = OPEN, CLOSE for TOR valves (0-100% for analog valve)

StatusConcerned valve status

Explicit = OPENED, CLOSED, FAILED

Controller PID

Value PID controlled value

SetPoint PID controlled remote set point

ModePID control Mode

Explicit = CASCADE, FORCED OUTPUT, AUTOMATIC, MANUAL

OutputPid Output

Explicit = 0 – 100%

ValidityPid is valid

Explicit = “YES” or “NO”

InhibitionPid has been inhibited

Explicit = “YES” or “NO”




NIGERIA – OML 100



CONTRACTOR ref: ??? -- -- -- -- --

Shut In Valves

ModeConcerned valve control mode

Explicit = FREE / PILOTED

CommandConcerned valve command

Explicit = OPEN, CLOSE

StatusConcerned valve status

Explicit = OPENED, CLOSED, FAILED

Safety bars (either pcs or pss)

StatusConcerned safety bar status

Explicit = TRIPPED / NORMAL




NIGERIA – OML 100



CONTRACTOR ref: ??? -- -- -- -- --

2.3 Sequence example

2.3.1 Sequence

2.3.2 Actions in steps

Actions in steps are always described on a dedicated table, as follows:

The aim of this table is to permit to save space for sequence drawing, i.e. to win in readability.

Step Display Action in step

100 BEGIN -

101 OPEN ICV to target> cv.ICV.Mode := Piloted

cv.ICV.command := set.ICV_Target

102 GL INJECTION GL injection sub sequence activation

103 END -

cv.ICV.command = set.ICV_Target

101

cmd.START^

STEP NAME

100

102

103

OPEN ICV to target

BEGIN

END

STEPNB

End of sub sequence

Operator pulsed command

Initial step

Standard step

Macro stepGL INJECTION




NIGERIA – OML 100



CONTRACTOR ref: ??? -- -- -- -- --

2.3.3 Explanations

- Transition from step 100 to 101:

- Transition from step 101 to 102:

- Actions in step 101:

cmd.START^

Operator Command Command function Pulsed action

cv.ICV.Command = set.ICV_Target

test

> cv.ICV.Mode := Piloted

One shoot action Affectation

cv.ICV.command := set.ICV_Target

Continuous action Affectation




NIGERIA – OML 100



CONTRACTOR ref: ??? -- -- -- -- --

2.4 Timers management

Timers are used as count down chronometers. A timer elapsed may be a condition for a sequence to pursuit.

Actions on timers

A timer can be loaded (given a time value), stopped (to stop its count down), restarted (when it has been stopped),tested if elapsed (test if it’s time value is equal to 0).

Functions:

The above actions are performed by the following code functions:

- Load: It loads the timer to a defined time value given in seconds and initiates the countdown.

Example Description

load int.GETimer with (10 sec.) The int.GETimer is set to 10 seconds countdown

- Elapsed: It is a boolean function. True once the timer countdown is elapsed (it value reach 0 seconds).

Example Description

int.GETimer = 0 The int.GETimer is elapsed

- Stop: It stops the timer countdown to its present countdown value.

Example Description

stop int.GETimer The int.GETimer countdown is stopped

- Start: It starts the timer countdown from its present countdown value.

Example Description

start int.GETimer The int.GETimer countdown is restarted




NIGERIA – OML 100



CONTRACTOR ref: ??? -- -- -- -- --

2.5 Logics codification

The commands / instructions (If, for, do, repeat, until, while…) are written in bold.

The use of tabulations permits to clearly identify the conditions to test and the actions to perform.

Example:

If condition A = TRUE

& condition B = FALSE

OR (condition C = TRUE & condition D = TRUE)

Then action 1

Else If condition E = FALSE

Then action 2

Else action 3

End If

End If

Documents

DFA Codifications Rules OML 100 Project RevAA