Validation, Transformation & Loading Solution (VTL)

(1)

VTL

High-quality Plant Asset Data Handover

High quality Plant Asset Data Handover

Validation, Transformation & Loading Solution

(VTL)

(

)

Tom Arsenovic Tom Arsenovic

Vice President, PP&M EMIA Services & Business Development Adrian Park,

Adrian Park,

(2)

Information validation & take-on

– Business challenges –

Business challenges



enormous data volumes



often undertaken at the end of a project



often undertaken at the end of a project

when there is limited time and resources



limited resources with necessary skills

$



typically cost $10-20M for a $1billion

CAPEX plant and take over 1 year



poor quality data can add 30% to

modification costs and can result in

wrong decisions impacting plant

reliability, and safety



solution is not just an IT tool:

– clear specification of requirements in

contracts

– organisation to follow-up and verify

– strategy of incremental handover

(3)

The challenge



Problematic information handover during asset lifecycle:

FEED d t il d d i

– FEED → detailed design

– detailed design → construction (including numerous sub-contractors)

– construction → commissioning

– operations, maintenance, enhancements etc

– decommissioning



The Solution

– information management plan covering the entire asset lifecycle

– detailed specification of engineering data requirements p g g q

– generally available commercial tools, acceptable to a wide range of

suppliers, which facilitates the efficient handover of quality controlled engineering information

(4)

Achieving seamless handover to operations via

continual loads

SP-PID SP-EL others Handover of FEED information to EP Handover of project ‘Traditional’ EPCM

Execution SP-3D SP-I SP-MAT

Plant handover

to EP project

information to operator Continual Incremental Handover

EP EP Exception Reports Standards/ Standards/ _CM_CM handover

design engineer procure construct commission startup

concept FEED operate maintain optimize

EP EP Standards/ Specifications Standards/ Specifications SP-I OWNER

OWNER OPERATOROPERATOR

SP-I ERP

Continuous validation / aggregation / consolidation

SP PID SP PID SP I Construction SPF EDW SPF EDW Contract Award

SP-PID Construction SP-PID

Analysis & simul

CMMS

(5)

Strategies to ensure improved handover



Information Management Scope (IMS): addresses hand-over

requirements in order to ensure safe and efficient operation of a

requirements, in order to ensure safe and efficient operation of a

facility

– minimum level of documentation required to effectively manage its assets and

business business

– data format requirements and taxonomies structured to be compatible with the

engineering, operating and maintenance systems to be used

– information specification provides the details of the required data and formats



Tools required to facilitate the handover of a high quality digital plant

– computerized tools to ensure validation, transformation and data loading

– facilitate an incremental handover (eliminates full handover every iteration)facilitate an incremental handover (eliminates full handover every iteration)

– consolidation of data in a single authoritative engineering data Warehouse,

providing a consistent source for asset information throughout the asset lifecycle via access from a simple web portal

– delivered over the lifecycle of the asset where possible

– codification of business rules – as needed from the enterprise to the project

level as needed

(6)

VTL overview

contractors

data validation team

t OO / PMC

CAPEX

project team

operations

at OO / PMC

p j

operations

VTL

Staging area SAP SPO/ SPF

VTL

suppliers

other Intergraph target systems other non-Intergraph target systems legacy systems QC Reports systems systems

(7)

VTL validation rules



powerful and highly flexible generic rule

definition capability including:

– syntax rules (ENS) – uniqueness validation – relationship cardinality

date & time validation – date & time validation – integer validation – string validation – pick-list validationp c st a dat o

– unit of measure validation – mandatory fields

– cascading errors

– PL/SQL and DLL rule definitions for more complex rules



rules may be included into rule sets that are

run against data submissions



rules and rule sets are reusable



severity of validation findings may be graded

on rules eg as “warnings” and “errors”

(8)

VTL configurable validation engine



role-based rules administration

with SPF Desktop Client.

p



wide range of standard out of the

box rule types that may be defined

in a SPF form by end users

y



configurable rules to check:

– naming standards

– mandatory relationships

– enumerated values

– ranges and UoMs for numeric

values values

– lengths and format for string values



custom rules may be written using

PL/SQL or NET

PL/SQL or .NET



rule sets for organizing rules that

are run together

(9)

VTL data import



plug-and-play “readers” allow

import from various file types:

– CSV – XLS



