How many today feel they manage the
changes to all their information
during a project In other
words are you confident that.
All of your as built information
is being kept up to date during
the operational phase.
No matter how small or large.
I imagine that this number is small.
But that is no surprise 'cause
it is a complex workflow.
So let me first define
what we mean by a workflow.
Digital workflows accord Bentleys
capabilities in a connected data environment.
The fundamentals of Workflow is delivered
by 2 applications that make up the CD.
Project Wise and I said Wise and
these are the 2 applications,
you will be seeing in the demo today.
Digital workflows are complete,
organizational process is automated
by a digital environment now note
the use of the word environment.
With a large business process
such as engineering change.
It often takes multiple best in class
systems to deliver an automated.
Efficient and compliant process and
you're going to see two of those systems
harmoniously working together today.
But we recognize each of journey.
It's the reason that such a small number
of confident in their process now.
You are all on this journey.
And only a few have got there,
but we as Bentley are here to help you.
So what exactly is the
purpose of this presentation.
Well, is to explain how the Bentley CD
delivers a digital workflow for engineering
change projects during operations.
I'm going to use some real user use
cases examples and actually then
show you the process in Bentley CD.
But first let's look at some
of our customers.
Understanding the importance of managing
their information during a change.
Or what we call in Bentley
management of change.
2 large oil and gas providers BP and Shell,
both use management of change
key to all of their plant.
Operations.
Ameren another nuclear power stations
within the USS all found this key to what
they care called configuration management.
And about to manage the configuration
of their plant and then sure it's
safe and working environment.
And then finally a large electrical
distribution company in the USA again
key to them is uptime reliability and safety.
And management of those
changes are key to their work.
But there's one similarity
between all of these users.
The risk is very high to them and they
realize the management of changes ascential.
To the risk of their safety and
operations so here's a few quotes.
You can't declare that you have
a digital twin with no digital
process to keep it up to date.
Also in 10 years time I want
a safe working environment.
I want to know then that the information,
I rely upon.
Is the right information?
Also my whole team sufficiency
is now improved because we know
the information is trusted.
Some great quotes.
But the key to managing changes.
Understanding the Inter related
information that there is important
information that you start with.
Witcher requirements,
you understand why you've
got to do something.
Then that relates then to standards
and then functional information.
The design information finally something
gets built the physical equipment.
Turn up with all their documentation and
information and all of this information is
related to their budgets and your schedules.
And actually it's asset Wise Alim
application is the key to put into
relating this and displays all
of that information in Contacts.
So one one thing changes let's
say federal requirement changes.
So you understand using all
these links between information?
What is going to be affected.
Asset Wise Allen provides a best practice
configuration management capability,
it addresses the problems of Information
Integrity in a changing environment.
And at its core is configuration
management practices.
They are simply there to
ensure that information.
Integrati is provided through a
closed loop change management process.
Starting with the requirements,
designing the information and the
physically ensuring what do you
have in place is what you need?
And what you designed and at the core
of all this is our management change.
So before we enter into some of these demos.
Let me define some of the roles that
have been involved in this overall
workflow that I'll be describing today.
You have maintenance, engineers going
out insight and physically doing work.
Aboard who overview the
entire change from above.
And then various engineers lead
responsible and discipline discipline
leads who review and as you do the
work itself changing the design.
Then finally and information controller.
She's the one who's responsible for
the information moving around the
system and the workflow itself.
So we enter into our digital
immersive asset in service.
Using the filters.
We look for any asset in an alarm state and
a pump was found to have reached a threshold.
1st we look at the details of the pump,
including it's functional and physical
information on the right than any associated.
Objects with the documents,
maybe in a limb or other operational
data sources.
The final we look at any events that have
been raised in this pump and you can see it.
Reached a sound and vibration threshold.
So we never know never get back
from the pump into asset Wise Alam
to understand more about the pump.
And gather its details.
So what happens next.
This linear workflow shows the early
stages of an investigation and then
the decision for a design change.
This early stage can be raised by asset
wise itself or using our interoperability
system interface with the lights at
Saps or Maximos to manage the work.
We've shown actually this workflow in
previous presentations, so please.
Contact me if you wish to see that,
but in light of time.
We have today I'm going to be
skipping out action one and 2.
So I'll set the scene for action 3.
The engineer has been on site and
as met with various other engineers.
And people.
The following conclusions are made.
The pump cannot be fixed and
it cannot be fixed in place.
There is actually no spare available that
meets the same functional requirements.
So the decision has been made to
start the process of a design change.
So let's have a look at that pump in asset,
Wise Asset Wise is full of
functional design information.
On what we call the tagged item that
intrinsically linked to an equipment item
populated but then supplier information.
On the physical aspects of the asset.
You can see the pump is manufactured by souls
are and it's used in various locations.
On the plant, not just the
pump were facing today.
You see its documentation.
Other information now if we go back
to the pump tag where we're a we
can now raise the design change.
We decide on the type of the change.
And then that decides the data and the
workflow the journey, it take some?
Now following creating the design
change itself.
We then take advantage of asset
wise unique object model built
on relating all objects together.
This is called affect analysis
and it shows all of the related
objects to that pump. In one view.
The pump was associated to appear in ID
and if we look at that PNI dot document.
You can see it's built up or
associated to many other tags.
And actually sitting within.
Other change packages and other projects.
And we'll talk about that later
supporting concurrent changes.
So I've decided this PN ideas key and of
course will change during this design change.
We've adding it as an effective.
Object.
And that then Add all the other tags.
To the overall change
and the effect analysis,
so I can then decide which ones
will actually be affected.
Here, the electric motor,
and also a pipe that's connected.
To the pump itself?
Finally, when we return to the change.
We then get a more complete picture
of the change itself.
There will be affected documents.
And the affected tags.
So we're still building this change
because we recognize that the
design is going to mean a new pump.
And completely documentation
are going to be needed.
We've decided to replace it and
actually not just replace it.
There's a bigger bigger plan
around the plant to upgrade it.
So we actually need a much
different functional specifications.
This means we create new tag numbers
and we do that using our document
and tag request system and we were
asking for key information such
as the project number, the system.
The type and even define a sequence number.
But most importantly when this type of
tag is created the system automatically
create all the relevant documentation needed.
And maybe child tags so he when
we look at this knew tag.
And look at this documentation,
you'll see a brand new data
sheet has been created.
And along with it.
A brand new pump motor 'cause,
obviously that would always
be a child of the pump.
So now when we navigate back to the change.
You'll see that these new objects
have been automatically associated
to the project that change project.
And you'll notice the 2 different
status is on the right.
Some of those tags that have been
affected or operational these new ones.
We created just now and a plan state.
No operational yet.
So let's have a look a bit closer at the
workflow technology with an asset wise.
This is just a small part
of that Workflow again.
Sorry running through, but the
fundamentals of the same for any task.
The task will be doing are
to review the workflow,
adding costs and timescales to the change.
Will complete those tasks and then
make a decision as to whether
go on a second review or maybe
just simply change approve.
Or then reject the change.
First, let me show you our
workflow system behind the scenes.
If you like we've logged
into our administrative.
Interface called director and
looked the Workflow Designer.
This highly configurable tool set
allows us to build role assigned tasks
in either series or in parallel.
And it can provide decision
making and also task rework.
Some of the steps in this workflow
control the information in the system,
such as the status of maybe the project.
And some of the steps manage
the automation that move and
synchronize data with Projectwise.
So now if we go back to the change project,
you will see the workflow attached
and look at the Workflow.
You can see each task and it's status is.
You can also see when we go
back to the change that.
You can manage his workflow using a
helper at the bottom of the screen.
The first task is to initiate the package.
In other words, ensure that all the
affected tags and documents are in
place and I think we can safely say,
we've done that now.
So we'll simply accept this
task and complete.
When I complete the systems ask
for a decision to be made when the
project needs to go in a full review.
And I say yes next.
I'll then move to the task and answer
more details such as the cost an estimate.
The duration.
When I complete you'll see the actual
state of the task is changed to proposed.
From Draft.
So when we go back to our workflow
designer you'll see the diagram shows
how the Workflow is progressing.
Yes, we've skipped a few steps,
but this is a demo.
But we're ready to implement the change.
The next starts tax or about
distributing the work for design a
user that is only using asset wise.
Not the full CD would have to return
to pour techniques of Transmittals,
returning back to the email age.
But with a bendy CDE.
It provides all of the workflow digitally
by synchronizing with Projectwise.
The client and then invite their
contractors to use their product wise.
To manage the project information.
I mentioned earlier,
but how is it wise managers concurrent
change and I'll explain more now after
now we've been building a project full of.
As built documents and tags.
These are object key to the
operation of your asset the last
thing you want is the plea project.
Project update and change you
will as operation information.
So I said,
was creates prototype copies of the
affected object so they can be changed.
As many times in the design
process is needed.
We call these change notices.
And when we reach a certain
stage of the Workflow.
These change notices or prototypes
are sent to Projectwise.
And a project is created along
with a project template folder.
Here you can see the template
folder being has been copied over
to this project and all of these.
Key prototype documents have
been passed into projectwise.
Next we then enter the world of
the contractor engineering design.
Various engineering disciplines
make them the changes to the
information within project wise in
their relevant discipline folders.
Project them wise provides review
workflows for these engineers to
review and then move the document
through its design lifecycle.
The final review is made by the
responsible engineer and the document
is flag to be sent back to us at Wise.
For the mechanical data sheet
of the new pump.
The user simply opens and
checked out the document.
He then makes the changes in Excel here.
I'm just changing a few attributes
but obviously they'll do a lot more.
And they finally save and close it,
which then automatically updates the
document in the project why server.
Now I'll be skipping a few review
steps due to the time restrictions,
but there's lots of great
presentations from projectwise team.
So, please have a look at those.
But finally the response will
engineer then does review.
He sets the final status and flags of
document ready to be sent back to us at Wise.
As the final State is reach
server In addition,
is automatically created
and both documents are sent.
The same process occurs for a PN ID here,
we're opening it in Bentleys
Open plant pain ID designer.
And the relevant changes
are made to the PNID.
The pump number is changed and also
all its functional information will
be modified to meet the new design.
And the same goes with the motor
and as with the Datasheet reviews
take place in the final response,
but engineer flags,
a document for synchronization.
And again the rendition is
created this time and I model.
So just to reiterate what is happening
the design files in fact copies or
prototypes of the as built documentation.
They made available in the project
folder structure in Projectwise,
where engineering modify the document and
run internal design review process is.
The response for engineer for the project
does a final check and the documents
are synchronized back to asset wise?
So we return now to the change in asset wise,
we can view these updated
prototype documents.
You can see then they have their
updated renditions in there
as well as their source files.
When they were I model rendition is
open you can view the tag the tag
numbers have changed on the pen ID.
As there.
Another example we can have a look at
the old tag number that was in the PNID.
And you can see that it's operational
status on the prototype has now
been set to removed.
As it's been removed from the PNID diagram.
On to the final steps,
but the most important in
terms of this digital workflow.
Once final sign off is done construction
can commence and during construction,
the azbill information can now be prepared.
For update. This means preparing
knew as built revisions of the
prototype objects ready to have
all the new information merged.
Into them when the change is closed out.
So from a technical perspective.
This is what we call implementing the
change is not just clicking implement
expecting something to happen.
As well other kinds of projects might
be running at the same time on the
same information or concurrently.
So it means each time information
is implemented you're making
a decision to lock that.
Information and the future revision
for the next as built revision.
It is very important that this is done.
Right at the end of this workflow
to minimize the impact then
of other concurrent changes.
And implementing takes into
account then the status is and the
importance and most importantly,
all those other changes that occuring.
In what state is they're at?
So if you look at the bottom of the screen.
You can see the Workflow
Helper is telling us.
Ready for implementation.
This time, the information controller
is informed they have work to
do in the except the work next.
They choose to implement the
change and then required to state.
Which documents and tags and want to
implement just as if they want to come back?
The users then taking through wizard
for each object that shows each
document and what concurrent change
request are currently running.
If any requests are also approved
or in design,
they can choose to either wait
until they are completed.
Carryover or implement then these
documents and tags on this project to
create a new revision to bind to the change.
Now, when we return to the change.
You can look at the progress talk topic,
and you see an extra set of columns in
the right providing a picture of the
entire implementation decision so far.
On the far right or your new
revisions that are locked to this
change in the middle of prototypes.
And at the start the provisions
that have been copied from.
The implementation occurs
during the construction phase.
Change the project to expect it and
so they continue to be modified and
the prototype continue to be updated.
Once construction is complete,
so we completely implementation to ours
and enter into what we call project
closeout for this workflow we've
chosen to automate merging all of the?
Current prototypes into the news,
but revisions when the the task is closed
out some users choose a different workflow.
And that's up to you.
So we're now looking at these knew as
built revisions when we click on them.
So you look at one of those old pump tags.
The old motor and now in operations,
the live revision.
Is now removed?
And if you look at the new
associated data sheet to the tag.
It's now totally available to operations.
It is the next revision and you can
see all of the information that
we entered is ready to be used.
Finally we complete.
And then closeout that the change.
The change is now available as a
complete ordered of the project
showing how the information is
changed from its original revisions.
Through the changes made to prototypes
and then the new physical changes to
the plant in the as operated data.
So, In summary.
Bentley CD automates what is a
very complex business process it
provides consistency in the workflow?
And therefore control to ensure
that you have a constant digital
performance twin in place.
It moves away from any uncontrolled
inefficient email process is.
And then audit all of the changes,
reducing the risks and increasing
therefore the assets safety.