1423030-20 - Metadata Management Tool

Request for Proposal (RFP) # 1423030-20
 
This Request for Proposal (RFP) is an invitation by the Toronto Police Service (TPS) to prospective and qualified proponents to submit proposals for a Metadata Management Tool, as further described in the RFP.
 
 
Submission Requirements
 
Proposals must be submitted through the MERX Electronic Bid Submission (“EBS”) System (https://www.merx.com/).
 
For assistance in using MERX, please contact MERX directly at 1-800-964-MERX or visit the MERX website at www.merx.com.  
 
Proponents are to submit their proposal through the MERX EBS System prior to 1:00:00 P.M. local time on Friday January 15 2021.
 
 
Objective
 
The business driver for implementing a metadata management solution is to facilitate several high priority use cases pertaining to Data Governance and Information Lifecycle Management:

• Data Catalog
• Data Ownership and Stewardship
• Data Quality
• Data Security
• Data Lineage

• Metadata repositories
• Business glossary
• Data lineage
• Impact analysis
• Rules management
• Metadata ingestion and translation

• Metadata repositories: Used by information managers to document and manage metadata, and to perform analysis using metadata. They can also use repositories to publish information about reusable assets that enables users to browse metadata during life cycle activities;
• Business glossary: A repository used to communicate and govern business terms, along with the associated definitions and the relationships between those terms;
• Data lineage: Specifies the data’s origins and where it moves over time. It also describes what happens to data as it passes through diverse processes. Data lineage can help to analyze how information is used and to track key bits of information that serve a particular purpose;
• Impact analysis: Conveys extensive details regarding the dependencies of information or the impact of a change on a data element;
• Rule management: Documentation of business rules that are tied to data elements and associated metadata;
• Metadata ingestion and translation: Using techniques or bridges for various sources, including, but not limited to:
  • Database Management System (DBMS) in Microsoft SQL Server
  • Extraction, transformation and loading (ETL) codebase in Microsoft SQL Server Integration Services (SSIS)
  • XML schema file
• On premises deployment: The data catalog and it’s codebase must be installed on premises and remain within TPS environment;
• For client-side deployment, the proposed solution must support TPS’s existing workstation and device standards, as specified in Appendix H, Section 13.3 of the RFP;
• For server-side deployment, the proposed solution must support TPS’s existing server and storage standards, as specified in Appendix H, Section 13.5 of the RFP; and
• For user identity and access management, the proposed solution must integrate with TPS’s existing identity management platform, as specified in Appendix H, Section 13.7 of the RFP.