Supplement 1

Enterprise Master Data Management (MDM) Requirements, System Development Methodology and Staffing Requirements

State of OhioDepartment of Administrative Services, Office of Information Technology

Supplement 1-Enterprise MDM Requirements, System Development Methodology and Staffing Requirements RFP 0A1213 Page 1

TableofContents

1.0Enterprise Master Data Management: Background and Overview

1.1General Scope

1.2Discovery Period

2.0General Project Requirements

2.1Data Management Strategy

2.1.1Data Governance & Stewardship

2.1.2Data Quality Management

2.1.3Metadata Management

2.1.4Key Deliverables

2.2Enterprise MDM Solution Architecture

2.2.1Key Deliverables

2.3Ohio Benefits Expansion and Hardware Upgrade

2.3.1Key Deliverables:

2.4Enterprise MDM Service Integration with EDW

2.4.1Key Deliverables:

2.5JFS Enterprise MDM Initiative

2.5.1Key Deliverables:

2.6Medicaid Provider Management

2.6.1Key Deliverables:

2.7Identity Management Integration

2.8Development and Testing Environment Support

2.9Maintenance and Operations

2.10Data Quality Execution

2.11Unanticipated Project Services

3.0Solutions Requirements: Business, Data and Non-Functional Requirements

3.1Overview of State Systems Referenced in this Supplement

3.2Additional State Data Stores

3.3Solution Sizing Requirements

3.4Organization of Requirements

3.5Business Requirements

3.6Data Requirements: “Individual” Domain

3.7Data Element Requirements: “Business” Domain

3.8Non-Functional Requirements

3.9RFP Assumptions

4.0State Project Delivery, Management, Methodology and Approach Requirements

4.1Project Management and Coordination Services

4.2State Project Governance Considerations

4.3Create and Maintain Project Plan

4.4Project Financial Management

4.5Project Review Check Point

4.6Meeting Attendance and Reporting Requirements

4.7Utilize OIT’s Document Sharing/Collaboration Capability

4.8Production/Version Control and Release Management

4.9Maintaining Solution and Operations Documentation

4.10Project Delivery, Role and Responsibility Requirements

4.11System/Environment Administration Support of the Project

4.12Establish and Manage a Program Management & Master Release Calendar

4.13Cooperation with State and State Contractors

4.14Requirements Confirmation and Analysis (for each release)

4.15Current Environment Assessment

4.16Data Governance and Stewardship

4.16.1Agency Data Quality Improvement Plan

4.17Analyze Phase Requirements (for each planned release)

4.18Design Phase Requirements (for each planned release)

4.19Build Phase Requirements (for each planned release)

4.20Test Phase Requirements (for each planned release)

4.20.1Project Incident Management

4.20.2Project Defect Management

4.21Deploy Phase Requirements (for each planned release)

4.22Organization Change Management

4.23Knowledge Transfer and Production Handoff (for each planned release)

4.24Project Completion Activities, Final Documentation and Post Implementation Support Obligations

4.25Future Project Services Pricing Response and Rate Card

5.0Schedule of Deliverables and Work Products

5.1Delivery and Deliverable Standards

5.2Schedule of Deliverables and Work Products

6.0State Staffing Requirements

6.1Contract Staffing and Key Activities

6.2Staffing Plan and Time Commitment

6.3Background Checks

7.0Assumptions

7.1Support Requirements

7.2Pre-Existing Materials

7.3Commercial Materials

8.0Informatica Platform Environments

8.1Informatica Platform Environment Implementation and Support During Development

9.0Appendix A: Project Development Methodology Deliverables by Release

1.0Enterprise Master Data Management: Background and Overview

The State is currently completing work on a Master Data Management (MDM) implementation which supports a cross-agency Integrated Eligibility solution. This MDM implementation when completed will contain two Master Data domains referred to as the Master Client Index (MCI) and Master Provider Index (MPI). This MDM implementation isbuilt using the Informatica Multi-Domain MDM platform, and is used to prevent data from being duplicated at the point of entry within the Integrated Eligibility system.

The purpose of this project is to expand the current MDM implementation with data from additional agencies and to enhance or add key MDM business capabilities. This expansion will advance the State’s ability to share and use Master Data within and across agencies, while accounting for Federal Regulations, Ohio Revised Code, and inter-agency data use agreements which govern the ability to do so. The scope of the Enterprise MDM RFPwill involve incorporating data from a limited set of systems from three (3) State Agencies: Ohio Department of Medicaid (ODM), Ohio Department of Job and Family Services (JFS) and Ohio Department of Administrative Services (DAS). The scope will allow the business capabilities to expand beyond the current focus on duplicate detection to include:

  • Facilitation of cross-agency integration via a common registry of system identifiers(IDs)
  • Improved Data Quality at point of entry via integrated data quality rules
  • Enhanced analytics through use of a harmonized golden record

