RIPSA SIR Final.docx
DOCX document 301 KB Posted
- Attached to
- Screening Information Request (SIR) for Runway Incursion Prevention through Situational Awareness (RIPSA)
- Solicitation number
- 693KA8-21-R-00000
View the file
Other files
| File | Type | Posted |
|---|---|---|
| J002 Labor Category and Skill Level Descriptions.pdf | ||
| J011 RIPSA FA CDRL List.doc | DOC document | |
| 20210301 Part A RIPSA Cost Price Workbook.xlsx | XLSX spreadsheet | |
| J004 Predelivery Document Checklist.pdf | ||
| J007 SAT Checklist - Copy.pdf | ||
| J008 CAI Checklist.pdf | ||
| J016 RIPSA Tech Description DIDs.doc | DOC document | |
| J005 FAT Checklist.pdf | ||
| J001 Preliminary Program Requirements for RIPSA.pdf | ||
| J013 RIPSA PM CDRL List.doc | DOC document | |
| J014 RIPSA PM DIDs.doc | DOC document | |
| J012 RIPSA FA DIDs.doc | DOC document | |
| J015 RIPSA Tech Desription CDRL List.doc | DOC document | |
| J010 Past Performance Questionnaire.doc | DOC document | |
| J006 First Article Delivery Checklist.pdf | ||
| J009 Field Checkout Checklist.pdf | ||
| J003 Referenced Documents.pdf |
Show all 17
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
PART 1- SECTION B
SUPPLIES OR SERVICES AND PRICES/COSTS
B.1 GENERAL
This Runway Incursion Prevention through Situational Awareness (RIPSA) Indefinite Delivery Indefinite Quantity (IDIQ) contract will provide Technology/Equipment and Technical Services in support of the Runway Incursion Reduction Program (RIRP). The Government seeks to evaluate three (3) different technological solutions for the requirements listed in the Screening Information Request (SIR). The solutions proposed in response to this solicitation must be capable of providing targeted surveillance capabilities for all aircraft or vehicles at protected intersections and drive a direct-to-pilot alerting system. The Contractor must provide all management, supervision, labor, facilities, equipment, material supplies, and services (except as may be expressly set forth in this Contract as furnished by the Government) and otherwise do all things necessary for, or incident to, the performance of the requirements set forth in Section C of this Contract, as incrementally requested and authorized by the Federal Aviation Administration (FAA) in the form of individually issued Delivery Orders (DOs)/Task Orders (TOs), hereby referred to collectively as “orders”. As used throughout this SIR, DOs are for all equipment and installation of the equipment for each site and will be issued on a Firm Fixed Price basis. TOs are for site engineering support and will be issued on a Time & Materials basis.
B.2 BASE AND OPTION PERIODS
The FAA may award up to three (3) contracts; one First Article System for each of the three airports specified in Section C.1.1. The term of each contract issued under this solicitation is a one (1) year base period and two (2) one-year option periods. The Contract Line Item Number (CLIN) structure in Section B.5. specifies the base periods for each of the contracts, which do not commence concurrently. In the event that a single Offeror provides different technological solutions, the Government reserves the right to award a contract to that Offeror for development and deployment of technological solutions at multiple airport sites. However, the Government intends to deploy different technological solutions to each of the three (3) airport sites and accordingly will not award the same technological solution to more than one (1) airport site. The FAA may issue an order at any time during the base and/or option periods. The orders will specify performance period(s) and may include base or option periods which extend the order up to twelve (12) months beyond the end date of this Contract.
B.3 INDEFINITE DELIVERY INDEFINITE QUANTITY CONTRACT
(a) This is an IDIQ contract. The FAA will order work under this Contract by placing Delivery Orders and Task Orders using the ordering procedures described in SIR Section G.5, Ordering Procedure.
(b) Delivery Orders issued under this Contract for First Article (FA) Delivery systems will be Firm Fixed Price orders. The FAA intends to procure up to three (3) separate First Article systems under this Contract.
(c) Task Orders issued under this Contract for Contract Management and Engineering Services Management are anticipated to be primarily Time and Material (T&M)/Labor Hour Task Orders.
(d) The FAA reserves the right to issue other types of Delivery and Task Orders under this Contract as appropriate.
B.4 GUARANTEED MINIMUM QUANTITY OF WORK
The Government guarantees that it will order at least $10,000 during the term of this Contract (the “Minimum Order Guarantee”). The Government has fully met the Minimum Order Guarantee once the aggregate dollar value of the Delivery and Task Order(s) combined placed on this Contract equals or exceeds the Minimum Guaranteed Value.
B.5 CLIN STRUCTURE
The Contract Line Item Number (CLIN) structure for this Contract is provided below. All CLINs in this Section must be performed in accordance with Section C – Description/Specifications/Statement of Work and delivered in accordance with the designated orders.
The Contract Line Item Numbers (CLINs) set forth below must be delivered on an Indefinite Delivery/Indefinite Quantity basis for each airport scenario proposed by and awarded to the Offeror.
B.5.1 BASE PERIOD - 12 Months - San Antonio International Airport Base Period Starts FY 2021
| CLIN |
| IAW SOW |
| SUPPLIES OR SERVICES |
| CLIN Type |
| Unit of Measure |
| Unit Price |
| Total Price |
| 0001a |
| C3.1 |
| Airport A - First Article (FA) System in accordance with (IAW) C3.1 |
| FP |
| 1 FA System |
| $- |
| $- |
| 0002a |
| C3.1 |
| Airport A – Pre-Delivery Documentation |
| FP |
Not separately priced (NSP)
| 0003a |
| C3.1 |
| Airport A - Factory Acceptance Testing |
| FP |
NSP
| 0004a |
| C3.1 |
| Airport A - First Article Equipment Delivery |
| FP |
NSP
| 0005a |
| C3.1 |
| Airport A - Site Acceptance Testing |
| FP |
NSP
| 0006a |
| C3.1 |
| Airport A - Contractor Acceptance Inspection |
| FP |
NSP
| 0007a |
| C3.1 |
| Airport A – Field Checkout Inspection |
| FP |
NSP
| 0008a |
| C3.1, C3.2, C3.3 |
| Site Engineering Support - Program Management/Systems Engineering: Labor (for the total quantity of Airport Scenario A FA Systems) IAW SOW C3.1, C3.2, C3.3 |
| T&M |
| Program Analyst – Level 1 |
| T&M Rate |
| 420 hrs |
| $- |
| $- |
| Technical Program Manager – Level 2 |
| T&M Rate |
| 60 hrs |
| $- |
| $- |
| Systems Engineer – Level 1 |
| T&M Rate |
| 520 hrs |
| $- |
| $- |
| Software Engineer – Level 2 |
| T&M Rate |
| 320 hrs |
| $- |
| $- |
| Systems Integrator/Field Technician – Level 3 |
| T&M Rate |
| 240 hrs |
| $- |
| $- |
| 0009a |
| C3.6 |
| Travel/Other Direct Costs (NTE) |
| CR |
| As Required |
| $20,000 |
| 0010a |
| C3.2 |
| Program Management Reports IAW C3.2 |
| FP |
NSP
| 0011a |
| C3.2 |
| Technical Meeting Reports IAW C3.2 |
| FP |
NSP
| Total Period |
| $- |
B.5.2 Option Period 1 San Antonio International Airport
| CLIN |
| IAW SOW |
| SUPPLIES OR SERVICES |
| CLIN Type |
| Hours |
| Unit Price |
| Total Price |
| 1008a |
| C3.1, C3.2, C3.3 |
| Project Management/Engineering Support IAW C3.1, C3.2, C3.3 |
| T&M |
| Program Analyst – Level 1 |
| T&M Rate |
| 420 |
| $- |
| $- |
| Technical Program Manager – Level 2 |
| T&M Rate |
| 40 |
| $- |
| $- |
| Systems Engineer – Level 1 |
| T&M Rate |
| 520 |
| $- |
| $- |
| Software Engineer – Level 2 |
| T&M Rate |
| 160 |
| $- |
| $- |
| Systems Integrator/Field Technician – Level 3 |
| T&M Rate |
| 400 |
| $- |
| $- |
| 1009a |
| C3.6 |
| Travel/Other Direct Costs(NTE) |
| CR |
$30,000
| 1010a |
| C3.1, C3.2, C3.3 |
| Technical Documentation |
| FP |
NSP
| Total Period |
| $- |
B.5.3 Option Period 2 San Antonio International Airport
| CLIN |
| IAW SOW |
| SUPPLIES OR SERVICES |
| CLIN Type |
| Hours |
| Unit Price |
| Total Price |
| 2008a |
| C3.1, C3.2, C3.3 |
| Project Management/Engineering Support IAW C3.1, C3.2, C3.3 |
| T&M |
| Program Analyst – Level 1 |
| T&M Rate |
| 240 |
| $- |
| $- |
| Technical Program Manager – Level 2 |
| T&M Rate |
| 20 |
| $- |
| $- |
| Systems Engineer – Level 1 |
| T&M Rate |
| 480 |
| $- |
| $- |
| Software Engineer – Level 2 |
| T&M Rate |
| 80 |
| $- |
| $- |
| Systems Integrator/Field Technician – Level 3 |
| T&M Rate |
| 190 |
| $- |
| $- |
| 2009a |
| C3.6 |
| Travel/Other Direct Costs (NTE) |
| CR |
$20,000
| 2010a |
| C3.1, C3.2, C3.3 |
| Technical Documentation |
| FP |
NSP
| Total Period |
| $- |
B.5.4 BASE PERIOD - 12 Months - Daytona Beach International Airport Base Period Starts FY 2022
| CLIN |
| IAW SOW |
| SUPPLIES OR SERVICES |
| CLIN Type |
| Unit/Hours |
| Unit Price |
| Total Price |
| 0001b |
| C3.1 |
| Airport B - First Article (FA) System in accordance with (IAW) C3.1 |
| FP |
| 1 |
| 0002b |
| C3.1 |
| Airport B – Pre-Delivery Documentation |
| FP |
NSP
| 0003b |
| C3.1 |
| Airport B - Factory Acceptance Testing |
| FP |
NSP
| 0004b |
| C3.1 |
| Airport B - First Article Equipment Delivery |
| FP |
NSP
| 0005b |
| C3.1 |
| Airport B - Site Acceptance Testing |
| FP |
NSP
| 0006b |
| C3.1 |
| Airport B - Contractor Acceptance Inspection |
| FP |
NSP
| 0007b |
| C3.1 |
| Airport B – Field Checkout Inspection |
| FP |
NSP
| 0008b |
| C3.1, C3.2, C3.3 |
| Site Engineering Support - Program Management/Systems Engineering: Labor (for the total quantity of Airport Scenario A FA Systems) IAW SOW C3.1, C3.2, C3.3 |
| T&M |
| Program Analyst – Level 1 |
| T&M Rate |
| 420 |
| $- |
| $- |
| Technical Program Manager – Level 2 |
| T&M Rate |
| 60 |
| $- |
| $- |
| Systems Engineer – Level 1 |
| T&M Rate |
| 520 |
| $- |
| $- |
| Software Engineer – Level 2 |
| T&M Rate |
| 320 |
| $- |
| $- |
| Systems Integrator/Field Technician – Level 3 |
| T&M Rate |
| 240 |
| $- |
| $- |
| 0009b |
| C3.6 |
| Travel/Other Direct Costs (NTE) |
| CR |
$20,000
| 0010b |
| C3.2 |
| Program Management Reports IAW C3.2 |
| FP |
NSP
| 0011b |
| C3.2 |
| Technical Meeting Reports IAW C3.2 |
| FP |
NSP
| Total Period |
| $- |
B.5.5 Option Period 1 Daytona Beach International Airport
| CLIN |
| IAW SOW |
| SUPPLIES OR SERVICES |
| CLIN Type |
| Hours |
| Unit Price |
| Total Price |
| 1008b |
| C3.1, C3.2, C3.3 |
| Project Management/Engineering Support IAW C3.1, C3.2, C3.3 |
| T&M |
| Program Analyst – Level 1 |
| T&M Rate |
| 420 |
| $- |
| $- |
| Technical Program Manager – Level 2 |
| T&M Rate |
| 40 |
| $- |
| $- |
| Systems Engineer – Level 1 |
| T&M Rate |
| 520 |
| $- |
| $- |
| Software Engineer – Level 2 |
| T&M Rate |
| 160 |
| $- |
| $- |
| Systems Integrator/Field Technician – Level 3 |
| T&M Rate |
| 400 |
| $- |
| $- |
| 1009b |
| C3.6 |
| Travel/Other Direct Costs (NTE) |
| CR |
$30,000
| 1010b |
| C3.1, C3.2, C3.3 |
| Technical Documentation |
| FP |
NSP
| Total Period |
| $- |
B.5.6 Option Period 2 Daytona Beach International Airport
| CLIN |
| IAW SOW |
| SUPPLIES OR SERVICES |
| CLIN Type |
| Hours |
| Unit Price |
| Total Price |
| 2008b |
| C3.1, C3.2, C3.3 |
| Project Management/Engineering Support IAW C3.1, C3.2, C3.3 |
| T&M |
| Program Analyst – Level 1 |
| T&M Rate |
| 240 |
| $- |
| $- |
| Technical Program Manager – Level 2 |
| T&M Rate |
| 20 |
| $- |
| $- |
| Systems Engineer – Level 1 |
| T&M Rate |
| 480 |
| $- |
| $- |
| Software Engineer – Level 2 |
| T&M Rate |
| 80 |
| $- |
| $- |
| Systems Integrator/Field Technician – Level 3 |
| T&M Rate |
| 190 |
| $- |
| $- |
| 2009b |
| C3.6 |
| Travel/Other Direct Costs (NTE) |
| CR |
$20,000
| 2010b |
| C3.1, C3.2, C3.3 |
| Technical Documentation |
| FP |
NSP
| Total Period |
| $- |
B.5.7 BASE PERIOD - 12 Months - Tucson International Airport Base Period Starts FY 2023
| CLIN |
| IAW SOW |
| SUPPLIES OR SERVICES |
| CLIN Type |
| Unit/Hours |
| Unit Price |
| Total Price |
| 0001c |
| C3.1 |
| Airport C - First Article (FA) System in accordance with (IAW) C3.1 |
| FP |
| 1 |
| $- |
| $- |
| 0002c |
| C3.1 |
| Airport C – Pre-Delivery Documentation |
| FP |
NSP
| 0003c |
| C3.1 |
| Airport C - Factory Acceptance Testing |
| FP |
NSP
| 0004c |
| C3.1 |
| Airport C - First Article Equipment Delivery |
| FP |
NSP
| 0005c |
| C3.1 |
| Airport C - Site Acceptance Testing |
| FP |
NSP
| 0006c |
| C3.1 |
| Airport C - Contractor Acceptance Inspection |
| FP |
NSP
| 0007c |
| C3.1 |
| Airport C – Field Checkout Inspection |
| FP |
NSP
| 0008c |
| C3.1, C3.2, C3.3 |
| Site Engineering Support - Program Management/Systems Engineering: Labor (for the total quantity of Airport Scenario A FA Systems) IAW SOW C3.1, C3.2, C3.3 |
| T&M |
| Program Analyst – Level 1 |
| T&M Rate |
| 420 |
| $- |
| $- |
| Technical Program Manager – Level 2 |
| T&M Rate |
| 60 |
| $- |
| $- |
| Systems Engineer – Level 1 |
| T&M Rate |
| 520 |
| $- |
| $- |
| Software Engineer – Level 2 |
| T&M Rate |
| 320 |
| $- |
| $- |
| Systems Integrator/Field Technician – Level 3 |
| T&M Rate |
| 240 |
| $- |
| $- |
| 0009c |
| C3.6 |
| Travel/Other Direct Costs (NTE) |
| CR |
$20,000
| 0010c |
| C3.2 |
| Program Management Reports IAW C3.2 |
| FP |
NSP
| 0011c |
| C3.2 |
| Technical Meeting Reports IAW C3.2 |
| FP |
NSP
| Total Period |
| $- |
B.5.8 Option Period 1 Tucson International Airport
| CLIN |
| IAW SOW |
| SUPPLIES OR SERVICES |
| CLIN Type |
| Hours |
| Unit Price |
| Total Price |
| 1008c |
| C3.1, C3.2, C3.3 |
| Project Management/Engineering Support IAW C3.1, C3.2, C3.3 |
| T&M |
| Program Analyst – Level 1 |
| T&M Rate |
| 420 |
| $- |
| $- |
| Technical Program Manager – Level 2 |
| T&M Rate |
| 40 |
| $- |
| $- |
| Systems Engineer – Level 1 |
| T&M Rate |
| 520 |
| $- |
| $- |
| Software Engineer – Level 2 |
| T&M Rate |
| 160 |
| $- |
| $- |
| Systems Integrator/Field Technician – Level 3 |
| T&M Rate |
| 400 |
| $- |
| $- |
| 1009c |
| C3.6 |
| Travel/Other Direct Costs (NTE) |
| CR |
$30,000
| 1010c |
| C3.1, C3.2, C3.3 |
| Technical Documentation |
| FP |
NSP
| Total Period |
| $- |
B.5.9 Option Period 2 Daytona Beach International Airport
| CLIN |
| IAW SOW |
| SUPPLIES OR SERVICES |
| CLIN Type |
| Hours |
| Unit Price |
| Total Price |
| 2008c |
| C3.1, C3.2, C3.3 |
| Project Management/Engineering Support IAW C3.1, C3.2, C3.3 |
| T&M |
| Program Analyst – Level 1 |
| T&M Rate |
| 240 |
| $- |
| $- |
| Technical Program Manager – Level 2 |
| T&M Rate |
| 20 |
| $- |
| $- |
| Systems Engineer – Level 1 |
| T&M Rate |
| 480 |
| $- |
| $- |
| Software Engineer – Level 2 |
| T&M Rate |
| 80 |
| $- |
| $- |
| Systems Integrator/Field Technician – Level 3 |
| T&M Rate |
| 190 |
| $- |
| $- |
| 2009c |
| C3.6 |
| Travel/Other Direct Costs (NTE) |
| CR |
$20,000
| 2010c |
| C3.1, C3.2, C3.3 |
| Technical Documentation |
| FP |
NSP
| Total Period |
| $- |
B.6 CONTRACT
The total maximum contract value for all CLINS (Base and Optional Requirements) is awarded as follows:
B.6.1 – BASE PERIOD
| CLIN |
| IAW SOW |
| SUPPLIES OR SERVICES |
| CLIN Type |
| San Antonio |
| Daytona |
Beach
| Tucson |
| Total Proposed Price |
| 0001x |
| C3.1 |
| Airport A/B/C - First Article (FA) System in accordance with (IAW) C3.1 |
| FP |
| $- |
| $- |
| $- |
| $- |
0002x
| Airport A/B/C –Pre-Delivery Documentation |
| FP |
| NSP |
| NSP |
| NSP |
| NSP |
| 0003x |
| C3.1 |
| Airport A/B/C –Factory Acceptance Testing |
| FP |
| NSP |
| NSP |
| NSP |
| NSP |
| 0004x |
| C3.1 |
| Airport A/B/C - First Article Equipment Delivery |
| FP |
| NSP |
| NSP |
| NSP |
| NSP |
| 0005x |
| C3.1 |
| Airport A/B/C - Site Acceptance Testing |
| FP |
| NSP |
| NSP |
| NSP |
| NSP |
| 0006x |
| C3.1 |
| Airport A/B/C - Contractor Acceptance Inspection |
| FP |
| NSP |
| NSP |
| NSP |
| NSP |
0007x
| Airport A/B/C –Field Checkout Inspection |
| FP |
| NSP |
| NSP |
| NSP |
| NSP |
| 0008x |
| C3.1, C3.2, C3.3 |
| Site Engineering Support - Program Management/Systems Engineering: Labor (for the total quantity of Airport Scenario A/B/C FA Systems) IAW SOW C3.1, C3.2, C3.3 |
| T&M |
| $- |
| $- |
| $- |
| $- |
| 0009x |
| C3.6 |
| Travel/Other Direct Costs (NTE) |
| CR |
| $20,000 |
| $20,000 |
| $20,000 |
| $60,000 |
| 0010x |
| C3.2 |
| Program Management Reports IAW C3.2 |
| FP |
| NSP |
| NSP |
| NSP |
| NSP |
| 0011x |
| C3.2 |
| Technical Meeting Reports IAW C3.2 |
| FP |
| NSP |
| NSP |
| NSP |
| NSP |
| Total Period |
| $ |
| $ |
| $ |
| $ |
B.6.2 – Option Period 1
| CLIN |
| IAW SOW |
| SUPPLIES OR SERVICES |
| CLIN Type |
| San Antonio |
| Daytona |
Beach
| Tucson |
| Total Proposed Price |
| 1008x |
| C3.1, C3.2, C3.3 |
| Project Management/Engineering Support IAW C3.1, C3.2, C3.3 |
| T&M |
| $- |
| $- |
| $- |
| $- |
| 1009x |
| C3.6 |
| Travel/Other Direct Costs (NTE) |
| CR |
| $30,000 |
| $30,000 |
| $30,000 |
| $90,000 |
| 1010x |
| C3.1, C3.2, C3.3 |
| Technical Documentation |
| FP |
| NSP |
| NSP |
| NSP |
| NSP |
| Total Period |
| $ |
| $ |
| $ |
| $ |
B.6.3 – Option Period 2
| CLIN |
| IAW SOW |
| SUPPLIES OR SERVICES |
| CLIN Type |
| San Antonio |
| Daytona |
Beach
| Tucson |
| Total Proposed Price |
| 2008x |
| C3.1, C3.2, C3.3 |
| Project Management/Engineering Support IAW C3.1, C3.2, C3.3 |
| T&M |
| $- |
| $- |
| $- |
| $- |
| 2009x |
| C3.6 |
| Travel/Other Direct Costs (NTE) |
| CR |
| $20,000 |
| $20,000 |
| $20,000 |
| $60,000 |
| 2010x |
| C3.1, C3.2, C3.3 |
| Technical Documentation |
| FP |
| NSP |
| NSP |
| NSP |
| NSP |
| Total Period |
| $ |
| $ |
| $ |
| $ |
B.6.4 – Total Price
| Subtotal First Article (FP CLINs) |
| $- |
| $- |
| $- |
| $- |
| Subtotal T&M CLINs |
| $- |
| $- |
| $- |
| $- |
| Subtotal (NTE Government Provided - CR CLINs) |
| $70,000 |
| $70,000 |
| $70,000 |
| $210,000 |
| Total Contract Price |
| $ |
| $ |
| $ |
| $ |
B.7 ADDITIONAL LABOR CATEGORIES
At any time and throughout the life of the Contract, the Contractor or the Government may propose additional labor categories, rates and descriptions necessary to support requirements of a specific Task Order. These additional labor categories, rates, and descriptions will be negotiated on a case-by-case basis. The additional categories, rates and descriptions proposed, upon determination by the Government in its sole discretion that they are necessary for the scope of the effort, and the prices are fair and reasonable, may be incorporated into Attachment J002 or incorporated into a specific Task Order.
PART 1- SECTION C
DESCRIPTION/SPECIFICATIONS/STATEMENT OF WORK
C.1 Introduction and Overview This Statement of Work (SOW) defines the performance specifications for a Runway Incursion Prevention through Situational Awareness (RIPSA) system and the technical services to be provided by the Contractor in support of the Runway Incursion Reduction Program (RIRP). The Federal Aviation Administration (FAA) envisions an innovative, cost-effective product that addresses the FAA’s minimal requirements in response to this SOW.
C.1.1 Background The FAA initiated a project under the RIRP to develop a toolkit of technologies and systems for RIPSA that could be implemented using industry-developed Commercial-Off-the-Shelf (COTS) surveillance sensors. This initiative responded to recommendations from the air traffic operational community as well as the National Transportation Safety Board (NTSB) and the Department of Transportation (DOT) Office of Inspector General (OIG) recommendations.
RIPSA is the RIRP’s current initiative aimed at reinforcing protection of the Runway Safety Area (defined as the area within 250 ft. to each side of a Runway Center Line). RIPSA utilizes a “Right-Site-Right-Size" approach to address specific runway incursion causal factors identified at candidate airports. It is primarily intended to mitigate Pilot Deviations (PD) and Vehicle/Pedestrian Deviations (V/PD), which result in approximately 80% of all Runway Incursions reported to the FAA. The RIRP team will work with qualified vendors to prototype, install and conduct test evaluations of RIPSA prototype systems at candidate airports. The outcome of these evaluations will be a set of System Requirements for use in future acquisitions of RIPSA systems in the National Airspace System (NAS).
These emerging technologies and systems will improve runway incursion (RI) reduction at airports without existing ground surveillance such as Airport Surface Detection Equipment - Model X (ASDE-X) and Airport Surface Surveillance Concept (ASSC). This toolkit will utilize targeted surveillance technologies to drive direct-to-pilot annunciators at key runway entry points (referred to as ”protected intersections”) that provide “just-in-time” situational awareness to pilots and vehicle operators.
The Government reserves the right to award more than one (1) airport site to the same offeror; however, the Government intends to deploy one (1) different technological solutions to each of the three (3) airport sites and accordingly will not award the same technological solution to more than one (1) airport site.
The RIRP is proposing a multi-year plan to develop, test, and evaluate the technologies assessed under RIPSA. The RIRP team has conducted site assessments at candidate airports across the NAS, and identified and selected airports that would benefit from and be receptive to the Operational Test and Evaluation (OT&E) of prototype RI mitigation technologies. The candidate airports selected are:
· San Antonio International Airport (SAT) – Airport Scenario A - Base Year Start FY 2021
· Daytona Beach International Airport (DAB) – Airport Scenario B - Base Year Start FY 2022
· Tucson International Airport (TUS) – Airport Scenario C - Base Year Start FY 2023
The solutions proposed in response to this Screening Information Request (SIR) must be capable of providing targeted surveillance capabilities for all aircraft or vehicles at protected intersections and drive a direct-to-pilot alerting system. Scalability and adaptability to accommodate varying airport/runway configurations are essential attributes required of these proposed solutions. Additionally, in response to this solicitation, the respondent must provide evidence that the system(s) proposed meet the requirements specified in Section C.3 below.
C.1.1.1 Phase I – First Article System Installation, Adaptation, and Site Acceptance
Under Phase I, the First Article Installation, Adaptation, and Site Acceptance, the vendor must provide and install the RIPSA First Article System and successfully complete Contractor Acceptance Inspection at candidate airports. The Contractor is also responsible for the procurement, installation, and integration of the RIPSA solution as identified in Section C.3.1. In addition, Phase I will include familiarization, maintenance training, and providing documentation identified in the Section C.3.1. The specific period of performance will be specified in the order, but Phase I is expected to be completed within twelve (12) months.
Table 1: Phase I RIPSA Implementation
Phase I RIPSA Implementation – Up to 12 Months
| # |
| Milestone |
| Responsible Party |
| 1 |
| Pre-delivery Documentation |
| Contractor |
| 2 |
| Factory Acceptance Testing |
| Contractor |
| 3 |
| First Article Delivery, Installation, Optimization |
| Contractor |
| 4 |
| Site Preparation |
| Government |
| 5 |
| Site Acceptance Testing |
| Contractor |
| 6 |
| Access to Government Furnished Equipment, Data and Information (e.g., STARS Data Feed, Telco, Light Interface) |
| Government |
| 7 |
| Contractor Acceptance Inspection |
| Contractor |
C.1.1.2 Phase II – FAA Operational Evaluation
Phase II is expected to commence upon successful completion of Phase I, by issuance of a Task Order in accordance with this contract. The Task Orders/Delivery Orders will identify specific milestones to be completed, Period of Performance (POP), and type of orders to be issued, i.e. T&M, FFP. Under Phase II, the vendor must provide maintenance and operations support to the FAA until the final operational evaluation period is complete and an operational approval decision is made. For activities under Phase II, the Contractor must support passive operational evaluations and activities including, but not limited to, support of the RIPSA Concept of Operations (CONOPS) activities. The FAA is responsible for development of the CONOPS and the associated test plan for the system to be evaluated.
The Contractor must perform various testing and operational trials over the course of up to twelve (12) months to validate specifications and requirements for a RIPSA system; as well as provide support to the safety case needed to approve the RIPSA Solution at each candidate airport.
The Contractor is also responsible for the Field Checkout of the RIPSA solution as identified in Attachment J009.
Table 2: Phase II RIPSA Implementation
Phase II Operational Evaluation – Up to 12 Months
| # |
| Milestone |
| Responsible Party |
| 1 |
| RIPSA CONOPS |
| Government |
| 2 |
| Safety Risk Management Panel/Document |
| Government |
| 3 |
| Shadow Operations/Data Collection & Analysis, and Test Report(s) |
| Government |
| 4 |
| Field Checkout |
| Contractor |
| 5 |
| Operational Evaluation/Data Collection & Analysis, and Test Report(s) |
| Government |
C.1.2 Scope of Work The Contractor must provide all management, supervision, labor, facilities, equipment, material supplies, and services (except as may be expressly set forth in this Contract as furnished by the Government, Section C.4) and otherwise do all things necessary for, or incident to, the performance of the requirements set forth in Section C.3 of this Contract, as incrementally requested and authorized.
C.1.3 Objectives The Contractor must provide services under the entire SOW to assist the FAA and RIRP Program Office to achieve their objective to procure, install, test and remove RIPSA First Article Test System(s). This SOW delineates the specific functional task areas that establish the scope of this Contract.
· Task Area 1: First Article Requirements
· Task Area 2: Contract Management
· Task Area 3: Engineering Support Management
C.2 References The Contractor must research and comply with all applicable FAA and DOT Orders, See Attachment J003 for list of References and Websites, as applicable, under the guidance of the Contracting Officer’s Representative (COR) regarding existing materials and specifications for Government systems. The Contractor must ensure all work is in full compliance with:
· FAA/Department of Transportation (DOT) orders and process guidelines;
· FAA Standards for product and service quality, including FAA Quality Assurance policy described in Section 3.10.4 of the Acquisition Management System (AMS); and
· Other applicable laws, regulations, and FAA or DOT policy.
C.3 Task Requirements The Contractor must support activities in the Task Areas identified below subject to the approval of the responsible FAA officials in those areas. Specific requirements delineated under Task Areas are not all inclusive and Contractor personnel may be required to perform other tasks directly related to the overall effort described herein.
Individual Delivery Orders will generally include appropriate and necessary tasking from Task Area 1 (First Article Requirements), Task Area 2 (Contract Management) and Task Area 3 (Engineering Support Management).
C.3.1 Task Area 1 – First Article Requirements The First Article Requirements include provisions for:
· Delivery and installation of the First Article system to the designated airport(s);
· Optimization, adaptation, and check-out of the First Article system at the designated airport(s);
· Airways Facilities (AF) familiarization briefing for the First Article system;
· First and second level maintenance to the First Article system;
· Delivery of Technical Documentation, Maintenance Manuals, Training and Familiarization Material for the First Article system; and
· Optional removal/disposition of installed First Article system.
C.3.1.1 First Article Equipment Technical Performance Requirements
The RIPSA system must meet all technical performance requirements defined in Attachment J001 of the Screening Information Request (SIR), “Preliminary Program Requirements for Runway Incursion Prevention through Situational Awareness (RIPSA)”.
C.3.1.2 First Article System Description The Contractor must provide comprehensive technical documentation for the RIPSA First Article system. At a minimum, the Contractor must submit the following documents: System Description Document, Software Design Description, Software Interface Specifications, and Factory Acceptance Test (FAT) Report. The Contractor must also submit a Spurious Emission Test Report, and Electromagnetic Compatibility (EMC)/ Electromagnetic Interference (EMI) Test Report, as applicable. Contractor must comply with the following Contract Data Requirements Lists (“CDRLs”), as specified in Attachments J011, J012, J015 and J016:
CDRL A001 System Description Document Delivery Date: 30 days after Post Award Conference
CDRL A002 Software Design Description Document Delivery Date: 30 days after Post Award Conference
CDRL A003 Software Interface Control Document (ICD) Delivery Date: 30 days after Post Award Conference
CDRL A004 Factory Acceptance Test Report Delivery Date: 30 days after Technical Contact request
CDRL A005 EMI/EMC Test Report Delivery Date: 30 days after Joint Kick-Off Meeting, or as applicable
C.3.1.3 Site Engineering Support
The Contractor must develop and provide a Project Implementation Plan (PIP) detailing all the activities associated with the implementation of the First Article system at each designated airport. The Contractor must include travel estimates for all support personnel to execute the PIP in accordance with AMS T3.2.3.D.2.(1)k. The PIP must include the plans for site survey, equipment delivery, installation, optimization, and maintenance for each designated airport. The PIP must include a system configuration drawing(s) that depicts the generic location of system components on the Airport Traffic Control Tower (ATCT), airfield, or any other facility/location.
Within the scope of this task, the Contractor must assist the FAA during the site survey at each designated airport. The Contractor must advise the FAA in selecting system component locations to achieve optimum effectiveness. The Contractor must review and provide comments on the Site Survey and Site Analysis reports after they are generated by the FAA, no later than 10 days after receipt of the reports. The Contractor must assist the FAA in the development of the Site Engineering Report (SER) by providing engineering drawings as deemed necessary by the FAA. These engineering drawings must be submitted in Drawing eXchange Format (DXF) or Drawing (DWG) format. Contractor must comply with the following CDRLs, as specified in Attachments J015 and J016:
CDRL A006 Project Implementation Plan Delivery Date: 30 Days after Joint Kick-Off Meeting
CDRL A007 Site Survey Report Review/Comments Delivery Date: 10 days after Receipt of Draft Site Survey Report
CDRL A008 Engineering Drawings Delivery Date: 30 days after Receipt of Final Site Survey Report
CDRL A009 Site Engineering Report Review/Comments Delivery Date: 10 days after Receipt of Site Engineering Report
C.3.1.4 Site Implementation C.3.1.4.1 First Article Equipment Delivery The Contractor must manage the delivery of all primary, ancillary and test equipment required for the installation, optimization, end-to-end testing, and maintenance of the RIPSA First Article system. The Contractor must inspect and test all the components to ensure it is fully functional according to the First Article sub-systems product specifications prior to shipping to the designated airport. Contractor must comply with the following CDRLs, as specified in Attachments J015 and J016:
CDRL A010 First Article Equipment Delivery Delivery Date: 60 days after Final SER C.3.1.4.2 Scheduling of On-Site Work
C.3.1.4.2.1 Facility Access Advanced coordination and clearance is required to gain access to FAA facilities and Airport Authority facilities. Coordination and advance notice is the responsibility of the FAA; however, the Contractor must verify that clearance for access has been received prior to arrival at any work site, since access will be denied if proper clearances and coordination have not been obtained. Note: procedures to obtain permits or access may be different from airport to airport.
C.3.1.4.2.2 Disruption of Air Traffic Control Operations The Contractor must avoid disruptions to air traffic control operations at the designated site and the Contractor must coordinate and plan all scheduled work activity on the airfield or on any FAA facility through the FAA Program Office.
C.3.1.4.3 Equipment Installation The Contractor must submit an installation manual detailing installation, optimization, testing, and safety procedures. The installation manual must include a list and description of any test equipment used during installation and optimization activities. The installation manual must also include procedures for proper removal and disposal of all the RIPSA components.
After completion of site preparation activities performed by the FAA, the Contractor must install all the RIPSA First Article components. Installation activities must include physical placement of equipment and integration with RIPSA airfield lighting components. Installation and testing activities of the equipment must not disrupt or interfere with, nor cause any disruption or interference with the air traffic operations in any way. If dismantling of existing facilities or equipment or other measures are necessary to complete the installation, full restoration to pre-installation conditions will be the responsibility of the Contractor.
The Contractor must repair any and all damage to facility buildings or premises caused by the Contractor's activities. Damage and finish degradation of any building, electronic subsystem and other installed equipment resulting from transportation and First Article equipment installation activities must be repaired or replaced by the Contractor. The Contractor must fully document all repairs. The Contractor must be responsible for all such repairs at no additional cost to the FAA. Contractor must comply with the following CDRLs, as specified in Attachments J015 and J016:
CDRL A011 Installation Manual Delivery Date: 60 Business Days Before (BDB) installation commencement C.3.1.4.4 System Optimization The Contractor must optimize the RIPSA system upon completion of installation. System optimization must adapt and tailor specific parameters to the airport environment.
Once the RIPSA system has been optimized and tested end-to-end at a given airport, it must remain capable of meeting the technical performance requirements without the need for manual adjustments, except during maintenance or when changes in the airport environment impose the necessity to alter any system operational parameters. Contractor must comply with the following CDRLs, as specified in Attachments J015 and J016:
CDRL A012 System Optimization Delivery Date: 30 days after Equipment Installation C.3.1.4.5 External Interfaces
The Contractor must support the testing of the RIPSA First Article system interface with the Automated Radar Terminal System (ARTS) or the Standard Terminal Automation Replacement System (STARS) at the FAA William J. Hughes Technical Center. These interfaces must comply with Attachment J001 “Preliminary Program Requirements for Runway Incursion Prevention through Situational Awareness (RIPSA)” document. Upon positive interface testing results, the Contractor must integrate the RIPSA First Article system with the ARTS Gateway (AGW) or the STARS at the designated airport, as applicable.
The Contractor must support the testing of the RIPSA First Article system Light Activation interface as provided by the FAA to demonstrate Light Activation (LA) Interoperability. Contractor must comply with the following CDRLs, as specified in Attachments J015 and J016:
CDRL A013 External Interface Test Support Delivery Date: 45 BDB Integration at First Designated Airport, or as applicable
C.3.1.4.6 First Article Site Acceptance Testing
The Contractor must develop and submit the Site Acceptance Test (SAT) procedures. After the system optimization, the Contractor must conduct the SAT to ensure that the system is installed, integrated, and functioning properly. The SAT will be witnessed by an FAA representative. Upon completion of the SAT, the Contractor must prepare and deliver the SAT Report. Once the SAT is successfully completed, the Contractor must participate in the Contractor Acceptance Inspection (CAI) meeting to be held at the designated airport. The CAI confirms that the RIPSA First Article system is ready for Field Checkout and that the FAA assumes ownership of the system. Contractor must comply with the following CDRLs, as specified in Attachments J015 and J016:
CDRL A014 Site Acceptance Test Procedures Delivery Date: 60 BDB Conduct of SAT
CDRL A015 Conduct Site Acceptance Test Delivery Date: 30 days after System Optimization
CDRL A016 Site Acceptance Test Report Delivery Date: 5 days after Completion of SAT
CDRL A017 Contractor Acceptance Inspection Meeting Delivery Date: 10 days after Completion of SAT C.3.1.4.7 Configuration Control
The Contractor must provide configuration control for all the First Article configuration items (CI) installed at the designated airport(s), software versions, and documentation. At a minimum, all the Hardware Configuration Items (HWCI) must be identified, labeled, and marked “RIPSA HWCI” to provide traceability from delivery of the RIPSA First Article system throughout the duration of the Contract. The Contractor must properly identify all documents with the Contract title and number to ensure traceability to a specific version of a software package, sub-system, or a hardware component.
The Contractor must request FAA approval prior to performing updates to any equipment or software version that forms part of the RIPSA First Article system configuration installed at the designated airport. Contractor must comply with the following CDRLs, as specified in Attachments J015 and J016:
CDRL A018 Configuration Items List Delivery Date: 5 days after Completion of System Optimization
C.3.1.5 First Article Maintenance The Contractor must provide first and second level maintenance support service to commence with the CAI of the first RIPSA First Article system and continue through the end of the testing phase. The Contractor must furnish all labor, tools, test equipment, spare/repair parts, expendables, and any other technical or administrative support necessary to perform corrective and preventive maintenance. All maintenance activities must be covered by the warranty in accordance with Section H.4 of the SIR. The Contractor must submit a Maintenance Plan that includes at a minimum:
· Description of the different maintenance levels;
· Procedures for each maintenance level;
· Skills requirements for each maintenance level; and
· Site spares/repair parts inventory.
Contractor must comply with the following CDRLs, as specified in Attachments J015 and J016:
CDRL A019 Maintenance Plan Delivery Date: 45 days after Post Award Conference C.3.1.5.1 Hardware and Software Maintenance The Contractor must provide all preventive and corrective maintenance of the RIPSA hardware and software components. The FAA will allow the Contractor and approved agents, reasonable access to inspect, update, maintain, repair, test, or make modifications during normal business hours and other hours mutually agreed to by the parties. The Contractor must obtain FAA approval prior to implementing any hardware and software components change(s).
The Contractor must submit a detailed first level and second level engineering maintenance manual. The manual must include all of the maintenance procedures that the trained personnel must follow to perform preventive, periodic and corrective maintenance on the equipment installed in its operating environment. Corrective site maintenance will consist of removal and replacement of failed Line Replaceable Units (LRUs) to restore service. Contractor must comply with the following CDRLs, as specified in Attachments J015 and J016:
CDRL A020 Engineering Maintenance Manual Delivery Date: TBD C.3.1.5.2 Training The Contractor must host a training material review conference at a location to be designated by the FAA. The Contractor must present to FAA representatives the fully developed training packages for technical users. The Contractor must correct errors, omissions and deficiencies in the training material discovered during the training material review conference. The training material must equip the technical users with the necessary knowledge to provide onsite RIPSA system maintenance. Contractor must comply with the following CDRLs, as specified in Attachments J015 and J016:
CDRL A021 Maintenance Training Conference Briefing Delivery Date: TBD C.3.1.6 Removal / Disposal If requested by the FAA, the Contractor must remove and dispose of any and all RIPSA components in accordance with applicable local, state, and federal disposal laws. The Installation Manual must include procedures for proper removal and disposal of all the RIPSA components. Contractor must comply with the following CDRLs, as specified in Attachments J015 and J016:
CDRL A022 De-Installation/Disposal of First Article System Delivery Date: 90 days after Receipt of Request by CO
C.3.2 Task Area 2 – Contract Management The Contractor must provide the necessary personnel to manage and administer the work required under this SOW. The Contractor must identify a Program Manager (PM) with the minimum experience of six (6) years as required in Attachment J002, who must serve as the principal focal point responsible for all aspects of the work being performed under this SOW including but not limited to: cost, schedule, deliverables status, performance, and risks.
C.3.2.1 Program Management The Contractor must manage the activities, personnel, resources, and subcontracts involved in the performance of the RIPSA First Article system Contract so as to mitigate risk, meet requirements, and achieve the program’s scheduled milestones. The Contractor must monitor and control the effort in accordance with approved work plans and schedules. The Contractor must also provide the FAA with clear, timely, and proactive communication on the status of planned and completed activities. The Contractor must describe the Contractor’s approach to managing the effort, mitigating risk, and delivering high-quality products and services that meet requirements in a Program Management Plan. Contractor must comply with the following CDRLs, as specified in Attachments J013 and J014:
CDRL B001 Program Management Plan Delivery Date: 10 Business Days After (BDA) Contract Award
C.3.2.2 Contract Master Schedule The Contractor must develop and maintain an overall Contract Master Schedule to manage all the activities associated with this SOW. The schedule must be based on the Contractor Work Breakdown Structure (CWBS). The Contract Master Schedule must contain, at a minimum, the activities, durations, deliverables and dependencies among the Contractor, Sub-contractors, and FAA activities. The Contractor must ensure that the schedule portrays a plan to meet the milestones and delivery requirements of this effort.
The Contractor Program Manager must track the progress and present the Contract Master Schedule to the COR at the beginning of each month. The Contractor must provide an adequate explanation to the COR for any proposed changes to the submitted Contract Master Schedule. No scope or schedule changes will be official until approved by the FAA Contracting Officer. The Contractor must use Microsoft (MS) Project 2010 or a later version to develop the Contract Master Schedule. Contractor must comply with the following CDRLs, as specified in Attachments J013 and J014:
CDRL B002 Contractor Work Breakdown Structure Delivery Date: 15 Business Days After (BDA) Contract Award
CDRL B003 Contract Master Schedule Delivery Date: 10 days after Post Award Conference and monthly thereafter
C.3.2.3 Monthly Status Reports The Contractor must submit monthly status reports. The monthly status reports must include an updated Contract Master Schedule, project accomplishments, issues, risks and risk mitigation strategies. The monthly report must include financial data including incurred labor costs, project travel costs, Other Direct Costs (ODC), as well as cumulative amounts and monthly burn rate. Contractor must comply with the following CDRLs, as specified in Attachments J013 and J014:
CDRL B004 Monthly Status Report Delivery Date: Monthly by the 10th calendar day of each month
C.3.2.4 Meetings During the Covid-19 working restrictions, all meetings may be held remotely at the discretion of the Government or Contractor. This may be mutually agreed upon and must be requested in writing 5 business days prior by either party.
C.3.2.4.1 Post Award Conference The Contractor must participate in a Post Award Conference with the FAA to be held at the Contractor’s facility. During the Post Award Conference, the Contractor must brief the FAA on the Contractor’s Program Management Plan for satisfying the tasks to be performed under this SOW. Contractor must comply with the following CDRLs, as specified in Attachments J013 and J014:
CDRL B005 Post Award Conference Briefing Delivery Date: 30 days after Contract Award C.3.2.4.2 Joint Kick-off Meeting and Site Survey The Contractor must participate in a Joint Kick-off meeting at the designated airport. During the Joint Kick-off meeting, the Contractor must brief the local FAA representatives and Airport Authority representatives on the Contractor’s RIPSA product. This meeting will present an opportunity for the Contractor to have a better understanding of the specific airport environment.
The Contractor must provide site preparation and infrastructure requirements for the First Article Equipment to be detailed in a Siting Analysis Report (SAR). Contractor must comply with the following CDRLs, as specified in Attachments J013 and J014:
CDRL B006 Site Specific Siting Analysis Report Delivery Date: 60 days after Post Award Conference C.3.2.4.3 Technical Interchange Meetings Technical Interchange Meetings (TIMs) are to be held as necessary to ensure effective resolution of issues throughout the life of the contract. The purpose of these meetings will be to identify, discuss and resolve technical, schedule, or programmatic issues associated with the Contract in general or with a specific task. These meetings will be conducted to discuss the status of site-specific implementation activities.
The Contractor must participate in weekly, bi-weekly, or monthly meetings and/or teleconferences as deemed necessary by the COR. The Contractor must provide a Field Checkout Inspection for the First Article Equipment. This inspection must meet the requirements specified in Attachment J010. Contractor must comply with the following CDRLs, as specified in Attachments J011 and J012:
CDRL B007 Field Checkout Delivery Date: TBD
C.3.3 Task Area 3 – Engineering Support Management The FAA anticipates that engineering support will be required during the test phase. Engineering support is divided into General Engineering Support and System Engineering Support, as outlined below.
C.3.3.1 General Engineering Support The Contractor must perform a range of General Engineering functions. These general engineering support services include but are not limited to:
· Interface development for integration of RIPSA to other airport safety applications;
· Demonstrations of RIPSA proposed enhancements;
· Preparing technical briefings; and
· Support development of FAA’s Safety Risk Management Document.
C.3.3.2 System Engineering Support The Contractor must provide systems engineering support as requested by the FAA. Performance under this task includes but is not limited to:
· Participating in Design Reviews;
· Refinement of RIPSA system technical documentation; and
· Addressing technical deficiencies of the RIPSA system.
C.4 FAA Furnished Equipment and Services The FAA will be responsible for providing the following equipment and services to the Contractor in support of the RIPSA system implementation at FAA facilities.
· Electrical power and Grounding The FAA will be responsible for providing electrical power and grounding for the RIPSA products up to the FAA demarcation point.
· Equipment Racks At some facilities, the FAA may require the Contractor to use existing FAA equipment racks.
· Equipment Space The FAA will provide space allocation for the required RIPSA equipment and installation.
C.5 Services C.5.1 Site Preparation The FAA will be responsible for conducting any site preparation necessary to accommodate the RIPSA system. The FAA will require the Contractor to provide site preparation and infrastructure requirements. The site preparation will include siting analysis, construction of a tower if necessary, equipment shelter, trenching, grounding, power, and running cables.
C.5.2 Siting Analysis The FAA will be responsible for conducting the siting analysis; however, Contractor must assist the FAA with such siting analysis.
C.5.3 Contractor Acceptance Inspection A FAA representative must oversee the Site Acceptance Test. If the FAA determines that the First Article System meets all technical and performance requirements under the Contract, then the FAA will accept the RIPSA equipment.
C.5.4 Test and Evaluation The FAA will test and evaluate the First Article system during the FAA’s Operational Evaluation phase that commences after SAT is complete. The Operational Evaluation results will be used to generate system requirements for a RIPSA acquisition program.
C.5.5 Environmental Control The FAA and Airport Authority will provide all environmental permits and controls regarding the installation of the equipment.
C.5.6 Facility Access The FAA will provide the Contractor with access to FAA facilities, airport buildings and grounds including any escorts or coordination of badges.
C.5.7 Physical Security The Contractor must install the RIPSA components in controlled access facilities.
C.6 Travel/Other Direct Cost The Contractor must obtain FAA authorization of travel prior to the commencement of travel. All travel must be compliant with 3.3.2-2 Reimbursement for Travel and Subsistence (April 2010)
Travel is reimbursed at Cost – No Fee.
Table 3 – Consolidated List of CDRL Descriptions
| CDRL |
| SOW |
Section
| Deliverable Name |
| Description |
| Delivery |
A001
C.3.1.2
System Description Document
| The Contractor must provide a comprehensive technical system description document, including all subsystems for the RIPSA First Article system. |
| 30 days after Post Award Conference |
| A002 |
| C.3.1.2 |
| Software Design Description Document |
| The Contractor must provide a comprehensive software system description document for the RIPSA First Article system. |
| 30 days after Post Award Conference |
| A003 |
| C.3.1.2 |
| Software Interface Control Document (ICD) |
| The Contractor must provide an ICD description document for the RIPSA First Article system providing the characteristics of the interface between the system and external users. |
| 30 days after Post Award Conference |
| A004 |
| C.3.1.2 |
| Factory Acceptance Test Report |
| The Contractor must support a Factory Acceptance Test for the RIPSA First Article system. |
| 30 days after Technical Contact request |
| A005 |
| C.3.1.2 |
| EMC/EMI Test Report |
| The Contractor must also submit Spurious Emission Test Report, and EMC/EMI Test Report, if applicable. |
| 30 days after Joint Kick-Off Meeting, or as |
applicable
| A006 |
| C.3.1.3 |
| Project Implementation Plan |
| The Contractor must develop a Project |
Implementation Plan 30 Days after Joint
| (PIP) detailing all the activities associated with the implementation of the First Article system at each designated airport. The PIP must include the plans for site survey, equipment delivery, installation, optimization, and maintenance for each designated airport. |
| Kick-Off Meeting |
| A007 |
| C.3.1.3 |
| Site Survey Report Review/Comments |
| The Contractor must assist the FAA during the site survey at each designated airport. The Contractor must advise the FAA in selecting system component locations to achieve optimum effectiveness. |
| 10 days after Receipt of Draft Site Survey Report |
| A008 |
| C.3.1.3 |
| Engineering Drawings |
| The Contractor must assist the FAA in the development of the Site Engineering Report (SER) by providing engineering drawings as deemed necessary. These engineering drawings must be submitted in Drawing eXchange Format (DXF) or Drawing (DWG) format. |
| 30 days after Receipt of Final Site Survey Report |
| A009 |
| C.3.1.3 |
| Site Engineering Report Review/Comments |
| The Contractor must assist the FAA in the development of the Site Engineering Report (SER) by providing engineering |
| 10 days after Receipt of Site Engineering Report |
deliverables as deemed necessary.
| A010 |
| C.3.1.4.1 |
| First Article Equipment Delivery |
| The Contractor must manage the delivery of all primary, ancillary and test equipment required for the installation, optimization, end-to- end testing, and maintenance of the RIPSA First Article system. |
| 60 days after Final SER |
| A011 |
| C.3.1.4.3 |
| Installation Manual |
| The Contractor must install all the RIPSA First Article components to include physical placement of equipment and integration with RIPSA airfield lighting components. |
| 60 Business Days Before (BDB) |
installation
| A012 |
| C.3.1.4.4 |
| System Optimization |
| The Contractor must optimize the RIPSA system upon completion of installation. |
| 30 days after Equipment Installation |
| A013 |
| C.3.1.4.5 |
| External Interface Interface Test Support |
| The Contractor must support the testing of the RIPSA First Article system interface with the ARTS or the STARS at the FAA William Hughes Technical Center. |
| 45 BDB |
Integration at First Designated Airport, or as applicable
| A014 |
| C.3.1.4.6 |
| Site Acceptance Test Procedures |
| The Contractor must develop and submit the Site Acceptance Test (SAT) procedures. After the system optimization, the Contractor must |
conduct the SAT to
60 BDB
Conduct of SAT ensure that the system is installed, integrated, and functioning properly.
| A015 |
| C.3.1.4.6 |
| Conduct Site Acceptance Test |
| The Contractor must conduct the SAT, that will be witnessed by an FAA representative. |
| 30 days after System Optimization |
| A016 |
| C.3.1.4.6 |
| Site Acceptance Test Report |
| The Contractor must prepare and deliver the SAT Report |
| 5 days after Completion of SAT |
| A017 |
| C.3.1.4.6 |
| Contractor Acceptance Inspection Meeting |
| The Contractor must confirm that the RIPSA First Article system is ready for field testing and the FAA will assume ownership of the system. |
| 10 days after Completion of SAT |
| A018 |
| C.3.1.4.7 |
| Configuration Items List |
| The Contractor must provide configuration control for all the First Article configuration items (CI) installed at the designated airport(s), software versions, and documentation. |
| 5 days after Completion of System Optimization |
| A019 |
| C.3.1.5 |
| Maintenance Plan |
| The Contractor must provide all preventive and corrective maintenance of the RIPSA hardware and software components. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .