CADIS Sol 03092010.doc

Computer Aided Dispatch Information System (CADIS)

HSCETC-10-R-00010

SECTION B: SUPPLIES/SERVICES PRICE/COST SCHEDULE

B.1 Price/Cost schedule

Offeror is to input hours, unit prices, CLIN total amounts, annual total contract value amounts, and a summary of all contract years with an estimated total value of the contract on an Excel spreadsheet.

B.2 ITEMS TO BE ACQUIRED

The Offeror shall furnish all personnel, facilities, equipment, material, supplies, and services (except as may be expressly set forth in this contract as furnished by the Government) and otherwise do all things necessary to, or incident to, performing and providing the following items of work: Computer Aided Dispatch Information System (CADIS).

CADIS will be comprised of a Commercial-Off-The-Shelf (COTS) software system and software development services.

The government is seeking a COTS solution that will enable implementation of the system without making modifications to the COTS package. The offeror shall configure the COTS product to perform the required functions for the Federal Protective Service (FPS) business operations.

The offeror shall also develop interfaces to existing systems as specified in the SOW, section C, and the Functional Requirements Document.

B.3 ORDERING ACTIVITY

The Department of Homeland Security, ICE and NPPD, will have the sole authority to request services under this contract.

B.4 CONTRACT CEILING

The ceiling for this contract is $ ________________ (to be determined).

B.5 NAICS/PSC

NAICS Code: 541512, Computer Systems Design Services

PSC Code: D307 Automated Information System Design and Integration Services

SECTION C: STATEMENT OF WORK (SOW)

1.0 Project Title

Computer Aided Dispatch Information System (CADIS)

1.1 Introduction

This Statement of Work (SOW) document outlines the current high-level functional and technical requirements of the Department of Homeland Security (DHS), National Protection Programs Directorate (NPPD), Federal Protective Services (FPS), and the Immigration and Customs Enforcement (ICE) Office of the Chief Information Officer’s (OCIO) integration, configuration and deployment utilizing an approved System Development Lifecycle methodology to implement CADIS.

2.0 BACKGROUND

FPS is responsible for providing security and law enforcement services for federal facilities. The role of CADIS is to support the FPS Law Enforcement Mission by:

Automating the FPS MegaCenter dispatch operation: The MegaCenters are the vital communications link between FPS Law Enforcement Officers (LEOs), federal facilities, contract guards at the entrance to the facilities, and emergency responders, providing 24 –hour security alarm monitoring and dispatch functions.

Currently, FPS manages dispatches and incidents from four MegaCenters located in Denver, Colorado; Battle Creek, Michigan; Suitland, Maryland; Philadelphia, Pennsylvania; and 11 regional offices. This dispatch and incident response solution was originally developed to support mission needs in a non-automated process. The Government Accountability Office (GAO) and FPS have determined that the current infrastructure no longer meets organizational requirements and does not adequately support the FPS Mission in the following ways:

· Manual Processes where automation is available to enhance performance

· Unreliable and non-standardized data management between MegaCenters

· Lack of a Geographic Information System (GIS)

· Lack of performance measurement capabilities

· Limited emergency fail-over and load sharing capabilities

· Dependence on individuals with domain knowledge

Providing access to information and robust reporting functionality to FPS Law Enforcement Personnel: In order to eliminate the current deficiencies and to address the new law enforcement requirements, CADIS must replace the current Daily Operations Log (DOL) and Web Records Management (WebRMS) systems and include the following three components:

1) Computer aided dispatch

2) Records management

3) Geographic information CADIS is aligned with the DHS and FPS Strategic Plans:

· DHS Strategic Goal of “Strengthen Our Nation's Preparedness and Emergency Response Capabilities”

· FPS Strategic Goal of “Collaborative Partnerships and Effective Communications and Efficient and Stakeholder-oriented Law Enforcement and Security Services”

2.1 EnVISIONED CAPABILITY

To eliminate current functionality gaps and to address new law enforcement requirements a new system is needed that will automate core FPS law enforcement business processes and will result in a more standardized, integrated, and efficient national information technology solution for FPS. The system must provide a level of scalability and compatibility with other DHS, ICE, and FPS systems and shall always be in compliance with emerging DHS enterprise architecture. Further, the system must reflect the seamless integration of the following three functional components:

1) Computer aided dispatch of personnel dispatching in response to incidents

2) RMS to collect, share, and report incident information based on National Incident Based Reporting System (NIBRS) standards. A system to conduct efficient call center management, which includes automated data collection, calls routing, viewing call history, etc.

3) Geospatial Information to display relevant neighborhood information, improve routing and track vehicles. FPS does not currently have GPS Vehicle Location Devices. The Mobile Computing Device(s) (MCD) used as the client computer for CADIS will not have GPS capability. FPS anticipates this integration as a future capability.

FPS requires 2D views of building interiors and exteriors. CADIS must be capable of routing response vehicles and tracking response vehicles. This is also an anticipated future capability. CADIS does not have to provide establishment of cordons, do blast plume monitoring, or building evacuation modeling. The Environmental Systems Research Institute (ESRI) database will provide the GIS data. It has been established for use by the Risk Assessment Management Program (RAMP) system. CADIS will get the GIS data from the ESRI database.

