Hello, everybody. Good morning. Good afternoon. Good evening, wherever you
are watching this video. This is IE 72 steps to a more efficient
Legacy migration. And in this video, we're going to talk about
various methodologies and tools available at your disposal
again. I'm ramamoorthy I've 20-some years of experience in this space.
I am part of Rockwell Automation production automation center of excellence in my prior
role. Being a responsibility is overseeing delivery
organizations and my current role me and my team are and
responsible and we develop packaged Solutions.
My background has a master's in electrical engineering
and the agenda today. It's going to be pretty simple at a very high level. If you have gone
through migration effort in some way shape or form
either Brownfield of Greenfield. It's not an easy path.
You got to figure out where you get started. What tools are available to you
the implementation methodology. Any overlap with
people your existing processes and technology
and Technology changes every day and now close it out with some commissioning
utilities. Should you use Rockwell Automation for commissioning what tools and
methodologies we use to Startup and commissioning system in a safe efficient
manner having said that let me dive into this picture here on the top left. If you see when
you go through migration effort, there are different entities. It's not an easy path.
Your corporate level standards your engineering requirements your kpis that has
to be reported and you look at your it systems and your enterprise-wide software and
Hardware has to be aligned with you. Look at the left side of that top
picture. What a local operator and maintenance in
person or an engineer has to do to do their jobs every day and also my greatest system
from platform to another platform in a safe Manner
and when you look at the instrument level you You either have to upgrade instrumentation
your it system or you keeping your marshalling cabinet or you rewiring it's
there are a lot of moving parts. And if you focus on the bottom left of the
picture, this is a typical project management methodology.
You wouldn't build a house without a foundation. So why would you go through a DCS
migration without a good definition of why you're doing what you're doing and
documenting and triage in your current systems.
So you start with a good definition and you go through your estimates. Approval processes
you go through your design a detailed design you look at the tools available the vendors
that can help you with migrating and then you have to do this with the idea of what you're
going to do for the next 12 to 24 months is going to impact how your facility is going to
be running for the next 15 to 20 years. And top right picture. You'll see
again the Purdue model on the left, right and the various libraries you have the process
libraries or what are your historian requirements?
Fireman stew if you're going to do to Edge Computing or the itot space.
I don't have anything replicate real plated to AI in here but sooner or later there's
going to be a column related to a i another way to look at the same methodology.
If you look at the person on the top and the checkered flag on the bottom, right you have
to worry about what are you going to reuse your panels?
What's your historian requirements arming methodologies? Do you want to optimize for?
Have cut over plan. And again, you're going to get an opportunity to migrate
your system. Do you want to replicate
asses or do you want anyway, what are you doing? Why are doing and how you
are going to do people are going to ask you
those questions when you go for and if you yell or funding for these projects
and then what options do you have the cyberspace
digital? Are you going to be know what your downtime is going to be?
Are you going to be okay with X number of days of downtime?
All those lead into what can we do as Raquel or donation to help you modernize your legacy
control system. You got to worry about your risk mitigation.
Your cost challenges behind every migration. I'm going to share a
quick PDF here as I'm as I'm loading this sheet up
as you're going to these migration methodologies, you're going to have
challenges in terms of the bottom line. Do you do you reduce
operational cost? How do you change? Or
production automation with business systems that can overlap with those.
So when you're done listening to this PowerPoint, you can download this PDF again.
You have to do it in a way that your scalable in what you do today
because there is always going to be an opportunity to expand
and you'll also have to worry about the flexibility of your system.
Are you going to be blocked then or you going to do it in a secure manner?
Those are things you have to worry about as you go through a modern PCS
again. These are some of the PDFs you will get as part of this that you
can take a deeper dive into these processes as us you go through
the next slide. I'm going to talk about the migration drivers
any time you go through a migration process. If you are one of
those individuals like me when somebody gives me a proposal. The first thing I do is I go
to the very last page and see what the purchase price is,
but then you have to realize there is more than The Upfront cost of migrating a system
on the left hand side. You'll see that Seven items listed there. Do I have to retrain my
operators something you have to worry about? What is the required maintenance requirements
for it? I'm going to be able to produce a better
quality product energy consumptions cyber compliance. You can you can dream the
list again. Like I said a few slides ago, whatever you do today, you got to worry about
long-term support in terms of operate and maintain your DCS system.
And if you look at the right-hand side, everybody is going to want to do it with
reduced. Smee reduce downtime reduce maintenance ability to interact with
multiple other information systems product changeover. So all this will lead
into are you doing it for the short haul in terms of looking at the price today
or do you want to look into total cost of ownership again
as part of this PowerPoint when you're when you download they'll be a PDF that talks a
little bit more about this by Quaker here in terms of how you compare the total cost of
ownership. Rdd-series system the easiest way to understand what what you have to do in
terms of evaluating is just not the initial Capital expense the maintenance cost down
time and the cost of not doing something you may get into a scenario where during a
referral process you might decide do I really have to upgrade again. You have to be in the
risk and reward Bike by delaying it a year what what risks am I taking on
that all leads into the Justifications of it which is one of the key
drivers of what we do from a migration standpoint
the next few slides after this. I'll be talking about our Fel / feet strategy.
What information can you use from your existing system?
Like I said earlier you want to do it proactively or do you want to do it when the
system breaks then you won't have any time in you're reacting to a situation.
You have to do it in a safe Manner and you have to improve operator awareness as
is you may very well know. Like every other company that is out there
you're all expected to do more with less and Workforce training and your ability to
maintain in training our Workforce and do things more efficiently is going to get
more and more difficult again. When you throw in the Cyber vulnerabilities like a few
slides earlier, I showed about the scalability of a system or debate is also how
secure and safe you are all that leads into how do you plan for these
one of the industry-leading?
Thought processes is a feed or an official process.
I'm going to be a little generic here considering the target audience may or may
not have migration background Fel in short form for fronted loading.
It is a methodology where you are doing the process in multiple steps like and I feel
what I feel to kill three the further down. You are your can narrow the
scope and you can make it more granular and you can narrow the
plus minus cost impact of it in at a very high level.
It's a justification process to go get funding.
It's a planning methodology with the whole idea of reducing the risks as
you go down the Fel process in the end of the day you want to do it in
the safest manner reducing the risks and this is a interesting chart. I call it
the dime dollar Grant chart what I mean by that is that the dollar symbols you see
when you start a process your ability to change your outcome
is very high and the cost to get what you want out of it is
relatively lower
as you go down the process and you want to change an outcome or change your controls
methodology or change the hardware software or whatever the case may be
as you wait further when you're in the design development phase
still going to cost you a little bit more but not as much as you wait towards the end when
you go into startup and commissioning the cost to change the outcome
is going to be significantly higher. Our meaning of the reprogram
redesign retest revalidate pretty much are doubling up on the
work and plus takes into account. All the Personnel that are on site that may be
waiting on others to complete their
scope of work. So the key a key thing here is as you go
through this process again, it's common sense, right the more you wait the higher
it's going to cost you. That's why I call this.
It's cos cost you a dime upfront or dollar which is in the middle relatively. It's a And
when you do it in the back end of a process, that's that's why when we say is Rockwell
Automation engage us talk to us. Help us help you in an Fel P type
setup. That's that's our methodology here. We want to help you do this in the most
efficient manner having said that we talked about the Fel
process in the next few slides. I'll talk about what are the DCS modernizations
strategies and implementation when you do go to a migration sale computerized Did your
Fel you're doing your feed and you want to 1 if you're wondering
how would I go about this again? You can click this link to get the pdf
version of it. There are many many ways to look at it. I
listed a few examples here. Do you want to do a hardcore Tower or do you want to do a cold
cut over meaning do you replace just the HMI and worry about the completely to the old and
the new system running in parallel and do of door cut over that way or do you want to rip
and replace or do you want to do a horizontal approach
where you take a say for? Sample a boiler system and if you have multiple boilers, do
you do all your boilers to together in one shark and terms of one
migration or you do you take a workable
approach where you take a subsystem take that subsystem down
and then migrated in one go from start to finish again.
Like I said earlier you want to replicate thing
keep things running asses or do you want to migrate again?
You're going to get one opportunity to do it and that's going to impact. Things that are
going to be running the way they are for the next 20 some years.
So these are some of the some of the things you want to think about and here is an
interesting comment as we were talking through talking to some of our customers is
we have gone through these processes over the years some of the customers comx
courts. I would say you need more than just good programmers. You need somebody process
engineer that understands the impacts the changes you have to understand what your
doing what you're doing and the second bullet is an example
where a customer said they had somebody come in and do a migration.
There were a bunch of religious e code from
20 25 years ago programmers Engineers didn't think they
needed the code migrated. It did not Port over
it created a minor incident again, when you're ignoring
deleting existing code look into it again. These are
common-sense approaches. But again, we have seen this happen in
Like so I thought it was important to share
again who you have in your team is critical
the right team will help you succeed. And the thing I've been saying the past few
minutes, right? What you do for the next 24 months is going to
impact what you're going to do for the next 15-20 years
like in the bottom. I have plan plan plan and bold and
repeated multiple times for a reason right? You got to plan your BC is migration. And you
have to have your smes you have up-to-date p&id is you have up-to-date pmpower PP of
peace is your I/O list up-to-date. What about your own definition documents and more
importantly. I have a slide in a couple of slides. I talk about the raci chart. If you
have no e.m. Somebody else doing commissioning multiple vendors somebody else
providing Hardware you want to make sure all your needs are
covered and there is no overlap or not not having to equal do the do the same task.
Gracie of who does what pain is going to be one of the key deliverables to
your success? That's why you need to have
good project management in your migration plans
again functional spec is a area where a lot of things are
ignored. One of the things we have seen on Legacy migrations
is how somebody thinks a process operates
is very very different from how the process can operate.
This is where your operator training and sitting with an operator to
understand and reverse engineering or primarily
interviewing The Operators to do a storyboarding will help
something we have learned as storyboarding also reduces your
screen counts where your you have a board operator that used to
control subsystem or system in a facility
with many screens by doing a good storyboarding and having a
plan to create various level 1 level 2 level
3 level 4 screens you can show Order now high-performance HMI is a 10-1
standard then
having putting screens showing redundant information. Again, the operator interface is
one of the
overlooked aspects of it. But in our experience we have seen that is
one area where you get the most bang for your buck as the storyboarding aspect with
operators. I talked about plan plan plan, right this
leads to what you need a project plan. You kick it off. You have a
plan and you budget things you make sure You have your definition documents all up to date
before you start going to a detailed design aspect before you start programming. Make
sure all your District official documents are signed off and
everybody is talking the same language. Then you go into
the development phase and one of the Man classic Rockwell Automation is we will never
deploy a system without 100% operator customer engineer
testing process Factory acceptance testing and we are proud of that. And then when you
go to site, how do you maintain and operate again the few things in bold? Here are some
of the key takeaways right before you start an architecture. Look at what
available architectures you may have for a small medium large DC is migration 2000 IO
5,000 I/O 10,000 I/O. So we have you don't want to reinvent the wheel and when you are
going through migration process, are there any migration reverse engineering tools that
can capture the information that's already in the existing DC? Yes to give it to you in a
user readable Word Excel PDF pipe format that you don't have to rewrite your
definition documents the previous slide when I said how your
system runs and how you think you run they run might be different
a good reverse engineering tool could capture a lot of those for you to make better
decisions. And again, like I said who you have in your
team is important don't rush. This is the next 24 months is going to be back what
happens to the next? Fifteen twenty years. I have a good racy.
Make sure you have reverse-engineered documents. Make sure your DCS and
visualization teams are up to date on when they are ready to start programming
don't start your development work until your definition is all complete again.
It's all common sense, but you've seen mistakes that happen when you're in a
fast-paced set-up that sometimes we skip a few steps that always comes back to bite us
last ps/2. Team continuity.
This is something we believe and we we institutionalize our processes within
our engineering community. But there is also an individual aspect of it
that somebody that was part of your development
programming scope team. Did they go and complete the startups of
those opportunities? We have seen a lot of
efficiency gained more importantly. It's not the skill level of the person then.
As much as the relationship you build going through the development processes or many
many months with a person either on the customer side or a
person on the Rockwell Automation side those personal relationships help a lot in the next
example is just the left hand side of the screen is an HR, but it's a racy.
This is a this is a racy from a real world project of the customer working with the
supplier with various vendors and any PC and Rockwell before we go in the
You want to identify who's responsible for what and who's accountable for what again
developable dresses. Just wanted to show the screenshot as
this is this is a typical ratio on a midsize project with automation scope and you want to
add other Scopes over ease into it
a digital piece again, this can grow again. That's when the program management
aspect of multiple vendor program multiple
vendor coordination comes into play.
Having said that we talked about the Fel
again. I want to take a quick second to to answer this question that comes up many
times. When do I need a field which is going to do I
need an Fel.
I'm hoping this chart would would boil that down
feed in many cases. You don't have a lot of information. You need to Define. Your you are
asking me to Define your A Chorus or your detailed design documentation
would say if we'd study typically provides the most bang for your
Lock and Fel would be if you're having a an idea
you wanted to understand. This is Can it can I justify how
do I get Capital funding? What platforms do I
have as options? Like I said earlier right people process technology the technology
piece of it what technology options do I have to
accomplish what I want to accomplish to make my molecule that my
customers would want to buy your orders and demand for Or
are we going to reuse my iOS there are am I going to do rip and replace? What am I
construction execution timeline things like that.
You would need you to I would say you need an Fel
in many cases. We have seen in Fel lead into a field study.
Once you go through a pilot and your your seed idea has taken shape and
the seeds germinated into a small plant before it becomes a tree. The
field study is critical it leads to a successful execution.
And you can have multiple multiple Fel 3 is happening in parallel. And this chart. What I
want to do wanted to convey is if you select a platform you don't know
what platform you want to go to Let's assume
you want to select blank. Eax. And if you don't have standards Define, this might be a
good time for you to start defining your standards as part of your
Fel feet process. If your p&id is a nihilist or out of date guess what starting with an
accurate documentation is not going to give you accurate results. You might you might be
better. A off spending the time to get that sorted out and when you have
multiple faces your you can do
multiple if you threes in parallel, and all of which would would lead into a
design build maintain operate philosophy
gained a lot of you're seeing this on demand. You may not be at automation Fair. However,
I'd like to point out after the fair you if you get an opportunity to go download I
recommend Scott Hayes for my team is presenting on IE 22 about PCS Macs the
Few slides I talked about eating he take a deep dive into
those methodologies digging into those experience.
He's a he's a global industry lead on the chemical engineering space on my team.
Now that we've talked about your feed process your Fel process and I briefly talked about
true love would like to double click and take a deeper dive into
various migration tools that are available on Rockwell deliver projects. Let's assume
you're on a complicated these yes solution. You want a cabling solution meaning can I? My
allow existing I/O to be maintained talking to Modern PCS or can we
have a methodology where we can replace existing I/O in a matter of minutes.
What does the best way to use various conversion tools that we may have go from a
platform to plantview XM terms of reverse engineering to understand what I have
running. So this is a screenshot of a couple of slides of what Rockwell Automation uses
today in terms of our migration Solutions. Crawlers of cabling solutions to
make sure we migrate you in a safe efficient manner
couple of things. We consider when we are going through these reverse engineering
record. Your data has to be normalized in some way shape or form
you were to create reports to make sure everybody's looking at the same information.
Your graphics has to be cut over in some way shape or form either.
You don't want to keep Legacy displays you want to identify aspects of Animation that
you want to bring over yet. These are some of the Aspects of
reviewing existing configuration
either from a configuration template standpoint existing
programming logic from a legacy system. Even from the visualization standpoint. Again,
like I said, a few minutes ago is a 10-1 standards of high-performance H my
from a graphical display in the modern PCS. Would you really want the
graphical representation looking at this or you want more of a gray scale
with alarm rationalization built into it
and I think it was my second slide. Third slide very short person from a starting point
when ending point to the checkered flag, one of the things there we talked about was
alarm rationalization. Do you really want an alarm page with 3000
alarms that nobody pays attention to you are going to get an opportunity to Define your
system. So you're not in that position anymore
having said that I'm going to jump into this slide here where we talked about a few km
platforms things that will allow you to migrate either with Allen-Bradley. Yo-yo to
be removed and minutes or keep the I/O and plays sometimes not require any programming
in some cases preserve feel termination. Some of these are cabling Solutions some of
these are data connections again for some of you that might be at automation Fair. Feel
free to attend Chris King for my team is going to be talking about what I mentioned in
the previous few slides of our migration modernization cabling Solutions, and if you
are remote feel free to download Cuz detailed or pointed PD 45 the talks about
it and Chris is about 40-some years of experience in the space with roklive and
other oems and he maintains our tools and migration methodologies. We accept that so
far. What all did we talked we talked about. How do you go from point A to point B, what
are the definition process is used for next plc-3 standpoint. What are the tools
Solutions available? Now you have hopefully have all your documentation ready to go you
understand where you are. Are you understand where you need to go now? It's where the
rubber meets the road is. How you going to go about implementing Your solution.
I'm not going to talk a whole lot about implementation other than a few high-level
tools and guidelines. This
is a simpler way to say if I were to simplify the slide into one sentence
making things complexes easy making things easy as contacts when you when
you're programming a system or defining a
Launcher reduce the complexity feel free to take advantage of the plan pxe
MEP structure that you would get if you are
and if you're if you're interested in this use building blocks meaning as there are a
collection of
control modules equipment module so on and so forth
if they are spread across your entire facility,
they all look and feel the same think about the advantages right
troubleshooting is easy programming is easy. If you have to make it
weak you can apply those global objects globally
across all your operations when it comes to maintenance
2 in the morning when your maintenance team wants to troubleshoot.
It's easier from a training standpoint. If you do have to call in somebody that
implement the system it is easy for them as well. So
from an offer a term eaten in scheme standpoint reducing complexity in using
repeatable building blocks is the way to go in our opinion
the second part be real there are there are things that when you when
you have in terms Ownership standard maintenance not everything can be repeatable
gather input from people that are going to maintain the system
run the system. And before you go
big Large Scale Pilot it pilot it on a smaller lower scale work out
the bugs and then expand and
deployed globally one of the areas where we found a huge
success working with large customers enterprise-wide starting a pilot.
Improving the process as you go further along
involving Engineers operators maintenance across the spectrum of people from the
customer side. And then from our Rockwell Automation side, you pilot a
small subsystem you started up you make sure
everybody is signed on bought into it. You're playing the right people and then rinse
repeat across the entire ecosystem rather than taking one big bite
you you take multiple small bites and the advantage
That is you're not you're not
stepping on a landmine write a paper cut is livable then if you step on a
landmine in the last piece, there are a couple more
slides on implementation best practices before you start.
I talked about architecture a few slides ago, right go to go to your local automation
website or your Tech connect and download or get in touch with your
broccoli sales representative or your project manager. What
a keishon tools do I have Do I have a small medium large go by
architecture that I can download? What can I do to reuse industry standards that may be
available from Rockwell what pre-engineered class base code? Can I use this helps
especially in a validation validated set-up lifecycleiq as I'm going to show a quick
example on the next slide on what we mean by this as a Rockwell Automation lifecycleiq
has delivered application the bottom of your screen. You'll see these the
hardware, right? Logix USC or flexes and the plan b
x libraries that come out of it. They'e MEP modules and control modules that
that you build into an application when you use a scalable application either plan PX or
our Premier systems library of objects are maintained by us. We use application called
manager various code generators tools to get the controller code the graphics the
historian tags, if you look at a typical screen where there are
the bottom right part here where you see there are
many many individual objects. Let's assume one of them is a reactor
reactor may have 15 20 different individual objects.
We have reactor block you're better off throwing the reactor
blocking your screen as you're building these applications rather than having to recreate
those blocks the scalability helps with
testing helps with operator training helps with
releasing your products on time. Having said that I
want to give a shout-out to come Lanham again, feel free to download. This
presentation. Tom has bought 35 years experience
is the mining application lead and he'll be talking at automation career. But his
PowerPoint in his Decks that will talk in more detail of a lifecycle
Services delivered solution will be available for you
the last couple of couple of other slides for you to think about as you're going through
migration. Strategy either by yourself or with a vendor or with Rafael automation.
These are some other questions some of these I have hinted in my previous
slide use the E MEP methodologies repeatable building blocks.
Like I said earlier make sure your system is
characterized. You don't want to put four pounds of Hardware or software code and a
1-pound bag and then understand do not understand why your screen updates or slower
why you have wireframing follow the SATA procedural motormonitor?
We recommend that you don't have to be in a batch facility, but that helps with your
flexibility helps with maintenance and helps with
optimal execution in some cases faster execution
the other part before we get into commissioning. I want
to pause and quickly summarize where we have
come so far we started off with saying understand where I am and where I
need to be
do I need a feed or an official or both? What does Documentation is do I have if I have
multiple vendors, what are their soon Lanes who's responsible
for what and who's going to do what when
what automation tools do I have to reverse engineer? What cabling Solutions do I have to
migrate? And if I'm going to use OEM tested blocks,
like I said, the building blocks are used example. I use a few slides earlier view you
want to re-interview her D1 use somebody else's building blocks that that are
validated tested and ready to go bring your Operators in for testing you
involve operations and maintenance during definition design phases of your project
pilot it before rescale big reuse I/O when you reuse existing I of possible if
it is not outdated one of the advantages you have it's a phased approach. You can always
go back and change your I/O Solutions later. If you don't have to rewire even better
reduces time where you have to have feel labor come in and rewire, which means you
have to retest every point and all this leads to how are you going to
commission this whole thing after you gonna feed study your
definition documents complete your factory acceptance is complete. Your code is ready
for commissioning want to talk a little bit about commissioning
methodologies Mark featured here leads our Field Services
support Rockwell
Automation installation and instrument service instrumentation Services team here in
North America this team primarily focuses on Decommissioning aspects of our installed
product and this slide I it's shouldn't be surprised. I told earlier
the dime Dollar Grand example right on the x-axis your project timeline
and the y axis you have cost spend the capex is green and not X right as you're
going through these processes. Look at the two vertical dotted lines the the furthermost
one and the one in the left, right? The more it takes to deliver if you delay let
me rephrase it. If you delay the start of commissioning from your schedule start-up
further. It's going to cost you more in terms of your comx cost. The risks are going
to be higher because which means you did not do something right along the process that
you're delaying the start of because you're not ready or when you go to site and when you
have completed everything you need to complete either you're mechanically not ready
or electrically not ready or you're behind on construction.
Now we have all these screws craft labor Engineers programmers. You name it waiting
on their system to be ready to start commissioning
that Gap is going to add up
the example. I used is actually learned it from a customer of ours think about her 24/7
facility. Most facilities are 24/7
your cost of not running for an hour. Let's say is a hundred and fifty K
150k downtime on a 24/7 facility for 10 days. Days is
30 some million dollars. That's that's
I got it acts up. Right. So that's the cost of not planning right here. You might have
saved a few hundreds of thousands of dollars, maybe even
a million dollars up front by skipping a few steps, but they always come back to bite you
in the rear end on the back end of the process. So
that's the message. I wanted to convey in the slide is
you're always going to have some breastfeeding from a cap action point or a
delayed start up from a topic standpoint or when you're not ready
mechanically. Typically, it's always going to delay an impact production, which is not any
one of us want to be except that what can we do to help you when you go into commissioning
it's common sense, right you use the latest and greatest I/O
information how you started the project with your ion formation.
Yes, I opens change. I'm not seeing a single project in my experience where you start with
the set of I/O that never changed all the way through commissioning same thing can be said
to be an IDE same thing can be said to definition. Documents so all these documents
that come out of your factory acceptance testing.
I hope they are already lined or updated will feed into or should feed into your
commissioning input meaning person wiring an instrument calibrating instrument has the
same information as a programmer that connect the that
ADHD I/O our users you're used to the structure to configure the iPhone make sure
everybody's looking using the same sheet of music so to speak
that leads to what can Rockwell Automation installation and instrumentation Services
bill for you sure starts the methodology that we use from a planning standpoint Greenfield
or wrong field outages or turnarounds from calibration standpoint or insulation
standpoint for commissioning start-up and construction management, and I talked about
static testing and commissioning just to get everybody lined on the terminology of what
restarted test is static and freedom Acres the first torqprove
Before you have energized the last two or upgrade energized more importantly. The last
one is where you have to make sure every step and every box on the right has to be
happening after the Box on the left of that has happened. Right? So you want to make sure
you're mechanically complete electrically wired verified tagging. But if I
instrumentation you energize you simulate your stroke growls, then you do water runs
before you do interlock testing. So on and so forth. So this is one slide where
Thought convey is a methodology. If you're trying to understand how we would execute a
project or how what what we would recommend how you execute a project. These things are
the things we expect you to do the office. These are things we recommend we do on site
there are few things that can interchange but majority of it is this is our recommendation
and when I say we used a few terminologies, those are rocker lot Nation
patented words estart ensure start itself.
Digital commissioning tool so we've been doing this for about seven
eight years deployed large-scale. It's piloted before 2016 first
acquired large scale in 2016. It's a paper is commissioning in our
experience using these methodologies to see
a 50% reduction in savings and time spent and so on and so forth that you
that you can create in the the bottom of my chart here.
And I'll show a few more screenshots on what those entire visisight a screenshot you go to
you pick an instrument these these information is already loaded if you are
attacked with an iPad in your hand trying to start up for check out an instrument. You can
pull up the instrument tells you where it is located what this instrument is. What is the
current status before faces restart ecstatic Credo Namek Dynamic with State you are on and
every technician that's on site. I can use this again. We use the word on my
previous slide OTS off the shelf. So you don't need a special
million dollar equipment to do it. It's a web browser based. You can do it on
your iPad or your phone syncs up in Google Maps for location tracking
you scan the device you make sure you are on the correct device. You can pull information
about the device have a dermoid the backend of this deck that it's about a 4
minute demo that we walk through you can plop schematics and more importantly.
Lee it's stable yet. It is configurable what I mean by
that
is this platform gives you an opportunity to add a new tab if you wanted to add a new tab
here to do something specific maybe JS a sidewalk type activity for specific area
of the plant or
type to any specific safety instrumentation. You can configure those
again. This is a screenshot that talks about it
a couple of more screenshots and different days is this one is a static check. What all
it entails. The device this one is a pretty Dynamic test. What all have you done again?
Both, these bottom boxes can be configured to your case and you can't empathize it and
reuse it for your next project or if you have a multisight installed and you want it all to
look and feel the same. It can be reused and promote template
again the key takeaway from this is 12. Meaning your red lines can be loaded into the
shore start methodology start document.
They can be viewed by technicians. You can read line at you can
flag it if it is not ready and more importantly on the next slide. I'll
show you a barcode right every single instrument that we would commission would
have a 3D barcode you scan the barcode it pulls up the information on the right. You
can get status associated with it. You can get details on where you are. And if
you are attack maintaining an instrument and you see a couple of instruments next to it
that are ready for your static testing or dynamic testing.
You can go down the process of claiming the device and completing the
process. This is where when I say it reduces downtime. You don't have to wait
for somebody to tell you that go commission this device again, it reduces paperwork
instead of carrying multiple binders with hundreds and hundreds of pages.
It's all in a tablet and the key the key thing that we liked
the story I use is if you go to a shopping mall and all of sudden you get
ads on your phone with some Store trying to want to sell you
something either through your phone.
It's all tracked by GPS technology. Right are ours is very similar, except. It's on an
instrumental. You can align it with
latitude longitude for every device. If you don't know where a device is this could take
you to the device helps you with commissioning lot faster
commissioning for GPS positions.
Again, this is a type of report. Like I talked earlier right
there. Where is the accountability when you want to know?
Big W when calibration data, this is a sample of a report and in some
cases you might want signature
the demo you'll see that as well. We're an operator or an engineer who were
custard the device would sign off that
this person he or she verified these 25 different things that you
wanted to verify an interesting aspect of okay start it can
also be used during development stage when you're in an office.
You can load a specific. Narrative or a sequence of operation
or an IO list update or a task within a project plan.
You can template eyes it in and you can give it to an engineer or a person program or
or by definition documents. You can exchange that back and forth with the
customer there is sign off and if things were changed
you can put it on your comments on what all
was changed and what all was approved with exception what all was not proved what always
changed could gives you a good paper trail in terms of Think things
the last piece again. This is a version of a completion status of a project
just a screenshot here to give an idea of what you have. I'm going to have two more
slides and then we jump into the demo here in terms of e star again. Like I said, it's a
digital commissioning tool you can customize it and understand location information. You
can put GPS information. The ability to work offline is a great feature that was
added relevance. Recently many cases if you are in a multi-storey facility or in the
basement with no Wi-Fi. Guess what you can still walk away with your
iPad with all the
information program. Obviously, you won't get real-time updates.
But the moment you walk over the building toward next closest Wi-Fi. It sinks. So there
is one truth when I say that that's what I mean.
We have ability to upload and download from Excel
into e start. So that is a plus in the key thing there.
Many times when you're going to commission a model because questions people ask us
how ready I am. I what's my percentage complete your morning
toolbox meetings are evening shift change meetings. Everybody wants to know what has
been tested. What does not been tested issues your pad
instead of relying on somebody's memory to forget something.
Everything is documented where you get 100% alignment
very good turnover, very good.
Pretty much complete nests from construction mechanical electrical standpoint.
It tells you good story and more importantly when you're done with
it. You can PDF this information and send it to
everybody or store. It makes it that this is my last slide and we'll jump with the
demo here after this one in summary.
This is off the shelf technology its Hardware software agnostic you get
real-time updates on Startup timeline, you get very accurate reporting.
You're not mechanically ready. You will know so you can delay
your crew coming into sight to do the work and what we have found the next. Two bullets
where the key in my opinion during uses the
amount of rework exponentially it improve rib reliability and quality when something was
done you really nude was done and something was not ready and was ready to be reworked.
You knew what it meant. And then last piece from a compliance accountability depending on
what type of facility or running you will know who did what when your typical water
Trails go faster, you've tested every logic alarming text or
complete so on and so forth, so Again, thanks for the opportunity. We jump
into the demo and I'll take over after that.
First screen that you will see when you enter the Easter application is a list of currently
active projects to access the project simply click on the
row. Once you've accessed the main project page,
you will see a list of devices or I/O for this project to access the device simply
select the device itself. You can see at the bottom of the screen. There's a list of
checklist. This is kind of the main data collection piece for the application.
The checklists are configurable by device type So
currently we're looking at transmitter we can see the information is collected for a
transmitter and the checklist. Are performed during commissioning of a
transmitter? If we go to a different device type
such as a drive we can see that the information collected for
a drive is different as is the checklist for driver also
different not only are the information that's collected
for transmitters drives different. This is configurable between different jobs. So
if we go and pick a different project such as
this test Here we can see that the information that's
collected as four drives DC drives is
different. The checklists are different on this project.
So it's highly highly configurable.
If you want to look at some of the features.
That are inside the application we can look at
there's location awareness. So you can update the GPS coordinates
and you can view those coordinates on a map.
You can add and remove documents
documents are stored in the central data store. So
you can have documents with the same name to access a document you simply stuck on the
link you can Look at PDFs or
images and to add those images you simply
drag and drop into this box here.
The another feature of the application
is besides all the data that you can capture is signature capture
so we can capture sign off on a commissioning stage.
Because we know how different every job is
this application is really been centered around configuration
and checklist are extremely easy to add simply by going to the admin page.
You can select checklist and you can create your own checklist
for example calibration.
Bration, and we'll give it a
calibration.
And we will add a control and we can say if the text box
and drive name
we can add any one of these number of controls checkboxes
as a safety
inspection performed.
For dropdowns radio very simple to add
will say Drive type
manual. automatic
and then we can save this put a different color
will save this and then the next step is simply to map
this checklist to a device type. So we'll pick a transmitter
and we will say that we want this calibration to show up.
And when we go now to our devices we pick our transmitter we can see the calibration is
there so it's really easy to add checklists on the
fly in order to get some reuse other things that
we've done include the ability to export these
templates so that you can reuse them from Project to project
you can export all the data in the project. You can re-import and all of the import
export is done through Excel. Miles to make it extremely easy to get
information in and out of your application without having to
use third-party tools. Everything is available through the application itself
due to its highly configurable nature. Not only can it be used for just commissioning an
IO list here. We have a sample that's doing a project
safety assessments and you can see that the
pgs a information is captured in the same way that a
commissioning checklist would be basically to fill out the form
and we can really use this for just about any application data collection application used
in the field.
Of course, the application also has all of the
Reporting aspects that you would expect on a typical
project. So completed devices. There's a bunch of
dashboard tape reports with graphs that show you
percent complete and kind of where you are in the project.
And that's a brief overview of the estart application. Thank you. Welcome back from the
demo. I hope that demo was useful to visualize what I try to convey in the
previous few slides East or short start methodology is more than just a commissioning
tool. It keeps track servile. Keep track. So programming keep track. So for example
flexibility with using your job safety walks and things like that those aspects of the
project from a feed to an FPL all the
Through commissioning. We are having a voice of customer session
that we are going to talk about automation pair but for people on demand feel free to
download the deck cd18 to know more about how does these subsets of these
slide deck was put into use with Con Edison and Russia and Alex said and myself are going
to be talking about it and other four points summarizing that I
referenced other sessions that if you are interested in either decius mixed methodology
IE 22 from Scott Hayes. Or if you're interested in IE 72, which is
this one the voice of the customer, and if you want to know more about our power
offering with lifecycleiq Services IQ, feel free to download these decks listed here.
Again. Thank you for your time, and really appreciate the opportunity, and I hope you
saw value and what we talked over the past few minutes.
Thanks again. Have a great day.