PWS.doc
DOC document 168 KB Posted
- Attached to
- Synopsis - Request For Information (RFI)
- Solicitation number
- W911QX23R0034
About this file
This performance work statement outlines research and development requirements for a strap-down pilotage system using advanced uncooled focal plane array sensors. The Army Research Laboratory seeks to develop a 21-camera prototype system integrated into a single head to provide pilots enhanced night vision capabilities without moving parts. Objectives include determining sensor performance for pilotage without blur and assessing functional benefits beyond vision. The contractor must design and integrate the sensor head, develop data and display systems, and analyze exploitation of full frame data streams. The contractor will also integrate visible and infrared cameras onto a helicopter to record and analyze test data. Deliverables include schedule, briefing, monthly status reports, funds reports, and a final report. The period of performance is 24 months from September 2023 to August 2025 at the University of Arizona. Only U.S. citizens may perform the work due to export control information. The contractor must implement security, training, and technology control plans and have a principal investigator with a SECRET clearance.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Synopsis-RFI (Sole Source using 6.302-1).doc | DOC document |
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 (PWS)
STRAP-DOWN PILOTAGE SYSTEM
05 MAY 2023
C.1 BACKGROUND
The United States Army at the Army Research Laboratory (ARL) is conducting an applied research and development program to provide state-of-the-art upgrades to its nighttime pilotage system for vertical lift platforms. By leveraging the current Modernized Pilot Night Vision System (MPNVS) capabilities which include a gimbaled head-tracked sensor where the sensor is pointed in the direction of the pilot's helmet direction, this program will investigate the performance of a comparatively low-cost "strap-down" pilotage system that is comprised of a super camera of 21 super uncooled focal planes providing roughly 21 Megapixel coverage in the forward direction of the aircraft. Additionally, the program will assess the technical challenges and opportunities to enable a low-cost advanced "strap-down" pilotage system that will offer pilots high performance night-time situational awareness and mobility, greater threat detection and collision avoidance, improved performance in degraded environments, and no moving parts for higher reliability and less maintenance costs.
C.2 OBJECTIVES
The objective of this effort is to conduct research and development into the application of strap-down pilotage system using advanced sensors uncooled focal plane array sensors. Specifically, the goal is to develop a pilotage testbed system for the investigation of pilotage sensor performance which will address research and development objectives across sensor development, architecture, display, system integration, proof of concept demonstration and student training in this critical sensor area. This effort will conduct research into the entire strap-down pilotage system to create a prototype system with high levels of performance beyond present similar systems. Proposed fundamental improvements will use a “strap-down” camera for Apache to ingest the entire forward flight path field of regard both in daytime and nighttime environments This novel “strap-down” approach offers a number of performance and maintenance improvements over the legacy head-tracked approach with sensor gimbal including, no moving parts, so operations, maintenance, and repairs are much less expensive; better flying capability in degraded visual environments (dust, smoke, fog, etc.).and the ability to detect enemy threat drones in the front sector of the aircraft.
Specific objectives of the research and development are:
1. Determine the ability of a strap-down pilotage system to create a high-performance night-time pilotage system.
2. Determine the ability of uncooled infrared (UCIR) microbolometer multi-core super-camera to create a high-performance pilotage without significant and time constant blur.
3. Determine the ability of a super uncooled (SUCIR) core to create a high-performance pilotage without significant time and constant blur.
4. Determine the ability of a SUCIR super-camera to provide functional benefits beyond pilotage using the large native field of regard (FOR).
C.3 REQUIREMENTS
C.3.1 The Contractor shall develop a 21-camera system integrated into a single camera head with alignment mechanisms. The sensors are either Uncooled Infrared (UCIR) or Super Uncooled Infrared (SUCIR) and integrated into the sensor head, where each camera can be modified, aligned, and the sensor head can also me mounted and aligned. Specific design and development of the large Field of Regard (FOR) super camera (sensor) uses UCIR and/or SUCIR component cameras. FOR is intended be 180 Degrees in azimuth and 90 Degrees threshold in elevation with 93 Degrees in elevation objective (+34Deg/-59Deg). The super camera sensitivity and resolution is intended to be designed such that the Target Task Performance (TTP) metric matches or exceeds Modernized Pilot Night Vision System (MPNVS) Pat all scene contrast temperatures.
C.3.2 The Contractor shall develop a data read-out and management system to (1) stream one or more channels of pilotage video to the helmet display with less than single frame capture latency, (2) stream full frame data to the attention subsystem and (3) archive full frame data.
C.3.3 The Contractor shall develop parallel applications of the full frame data stream supporting the 21 focal plan array super camera. The system must deliver pilotage visuals with less-than single frame latency. In addition to the real-time stream, however, the system must implement automated analysis, databasing and exploitation.
C.3.4 The Contractor shall develop a system to handle the massive amount of data (110 to 1000 times more than a conventional camera with a large 30 to 40 degrees Field of View (FOV)) generated by the super camera and convey through an appropriate display the correct amount of contextual data.
C.3.5. The Contractor shall develop methods, algorithms, and processes to fully understand the data and how to appropriately display the information generated by the data to a human end user.
C.3.6 The Contractor shall develop algorithms for drone detection over the super camera sensor Field of Regard (FOR). Within this requirement, the performance of the algorithms will be assessed and reported.
C.3.7 The Contractor shall integrate the Visible (VIS) and Long-Wave InfraRed (LWIR) super cameras onto a rotorcraft (helicopter). The Contractor shall have three testing requirements (defined below) as part of the integration of the VIS and LWIR super camera onto a rotorcraft (helicopter). The three activities are:
1. Activity number 1: The integration effort shall include experiments which will include recording the data from the VIS and LWIR super cameras such that the imagery can be analyzed post flight.
2. Activity number 2: The integration effort shall include experiments of the VIS and LWIR super cameras integrated onto the rotorcraft after the super uncooled focal planes are integrated into the two positions of the super camera. Experiments shall include recording data from the VIS and LWIR super cameras such that the imagery can be analyzed post flight.
3. Activity number 3: Final field activity shall include an outdoor day and night demonstration of the super camera using the Elbit helmet. This requirement shall be a static demonstration to demonstrate the performance of the super camera.
C.4 DELIVERABLES
C.4.1 The Contractor shall submit all PWS deliverables to the COR for inspection and acceptance. Unless otherwise stated in this PWS, the Contractor shall use best commercial formats, standards, and practices for deliverables.
C.4.2 The below table summarizes the technical deliverables as required by this PWS.
| Deliverable |
| PWS Reference |
| Due Date |
| Initial Schedule Report |
| C.4.3 |
| NLT 15 days after contract award |
| Kick Off Briefing |
| C.4.4 |
| NLT 30 days after contract award |
| Monthly Status Reports |
| C.4.5 |
| NLT 45 days after contract award and then subsequentially NLT the 10th day of each month following the PoP reporting on |
| Contract Funds Status Report |
| C.4.6 |
| NLT 100 days after contract award and then subsequentially quarterly or NLT the 10th day of each month following the PoP reporting on |
| Final Report |
| C.4.7 |
| NLT 30 days after contract PoP |
C.4.3 Initial Schedule: The Contractor shall provide a schedule of all work to be performed no later than (NLT) fifteen (15) days after contract award. The schedule shall be separated by both time/date and major milestones that will occur throughout the development work.
C.4.4 Kick Off Briefing: The Contractor shall provide a kickoff briefing in PowerPoint format including presentation NLT thirty (30) days after contract award.
C.4.5 Monthly Status Reports: The Contractor shall provide the first monthly report NLT 45 days after contract award and then subsequentially NLT the tenth (10th) day of each month following the period of performance (PoP) reporting on. The Contractor shall provide the monthly status reports to the COR summarizing current program activities and accomplishments, problems encountered (including identification of any problems, issues and delays and any corrective action that was taken to correct identified problems), recommended solutions to problems, incurred costs, schedule status (planned versus actual with rationale for deviations) and planned activities and costs for the next month.
C.4.6 Contract Funds Status Report: The Contractor shall provide quarterly status reports on spent funds and monthly man-hours. The Contractor shall provide the first Contract Funds Status Report NLT 100 days after contract award and then subsequentially quarterly or NLT the 10th day of each month following the PoP reporting on. Each report shall clearly list the total man-hours expended against each labor category (direct and indirect), individuals listed by name, material expenses, and travel expenses.
C.4.7 Final Report: The Contractor shall provide a final report no later than (NLT) thirty (30) days after the contract PoP detailing the findings from all efforts performed under this task order. The Contractor shall ensure the report includes all refinements made to the system, lessons learned, recommendations for further enhancements, and a final cost incurred report. The COR will review and comment on the final report within fifteen (15) days of receipt. Upon receipt of the COR comments, the Contractor shall revise the final report to incorporate the COR’s comments and deliver one (1) copy electronically as well as one (1) printed hard copy to the COR at the Final Refinement Solution Demonstration NLT 15 days after receipt of COR comments or NLT 60 days after the contract period of performance of 24 months (September 2023 – August 2025). The place of performance is University of Arizona, 1630 E University Blvd, Tucson, AZ 85747
C.5 SECURITY REQUIREMENTS
C.5.1 The Contractor shall create a technology control plan (TCP) or similar document to manage the contracting security requirements of the effort, including but limited to handling, storage, and management of Controlled Unclassified Information (CUI), Export Controlled Arms (EAR) and International Traffic in Arms Regulations (ITAR) information, physical access and control of restricted information, training of personnel in the handling, storage, and management of restricted information.
C.5.2 The Contactor shall have only US Citizens working on this effort, since much of this effort involves both Export Controlled Arms (EAR) and International Traffic in Arms Regulations (ITAR) information.
C.5.3 The Contractor shall have all personnel working on this effort receive proper training in handling, storing, and management of Controlled Unclassified Information (CUI), including EAR and ITAR type information according to government regulations.
C5.4 The Contractor shall have a principal investigator who shall have a current SECRET clearance. All classified information and discussions shall occur only at a designated Government facility. No classified information or work will occur outside of the designated government facility. All other US Citizens working on this effort do NOT have to have a security clearance.
C.6 ANTI-TERRORISM/OPERATIONAL SECUIRTY (AT-OPSEC)
C.6.1 For contractors requiring Common Access Card (CAC). Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.
C.6.2 iWATCH Training. This standard language is for Contractor employees with an area of performance within an Army controlled installation, facility or area. The Contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity (ATO). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. The training shall be 14 calendar days of contract award.
C.6.3 For contracts that require OPSEC Training. Per AR 530-1 Operations Security, the contractor employees must complete Level I OPSEC Awareness training. New employees must be trained within 30 calendar days of their reporting for duty and annually thereafter.
C.6.4 For information assurance (IA)/information technology (IT) training. All contractor employees and associated sub-contractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working in IA/IT functions must comply with DoD and Army training requirements in DoD 8570.01, DoD 8570.01-M and AR 25-2 within six (6) months of appointment to IA/IT functions.
C.6.5 For all contractors with security clearances. Per AR 381-12 Threat Awareness and Reporting Program (TARP), contractor employees must receive annual TARP training by a CI agent or other trainer. Please see below information for making report.
iSALUTE: https://www.inscom.army.mil/isalute/ iWATCH: https://www.myarmyonesource.com/ Spy Hotline: 1-800-CALL-SPY
C.7 GOVERNMENT FURNISHED EQUIPMENT (GFE) / GOVERNMENT FURNISHED INFORMATION (GFI) GOVERNMENT FURNISHED PROPERTY (GFP) / OTHER GOVERNMENT FURNISHED MATERIALS
C.7.1 There shall be no GFE, GFI, GFP or other government furnished materials.
C.8.0 Homeland Security Presidential Directive (HSPD)-12 C.8.1 Routine access of contractor personnel to Government-controlled facilities is NOT required.
C.8.2. Access to Government controlled information systems is NOT required.
C.8.3 Contractor will comply with HSPD-12 standards by:
- informing the COR of the contract at least 30 days in advance of any visit to a government facility.
- completing and returning visit request authorization (VAR) and submitting to government security office at least 15 days before visiting.
- having at least 2 forms of ID when visiting the facility for badging purposes with at least one ID being a state issued driving license with picture.
- National Agency Check with Inquiries is not required.
- Federal Information Processing Standard (FIPS) Publication (PUB) 201 compliant products and service components are not applicable to this contract.
- All Federal government identification cards and badges will be returned at the end of each day prior to each contractor leaving the government facility.
Contracting Officer:
Legal Advisor:
File details come from the government source that posted it. Updated .