WS-25-0001 HR3D Draft PWS.pdf

DRAFT

Draft Performance Work Statement (PWS)

WS-25-0001

High Resolution Three-Dimensional Geospatial Information (HR3DGI O&TI III)

Operations & Technology Integration III

Part 1. General Information

1.1 Introduction and Background: The US Army Geospatial Center (AGC) provides timely, accurate and relevant High Resolution Three-Dimensional (HR3D) Data to enable geospatial information, capabilities, and domain expertise for the Army Geospatial Enterprise implementation and Geospatial Data Fabric. The HR3D mission provides critical information to the Warfighter in all Domains and in all Combatant Commands (CCMDs). The purpose of the HR3D mission, is to collect, process, disseminate, store, and maintain data collected by conducting wide area high altitude flight operations. Processed HR3D data serves as foundational geospatial data products for the Department of Defense (DoD), Coalition Partners, and Host Nations. Data collection is primarily Outside of the Continental U.S. (OCONUS) with some in the Continental U.S. (CONUS). The data provided from HR3D supports Government efforts for terrain analysis, change detection, threat analysis, intelligence preparation of the battlefield (IPB), operational and tactical mission planning, intelligence, surveillance, and reconnaissance (ISR) support, engineer planning, Aerial Port of Debarkation (APOD), Seaport of Debarkation (SPOD), Large Scale Combat Operations (LSCO), Counter Insurgency (COIN), Humanitarian and Disaster Relief (HADR) and many other uses. The Warfighter Support Directorate (WSD), HR3D Program is a part of the US Army Corps of Engineers (USACE) at the US Army Geospatial Center (AGC). The HR3D Program focuses on providing high fidelity geospatial foundational data/terrain mapping, and provides support to all authorized Army, DoD, and other government organizations.

This SATOC IDIQ/CPFF contract performance work statement (PWS) describes the services and tasks to be undertaken. The purpose is to collect, process, disseminate, apply, and maintain HR3D geospatial data by conducting flight and collection operations and by processing and producing the required HR3D data products (comprised of but not limited to, LiDAR, EO, bathymetric, Synthetic Aperture Radar (SAR), Hyperspectral Imaging (HSI) and unclassified commercial satellite imagery data). In addition, the Department of Defense (DoD) is pursuing advancements in LiDAR, SAR, HSI and bathymetric sensor technology. This is a result of the operational requirement to provide high fidelity terrain mapping from a higher altitude, higher velocity aircraft platform (to reduce risk from adversary fire). DoD requires advancement in supporting LiDAR, SAR, HSI and bathymetric collection, data processing, storage, and dissemination technology. Current LiDAR collection systems are rapidly improving/increasing area collection rates as well as increasing the geospatial fidelity of the data. In order to keep pace with the improving collection systems, improved, more rapid data processing needs to be integrated into the HR3D program. The HR3D program is also looking for emerging technology integration for LiDAR, EO, SAR, HSI, bathymetric and Measurement and Signals Intelligence (MASINT) sensors.

1.2 Scope: This PWS defines the requirements for Contractor-provided services necessary to support the HR3D program. These services cover all requirements, including the following:

Manned fixed wing platform collection of wide area airborne and bathymetric collection that capture 5-, 10- and 50-centimeter spatial resolution EO imagery, 50cm LiDAR, FOPEN and 20m depth bathymetry data and multi-INT.

Provide large scale, worldwide on site, and advanced cloud based geospatial data processing, exploitation, analysis, meshing of data to create and deliver 2, 2.5 and 3D content, and rapid dissemination.

Provide a centralized CONUS based data content management, exploitation, analysis and reach back architecture to support end user requests.

Provide a COCO fleet integrated with Government furnished sensors with responsibility for aircraft and sensor maintenance, materials, aircraft and personnel mobilization and demobilization.

Provide technology integration and value engineering with an emphasis toward next generation unmanned and terrestrial capabilities with services on demand, as well as rapid data processing workflows with advanced software capabilities and/or AI/ML.

Provide meetings, deliverables, schedules, configuration management, personnel management, risk management, quality control, security, and overall program compliance.

1.3 Description of Services: The Contractor shall provide a fully integrated flight operation, collection, and processing service to support worldwide HR3D collections requirements. The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items necessary to perform the HR3D support tasks as defined in this PWS, except for those items specified as Government-furnished property (GFP), services and information.

1.4 Objectives: The objective of this effort is to collect, process, disseminate, exploit, store, and manage airborne LiDAR, EO, bathymetric, SAR, HSI, SI, multi-INT to support the end user HR3D requirements and operations.

Period and Place of Performance: The contract will be a base period of 12 months, with nine (9) 12-month option periods. Place of performance is at the OCONUS base camp locations identified in PWS paragraph 5.2.1 and within the designated AOR’s listed for each base camp, and the CONUS locations identified in paragraphs 5.2.1.2 and 5.2.1.3.

Access to and Disclosure of Information: The Contractor may require access to data and information proprietary to a government agency, another Government Contractor, or of such nature that its dissemination or use, other than as specified in this contract, would be adverse to the interests of the Government or others. Except to authorized Government personnel, or upon written approval of the Contracting Officer or designated representative, neither the Contractor, nor Contractor employees, shall divulge nor release data or information developed or obtained in the performance of this contract.

The Contractor shall direct to the Program Manager (PM) and Contracting Officer’s Representative (COR) all inquiries, comments, or complaints arising from matters observed, experienced, or learned as a result of, or in connection with the performance of this contract, the resolution of which may require the dissemination of official information.

Inquiries received by the Contractor regarding work performed under this contract shall be referred to the Contracting Officer for evaluation under the Freedom of Information Act (FOIA) of 1975, Public Law 93-502, 5 U.S.C., Section 552. The Contractor shall not release any information concerning this project to the public without written authorization from the Contracting Officer.

1.5 Quality Control: The Contractor shall implement, maintain, and use QC and quality assurance (QA) procedures to ensure proper oversight for data collected, personnel, training, facilities, equipment, supplies, services, and subcontractors. The Contractor’s QCP is the means by which the Contractor assures its work complies with the requirements of the contract. The Contractor shall develop and maintain an effective Quality Control Plan (QCP) to ensure services are satisfactorily performed under this contract. The Contractor shall implement procedures to identify, prevent, and ensure non-recurrence of defective services and data products. The Contractor’s QCP is the means by which the Contractor shall develop QCP procedures that address the areas identified in Section 5, Specific Tasks in this PWS.

The QCP shall address the internal quality control processes with clear and direct lines of communication to ensure accountability to the Contractor’s senior management and leadership;

address overall project management and administration; cover all services described in this PWS to include essential services as identified in the Performance Requirements Summary (PRS);

describe a method, acceptable to the Government, of identifying deficiencies in the quality of service performed under this contract before the level of performance becomes unacceptable, and address processes for corrective actions without dependence upon Government direction;

require documentation of all Contractor QC inspections and corrective actions be maintained by the Contractor throughout the term of this contract. Copies of inspection documents will be provided to the COR upon request and they will describe the methods of communication with the Government regarding performance of the contract. The QCP shall include regular and formal meetings with the Government and proposed formats and/or schedules for informal communications (e.g., periodic emails to the PM and COR).

1.6 Quality Assurance: The Government will evaluate the Contractor’s performance under this contract in accordance with the QCP and the Government’s Quality Assurance Surveillance Plan (QASP). The QASP will be used to evaluate contractor performance in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rates.

1.7 Government Remedies: The Contracting Officer will follow Federal Acquisition

Regulation (FAR) 52.246-5, “Inspection of Services – Cost Reimbursement” for the Contractor’s failure to perform satisfactory services or failure to correct nonconforming services.

1.8 Recognized Holidays: Below is a list of the federal holidays to be observed by the Contractor personnel performing within CONUS:

New Year’s Day Martin Luther King Jr. Birthday Memorial Day Juneteenth Independence Day Labor Day Thanksgiving Day Christmas Day

1.9 Hours of Operation: For OCONUS operations and support under this effort, normal operating hours will be 24 hours a day, 7 days a week (24/7); and individual employees shall be expected to work 12 hours a day, 7 days a week to support the 24/7 operations. For the portions of this effort that are conducted CONUS, the Contractor shall be responsible for conducting business between the hours of 9:00am and 5:00pm, Monday through Friday, except for supporting emergency management operations during which time business may need to be conducted 24 hours a day for the duration of the emergency management operations. The Government estimates approximately 14 days per year for supporting emergency management operations.

1.10 Security Requirements

All security requirements will be addressed in the DD Form 254 that will be issued upon award of the contract. Key Personnel (see Section 5.3.4 of this PWS), with the exception of the Chief Mechanic, will possess Top Secret (TS) Sensitive Compartmented Information (SCI) security clearances to work on the contract. The Chief Mechanic and Contractor personnel performing work onsite at any of the various processing locations will be required to have a security clearance of no lower than Top Secret.

The Contractor shall maintain at least a TS Facility Clearance and make available approved Secret storage sufficient to accommodate the needs of this PWS.

The Contractor shall provide personnel who have clearances in place, enabling the capability for the Government to authorize access to SCI. All deployed personnel shall have a security clearance of no lower than Secret to work on the contract.

Physical Security: The Contractor shall be responsible for safeguarding all Government equipment, information, and property provided for Contractor use based on direction from the Government, as applicable.

1.11 Antiterrorism/Operational Security (AT/OPSEC)

1.11.1 All Contractor employees, to include all associated subcontractor employees requiring access to Army installations, facilities, and controlled access areas shall complete AT Level I awareness training within 30 calendar days after contract start date or the effective date of incorporation of this requirement into the contract, whichever is applicable. AT Level I awareness training is available at the following website:

https://jko.jten.mil/courses/atl1/launch.html. The Contractor shall submit certificates of completion for each affected Contractor employee and subcontractor employee to the COR within 7 calendar days after completion of training by all employees and subcontractor personnel. This includes new Contractor employees as they are assigned.

1.11.2 Contractor employees and all associated subcontractor employees shall comply with applicable installation, facility, and area commander installation/facility access and local security policies and procedures (provided by the COR as Government Furnished Information (GFI)) at contract start date or the effective date of incorporation of this requirement into the contract, whichever is applicable) such as the wearing of identification badges, etc. The Contractor shall also provide all information locally required for background checks to meet installation access requirements to be accomplished by the installation Provost Marshal Office, Director of Emergency Services, or Security Office. Contractor workforce must comply with all personal identity verification requirements as requested by the COR based on DoD, Headquarters, Department of the Army (HQDA), and/or local policy. In addition, should the Force Protection Condition (FPCON) at any individual facility or installation change, the COR may require changes in Contractor security matters or processes. During FPCON Charlie and Delta and other required postures (such as Lockdown, Shelter in Place, or Evacuation), Contractor employees will resume work as soon as possible after FPCON has been lowered or the posture returned to normal operations. This pertains to real situations and exercises.

1.11.3 The Contractor and all associated subcontractors shall ensure that all of their employees participate in local training, as required by the COR based on the local AT Officer requirements, such as local iWatch training, to inform employees of the types of behavior to look out for and instruct employees to report suspicious activity to the COR.

1.11.4 The Contractor shall develop an OPSEC Standard Operating Procedure (SOP)/Plan within 90 calendar days of contract award. The OPSEC SOP/Plan must be reviewed and approved by the Requiring Activity (RA) OPSEC Officer. The SOP/Plan will include the Government’s critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it. In addition, the Contractor shall identify an individual who will be an OPSEC Coordinator.

1.11.5 The Contractor and all associated subcontractors shall ensure that all local clearance procedures (i.e., return of identification badges provided by the COR as GFI at the contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable) are followed for departing Contractor and subcontractor employees.

1.11.6 CONUS-based Contractor employees and associated subcontractor employees who will perform work OCONUS will receive area of responsibility (AOR) specific AT awareness training as directed by Army Regulation (AR) 525-13 and meet all country clearance requirements per the Personnel Policy Guidance (PPG) and local deployment requirements and documentation. The COR will provide information (required training, country clearance requirements, and local deployment requirements/documentation) as GFI at the contract start date or the effective date of incorporation of this requirement into the contract, whichever is applicable.

1.11.7 Contractor employees and associated subcontractor employees, who are authorized to accompany U.S. Armed Forces deployed outside the U.S. in contingency operations; humanitarian or peacekeeping operations; or other military operations or exercises, when designated by the combatant commander, shall comply with local AT/OPSEC policies.

These policies include required compliance with laws and regulations, pre-deployment requirements, required training (per combatant command guidance), personnel data requirements to address before deployment, and required documentation. The COR will provide these policies as GFI at the contract start date or the effective date of incorporation of this requirement into the contract, whichever is applicable.

1.11.8 Non-local national (not citizens of the foreign country of performance or delivery) Contractor employees and associated subcontractor employees who are required to provide performance or delivery in a foreign country are to comply with country and theater clearance requirements and allow the combatant commander to exercise oversight to ensure the Contractor's compliance with combatant commander and subordinate task force commander policies and directives. The COR will provide this information (requirements, policies and directives) as GFI at the contract start date or the effective date of incorporation of this requirement into the contract, whichever is applicable.

1.11.9 Contractors and all associated subcontractors who will handle or have access to Classified Information are to be directed to analyze FAR 52.204-2, Security Requirements. This clause involves access to information classified "Confidential", "Secret", or "Top Secret" and requires Contractors to comply with: The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M); and any revisions to DoD 5220.22-M, notice of which is to be provided by the COR as GFI at contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable.

1.11.10 Contractor personnel and associated subcontractor personnel who require access to Government Information Systems must successfully complete the DoD Information Assurance (IA) Awareness training, and all other mandatory IA training/forms, which are required by the Government Organization(s) that control(s) the system(s) that the Contractor requires access to, before accessing these Government information system(s). The DoD IA Awareness training must be completed annually thereafter. The COR will provide the Contractor with the specific requirement(s) that must be met for access to these systems as GFI at the contract start date or the effective date of incorporation of this requirement into the contract, whichever is applicable.

1.12 Special Qualifications: Expertise and past performance in wide area high altitude collections and data processing simultaneously in multiple CCMDs.

1.13 Post Award Conference/Periodic Progress Meetings:

The Contractor shall conduct a kickoff meeting two weeks after contract award telephonically, virtually, or in person at the AGC in Alexandria, VA, or at the Contractor’s facility.

The Contractor shall conduct program management reviews monthly either by telephone, virtually, in person at the AGC in Alexandria, VA, or in person at the Contractor’s facility.

The Contractor shall conduct weekly technical status updates telephonically or virtually with the COR and in-theater Government representatives.

The COR for this contract will be designated prior to contract award.

The COR monitors all technical aspects of the contract and assists in contract administration.

The COR is authorized to perform the following functions:

• Assure the Contractor performs the technical requirements of the contract;

• Perform inspections necessary in connection with contract performance;

• Maintain written and oral communications with the Contractor concerning technical aspects of the contract;

• Issue written interpretations of technical requirements, including Government drawings, designs, and specifications;

• Monitor Contractor’s performance and notify both the Contracting Officer and Contractor of any deficiencies;

• Coordinate availability of GFP; and provide site-entry of Contractor personnel.

A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates, or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting contract.

Contract Manager: The Contractor shall provide a Contract Manager who, during the post-award phase, will participate in modifications and work to ensure that the services being provided by the Contractor meet the requirements of the PWS. The name of this person and an alternate who shall act for the Contractor when the primary Contract Manager is absent shall be designated in writing to the Contracting Officer. The Contract Manager or alternate shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract.

Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their Contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure all documents or reports produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed.

1.14 Travel: To the maximum possible extent, the Contractor shall provide electronic media over existing secure high bandwidth or other secure communications links rather than by Contractor travel. The Contractor shall travel between the Contractor’s facility and OCONUS locations as required to carry out the tasks specified in this PWS. The Contractor shall comply with the Joint Travel Regulations (JTR). The JTR are applicable to uniformed members of the seven uniformed services (i.e., Uniformed Members of the Army, Navy, Air Force, Marine Corps, Coast Guard, National Oceanic and Atmospheric Administration Commissioned Corps, and Public Health Service Commissioned Corps), DoD civilian employees and others traveling at DoD expense.

1.15 Documentation: The Contractor shall deliver to the COR all documents and materials as deliverables developed under this effort for inspection and acceptance. The Contractor shall provide all document deliverables in hard copy, softcopy, or secure communications in accordance with the DD1423 CDRLs. The Contractor shall document all work performed under this effort as follow s:

1.15.1The Contractor shall provide monthly reports on the 10th day of each month beginning the month after contract award. The Contractor shall deliver the monthly status reports via secure communications to the COR on the tenth day of each month after contract award. The Contractor shall provide monthly status reports summarizing current program accomplishments measured against the tasks outlined previously, identification and summary of any unresolved problems, incurred costs, meetings attended, planned activities for the next month, issues, and recommendations. The Contractor shall ensure the monthly report includes a spending plan for the period of performance; actual expenditures to date; actual expenditures for the month just ended; and monthly and cumulative variation of actual expenditures from the planned expenditures.

The Contractor shall include in the spending plan all costs to include labor, overhead expenses, description (to include cost and results obtained) of each trip taken in the previous month, and fees. The Contractor shall include detailed copies of all invoices submitted to date for payment from both the prime contractor as well as all subcontractors. The Contractor shall ensure each invoice details the labor categories, labor rates, labor hours, and all ODCs, Materials.

1.15.2 The Contractor shall also answer the following questions within the monthly reports:

• Is the work progressing on schedule?

• What is the percent of completion/against objective?

• What is the dollar value completed/budgeted?

• What is the total number of contract employees currently on contract/objective?

• Was Contractor Manpower Reporting (CMR) performed during the monthly reporting period? If so, what information was entered?

• What are names of the Contractor personnel, who are/were deployed during the period?

• What is the total monthly cost per deployment location/site?

• How many SQ/KM of data was collected, by each aircraft?

• How many SQ/KM of data by each aircraft has been processed and what is the data processing backlog by location?

• How many hours of flight by aircraft were undertaken to collect vs the number of hours the aircraft flew?

• Operational status of each aircraft, next phased maintenance scheduled, and number of hours aircraft is expected to be out of service?

1.15.3 The Contractor shall provide to the COR a weekly status report, to include any incidents of data collection for which data is unusable, corrupted, or indicate error in sensor or sensor operators.

1.15.4 The Contractor shall provide to the COR an accident report and a serious incident and compliance report no later than one (1) day after an accident or serious incident.

1.15.5 The Contractor shall provide to the PM and COR a detailed report of all incidents of collection errors made by sensor operators resulting in unusable data, corrupted data and/or cancelled missions.

1.15.6 Final Report: The Contractor shall submit a draft Final Report one (1) month prior to the end of the contract to the COR for review. The COR will review the draft Final Report within two (2) weeks. The Contractor shall provide a revised Final Report based on COR comments one

(1) week prior to the end of the contract.

1.15.7 The Contractor shall submit a Property Control Plan to the COR within one (1) week after contract award.

1.15.8 The Contractor shall submit a Transition Plan at the solicitation closing date of the RFP for its plan to obtain an Air Worthiness Release (AWR) for all aircraft and achieve full operational readiness by the contract base period start date. The Contractor shall also submit a Transition Plan no later than 8 months prior the contract end date, which details how the Contractor can ramp-down and transition to a new contractor, and/or remove and package all GFE, if applicable. The Government will give the Contractor 30 days’ notice when the second Transition Plan is due.

1.15.9 The Contractor shall submit an OPSEC plan to the COR within 90 calendar days of contract award.

Part 2. Definitions and Acronyms

2.1 Definitions

CONTRACTOR

A supplier or vendor awarded a contract to provide specific supplies or service to the

Government. The term as used in this contract refers to the prime contractor.

CONTRACTING OFFICER

A person with authority to enter into, administer, or terminate contracts and make related determinations and findings on behalf of the Government. Note: The only individual who can legally bind the Government.

CONTRACTING OFFICER'S REPRESENTATIVE (COR)

A representative from the requiring activity appointed in writing by the Contracting Officer to perform surveillance and to act as liaison to the Contractor.

DEFECTIVE SERVICE

A service output that does not meet the standard of performance associated with it in the PWS.

DELIVERABLE

Anything that can be physically delivered, including data deliverables in accordance with the

CDRLs, and also including non-manufactured things such as meeting minutes or reports.

HR3DGI SYSTEM

An airborne or terrestrial vehicle, equipped with the HR3DGI sensors, together with the HR3DGI data processing capability.

KEY PERSONNEL

“Personnel” means employees of the contractor, or any subcontractor(s), affiliates, joint venture partners, or team members, and consultants engaged by any of those entities.

