Dinuba City Council
August 12, 2025

FY 2024 SAFECOM Guidance on Emergency Communications Grants • CARES Act. Signed into law on March 27, 2020, the CARES Act provided emergency assistance and healthcare response for individuals, families, and businesses affected by the 2020 public health crisis. The Act included over $2.2 trillion in economic relief, split across the public and private sectors. Division B: Emergency Appropriations for Coronavirus Health Response and Agency Operations, provided supplemental funding to federal departments and agencies, as well as additional funding allocated to existing federal grant programs. Grant applicants are encouraged to review the federal financial assistance opportunities available through the Act to support emergency communications investments.
34 • National Emergency Communications Plan (NECP). The NECP establishes a vision to enable the nation’s emergency response community to communicate and share information securely across communications technologies in real time, including all levels of government, jurisdictions, disciplines, organizations, and citizens impacted by any threats or hazards event. Its focus is to ensure the public safety community and citizens are collectively driving toward a common end-state for communications. The NECP provides guidance to those that plan for, coordinate, maintain, invest in, and use communications to support response and recovery operations.35
Grant recipients should read the NECP to understand the national emergency communications strategy, and to ensure proposed investments support the goals, objectives, and recommendations of the Plan. In addition, grant applicants are encouraged to review NECP supplemental materials such as assessments, annual progress reports, and implementation documents. Additionally, grant applicants should work with the SWIC to ensure alignment of the SCIP and other emergency communications plans to the NECP.
• Middle Class Tax Relief and Job Creation Act of 2012. Signed into law on February 22, 2012, the Act established the FirstNet Authority, an independent authority within NTIA, and directed it to ensure the establishment of the NPSBN. The Act reallocated and designated 700 MHz D Block spectrum for public safety use, and instructed the FCC to grant an exclusive license to the FirstNet Authority for the D Block spectrum and adjacent existing public safety broadband spectrum (collectively referred to as Band 14). The FirstNet Authority engaged in comprehensive outreach and consultation with public safety entities in federal, state, local, tribal, and territory jurisdictions to plan for the network. The FirstNet Authority actively sought input from federal, tribal, state, and territorial governments; paid and volunteer first responders and other public safety personnel; industry; and other stakeholders on what the network should offer, how it should function, and how to meet the technical objectives of the network. The FirstNet Authority conducted an open, competitive procurement for an industry partner to deploy the network. The agency selected AT&T as its network contractor and launched network deployment in 2018 after consulting with all states, territories, and Washington, D.C., to develop network plans. The resulting FirstNet network solution is operational in all 56 states, territories, and Washington, D.C., and is based on a single, national network architecture that evolves with technological advances and consists of a physical, separate evolved packet core (EPC) network and radio access networks (RANs).38 37 36
FirstNet competes as a services-based business where eligible users choose to subscribe to a level of service that aligns with their mission needs. The principal responsibilities of federal, state, 34 For more information on the CARES Act, see: congress.gov/bill/116th-congress/house-bill/748. 35 For more information on the NECP, see: cisa.gov/national-emergency-communications-plan. 36 For more information on the Act, see: ntia.doc.gov/category/public-safety. 37 47 U.S.C.§ 1421(a). 38 For more information on the FirstNet Core, see:
about.att.com/story/nationwide_launch_of_firstnet_dedicated_core_network.html. 21

FY 2024 SAFECOM Guidance on Emergency Communications Grants local, tribal, and territorial public safety entities are the acquisition of authorized and compatible devices and applications that operate on the network and determination of connectivity of proprietary databases that could support public safety operations. Infrastructure and maintenance costs of FirstNet-owned EPC, RANs, and NPSBN deployable assets (e.g., COWs, Cell on Light Trucks [COLTs], Satellite COLTs, Flying Cell on Wings, CRDs, mini-CRDs) will be borne by the FirstNet Authority and its NPSBN contractor.

Only after receiving guidance from the FirstNet Authority on the technical requirements of and compatibility with the NPSBN should grant recipients acquire long-term evolution (LTE) devices or network equipment. Additional outreach and planning activities (e.g., community engagement and education, documenting user needs) that support the NPSBN should be done in consultation with the FirstNet Authority.
39 Applicants interested in investing federal funds in broadband-related projects should consult with the FirstNet Authority and the federal granting agency to understand all requirements impacting broadband investments. The FirstNet Authority is the sole nationwide licensee for Band 14 spectrum and does not anticipate entering into any other spectrum agreements. Applicants should work closely with the SWIC, statewide emergency communications leaders, and the federal granting agency to ensure projects remain in compliance with programmatic and technical requirements of the NPSBN.

In addition to the duties of the FirstNet Authority, the Act also charged NTIA with establishing grant programs to assist state, regional, tribal, and local jurisdictions with planning activities to support the implementation of the NPSBN and improve 911 services. These grants are now closed.

Grant applicants should continue to monitor current federal actions affecting broadband and 911 programs funded through the Act.40
• IPAWS Modernization Act of 2015 and subsequent policies. Signed into law in April 2016, Public Law 114-143 calls for the modernization of IPAWS to ensure that under all conditions, the president, federal agencies, and state, local, and tribal governments can alert and warn the civilian population in areas endangered by natural disasters, acts of terrorism, and other man-made disasters or threats to public safety.

The Modernization Act requires IPAWS to be designed to adapt to and incorporate future technologies for communicating directly with the public, provide alerts to the largest portion of the affected population feasible, and improve the ability of remote areas to receive alerts; promote local and regional public and private partnerships to enhance community preparedness and response; provide redundant alert mechanisms; and protect individual privacy.41 Additionally, the Modernization Act established the IPAWS Subcommittee to develop and submit recommendations for the National Advisory Council (NAC). The NAC provided a report to the FEMA Administrator in February 2019. The FEMA Administrator’s Response to the NAC was signed in September 2019, prioritizing recommendations, highlighting current plans, and identifying areas where more resources are required.

Subsequently, the William M. (Mac) Thornberry National Defense Authorization Act for FY 2021 (Public Law 116-283), provided any commercial mobile service licensee electing to transmit emergency alerts may offer subscribers the capability of preventing the subscriber’s device from receiving such alerts, or classes of such alerts, other than an alert issued by the president or the 39 For more information on LTE network equipment, see: nist.gov/ctl/pscr/process-document-nist-list-certified-devices. 40 For more information on the 911 Grant Program, visit: 911.gov/projects/federal-funding. 41 For more information on the IPAWS Modernization Act, see: congress.gov/bill/114th-congress/senate-bill/1180. 22

FY 2024 SAFECOM Guidance on Emergency Communications Grants FEMA Administrator. This change implements new national alerting requirements that supplement requirements in Executive Order 13407—Public Alert and Warning System and the IPAWS Modernization Act.
42 • PPD–8, National Preparedness. Signed by the president in March 2011, this directive is aimed at strengthening the security and resilience of the United States through systematic preparation for the threats that pose the greatest risk to the security of the nation. It consists of four main components: National Preparedness Goal; National Preparedness System; National Preparedness Report; and the Campaign to Build and Sustain Preparedness. The directive emphasizes national preparedness is the shared responsibility of the whole community.43 As a result, many grants that fund emergency communications now require grant applicants to engage the whole community in planning. FY 2022 federal grant programs require applicants to demonstrate how a whole community approach to project planning was used and explain how core capabilities were improved. Applicants are encouraged to engage their community early in project development to ensure they can provide evidence of community involvement in applications, which in turn improves preparedness and response.

Spectrum Issues
The FCC authorizes state, local, and some tribal public safety entities to use specific spectrum bands to operate emergency communications systems. By statute, the FirstNet Authority holds the FCC license for the 700 MHz public safety broadband spectrum to deploy the NPSBN. Grant applicants seeking federal funds for emergency communications projects should be aware of initiatives and actions affecting spectrum use for public safety entities. Applicants should review the following spectrum issues, confirm their proposed projects are consistent with regulatory requirements and initiatives, and consult the appropriate coordinator (e.g., Frequency Coordinator, SWIC), the FCC, and/or the FirstNet Authority early in the project development process to determine whether the grant applicant will have authority to operate in the desired spectrum, once complete. Key spectrum-related issues are described below:
44 • Very High Frequency (VHF)/Ultra-High Frequency (UHF) Narrowbanding. The FCC mandated all non-federal LMR licensees operating between 150 and 512 MHz and using 25 kilohertz (kHz) bandwidth voice channels to migrate to 12.5 kHz bandwidth or equivalent efficiency by January 1, 2013. Grant applicants should confirm existing LMR systems are compliant with these narrowbanding requirements and consult with the SWIC and the FCC on any non-compliance issues to avoid admonishment, monetary fines, or loss of license. Grant applicants that have not complied with the FCC narrowband mandate may face limitations on their eligibility for federal funding. Grant applicants that are operating on 25 kHz bandwidth voice channels pursuant to a waiver should provide a copy of the waiver as well as a description of how the applicant intends to come into compliance upon the expiration of the waiver. 46 45
• 4.9 gigahertz (GHz). The FCC mandated that all incumbent licensees operating in the 4.9 GHz band as of January 18, 2023, submit granular technical data on their existing operations into the 42 For more information on the William M. (Mac) Thornberry National Defense Authorization Act for FY 2021, see:
congress.gov/bill/116th-congress/house-bill/6395. 43 For more information on PPD-8, see: dhs.gov/presidential-policy-directive-8-national-preparedness. 44 For more information on frequency coordinators, see: fcc.gov/general/public-safety-frequency-coordinators. 45 For more information on narrowbanding, see: fcc.gov/narrowbanding-overview. 46 See “Guidance for licensees for FCC’s narrowband operation requirement” at: fcc.gov/document/guidance-licenseesfccs-narrowband-operation-requirement. Grant applicants with questions on narrowbanding may contact the FCC at ULS support: 1-877-480-3201.
23

FY 2024 SAFECOM Guidance on Emergency Communications Grants FCC’s Universal Licensing System (ULS). Licensees are given at least one year from the publication date of the FCC’s order in the Federal Register to submit the data.47 In general, grant applicants should consult with the regulatory agency and appropriate state-level points of contact when developing public safety projects to ensure entities are in compliance with federal spectrum initiatives and regulations, and projects will have authority to operate in the designated spectrum. To assist state, local, tribal, and territorial levels of government, many grants that fund interoperable communications equipment allow grant funds to be used for spectrum-related activities, including: 49 48 • Identification, assessment, coordination, and licensing of new spectrum resources • Development and execution of spectrum migration plans • Assessment of current communications assets, services, and capabilities • Training associated with systems migration to new spectrum allocations • Replacement of non-compliant communications equipment and services • Acquiring/upgrading tower sites and facilities needed to comply with spectrum migration50 • Reprogramming existing equipment to comply with spectrum migration Reduction and Streamlining of Grants
Over the past decade, the fluctuation of grants funding emergency communications (e.g., elimination of dedicated funding streams in favor of consolidated programs, required spending on federal priorities) has increased competition for funding. Understanding that grants are in high demand, emergency communications leaders and agencies are strongly encouraged to work with other jurisdictions and disciplines to coordinate resources and projects, facilitate asset-sharing, and avoid duplication of activities. Additionally, when developing funding proposals, grant applicants are advised to work with state-level planning offices to incorporate emergency communications needs into statewide plans and to ensure communications projects are prioritized by states and territories. Applicants are encouraged to:
• Coordinate projects with the SWIC, neighboring jurisdictions, and multiple agencies • Develop regional, multi-jurisdictional, multi-disciplinary, and cross-border projects to not only promote greater interoperability across agencies, but also to pool grant resources, facilitate assetsharing, and eliminate duplicate purchases51 • Leverage assessment data to develop strong statements of need that can be shared with state leaders responsible for prioritizing projects for funding52 47 For more information on the FCC updates to 4.9 GHz band rules, see: fcc.gov/document/fcc-updates-49-ghzband-rules-seeks-further-comment. 48 Contact the FCC’s Public Safety Homeland Security Bureau at [email protected] and the FirstNet Authority at [email protected]. 49 While federal licensing fees are generally not allowable under most federal grants, public safety entities are often exempt from FCC filing fees. For more information, see: fcc.gov/licensing-databases/fees. 50 Consult the grant officer as some federal grants do not allow construction or ground-disturbing activities. 51 Applicants should work with SWICs and the FCC to ensure projects do not interfere with the 800 MHz rebanding effort occurring along the U.S.-Canada and U.S.-Mexico borders. For more information on the rebanding process, see: fcc.gov/general/800-mhz-spectrum. Federal funding may not be allocated to international entities, unless authorized by law, and placement of federally funded equipment on international property may be subject to special terms and conditions. Recipients should work closely with grant officers on these projects. 52 Applicants are encouraged to use AARs and similar assessments to demonstrate where there are gaps in emergency communications, and to appeal to state-level leaders for funding to address those gaps. 24

FY 2024 SAFECOM Guidance on Emergency Communications Grants • Identify additional sources of funding for emergency communications improvements53

3.4 Understand Federal Grant Requirements and Restrictions Federal Grant Requirements
Emergency communications grants are administered by numerous federal agencies in accordance with various statutory, programmatic, and departmental requirements. Grant applicants are encouraged to carefully review grant guidance to ensure applications meet all grant requirements, including:
• Program goals
• Eligibility requirements
• Application requirements (e.g., due dates, submission dates, matching requirements) • Allowable costs and restrictions on allowable costs
• Accredited technical standards preferred, required, or allowed under each program, if applicable • Reporting requirements
Additionally, recipients should be aware of common requirements for grants funding emergency communications, including: 54
• Environmental Planning and Historic Preservation (EHP) Compliance. Recipients must comply with all applicable EHP laws, regulations, Executive Orders, and agency guidance.

Recipients are strongly encouraged to discuss projects with federal grant program officers to understand EHP restrictions, requirements, and review processes prior to starting the project. • NIMS. Homeland Security Presidential Directive 5 (HSPD-5), Management of Domestic Incidents, requires the adoption of NIMS to strengthen and standardize preparedness response, and to receive preparedness grant funding. State, local, tribal, and territorial recipients should ensure that they meet, or are working to meet, the most recent NIMS implementation and reporting requirements as described in the applicable Notice of Funding Opportunity and NIMS Implementation Objectives published by FEMA.55
• Stakeholder Preparedness Review (SPR) Submittal. The Stakeholder Preparedness Review replaces the State Preparedness Report. Section 652(c) of the Post-Katrina Emergency Management Reform Act of 2006 (Public Law 109-295), 6 U.S.C. §752(c), and requires any state, territory, urban area, or tribe that receives federal preparedness assistance administered by DHS to submit an annual SPR to FEMA. The SPR is a self-assessment of a jurisdiction’s current capability levels against the targets identified in the THIRA. Jurisdictions use the SPR to estimate their current preparedness capabilities and compare those to their THIRA results to identify gaps. They also use the SPR to identify potential approaches for addressing those capability gaps. 53 For additional sources of funding, see the List of Federal Financial Assistance Programs Funding for Emergency Communications or the Funding Mechanisms Guide for Public Safety Communications, posted to the SAFECOM website at: cisa.gov/safecom/funding. 54 While these are common requirements that affect many emergency communications grants, they may not apply to all grants; applicants should consult their grant guidance and grant officer for specific questions on grant requirements. 55 The NIMS Implementation Objectives reflect the concepts and principles contained in NIMS and clarify the NIMS implementation requirements in FEMA preparedness grant Notices of Funding Opportunity. As recipients and subrecipients of federal preparedness (non-disaster) grant awards, jurisdictions and organizations must achieve, or be actively working to achieve, all of the NIMS Implementation Objectives. Additional NIMS implementation guidance can be found at: fema.gov/emergency-managers/nims/implementation-training. 25

FY 2024 SAFECOM Guidance on Emergency Communications Grants • Threat and Hazard Identification and Risk Assessment. Since 2019, DHS/FEMA has required Homeland Security Grant Program (State Homeland Security Program and Urban Area Security Initiative), Tribal Homeland Security Grant Program, and Emergency Management Performance Grant Program recipients to complete a THIRA report every three years (previously, a THIRA was required annually). Grant recipients are also required to submit an SPR annually.

Communities use the THIRA process to better understand their risks and determine the level of capabilities needed to address those risks. Through the THIRA process, communities set goals for building and sustaining their capabilities. It results in whole community-informed capability targets and resource requirements necessary to address anticipated and unanticipated risks.56 Developing and updating an effective THIRA/SPR requires active involvement from the whole community. This can result in more complete, accurate, and actionable assessments and planning efforts. Therefore, recipients should actively engage a wide variety of stakeholders in the THIRA/SPR process. Emergency communications subject matter experts should be involved in the THIRA/SPR process and provide input as appropriate, including but not exclusive to the potential impacts of threats and hazards on emergency communications. For additional information, refer to each grant program’s Notice of Funding Opportunity or the Preparedness Grants Manual for reporting requirements, including the THIRA/SPR. Grant recipients participating in risk assessments are strongly encouraged to:
57 o Analyze communications gaps, excesses, and deficiencies within the state regularly o Utilize THIRA to identify communications-specific threats and hazards and set core capability targets identified in the National Preparedness Goal o Ensure THIRA updates include outcomes as stated in program guidance o Assist with the development of the SPR
• Nationwide Cybersecurity Review. Recipients and subrecipients of State Homeland Security Program and Urban Area Security Initiative awards are required to complete the Nationwide Cybersecurity Review, enabling agencies to benchmark and measure progress of improving their cybersecurity posture. The Chief Information Officer (CIO), Chief Information Security Officer (CISO), or equivalent of each recipient and subrecipient should complete the Nationwide Cybersecurity Review. If there is no CIO, CISO, or equivalent, the most senior cybersecurity professional should complete the assessment.58
• Reporting. Federal agencies are improving how they demonstrate the impact and effectiveness of federal grant programs. As a result, recipients may be required to report project-level information, performance measurement data, detailed financial reports, and progress reports.

Recipients are encouraged to use existing documentation and data (e.g., SCIPs, AARs, assessments) to measure performance and demonstrate how gaps in capabilities will be/were addressed through federal grant funding. Recipients are strongly encouraged to:
o Develop performance measures at the start of the grant o Include interval performance measures and milestones to gauge project progress o Track performance and report the impact of funds on emergency communications o Include metrics on improvements in interval and final grant reports 56 For additional information on the THIRA process, see: fema.gov/emergency-managers/nationalpreparedness/goal/risk-capability-assessment. 57 DHS/FEMA developed a Preparedness Grants Manual to guide grant applicants and recipients on how to manage their grants and other resources, available at: fema.gov/grants/preparedness/manual. 58 The Nationwide Cybersecurity Review is completed on the Multi-State Information Sharing and Analysis Center.

For more information, visit cisecurity.org/ms-isac/services/ncsr or email [email protected]. 26

FY 2024 SAFECOM Guidance on Emergency Communications Grants Recipients should ensure all grant requirements are met and that they can implement the project as proposed and within the grant period of performance; properly manage grant funding; fulfill grant reporting requirements; and comply with federal grant restrictions.

Federal Grant Restrictions
Recipients should be aware of common restrictions on federal grant funding and should consult the grant officer with any questions, particularly as requirements vary by program. • Commingling or Duplication of Funds. Since multiple agencies are involved in communications projects, projects are often funded with multiple grant programs, creating a risk of commingling and duplication. Recipients must ensure federal funds are used for purposes that were proposed and approved and have financial systems in place to properly manage grant funds. Recipients cannot commingle federal sources of funding. In addition, federal funds cannot purchase or pay for the same cost or activity already paid for from another source of funding (e.g., insurance claim). This is referred to as a prohibition on the duplication of benefits or “double-dipping.” The accounting systems of all recipients and sub-recipients must ensure federal funds are not commingled with funds from other awards or federal agencies, nor duplicate benefits. • Cost Sharing/Matching Funds. Recipients must meet all matching requirements prescribed by the grant. If matching funds are required, grant recipients must provide matching funds or in-kind goods and services that must be:
 Allowable under the program and associated with the investment  Applied only to one federal grant program
 Valued at a cost that is verifiable and reasonable
 Contributed from non-federal sources
 Treated as part of the grant budget
 Documented the same way as federal funds in a formal accounting system • Funding and Sustaining Personnel. In general, the use of federal grant funding to pay for staff regular time is considered personnel and may be allowable. Recipients are encouraged to refer to the applicable grant program guidance and develop a plan to sustain critical communications positions in the event federal funds are not available to support the position in future years. • Supplanting. Most grant funds cannot supplant (or replace) funds previously funded or budgeted for the same purpose. Most federal grants funding emergency communications restrict recipients from hiring personnel for the purposes of fulfilling traditional public safety duties or to supplant traditional public safety positions and responsibilities. Review applicable grant program guidance for specific rules on supplanting.
27

FY 2024 SAFECOM Guidance on Emergency Communications Grants

4. Eligible Activities
The following section details eligible emergency communications activities commonly funded by federal grants, including Personnel and the four common cost categories: Planning and Organization, Training, Exercises, and Equipment. Grant applicants seeking to improve interoperable emergency communications are encouraged to allocate grant funding to these activities but must consult the specific grant guidance for allowable costs.
59 The intent of this section is to raise awareness as to the types of costs that can be covered under most federal grants funding emergency communications. However, applicants should note all activities listed in this section may not be eligible for funding under all grant programs. Applicants should read each grant program’s guidance and related information carefully to ensure activities proposed are eligible under the program before developing or submitting applications.

4.1 Personnel
Many federal grants allow recipients to hire full- or part-time staff, contractor staff, or consultants to assist with emergency communications planning, training, and exercise activities. Allocating funding toward personnel helps ensure grants and grant-funded projects are managed, state-level planning meetings are attended, emergency communications needs are represented, and plans are completed.

Personnel can be hired to develop and conduct training and exercises, and to complete AARs. 60 Eligible Personnel Costs
• Personnel to assist with planning. Full- or part-time staff, contractors, or consultants may be hired to support emergency communications planning activities, including:
 Statewide, local, tribal, territorial, or regional interoperability coordinator(s)  Project manager(s)
 Program director(s)
 Emergency communications specialists (e.g., frequency planners, radio technicians, cybersecurity technologists)
• Personnel to assist with training. Full- or part-time staff, contractors, or consultants may be hired to support emergency communications training activities, including personnel who can:
 Assess training needs
 Develop training curriculum
 Train the trainers
 Train emergency responders
 Promote cross-training and continuous training to address changes in the workforce  Ensure personnel are proficient in using existing and new technologies  Develop exercises to test training
 Support training conferences
 Develop and implement a curriculum covering technical issues raised by broadband and other technologies
 Address continuity of operations planning requirements 59 The general cost categories for grants include Planning, Organization, Equipment, Training, and Exercises (POETE). Some grants do not provide a category for Organizational costs but allow organizational costs to be included under the Planning cost category. Applicants should be aware that emergency communications personnel, planning, and organizational costs are often allowable under the Planning cost category for grants. 60 Typically, the use of federal grant funding to pay for staff or contractor regular time is considered personnel. 28

FY 2024 SAFECOM Guidance on Emergency Communications Grants  Serve as subject matter experts (e.g., environmental engineers, grant administrators, financial analysts, accountants, attorneys)
• Personnel to assist with exercises. Full- or part-time staff, contractors, or consultants may be hired to support exercises. This includes personnel who will:
 Assess immediate needs and future requirements
 Plan and conduct in-person or virtual exercises in accordance with NIMS and the Homeland Security Exercise and Evaluation Program (HSEEP)  Implement NECP goals, objectives, and success indicators  Lead After-Action Conferences and prepare AARs
Additional Requirements and Recommendations for Personnel Activities Grant recipients should be aware of common restrictions on federal grant funding for emergency communications personnel.
• Sustaining Grant-Funded Positions. Recipients should ensure funding for critical communications positions is sustained after the grant period of performance has ended and core capabilities are maintained.
• Overtime. Some federal grants permit the use of funds for overtime related to training. These expenses are limited to additional costs that result from personnel working more than 40 hours per week as a direct result of their attendance at approved activities (e.g., emergency communications training and exercises).
• Backfill-related Overtime. Some federal grants allow funds to be used for backfill-related overtime. These expenses are limited to personnel who work overtime to perform duties of other personnel who are temporarily assigned to grant-funded activities (e.g., to attend approved, grantfunded emergency communications training or exercises). These costs are calculated by subtracting the non-overtime compensation, including fringe benefits of the temporarily assigned personnel, from the total costs for backfilling the position. Recipients should ensure grant funds can be used for overtime and consult their grant officer to correctly calculate overtime expenses.

4.2 Planning and Organization
Allocating grant funding for planning helps entities identify and prioritize needs, define capabilities, update preparedness strategies, refine communications plans, identify where resources are needed most, and deliver preparedness programs across multiple jurisdictions, disciplines, and levels of government.

Grant recipients are strongly encouraged to assess needs before planning projects, and to carefully plan projects before purchasing equipment.

Eligible Planning and Organization Costs
• Development or enhancement of interoperable emergency communications plans. Grant funds may be used to develop or enhance interoperable communications plans and align plans to the strategic goals, objectives, and recommendations set forth in the NECP. Examples of emergency communications plans include:
 Plans to implement and measure the NECP
 SCIPs
 TICPs, FEMA RECPs, or other tactical or regional communications plans  Disaster emergency communications plans
29

FY 2024 SAFECOM Guidance on Emergency Communications Grants  Communications system lifecycle planning, including migration planning and use of the Emergency Communications System Lifecycle Planning Guide61  Plans for narrowband conversion and compliance
 Plans for broadband integration with broader communications capabilities  Planning for SCSI projects to share communications and infrastructure resources with partners  Stakeholder statements of need and concept of operations (CONOPS)  As-is and proposed enterprise architectures
 System engineering requirements
 Acquisition planning for the procurement of systems or equipment  Planning for continuity of communications, including backup solutions, if primary systems or equipment fail (e.g., contingency and strategic planning)  Planning for training and exercises
 Identifying physical and cyber security measures for communications networks and systems  Planning activities for the transition of 911 to NG911 (e.g., NG911 Self-Assessment Tool ) 62  Planning for transitions to AES 256-bit encryption and comprehensive encryption key management capabilities for LMR systems
 Planning for cross jurisdictional alerting
 Plans for issuing alerts, warnings, and notifications (e.g., Wireless Emergency Alerts) • Engagement of federal, state, local, tribal, territorial, private, and public sector entities in planning. Many federal grants require engagement of the whole community in planning to adequately assess and address needs and to implement the National Preparedness System. The National Preparedness Goal and the National Preparedness System concepts, as described in PPD– 8, recognize the development and sustainment of core capabilities are not exclusive to any single level of government or organization, but rather require combined efforts of the whole community.63 Coordination and planning benefit from including a variety of traditional and non-traditional entities supporting public safety, such as tribes, medical facilities, alerting authorities, nongovernmental organizations, public works, utilities, forestry services, military, private sector, and the American Red Cross. Including these under-represented organizations or sectors will assist with the development of strategic, operational, and contingency plans. As a result, the following activities are often supported through federal grants funding emergency communications:
 Conducting conferences and workshops to receive input on plans  Meeting expenses related to planning
 Public education and outreach on planning
 Travel and supplies related to planning or coordination meetings  Attending planning or educational meetings on emergency communications • Establishment or enhancement of communications interoperability governing bodies. Strong governance structures and leadership are essential to effective decision-making, coordination, planning, and managing of emergency communications initiatives. Grant funds may be used to establish, update, or enhance statewide, regional (e.g., multi-state, multi-urban area), or local governing bodies. Eligible activities may include:
 Developing MOUs and Memoranda of Agreement (MOA) to facilitate participation in planning and governance activities
61 For guidance on emergency communications system lifecycle planning, see: cisa.gov/safecom/funding. 62 SAFECOM/NCSWIC developed a dynamic NG911 Self-Assessment Tool for use by state, regional, and local emergency communications centers (ECCs)/public safety answering points (PSAPs) personnel. For more information or to download this tool, see: 911.gov/projects/ng911-self-assessment-tool. 63 Core capabilities include Prevention, Protection, Mitigation, Response, and Recovery, and are further defined in the National Preparedness Goal on the FEMA website at: fema.gov/emergency-managers/national-preparedness/goal. 30

FY 2024 SAFECOM Guidance on Emergency Communications Grants  Meeting or workshop expenses associated with receiving input on plans or supporting a funded activity
 Increasing participation in governing bodies through public education and outreach  Travel and supplies for governing body meetings
 Attending planning or educational meetings on emergency communications  Developing SOPs or templates to provide access to and use of resources  Continued broadband planning and coordination efforts  Ensuring coordination between traditional governance programs and other decisionmaking offices, bodies, and individuals that oversee new technology deployments in states, territories, localities, and tribes
• Development of emergency communications assessments and inventories. Grant recipients are encouraged to allocate grant funding to planning activities, such as assessments of:
 Technology capabilities, infrastructure, and equipment (e.g., updating the CASM Tool, creating LMR, LTE, and 5G fleet maps, NG911 Self-Assessment Tool)  SOPs, coordination of interoperability channels, and regional response plans  Training and exercises
 Spectrum regulatory compliance assessments and system coverage analysis  Cost maintenance modeling for equipment and usage
 Implementation and maintenance of identity, credential, and access management (ICAM) capabilities, including phishing resistant MFA solutions • Development or enhancement of interoperable emergency communications protocols. Funds may be used to enhance multi-jurisdictional and multi-disciplinary common planning and operational protocols, including the development or update of:
 SOPs, shared channels and talk groups, and the elimination of coded substitutions (i.e., developing and implementing common language protocols)
 Partnership agreements, MOUs, and cross-state border agreements  Plans to integrate SOPs across disciplines, jurisdictions, levels of government, and with private entities, as appropriate, and into mutual aid agreements  Response plans to specific disaster or emergency scenarios  Field Operations Guides and templates for Field Operations Guides • Planning activities for emerging technologies. Grant funds may be used to plan for the operationalization of NPSBN/FirstNet, other public safety broadband capabilities, and advanced technologies. Activities may include:
 Defining users’ immediate technology needs and future requirements  Updating SCIPs to incorporate high-level goals and initiatives  Developing plans to optimize broadband use in support of public safety operations  Continued collection of broadband usage data, use cases, and needs analyses  Developing agreed-upon standards for the use of common applications to promote enhanced level of situational awareness
 Preliminary planning for implementation, operations, policy, acquisition, and tactical integration of technologies
 Conducting assessments of cyber risks and strategies to mitigate vulnerabilities before the deployment of IP-based networks
31

FY 2024 SAFECOM Guidance on Emergency Communications Grants  Implementing ICAM solutions to address growing data management, interoperability, and cybersecurity challenges, with consideration for federated solutions, such as the Trustmark Framework64
 Collecting and reporting granular 4.9 GHz technical and licensing data per the FCC’s rules  Enhancing LMR encryption interoperability and capabilities through comprehensive transition to P25 AES-256 encryption with effective encryption key management • Use of priority service programs. Grant funds may be used to assist priority service planning and engineering, and to facilitate participation in federal priority service programs, including: 65  Government Emergency Telecommunications Service (GETS)  Wireless Priority Service (WPS)
 Telecommunications Service Priority (TSP)
• Use of alerts, warnings, and notifications. Grant funds may be used to acquire mass notification alert systems that include IPAWS : 66
 Emergency Alert System (EAS)
 Wireless Emergency Alerts (WEA)
 National Oceanic and Atmospheric Administration (NOAA) Non-Weather Emergency Messages via National Weather Service All Hazards Weather Radio  Internet-based services
 Unique and local alerting systems
In addition to distributing AWNs through EAS, WEA, and NOAA Weather Radio, IPAWS supports Internet-based products and services that redistribute alerts via the IPAWS All Hazards Information Feed. Examples include digital signage, wireless device applications, desktop alerting, assistive devices, and siren systems.

Additional Requirements and Recommendations for Planning Activities Additional activities in support of federal planning initiatives include updating and submitting a SPR, THIRA, and SCIP, as well as demonstrating NIMS implementation.67

4.3 Training
Eligible Training Costs
Recipients are encouraged to allocate federal grant funds to support emergency communications and incident response training. Communications-specific training activities should be incorporated into statewide training and exercise plans and be reflected in SCIPs. Recipients should continue to train and improve efficiency on LMR systems as it is necessary to ensure public safety officials can achieve mission critical voice communications. As public safety agencies integrate other communications technologies into operations, the need for training becomes even more critical to ensure response personnel are maximizing all capabilities. Training projects should be consistent with the NECP priorities and address gaps identified through SCIPs, TICPs, AARs, and other assessments. Training reinforces 64 For more information on ICAM and the Trustmark Framework, see: cisa.gov/safecom/icam. 65 For more information on priority services, see: cisa.gov/resources-tools/programs/priority-telecommunicationsservices. 66 For more information on IPAWS, see: fema.gov/emergency-managers/practitioners/integrated-public-alertwarning-system. 67 For more information on the Preparedness Grants Manual, see: fema.gov/grants/preparedness/manual. 32

FY 2024 SAFECOM Guidance on Emergency Communications Grants SOPs and proper equipment use and proficiency by personnel. Grant recipients are strongly encouraged to include training in projects that involve new SOPs or equipment purchases. • Development, delivery, attendance, and evaluation of training.68 Grant funds may be used to plan, attend, and conduct communications-specific training workshops or meetings to include costs related to planning, meeting space, and other logistics costs, facilitation, travel, and training development. Communications-specific training should focus on the following:
 Use of SOPs and other established operational protocols (e.g., common language)  NIMS/ICS training
 Any ICS Communications Unit/Information Technology Service Unit position-specific training (e.g., COML, COMT, ITSL, ITSS, RADO, INTD, AUXCOMM, INCM)  Information for elected officials and decision-makers to understand public safety communications and requirements
 Use of equipment and advanced data capabilities (e.g., voice, video, text)  Disaster preparedness
 Peer-to-peer training
 Regional (e.g., multi-state, multi-urban area) operations  Population or updates of CASM Tool
 Integration of technologies (e.g., NG911, broadband, AWN capabilities, 5G) into public safety operations
 Cybersecurity and physical security education
• Expenses related to training. Many federal grants allow expenses related to training, including:
 Travel
 Public education and outreach on training opportunities  Supplies related to training (e.g., signs, badges, materials)  Software programs and applications to enable remote learning Additional Requirements and Recommendations for Training Activities Recipients should target funding toward certified emergency communications activities, including:
• NIMS Implementation. State, local, tribal, and territorial entities must adopt NIMS as a condition of many federal grants. Given that implementation of NIMS requires certain training courses, recipients may target funding towards NIMS-compliant training. 69 • Completion of Communications Unit Leader/Information Technology Service Unit Leader and other ICS Communications Unit/Information Technology Service Unit Training. CISA, in partnership with FEMA’s National Integration Center, the DHS Science and Technology Directorate, and practitioners from across the country, developed performance and training standards for the All-Hazards COML/ITSL and formulated a curriculum and comprehensive AllHazards COML/ITSL Course. Recipients should target grant funding toward this training to improve on-site communications during emergencies, as well as satisfy NIMS training requirements.
68 DHS training catalogs are available at: dhs.gov/training-technical-assistance. CISA Service Catalog is available at: cisa.gov/resources-tools/services. The federal-sponsored and state-sponsored course catalogs can be found at:
firstrespondertraining.gov/frts/. 69 NIMS is a national framework for response that requires state, local, tribal, and territorial stakeholders to adopt a national ICS, complete certified training, and integrate the framework into state and local protocols. For more information on NIMS training, see: fema.gov/emergency-managers/nims. 33

FY 2024 SAFECOM Guidance on Emergency Communications Grants • Recommended 911 Minimum Training for Telecommunicators. The National 911 Program facilitated a project to establish universally accepted minimum training guidelines to be used for aspiring and current 911 telecommunicators, and to provide the foundation for ongoing professional development. The Recommended Minimum Training Guidelines identify the minimum topics to be included in any telecommunicator training program.

4.4 Exercises
Exercises should be used to demonstrate and validate skills learned in training and to identify gaps in capabilities. To the extent possible, exercises should include participants from multiple jurisdictions, disciplines, and levels of government and include emergency management, emergency medical services, fire services, law enforcement, public safety telecommunicators, interoperability coordinators, key information technology and cybersecurity personnel, public health officials, hospital officials, officials from colleges and universities, and other disciplines and private sector entities, as appropriate. Findings from exercises can be used to update programs to address gaps in emergency communications and emerging technologies, policies, and partners. Recipients are encouraged to increase awareness and availability of emergency communications exercise opportunities across all levels of government.

Eligible Exercise Costs
• Design, development, execution, and evaluation of exercises. Grant funds may be used to design, develop, conduct, and evaluate interoperable emergency communications exercises, including tabletop and functional exercises. Activities should focus on:
 Use of new or established operational protocols, SOPs, and equipment  Regional (e.g., multi-state, multi-jurisdictional) participation  Integration of broadband services, devices, and applications into public safety operations70 • Expenses related to exercises. Many federal grants allow for expenses related to exercises, including:
 Meeting expenses for planning or conducting exercises  Public education and outreach
 Travel and supplies
Additional Requirements and Recommendations for Exercise Activities Recipients should target funding toward federal exercise initiatives, including participation in the communications components of the National Level Exercises and the following:
• Management and execution of exercises in accordance with HSEEP. The HSEEP library provides guidance for exercise design, development, conduct, and evaluation of exercises, as well as sample exercise materials.71
• Implementation of NIMS. HSPD-5 requires all federal departments and agencies to adopt NIMS and use it in their individual incident management programs and activities, including all preparedness grants for state, local, tribal, and territorial recipients. DHS/FEMA recipients should 70 The FirstNet Authority developed the Broadband Exercise Inject Catalog, providing realistic, consistent, and accurate exercise questions and injects to promote integrating wireless broadband capabilities into public safety training opportunities. The catalog is compatible with HSEEP Master Scenario Events List templates, easily searchable, and can be used for both discussion-based and operations-based exercises. Email the FirstNet Authority at [email protected] to receive the latest version of the Broadband Exercise Inject Catalog. 71 HSEEP resources are available at: fema.gov/emergency-managers/national-preparedness/exercises/hseep. 34

FY 2024 SAFECOM Guidance on Emergency Communications Grants review NIMS implementation criteria at: fema.gov/emergency-managers/nims, and ensure all federally funded training and exercise activities align with NIMS standards. • Coordination with state-level partners. Communications-specific exercise activities should be coordinated with the SIGB or SIEC and SWIC to facilitate participation by appropriate entities (e.g., public safety, utilities, private sector, federal agencies) and resources (e.g., deployable assets).

4.5 Equipment
Emergency management and response providers must regularly maintain communications systems and equipment to ensure effective operation, as well as upgrade their systems when appropriate. Grant recipients are strongly encouraged to invest in accredited technical standards-based equipment that supports statewide plans for improving emergency communications and interoperability among systems.

Eligible Expenses72
• Design, construction, implementation, enhancement, replacement, maintenance, and disposition of emergency communications systems and equipment, including:
73  System engineering requirements
 As-is and proposed enterprise architectures
 Interoperability feature, function, and capability verification and validation testing plans  System lifecycle plans
 Migration to approved, open architecture, accredited standards-based technologies (e.g., P25 AES encryption)
 Integration of existing capabilities and advanced technologies (e.g., multi-band/multi-mode capable radio, Internet of Things devices, Artificial Intelligence, Machine Intelligence, and data science solutions)
 Integration of cybersecurity tools and services (e.g., cyber appliance insertion, taps and probes, firewalls, security information and event management, malware protection, twofactor authentication, web application firewalls, hardware and software implementation)  Analysis and monitoring of cybersecurity and physical security risks  Project management costs associated with systems and equipment  Procurement of technical assistance services for management, implementation, and maintenance of communications systems and equipment
 Reimbursement of cellular and satellite user fees when used for backup communications • Use of narrowband equipment. The FCC mandated all non-federal LMR licensees operating between 150 and 174 MHz, 421–470 MHz, and using 25 kHz bandwidth voice channels to migrate to 12.5 kHz bandwidth or equivalent efficiency by January 1, 2013 (except where narrowband waivers have been permitted). Grant recipients operating wideband pursuant to a waiver should prepare existing systems for eventual compliance upon the expiration of the waiver by prioritizing grant funding, where allowable, toward the following:
 Replacing non-compliant equipment
 Acquiring/upgrading additional tower sites to maintain coverage after conversion  Reprogramming existing equipment to operate in compliance with the FCC’s rule 72 While activities listed are generally allowable for traditional LMR investments, these activities may be restricted for broadband-related investments. Applicants are strongly encouraged to consult their federal granting agency before developing broadband proposals for funding to determine if those activities are allowable under the grant. 73 Not all federal grants permit construction-related activities. Consult the grant officer to determine whether construction activities are allowed. For grants that support construction-related activities, see applicable EHP requirements to select construction-related activities in this guidance. 35

FY 2024 SAFECOM Guidance on Emergency Communications Grants • Site upgrades for emergency communications systems.
 Installing or expanding battery backup, generators, solar panels, fuel systems, or grounding systems
 Evaluating existing shelter space for new communications equipment  Conducting tower loading analysis to determine feasibility of supporting new antennas and equipment, as well as tower hardening or replacement to withstand harsh environmental conditions
 Analyzing site power and grounding systems to determine upgrades needed for additional communications equipment
 Analyzing physical site security provisions for upgrades and enhancements (e.g., fences, lighting, alarm systems, surveillance cameras, shelter access hardening, protective measures, monitoring, smart cards, biometrics or keyless entry systems)  Evaluating and upgrading Public Safety Answering Points, Emergency Communications Centers, and other 911 infrastructure sites to determine requirements and deploy hardware and software upgrades
• Upgrading connectivity capabilities for emergency communications systems.  Documenting existing wireline and wireless backhaul resources to determine used and excess capacity (e.g., connectivity type of either fiber, wireless, or cable at communications sites and existing public safety facilities)  Analyzing existing IP backbone to determine gaps in supporting high bandwidth public safety communications systems access, connectivity, and applications  Planning and modeling network capacity to ensure backhaul links and aggregation points are appropriately provisioned
 Upgrading existing backbone to support advanced Quality of Service capabilities  Installing fiber optic connections and microwave connectivity to support enhanced communications, networking capabilities, and redundancy requirements  Ensuring robust cybersecurity protocols and physical security protections are in place  Assessing and documenting usage of wireless communications capabilities including:
− Mobile data systems facilitated through government-owned or commercial services − Applications
− Devices or platforms supported
− Speed/capacity
− Accessible data
− Redundancy and resiliency of systems or services
− Cost of services and systems
− Existing gaps in capabilities, connectivity, coverage, or application support − Standards-based mission critical solutions, including voice, video, and data • Purchase of:
o Standards-based interoperable communications equipment listed on the Authorized Equipment List (AEL)74
o P25 standards-compliant radio equipment listed on the P25 CAP Approved (GrantEligible) Equipment List75 o Broadband user equipment on the NIST List of Certified Devices76 74 For a list of equipment typically allowed by DHS/FEMA grants, see: fema.gov/grants/tools/authorized-equipmentlist. The AEL consists of 21 equipment categories further divided into sub-categories and individual items. 75 For a list of P25 compliant radio equipment, see: dhs.gov/science-and-technology/approved-grant-eligible-equipment. 76 For a list of NIST certified devices, see: nist.gov/ctl/pscr/process-document-nist-list-certified-devices. 36

FY 2024 SAFECOM Guidance on Emergency Communications Grants o Broadband applications, services, and equipment that meet appropriate protocols and standards for access to, use of, or compatibility with the NPSBN/FirstNet77 o Broadband data and voice cache communications capabilities (e.g., in-vehicle routers, Wi-Fi hotspots, private 5G, multi-access edge computing, and other devices) that augment network access and enable operations in areas where network coverage is challenging or there is an increased need for access and throughput  Ancillary equipment to facilitate planning and implementation of interoperable public safety grade communications systems and capabilities (e.g., radio frequency and network test equipment including handheld spectrum analyzers, cable testers)  Software that is IPAWS-compliant to issue alerts, warnings, and notifications to the public  Physical security equipment (e.g., biometric accesses control systems, door locks)  Cybersecurity equipment (e.g., cyber appliances, taps and probes, phishing resistant hardware authenticators)
 Auxiliary communications equipment (e.g., amateur radios, HF, SHARES radios and gateways, satellite devices)
Additional Requirements and Recommendations for Equipment Purchases Recipients should anticipate additional requirements when purchasing equipment with federal grant funds, including:
• Assignment of full-time Statewide Interoperability Coordinator. DHS/FEMA requires all states and territories that use Homeland Security Grant Program funds to designate a full-time SWIC who has the authority and resources to actively improve interoperability with emergency management and response agencies across all levels of government. Responsibilities include establishing and maintaining statewide plans, policies, and procedures, and coordinating decisions on communications investments funded through federal grants. SWIC status information will be maintained by CISA and verified by FEMA through programmatic monitoring activities for DHS/FEMA grant recipients.
• Coordination with statewide emergency communications leaders. Recipients are strongly encouraged to coordinate with the SWIC, other emergency communications governance bodies and leadership, and appropriate state, local, tribal, and territorial partners to ensure consistency with statewide plans, and compatibility among existing and proposed emergency communications systems. • Compliance with technical standards. DHS/FEMA recipients must ensure all grant-funded equipment complies with technical standards in the SAFECOM Guidance Appendix B, unless otherwise noted in a program’s grant guidance. Other federal grants require recipients to explain how their procurements will comply with applicable technical standards for LMR, IP-based systems, and alert and warning systems or provide compelling reasons for using non-standards-based solutions.

Recipients should document all purchases and evidence of compliance with standards-based requirements and verify compliance and interoperability through comprehensive testing. 78 77 For a full list of broadband applications, services, and equipment that meet appropriate protocols and standards for access to, use of, or compatibility with the NPSBN/FirstNet, go to FirstNet.com or contact the FirstNet Authority at [email protected]. 78 Technical standards and requirements vary among federal grant programs (especially grants funding research and testing). Applicants should review grant guidance to ensure specific standards, terms, and conditions are met.

DHS/FEMA grant recipients must adhere to compliance requirements specified in SAFECOM Guidance Appendix D. 37

FY 2024 SAFECOM Guidance on Emergency Communications Grants • Compliance with FCC Requirements. Applicants are encouraged to consult with the FCC during application development to determine whether projects will be able to access the appropriate spectrum for planned operations or if a waiver is needed. Contact the FCC at [email protected]. • Compliance with federal EHP laws and policies. Recipients must ensure federally-funded projects comply with relevant EHP laws. Construction and installation of communications towers and other ground-disturbing activities frequently require EHP review. Each agency (and sometimes each program) has its own EHP compliance process. Recipients should discuss proposed constructionrelated activities with federal granting agencies before beginning work to determine whether proposed activities are allowed, and to determine if proposed activities are subject to EHP review.79 • Adoption of new technologies. Recipients are encouraged to migrate to approved, open architecture, accredited standards-based systems and to integrate existing and other advanced technologies, applications, and software (e.g., multi-band/multi-mode capable radio) to expand disaster communications capabilities among emergency response providers. • Sustainment of current LMR capabilities. Grant recipients are strongly encouraged to sustain current LMR capabilities for mission critical voice capabilities so that systems continue to deliver highly available and reliable communications.
• Compliance with federal procurement requirements. As a condition of funding, recipients agree to comply with federal procurement requirements. Recipients are responsible for ensuring open and competitive procurements, subject to the specific programmatic requirements of the grant, and applicable state or local procurement requirements. Recipients are required to have written procurement policies in place, are encouraged to follow the same policies and procedures it uses for procurement from its non-federal funds, and should include any clauses required by the federal government. The following are key procurement tenets when using federal funds:
o Procurement transactions should be conducted to ensure open and free competition o Recipients/sub-recipients may not supplant, or replace, non-federal funds that are already budgeted or funded for a project
o Recipients/sub-recipients should avoid non-competitive practices (e.g., contractors that developed the specifications for a project should be excluded from bidding) • Compliance with covered telecommunications restrictions. Grant recipients should be aware of restrictions on the procurement and use of certain covered telecommunications equipment as a result of the John S. McCain National Defense Authorization Act of 2019 and subsequent legislation. In compliance with the Act, federal grant funds obligated by executive agencies may not be used to procure, obtain, extend, renew, or enter into a contract with certain covered telecommunications providers. The FCC maintains the list of communications equipment and service providers deemed threats to U.S. national security at fcc.gov/supplychain/coveredlist. • Promotion of regional capabilities. Grant recipients should coordinate and collaborate with agencies from neighboring municipalities, counties, intra-state regions, contiguous states, and interstate regions to facilitate regional operable and interoperable solutions, including shared solutions.
• Development of communications system lifecycle plans. Emergency responders must upgrade and maintain communications systems to ensure effective operation. Some programs require 79 To learn more about federal EHP requirements, see the Council on Environmental Quality Regulations, 40 CFR Part 1500-1508, or the U.S. Department of Energy website at: energy.gov/nepa/downloads/40-cfr-1500-1508-ceqregulations-implementing-procedural-provisions-nepa-ceq-1978. 38

FY 2024 SAFECOM Guidance on Emergency Communications Grants recipients to submit system lifecycle plans for equipment purchased with federal grant funds. As a result, recipients should develop a system lifecycle plan for any communications system. • Understanding of cost share. Federal grants often require recipients to provide a percentage of the total costs allocated to equipment. Federal funds cannot be matched with other federal funds, but can be matched through state, local, tribal, or territory cash and in-kind contributions. Match requirements are often waived for ancillary territories. Grant recipients should refer to the applicable grant guidance and consult the awarding agency with any questions regarding cost share requirements.
39

FY 2024 SAFECOM Guidance on Emergency Communications Grants

5. Emergency Communications Systems and Capabilities
Emergency communications are accomplished through many technologies, each with varying capabilities, standards, and features. As the public safety community adopts new technologies, LMR will remain an important tool for mission critical voice communications for emergency responders in the field for many years to come. Successful future planning requires a multi-path approach in maintaining LMR systems’ operability and interoperability while planning and deploying new emergency communications technologies. As such, grant recipients should invest in sustaining LMR capabilities while also planning for new technologies.

As LMR and IP-based technologies continue to become integrated with one another, interoperability and cybersecurity are increasingly important. When procuring equipment or software for emergency communications systems, grant recipients are strongly encouraged to purchase standards-based technologies to facilitate interoperability and security among jurisdictions and disciplines at all levels of government. Table 2 provides best practices for promoting interoperability and security in several types of emergency communications capabilities. For detailed standards and resources for each system type, refer to Appendix B.

Table 2. Best Practices when Purchasing Emergency Communications Capabilities Systems Best Practices
Land Mobile
Radio
• Review P25 accredited technical standards for LMR and the P25 Steering Committee Approved List of Accredited Technical Standards • Select P25 Compliance Assessment Program (P25 CAP) approved equipment • Obtain documented evidence of P25 CAP compliance; in the absence of testing information on the P25 Compliance Assessment Bulletins, entities should request results of applicable test procedures identified in the P25 standards list • Ensure additional features purchased are P25 compliant (e.g., AES 256 encryption) • Avoid non-standard and proprietary features, but if necessary, ensure features are identified and understand impacts on operability and interoperability • Provide written justification for non-compliant P25 purchases Public Safety
Broadband
• Seek guidance from the FirstNet Authority on how to best incorporate broadband communications into a public safety entity’s communications ecosystem Alerts,
Warnings, and
Notifications
• Read the IPAWS Best Practices and consult with IPAWS Program Management Office for compatible alert origination software tools
• Reference the IPAWS Program Planning Toolkit
• Review the IPAWS list of critical capabilities and recommended features of an alert origination software tool
• Ensure software tool compliance with the IPAWS CAP Profile and support of a testing environment
• Complete the IPAWS Memorandum of Agreement process
911 Systems • Discover standards through the NG911 Standards Identification and Review • Use the NG911 Self-Assessment Tool to determine NG911 maturity state • Consider SAFECOM and NCSWIC NG911 transition guidance for next steps • Select IP-enabled, accredited standards-based 911 equipment and software Data Exchange
and Information
Sharing
Environment
• Evaluate data information sharing needs and standards based on existing systems, users, and the type of information being exchanged • Read the Organization for the Advancement of Structured Information Standards (OASIS) Emergency Data eXchange Language (EDXL) and National Information Exchange Model (NIEM) resources on data messaging standards • Read the SAFECOM/NCSWIC guidance and best practices provided by the Approach for Developing an Interoperable Information Sharing Framework 40

6. Grants Management Best Practices
FY 2024 SAFECOM Guidance on Emergency Communications Grants Proper management of grants enables recipients to effectively implement projects and access grant funds.

It also can establish the entity as a trusted and capable steward of federal funding that is able to manage additional funds in the future. This section provides guidance and best practices for recipients to use throughout the grant lifecycle. Table 3 provides best practices during the four major phases of the grant:
• Planning grant applications (Pre-Award)
• Reviewing award agreements and funding (Award)
• Implementing grant-funded projects (Post Award)
• Completing federal grant projects (Closeout)
Table 3. Suggested Actions and Best Practices to Use during Grant Cycle Phases Phases Suggested Actions / Best Practices
PreAward
• Review and understand the NECP, SCIP, and other applicable plans • Coordinate with the SWIC and other key governance bodies and leadership to document needs, align projects to plans, and identify funding options80 • Work with SAA to include projects in state preparedness plans and to secure funding • Review program requirements included in grant guidance • Consult the federal granting agency, spectrum authority (i.e., FCC or FirstNet Authority), and SAFECOM Guidance when developing projects
• Align projects to federal and state-level plans and initiatives • Include coordination efforts with the whole community in applications • Identify staff to manage financial reporting and programmatic compliance requirements • Develop project and budget milestones to ensure timely completion • Identify performance measures and metrics that will help demonstrate impact • Consider potential impacts of EHP requirements on implementation timelines • Ensure proper mechanisms are in place to avoid commingling and supplanting of funds • Evaluate the ability of sub-recipients to manage federal funding • Consider how the project will be sustained after grant funding has ended Award • Review award agreement to identify special conditions, budget modifications, restrictions on funding, pass-through and reporting requirements, and reimbursement instructions • Update the proposed budget to reflect changes made during review and award • Inform sub-recipients of the award and fulfill any pass-through requirements Post
Award
• Establish repository for grant file and related data to be collected and retained from award through closeout, including correspondences, financial and performance reports, project metrics, documentation of compliance with EHP requirements and technology standards • Ensure fair and competitive procurement process for all grant-funded purchases • Understand the process for obtaining approval for changes in scope and budget • Adhere to proposed timeline for project and budget milestones; document and justify any delays impacting progress or spending
• Leverage federal resources, best practices, and technical assistance • Complete financial and performance reports on time
• Draw down federal funds as planned in budget milestones or in regular intervals • Complete projects within grant period of performance
Closeout • Ensure all projects are complete
• Maintain and retain data as required by the award terms and conditions • File closeout reports; report on final performance
80 Stakeholders can also contact their respective CISA Emergency Communications Coordinator for guidance. 41

FY 2024 SAFECOM Guidance on Emergency Communications Grants

7. Funding Sources
Applicants should consider all available funding sources, including traditional grants to help fund initial capital investments or improvements to communications systems, as well as other sources of funding that may entirely or partially fund emergency communications projects.

Traditional Grant Funding
CISA is charged with coordinating federal grants funding emergency communications. Through its work with the ECPC Grants Focus Group, CISA identified more than 90 federal grants and loans that fund emergency communications in the past fiscal year. When applying for these funds, grant applicants are encouraged to:
81 • Identify current grant funding available and alternative sources of funding • Review eligibility requirements, program goals, and allowable costs • Understand what past grants have funded in your jurisdiction • Partner with entities eligible to receive other funding sources Other Sources of Federal Funding
While SAFECOM Guidance traditionally covers federal financial assistance programs, there are other grant and loan programs that can provide extensive funding for state, local, tribal, and territorial public safety communications needs. For example, the U.S. Department of Agriculture (USDA) Rural Utility Service integrated interoperable emergency communications and 911 upgrade authority in its Telecommunications Loan Program, and loans and grants from USDA Rural Development’s Community Facilities Program provided critical funding for emergency communications projects. While loans offer an alternative to traditional grants, applicants should work with financial experts to understand loan terms and ensure their proposals meet all requirements under each program.

Also, there are several federal programs that are not solely focused on public safety communications (e.g., Rural Telecommunications and Rural Electrification Programs). These programs can improve access to 911 services; provide all-hazards warnings; improve integration and interoperability of emergency communications; provide critical infrastructure protection and outage prevention; and increase the reliability of standby power to emergency responders. Applicants are encouraged to identify additional funding sources, such as rural grants and loans or private and philanthropic grants, and work with eligible entities for those programs to improve communications infrastructure. 81 For an updated list of federal grants and loans that fund emergency communications, see: cisa.gov/safecom/funding.

Applicants can find and search grants and loans at: grants.gov. 42

FY 2024 SAFECOM Guidance on Emergency Communications Grants Funding and Sustainment Resources
CISA, SAFECOM, and NCSWIC publish numerous resources for state, local, tribal, and territorial governments and their public safety agencies to identify funding mechanisms for emergency communications projects. The following list includes educational documents and tools designed for stakeholders, available on the SAFECOM Funding Resources webpage. • Funding Mechanisms Guide for Public Safety Communications, assists public safety agencies in identifying funding sources for emergency communications projects. It highlights strengths, challenges, opportunities, and other considerations for funding sources to help agencies determine if certain mechanisms are suitable for their community. The guide also provides funding examples from states and localities, showcasing challenges and successes associated with real-world applications. • Emergency Communications System Lifecycle Planning Guide and the Lifecycle Planning Tool, aids stakeholders in their efforts to fund, plan, procure, implement, support, and maintain public safety communications systems, and eventually to replace and dispose of system components. • Emergency Communications Systems Value Analysis Guide and the accompanying Understanding the Value of Public Safety Communications Systems: A Brochure for Elected Officials and Decision-Makers, assist public safety agencies in evaluating communications systems and equipment for cost-effectiveness and value to its users. Materials describe common system components, including considerations and features required by public safety agencies that are unique to specific roles.
• Funding and Sustaining LMR: Materials for Decision Makers, provides an overview of radio systems, including information on their importance to public safety communications, as well as challenges to consider when upgrading systems.
o Funding and Sustaining LMR Trio, Part 1: Educating Decision-Makers on LMR Fundamentals, includes information on basic LMR system components such as simple diagrams, terminology, history, and current usage of LMR technologies by public safety agencies. o Funding and Sustaining LMR Trio, Part 2: Educating Decision-Makers on LMR Technology Issues, provides information about emerging technologies and the impact such technologies will have on LMR systems as they evolve. Information includes the LMR-to-LTE transition, and the need to sustain mission-critical voice through such transitions. o Funding and Sustaining LMR Trio, Part 3: Educating Project and Acquisition Managers on Project 25, delivers an introduction to standards-based purchasing, and an overview of the P25 standard explaining its importance to public safety interoperability. o Funding and Sustaining LMR Systems Brochure, serves as a tri-fold handout for state, local, tribal, and territorial government decision-makers and elected officials to explain the importance of funding and sustaining public safety radio systems. o Promoting the Importance of Funding and Sustaining LMR Action Memorandum, urges decision-makers to support the funding and sustainment of LMR systems. To help decisionmakers justify these purchases, the memorandum summarizes best practices from the LMR Trio and provides a list of resources for more information. • Interoperability Business Case: An Introduction to Ongoing Local Funding, advises the community on the elements needed to build a strong business case for funding interoperable communications. • Contingency Considerations When Facing Reductions in Emergency Communications Budgets, provides a series of contingency considerations to justify investment in four mission-critical resource categories: personnel, operating costs, equipment, and software. • Contingency Planning Guide for Emergency Communications Funding, provides a comprehensive look at the considerations public safety officials must weigh when planning for or facing budget reductions and recommends actions to take before, during, and after budget cuts. 43

FY 2024 SAFECOM Guidance on Emergency Communications Grants In addition, public safety agencies may reference materials on the SAFECOM Technology Resources and SAFECOM P25 Resources webpages to inform planning and funding for emergency communications projects.
• The Funding and the Future of P25 video, provides an overview of the value and advantages of P25 as a long-term investment in a community’s public safety. Presented through interviews of emergency communications practitioners and managers nationwide, the six-minute video focuses on the features and comparative costs of P25 standards-based systems versus non-P25 systems, the practical value of P25 technology in public safety operations, and recommendations for funding P25. Looking ahead, the presenters discuss the current states of P25 and LTE broadband technology, emphasizing the durability, transmitting power, one-to-many communication, and emergency push-to-talk features of P25 radios. Their conclusion: P25 and LTE are not exclusive options but likely complementary components of public safety communications in the future. 44

FY 2024 SAFECOM Guidance on Emergency Communications Grants Appendix A – Acronym List
3GPP Third Generation Partnership Project
AAR After-Action Report
AEL Authorized Equipment List
AES Advanced Encryption Standard
ANSI American National Standards Institute
ATIS Alliance for Telecommunications Industry Solutions, Inc.

AUXCOMM Auxiliary Communications
AWN Alerts, Warnings, and Notifications
CAP Common Alerting Protocol
CAPRAD Computer Assisted Pre-Coordination Resource and Database CASM Communication Assets Survey and Mapping
CDM Continuous Diagnostics and Mitigation
CFR Code of Federal Regulations
CIO Chief Information Officer
CISA Cybersecurity and Infrastructure Security Agency
CISO Chief Information Security Officer
CJIS Criminal Justice Information Services
CEQR Council on Environmental Quality Regulations
COLT Cell on Light Trucks
COML Communications Unit Leader
COMSEC Communications Security
COMT Communications Technician
CONOPS Concept of Operations
COW Cell on Wheels
CRD Compact Rapid Deployables
CSIRT Computer Security Incident Response Team
CSRIC Communications Security Reliability and Interoperability Council CSSI Console Subsystem Interface
CSSP Communications Sector-Specific Plan
DE Distribution Element
DES-OFB Data Encryption Standard-Output Feedback
DHS Department of Homeland Security
EAS Emergency Alert System
ECC Emergency Communications Center
ECPC Emergency Communications Preparedness Center
EDXL Emergency Data eXchange Language
A-1

FY 2024 SAFECOM Guidance on Emergency Communications Grants EHP Environmental Planning and Historic Preservation
EO Executive Order
EPC Evolved Packet Core
ETSI European Telecommunications Standards Institute
FCC Federal Communications Commission
FEMA Federal Emergency Management Agency
FIPS Federal Information Processing Standards
FirstNet Authority First Responder Network Authority
FY Fiscal Year
GETS Government Emergency Telecommunications Service
GFIPM Global Federated Identity and Privilege Management GRA Global Reference Architecture
GSMA Groupe Speciale Mobile Association
HAVE Hospital Availability Exchange
HF High Frequency
HSEEP Homeland Security Exercise and Evaluation Program HSPD Homeland Security Presidential Directive
ICAM Identity, Credential, and Access Management
ICS Incident Command System
IDS Intrusion Detection
IEC International Electrotechnical Commission
IEEE Institute of Electrical and Electronics Engineers
IEP Information Exchange Package
IEPD Information Exchange Package Documentation
IETF Internet Engineering Task Force
INCM Incident Communication Center Manager
INTD Incident Tactical Dispatcher
IP Internet Protocol
IPAWS Integrated Public Alert and Warning System
IPS Intrusion Prevention
IS Independent Study
ISE Information Sharing Environment
ISO International Organization for Standardization
ISSI Inter Radio Frequency Subsystem Interface
IT Information Technology
ITSL Information Technology Service Unit Leader
ITU International Telecommunications Union
LMR Land Mobile Radio
A-2

FY 2024 SAFECOM Guidance on Emergency Communications Grants LTE Long-Term Evolution
MFA Multi-Factor Authentication
MHz Megahertz
MOA Memorandum of Agreement
MOU Memorandum of Understanding
NAC National Advisory Council
NASNA National Association of State 911 Administrators
NCCIC National Cybersecurity and Communications Integration Center NCSWIC National Council of Statewide Interoperability Coordinators NECP National Emergency Communications Plan
NENA National Emergency Number Association
NEP National Exercise Program
NERC North American Electric Reliability Corporation
NG-SEC NENA Security for NG911 Standard
NHTSA National Highway Traffic Safety Administration
NIFOG National Interoperability Field Operations Guide
NG911 Next Generation 911
NIEM National Information Exchange Model
NIMS National Incident Management System
NIST National Institute of Standards and Technology
NISTIR NIST Internal/Interagency Reports
NOAA National Oceanic and Atmospheric Administration
NOFO Notice of Funding Opportunity
NPSBN Nationwide Public Safety Broadband Network, or FirstNet NRI National Risk Index
NTIA National Telecommunications and Information Administration OASIS Organization for the Advancement of Structured Information Standards OGC Open Geospatial Consortium
OMA Open Mobil Alliance
OMB Office of Management and Budget
P25 Project 25
P25 CAP P25 Compliance Assessment Program
PMO Project Management Office
POETE Planning, Organization, Equipment, Training, and Exercises PPD Presidential Policy Directive
PSAP Public Safety Answering Point
PSCR Public Safety Communications Research
PSHSB Public Safety & Homeland Security Bureau
A-3

FY 2024 SAFECOM Guidance on Emergency Communications Grants PTIG Project 25 Technology Interest Group
RADO Radio Operator
RAN Radio Access Network
RECCWG Regional Emergency Communications Coordination Working Group RECP Regional Emergency Communications Plans
RF Radio Frequency
RFI Request for Information
RM Resource Messaging
SAA State Administrative Agency
SAME Specific Area Message Encoding
SCIP Statewide Communication Interoperability Plan
SCSI Shared Communication Systems and Infrastructure
SDO Standard Development Organization
SHARES SHAred RESources High Frequency Radio Program
SIGB Statewide Interoperability Governing Body
SIEC State Interoperability Executive Committee
SLIGP State and Local Implementation Grant Program
SOP Standard Operating Procedure
SPR Stakeholder Preparedness Review
SWIC Statewide Interoperability Coordinator
TDoS Telephone Denial of Service
TFOPA Task Force on Optimal Public Safety Answering Point Architecture THIRA Threat and Hazard Identification and Risk Assessment TIA Telecommunications Industry Association
TICP Tactical Interoperable Communications Plan
TSP Telecommunications Service Priority
UHF Ultra High Frequency
USDA United States Department of Agriculture
URT Unified Reporting Tool
US-CERT U.S. Computer Emergency Readiness Team
VHF Very High Frequency
VoIP Voice over Internet Protocol
WEA Wireless Emergency Alerts
WPS Wireless Priority Service
XML Extensible Markup Language
A-4

FY 2024 SAFECOM Guidance on Emergency Communications Grants Appendix B – Technology and Equipment Standards and Resources This appendix provides grant applicants and recipients with operational best practices, technical standards, and resources to reference when developing communications systems. Above all, grant recipients should purchase standards-based technologies and equipment that promote interoperability with partners.

How to Use this Appendix
When procuring communications infrastructure, there are overarching considerations, guidelines, and specific standards to follow. No single document could include everything public safety communications system planners need to know. However, this appendix lists accredited technical standards applicable to public safety communications systems and resources for additional information. The following topics are included in this appendix:

System Lifecycle Planning....................................................................B-1 Cybersecurity.........................................................................................B-3 Continuity and Resilience.....................................................................B-7 Land Mobile Radio .............................................................................B-10 Nationwide Public Safety Broadband Network.................................B-14 Alerts, Warnings, and Notifications...................................................B-16 911 Systems .........................................................................................B-18 Data Exchange and Information Sharing Environment..................B-21 System Lifecycle
Planning

Grant recipients should employ best practices and recommendations from the 2018 Emergency Communications System Lifecycle Planning Guide The Cybersecurity and Infrastructure Security Agency (CISA), in collaboration with SAFECOM and the National Council of Statewide Interoperability Coordinators (NCSWIC), developed the Emergency Communications System Lifecycle Planning Guide, which provides recommended actions through easyto-use checklists for each phase of the system lifecycle planning model. It is intended for stakeholders to use in their efforts to fund, plan, procure, implement, support, and maintain public safety communications systems, and eventually replace and dispose of system components.

Each phase of the system lifecycle planning model—Pre-Planning; Project Planning; Request for Proposals and Acquisition; Implementation; Support, Maintenance, and Sustainment; End-of-Lifecycle Assessment and Replacement; and Disposition—includes best practices, considerations, and recommended checklists to assist public safety agencies embarking on system lifecycle planning.

Specifically, the checklists are designed to be torn-out, referenced, and used by project management teams throughout the system lifecycle. Table B-1 summarizes the system lifecycle planning model phases and high-level recommendations contained in the Emergency Communications System Lifecycle Planning Guide. Reference the guide for additional recommendations.

B-1

FY 2024 SAFECOM Guidance on Emergency Communications Grants Table B-1. System Lifecycle Planning Model and Recommendations Summary Planning Model Recommendations
Phase 1: Pre-Planning
Timing: 6–12 months
Goals: Inform and secure the
decision to replace, upgrade,
maintain, dispose of, and/or
acquire a new system
• Establish the core planning team
• Research and develop system and funding options
• Decide on the optimal and alternative solutions with funding options • Plan for frequency needs and channel programming
• Develop a business case, presentation materials, and strategic plan • Identify a legislative- or executive-level project champion • Present to decision-makers and secure funding to support the initial build-out and sustain the system throughout the entire lifecycle Phase 2: Project Planning
Timing: 6–18 months
Goals: Formalize the project
team; identify operational and
technical requirements for
system replacement and
upgrade; and develop the
project plan
• Consider the length of the planning process and communicate expected timeframes to elected officials
• Collect user needs and requirements and incorporate into project plans • Engage with communications leaders early for guidance and support (e.g., Statewide Interoperability Coordinators [SWIC], Statewide Interoperability Governing Bodies [SIGB])
• Identify strong Project Sponsors (e.g., state or local elected officials) • Begin planning the Request for Proposals (RFP)
Phase 3: RFP and Acquisition
Timing: 6–12 months
Goals: Select the appropriate
procurement vehicle and acquire
systems, components, and
services
• Develop a written action plan
• Form the RFP team
• Develop the Statement of Work (SOW)
• Include specifications, requirements, and standards compliance in RFP • Establish written evaluation criteria, well before the award • Conduct a formal objective review process and document results Phase 4: Implementation
Timing: 12–18 months
Goals: Develop an
implementation plan; install new
systems; test; train users; and
transition from legacy to new
• Develop the implementation plan
• Understand and document testing procedures (e.g., factory testing, staging, site installation and testing, coverage verification, compliance and interoperability testing and acceptance, cut-over, final acceptance) • Update operational procedures and train users
• Promote new communications capabilities and benefits to the community Phase 5: Support, Maintenance
and Sustainment
Timing: Year(s) 1–25
Goals: Inventory and maintain
equipment; manage budget;
assess and communicate needs
• Maintain an accurate inventory of equipment (e.g., scope, database tool, inventory team, processes to compile and secure data)
• Determine and execute an ongoing maintenance and operations model • Manage the budget when the project is conceived, directly before it is funded and after delivery
• Share communications needs with decision-makers early and continually Phase 6: End-of-Lifecycle
Assessment and Replacement
Timing: Years 7–25
Goals: Determine when to
replace systems or components
with solutions to best fit
operational and technical needs
• Conduct ongoing assessments of current system (e.g., implement a balanced scorecard) to plan for technology maturity
• Refresh or upgrade systems, as needed, to extend the life • Determine potential replacement solutions, with consideration to support national, state, and regional interoperability initiatives; consider early adoption of new technologies; and, adhere to widely-used technical standards
Phase 7: Disposition
Timing: 90 days after cut-over or
transition
Goals: Determine options and
dispose of legacy systems or
components
• Develop the disposition plan
• Determine options (e.g., reuse or repurpose old components, consider space availability, convey surplus equipment to partner agencies) in consideration of legal or policy limitations, and business requirements • Brief leaders on disposition plans
• Identify lessons learned following disposition
B-2

FY 2024 SAFECOM Guidance on Emergency Communications Grants Cybersecurity
Grant recipients should implement the NIST Cybersecurity Framework and take advantage of existing cybersecurity standards, guidance, tools, and resources
The public safety community must continually identify risks and address evolving security requirements.

Emergency communications cybersecurity is a shared mission across all levels of government, the private sector, nongovernmental organizations, and even the public. To protect emergency communications from cyber threats and attacks, recipients will need to invest in solutions that enhance cybersecurity posture.

Cybersecurity must be addressed through planning, governance, and technology solutions that secure networks. Recipients should ensure cybersecurity planning is comprehensive and maintained throughout the lifecycle of all network components. Cybersecurity risk management should also include updates to non-technology support activities, such as mutual aid agreements, standard operating procedures, and policy development. Personnel should be trained on the latest security, resiliency, continuity and operational practices and maintain in-service training as new technology and methods become available.

Despite every effort, cyber incidents can and do occur. Being prepared to execute response processes and procedures, prevent expansion of the event, mitigate its effects, and eradicate the incident is necessary.

Incident response plans, recovery or resiliency plans, and continuity of operations plans are useful in cybersecurity incident response. Recovery planning processes and strategies are improved by incorporating lessons learned into future activities.

Cybersecurity Framework
The National Institute of Standards and Technology (NIST) developed the Cybersecurity Framework as a flexible and voluntary risk-based approach that outlines techniques to reduce cybersecurity risk. The new

2.0 edition (released in February 2024) is designed for all audiences, industry sectors, and organization types—regardless of their degree of cybersecurity sophistication. Recipients are strongly encouraged to implement NIST’s framework to complement an existing risk management process or to develop a credible program if one does not exist. In addition to NIST materials, sector-specific Cybersecurity Framework guidance is available from CISA.

The NIST Cybersecurity Framework establishes six functions to integrate cybersecurity into mission functions and operations, including: 1) govern the organization’s cybersecurity risk management strategy, expectations, and policy; 2) identify, evaluate, and prioritize risks; 3) protect against identified risks; 4) detect attacks and compromises to the network as they arise; 5) respond with actions to cybersecurity incident; and 6) recover assets and operations affected to ensure the resiliency and continuity of communications. CISA’s Emergency Services Sector has developed tailored guidance specific to emergency service disciplines, including a NIST Framework implementation guide with a repeatable process to identify and prioritize cybersecurity improvements.82 There is considerable cybersecurity guidance available from government, industry, and academic organizations and a multitude of standards development organizations (SDOs) that contribute to technical standards and best practices. Organizations managing critical infrastructure will continue to have unique risks―different threats, different vulnerabilities, and different risk tolerances—and how they implement the standards and guidance available will vary. There is currently no one-size-fits-all network cybersecurity solution. Table B-2 lists some of the potentially applicable standards for cybersecurity that recipients should leverage as they identify and select the standards that fit their system and mission needs. Table B-3 lists 82 Suggested resources include the Emergency Services Sector Cybersecurity Framework Implementation Guidance and Emergency Services Sector Roadmap to Secure Voice and Data Systems.

B-3

FY 2024 SAFECOM Guidance on Emergency Communications Grants cybersecurity resources for additional information. While these lists are not exhaustive, they include some of the more comprehensive guidance for the public safety community.

Table B-2. Cybersecurity Standards
Organizations Standards
Third Generation
Partnership Project
(3GPP) Security
Standards
3GPP’s security working group, SA3, is continuously updating security standards associated with prevalent technologies. Specifically, the group is addressing 3GPP standards for network access security, network domain security, user domain security, application domain security, and user configuration and visibility of security is important for critical infrastructure implementations. 3gpp.org.

American National
Standards Institute
(ANSI) / International
Society of Automation
(ISA)
ANSI/ISA standards focus on automation and control systems solutions. The NIST Cybersecurity Framework recommends two ANSI/ISA standards for use:

ANSI/ISA-62443-2-1 (99.02.01)-2009 and ANSI/ISA-62443-3-3 (99.03.03)-2013.

Also, outputs of the Alliance for Telecommunications Industry Solutions (ATIS) Emergency Services Interconnection Forum, Next Generation Interconnection Interoperability Forum, and Wireless Technologies and Systems Committee are important to the public safety community. isa.org
Criminal Justice
Information Services
(CJIS) Security Policy
CJIS standards contain information security requirements, guidelines, and agreements reflecting the will of law enforcement agencies for protecting the sources, transmission, storage, and generation of Criminal Justice Information. fbi.gov/about-us/cjis/cjis-security-policy-resource-center.

European
Telecommunications
Standards Institute
(ETSI)
ETSI Telecommunications & Internet converged Services & Protocols for Advanced Networks (TISPAN) has been a key standardization body in creating Next Generation Network (NGN) specifications, and their Cyber Security committee focuses entirely on privacy and security activities. Of note for emergency communications are the ETSI TS 102, 123, 182, and 282 series. etsi.org.

Federal Information
Processing Standards
(FIPS)
FIPS establishes the minimum security requirements for federal information systems. nist.gov/itl/publications-0/federal-information-processing-standards-fips.

Health Insurance
Portability and
Accountability Act of
1996 (HIPAA)
Legislation enacted by Congress in 1997 to streamline medical regulations, privacy considerations, and the efficiency and security of medical care. The standards/rules associated with HIPAA address some of the NIST Cybersecurity Framework functions. hhs.gov/hipaa/index.html.

International
Organization for
Standardization (ISO) /
International
Electrotechnical
Commission (IEC)
Standards
The ISO/IEC 27000 series of standards provide a foundation for information security management best practices. Of interest to emergency communication networks may be ISO/IEC 27001, ISO/IEC 27003, ISO/IEC 27002, ISO/IEC 27032, and ISO/IEC 17799. iso.org/home.html.

Institute of Electrical and
Electronics Engineers
(IEEE)
IEEE produces sector-specific security standards, as well as industry guidance.

Of interest to networks may be the 802, 1363, and 1619 series, as well as C37.240-2014 IEEE Standard Cybersecurity Requirements for Substation Automation, Protection, and Control Systems. ieee.org.

International
Telecommunication
Union (ITU)
A fundamental role of ITU is to build confidence and security in the use of Information and Communication Technologies. Of note for emergency communications networks include X.800, X.805, and X.1051. itu.int/en/Pages/default.aspx.

Internet Engineering
Task Force (IETF)
IETF Working Groups are the primary mechanism for development of IETF standards. IETF Working Groups currently have more than 600 standards regarding security mechanisms, integrity mechanisms, network layer security, transport layer security, application layer security, encryption algorithms, key management, secure messaging, etc. ietf.org.

B-4

FY 2024 SAFECOM Guidance on Emergency Communications Grants Organizations Standards
National Fire Protection
Association 1221/1225
A standard for the installation, maintenance, and use of emergency services communications systems, including cybersecurity considerations. nfpa.org/codesand-standards/all-codes-and-standards/list-of-codes-andstandards/detail?code=1221.

NIST Recommendations
on Cybersecurity (Special
Publications 800 Series)
NIST’s 800 series provides targeted cybersecurity guidance and are strongly encouraged to be incorporated into cybersecurity planning. In particular, NIST 800-53r5 covers Cybersecurity and Privacy controls and NIST 800-63-4 covers requirements for implementing digital identity solutions. csrc.nist.gov/publications/sp.

North American Electric
Reliability Corporation
(NERC) Reliability
Standards
Reliability standards address the security of cyber assets essential to the reliable operation of the electric grid. With emerging interconnectivity of infrastructure, the emergency communications community may also need to address these standards. nerc.com/pa/Stand/Pages/USRelStand.aspx.

Telecommunications
Industry Association
(TIA)
TIA has both Cybersecurity and Public Safety working groups. Standards of particular use for emergency communications include: TR-8, TR-30, TR-34, TR41 TR-42 TR-45, TR-47, TR-48, TR-49, TR-50 M2M, TR-51, and TIA-102. tiaonline.org.

Table B-3. Cybersecurity Resources
Organizations Resources
Committee on
National
Security
Systems
• Committee on National Security Systems Policies
Department of
Homeland
Security (DHS)
• CISA’s Public Safety Communications and Cyber Resiliency Toolkit • CISA Central
• CISA Cyber Essentials Toolkit
• CISA Transition to NG911 Resources
• CISA 911 Cybersecurity Resource Hub for Emergence Communications Centers • CISA Cybersecurity Training and Exercises
• CISA Emergency Services Sector Cybersecurity Framework Implementation Guidance • CISA “First 48”: What to Expect When a Cyber Incident Occurs • CISA Guide to Getting Started with a Cyber Risk Assessment • CISA Resources for State, Local, Tribal, and Territorial (SLTT) Governments • CISA Stop Ransomware / Public Safety Emergency Communications Resources • Cybersecurity Incident & Vulnerability Response Playbooks • Cyber Resiliency Resources for Public Safety Fact Sheet • Emergency Services Sector (ESS) Cyber Risk Assessment – 2012 • ESS Roadmap to Secure Voice and Data Systems – 2014
• ESS Cybersecurity Framework Implementation Guidance – 2020 • Federal Virtual Training Environment (FedVTE)
• National Cyber Awareness System
• National Cyber Incident Response Plan
• National Infrastructure Protection Plan
• Best Practices for Encryption in Project 25 Public Safety Land Mobile Radio Systems Department of
Energy
• Energy Sector Cybersecurity Capability Maturity Model (C2M2) Program B-5

FY 2024 SAFECOM Guidance on Emergency Communications Grants Organizations Resources
Executive
Orders (EO) and
President
Directives
• EO 13636: Improving Critical Infrastructure Cybersecurity • EO 13231: Critical Infrastructure Protection in the Information Age and EO 13286 • EO 13618: Assignment of National Security and Emergency Preparedness Communications Functions
• Executive Office of the President, Presidential Policy Directive 21 (PPD – 21) • EO 13407: Public Alert and Warning System
• EO 13800: Strengthening the Cybersecurity of Federal Networks and Critical Infrastructure
• EO 14028: Improving the Nation’s Cybersecurity
Federal Bureau
of Investigation
• Cyber Crime
• Federal Bureau of Investigation Internet Crime Complaint Center Industry Alerts Federal
Communications
Commission
• Communications Security, Reliability and Interoperability Council (CSRIC) • Task Force on Optimal PSAP Architecture (TFOPA)
• Cyber Security Planning Guide
Federal
Emergency
Management
Agency
• Emergency Management and Response-Information Sharing and Analysis Center (EMRISAC) • Cybersecurity Gap Analysis, FEMA National Cyber Resilient Architecture, and Training resources
Government
Accountability
Office
• U.S. Government Accountability Office, Cybersecurity
National
Institute of
Standards and
Technology
• Cybersecurity Framework 2.0
• Internal/Interagency Reports (NISTIRs)
• National Initiative for Cybersecurity Education (NICE) • NICE Cybersecurity Workforce Framework
• Assessing Security and Privacy Controls in Information Systems and Organizations • Digital Identity Guidelines
Various
Industry and
Associations
• ATIS Industry Best Practices
• Association of Public-Safety Officials, International (APCO), APCO Cybersecurity, and Cybersecurity Resources, including APCO Cybersecurity Guide for Public Safety Communications Professionals and APCO Introductory Guide to Cybersecurity for PSAPs • ISACA COBIT 5 Framework
• ITU Security Standards Roadmap
• Center for Internet Studies (CIS) Critical Security Controls (CSC), available through the Multi-State Information Sharing and Analysis Center
• National Association of State Chief Information Officers (NASCIO) Cybersecurity Awareness, including NASCIO Cyber Disruption Response Planning Guide for States • National Conference of State Legislation Cybersecurity Training for State Employees • NENA, including NG-SEC
• Open Web Application Security Project (OWASP) Top Ten Project • OWASP Internet of Things Project
B-6

FY 2024 SAFECOM Guidance on Emergency Communications Grants Continuity
and
Resilience
Grant recipients should target funding toward activities that address communications continuity, survivability, and resiliency. Activities can include system assessments, analysis of threats and vulnerabilities, and strategic plan and procedural updates to mitigate identified risks
Lessons learned from major disasters, unplanned events, and full-scale exercises have identified a need for greater coordination of emergency communications among senior elected officials, emergency management agencies, and first responders at all levels of government. Responders arriving on the scene of a domestic incident are not always able to communicate with other response agencies, particularly when the incident requires a multi-agency, regional response effort, or when primary communications capabilities fail. This lack of operability and interoperability between agencies is further complicated by problems with communications continuity, survivability, and resilience, which hinders the ability to share critical information, and can compromise the unity-of-effort required for an effective incident response.

Applicants investing in emergency communications are encouraged to work with Statewide Interoperability Coordinators, Statewide Interoperability Governance Bodies, and appropriate stakeholders across levels of government to:
• Establish robust, resilient, reliable, secure, and interoperable communications capabilities • Plan for mission-related communications and connectivity among government leadership, internal elements, other supporting organizations, and the public under all conditions • Trace all communications systems/networks from end-to-end to identify single points of failure • Recipients should also address the following issues:
o Integrate communications needs into continuity planning efforts and emergency operations plans by incorporating mitigation options to ensure uninterrupted communications support
o Maintain and protect communications capabilities against emerging threats, both manmade and natural, to ensure their readiness when needed o Frequently train and exercise personnel required to operate communications capabilities o Test and exercise communications capabilities
o Establish a cybersecurity plan that includes continuity of an “out of band” communications capability such as High Frequency (HF) Radio Frequency (RF), fiberbased communications pathways that do not rely on public infrastructure • Ensure key communications systems resiliency through:
o Availability of secondary and backup systems
o Development of standard operating procedures and training to address the use of secondary and backup systems
o Diversity of network element components and routing
o Geographic separation of primary and alternate transmission media o Availability of backup power sources
o Access to systems that are not dependent on commercial infrastructure o Maintained spare parts for designated critical communications systems o Agreements with commercial suppliers to remediate communications Single Point of Failures
B-7

FY 2024 SAFECOM Guidance on Emergency Communications Grants Table B-4. Continuity and Resilience Resources
Resource Description
FEMA National
Continuity Programs
National Continuity Programs highlight the national policy and guidance for continuity of operations initiatives. They provide guidance and assistance to support continuity preparedness for federal departments and agencies; state, local, tribal, and territorial government jurisdictions; and private sector organizations.

CISA Shields Ready Shields Ready campaign is designed to help all critical infrastructure stakeholders to take action to enhance security and resilience—from industry and businesses to government entities at all levels, and even individuals by providing recommendations, products, and resources to increase individual and collective resilience for different risk contexts and conditions.

CISA Regional
Resiliency
Assessment
Program
The Regional Resiliency Assessment Program is a cooperative assessment of specific critical infrastructure within a designated geographic area. DHS works with selected areas each year to conduct a regional analysis of surrounding infrastructure and address a range of resilience issues that could have significant regional or national consequences if disrupted.

CISA Ten Keys to
Obtaining a Resilient
Local Access
Network
This document introduces resiliency concepts and provides ten keys to obtaining and maintaining resiliency in a local access network, such as knowing the exact network infrastructure in the local loop, interfacing with commercial service providers, and properly maintaining alternative path solutions. CISA developed these ten fundamental steps, supported by descriptive text and visually appealing graphics, as recommendations to help organizations maintain critical communications in emergency situations.

CISA Public Safety
Communications
Resiliency SelfAssessment
Guidebook
This document provides a self-assessment methodology for public safety entities to identify and address potential points of failure in their communication networks by evaluating the local access networks of their primary and alternate operating facilities.

The methodology describes the process of gathering data on network infrastructure, creating logical and physical network maps, and choosing resiliency solutions based on the network maps. DHS also developed a Resiliency Fact Sheet to understand communications continuity planning and offer resources to assist entities.

CISA Priority
Services Programs
Priority Services Programs, including the Government Emergency Telecommunications Service, Wireless Priority Service, and Telecommunications Service Priority, support national leadership; federal, state, local, tribal, and territorial governments; first responders; and other authorized national security and emergency preparedness users. They are intended to be used in an emergency or crisis situation when data, landline, or wireless networks are congested and the probability of completing a normal transmission or call is reduced.

CISA
Electromagnetic
Pulse (EMP)
Guidance
The EMP Protection and Resilience Guidelines for Critical Infrastructure and Equipment provides guidelines to assist federal, state, and local officials and critical infrastructure owners and operators to protect mission essential equipment against EMP threats. There are four EMP Protection Levels defined. These levels were initially developed at the request of the federal Continuity Communications Managers Group but are applicable to any organization that desires to protect its electronics and critical infrastructures.

Infrastructure
Obstructions to
Radio Propagation
This document provides an overview of obstructions and interferences to radio frequency resources, including both active and passive sources. In addition, it includes a series of example planning approaches that agencies have taken to prevent or mitigate obstructions.

Public Safety
Communications and
Cyber Resiliency
Toolkit
This document assists public safety agencies and others responsible for communications networks in evaluating current resiliency capabilities, identifying ways to improve resiliency, and developing plans for mitigating the effects of potential resiliency threats. Through an interactive graphic, users can explore topic specific systems-based resources and learn more about key threats to communications and cyber resiliency.

B-8

FY 2024 SAFECOM Guidance on Emergency Communications Grants Resource Description
Public Safety
Communications
Dependencies on
Non-Agency
Infrastructure and
Services
This white paper provides high-level insights on non-agency communications infrastructure for system administrators, public safety decision-makers, and other stakeholders involved in public safety communications planning or implementation.

While not a comprehensive guide, this document equips stakeholders with real-word examples of these dependencies, recommendations for ensuring resiliency and continuity of operations, and supplemental resources.

Cyber Resiliency
Resources for Public
Safety Fact Sheet
This document provides an overview of publicly available cybersecurity evaluations and resources, helping stakeholders ensure the scope and requirements of resiliency assessments are aligned with their needs.

Radio Frequency
Interference Best
Practices Guidebook
This document provides stakeholders with an overview of RF interference concepts, threats, and mitigation initiatives. Applicants can review this guidebook to understand ongoing efforts related to awareness, preparation, mitigation, and current laws pertaining to RF interference. The document also provides best practices on how to recognize, respond to, report, and resolve RF interference incidents.

Resilient Power Best
Practices Fact Sheet
This document summarizes recommendations from the CISA Resilient Power Working Group, consisting of federal, state, local, tribal, and territorial stakeholders, non-profits, and private industry. These critical communications infrastructure best practices should be part of a comprehensive, risk-informed Business Continuity and Continuity of Operations plans, developed per FEMA guidance.

CISA Infrastructure
Dependency Primer
This tool is a supplement to the Infrastructure Resilience Planning Framework and is intended to help state and local planners better understand how infrastructure dependencies can impact risk and resilience in their community and incorporate that knowledge into planning activities.

B-9

FY 2024 SAFECOM Guidance on Emergency Communications Grants Land
Mobile
Radio
Grant recipients should purchase digital LMR systems and equipment compliant with the Project 25 (P25) Suite of Standards (Telecommunications Industry Association), and include all needs and requirements, identifying applicable P25 standards and stating their agency requirements for interoperability in any SOW or acquisition documents
Recipients should purchase P25 compliant systems and equipment that has been assessed as compliant in accordance with the P25 Compliance Assessment Program, or approved test procedures of the P25 standards in the absence of completed P25 Compliance Assessment Program testing
Recipients are strongly encouraged to implement or transition to comprehensive Advanced Encryption Standard (AES) 256 -bit encryption on all LMR systems. Use of proprietary/non - standard encryption, privacy options (e.g., ADP, Encryption Lite, ARC4), or deprecated encryption (i.e., Data Encryption Standard [DES] and all derivatives) is not an acceptable use of federal grant funding as these algorithms have been compromised, deprecated, and offer little protection Recipients should ensure all P25 eligible equipment, features, functions, and capabilities selected are P25 compliant and are tested to ensure interoperability, to include new equipment and upgrades
When purchasing interoperability equipment, services, and gateway devices to provide connectivity between LMR systems, those devices should, at a minimum, be implemented using P25 compliant wireline interfaces (e.g., ISSI, CSSI, DFSI) LMR systems are terrestrially-based, wireless, narrowband communications systems commonly used by federal, state, local, tribal, and territorial emergency responders, public works/public service entities, and the military in non-tactical environments, to support voice and low-speed data communications. These systems are designed to meet public safety’s unique mission and critical voice requirements and support timesensitive, lifesaving tasks, including sub-second voice call-setup, group calling capabilities, high-quality audio, and priority access to the end-user. Because LMR systems implemented by the public safety community support responders’ safety and lifesaving operations, they are designed and implemented to achieve the highest levels of availability, reliability, redundancy, coverage, and capacity, and can operate in harsh natural and man-made environments. LMR technology has progressed over time from conventional, analog voice service to complex systems incorporating IP networking, digital protocols, and trunked features.

