http://fiatech.org/images/stories/events/techconference/2010/presentations/bonus/why-and-how-iso-159

Page 1

Why and How ISO15926 Must Succeed A Software Vendor’s Perspective

Andrew McBrien, Director, Product Management March 29th, 2010

© 2010 Aspen Technology, Inc. All rights reserved


Agenda   Introducing AspenTech   Standards: Strategically critical to AspenTech   A Personal History with Standards: Lessons Learned   AspenTech Implementation of ISO15926: Philosophy and Approach   AspenTech and ISO15926: Current Status   AspenTech Contributing to the Success of ISO15926

© 2010 Aspen Technology, Inc. All rights reserved

|

2


Disclaimer

Aspen Technology may provide information regarding possible future product developments including new products, product features, product interfaces, integration, design, architecture, etc. that may be represented as “product roadmaps”. Any such information is for discussion purposes only and does not constitute a commitment by Aspen Technology to do or deliver anything in these product roadmaps or otherwise. Any such commitment must be explicitly set forth in a written contract between the customer and Aspen Technology, executed by an authorized officer of each company.

© 2010 Aspen Technology, Inc. All rights reserved

|

3


Introducing AspenTech

Š 2010 Aspen Technology, Inc. All rights reserved

|

4


Optimizing Process Manufacturing

Reduce costs, improve margins, increase return on capital

Design the Plant

  Innovate   Optimize capital   Reduce time to market   Increase plant uptime   Optimize throughput and product value   Design for energy efficiency

Operate the Plant

Manage the Supply Chain

  Maximize flexibility and responsiveness   Increase throughput   Increase yields   Reduce energy costs   Reduce inventory costs

© 2010 Aspen Technology, Inc. All rights reserved

|

  Enable demanddriven supply chain   Reduce supply stocks and run-outs   Reduce transportation and storage costs   Optimize inventory levels

5


Standards: Strategically critical to AspenTech

Š 2010 Aspen Technology, Inc. All rights reserved

|

6


Engineering: A Typical Asset Life-cycle

Many touch-points, between many vendors Tool selection may differ project to project Š 2010 Aspen Technology, Inc. All rights reserved

|

7


Without standards, life-cycle integration is limited by available proprietary interfaces

Proprietary interface with AspenTech

Vendor 1

Vendor 2

Vendor 3

Proprietary interface with AspenTech

No proprietary interface

User’s choice limited

Solution value reduced

Users: Flexibility and agility impeded AspenTech: High cost of maintaining multiple interfaces Š 2010 Aspen Technology, Inc. All rights reserved

|

8


Standards: Agility and responsiveness for Users and Vendors

Vendor 1

Standards-based interface

Vendor 2

Vendor 3

Standards-based interface

Flexible choice

Standards-based interface

Users: Flexibility and agility enabled, solution value assured Vendors: Development efficiency and responsiveness Š 2010 Aspen Technology, Inc. All rights reserved

|

9


Enterprise Operations: IT Strategies demand standards ERP

ISA S-95

ISA S-88

Chemical Supply Chain Demand Planning

Supply Planning

Manufacturing Execution Production Scheduling

ProdML

Information Management

Production Management

WITSML

Petroleum Supply Chain Fleet Optimizer

IMOS

OPC

DCS

.. plus many others

Š 2010 Aspen Technology, Inc. All rights reserved

|

10

Yield Accounting


A Long Personal History with Standards: Lessons Learned

Š 2010 Aspen Technology, Inc. All rights reserved

|

11


A Long Personal History with Standards

  Data interoperability, asset life-cycle

ISO 15926 Global CAPE-Open CAPE-Open   Integration of models and simulation pdXi   Datathermodynamics interoperability,into process and equipment design ISO 10303/221   Data interoperability, asset life-cycle 1980s

1990s © 2010 Aspen Technology, Inc. All rights reserved

2000s |

12


Scorecard

ISO 15926 Global CAPE-OPEN CAPE-OPEN pdXi ISO 10303/221

… so what have I learnt?

© 2010 Aspen Technology, Inc. All rights reserved

|

13


Productized implementations: Essential for practical standards Development of Interface Standards

“Lab-scale” prototyping

Version 0.9 Delivered

Version 0.93 Delivered

Vendorimplementation starts

Version 1.0 Delivered

Production-scale implementation: Surfaced ambiguity and errors, identified impracticalities Drove significant evolution of Interface Standard

© 2010 Aspen Technology, Inc. All rights reserved

|

14


Well-funded, dedicated resource: Essential to develop standards $1.8MM (CY 2010)

ISO 10303 (Part 221)

ISO 15926

Voluntary effort

Significant investment

Strong foundation

Results applied in practice Formal Investment # Applications

Š 2010 Aspen Technology, Inc. All rights reserved

|

15


It Takes Two to Tango. For Standards to Succeed, it Takes Many “Watson, please come to my laboratory” … but what if the telephone had stopped there?

1995: pdXi data model No other adoption   No interoperability benefits

Zyqad Process WorkBench (now Aspen Basic Engineering)

© 2010 Aspen Technology, Inc. All rights reserved

|

16


Adoption differs with need, sophistication

Global CAPE-Open Interfaces

Interface

Purpose

Knowledge

Adoption

Unit Operations

Model proprietary equipment

Core process engineering

All mainstream simulators

Thermodynamics

Model proprietary chemistry

Core process modeling

All mainstream simulators + niche products

“Equation System”

Problemspecific mathematics

Advanced numerics

Niche product

© 2010 Aspen Technology, Inc. All rights reserved

|

17


How does ISO15926 Benchmark? Lesson

ISO 15926

Productized implementations essential

  Off-the-shelf support by multiple vendors

Well-funded, dedicated resource essential

  $70k raised in three weeks   Full-time resource in place

Standards succeed only with broad support

  Support of all major process plant software vendors

Adoption differs with need, sophistication

  Multiple implementation approaches available

© 2010 Aspen Technology, Inc. All rights reserved

|

18


AspenTech Implementation of ISO15926: Philosophy and Approach

Š 2010 Aspen Technology, Inc. All rights reserved

|

19


Anatomy of ISO 15926 Implementation approaches Reference Data Library Common vocabulary

XMpLant

•  Part 11

iRing

•  Part 8

Others

•  Part 11

10s of man-years

© 2010 Aspen Technology, Inc. All rights reserved

|

20


Organizational Maturity   “Organizations cannot skip stages or the associated activities without introducing weaknesses into their EIM programs, which will cause them to fail later on.”   “Organizations cannot implement EIM as a single project. Rather, it requires a gradual building of skills, awareness and technology. It must happen in iterative phases over time.”

  Gartner, "Introducing the EIM Maturity Model" (2009)

© 2010 Aspen Technology, Inc. All rights reserved

|

21


AspenTech: XMpLant Selected

Reference Data Library Common vocabulary

•  Part 11

XMpLant

10s of man-years

•  Easy entry-point •  Already proven when our implementation iRing •  Part 8 started •  Strong network-effect Which should

AspenTech •  Fast – first production-quality implementation in 3 months choose? •  Good platform to contribute enhancements Others •  Part 11Data to Reference

© 2010 Aspen Technology, Inc. All rights reserved

|

22


AspenTech and ISO15926: Current Status

Š 2010 Aspen Technology, Inc. All rights reserved

|

23


Matrix 123 (Proteus) Project: May 2009

P&ID to 3D: Matrix 3

XMpLant-based

Multiple vendors

P&ID to P&ID: Matrix 1

3D to 3D: Matrix 2

Achieved

• On specification •  On time •  On (the vendors’ own) budgets

© 2010 Aspen Technology, Inc. All rights reserved

|

24


Example: AspenTech P&ID to AVEVA PDMS Aspen Basic Engineering

P&ID exported to XMpLant file •  Equipment, Instruments, Piping •  Connectivity

Imported into AVEVA PDMS

•  Graphics

•  Define logic of 3D Model © 2010 Aspen Technology, Inc. All rights reserved

|

25


AspenTech and ISO 15926: Fully supported, project-ready interface

January 2010: Update (XMpLant v3.3.3) Fall 2009: Commercial release (XMpLant v3.2) May 2009: FIATECH Conference Demonstration

Š 2010 Aspen Technology, Inc. All rights reserved

|

26


Driving ISO15926 to Success

Š 2010 Aspen Technology, Inc. All rights reserved

|

27


Calendar Year 2010: Aggressive Goal

“ISO 15926 fully operational for process plant within 2010” Endorsed by FIATECH BoD AspenTech: Funding Steering Team Resource

© 2010 Aspen Technology, Inc. All rights reserved

|

28


AspenTech Technical Activities in 2010

Reference Data Library Contribute AspenTech Common Core Data Model

XMpLant

•  Active development of XMpLant schema iRing

•  Project management

•  Part 8

•  Feedback to Reference Data Library •  Ongoing support for productized interfaces Which should •  Element 9 RoadmapAspenTech Champion choose? Others

© 2010 Aspen Technology, Inc. All rights reserved

•  Part 11

|

29


Call to Action   Learn more –  Visit project and vendors’ booth in Technology Showcase –  AspenTech: Booth 6

  Strengthen the network effect –  ISO 15926 delivers value today, bake it into your IT strategy

  Make ISO 15926 fully-operational in CY 2010 –  Support FIATECH and POSC Caesar joint project –  Resource and/or funding –  Use Cases, testing and feedback

© 2010 Aspen Technology, Inc. All rights reserved

|

30


Turn static files into dynamic content formats.

Create a flipbook
Issuu converts static files into: digital portfolios, online yearbooks, online catalogs, digital photo albums and more. Sign up and create your flipbook.