constant prompted and custom



constant, prompted, and custom

code values may be inserted



comparison with previous

s bmission to disco er deletes

submission to discover deletes;

implicit and explicit deletes

supported

t

ti

b

d

Wi d



automation based on Windows

Workflow Foundation



mapping and transformation

b

d

i d

d d XSLT

based on industry-standard XSLT

(10)

VTL mapping and transformation



XSLT transformation (Extensible

(

Style Sheet Language) is used

during both import and export to

the staging area

g g



XSLT is a very robust

technology supporting a very

gy

pp

g

y

wide range of transformations



customers may choose any tool

custo e s

ay c oose a y too

to generate XSLT

transformations

(11)

VTL staging area



VTL staging area based on SmartPlant

Foundation where:

– user/user group access rights are managed

– validation rules are managed

– rule sets are managed

– data submissions loaded

– validation executed and results held

– data submissions and validation results may

be q eried and na igated be queried and navigated

– full auditable traceability of all validation and

updates performed



VTL schema

– staging area schema (aligned with SPO Core)

is provided OOTB

– OOTB schema accepts most common OO

handover data

– role-based navigation provided by SPF

– may be modified using the SPF UML based

schema editor schema editor

(12)

VTL data export/load



plug-and-play “writers” allow

export/load to various systems

export/load to various systems.



OOTB writers for loading SPF 3.8

and 4 x systems

and 4.x systems



OOTB generic writer will invoke

any EXE hand off data and

any .EXE, hand-off data, and

monitor progress



based on Windows Workflow



based on Windows Workflow

Foundation

i

d t

f

ti



mapping and transformation

based on industry-standard XSLT

(13)

IMPORTANT DISCLAIMER

This document is designed to communicate a perspective

g

p

of likely R&D prioritization based on the current indicators

of client demand. It will change both in scope and timing

i

t i d

t

d

hi h i

it d

i

in response to industry demand, which is quite dynamic.

Intergraph retains all decision rights as to what will be

included in a particular release and does not make

included in a particular release, and does not make

binding commitments outside of a written commercial

(14)

Validation Transformation & Loading (VTL)

-selected items from backlog

selected items from backlog



extend reader plug-ins

XML ISO 15926

– XML, ISO 15926

– extract of tags from CAD files, scanned files, MS Office

files and PDF files under loading

– hotspotting CAD PDF under loadinghotspotting CAD, PDF under loading



web service loading



run VTL direct on a SPO implementation

li

i

di i



list view editing



Excel load registers and mappings (to be released)



KPI and dashboard reporting

p

g



export and bulk load to SAP PM



support for multiple domains for cross-source

comparison

(15)

SPO VTL – benefits & value proposition

 Reduced time and cost of data handover from

CAPEX projects and turnaroundsp j

– $10-20m – up to 1 year

 Improved range, quality, and consistency of

validation performed

 Simple for end-users to define rules

 End-to-end automation

 Enable comparison of data in the staging area

with data in the target SPF system via PL/SQL rules

F ll dit bl t bilit f d t b i i

 Fully auditable traceability of data submissions,

validation performed, results and manual changes

 Support for the increasingly data centric

deliveries from projects

 Tight integration with target engineering

database including comparison of data with data g p

(16)

Extract from Shell Presentation

(17)

Extract from Shell Presentation

(18)

Summary



The challenge

– data volumes are enormousdata volumes are enormous

– data is usually delivered incomplete, with errors or badly formatted – limited time or resources to validate data during project close-out



Benefits

– accelerated and improved start-up and commissioning process  can take up to one year to load operations systems

– reduced information management cost at handover

 costs involved for a $1 billion CAPEX project are typically $10-20 million

 reduction of 80% cost should be possible by implementing data handover standards & specifications and automation of receipt, verification and loading

reduced modification cost – reduced modification cost

 validating and correcting data for a modification can be up to 30% of the modification cost



Enabled through

g

– rapid loading of massive data quantities – support for continual incremental handover

– rules based and automated quality assurance for very large data or information sets – rules based and automated conversion

(19)

(20)

Integrating the

Engineering Enterprise

IMPORTANT DISCLAIMER

This document is designed to communicate a perspective of likely R&D prioritization based on the current indicators of client demand. It will change both in scope and timing in response to industry demand, which is quite dynamic. Intergraph retains all decision rights as to