Enterprise Integration using AssetWise

(1)

tl ey S ys te m s, In co rpo rat ed

(2)

• How to ensure that all affected information is taken into account when planning and managing changes to asset information • How the AssetWise Common Service Bus

provides quality controlled asset information via automated integration to upstream and downstream enterprise systems

(3)

• Enterprise Integration Architecture

– For EPC and Construction

– For Operations

• Integration Strategy

– Options available for new implementations

• Out of the Box Connectors

– SharePoint, ProjectWise, Outlook

– Generic Connectors and Integration Tools

• Storage Drivers • eB Event Handlers

• What our users are doing

(4)

What is AssetWise?

is an operations information modeling platform

for delivering asset lifecycle information management to operators of infrastructure assets…

a suite of interoperable applications and

on-line services to improve the management and operational performance, safety, compliance of infrastructure assets.

(5)

• Asset Lifecycle Information

Management (ALIM) for complex, highly engineered facilities and networks

• Manage asset information throughout the lifecycle

– Information integrity

– Regulatory compliance

– Operational efficiency

• Add value to your information and extend the life of your infrastructure assets

(6)

35 percent of IT dollars are spent building point-to-point interfaces

– According to Gartner Group and Forrester Research

• We can extrapolate: 35 percent of an implementation budget will go to integration tasks

• An enterprise integration strategy is

necessary to control & reduce these costs

(7)

– i.e. Maximo, EMPRV, AssetSuite, SAP

• Document Management

– Documentum, Curator, FileNet, LiveLink

• Operational

– AutoTour / AutoLog

• Middleware

– Tibco, BizTalk

• 2D and 3D Design Tools

– OpenPlant, AutoPlant, AVEVA, Intergraph

Enterprise System Integration Types

What systems do you need to integrate? Please let

us know in the upcoming poll!

(8)

5) 2D and 3D Design Tools

What types of enterprise systems do you

have integrated, or need to integrate?

(9)

Example Enterprise Architecture

AssetWise provides: • Master tag Register • Configuration Hub

• Receive and validate information from Design Tools

• Provide Tag information to downstream systems like SAP and Work Management

• Provide authorized information to external and internal parties via formal distribution

(10)

(11)

• ISO 15926 works by first providing a publicly-available set of reference data.

• To use ISO 15926, organizations first map their internal data stores and applications to the reference data.

• The reference data is also used at the beginning and the end of information exchanges to validate it.

[https://www.posccaesar.org/wiki/ISO15926Primer_HowItWorks]

What about ISO15926?

(12)

(13)

(14)

• Standard Integration Strategy

– Out of the box connectors

• ProjectWise • SharePoint • MS Outlook

– Using AssetWise only services layer and API

– Using middleware like Tibco & Biztalk

– Using REST “Quicklinks”

• Using Partners

– e.g. SAIC or ACE

• Working with User IT Departments

Options

How do you implement your integrations? Please

let us know in the upcoming poll!

(15)

2) Technology partners such as SAIC or ACE

3) Professional services through the software vendor

(16)

Methodologies

• Platform integration

• Database events triggering stored procedures

• Snapshots

• Data Quality Service (DQS)

• User facing API-based methods:

• Stand-alone Applications

• Stand-alone Web Pages

• Plug-in Web Pages for AssetWise

• Scripts running in Office Apps

(17)

Example: Integration with Maximo

(18)

• Two Categories of Integration

– Upstream and Downstream Integration

• Upstream (incoming)

– Depending on incoming source might be:

• Synchronous API integration

• Asynchronous CSV or XML file consumption using eB Services layer including configurable engines and queue technology

• Data Quality Services (DQS)

• Downstream (outgoing)

– Using standard configurable XML snapshots based on predefined events

• Snapshot generation normally based on object approval or workflow step completion • Snapshot published to predefined locations including database table, directory or

middleware

(19)

Snapshots

(20)

• Used to create a “snapshot in time” of an AssetWise

object’s meta-data including attributes and relationships. • The content of a snapshot is configurable and by using

the AssetWise “OnSnapShotCreated” event, XML snapshots may be provided to integration ports.

(21)

• All primary objects may be configured to produce snapshots

• Snapshot creation is event driven. The particular event is configurable.

Snapshot Characteristics

• Snapshots are created as XML and may be configured to be rendered as HTML or PDF

• Snapshot contents are user definable.

(22)

Viewing a Snapshot

Soon after approval of this document, the snapshot is available…

(23)

Snapshots Rendered as XML or PDF

(24)

Sharing the Snapshot downstream

(25)

(26)

• AssetWise supports external repositories

– either through custom integrations or

– through product-level integrations such as with SharePoint.

• AssetWise storage architecture also supports pluggable storage device drivers

– can be written by customers or other third parties using a public API.

• The pluggable storage device drivers can be installed easily and are automatically recognized by AssetWise.

(27)

(28)

• eB Insight introduces the ability for developers to write custom storage drivers

– Primary purpose is to enable reading and writing of file contents to any arbitrary storage device or

– to develop a driver that behaves in a specific manner which is different to the standard drivers.

• Examples of possible drivers are:

– Windows file system

– FTP, Http or other web protocols

– File contents stored as blobs in a Database

– Connections to 3rd Party systems like Curator, Documentum

(29)

• Sometimes automation is not enough freedom…

– AssetWise event handlers allow users to create business rules using well known database languages like T-SQL and PL/SQL

– These event handlers are then plugged into the AssetWise event model for custom behavior

(30)

AssetWise Connectors

(31)

(32)

• UK Rail Company (in test or production)

– AssetWise/ProjectWise Connector

– AssetWise/SharePoint Connector

– Event based Document Distribution (of PW files)

• using AssetWise Automation and Event Handlers

• UK Rail Company (Future)

– Tag Register Services

– i-Model Data Distribution from Design Tools

– Data Quality Services (DQS)

– Periodic Bulk Data Import

(33)

– AssetWise Generic Integration (snapshots & API)

• EMPRV Work Management System • Up and downstream; data and files

– Biztalk middleware

– “Push” model

• East Coast Utility

• Maximo Work Management System

• Up and downstream; data only (files remain in eB)

– Tibco middleware

– “Pull” model (from Tibco)

(34)

• Fuel Processing User

• Maximo Work Management System

• Up and downstream; data only (files remain in eB)

– No Middleware, using File Location

– “Push Model”

• Midwest Nuclear Operating Company

• AssetSuite Work Management System

• Curator Records Management System (using Storage Driver) • Up and downstream; data and files.

– No Middleware, using staging tables in Database

(35)

• Advanced Technology Company

• LiveLink Document Management System • Downstream only; files only

– No Middleware, direct drop into LiveLink

– “Push Model”

• Southeast Coast Utility

– Assetwise Generic Integration (API)

• Maximo Work Management System • Up stream;

• Various

(36)

 AssetWise is architected with integration needs in mind

 ISO15926 is an important factor – AssetWise, and Bentley

tools in general, are well positioned to meet this requirement

 _{Most installations have unique integration requirements –}

having a proven integration strategy saves money and time

 AssetWise provides common OOTB integration connectors

 Bentley has integration successes over a wide spectrum of

users – industry tested and proven strategy!

(37)