Attachment D.1 - PWS.pdf

Learn more at fema.gov June 2021 1

Federal Emergency Management Agency

PERFORMANCE WORK STATEMENT (PWS) FOR:

Unmanned Aircraft Systems Services

DEPARTMENT OF HOMELAND SECURITY (DHS)

1.0 General

1.1 Background

The mission of the Federal Emergency Management Agency (FEMA) is to help people before, during, and after disasters. To execute this mission, FEMA utilizes programs and activities that support the reduction of loss of life and property and protects the Nation from all hazards, including natural disasters, acts of terrorism, and other man-made disasters, by leading and supporting the Nation in a risk based, comprehensive emergency management system of preparedness, response, recovery, and mitigation.

The FEMA Response Directorate coordinates and provides the core federal disaster response capabilities needed to save lives, reduce suffering, and protect property in communities throughout the Nation that have been overwhelmed by the impact of a major disaster or emergency, regardless of cause. The Response Directorate ensures that federal emergency response systems and capabilities are properly poised to support states and overwhelmed communities.

To support emergencies (declared or undeclared), disaster response operations and other national events or incidents, within the United States, its territories and possessions, FEMA may require Unmanned Aircraft Systems (UAS) services for response and recovery operations. UAS include the unmanned aircraft and the equipment necessary for the safe and efficient operation of that aircraft.

This mission relies significantly on the strategic use of industry leading enterprise-class information technologies (such as cloud computing platforms, databases, geospatial and image processing and analysis software, and flexible application development and programming interfaces) and specialized methodologies that enable efficient and secure collection, analysis, storage, visualization, and communication of complex geospatial information- such as remote sensing, crowdsourcing, topographical and infrastructure data.

FEMA requires a contracted source of advanced UAS operation services for various types of UAS to successfully execute the services, described in this Performance Work Statement (PWS). Expertise will be leveraged across a range of full lifecycle data through imagery analysis and geospatial analytics in support of these tasks.

This contract will enable FEMA to provide timely and efficient support to Stafford and non-Stafford requirements. The Air Operations Program Office (AOPO) will oversee, organize, and unify all FEMA aviation-related efforts and seek to employ innovative capabilities and technologies to reduce disaster risk, stabilize community lifelines, and support survivors and communities.

For purposes of this PWS, the term state (e.g., one of the 50 in the United States) will encompass all relevant tribes or territories.

1.2 Objective

This PWS defines the requirements for the provision, operation, and maintenance of UAS in support of emergencies (declared or undeclared), disaster response and recovery operations within the United States and its territories and possessions. The contractor shall deliver UAS capabilities that enhance response and recovery capabilities, situational awareness, surveillance, reconnaissance, and data collection in concert with FEMA’s objectives. This includes ensuring compliance with all applicable federal, state, and local regulations, as well as adherence to safety, security, and operational standards.

The goal is to provide reliable, efficient, and cost-effective UAS services that meet mission-critical requirements while maintaining the highest levels of quality and performance.

1.3 Scope

The contractor shall be tasked to provide specialized UAS services that will support operations requiring aerial capabilities. These services may include imagery collection, confined space accessibility and reconnaissance, geographical mapping, remote sensing (possibly in Chemical, Biological, Radiological, and Nuclear (CBRN) environments), delivery of resources/commodities, tactical communications, and other specialized tasks outlined in an executed task order under this PWS.

The contractor shall provide all personnel, training, supervision, equipment, materials, facilities, supplies, and services necessary to perform UAS services in support of the tasks and deliverables described in this PWS, unless otherwise specified as government-furnished materials or services.

The contractor shall ensure the safe, efficient, and compliant operation of UAS platforms in accordance with applicable federal, state, and local regulations, and must provide certification and accreditation support to acquire Authority to Operate (ATO) and meet FEMA, DHS, NIST, and other controls as required.

1.4 Period of Performance

The period of performance is for up to a 12-month base period starting at contract award, with four, (4) 12-month option periods. Services may be required to be performed up to 24 hours a day, seven days a week, including federal holidays.

1.5 Place of Performance

The place of performance will vary depending on operational needs and will be cited in each task order issued under the contract, Additionally, the contractor shall provide support services throughout the geographical United States inclusive of its Territories, Compacts of Free Association, and possessions.

1.6 Hours of Operation

Following task order issuance, the contractor shall be responsible for providing UAS and qualified personnel, accepting taskings and performing UAS services up to 24 hours a day, 7 days a week, who are familiar with the contract's terms and conditions. The Contracting Officer (CO) will determine the hours of services when other than up to 24 hour/7-day service is required.

1.7 Applicable Documents

All applicable federal aviation regulations, policies, and requirements shall be adhered to and followed by the contractor and support staff. Work to be accomplished under this PWS shall be performed using best practices and guidelines.

In addition, the contractor shall comply with all provisions of applicable statutes, tenders of service, and contract terms as such may affect flight safety, as well as with all applicable FAA Regulations, airworthiness, certifications, directives, orders, qualifications, rules, reporting requirements and standards promulgated under the Federal Aviation Act of 1958, as amended. Compliance with published standards may not, standing alone, constitute compliance with generally accepted standards of airmanship, training, or maintenance.

1.8 Performance Requirements Summary

This contract includes a Performance Requirements Summary (PRS) at PWS 6.0. The PRS plays an integral role in the administration of the contract. In addition to any applicable inspection clauses or other related terms and conditions contained in the contract, the PRS shall serve as a primary tool for inspection and acceptance of services as facilitated by the Contracting Officer’s Representative (COR).

Evaluation of the contractor’s overall performance shall be in accordance with the performance standards set forth in the PRS, and will be conducted by the COR. The PRS constitutes a material aspect of the contract and will not be changed or otherwise modified without prior written approval of the Contracting Officer (CO).

2.0 Specific Requirements/Tasks

(a) The contractor shall provide capabilities of UAS that will be used to perform services to include, but not limited to:

High resolution imaging Confined space reconnaissance Standard RGB imagery for general visual analysis Data collection Establish and integrate Remote sensing (possibly in CBRN environments) Web-based storage and data services Tactical and non-tactical communications Commodities movement Debris reconnaissance Additional and emerging capabilities and technology (e.g. Light Detection and Ranging

(LIDAR), Hyperspectral Imaging (HSI)) to include technical assistance/subject matter expert assistance

(b) The contractor shall provide full lifecycle data management and governance support to facilitate efficient and secure data acquisition, integration, standardization, processing, analysis, quality control, disclosure avoidance, dissemination, storage, archiving, recovery, and maintenance of disparate data (including from business systems, ground-based and aerial sensors, mobile and crowd sourced systems, among others).

(c) The contractor shall implement appropriate safeguards to ensure the confidentiality, integrity, security, and storage of collected data, adhering to DHS policies and applicable federal laws governing the protection of sensitive information, as well as provide continuous monitoring of utilization, performance, compliance of computing infrastructures and cloud systems and support the development and use of tools and services to monitor and automatically identify, document, and remedy changes or issues related to security, compliance, bugs, vulnerabilities and for tracking and measurement of the utilization of system components, web services, data feeds, other statistics. Any Personally Identifiable Information (PII), a subset of Controlled Unclassified Information (CUI), contained within associated data shall be handled in strict compliance with the security and privacy requirements outlined in the relevant section of this contract.

(d) The contractor shall provide support in the development, implementation, and operation and maintenance of risk-based models; analytic workflows; web applications, and tools and platforms to aid FEMA program areas in prioritizing and maximizing limited resources in support of steady-state, emergent, and/or crisis events.

(e) The contractor shall interface with designated technical/task monitors as defined at the task order level.

(f) The contractor shall establish and maintain a complete Quality Control Plan no later than 60 days following contract award. Updates will be made following any mishap as requested by the COR.

(g) The contractor shall develop an Authority To Operate (ATO), and build or help contribute to a Security Requirements Traceability Matrix (SRTM) upon contract award or at the request of the

CO.

(h) The contractor shall retain copies of flight logs, narrative reports, as well as any related data and documentation of operations. These records shall be maintained for three years beyond the calendar year of task action. The contractor will be required to maintain detailed logs of all CUI/PII data, including storage locations, access records, and disposal dates. Periodic audits will be conducted to ensure compliance with CUI/PII retention and handling requirements.

(i) The contractor shall provide imagery and remotely sensed data (e.g., still images, video, and environmental monitoring). Imagery required may be varied based upon requirements or usage (e.g., standard definition, 2-D, 3-D, high-definition, multi-spectral, etc.). Unless otherwise directed, the contractor will ensure that all recorded data and imagery captured is correctly categorized, labeled, and stored (using a protected, web-based storage and data services solution); and will be handled in compliance with all privacy and cybersecurity requirements; and ensure that all remotely sensed imagery and data are forwarded to the Response Geospatial Office (RGO) which is the office of primary responsibility for all such imagery and data collected via UAS for FEMA.

(j) The contractor shall provide remote sensing for measuring, detecting, or in CBRN environments.

(k) The contractor shall provide geographic mapping, terrain analysis, and surveying using UAS-mounted cameras and/or sensors, generate elevation models contour maps, and 3D reconstruction of landscapes, and provide real-time geospatial data for mission planning and situational awareness.

(l) The contractor shall support damage assessments by imaging and/or measuring damage to infrastructure, buildings, and critical facilities following natural disaster, monitor environmental conditions such as flooding, wildfires, or hazardous material spills, and provide aerial imagery and situational awareness.

(m) The contractor shall perform perimeter surveillance and monitoring for critical infrastructure, facilities, or event security; detect unauthorized activity or intrusions using UAS-mounted cameras and sensors; perform tasks tailored to unique mission requirements such as confined space reconnaissance (camera and/or sensor based); and, provide customized UAS solutions for specific operational challenges.

(n) The contractor shall provide support in performing aerial delivery of resources and/or commodities, providing all necessary material, equipment, and personnel to facilitate the loading, unloading, and delivery of cargo. The contractor shall also be responsible for operating equipment that aligns with the technical specifications and operational requirements of the UAS platforms.

(o) The contractor shall leverage emerging technologies (e.g., Light Detection and Ranging (LIDAR), Hyperspectral Imaging (HSI)), and other technologies as they may acquire) and will include all necessary technical assistance/subject matter expert assistance needed to leverage the technology solution, as applicable. UAS are part of a fast-growing collection of integrated, emerging technologies with tremendous potential to revolutionize many aspects of emergency management and public safety. As technologies for UAS platforms become available and mature, the Air Operations Program Office will look to leverage such new technologies to meet Agency requirements when relevant to the operational mission.

(p) The contractor shall provide debris reconnaissance.

(q) The contractor shall provide technical assistance and information designed to provide maximum coordination and expeditious, efficient and effective utilization of UAS assets in support of FEMA disaster or non-disaster operations. Such technical assistance shall consist of technical personnel to participate in meetings and exercises and preparing or assisting in the preparation of informational material, including but not limited to manuals, documents, listings, reports, specifications and other data as required.

(r) The contractor shall provide UAS with communications capabilities (voice, data, WiFi) to support government operations in tactical and non-tactical conditions. These capabilities shall enable real-time data transmission, communication, and operational coordination in both standard and austere environments.

2.1 Activation and Availability Requirements

Upon issuance of a task order, the contractor and requested UAS shall be activated and positioned at the location specified by the government within 24 hours (or as agreed upon by FEMA) along with all necessary equipment required to meet aircraft performance limitations and mission requirements.

The contractor shall activate and provide sufficient personnel, UAS platforms, supporting equipment, and materials necessary to support operations, as ordered.

The contractor shall be able to execute assigned flight operation taskings within a 2-hour response time.

The contractor shall promptly notify the COR or CO of any changes.

The contractor shall provide UAS operations within a specified mile radius and location as outlined in the task order. FEMA may facilitate access to restricted areas to enable operations. Adjustments to the coverage area may be required based on real-time updates from FEMA.

2.2 Equipment Liability Limitation

The contractor shall be responsible for the proper operation, maintenance, and handling of all UAS, and associated equipment provided under this contract. The contractor shall be liable for any damage, loss, or malfunction of UAS equipment resulting from negligence, improper maintenance, or failure to comply with operational guidelines.

The contractor shall be responsible for any loss and/or damage to equipment. Liability for loss and/or damages shall be commensurate with standard commercial service.

The contractor shall notify the technical/task monitor and COR/CO of any damage, loss, or malfunction of UAS equipment. Minimally, the notification shall include:

A detailed description of the incident An assessment of the cause of the damage or loss

Additional reporting requirements may be specified following contract/task order award.

2.3 Delays and Diversions

A delay of the UAS team caused by factors beyond the control and without the fault or negligence of the contractor, shall be considered as contractor-uncontrollable; a delay for any other reason shall be considered contractor-controllable. When a delay or deviation from task/schedule occurs at any point of a mission for any reason, the contractor shall immediately notify the COR.

Contractors are held responsible during controllable delays. If the delay is determined to be chargeable against the contractor, the contractor shall be responsible for any other added costs such as, but not limited to:

Provisions for security of UAS Equipment, and cargo All other costs associated with said cancellation

3.0 Contractor Personnel

The contractor shall provide qualified personnel to perform all requirements specified in this PWS.

The contractor shall demonstrate that both the organization and proposed key personnel will be able to successfully complete the efforts and tasks under this acquisition (demonstrable experience working with state, local, tribal, territory and federal governments; demonstrable experience in rapid execution of contractor operations, including: pre and post incident (hurricanes, earthquakes, tsunami etc.)).

The government reserves the right to assess the technical skills, competencies, and suitability of contractor personnel and to request personnel replacements in writing if the individual’s qualifications or performance are judged deficient.

The contractor shall submit in writing the availability of key personnel who will be assigned to a task before disaster activations are declared. Key personnel are all individuals who will support these tasks in a primary capacity, to include full and part-time personnel.

3.1 Contractor Management of Qualified Personnel

The contractor shall be responsible for managing and overseeing the activities of all contractor personnel, as well as subcontractor efforts used in performance of this contract along with providing qualified personnel to meet both surge and disaster requirements. The contractor's management responsibilities shall include all activities necessary to ensure the accomplishment of timely and effective support performed in accordance with the requirements contained in the PWS.