DHS Geospatial Information System Compliance: All implementations shall comply with the policies and requirements set forth in the DHS Geospatial Information Infrastructure (GII), including (but not limited to) the following:

· The DHS geospatial data model shall be used building to the GII.

· All data within the GII, whether adopted or developed, shall be submitted to the DHS Enterprise Data Management Office (EDMO) for review and insertion into the DHS Data Reference Model.

The FPS CADIS will eliminate the deficiencies mentioned above and will return many critical hours of resources. CADIS shall have the capability to collect, modify, store, retrieve, and process record management and geographic information data via a report management function and a record management system. It will improve FPS officer safety, as the current manual processes will be automated; reducing the chances of critical errors by removing the extensive liability that currently exists with the dispatchers. Additionally, CADIS will provide intelligent resources in reporting information that is needed to make knowledgeable business decisions and aid in criminal analysis, helping FPS’ efforts in providing preventative security measures.

CADIS will interface with the Security Information System (SIS) for processing of all electronic security systems being monitored, including Intrusion Detection System (IDS) and Access Control System (ACS) alarms, and fire alarms. Future spirals or enhancements may follow this contract to provide additional functionality and will be identified later. (See Interface E in section 5.9) CADIS will consolidate geographically and functionally alarm inputs, the dispatch decision-making and recordkeeping sites, and dispatch communications hub for FPS. CADIS will be able to dispatch from four FPS MegaCenters to any LEO within the United States and its territories.

Specifically, the system shall:

· Be fully NIBRS compliant.

· Implement a system availability of 99.999 percent when measured on a 24-hour per day, seven day a week basis for 365 days. Processor, disk storage, and power supply redundancy may be required in order to achieve the desired availability and protection of information. The system shall be configured such that operating a training component and/or running reports will not affect system response time. This availability requirement applies to both dispatch capabilities and record management components. There is no requirement for offline capability for dispatch functions.

· Interface with external applications and data sources such as the FPS Risk Assessment Management Program (RAMP), National Crime Information Center (NCIC), and other systems, as listed in section 5.9.

· Have the ability to push the client application via the DHS network to desktops and Mobile Computing Devices (MCD) utilizing Big Fix.

· Allow a user the ability to access the application, download appropriate information and forms relating to incidents, and submit the necessary information without re-keying information.

· Allow the capability to be directly expandable by adding hardware and Commercial-Off-The-Shelf (COTS) modules.

· Include a feature for backup, archival and recovery capability without taking CADIS out of service and with minimal impact on dispatch operations.

· Provide the capability for users to work offline in the event of connectivity failures, and the capability to continue to work off-line in the event the failure occurs in the middle of a session without any data loss, and to upload saved offline data when connectivity is re-established. All solutions must meet DHS Regulation 4300A. Therefore, CADIS may not be based on a peer-to-peer architecture.

· Contain data exporting capabilities. CADIS must have the capability to export data in industry standard database formats to facilitate providing data to other databases controlled by DHS and/or other Government entities.

· Be able to generate standard automated forms and templates to be used by all regions; such as incident report, spot report, etc.

· Contain a wide variety of reports and statistical information for analysis and management reporting and/or reporting requirements in real time.

· Allow ad-hoc, dynamically generated reports such that code modifications are not required for each new report.

· CADIS will integrate with an ESRI database and use data provided by that system

· Archiving: Any active records shall be indefinitely available, anything that has a disposition or is closed, minimum 12 months

2.2 CADIS Deployment Considerations

The Contractor shall be aware of the following consideration as it relates to the deployment of CADIS:

2.2.1 CADIS will initially be hosted in the FPS MegaCenters and eventually move to the DHS datacenter..

2.2.2 Geographic locations of clients:

1) Law Enforcement Officers (LEO) use Mobile Computing Devices (MCS). LEOs are located throughout the United States and its territories (Estimated 600 mobile clients). MCDs are Government Furnished Equipment (GFE) . MCD specifications are provided as an attachment.

2) Dispatch clients are located in the MegaCenters in Denver, Colorado; Battle Creek, Michigan; Suitland, Maryland; and Philadelphia, Pennsylvania. There are approximately 30 desktop computers at each of the MegaCenters. CADIS will initially be hosted in the FPS MegaCenters and eventually move to the DHS datacenter. Dispatch workstations are provided and are GFE. Dispatch workstation specifications are to be provided by the vendor and approved by the Government.

3) Regional/Reporting Clients are located nationwide but organized into eleven regions plus the Headquarters office in Washington, DC and the Federal Law Enforcement Training Center (FLETC).

2.2.3 Software deployments shall be arranged at various locations in each region, however, all clients, stationery and mobile, shall have the ability to install the required software, upgrades and patches using the existing DHS network and ICE-owned Big Fix utilities. Follow up with individual users for completion of installation will be accomplished by FPS personnel.