1.1General Scope

  • Provide a functional (process and data quality) and technical assessment (design) of the current MDM implementation,documentinglessons learnedand recommendations for the future state architecture
  • Design and gain approval for an Enterprise MDM architecture which supports data maintenance, data integration and analytics use cases for ODM, JFS and DAS as defined in Section 2.0
  • Ensure the Enterprise MDM solution will be able to support three (3) Master Data Domains: Individual, Business, and Employee, and a common set of Master Reference Data. Only Individual, Business and Master Reference Data are in scope. The domains are defined as follows:

Individual: An Individual who is interacting for themselves or on the behalf of another Individual to engage with or receive services from the State. An Individual has various internal names including citizen, resident, client, recipient, beneficiary, individual tax payer, claimant, seeker, providers, etc.

Business: A business is an individual or organization who is engaged in providing products or services to or on behalf of the State. A Business has various internal names including licensed/certified providers, local education districts, hospitals, day care centers, community homes, payers, pharmacies, laboratories, vendor, etc.

Employee: Any individual who is fulfilling the role of a known State agency employee, contingency worker, contract worker, staff, Contractor, etc.

Master Reference Data: Master Reference Data is any look-up data, look-up codes or any other type of data that is used exclusively for categorizing data within one of the primary Data Domains

  • Ensure the architecture is flexible to expand scope over time with respect to modifying the number of hubs, agencies, source/target systems, domains, tables, attributes, rules, algorithms, etc.
  • Ensure the architecture complies with all Federal, State and inter-agency guidelines with respect to the use and sharing of data between ODM, JFS and DAS, and can be expanded to additional agencies as business needs require
  • Design, develop and implement a Data Governance and Stewardship strategy, which accounts ensuring timely decisions are made and that data is actively managed and monitored to ensure initial and on-going data quality
  • Design, develop and implement a Data Quality Management strategy which allows for the proactive definition, documentation and education of Master Data quality standards and the active review of data to ensure adherence to defined standards
  • Design, develop and implement a Metadata Management strategy, which will result in standardized processes and tools for obtaining, verifying, storing and distributing business/technical metadata relevant to the Enterprise MDM implementation utilizing Informatica’s Business Glossary and Metadata Manager
  • Lead the data remediation efforts to ensure that the Enterprise MDM solution is loaded with high quality Master Data
  • Work with each Agency to re-assess, refine and validate functional, data and non-functional requirements to ensure a complete and implementable set of requirements for the releases identified in Section 2.3, 2.4, 2.5 and 2.6
  • Design, build, test, implement and provide warranty support for the releases identified in Sections 2.3 and 2.4
  • Complete the design work, and create implementation plans for the releases identified in Sections 2.5 and 2.6
  • Specify and implement Informatica Platform environments to support development and testing activities for the releases identified in Sections 2.3, 2.4, 2.5 and 2.6 consistent with environment requirements defined in Sections 2.8 and 8.0
  • Provide industry best practices for integrating an Identity Management solution with a Master Data Management solution as defined in Section 2.7
  • Define and document a post-implementation Maintenance and Operations (e.g., “Run”) strategy for the Enterprise MDM environment
  • Assume ownership for Maintenance and Operations (M&O) for releases covered in Section 2.3 and 2.4 once the respective warranty periods have completed
  • Overview of anticipated releases:

Refer to Document Section #: / Release / Domains in Scope / Agencies in Scope / Source System / Consuming System / Anticipated Project Release Date
2.3 / Ohio Benefits expansion and hardware upgrade /
  • Individual
  • Business
/
  • DAS
  • Medicaid
  • JFS
/
  • Ohio Benefits
  • Master Client Index
/
  • EDW
  • Ohio Benefits
  • MMIS
/ May/Jun 2018
2.4 / Enterprise MDM Service integration with EDW /
  • Individual
  • Business
/
  • Medicaid
/
  • Enterprise MDM
/
  • Enterprise Data Warehouse
/ Sep 2018
2.5 / JFSEnterprise MDM Initiative /
  • Individual
/
  • JFS
/
  • OJI
  • OWCMS
  • Ohio Benefits
  • + 1 TBD
