1. Introduction to Bentley eB Enterprise Bridge
Gary Cochrane – Information Management Sales Executive

2. What is AssetWise / What is eB?
AssetWise is a suite of interoperable applications and on-line services to improve the management and operational performance, safety, and compliance of infrastructure assets. eB
eB 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
AssetWise is all about managing the asset information throughout its lifecycle.
Key to the success of this initiative is a technology platform that embraces the ALIM strategy described by ARC.
AssetWise technology and products enable operator/owners to:
Increase the useful life and financial return on Infrastructure assets
Lower operational cost by improving operational efficiency
Minimize business risk associated with regulatory compliance

3. 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

4. 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

5. 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 …

6. The eB Platform – Object Types

7. The eB Platform – Workflow Engine
Advanced Workflow capabilities, including:
Branching, & parallel routes
Conditional tasks
Individual or group assignment of tasks
notifications
Time allotments for tasks
Schedule calculations
GUI Design tool

8. The eB Platform – Workflow Engine

9. 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

10. 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 Standard
And listed on the official DoD approved products register

11. What eB is NOT eB is not: Although eB does manage documents…
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

12. 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

13. 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

14. 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.. …”

15. Textbook Configuration Management
Contractual Requirements
Engineering Requirements
Regulatory Requirements
Requirements
What is required to be there
Must Conform
Must Conform
What our documents say is there
What is actually there
CM process enables the organization to maintain equilibrium between the three
Asset Information
Item Configuration
The Configuration management Equilibrium –
(Change Item, Requirement and Doc labels to suit audience)
What is required, what there is, what we say there is!
Requirements: Customer, Regulatory (Federal), Nuclear, Safety
Information: Knowledge capture, design specs, procedures, policies , etc --> Why was something built the way it was? -> If I want to make a change what will be impacted?
Deliverable: End product
Software Example:
The objective of eB is to manage requirements, things we work with and the data about them
Things (product, plant, business process) are created to meet a need based on requirements. The deliverable must conform to the customer requirements but also the specs (design requirements) must conform to describe support the deliverable.
What happens when a requirements change is introduced, we can understand what impact the changes have on the deliverable and the specs? We can ensure that the supporting information and the final deliverable reflect the changes. So if I pick up a copy of a spec of the UI and it doesn’t match the UI I have an information problem – the spec wasn’t updated to reflect the changes.
Adding information to eB we ask “for what” what – the “what” should be a document in eB – relating the information describing it/underwriting it provides context.
Laptop Example:
If I have a notebook and Dave needs to fix the laptop. He doesn’t say give me drawing A, he says I’m working on this what information do you have? And eB says I have a hundred documents on it – Dave says that’s too much – I’m looking just for drawings – eB can tell me ok - I have 5 drawings for that notebook – now Dave has 5 manageable pieces of information
Pump Example:
I working on Pump 1: eB can tell me its knows all about pump1 – what do I want to know the invoicing, QA history, drawings, the mechanic, owner, designer, etc. all entered and related under change management.
MENTION BI-DIRECTIONAL NATURE OF RELATIONSHIPS TO SHOW CONTEXT
Item
Functional /Process Data &
Information
Item Configuration
Information
Must Conform

16. Managing Information in Context
Equipment Asset
Requirements
Drawing
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
Projects
Location
Change Requirements
People
Documents
Distribution Order
Managing information in Context
CM emphasizes the functional relation between parts, subsystems, and systems for effectively controlling system change
It helps to verify that proposed changes are systematically considered to minimize adverse effects
Changes to the system are proposed, evaluated, and implemented using a standardized, systematic approach that ensures consistency, and proposed changes are evaluated in terms of their anticipated impact on the entire system
CM verifies that changes are carried out as prescribed and that documentation of items and systems reflects their true configuration. A complete CM program includes provisions for the storing, tracking, and updating of all system information on a component, subsystem, and system basis
= One-to-one/One-to-many Bidirectional ‘Named’ Relationships

17. Enterprise Citizenship
Financials
Collaboration
Legacy
Users
Enterprise Users
Collaboration
Visibility
Information Quality
Compliance
Governance
Change Control
Asset Maintenance
Human Resources
Program Management
Just by the nature of the solutions the AssetWise Platform is applied to, it will almost always require some type of interface to other enterprise systems. In this regard, we need to look at the platform as being part of an IT ecosystem that is tied together in a way that is dictated by the account’s overall IT infrastructure architecture. Sometimes point to point is fine, other times it will be a commercial messaging bus like TIBCO or Microsoft Biztalk.
In any case, the means to participate in these environments is by using one or more of the interfaces provided in our platform.
eB, a member of the AssetWise family
Information Management
Configuration Control
Controlled Docs
Records Management
Engineering Design
Corrective Action
Human Performance
Knowledge Management

18. 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
Indeed, a recent study carried out by the US Government noted that 40% of an engineers day is spent finding and validating information.
40% - That is a BIG number.
Is that you? Is much of your day spent looking for hard-to-find information?

19. Cost of Inadequate Interoperability
Bentley Systems, IncorporatedBentley Systems, Incorporated
4/16/2017
Cost of Inadequate Interoperability
In U.S. Capital Facilities Industry NIST CGR
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
© 2005 Bentley Systems, Incorporated© 2002 Bentley Systems, Incorporated

20. 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?

21. eB-enhanced Configuration Management
Requirements Management
CAD
Office
Web
ERP
CRM
Marketing HR
Closed Loop Change Process
I tem
Management
Document
Management
Item Management -
Item can represent a physical or virtual object, it could be a work breakdown structure in a statement of work, component lists, equipment lists, etc – could be anything your working on. Its that common denominator object that allows us to create and associate relationships between the context and the content. What ever the document object represents what is it about – then when I integrate with the LOB systems – I can tell eB I’m interested in this item and ask what information do you have – and retrieve current information from all related sources.
Requirements Management –
Provide different views of the system based on group/role. So QA view could be different from operations from maintenance from engineering. We can model it the way you want to see it. Ultimately the same content shown in different ways to different groups.
Change Management – Heart of the application!
Well defined STANDARDS BASED change management process built into the product. Institute a change management process, if you check something in and approve it and later you want to change it, raise a change request – this process captures the reason behind a change and the presents the impact of a change. We also support the idea of a fast-track process that provides for changes classified appropriately (low risk) to be fast-tracked to avoid a complex change request process but still adhere to change management to capture and identify changes.
Records Management –
Enables us to capture the document activity, events and history. So we can understand why something changed and when it changed. By capturing formal records of change we can take status snapshots and baselines and use them to compare past, present and future states. ALSO PROVIDES EASY ACCESS TO KNOWLEDGED CAPTURED IN RECORDS
Also enables you to define disposition rules how to be managed, sorted, classified, destroyed
Records Management

22. 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?

23. 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

24. 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.

25. Example 1 – Hypothetical Changes
Added to Change Package: CP1
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
Unscheduled, to be included in future
Scheduled for immediate action

26. 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.

27. 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

28. 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?

29. 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
Requirements
Drawing
Procedures
People
Equipment System

30. 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

31. 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

32. NERC CIP-001 for Sabotage Reporting

33. NERC CIP-001 – Contains 4 Requirements

34. 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

35. 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

36. What can we do for Comms?