These enhancements have improved the interoperability, spectral efficiency, security, reliability, availability, redundancy, and functionality of voice and low-speed data communications.

The public safety community is following a multi-path approach to develop, establish, and maintain critical communications capabilities. To improve interoperability across investments, grant recipients are strongly encouraged to ensure digital voice systems and equipment purchased with federal grant funds are compliant with the Project 25 (P25) Suite of Standards, unless otherwise noted in a program’s grant guidance.

Recipients should ensure all new and upgraded P25 eligible equipment, features, functions, and capabilities 83 83 Applicants should read grant guidance carefully to ensure compliance with standards, allowable cost, documentation, reporting, and audit requirements. If interested in using federal funds to purchase equipment that does not align with P25 standards or does not appear on the approved equipment list, the applicant should consult with the federal grantmaking agency to determine if non-P25 compliant equipment is allowable. In some cases, written justification must be provided to the grantor. Many agencies will not approve non-standards-based equipment unless there are compelling reasons for using other solutions. Authorizing language for most emergency communications grants strongly encourages investment in accredited technical standards-based equipment. Funding requests by agencies to replace or add radio equipment to an existing non-P25 system (e.g., procuring new portable radios for an existing analog system) will be considered if there is a clear rationale why such equipment should be purchased and written justification of how the equipment will advance interoperability and support eventual migration to interoperable systems. Written justification should also explain how that purchase will serve the needs of the applicant better than equipment or systems that meet or exceed such standards. Absent compelling reasons for using other solutions, agencies should invest in accredited technical standards-based equipment.

B-10

[email protected]
FY 2024 SAFECOM Guidance on Emergency Communications Grants selected for procurement are verifiably P25 compliant and interoperable. When federal grant funds are used to purchase P25 LMR equipment and systems that contain non-standard features or capabilities while a comparable P25 feature or capability is available, recipients must ensure the standards-based feature or capability is also purchased to ensure interoperability. For more information on P25, contact the P25 Steering Committee at [email protected].

Grant recipients should purchase P25 compliant systems and equipment that has been assessed in accordance with the P25 Compliance Assessment Program (P25 CAP). P25 accredited standards provide many technical specifications designed to ensure equipment is interoperable regardless of manufacturer.

Recipients should obtain documented evidence of P25 compliance from the manufacturer that the equipment has been tested and passed all the applicable, published, normative P25 compliance assessment test procedures for performance, conformance, and interoperability as defined in the latest P25 Compliance Assessment Bulletins for testing requirements. If documentation for applicable equipment is not available through the P25 CAP or there is an absence of applicable testing in the P25 CAP, recipients should obtain documented evidence from the manufacturer stating that all applicable tests were conducted in accordance with the published test procedures in the P25 Suite of Standards and successfully passed. In the absence of applicable P25 testing procedures, agencies should work with the providing manufacturer/vendor to ensure that procured equipment or services meet stated requirements and are interoperable with the procuring agency’s known interoperability partners. Contact the P25 CAP at for additional guidance.
84 Encryption
Recipients using federal funds to purchase encryption for new or existing communications equipment shall ensure encryption capabilities are compliant with the published P25 Block Encryption Protocol Standard.

Recipients investing in encryption must implement the AES 256-bit Encryption Algorithm as specified in the P25 Block Encryption Protocol. References to the current version of the P25 Block Encryption Protocol, ANSI/TIA-102.AAAD should be included in all procurement documents, along with specific agency requirements for primary, secondary, backup, or interoperability systems/capabilities where applicable.

The P25 Suite of Standards references the use of AES as the primary encryption algorithm, which is the only federally approved encryption standard for LMR communications by NIST. While the P25 accredited technical standard allows Data Encryption Standard-Output Feedback (DES-OFB) for backwards compatibility and interoperability with legacy DES-only equipment, it is imperative that entities continue to transition to a common AES-only environment to ensure secure encrypted interoperable communications with public safety partners at all levels of government. While most federal agencies have transitioned to AES encryption, some state, local, tribal, and territorial agencies continue to use DES as their primary means of encryption or other proprietary/non-standard encryption algorithms.

However, the continued use of DES and its derivatives enables a specific vulnerability in LMR encryption.

NIST, which approved the use of DES in 1976, withdrew Federal Information Processing Standard (FIPS)- 46, Data Encryption Standard as a standard on May 19, 2005, citing the weakness and repeated compromise of DES and the availability of the current federal standard specified in FIPS-197, Advanced Encryption Standard. DES has since been deprecated in P25 standards and is only maintained to enable P25 AES encryption-compliant equipment to also include DES for the purposes of interoperability with 84 Regardless of the status and availability of P25 CAP testing documentation, grant recipients should include comprehensive acceptance test plan(s) and testing criteria of stated requirements in their procurement and contractual documents to ensure that the required and expected interoperability of features, functions, and services has been provided, especially in multi-manufacturer/vendor implementation environments. The manufacturer/vendor should verify (as part of formal systems acceptance processes) the equipment or services are P25 standards compliant and interoperable with other equipment, features, functions, and capabilities.

B-11

FY 2024 SAFECOM Guidance on Emergency Communications Grants equipment supporting legacy DES products. As a result of subsequent policies, federal agencies must only use NIST approved AES 256-bit encryption. For more information, see CISA’s Transition to AES. 85 86 Recipients seeking to use federal grant funds to purchase non-standard, deprecated encryption features (e.g., 40/56-bit encryption, proprietary privacy solutions, DES or any DES derivatives) or capabilities for new or existing equipment must ensure AES 256-bit encryption is also purchased for interoperability with other emergency responders. The equipment must also use the NIST-approved algorithm available to all public safety agencies and disciplines regardless of level of government. Agencies currently using DES or DES derivatives may continue to use this encryption method for interoperability but should migrate to AES for all encryption as soon as possible. The continued use of DES, its derivatives, manufacturers’ privacy features, or other non-standard encryption algorithms for any LMR encryption is strongly discouraged and presents substantial risks of compromised communications.

Agencies acquiring encryption capabilities are strongly encouraged to only procure subscriber equipment that supports multi-key operations and capabilities. This allows multiple encryption keys to be stored within the subscriber unit’s cryptographic module facilitating the use of different encryption keys for channels or talkgroups. Multikey capabilities also permit more than one Key Management Facility or Key Fill Device to provide encryption keys to subscriber devices. Single key capable devices only allow the use of a single encryption key.

Interconnecting Systems
When purchasing P25 interoperability equipment, services, and devices to provide connectivity between LMR systems, those devices should, at a minimum, implement the P25 wireline interfaces, such as the Inter Radio Frequency Subsystem Interface (ISSI) or Console Subsystem Interface (CSSI). Note, there are potential interoperability issues of features and functionality afforded by these interfaces when implementing ISSI/CSSI, especially when using various system manufacturers as there are implementation differences driven by each manufacturer’s interpretation of the technical standards. These implementation differences may manifest in the lack of interoperability of current P25 system features, functions, and services supported by and through these interfaces. Therefore, it is imperative that agencies implementing ISSI or CSSI create comprehensive needs and requirements documentation specifically detailing which P25 features, functions, and services are required, and the expected behaviors of the connected systems supported by the ISSI or CSSI.

While baseline P25 accredited technical standards for ISSI/CSSI connections exist, they remain under development and revision. Due to the limited availability of completed technical standards and differing manufacturer’s features and functionality implementation practices, public safety agencies should consider the planning and technical complexities associated with the implementation of ISSI/CSSI capabilities to connect RF-subsystems (RFSS) from the same or dissimilar LMR suppliers/manufacturers.

As such, grant applicants should:
• Ensure that existing operability and interoperability between RFSS/networks remain intact and operational during and after ISSI/CSSI implementation;
85 The 2002 Federal Information Security Management Act, Public Law 107-347, and the 2014 Federal Information Systems Modernization Act, Public Law 113-283, prohibits the use of any other encryption algorithm by federal entities. While these statutes permit only NIST approved AES encryption use by federal entities, such prohibitions do not directly apply to SLTT agencies. However, SLTT agencies desiring to maintain encrypted interoperable communications with federal agencies should transition to AES 256-bit encryption. 86 CISA’s Transition to Advanced Encryption Standard document is available at: cisa.gov/sites/default/files/2023- 10/23_0918_fpic_AES-Transition-WhitePaper_Final_508C_23_1023.pdf.

B-12

FY 2024 SAFECOM Guidance on Emergency Communications Grants • Identify explicit requirements of features, functionalities, and capabilities that the ISSI/CSSI connections will support to a same or dissimilar manufacturer’s RFSS/systems, including interoperability requirements, in any SOW, acquisition documents, or contracts; • Require the prospective vendor/manufacturer to illustrate their ability and acceptance to provide these explicit features, functionalities, and capability requirements for ISSI/CSSI implementations, regardless of which manufacturer’s ISSI/CSSI and RFSS/networks are in place, in the appropriate purchasing agreements or contracts;
• Confirm the selected supplier/manufacturer develops and executes a comprehensive acceptance test plan that validates P25 accredited standards compliance, as well as successful operability and interoperability of features, functions, and capabilities on each side of the ISSI/CSSI connection(s), consistency with procurement and acquisition requirements, and compliance with agreed upon performance, applicable technical standards, passage of available standards-based testing, and expectations of operations amongst ISSI/CSSI connected RFSS/networks; • Submit evidence to the federal granting agency, if required, documenting successful P25 CAP testing (e.g., P25 product Summary Test Reports available on the P25 CAP website), certifying compliance with applicable accredited technical standards, as well as evidence of effective operability and interoperability of features, functions, and capabilities with all ISSI partners.

Interconnecting LMR and Broadband Networks
Applicants may also be interested in using grant funds to enable interoperability between existing LMR and long-term evolution (LTE) or 5G/6G broadband networks. Note, TIA/ATIS P25 accredited technical standards for interconnecting LMR to LTE/5G/6G systems remain under development. While the 3GPP accredited standards exist, the TIA/ATIS P25 accredited standards remain a work in progress.

Notwithstanding, agencies should pursue solutions that are 3GPP standards compliant and interoperable.

Agencies should also thoroughly investigate prospective vendor plans for supporting changes to their product offerings when the TIA/ATIS P25 standards are completed.

Agencies should be aware of the multiple proprietary solutions offered by vendors/manufacturers that may provide acceptable LMR to LTE/5G/6G voice service integrations. However, while potentially achieving adequate LMR to LTE/5G/6G voice interoperability, these proprietary solutions may not be interoperable amongst themselves or with a broadband provider’s network level Push-to-Talk (PTT) voice service, thus creating an LTE/5G/6G interoperability issue. Additionally, the indiscriminate, non-planned use of some LTE/5G/6G to LMR Over the Top (OTT) PTT solutions has proven to be potentially detrimental to the hosting LMR systems and created significant operability issues due to site loading issues on the host system infrastructure. Investing in solutions that are not based on open standards is a misuse of federal funds, as additional solutions may be needed to restore or provide required interoperability among participating jurisdictions.

Considering the numerous potential PTT voice solutions and the cautions regarding the lack of interoperability of various OTT PTT applications, agencies should fully explore (and test) PTT solutions with potential providers while ensuring the agency’s requirements for LMR to broadband voice capabilities are met. Agencies should work closely with the federal granting agency, broadband providers, and application suppliers to ensure that grant-funded systems and equipment will be compatible and interoperable with current and future solutions.

Grant applicants should consult the federal granting agency before submitting requests for ISSI/CSSI and LMR to LTE/5G/6G broadband-related project investments to determine whether certain costs are allowed.

B-13

FY 2024 SAFECOM Guidance on Emergency Communications Grants The P25 Steering Committee published a list of Approved Project 25 Suite of Standards that includes the most recent documents and revisions. Also, the Statement of Project 25 User Needs and the P25 Technology Interest Group’s Capabilities Guide can help determine which standards are applicable to proposed purchases and projects.

Table B-5. Land Mobile Radio Standards and Resources
Organizations Standards and Resources
P25 Compliance
Assessment
Program
P25 CAP is a partnership of DHS, industry, and the emergency response community. It is a formal, independent process for ensuring communications equipment declared by the supplier is P25 compliant and tested against standards with published results. It publishes Compliance Assessment Bulletins on policy, testing, and reporting requirements, and an approved equipment list that may be eligible for grants.

P25 Steering
Committee
P25 Steering Committee is the governing authority of P25 and the sole authority for approving standards proposals, telecommunications system bulletins, and white papers. It works closely with manufacturers to develop and maintain the P25 Suite of Standards that best serves the continually evolving needs of the public safety community. The committee recently produced the Statement of P25 User Needs, which provides high-level explanations of system architecture, features, and functions as defined in P25 standards.

Telecommunications Industry
Association
TIA is accredited by the American National Standards Institute and responsible for publishing the P25 Suite of Standards, approved by the P25 Steering Committee. To date, it has published over 90 documents detailing the specifications, messages, procedures, and tests applicable to the 11 interfaces, multiple feature sets, and functions offered by P25.

Federal
Partnership for
Interoperable
Communications
(FPIC)
FPIC serves as a coordination and advisory body to address technical and operational wireless issues relative to interoperability within the public safety emergency communications community, interfacing with voluntary representatives from federal, state, local, territorial, and tribal organizations. FPIC has developed multiple resources, including the Operational Best Practices for Encryption Key Management, P25 ISSI and CSSI Primer, and Best Practices for Planning and Implementation of P25 ISSI and CSSI, Volumes I and II. These documents are published on the SAFECOM P25 Resources webpage, along with other P25 and LMR encryption resources. 911 Program
Office
The 911 Program Office provides several resources on LMR standards for interconnecting NG911 systems and broadband technologies. These include the NG911 Interstate Playbook, which provides best practices, guidance, and considerations on PSAP interconnectivity with NG911, as well as the 911 Program Office’s NG911/Public Safety Broadband Network Interconnection resource page.

B-14

FY 2024 SAFECOM Guidance on Emergency Communications Grants Nationwide
Public
Safety
Broadband
Network
Applicants interested in investing federal funds in broadband -related infrastructure projects should consult the federal granting agency to understand all requirements and restrictions impacting broadband investments
Grant recipients should consult with any applicable governing bodies and the FirstNet Authority to ensure the project does not conflict with network deployment efforts Recipients may be able to use grant funds for the implementation of alternative broadband technologies and the deployment of fiber optic backhaul networks in rural and unserved areas
Applicants investing in broadband technologies should be aware that the federal government is overseeing the operations and maintenance of the Nationwide Public Safety Broadband Network (NPSBN). The First Responder Network Authority’s (FirstNet Authority) mission is to ensure the building, deployment, and ongoing operation of the NPSBN to provide LTE-based broadband and 5G services and applications to public safety entities. The network is a single, nationwide network architecture consisting of a secure, redundant evolved packet core network (EPC), transport backhaul, and radio access networks (RANs) in the 50 states, five territories, and the District of Columbia.

Applicants should coordinate with the FirstNet Authority in advance of any strategic acquisition of LTE equipment to ensure understanding of all requirements and restrictions impacting broadband investments and that purchases support future service choices. Applicants should also monitor federal actions affecting broadband investments and continue planning and outreach activities (e.g., community education, documenting user needs), as well as work with applicable governing bodies in preparing for and leveraging broadband and other technologies, including:
• Leveraging broadband devices including, but not limited to smartphones, feature phones, tablets, wearables, laptops, ruggedized smartphones, ruggedized tablets, USB modems/dongles, invehicle routers, and Internet of Things devices; • Employing agency-owned and managed broadband deployable equipment, enabling public safety agencies to own and dispatch coverage expansion or capacity enhancement equipment within their jurisdiction;
• Using broadband device accessories that enable efficient and safe public safety operations such as headsets, belt clips, earpieces, remote Bluetooth sensors, and ruggedized cases; • Installing standards-based equipment to provide interworking between LTE and existing LMR systems within their jurisdiction when needed;
• Installing FirstNet SIM/UICC devices to allow public safety users to update existing devices, “Bring Your Own Device” plans, and new devices to operate on public safety prioritized services; • Securing one-time purchase and subscription-based applications for public safety use, which could include, among several other options, enterprise mobility management, mobile Virtual Private Network, identity services, or cloud service tools; and • Developing in-building coverage solutions that help users maintain connections to their mission critical networks and services.

Non-LTE wireless broadband technologies, such as Wi-Fi, WiMAX, and mesh networks, are sometimes used to supplement public safety communications. These solutions, which are either agency-owned or provided by a commercial provider, allow agencies to access voice, data, and video applications. Grant recipients should consider the overall impact of using other wireless broadband technologies given ongoing advancements in FirstNet’s deployment and unique interoperability challenges introduced by each of the various technologies.

Considering these cautions, applicants may be able to use federal grant funds for costs related to the implementation of alternative broadband technologies and the deployment of fiber optic backhaul networks B-15

FY 2024 SAFECOM Guidance on Emergency Communications Grants in rural and unserved areas. Applicants should work closely with the federal granting agency and commercial suppliers and providers to ensure that grant-funded systems and equipment will be compatible and interoperable with current and future solutions. Applicants are encouraged to implement innovative solutions that improve communications capabilities and are consistent with the deployment of the NPSBN.

Table B-6. Broadband Technology Standards and Resources Organizations Standards and Resources
FirstNet
Authority
The Middle Class Tax Relief and Job Creation Act of 2012 created the FirstNet Authority as an independent authority within the National Telecommunications and Information Administration to provide emergency responders with the first nationwide, high-speed, broadband network dedicated to public safety: firstnet.gov.

In establishing requirements for the NPSBN and providing 20 MHz of the upper 700 MHz spectrum to the FirstNet Authority, Congress directed the Authority to ensure the building, operation, and maintenance of a wireless, nationwide interoperable public safety broadband network based on a single national network architecture. The Authority holds the single nationwide FCC license for the 20 MHz of combined Public Safety Broadband Spectrum (758-768 MHz and 788-798 MHz), commonly referred to as Band 14. The FirstNet Authority license also incorporates two one-MHz guard bands at 769 and 799 MHz. Subscription to the NPSBN and use of approved NPSBN devices enables prioritized access to Band 14 spectrum for public safety entities.
3GPP 3GPP is the SDO responsible for development and maintenance of LTE and 5G specifications, though various standards from TIA, ATIS, the Groupe Speciale Mobile Association (GSMA), and the Open Mobile Alliance (OMA) also contribute to broadband functionality and interoperability.

IEEE The 802.11a, 802.11b/g/n, and 802.11ac wireless standards are collectively known as Wi-Fi technologies and developed and maintained by IEEE. The Official IEEE 802.11 Working Group Project Timelines provides status of each networking standard under development, and a link to each effort. IEEE also maintains the WiMAX family of 802.16 standards.

Open
Geospatial
Consortium
(OGC)
OGC is an international non-profit organization committed to making quality open standards for the global geospatial community. These standards are made through a consensus process and are freely available for anyone to use to improve sharing of the world's geospatial data.

B-16

FY 2024 SAFECOM Guidance on Emergency Communications Grants Alerts,
Warnings,
and
Notifications
Grant recipients using funds to cover costs associated with AWN systems should:
• Establish strong governance and engage in collaboration with existing AWN stakeholders
• Ensure well -documented and field -tested plans, policies, and procedures, are executed, evaluated for potential gaps, and adapted to evolving AWN capabilities • Invest in secure and resilient AWN solutions, and incorporate safeguards to ensure the accuracy of messaging
• Consider diversity and inclusion influence accessibility to AWN issuances, as well as how people receive, interpret, and respond to messages • Invest in solutions that enable comprehensive, targeted, specific, and transparent messaging, while minimizing issuance and dissemination delays • Select software or equipment that also supports regional operable and interoperable solutions
If accessing IPAWS, grant recipients should select IPAWS -compatible software that meets the IPAWS minimum critical capabilities87
During an emergency, alerts, warnings, and notifications (AWNs) enable public safety officials to provide the public with information quickly. The Federal Emergency Management Agency (FEMA) Integrated Public Alert and Warning System (IPAWS) is an Internet-based capability that federal, state, local, tribal, and territorial authorities can use to issue alerts, warnings, and notifications to the public. IPAWS is accessed through compatible origination software that meets the Common Alerting Protocol (CAP) 1.2 specification required by IPAWS OPEN. There is no cost to send messages through IPAWS, although there may be costs associated with acquiring compatible alert origination software. IPAWS is not mandatory and does not replace existing methods of alerting, but instead complements existing systems and offers unique added capabilities.

FEMA, in accordance with Executive Order 13407, developed IPAWS to ensure that under all conditions the President of the United States can alert and warn the public via the National Public Warning System, a component of IPAWS. In addition, federal, state, local, tribal, and territorial authorities can utilize IPAWS to issue alerts, warnings, and notifications within their jurisdictions. IPAWS improves public safety notification capabilities by allowing authorized Alerting Authorities to deliver AWNs simultaneously through multiple communications pathways, reaching as many people in the impacted area as possible to save lives and protect property. These communication pathways include:
• Emergency Alert System (EAS) used by authorized Alerting Authorities to send detailed warnings via broadcast, cable, satellite, and wireline radio and television channels; • Wireless Emergency Alerts (WEA) used by authorized Alerting Authorities to geographically target alert messages to mobile devices, generally using cellular broadcast technology; • National Weather Service Dissemination Systems, including the National Oceanic and Atmospheric Administration (NOAA) Weather Radio;
• Unique Alerting Systems, such as siren systems, digital signage, and wall beacons, that have permission to retrieve alerts directly from IPAWS and deliver the alerts to their customer base; and • Future Systems, including computer gaming systems, Internet search engines, social sharing websites, wireless device applications, smart home technologies, and others that are or could use IPAWS.

In order to access IPAWS, grant recipients should select equipment and applications that adhere to both the CAP and IPAWS CAP Profile standards, as well as meet the IPAWS minimum critical capabilities. Alert, warning, and notification software and equipment is developed, produced, and distributed by various vendors.

While the federal government does not endorse any specific vendor, particular software, or equipment, grant recipients should confirm vendors meet IPAWS compatibility, provide training and support services, use basic security measures (e.g., firewalls, anti-virus tools, anti-spyware tools), implement strong access controls 87 IPAWS minimum critical capabilities are available at: emilms.fema.gov/is_0251a/curriculum/1.html.

B-17

FY 2024 SAFECOM Guidance on Emergency Communications Grants requiring authentication of users, and connect to the IPAWS Technical Support Services environment. In addition, recipients should also consider factors affecting continuity of operations, such as support of remote employees, mobile alerting capabilities, and contingent operations in disruptive circumstances.

To maintain AWN issuance proficiencies, agencies sending alerts should conduct trainings, exercises, and tests of systems on a regular basis. Lessons observed from these activities and incidents should be evaluated, documented, and incorporated into future operations. Alerting Authorities are encouraged to pose any questions about WEA delivery to wireless providers serving their area and to report the results of WEA trainings, exercises, and tests to the Federal Communications Commission’s Public Safety and Homeland Security Bureau at [email protected]. Alerting Authorities should also work to minimize issuance delays, from the point of a hazard’s detection to dissemination, by creating message templates, expediting information sharing, identifying and establishing triggers, and avoiding ad-hoc decision making.

For continued access to IPAWS, and to increase user proficiency and reduce alerting errors, the IPAWS Program Management Office requires authorized Alerting Authorities to demonstrate their ability to compose and send a message through the IPAWS-OPEN system at regular intervals. Such demonstration must be performed monthly through generation of a successful message sent to the IPAWS-OPEN Technical Support Services Facility.

Agencies are encouraged to coordinate with regional partners and submit applications that promote regional (e.g., multi-jurisdictional, cross-state, cross-border) collaboration and cost-effective measures. AWN grant funds should focus on eligible public alert and warning activities to include, but not limited to, the purchase, training, exercising, replacement, and maintenance (e.g., annual license, subscription fees, upgrades) of alert, warning, and notification systems, software, and equipment.

Table B-7. AWN Standards and Resources
Organizations Standards and Resources
Common Alerting
Protocol (CAP)
The CAP standard is an open, non-proprietary digital format for exchanging emergency alerts that was developed by Organization for the Advancement of Structured Information Standards (OASIS). CAP allows a consistent alert message to be disseminated simultaneously over many different dissemination mechanisms. The CAP format is compatible with emerging technologies, such as web services, as well as existing formats including the Specific Area Message Encoding used for the NOAA Weather Radio and the EAS, while offering enhanced capabilities including images, maps, and video.

OASIS FEMA worked with OASIS to develop a standardized international technical data profile that defines a specific way of using the standard for the purposes of IPAWS. The CAP standard and supplemental IPAWS CAP Profile ensure compatibility with existing warning systems: oasis-open.org/committees/tc_home.php?wg_abbrev=emergency#tc-tools.

FEMA Integrated
Public Alert and
Warning System
(IPAWS)
The IPAWS Program Management Office (PMO) does not endorse any specific vendor, piece of software, or equipment. Test results for any alert and warning software or equipment tested at the IPAWS Technical Support Services Facility can be made available to assist agencies in making procurement decisions by contacting the IPAWS PMO at [email protected].

Public Safety
Communications
Ten Keys to
Improving
Emergency
Alerts, Warnings
& Notifications
This document provides organizations a series of governance, coordination, planning, cybersecurity, and resiliency best practices to help ensure the successful implementation of their emergency AWN systems and programs. Government and non-government emergency managers, alert originators, system administrators, system operators, and managers can leverage this foundational guidance to deliver timely and actionable messaging during the critical moments of an incident when coordinated communications—down to the second—can save lives.

Essentials of
Alerts, Warnings,
and Notifications
Developed with SAFECOM and NCSWIC, this document provides an overview of AWN fundamentals and emerging trends. Applicants can review this guidance for future considerations, next steps, and examples of successful AWN system projects.

B-18

FY 2024 SAFECOM Guidance on Emergency Communications Grants 911 Systems
Grant recipients using funds to cover costs associated with 911, Enhanced 911 (E911), or Next Generation 911 (NG911) should rely on guidance from the National 911 Program and:
• Discover standards through the NG911 Standards Identification and Review • Use the NG911 Self -Assessment Tool to determine NG911 maturity state • Consider SAFECOM and NCSWIC NG911 transition guidance for next steps • Select Internet Protocol (IP) -enabled, standards -based 911 equipment and software The National 911 Program, administrated by the Department of Transportation National Highway Traffic Safety Administration (NHTSA), provides federal leadership and coordination in supporting and promoting optimal 911 services. This federal home for 911 plays a critical role by coordinating federal efforts that support 911 services in emergency communication centers (ECCs)/public safety answering points (PSAPs) across the nation
NG911 will seamlessly connect ECCs/PSAPs and allow for the transmission and reception of multimedia type data (e.g., text messages, pictures, and video). As NG911 standards continue to evolve, applicants should consult the NG911 Standards Identification and Review to ensure that solutions developed or procured meet industry guidelines and standards. Applicants should consider the following when planning and implementing NG911:
• Strive for IP-enabled NG911 open standards and understand future technology trends to encourage system interoperability and emergency data sharing • Establish collaborative relationships and policy mechanisms that facilitate the ongoing coordination required to plan, deploy, operate, and maintain NG911 systems • Determine the responsible entity(ies) and mechanisms for geospatial data acquisition, reconciliation, and synchronization that are required for NG911 • Establish system access, security controls, and comprehensive cybersecurity plans to protect and manage access to NG911
• Ensure formalized governance models are in place to aid in the transition from legacy 911 to NG911 • Develop and implement sustainable funding models that support the planning, design, deployment, and ongoing operation of NG911
• Develop contract language that ensures the accountability of contractors in building, testing, deploying, operating, and maintaining interoperable and secure NG911 systems • Create a cybersecurity plan that includes voice (both administrative lines and 911) and data systems (e.g., Computer-Aided Dispatch)
Table B-8. NG911 Resources
Resource Description
National 911
Program Office
The National 911 Program also provides the 911 community with a collection of documents, website links and other resources generated by both the program and other industry experts. These vetted resources address topics including emerging emergency communications technologies, wireless deployment, E911 location accuracy, cybersecurity, FirstNet, NG911, governance and 911 legislation, and are located in the Document and Tools section of the National 911 Program’s website.

B-19

FY 2024 SAFECOM Guidance on Emergency Communications Grants Resource Description
NG911 Maturity State
Self-Assessment
Tool
This Self-Assessment Tool helps ECC/PSAP administrators and oversight personnel evaluate a system’s NG911 maturity state and understand the next steps necessary to continue deployment. It contains a detailed, easy-to-use NG911 readiness checklist that establishes common terminology and identifies key milestones to help 911 call centers understand the multi-year NG911 implementation process. The tool is a downloadable Microsoft Excel file, which ensures that collected results are only shared with the agency completing the assessment. The tool translates the answers from ECC/PSAP personnel into one of six maturity states: Legacy, Foundational, Translational, Intermediate, Jurisdictional End State, or National End State. Adopting and sharing the tool’s terminology allows for improved communication—with vendors, industry colleagues, elected officials, and others—at the user’s discretion. 911 Grant Program The Middle Class Tax Relief and Job Creation Act of 2012 authorized $115 million for a targeted 911 Grant Program administered by the Departments of Transportation and Commerce. The grant closed in September 2022. Visit 911.gov/projects/federalfunding for information along with other federal programs that may fund 911 activities. 911 Coronavirus/
COVID-19 Resources
This website provides numerous Coronavirus/COVID-19 resources, including a webinar for telecommunicators and EMS clinicians, as well as guidance on preparing and managing a pandemic response.

National Emergency
Number Association
(NENA) Security for
NG911 Standard
Standards of note for NG911 networks include NENA-STA-010: Detailed Functional and Interface Specification for the NENA i3 Solution; NENA 75-001: NENA Security for NG911 Standard (NG-SEC); NENA 75-502: NG-SEC Audit Checklist; NENA 04- 503: Network/System Access Security Information Document, and NENA-INF-015.1- 2016: NG911 Security Information Document. nena.org.

NG911 Standards
Identification and
Review
Collection of resources from all major standards bodies that address cybersecurity when planning for NG911 deployments: 911.gov/issues/ng911/standards-forenhanced-and-next-generation-911/.

Cyber Risks to
NG911 White Paper
This white paper provides an overview of the cyber risks that NG911 systems may face. It is intended to serve as an informational tool for system administrators to better understand the full scope and range of potential risks, as well as recommend mitigations to these risks. Developed by CISA in conjunction with the Department of Transportation, the document is an introduction to improving the cybersecurity posture of NG911 systems nationwide.