The personnel specified as “Key Personnel” in Section 5.3.4 of this PWS are considered to be essential to the work being performed under this contract. Prior to diverting any of the specified individuals to other projects, the Contractor shall notify the Contracting Officer reasonably in advance and shall submit justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on the program. No diversion shall be made by the Contractor without the written consent of the Contracting Officer.

PERFORMANCE WORK STATEMENT

Statement of work (SOW) for performance-based acquisitions that describes the required results in clear, specific, and objective terms with measurable outcomes.

PHYSICAL SECURITY

Actions that prevent the loss or damage of Government property.

PLATFORM

An airborne or terrestrial vehicle.

QUALITY ASSURANCE

Actions taken by the Government to assure contracted services meet PWS requirements.

QUALITY CONTROL PLAN

A written document specifying the surveillance method used for surveillance of Contractor performance.

QUALITY CONTROL

Actions taken by a Contractor to control the performance of contracted services to meet PWS requirements.

SUBCONTRACTOR

One that enters into a contract with a prime Contractor. The Government does not have privity of contract with the subcontractor.

WORK DAY

The number of hours per day the Contractor provides services in accordance with the contract.

WORK WEEK

Monday through Friday, unless specified otherwise.

2.2 Acronyms

24/7 24 hours a day, 7 days a week 3D Three Dimensional AC Advanced Capability ACOR Alternate Contracting Officer's Representative AFARS Army Federal Acquisition Regulation Supplement AFRICOM U.S. Africa Command AGC Army Geospatial Center AGL Above Ground Level ALTM Airborne Laser Terrain Mapper AOR Area of Responsibility AR Army Regulation AT Anti-Terrorism AWR Air Worthiness Release CCE Contracting Center of Excellence CCMD Combatant Command CENTCOM U.S. Central Command CF Coalition Forces CFE Contractor-Furnished Equipment CFR Code of Federal Regulations CLIN Contract Line-Item Number CMR Contractor Manpower Reporting CONEX Container Express CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer’s Representative COTS Commercial Off-the-Shelf CRC CONUS Replacement Center CWBS Contract Work Breakdown Structure DA Department of the Army DCMA Defense Contract Management Agency DD Department of Defense Form DD250 Department of Defense Form 250 (Receiving Report) DD254 Department of Defense Contract Security Requirement List DEM Digital Elevation Model DFARS Defense Federal Acquisition Regulation Supplement DMDC Defense Manpower Data Center DoD Department of Defense EC Enhanced Capability

ELINT Electronic Intelligence EO Electro Optical EUCOM U.S. European Command FAA Federal Aviation Administration FAR Federal Acquisition Regulation FMC Fully Mission Capable FPCON Force Protection Condition GCS Ground Control Station GeoTIFF Geographically Tagged Image File Format GFE Government-Furnished Equipment GFI Government-Furnished Information GFR Government Flight Representative GOTS Government Off-the-Shelf GPS Global Positioning System GS General Services GSE Ground Support Equipment HAZMAT Hazardous Material HIPAA Health Insurance Portability and Accountability Act of 1996 HITL Hardware in the Loop HQDA Headquarters, Department of Army HR3DGI High-Resolution Three-Dimensional Geospatial Information HSI Hyper-spectral Imaging IA Information Assurance IMS Integrated Master Schedule INDO-PACOM U.S. Indo-Pacific Command ITAR International Traffic in Arms Regulation JHU John Hopkins University

JP2 JPEG 2000

JPG Joint Photographic Experts Group KO Contracting Officer LAS Laser File Format Exchange LIDAR Light Detection and Ranging LOA Letter of Authorization MD Maryland MFW Manned Fixed Wing MOA Military Operating Area?

MrSID Multi-resolution Seamless Image Database N/A Not Applicable NGA National Geospatial-Intelligence Agency NITF National Image Transmission Format NORTHCOM U.S. Northern Command OCI Organizational Conflict of Interest OCONUS Outside the Continental United States (includes Alaska and Hawaii)

ODC Other Direct Costs OPSEC Operational Security PDSS Pre-Deployment Site Survey PIPO Phase In/Phase Out PM Program Manager POC Point of Contact PRS Performance Requirements Summary PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QC Quality Control QCP Quality Control Plan RGB Red, Green, Blue SAR Synthetic Aperture Radar SCI Sensitive Compartmented Information SIGINT Signals Intelligence SOCOM U.S. Special Operations Command SOP Standard Operating Procedure SOUTHCOM U.S. Southern Command SOW Statement of work TBO Time Before Overhaul TE Technical Exhibit TM Technical Monitor TOT Time over Target TPOC Technical Point of Contact TS Top Secret U.S. United States UAS Unmanned Aerial System USACE United States Army Corp of Engineers WBS Work Breakdown Structure

Part 3. Government Furnished Information, Equipment, Services and Facilities

3.1 General

3.1.1 The Government will provide CAC cards for Contractor personnel.

3.1.2 The Government will provide Synchronized Pre-deployment Operational Tracker (SPOT) coordination for any OCONUS travel.

3.2 The Government will provide the following information:

3.2.1 DD 1423 to be provided upon contract award.

3.2.3 DoD flight information publications, updates, and supplements appropriate to the area of operations thirty (30) days after contract award.

3.2.4 A Letter of Authorization (LOA) for Contractor personnel to permit attendance at a CONUS Replacement Center (CRC) or similar approved replacement center, in accordance with DoD guidance. The LOA will validate, at a minimum, their Contractor employment, GS equivalency (GS 12 or 13), and authority to process within twenty (20) days of contract award.

3.2.5 Applicable installation, facility, and area commander installation and facility access and local security policies and procedures upon deployment date.

3.2.6 Requirements for AOR–specific AT awareness training and local deployment requirements and documentation. The COR will provide this information (required training, country clearance requirements, and local deployment requirements and documentation) as GFI at contract award.

3.2.7 Local AT/OPSEC policies, including required compliance with laws and regulations, pre-deployment requirements, required training (per combatant command guidance), and personnel data requirements provided by the COR as GFI at contract award.

3.2.8 Country and theater clearance requirements and combatant commander and subordinate task force commander policies and directives provided by the COR as GFI at contract award.

3.2.10 Specific requirements that must be met for access to Government information systems as GFI at contract award.

3.2.11 CCMD documentation with approval to deploy and operate the HR3D mission in support of the CCMD, for example OPORDS, FRAGOS, and CONOPS.

3.3 The Government will provide all required sensors and cameras, including but not limited to, the list below:

Sensor Total Units

• Optech Galaxy T2000 13 or more

• Leica City Mapper 2 One or more

• Leica ALS80UP 11 or more

• Leica SPL 100HA 2 or more

• Leica SPL 100 2 or more

• Chiroptera-5 LiDAR One or more

• Sigma Space High Altitude Speed, and Resolution Photonic (HARP) LiDAR One or more

• Phase One iXM EO Cameras 35 or more

• Phase One SPARC 2 or more

• Vision Map Mist are we continuing use?

• 3DEO FOPEN LiDAR 2 or more

• Leonardo Osprey 30 AESA Radar One or more

• Parson ICS 550 One or more

• DRT 3300 One or more

• Lanshark/Sharkcage System One or more

• ViaSAT Communications One or more

• Starlink Airborne System 2 or more?

• San Juan SI One or more?

• LN-251 (system for SAN JUAN)

• L3 Harris Wescam MX25 One or more?

• MDRMN One or more?

• Mayflower Magna F system 7 or more?

• Controller CC3X One or more?

• Operator Console OC60 One or more?

• Laser Controller 1U Crystal RS112S14 One or more?

• TermoTek Chiller One or more?

• GSM 4000 One or more?

• Tornado / Shadowcat One or more?

• Crystal 2U LIDAR OBP Computer One or more?

• Crystal 2U EO OBP Computer One or more?

• KIV-77 One or more?

• TA-24 SAASM GPS Receiver One or more?

• GPS AT1675-180 One or more?

• VR-18 One or more?

• VORTEX TCDL One or more?

• TNT One or more?

• HTL One or more?

• Delta Labs Processor (DLP) One or more?

• DAEDALUS One or more?

• INGRES One or more?

• Telephonics RDR-1700G(V)2 One or more?

• Starlink Aero Terminal One or more

These items will be provided to the contractor at the deployment sites no later than 7 days prior to the start of the base period.

3.3.1 All GOTS and COTS software that is required for use in operation of the system. It has been established that this software is compatible with Government-approved networks and flight systems. GOTS/COTS software items are listed in Table 1:

Developer Software Title Use Aeroptic Aeroptic Framemeta Generator Aeroptic Aeroptic Boresight Applanix PosPac Applied Imagery Quick Terrain (QT) Modeler LiDAR data exploitation GIA Geoid09 Converter JHUAPL HR3DApp (GOTS) Leica CLM (Leica License Manager) Leica Inertial Explorer Microsoft Microsoft Office PhaseOne CaptureOne Pro PhaseOne PhaseOne FirmwareUpdater Simactive Correlator 3D Skyline Photomesh Teledyne Optech DiskExtract Teledyne Optech LynxSurvey USACE HyperCube (GOTS) VisionMap ArcGIS Visionmap Planning

Extension

VisionMap FlightViewer VisionMap Lightspeed Manager Woolpert TOFRCLI, TOFRUTILS, boresight, AdjustSBET_GPS

Table 1

3.3.2 The government will provide the following communication systems and radios at deployment sites NLT 7 days prior to the start of the base period.

• Harris PRC 117G (14 or more)

• Harris PRC117F (6 or more)

• ARC231 (2 or more)

• CSEL radios (18 or more)

• SKL (29 or more)

• APX-119

3.3.3 The government will provide ALTM software and any other ITAR-restricted equipment or information.

3.4 The Government (COCOM) will provide the following services and facilities:

3.4.1 Mission scheduling and planning sufficient to allow Air Operations Center airspace coordination and ATO development within 72 hours prior to mission.

3.4.2 Operation of Multi-INT Sensors.

3.4.3 Coordination with Tactical Air Control facilities for emergency mission requirements within twelve (12) hours of mission.

3.4.4 Access to Coalition Forces (CF) weather facilities daily prior to mission.

3.4.5 Access to mission profile intelligence briefing for threat identification and assessment daily prior to mission.

3.4.6 Access to CF airfields as required for mission performance daily prior to mission.

3.4.7 The Government Contracting Officer will appoint a GFR to monitor the Contractor's flight and ground operations. At its unilateral discretion, the Government may incorporate DFARS

252.228.7001 Ground and Flight Risk in the future.

3.4.8 Flight oversight of all airspace and aviation procedures by the OCONUS TM and Contract Officer Appointed GFR or designated equivalent daily prior to mission.

3.4.9 Flight profiles that will avoid areas where hostile air threat activities are known to exist or are anticipated to occur based on current threat assessments provided daily prior to mission.

3.4.10 A secure base of operations daily from start to finish of deployment.

3.4.11 The Government will provide all necessary utilities (e.g., water, power, fuel) to support operations in areas where they are not commercially available to the Contractor daily from start to finish of deployment.

3.4.12 Housing and office locations at forward deployed locations while operating in areas where these items are not commercially available daily from start to finish of deployment. In addition, the Government will be required to provide housing if the Operational Commander requires the Contractor personnel to live on a base or FOB due to operational/Force Protection reasons or other mission requirements.

3.4.13 A secure OCONUS facility for any data processing of classified data daily from start to finish of deployment.

3.4.14 Adequate office space that includes adequate power supply and cooling for Contractor personnel who are required to work onsite at Government facilities as part of performing this effort daily from start to finish of deployment.

3.4.15 The Government will provide security for personnel, and aircraft when operating in any environment such as an active combat zone where continuing contingency operations are ongoing daily from start to finish of deployment.

3.4.16 A group CRC class (or equivalent) to begin no later than Day 30 of the transition period.

3.4.17 OCONUS HAZMAT and shipping inspectors as required for remobilization thirty (30) days from final date of remobilization.

3.4.18 Military transport as required for mobilization, remobilization, and shipment of spares and equipment depending upon the theater of operations as required.

Part 4. Contractor Furnished Items and Responsibilities

4.1 General

4.1.1 The Contractor shall furnish everything required to perform the requirements of this PWS except for the items listed that will be provided by the Government in Part 3 of this PWS.

4.2 The Contractor shall furnish the following equipment: A minimum of seven turboprop aircraft, up to three multi-mission turboprop aircraft, and three jet Federal Aviation Administration (FAA)–certified aircraft that meet the HR3D operational requirement and support equipment to maintain the safe operation of the aircraft. The Contractor shall assume total responsibility for the maintenance and repair of the multi-mission aircraft.

4.2.1 The collection operations will be comprised of the following fleet:

Up to ten (10) manned (turboprop) airborne HR3D I Light Detection and Ranging (LiDAR)/Electro-Optical (EO) collection systems.

One (1) manned (jet) airborne HR3D II LiDAR/EO collection system.

Two (2) manned (jet) airborne HR3D III LiDAR/EO collections systems.

4.2.2 The Contractor shall provide and maintain manned fixed wing platforms to include the following:

4.2.3 The Contractor shall provide up to ten (10) FAA–certified aircraft, that must fulfill all Army AWR requirements in compliance with DCMA 8210, fully modified and equipped to provide services as an airborne mapping platform and capable of continuously travelling 750 NM from its base of operations to its collection area, performing a one-hour on-station collection, and returning to base. These aircraft will be used for the sensor and camera configurations to meet the PWS requirements for either the BE I, (EC or AC) systems. These aircraft also can be used for the sensor and camera configurations for the BE II system, if necessary.

4.2.4 The Contractor shall provide one (1) FAA-certified aircraft, that must fulfill all Army AWR requirements in compliance with DCMA 8210, fully modified and equipped to provide services as an airborne mapping platform capable of continuously travelling 1,000 NM from its base of operations to its collection area, performing a four-hour on-station collection, and returning to base. This aircraft will only be used for the sensor and camera configurations to meet the PWS requirements for the BE II system.

4.2.5 The Contractor shall provide one (2) FAA-certified aircraft, that must fulfill all Army AWR requirements in compliance with DCMA 8210, fully modified and equipped to provide services as an airborne mapping platform capable of continuously travelling 3,000 NM from its base of operations to its collection area, performing a four-hour on-station collection, and returning to base. This aircraft will only be used for the sensor and camera configurations to meet the PWS requirements for the BE III system.

4.3 The Contractor shall develop and document a sparing strategy for the platforms. This sparing strategy will include recommendations for LRUs at the bases of operations, and identification of long lead-time components and subassemblies to be procured and held at the Contractor’s CONUS facility or other suitable location, CONUS or OCONUS.

4.3.1 The Contractor shall procure spare parts for the platforms in accordance with the sparing strategies.

4.3.2 The Contractor shall provide the personnel and equipment required to maintain the platforms.

4.3.3 The Contractor shall assume total responsibility for the maintenance and repair of the platforms, and all other CFE required to perform the required tasks.

4.4 The Contractor will operate the COCO aircraft under a State Use Designation with the US Army serving as the Air Worthiness Release (AWR) Authority.

4.4.1 The Contractor shall provide commercial aircraft insurance for COCO aircraft and aircraft operations.

4.4.2 The Contractor shall be bound by the operating procedures contained in the combined regulation/instruction entitled "Contractor's Flight and Ground Operations" in effect on the date of contract award, and the applicable updated regulation/instruction during performance.

Part 5. Specific Tasks

5.1 General

