1.Using ISDDs
Dr. Avin Mathew
CTO
MIMOSA
amathew@mimosa.org
2.
3.Estimated Benefits of Interoperability
5% reduction in equipment capital costs
From internal study of a large owner/operator in conjunction with its EPCs and suppliers
8% total project capital cost,14% reduction in project schedule,5-15% reduction in annual maintenance cost
Studies from CII and NIST
4.Fiatech O&M Information Needs Survey
Survey of ten process industry companies
5.Fiatech O&M Information Needs Survey
Six out of nine companies claimed that 50% or less of information required by O&M was in an immediate usable form
Primary driver for O&M "evergreen" data maintenance is safety and regulatory requirements
6.Where are Equipment Datasheets used?
Engineering / Design
Capture engineering design requirements
Simulation and testing
Metric by which to measure project completeness
Procurement
RFQ and bid tabulation from supplier responses
Capture supplier model characteristics
7.Where are Equipment Datasheets used?
Completions / Commissioning / Startup
Capture as-built asset characteristics
Configuration of MES / Control Systems
Instrumentation calibration
Operations
Set points for alarms and alerts
Process simulation and optimization
Maintenance
Compare against supplier product data sheet for make/model matchup
Instrument calibration
Input to reliability modelling
Decommissioning / Disposal
Regulatory requirements for sale?
8.Plan /Program / Contract
Engineer / Design
Procure
Fabricate / Construct
Complete / Commission / Start-up
Operate / Maintain
Decommission / Dispose
Determine design % completeness by analyzing filled in datasheet properties required by equipment type for each phase
Align engineering terminology across teams using industry RDLs as a base
Handover machine-interpretable datasheets for immediate loading into engineering master data system to compare against the physical asset and configuring O&M systems
Select project specific templates from ISDDs for structured data entry by engineers
Pre-populate datasheets from previous phases (e.g. design basis)
as engineers choose equipment to design
Automate technical comparison of vendor offerings; determine if RFQ responses fall within distribution of RFI responses
Matchup requirements against product datasheets from equipment suppliers
9.Use CaseStructured Data Exchange
Avoid transcribing data at each stage
Reduce long-term operational cost
Improve data quality
Improve time to market
Owner/Operators
Suppliers
>
XML
CCOM
EPCs
>
XML
CCOM
>
XML
CCOM
10.Use CaseConvert Semi-structured to Structured Data
Continue using existing data entry work process using spreadsheets
Make actionable / structured data easily consumable
Convert
>
XML
API Instances
CCOM
Instances
Linear
Instances
ASME Instances
ISA Instances
PIP Instances
>
XML
ISDDs
11.Use CaseGenerate Linear Data Sheet Templates
Tailor template according to stage
Ensure consistent experience and validation
Structured data is easily consumable
>
XML
ISDDs
Linear
Templates
Generate
Project
Characteristics
(applicability,
constraints
current stage)
12.Extensible ISDDs
13.Maturity Model
14.Using ISDDs
Dr. Avin Mathew
CTO
MIMOSA
amathew@mimosa.org