© 2014 bentley systems, incorporated introduction to bentley eb enterprise bridge gary cochrane –...

© 2014 Bentley Systems, Incorporated

Introduction to Bentley eBEnterprise Bridge

Gary Cochrane – Information Management Sales Executive

2 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

What is AssetWise / What is eB?

AssetWise AssetWise is a suite of interoperable applications and on-line services to improve the management and operational performance, safety, and compliance of infrastructure assets.

eBeB is an information modeling platform for delivering lifecycle information management to operators of infrastructure assets… and also the software platform upon which AssetWise products are built


eB is…

• An Information Modeling Platform– Providing core tools to model business processes and the objects

they govern• Full compliment of built-in configurable object types• Workflow engine• Rendition engine• Records Management engine• Relationship engine

• The Platform on which AssetWise products are built– Example: The new Construction Work Package application

• Took ConstructSim and re-built it on top of the eB platform


AssetWise Applications in Geospatial

• What Applications do we currently have that are built on eB?– Within the Geospatial space?

• Well at this point, none

• So we are selling the platform…– With Professional Services to configure it to solve a particular

business need• The key being “configuration”• With the goal to minimize customization (e.g. compiled code)• eB is extremely configurable


The eB platform

• Object types, to highlight a few…– Documents– Persons– Physical Items

• Equipment, Buildings, essentially anything I can touch– Virtual items

• Systems, Assemblies, Procedures, things I can’t touch– Projects– Locations– …


The eB Platform – Object Types


The eB Platform – Workflow Engine

• Advanced Workflow capabilities, including:– Branching, & parallel routes– Conditional tasks– Individual or group assignment of tasks– Email notifications– Time allotments for tasks– Schedule calculations– GUI Design tool


The eB Platform – Workflow Engine


The eB Platform - Relationships

• Relationship Types:– One-to-one

• A Procedure that has but one owner (person responsible)• An equipment item has a single location

– One-to-Many• An Operators Manual applies to 10 purchased items of the same model

– Many-to-Many• There are multiple persons on a project, yet those persons are on multiple

projects


The eB Platform – Records Management

• Optional, but seamless module– Full File Plan Support

• A File plan defines the record retention requirements for a given class of documents.

– Time-Based Disposition– Event-based Disposition– Supports Move, and Destroy disposition types– Full Audit Trail– Compliant with DoD 5015.2 Standard

• And listed on the official DoD approved products register


What eB is NOT

• eB is not:– A Document Management System

• Although eB does manage documents…– Documents are only the tip of the

iceberg– As a general rule, the argument for

eB is not compelling if only using it for document check-out/in


Confused yet?

• We’ve discussed the core feature set, and what eB is *not*, so again, what is eB?

• From our Web site…– eB helps you control information and manage change throughout the

asset lifecycle, ensuring the delivery of accurate, trusted information to operations and maintenance teams — wherever and whenever it is needed

– eB uniquely integrates configuration and change management best practices to deliver asset information management services throughout the infrastructure asset lifecycle


eB *is* a Configuration Management solution

• CM is a formal process that facilitates orderly management of system information and system changes for such beneficial purposes as:– to revise capability– improve performance, reliability, or maintainability– extend life– reduce cost– reduce risk and liability– or correct defects


CM Justification

• Return on Investment– The cost of implementing CM is returned many fold in cost avoidance– The lack of CM, or its ineffectual implementation, can be very

expensive and sometimes can have catastrophic consequences such as failure of equipment or loss of life

“… we learned that the blowout preventer had been modified in unexpected ways…”

“… BP told us the modifications on the BOP were extensive. After the accident, they asked Transocean for drawings of the blowout preventer. Because of the modifications, the drawings they received didn't match the structure on the ocean floor.. …”


Textbook Configuration Management

Requirements

What is required to be

there

Item Configuration

What is actually there

Must C

onfor

m Must Conform

Must Conform

Asset Information

What our documents say is there

Functional /ProcessData &

Information

ItemConfigurationInformation

Item

Contractual Requirements

Engineering Requirements

Regulatory Requirements

CM process enables the organization to maintain equilibrium between the

three


Managing Information in Context

• Typically all this information exists…

• But exists in different silos

• Thus making relationships difficult or impossible

• By federating the silos, eB enables the organization to capture the what, but also the why, how and when

• Creates auditable sequences of how and why information changed

ProjectsLocation

Change Requirements

PeopleDocuments

Distribution Order

Equipment Asset

Requirements

Drawing= One-to-one/One-to-many Bidirectional ‘Named’ Relationships


eB, a member of the AssetWise family Information Management Configuration Control Controlled Docs Records Management Engineering Design Corrective Action Human Performance Knowledge Management

Asset Maintenance

Collaboration

Human Resources Program Management

UsersLegacy Enterprise Users Collaboration Visibility Information Quality Compliance Governance Change Control

Enterprise Citizenship

Financials


NIST Study on Interoperability

“An estimated 40% of engineering time is dedicated to locating [finding] and validating

information…”

US National Institute of Standards & Technology

Return on interoperability: the new ROI


In U.S. Capital Facilities Industry NIST CGR 04-867

Annual cost burden is $15.8 billion• $10.5 billion - owners• $5.3 billion – architects, engineers, contractors,

fabricators

The interoperability problems are caused by:• Highly fragmented nature of the industry• Continued use of paper-based practices• Lack of standardization• Inconsistent technology adoptions

Cost of Inadequate Interoperability


Information Integrity

• Maintaining Trusted Information– A structured CM program ensures that documentation for items is

