21

Data integrity and consistency

Embed Size (px)

Citation preview

Page 1: Data integrity and consistency
Page 2: Data integrity and consistency

Data integrity and consistencyData Flow

Presented by Marek Jadczyk

The Woodlands Resort & Conference Center, Woodlands TX

Page 3: Data integrity and consistency

Page 3

1. Introduced data management concept.

2. Streamlines data flow.

3. Enforced data preparedness.

4. Removed chaos from data exchange.

5. Enforced data standardization.

6. Breaks old habits (at the price).

Aveva impact on the business

Page 4: Data integrity and consistency

In today’s project environment two ingredients are vital to its

success – keeping with the budget and keeping with schedule. With

the fierce competition on the labor market, company that can

provide both is a sure winner. Among number of other skills, proper

organization and handling of the large amount of data flooding

everyone involved is a paramount. One of the tools provided to deal

with this challenge is data storage software known otherwise as

database.

However, if it is not used properly it will only add to the chaos.

Page 4

Page 5: Data integrity and consistency

Page 5

Introduction“One Person’s data is another person’s noise” - unknown

Page 6: Data integrity and consistency

Page 6

1. Project design stages are all about data and information.

IntroductionNeed of data

2. Controls, Instrumentation, Electrical in design stages are offering nothing more than data

in different formats.

3. Drawings, Excel files, PDF articles, Word documents, JPG Pictures. How do we manage following:

a) Data change?

b) Data addition/deletion?

c) Data check?

4. Who is responsible for data maintenance or data flow?

Page 7: Data integrity and consistency

Page 7

TAG# Description Instrument

Service

P&ID Location

30-XV-0002 Valve User defined valve

30-HV-0010 Valve Hand ValveInlet Separator Isolation Valve

Inlet Separator Inflow Valve

Cost associated with description errors – 1 contractor for 120 hours @

$115/hr.

CDN$ 13,800

Expertise level

Page 8: Data integrity and consistency

Page 8

1. Basic data configuration

Database

a) Plant areas

b) Process units

c) Pick lists

d) Tag format

e) Type catalogue

f) Instrumentation datasheets

VINS

Setup

Physical devices vs virtual soft points

Page 9: Data integrity and consistency

Page 9

Level Control Valve

I/P Converter

INS Instrument LV Control Valve FLD

INS Instrument LVControl Valve

(with I/P)AO FLD I/P To JB

INS Instrument LY I/P Converter AO FLD I/P To JB

Incorrect data input

Page 10: Data integrity and consistency

Page 10

Another Example of Ambiguity

Class NameClass

DescriptionFunction Description

I/O

TypeLocation Wiring Rule

Operating

PrincipleSystem

INS Instrument AE Analyzer Sensor FLD PLC

INS Instrument AECO2 Analyzer

ElementFLD Analysis

INS Instrument AI Indicator DCS PLC

VINSVirtual

InstrumentAI Indicator n/a DCS none Analysis

INS Instrument PV Control Valve FLD

INS Instrument PVControl Valve (with

I/P)AO FLD I/P To JB

INS Instrument PY I/P Converter AO FLD I/P To JB

Results in:

a) Associated cost

b) Incorrect I/O assessment

c) Data transfer confusion

Page 11: Data integrity and consistency

Page 11

Sources of Ambiguity

1. Unclear responsibilities.

2. Different Professional Backgrounds.

3. Multiple Information Source.

4. Cultural Barriers And Differences.

5. Employee Experience Level.

Page 12: Data integrity and consistency

Page 12

1. Project Group

a) Ineffective project team.

b) Bad decisions based on bad data.

c) Appearance of incompetency to the client.

d) Damaged corporate image.

e) Loss of future contracts.

The Consequences

Page 13: Data integrity and consistency

Page 13

1. Cost of fixing errors

2. Cost of the unnecessary extra equipment

3. Engineering time

4. Cost associated with changes on site

Impact on the Budget

Page 14: Data integrity and consistency

Page 14

1. Extended development time.

2. Missed milestones.

3. Extended commissioning time.

Impact on the Schedule

Page 15: Data integrity and consistency

Page 15

1. Educate and create buy in by project team and management.

2. Get right people for the job (it may bring higher costs at the beginning, but huge savings at

the end).

3. Spend time in preparing data at the beginning of the project.

4. Implement strict rules while handling data.

5. Create specific roles with clearly defined expectations.

Solutions?

Page 16: Data integrity and consistency

Page 16

1. Instrumentation Lead

Instrumentation technician or engineer shall be responsible for all details pertaining to the

instrument and instrument installation only. Specification of all of the instrument requirements is

solely in this person scope of work and he/she will be responsible before the project.

Solutions?

Assign specific duties to the roles

Page 17: Data integrity and consistency

Page 17

1. Controls Lead

Controls Lead or designate is responsible for I/O assignment. However, this is an activity that

belongs to the latter part in the project. Involvement is not expected early, but it is vital and the I/O

review shall be conducted as soon as possible.

They are also responsible for creating reports pertaining to Control Systems – Instruments

Ranges List, Alarms List, S(et)P(oints) List.

Using Electrical Module loop drawings should be created by Controls Group

Solutions?

Assign specific duties to the roles

Page 18: Data integrity and consistency

Page 18

Database Manager/Lead:

1. Creating Initial Entries

2. Managing changes

3. Adding and deleting

a) Major equipment

b) Devices

c) Instruments

d) Soft points

4. Reporting

5. Becoming a single source for P&ID management

Roles

Page 19: Data integrity and consistency

Page 19

Structure

Process Lead

Coordinator(Database Lead?)

Electrical

LeadControls Lead

Instrumentation

Lead

Electrical

Group

Controls

Group

Instrumentation

Group

Page 21: Data integrity and consistency