70RSAT25RFI000037 CAD-to-CAD-SOO.pdf

DEPARTMENT OF HOMELAND SECURITY (DHS)

STATEMENT OF OBJECTIVES (SOO) FOR CAD-TO-CAD INTEROPERABILITY

COMPLIANCE AND CONFORMANCE TESTING PROJECT

PURPOSE. The purpose of this document is to define the objectives of the design, development, test, and implementation of a computer aided dispatch (CAD)-to-CAD Interoperability Compliance / Conformance testing approach.

SCOPE.

The scope of this effort is detailed further in the performance objectives section of this document. However, the scope for the CAD-to-CAD Interoperability Compliance and Conformance Testing Project is to:

1) Propose and implement a CAD-to-CAD interoperability compliance and conformance testing methodology that can be scaled nation-wide, including, but not limited to, defining and evaluating standards-based interoperability, developing testing use cases and solutions, and conducting pilots to validate these capabilities.

2) Collaborate with CAD Stakeholders and foster industry understanding and support throughout the project. Stakeholders include, but are not limited to, Emergency Communication Centers (ECCs) and Public Safety Answering Points (PSAPs) at the state, local, tribal, and territorial levels, DHS, the Department of Transportation, the vendor community, representative associations, and organizations (including first responder groups), and the critical presence of public safety representatives from across the country.

3) Define appropriate technical means for conducting interoperability testing.

4) Continue contributing to the development of CAD standards and capabilities through collaboration with governing organizations to ensure the standards and capabilities address current and future needs of the stakeholders. Recommend a comprehensive, sustainable, market-based business model to implement and govern interoperability testing that ensures long-term financial viability and does not rely on perpetual government funding or subsidy.

PERIOD OF PERFORMANCE. The period of performance for this statement of objectives is XX months, beginning XX/XX/2025 and ending XX/XX/202X.

PLACE OF PERFORMANCE. Work under this project shall be performed within the contiguous United States (CONUS) unless the prior written approval of the Contracting Officer is sought and obtained by the performer.

GOVERNMENT FURNISHED PROPERTY. No government furnished property will be provided for this project unless expressly stated in the contract. In such instances, DHS will maintain property records. It is expected that the selected performer will have the necessary equipment to adequately meet the requirements of this proposed solution.

Before purchasing any individual item equal to or exceeding $3,000 that is required to support technical tasks performed pursuant to this effort, the performer shall obtain the Department of Homeland Security’s (DHS) Science and Technology (S&T) Contracting Officer’s prior written consent. If the DHS S&T Contracting Officer consents to such purchase, such item shall become the property of DHS. The performer will maintain any such items according to currently existing property accountability procedures. The DHS S&T Contracting Officer will determine the final disposition of any such items in writing.

BACKGROUND.

Computer-aided dispatch (CAD) systems are an integral part of emergency response. Public safety personnel rely on CAD systems to track incidents, dispatch personnel based on location information, and send relevant information to these dispatched personnel, among other things.

CAD-to-CAD interoperability is vital to successfully respond to incidents that require a unified response from multiple jurisdictions or public safety (Fire/Law Enforcement/EMS) disciplines.

Without interoperable systems, personnel are incapable of efficiently sharing information and leveraging the CAD system’s full capabilities, costing incident responders precious time.

Most CAD technology in use today by first responders was not developed to be interoperable with other systems and no communication or data exchange standards are currently in widespread use.

Given this premise, existing CAD systems were designed to meet jurisdictional needs, therefore each is unique as they’re tailored to address needs at the local level. As these systems are migrated or upgraded to conform with the emergence of 5G, there is no single approach or methodology for implementation of CAD systems and thus each implementation may not be fully interoperable or compatible, therefore creating challenges with sharing information across these critical systems.

As a result, situational awareness may suffer, operational inefficiencies may be introduced that negatively impact the optimum response to an incident. In addition, improvised interoperability maybe achieved by developing custom interfaces that can be very costly to develop and maintain.