3.2 Key Personnel

The Contractor’s Operations Project Manager (COPM) is hereby designated as key personnel for this requirement. The government may designate additional key personnel during contract performance.

The COPM shall be the primary technical and managerial interface between the contractor, CO and COR.

The Contracts Administration Program Manager (CAPM) shall act for the contractor when the COPM is absent. The COPM or CAPM shall have full authority to act for the contractor on all contract matters relating to daily operations.

The COPM or alternate must be available and actively engaged on a 24/7 basis pre-issuance of the task order while operations are starting up as well as throughout the lifecycle of the task order as specified herein; to meet with government personnel on a 24/7 basis to discuss problems and strategize operational approaches to meet mission needs.

The COPM and/or alternate shall meet with the CO and COR as often as determined necessary during operations by the FEMA CO to maintain satisfactory performance and to resolve other issues pertaining to FEMA/contractor procedures. Virtual meetings are acceptable and encouraged. At these meetings, a mutual effort will be made to resolve all problems identified.

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

The justification must include a detailed explanation of the circumstances, a complete resume for the proposed substitute, and other information requested by the CO necessary to approve or disapprove the substitution. An interview may also be required. No substitutions shall be made of accepted key personnel apart from sudden illness or death or termination of employment. The CO and the COR will evaluate such requests and promptly notify the contractor of approval or disapproval in writing.

The contractor shall identify key personnel for the total period of a contract. The contractor shall ensure the continued assignment of key personnel throughout the duration of the contract, unless substitution is authorized by the CO.

The designated key contract personnel, duties and responsibilities and minimum qualifications are listed below:

The COPM must possess a range of qualifications to effectively lead a project to successful completion.

These qualifications include:

Strong organizational and planning skills to set, manage, and meet project deadlines Excellent leadership and team management abilities to lead a team of diverse individuals and inspire them towards achieving common goals Exceptional communication skills to facilitate clear and effective communication among team members and stakeholders Ability to use critical thinking and problem-solving skills to identify potential issues and develop effective solutions Good understanding and experience with project management tools and methodologies to apply them effectively in different projects Strong financial management skills to develop and manage project budgets Capability to handle multiple tasks and projects simultaneously and efficiently Excellent negotiation and decision-making skills to resolve conflicts and make crucial project decisions

These qualifications are essential for ensuring that the project manager can manage the project on time and on budget, gain the confidence of all stakeholders, and lead a highly motivated team to a successful outcome.

3.3 UAS Operators

The contractor shall provide sufficient qualified personnel to execute assigned operations and perform requirements specified in the PWS. For the operation of UAS, the contractor shall ensure that all personnel involved in the mission meet the following requirements:

Remote Pilot in Command (RPIC) – the RPIC must hold current certification as required by the government, possess demonstrated experience operating UAS of similar size, type, and complexity to those specified in the contract, and must comply with all applicable FAA regulations and mission specific requirements.

Visual Observer (VO) – the VO must be trained and qualified to assist the RPIC in maintaining visual line of sight with the UAS during operations, as required by FAA, and visual observers must have a clear understanding of airspace awareness, situational monitoring, and communication protocols.

Maintenance personnel (MP) – the MP must be certified and trained to perform inspections, repairs, and maintenance on the specific UAS platforms used under this contract, and maintenance logs and record must be maintained in accordance with FAA regulations and contract requirements.

Mission support staff – additional personnel such as payload operators or data analysts, must be qualified and trained to operate mission specific equipment (e.g. cameras, sensors, or communication systems) integrated with the UAS, and support staff must adhere to all safety and operational protocols outlined in the PWS.

Training and currency – FEMA UAS operators must obtain FAA Remote Pilot Certification (14 CFR 107 Small UAS) which demonstrates the operator understands Federal Aviation Administration regulations, operating requirements, and procedures. The contractor shall provide documentation of training certifications, and currency for all personnel to the COR, as required.

3.4 Government Key Personnel

FEMA contract program office staff includes:

3.4.1 Contracting Officer

The CO has ultimate contracting authority, and all contracting issues fall under their purview. COs are responsible for administering the contract, including the resolution of disputes and protests, and terminating and/or closing out of the contract. COs are responsible for ensuring all contractors receive impartial, fair, and equitable treatment.

3.4.2 Contracting Officer’s Representative

CORs are specifically appointed by the CO and delegated limited responsibilities for inspecting and accepting work performed by the contractor. CORs are responsible for assisting and advising the CO on technical matters relating to issuing task orders and administering the contract. CORs are not authorized to change any terms of the contract.

3.4.3 Program Manager

The Program Manager (PM) is appointed by the FEMA Component Acquisition Executive and ensures the contract meets cost, schedule, and performance goals. The PM is responsible to articulate steady-state and operational requirements on behalf of the agency, assess impacts and apply any mitigation needed to ensure objectives are met. The contract COR reports to the PM. The PM does not replace the:

