8-Appendix D.pdf

Appendix D – Data Management Strategy

Data Management Strategy

The City requires access to its data whether stored on site, in a hosted or cloud-based solution or maintained by a third party. To this end, the City requires compliance with data management standards and requirements to facilitate continued cost-effective access to all forms of City data.

Data Management Standard Framework:

The City has adopted the Data Management Association’s Guide to Data Management Body of Knowledge (DMBOK) as its data management framework.

Data Governance

Data Governance aspects for all data managed on-site or off-site must minimally include consideration for:

• Data Operations including backup, recovery, monitoring, performance, disaster recovery, and business continuity as related to database activity.

• Data Security including access control, encryption as required, data upload, data download, Health Insurance Portability and Access Act (HIPAA), Personally Identifiable Information (PII), Criminal Justice Information Service (CJIS), and other possible administrative or legal requirements

• Data Quality including use of City Geo verification, City GIS districts, use of City Shape files, and overall data consistency and integrity

• Data Master includes use of standard look up data

• Data Meta includes a Data Dictionary, an Entity Relation Diagram, and relevant data descriptions

• Data Availability including data reporting, extraction, inspection, review, migration, end of contract data resolution, and identification and agreement regarding the final disposition of City data at the end of contract.

• Data Architecture

Database Management Systems

The City requires, where needed, that the Proposer provide an industry standard Relational Database Management System that meets the needs of all other requirements within this document. These include but are not limited to:

• Security

• Data Integrity

• Backup and recovery ability to meet provided requirements for Service Level Agreement

(SLA) and Disaster Recovery

• Backup and Recovery to within SLA for data incidents where data recovery is required

• Performance characteristics to meet the required application SLAs as provided

• The ability to provide scheduled and ad hoc data extract requests

• The ability, if requested, to provide a periodically updated full copy of the database solution for storage and full data access at a location of the City’s choosing

• The data should be available at the end of the contract period as an industry standard supported backup file type to allow the City to recover the data on a City location and have full access and use of the data within the database system.

The City understands that there is a multiplicity of database types now available that are not considered to be standard Relational Database Management Systems. These Not or Not Only Structured Query Language (“NoSQL”) or non-relational systems may be presented as part of the proposal where their function is required to provide the required City service.

The City requires Proposers to provide:

• An Entity Relationship Diagram (ERD)

• A Data Dictionary including table name, column name, data type, length, any constraints, default values, primary key/foreign key (to what tables and columns), how used in support of the solution.

Depending on data access parameters, other database technology solutions may be considered, if City data is accessible to its employees and delegates.

Appendix D – Data Management Strategy