DHS S&T sponsored research has resulted in the development of a CAD-to-CAD Interoperability Functional Specification, Technology Solution Description, and other artifacts that can be potentially leveraged to develop a CAD-to-CAD interoperability testing approach that will encourage and ensure better reliability and consistency across the ecosystem. The ecosystem envisions achieving both a Next Generation 911 (NG-911) conformance / compliance program and ECC / PSAP ecosystem by piloting into a CAD-to-CAD Compliance / Conformance adapted from Project 25 Compliance Assessment Program (P25 CAP) and sub-component of Next Generation 911 efforts.

The ultimate objective is to address the lack of data communications interoperability between different first responder’s disciplines and systems. This is envisioned through a supportive stakeholder community and creation of an agreed upon standards-based approach to creating a comprehensive testing program that will be implemented through one or more entities in combination with a management oversight entity to ensure program implementation. The existence and use of the testing program will drive progressive industry behavior toward actions that reduce unacceptable risk to public safety by significantly increasing the availability of demonstrably interoperable systems. Alternatively, the objective is NOT to identify, select and drive compliance to only a single industry standard.

PERFORMANCE OBJECTIVES.

The CAD-to-CAD Interoperability Compliance and Conformance testing solution must:

TEST METHODOLOGY (WHAT/WHERE/WHEN/HOW ARE WE TESTING & WHO IS

TESTING)

1. Propose and implement a CAD-to-CAD interoperability compliance and conformance testing methodology that can be scaled nation-wide.

1.1. The testing methodology shall accommodate both monitored and self-administered tests.

1.2. The testing methodology shall be malleable to allow for innovation and adapt to accommodate evolving requirements and standards.

1.3. Interoperability must be tested and validated through both conformance testing and end-to-end testing.

1.4. The program must address access to, interpretation of, and availability of test results.

1.5. Analyze existing testing efforts elsewhere in the industry to understand lessons learned and identify best practices as well as evaluate the likelihood of competition from existing testing solutions or internal testing by vendors.

1.6. Determine if and how the approach can be adopted, scaled, and deployed by the industry participants such as CAD developer, CAD vendors, and potential CAD users.

1.7. Document requirements and use cases to be tested.

1.8. Research and analyze test development models that could support interoperability testing in the CAD industry.

1.9. Analyze technical issues for interoperability testing.

1.10. Conduct pilot testing to validate approach.

1.11. Incorporate cybersecurity considerations into the testing methodology to address potential vulnerabilities in interoperable systems.

1.12. Ensure the independence and impartiality of the testing program.

1.13. Be scalable to accommodate new technologies and evolving requirements in the future

(e.g., integration w/NG911) evolving nature of CAD technologies and standards?

Building in mechanisms for updates and revisions.

1.14. Prioritize automation in the testing process to reduce costs and turnaround time while building in mechanisms for updates and revisions based on the evolving nature of CAD technologies and standards.

1.14.1. Exploring automated test generation and execution opportunities.

1.15. Determine the most effective scope (balancing comprehensiveness with practicality) for the test methodology in terms of tested functionalities and types of CAD systems.

1.16. Determine the feasibility of establishing a centralized testing facility or repository for

CAD interoperability data.

1.17. Address potential compatibility issues between different CAD systems during testing.

Standardized testing protocols and compatibility layers may be needed.

1.18. Assessing the competitive landscape and identifying unique selling points.

1.19. Be standards-based by complying to recognized and widely adopted standards and protocols, such as 3rd Generation Partnership Project (3GPP), Next Generation 911 (NG911), National Emergency Number Association (NENA) i3, National Information Exchange Model (NIEM), IEEE, etc.

1.20. User-driven, considering the needs, preferences, and feedback of the end-users, and involves them in the design, development, testing, and evaluation of the CAD testing project.

1.21. Modular, flexible, and scalable, such that it can be adapted to accommodate future technologies, innovations, and requirements.

STAKEHOLDER COLLABORATION AND INPUT

2. Collaborate with CAD Stakeholders and foster industry understanding and support throughout the project. Stakeholders include Emergency Communication Centers (ECCs) and Public Safety Answering Points (PSAPs) at the state, local, tribal, and territorial levels, DHS, the Department of Transportation, the vendor community, representative associations and organizations (including first responder groups), and the critical presence of public safety representatives from across the country.