Cyber Risks to
NG911: Telephony
Denial of Service
This fact sheet familiarizes public safety communications partners with Telephony Denial of Service (TDoS) threats to NG911. The document overviews common TDoS attack vectors, highlights real-world TDoS incidents, and suggests best practices to mitigate TDoS impacts.

NG911 IncidentRelated Imagery
Impacts 101
This document provides public safety and emergency communications leadership with considerations for addressing incident-related imagery. It also provides topic-specific guidance and available resources.

FCC CSRIC Reports The Communications Security, Reliability, and Interoperability Council's mission is to provide recommendations to the FCC to ensure, among other things, optimal security and reliability of communications systems, including telecommunications, media, and public safety. For CSRIC reports, visit: fcc.gov/about-fcc/advisorycommittees/communications-security-reliability-and-interoperability.

Geographic
Information System
(GIS) Lifecycle Best
Practices Guide
This guide provides an overview of the GIS lifecycle from planning and implementation to assessing the need to upgrade capabilities. It also highlights best practices for each of the six phases, such as establishing a governance structure, identifying technical requirements for procuring resources, and developing policies and procedures to manage and secure data.

NG911 Interstate
Playbook
This resource provides best practices, guidance, and considerations on PSAP transition to NG911. Compiled by state 911 administrators, the playbook’s four chapters note new methods of connectivity and information sharing among multiple, separate jurisdictions and states.

B-20

FY 2024 SAFECOM Guidance on Emergency Communications Grants Resource Description
NG911/Public Safety
Broadband Network
Information
This 911 Program Office webpage summarizes current efforts to integrate NG911 and Public Safety Broadband Networks: 911.gov/projects/ng911-psbninterconnection/.

Kari’s Law and RAY
BAUM’S Act
Compliance
This webpage provides information on Kari’s Law, which ensures anyone can reach a 911 call center when dialing from a multi-line telephone system, as well as the RAY BAUM’S Act, which emphasizes the importance of making dispatchable location information from all 911 calls available to PSAPs. Information includes tools for the 911 Community, such as an overview of legislation, detailed lists of state laws and FCC rules, compliance rules and deadlines, and an interactive checklist towards compliance.

NG911 Procurement
Guidance
The National 911 Project has developed NG911 Procurement Guidance for PSAP managers to follow as they upgrade outdated systems. The guidance document assists in the areas of contract negotiation, establishment of scope of work documents, and creation of service for the NG911 system once upgrades are complete. In addition, the document defines a set of important terms used in contract procurements, provides a checklist of considerations while negotiating the Statement of Work, and lists suggestions for ensuring that critical security procedures are established and managed.

The “State of 911”
Webinar Series
Pending 911 legislation may provide “a once in a career” opportunity to plan, prepare, and take advantage of federal grant funding to implement NG911. This webinar series shares information to help states prepare for possible future federal grant funding:

State of 911 Webinars.

The Successful
NG911 Transition: A
Case Study of the
California Office of
Emergency Services
This case study provides insights and guidance directly from the team leading California’s NG911 upgrades at 437 PSAPs. In addition to insights, best practices, and guidance, this case study also provides helpful resources.

The California
Statewide NG911
Geographic
Information System
A Tale of Two
Approaches:

Mandatory vs.

Voluntary
Implementations of
NG911
This document highlights California’s process of implementing a statewide GIS system. Paired with the GIS Lifecycle Best Practices Guide for NG911, it provides users with helpful tips for navigating the GIS lifecycle, including planning, governance, funding, and security considerations.

This document tackles some common challenges, opportunities, and considerations for both mandatory and voluntary deployments of NG911.

Utilizing
Partnerships to Make
NG911 Possible
This document lists a variety of resources inside and outside government agencies that should be tapped to ensure proper planning, procurement, and implementation of NG911.
911 Cybersecurity
Resource Hub
This webpage contains SAFECOM and the National Council of Statewide Interoperability Coordinators resources for ECCs, including resources for reporting a cyber incident, real world use cases, planning: response and recovery, cybersecurity awareness and training, protecting networks from cyberattacks, design and implementation, and risk assessments.

B-21

FY 2024 SAFECOM Guidance on Emergency Communications Grants Data Exchange
and
Information
Sharing
Environments
Agencies should perform an evaluation of who the organization most often communicates with, and what types of information are commonly exchanged Grant recipients using federal funds for data exchange solutions should ensure the solutions comply with OASIS EDXL suite of data messaging standards and NIEM framework
For any grant funding software -based patient tracking products, the product is strongly encouraged to comply with OASIS EDXL -TEP, Bi -directional Transformation of OASIS EDXL -TEP (Tracking of Emergency Patients) v1.1, and HL7 v2.7.1 Specification Version
Data exchange and information sharing solutions are as fundamental as a digital data “snapshot” transferred over electronic media, or as tailored as custom-interface applications that allow proprietary applications to be linked. Challenges to effective information exchange include increasing types of data being exchanged, such as geographic information systems, evacuee or patient tracking, biometrics, accident and crash telematics, Computer-Aided Dispatch, Automatic Vehicle Location, and more. To communicate seamlessly with the increasingly interconnected systems of the broader community, agencies should consider standards-based information exchange models.

The National Information Exchange Model (NIEM) is a framework for exchanging information that provides common terminology for users and a repeatable, reusable process for developing information exchange requirements. NIEM was established by the Departments of Justice and Homeland Security in 2005 to unite stakeholders from federal, state, local, tribal, and territorial governments and the private sector, to develop and deploy a national model for information sharing and the organizational structure to govern it. Today, all 50 states and many federal agencies are using or considering NIEM, including adoption by the Departments of Agriculture, Defense, Health and Human Services, and Transportation. NIEM allows disparate systems to share, exchange, accept, and translate information in an efficient manner that all users can understand.

In addition to the NIEM framework, agencies should reference the Global Reference Architecture (GRA) and the OASIS Emergency Data eXchange Language (EDXL) suite of data messaging standards.

Applicable standards include the CAP; distribution element; hospital availability exchange; resources messaging; reference information model; situation reporting; and tracking emergency patients. • Global Reference Architecture provides guidance for agencies to develop and establish a serviceoriented architecture for public safety information sharing. The GRA incorporates and reuses appropriate subsets of the NIEM, as well as other models such as the Global Federated Identity and Privilege Management (GFIPM) sponsored by the Departments of Justice and Homeland Security. The GRA provides practitioners with overarching guidance that demonstrates how federal initiatives, including NIEM and GFIPM, work together and how to accelerate the planning process. Agencies can use this GRA tool to develop a well-conceived, formal approach to designing information sharing solutions and systems. A key benefit of a reference architecture is it helps promote consistent thinking and approaches among the people who use it, even if they have not shared information with each other.
• OASIS EDXL suite of data messaging standards facilitates information sharing among public safety agencies. Grant-funded systems, developmental activities, or services related to emergency response information sharing should comply with the following OASIS and HL-7 standards:
"OASIS EDXL-TEP" and Bi-directional Transformation of OASIS EDXL-TEP (Tracking of Emergency Patients) v1.1 and HL7 v2.7.1 Specification Version and OASIS EDXL suite of data messaging standards. Compliance should include the following OASIS EDXL standards:
o Common Alerting Protocol, version 1.2 or latest version o Distribution Element (DE), version 1.0 or latest version o Hospital AVailability Exchange (HAVE), version 1.0 or latest version B-22

FY 2024 SAFECOM Guidance on Emergency Communications Grants o Resource Messaging (RM) standards, version 1.0 or latest version In efforts to develop an Information Sharing Framework (ISF) to support public safety telecommunications, the SAFECOM and National Council of Statewide Interoperability Coordinators (NCSWIC) established the Information Sharing Framework Task Force comprised of information technology and communications subject matter experts from public safety agencies across the country. This task force has developed an ISF to ensure effectiveness of new products and technologies as agencies transition to mobile and fully interconnected environments.

To begin using the functional components of the ISF integration layer, public safety agencies should ask the following high-level operational questions:
• What is the content?
• What is the data source?
• Who owns the data?
• Who needs it?
• Over what path?
• Over what application?
A few of the widely used exchange models are provided as part of this appendix; however, an evaluation of who the organization most often communicates with, and what types of information are commonly exchanged, is recommended in selecting an ideal data exchange and information sharing solution. For more information on how to develop and implement an ISF and customize it for various use cases, see the SAFECOM/NCSWIC Approach for Developing an Interoperable Information Sharing Framework.

Table B-9. Data Exchange Standards and Resources
Organizations Standards and Resources
NIEM Applicants are encouraged to reference the NIEM website to develop a greater understanding of data exchange functions and processes.

GRA Many Department of Justice grant solicitations require its grant recipients to comply with the GRA, specifically the Global Standards Package, which describes a full information sharing technology standards implementation suite that addresses data standardization, messaging architecture, security, and privacy requirements. For additional information, including technical assistance and training opportunities, visit the Office of Justice Programs website at: https://bja.ojp.gov/program/it/nationalinitiatives/gra.

OASIS OASIS Emergency Management Technical Committee creates incident- and emergency-related standards for data interoperability: Common Alerting Protocol; EDXL – Distribution Element; EDXL – Resource Messaging; and EDXL – Tracking of Emergency Clients. oasis-open.org.

SAFECOM and
NCSWIC Information
Sharing Framework
Task Force
SAFECOM and NCSWIC, in coordination with CISA and the Johns Hopkins Applied Physics Laboratory, developed an ISF to help responders to discover, access, and consume any relevant information on a need-to-know basis, regardless of jurisdiction, affiliation, or location. cisa.gov/safecom/technology.

Information Sharing
Assessment Tool
The Information Sharing Assessment Tool, developed by DHS with the guidance of local, state, and federal public safety practitioners, is a tool for public safety officials and first responders to identify their own information sharing capabilities and gaps. It aims to empower communities to develop an action plan to address their most pressing information-sharing gaps; publicize their progress and achievements; and facilitate inter-agency and cross-discipline information sharing. 911 DataPath This effort is a result of a formal recommendation by the FCC's TFOPA and includes a Strategic Plan and Administrative Dataset for Decision Making: 911.gov/projects/911- datapath/.

B-23

FY 2024 SAFECOM Guidance on Emergency Communications Grants Appendix C – Emergency Communications Resources
This appendix provides links to references in the SAFECOM Guidance and additional resources to help grant applicants develop emergency communications projects and complete federal grant applications. Visit the SAFECOM website (cisa.gov/safecom) for additional resources. 911 / Next Generation 911 (NG911)
• See Appendix B in the SAFECOM Guidance
• National 911 Program Website: 911.gov
o 911 DataPath: 911.gov/projects/911-datapath/
o 911 Grant Program: 911.gov/projects/federal-funding
o NG911 Standards Identification and Review: 911.gov/docs-and-tools/#sort=date o NG911 Self-Assessment Tool: 911.gov/projects/ng911-self-assessment-tool/ o Webinars: 911.gov/webinars/
o Federal Funding Programs for 911: 911.gov/projects/federal-funding • National Association of State 911 Administrators: nasna911.org and nasna911.org/contact-911 • National Emergency Number Association: nena.org
Cybersecurity
• See Appendix B in the SAFECOM Guidance
• NIST Cybersecurity Framework 2.0: nist.gov/cyberframework • CISA Cyber Resource Hub: cisa.gov/cyber-resource-hub
• CISA Public Safety Cybersecurity Website: cisa.gov/public-safety-cybersecurity Department of Justice (DOJ)
• Law Enforcement Tech Guide for Communications Interoperability: cisa.gov/safecom/planning-resources Cybersecurity and Infrastructure Security Agency (CISA) • CISA Website: cisa.gov
• Contact Information: [email protected]
• 911 Cybersecurity Resource Hub: SAFECOM/National Council of Statewide Interoperability Coordinators resources for Emergency Communications Centers: cisa.gov/911-cybersecurity-resource-hub • Identity, Credential, and Access Management Resources and Trustmark Framework: cisa.gov/safecom/icam • National Emergency Communications Plan: cisa.gov/national-emergency-communications-plan • National Interoperability Field Operations Guide: cisa.gov/safecom/field-operations-guides • Pandemic Guidelines for 911 Centers: cisa.gov/resources-tools/programs/emergency-communicationspandemic-guidance • Priority Services Programs: cisa.gov/resources-tools/programs/priority-telecommunications-services • Shared Communication Systems and Infrastructure: cisa.gov/resources-tools/services/shared-communicationsystems-and-infrastructure • Technical Assistance and Training Catalogs: cisa.gov/safecom/ictapscip-resource, dhs.gov/training-technicalassistance, and cisa.gov/resources-tools/resources/cisa-services-catalog • Transition to Advanced Encryption Standard: cisa.gov/sites/default/files/2023-10/23_0918_fpic_AESTransition-WhitePaper_Final_508C_23_1023.pdf C-1

FY 2024 SAFECOM Guidance on Emergency Communications Grants Federal Communications Commission (FCC)
• FCC Public Safety and Homeland Security Bureau: fcc.gov/public-safety-and-homeland-security • Contact Information: [email protected]
• FCC Fee Filing Guide for the Wireless Telecommunications Bureau: fcc.gov/licensingdatabases/fees/application-processing-fees • FCC Narrowbanding Website: fcc.gov/narrowbanding-overview • Communications Security Reliability and Interoperability Council: fcc.gov/about-fcc/advisorycommittees/communications-security-reliability-and-interoperability • Task Force on Optimal Public Safety Answering Point Architecture: fcc.gov/about-fcc/advisorycommittees/general/task-force-optimal-public-safety-answering-point • FCC 700 MHz Public Safety Broadband Spectrum Guidance: fcc.gov/700-mhz-public-safety-narrowbandspectrum • FCC 800 MHz Transition: fcc.gov/general/800-mhz-spectrum • Narrowbanding Guidance
o SAFECOM Guidance, Section 3.3
o Guidance for licensees for FCC’s narrowband operation requirement: fcc.gov/narrowbanding-overview o Information on Frequency Coordinators: fcc.gov/general/public-safety-frequency-coordinators o Contact Information: [email protected]
• Ending 9-1-1 Fee Diversion Now Strike Force (911 Strike Force) Report: fcc.gov/911strikeforce • 911 Fee Reports and Reporting: fcc.gov/general/911-fee-reports Federal Emergency Management Agency (FEMA)
• FEMA Grants Website: fema.gov/grants
o Authorized Equipment List: fema.gov/grants/tools/authorized-equipment-list o Information Bulletins: fema.gov/grants/preparedness/about/informational-bulletins o Preparedness Grants Manual: fema.gov/grants/preparedness/manual • Comprehensive Preparedness Guide 201: fema.gov/emergency-managers/national-preparedness/goal/riskcapability-assessment • Environmental Planning and Historical Preservation (EHP): SAFECOM Guidance, Section 4.5 - Additional Requirements and Recommendations for Equipment Purchases o EHP guidance for DHS/FEMA grant applications: fema.gov/grants/guidance-tools/environmental-historic o For questions on EHP for DHS/FEMA grants, contact: [email protected] o For information on federal EHP requirements, see the Council on Environmental Quality Regulations, 40 CFR Part 1500-1508: energy.gov/sites/prod/files/NEPA-40CFR1500_1508.pdf • Integrated Public Alert and Warning System (IPAWS) Program Office: fema.gov/emergencymanagers/practitioners/integrated-public-alert-warning-system o Alerting Authorities and State, Local, Tribal, and Territorial Users: fema.gov/emergencymanagers/practitioners/integrated-public-alert-warning-system o Common Alerting Protocol: fema.gov/emergency-managers/practitioners/integrated-public-alertwarning-system/technology-developers/common-alerting-protocol o Information Materials: fema.gov/emergency-managers/practitioners/integrated-public-alert-warning-system o IPAWS Best Practices: fema.gov/sites/default/files/documents/fema_ipaws-best-practices-guide.pdf o IPAWS Components: fema.gov/emergency-managers/practitioners/integrated-public-alert-warning-system o IPAWS Modernization Act of 2015: congress.gov/bill/114th-congress/senate-bill/1180 o IPAWS Program Planning Toolkit: fema.gov/emergency-managers/practitioners/integrated-public-alertwarning-system/public-safety-officials/toolkit • Presidential Policy Directive–8: dhs.gov/presidential-policy-directive-8-national-preparedness and fema.gov/emergency-managers/national-preparedness
• National Incident Management System (NIMS): fema.gov/emergency-managers/nims C-2

FY 2024 SAFECOM Guidance on Emergency Communications Grants o NIMS National Standard Curriculum Training Development Guidance: fema.gov/emergencymanagers/nims/implementation-training • National Preparedness Goal: fema.gov/emergency-managers/national-preparedness/goal • National Preparedness System: fema.gov/emergency-managers/national-preparedness/system • National Risk Index: fema.gov/flood-maps/products-tools/national-risk-index • Stakeholder Preparedness Review: fema.gov/emergency-managers/national-preparedness/goal/riskcapability-assessment • State Administrative Agency Contact List: fema.gov/grants/preparedness/about/state-administrative-agencycontacts • State Homeland Security Director Office Information: dhs.gov/state-homeland-security-and-emergencyservices • Threat and Hazard Identification and Risk Assessment: fema.gov/emergency-managers/nationalpreparedness/goal/risk-capability-assessment • Training: fema.gov/emergency-managers/national-preparedness/training and firstrespondertraining.gov/frts/ o Homeland Security Exercise and Evaluation Program: fema.gov/emergency-managers/nationalpreparedness/exercises/hseep o Incident Command System Resource Center: training.fema.gov/emiweb/is/icsresource Federal Grants Information and Listings
• Office of Management and Budget Circulars, Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards: govinfo.gov/app/details/CFR-2014-title2-vol1/CFR-2014-title2- vol1-part200
• Grants.gov Website: grants.gov
• FEMA Grants: fema.gov/grants
• SAFECOM compiled List of Federal Financial Assistance Programs Funding Emergency Communications:
cisa.gov/safecom/emergency-comms-grants-list
First Responder Network Authority (FirstNet Authority) / Nationwide Public Safety Broadband Network • FirstNet Authority Website: firstnet.gov
• FirstNet Authority Contact Information: [email protected] • NTIA Public Safety Website: ntia.doc.gov/category/public-safety • Middle Class Tax Relief and Job Creation Act: govinfo.gov/content/pkg/PLAW-112publ96/pdf/PLAW112publ96.pdf SAFECOM / National Council of Statewide Interoperability Coordinators (NCSWIC) • Best Practices for Planning and Implementation of Project 25 Inter-RF Subsystem (ISSI) and Console Subsystem (CSSI), Volumes I and II: cisa.gov/resources-tools/resources/p25-resources • Contingency Considerations When Facing Reductions in Emergency Communications Budgets:
cisa.gov/sites/default/files/2023-02/22_0302_contingency_planning_fact_sheet_final_508.pdf • Contingency Planning Guide for Emergency Communications Funding: cisa.gov/sites/default/files/2023- 02/22_0302_contingency_planning_guide_for_emergency_communcations_funding_final_508.pdf • Emergency Communications System Lifecycle Planning Guide: cisa.gov/sites/default/files/2023- 02/Emergency%20Communications%20System%20Life%20Cycle%20Planning%20Guide%20August%202 011%20508c.pdf
• Governance Guide for State, Local, Tribal, and Territorial Emergency Communications Officials:
cisa.gov/sites/default/files/publications/2018%2520Emergency%2520Communications%2520Governance% 2520Guide%2520for%2520State%252C%2520Local%252C%2520Tribal%2520and%2520Territorial%2520 Officials.pdf
• Interoperability Planning for Wireless Broadband:
cisa.gov/sites/default/files/publications/interoperability_planning_wireless_broadband_web_111711.pdf C-3

FY 2024 SAFECOM Guidance on Emergency Communications Grants • The Funding and the Future of P25 Video: cisa.gov/resources-tools/resources/p25 • Funding and Sustaining LMR: Materials for Decisions-Makers: cisa.gov/safecom/funding • Funding Mechanisms Guide for Public Safety Communications: cisa.gov/sites/default/files/2023- 02/21_0621_funding_mechanisms_guide_final_508.pdf
• NG911 Self-Assessment Tool: 911.gov/projects/ng911-self-assessment-tool/ • Operational Best Practices for Encryption Key Management: cisa.gov/sites/default/files/publications/08-19- 2020_Operational-Best-Practices-for-Encryption-Key-Mgmt_508c.pdf • Project 25 ISSI and CSSI Primer: cisa.gov/sites/default/files/publications/20190130%2520ISSICSSI%2520Primer%2520FINAL%2520508C.pdf • Public Safety Communications Dependencies on Non-Agency Infrastructure and Services:
cisa.gov/sites/default/files/publications/Public%2520Safety%2520Communications%2520Dependencies%25 20on%2520Non-Agency%2520Infrastructure%2520and%2520Services_10-21-20_508c.pdf • Public Safety Communications Evolution Brochure:
cisa.gov/sites/default/files/publications/Public_Safety_Communications_Evolution_FINAL_01222019_508C.pdf • Public Safety Communications: Ten Keys to Improving Emergency Alerts, Warnings & Notifications:
cisa.gov/sites/default/files/publications/safecom-ncswic_ten_keys_to_improving_awns_4.26.19_- _final_section_508_compliant.pdf
• Public Safety Communications Resiliency: Ten Keys to Obtaining a Resilient Local Access Network:
cisa.gov/sites/default/files/publications/07202017_10_Keys_to_Public_Safety_Network_Resiliency_010418 _FINAL508C.pdf
• Public Safety Communications Network Resiliency Self-Assessment Guidebook:
cisa.gov/sites/default/files/publications/DHS%2520ECD%2520Public%2520Safety%2520Communications% 2520Network%2520Resiliency%2520Self-Assessment%2520Guidebook_11.29.18%2520-%2520FINAL.pdf • Regional Interoperability Communications Plan Template: cisa.gov/sites/default/files/2023- 02/Regional%20Interoperable%20Communications%20Plan%20%28RICP%29%20Template.pdf • SAFECOM Interoperability Continuum:
cisa.gov/sites/default/files/publications/21_0615_cisa_safecom_interoperability_continuum_brochure_final.pdf • SAFECOM Member List: cisa.gov/safecom/membership
• Statewide Interoperability Coordinator (SWIC): See SAFECOM Guidance, Sections 3.2 and 4.2 • Statewide Communication Interoperability Plan (SCIP): See SAFECOM Guidance, Sections 2.2 and 4.2 o CISA SCIP Website: cisa.gov/resources-tools/services/statewide-communication-interoperability-plansworkshops o To find your SCIP, please contact your SWIC or SCIP Point of Contact. SWIC contact information can be found on the NCSWIC membership page: cisa.gov/safecom/ncswic-membership Standards
• SAFECOM Guidance on Technology and Equipment Standards: SAFECOM Guidance, Section 4.5 and Appendix B
• Association of Public-Safety Communications Officials standards: apcointl.org/services/standards/ o Project 43: Broadband Implications for the PSAP: apcointl.org/technology/next-generation-9-1- 1/project-43-broadband-implications-for-the-psap/
• Data Exchange and Information Sharing Environment: See Appendix B in the SAFECOM Guidance o National Information Exchange Model: niem.gov
o OASIS, Standards for Data-Related Investments: oasis-open.org o Information Sharing Assessment Tool: dhs.gov/science-and-technology/isat • Long-term evolution (LTE) for Public Safety Broadband: See Appendix B in the SAFECOM Guidance o 3GPP RAN5 Mobile Terminal Conformance Testing: 3gpp.org/3gpp-groups/radio-access-networksran/ran-wg5 • NENA i3 Solution – Stage 3: nena.org/page/standards
• NIST List of Certified Devices: nist.gov/ctl/pscr/process-document-nist-list-certified-devices C-4

FY 2024 SAFECOM Guidance on Emergency Communications Grants • Project 25 (P25) Standards for Land Mobile Radio:
standards.tiaonline.org/standards/technology/project_25/index.cfm o P25 Technology Interest Group: project25.org
o P25 Compliance Assessment Program: dhs.gov/science-and-technology/p25-cap o P25 Compliance Assessment Program list of approved radio equipment: dhs.gov/science-andtechnology/approved-grant-eligible-equipment o Statement of P25 User Needs (SPUN): cisa.gov/resources-tools/resources/p25-resources C-5

FY 2024 SAFECOM Guidance on Emergency Communications Grants Appendix D – Compliance Requirements for DHS Grants
This appendix provides guidance for Department of Homeland Security (DHS) and Federal Emergency Management Agency (FEMA) preparedness grants. Recipients using DHS/FEMA funds for emergency communications activities must comply with the SAFECOM Guidance on Emergency Communications Grants (SAFECOM Guidance) in accordance with DHS Standard Terms and Conditions. Table D-1 provides a list of requirements for DHS/FEMA grants. For additional information, see relevant sections within the SAFECOM Guidance. DHS/FEMA recipients should also refer to the specific Notice of Funding Opportunity or the Preparedness Grants Manual for all programmatic requirements that apply (fema.gov/grants).

Table D-1. SAFECOM Guidance Compliance Instructions for DHS Recipients Topics Requirements
National and
Statewide Plan
Alignment
Sections 2.2, 2.5,

3.1 • Describe in applications how proposed projects will support national goals and objectives in the National Emergency Communications Plan (NECP).
• Describe in applications how proposed projects will align with your state or territory’s Statewide Communication Interoperability Plan (SCIP) goals and objectives. To find your SCIP, contact your Statewide Interoperability Coordinator (SWIC) or SCIP Point of Contact. Contact information for SWICs can be found on the NCSWIC membership page:
cisa.gov/safecom/ncswic-membership.
• Explain how proposed projects address or support communications resiliency.

Project
Coordination
Sections 2.1, 2.2,

2.4, 3.2, 3.3
• List all participants involved in project planning to demonstrate engagement with the whole community in accordance with Presidential Policy Directive-8 and the NECP. • Develop regional, multi-jurisdictional, multi-disciplinary, and cross-border projects to promote greater interoperability across agencies, pool grant resources, facilitate assetsharing, and eliminate duplicate purchases. • Designate a full-time SWIC who has the authority and resources to actively improve interoperability with emergency management and response agencies across all levels of government, to include establishing statewide plans, policies, and procedures, and coordinating decisions on communications investments funded through federal grants. • Coordinate proposals with statewide emergency communications governance bodies and leaders (e.g., State Interoperability Executive Committee, SWIC, 911 Administrator).

National
Incident
Management
System (NIMS)
Sections 3.4, 4.3,

4.4 • NIMS Implementation Objectives clarify the specific NIMS implementation criteria to be eligible for FEMA preparedness grants (see: fema.gov/emergencymanagers/nims/implementation-training). Some grants may have additional NIMS training or personnel credentialing criteria (see the applicable Notice of Funding Opportunity for details).
• States, territories, and tribal grant recipients report NIMS implementation annually in the Stakeholder Preparedness Review (SPR). States/territories and tribal grant recipients must submit their annual SPR through the Unified Reporting Tool (URT) and email a copy of the URT submission to their respective DHS/FEMA Regional Federal Preparedness Coordinator and copy [email protected]. SPR submissions are due no later than December 31 each year.

Spectrum
Licensing
Section 3.3
• If a project requires a new spectrum license, consult the appropriate statewide coordinator (e.g., SWIC), the Federal Communications Commission, and/or the FirstNet Authority to ensure the recipient will have authority to operate in the desired spectrum. Spectrum consultation should begin prior to application submission or during early phases of an approved project. A spectrum license must be in place before associated equipment can be purchased.

D-1

FY 2024 SAFECOM Guidance on Emergency Communications Grants Topics Requirements
Planning and
Organization
Sections 2.2, 3.4,

4.2 • Update and submit the SPR and Threat and Hazard Identification and Risk Assessment (THIRA). The Comprehensive Preparedness Guide 201 provides a three-step process for conducting a THIRA/SPR. Follow THIRA/SPR submission instructions in program guidance.
• Complete and submit the Nationwide Cybersecurity Review to benchmark and measure progress towards improving cybersecurity posture.

Training
Sections 2.3, 4.3
• Describe in applications how training projects support the NIMS Training Program, are consistent with NECP priorities, and address gaps identified through your state or territory’s SCIP, After-Action Reports, and other assessments.

Exercises
Section 2.3, 4.4
• Include participants from multiple jurisdictions, disciplines, and levels of government and private sector entities, as appropriate. For additional FEMA exercise guidance, see fema.gov/emergency-managers/national-preparedness/exercises. • Manage and execute exercises in accordance with the Homeland Security Exercise and Evaluation Program.

Equipment
Section 4.5
• Ensure equipment procurements comply with the covered telecommunications restrictions outlined in the John S. McCain National Defense Authorization Act of 2019 as outlined in FEMA Policy #405-143-1.

Land Mobile
Radio (LMR)
Equipment
Sections 2.5, 4.5,
5, Appendix B
• LMR systems are designed to meet public safety’s unique mission critical requirements and support time-sensitive, lifesaving tasks, including rapid voice call-setup, group calling capabilities, high-quality audio, and guaranteed priority access to the end-user. The public safety community is expected to follow a multi-path approach to network infrastructure use and development of advanced technologies. Recipients should sustain current LMR capabilities during deployment of advanced technologies in accordance with the NECP. • Select Project 25 (P25) standards-based equipment for LMR mission critical voice communications. See the DHS Authorized Equipment List to determine allowable equipment types for DHS/FEMA preparedness grants, and the P25 Compliance Assessment Program Approved Equipment List. If proposal includes any non-P25 LMR equipment, recipients must apply for prior approval.

Next Generation
911 (NG911)
Systems
Sections 2.5, 4.5,
5, Appendix B
• NG911 is an Internet Protocol (IP)-based system that allows digital information (e.g., voice, photos, videos, text messages) to flow seamlessly from the public through the 911 network to emergency responders. If proposal includes NG911 systems, review the NG911 Standards Identification and Review and select IP-enabled 911 open standards equipment and software. For additional information, consult the National 911 Program Office at 911.gov.

Public Safety
Broadband
Sections 2.5, 4.5,
5, Appendix B
• Consult with applicable governing bodies and leaders for the latest guidance from the FirstNet Authority, planning for public safety broadband network activities, and identifying the authority to operate on public safety spectrum. For additional information, refer to firstnet.gov.

Alerts,
Warnings, and
Notifications
Sections 2.5, 4.5,
5, Appendix B
• The Integrated Public Alert and Warning System (IPAWS) is a modernization and integration of the nation’s alert and warning infrastructure. Federal, state, local, tribal, and territorial Alerting Authorities can use IPAWS to alert, warn, and notify the public with public safety information simultaneously via the Emergency Alert System, Wireless Emergency Alerts, the National Oceanic and Atmospheric Administration Weather Radio, and other public alerting systems from a single interface. If proposal includes alerts and warnings, review IPAWS informational materials and Common Alerting Protocol standard at fema.gov/emergency-managers/practitioners/integrated-public-alert-warningsystem/technology-developers/common-alerting-protocol.

D-2