2.2.4 Mobile Computing Devices (MCDs):

The appropriate software shall be installed and configured on existing mobile computing devices used by the law enforcement users. MCD’s will connect to the DHS network via a Sprint AirCard or may be connected to the ICE network via a Local Area Network at a regional office or at a MegaCenter. When connected to the ICE network via the AirCard, a VPN Token is used to provide a secure connection. MCDs do not have GPS capability built in.

2.2.5 The system shall have the capability to integrate alarm location, floor plans and building data. CADIS will interface to the ESRI database to obtain floor plan and alarm data for approximately 9000 buildings. There are one to many floors in each building. This capability will be delayed from the initial deployment, and may be implemented in Option Year 2 or later of the CADIS implementation.

2.3 Best practice implementation of cadis product

It is the intent of FPS to adapt to the current industry best practices as it relates to the FPS operating procedures and the operating environment of CADIS. Implementing CADIS will enable key FPS stakeholders the opportunity to assess current operating procedures against any productivity gains that can be realized through the introduction of automation. Consequently, neither a blanket “technology driving the process,” nor a “process driving the technology” approach will be embraced, but a balanced approach that seriously evaluates the cost/benefit trade-off in moving from current to new operating procedures.

3.0 SCOPE OF WORK

The Contractor shall perform work in accordance with this SOW and exercise a methodical approach to planning, organizing and managing resources to procure and provide all labor, software licenses and materials to successfully integrate, provide training, deliver and deploy a robust, expandable, and scalable enterprise-level COTS based system. This product shall have computer aided dispatch, records management, and Geospatial information capability and shall satisfy the functional requirements identified in the CADIS Functional Requirements Document (FRD – which is attachment #3).

The contract shall execute Project Management Institute (PMI) best practices from the Project Management Body of Knowledge (PMBoK) methodology to support the CADIS project. The Contractor shall provide the best business processes as prescribed by industry and the selected product to identify the as-is and to-be business processes, and to the extent possible implement those selected best practices.

The Contractor shall adhere to the guidance and standards outlined in Section 4.3. The effort shall follow a pre-defined ICE Architecture Division System Lifecycle Management (SLM) work pattern for COTS/GOTS (Government-Off-The-Shelf) products that incorporates a reduction of design and development activities.

4.0 APPLICABLE DOCUMENTS

4.1 Technical Documents and Resources for References

The technical documents below are applicable to this SOW and will be made available as part of Government Furnished Information (GFI) via CD or Government Furnished Website.

· Architecture Test and Evaluation Plan

· CADIS Functional Requirements Document

· DHS/ICE Baseline Security Requirements

· DHS Section 508 Guide for Accessible Web Content

· Enterprise Systems Assurance Plan

· ICE System Lifecycle Management Handbook (SLM)

· ICE Technical Architecture Guidebook

· ICE Technical Reference Model

· IT Security Program Handbook (DHS Mgmt Directive 4300A, version 5.5)

· MCD CF 19 Toughbook Specs

· National Incident-Based Reporting System (NIBRS)

· Office of Management and Budget (OMB) Circular A-11, Part 7

· Project Tailoring Plan Template

· System Lifecycle Management (SLM) Gate Review Document and SLM Work Patterns

4.2 OTHER SUPPORTING DOCUMENTATION AND GUIDANCE

The documents listed below will be made available as part of GFI via CD or Government Furnished Website. Additional references are listed in the FRD.

· CADIS FRD

· RAMP MCD technical specification (MCD CF 19 Toughbook Specs)

4.3 COMPliance with STANDARDS AND PROCESSES

The Contractor shall ensure that the system is in full compliance with all DHS and ICE Enterprise Architecture (EA), SLM and security guidelines and regulation and the "DHS AD 102.01". The Contractor must comply with all technology standards and architecture policies, processes, and procedures defined in ICE OCIO Architecture Division publications and DHS Architecture Division publications. These publications include, but are not limited to, the following:

· DHS/ICE Architecture Test and Evaluation Plan

· DHS/ICE Enterprise Systems Assurance Plan

· DHS/ICE System Lifecycle Methodology Handbook, Pre-defined COTS Work Pattern. The ICE SLM is in compliance with the DHS System Development LifeCycle methodology (SDLC)

· DHS/ICE Technical Architecture Guidebook

· DHS/ICE Technical Reference Model

· DHS/ICE Web Standards and Guidelines

The Contractor shall not deviate from the technology standards that are specified in the above documents, without express approval granted by the Government via the formal Technology Change Process. If a deviation from the technology standards is desired, the Government Project Manager must submit a formal request to the Architecture Division for adjudication. The Contractor shall not proceed with the deviation unless the Architecture Division approves the formal request and grants a waiver to deviate from the Technology Standards. If the Architecture Division approves the technology change request, the Contractor shall comply with all stipulations specified within the approval notification.

The Contractor shall not deviate from the SLM Process (including any tailored SLM work pattern) without express approval granted by the Government via the formal Request for Deviation (RFD) Process. If a deviation from the SLM Process is desired, the Government Project Manager must submit a formal RFD to the Architecture Division for adjudication. The Contractor shall not proceed with the deviation unless the Architecture Division approves the formal request and grants a waiver to deviate from the SLM Process. If the Architecture Division approves the RFD, the Contractor shall comply with all stipulations specified within the approval notification.

5.0 SPECIFIC TASKS

The requirements listed in this section are a representative sample of the complete requirements, which may be found in the CADIS FRD.

5.1 Program Management support

The Contractor shall establish and implement the operating procedures and oversight activities necessary for project planning, Work Breakdown Structure (WBS), quality assurance, and risk assessment. Centralized administrative, clerical, and documentation support shall be provided. The Contractor shall manage project metrics, risk, and schedule items.

The Contractor shall comply with Capability Maturity Model Integration (CMMI) Level 2 Process Areas, including Requirements Management, Project Planning, Project Monitoring and Control, Supplier Agreement Management, Measurement and Analysis, Process and Product Quality Assurance, and Configuration Management.

The Contractor shall develop and deliver a Project Management Plan (PMP). Reporting cycles begin with Government acceptance of the PMP. The PMP shall describe the management, technical, and organizational approach, resources, and controls to be employed to meet CADIS cost, accomplish project planning, and schedule requirements. The PMP shall include a WBS with associated dictionary to reflect actual activities. The WBS shall trace all work; serve as framework for defining and planning project work segments; be constructed as a logic-network employing Critical Path Methodology (CPM) representing all proposed activities, milestones, and major deliverables for the project period of performance; shall be sufficiently detailed to mitigate risk and measure performance; shall be delivered using an MS Office Suite product.

The Contractor shall participate in weekly teleconference or video teleconference meetings to report progress toward contract deliverables, update status from the previous reporting period, advise current objectives, problems or delay issues, proposed corrections and responsible parties; meeting minutes that capture discussions held and key action items shall be provided within two business days following each meeting, and include minutes from all significant meetings in a Weekly Project Status Reports to the Contracting Officers Technical Representative (COTR).

5.2 Commercial Off-The-Shelf (COTS) Computer aided dispatch SYSTEM The Contractor shall provide a COTS COMPUTER AIDED DISPATCH system that shall have the capability to collect, modify, store, retrieve, and process record management and geographic information data. The system shall provide a level of scalability and compatibility with other DHS, ICE, and FPS systems and shall always be in compliance with emerging DHS enterprise architecture. The Government will notify the Contractor of any such changes.

This system shall:

· Be fully NIBRS compliant.

· Implement a system availability of 99.999 percent when measured on a 24-hour per day, seven day a week basis for 365 days. Processor, disk storage, and power supply redundancy may be required in order to achieve the desired availability and protection of information. The system shall be configured such that operating a training component and/or running reports will not affect system response time. This availability requirement applies both to dispatch capabilities and records management components. There is no offline requirement for dispatch functions.

· Interface with external applications and data sources listed in section 5.9.

· Have the ability to push the client application via the DHS network to desktops and Mobile Computing Devices (MCD) utilizing Big Fix.

· Allow a user the ability to access the application, download appropriate information and forms relating to incidents, and submit the necessary information without re-keying information.

· Allow the capability to be directly expandable by adding hardware and Commercial-Off-The-Shelf (COTS) modules.

· Include a feature for backup, archival, and recovery capability without taking CADIS out of service and with minimal impact on dispatch operations.

· Provide the capability for users to work offline in the event of connectivity failures, and the capability to continue to work off-line in the event the failure occurs in the middle of a session without any data loss, and to upload saved offline data when connectivity is re-established. The CADIS architecture for this capability must meet DHS Management Directive 4300A. Therefore, peer-to-peer architectures are not allowed.

· Contain data exporting capabilities. CADIS must have the capability to export data in industry standard database formats to facilitate providing data to other databases controlled by DHS and/or other Government entities.

· Be able to generate standard automated forms and templates to be used by all regions; such as incident report, spot report, etc.

· Contain a wide variety of reports and statistical information for analysis and management reporting and/or reporting requirements in real time.

· Allow ad-hoc, dynamically generated reports such that code modifications are not required for each new report.

· Provide the capability to archive active incidents indefinitely and archive dispositioned or closed incidents for a minimum of 12 months.

· The Contractor shall:

1) Provide a development and integration environment with Government supplied equipment as needed.

