CADIS_Sol_04082010.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) outlines the current high-level functional and technical requirements for the Computer Aided Software Information System (CADIS) procurement. The effort is sponsored by the Department of Homeland Security (DHS), National Protection Programs Directorate (NPPD), Federal Protective Service (FPS), and the Immigration and Customs Enforcement (ICE) Office of the Chief Information Office (OCIO).

2.0 BACKGROUND

FPS is responsible for providing security and law enforcement services for federal facilities. FPS has many divisions. There are five FPS divisions that are the main stakeholders in the CADIS project:

1. Communications Management Division (MegaCenter Operations)

2. Risk Management Division

3. Uniformed Operations Division (Law Enforcement)

4. Threat Management Division (Investigative)

5. Firearms and Training Division (Law Enforcement Training – FLETC)

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. Reporting and management is done from FPS Headquarters in Washington, D.C. and from 11 regional offices. The current 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

· Lack of Standard Operating Procedures (SOPs) Across MegaCenters and LEO components 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 Dispatch Operations Log (DOL) and Web Records Management (WebRMS) systems and include the following three components:

1) Computer aided dispatch

2) Incident management with records management and reporting

3) Geographic information CADIS goals support the missions of DHS and FPS:

· DHS’s mission is to lead the unified national effort to secure the country and preserve our freedoms.”

· FPS’s mission is to keep America safe by mitigating risk to federal facilities and their occupants.

2.1 EnVISIONED CAPABILITies for the CADIS COTS based Solution 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. Scalability must include expansion of the business operations based on new required functionality and expansion of the volume of incidents that CADIS must handle.

Furthermore, the system must reflect the seamless integration of the following three functional components:

1) Computer aided dispatching of Law Enforcement Officers (LEOs) that are dispatched in response to incidents. The Dispatching of personnel from the MegaCenters is accomplished with 3 operations functions: Alarm Monitors, Call Takers, and Dispatchers.

2) Records management and reporting to collect, share, and report incident information based on National Incident Based Reporting System (NIBRS) standards. FPS currently uses some proprietary codes mixed with NIBRS codes. It is the intention of FPS to convert to an all-NIBRS coding scheme. FPS needs a system to conduct efficient call center management, which includes automated data collection, call routing, and viewing incidents and call history, etc.

3) Geospatial Information System component 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. CADIS does not have to provide a Chemical, Biological, Radiological or Explosive (CBRNE) Component. However, if the COTS product being proposed has such capabilities, the Government would like to know about them.

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.

It is envisioned that 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 records 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 alarm monitoring, including Intrusion Detection System (IDS) and Access Control System (ACS) alarms, and fire alarms. Each MegaCenter has an independent SIS system, linked to a Radionics 6600 alarm panel. Each MegaCenter maintains a unique database of alarms. In the event of failover from a failed MegaCenter to a backup MegaCenter, the backup MegaCenter shall integrate the alarms from the failed MegaCenter with their own. The interface between SIS and DOL is effectively a manual interface today. The Government wants to automate the interface between SIS and CADIS. If it is within the capability of the COTS product to do so, the Contractor shall specify how this would be done.

CADIS will consolidate geographical and functional alarm inputs, the dispatch decision-making and recordkeeping sites, and dispatch communications hub for FPS. CADIS will be able to dispatch from any of the four FPS MegaCenters to any LEO within the United States and its territories.

In the event of a failure of a MegaCenter whereby it cannot do the dispatch functions, one of the other MegaCenters must be capable of assuming the workload of the failed MegaCenter, process incoming calls, monitor alarms, and dispatch LEOs regardless of the region they serve. Currently, the MegaCenters operate and backup each other in pairs. Battle Creek backs up Suitland & vice versa; Denver backs up Philldelphia and vice versa. The Government wants to improve this backup capability, if possible. The Contractor shall specify their approach to providing backup and failover of one MegaCenter to another. Upon restoration of service in the failed MegaCenter, the system must be able to synchronize the data and make visible and available for action in the restored MegaCenter, all incidents created by the backup MegaCenter.

In addition, CADIS must:

· Be fully NIBRS compliant. However, CADIS does not have to send NIBRS reports to the FBI.

· Implement a system availability that provides 24 x 7 x 365 operational readiness with minimal outages for maintenance and implementation of software application changes and upgrades. Since this is a Law Enforcement System, the Government wants the system to be available and operational as close to 99.5 % of the time as is possible. The Contractor shall specify the level of availability they expect to be able to provide.

· 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.

· 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.10.

· Have the ability to push the client application via the DHS network to desktops and Mobile Computing Devices (MCD) utilizing Big Fix. The Contractor shall develop the MicroSoft Installation (MSI) packages that are used by Big Fix to deploy the client applications.

· 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. Expansion shall include expansion of business functionality, as well as expansion of the volume of incidents processed.

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

· 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 via an interface to the Risk Assessment Management System (RAMP).

· Archiving: Incidents that are open must be available online until they are dispositioned. Incidents that have been dispositioned must be kept a minimum of 12 months. Depending on the type of incident, retention of incidents beyond 12 months will vary. Retention periods for all types of incidents will be specified during the requirements definition phase.

· The Government will manually install all server application components and manually deploy all client application software to the workstations in the MegaCenters.

2.2 CADIS Deployment Considerations

THIS SECTION HAS BEEN MOVED AND COMBINED WITH SECTION 5.4 CADIS DEPLOYMENT CONSIDERATIONS

2.3 Best practice implementation of cadis product

It is the intent of FPS to adopt 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. The Contractor shall execute PMI best practices from the PMBOK and follow the ICE SLM COTS/GOTS work pattern.

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 proven, 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).

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

· RAMP MCD technical specification (MCD CF 19 Toughbook Specs) The documents listed above are available for downloading from the FedBizOpps web site where this solicitation is posted.

4.2 OTHER SUPPORTING DOCUMENTATION AND GUIDANCE

THIS SECTION WAS MERGED WITH 4.1 above

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 Information Technology Change Request (ITCR) 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.

The Contractor shall provide software and hardware implementation in compliance with the CMMI Level 2 standards using the ICE SLM processes. The Government expects the Contractor to have been assessed at CMMI level 2 in order to submit a proposal. Either the COTS vendor or the Integrator must have achieved a CMMI level 2 assessment.

5.0 SPECIFIC TASKS

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 management. 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 provide a draft Project Management Plan (PMP), and within 45 business days after contract award, the Contractor shall provide a final PMP detailing their architectural and COTS system configuration approach, implementation strategy, COTS/GOTS SLM documentation/review approach, and their approach to developing Standard Operating Procedures (SOPs), The PMP shall also include a project schedule for the Base Year, with work breakdown structure.

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 Microsoft Office 2003 Product Suite. .

The Contractor shall participate in daily and/or 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. The Contractor shall provide a Weekly Project Status Report to the Contracting Officers Technical Representative (COTR). The Contractor shall assist the COTR in creating monthly status reports, OCIO Project Activity Reports (OPAR) and Program Management Reviews (PMRs).

5.2 Commercial Off-The-Shelf (COTS) Computer aided dispatch SYSTEM The requirements listed in this document are a representative sample of the complete requirements, which may be found in the CADIS FRD. The complete requirements specified in the CADIS FRD comprise the requirements that must be fulfilled by the delivered system.

The Contractor shall identify which requirements in the FRD will be satisfied by the COTS product “out-of-the-box”. Software configurations that must be accomplished in order to fulfill a requirement are considered part of the “out-of-the-box” functionality. Any software program code changes required to meet a requirement are considered enhancements and not “out-of-the-box” functionality. Therefore, interfaces may not be “out-of-the-box” functionality, unless the COTS product already has the interface; e.g., the NCIC interface may be a standard feature of the COTS product and would therefore be “out-of-the-box” functionality.

5.3 SOFTWARE Configuration and Implementation support

The Contractor shall deploy and integrate a COTS system that provides a level of scalability and compatibility and that continues to be compliant with the DHS/ICE enterprise architecture. The COTS product shall be scalable to meet increasing volumes of alarms, calls, incidents, and reporting requirement needs of an expanding FPS business. FPS cannot predict how big this expansion will be or how quickly it will take place. The COTS product shall also be expandable to meet future requirements to support new business processes. The Government understands that if the product does not currently provide a function to support a new business process, it may have to be enhanced. It is the ability to be enhanced that the Government is seeking.

The Contractor shall:

· Work with FPS to determine how to configure the COTS product to support the FPS business processes and develop Standard Operating Procedures (SOPs) for CADIS for the MegaCenters, Headquarters and Regional offices, and for LEOs. FPS expects to adopt the business processes and workflow of the COTS product with no programmatic changes being required.

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

· Support implementing CADIS in the Government’s Functional Quality Test (FQT), User Acceptance Test (UAT), Training, System Assurance Test (SAT), and Production environments.

· Develop all required SLM documentation and deliver it to and maintain it in the government provided Electronic Library Management System (ELMS). Access to ELMS from the contractor’s work site will be enabled. The Government shall provide the Contractor a laptop with VPN token and the ability to access ELMS from the Contractor’s facility.

· Provide implementation support of 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. While the Government does the installations, the Contractor may be required to attend the implementation at Suitland, MD. The Contractor would not normally be expected to attend installations at any other facility.

· Integrate software that will allow users to view available historical data for user activities of all system users.

· Provide a CADIS system that will allow for broad search/query capabilities, including ad-hoc reporting. Provide standard “canned” reports if they are available “out-of-the-box” with the COTS product.

· 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.

· 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.

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

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

· 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

This section defines the requirements for the deployment of CADIS.

5.4.1 Numbers of users and licenses:

1) There are 20 operations consoles at Suitland, 19 at Battle Creek, 18 at Denver, and 14 at Philadelphia. The Government wants concurrent licenses for all 71 of the operations consoles.

2) There are approximately 900 LEOs who have MCDs. The Government wants 500 concurrent client licenses for the MCDs and 100 additional licenses for other types of workstations, for a total of 600 client licenses.

3) In addition, there are approximately 1700 Records Management and Reporting users. The Government wants 800 concurrent licenses to support them.

5.4.2 Geographic Location of Servers and Clients:

1) CADIS will initially be hosted on servers in the FPS MegaCenters and may eventually move to the DHS datacenter. COTS vendors shall specify in their proposal the requirements for servers and workstations necessary to support the COTS product in the MegaCenter environment. Servers and operations consoles exist in all MegaCenters today. If current capacity is not sufficient to meet the COTS product’s requirements, the Government will procure and upgrade the servers and workstations at the MegaCenters to meet the stated requirements from the COTS Vendor. The Contractor shall ensure that deployment of the application to all four MegaCenters shall be accomplished with the 12 month Base Year of the contract.

2) Operations consoles are located in the MegaCenters in Denver, Colorado; Battle Creek, Michigan; Suitland, Maryland; and Philadelphia, Pennsylvania. Three functions are performed on the operations consoles: Alarm Monitor, Call Taker, and Dispatcher. Each console has a minimum of 3 LCD Display monitors. All Alarm Monitors, Call Takers, Dispatchers and system administrator personnel shall be trained prior to operational implementation of the system in the MegaCenters.

3) CADIS client workstations used by administrative personnel for records management and reporting, as well as some monitoring functions are either desktop or laptop computers and are located nationwide. FPS is organized into eleven regions plus the Headquarters office in Washington, DC and the Federal Law Enforcement Training Center (FLETC) at Glynco, GA. Deployment to these workstations will be performed by the Government. The contractor shall ensure that deployment to these workstations is accomplished within the 12 month Base Year of the contract.

4) Law Enforcement Officers (LEO) use the Panasonic CF-19 Mobile Computing Devices (MCD). LEOs are located throughout the United States and its territories. Usage of MCDs by LEOs will be phased in after deployment at the MegaCenters. The CADIS system shall be completely installed, tested, implemented, and operational for three months in the four FPS MegaCenters, prior to deploying to the MCD users. If possible, the Government wants to complete the implementation on the MCDs within the 12 month Base Year of the contract.

All workstations, including MCDs are Government Furnished Equipment (GFE). MCD specifications for are provided along with the solicitation. All LEO users of CADIS shall be trained prior to deployment of the system to the MCDs.

5.4.3 Application Deployment Responsibilities

Application software deployments to servers and clients shall be performed by the Government. The Government will manually install the server and client software at the MegaCenters. The Contractor shall provide Version Description Documents (VDD) for each CADIS release that specify all information required to install the system.

The Government shall use Big Fix to deploy application software to all clients outside the MegaCenters, including workstations in offices and MCDs used by LEOs. The Contractor shall create the VDDs and Microsoft Software Installation (MSI) packages used by Big Fix for these deployments. Follow up with individual users for completion of installation will be accomplished by FPS personnel.

5.5 DATA MIGRATION and transition

The Government is contemplating whether or not to migrate the data in the existing DOL and WebRMS systems to CADIS. In order to make the decision, the Government requests that the Contractor provide in their proposal their approach to performing a requirement definition and feasibility cost/benefit analysis for this effort and price just that part of the data migration effort.

Based on the outcome and recommendations in analysis, the Government may determine that it is not in its best interest to migrate historical data. If the Government decides to execute the data migration, that will be funded separately from the analysis.

There are approximately 800,000 records in the current legacy DOL and a total of 33,000 records from WebRMS systems that are candidates for migration to CADIS. File formats for DOL and WebRMS will be provided during the post-award requirements definition phase of the project.

If the Government decides to migrate the data, the Contractor shall 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.

5.6 Operations and Maintenance

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

· 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.10. 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.

· Assist FPS in maintaining the Standard Operating Procedures (SOPs) for the CADIS system 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.

· Monitor and compile data statistics for batch and interface production processing; identification of corrupt files or processes; and system archiving and data archiving when applicable.

· Provide on-call support 24 x 7 x 365 from the Contractor’s facility for tier 2 and tier 3 problems reported to the DHS/ICE Service Desk. The Contractor shall resolve all problems associated with the CADIS application on servers and workstations. This is normally feasible by fixing problems with the software at the Contractor’s facility and having the changes installed in production by the Government. All hardware maintenance is performed by the FPS ITFO or the hardware vendor.

· 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.6.1 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. The Contractor shall produce the Version Description Documents required by AHS to install software in the test and production environments. The Contractor shall deliver all software to the Government for installation.

The Contractor shall also:

· 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. label all software releases, regardless of content;

· And, submit an electronic version of all document deliverables to the Electronic Library Management System (ELMS) library.

5.6.2 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.

It is anticipated that a given number of personnel, to be determined by the Contractor, 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 couple per month at most and would generally be limited to changes to the interfaces after they have been developed and implemented. The Government does not anticipate making software program changes to the COTS program modules to create functionality that does not already exist in the COTS product. The Government understands that all such changes would normally be processed through the COTS Vendor’s User Group. SCRs should not be required to change COTS configurations. All configuration changes should be capable of being performed by the FPS System Administrator or a Contractor.

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.7 TRAINING

The Contractor shall develop a training plan leveraging existing COTS based system training material for all user types. 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 at FLETC 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 training 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.

· Alarm Monitors, Call Takers, Dispatchers 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) Training must be accessible to all applicable FPS users – both Government and Contractors - and FLETC.

5.8 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:

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

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

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

· System Security Plan (SSP)

· Security Test and Evaluation (ST&E)

· Security Assessment Report (SAR)

· Vulnerability Scanning Assessment

· Other Security Related Documents

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

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

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.

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

5.9 Risk management

The Contractor shall provide guidance, recommendations, manage and execute activities in support of Risk Management:

· Perform risk assessments and management activities as part of the SSP and SAR process;

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

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

· Perform 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. 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 in the MegaCenters.

INTERFACE A: National Crime Information Center System (NCIC) – price separately 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 B: National Law Enforcement TELECOMMUNICATIONS SYSTEM (NLETS) – price separately 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 C: Security information system (SIS)

– price separately 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.

INTERFACE D: Risk Assessment Management Program (RAMP)

- Price separately

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 CADIS. The final deliverable product will be the successful integration of CADIS and RAMP 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 E: State Crime Information SYSTEMS Optional – to be negotiated, do not price Some states do not provide data to NLETS. The interface to NLETS will give CADIS data that is provided by the states to NLETS. However, FPS would like to be able to access State Crime Information Systems to get state data that is not provided to NLETS. If the contractor has a technical solution that would enable CADIS to interface to the state databases and get the state data that is missing from NLETS, the Government would like to know about it. Please provide any information you have on the capabilities of your COTS product to satisfy this need.

INTERFACE F: DHS/ICE geospatial database Optional – to be negotiated, do not price CADIS shall have the capability to interface to an ESRI database to obtain floor plan and alarm data for approximately 10,000 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 1 or later of the CADIS implementation.

CADIS GIS component shall integrate, and interface with the DHS / ICE existing geospatial database 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 G: 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.