Tip:
Highlight text to annotate it
X
Scaling up your PI System successes across your company can be difficult.
What works at one site might not work, or even make sense at another.
Part of the problem is that different sites,
even if they make the same stuff and do the same thing might have different instrumentation,
different names for the same thing, different ways of doing the same roll-ups and on and
on.
But there's help. OSIsoft offers the Asset Based PI Jumpstart to help you scale what
worked well locally to a global scale. It includes an in person workshop customized
for you.
For example, here's Jason. His corporate folks have set a goal to reduce global energy consumption
by 5%. He'll say: 'The notifications I built for my unit are saving us lots of energy.
So are the displays and reports. We have lots of different sites and they each have a PI
Server. Now, If everyone rolled out the same projects locally, we could hit that goal.'
So for example, anyone with heat exchangers could have the same maintenance notifications
that are saving so much energy at his site.
Jason also thought that sites that make the same product could find ways to save energy
by comparing their data side-by-side. And if all the sites everywhere tied their data
into the company ERP system, the visibility would make local sore spots react more quickly.
BUT! when he looked into the details, Jason discovered big differences in what each site
had chosen to instrument. And other differences too--different naming conventions,
KPI algorithms, engineering units. Even the sites that made the same product had completely
different views because the instrumentation was from different vendors, installed in different
decades by folks who made different design decisions.
Jason said' Yknow, I really need to expose the data in a way thats easy to share if it's
going to be useful to headquarters.'
This is where the Asset Based PI Jumpstart comes in. In the workshop Jason learned
to design a hierarchy of company assets with links to all the remarkably different sources
of data at each site. The model used templates to make things consistent, so that each similar
asset exposed the same set of sensors for trending, used the same names, and the same
units of measure. Calculations and notifications that had been developed in isolation were
now centrally defined with a template, and then applied to each asset that required them.
In short, Jason and his colleagues learned how to use PI Asset Framework to apply the
consistency that was required to share their data across the enterprise.
Now when Jason adds a piece of equipment, its sensors appear in the model with easy-to-understand
aliases that everybody can recognize. And the displays, calculations, and lab inputs it
requires are available without any extra work. It even appears automatically on the current
production reports. Every site can now use Jason's energy saving notifications and displays
by pointing his template to their own assets. It is a generational change to a more collaborative
and disciplined way of doing real-time data.
The Asset Based PI Jumpstart includes an installation of the latest PI Server version,
a 3 day workshop that teaches up to 8 students how to create templates and elements that
fit their processes, and a fully functional copy of PI Coresight so you can create
reusable displays right away.
The Asset Based PI Jumpstart delivers an elevation in how you use the PI System
to get what's important to you done.
OSIsoft has built the PI System since 1985. People use the PI System for many, many things,
but it comes down to connecting people--engineers, operators, analysts, and managers--to the
data that is relevant to them. And we do it really well.