2) Add backup processes and contingency plan which shall include manual process of data during controlled outages and in case of disaster.

3) Provide a development and testing environment. Documentation shall be delivered to and maintained in the government provided Electronic Library Management System (ELMS). Access to ELMS from the contractor’s work site will be enabled.

5.3 SOFTWARE Configuration and Implementation support

The Contractor shall deploy and integrate a COTS system that provides a level of scalability and compatibility with other DHS, ICE, and FPS systems and is in compliance with current DHS/ICE enterprise architecture.

Within 45 business days after contract award, the Contractor shall provide an initial report detailing their architectural and COTS based system configuration approach, implementation strategy, COTS/GOTS SLM documentation/review approach, and their ability to reinforce other ICE mission applications. This information shall be included in the Project Management Plan.

The Contractor shall provide software and hardware implementation in compliance with the CMMI Level 2 standards. The Government estimates that a minimum of 600 concurrent users shall be able to access all CADIS applications at regional offices, from dispatch workstations, and MCDs. An Enterprise license is required to support the minimum projected user base. Consider that CADIS has a maximum potential projected user base of about 1250 users across the 50 states and territories. When costing CADIS client licenses, the Government anticipates licenses will be priced based on user roles. There are approximately 900 LEOs who will utilize MCDs. There are approximately 125 dispatchers. The Government currently anticipates that of the 600 concurrent users, 100 would be dispatchers and 900 would be LEOs.

The Contractor shall:

· Provide implementation support of the CADIS at all four MegaCenters located in Denver, Colorado; Battle Creek, Michigan; Suitland, Maryland; Philadelphia, Pennsylvania; Glynco/FLETC Training Center, Washington DC, and 11 regional offices. CADIS will initially be hosted in the FPS MegaCenters and eventually move to the DHS datacenters.

· CADIS is fully operational at four MegaCenters: Suitland, MD, Battle Creek, MI, Philadelphia, PA, and Denver, CO. Each MegaCenter dispatches personnel to its own region(s). The MegaCenters operate in pairs, such that if one of the pair is down, the other takes over dispatching for the other. Suitland is paired with Battlecreek. Philadelphia is paired with Denver. None of the MegaCenters provides backup for a MegaCenter outside the pairing. For example, If Suitland is down, Battle Creek takes over their dispatching and vise versa. But Suitland does not take over dispatching for Denver or Philadelphia. Therefore, all four MegaCenters function as both a primary and a single backup site. When a MegaCenter is acting as a backup site, it is considered the Disaster Recovery site.

· Incorporate workflow capability and flexibility; Support FPS in their development of operational procedures to support the new CADIS capabilities.

· Integrate software that will allow users to view available historical data for each individual system user.

· Integrate software that will allow for broader search/query capabilities, avoiding and/or eliminating the need to continually require ad-hoc code writing.

· Design the software with internal flagging capability based on incident reporting. These flags would permit prioritizing leads to be pursued by the FPS Inspectors or other Federal law enforcement entities.

· Allow users to access and interact with the CADIS application.

· Conduct the necessary testing in accordance with the ICE SLM Pre-defined Work Pattern for COTS/GOTS products to ensure functional capability and ease of use.

· Maintain software development libraries to facilitate the development, testing, and implementation of software.

· Follow detailed guidance contained within the FRD regarding system functional requirements and timing for delivery of functionality.

· Design the application and development and test environments in compliance with ICE OCIO Application Hosting Services (AHS) such that it can be hosted at the MegaCenters. CADIS will initially be hosted in the FPS MegaCenters and eventually move to the DHS datacenters.

The Contractor shall prepare for and participate in SLM reviews to ascertain progress in defining system technical requirements; determine systems engineering direction and progress, and the degree of convergence on a balanced, complete configuration.

5.4 CADIS Deployment Considerations

The Contractor shall be aware of the following considerations as they relate to the deployment of CADIS:

5.4.1 The CADIS servers and system shall be completely installed, tested, implemented, and operational for at least three months in the four FPS MegaCenters, prior to deploying to the MCD users.

5.4.2 All dispatch and system administrator users shall be trained prior to operational implementation of the system.

5.4.3 Geographic locations of clients:

1) Dispatch clients are located in the MegaCenters in Denver, Colorado; Battle Creek, Michigan; Suitland, Maryland; and Philadelphia, Pennsylvania. All workstations are considered GFE.

2) Regional/Reporting Clients, including mobile and desktop users, are located nationwide but organized into eleven regions plus the Headquarters office in Washington, DC.

5.4.4 All upgrades and patches to CADIS software shall be deployed to desktop computers and mobile clients using the existing DHS network and Big Fix utilities. Follow up with individual users for completion of installation will be accomplished by FPS personnel.

5.4.5 Mobile Computing Devices (MCDs):

The appropriate software shall be installed and configured on existing mobile computing devices used by the law enforcement users. MCD specifications will be provided as an attachment to this SOW. Deployment to MCDs is to occur no sooner than three months after successful implementation of the system in the MegaCenters. All LEO users shall be trained prior to distribution and implementation of the system to desktop and mobile computers.

5.5 DATA MIGRATION and transition

The Contractor shall plan and execute a successful data migration and transition effort, migrating a total of approximately 800,000 records from the current legacy DOL and a total of 33,000 records from WebRMS systems to CADIS. Prepare a detailed Data Migration and Transition Plan as defined by the SLM, making use of a structured multi-phase methodology that includes multiple (a) Data Discovery; (b) Analysis, Mapping and Planning; (c) Data Extraction, Translation and Load (ETL) Strategy and Planning; (d) Mock Conversions, Cleansing and Validation; and (e) Full Migration and Deployment phases. File formats for DOL and WebRMS will be provided during the post-award requirements definition phase of the project. Based on the outcome of the requirements definition effort, the Government may determine that it is not in its best interest to migrate historical data.

5.6 OPERATIONS AND MAINTENANCE (O&M)

The Contractor shall fully maintain the CADIS application system and software developed under this task. Tasks include, but are not limited to the following:

· Maintain the application to identify and correct software application, performance and implementation failures for all CADIS components. Maintenance includes emergency repairs performed when immediate correction is necessary to continue user service corrective work [includes System Change Requests (SCRs)] or to reflect requirements/specifications, and updating and maintaining the required SLM documentation, as necessary. If vendor support is required on-site, this must be accomplished within 72 hours during normal business hours.

· Perform maintenance tasks to meet changes in requirements of the users or user environment; enhance the system to provide additional or changed functionality; adapt the system to changes in business processes; or extend software to new users.

· Maintain the current external CADIS interfaces as identified in section 5.9. Provide adaptive support in instances where external connection requirements change.

· Provide coordination with FPS and field personnel, including assistance with defining and configuring user accounts in CADIS, and preparation of information to be disseminated to customers, including brochures and informational sheets.

· Implement IT management concepts and policies consistent with the Information Technology Infrastructure Library (ITIL) version 3.

· Assist FPS in developing the initial Standard Operating Procedures (SOPs) for the CADIS system and maintain them throughout the period of performance.

· Provide updated SOP scripts and procedures to staff when new information, releases or changes regarding CADIS have been distributed and/or implemented.

· Perform all system administration activities associated with ICE application processes under this SOW, as specified. These activities shall include monitoring and compilation of data statistics for batch and interface production processing; identification of corrupt files or processes; and system archiving and data archiving when applicable.

· Staff a full-time (24 x 7 x 365) Tier 2/3 experienced national CADIS Help Desk to provide COTS product support. Tasks shall include but are not limited to the following:

· Maintain the current external CADIS interfaces as identified in the final FRD.

· Meet with the COTR on the technical issues on an as needed basis at the discretion of the Government Project Lead.

· Produce Help Desk Support documentation as required. This documentation will include information on Frequently Asked Questions and protocols for such common tasks as password resets, call routing, and hardware support and maintenance.

5.7 Configuration MANAGEMENT

The Contractor shall conduct configuration management for all development and maintenance tasks under the guidelines set forth by the ICE OCIO Architecture Division; conduct project-level configuration management for all development and maintenance work for the applications/database; execute all approved requests for changes to establish baselines via the approved SCR process, assist with chartering and conducting Change Control Board (CCB) meetings; assign proper identification of all configuration items in accordance with agreed on conventions. This includes the proper labeling of all software releases, regardless of content; and, submitting an electronic version of all deliverables to the ICE’s Electronic Library Management System (ELMS) library.

5.6.1 MANAGEMENT SYSTEM CHANGE REQUIREMENTS

Software changes to applications are based upon the submission and Government approval of an SCR. The Contractor shall be responsible for carrying out all application maintenance requirements projects according to open SCRs and entering the data in the ICE approved management tracking tool. Currently, ICE uses Serena Tracker. Prior to commencing a system modification, the OCIO and FPS Project Managers will determine the degree of the modification as minor, moderate, or major; prioritize execution of SCR efforts and direct the Contractor to perform activities to address SCR emergency maintenance will be performed at the direction of the Government. The respective OCIO Project Manager must approve all SCRs in writing.

All SCR related work shall be part of the O & M effort and therefore shall be Cost Plus Fixed Fee. It is anticipated that a given number of personnel will be dedicated to the O & M effort to accomplish the SCR work. The offeror is expected to propose a given number of personnel that they think will be required to maintain the CADIS system. Those personnel will also do the SCR work. The volume of changes to the system is not expected to be more than a few per month, once all the interfaces have been developed and implemented.

The Contractor, at a minimum, shall perform the following activities in support of executing SCR activities:

· Align activities to conform to ICE SLM requirements

· Collect, validate and document SCRs

· Define, analyze, plan and document the full scope of the SCRs

· Determine external factors and interdependencies related to SCRs

· Assigning roles and responsibilities to contract personnel supporting the SCR effort

· Execute authorized activities in support of SCR efforts

· Review and analyze time history of SCRs

· Evaluation of outcomes of SCRs (Quarterly)

· Reporting on changes on the project, and deviation from change management plan

· Maintain an archive (history) of changes in the system

5.8 TRAINING

The Contractor shall develop a training plan leveraging existing COTS based system training material for all three user categories. The Government anticipates that training shall cover approximately 16 system administrators and 125 dispatchers located at the four MegaCenters for the initial system implementation. Training of approximately 900 LEOs throughout the U.S. and its territories is required prior to system deployment to MCDs. Training of new hires thereafter will be accomplished by FPS and will not require the support of the selected contractor.

Specifically, the Contractor shall develop and submit a CADIS Integrated Training Plan for Government approval, and subsequent Contractor execution. The plan shall emphasize the business processes and standard operating procedures relating to the new system to provide a broader scope to users and enhance understanding with all users. The Contractor shall propose a blended training approach that provides overall best value and the best approach to training based on the contractor’s experience in providing training for their product.

The plan must, at a minimum, include the following elements:

1) A training approach that takes into account overall cost and operational requirements, and that has a minimal impact on day-to-day operations.

2) Initial user training:

· All users shall receive a general overview of the system, its functionality, and operation..

· Specific users shall receive training on operational procedure changes associated with the implementation of CADIS.

· Dispatch and system administrator training at each of the four MegaCenters including interactive, hands on use of the system.

· LEO users through the most cost effective means.

3) Refresher training: All dispatch and system administrator users shall receive annual refresher training conducted at each of the four MegaCenters.

4) Maintaining Training Documentation: Maintain and update existing training documentation as well as provide an electronic copy of all training material whenever an update is developed.

5) Be accessible to all applicable FPS users – both Government and Contractors - and FLETC.

5.9 certification and accreditation The Contractor shall assist ICE Information Assurance Division (IAD) in developing, implementing, and maintaining a Certification and Accreditation (C&A) program, by providing information to IAD that complies with DHS and other Federal requirements and supports the ICE enterprise. The Contractor shall provide support activities that enable the establishment and maintenance of a C&A status of Authority to Operate (ATO). Specific tasks include:

5.9.1 The Contractor shall provide security artifacts in support of the CADIS ICE Security requirements and governance.

5.9.2 The Contractor shall support the CADIS Information Systems Security Officer (ISSO) in the development of the following and related security documents:

5.9.2.1 Privacy Threshold Assessment (PTA) and resultant Privacy Impact Assessment (PIA)

5.9.2.2 System Security Plan (SSP)

5.9.2.3 Security Test and Evaluation (ST&E)

5.9.2.4 Security Assessment Report (SAR)

5.9.2.5 Vulnerability Scanning Assessment

5.9.2.6 Other Security Related Documents

5.9.3 The Contractor shall provide technical expertise on C&A, Federal Information Security Management Act (FISMA), and other information assurance activities.

5.9.4 The Contractor shall verify that information assurance is being addressed throughout the SLM process.

5.9.5 The Contractor shall prepare specified CADIS Major Applications (MA) C&A documentation to include the C&A artifacts listed above in accordance with the appropriate National Institute of Standards and Technology (NIST), DHS C&A methodology, and other Federal guidance.

5.9.6 The Contractor shall verify that information assurance is being addressed throughout the SLM process.

5.9.7 The Contractor shall provide guidance, recommendations, manage and execute activities in support of CADIS:

5.9.7.1 Risk assessment and management activities as part of the SSP and SAR process;

5.8.6.1.1 Identify, monitor and manage risks based upon the 19 OMB Risk Facets

5.9.7.2 Evaluation and management of CADIS Plan of Action and Milestones (POA&M) criteria and the assured completion of; and

5.9.7.3 Quality assurance reviews of IA-related documented processes and procedures, as it pertains to C&A activities.

5.10 INTERFACES:

CADIS will have the capability to interface with the systems below. Separately propose costs to interface CADIS with each of the following third-party systems. It is the intent of the Government to incorporate some of the interfaces for implementation and delivery with the initial contract award, and others at a later date. Regardless, the Government may unilaterally exercise any, all, or none of these interfaces. Detail functional specification for these interfaces will be developed during the functional requirements definition phase of the project.

5.10.1 Interfaces Expected Upon Initial Deployment

The following interfaces are expected to be operational upon the initial deployment of CADIS.

INTERFACE A: Risk Assessment Management Program (RAMP) Optional – to be negotiated, do not price

CADIS components shall interface with and automate data received from the FPS RAMP system. RAMP is the centralized source of information used by FPS for risk assessment and management including all information on federal facilities, contact information, and much more. RAMP is the system of record for FPS. CADIS will access building information, including building number, address, contact information and other general information from RAMP. The CADIS-RAMP interface must be able to parse the data, update call records in the CADIS, populate the CADIS screens, update RMS, and provide address data to GIS. The final deliverable product will be the successful integration of CADIS and RAMP through integration, certification, and “live” demonstrated operation.

interface B: Post Tracking System (PTS) Optional – to be negotiated, do not price

CADIS components shall interface with and automate data received from the FPS PTS. PTS is the centralized source of information used by FPS for tracking whether guard posts are manned as required. PTS’s purpose is to ensure that the Contractors are meeting the requirements of their contracts, such as ensuring that guard posts are staffed with guards that meet the Government’s training and certification requirements. PTS information is used to compare, reconcile, and certify the invoices submitted by the Contractors prior to payment.

The CADIS-PTS interface must be able to provide CADIS with guard post information such as guard post location, the name of the guard manning the post, and the guard post contact information. The final deliverable product will be the successful integration of CADIS and PTS through integration, certification, and “live” demonstrated operation. PTS will be available for PTS integration during the development phase of CADIS.

INTERFACE C: National Crime Information Center System (NCIC) CADIS shall interface with the NCIC. The interface must include interfaces for NCIC database queries meeting state and federal specifications. The CADIS – NCIC interface must meet each state’s regulations. The NCIC database inquiry or query will give the user pre-defined entry fields to aid in entering data into those fields. This capability must provide the user with interactive tools informing the user of specific query fields requiring data entry for each state in the regions, and inform the user of the format and exact number and structure of data characters required. The CADIS–NCIC interface must authenticate users’ Social Security numbers by automatically including it in the ‘sent query’, and must provide secure connection to each state meeting state and local security regulations. All NCIC query returns must be presented, accessed for display, and/or printed in a simple manner by the user, and stored in the CADIS RMS database subject to random access for review based on user privileges and security. The final deliverable product will be the successful interface between CADIS and NCIC through integration, certification, and “live” demonstrated operation.

INTERFACE D: National Law Enforcement Tracking System (NLETS) CADIS shall interface with the NLETS database and perform NLETS database inquiries. The interface must include interfaces for NLETS database queries meeting state and federal specifications. The CADIS-NLETS interface must meet NLETS regulations. The NLETS database inquiry or query will give pre-defined entry fields to aid the user in entering data into those fields. This capability must provide the user with interactive tools that inform the user of the specific query fields requiring data entry, and inform the user of the format and exact number and structure of data characters required. The CADIS–NLETS interface must authenticate users’ Social Security numbers by automatically including the number in the ‘sent query’, and must provide secure connection to NLETS meeting, NLETS security regulations. All NLETS query returns must be presented, accessed for display, and/or printed in a simple manner by the user, and stored in the CADIS RMS database, subject to random access for review, based on user privileges and security. The final deliverable product will include the successful interface of CADIS and NLETS through integration, certification, and “live” demonstrated operation.

interface E: Security information system (SIS) Optional – to be negotiated, do not price CADIS components shall interface with and automate receiving information from the SIS. SIS is a central station for automatic alarm monitoring. There are four independent SIS systems that will provide alarm data to the CADIS system operating in the four MegaCenters. The geo-located alarm points are available through the SIS alarm monitoring system. The CADIS interface accepts the data feed over a serial link formatted using XML. The CADIS interface must parse the data and create a call record to notify the system that there is an alarm. The final deliverable product will be the successful integration of CADIS and SIS through integration, certification, and “live” demonstrated operation.

5.10.2 Interfaces Expected After Initial Deployment

The following interfaces are expected to be operational options after the initial deployment of CADIS, as directed by the Government

INTERFACE F: State Crime Information Center SYSTEMS Optional – to be negotiated, do not price In addition to NCIC, CADIS shall provide the same interface functionality of NCIC for each state’s and territory Crime Information Center. In light of recent regional efforts to better share information, the Contractor shall investigate whether interfaces are required with each state jurisdiction where CADIS is deployed, or whether regional interfaces may be more appropriate.

INTERFACE G: DHS/ICE geospatial database Optional – to be negotiated, do not price CADIS GIS component shall integrate, and interface with the DHS / ICE existing geodatabase repository for the purpose of importing base maps and map layers. The geospatial data will be used by CADIS to display facility and officer locations, traffic maps, street maps, and any other geographic information required by FPS. The interface must adhere to DHS/ICE standards, and existing Geospatial Repository (GRR) datasets that use the Environmental Systems Research Institute (ESRI) product suite. CADIS Geospatial interface must provide local base map and map layer data access for use by the CADIS system. The interface specifications will be defined during requirements definition phase. There are no predefined workflows. FPS will use the workflows extant in the selected COTS product. CADIS GIS data is updated by GSA, as needed when building data changes. Those changes are automatically reflected in the ESRI database available to CADIS.

interface H: ICEPIC Optional – to be negotiated, do not price CADIS components shall integrate with and automate report input to the ICE Pattern Analysis and Information Collection System (ICEPIC). The interface must include interfaces for CADIS database queries meeting state and federal specifications. The interface specifications will be defined during requirements definition phase. The CADIS database inquiry or query will provide pre-defined entry fields to aid the user in entering data into those fields. This capability must provide the user with interactive tools that inform the user of specific query fields requiring data, and inform the user of the format and exact number and structure of data characters required. The CADIS– ICEPIC interface must authenticate users’ Social Security numbers by automatically including the number in the sent query. The interface must provide secure connection to ICEPIC that meets ICEPIC security regulations. All ICEPIC query returns must be presented, accessed for display, and/or printed in a simple manner by the user and stored in the CADIS RMS database subject to random access for review based on user privileges and security. The final deliverable product will be the successful integration of ICEPIC and CADIS through integration, certification, and “live” demonstrated operation. The CADIS RMS module must be capable of interfacing with the ICEPIC to allow for a CADIS user to enter a query and receive results that are stored in CADIS.

5.11 Phase In

The Contractor shall identify all their Key staff and have critical project management support staff and other critical positions and subcontractors on-board and through the ICE Security process within 90 days after the contract is awarded.