/
  • OJI
  • OWCMS
  • Ohio Benefits
/ Multi-Phase
  • April 2018
  • TBD

2.6 / Medicaid Provider Management /
  • Business
/
  • Medicaid
  • DAS – OAKS (Finance)
/
  • MMIS
  • OAKS
/
  • EDW
  • OAKS
/ No earlier than Dec 2018
2.7 / Identity Management (IDM) Integration /
  • Future
/
  • DAS - DX
/
  • IDM
/
  • N/A
/ Future

1.2Discovery Period

After award of Contract and commencement of work by the Contractor, the Enterprise MDM Project will be in a Discovery Period. The discovery period is anticipated to have a duration of approximately three (3) months and is comprised of the Enterprise MDM Solution Architecture, Data Management Strategy, and Ohio Benefits Expansion and Hardware Upgrade work that will occur during this timeframe. Any State-approved refinements to the Project or Work required due to the discovery period, may be cause for a limited fee adjustment. During the discovery period, a Go/No-Go decision will be made by the State. If the State decides not to go forward with the Work described in this Supplement, cancels this RFP for any reason, or contracts for the Work through some other process or through another RFP, the State will be liable to the Contractor for those deliverables completed and approved by the State during the discovery period.

2.0General Project Requirements

2.1Data Management Strategy

2.1.1Data Governance & Stewardship

The State has implemented Data Governance practices to drive business-centric decision-making within agencies. As the State expands the use of the Master Data Management service across agencies, it recognizes that its Data Governance practicesmust do the same. The State is asking for the Offeror to evaluate current Data Governance practices, and to propose and implement a Data Governance Strategy and Framework that recognizes the unique decision-making needs at the State and Agency levels

The Offerorwill be expected to:

  • Define a Data Governance Strategy and Framework to meet State and Agency Level needs
  • Define and Document key aspects of the framework including policies, procedures, roles & responsibilities, key performance indicators, etc.
  • Mentor individuals assigned to Data Governance roles

2.1.2Data Quality Management

The State understands the importance of ensuring quality data is loaded into the Enterprise MDM, and the need to continually and proactively monitor the data over time to ensure Data Quality persists. The Offerorwill be expected to develop a Data Quality Strategy and Approach which will, at a minimum, encompass the following:

  • Processes to define, approve data quality standards, match rules, merge rules, unmerge rules, etc.
  • Formalized approaches to:

Profile and analyze data

Identify, document and remediate data quality issues

Identify missing data and establish enrichment plans

Monitor data quality over time

Develop reusable data quality rules to automate data standardization and cleansing

  • Training materials to train Data Governance and Project team members on Data Quality Management

2.1.3Metadata Management

The State understands that as it continues to drive stronger Data Management practices, the importance of managing its Business and Technical metadata will increase. Therefore, the Offeror is expected to develop an approach to creating, managing and making available Metadata related to the Enterprise MDM implementation. The Offeror will be expected to:

  • Develop a Metadata Management Strategy and Approach to manage and monitor the metadata
  • Install and Configure InformaticaBusiness Glossary and Metadata Managerin accordance with the defined process and metadata attribute requirements
  • Train Data Stewards and project team members on the processes and tools adopted
  • Import relevant existing Metadata into the tools
  • Support the Business Glossary and Metadata Managerenvironments during the project phases
  • Define and implement processes to maintain Business Glossary and Metadata Manager environments on an ongoing basis.

2.1.4Key Deliverables

  • Data Governance Strategy and Framework
  • Metadata Management Strategy and Approach
  • Data Quality Management Strategy and Approach
  • Organizational Change Strategy and Plan
  • Organization Change Job Aids and Training Materials
  • Training materials (guides, job aids and/or play or run books) for Business Glossary and Metadata Manager

Refer to Sections 4 and 5 as well as Appendix A of this supplement for a complete discussion of methodology, deliverables and work products

2.2Enterprise MDM Solution Architecture

The long-term architectural direction with respect to the architecture model (single or multiple hubs) and the implementation style (Consolidation, Co-existence, Transaction, etc.), which must be implemented, are not defined. The Offeror is being asked to assess the defined functional requirements, data requirements, non-functional requirements, current state architecture, relevant Federal and State laws pertaining to sharing data across agencies (please refer to Supplement 2), and to propose an Enterprise MDM solution architecture and implementation style.

