Food for Thought
Asset Lifecycle Mgmt
Datamation universal Information Platform (uIP)
to software solutions what the assembly line brought to manufacturing of
Delivering business solutions the
Datamation uIP way
The figure below shows how a
Datamation uIP installation can be tailored for individual
customers' current, as well as evolving needs. Meaning change is effected without having
to go through major overhauls every time new technology comes along. What
is more, our modular approach makes the Datamation uIP scaleable to
support the smallest SME through to the largest multi-national
corporation, simply by adding new application modules, data modules or
Delivering value with the
Creating a tailored solution:
The Datamation universal Information Platform (uIP):
Provides general purpose functions such as
search, navigation, import (including validation and cleansing) and
export. In addition, it provides control functions that ensure that the
data in its database is always readily usable and fit for the purpose without any overhead to translate the data.
Add functionality that "specialise" the
Datamation uIP for specific application areas or industry sectors. These
modules are delivered by Datamation and / or its development partners
Tailor the Datamation uIP solution to the
exact needs of individual customers.
The Datamation uIP seamlessly fits
within installed infrastructure:
Facilitates input of data from external
databases or datasets. Imported data is placed in a "quarantines" area of
the Datamation uIP database. If necessary, validated and cleansed before
being approved to include in the database. This ensures the Datamation uIP database
integrity at all times.
These are packaged and / or bespoke modules
that synchronise the uIP with external functions. Furthermore, the modularity of the Datamation uIP database makes building of such interfaces significantly
simpler than traditional methods.
Help rationalise installed infrastructure and
continue to meet evolving needs:
A Datamation uIP represents the ideal
platform for rationalising existing installations as well as evolving the
solution as business needs dictate. That is, over time getting rid of "dead
wood" as well as adding new functionality. All this is done progressively
with minimum disruption to day-to-day operations.
not replicating all the data in these systems (as-is view), but only the
part from each that is relevant to creating the to-be master view, see
Our experience has shown that the business functions,
of any old system represents only a small fraction of the overall
functionality of that system. The rest being general purpose
functions such as data management, search,
navigation, reporting. With the Datamation uIP providing such functions, replacing the business functions of the old system can
be with a fraction of the effort that went into the development of the old
system. Furthermore, any migrated module removes
one disjointed system.
Create a holistic view of data held in disjoined systems (not shown
in the figure):
Migrating old systems is particularly effective with small bespoke
applications. Larger systems demand another strategy to reduce impact on
day-to-day operations as they may affect a large user base. Here we first
a "master" view of data from related systems, e.g. multiple stock systems.
Add new functionality (not shown in the figure): When new
functionality is needed to a uIP-Powered solution, it is effected by adding
a new packaged and/or bespoke module rather that customisation
of the uIP-Powered solution.
Retire old functionality (not shown in the figure):
When certain functionality reaches its "sell-by date"
the related module is simply retired.
However, the data created by that module lives on and is seamlessly usable
by whatever module replaces it.
Expand and scale up the solution:
Connecting to other uIPs:
Provides the ability to configure and
scale up a Datamation uIP to meet virtually any business requirement. For
instance, starting as a pilot in local area and rationalise the
applications in that area. Then repeat the process in other areas, each
around a separate uIP environment. Then connect the different uIP
environments. This approach provide local autonomy to the data, while still
conforming to corporate structure and governance.