CALIFORNIA GOVERNOR’S OFFICE OF EMERGENCY SERVICES
FY 2024 State Homeland Security Grant Program
Grant Number #2024-0088 CalOES ID# 107-00000
Subgrantee name: ____________________________________ Project: _________________

REQUEST FOR SOLE SOURCE PROCUREMENT AUTHORIZATION

1. Project name: _________________________ Project Budget: $__________________

2. Describe the project and/or activity that will be provided by the proposed sole source vendor/contractor.

3. Describe your organization’s standard procedures when sole source contracting is considered, including the conditions under which a sole source contract is allowed, and any other applicable criteria (i.e. approval requirements, monetary thresholds, etc.).

4. Indicate which of the following circumstances resulted in your organization’s need to enter into a sole source contract.
a. Item/service is only available from one source (Describe the process used to make that determination. Please provide details.)
b. A public urgency or emergency will not permit a delay resulting from competitive solicitation. According to the US Department of Homeland Security/FEMA, “Time constraints will not be considered a factor if the subgrantee has not sought competitive bids in a timely manner.” (Describe the urgency or emergency. Please provide details) c. After solicitation of a number of sources, competition was determined inadequate. (Describe the solicitation process that determined competition was inadequate. Please provide details, and attach any relevant supporting material, Request for Proposal, etc.)

5. Did your organization confirm that the contractor/vendor is not debarred or suspended?

6. Will your organization be able to complete all activities associated with the sole source contract by the end of the grant performance period?

7. Has your organization determined the costs are reasonable?

8. Please attach a copy of the cost benefit analysis prepared for this procurement.

Submitted by_________________________ __________________________ Date:_____________ (Name) (Signature)

City Council Staff Report
Department: FIRE SERVICES August 12, 2025
To: Mayor and City Council
From: Greg Chastain, Fire Chief
By:

Subject: Authorization to Execute an Agreement Between the City of Dinuba and Valley Regional Occupational Program (GC)
RECOMMENDATION:

Council to Authorize the City Manager to execute an agreement between the City of Dinuba and Valley Regional Occupational Program (VROP) to provide emergency medical technician (EMT) field training.

EXECUTIVE SUMMARY:

The fire department proposes to renew an agreement with VROP to provide EMT students with the field training opportunities required to obtain their EMT licenses.

OUTSTANDING ISSUES:

DISCUSSION:

The State of California requires EMT students to complete 24 hours of supervised clinical experience, which must include a minimum of 10 patient contacts. During these contacts, students perform patient assessments and practice EMT skills. The EMT field training programs allow fire department staff to observe potential employment candidates and provide students with an opportunity to experience what it is like to work at Dinuba Fire Department. City Council is asked to approve the agreement and authorize the City Manager to sign it. The agreement is included herein as Attachment 'A'.

FISCAL IMPACT:

None.

PUBLIC HEARING:

ATTACHMENTS:

1. Attachment 'A'

AGREEMENTBETWEEN

VALLEYREGIONALOCCUPATIONALPROGRAM
AND

CITYOFDINUBA
This is an Agreement between Valley Regional Occupational Program (hereinafter referred to as "Valley ROP")andtheCityofDinuba(hereinafterreferredtoas "City") (collectively reference herein as “the Parties”) and is effective as ofJuly 1, 2025

RECITALS
ValleyROP conducts anEmergency Medical Technician-Basic (EMT-B)TrainingProgram,which provides pre-hospital, clinical, and field training forstudents desiring to become EMT-B in accordance with the provisions of California laws and regulations.

ValleyROPis desirousthat itsstudents participating in anEMT-Bfield experiencewithCity; and City has field facilities for furnishing this field experience to the students participating in the Valley ROP's programand is desirous ofmaking itsfield facilities available for this purpose.

AGREEMENT
NOW, THEREFORE, the parties agree as follows:

1. City agreesto provide a supervised program offield experience to the selectedEMT-Bstudentsin accordancewith the terms and conditionsstated in this Agreement. Individualssupervising the field experience shall bemutually acceptable to the parties.

2. The period oftime for eachstudent'sfieldexperience atCityshall bemutually agreed upon between City and Valley ROP prior to the beginning of each student's field experience. Reasonable extensions may be agreed to by the partiesif a particularstudent requires additional experience.

3. The number ofstudentsto participate in the field experience at City at anygiventime shall be mutuallyagreeduponbyValleyROPandCitypriortothebeginningofthefieldexperienceprogram, andmay bemodified fromtime to time bymutual agreement upon the request of either party.

4. CitymayrequireValleyROP towithdrawanystudentfromCity'sfieldexperiencetraining program whoCitydeterminesisnotperformingsatisfactorily,orwhorefusestofollowCity's administrative and patient care policies, procedures,rules and regulations.

5. Valley ROP shall notify studentsthat the studentsshall be responsible for:
a. Followingtheadministrativeandpatientcarepolicies,procedures,rulesandregulationsof City;
b. Acquiring and using the necessary and appropriate uniforms and personal protective equipment when not provided byCity;
Docusign Envelope ID: 05A242CE-38E6-4FC1-B0BD-0AEFE529B7BE

2 c. Arrangingfortheirowntransportationandpersonallivingaccommodationsandcostswhen not provided byCity; and
d. Adhering to program requirements concerning obtaining the necessary health screening.

ValleyROPwillprovidethisinformationtotheCity.

6. City shall maintain in its normal course of business complete attendance and progress records and reports on each student's performance and shall provide an evaluationfor each studenttoValleyROPonformsprovidedbyValley ROP. All student records shall be maintained by City in a secure location preventing access by unauthorized individuals.

City shall not forward to any other person or agency a student record without written consent of the parent/guardian, student over the age of 18, or Valley ROP.

7. City shall, upon reasonable request, permit ValleyROP and/or appropriate governmental agencies charged with the responsibility of accrediting or approving the EMT-B training program to inspect the field facilities,services available forfield experience,student'srecords, and such other materials which pertain to the field training program.

8. It is expressly agreed and understood by ValleyROP and Citythatthestudentsunderthisprogram areinattendanceatCity for educational purposes.

9. In accordance with EducationCode section 45125.1,City shall conduct criminal background checks ofits employees having contact with ValleyROP students. Upon receipt ofthe background checkCity will certify to ValleyROP that anyCity employee having regular contact with students has not been convicted of a violent orseriousfelony as defined by statute.

10. City agrees to submit a written accident report to Valley ROP within twenty-four (24) hours of an accident or incident when a student has suffered an injury, injured another individual, or has been involved in an activity requiring notification oflaw enforcement or emergency personnel.

11. City shall not discriminate on the basis ofrace,religion,sex, national origin, age, handicap, or sexual orientation in the operation of the field training program.

12. City will ensure that allstaffmembers working with ValleyROP students are familiar with and agree to adhere to child abuse and/ormissing children reporting obligations and procedures under California law, including but not limited to, EducationCode section 49370 and PenalCode sections 1166 et seq.

13. It is agreed and understood that the partiesto this Agreement are independent contractors, and that neitheristhe employee or employer ofthe other and that the employee of one are not the employees of the other.

14. ValleyROP shalltake out andmaintain during all periodsthisAgreementisin effect general liability insurance and property insurance naming City as additional insured, indemnifying said additional insuredsfrom and against any and allloss or damage, and from any and all liability for any loss or damage, and allsuits, actions, or claims brought by any and all person or persons because of, arising out orresulting fromthe use ofreal property and the services being provided by Valley ROP, any dangerous or defective condition thereof, or any act or omission by ValleyROP,said insurance shall be primary toCity's general and property insurance policies and shall initially and Docusign Envelope ID: 05A242CE-38E6-4FC1-B0BD-0AEFE529B7BE

3 hereafter be increased to provide coverage in the same amounts as ValleyROP's public liability policy.CertificatesofsaidinsuranceshallbeprovidedtotheCityannually.ValleyROPandCityshall eachmaintain in fullforce and effect during the full termofthis Agreement liability insurance programs.

15. In lieu of and notwithstanding the pro rata risk allocation which might otherwise be imposed between the Parties pursuant to Government Code Section 895.6, the Parties agree that all losses or liabilities incurred by a party shall not be shared pro rata but instead ValleyROP andCity agree that pursuant to Government Code Section 895.4, each of the parties hereto shall fully indemnify, defend, and hold each of the other parties, their officers, board members, employees, agents and students, harmlessfrom any claim, expense or cost, damage orliability imposed for injury (as defined by GovernmentCodeSection 810.8) occurring by reason ofthe negligent acts or omissions or willfulmisconduct ofthe indemnifying party, its officers, employees, of agents and students, under orin connectionwith or arising out of any work, authority orjurisdiction delegated to such party under this Agreement. No party, nor any officer, boardmember, employee, agent or studentthereofshall be responsible for any damage orliability occurring by reason of the negligent acts or omissions or willful misconduct of the other parties hereto their officers, board members, employees of agents orstudents, under orin connection with or arising out of any work authority or jurisdiction delegated to such other parties underthis Agreement.

16. ValleyROPshall ensurethatitsstudents are coveredunderValleyROP'sblanketprogramfor workers compensation. AcopyofthispolicywillbeprovidedtotheCity annually.

17. Valley ROP shall provide basic HIPPA Training for Emergency Medical Services prior to scheduling field training with City. Field training shall include but is not limited to the following topics; Protected Health Information (PHI), Minimum Necessary Standard, Patient Privacy, Permitted Disclosures, Documentation and Security, and Consequences of Violations.

18. Cityshallnotsubcontractorassignanyoftheservices contemplatedunderthisAgreement.

19. ThisAgreementmaybeterminatedbyeitherpartyat anytimeuponmutual agreementoftheparties.

To terminate thisAgreement, either party shall give six (6)monthswritten notice priorto the date of termination.

20. ThisAgreement constitutesthe entire agreement between ValleyROP and City, and supersedes any prior or contemporaneous understanding or agreementwith respect to the services being provided.

21. ThetermsandconditionsofthisAgreementshallbegovernedbythelawsofthestateofCalifornia with venue in FresnoCounty,California.

22. This Agreement shall be for three (3) years and the Parties shall have the option to renew such Agreement every year thereafter.

23. Valley ROP's Superintendent, and City administrative representative may mutually agree upon, and may formalize by a separate writing, the operational details of the field training program, and such separate agreement and writing will be binding on both the Valley ROP and the City in the same manner asifthey had been part ofthis agreement.

Docusign Envelope ID: 05A242CE-38E6-4FC1-B0BD-0AEFE529B7BE

4 24. Any controversy, claimordispute,whetherbasedon contract,tortorstatute under eitherCalifornia or federal law, arising out of orrelating to this Agreement any alleged breach of itshall be determined and settled by binding arbitration in accordance with theCommercial Arbitration Rules ofthe American Arbitration Association, and a judgment on the award rendered by the arbitrator(s) may be entered in any court having jurisdiction. The arbitration will be conducted in Fresno, California. The prevailing party in the arbitration proceeding will be entitled to recoveritsreasonable attorneys' fees and costs expended orincurred relating to or arising out of the arbitration matter.

25. This Agreementmay bemodified or amended without additional consideration at any time by mutual written consent of the parties.

26. All notices, demands, or other writingsin the Agreement provided to be given or madeorsent,or whichmaybegiven ormadeorsent, by eitherparty hereto totheother,shall be deemed to have been fully given ormade orsent whenmade in writing and deposited in the United States mail, registered or certified, postage prepaid, and addressed asfollows:

Luis Patlan Fabrizio Lofaro
City Manager Superintendent
City of Dinuba Valley Regional Occupational Program
405 E El Monte Way 310 West Myrtle Ave.

Dinuba, CA 93618 Reedley, CA 93654

27. Each of the persons signing this Agreement represents and warrants that such person has been duly authorized to sign this Agreement on behalf of the party indicated, and each of the Parties by signing this Agreement warrants and represents that such party is legally authorized and entitled to enter into this Agreement.

CITY OF DINUBA VALLEY REGIONAL OCCUPATIONAL

PROGRAM
By: By:

City Manager Superintendent
Date: Date:

Docusign Envelope ID: 05A242CE-38E6-4FC1-B0BD-0AEFE529B7BE 7/29/2025
Fabrizio Lofaro

City Council Staff Report
Department: PUBLIC WORKS August 12, 2025
To: Mayor and City Council
From: George Avila, Public Works Director
By: Santillan Anna, Fiscal Analyst I
Subject: Award Well 18 Improvements Project and Adopt Resolution No. 2025-42 and Approving FY 25/26 Budget Amendment No. 2026-01 (GA) RECOMMENDATION:

Council to approve the following actions by one motion:

1. Award Well 18 Improvements Project to Logan Bros Pump & Ag, Inc. in the amount of $90,492; and,

2. Adopt Resolution No. 2025-42 approving Budget Amendment No. 2026-1 for FY 25/26 to fund the subject project.

EXECUTIVE SUMMARY:

Well 18 located at 820 N Euclid Ave has been out of service due to mechanical failures.

Staff solicited informal bids for needed repairs to the well and recommends awarding project to Logan Bros Pump & Ag, Inc. in the amount of $90,492.

OUTSTANDING ISSUES:

None.

DISCUSSION:

Municipal production wells are crucial for the City of Dinuba, as groundwater is the city's source of drinking water. Dinuba currently operates six active municipal wells, which deliver safe and reliable potable water to homes, schools, businesses, and public facilities. Well 18 was taken out of service due to severe clogging of the well perforations, which resulted in diminished performance and water production. Well 18, located in the northern sector of the City, is a critical source of groundwater supply and plays a vital role in meeting the potable water demand for that part of town.

A recent inspection confirmed the need for rehabilitation, including the mechanical

cleaning of the well screen through jetting and air-lift operations. Following this, a video inspection will be conducted to assess the effectiveness of the cleaning and to evaluate any remaining obstructions or damage to the well or pump appurtenances. In addition to cleaning, a section of the eight-inch steel pipe within the well column requires replacement to restore structural integrity and flow capacity. After cleaning and replacement, the well will be chlorinated and test-pumped to confirm restoration of functionality. Finally, the pump and related appurtenances will be reinstalled.

Staff solicited informal bids for the necessary improvements and received two (2) proposals. The bid results are as follows:

Logan Bros Pump & Ag, Inc. $90,492
Belknap Pump Company $156,050
Upon review, it was determined that the bid received from Logan Bros Pump & Ag, Inc. in the amount of $90,492, met the required specifications. Staff recommends that the City Council award the contract to Logan Bros Pump & Ag, Inc. to proceed with the necessary work.

A budget amendment is also needed as the cost of these repairs was not anticipated in the FY 2025-26 budget. Staff recommends that the City Council adopt Resolution No. 2025-42, as outlined in Attachment 'A', approving Budget Amendment No. 2026-01 for Fiscal Year 2025/26 in the amount of $102,500. The additional requested funding will be used to make necessary repairs at Well 16 located on Kamm Ave.

FISCAL IMPACT:

The subject project will be funded by reserves in the Water Operating Fund.

PUBLIC HEARING:

None.

ATTACHMENTS:

1. Resolution 2025-42

City Council Staff Report
Department: CITY MANAGER'S OFFICE August 12, 2025
To: Mayor and City Council
From: Daniel James, Assistant City Manager
By:

Subject: Resolution No. 2025-43, Authorization to Purchase Real Property (APN:
014-171-010) (DJ)
RECOMMENDATION:

Council to adopt Resolution No. 2025-43 authorizing the purchase of real property located at 1051 East El Monte Way (APN: 014-171-010)
EXECUTIVE SUMMARY:

The City is planning to construct a roundabout at the intersection of E. El Monte Way and Perry Avenue to alleviate congestion and improve safety. In order for the new roundabout to be configured using the most optimal design, real property located at 1051 East El Monte Way (northwest corner of E. El Monte Way and Perry Avenue) must be acquired. Staff have negotiated the purchase of the property with the seller for the amount of $232,000. The staff are requesting that the City Council authorize the City Manager or designee to execute the purchase agreement.

OUTSTANDING ISSUES:

None
DISCUSSION:

The intersection of El Monte Way and Perry Ave. has experienced a variety of traffic issues for many years. In order to alleviate these issues, a new roundabout is being planned at the intersection. Staff are currently in the design phase of the project and have determined that, in order to accommodate the improvements necessary to construct the roundabout, real property must be acquired to the east of the intersection of El Monte Way and Perry Ave. Staff have negotiated the purchase of the property with the seller and is asking that the City Council formally approve the purchase and authorize the City Manager or designee to execute the purchase agreement. An APN map of the subject property is attached herein as 'Exhibit A' of 'Attachment A.'

Property Location: 990 East El Monte Way. Dinuba, CA 93618 APN: 018-011-006
Purchase Price: $232,000
Funding: Measure R (TCAG)
Staff has prepared Resolution No. 2025-43 which outlines the terms of the purchase of the subject property. The Resolution is attached herein as 'Attachment A.' Staff has also executed a Purchase Agreement with the seller which is contingent upon approval of the purchase by City Council. Should Council not approve the sale, the agreement would become null and void. A copy of the purchase agreement is attached as 'Attachment B.' Staff recommends Council adopt Resolution No. 2025-43 and authorize the City manager, or designee to execute all documents pertaining to the purchase of the property.

FISCAL IMPACT:
$232,000 to be funded by local Measure R monies which have been allocated by TCAG.

PUBLIC HEARING:

None required.

ATTACHMENTS:

1. A. Resolution 2025-43 - Real Property Purchase

2. B. Purchase Agreement

RESOLUTION 2025-43

A RESOLUTION OF THE CITY COUNCIL

OF THE CITY OF DINUBA AUTHORIZING THE PURCHASE OF REAL PROPERTY LOCATED AT EL MONTE AND PERRY AVENUE.

WHEREAS, the City of Dinuba is proposing a Roundabout at El Monte and Perry Avenue; and
WHEREAS, the El Monte and Perry Avenue Roundabout requires the acquisition of property in order to accommodate the most functional design; and WHEREAS, the use of Measure R funds in the amount of $232,000 have been allocated for property acquisition for the new roundabout; and
WHEREAS, the owners have agreed to sell the property listed below to the City:

Property Owner APN Address
RAUL ANGULO 014-171-010 1051 East El Monte Way
Dinuba, CA 93618
WHEREAS, the City Engineer recommends the acquisition of the subject property from the property owners listed above in order to accommodate the proposed roundabout; NOW, THEREFORE, BE IT RESOLVED that the City Council of Dinuba herby takes the following actions:

1. Authorizes the purchase of real property located at 1051 East El Monte Way in Dinuba, California.

2. Authorize the City manager or designee to execute all documents related to the purchase and transfer of the property to the City of Dinuba.

3. The above recitals are true and correct and are adopted as the findings of the City Council.

4. The provisions of this Resolution are severable and if any provision, clause, sentence, word or part thereof is held illegal, invalid, unconstitutional, or inapplicable to any person or circumstances, such illegality, invalidity, unconstitutionality, or inapplicability shall not affect or impair any of the remaining provisions, clauses, sentences, sections, words or parts thereof of the Resolution or their applicability to other persons or circumstances.

5. That the City Clerk shall certify to the adoption of this Resolution and that the same shall be in full force and effect.

IN WITNESS THEREOF, I, Maribel Reynosa, Mayor of the City of Dinuba have hereunto set my hand and caused the great seal of the City of Dinuba to be affixed, on this day of two-thousand-twenty-three.

PASSED AND ADOPTED this day of , 20 by the following vote:

AYES: COUNCIL MEMBERS:

NOES: COUNCIL MEMBERS:

ABSTAIN: COUNCIL MEMBERS:

ABSENT: COUNCIL MEMBERS:

Mayor
ATTEST:

Maria Alaniz, City Clerk

EXHIBIT 'A'

DISCLOSURE REGARDING

REAL ESTATE AGENCY RELATIONSHIP
(As required by the Civil Code)
(C.A.R. Form AD, Revised 12/24)
(If checked) This form is being provided in connection with a transaction for a leasehold interest exceeding one year as per Civil Code §§ 2079.13(j), (k), and (l).

When you enter into a discussion with a real estate agent regarding a real estate transaction, you should from the outset understand what type of agency relationship or representation you wish to have with the agent in the transaction.

SELLER'S AGENT
A Seller's agent under a listing agreement with the Seller acts as the agent for the Seller only. A Seller's agent or a subagent of that agent has the following affirmative obligations:

To the Seller: A Fiduciary duty of utmost care, integrity, honesty and loyalty in dealings with the Seller.

To the Buyer and the Seller:
(a) Diligent exercise of reasonable skill and care in performance of the agent's duties. (b) A duty of honest and fair dealing and good faith.
(c) A duty to disclose all facts known to the agent materially affecting the value or desirability of the property that are not known to, or within the diligent attention and observation of, the parties. An agent is not obligated to reveal to either party any confidential information obtained from the other party that does not involve the affirmative duties set forth above.

BUYER'S AGENT
A Buyer's agent can, with a Buyer's consent, agree to act as agent for the Buyer only. This includes a Buyer's agent under a buyer-broker representation agreement with the Buyer. In these situations, the agent is not the Seller's agent, even if by agreement the agent may receive compensation for services rendered, either in full or in part from the Seller. An agent acting only for a Buyer has the following affirmative obligations:

To the Buyer: A fiduciary duty of utmost care, integrity, honesty and loyalty in dealings with the Buyer.

To the Buyer and the Seller:
(a) Diligent exercise of reasonable skill and care in performance of the agent's duties. (b) A duty of honest and fair dealing and good faith.
(c) A duty to disclose all facts known to the agent materially affecting the value or desirability of the property that are not known to, or within the diligent attention and observation of, the parties. An agent is not obligated to reveal to either party any confidential information obtained from the other party that does not involve the affirmative duties set forth above.

AGENT REPRESENTING BOTH SELLER AND BUYER
A real estate agent, either acting directly or through one or more salespersons and broker associates, can legally be the agent of both the Seller and the Buyer in a transaction, but only with the knowledge and consent of both the Seller and the Buyer.

In a dual agency situation, the agent has the following affirmative obligations to both the Seller and the Buyer:
(a) A fiduciary duty of utmost care, integrity, honesty and loyalty in the dealings with either the Seller or the Buyer. (b) Other duties to the Seller and the Buyer as stated above in their respective sections.

In representing both Seller and Buyer, a dual agent may not, without the express permission of the respective party, disclose to the other party confidential information, including, but not limited to, facts relating to either the Buyer's or Seller's financial position, motivations, bargaining position, or other personal information that may impact price, including the Seller's willingness to accept a price less than the listing price or the Buyer's willingness to pay a price greater than the price offered.

SELLER AND BUYER RESPONSIBILITIES
Either the purchase agreement or a separate document will contain a confirmation of which agent is representing you and whether that agent is representing you exclusively in the transaction or acting as a dual agent. Please pay attention to that confirmation to make sure it accurately reflects your understanding of your agent's role.

The above duties of the agent in a real estate transaction do not relieve a Seller or Buyer from the responsibility to protect their own interests. You should carefully read all agreements to assure that they adequately express your understanding of the transaction. A real estate agent is a person qualified to advise about real estate. If legal or tax advice is desired, consult a competent professional.

If you are a Buyer, you have the duty to exercise reasonable care to protect yourself, including as to those facts about the property which are known to you or within your diligent attention and observation.

Both Sellers and Buyers should strongly consider obtaining tax advice from a competent professional because the federal and state tax consequences of a transaction can be complex and subject to change.

Throughout your real property transaction you may receive more than one disclosure form, depending upon the number of agents assisting in the transaction. The law requires each agent with whom you have more than a casual relationship to present you with this disclosure form. You should read its contents each time it is presented to you, considering the relationship between you and the real estate agent in your specific transaction. This disclosure form includes the provisions of §§ 2079.13 to 2079.24, inclusive, of the Civil Code set forth on page 2. Read it carefully.

Note: Real estate broker commissions are not set by law and are fully negotiable.

I/WE ACKNOWLEDGE RECEIPT OF A COPY OF THIS DISCLOSURE AND THE PORTIONS OF THE CIVIL CODE PRINTED ON THE SECOND PAGE.

Buyer Seller Landlord Tenant Date
Buyer Seller Landlord Tenant Date
Agent DRE Lic. #
Real Estate Broker (Firm)
By DRE Lic. # Date
(Salesperson or Broker-Associate, if any)
AD REVISED 12/24 (PAGE 1 OF 2)
DISCLOSURE REGARDING REAL ESTATE AGENCY RELATIONSHIP (AD PAGE 1 OF 2) Phone: Fax:

Produced with Lone Wolf Transactions (zipForm Edition) 717 N Harwood St, Suite 2200, Dallas, TX 75201 www.lwolf.com X City of Dinuba
Harness Realty 01893543
Scott Harness 01893543
Scott Harness, Broker, 124 W Tulare st Dinuba CA 93618 5593058361 City of Dinuba Scott Harness
Authentisign ID: 80186498-E56E-F011-8DCA-00224822F75A Authentisign ID: C2CAED2C-7D71-F011-8DCA-00224822F75A

CIVIL §§ 2079.13 - 2079.24 (2079.16 APPEARS ON THE FRONT) 2079.13. As used in this section and §§ 2079.7 and 2079.14 to 2079.24, inclusive, the following terms have the following meanings:
(a) “Agent” means a person acting under provisions of Title 9 (commencing with § 2295) in a real property transaction, and includes a person who is licensed as a real estate broker under Chapter 3 (commencing with § 10130) of Part 1 of Division 4 of the Business and Professions Code, and under whose license a listing is executed or an offer to purchase is obtained. The agent in the real property transaction bears responsibility for that agent's salespersons or broker associates who perform as agents of the agent. When a salesperson or broker associate owes a duty to any principal, or to any buyer or seller who is not a principal, in a real property transaction, that duty is equivalent to the duty owed to that party by the broker for whom the salesperson or broker associate functions. (b) “Buyer” means a transferee in a real property transaction, and includes a person who executes an offer to purchase real property from a seller through an agent, or who seeks the services of an agent in more than a casual, transitory, or preliminary manner, with the object of entering into a real property transaction. “Buyer” includes a vendee or lessee of real property. (c) “Commercial real property” means all real property in the state, except (1) single-family residential real property, (2) dwelling units made subject to Chapter 2 (commencing with § 1940) of Title 5, (3) a mobilehome, as defined in § 798.3, (4) vacant land, or (5) a recreational vehicle, as defined in § 799.29. (d) “Dual agent” means an agent acting, either directly or through a salesperson or broker associate, as agent for both the seller and the buyer in a real property transaction. (e) “Listing agreement” means a written contract between a seller of real property and an agent, by which the agent has been authorized to sell the real property or to find or obtain a buyer, including rendering other services for which a real estate license is required to the seller pursuant to the terms of the agreement. (f) “Seller's agent” means a person who has obtained a listing of real property to act as an agent for compensation. (g) “Listing price” is the amount expressed in dollars specified in the listing for which the seller is willing to sell the real property through the seller's agent. (h) “Offering price” is the amount expressed in dollars specified in an offer to purchase for which the buyer is willing to buy the real property. (i) “Offer to purchase” means a written contract executed by a buyer acting through a buyer's agent that becomes the contract for the sale of the real property upon acceptance by the seller. (j) “Real property” means any estate specified by subdivision (1) or (2) of § 761 in property, and includes (1) single-family residential property, (2) multiunit residential property with more than four dwelling units, (3) commercial real property, (4) vacant land, (5) a ground lease coupled with improvements, or (6) a manufactured home as defined in § 18007 of the Health and Safety Code, or a mobilehome as defined in § 18008 of the Health and Safety Code, when offered for sale or sold through an agent pursuant to the authority contained in § 10131.6 of the Business and Professions Code. (k) “Real property transaction” means a transaction for the sale of real property in which an agent is retained by a buyer, seller, or both a buyer and seller to act in that transaction, and includes a listing or an offer to purchase. (l) “Single-family residential property” or “single-family residential real property” means any of the following: (1) Real property improved with one to four dwelling units, including a leasehold exceeding one year's duration. (2) A unit in a residential stock cooperative, condominium, or planned unit development. (3) A mobilehome or manufactured home when offered for sale or sold through a real estate broker pursuant to § 10131.6 of the Business and Professions Code. (m) “Sell,” “sale,” or “sold” refers to a transaction for the transfer of real property from the seller to the buyer and includes exchanges of real property between the seller and buyer, transactions for the creation of a real property sales contract within the meaning of § 2985, and transactions for the creation of a leasehold exceeding one year's duration. (n) “Seller” means the transferor in a real property transaction and includes an owner who lists real property with an agent, whether or not a transfer results, or who receives an offer to purchase real property of which he or she is the owner from an agent on behalf of another. “Seller” includes both a vendor and a lessor of real property. (o) “Buyer's agent” means an agent who represents a buyer in a real property transaction. (p) “Buyer-broker representation agreement” means a written contract between a buyer of real property and a buyer's agent by which the buyer's agent has been authorized by the buyer to provide services set forth in subdivision (a) of § 10131 of the Business and Professions Code for or on behalf of the buyer for which a real estate license is required pursuant to the terms of the contract. 2079.14. (a) A copy of the disclosure form specified in § 2079.16 shall be provided in a real property transaction as follows: (1) The seller's agent, if any, shall provide the disclosure form to the seller before entering into a listing agreement. (2) The buyer's agent shall provide the disclosure to the buyer as soon as practicable before the execution of a buyer-broker representation agreement and execution of the buyer's offer to purchase. If the offer to purchase is not prepared by the buyer's agent, the buyer's agent shall present the disclosure form to the buyer not later than the next business day after receiving the offer to purchase from the buyer. (b) The agent providing the disclosure form specified in § 2079.16 shall obtain a signed acknowledgement of receipt from the buyer or seller except as provided in § 2079.15. 2079.15. In any circumstance in which the seller or buyer refuses to sign an acknowledgment of receipt pursuant to § 2079.14, the agent shall set forth, sign, and date a written declaration of the facts of the refusal. 2079.16 Reproduced on Page 1 of this AD form.
2079.17(a) As soon as practicable, the buyer's agent shall disclose to the buyer and seller whether the agent is acting in the real property transaction as the buyer's agent, or as a dual agent representing both the buyer and the seller. This relationship shall be confirmed in the contract to purchase and sell real property or in a separate writing executed or acknowledged by the seller, the buyer, and the buyer's agent prior to or coincident with execution of that contract by the buyer and the seller, respectively. (b) As soon as practicable, the seller's agent shall disclose to the seller whether the seller's agent is acting in the real property transaction as the seller's agent, or as a dual agent representing both the buyer and seller. This relationship shall be confirmed in the contract to purchase and sell real property or in a separate writing executed or acknowledged by the seller and the seller's agent prior to or coincident with the execution of that contract by the seller. (c) The confirmation required by subdivisions (a) and (b) shall be in the following form:

Seller's Brokerage Firm DO NOT COMPLETE. SAMPLE ONLY License Number ______________ Is the broker of (check one): the seller; or both the buyer and seller. (dual agent) Seller's Agent DO NOT COMPLETE. SAMPLE ONLY License Number ______________ Is (check one): the Seller's Agent. (salesperson or broker associate) both the Buyer's and Seller's Agent. (dual agent) Buyer's Brokerage Firm DO NOT COMPLETE. SAMPLE ONLY License Number ______________ Is the broker of (check one): the buyer; or both the buyer and seller. (dual agent) Buyer's Agent DO NOT COMPLETE. SAMPLE ONLY License Number ______________ Is (check one): the Buyer's Agent. (salesperson or broker associate) both the Buyer's and Seller's Agent. (dual agent) (d) The disclosures and confirmation required by this section shall be in addition to the disclosure required by § 2079.14. An agent's duty to provide disclosure and confirmation of representation in this section may be performed by a real estate salesperson or broker associate affiliated with that broker. 2079.18 (Repealed pursuant to AB-1289)
2079.19 The payment of compensation or the obligation to pay compensation to an agent by the seller or buyer is not necessarily determinative of a particular agency relationship between an agent and the seller or buyer. A listing agent and a selling agent may agree to share any compensation or commission paid, or any right to any compensation or commission for which an obligation arises as the result of a real estate transaction, and the terms of any such agreement shall not necessarily be determinative of a particular relationship. 2079.20 Nothing in this article prevents an agent from selecting, as a condition of the agent's employment, a specific form of agency relationship not specifically prohibited by this article if the requirements of § 2079.14 and § 2079.17 are complied with. 2079.21 (a) A dual agent may not, without the express permission of the seller, disclose to the buyer any confidential information obtained from the seller. (b) A dual agent may not, without the express permission of the buyer, disclose to the seller any confidential information obtained from the buyer. (c) “Confidential information” means facts relating to the client's financial position, motivations, bargaining position, or other personal information that may impact price, such as the seller is willing to accept a price less than the listing price or the buyer is willing to pay a price greater than the price offered. (d) This section does not alter in any way the duty or responsibility of a dual agent to any principal with respect to confidential information other than price. 2079.22 Nothing in this article precludes a seller's agent from also being a buyer's agent. If a seller or buyer in a transaction chooses to not be represented by an agent, that does not, of itself, make that agent a dual agent. 2079.23 (a) A contract between the principal and agent may be modified or altered to change the agency relationship at any time before the performance of the act which is the object of the agency with the written consent of the parties to the agency relationship. (b) A lender or an auction company retained by a lender to control aspects of a transaction of real property subject to this part, including validating the sales price, shall not require, as a condition of receiving the lender's approval of the transaction, the homeowner or listing agent to defend or indemnify the lender or auction company from any liability alleged to result from the actions of the lender or auction company. Any clause, provision, covenant, or agreement purporting to impose an obligation to defend or indemnify a lender or an auction company in violation of this subdivision is against public policy, void, and unenforceable. 2079.24 Nothing in this article shall be construed to either diminish the duty of disclosure owed buyers and sellers by agents and their associate licensees, subagents, and employees or to relieve agents and their associate licensees, subagents, and employees from liability for their conduct in connection with acts governed by this article or for any breach of a fiduciary duty or a duty of disclosure.

Published and Distributed by: REAL ESTATE BUSINESS SERVICES, LLC. a subsidiary of the California Association of REALTORS® AD REVISED 12/24 (PAGE 2 OF 2)
DISCLOSURE REGARDING REAL ESTATE AGENCY RELATIONSHIP (AD PAGE 2 OF 2) Produced with Lone Wolf Transactions (zipForm Edition) 717 N Harwood St, Suite 2200, Dallas, TX 75201 www.lwolf.com City of Dinuba Authentisign ID: 80186498-E56E-F011-8DCA-00224822F75A Authentisign ID: C2CAED2C-7D71-F011-8DCA-00224822F75A

CALIFORNIA RESIDENTIAL PURCHASE AGREEMENT

AND JOINT ESCROW INSTRUCTIONS
(C.A.R. FORM RPA, Revised 12/24)
Date Prepared:

1. OFFER:

A. THIS IS AN OFFER FROM (“Buyer”).

B. THE PROPERTY to be acquired is , situated
in (City), (County), California, (Zip Code),
Assessor's Parcel No(s). (“Property”).
(Postal/Mailing address may be different from city jurisdiction. Buyer is advised to investigate.) C. THE TERMS OF THE PURCHASE ARE SPECIFIED BELOW AND ON THE FOLLOWING PAGES.

D. Buyer and Seller are referred to herein as the "Parties." Brokers and Agents are not Parties to this Agreement.

2. AGENCY:

A. DISCLOSURE: The Parties each acknowledge receipt of a “Disclosure Regarding Real Estate Agency Relationship” (C.A.R.

Form AD) if represented by a real estate licensee. Buyer's Agent is not legally required to give to Seller's Agent the AD form Signed by Buyer. Seller's Agent is not legally obligated to give to Buyer's Agent the AD form Signed by Seller.

B. CONFIRMATION: The following agency relationships are hereby confirmed for this transaction.

Seller's Brokerage Firm License Number
Is the broker of (check one): the Seller; or both the Buyer and Seller (Dual Agent).

Seller's Agent License Number
Is (check one): the Seller's Agent. (Salesperson or broker associate); or both the Buyer's and Seller's Agent (Dual Agent).

Buyer's Brokerage Firm License Number
Is the broker of (check one): the Buyer; or both the Buyer and Seller (Dual Agent).

Buyer's Agent License Number
Is (check one): the Buyer's Agent (Salesperson or broker associate); or both the Buyer's and Seller's Agent (Dual Agent).

C. More than one Brokerage represents Seller, Buyer. See, Additional Broker Acknowledgement (C.A.R. Form ABA).

D. POTENTIALLY COMPETING BUYERS AND SELLERS: The Parties each acknowledge receipt of a “Possible Representation of More than One Buyer or Seller - Disclosure and Consent” (C.A.R. Form PRBS).

3. TERMS OF PURCHASE AND ALLOCATION OF COSTS: The items in this paragraph are contractual terms of the Agreement.

Referenced paragraphs provide further explanation. This form is 17 pages. The Parties are advised to read all 17 pages.

Para # Paragraph Title or Contract
Term
Terms and Conditions Additional Terms
A 5, 5B (cash) Purchase Price $ All Cash
B Close Of Escrow (COE) Days after Acceptance
OR on (date)
C 33A Expiration of Offer 3 calendar days after all Buyer Signature(s) or (date),
at 5PM or AM/ PM
D(1) 5A(1) Initial Deposit Amount $ ( % of purchase price) (% number above is for calculation purposes
and is not a contractual term)
within 3 (or ) business days
after Acceptance by wire transfer
OR
D(2) 5A(2) Increased Deposit See attached Increased Deposit Addendum (C.A.R. Form IDA) E(1) 5C(1) Loan Amount(s): First
Interest Rate
Points
$ ( % of purchase price)
Fixed rate or Initial adjustable rate
● not to exceed %
● Buyer to pay up to points to obtain the
rate above
Conventional or, if checked,
FHA (Forms FVAC/HID attached)
VA (Form FVAC attached)
Seller Financing
Other:

If FHA or VA checked, Deliver list of
lender required repairs
17 (or ) Days after Acceptance
E(2) 5C(2) Additional Financed Amount
Interest Rate
Points
$ ( % of purchase price)
Fixed rate or Initial adjustable rate
● not to exceed %
● Buyer to pay up to points to obtain
rate above
Conventional or, if checked,
Seller Financing
Other:

E(3) 7A Occupancy Type Primary, or if checked, Secondary Investment F 5D Balance of Down Payment $
PURCHASE PRICE TOTAL $
© 2024, California Association of REALTORS®, Inc.

RPA REVISED 12/24 (PAGE 1 OF 17) Buyer's Initials / Seller's Initials / CALIFORNIA RESIDENTIAL PURCHASE AGREEMENT AND JOINT ESCROW INSTRUCTIONS (RPA PAGE 1 OF 17) Phone: Fax:

Produced with Lone Wolf Transactions (zipForm Edition) 717 N Harwood St, Suite 2200, Dallas, TX 75201 www.lwolf.com July 31, 2025
City of Dinuba
1051 E El Monte Way
Dinuba Tulare 93618
014-171-010
Harness Realty 01893543
X
Scott Harness 01893543
X
X
232,000.00 X
X 60
2,500.00 1.08
X
229,500.00
232,000.00
Scott Harness, Broker, 124 W Tulare st Dinuba CA 93618 5593058361 City of Dinuba Scott Harness
Authentisign ID: 80186498-E56E-F011-8DCA-00224822F75A Authentisign ID: C2CAED2C-7D71-F011-8DCA-00224822F75A

Property Address: Date:

G SELLER PAYMENT TO COVER BUYER EXPENSES AND COSTS
G(1) 5E Seller Credit to Buyer $ For closing costs
G(2) ADDITIONAL SELLER CREDIT TERMS (does not include buyer broker compensation):

G(3) 18A(2),
18A(3)
Seller Payment for Buyer's
Obligation to compensate Buyer's
Broker
Buyer Compensation Affirmation
Seller agrees to pay, out of transaction proceeds, % of the final purchase price AND, if applicable $ OR, if checked $ toward
the obligation of Buyer to compensate Buyer's Broker.

Buyer affirmatively represents that, at the time this offer is made, Buyer has a written agreement with Buyer's Broker that: (i) is valid; (ii) covers the Property; and (iii) provides for compensation for no less than the amount stated above.

H(1) 5B Verification of All Cash (sufficient
funds)
Attached to the offer or 3 (or ) Days
after Acceptance
H(2) 6A Verification of Down Payment and
Closing Costs
Attached to the offer or 3 (or ) Days
after Acceptance
H(3) 6B Verification of Loan Application Attached to the offer or 3 (or ) Days after Acceptance
Prequalification Preapproval
Fully underwritten preapproval
I Intentionally Left Blank
J 16 Final Verification of Condition 5 (or ) Days prior to COE K 23 Assignment Request 17 (or ) Days after Acceptance

L CONTINGENCIES TIME TO REMOVE CONTINGENCIES CONTINGENCY REMOVED L(1) 8A Loan(s) 17 (or ) Days after Acceptance No loan contingency L(2) 8B Appraisal: Appraisal contingency
based upon appraised value at a
minimum of purchase price or
$
17 (or ) Days after Acceptance No appraisal contingency Removal of appraisal contingency
does not eliminate appraisal
cancellation rights in FVAC.

L(3) 8C, 12 Investigation of Property 17 (or ) Days after Acceptance Informational Access to Property 17 (or ) Days after Acceptance REMOVAL OR WAIVER OF Buyer's right to access the Property for informational purposes is NOT a contingency, does NOT create cancellation rights, and applies even if contingencies are removed.

CONTINGENCY:

L(4) 8D Insurance 17 (or ) Days after Acceptance
L(5) 8E, 14A Review of Seller Documents 17 (or ) Days after Acceptance, or 5 Days after Delivery, whichever is later
L(6) 8F, 13A Preliminary ("Title") Report 17 (or ) Days after Acceptance, or 5 Days after Delivery, whichever is later
L(7) 8G, 11L Common Interest Disclosures
Per Civil Code § 4525 or Agreement
17 (or ) Days after Acceptance, or 5 Days
after Delivery, whichever is later
L(8) 8H, 9B(6) Review of leased or liened items
(E.g. solar panels or propane tanks)
17 (or ) Days after Acceptance, or 5 Days
after Delivery, whichever is later
CR-B attached
L(9) 8K Sale of Buyer's Property Sale of Buyer's property is not a contingency, UNLESS checked here: C.A.R. Form COP attached M Possession Time for Performance Additional Terms
M(1) Time of Possession Upon notice of recordation, OR 6 PM or AM/ PM on date specified, as
applicable, in 3M(2) or attached TOPA.

M(2) 7D Seller Occupied or Vacant units COE date or, if checked below, days after COE (29 or fewer days)
days after COE (30 or more days)
C.A.R. Form SIP attached if 29 or
fewer days. C.A.R. Form RLAS
attached if 30 or more days.

M(3) 4A, 7A Occupied units by tenants or
anyone other than the Seller
Tenant Occupied Property Addendum
(C.A.R. Form TOPA) attached
See 7A if TOPA is not attached.

N Documents/Fees/Compliance Time for Performance
N(1) 14A Seller Delivery of Documents 7 (or ) Days after Acceptance N(2) 19B Sign and return Escrow Holder
Provisions and Instructions
5 (or ) Days after Delivery
N(3) 11L(2) Time to pay fees for ordering HOA
Documents
3 (or ) Days after Acceptance
N(4) 10B(1) Install smoke alarm(s), CO
detector(s), water heater bracing
7 (or ) Days after Acceptance
N(5) 32 Evidence of representative authority 3 Days after Acceptance O Intentionally Left Blank
RPA REVISED 12/24 (PAGE 2 OF 17) Buyer's Initials / Seller's Initials / CALIFORNIA RESIDENTIAL PURCHASE AGREEMENT AND JOINT ESCROW INSTRUCTIONS (RPA PAGE 2 OF 17) Produced with Lone Wolf Transactions (zipForm Edition) 717 N Harwood St, Suite 2200, Dallas, TX 75201 www.lwolf.com 1051 E El Monte Way, Dinuba, CA 93618 July 31, 2025
X
X
City of Dinuba
Authentisign ID: 80186498-E56E-F011-8DCA-00224822F75A Authentisign ID: C2CAED2C-7D71-F011-8DCA-00224822F75A

Property Address: Date:

P Items Included and Excluded
P(1) 9 Items Included - All items specified in Paragraph 9B are included and the following, if checked:

Stove(s), oven(s), stove/oven
combo(s);
Refrigerator(s);
Wine Refrigerator(s);
Washer(s);
Dryer(s);
Dishwasher(s);
Microwave(s);
Additional Items Included:
.

Video doorbell(s);
Security camera equipment;
Security system(s)/alarm(s), other than
separate video doorbell and camera
equipment;
Smart home control devices;
Wall mounted brackets for video or audio
equipment;
.
.

Above-ground pool(s) / spa(s);
Bathroom mirrors, unless
excluded below;
Electric car charging systems
and stations;
Potted trees/shrubs;
.
.

P(2) Excluded Items:
; ; ;
Q Allocation of Costs
Para # Item Description Who Pays (if Both is checked, cost to be split equally unless Otherwise Agreed)
Additional Terms
Q(1) 10A, 11A Natural Hazard Zone Disclosure
Report, including tax information
Buyer Seller Both Environmental
Other
Provided by:

Q(2) Optional Wildfire Disclosure Report Buyer Seller Both Provided by:

Q(3) (A) Report
(B) Report
Buyer Seller Both
Buyer Seller Both
Q(4) 10B(1) Smoke alarms, CO detectors, water
heater bracing
Buyer Seller Both
Q(5) 10A
10B(2)
Government Required Point of Sale
inspections, reports
Buyer Seller Both
Q(6) 10B(2) Government Required Point of Sale
corrective/remedial actions
Buyer Seller Both
Q(7) 19B Escrow Fee Buyer Seller Both Each to pay their own fees Escrow Holder:

Q(8) 13 Owner's title insurance policy Buyer Seller Both Title Co. (If different from Escrow Holder):

Q(9) Buyer's Lender title insurance policy Buyer Unless Otherwise Agreed, Buyer shall purchase any title insurance
policy insuring Buyer's lender.

Q(10) County transfer tax, fees Buyer Seller Both
Q(11) City transfer tax, fees Buyer Seller Both
Q(12) 11L(2) HOA fee for preparing disclosures Seller
Q(13) HOA certification fee Buyer
Q(14) HOA transfer fees Buyer Seller Both Unless Otherwise Agreed, Seller shall pay for separate HOA moveout fee and Buyer shall pay for separate move-in fee. Applies if
separately billed or itemized with
cost in transfer fee.

Q(15) Private transfer fees Seller, or if checked, Buyer Both Q(16) fees or costs Buyer Seller Both
Q(17) fees or costs Buyer Seller Both
Q(18) 10C Home warranty plan chosen by Buyer.

Coverage includes, but is not limited to:

Buyer Seller Both If Seller or Both checked, Seller's
cost not to exceed $ .

Issued by:

Buyer waives home warranty plan
R OTHER TERMS:

RPA REVISED 12/24 (PAGE 3 OF 17) Buyer's Initials / Seller's Initials / CALIFORNIA RESIDENTIAL PURCHASE AGREEMENT AND JOINT ESCROW INSTRUCTIONS (RPA PAGE 3 OF 17) Produced with Lone Wolf Transactions (zipForm Edition) 717 N Harwood St, Suite 2200, Dallas, TX 75201 www.lwolf.com 1051 E El Monte Way, Dinuba, CA 93618 July 31, 2025
X
X
X *SnapNHD - The Industry Leader*
X
Chicago Title Reedley
X 50/50
Chicago Title Reedley
X
X
Offer contingent upon approval by Dinuba City Council, Escrow to be 60 days or sooner. Property to be delivered vacant.

City of Dinuba
Authentisign ID: 80186498-E56E-F011-8DCA-00224822F75A Authentisign ID: C2CAED2C-7D71-F011-8DCA-00224822F75A

Property Address: Date:

4. PROPERTY ADDENDA AND ADVISORIES: (check all that apply) A. PROPERTY TYPE ADDENDA: This Agreement is subject to the terms contained in the Addenda checked below:

Tenant Occupied Property Addendum (C.A.R. Form TOPA) (Should be checked whether current tenants will remain or not.) Probate Agreement Purchase Addendum (C.A.R. Form PA-PA) Manufactured Home Purchase Addendum (C.A.R. Form MH-PA) Tenancy in Common Purchase Addendum (C.A.R. Form TIC-PA) Stock Cooperative Purchase Addendum (C.A.R. Form COOP-PA) Mixed Use Purchase Addendum (C.A.R. Form MU-PA) Other
B. OTHER ADDENDA: This Agreement is subject to the terms contained in the Addenda checked below:

Addendum # (C.A.R. Form ADM) Short Sale Addendum (C.A.R. Form SSA) Back Up Offer Addendum (C.A.R. Form BUO) Court Confirmation Addendum (C.A.R. Form CCA) Septic, Well, Property Monument and Propane Addendum (C.A.R. Form SWPI) Buyer Intent to Exchange Addendum (C.A.R. Form BXA) Seller Intent to Exchange Addendum (C.A.R. Form SXA) Other Other
C. BUYER AND SELLER ADVISORIES: (Note: All Advisories below are provided for reference purposes only and are not intended to be incorporated into this Agreement.)
Buyer's Investigation Advisory (C.A.R. Form BIA) Fair Housing and Discrimination Advisory (C.A.R. Form FHDA) Wire Fraud Advisory (C.A.R. Form WFA) Cal. Consumer Privacy Act Advisory (C.A.R. Form CCPA) (Parties may also receive a privacy disclosure from their own Agent.) Wildfire Disaster Advisory (C.A.R. Form WFDA) Statewide Buyer and Seller Advisory (C.A.R. Form SBSA) Trust Advisory (C.A.R. Form TA) Short Sale Information and Advisory (C.A.R. Form SSIA) REO Advisory (C.A.R. Form REO) Probate Advisory (C.A.R. Form PA) Other Other

5. ADDITIONAL TERMS AFFECTING PURCHASE PRICE: Buyer represents that funds will be good when deposited with Escrow Holder.

A. DEPOSIT:
(1) INITIAL DEPOSIT: Buyer shall deliver deposit directly to Escrow Holder. If a method other than wire transfer is specified in paragraph 3D(1) and such method is unacceptable to Escrow Holder, then upon notice from Escrow Holder, delivery shall be by wire transfer.
(2) RETENTION OF DEPOSIT: Paragraph 26, if initialed by all Parties or otherwise incorporated into this Agreement, specifies a remedy for Buyer's default. Buyer and Seller are advised to consult with a qualified California real estate attorney: (i) Before adding any other clause specifying a remedy (such as release or forfeiture of deposit or making a deposit non-refundable) for failure of Buyer to complete the purchase. Any such clause shall be deemed invalid unless the clause independently satisfies the statutory liquidated damages requirements set forth in the Civil Code; and (ii) Regarding possible liability and remedies if Buyer fails to deliver the deposit.

B. ALL CASH OFFER: If an all cash offer is specified in paragraph 3A, no loan is needed to purchase the Property. This Agreement is NOT contingent on Buyer obtaining a loan. Buyer shall, within the time specified in paragraph 3H(1), Deliver written verification of funds sufficient for the purchase price and closing costs.

C. LOAN(S):
(1) FIRST LOAN: This loan will provide for conventional financing UNLESS FHA, VA, Seller Financing (C.A.R. Form SFA), or Other is checked in paragraph 3E(1).
(2) ADDITIONAL FINANCED AMOUNT: If an additional financed amount is specified in paragraph 3E(2), that amount will provide for conventional financing UNLESS Seller Financing (C.A.R. Form SFA), or Other is checked in paragraph 3E(2). (3) BUYER'S LOAN STATUS: Buyer authorizes Seller and Seller's Authorized Agent to contact Buyer's lender(s) to determine the status of any Buyer's loan specified in paragraph 3E, or any alternate loan Buyer pursues, whether or not a contingency of this Agreement. If the contact information for Buyer's lender(s) is different from that provided under the terms of paragraph 6B, Buyer shall Deliver the updated contact information within 1 Day of Seller's request. (4) FHA/VA: If FHA or VA is checked in paragraph 3E(1), a FHA/VA amendatory clause (C.A.R. Form FVAC) shall be incorporated and Signed by all Parties. Buyer shall, within the time specified in paragraph 3E(1), Deliver to Seller written notice (C.A.R. Form RR or AEA) (i) of any lender requirements that Buyer requests Seller to pay for or otherwise correct or (ii) that there are no lender requirements. Notwithstanding Seller's agreement that Buyer may obtain FHA or VA financing, Seller has no obligation to pay or satisfy any or all lender requirements unless agreed in writing.

D. BALANCE OF PURCHASE PRICE (DOWN PAYMENT, paragraph 3F) (including all-cash funds) to be deposited with Escrow Holder pursuant to Escrow Holder instructions.

E. LIMITS ON CREDITS TO BUYER: Any credit to Buyer as specified in paragraph 3G(1) or Otherwise Agreed, from any source, for closing or other costs that is agreed to by the Parties (“Contractual Credit”) shall be disclosed to Buyer's lender, if any, and made at Close Of Escrow. If the total credit allowed by Buyer's lender (“Lender Allowable Credit”) is less than the Contractual Credit, then (i) the Contractual Credit from Seller shall be reduced to the Lender Allowable Credit, and (ii) in the absence of a separate written agreement between the Parties, there shall be no automatic adjustment to the purchase price to make up for the difference between the Contractual Credit and the Lender Allowable Credit.

6. ADDITIONAL FINANCING TERMS:

A. VERIFICATION OF DOWN PAYMENT AND CLOSING COSTS: Written verification of Buyer's down payment and closing costs, within the time specified in paragraph 3H(2) may be made by Buyer or Buyer's lender or loan broker pursuant to paragraph 6B.

B. VERIFICATION OF LOAN APPLICATIONS: Buyer shall Deliver to Seller, within the time specified in paragraph 3H(3) a letter from Buyer's lender or loan broker stating that, based on a review of Buyer's written application and credit report, Buyer is prequalified or preapproved for any NEW loan specified in paragraph 3E. If any loan specified in paragraph 3E is an adjustable rate loan, the prequalification or preapproval letter shall be based on the qualifying rate, not the initial loan rate.

C. BUYER STATED FINANCING: Seller is relying on Buyer's representation of the type of financing specified (including, but not limited to, as applicable, all cash, amount of down payment, or contingent or non-contingent loan). Seller has agreed to a specific closing date, purchase price, and to sell to Buyer in reliance on Buyer's specified financing. Buyer shall pursue the financing specified in this Agreement, even if Buyer also elects to pursue an alternative form of financing. Seller has no obligation to cooperate with Buyer's efforts to obtain any financing other than that specified in this Agreement but shall not interfere with closing at the purchase price on the COE date (paragraph 3B) even if based upon alternate financing. Buyer's inability to obtain alternate financing does not excuse Buyer from the obligation to purchase the Property and close escrow as specified in this Agreement.

RPA REVISED 12/24 (PAGE 4 OF 17) Buyer's Initials / Seller's Initials / CALIFORNIA RESIDENTIAL PURCHASE AGREEMENT AND JOINT ESCROW INSTRUCTIONS (RPA PAGE 4 OF 17) Produced with Lone Wolf Transactions (zipForm Edition) 717 N Harwood St, Suite 2200, Dallas, TX 75201 www.lwolf.com 1051 E El Monte Way, Dinuba, CA 93618 July 31, 2025
X X
X X
City of Dinuba
Authentisign ID: 80186498-E56E-F011-8DCA-00224822F75A Authentisign ID: C2CAED2C-7D71-F011-8DCA-00224822F75A

Property Address: Date:

7. CLOSING AND POSSESSION:

A. OCCUPANCY: If Buyer intends to occupy as a primary or secondary residence (see paragraph 3E(3)), and unless Otherwise Agreed, such as in C.A.R. Form TOPA: (i) the unit Buyer intends to occupy shall be vacant at the time possession is delivered to Buyer, and (ii) if the Property contains more than one unit, within 3 Days after Acceptance Buyer shall give Seller written notice of which unit Buyer intends to occupy. Occupancy may impact available financing. Seller shall disclose to Buyer if occupied by tenants or persons other than Seller, and attach C.A.R. Form TOPA in a counter offer if not part of Buyer's offer.

B. CONDITION OF PROPERTY ON CLOSING:

Unless Otherwise Agreed: (i) the Property shall be delivered “As-Is” in its PRESENT physical condition as of the date of Acceptance; (ii) the Property, including pool, spa, landscaping and grounds, is to be maintained in substantially the same condition as on the date of Acceptance; (iii) Except as specified in paragraph 9C, Seller is not responsible to repair any holes left after the removal of any wall hangings (such as pictures and mirrors), brackets, nails or other fastening devices; and (iv) all debris and personal property not included in the sale shall be removed by Close Of Escrow or at the time possession is delivered to Buyer, if not on the same date. If items are not removed when possession is delivered to Buyer, all items shall be deemed abandoned.

Buyer, after first Delivering to Seller written notice to remove the items within 3 Days, may pay to have such items removed or disposed of and may bring legal action, as per this Agreement, to receive reasonable costs from Seller.

C. Buyer is strongly advised to conduct investigations of the entire Property in order to determine its present condition.

Seller and Agents may not be aware of all defects affecting the Property or other factors that Buyer considers important.

Property improvements may not be built according to code, in compliance with current Law, or have had all required permits issued and/or finalized.

D. SELLER REMAINING IN POSSESSION AFTER CLOSE OF ESCROW: If Seller has the right to remain in possession after Close Of Escrow pursuant to paragraph 3M(2) or as Otherwise Agreed: The Parties are advised to (i) consult with their insurance and legal advisors for information about liability and damage or injury to persons and personal and real property; and (ii) consult with a qualified California real estate attorney where the Property is located to determine the ongoing rights and responsibilities of both Buyer and Seller with regard to each other, including possible tenant rights, and what type of written agreement to use to document the relationship between the Parties. Buyer is advised to consult with Buyer's lender about the impact of Seller's occupancy on Buyer's loan.

E. At Close Of Escrow: (i) Seller assigns to Buyer any assignable warranty rights for items included in the sale; and (ii) Seller shall Deliver to Buyer available Copies of any such warranties. Agents cannot and will not determine the assignability of any warranties.

F. Seller shall, on Close Of Escrow unless Otherwise Agreed and even if Seller remains in possession, provide keys, passwords, codes and/or means to operate all locks, mailboxes, security systems, alarms, home automation systems, intranet and Internet-connected devices included in the purchase price, garage door openers, and all items included in either paragraph 3P or paragraph 9. If the Property is a condominium or located in a common interest development, Seller shall be responsible for securing or providing any such items for Association amenities, facilities, and access. Buyer may be required to pay a deposit to the Homeowners' Association (“HOA”) to obtain keys to accessible HOA facilities.

8. CONTINGENCIES AND REMOVAL OF CONTINGENCIES:

A. LOAN(S):
(1) This Agreement is, unless otherwise specified in paragraph 3L(1) or an attached CR-B form, contingent upon Buyer obtaining the loan(s) specified. If contingent, Buyer shall act diligently and in good faith to obtain the designated loan(s). If there is no appraisal contingency or the appraisal contingency has been waived or removed, then failure of the Property to appraise at the purchase price does not entitle Buyer to exercise the cancellation right pursuant to the loan contingency if Buyer is otherwise qualified for the specified loan and Buyer is able to satisfy lender's non-appraisal conditions for closing the loan.
(2) Buyer is advised to investigate the insurability of the Property as early as possible, as this may be a requirement for lending.

Buyer's ability to obtain insurance for the Property, including fire insurance, is part of Buyer's Insurance contingency. Failure of Buyer to obtain insurance may justify cancellation based on the Insurance contingency but not the loan contingency. (3) Buyer's contractual obligations regarding deposit, balance of down payment and closing costs are not contingencies of this Agreement, unless Otherwise Agreed.
(4) If there is an appraisal contingency, removal of the loan contingency shall not be deemed removal of the appraisal contingency. (5) NO LOAN CONTINGENCY: If "No loan contingency" is checked in paragraph 3L(1), obtaining any loan specified is NOT a contingency of this Agreement. If Buyer does not obtain the loan specified, and as a result is unable to purchase the Property, Seller may be entitled to Buyer's deposit or other legal remedies.

B. APPRAISAL:
(1) This Agreement is, unless otherwise specified in paragraph 3L(2) or an attached CR-B form, contingent upon a written appraisal of the Property by a licensed or certified appraiser at no less than the amount specified in paragraph 3L(2), without requiring repairs or improvements to the Property. Appraisals are often a reliable source to verify square footage of the subject Property. However, the ability to cancel based on the measurements provided in an appraisal falls within the Investigation of Property contingency. The appraisal contingency is solely limited to the value determined by the appraisal. For any cancellation based upon this appraisal contingency, Buyer shall Deliver a Copy of the written appraisal to Seller, upon request by Seller.
(2) NO APPRAISAL CONTINGENCY: If "No appraisal contingency" is checked in paragraph 3L(2), then Buyer may not use the loan contingency specified in paragraph 3L(1) to cancel this Agreement if the sole reason for not obtaining the loan is that the appraisal relied upon by Buyer's lender values the property at an amount less than that specified in paragraph 3L(2). If Buyer is unable to obtain the loan specified solely for this reason, Seller may be entitled to Buyer's deposit or other legal remedies.
(3) Fair Appraisal Act: See paragraph 29 for additional information.

C. INVESTIGATION OF PROPERTY: This Agreement is, as specified in paragraph 3L(3), contingent upon Buyer's acceptance of the condition of, and any other matter affecting, the Property. See paragraph 12.

