Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Statement of Work Data Warehouse Services to Support Intergraph RMS Implementation SECTION C DESCRIPTION/SPECIFICATION/STATEMENT OF WORK C.1 C.1.1 SCOPE/BACKGROUND In Fiscal Year 2008, the Metropolitan Police Department (MPD) embarked on a significant upgrade and integration of its information technology infrastructure through Phase I of the Law Enforcement Information Management System (LEIMS) Program. Phase I involved the building of a Data Warehouse in which to store several of MPD’s Priority I data sources. C.1.1.1 The Data Warehouse was built by Data Vision Group (a subcontractor in the first contract to Dimension Data and the prime in the second contract). C.1.1.2 The Data Warehouse is divided into two components: a replication of the original source data in a Legacy Data Warehouse (LDW) and an Operational Data Warehouse (ODW) upon which to do further analysis and reporting. C.1.1.3 MPD purchased Informatica as the ETL tool to build and support the Warehouse. C.1.1.4 The Operational Data Warehouse is being positioned as the repository of all MPD reportable data. C.1.2 Phase II of the LEIMS Program involved the creation of a comprehensive Records Management System (RMS). This is being executed through multiple phases involving planning, infrastructure development, data improvement, and acquisition and employment of improved replacement systems. C.1.2.1 MPD contracted with Yellow House Associates to build a customized Records Management System (RMS). The first of the RMS modules, Automated Field Reporting, was implemented in April 2009. Additional modules have been added since then, including an Interim Arrest & Booking module and the Investigative Case Management (ICM) module, which replaces the older case management application. C.1.2.2 In the summer of 2010, however, MPD contracted with Intergraph Public Safety to implement their commercial off-the-shelf (COTS) RMS application, which provides a more all-in-one solution for many of MPD’s operational needs. The desktop version of this application is called I/LEADS, and the mobile version is called IFR. As part of the Task Order, Intergraph is also working with MPD and the District Office of Unified Communications (OUC) to upgrade its CAD schema to v9.1 and converting the CAD database from Oracle to SQL Server. C.1.3 The first phase of the Intergraph award to MPD includes a preliminary export of data to the Legacy Data Warehouse as well as a one-time data conversion to the Data Warehouse Services to Support Intergraph RMS Implementation DCTO-2011Operational Data Warehouse. MPD is seeking a vendor to provide additional services to update the Warehouse in preparation for, and following, this conversion. C.1.3.1 Add new fields from the Yellow House Field Reporting, Arrest & Booking and ICM Modules within MPD’s RMS, via an Informatica Extract, Transform and Load (ETL) process, to the related tables that are already part of the Legacy and Operational Data Warehouses; C.1.3.2 Supplement the Operational Data Warehouse with a subset of fields from the Legacy Data Warehouse; C.1.3.3 Transfer new I/LEADS fields from the Legacy Data Warehouse to the Operational Data Warehouse via an Informatica ETL process, and train MPD members to do the same; C.1.3.4 Prepare a Feasibility Study to Convert the Data Warehouse from an Oracle 10G platform to SQL Server. If successful, Contractors will perform the conversion; C.1.3.5 Map Computer-Aided Dispatch (CAD) 911/311 data as an additional data source to the Legacy and Operational Warehouses; and C.1.3.6 Provide ongoing support and maintenance of the Data Warehouse to MPD, OUC, the District of Columbia Office of the Chief Technology Officer (OCTO) and Intergraph during the transition to I/LEADS and IFR. C.1.4 The addition of one new data source and several new data fields into the Data Warehouse noted in Section C.1.3 will satisfy the same initial operational objectives defined at the beginning of Phase I of the LEIMS Program. Specifically, the Data Warehouse standardizes data and uses a logical data structure to store data currently contained in multiple systems. It is expected that these additional data will be standardized using the Global Justice XML Data Model (GJXDM), and exchanged through an Informatica Extract, Transform and Load (ETL) process. C.1.5 All contractor tasks will involve at least weekly, but often daily, coordination between the vendor, MPD, OUC and Intergraph staff. 2 Data Warehouse Services to Support Intergraph RMS Implementation DCTO-2011C.2 DEFINITIONS Acronym Name Description ETL Extract, Transform, and Load GJXDM XML data model LDW Legacy Data Warehouse LEIMS Law Enforcement Information Management System MPD Metropolitan Police Department OCTO Office of the Chief Technology Officer ODW Operational Data Warehouse Oracle Relational database SQL Server Relational database C.3 C.3.1 C.3.1.1 C.3.2 C.3.2.1 The functions performed when pulling data out of one database and placing it into another of a different type. Global Justice XML Data Model (GJXDM or Global JXDM) is a data reference model for the exchange of information within the justice and public safety communities One half of MPD’s Data Warehouse, which serves as a backup of the original primary source databases (crime, arrest, case management and other databases dating back several years) Name of the technical system planned for MPD in FY 2008 Primary law enforcement agency of the District of Columbia District of Columbia government agency that coordinates technology projects throughout the city Second half of MPD’s Data Warehouse: subset of the LDW, which standardizes the data for future analysis and reporting A relational database management system (DBMS) from Oracle A relational database management system (DBMS) from Microsoft REQUIREMENTS Add new fields from the Yellow House Field Reporting, Arrest & Booking and ICM Modules within MPD’s RMS, via an Informatica Extract, Transform and Load (ETL) process, to the related tables that are already part of the Legacy and Operational Data Warehouses; Contractors shall work with Yellow House and MPD to identify additional fields added since early CY 2010 to MPD’s RMS as part of the development of the new modules. They will then use an Informatica ETL process to populate the LDW and ODW with these new fields. Supplement the Operational Data Warehouse with a subset of fields from the Legacy Data Warehouse Contractors shall identify and incorporate fields defined as crucial to the Intergraph Data Conversion, but missing from the current LDW, to the ODW, again via an Informatica ETL process. 3 Data Warehouse Services to Support Intergraph RMS Implementation DCTO-2011C.3.3 Transfer new I/LEADS fields from the Legacy Data Warehouse to the Operational Data Warehouse via an Informatica ETL process, and train MPD members to do the same C.3.3.1 Intergraph will identify the fields for, and perform the mapping of, new I/LEADS fields to the LDW. Intergraph will then perform a database export to the LDW, ensuring that the format of fields in production I/LEADS is identical to the format in the LDW. Assistance will then be needed from the contractors to transfer these new I/LEADS fields from the LDW to the ODW via an Informatica ETL process. These data elements will be used for future reporting. C.3.3.2 As part of this task, contractors will train two MPD IT representatives how to transfer fields added to I/LEADS in the future from the LDW to the ODW, and provide written documentation for this function in the Post Project Report (C.6.5). C.3.4 Prepare a Feasibility Study to Convert the Data Warehouse from an Oracle 10G platform to SQL Server. If successful, Contractors will perform the conversion; C.3.4.1 Contractors shall prepare a Feasibility Study for MPD’s review and approval to list the steps required to convert the Data Warehouse from Oracle 10G to SQL Server. This will involve researching known Microsoft and other tools to perform such conversions. The plan will also include regression and performance testing steps, as well as a risk assessment, to ensure both the LDW and ODW continue to function properly after the conversion. C.3.4.2 If MPD approves the work described in the Feasibility Study, and preliminary testing demonstrates such a conversion will be successful, contractors will also perform the conversion. C.3.5 Map Computer-Aided Dispatch (CAD) 911/311 data as an additional data source to the Legacy and Operational Warehouses. C.3.5.1 MPD has archived two years of older (1998-1999) GEAC CAD data (currently stored as a flat file) and up to 10 years of more recent Intergraph CAD data (stored in a replicated Oracle database server called the DCCADMIR and Microsoft Access files). CAD data for much of 2011 is in the process of being converted to SQL. Contractors shall map all available data from these sources to the LDW and the ODW. C.3.5.2 Contractors shall publish the selected priority systems through an Informatica ETL process, in accordance with the standards and schema used to build the original Data Warehouse. C.3.5.3 The Data Warehouse shall not replace the existing source. Data shall continue to be entered into the CAD system and update in the Data Warehouse. C.3.5.4 Contractors shall ensure the Data Warehouse is continuously updated with data from these new systems using the same architecture developed during LEIMS I. 4 Data Warehouse Services to Support Intergraph RMS Implementation DCTO-2011C.3.5.5 Contractors shall ensure the completeness and accuracy of the loads using the same testing and MPD approval procedures developed during LEIMS I. C.3.6 Provide ongoing support and maintenance of the Data Warehouse to MPD, OUC, the District of Columbia Office of the Chief Technology Officer (OCTO) and Intergraph during the transition to I/LEADS and IFR. C.3.6.1 As part of the one-time Data Conversion, Intergraph will be writing directly to the ODW and bypassing the ETL functionality. The Contractor shall provide ongoing support of, and maintenance to, the Data Warehouse. Examples of related tasks will include: C.3.6.1.1 Conducting preventative maintenance tasks, such as log monitoring and error troubleshooting, to ensure that the Data Warehouse loads flow as scheduled; C.3.6.1.2 Conducting perfective maintenance tasks, such as database tuning and software upgrades, to ensure that the Data Warehouse environment continues to operate at optimal efficiency; C.3.6.1.3 Working with MPD and its partners to establish production support procedures; C.3.6.1.4 Ensuring that all data flows to the Citywide Data Warehouse are uninterrupted; C.3.6.1.5 Serving as technical support/help desk for user-generated questions about the Data Warehouse and the data it contains; and C.3.6.1.6 Working with MPD and its vendors to plan for and implement high availability and disaster recovery solutions, including backups and mirroring. C.4 TECHNICAL STANDARDS C.4.1 The Contractor shall recognize MPD’s architecture as being developed as part of the LEIMS project as the target architecture for MPD development. All installation, development, deployment and migration activities performed through this contract shall employ this architecture and these specific components as appropriate. C.4.2 MPD builds technology systems in accordance with a logical information technology architecture design that enables data exchange and application integration across the enterprise. Extensible and adaptable in nature, the architecture model scope includes legacy systems, custom and off-the-shelf applications. 5 Data Warehouse Services to Support Intergraph RMS Implementation DCTO-2011C.5 C.5.1 TECHNICAL STANDARDS FOR IMPLEMENTATION MPD has set a number of technical standards for implementation of the Data Warehouse. The Contractor shall implement its work in accordance with the specific configuration, software components and standards of the following model: Table C-1 – District Product Standards ETL Tool Informatica Power Center Data Quality Tool Informatica Data Quality Tool Relational database Oracle 10g or SQL Server C.11 COOPERATION WITH OTHER CONTRACTORS C.11.1 Contractors shall cooperatively work as a team with each other as well as with any other Contractors assigned to MPD’s customized RMS and Intergraph RMS projects. Contractors shall not commit or permit any act that will interfere with the performance of work by another District Contractor or by any District employee. C.11.2 Contractors may have to sign non-disclosure agreements with other MPD contractors. C.12 C.12.1 BACKGROUND CHECKS All Contractor personnel involved in the project shall submit to a background check including fingerprinting. Contractors and/or the ITSA COTR, OST, shall be responsible to pay the FBI processing fee of $35 per person. 6 Data Warehouse Services to Support Intergraph RMS Implementation DCTO-2011F.3 DELIVERABLES The Contractor shall submit the following deliverables to the COTR along with those specified in Section C.3. CLIN Deliverable 1 C.6.1 Deliverable 1 Project Kickoff Meeting 2 C.6.2 Deliverable 2 Project Management Plan C.6.3 Deliverable 3 Weekly Progress Reports C.1.3.1 Add new fields from the Yellow House Field Reporting, Arrest & Booking and ICM Modules within MPD’s RMS, via an Informatica Extract, Transform and Load (ETL) process, to the related tables that are already part of the Legacy and Operational Data Warehouses C.1.3.2 Supplement the Operational Data Warehouse with a subset of fields from the Legacy Data Warehouse C.1.3.3 Transfer new I/LEADS fields from the Legacy Data Warehouse to the Operational Data Warehouse via an Informatica ETL process, and train MPD members to do the same C.1.3.4 Prepare a Feasibility Study to Convert the Data Warehouse from an Oracle 10G platform to SQL Server. If successful, Contractors will perform the conversion C.1.3.5 Map Computer-Aided Dispatch (CAD) 911/311 data as an additional data source to the Legacy and Operational Warehouses C.1.3.6 Provide ongoing support and maintenance of the Data Warehouse to MPD, OUC, the District of Columbia Office of the Chief Technology Officer (OCTO) and 3 4 5 6 7 8 9 Quantity 2 Format/ Method of Delivery Meeting Due Date To Whom 10 days from contract award MPD Project Team COTR 20 days from contract award Weekly N/A Document (hard and soft copy) Document (hard and soft copy) N/A 75-90 days from contract award COTR N/A N/A 75 days from contract award COTR N/A N/A 60-75 days from contract award for transfer COTR 2 Document (hard 120 days from and soft copy) contract award COTR N/A N/A 160 days from contract award COTR N/A N/A Ongoing COTR 1 7 COTR Data Warehouse Services to Support Intergraph RMS Implementation DCTO-2011- 10 Intergraph during the transition to I/LEADS and IFR C.6.5 Deliverable 4 Post-Project Report 2 Document (hard 10 days from and soft copy) expiration of contract 8 COTR