
| 

|

|

|

|

|
Return On
Investment
When you build a system,
you need to consider both the hard and soft ROI. Hard
ROI is the measurable savings, either in staffing,
costs, or time. Soft ROI benefits, or intangibles, are
those payoffs that you can’t quantify or express in
monetary units.
Immediate Hard Development
ROI
One of the principal benefits of
ObjectRiver Master Data Management is an immediate hard
ROI in terms of reduced development time. After you
create a data model, you can generate the master
database infrastructure with the push of a button.
For the typical enterprise project, ObjectRiver
MDM generates over 1,000 files containing 150-200,000
lines of code. A project of this magnitude would
otherwise take a team of developers at least ten months
to create. And, the solution is tailored to solving your
unique problems. ObjectRiver imposes no constraints
or restrictions on the type of data you need to support
your business goals.
The modeling process
doesn’t require
programming, pilot projects, or prototypes, which
shortens the project design timeframe. Since most
companies already have data models, a proof of concept trial with ObjectRiver
MDM is a low risk verification that can quickly demonstrate
the value of a model-driven solution in your
project.

The Database
Access Layer includes:
- Relational database tables and stored procedures
- Business objects with standard
create/reaChartd/update/delete interfaces, eliminating the
need to write data mapping code and complex SQL
statements
- Object-oriented code that accelerates the
development of business rules and applications
- Automatic audit trails
- A business event factory for synchronizing data
silos and integrating applications based on data
updates
With this immediate hard ROI, you can actually
use ObjectRiver MDM to rescue projects that are behind
schedule.
Soft Development
ROI
What is the cost of
change? As your system evolves over time,
business requirements or industry regulations will
change the data model. In reality, the model is
constantly evolving, because you are always adding new
business codes and definitions. The ObjectRiver MDM
Model Compiler regenerates the entire system when you
change the model. This includes creating new
documentation that represents the business model as well
as the physical model.
What is the cost of picking the
wrong standard? Industry middleware
standards are not something that you want to bet your
career on. ObjectRiver MDM is completely database
infrastructure, and it works with all current Java-based
middleware standards. If you want to build J2EE, Web
Services, or JSP applications today, you can. If a new
standard emerges tomorrow that better suits your needs,
you can start building applications to that standard.
What is the cost of
failure? Choosing a solution only to find
out six months into the implementation that it has
severe feature or performance issues means that you need
to throw away a good portion of your code, if you are
even allowed to finish. Defining a model of your
information by building consensus among the people who
own and manage the information mitigates this risk.
Building a model actually proves that the problem can be
solved.
Hard Business
ROI
The risk of doing business with
bad information and the savings from automatic
auditing can totally justify the MDM solution for
a financial institution. Centralization also reduces
the duplication of effort that occurs if each
division builds their own solution.
Soft Business ROI
Though
the soft business ROI does not show up as a bottom-line
savings, it can be gauged by the efficiencies of a
system that responds to business transactions in
real-time. Soft ROI also manifests itself as a return in
intangible elements, including faster time to market,
competitive advantage, brand strength, and customer
experience and satisfaction.
Summary
The
real return on investment from ObjectRiver MDM is that
it provides a foundation for building world-class
applications that could not have been built prior to
this technology. With ObjectRiver, companies that were
previously building read-only operational data stores
can now build transactional, audited, event-driven,
master data stores. Instead of building a limited
solution that might solve one specific problem, they are
able to build a solution that adapts to their
ever-changing business needs.

JP Morgan Case Study
|
| | |