The proposed Enterprise MDM solution architecture must make use of Informatica’s Multi-Domain MDM solution. The State has procured an enterprise license for InformaticaMulti-Domain MDM, which has sufficient licensing to support up to nine (9) hub instances, each containing up to four (4) data domains with an unlimited number of consolidated records. Additionally, the State has no limitations on the number of named users of Informatica Data Director (IDD).

The State has the following additional Informatica technologies, which must be considered as the overall architecture is designed

  • InformaticaPowerCenter
  • Informatica Data Quality
  • Informatica Business Glossary
  • Informatica Metadata Manager

2.2.1Key Deliverables

  • Current Environment Architectural Assessment
  • Proposed Solution Architecture

Refer to Sections 4 and 5 as well as Appendix A of this supplement for a complete discussion of methodology, deliverables and work products

2.3Ohio Benefits Expansion and Hardware Upgrade

The Ohio Department of Administrative Services (DAS) in coordination with the Ohio Department of Medicaid (ODM) and the Ohio Department of Job and Family Services (JFS) have jointly implemented an Integrated Eligibility solution, Ohio Benefits (O.B.). To provide enhanced capabilities for managing and searching for Individual (Client) and Business (Provider) Master Data, O.B. was integrated with a lightweight MDM implementation. The existing MDM solution provides a Master Data repository and probabilistic search capabilities to identify and prevent duplicate records from being introduced into the Ohio Benefits solution. To continue to improve data quality, the goal of this project is to transition from a lightweight MDM implementation to a more robust solution and to transition to a new hardware infrastructure, which will be provided by the state. As part of this initiative, the Offeror will be expected to:

  • Partner with the DAS-OIT team to define HW specifications
  • Install, configure and support Informatica Multi-Domain MDM and other required platform services during the project
  • Assess and enhance, as appropriate, search capabilities used to identify potential duplicates early in the Master Data Managementprocess
  • Partner with the assigned Data Steward to create new workflows to:

Standardize, Cleanse and Enrich source system data as required to meet eEnterprise MDM data standards

Identify duplicate records and, when necessary, manually resolve them into a single global record, with a unique global identifier

Monitor Enterprise MDM Process and Master Data quality key performance indicators (KPI’s) to ensure the efficiency and effectiveness of the solution

  • Implement automated data integration between the Enterprise MDM service, O.B. and MMIS to eliminate manual processes currently required in each source system to propagate updates resulting from changes to Master Data (e.g., attributes, merge, unmerge, etc.)
  • Refer to Section 3 of this supplement for a complete list of business, data and non-functional requirements

2.3.1Key Deliverables:

  • Project Charter, Plan, and Kick-Off Package
  • Data Cleansing Approach and Tools
  • Requirements Definition
  • Solution Architecture
  • Data Quality Remediation Plan
  • Implementation & Deployment Strategy
  • Capacity Plan
  • Functional Design Document(s)
  • Technical Design Document(s)
  • Security Design
  • Technology Environments for Development and Test
  • Data Conversion/Migration Plan
  • Test Strategy
  • Data Quality Scorecard
  • Solution Component Code, Objects & Configuration
  • Test Scripts & Cases
  • Deployment & Stabilization Plan
  • System Test Results Report
  • Performance Test Results Report
  • User Acceptance Test Results Report
  • Operational Readiness Test Results Report
  • System Turnover

Refer to Sections 4 and 5 as well as Appendix A of this supplement for a complete discussion of methodology, deliverables and work products

2.4Enterprise MDM Service Integration with EDW

The Ohio Department of Administrative Services (DAS) is establishing an Enterprise Data Warehouse (EDW) to provide cross-agency analytic capabilities. To facilitate the integration of data from multiple source systems, the Enterprise MDM system will become the EDW’s source of truth for Individual and Business Master Data. The outcome of the EDW Integration scope will be an enterprise methodology and initial implementation for providing the EDW with high quality Master Data. The methodology and implementation concepts must be reusable and scalable, to support the EDW as its scope expands and begins to incorporate data from additional agency solutions. As part of this initiative, the Offeror will be expected to:

  • Partner with the DAS EDW team to develop a transition plan to use Enterprise MDM service as the source of their master data (i.e., Individual and Business)
  • Convert EDW sourcing Individual and Business Master Data from MMIS to the enhanced Enterprise MDM service for Individual (Recipient) and Business (Provider) conformed dimension management.
  • Develop integration services which provide batch and (near) real-time look-up of the unique global identifier
  • Refer to Section 3 of this supplement for a complete list of business, data and non-functional requirements

2.4.1Key Deliverables: