Computer Aided Dispatch Information System FINAL RFP

AMENDED TO ISSUE NOTICE:

1) The proposal due date is extended to April 29, 2010.

2) The solicitation Sections B through M are replaced with this amendment.

3) The Functional Requirements Document is replaced with this amendment.

4) An amended solicitation is posted April 8, 2010.

5) An amended Functional Requirements Document is posted April 8, 2010.


Previous amendment language removed.


The Department of Homeland Security (DHS), Immigration and Customs Enforcement (ICE), Federal Protective Service (FPS) is responsible for providing security and law enforcement services for federal facilities.
The ICE Office of Acquisition (OAQ) plans to offer a requirement for a Computer Aided Dispatch Information System (CADIS) in support of the FPS Law Enforcement Mission.

Previous text removed.

This is a full and open competition with proposals due APRIL 29, 2010.

AMENDED TO ISSUE NOTICE:

1) The proposal due date will be extended to April 29, 2010.

2) Significant areas of change in the solicitation may be but are not limited to: 5 nines requirement, backup/failover of the centers, alarm data transfer, small business and evaluation criteria.

3) An amended solicitation will be posted in the next few days.


Previous amendment language removed.


The Department of Homeland Security (DHS), Immigration and Customs Enforcement (ICE), Federal Protective Service (FPS) is responsible for providing security and law enforcement services for federal facilities.
The ICE Office of Acquisition (OAQ) plans to offer a requirement for a Computer Aided Dispatch Information System (CADIS) in support of the FPS Law Enforcement Mission.
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 (CAD) System for personnel dispatching in response to incidents.
2) Record Management System (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) Geographic Information System (GIS) to provide location information to assess dangerous sites, improving routing, vehicle tracking and to display other relevant neighborhood information.

Furthermore, the proposed CADIS must replace the current Daily Operations Log (DOL) and Web Records Management System (WebRMS).
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. CADIS 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.
Specifically, the system shall:
• Be fully National Incident Based Reporting System (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.
• Interface with external applications and data sources.
• Have the ability to push the client application via the DHS network to desktops and Mobile Computing Devices (MCD) via the internal network.
• 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.
• 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.

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.

This is a full and open competition with proposals due APRIL 29, 2010.

AMENDED TO ISSUE NOTICE:

1) The proposal due date will be extended to April 29, 2010.

2) Significant areas of change in the solicitation may be but are not limited to: 5 nines requirement, backup/failover of the centers, alarm data transfer, small business and evaluation criteria.

3) An amended solicitation will be posted in the next few days.


AMENDED TO ISSUE AN AMENDED RFP, POST QUESTIONS AND ANSWERS, POST Pre-Proposal Conference Slides and Attendance List.

The proposal due date has not been extended.

AMENDED TO ISSUE THE FINAL RFP.

AMENDED TO INCLUDE NOTICE THAT THERE IS A PREPROPOSAL CONFERENCE FOR THIS EFFORT ON MARCH 16, 2010 as noted in Section L.

The Department of Homeland Security (DHS), Immigration and Customs Enforcement (ICE), Federal Protective Service (FPS) is responsible for providing security and law enforcement services for federal facilities.
The ICE Office of Acquisition (OAQ) plans to offer a requirement for a Computer Aided Dispatch Information System (CADIS) in support of the FPS Law Enforcement Mission.
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 (CAD) System for personnel dispatching in response to incidents.
2) Record Management System (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) Geographic Information System (GIS) to provide location information to assess dangerous sites, improving routing, vehicle tracking and to display other relevant neighborhood information.

Furthermore, the proposed CADIS must replace the current Daily Operations Log (DOL) and Web Records Management System (WebRMS).
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. CADIS 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.
Specifically, the system shall:
• Be fully National Incident Based Reporting System (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.
• Interface with external applications and data sources.
• Have the ability to push the client application via the DHS network to desktops and Mobile Computing Devices (MCD) via the internal network.
• 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.
• 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.

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.

This is a full and open competition with proposals due APRIL 8, 2010.

AMENDED TO ISSUE AN AMENDED RFP, POST QUESTIONS AND ANSWERS, POST Pre-Proposal Conference Slides and Attendance List.

The proposal due date has not been extended.

AMENDED TO ISSUE THE FINAL RFP.

AMENDED TO INCLUDE NOTICE THAT THERE IS A PREPROPOSAL CONFERENCE FOR THIS EFFORT ON MARCH 16, 2010 as noted in Section L.

The Department of Homeland Security (DHS), Immigration and Customs Enforcement (ICE), Federal Protective Service (FPS) is responsible for providing security and law enforcement services for federal facilities.
The ICE Office of Acquisition (OAQ) plans to offer a requirement for a Computer Aided Dispatch Information System (CADIS) in support of the FPS Law Enforcement Mission.
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 (CAD) System for personnel dispatching in response to incidents.
2) Record Management System (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) Geographic Information System (GIS) to provide location information to assess dangerous sites, improving routing, vehicle tracking and to display other relevant neighborhood information.

Furthermore, the proposed CADIS must replace the current Daily Operations Log (DOL) and Web Records Management System (WebRMS).
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. CADIS 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.
Specifically, the system shall:
• Be fully National Incident Based Reporting System (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.
• Interface with external applications and data sources.
• Have the ability to push the client application via the DHS network to desktops and Mobile Computing Devices (MCD) via the internal network.
• 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.
• 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.

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.

This is a full and open competition with proposals due APRIL 8, 2010.

ADDED SECTION A, SF33.

AMENDED TO ISSUE THE FINAL RFP.

AMENDED TO INCLUDE NOTICE THAT THERE IS A PREPROPOSAL CONFERENCE FOR THIS EFFORT ON MARCH 16, 2010 as noted in Section L.

The Department of Homeland Security (DHS), Immigration and Customs Enforcement (ICE), Federal Protective Service (FPS) is responsible for providing security and law enforcement services for federal facilities.
The ICE Office of Acquisition (OAQ) plans to offer a requirement for a Computer Aided Dispatch Information System (CADIS) in support of the FPS Law Enforcement Mission.
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 (CAD) System for personnel dispatching in response to incidents.
2) Record Management System (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) Geographic Information System (GIS) to provide location information to assess dangerous sites, improving routing, vehicle tracking and to display other relevant neighborhood information.

Furthermore, the proposed CADIS must replace the current Daily Operations Log (DOL) and Web Records Management System (WebRMS).
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. CADIS 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.
Specifically, the system shall:
• Be fully National Incident Based Reporting System (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.
• Interface with external applications and data sources.
• Have the ability to push the client application via the DHS network to desktops and Mobile Computing Devices (MCD) via the internal network.
• 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.
• 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.

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.

This is a full and open competition with proposals due APRIL 8, 2010.

AMENDED TO UPDATE EXPECTED RFP ISSUANCE DATE AS MARCH 5, 2010.

AMENDED TO INCLUDE NOTICE THAT THERE WILL BE A PREPROPOSAL CONFERENCE FOR THIS EFFORT. ANTICIPATED DATE IS MARCH 18, 2010 AND LOCATION TBD.

The Department of Homeland Security (DHS), Immigration and Customs Enforcement (ICE), Federal Protective Service (FPS) is responsible for providing security and law enforcement services for federal facilities.
The ICE Office of Acquisition (OAQ) plans to offer a requirement for a Computer Aided Dispatch Information System (CADIS) in support of the FPS Law Enforcement Mission.
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 (CAD) System for personnel dispatching in response to incidents.
2) Record Management System (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) Geographic Information System (GIS) to provide location information to assess dangerous sites, improving routing, vehicle tracking and to display other relevant neighborhood information.

Furthermore, the proposed CADIS must replace the current Daily Operations Log (DOL) and Web Records Management System (WebRMS).
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. CADIS 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.
Specifically, the system shall:
• Be fully National Incident Based Reporting System (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.
• Interface with external applications and data sources.
• Have the ability to push the client application via the DHS network to desktops and Mobile Computing Devices (MCD) via the internal network.
• 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.
• 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.

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.

A full and open competition is anticipated with a request for proposals expected to be issued APPROXIMATELY EARLY MARCH, 2010 with proposals due approximately 30 days later.

AMENDED TO UPDATE EXPECTED RFP ISSUANCE DATE AS APPROXIMATELY MID TO LATE FEBRUARY, 2010.

AMENDED TO INCLUDE NOTICE THAT THERE WILL BE A PREPROPOSAL CONFERENCE FOR THIS EFFORT. DATE AND LOCATION TBD.

The Department of Homeland Security (DHS), Immigration and Customs Enforcement (ICE), Federal Protective Service (FPS) is responsible for providing security and law enforcement services for federal facilities.
The ICE Office of Acquisition (OAQ) plans to offer a requirement for a Computer Aided Dispatch Information System (CADIS) in support of the FPS Law Enforcement Mission.
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 (CAD) System for personnel dispatching in response to incidents.
2) Record Management System (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) Geographic Information System (GIS) to provide location information to assess dangerous sites, improving routing, vehicle tracking and to display other relevant neighborhood information.

Furthermore, the proposed CADIS must replace the current Daily Operations Log (DOL) and Web Records Management System (WebRMS).
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. CADIS 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.
Specifically, the system shall:
• Be fully National Incident Based Reporting System (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.
• Interface with external applications and data sources.
• Have the ability to push the client application via the DHS network to desktops and Mobile Computing Devices (MCD) via the internal network.
• 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.
• 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.

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.

A full and open competition is anticipated with a request for proposals expected to be issued APPROXIMATELY MID TO LATE FEBRUARY, 2010 with proposals due approximately 30 days later.

AMENDED TO UPDATE EXPECTED RFP ISSUANCE DATE TO ON OR ABOUT JANUARY 25, 2010.

RELEASE A DRAFT SOLICITATION FOR INDUSTRY COMMENTS AND QUESTIONS, PROVIDE TO TRAVIS.GRAHAM@DHS.GOV ON OR BEFORE JANUARY 14, 2010 BY 12PM EASTERN TIME.


The Department of Homeland Security (DHS), Immigration and Customs Enforcement (ICE), Federal Protective Service (FPS) is responsible for providing security and law enforcement services for federal facilities.
The ICE Office of Acquisition (OAQ) plans to offer a requirement for a Computer Aided Dispatch Information System (CADIS) in support of the FPS Law Enforcement Mission.
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 (CAD) System for personnel dispatching in response to incidents.
2) Record Management System (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) Geographic Information System (GIS) to provide location information to assess dangerous sites, improving routing, vehicle tracking and to display other relevant neighborhood information.

Furthermore, the proposed CADIS must replace the current Daily Operations Log (DOL) and Web Records Management System (WebRMS).
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. CADIS 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.
Specifically, the system shall:
• Be fully National Incident Based Reporting System (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.
• Interface with external applications and data sources.
• Have the ability to push the client application via the DHS network to desktops and Mobile Computing Devices (MCD) via the internal network.
• 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.
• 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.

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.

A full and open competition is anticipated with a request for proposals expected to be issued on or about January 6, 2010 with proposals due approximately 30 days later.

AMENDED TO UPDATE EXPECTED RFP ISSUANCE DATE TO ON OR ABOUT JANUARY 6, 2010.


The Department of Homeland Security (DHS), Immigration and Customs Enforcement (ICE), Federal Protective Service (FPS) is responsible for providing security and law enforcement services for federal facilities.
The ICE Office of Acquisition (OAQ) plans to offer a requirement for a Computer Aided Dispatch Information System (CADIS) in support of the FPS Law Enforcement Mission.
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 (CAD) System for personnel dispatching in response to incidents.
2) Record Management System (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) Geographic Information System (GIS) to provide location information to assess dangerous sites, improving routing, vehicle tracking and to display other relevant neighborhood information.

Furthermore, the proposed CADIS must replace the current Daily Operations Log (DOL) and Web Records Management System (WebRMS).
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. CADIS 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.
Specifically, the system shall:
• Be fully National Incident Based Reporting System (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.
• Interface with external applications and data sources.
• Have the ability to push the client application via the DHS network to desktops and Mobile Computing Devices (MCD) via the internal network.
• 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.
• 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.

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.

A full and open competition is anticipated with a request for proposals expected to be issued on or about January 6, 2010 with proposals due approximately 30 days later.

The Department of Homeland Security (DHS), Immigration and Customs Enforcement (ICE), Federal Protective Service (FPS) is responsible for providing security and law enforcement services for federal facilities.
The ICE Office of Acquisition (OAQ) plans to offer a requirement for a Computer Aided Dispatch Information System (CADIS) in support of the FPS Law Enforcement Mission.
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 (CAD) System for personnel dispatching in response to incidents.
2) Record Management System (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) Geographic Information System (GIS) to provide location information to assess dangerous sites, improving routing, vehicle tracking and to display other relevant neighborhood information.

Furthermore, the proposed CADIS must replace the current Daily Operations Log (DOL) and Web Records Management System (WebRMS).
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. CADIS 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.
Specifically, the system shall:
• Be fully National Incident Based Reporting System (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.
• Interface with external applications and data sources.
• Have the ability to push the client application via the DHS network to desktops and Mobile Computing Devices (MCD) via the internal network.
• 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.
• 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.

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.

A full and open competition is anticipated with a request for proposals expected to be issued on or about December 25th with proposals due approximately 30 days later.