D. INSURANCE: This Agreement is, as specified in paragraph 3L(4), contingent upon Buyer's assessment of the availability and approval of the cost for any insurance policy desired under this Agreement.

E. REVIEW OF SELLER DOCUMENTS: This Agreement is, as specified in paragraph 3L(5), contingent upon Buyer's review and approval of Seller's documents required in paragraph 14A.

RPA REVISED 12/24 (PAGE 5 OF 17) Buyer's Initials / Seller's Initials / CALIFORNIA RESIDENTIAL PURCHASE AGREEMENT AND JOINT ESCROW INSTRUCTIONS (RPA PAGE 5 OF 17) Produced with Lone Wolf Transactions (zipForm Edition) 717 N Harwood St, Suite 2200, Dallas, TX 75201 www.lwolf.com 1051 E El Monte Way, Dinuba, CA 93618 July 31, 2025
X
City of Dinuba
Authentisign ID: 80186498-E56E-F011-8DCA-00224822F75A Authentisign ID: C2CAED2C-7D71-F011-8DCA-00224822F75A

Property Address: Date:

F. TITLE:
(1) This Agreement is, as specified in paragraph 3L(6), contingent upon Buyer's ability to obtain the title policy provided for in paragraph 13G and on Buyer's review of a current Preliminary Report and items that are disclosed or observable even if not on record or not specified in the Preliminary Report, and satisfying Buyer regarding the current status of title. Buyer is advised to review all underlying documents and other matters affecting title, including, but not limited to, any documents or deeds referenced in the Preliminary Report and any plotted easements. (2) Buyer has 5 Days after receipt to review a revised Preliminary Report, if any, furnished by the Title Company and cancel the transaction if the revised Preliminary Report reveals material or substantial deviations from a previously provided Preliminary Report.

G. CONDOMINIUM/PLANNED DEVELOPMENT DISCLOSURES (IF APPLICABLE): This Agreement is, as specified in paragraph 3L(7), contingent upon Buyer's review and approval of Common Interest Disclosures required by Civil Code § 4525 and under paragraph 11L (“CI Disclosures”).

H. BUYER REVIEW OF LEASED OR LIENED ITEMS CONTINGENCY: Buyer's review of and ability and willingness to assume any lease, maintenance agreement or other ongoing financial obligation, or to accept the Property subject to any lien, disclosed pursuant to paragraph 9B(6), is, as specified in paragraph 3L(8), a contingency of this Agreement. Any assumption of the lease shall not require any financial obligation or contribution by Seller. Seller, after first Delivering a Notice to Buyer to Perform, may cancel this Agreement if Buyer, by the time specified in paragraph 3L(8), refuses to enter into any necessary written agreements to accept responsibility for all obligations of Seller-disclosed leased or liened items.

I. REMOVAL OR WAIVER OF CONTINGENCIES WITH OFFER: Buyer shall have no obligation to remove a contractual contingency unless Seller has provided all required documents, reports, disclosures, and information pertaining to that contingency. If Buyer does remove a contingency without first receiving all required information from Seller, Buyer is relinquishing any contractual rights that apply to that contingency. If Buyer removes or waives any contingencies without an adequate understanding of the Property's condition or Buyer's ability to purchase, Buyer is acting against the advice of Agent.

J. REMOVAL OF CONTINGENCY OR CANCELLATION:
(1) For any contingency specified in paragraph 3L, 8, or elsewhere, Buyer shall, within the applicable period specified, remove the contingency or cancel this Agreement. (2) For the contingencies for review of Seller Documents, Preliminary Report, and Condominium/Planned Development Disclosures, Buyer shall, within the time specified in paragraph 3L or 5 Days after Delivery of Seller Documents or CI Disclosures, whichever occurs later, remove the applicable contingency in writing or cancel this Agreement. (3) If Buyer does not remove a contingency within the time specified, Seller, after first giving Buyer a Notice to Buyer to Perform (C.A.R. Form NBP), shall have the right to cancel this Agreement.

K. SALE OF BUYER'S PROPERTY: This Agreement and Buyer's ability to obtain financing are NOT contingent upon the sale of any property owned by Buyer unless the Sale of Buyer's Property (C.A.R. Form COP) is checked as a contingency of this Agreement in paragraph 3L(9).

9. ITEMS INCLUDED IN AND EXCLUDED FROM SALE:

A. NOTE TO BUYER AND SELLER: Items listed as included or excluded in the Multiple Listing Service (MLS), flyers, marketing materials, or disclosures are NOT included in the purchase price or excluded from the sale unless specified in this paragraph or paragraph 3P or as Otherwise Agreed. Any items included herein are components of the home and are not intended to affect the price. All items are transferred without Seller warranty.

B. ITEMS INCLUDED IN SALE:
(1) All EXISTING fixtures and fittings that are attached to the Property; (2) EXISTING electrical, mechanical, lighting, plumbing and heating fixtures, ceiling fans, fireplace inserts, gas logs and grates, solar power systems, built-in appliances and appliances for which special openings or encasements have been made (whether or not checked in paragraph 3P), window and door screens, awnings, shutters, window coverings (which includes blinds, curtains, drapery, shutters or any other materials that cover any portion of the window) and any associated hardware and rods, attached floor coverings, television antennas, satellite dishes, air coolers/conditioners, pool/spa equipment (including, but not limited to, any cleaning equipment such as motorized/automatic pool cleaners, pool heaters, pool nets, pool covers), garage door openers/remote controls, mailbox, in-ground landscaping, water features and fountains, water softeners, water purifiers, light bulbs (including smart bulbs) and all items specified as included in paragraph 3P, if currently existing at the time of Acceptance.

Note: If Seller does not intend to include any item specified as being included above because it is not owned by Seller, whether placed on the Property by Agent, stager or other third party, the item should be listed as being excluded in paragraph 3P(2) or excluded by Seller in a counter offer. (3) Security System includes any devices, hardware, software, or control units used to monitor and secure the Property, including but not limited to, any motion detectors, door or window alarms, and any other equipment utilized for such purpose. If checked in paragraph 3P, all such items are included in the sale, whether hard wired or not. (4) Home Automation (Smart Home Features) includes any electronic devices and features including, but not limited to, thermostat controls, kitchen appliances not otherwise excluded, and lighting systems, that are connected (hard wired or wirelessly) to a control unit, computer, tablet, phone, or other “smart” device. Any Smart Home devices and features that are physically affixed to the real property, and also existing light bulbs, are included in the sale. Buyer is advised to use paragraph 3P(1) or an addendum to address more directly specific items to be included. Seller is advised to use a counter offer to address more directly any items to be excluded. (5) Non-Dedicated Devices: If checked in paragraph 3P, all smart home and security system control devices are included in the sale, except for any non-dedicated personal computer, tablet, or phone used to control such features. Buyer acknowledges that a separate device and access to wifi or Internet may be required to operate some smart home features and Buyer may have to obtain such device after Close Of Escrow. Seller shall de-list any devices from any personal accounts and shall cooperate with any transfer of services to Buyer. Buyer is advised to change all passwords and ensure the security of any smart home features.
(6) LEASED OR LIENED ITEMS AND SYSTEMS: Seller, within the time specified in paragraph 3N(1), shall (i) disclose to Buyer if any item or system specified in paragraph 3P or 9B or otherwise included in the sale is leased, or not owned by Seller, or is subject to any maintenance or other ongoing financial obligation, or specifically subject to a lien or other encumbrance or loan, and (ii) Deliver to Buyer all written materials (such as lease, warranty, financing, etc.) concerning any such item.

RPA REVISED 12/24 (PAGE 6 OF 17) Buyer's Initials / Seller's Initials / CALIFORNIA RESIDENTIAL PURCHASE AGREEMENT AND JOINT ESCROW INSTRUCTIONS (RPA PAGE 6 OF 17) Produced with Lone Wolf Transactions (zipForm Edition) 717 N Harwood St, Suite 2200, Dallas, TX 75201 www.lwolf.com 1051 E El Monte Way, Dinuba, CA 93618 July 31, 2025
City of Dinuba
Authentisign ID: 80186498-E56E-F011-8DCA-00224822F75A Authentisign ID: C2CAED2C-7D71-F011-8DCA-00224822F75A

Property Address: Date:
(7) Seller represents that all items included in the purchase price, unless Otherwise Agreed, (i) are owned by Seller and shall be transferred free and clear of liens and encumbrances, except the items and systems identified pursuant to paragraph 9B(6), and (ii) are transferred without Seller warranty regardless of value. Seller shall cooperate with the identification of any software or applications and Buyer's efforts to transfer any services needed to operate any Smart Home Features or other items included in this Agreement, including, but not limited to, utilities or security systems.

C. ITEMS EXCLUDED FROM SALE: Unless Otherwise Agreed, the following items are excluded from sale: (i) All items specified in paragraph 3P(2); (ii) audio and video components (such as flat screen TVs, speakers and other items) if any such item is not itself attached to the Property, even if a bracket or other mechanism attached to the component or item is attached to the Property; (iii) furniture and other items secured to the Property for earthquake or safety purposes. Unless otherwise specified in paragraph 3P(1), brackets attached to walls, floors or ceilings for any such component, furniture or item will be removed and holes or other damage shall be repaired, but not painted.

10. ALLOCATION OF COSTS:

A. INSPECTIONS, REPORTS, TESTS AND CERTIFICATES: Paragraphs 3Q(1), (2), (3), and (5) only determines who is to pay for the inspection, report, test, certificate or service mentioned; it does not determine who is to pay for any work recommended or identified in any such document. Agreements for payment of required work should be specified elsewhere in paragraph 3Q, or 3R, or in a separate agreement (such as C.A.R. Forms RR, RRRR, ADM or AEA). Any reports in these paragraphs shall be Delivered in the time specified in paragraph 3N(1).

B. GOVERNMENT REQUIREMENTS AND CORRECTIVE OR REMEDIAL ACTIONS:
(1) LEGALLY REQUIRED INSTALLATIONS AND PROPERTY IMPROVEMENTS: Any required installation of smoke alarm or carbon monoxide device(s) or securing of water heater shall be completed within the time specified in paragraph 3N(4) and paid by the Party specified in paragraph 3Q(4). If Buyer is to pay for these items, Buyer, as instructed by Escrow Holder, shall deposit funds into escrow or directly to the vendor completing the repair or installation. Prior to Close Of Escrow, Seller shall Deliver to Buyer written statement(s) of compliance in accordance with any Law, unless Seller is exempt. If Seller is to pay for these items and does not fulfill Seller's obligation in the time specified, and Buyer incurs costs to comply with lender requirements concerning those items, Seller shall be responsible for Buyer's costs. (2) POINT OF SALE REQUIREMENTS:
(A) Point of sale inspections, reports and repairs refer to any such actions required to be completed before or after Close Of Escrow that are required in order to close under any Law and paid by the Party specified in paragraphs 3Q(5) and 3Q(6) and any such repair, shall be completed prior to final verification of Property, unless Otherwise Agreed. Defensible space compliance shall be determined as agreed in C.A.R. Form FHDS. If Buyer agrees to pay for any portion of such repair, Buyer, shall (i) directly pay to the vendor completing the repair or (ii) provide an invoice to Escrow Holder, deposit funds into escrow sufficient to pay for Buyer's portion of such repair and request Escrow Holder pay the vendor completing the repair.
(B) Buyer shall be provided, within the time specified in paragraph 3N(1), unless Parties Otherwise Agree to another time period, a Copy of any required government-conducted or point-of-sale inspection report prepared pursuant to this Agreement or in anticipation of this sale of the Property. (3) REINSPECTION FEES: If any repair in paragraph 10B(1) is not completed within the time specified and the lender requires an additional inspection to be made, Seller shall be responsible for any corresponding reinspection fee. If Buyer incurs costs to comply with lender requirements concerning those items, Seller shall be responsible for those costs. (4) INFORMATION AND ADVICE ON REQUIREMENTS: Buyer and Seller are advised to seek information from a knowledgeable source regarding local and State mandates and whether they are point of sale requirements or requirements of ownership. Agents do not have expertise in this area and cannot ascertain all of the requirements or costs of compliance.

C. HOME WARRANTY:
(1) Buyer shall choose the home warranty plan and any optional coverages. Buyer shall pay any cost of that plan, chosen by Buyer, that exceeds the amount allocated to Seller in paragraph 3Q(18). Buyer is informed that home warranty plans have many optional coverages, including but not limited to, coverages for Air Conditioner and Pool/Spa. Buyer is advised to investigate these coverages to determine those that may be suitable for Buyer and their cost. (2) If Buyer waives the purchase of a home warranty plan in paragraph 3Q(18), Buyer may still purchase a home warranty plan, at Buyer's expense, prior to Close Of Escrow.

11. STATUTORY AND OTHER DISCLOSURES (INCLUDING LEAD-BASED PAINT HAZARD DISCLOSURES) AND CANCELLATION RIGHTS:

A. TDS, NHD, AND OTHER STATUTORY AND SUPPLEMENTAL DISCLOSURES:
(1) Seller shall, within the time specified in paragraph 3N(1), Deliver to Buyer: unless exempt, fully completed disclosures or notices required by §§ 1102 et. seq. and 1103 et. seq. of the Civil Code (“Statutory Disclosures”). Statutory Disclosures include, but are not limited to, a Real Estate Transfer Disclosure Statement (C.A.R. Form TDS), Natural Hazard Disclosure Statement ("NHD"), notice or actual knowledge of release of illegal controlled substance, notice of special tax and/or assessments (or, if allowed, substantially equivalent notice regarding the Mello-Roos Community Facilities Act of 1982 and Improvement Bond Act of 1915) and, if Seller has actual knowledge, of industrial use and military ordnance location (C.A.R. Form SPQ or ESD), and, if the Property is in a high or very high fire hazard severity area, the information, notices, documentation, and agreements required by §§ 1102.6(f) and 1102.19 of the Civil Code (C.A.R. Form FHDS). (2) The Real Estate Transfer Disclosure Statement required by this paragraph is considered fully completed if Seller has completed the section titled Coordination with Other Disclosure Forms by checking a box (Section I), and Seller has completed and answered all questions and Signed the Seller's Information section (Section II) and the Seller's Agent, if any, has completed and Signed the Seller's Agent's section (Section III), or, if applicable, an Agent Visual Inspection Disclosure (C.A.R. Form AVID). Section V acknowledgment of receipt of a Copy of the TDS shall be Signed after all previous sections, if applicable, have been completed. Nothing stated herein relieves a Buyer's Agent, if any, from the obligation to (i) conduct a reasonably competent and diligent visual inspection of the accessible areas of the Property and disclose, on Section IV of the TDS, or an AVID, material facts affecting the value or desirability of the Property that were or should have been revealed by such an inspection or (ii) complete any sections on all disclosures required to be completed by Buyer's Agent. (3) Seller shall, within the time specified in paragraph 3N(1), provide “Supplemental Disclosures” as follows: (i) unless exempt from the obligation to provide a TDS, complete a Seller Property Questionnaire (C.A.R. Form SPQ) by answering all questions and Signing and Delivering a Copy to Buyer; (ii) if exempt from the obligation to provide a TDS, complete an Exempt Seller Disclosure (C.A.R. Form ESD) by answering all questions and Signing and Delivering a Copy to Buyer.

RPA REVISED 12/24 (PAGE 7 OF 17) Buyer's Initials / Seller's Initials / CALIFORNIA RESIDENTIAL PURCHASE AGREEMENT AND JOINT ESCROW INSTRUCTIONS (RPA PAGE 7 OF 17) Produced with Lone Wolf Transactions (zipForm Edition) 717 N Harwood St, Suite 2200, Dallas, TX 75201 www.lwolf.com 1051 E El Monte Way, Dinuba, CA 93618 July 31, 2025
City of Dinuba
Authentisign ID: 80186498-E56E-F011-8DCA-00224822F75A Authentisign ID: C2CAED2C-7D71-F011-8DCA-00224822F75A

Property Address: Date:
(4) In the event Seller or Seller's Agent, prior to Close Of Escrow, becomes aware of adverse conditions materially affecting the Property, or any material inaccuracy in disclosures, information or representations previously provided to Buyer under this paragraph, Seller shall, in writing, promptly provide a subsequent or amended TDS, Seller Property Questionnaire or other document, in writing, covering those items. Any such document shall be deemed an amendment to the TDS or SPQ.

However, a subsequent or amended disclosure shall not be required for conditions and material inaccuracies of which Buyer is otherwise aware, or which are discovered by Buyer or disclosed in reports or documents provided to or ordered and paid for by Buyer.

B. LEAD DISCLOSURES:
(1) Seller shall, within the time specified in paragraph 3N(1), for any residential property built before January 1, 1978, unless exempted by Law, Deliver to Buyer a fully completed Federal Lead-Based Paint Disclosures (C.A.R. Form LPD) and pamphlet (“Lead Disclosures”).
(2) Buyer shall, within the time specified in paragraph 3L(3), have the opportunity to conduct a risk assessment or to inspect for the presence of lead-based paint hazards.

C. HOME FIRE HARDENING DISCLOSURE AND ADVISORY: For any transaction where a TDS is required, the property is located in a high or very high fire hazard severity zone, and the home was constructed before January 1, 2010 , Seller shall, within the time specified in paragraph 3N(1), Deliver to Buyer: (i) a home hardening disclosure required by law; and (ii) a statement of features of which the Seller is aware that may make the home vulnerable to wildfire and flying embers; and (iii) a final inspection report regarding compliance with defensible space requirements if one was prepared pursuant to Government Code § 51182 (C.A.R. Form FHDS).

D. DEFENSIBLE SPACE DISCLOSURE AND ADDENDUM: For any transaction in which a TDS is required and the property is located in a high or very high fire hazard severity zone, Seller shall, within the time specified in paragraph 3N(1), Deliver to Buyer (i) a disclosure of whether the Property is in compliance with any applicable defensible space laws designed to protect a structure on the Property from fire; and (ii) an addendum allocating responsibility for compliance with any such defensible space law (C.A.R. Form FHDS).

E. WAIVER PROHIBITED: Waiver of Statutory, Lead, and other Disclosures in paragraphs 11A(1), 11B, 11C, and 11D are prohibited by Law.

F. RETURN OF SIGNED COPIES: Buyer shall, within the time specified in paragraph 3L(5) OR 5 Days after Delivery of any disclosures specified in paragraphs 11A, B, C or D, and defensible space addendum in paragraph 11D, whichever is later, return Signed Copies of the disclosures, and if applicable, addendum, to Seller.

G. TERMINATION RIGHTS:
(1) Statutory and Other Disclosures: If any disclosure specified in paragraphs 11A, B, C, or D, or subsequent or amended disclosure to those just specified, is Delivered to Buyer after the offer is Signed, Buyer shall have the right to terminate this Agreement within 3 Days after Delivery in person, or 5 Days after Delivery by deposit in the mail, or by an electronic record or email satisfying the Uniform Electronic Transactions Act (UETA), by giving written notice of rescission to Seller or Seller's Authorized Agent. If Buyer does not rescind within this time period, Buyer has been deemed to have approved the disclosure and shall not have the right to cancel.
(2) Defensible Space Compliance: If, by the time specified in paragraph 11F, Buyer does not agree to the terms regarding defensible space compliance Delivered by Seller, as indicated by mutual signatures on the FHDS, then Seller, after first Delivering a Notice to Buyer to Perform, may cancel this Agreement.

H. WITHHOLDING TAXES: Buyer and Seller hereby instruct Escrow Holder to withhold the applicable required amounts to comply with federal and California withholding Laws and forward such amounts to the Internal Revenue Service and Franchise Tax Board, respectively. However, no federal withholding is required if, prior to Close Of Escrow, Seller Delivers (i) to Buyer and Escrow Holder a fully completed affidavit (C.A.R. Form AS) sufficient to avoid withholding pursuant to federal withholding Law (FIRPTA); OR (ii) to a qualified substitute (usually a title company or an independent escrow company) a fully completed affidavit (C.A.R. Form AS) sufficient to avoid withholding pursuant to federal withholding Law AND the qualified substitute Delivers to Buyer and Escrow Holder an affidavit signed under penalty of perjury (C.A.R. Form QS) that the qualified substitute has received the fully completed Seller's affidavit and the Seller states that no federal withholding is required; OR (iii) to Buyer other documentation satisfying the requirements under Internal Revenue Code § 1445 (FIRPTA). No withholding is required under California Law if, prior to Close Of Escrow, Escrow Holder has received sufficient documentation from Seller that no withholding is required, and Buyer has been informed by Escrow Holder.

I. MEGAN'S LAW DATABASE DISCLOSURE: Notice: Pursuant to § 290.46 of the Penal Code, information about specified registered sex offenders is made available to the public via an Internet Web site maintained by the Department of Justice at www.meganslaw.ca.gov. Depending on an offender's criminal history, this information will include either the address at which the offender resides or the community of residence and ZIP Code in which he or she resides. (Neither Seller nor Agent are required to check this website. If Buyer wants further information, Agent recommends that Buyer obtain information from this website during Buyer's investigation contingency period. Agents do not have expertise in this area.) J. NOTICE REGARDING GAS AND HAZARDOUS LIQUID TRANSMISSION PIPELINES: This notice is being provided simply to inform you that information about the general location of gas and hazardous liquid transmission pipelines is available to the public via the National Pipeline Mapping System (NPMS) Internet Web site maintained by the United States Department of Transportation at http://www.npms.phmsa.dot.gov/. To seek further information about possible transmission pipelines near the Property, you may contact your local gas utility or other pipeline operators in the area. Contact information for pipeline operators is searchable by ZIP Code and county on the NPMS Internet Website. (Neither Seller nor Agent are required to check this website. If Buyer wants further information, Agent recommends that Buyer obtain information from this website during Buyer's investigation contingency period. Agents do not have expertise in this area.) K. NATURAL AND ENVIRONMENTAL HAZARDS: Seller shall, within the time specified in paragraph 3N(1), if required by Law:
(i) Deliver to Buyer the earthquake guide and environmental hazards booklet, and for all residential property with 1-4 units and any manufactured or mobile home built before January 1, 1960, fully complete and Deliver the Residential Earthquake Risk Disclosure Statement; and (ii) even if exempt from the obligation to provide a NHD, disclose if the Property is located in a Special Flood Hazard Area; Potential Flooding (Inundation) Area; Very High Fire Hazard Zone; State Fire Responsibility Area; Earthquake Fault Zone; Seismic Hazard Zone; and (iii) disclose any other zone as required by Law and provide any other information required for those zones.

L. CONDOMINIUM/PLANNED DEVELOPMENT DISCLOSURES:
(1) Seller shall, within the time specified in paragraph 3N(1), disclose to Buyer whether the Property is a condominium or is located in a planned development, other common interest development, or otherwise subject to covenants, conditions, and restrictions (C.A.R. Form SPQ or ESD).

RPA REVISED 12/24 (PAGE 8 OF 17) Buyer's Initials / Seller's Initials / CALIFORNIA RESIDENTIAL PURCHASE AGREEMENT AND JOINT ESCROW INSTRUCTIONS (RPA PAGE 8 OF 17) Produced with Lone Wolf Transactions (zipForm Edition) 717 N Harwood St, Suite 2200, Dallas, TX 75201 www.lwolf.com 1051 E El Monte Way, Dinuba, CA 93618 July 31, 2025
City of Dinuba
Authentisign ID: 80186498-E56E-F011-8DCA-00224822F75A Authentisign ID: C2CAED2C-7D71-F011-8DCA-00224822F75A

Property Address: Date:
(2) If the Property is a condominium or is located in a planned development or other common interest development with a HOA, Seller shall, within the time specified in paragraph 3N(3), order from, and pay any required fee as specified in paragraph 3Q(12) for the following items to the HOA (C.A.R. Form HOA-IR): (i) Copies of any documents required by Law (C.A.R. Form HOA-RS); (ii) disclosure of any pending or anticipated claim or litigation by or against the HOA; (iii) a statement containing the location and number of designated parking and storage spaces; (iv) Copies of the most recent 12 months of HOA minutes for regular and special meetings; (v) the names and contact information of all HOAs governing the Property; (vi) pet restrictions; and (vii) smoking restrictions (“CI Disclosures”). Seller shall itemize and Deliver to Buyer all CI Disclosures received from the HOA and any CI Disclosures in Seller's possession. Seller shall, as directed by Escrow Holder, deposit funds into escrow or direct to HOA or management company to pay for any of the above.

M. SOLAR POWER SYSTEMS: For properties with any solar panels or solar power systems, Seller shall, within the time specified in paragraph 3N(1), Deliver to Buyer all known information about the solar panels or solar power system. Seller shall use the Solar Advisory and Questionnaire (C.A.R. Form SOLAR).

N. BALCONIES, EXTERIOR STAIRWAYS AND OTHER ELEVATED ELEMENTS: For properties with any building containing 3 or more dwelling units with elevated balconies, stairways or other elements, Seller shall, within the time specified in paragraph 3N(1), Deliver to Buyer the Wooden Balcony and Stairs Addendum (C.A.R. Form WBSA) and comply with its terms.

O. KNOWN MATERIAL FACTS: Seller shall, within the time specified in paragraph 3N(1), DISCLOSE KNOWN MATERIAL FACTS AND DEFECTS affecting the Property, including, but not limited to, known insurance claims within the past five years, or provide Buyer with permission to contact insurer to get such information (C.A.R. Form ARC), and make any and all other disclosures required by Law.

12. BUYER'S INVESTIGATION OF PROPERTY AND MATTERS AFFECTING PROPERTY:

A. Buyer shall, within the time specified in paragraph 3L(3), have the right, at Buyer's expense unless Otherwise Agreed, to conduct inspections, investigations, tests, surveys and other studies (“Buyer Investigations”).

B. Buyer Investigations include, but are not limited to:
(1) Inspections regarding any physical attributes of the Property or items connected to the Property, such as:
(A) A general home inspection.
(B) An inspection for lead-based paint and other lead-based paint hazards. (C) An inspection specifically for wood destroying pests and organisms. Any inspection for wood destroying pests and organisms shall be prepared by a registered Structural Pest Control company; shall cover the main building and attached structures; may cover detached structures; shall NOT include water tests of shower pans on upper level units unless the owners of property below the shower consent; shall NOT include roof coverings; and, if the Property is a unit in a condominium or other common interest subdivision, the inspection shall include only the separate interest and any exclusive-use areas being transferred, and shall NOT include common areas; and shall include a report (“Pest Control Report”) showing the findings of the company which shall be separated into sections for evident infestation or infections (Section 1) and for conditions likely to lead to infestation or infection (Section 2). (D) Any other specific inspections of the physical condition of the land and improvements. (2) Investigation of any other matter affecting the Property, other than those that are specified as separate contingencies. Buyer Investigations do not include, among other things, an assessment of the availability and cost of general homeowner's insurance, flood insurance, and fire insurance. See, Buyer's Investigation Advisory (C.A.R. Form BIA) for more.

C. Without Seller's prior written consent, Buyer shall neither make nor cause to be made: (i) invasive or destructive Buyer Investigations, except for minimally invasive testing required to prepare a Pest Control Report, which shall not include any holes or drilling through stucco or similar material; or (ii) inspections by any governmental building or zoning inspector or government employee, unless required by Law.

D. Seller shall make the Property available for all Buyer Investigations. Seller is not obligated to move any existing personal property.

Seller shall have water, gas, electricity and all operable pilot lights on for Buyer's Investigations and through the date possession is delivered to Buyer. Buyer shall, (i) by the time specified in paragraph 3L(3), complete Buyer Investigations and satisfy themselves as to the condition of the Property, and either remove the contingency or cancel this Agreement, and (ii) by the time specified in paragraph 3L(3) or 3 Days after receipt of any Investigation report, whichever is later, give Seller at no cost, complete Copies of all such reports obtained by Buyer, which obligation shall survive the termination of this Agreement. This Delivery of Investigation reports shall not include any appraisal, except an appraisal received in connection with an FHA or VA loan.

E. Buyer indemnity and Seller protection for entry upon the Property: Buyer shall: (i) keep the Property free and clear of liens; (ii) repair all damage arising from Buyer Investigations; and (iii) indemnify and hold Seller harmless from all resulting liability, claims, demands, damages and costs. Buyer shall carry, or Buyer shall require anyone acting on Buyer's behalf to carry, policies of liability, workers' compensation and other applicable insurance, defending and protecting Seller from liability for any injuries to persons or property occurring during any Buyer Investigations or work done on the Property at Buyer's direction prior to Close Of Escrow. Seller is advised that certain protections may be afforded Seller by recording a “Notice of Non-Responsibility” (C.A.R.

Form NNR) for Buyer Investigations and work done on the Property at Buyer's direction. Buyer's obligations under this paragraph shall survive the termination of this Agreement.

13. TITLE AND VESTING:

A. Buyer shall, within the time specified in paragraph 3N(1), be provided a current Preliminary Report by the person responsible for paying for the title report in paragraph 3Q(8). If Buyer is responsible for paying, Buyer shall act diligently and in good faith to obtain such Preliminary Report within the time specified. The Preliminary Report is only an offer by the title insurer to issue a policy of title insurance and may not contain every item affecting title. The company providing the Preliminary Report shall, prior to issuing a Preliminary Report, conduct a search of the General Index for all Sellers except banks or other institutional lenders selling properties they acquired through foreclosure (REOs), corporations, and government entities.

B. Title is taken in its present condition subject to all encumbrances, easements, covenants, conditions, restrictions, rights and other matters, whether of record or not, as of the date of Acceptance except for: (i) monetary liens of record unless Buyer is assuming those obligations or taking the Property subject to those obligations; and (ii) those matters which Seller has agreed to remove in writing. For any lien or matter not being transferred upon sale, Seller will take necessary action to deliver title free and clear of such lien or matter.

C. Seller shall within 7 Days after request, give Escrow Holder necessary information to clear title.

D. Seller shall, within the time specified in paragraph 3N(1), disclose to Buyer all matters known to Seller affecting title, whether of record or not.

E. If Buyer is a legal entity and the Property purchase price is at least $300,000 and the purchase price is made without a bank loan or similar form of external financing, a Geographic Targeting Order (GTO) issued by the Financial Crimes Enforcement Network, U.S. Department of the Treasury, requires title companies to collect and report certain information about the Buyer, depending on where the Property is located. Buyer agrees to cooperate with the title company's effort to comply with the GTO.

RPA REVISED 12/24 (PAGE 9 OF 17) Buyer's Initials / Seller's Initials / CALIFORNIA RESIDENTIAL PURCHASE AGREEMENT AND JOINT ESCROW INSTRUCTIONS (RPA PAGE 9 OF 17) Produced with Lone Wolf Transactions (zipForm Edition) 717 N Harwood St, Suite 2200, Dallas, TX 75201 www.lwolf.com 1051 E El Monte Way, Dinuba, CA 93618 July 31, 2025
City of Dinuba
Authentisign ID: 80186498-E56E-F011-8DCA-00224822F75A Authentisign ID: C2CAED2C-7D71-F011-8DCA-00224822F75A