The Contractor shall provide all labor, equipment, technical, managerial, logistical, and engineering support and services to support the U.S. Government in the execution of its HR3D operation and sustainment mission. The Contractor shall provide personnel possessing the skills, knowledge, certifications, and training to satisfactorily perform the services required by this PWS. The Contractor shall procure and manage all materials, supplies, and services needed to perform the tasks specified in this PWS. The remainder of this section describes the specific tasks and activities that the Contractor shall conduct. All acronyms are spelled out as follows and are listed as solely the acronym thereafter.

5.2 Technical and Operations Tasks

5.2.1 Locations (OCONUS and CONUS)

BE I

Camp Lemonnier, Djibouti (1 MFW – BE I System) in AFRICOM AOR Al Asad Airbase, Iraq (1 MFW – BE I System) in CENTCOM AOR Bacau, Romania, Poland (2 MFW BE I) in EUCOM AOR Zamboanga, Philippines (1 MFW – BE I) in INDOPACOM AOR Australia (1 MFW – BE I) in INDOPACOM AOR Panama (1 MFW – BE I) in SOUTHCOM AOR

BE II

Camp Lemonnier, Djibouti (1 MFW – BE II System) in AFRICOM AOR

BE III

Cebu, Philippines (1 MFW – BE III System) in INDOPACOM AOR West African Basing Location TBD (1 MFW – BE III System) in AFRICOM AOR

Each OCONUS base camp/deployed site in the list above is within a CCMD AOR. CCMD AORs and their geographic limitations are detailed further in Figure 1 of the PWS.

The geographic locations of data collection missions are defined in the CCMD generated OPORD/TASKORD/EXORDs received by the Government.

Figure 1

5.2.1.2 CONUS Test and Evaluation (T&E) Locations are listed below: HR3D MOA, southern Ohio Valentine MOA, Marfa, Texas Tombstone MOA, Arizona/Texas border.

5.2.1.3 CONUS Basing Location:

Manassas, VA (1 MFW – BE I) in NORTHCOM AOR

CONUS Military Installation collection sites are listed below:

MacDill AFB, Florida Avon Park, Florida Fort Bragg/Camp Mackall, North Carolina Camp Lejeune, North Carolina Fort Polk/Camp Beauregard/Claiborne Range, Louisiana Camp Shelby, Mississippi Joint Base Lewis McChord/Yakima Training Center, Washington Fort Drum, New York Fort Benning, Georgia Atterbury, Muscatatuck, Jefferson, Indiana Camp Ravenna, Ohio Washington DC Fort Gordon, Georgia Fort Rucker, Alabama

Yuma Proving Grounds, Arizona

5.2.1.4 One (1) MFW shall be operational for CONUS-based operations at the levels of effort stated in PWS Section 5.5.5

5.2.2 Manned Fixed Wing Platforms Collection and Processing

The Contractor shall provide technical, management, engineering, maintenance, testing, training, and operational support that include the following:

5.2.2.1 Collection

5.2.2.1.1 The Contractor shall operate the GFE equipment and software identified in Part 3 of this PWS.

5.2.2.1.2 The Contractor shall plan and conduct HR3D data collection missions upon receipt from CCMD Collection Management (CM)/Air Operations directives.

5.2.2.1.3 The Contractor shall keep and make available for Government inspection, a logbook record of all flights performed.

5.2.2.1.4 The Contractor will provide the ability to collect airborne data using contractor owned aircraft capable of integrating Government furnished sensors within 60 days of contract award (must be able to operate a minimum of 2 aircraft per CCMD within 60 days of contract award and capable of collecting a minimum of 300 sq/km per flight/aircraft for BE I; 800 sq/km per flight/aircraft for BE II and 2000 sq/km per flight/aircraft for BEIII.

5.2.2.1.5 The Contractor shall maintain a 90% Operational Readiness rate to respond to missions from the Government within 24 hours.

5.2.2.1.6 The Contractor shall perform collection missions in accordance with the OPORDS for each of the performance locations identified in paragraph 5.2.1. Collection missions will take place during daylight hours for EO and LiDAR collections and during nighttime hours for LiDAR. Collection mission flight hours will optimize sun angles for the highest quality EO imagery. The priority of data collection is in accordance with the CCMD data requests.

5.2.2.1.7 A flight or a series of flights (also known as sortie or sorties), with a fully mission capable (FMC) maintained aircraft (having departed from a deployed location or base camp) flying at approved altitudes, with flight crew on board, sensors and cameras fully mission capable/maintained and operational, transiting to a location, collecting data over one or more location/area provided by the CCMD CM, transiting from area of collection to return to the deployed location/base camp. Each mission flight time total is up to eight hours with time over target(s) up to six hours, subject to and in accordance with the requirements in DFARS 252.228- 7001, Ground and Flight Risk and IAW DCMA 8210 and AR 95-1.

5.2.2.1.8 The Contractor shall accommodate a standard operational flight profile of 8,000 feet (ft) AGL to 19,000 ft AGL for the BE I systems; and 15,000 ft AGL to 35,000 ft AGL for the BE II and BE III systems and accommodate mutually agreeable flight profiles outside of these bands based on operational, sensor, and aircraft limitations.

5.2.2.1.9 The Contractor shall collect 1 m LIDAR and 10 cm EO imagery or better with the manned fixed wing systems.

5.2.2.2…