Statement of Objective for Transactional Reporting Solution (Discoverer replacement) v1 09262019.Discoverer replacement

Enterprise Services Center

September 26, 2019 Statement of Objective for

ESC Enterprise Transactional Reporting Solution

Enterprise Transactional Reporting Solution

Executive Summary and Background Federal Aviation Administration (FAA), Mike Monroney Aeronautical Center (MMAC), Oklahoma City, OK the Enterprise Services Center (ESC) operates under the Department of Transportation (DOT) as a shared service provider for financial services and systems within the Federal government. ESC is seeking to replace an unsupported reporting solution.

Within the Financial Systems, ESC has a broad spectrum of reporting avenues, and ESC’s customers have an equally broad set of report consumption needs. Oracle Discoverer is the ESC customers most relied upon transactional reporting tool due to its ability to meet standard, flexible reporting and ad hoc data consumption needs.

ESC’s Discoverer is a web-based, on premises installation with access integration through Oracle E-Business Suite (EBS), version 12.2. It currently contains approximately 55 subject areas, 2,000 folders and 45,000 workbooks. ESC’s Discoverer supports approximately 2,000 active reporting users, of which, roughly half construct their workbooks. The execution rate for reports is 3,000 per day and 65,000 per month. Reports vary in complexity but are predominately tabular data results with a small mix of crosstab, or pivot table, layouts. ESC’s Discoverer End User Layer (EUL) is primarily based upon the Oracle Federal Financials EBS and Unison Procurement Request Information System Management (PRISM) data model designs with some custom folders included for specialized reporting. While these two data sources are noted specifically, additional sources exist.

Problem Statement With Oracle’s de-support of Discoverer, ESC has a need to replace its current reporting solution. The solution must provide, at a minimum, the basic reporting capabilities of Discoverer. The primary use of Discoverer for ESC customers includes: 1) Pre-Built reporting, and 2) Ad-hoc reporting.

Objective Statement The primary objective is the implementation of a transactional reporting solution. It will be required to migrate all of the ESC existing Discoverer EUL components and workbooks to the new reporting solution. The solution must maintain the existing security, including user, EUL components, workbooks, and data fields.

ESC is seeking consulting services for implementation and training of the proposed solution.

Assumptions Consider the following assumptions in response preparation:

· Solution can be either Software as a Service (SaaS) or Commercial Off The Shelf (COTS)

· Product support is included

· Licensing structure is included

· Up to 5 individual environments to support Configuration Management (CM) processes. These include, but not limited to Production, User Acceptance Test, System Integration Test, Development, and Disaster Recovery (or High Availability for Cloud based solution) Product Capabilities The following capabilities are required:

Reporting Capabilities Support for both relational and analytical data models

a. User level ability to build reports from a predefined data model

b. Full feature reports publishing, including graphics, logos, and multiple output formats

c. Output sorting, filtering (with and without prompts/parameters), data conditions, totals/sub-totals, and addition of calculation/function data elements

d. User sharing of report definitions with other users and roles/groups. User’s access to the data must not be shared

e. Save the reports in various industry standard formats, including Excel (tabular and pivot), CSV, text, and PDF

f. Drill-down capabilities (e.g. charts/graphs to supporting data; summary report data to supporting report data)

g. Support for multiple data sources

h. Ability for read-only users to tailor pre-built reports (Display/Hide columns, Add total/subtotals)

i. Ability to create ad hoc reports – i.e. dynamic data selection and/or list of values for parameters; ability to select fields

j. Ability to create dashboards with drill down capabilities

k. Ability to filter report results

l. Ability to schedule report execution

m. Provide internal reporting of activity (e.g. user level auditing of connectivity and executed reports, tracking report design changes, report execution metrics)

n. Limit who can save, delete or copy reports by customer defined responsibilities/groups

o. Save individual reports/objects in a third-party source control system

Installation & Configuration The following capabilities are required:

A web-based user interface The ability to migrate individual report objects from one environment to another

Security: Authorization & Authentication The solution must meet all security standards pertinent to ESC and the Federal Government.

Federal Information Security Management Act (FISMA) security standards and controls baseline in NIST SP 800-53 for government IT systems categorized as Moderate.

Federal Risk and Authorization Management Program (FedRAMP) at Moderate certification if implemented on as a cloud based, SaaS solution.

User/Group management capabilities, managing permissions, and report access privileges and authorizations.

Integration with third party Single Sign-On (SSO) providers (i.e. Oracle Identity Manager).

p. Multiple levels for user roles from an Advanced User to build reports to a Standard User that can only consume reports

q. Ability to control access to certain reports by user/group

System Support & Sustainability The following capabilities are required:

High availability (99%), not including planned service interruptions, for a SaaS solution Solution should provide flexible support options (self-service, email, phone, etc.) during standard and off business hours Electronic or printed materials for full solution technical documents and user manuals (i.e. online help and training) Provide a formal mechanism (customer advisory board, forums, discussion boards) for gathering customer feedback and suggestions to incorporate into future product releases and roadmaps Product-specific technical and functional training, and materials

Discoverer Migration The following capabilities are required:

An automated migration of existing Discoverer EUL components and workbooks to the new reporting solution Ability to maintain the existing security, including user, EUL components, workbooks, and data fields

ESC Enterprise Transactional Reporting Solution Page 1 of 4 image1.png