accurate and consistent with the actual physical design of the item– In many cases, without CM, the documentation exists but is not

consistent with the item itself• For this reason, engineers, contractors, and management are frequently

forced to redevelop documentation reflecting the actual status of the item before they can proceed with a change

How much time does your Operational Staff spend locating [finding] and validating information?


Requirements Management

I temManagementDocument

ManagementEmail

CAD

Office

Web

ERP

CRM

Marketing

HR

Records Management

Closed Loop Change Process

eB-enhanced Configuration Management


Example 1

• Context:– An operational hydro-electric station– All drawings/documents up-to-date– Significant changes only possible during scheduled outages– Change comes at you from all directions

• Regulatory bodies changing requirements• Operational personnel making suggestions/requests• Maintenance forced to replace, rather than fix• Engineering planning to expand capacity

– How to manage all this change?


Example 1 – Hypothetical Changes

• Change Requests are logged in eB– CR1 - Operations requests more clearance around a Transformer– CR2 – New EPA Regulations governing reduced emissions impact

discharge System– CR3 – Maintenance indicates pump operational temperatures are

rising and predicting early failure• However the current model of pump is no longer available• Need access to original Requirements to determine suitable replacement

– CR4 - Engineering has Capital Improvement Project to upgrade Turbine #2 for increased capacity and efficiency

– CR5 – Operator notes drawing shows incorrect hand-wheel orientation on valve


Change Request Lifecycle

• eB Change Requests are objects to themselves– Each Change Request is routed for Review/Approval via an eB

Workflow– Change Requests may be linked to equipment (physical items),

document (document items), procedures (virtual items), and so on– Change requests will also be linked to the originating person

• Approved Change Requests are then added to Change Packages– Or, simple Change Requests may be acted upon immediately

• Such as CR5 which only requires a correction on a drawing.


Example 1 – Hypothetical Changes

• Change Requests logged in eB– CR1 - Operations requests more clearance around a Transformer– CR2 – New EPA Regulations governing reduced emissions impact

discharge System– CR3 – Maintenance indicates pump operational temperatures are

rising and predicting early failure• However the current model of pump is no longer available• Need access to original Requirements to determine suitable replacement

– CR4 - Engineering has Capital Improvement Project to upgrade Turbine #2 for increased capacity and efficiency

– CR5 – Operator notes drawing shows incorrect hand-wheel orientation on valve

Added to Change Package: CP1

Scheduled for immediate action

Unscheduled, to be included in future


Change Package – Impact Analysis

• CP1 is then routed for Review/Approval, and ultimately implemented

• Once CP1 is finalized, we now need to know:– What Drawings/Documents will be modified to reflect the pending

equipment changes?– What Procedures might need to be modified to align with

new/modified equipment?– Will Operations personnel need to be retrained on the new

equipment?– Etc.


Document Revisions

• When the Change Package is implemented…– All affected documents are versioned

• Previous versions remain visible to Operations personnel• But status changes to “Under Change”

– New Versions are unlocked, packaged, and sent to Engineering• Engineering might be in-house, but just as likely to be external

– At project end, As-Built drawings are created from the As-Bid drawings

• As-built drawings are then checked back in to eB, and supersede the original versions

• At this point, new versions are visible to Operations


Change Closeout – Records Analysis

• What is the Records impact from the Change Package?– New drawings supersede older revisions

• What is our policy for keeping the old drawings?– For the new Pump, did we already have any of those models within

our enterprise?• If so, then we should already have the operators manual within eB, and can

now just link another instance to it• If not, then we need to get that document from the vendor, add it to eB, and

link it to the new physical item– When we retired the old pump…

• Can we dispose of the Operators Manual?• Or do we still have other instances of that pump in operation?


Summary

• Information Modeling is about objects, relationships, and the closed loop change process:– A new regulatory requirement affects a functioning system– Which consists of physical items,– Which are described by documents,– And governed by procedures / best practices– And operated by trained personnel

Equipment System

Requirements

Drawing Procedures People


Requirements – A Closer Look

• Requirements are Documents?– No, but that’s how we receive them from Regulatory bodies

• However, that’s not how we manage them– Document level is not granular enough

• Because a single document typically contains multiple requirements– Within eB, a Requirements document is broken down

• Individual Requirements are modeled as Virtual Items• All Requirements within the Document are then linked into a Virtual Item

Group object


Requirements Example

• North American Energy Reliability Corporation (NERC)– Over 1,600 pages of standards for operation of North American grid– Divided into approximately 80 documents

• CIP Standard for Critical Infrastructure Protection– Documents CIP-001 through CIP-009

• Example Document CIP-001


NERC CIP-001 for Sabotage Reporting


NERC CIP-001 – Contains 4 Requirements


Information Modeling in eB

• Each individual Requirement modeled in eB– Then the requirement can be linked as appropriate

• To Systems• To Physical Items• To Locations• To Documents, etc.

– Thus it becomes possible to predict the impact of a modified requirement

• As opposed to a modified document


What we’ve done with eB thus far

• Electronic Plan Review– Developed data-model and workflow for City/County governments to

track plan review process

• Utility Owner Workflow– Developed data-model and workflow for Utility Owner to send

Change Packages to Engineering organizations for project work

• Capital Improvement Projects– Developed data-model and workflow for City/County governments to

manage their project process


What can we do for Comms?

© 2014 bentley systems, incorporated introduction to bentley eb enterprise bridge gary cochrane –...

Documents

incorporated eb

eb platform slide

bentley systems

eb platform object types

software platform

configurable slide

information modeling

incorporated introduction