PWS - Yellowscan_REV_FINAL_09042025.docx
DOCX document 33 KB Posted
- Solicitation number
- W912HZ25QA019
About this file
This Performance Work Statement (PWS) details a data collection project for the Army Corps of Engineers' Engineering Research and Development Center (ERDC) Geotechnical and Structures Laboratory. The objective is to procure services for a vendor to conduct LiDAR scanning using a Yellowscan Voyager-30 UAS LiDAR system at the Vicksburg Municipal Airport over three days. The vendor will perform multiple flights at varying altitudes (15-200m) across two different object configurations, capturing three-dimensional point cloud data in LAS file format.
The solicitation is structured as a combined synopsis/solicitation for commercial services, with the intent to award a single purchase order to the lowest-priced technically acceptable offeror. The period of performance is 8 weeks from the award date, and the vendor will be required to deliver geo-referenced LAS files within two weeks of data collection. Key requirements include traveling to Vicksburg with the LiDAR sensor and UAS, performing specified flight patterns, and providing high-quality point cloud data for Army research purposes. The project will focus on determining the ground resolution and vertical accuracy of the Yellowscan Voyager-30 LiDAR sensor for potential field deployment.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Solicitation - W912HZ25QA019.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PERFORMANCE WORK STATEMENT
Data collection using Yellowscan Voyager 30 UAS LiDAR system
1.0 General: This performance work statement (PWS) describes the non-personal services required by the Engineering Research and Development Center (ERDC) Geotechnical and Structures Laboratory (GSL) located in Vicksburg, Mississippi.
2.0 Background: The Army has a need to determine the ground resolution and vertical accuracy of the Yellowscan Voyager-30 LiDAR sensor deployed from an unmanned aerial system (UAS) by scanning objects of various sizes placed on an airfield surface. The three-dimensional point clouds resulting from the scans are necessary for the ERDC to employ its proprietary detection algorithms for performing surface detections of the various objects. The combination of the data collection effort and the ERDC detection algorithms will help the Army determine the effectiveness of the Yellowscan Voyager 30 LiDAR system for field deployment.
3.0 Objective: The overall objective is to procure services for a Vendor to travel to Vicksburg with a Yellowscan Voyager-30 LiDAR sensor and a UAS system of the vendor’s choice and perform a series of flights from altitudes ranging from 15 to 200-m above ground level and each for a distance of approximately 500-m at the Vicksburg Municipal Airport (VMA) over the course of three days of data collection. ERDC will set up a series of objects on an asphalt road paralleling the main runway at VMA. The parallel road begins at roughly the following coordinate: 32°14'50.2"N 90°55'40.8"W. Two different configurations of objects would be emplaced on subsequent days (Configuration #1 and #2 in the table below) to provide a wider range of data for ERDC to analyze.
4.0 Requirements and Deliverables:
4.1 Day 1 – Configuration #1: Vendor will perform a series of flights from altitudes ranging from 15 to 200-m above ground level and each for a distance of approximately 500-m at the Vicksburg Municipal Airport (VMA).
| Sensor |
| Replicate |
| Flight Altitude |
| LiDAR |
| 1 |
| 15m |
| 30m |
| 60m |
| 120m |
| 2 |
| 15m |
| 30m |
| 60m |
| 120m |
| 3 |
| 15m |
| 30m |
| 60m |
| 120m |
12 Total LAS Files
Deliverable: The vendor will provide ERDC a series of three-dimensional point clouds in a LAS file format from each flight as a deliverable. These LAS files must be geo-referenced, but no colorization is required. These LAS files are to be delivered to ERDC personnel within two weeks of the completion of the data collection effort at VMA.
4.2 Day 2 – Configuration #2: Vendor will perform a series of flights from altitudes ranging from 15 to 200-m above ground level and each for a distance of approximately 500-m at the Vicksburg Municipal Airport (VMA).
| Sensor |
| Replicate |
| Flight Altitude |
| LiDAR |
| 1 |
| 15m |
| 30m |
| 60m |
| 120m |
| 2 |
| 15m |
| 30m |
| 60m |
| 120m |
| 3 |
| 15m |
| 30m |
| 60m |
| 120m |
12 Total LAS Files
Deliverable: The vendor will provide ERDC a series of three-dimensional point clouds in a LAS file format from each flight as a deliverable. These LAS files must be geo-referenced, but no colorization is required. These LAS files are to be delivered to ERDC personnel within two weeks of the completion of the data collection effort at VMA.
5.0 Place of Performance: Performance will take place at Vicksburg Municipal Airport (VMA). The Contractor will not access ERDC.
6.0 Period of Performance: The Period of Performance will be 8 Weeks from date of award.
7.0 CUI: No CUI involved.
8.0 Security Requirements:
8.1. General security requirements and guidance: The security requirements described below apply to all contract personnel (including employees of the prime Contractor (“Contractor”) and all subcontractor employees) supporting the performance requirements of this contract. The Contractor is responsible for compliance with these security requirements. Questions regarding security matters shall be addressed to the designated Government representative (e.g., Contracting Officer Representative (COR), Requiring Activity (RA) representative, or Contracting Officer (if a COR or other RA representative is not appointed)). Contract personnel are critical to the overall security and safety of U.S. Army Corps of Engineers (USACE) installations, facilities and activities, and security awareness training contributes to those efforts. The Department of Defense (DoD) and Army security training requirements specified below, if applicable, are performance requirements; all applicable contract personnel shall complete initial training within 30 days of contract award or the date new contract personnel begin performance on the contract. Within five business days from the completion of training, the Contractor shall provide written documentation (e.g., email or memorandum) to the Government representative. The documentation shall include the names of contract personnel trained and which training they completed; the Contractor shall maintain training records as part of their contract files and be prepared to provide copies of training certificates to the Government representative. Contractor personnel and vehicles are subject to search when entering federal installations. Additionally, all contract personnel shall comply with Force Protection Condition (FPCON) measures, Random Antiterrorism Measures (commonly referred to as “RAMs”), and Health Protection Condition (HPCON) measures. The Contractor is responsible for meeting performance requirements during elevated FPCON and/or HPCON levels in accordance with applicable RA plans and procedures --this includes identifying mission essential and non-mission essential personnel. In addition to the changes otherwise authorized by the changes clause of this contract, should the FPCON or HPCON levels at any individual facility or installation change, the Government may implement security changes that affect contract personnel. The Contractor shall ensure all contract personnel are aware of their security responsibilities, including any site-specific requirements identified in local policies or procedures.
8.2. Pre-screen candidates using E-Verify Program: Contractors shall comply with the requirements set forth in FAR clause 52.222-54 Employment Eligibility Verification and FAR Subpart 22.18 in using the E-Verify Program at (https://www.e-verify.gov/) (website subject to change) to meet the contract employment eligibility requirements. Contractors are encouraged to cooperate with Federal and State agencies responsible for enforcing labor requirements to include eligibility for employment under United States immigration laws in accordance with FAR 22.102-1(i). An initial list of verified/ eligible candidates shall be provided to the COR no later than three business days after the initial contract award. When contracts are with individuals, the individuals will be required to complete a Form I-9, Employment Eligibility Verification, and submit it to the Contracting Officer to become part of the official contract file.
9.0. Performance Metrics. This is a performance-based acquisition; therefore, performance metrics will be used. Contractor performance will be measured based on quality of customer satisfaction, timeliness of submission of deliverables, and timeliness of submission of proper invoices. The Quality Assurance Surveillance Plan (QASP) provides a systematic method to evaluate performance for the stated contract. The QASP explains the following:
| • | What will be monitored. |
| • | How monitoring will take place. Who will conduct monitoring. |
| • | How monitoring efforts and results will be documented. |
The QASP does not detail how the contractor accomplishes the work. Rather, the QASP is created with the premise that the contractor is responsible for management and quality control actions to meet the terms of the contract. It is the Government’s responsibility to be objective, fair, and consistent in evaluating performance. In addition, the QASP should recognize that unforeseen and uncontrollable situations may occur.
The QASP is a living document and, as such, may be changed as needed. However, the Contracting Officer must approve changes. The COR will submit recommended changes to the Contracting Officer for approval.
The QASP shall comply with the Federal Acquisition Regulation (FAR), Subpart 37.6, Performance Based Acquisition and 46.4, Government Contract Quality Assurance. In addition, FAR, Subpart 46.103, Contracting Officer Responsibilities, states that agencies shall develop quality assurance surveillance plans when acquiring services.
The Contractor shall provide their own Quality Management Plan clearly stating the assurance of work quality according to their policies. It is to be submitted at the time of the contractor proposal.
10.0. Performance Requirements Summary.
| Task /Deliverables |
| Standards/AQLS |
| Inspections |
| Rating |
| Incentive/Disincentive |
| PWS Day 1 – Configuration #1: Vendor will perform a series of flights from altitudes ranging from 15 to 200-m above ground level and each for a distance of approximately 500-m at the Vicksburg Municipal Airport (VMA). |
| Standards: |
The vendor will provide ERDC a series of three-dimensional point clouds in a LAS file format from each flight as a deliverable. These LAS files must be geo-referenced, but no colorization is required. These LAS files are to be delivered to ERDC personnel within two weeks of the completion of the data collection effort at VMA.
Who: Contracting Officer will inspect all deliverables.
Standard(s): Inspection applies to all standards and submittals and the ERDC makes every effort possible to provide feedback promptly. However, the contractor is advised to allow at least 10 business days for review and return of accepted deliverable(s). Generally, 10 business days is sufficient, however longer review windows may be required for unusually large or complex reviews/responses.
| Rating task completion according to Table 1 performance standards. |
| Rating task completion according to Table 1. |
If the Performance Standards are found to be non-compliant the Contractor / Vendor is responsible for correcting the task(s) to a Performance Rating above Unsatisfactory and the resulting action will require completion of the task(s) at no additional cost or extension to the Period of Performance.
PWS Day 2 – Configuration #2: Vendor will perform a series of flights from altitudes ranging from 15 to 200-m above ground level and each for a distance of approximately 500-m at the Vicksburg Municipal Airport (VMA).
Standards:
The vendor will provide ERDC a series of three-dimensional point clouds in a LAS file format from each flight as a deliverable. These LAS files must be geo-referenced, but no colorization is required. These LAS files are to be delivered to ERDC personnel within two weeks of the completion of the data collection effort at VMA.
Who: Contracting Officer will inspect all deliverables.
Standard(s): Inspection applies to all standards and submittals and the ERDC makes every effort possible to provide feedback promptly. However, the contractor is advised to allow at least 10 business days for review and return of accepted deliverable(s). Generally, 10 business days is sufficient, however longer review windows may be required for unusually large or complex reviews/responses.
| Rating task completion according to Table 1 performance standards. |
| Rating task completion according to Table 1. |
If the Performance Standards are found to be non-compliant the Contractor / Vendor is responsible for correcting the task(s) to a Performance Rating above Unsatisfactory and the resulting action will require completion of the task(s) at no additional cost or extension to the Period of Performance.
Table 1. Performance Ratings and Criteria
Performance Rating Criteria
Excellent or Outstanding Performance meets contractual requirements and exceeds many to the government's benefits. The contractual performance of the element or sub-element being assessed was accomplished with no problems and contractor actions were highly effective.
| Very Good |
| Performance meets contractual requirements and exceeds some to the government benefits. The contractual performance was accomplished with few minor problems for which corrective actions taken by the contractor were effective. |
| Good |
| Performance meets contractual requirements. The contractual performance contains some minor problems for which corrective actions taken by the contractor were satisfactory. |
| Marginal |
| Performance does not meet some contractual requirements. The contractual performance reflects a serious problem for which the contractor has not yet identified corrective actions. The contractor's proposed actions appear marginally effective or were not fully implemented. |
| Unsatisfactory |
| Performance does not meet contractual requirements, and recovery is not likely in a timely manner. The contractual performance contains serious problem(s) for which the contractor's corrective actions appear or were ineffective. |
File details come from the government source that posted it. Updated .