Contracting Specialist, COR, or CO for this contract. The PM is not authorized to change any terms of the contract. Only the CO can give the contractor a notice to proceed or an executed task order.

3.4.4 Technical/Task Monitor

At the task order level, or following a task order award, the CO or the COR shall appoint technical/task monitors. Technical/task monitors do not have COR authority but will assist the COR in monitoring individual tasks performed by the contractor. In many cases the designated FEMA regional point of contact or field level federal air operations personnel, will assist the COR in defining the requirements of the task orders issued under the contract and may inspect subsequent work products.

4.0 Employee Identification

The contractor shall comply with all government escort rules and requirements. All contractor employees shall identify themselves as contractors when their status is not readily apparent (i.e., in meetings, when answering a government telephone, in email messages, etc.) and always display all identification and visitor badges in plain view above the waist.

4.1 Employee Conduct

All contractor employees and their representatives are required to conduct themselves in a professional manner while servicing and performing the terms of the contract. At any time during the performance of a task order, the CO may order the contractor to remove personnel from further performance under the contract for security reasons, misconduct, or violation of regulations.

4.2 Removing Employees for Misconduct or Security Reasons

The government may, at its sole discretion, via the CO, direct the contractor to remove any contractor employee from DHS facilities for misconduct or security reasons. In the event it becomes necessary to replace any contractor employee for any of the above reasons, the contractor shall bear all costs associated with such removal including the costs for replacement of any employee so removed. Removal does not relieve the contractor of the responsibility to continue providing the services required under the contract. The CO may provide the contractor with a written explanation to support any request to remove an employee.

4.3 Reference Documents

The following documents will be used by the contractor in performing the work described in this document:

41 CFR Part 102-33 Management of Government Aircraft

DHS Management Directive-0020-1 Aviation Management and Safety 2005

FEMA Directive 104-21-0006 FEMA Air Operations Program

FEMA Air Operations Guide, April 2025

FEMA AOS-01 Management Standards Memo (pending approval)

FEMA AOS-02 Operations Standards Memo (pending approval)

FEMA AOS-03 Training Standards Memo (pending approval)

FEMA AOS-04 Safety Standards Memo (pending approval)

FEMA AOS-05 Maintenance Standards Memo (pending approval)

Once the standards are finalized, they must be used as guidance for the contractor’s operations in support of this contract.

4.4 Other Applicable Conditions

The contractor shall provide sufficient qualified personnel to execute assigned operations and perform the requirements specified. Promoting safe operations is a duty of all personnel. All operations should be employed in the safest manner practicable, without taking unnecessary risks.

4.4.1 Security

Additional security requirements may be specified in each task order. The contractor shall ensure all personnel assigned to a task order do not have criminal records and are eligible for appropriate approval to enter designated locations. Contractor personnel may be required to carry a public trust clearance.

As part of the performance of a task order, the contractor may be required to work with other entities including other government contractors or Other Federal Agencies (OFAs).

Information made available to the contractor by the government for the performance of this effort shall be used only for those purposes specified and shall not be used in any other way without the written authorization of the CO.

4.4.2 Safety

Contractor personnel shall obey and follow all federal, state, local, tribal, territory, FEMA policy, rules, regulations and or laws regarding the safe operation of any UAS or other designated equipment.

It is the duty of all personnel to contribute to safe operations. Any identified safety hazard, whether procedural, operational, or maintenance related, should be corrected as soon as possible per the requirements set forth in the FEMA UAS Safety Standard.

The contractor shall support any of the FEMA emergency response team/task force or executive requirements, as described in this PWS, and comply with all applicable laws, regulations, standards, and commercial practices with the focus on safety and customer service.

The contractor shall conform to the safety requirements contained in this PWS for all activities related to the accomplishment of the work to include, but not limited to the following:

• Provide protection to government furnished property, if issued, to prevent damage during the period the property is under the control or in possession of the service provider.

• Include a clause in all subcontracts to require sub-service providers to comply with the safety provisions of this agreement.

4.5 Travel

The contractor shall manage and provide funding for all aspects of travel for the UAS team to include all travel costs, room, and board, etc. in accordance with federal travel regulations.

4.6 Post Award Conference

The contractor shall attend a post award conference with the CO and the stakeholder no later than five

(5) calendar days after award. The purpose of the post award conference, which will be chaired by the CO, to discuss technical and contracting objectives of this contract. The post award conference will be held via a virtual platform.

4.7 Continuity Plans

4.7.1 Business Continuity Plan

The contractor shall prepare and submit a Business Continuity Plan (BCP) to the government. The plan shall be due 30 business days after the date of award and will be updated on an annual basis. The BCP shall document contractor plans and procedures to maintain support during an emergency, including natural disasters and acts of terrorism. The BCP, at a minimum, shall include the following:

A description of the contractor’s emergency management procedures and policy A description of how the contractor will account for their employees during an emergency How the contractor will communicate with the government during emergencies A list of primary and alternate contractor points of contact, each with primary and alternate telephone numbers and email addresses.

Individual BCPs shall be activated after determining that an emergency has occurred, shall be operational within 24 hours of activation or as directed by the government, and shall be sustainable until the emergency is resolved, or the contract is terminated, whichever comes first. In case of a life-threatening emergency, the COR shall immediately contact the COPM to ascertain the status of any contractor personnel located in government-controlled space affected by the emergency. When any disruption of normal, daily operations occurs, the COPM and the COR shall promptly open an effective means of communication and verify:

Key points of contact (government and contractor) Temporary work locations (alternate office spaces, telework, virtual offices, etc.)

Means of communication available under the circumstances (e.g. email, webmail, telephone, FAX, courier, etc.)

Essential contractor work products expected to be continued, by priority

The government and COPM shall make use of the resources and tools available to continue contracted functions to the maximum extent possible under emergency circumstances. Contractors shall obtain approval from the CO prior to incurring costs over and above those allowed for under the terms of this contract. Regardless of contract type, and of work location, contractors performing work in support of authorized tasks within the scope of their contract shall charge those hours accurately in accordance with the terms of this contract.

4.7.2 Security Plan

The contractor shall prepare and submit a security plan to the government which shall be due 30 business days after the date of award and will be updated on an annual basis. The plan shall list measures to address security issues, including those to protect resources (i.e., people, equipment) and secure CUI/PII as required by law. This plan should cover access control, awareness and training, audit and accountability, configuration management, identification and authentication, incident response, maintenance, media protection, physical protection, personnel security, risk assessment, security assessment, communications protection, information integrity, and include a system security plan. The system security plan must document how required security controls are met covering a continuous monitoring strategy, incident response plan, supply chain risk management, and covers potential for the development of a plan of action and milestones that outlines the contractor’s plan to correct any deficiencies in the required security controls, at a minimum.

4.8 Reporting

4.8.1 General Reporting Requirements

The contractor shall provide all written reports in electronic format with read/write capability using applications that are compatible with DHS workstations (Microsoft Office Applications).

4.8.2 Status Reporting

The contractor shall notify the CO, immediately or as soon as possible, of any issues or problems requiring a government response. The contractor shall retain appropriate number of key personnel who have the necessary knowledge, skills, ability, and experience to effectively manage the task order requirements. The contractor shall be proactive in identifying problem areas and providing corrective actions.

Following task order issuance, the contractor shall provide status reports, as defined by the task order, to the Air Operations Branch Director (or designee) and to the CO and COR which shall include, but not limited to:

A summary of the work accomplished (e.g., sorties, flight hours, equipment used, registration number, pilot name, flight plan summary, etc.)

System and crew location(s) Operating system status Any current and foreseeable problems and proposed corrective actions

Upon request, the contractor shall provide a UAS strategy to document area operations. Minimally, the strategy will incorporate coordination activities of responding entities/personnel performing UAS missions within a designated area of operation with additional specifics to be requested following task order issuance.

4.8.3 UAS Reporting

All UAS flight information must be recorded in the FEMA UAS Mission Log (AOF-2-2) and will include, at a minimum, but not limited to:

Date, Time, Location of Launch Platform Flight Crew Date, Time, Location of Landing Reason for Flight and/or Flight Activity Additional Flight Information (ex. Incident, Accident, Mishap) User Maintenance Performed

Unless otherwise directed, the contractor’s UAS flight team will ensure that all recorded data and imagery captured by the UAS during the mission is correctly categorized, labeled, and stored; and will be handled in compliance with all Response Geospatial Office (RGO), privacy, and cybersecurity requirements.

4.8.4 Progress Report

The contractor shall provide a weekly progress report to the Contracting Officer and COR via electronic mail on the 1st business day of each week. In the event the 1st business day of each week falls on a Federal Holiday, the contractor shall provide this report on the following business day. This report shall include a summary of all contractor work performed, including a breakdown of labor hours by labor category, all direct costs by line item, an assessment of technical progress, schedule status, any travel conducted and any contractor concerns or recommendations for the previous reporting period. This report shall be provided weekly for the life of this contract regardless of deployment status. The due date of this report may be altered with approval from the COR and CO.

4.8.5 Monthly Progress Report

The contractor shall provide a monthly continuous monitoring report on the 1st business day of each month. In the event the 1st business day of each week falls on a Federal Holiday, the contractor shall provide this report on the following business day. This report shall include a summary of data and storage system services used in support of this contract. This report shall be provided monthly for the life of this contract regardless of deployment status, and cover the system’s posture, findings from scans, identify system deficiencies and solutions, status of system checks, and other security control activities to support risk management. Any changes to the formatting of this report must be coordinated with the COR and CO in advance of implementation. The due date of this report may be altered with approval from the COR and CO.

4.8.6 Progress Meetings

The Project Manager shall be responsible for keeping the COR informed about contractor progress throughout the performance period of this contract and ensure contractor activities are aligned with DHS objectives. At a minimum, the Project Manager shall review the status and results of Contractor performance with the COR on a quarterly basis via a virtual platform.

4.8.7 After Action Report (AAR)

The contractor shall provide AARs no later than 45 days following completion of the task order. The report shall also include an overview of the performance of equipment and teams to include lessons learned, best practices, safety record, and recommendations for major plan maintenance and procedural revisions.

4.9 Government Acceptance Period

The COR will review deliverables prior to acceptance and provide the contractor with an e-mail documenting reasons for non-acceptance, if applicable. If the deliverable is acceptable, the COR will send an e-mail to the contractor with notification that the deliverable has been accepted.

4.9.1 COR Review

The COR has the right to reject or require correction of any deficiencies found in the deliverables that are contrary to the information contained in the contractor’s accepted proposal.

In the event of a rejected deliverable, the contractor will be notified in writing by the COR of the specific reasons for rejection. The contractor may have an opportunity to correct the rejected deliverable and return the proposal per delivery instructions.

For administrative contract deliverables, the COR will have 7 business days to review and make comments. The contractor shall then have 7 business days to make corrections and redeliver.

Deliverables under a task order have more expedient deadlines for update and review (e.g., 2-6 hours).

For deliverables required under a task order, the COR will review requirements and determine the timeline for contractor deliverables.

All other review times and schedules for deliverables shall be agreed upon by the parties based on the final approved Project Plan.

The contractor shall be responsible for timely delivery of deliverables to government personnel in the agreed upon review chain, at each stage of the review. The contractor shall work with specified personnel reviewing the deliverables to assure that the established schedule is maintained.

5.0 Deliverables

(a) The contractor shall provide status reports, progress reports, and other deliverables as required in a format proposed by the contractor and agreed to by the Government, and program office.

(b) The contractor shall provide support to FEMA and AOPO, as required, in the writing, review, and preparation of deliverables, forms, imagery and remotely sensed data. All deliverables prepared by the contractor shall be on the behalf of FEMA and the contractor shall not independently publish or distribute any document without prior written permission from the CO.

(c) The draft and final deliverables of all associated working papers, other material, imagery and remotely sensed data deemed relevant by FEMA which have been generated, and stored by the contractor in the performance of these tasks are the exclusive property of the U.S. Government and shall be submitted to FEMA at the conclusion of the tasks.

(d) FEMA will be the sole authorized source for releasing verbally or in writing any data, the draft deliverables, final deliverables, or any other written or printed materials, imagery and remotely sensed data pertaining to this task order. No information shall be released by the selected contractor. Any request for information relating to these tasks presented to the selected contractor shall be submitted to FEMA for response.

(e) Press releases, marketing material, or any other printed or electronic documentation and imagery and remotely sensed data related to this project shall not be publicized without the written approval of FEMA.

(f) The following deliverables shall be provided as required. Due dates may be dependent on specific milestones as documented in the PMP. All references to days are in calendar days.

(g) The products will be completed at the For Official Use Only (FOUO) level, unless otherwise noted in the award.

The contractor shall consider items in BOLD below as having mandatory due dates. Items in italics below are deliverables or events that must be reviewed and/or approved by the COR prior to proceeding to next deliverable or event in this PWS.

ITEM PWS REFERENCE DELIVERABLE/EVENT DUE BY DISTRIBUTION

1 2.0/7.0 Imagery and remotely sensed data

Determined at the task order level/within 14 days of collection, at the end of the period of performance, and upon request by Air Operations, COR

Air Operations Program Office, COR, Contracting Officer

2 2.0 Authority To Operate/Security Requirements Tracking Matrix

Determined at the task order level, and upon request by Air

Operations, COR

COR, Contracting Officer

3 2.0 Quality Control Plan No later than 60 days after contract award COR, Contracting Officer

4 2.1 Activation and Availability Within 24 hours COR, Contracting Officer

5 4.6 Post Award Conference No later than 5 calendar days after award

COR, Contracting Officer

6 4.7.1 Business Continuity Plan 30 days after contract award/updated annually

COR, Contracting Officer

7 4.7.2 Security Plan 30 days after contract award/updated annually

COR, Contracting Officer

8 4.8 Reporting 2 weeks after contract award Varies

9 4.8.2 Status Report Daily by 5 pm EDT – at task order level COR, Contracting Officer

10 4.8.2 UAS Strategy Upon request Air Operations Program Office, technical/task monitor, COR, Contracting Officer

