Migrating and delivering data in a form that can be used by
data-centric systems is one of the most important elements for
a successful move to the SmartPlant solutions. Intelligent
systems can convert data to information, but this requires some
form of raw data to be able to function. This discussion of the
relationship between systems and data may seem trivial, but it
is fundamental to the successful implementation of any new
system.
Through the years, we have gathered many lessons learned during
data migration projects.
Here is a list of my top five lessons
learned:
When planning a new system installation, place a line item in
the budget for data conversion and migration. In our
experience, the migration effort can easily equal the time and
cost for system licensing, delivery, training, and startup. The
good news is that the investment will serve you for many years to come.
A former boss of mine frequently said, "Projects will come and
go, but objects (data) will last forever." Once migration and
data recovery have been performed, the result should be
considered an asset of the corporation. It should be secure,
maintained, and continually used as facilities are designed and
modified and decisions are made.
Create and migrate information once and use it many times. The
value of information is directly proportional to the number of
times it is used. Information referenced even once has real
benefit.
Always evaluate how information will be accessible by multiple
systems. Fundamentally, today's technical systems are designed
to look at the same plant elements - just different views. Make
sure that information is accessible across multiple platforms.
SmartPlant Foundation has a groundbreaking capability to unify
different information about a plant and the changes made to it.
There is tremendous value in SmartPlant Foundation's ability to
manage and publish information through multiple data systems.
The industry will continue to develop advancements to "glue" together
data centers.
Consider the role within your company for "information
engineers." Traditionally, companies have employed
system/application specialists, but now is the time to take
this role to the next level. Information Engineers are responsible for ensuring that information about their
particular specialty (rotating equipment, heat exchangers,
instruments) is being fully captured, retained, and used
multiple times.
The management track for the Intergraph 2003 IP&P conference
reflects the emphasis on "data as the fuel." The topics cover
significant challenges we all face as we define
data-centricity; the business value of integration;
e-collaboration in the 21st century; and the owner and EPC of
the future. The implications are clear: we must plan and
maintain our information with as much care as we have
traditionally planned and maintained our software applications. When we achieve this, companies will begin to see the non-linear
benefits that can provide a new competitive advantage.
Joe Morray - is president of Trinity
Technologies. For more information on content management tools
and Documentum, visit http://www.trinitytechnologies.com.
