document
DESCRIPTION
http://fiatech.org/images/stories/events/techconference/2005/teague.pdfTRANSCRIPT
FIATECH Meeting #1 April 2005
Interoperability Standards
FIATECH’s FocusApril 20, 2005Tom Teague
President, ePlantData, Inc.
FIATECH Meeting #2 April 2005
The Vision of an Integrated and Automated Capital Projects Industry
“Fully integrated and highly automated project processes coupled with radically advanced technologies across all phases and functions of the project/facility lifecycle..”
Interoperability is gold
FIATECH Meeting #3 April 2005
Interoperability Problem
Application 1 Application 2Map
Map
Application 1 Application 2Map
Map
All applications store data in a unique way A mapping is always
needed to share data
Enterprise 1 100s of tools
Enterprise 2 100s of tools
• Large companies use several hundred tools– Internal & commercial software, including repositories
• Collaboration with 10s to 100s of enterprises– Size ranges from very large to very small– Each company uses it’s own preferred tool set
1000’s of mappings needed – low cost is key
FIATECH Meeting #4 April 2005
Solution: Common Format
• Common format enables cross- organization exchanges
Common File Format
Application 1 Application 2
Map Map
or Database
Common File Format
Application 1 Application 2
Map Map
or DatabaseXML
• XML enables affordable, extensible maps without requiring any new standards
• All that is needed is cooperation/agreement
FIATECH Meeting #5 April 2005
Interoperability Standard
Interoperability: “the ability of two or more systems or components to exchange information and to use the information that has been exchanged”… Institute of Electrical and Electronics Engineers. IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries. New York, NY: 1990
Standard: “something set up and established by authority as a rule for the measure of quantity, weight, extent, value, or quality”… Merriam Webster Online Dictionary
FIATECH Meeting #6 April 2005
What about standards?• Common format solution long recognized• Industry standards efforts for 15 years
– ISO 10303 (STEP) – data exchange– ISO 15926 – data repository– IAI-IFC
• Standards are yet to be widely deployed• Why?
FIATECH Meeting #7 April 2005
Lessons Learned“Although any specific approach to standards must be sensitive to particulars of the relevant technology, applications, and markets, the one emerging from the standards community reflects these lessons:
collect a small group of vendors, write a small, simple specification that covers the important functions, omit nonessentials, leave room for both new technologies and possible backtracking, identify real-world test-beds for the standard, andget it out the door as soon as possible.”
…Martin Libicki, 1995Stanford University
FIATECH has embraced these lessons
FIATECH Meeting #8 April 2005
FIATECH Interoperability Focus• Roadmap Vision: Widespread interoperability• Research, development, deployment• Aggressively deliver results
FIATECH Meeting #9 April 2005
FIATECH Interoperability Activities
• DSC: Data Standards Clearinghouse• AEX: Automating Equipment information eXchange• IRR: Interoperability Requirements for the Roadmap• AVP: Automating Valve Procurement• AGC XML: Associated General Contractors XML for
construction documents
FIATECH Meeting #10 April 2005
FIATECH’s Data Standards Clearinghouse: Information Resource for Industry Standards
• CIMIS• ISO 10303
(STEP)– AP-221– AP-227
• ISO 15926 / InfoWebML
• MIMOSA• PIDX• PLIB
Plant• IAI-IFC / BLIS• aecXML• gbXML• LandXML• oBIX• OmniClass• OpenGIS• OSCRE• xPPRL• OPX
Building
Both AEXASCIICIS/2IAI-IFC/ifcXMLNCS
ISO 15926 / InfoWebMLOGC-GMLOpenGIS(R)
FIATECH Meeting #11 April 2005
Data Standards Clearinghouse• Web Information Resource
– http://www.fiatech.org/projects/idim/dscdata.htm• Aligned to FIATECH Roadmap• Introductory background paper available –
“Demystifying Interoperability”• Summary Content about the standard
– Sponsor, contact, web site– Usage & scope– Characteristics framework– Development & Deployment Status
• Links to Sponsor Web Sites
FIATECH Meeting #12 April 2005
FIATECH Meeting #13 April 2005
FIATECH Meeting #14 April 2005
FIATECH Interoperability Activities
• DSC: Data Standards Clearinghouse
Projects Using FIATECH’s Interoperability Process
• AEX: Automating Equipment information eXchange• IRR: Interoperability Requirements for the Roadmap• AVP: Automating Valve Procurement
FIATECH Meeting #15 April 2005
Interoperability Process
• Define detailed requirements– For high business value subsets in industry work process– Across organization & software boundaries
• Deploy in software– Adopt, adapt or develop XML schemas– Collaborate & consult with industry groups, including standards– Deploy high-value subsets in industry software
• Incorporate into industry practice– Use interoperable software on real projects– Feed results to standards organizations
• Repeat while business results obtained
AEX pioneering and demonstrating how it works
FIATECH Meeting #16 April 2005
AEX Project• Requirements (2002-2003)
– Equipment: design, procure, install, operate/maintain– Initial Subset: Equipment Design & Procurement
• Deployment (2003-2005)– Developed XML schemas (2003-2005)
• Core schema architecture for technical data & core equipment• Details: centrifugal pumps, heat exchangers, fans
– Collaborating with PIP, HI, DIPPR, API and ASHRAE– Centrifugal pump software demonstration (2004-2005)
• Industry Practice (2005-2006)– Commercial software interfaces – Feed results to industry standards – PIP, HI and API
• Repeat (2005 +)– XML for 25 equipment types planned for 2005-2006
FIATECH Meeting #17 April 2005
IRR Project• Interoperability Requirements for Roadmap
– First step in FIATECH Interoperability Process– Identify high-value subsets for deployment– Define detailed requirements for high-value subsets
• Interoperability Requirements Needed for:– Element 9: Life Cycle Info Mgt / Technical Framework– Element 1: Project Planning– Element 2: Automated Design– Element 3: Automated Procurement– Element 4: Intelligent Job Site– Element 5: Intelligent O&M– Element 6: Real-time Project Control
FIATECH Meeting #18 April 2005
IRR – Automated Design• March 2005 Workshop – Opportunity Areas
– Equipment Data “handover” (Project to O&M)– Vendor Information Intelligent Engineering Systems– Logical (2D, P&ID) Physical Model (3D)– Status/ownership information over life-cycle
• Project Plan– March 2005 – July 2005– Deliverable: Written report for high-value opportunities– Shared project cost: $15,000– Participation Fee: $2,000
FIATECH Meeting #19 April 2005
AVP Project
• Requirements– Streamline commodity valve procurement– Identified by team for Roadmap Element 3: Procurement
• Deploy– Technically verify vendor valve bid quotes & obtain info
• Compare PIP standard valve to supplier & internal catalogs• Obtain key vendor information for intelligent engineering systems
– Collaborative effort with Process Industry Practices (PIP)– Use XML schemas leveraged/extended from AEX
• Project Plan– Currently forming – completion: 9 months from start– Shared project cost: $45,000 – Annual benefits estimated at $100,000+ per company
FIATECH Meeting #20 April 2005
FIATECH – Driving Interoperability
• Roadmap Vision: Widespread interoperability• Research, development, deployment• Aggressively deliver results
By cooperatively implementing through:• AEX Project – equipment life cycle• IRR Project – high value opportunity requirements• AVP Project – commodity valve procurement• AGC XML Project – construction documents . . . More to come, sponsor companies drive