11 4.8.3 UAS Reporting As determined by the program office

Air Operations Program Office, technical/task monitor, COR, Contracting Officer

12 4.8.4 Weekly Progress Report 1st business day of each week COR, Contracting Officer

13 4.8.5 Monthly Progress Report 1st business day of each week COR, Contracting Officer

14 4.8.7 After Action Report NLT 45 days following task order completion COR, Contracting Officer

6.0 Performance Requirements Summary (PRS)

The PRS establishes key elements of contractor performance that represent “mission essential” service requirements, which are identified in the table below in the “Service Output” column. The “Performance Objective” column represents the standard against which contractor performance will be measured in relation to accomplishment of the corresponding service output. The performance objective or “standard” describes the minimum acceptable level of service by the contractor for satisfactory performance. The “Acceptable Quality Level (AQL)” column displays the maximum allowable deviation from the performance objective, which, if exceeded, evokes the negative incentive specified in the table below.

Service Output Performance Objective Acceptable Quality Level (AQL) Positive

Incentive Negative incentive

1. Data Collection Accuracy (PWS 2.0)

UAS must collect and transmit data with at least 98% accuracy

98% accuracy in data collection

A positive CPARS rating will be administered

If non-compliant as stated in the PWS or as specified in the Task

Order, an “Unsatisfactory” CPARS rating will be earned

2. Mission Availability (PWS

2.3)

UAS (hardware, systems, and personnel) operational readiness at all times

>95% availability during mission critical periods

A positive CPARS rating will be administered

If non-compliant as stated in the PWS or as specified in the Task

Order, an “Unsatisfactory” CPARS rating will be earned

3. Flight Operations (PWS

2.3.3)

UAS must complete assigned missions with no more than 1% deviation from flight plan parameters

99% adherence to flight plans

A positive CPARS rating will be administered

In non-compliant with 2 or more occurrences, or as specified in the

Task Order, an “Unsatisfactory” CPARS rating will be earned

4. Payload Delivery (PWS 3.3)

UAS must deliver payloads within 5 minutes of scheduled delivery time

95% on-time delivery rate

Review of delivery logs, mission reports, and requestor’s feedback

If non-compliant as stated in the PWS or as specified in the Task

Order, an “Unsatisfactory” CPARS rating will be earned

7.0 Personally Identifiable Information

To accomplish the tasks outlined in this contract, the contractor may receive the following PII data elements:

Facial image License plate number Location address

PII information includes any direct flight safety requirements questions related to security and weight related factors that could impact UAS safety requirements.

Contractor operations shall only collect or use UAS-collected information to the extent that such collection, and/or use, is consistent with an authorized purpose. The contractor shall take appropriate steps to ensure UAS-collected information covered by the Privacy Act is not disseminated outside of FEMA. FEMA will disseminate such information as required by law or fulfills an authorized purpose in support of the Agency’s mission. No UAS-recorded data shall be downloaded or recorded for personal use or posted onto a personally owned device or website.

The contractor shall coordinate with RGO for data and imagery storage, protection, and dissemination requirements. Air Operations will facilitate the contractor-RGO connection.

No UAS-recorded data shall be downloaded or recorded for personal use or posted onto a personally owned device or website, nor retained by the contractor. The contractor shall remit to FEMA all UAS collected imagery and data within 14 days of collection, at the end of the period of performance, and upon request by Air Operations.

The contractor shall ensure no computer matching, as defined in 5 U.S.C. § 552a(o), will occur for the purpose of establishing or verifying eligibility or compliance as it relates to cash or in-kind assistance or payments under federal benefit programs.

If at any time during the term of this contract any part of FEMA PII, in any form, that the contractor obtains from FEMA ceases to be required by the contractor for the performance of the task order or upon termination of the task order, whichever occurs first, the contractor shall, within fourteen (14) days thereafter, promptly notify FEMA and securely transmit PII to FEMA, or, at FEMA’s written request destroy, un-install and/or remove all copies of such PII in the contractor’s possession or control and certify in writing to FEMA that such tasks have been completed.

Contractor access to proprietary information is required under this PWS. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with DHS MD 11042.1, Safeguarding Sensitive but Unclassified (For Official Use Only) Information. The contractor shall ensure that all contract personnel having access to business or procurement sensitive information sign a non-disclosure agreement (DHS Form 11000-6).

8.0 Safeguarding of Controlled Unclassified Information (JULY 2023)

Definitions. As used in this clause:

Adequate Security means security protections commensurate with the risk resulting from the unauthorized access, use, disclosure, disruption, modification, or destruction of information. This includes ensuring that information hosted on behalf of an agency and information systems and applications used by the agency operate effectively and provide appropriate confidentiality, integrity, and availability protections through the application of cost-effective security controls.

Controlled Unclassified Information (CUI) is any information the government creates or possesses, or an entity…