ODS Product Overview
The Operational Data Store (ODS) of OIPA provides the capability to access records in the OIPA database (i.e. duplicated dataset from an instance of OIPA) without directly impacting production data. This is a on premises installed capability and allows expedient access to policy data for reporting and analytics. The structure of the 'Data Analytics' tables mirrors the configured customer rules and data schema and is not simply copies of the base OIPA tables.
Key Features and Benefits of ODS solution
In the current state, OIPA customers have no choice but to run the reporting and analytic interfaces directly against the OIPA database in order to exchange data with other downstream applications in a batch environment. This causes certain types of changes included in an OIPA upgrade to impact the interface logic and/or the downstream, which in turn makes upgrade projects too costly and/or too time consuming. This hinders customers' ability to keep current with new versions of OIPA.
It’s been determined that an OIPA specific data store supplied by Oracle and bundled with OIPA ('ODS') would help isolate the OIPA application database from the reporting and analytic interfaces, thereby making it easier for a client to upgrade to a particular OIPA version.
ODS Architecture Design Principles
The system architecture has been based on the following design principles that establish a consistent set of rules and guidelines for the design and development of the system:
- The system architecture should have a multi-tier design with well-defined service layers to ensure flexibility and continued enhancement.
- The application should be multi-platform, portable, and scalable.
- The database access should be implemented in a consistent, database-independent manner.
- The database traffic should be optimized to the utmost degree to increase scalability and availability of the system.
- The presentation layer should support, but not be limited to, a browser-based user interface.
- The system should easily integrate with other technology components.
- The system should leverage open standards wherever possible.
- The system should be independent of OIPA versions.