2.1. Provide stakeholders early and continuous visibility, input and access to testing methodologies

2.2. Seek stakeholder feedback on requirements for interoperability to better foster wide-spread stakeholder adoption of the testing program.

2.3. Engage stakeholder representatives from the first responder community and industry and foster industry understanding and support around a testing program approach.

2.4. Solicitation of input and feedback from active stakeholders must continue throughout the testing design, implementation and assessment processes going forward.

2.5. Define the potential roles of CAD stakeholders and testers.

2.6. Employ strategies to encourage widespread adoption of the testing program among stakeholders.

2.7. Engage with potential partners, such as industry associations and technology providers, to support the program.

2.8. Ensure participation from all relevant stakeholders, including CAD vendors, first responders, public safety agencies, and government organizations.

2.9. Establish a feedback mechanism that will be used to gather input from stakeholders throughout the development and implementation of the testing program:

2.10. Promote awareness and adoption of the testing program within the CAD community.

TESTING MEANS AND EQUIPMENT (WHAT IS NEEDED TO TEST)

3. Define appropriate technical means for conducting interoperability testing:

3.1. Determine the technical infrastructure and resources required to run the testing program efficiently. This includes considerations for hardware, software, data storage, and security.

3.2. Document the architecture and various components.

3.3. Manufacturer agnostic whenever possible when recommending equipment.

SUSTAINABLE BUSINESS MODEL

4. Recommend a comprehensive, sustainable, market-based business model to implement and govern interoperability testing that ensures long-term financial viability and does not rely on perpetual government funding or subsidy.

4.1. OPERATIONS

