APPENDIX A3 ISE SCOPE OF WORK (SOW) AND RESPONSE FORM Appendix A3 is presented in two (2) parts. PART I provides a list of questions which need to be responded to by the Proposer. The questions pertain to the Project Approach Proposer intends to employ to perform the tasks, produce the deliverables, and satisfy the desired knowledge transfer as outlined in PART II. PART II provides a draft Scope of Work (SOW) for the professional services and deliverables the County requires from the Contractor to: Install, configure, and test the software suite on County-provided infrastructure; Develop and deploy six pilot information exchanges to prove the capabilities of the software; and Ensure knowledge transfer from the Contractor to County ISD staff. Proposers should provide a) labor categories and b) estimated (hourly) level of effort for each major task area noted in PART II. Additional Notes 1. SOW Performance Management: Upon contract award, the County will work with the Contractor to further define the scope, timeline, acceptance criteria, and resources to be applied to each task and deliverable and will issue task orders to manage the latter’s performance. 2. Assigned Personnel Qualifications: All assigned Contractor staff performing in satisfaction of the tasks and deliverables in this SOW will be required to submit to and successfully pass a criminal background check prior to assignment to the County. Specific instructions will be provided by the County upon contract award. 1 TABLE OF CONTENTS PART I – ISE SCOPE OF WORK PROJECT APPROACH ........................................................................................................................................... 4 1. 2. 3. Product Vision and Future Enhancement Strategy ........................................................................................................................................ 4 Project Methodology and Implementation .................................................................................................................................................... 4 Training Approach .......................................................................................................................................................................................... 5 PART II – ISE SCOPE OF WORK DELIVERABLES AND LABOR CATEGORIES ...................................................................................................... 6 1. ISE Project Governance .......................................................................................................................................................................................... 7 Project Planning.............................................................................................................................................................................................. 7 Project Staffing ............................................................................................................................................................................................... 8 Project Progress Monitoring........................................................................................................................................................................... 9 Change Order Management ......................................................................................................................................................................... 11 ISE Training and Knowledge Transfer ........................................................................................................................................................... 12 2. ISE Design and Requirements Definition .............................................................................................................................................................. 12 ISE Design ..................................................................................................................................................................................................... 12 ISE Validation ........................................................................................................................................................................ 13 3. ISE Installation and Testing................................................................................................................................................................................... 14 SOA ISE ........................................................................................................................................................................................... 14 ISE and Subsystem Validation and Testing..................................................................................................................................... 16 ................................................................................................................................................................................................... 18 4. Master Data Management Governance and Data Loading .................................................................................................................................. 21 Master Data Management (MDM) Governance .......................................................................................................................................... 21 and Testing of ISE Solution - MDM ........................................................................................................................................ 23 5. ISE PSAP Implementation ..................................................................................................................................................................................... 25 PSAP Exchange Implementation Design .................................................................................................................................. 28 Message ..................................................................................................................................................................................... 32 Message ...................................................................................................................................................................................... 33 Workflow Processing .................................................................................................................................................................................... 35 Master Index Update .................................................................................................................................................................................... 38 2 Data Management Index ................................................................................................................................................................. 39 Database .......................................................................................................................................................................................... 40 Content Management ................................................................................................................................................................. 41 and Event Logging and Exception Handling .................................................................................................................................. 43 3 PART I – ISE SOW PROJECT APPROACH 1. Product Vision and Future Enhancement Strategy A. Describe the Proposer’s product vision and how the Proposer sees the product in the marketplace with a two- to five-year outlook; include a statement of strategic direction. B. Describe plans, with timeframes, to enhance your service offerings. C. To what degree will these enhancements be transparent to customers? D. What are the Proposer’s intentions concerning evolving industry technology standards affecting the capabilities specified in Appendix A2? E. What existing industry standards are currently implemented/supported in Proposer’s solution? F. What emerging industry standards are currently planned for implementation in Proposer’s solution? Please include estimated dates when these will be supported. G. Describe the Proposer's current and future plans to offer its customers enhancements to the existing the products in its proposed solution; include the frequency of enhancements, estimated dates for future enhancements, and address within its plan the backwards compatibility approach and end of support life cycle. 2. Project Methodology and Implementation A. Provide an implementation project plan the Proposer would employ for the project and an explanation of how it will support the project requirements and logically lead to the required deliverables. The description shall include the organization of the project team, including accountability and lines of authority. B. Provide a proposed payment plan, based on the tasks and deliverables in submitted project plan. C. Describe how the relationship between the County and Proposer will be managed from an account and technical support perspective. 4 D. Explain what the Proposer would require from the County to ensure the successful implementation of the ISE solution. E. Provide resumes, experience narratives and, at least, one reference for key personnel who will be assigned to the project, if awarded the contract. F. Provide Project Team Organizational Chart with County and Proposer Responsibilities. G. Provide sample Microsoft Project (2007) based Work Breakdown Structure (WBS) for a similar project. H. Provide a sample Risk Management Plan for a similar project. 3. Training Approach A. Include a matrix describing training for four different audiences: 1) Technical System Administrators 2) Operational System Users/Administrators 3) Database Administrators 4) Development and Configuration users Please describe in the matrix the type and quantity of training that will be provided for each audience. The description must include the methods by which training will be provided. (e.g., online, on-site, webcast, self-paced online courses, etc.) B. Explain how the Proposer will work with the County to determine training needs and tailor the curriculum. C. Describe the type of training provided at each stage/phase of the project as well as follow-up training after implementation. 5 D. Explain the ability to provide training at a County location. E. Describe the ongoing training programs available for the proposed solution and related components. F. Describe the training facility requirements for physical layout, equipment specifications, course pre-requisites and internet connectivity specifications. 4. Value Added Services (Optional) Proposers are encouraged but not required to offer any optional value added services they believe would help the County to effectively implement, operate or use the proposed system. Information provided in this section must be directly relevant to Information Sharing Environment solution offered and not to exceed two (2) pages in length. Do indicate the costs of these optional value added services in Appendix B, Proposal Cost Response Form. PART II – ISE SOW DELIVERABLES AND LABOR CATEGORIES DRAFT SCOPE OF WORK Performance is divided into the five areas listed below:1 Project Governance; ISE Design and Infrastructure Validation; ISE Installation and Testing; Master Data Management Governance and Data Loading; and ISE PSAP Implementation. Detailed tasks and deliverables are itemized below; deployment of the ISE and its related sub-systems will be performed in a collaborative manner involving the selected Contractor staff, and staff from the Networks, Storage, Security, Database, Applications, and Operating Systems groups within the 1 For each of these areas, Contractor is expected to provide knowledge transfer for implementation and operations support for the ISE solution; see ISE Project Governance section for specific knowledge transfer requirements. 6 Santa Clara County (SCC) Information Services Department (County), and selected partner agency IT staff. The majority of work will be performed within the Santa Clara County (SCC) primary data center located at 1555 Berger Drive, San Jose, CA. DRAFT SCOPE OF WORK RESPONSE - INSTRUCTIONS TO PROPOSERS Proposers are required to enter the following information in the SOW table below: 1. Proposed labor categories that they would apply across tasks/deliverables in the SOW in the BLUE shaded areas of the table below; 2. Estimated number of hours, per labor category for each major task/deliverable area in the GREEN shaded areas of the table below; 3. Total number of hours for each major task/deliverable area in the PURPLE shaded areas of the table below; and 4. Total number of hours, per labor category in the RED shaded areas at the bottom of the table below. Additionally, in Appendix B Cost Proposal, proposers will need to provide a table of all proposed labor categories listed here, along with fully loaded labor rates for the base year and four option years (five years total). Labor Categories SOW Task/Deliverable Area Totals (Example) Project Manager2 1. ISE Project Governance This section of the SOW defines Project Governance tasks for project management, staffing, progress monitoring, change order management and training. 1.1. Project Planning 1.1.1. 2 xxx xxx Performance Requirements Proposers can replace this example column with their proposed labor categories; they may also transfer this SOW table to Microsoft Excel if that would be easier for them to work with. 7 Labor Categories SOW Task/Deliverable Area Totals (Example) Project Manager2 1.1.1.1. Work with the County ISE Project Manager (PM) to develop and implement ISE project management plans that address task management, risk management, and financial management. 1.1.1.2. Develop an integrated Work Breakdown Structure (WBS) for the ISE project. 1.1.2. Deliverables 1.1.2.1. ISE integrated Project WBS (Microsoft Project format). 1.1.2.2. ISE Project Task Management Plan (Microsoft Word format). 1.1.2.3. ISE Project Risk Management Plan (Microsoft Word format). 1.1.2.4. ISE Project Change Management Plan (Microsoft Word format). 1.1.2.5. ISE Project Financial Management Plan (Microsoft Word format). 1.2. Project Staffing 1.2.1. Performance Requirements 1.2.1.1. Assign appropriate staff to the project. 8 xxx xxx Labor Categories SOW Task/Deliverable Area (Example) Project Manager2 1.2.1.2. Work with the County ISE PM to establish an integrated implementation team, whereby the awarded Contractor and County staff collaborate to implement the ISE. 1.2.2. Deliverables 1.2.2.1. Contractor staffing plan (Microsoft Excel format). 1.2.2.2. Contractor staff resumes (Microsoft Word format). 1.2.2.3. Integrated Project Team Structure (organization chart) (Microsoft Visio format). 1.3. Project Progress Monitoring 1.3.1. Performance Requirements 1.3.1.1. Provide weekly project status reports that document: 1.3.1.1.1. Accomplishments for the past week, referenced to WBS task numbers and specific deliverables submitted vs. approved. 1.3.1.1.2. Planned activities for the following week referenced to WBS task numbers and expected deliverables to be submitted. 1.3.1.1.3. Difficulties encountered or roadblocks that require ISE PM or executive committee action 9 xxx Totals Labor Categories SOW Task/Deliverable Area 1.3.1.1.4. Changes to staffing – new staff, departing staff, staff unavailability, vacations, on site or off site work schedule, etc. 1.3.1.2. Participate in monthly program review meetings, providing at a minimum these elements of information: 1.3.1.2.1. Task milestone accomplishments during the period. 1.3.1.2.2. Planned milestone accomplishments (next period). 1.3.1.2.3. Current and planned change orders. 1.3.1.2.4. 90-day look at Contractor staffing. 1.3.1.2.5. Other issues affecting risks or project success. 1.3.1.3. Assist in identification and mitigation of project risks and issues, and participate in Monthly risk and issue management meetings. 1.3.2. Deliverables 1.3.2.1. Weekly status report (Microsoft Excel format, template to be provided). 1.3.2.2. Monthly program review presentation (Microsoft PowerPoint format, template to be provided). 10 (Example) Project Manager2 Totals Labor Categories SOW Task/Deliverable Area 1.3.2.3. Monthly updated Project Risk and Issue Register (County Provided SharePoint Site specific report structure will be provided upon award). 1.4. Change Order Management 1.4.1. Performance Requirements 1.4.1.1. Work with the County ISE PM to develop and implement ISE Project Change Order Management Plan that will address contract scope and financial change management process to manage any necessary modifications in scope, financial, tasks or timeline. 1.4.1.2. Produce monthly Project Change Order Register status report, and participate in monthly Project Change Order management meetings, providing input for the status of open change orders. 1.4.2. Deliverables 1.4.2.1. Monthly updated Project Change Order Register (County Provided SharePoint Site specific report structure will be provided upon award). 11 Totals (Example) Project Manager2 xxx xxx Labor Categories SOW Task/Deliverable Area 1.4.2.2. Monthly Change Order Status presentation (part of 1.3.2.2). 1.5. ISE Training and Knowledge Transfer 1.5.1. Performance Requirements 1.5.1.1. Work with County ISE PM and County staff to develop a tailored Training and Knowledge Transfer Plan that identifies the Contractor’s ISE solution topics to be covered, method of knowledge transfer/training, and delivery timeline. 1.5.2. Deliverables 1.5.2.1. Contractor to provide a County ISE Training and Knowledge Transfer Plan (Microsoft Word Document format). 1.5.2.2. Contractor to provide a list of recommended ISE product training, with prerequisites, duration, location, and cost. 1.5.2.3. Copies of all Contractor reference material related to ISE solution products – data sheets, white papers, training material, installation guides, etc. 2 2.1 12 ISE Design and Requirements Definition ISE Design Totals (Example) Project Manager2 xxx Labor Categories SOW Task/Deliverable Area 2.1.1 Performance Requirements 2.1.1.1 Work with County staff to develop the ISE design document for development (DEV) and system test (SYSTEST). 2.1.1.2 Provide an ISE installation and configuration document that addresses application installation, configuration, and deployment of the ISE solution to both the DEV and SYSTEST environments. 2.1.2 Deliverables 2.1.2.1 ISE solution design document for the County provided DEV and SYSTEST environments. (Microsoft Word/Excel/Visio format, as needed). 2.1.2.2 ISE solution installation and configuration document for the County provided DEV and SYSTEST solution (Microsoft Word/Excel/Visio format, as needed). 2.1.2.3 ISE RTM documents (Microsoft Excel format). 2.2 13 ISE Infrastructure Validation (Example) Project Manager2 Totals Labor Categories SOW Task/Deliverable Area This section of the SOW defines ISE Design and Infrastructure Validation tasks for the Contractor’s solution. 2.2.1 Performance Requirements 2.2.1.1 Work with County staff to validate ISE infrastructure requirements and specifications for the County to use during the ISE solution implementation. 2.2.1.2 Provide the ISE infrastructure performance and availability requirements that will support the design specifications developed in the ISE Design task. 2.2.2 Deliverables 2.2.2.1 3 3.1 14 Document the infrastructure performance and availability requirements to be used by the Contractor in validating the County infrastructure ISE solution environment. (Microsoft Word/Excel/Visio format, as needed). ISE Installation and Testing SOA Governance (Example) Project Manager2 Totals Labor Categories SOW Task/Deliverable Area This section of the SOW defines the tasks to support development of SOA governance for the County ISE solution. 3.1.1 3.1.1.1 Performance Requirements Work with County staff to ensure knowledge transfer, develop the SOA Governance policy and protocol documents supporting: 3.1.2 3.1.2.1 Service design; Service management; Service re-use; Service description; Service metadata; Service contracts; Service monitoring; Service policy enforcement; and Service security. Deliverables SOA Governance Policies and protocols (one or more documents) (Microsoft Word format) addressing: Service design; Service management; Service re-use; 15 (Example) Project Manager2 Totals Labor Categories SOW Task/Deliverable Area 3.2 Service description; Service metadata; Service contracts; Service monitoring; Service policy enforcement; and Service security. Baseline ISE and Subsystem Validation and Testing This section of the SOW defines the tasks to support installation, baseline validation of installation, and testing, and security for the County ISE solution. Installation of the baseline ISE applications will be accomplished by County. The Contractor will be asked to support installation and to validate/test the installed applications to assure their readiness for implementing the Public Safety Access Point (PSAP) information exchanges described in Section 5 below. All Contractor tasks will focus on the County prepared DEV and SYSTEST environments; County will be responsible for cloning the ISE SYSTEST environment to User Acceptance Test (UAT) and Production (PROD) environments. 3.2.1 3.2.1.1 16 Performance Requirements Monitor, support, validate and document the installation of the ISE components as defined (Example) Project Manager2 Totals Labor Categories SOW Task/Deliverable Area in Appendix A2 Functional Requirements onto the County provided DEV and SYSTEST environments; particular activities within this phase that Contractor will perform are: review and approve infrastructure before the start of ISE installation; test infrastructure environment related to access and performance using Contractor methods and tools; validate and approve the installation of all ISE components; conduct ISE system testing and report test results for developmental, integration, and acceptance testing for all installed ISE solution capabilities; and provide documentation to support the administration and operations of the ISE solution. 3.2.2 3.2.2.1 17 Deliverables ISE solution DEV and SYSTEST infrastructure environment test plan, checklists, and scripts (Microsoft Word format). To be used by Contractor to validate County infrastructure environment. (Example) Project Manager2 Totals Labor Categories SOW Task/Deliverable Area 3.2.2.2 ISE DEV and SYSTEST infrastructure environment test results documents (Microsoft Word format). 3.2.2.3 ISE administration guides, installation configuration materials, run-books, operations guide(s), and troubleshooting and recovery documents, tailored to County implementation (Microsoft Word format). 3.2.2.4 Contractor Final Approval of the ISE solution Installation Acceptance Checklist/RTM based on the Appendix A2 Functional and Appendix A1 Non-Functional Requirements (Microsoft Word/Excel format). 3.2.2.5 ISE solution capabilities test plan, checklists, and scripts based on Appendix A2 Functional Requirements (Microsoft Word format). 3.2.2.6 ISE solution capabilities test results documents based on 3.2.2.5 (Microsoft Word format). 3.2.2.7 ISE protocol document to move to the developed services and scripts into a source control environment. 3.3 3.3.1 18 ISE Security Performance Requirements (Example) Project Manager2 Totals Labor Categories SOW Task/Deliverable Area 3.3.1.1 Work with County staff to develop the ISE Security Configuration Acceptance Checklist based on the Appendix A2 Functional security requirements. 3.3.1.2 Work with County Staff to configure the ISE solution components to comply with Federal, State and County standards for Criminal Justice and Health Information security as specified in the requirements. 3.3.1.3 Document areas of the ISE solution where security compliance is not possible or where there are areas of risk that the County must accept. 3.3.1.4 Work with the County to develop and execute the security system test plan based upon County criteria. 3.3.1.4.1 Develop security system test plan (Microsoft Word format/test scripts); 3.3.1.4.2 Perform security system tests per the developed test plan; and 3.3.1.4.3 Document security test results (Microsoft Word format). 3.3.1.5 19 Work with County Staff to deliver the ISE System Security Plan (SSP). (Example) Project Manager2 Totals Labor Categories SOW Task/Deliverable Area 3.3.2 Deliverables 3.3.2.1 ISE Security Test Plan, with checklists and test scripts (Microsoft Word format). Note: County provides Security Test Plan Criteria. 3.3.2.2 ISE Security System Test Results (Microsoft Word format). 3.3.2.3 ISE documentation to explain areas of the ISE solution where security compliance is not possible (Microsoft Word format). 3.3.2.4 Content to be included in the ISE SSP (Microsoft Word format) to include: 3.3.2.4.1 Description of the specific deficiencies in the ISE solution component(s); 3.3.2.4.2 Identification of the specific security standards or polices not satisfied; 3.3.2.4.3 Description of the reason for the deficiency; 3.3.2.4.4 Recommendations to resolve/mitigate the risk; and 3.3.2.4.5 Completed and approved ISE Security Configuration Acceptance Checklist (Microsoft Word/Excel format). 20 (Example) Project Manager2 Totals Labor Categories SOW Task/Deliverable Area 4 Master Data Management Governance and Data Loading 4.1 Master Data Management (MDM) Governance This section of the SOW defines tasks to support MDM Governance for the ISE solution. 4.1.1 Performance Requirements 4.1.1.1 Work with County staff to ensure knowledge transfer for Master Data Management. 4.1.1.2 Evaluate the County’s current data model that contains Criminal Justice and Public Safety domain specific schemas. 4.1.1.3 Propose a design model to integrate County data model into proposed solution. 4.1.1.4 Provide necessary steps to implement the MDM environment. 4.1.2 4.1.2.1 Deliverables MDM Governance Policy document (Microsoft Word format), addressing the following MDM implementation factors. Managing multiple domains within a single MDM instance; 21 (Example) Project Manager2 Totals Labor Categories SOW Task/Deliverable Area Implementation of data governance policy within the MDM Solution; Document how Data Stewards will be implemented within the MDM Solution; Data model integration with ISE services; Data matching strategy; Document how the master records will be governed and implemented; 4.1.2.2 MDM design document to integrate the County’s current data model that contains Criminal Justice and Public Safety domains into the proposed ISE solution (Microsoft Word format); an initial set of attribute domains is provided below: 4.1.2.3 22 People Places Events Items Charges Associations Entities Scripts to provision a Microsoft SQL Server Database supporting the MDM portion of the ISE solution including primary keys, indexes, and constraints. (Example) Project Manager2 Totals Labor Categories SOW Task/Deliverable Area 4.1.2.4 MDM environment installation and configuration instructions document (Microsoft Word format). 4.1.2.5 MDM data updating and synchronization approach document (Microsoft Word format). 4.1.2.6 MDM Operational Plan (Microsoft Word format) that addresses data quality, data profiling, data cleansing, defect prevention, and metrics. 4.1.2.7 MDM Policies and Procedures Manual to address items in 4.1.2.1 (Microsoft Word format). 4.2 Configuration and Testing of ISE Solution MDM This section of the SOW defines the tasks to support data loading, query, and reports for the Contractor’s ISE solution. 4.2.1 4.2.1.1 23 Performance Requirements Work with County staff to develop a Public Safety and Criminal Justice Data Validation Acceptance Checklist to validate the performance of this task. (Example) Project Manager2 Totals Labor Categories SOW Task/Deliverable Area 4.2.1.2 Provide scripts to support validation of data loaded into the MDM database. 4.2.1.3 Transform and load sample (1,000) records from the County’s legacy system into the MDM database (basic characteristics of the data will be provided via a County executed Non-Disclosure Agreement). 4.2.1.4 Demonstrate the user interface or console to allow querying of data loaded. 4.2.1.5 Provide requested sample management reports to be produced from loaded data. 4.2.2 Deliverables 4.2.2.1 Fully cleansed and loaded Public Safety and (selected) criminal justice data into the ISE solution. County to provide data. 4.2.2.2 User interfaces and scripts to validate the data loaded in 4.2.2.1. 4.2.2.3 Provide Seven (7) Management reports produced from data loaded into MDM; while specific report formats will be developed/provided upon contract award, here are some examples of the reports to be produced: Mutual Aid Report - by agency; 24 (Example) Project Manager2 Totals Labor Categories SOW Task/Deliverable Area My Resources - list of local resources; Shared Call Count Report - number of shared calls between agencies; Number of calls by requestor (date range); Number of calls by area (date range); Number of calls by type (date range); and Number of calls by code (date range). 4.2.2.4 Completed and approved Public Safety and Criminal Justice Data Validation Acceptance Checklist. (Microsoft Word/Excel format). 4.2.2.5 Deliver a loaded MDM database with Public Safety data and County provided sample set of records from the County’s legacy criminal justice system into the MDM database. 5 ISE PSAP Implementation County currently has a Public Safety information exchange project under development called the Silicon Valley Regional Interoperability Authority – Data Exchange (SVRIA-DX). The objective of the SVIRA-DX project is to implement data exchanges between multiple Public Safety Answer Point (PSAP) Computer Aided Dispatch (CAD) systems 25 (Example) Project Manager2 Totals Labor Categories SOW Task/Deliverable Area throughout the County, cities, and towns, and with neighboring Counties. This section of the SOW defines tasks for the Contractor to develop services and configure the ISE to implement Public Safety information exchanges as a means to test the capabilities of the solution. These tasks focus on developing the services to support the handling of the message exchanges. Figure 5-1 below provides a conceptual view of the ISE and how it interacts with the SVRIA-DX information exchange source and destination agencies. The symbols in orange identified in Figure 1 below identify the specific PSAP implementation tasks to be executed by the Contractor; each of these tasks are described in more detail in the paragraphs that follow. 26 (Example) Project Manager2 Totals Figure 5-1: ISE RFP Contractor Professional Services Task Areas 27 Labor Categories SOW Task/Deliverable Area 5.1 Totals (Example) Project Manager3 PSAP Information Exchange Implementation Design This section of the SOW defines tasks for developing the services to support the handling of the message exchanges. 5.1.1 Performance Requirements 5.1.1.1 Work with County staff on the ISE solution design to implement the Public Safety information exchange, with recommendations for best practices. 5.1.1.2 Work with County staff to determine what if any additional infrastructure may need to be provisioned to support the implementation of the Public Safety information exchanges. 5.1.1.3 Develop, implement, and test the services to consume and publish County provide PSAP CAD Exchanges with assistance from County Staff. 5.1.2 3 Deliverables Proposers can replace this example column with their proposed labor categories; they may also transfer this SOW table to Microsoft Excel if that would be easier for them to work with. 28 Labor Categories SOW Task/Deliverable Area 5.1.2.1 Develop, implement, and test the services to handle the messages within the ISE solution for the following exchanges: Call for Service (Create, Update, Close, and Transfer) – Interface Exchange Package Document (IEPD) Documents provided by County; Request for Resource – IEPD Documents provided by County; Unit Status Update – IEPD Documents provided by County; Available Resource Response – IEPD Documents provided by County; Request Availability Query – IEPD Documents provided by County; and Request Unit Status Update – IEPD Documents provided by County. 5.1.2.2 Develop documentation for design patterns for creating services supporting the following functionality: Consume the message (receive the message and validate its composition). 29 (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area Update an exception SQL database if the message does not meet message constraints. Record the receipt of the message to a logging SQL database. Archive the message in its original format to an archival SQL database. Extract the message data elements and update a staging SQL database with the message values. Update the MDM repository using message attribute values. Validate the MDM indexes based on the insertion of the new values. Develop documentation on the workflow process based on Message types (header), Message attribute values, and Message content (images, metadata, attachments – Base64); includes sending message to alternate or additional consumers. Implement and execute federated queries based on workflows or message types (events) and publish the responses. Implement and execute notifications based on Message types (header), 30 (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area Message Data values, and Message content (images, metadata, attachments – Base64). Publish the message to a contract subscriber based on predefined contracts (SQL database records for each message type). 5.1.2.3 Produce a report that identifies that a message has been consumed (received the message and validated its composition). 5.1.2.4 Produce a report that identifies the extraction of the message attribute values and updates a staging SQL database. 5.1.2.5 Produce a report that identifies that a workflow handled messages based on Message types (header), Message attribute values, and Message content (images, metadata, attachments – Base64). 5.1.2.6 Produce a report that identifies that the workflow sent a message to predefined consumers. 5.1.2.7 Produce a report that identifies that the federated queries were executed based on workflows or message types (events) and that responses were published to consumer(s). 31 (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area 5.1.2.8 Produce a report that identifies that the notifications were sent to recipients based on Message types (header), Message attribute values, and Message content (images, metadata, attachments – Base64). 5.1.2.9 Produce a report that identifies that the published original message was sent by the publisher and received by the consumer. 5.1.2.10 Completed and approved PSAP Information Exchange Publishing and Consuming Acceptance Checklist. 5.2 Consuming Message This section of the SOW defines tasks for the Contractor to develop services and configure the ISE to handle receipts of messages from the County’s Computer Aided Dispatch (CAD) system. 5.2.1 Performance Requirements 5.2.1.1 Work with County staff to develop the Consuming Message Acceptance Checklist to validate the performance of this task. 5.2.1.2 Provide consuming service(s) to receive published CAD messages. 32 (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area 5.2.1.3 5.2.2 Contractor shall implement the services to consume CAD messages with assistance from County Staff. Deliverables 5.2.2.1 Develop, implement, and validate the services to consume following exchanges: Call for Service (Create, Update, Close, and Transfer) – IEPD Documents provided by County; Request for Resource – IEPD Documents provided by County; Unit Status Update – IEPD Documents provided by County; Available Resource Response – IEPD Documents provided by County; Request Availability Query – IEPD Documents provided by County; and Request Unit Status Update – IEPD Documents provided by County. 5.2.2.2 5.3 33 Completed and approved Consuming Message Service Acceptance Checklist (Microsoft Word/Excel format). Publishing Message (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area This section of the SOW defines tasks for the Contractor to develop services and configure the ISE to handle the publishing of the messages to contractual consumers. The focus of these tasks will be to publish them to an agency consumer upon completion of the complimentary tasks as defined in this document. 5.3.1 Performance Requirements 5.3.1.1 Work with County staff to develop the Publishing Message Acceptance Checklist to validate the performance of this task. 5.3.1.2 Provide publishing services that will publish CAD messages to a designated consumer. 5.3.1.3 Contractor shall implement the services for publishing CAD messages with assistance from County Staff. 5.3.2 5.3.2.1 Deliverables Build and configure publishing service that will send a message to the recipient contract consumer (while ancillary processing can be occurring - MDM, Notifications, etc.) for the following exchanges: Call for Service (Create, Update, Close, and Transfer) – IEPD Documents provided by County 34 (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area Request for Resource – IEPD Documents provided by County Unit Status Update – IEPD Documents provided by County Available Resource Response – IEPD Documents provided by County Request Availability Query – IEPD Documents provided by County Request Unit Status Update – IEPD Documents provided by County 5.3.2.2 5.4 Completed and approved Publishing Message Service Acceptance Checklist (Microsoft Word/Excel format). Workflow Processing This section of the SOW defines tasks for the Contractor to develop processes to support Workflow handling. The workflows execute based on a series of sequential messages that together will spawn a set of tasks to be handled and/or responded to via database inserts and will send notifications to recipients. 5.4.1 5.4.1.1 35 Performance Requirements Work with County staff to develop the Workflow Processing Acceptance Checklist to validate the performance of this task. (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area 5.4.1.2 Build services to support the handling of Workflows and Complex Event processing as part of consuming and publishing message exchange services. 5.4.1.3 Build services that support notifications, triggers and the generation of reports based on workflows and complex events. 5.4.1.4 Work with County staff to define triggers for workflow notifications. 5.4.2 5.4.2.1 Deliverables Develop and implement the services supporting workflow and complex event processing for the following exchanges: Call for Service (Create, Update, Close, and Transfer) Request for Resource Unit Status Update Available Resource Response Request Availability Query Request Unit Status Update 5.4.2.2 36 Develop and document services are supporting the Receipt of a message and validating its composition. (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area 5.4.2.3 Provide Implementation Design document for the identified messages (Microsoft Word format). 5.4.2.4 Develop and document services supporting the Sending of a notification to recipient(s) based on receipt of a series of messages over a predefined duration of time. 5.4.2.5 Develop and document services supporting a trigger count-down timer that triggers a notification if a message is not received or database records are not changed (inserted, updated or delete) within the count-down duration. 5.4.2.6 Develop and document the services that send reports based on the triggers. 5.4.2.7 Develop and document services to send notifications to recipients based on predefined rules including: Multiple messages of a specific type within a duration of time; Multiple messages from the same are within a duration of time; and Multiple messages from different agencies (Fire, EMS, Police) within a duration of time. 37 (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area 5.4.2.8 5.5 Completed and approved Workflow Processing and Complex Event Processing Acceptance Checklist (Microsoft Word/Excel format). Master Index Update This section of the SOW defines tasks for the Contractor to develop services and configure the Master Index to reflect the information contained in the CAD exchanges as a means to test the capabilities of the solution. 5.5.1 Performance Requirements 5.5.1.1 Work with County staff to develop the Master Index Update Acceptance Checklist to validate the performance of this task. 5.5.1.2 Provide ability to update the master index to address MDM service tasks. 5.5.2 Deliverables 5.5.2.1 Build and configure the master index to address the following tasks: 5.5.2.2 Insert message attribute values into the corresponding Master Index supporting Computer Aided Dispatch. 38 (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area 5.5.2.3 Provide scripts that validate the Master Index record has been updated from MIU-1a. 5.5.2.4 Completed and approved Master Index Update Acceptance Checklist (Microsoft Word/Excel format). 5.6 Master Data Management Index This section of the SOW defines tasks for the Contractor to develop services and configure the Master Data Management Index to reflect the information contained in the CAD exchanges as a means to test the capabilities of the solution. 5.6.1 Performance Requirements 5.6.1.1 Work with County staff to develop the MDM Index Acceptance Checklist to validate the performance of this task. 5.6.1.2 Provide a Master Data environment using County provided data models. 5.6.1.3 Provide supporting documentation of the steps to configure and populate the MDM Index. 5.6.1.4 Validate the MDM environment. 5.6.2 39 Deliverables (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area 5.6.2.1 Design, build and configure the MDM Index environment in collaboration with the County Staff using a provided data model supporting Criminal Justice and Public Safety. 5.6.2.2 Provide documentation for the steps to configure and populate an MDM Index. 5.6.2.3 Build and load the MDM Index from data provided by the County. 5.6.2.4 Provide scripts that validate the MDM index contains the identifying master record relationships to other MDM tables. 5.6.2.5 Completed and approved MDM Index Acceptance Checklist (Microsoft Word/Excel format). 5.7 Staging Database This section of the SOW defines tasks for the Contractor to develop a staging database for the ISE solution. 5.7.1 5.7.1.1 40 Performance Requirements Work with the County to develop a staging database that will be used for storing any message prior to processing by the ISE Solution. (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area 5.7.1.2 Work with County staff to develop the Staging Database Acceptance Checklist to validate the performance of this task. 5.7.1.3 Provide a service interface to store message attributes into a staging database. 5.7.2 Deliverables 5.7.2.1 Build and configure services to store message values for the following service tasks: Store the received CAD message attribute values into the corresponding CAD domain tables into a staging database. Provide scripts that validate the CAD message attribute values have been stored in the staging database. 5.7.2.2 5.8 Completed and approved Staging Database Acceptance Checklist (Microsoft Word/Excel format). Enterprise Content Management This section of the SOW defines tasks for the Contractor to develop services and configure the ISE solution to store a message into an Enterprise Content Management (ECM) system. 5.8.1 41 Performance Requirements (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area 5.8.1.1 The ECM will be used for storing unstructured data such as photos, documents, and other similar unstructured data. 5.8.1.2 Work with County staff to develop the ECM Acceptance Checklist to validate the performance of this task. 5.8.1.3 Note: ECM test environment to be provided by County. 5.8.1.4 Provide a set of services for storing message content (Base64) object into ECM environment. 5.8.2 5.8.2.1 Deliverables Build and configure services for storing message content into an ECM environment consisting of the following: Update an ECM database (SQL Server) with Content meta attribute values (Base64) received from a message using ECM API, Web Service or direct insertion (T-SQL); include the generation of a unique identifier for the content. Store, the Content in a file-store/share, using the unique identifier in ECM -1a and ECM-1b 42 (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area Log the ECM insertion event in the ISE solution database. 5.8.2.2 5.9 Completed and approved ECM Acceptance Checklist (Microsoft Word/Excel format). Message and Event Logging and Exception Handling This section of the SOW defines tasks for the Contractor to develop services and configure the ISE solution implementation of the message, event logging, and exception handling. 5.9.1 Performance Requirements 5.9.1.1 Work with County staff to develop the Exceptions Acceptance Checklist to validate the performance of this task. 5.9.1.2 Provide a framework for the handling and logging of message and service exceptions. 5.9.1.3 Provide supporting documentation for how the ISE solution will be configured to handle exceptions. 5.9.1.4 Provide recommended best practices for handling exceptions. 43 (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area 5.9.1.5 Work with County staff to develop the Message Logging Acceptance Checklist to validate the performance of this task. 5.9.1.6 Provide a framework for supporting the Logging of message and events. 5.9.1.7 Define the processes and services to support a standardized Logging framework. 5.9.1.8 Work with County staff to develop the Exceptions Database Acceptance Checklist to validate the performance of this task. 5.9.1.9 Work with the county to develop a Logging and Exception database. 5.9.2 Deliverables 5.9.2.1 Build and configure a framework for the handling of exceptions during the processing of messages by services. 5.9.2.2 Using County defined attributes, build and configure an exception database to be used to store exception objects and message attributes to identify the record. 5.9.2.3 Provide supporting documentation for how exception handling has been implemented, such as schema violations, unavailable resources, network connectivity errors, 44 (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area database connection errors, or related errors. (Microsoft Word Format) 5.9.2.4 Provide a best practices document for handling exceptions throughout the environment with an emphasis on storing/logging exceptions, and providing notifications and alerts. (Microsoft Word Format) 5.9.2.5 Build and/or configure services for the Logging for all activities, events, triggers, handlers, workflows, messages, notifications. 5.9.2.6 Using County defined attributes, build and configure a logging database to be used to store raw messages and message attributes to identify the record. 5.9.2.7 Define and document the processes and services for handling a standardized framework to support logging service and message attributes including, but not limited to, submitter IP address, access ID (credentials), message type, date/time stamp, consumer ID, Events, triggers, processes, code execution, authentication access, processing (startup, failure, and shutdown), and message header. 45 (Example) Project Manager3 Totals Labor Categories SOW Task/Deliverable Area 5.9.2.8 Provide a Message Logging Framework document (Microsoft Word Format) 5.9.2.9 Provide a completed and approved Messaging Logging Acceptance Checklist. (Microsoft Word/Excel format). 5.9.2.10 Provide a completed and approved Exception Acceptance Checklist. (Microsoft Word/Excel format). 5.9.2.11 Provide a completed and approved Exception Database Acceptance Checklist. (Microsoft Word/Excel format). Total hours for each labor category 46 (Example) Project Manager3 Totals