Attachment 4_QASP_12760426Q0137.pdf
PDF 278 KB Posted
- Attached to
- Phoenix Nextgen Infrared Scanning System
- Solicitation number
- 12760426Q0137
- Issued by
-
Department of Agriculture Forest Service
About this file
This is a Quality Assurance Surveillance Plan (QASP) for the Phoenix NexGen Linux SBC Completion Effort (2026) under the USDA Forest Service National Infrared Operations (NIROPS).
The QASP defines the Government's methods for monitoring and evaluating contractor performance against the Performance Work Statement requirements. The plan applies to four primary work scope areas: remaining software modernization (~25%), fabrication and integration of SI-DRA-SBC hardware, system-level integration and validation, and support and maintenance during the performance period. Government surveillance will be conducted through demonstration-based validation, functional testing, system integration testing, and operational mission simulation. The Contracting Officer holds final authority on contractual matters, while the COR (Bill Forsyth, 208-387-5720, William.Forsyth@usda.gov) manages technical administration and proper surveillance. Government Technical Monitor Michael Mann (208-387-5647, Michael.Mann@usda.gov) assists with oversight and measurement. The COR must document all surveillance activities on Surveillance Activity Summary Forms and maintain a complete quality assurance file throughout the contract life.
The Surveillance Activity Summary Form specifies seven distinct deliverables with corresponding performance standards and acceptable quality levels: log streaming stabilization with no data loss, file compatibility conversion (100% successful .PLF to .BIL conversion), real-time orthorectification at 200 lines/second, data anomaly diagnostics with 100% detection, SI-DRA-SBC hardware fabrication and assembly, support and maintenance maintaining operational availability, and full system validation through operational mission simulation. All monitoring is to be performed by Government technical representatives prior to acceptance testing or during the performance period, with formal acceptance testing required within 30 calendar days of receipt.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFQ_12760426Q0137.pdf | ||
| Attachment 1-BOM.xlsx | XLSX spreadsheet | |
| Attachment 2_USDA Security Contract Language.pdf | ||
| Attachment 3_ICT Accessibility Requirements.pdf | ||
| Attachment 5_PWS_12760426Q0137.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
National Infrared Operations - Phoenix NexGen Linux SBC Completion Effort (2026)
QASP
Quality Assurance Surveillance Plan (QASP)
Phoenix NexGen Linux SBC – Completion Effort (2026)
USDA Forest Service – NIROPS
1. Purpose
This Quality Assurance Surveillance Plan (QASP) defines the methods the Government will use to monitor and evaluate contractor performance under the Performance Work Statement (PWS).
The objective is to ensure that:
• Contractor performance meets all technical and functional requirements
• Deliverables meet acceptance criteria defined in the PWS
• Payments are made only for accepted and conforming work
2. Scope
This QASP applies to all work defined in the PWS, including:
• Remaining software modernization (~25%)
• Fabrication and integration of SI-DRA-SBC hardware
• System-level integration and validation
• Support and maintenance during the period of performance
The contractor is responsible for managing and developing a quality control plan to meet the quality standards established in the PWS. This QASP is put in place to define the surveillance the Government will perform for quality assurance.
This QASP is part of the contract, however it is not intended to replace the Contractor’s quality control plan. The Government may provide the Contractor with an informational copy of the QASP to support the Contractor’s efforts in developing a quality control plan that will inter-relate with the QASP.
3. Government Resources
The following personnel will implement all surveillance activities:
Contracting Officer. The Contracting Officer ensures performance of all necessary actions for effective contracting, ensures compliance with the terms of the contract and safeguards the interests of the Government in the contractual relationship. It is the Contracting Officer that assures the Contractor receives impartial, fair and equitable treatment under the contract. The Contracting Officer is ultimately the final authority on contractual matters.
Contracting Officer:
Telephone Number: N/A Email:
Contracting Officer’s Representative (COR). The COR is responsible for technical administration of the contract and assures proper Government surveillance of the Contractor’s supplied items. The COR is not empowered to make any contractual commitments or to authorize any contractual changes on the Government’s behalf.
Any changes that the Contractor deems may affect contract price, terms, or conditions shall be referred to the Contracting Officer for action.
Contracting Officer’s Representative: Bill Forsyth Telephone Number: 208-387-5720 Email: William.Forsyth@usda.gov
COR Designees. Additionally, COR Designees, also known as Government Technical Monitors (GTMs), may be named to ensure that the Government sufficiently directs, oversees, measures and monitors contractor’s supplies. GTMs will provide information to the overall contract COR.
Government Technical Monitor: Michael Mann Telephone: 208-387-5647 Email: Michael.Mann@usda.gov
4. Documentation
The results of all supplied activity shall be documented on the Surveillance Activity Summary Form. The COR shall submit copies of the Surveillance Activity Summary Form at the conclusion of contract performance and whenever contractor performance fails to meet acceptable quality levels.
The COR will, in addition to providing documentation to the Contracting Officer, maintain a complete quality assurance file. The file will contain copies of all reports, mailto:William.Forsyth@usda.gov mailto:Michael.Mann@usda.gov evaluations, recommendations, surveillance checklists, and any actions related to the Government’s performance of the quality assurance surveillance function. All such records will be retained for the life of the contract and forwarded to the Contracting Officer upon completion.
5. Methods of Quality Assurance Surveillance
The Forest Service will use demonstration-based validation, functional testing, system integration testing and operational mission simulation for methods of quality assurance.
The Forest Service reserves the right to refuse acceptance of any nonconforming supplies. Quality issues with supplies tendered for acceptance or rejected by the Government shall be resolved per the Federal Acquisition Regulation.
National Infrared Operations - Phoenix NexGen Linux SBC – Completion Effort
Surveillance Activity Summary Form
PWS
Section
Required Service Performance Standard Acceptable Quality Level (AQL)
Monitoring Method Monitoring Performed by/ Date(s)
2.0 - A, B, C, D
Complete remaining software modernization (~25%)
All functions implemented and integrated without fault or crash
Meets all acceptance criteria in section 4.0 of
PWS
Functional testing demonstration, & code review
Government technical representative prior to acceptance testing
2.1 - A Log streaming stabilization and anomaly handling
Stable logging with no performance loss
No data loss or crashes with repeatable results
Test datasets, validation runs
Government technical representative prior to acceptance testing
2.1 - B Expand file compatibility
Successful .PLF → .BIL conversion
100% successful file conversion with no data loss.
Dataset testing Government technical representative prior to acceptance testing
2.1 - C Real Time Orthorectification
Matches previous system performance.
Sustained processing at 200 lines/sec
Meets all acceptance criteria in section 4.0
PWS
Performance testing during demonstration
Government technical representative prior to acceptance testing
2.1 - D Implement diagnostics for data anomalies
System detects and prevents crashes from bad data
100% detection with no unhandled failures.
Meets all acceptance criteria defined in section 4.0 PWS
Fault injection testing
Government technical representative prior to acceptance testing
2.2 - E Fabricate SI-DRA- SBC system
Fabricate and assemble the SI-DRA-SBC as described in section 2.2 PWS
Hardware assembled with software integrated successfully.
Fully functional system ready for testing
Hardware inspection with demonstrated software integration test
Government technical representative prior to acceptance testing
3.0 - F Support and Maintenance
Provide maintenance support described in section 3.0 PWS
System maintains operational availability.
Issues resolved in a timely manner
Support as described in section
3.0 PWS
Government technical representative during period of performance
4.0 Execute full system
validation
All tasks in section 2.0 are completed on the Phoenix system and the system operates without fault or errors
Meets all acceptance criteria in section 4.0
PWS
Formal acceptance testing through operational mission simulation as outlined in section
4.0 PWS
Government technical representative within 30 calendar days of receipt
Contracting Officer:
File details come from the government source that posted it. Updated .