4.1.1. Analyze and recommend the most viable financial model to sustain the CAD-to- CAD testing program (models may include membership fees, pay-per-test, or public-private partnerships.

4.1.2. Consider market dynamics and stakeholder preferences.

4.1.3. Demonstrate how CAD-to-CAD testing can be operationalized as a commercial service.

4.1.4. Analyze potential business models for sustainability.

4.1.5. Suggest how cost of testing will be distributed among stakeholders.

4.1.5.1. How would you structure the pricing model for vendors and public safety agencies participating in the program?

4.1.6. Explore how the program will address the evolving nature of CAD technologies and standards.

4.1.7. Cost-effective and sustainable, such that it can leverage existing commercial off the shelf (COTS) solutions, infrastructure, and resources, that will minimize duplication and redundancy, and maximize return on investment, and ensures long-term maintenance and support.

4.2. GOVERNANCE

4.2.1. Define a visible and effective governance structure.

4.2.2. Ensure a balanced and effective governance structure for the program, including stakeholder representation and decision-making processes.

4.2.3. Establish a transparent governance structure with diverse stakeholder representation.

4.2.4. Ensure a balanced and effective governance structure for the program, including stakeholder representation and decision-making processes.

4.2.5. Demonstrate potential blueprint for a governance structure including hypothetical representatives from all stakeholder roles and how tools or suite of tools would be utilized by users.

5. Administrative

5.1. PROJECT MANAGEMENT

5.1.1. The contractor shall provide Project Management services to ensure that required reporting is submitted and that the contract tasks are successfully completed.

5.2. CYBERSECURITY AND OTHER PROTECTIONS

5.2.1. Ensure data security and privacy throughout the testing process, particularly when handling sensitive public safety information.

5.2.2. Ensure the security and privacy of sensitive data exchanged during testing.

5.2.3. Protect the privacy of individuals and ensure that personal information is only used for authorized purposes.

5.2.4. Robust security protocols and data handling practices.

5.2.5. Implement appropriate security measures to prevent cyberattacks and unauthorized access to sensitive information.

5.2.6. Comply with the current versions of National Institute of Standards and

Technology (NIST) 800-53, NIST 800-55, NIST 800-171, NIST Risk Management Framework, DHS Policy Directive 4300A, and other applicable standards.

5.2.7. Finally, while interoperability is the primary focus of this project, we recognize the necessity to always be cognizant of the existence of cyber threats as an overlay consideration when engaging in the design and execution of standard architecture, design elements and system testing requirement. As attack surfaces are created, identified and exploited, awareness of those risks should always be a primary consideration. Even though specifically addressing cybersecurity is not an identified part of the deliverables of this project, its existence is topical and always relevant.

Provide information and make recommendation about integrating this effort into existing interoperability testing program(s), including steps to take to ensure substantive project integration.

OPERATING CONSTRAINTS.

Testing Methodology must:

• Test Interoperability of CAD systems.

• Accommodate both monitored and self-administered tests.

• Interoperability must be tested and validated through both conformance testing and end-to-end testing.

• Must address access to, interpretation of, and availability of test results.

KEY PERSONNEL.

The performer shall provide qualified personnel to perform all objectives specified in this SOO.

Certain roles of this effort are critical to its success, and therefore, have been designated as key personnel by the Government. The performer shall provide the name and qualifications of proposed key personnel as part of their response to this SOO.

Personnel provided by the respondents will have the skills and technical background necessary to successfully complete the tasks described in this plan. The respondents shall implement and manage the technical approach, organizational resources, management, and quality controls to be employed to meet the cost, performance, and schedule requirements throughout task order execution.

The following personnel are designated as key for this effort; however, the Government reserves the right to designate additional personnel roles as key after award.

1. Program Manager

a. Absorb, organize, and communicate large quantities of information in a fast-paced environment in a clear, concise, and accurate manner.

b. Keep informed of the mission, organizational structure, key personnel, current activities, status of current projects, and any issues affecting the organization.

c. Communicate with senior staff, customers, and other staff in a manner that is clear, concise, succinct, and professional.

d. Manage a variety of functions simultaneously and with flexibility to work under competing demands and deadlines.

e. Operate independently and work collaboratively in a team environment.

f. Proficiency in Microsoft Office products including Microsoft Teams and PowerPoint

2. Technical Lead

a. Experience and knowledge of the innerworkings of ECCs and

PSAPs

b. Experience and knowledge of CAD technology

c. Experience and knowledge of applicable standards and systems

i. APCO Project 25 (P25)

ii. Emergency Alert System (EAS)

iii. Integrated Public Alert and Warning System (IPAWS)

iv. Wireless Emergency Alerts (WEA)

v. National Incident Management System (NIMS)

vi. Incident Command System (ICS)

vii. The First Responder Network Authority (FirstNet)

viii. NG911 (Next Generation 911)

ix. National Public Safety Telecommunications Council

(NPSTC)

x. Radio Frequency Spectrum Allocation

Before replacing any individual designated as key by the Government, the performer shall notify the Contracting Officer no less than 14 business days in advance, submit written justification for replacement, and provide the name and qualifications of any proposed substitute(s). All proposed substitutes shall possess qualifications equal to or superior to those of the key person being replaced, unless otherwise approved by the Contracting Officer. The performer shall not replace key personnel without approval from the Contracting Officer.

APPLICABLE DOCUMENTS OR REFERENCES.

1. DHS S&T CAD-to-CAD Interoperability Operations & Technical

Requirements

2. DHS S&T CAD-to-CAD Interoperability Technical Solution

Description

3. DHS S&T CAD-to-CAD Interoperability Pilot Sites Implementation

Report

4. SAFECOM’s Interoperability Continuum1

5. SAFECOM Resources2

6. NCSWIC 2023 Strategic Plan3

7. NIST: Public Safety Use Cases4

8. Trustmark5 6 7 Documentation

9. NENA i3

10. National Information Exchange Model

11. NIST 800-53

12. NIST 800-55

13. NIST 800-171

14. NIST Risk Management Framework

15. DHS Policy Directive 4300A

INTELLECTUAL PROPERTY.

All deliverables for this contract should be treated as the intellectual property of the Department of Homeland Security, unless otherwise informed by the Contracting Officer and/or Contracting Officer Representative.

PROPERTY DISPOSAL.

Before purchasing any individual item equal to or exceeding $5,000 that is required to support technical tasks performed pursuant to this SOO, the performer shall obtain the DHS S&T Contracting Officer’s prior written consent. Property associated or purchased for this contract shall be the property of DHS but be managed and maintained by the performer (where applicable) following DHS property accountability regulations. The DHS S&T Contracting Officer will determine the final disposition of any such items in writing. For the non-accountable property acquired under this contract, material may be disposed of in place with the vendor at the discretion of the DHS S&T Contracting Officer.

1 SAFECOM’s Interoperability Continuum can be found here: https://www.cisa.gov/sites/default/files/2022- 12/21_0615_cisa_safecom_interoperability_continuum_brochure_final.pdf 2 SAFECOM Resources can be found here: https://www.cisa.gov/safecom/resources 3 NCSWIC 2023 Strategic Plan can be found here: https://www.cisa.gov/sites/default/files/2023- 05/23_0406_ncswic_2023_ncswic-strategic-plan_20230324_508C.pdf 4 NIST’s Public Safety Use Cases can be found here: https://pages.nist.gov/PublicSafetyUseCases/introduction.html 5 For more information on Trustmark, please visit https://trustmarkinitiative.org/specifications/trustmark-framework/ 6 More information about Trustmark development and pilots by the Georgia Tech Research Institute (GTRI) can be found at https://trustmark.gtri.gatech.edu/technical-framework/ 7 To access the Trustmark code, please visit https://github.com/Trustmark-Initiative https://www.cisa.gov/safecom/resources https://www.cisa.gov/sites/default/files/2023-05/23_0406_ncswic_2023_ncswic-strategic-plan_20230324_508C.pdf https://www.cisa.gov/sites/default/files/2023-05/23_0406_ncswic_2023_ncswic-strategic-plan_20230324_508C.pdf https://pages.nist.gov/PublicSafetyUseCases/introduction.html https://trustmarkinitiative.org/specifications/trustmark-framework/ https://trustmark.gtri.gatech.edu/technical-framework/ https://github.com/Trustmark-Initiative

Various standards and regulations govern public safety and emergency communications to ensure effective and interoperable communication among different agencies and jurisdictions.

Some of the key (US) standards and systems include:

1. APCO Project 25 (P25) APCO Project 25 is a set of standards for digital radio communication commonly used by public safety and emergency services agencies. P25 ensures interoperability among different radio equipment manufacturers and enables secure and reliable communication.

2. Emergency Alert System (EAS) The Emergency Alert System is a national public warning system that allows the President to address the nation during a national emergency. It also facilitates state and local alerts, such as weather warnings and AMBER Alerts.

3. Integrated Public Alert and Warning System (IPAWS) IPAWS is a FEMA-managed system that integrates various alert and warning systems, including the EAS and Wireless Emergency Alerts (WEA), to deliver emergency messages to the public via various communication channels.

4. Wireless Emergency Alerts (WEA) WEA is a system for sending emergency messages to mobile devices in a specific geographic area. It is used for AMBER Alerts, weather warnings, and Presidential Alerts.

5. National Incident Management System (NIMS) NIMS is a framework for organizing and managing emergency response efforts. It includes standardized procedures, organizational structures, and communication protocols to enhance interoperability among responding agencies.

6. Incident Command System (ICS) ICS is a standardized management system used for the command, control, and coordination of emergency response efforts. It includes a structured approach to communication and incident management.

7. FirstNet The First Responder Network Authority (FirstNet) is an independent authority that oversees the development and operation of a nationwide broadband network dedicated to public safety and emergency services. FirstNet provides a high-speed, secure network for first responders.

8. NG911 (Next Generation 911) NG911 is an initiative to upgrade the existing 911 systems to support multimedia data, text, images, and videos, in addition to voice calls, to improve emergency communication and response.

9. National Public Safety Telecommunications Council (NPSTC) NPSTC provides guidance and recommendations for public safety communications standards and practices, working to ensure that technologies and policies meet the needs of first responders.

10. Radio Frequency Spectrum Allocation The Federal Communications Commission (FCC) allocates and manages radio frequency spectrum for public safety and emergency services, ensuring that different agencies and jurisdictions have access to the necessary spectrum for their communication needs.

STATEMENT OF OBJECTIVES (SOO) FOR CAD-TO-CAD INTEROPERABILITY COMPLIANCE AND CONFORMANCE TESTING PROJECT