Total Cost of Ownership (TCO) value optimization is nowadays the main strategic business objective in any kind of ERP product implementation ( i.e. either brownfield or greenfield). The key lever available to achieve the same is the server based HW architecture options for technical landscape architecture and should be baselined in starting phases of the implementation program itself. This ensures risk acceptance and corresponding mitigation w.r.t desired allocation of budget upfront and HW procurement guidelines between the implementation partner and the HW vendors.
OUAF Framework and ORMB Product Architecture
Oracle Utilities Application Framework (OAUF) based product installations, including Oracle Revenue Management & Billing(ORMB),provide multiple server HW architecture options to achieve optimization as per business needs. The 3 key drivers for baselined architecture are encompassed in “Architect Triangle” i.e. Availability, Performance and Maintainability.
The infographic below is a snapshot of the key OUAF framework benefits, architecture dimension triangle, OUAF Architecture Models and default ORMB product architecture.
ORMB Deployment Architecture Options
The infographic below captures the various HW server architecture variations for ORMB thereby clearly articulating the selection parameters, its advantages and disadvantages of the various options involved.
ORMB Batch Deployment Architecture Options
ORMB product architecture highlight is its Online Transaction Processing (OLTP) capability but its core strength lies in background batch processing feature, with numerous standard background processes supplied as part of the inherent product itself.
In the current releases of the ORMB, the batch component can be embedded in the online system or as an external component at server level. This is a crucial decisive factor in the baselined ORMB deployment architecture as per business expectations for final hardware solution w.r.t background processing. The infographic below shows the deployment options for the batch processing.
The final ORMB deployment architecture depends on the mainly on the service levels desired for OLTP and batch processing along with regulatory and non-functional requirements like performance etc. driven by business requirements of the customer. ORMB inherent architecture is flexible enough to handle the same as articulated above for Financial Institutions and Healthcare players.