Project Background
The Ontario Energy Board (OEB) stores both internal and external data, which is collected from many sources, including customer relationship management software (Pivotal), and web forms (HTML, ColdFusion, PHP). Data is limited to specific security groups, and reported on/reviewed regularly.
OEB servers are hosted in Azure and connected with internal applications such as Oracle Business Intelligence (OBIEE 12c, Product Version 12.2.1.4.0) and Oracle Data Visualization for reporting and visualization purposes.
The OEB requires a qualified Vendor to provide the services and deliverables required to migrate the OEB’s OBIEE 12c servers to OACS (Oracle Analytics Cloud Service).
Objectives
The migration to OACS is in line with the OEB’s “Digital-First” approach and Cloud Migrations initiatives. As well, OACS has additional features which will help enhance self-reporting and data visualization capabilities at the OEB (including such embedded machine learning and natural language processing technologies).
Purpose and Scope
The purpose and scope of the is project will migrate the OEB’s 12c servers to OACS. The OEB currently has 75 Named User Plus (NUP) licenses. In discussions with Oracle and during this migration, these will be converted to:
3 OCPUs of Oracle Analytics Cloud Service - 2 of which will be used for the Production environment, 1 of which will be used for the Non-Production/UAT environment as follows:
1. One OBIEE 12c Environment - Currently the OEB has 2 OBIEE 12c servers, which contain different Subject Areas and security roles/members. All other configurations are similar. The first deliverable is to merge the two.
2. One OACS Production - After the first deliverable is complete, the single OBIEE 12c environment should be used to configure the new OACS environment. All configurations, including but not limited to Subject Areas, Security, Catalog, Agents, and Usage Tracking should be migrated. Additional configurations such as Oracle Ask, Multi-Factor Authentication, Skin Customizations, and new features available with OACS should also be configured, in discussion with the OEB. The migration should be seamless to the end-users.
3. One Non-Production Environment (UAT) - Comparable to Deliverable 2.
4. Design Documentation and Knowledge Transfer - Design documentation, including configuration, maintenance, and performance monitoring details must be provided to the OEB, along with Knowledge Transfer sessions with the Network Analysts, Network & Security Analyst and Reporting & Database Analyst.
5. Live, Virtual End-User Training - Training must highlight the seamless migration, similar functionality, and additional features of OACS (such as Oracle Ask, embedded machine learning, natural language processing technologies, Auto-Insights, Explain, etc.).
The term of the Agreement is for a five (5) month term with no extensions.
Full details of the RFS document is available only through MERX at www.merx.com or 1-800-964-6379, MERX reference number 0000235132.
