Business Case Our Challenge. Asset lifecycle definition of engineering information to support Operation, Maintenance and Projects

Transcription

1 Asset lifecycle definition of engineering information to support Operation, Maintenance and Projects Business Case Our Challenge How to move from the current position of; Intelligent schematics (P&ID s) (2d) Intelligent Instrumentation system auto producing project deliverables (2d) Multi-discipline 3d modelling supporting BIM and auto-generating piping deliverables (3d,4d,5d) Key Enabler; Governance for the creation of a The Digital Asset To a position of integrated design systems that follow a defined Asset Information Lifecycle and support digital handover

2 The Digital Asset Follows a defined lifecycle Is created from many sources Defined by a master model definition Has value to multiple consumers Value increased when the defined digital Asset reflects the physical asset Asset Information Lifecycle Start of Life Startup ~ 2-3 years ~ years End of Life Concept, Detail, Construct & Commission Operate & Maintain Governance People Process Technology Project Phases As-Is Read Only Management of Tag Management Doc Management Model Management Engineering Design Data Content Management Management of Change Process Change Process Asset Data Materials Data Spares Management Integrity Library CMMS Authoring Modification Projects Project Information Systems Asset Information Systems Asset Operate & Maintain Systems 2

3 Asset Information Landscape Systems Stakeholders Phases Deliverables Asset Information lifecycle PFD MV & LV SLD BS Schematics 3D Model AutoCAD Stage 2 Concept PFD P&ID SLDs Schematics Lists 3D Model Studies Microstation Stage 3 Basic PFD P&ID SLDs Revit Stage 4 Detail Layouts Isometrics Lists Schematics Datasheets AFD s Schedules/Indexes 3D Model Impact Assessment Project Delivery Systems DQ DQ Check FAT SAT Stage 5 Fabrication / Construction Permits Constructability Plans Opes Mech.Comp Certification SmartPlant Suite TTOP VTOP SPA Methods Statements Inspections Verifications Navisworks Design Groups Management Groups Sub Contractors Suppliers Vendors Fabricators Maintenance Operations Stage 6 Commissioning CTP Permits LOTO calibration Microsoft Office Handover Delivery Platform Document Control system Data Management System Project Delivery Platform Project Handover system The Class Library & the Data Model The Class Library is a grouping of allowable equipment types and the expected data associated with them. Owner Unit Area Plant The Data Model is supported by the class library and identifies the way that data is created, manipulated & measured as it flows from concept through Construction, Commissioning and Operations Manufacturer Status Variant WorkPacks Systems Document Information Management Governance is the foundation that defines how the data model is implemented and is a source of Clarity for project delivery requirements (D) Model Spares S 3

4 The Tag Information Governance (e.g. Pump) Is classified as a functional object It s function is satisfied by a number of physical classes Must be named Must belong to a number of taxonomies (e.g. Process Hierarchy & Maintenance Hierarchy) To be complete requires Attributes (e.g pressures, Temperatures etc) To be complete requires 4 documents (e.g. Datasheet, P&ID, Operations manual etc) Can have a parent tag (e.g. Skid or package) Belongs to an Area Belongs to a System Requires a Manufacturer The function of pump can be physically satisfied by a number of types of pumps (e.g. Centrifugal, Piston, Diaphragm etc) Image extracted from Aveva ISM The Class Library Classes Structure the equipment types that are to be tagged into classes The Class and its description Image extracted from Aveva ISM 4

5 The Class Library Functional & Physical Functional Class Physical Class Asset Constructed Relationship Model By defining a relationship between the Tag Class and the Physical Class, enriches the data associated with the Tag by implying the Asset s Data to the Tag item. The Class Library Attributes The class Normalisation & allocation of Attributes to Classes and rules for their format and lifecycle Image extracted from Aveva ISM 5

6 The Class Library Tag Template Classification Properties Model The Class Library Relationships Class Responsibility Class Phase Functional Tag Class Ref Obj Physical Equip Class Asset EQP Class Constructed Responsibility Relationship Model EQP Class Phase Tag types can be related to REFERENCE Objects. REFERENCE Objects are items that can carry properties and dependencies to further enrich the tag data. 6

7 The Class Library Relationships Class Document Requirements Defined Rel Tag DOC s Tag PROP Defined Rel REF Object DOC s Defined Rel ASSET DOC s Defined Rel MODEL DOC s Functional Class Physical Class Class Property Requirements REF Object PROP ASSET PROP MODEL PROP The Class Library Rules The application of rules across multiple disciplines and systems Naming Conventions Unit of Measure Rules Image extracted from Aveva ISM 7

8 The Class Library Responsibility Image extracted from Aveva ISM The Class Library Standards ISO 5926 Industrial automation systems and integration -- Integration of life-cycle data for process plants PAS 92 Specification for information management for the capital/delivery phase of construction projects using building information modeling ISO 2948 Building information models -- Information delivery manual Image extracted from Aveva ISM 8

9 The Class Library Property Characteristics Functional Class Property Requirements gained by relationships Tag PROP Scoped By PROP System REF Object PROP ASSET PROP Scoped By Scoped By Scoped By PROP Responsibility PROP Phase PROP Picklist Property Characteristics. These Scoped by Characteristics ensure data is validated and allow Viewing and sorting of properties by phase and responsibility MODEL PROP Scoped By PROP UoM Physical Class The Class Library The Tag Area Owner Unit Plant Status WorkPacks Manufacturer Document Variant Systems Model Spares S 9

10 The Equipment Class Library D The Data Model needs to be object based and in context Consider the Functional and the physical requirements of each class of object Consider the Data Requirements for each Phase of the Lifecycle Consider the ownership and responsibilities of the data requirements through the phases of the lifecycle. Consider the characteristics of class attributes to influence data management processes and tools For every physical asset there must be a digital asset Project Delivery Requirements Report Functional Class Physical Class Attributes Requirement Document Requirement Physical Attribute Requirement Contractual clarity across all phases of the project based on the Information Governance 0

11 Digital Handover Handover Process Operations Asset Data Materials Data Spares Management Integrity Library CMMS Authoring Completeness based on Information requirements SAP MAXIMO etc Managed Handover Asset Operate & Maintain Systems Business Case The Result An Information Governance framework has delivered Clarity of project scope per discipline per phase per stakeholder Definition of System integration requirements Support for Digital Handover

12 Thank You Questions & Answers Colum Lynch Information Systems Consultant T: colum.lynch@pmgroup-global.com Jeremy Freeman Sector Business Development Director T: jeremy.freeman@pmgroup-global.com Engineers Architects Project Managers Constructors