Amendment 1 SAI SIR Section J.6 01.10.24v2.docx

BASIC ORDERING AGREEMENT (BOA) BETWEEN

FEDERAL AVIATION ADMINISTRATION (FAA)

AND

XXXXX for

SURFACE AWARENESS INITIATIVE (SAI)

WHEREAS, the Federal Aviation Administration (the “FAA”) wishes to purchase SAI products off the Qualified Product List (QPL) as specified herein from the vendor (XXXXX).

NOW THEREFORE, the FAA and XXXXX (collectively the “Parties”) mutually agree as follows:

ARTICLE 1. PARTIES

The parties to this Agreement are the Federal Aviation Administration (FAA) and XXXXX.

ARTICLE 2. SCOPE

a. The purpose of this Agreement between the Federal Aviation Administration (FAA) and the vendor is to establish the terms for purchasing products off the QPL. Those terms are contained in the embedded documents in attachment 1.

ARTICLE 3. EFFECTIVE DATE and TERM The effective date of this Agreement is the date on which it is signed by the FAA or Vendor, whichever is later. This Agreement will remain in effect until the Agreement is concluded in accordance with Article 4 unless earlier terminated by the parties as provided herein.

ARTICLE 4. SCHEDULE

This agreement is effective for 15 years starting on the effective date stated in Article 3 above.

The FAA reserves the ability to periodically re-open the QPL for new entrants and new requirements. The FAA anticipates that the QPL will be re-opened 18 Months after the initial establishment, and then every 3 years thereafter. FAA reserves the right to alter this schedule at FAA’s convenience.

ARTICLE 5. LEGAL AUTHORITY

This Agreement is entered into the authority of 49 U.S.C. 106(1) and (m), which authorizes agreements and other transactions on such terms and conditions as the FAA Administrator determines necessary.

ARTICLE 7. POINTS OF CONTACT

FAA Parties For the FAA regarding this Agreement

ARTICLE 8. CHANGES, MODIFICATIONS

Changes and/or modifications to this Agreement will be in writing and signed by a FAA Contracting Officer and the vendor. The modification will cite this Agreement, and will state the exact nature of the modification. No oral statement by any person will be interpreted as modifying or otherwise affecting the terms of this Agreement.

ARTICLE 9. TERMINATION

The FAA may terminate this Agreement with or without cause with a 30-day notice in writing.

AGREED:

Vendor Federal Aviation Administration

Official:

Title: Contracting Officer

Date: ________________________ Date: ___________________

Witness: ____________________

Attachment 1 image1.emf

Microsoft_Word_97_-_2003_Document.doc image2.emf

SAI SIR Section E 12.27.23.docx

TABLE OF CONTENTS

Section E - Inspection and Acceptance 2

E. 1 AMS 3.1-1 Clause and Provision Incorporated by Reference (July 2019) 2

E. 2 Government Inspection and Acceptance 2

E.2.1 Acceptance Data Package 3

E. 3 Deviations and Waivers 3

E. 4 Deficiencies 4

Surface Awareness Initiative

12/27/2023 Section E – Inspection and Acceptance

- Inspection and Acceptance

AMS 3.1-1 Clause and Provision Incorporated by Reference (July 2019)

This screening information request (SIR) or contract, as applicable, incorporates by reference the provisions or clauses listed below with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make the full text available, or Offerors and contractors may obtain the full text via Internet at https://fast.faa.gov/contractclauses.cfm.

CLAUSE

TITLE

DATE

3.10.4-2

Inspection of Supplies - Fixed Price

November 1997

3.10.4-4

Inspection of Services - Both Fixed-Price & Cost Reimbursement

April 1996

3.10.4-5

Inspection - Time and Materials and Labor Hour

April 1996

3.10.4-11

Inspection – Dismantling, Demolition, or Removal of Improvements

April 1996

3.10.4-14

Assignment of a Quality Reliability Officer (QRO)

July, 2023

3.10.4-16

Responsibility of Supplies

April 1996

3.10.4-25

Alternate Quality System Plan

April 2009

3.10.4-26

Technical Data Quality Requirement for NAS Procurements

January 2004

Government Inspection and Acceptance

The Contracting Officer or their appointed Government representative, will verify that the Contractor’s system complies with contract requirements. The Government representative has the authority to witness tests and inspect and accept or reject supplies provided under this contract. Details on the Contractor Officer’s authority and appointed representatives are contained in Section G.

The Contractor must provide the Government representative documentation and information upon request, and site access to verify that all equipment has been installed consistent with configuration, infrastructure, safety, and security requirements in effect at the time of their contractual acceptance. The Government representative may elect to monitor certain deliverables remotely.

The Government will perform final inspection and acceptance on all system components and aggregates, including all software, firmware, and hardware under Part I-Section F, Delivery or Performance, of this contract including installation services. Final acceptance consists of satisfactory completion of all inspections and tests associated with the delivered items and is indicated in the Acceptance Data Package approval letter from the Contracting Officer. Final acceptance shall be made by the Contracting Officer or designated representative.

The Contractor must provide all artifacts, perform all activities, and meet all criteria defined in Section C.4.2.9.7 to obtain Government Acceptance.

Acceptance Data Package

Final acceptance occurs when the Contracting representative issues the ADP approval letter to the contractor. The ADP is created by the contractor and contains at a minimum:

· Verification testing of end-to-end SAI Services will be performed jointly by the Government and the Contractor at the installation site in accordance with the procedures specified in the Site Acceptance Test Procedures (SATP). Acceptance of end-to-end Services Verification Test results in the SATP are indicated by Government representive signatures in the signature block.

· Service Acceptance Test (SAT) Report. Completed SAT Report, including Government signed test results in the SATP and any checklists, to provide evidence that the system meets the SAI MRD (Attachment J.1) and Performance Work Statement (PWS), and demonstrate that the system was installed IAW site design drawings and specifications. The SAT Report also needs to include a complete assessment of the system operational performance, based on data collected during on-site tests.

· Contractor Acceptance Checklist. Completed CAC SAI-IM05 to ensure that the installation is complete and meets requirements of the SAI MRD (Attachment J.1) and the Performance Work Statement (PWS). Any findings of deficiencies must be documented. The items identified as deficiencies must be resolved or have solid plan/date for remediation prior to system acceptance, unless agreed upon by the Government Team.

· Documentation of the hardware and software configuration of the installed system components as tested, including an inventory and identification of all units and line replaceable units (LRU) installed.

· Red-Lined Drawings. One complete set of facility drawings red-lined during the installation process.

The contractor must certify that the system, as installed, meets all specifications and operational performance requirements, to obtain Government acceptance.

Deviations and Waivers

The Contractor may request, via deviation or waiver, relief from one (1) or more specific requirements for a specific service order. At the time of request, the Contractor must describe in detail the discrepancy and the exact departure from the requirement(s). The Contractor must describe the reasons that make it impossible or unreasonable to comply with the requirement(s) within the approved delivery schedule. Consideration to the Government must be proposed with each request.

Requests for permanent departures from requirement(s) must be accomplished in accordance with the Configuration Management requirements.

A deviation is defined as a written authorization to temporarily depart from one (1) or more specific requirements for a specific service order.

A waiver is defined as a written authorization to provide a service that does not meet contract requirements but is nevertheless considered suitable for operation “as is.” The waiver applies to specific requirements for a specific order for the duration of that service implementation.

All requests for deviation or waiver must be submitted by letter to the Contracting Officer.

Deficiencies

If the Contractor independently discovers a deficiency in accepted supplies or services, the Contactor must submit to the Contracting Officer, in writing within 10 calendar days after discovery, a recommendation for corrective actions, together with supporting information in sufficient detail for the Contracting Officer to determine what corrective action, if any, should be taken.

The Contractor must promptly comply with any written direction from the Contracting Officer to correct such a deficiency, at no increase in the contract price.

image3.emf

SAI SIR Section J.2 12.27.23.docx

12/27/2023 Attachment J.2 – Strategic Plan

12/27/2023 Attachment J.2 – Strategic Plan

Strategic Plan

Version 1.0

27 December 2023

Introduction

The purpose of this Strategic Plan is to facilitate communication between the Federal Aviation Administration (FAA) and Industry for the Surface Awareness Initiative (SAI). This document provides overarching program objectives and vision for the deployment of solutions that will provide surface situational awareness to operational environments that do not have existing Airport Surface Detection Equipment (ASDE) or Airport Surface Surveillance Capability (ASSC) systems. This plan also provides information about the planned FAA acquisition approach and provides insight on issues of importance to the FAA. The information and timelines in this plan are subject to change.

In 2021, an Operational Needs Assessment (ONA) was conducted that identified the need for increased surface situational awareness at airports which currently are not equipped with surface surveillance equipment to reduce runway incursions. The FAA has identified over 230 airports that are potential candidates for an SAI solution. The ONA resulted in the identification of the first 45 candidate airports (Attachment A).

SAI will deliver innovative, cost-effective technological solutions to airports without existing surface surveillance capabilities to expand Air Traffic Control’s (ATC) surface situational awareness. SAI solutions will leverage Automatic Dependent Surveillance – Broadcast (ADS-B) as a primary source of aircraft position both on the surface and in airport arrival and departure corridors. These ‘targets’ will be displayed overtop an airport surface map that will at a minimum depict runways, taxiways, hold ramps, and other movement areas.

Objectives

The FAA is pursuing implementation of SAI solutions with the greatest sense of urgency. These solutions must be effective in providing enhanced surface situational awareness with an architecture that supports rapid deployment with minimal impact to existing infrastructure and operations.

SAI solutions must meet minimum performance requirements; however, the FAA is also interested in enhanced capabilities beyond minimum performance as well as future expansion of inherent performance that may be pursued after initial solution commissioning.

Program Scope

The SAI program includes additional scope items beyond provision of the surface situational awareness solution. The SAI solution provider must provide these services:

· Solution Installation – The solution provider must be responsible for the installation of all on-site equipment. This work must be in accordance with prescribed policy and requirements. At FAA facilities, the solution provider must consult and get approvals from the designated FAA representative for all matters relative to placement, power, integration, and/or any other aspects they identify.

· Training – The solution provider must deliver documentation (to include user manual) and materials that describe the functionality and operation of the solution to support the FAA’s development of web-based training courses. The solution provider must conduct on-site user training at each site prior to completion of solution implementation.

· Sustainment Services – The solution provider must monitor the status of the SAI solution. The solution provider must report anticipated and unanticipated service disruption to the installation site specific focal point. The solution provider must repair and restore service, address SAI solution outages, and maintain solution as necessary to ensure continuity of service.

· Upgrades – The solution provider must provide any routine upgrades to their SAI solution. Any upgrades must not negatively impact the capability of the equipment installed to meet all qualification requirements.

Acquisition Approach

Under this SAI acquisition, the FAA intends to develop a Qualified Product List (QPL), from which the FAA and other entities, such as airport authorities (using their independent authority and processes), may elect to procure products for surface situational awareness[footnoteRef:1]. A QPL establishes a list of qualified products that have been evaluated and meet all applicable qualification requirements. [1: While other entities outside of the FAA may utilize the FAA’S QPL for commercial SAI applications, they are not bound to FAA contract vehicles nor pricing. However, entities may not represent any product as a QPL product that has not been selected by FAA for the QPL.]

Initial establishment of the QPL will be based on a Screening Information Request (SIR) where Offerors Technical Volumes will be evaluated on PASS/FAIL criteria. After evaluation of the Technical Volumes, those submissions that “PASS” will be selected to conduct an Operational Capability Demonstration (OCD). The OCD, which will also be evaluated on PASS/FAIL criteria, will ensure solution compliance to minimum performance requirements. In addition, the OCD will serve as an opportunity for Offerors to demonstrate performance beyond what is required (enhanced functionality) in time allotted. When selected for the OCD, the Offeror must submit the remaining SIR Volumes (e.g., price, past performance) for FAA evaluation.

If the Offeror passes both the Technical Volume Evaluation and OCD, the solution will be placed on the QPL. For work orders from the QPL, the FAA has identified four categories within the source selection process to allow the Government to fit the selection criteria to the specifics of a particular airport. With a possibly large scope of airports for which work orders can be made, this allows the award decision to better align with the environment of the airport identified for a SAI solution. Work orders from the QPL for three categories will be made on Best Value determination, while one category will be awarded using Lowest Price, Technically Acceptable (LPTA). Best value describes the solution that is the most advantageous to the FAA based on technical evaluation (adjectival rating based on identified strengths and weaknesses), past performance, total evaluated price, and FAA’s independent risk and opportunity assessment. Under LPTA, in addition to Section M.2 Determination of Responsibility, Section M.3.3 criteria for Basis of Exclusion and all other criteria identified in the SIR, Technically Acceptable, is defined as solution that meets the critical requirements as defined in Attachment J-3 Requirements Compliance Matrix.

To ensure an understanding of whether a proposed enhanced technical capability is identified as either an enhanced capability or opportunity, the following examples are provided:

The following examples may constitute enhanced functionality beyond minimum performance:

· User displays that enable entry and viewing of dynamic data (i.e., scratch pad)

· Differentiating targets based on target report quality metrics

· Mode C altitude correction

· Ability to record and playback data

The following items are examples of opportunities that a proposed solution could provide:

· Alerting / notifications of targets in collision conflict

· Incorporating target position information from other sources, while still being compliant with minimum performance requirements

· SAI solution can be made available for operational use in an accelerated timeframe that results in a delivery faster than that required in Section F

· SAI solution’s cybersecurity attributes have been evaluated by a FedRAMP accredited third party assessment organization

The QPL will be reassessed after 18 months and then every 3 years thereafter. Candidates that previously failed to make the QPL would be able to qualify with technical proposal submission and an OCD. Solutions already on the list could also resubmit proposals, to account for pricing adjustments and/or enhance capabilities, and consequently, update their best value determination. At the time of QPL reassessment, the FAA may also request written confirmation of each current QPL vendor’s desire to remain on the QPL. Any vendor not responding to the request for confirmation by the stated deadline in that request may be deleted off the QPL as an indication of lack of interest. Vendors may request to withdraw at any time by submitting a written request to the CO.

After initial deployment of an SAI solution pursuant to a work order from the QPL, the FAA may elect to issue discrete task orders to modify the provided service. Situations that may constitute such a need would be to address ATC suitability issues and airport configuration changes.

Attachment A

Initial Airport Site Listing

The first five airports have been prioritized to receive a SAI solution, however, the FAA reserves the right to revise the priority, as needed. The FAA will identify a site priority listing of the remaining 40 sites as a future activity.

A-1 image2.emf image1.png image4.emf

SAI SIR Section J.3 12.27.23.xlsx

MRD

3.1 Critical Functional Requirements

3.1.1 Display System

[SAI-1] The SAI system must include display(s) running surface awareness applications that provide increased situational awareness to ATC personnel. Note: The quantity of displays will be based on individual site surveys. Demonstration (D)

[SAI-2] The surface awareness application must display Targets that are detected by the SAI system and are within the defined Coverage Volume. Demonstration (D)

[SAI-3] The surface awareness application must differentiate aircraft from vehicles. Demonstration (D)

[SAI-4] The surface awareness application must include a map that accurately depicts the: Demonstration (D)

a. Runways, taxiways, and other areas of an airport/heliport which are utilized for taxiing/hover taxiing, air taxiing, takeoff, and landing of aircraft. Demonstration (D)

b. Gates, ramps, parking areas, and other areas of an airport where aircraft may be present. Demonstration (D)

[SAI-5] The surface awareness application must be user interactive, including the following basic functions: Demonstration (D)

a. Pan Demonstration (D)

b. Zoom Demonstration (D)

c. Selectable Data Blocks for displayable Targets Demonstration (D)

d. System Time Demonstration (D)

e. Rotate the map Demonstration (D)

[SAI-6] The surface awareness application must display the current System State. Demonstration (D)

3.1.2 Surveil Target

[SAI-7] The source of SAI Target information must be derived from ADS-B data. Demonstration (D)

[SAI-8] The SAI system must detect actively transmitting ADS-B equipped aircraft. Inspection (I) Demonstration (D)

[SAI-9] The SAI system must detect actively transmitting ADS-B equipped ground vehicles (e.g., trucks). Inspection (I) Demonstration (D)

[SAI-10] The display of Targets must be configurable based on location and altitude. Demonstration (D)

3.1.3 Equipment

[SAI-11] The SAI display used in the tower cab must have mounting options compatible with existing tower configurations, including VESA and freestanding mounting. Inspection (I)

[SAI-12] The display presentation must be discernable in all lighting conditions. Demonstration (D)

[SAI-13] The display equipment must provide user controls for brightness, contrast, and sharpness. Demonstration (D)

[SAI-14] The display must have a diagonal viewing size of at least 20 inches. Inspection (I)

[SAI-16] SAI equipment installed outdoors must be protected from the environment. Inspection (I) Demonstration (D)

[SAI-17] SAI equipment installed inside of FAA facilities must not interfere with operations or existing equipment. Analysis (A)

[SAI-18] SAI equipment connected to facility power must comply with the power quality requirements of FAA-G-2100J, Electronic Equipment, General Requirements, Paragraph 3.1.1.2 Analysis (A)

[SAI-19] SAI solutions must adhere to FAA spectrum management requirements in accordance with FAA Order 6050.32, Spectrum Management Regulations and Procedures Manual, and FAA Order 6050.19E, Radio Spectrum Planning. Analysis (A)

3.1.4 System Control

[SAI-20] The SAI solution must include an interface(s) that provides control AND monitoring of the service to the service provider. Demonstration (D)

[SAI-21] The SAI system must automatically collect service performance data in support of the Technical Performance Measures Report (TPMR). Demonstration (D)

[SAI-22] The SAI system must automatically monitor the health of subsystems to determine the System State. Demonstration (D)

[SAI-23] The SAI system must periodically synchronize its system time to Coordinated Universal Time (UTC). Demonstration (D)

[SAI-24] The timestamps in all messages must be relative to UTC. Inspection (I)

3.1.5 Information Systems Security

3.2 Critical Performance Requirements

[SAI-26] The SAI system must detect ADS-B equipped Targets located on the airport surface and within 5 nautical miles of each runway threshold greater than or equal to 99 percent of the time. Analysis (A)

[SAI-27] The SAI system must be capable of receiving AND decoding all ADS-B messages, including both 1090 Mega Hertz (MHz) and 978 MHz sources, in accordance with DO-260B AND DO-282B. Demonstration (D)

[SAI-28] The maximum delay between the receipt of the last bit of a valid ADS-B position message at the ground station and the display of the Target on the controller application must be less than or equal to 1.0 seconds 99% of the time. Analysis (A)

[SAI-29] All Targets within the defined Coverage Volume must be updated and maintained on the display at least every:

1.0 sec 95% of the time for non-staionary 1090ES Targets

5.5 sec 85% of the time for stationary 1090ES Targets

1.3 sec 95% of the time for UAT Targets. Demonstration (D)

[SAI-30] The display map registration must have an accuracy of at least 20 feet. Analysis (A)

[SAI-31] The SAI system Adjusted Service Availability must be greater than or equal to 0.99 over the preceding 12 months. Analysis (A)

[SAI-32] The SAI system must have a Mean Time-to-Repair (MTTR) less than or equal to 0.5 hours. Analysis (A)

[SAI-33] The SAI system Target loading capacity must be greater than or equal to 200 Targets located anywhere within the coverage area. Analysis (A)

PWS

Requirements Yes/No Notes

Operations and Maintenance

C.4.2.1 Program Management

C.4.2.1.1 Meeting Support

C.4.2.1.2 Integrated Master Schedule

C.4.2.1.3 Data Management

C.4.2.1.4 Risk Management

C.4.2.1.5 Configuration Management

C.4.2.2 Systems Engineering

C.4.2.3 Training

C.4.2.5 System Safety

C.4.2.6 Service Requalification Testing

C.4.2.7 Service Performance Monitoring

C.4.2.7.1 Discrepancy Management

C.4.2.7.2 Discrepancy Database

C.4.2.8 Service Monitoring, Operations, and Maintenance

C.4.2.8.1 Customer Support Service

C.4.2.8.2 Service Performance

C.4.2.8.3 Service Maintenance

Implementation

C.4.2.9 Implementation

C.4.2.9.1 Implementation Planning

C.4.2.9.2 Design Site Survey

C.4.2.9.3 Site Design

C.4.2.9.4 Site Readiness

C.4.2.9.5 Site Implementation

C.4.2.9.6 Service Acceptance Test

C.4.2.9.7 Equipment Storage

C.4.2.9.8 Damage to Site image5.emf

SAI SIR Section J.4 12.27.23.xlsx SAI CDRLs

Electronic (1)

Electronic (1)

Electronic (1)

Electronic (1)

Electronic (1)

Electronic (1)

Electronic (1)

Electronic (1)

Electronic (1)

Electronic (1)

Electronic (1)

Electronic (1)

Notes:

*1. Data Item Description (DID) identification number where detailed preparation instructions are provided.

*2. The specific paragraph number of the applicable contractual document that contains the tasking that generates a requirement for the data item. Normally, this will be the Performance Work Statement (PWS) paragraph.

*3. A-Requires Government approval, I-for information only.

*4. The Contractor must provide the deliverables in "Calendar" days unless otherwise specified.

*5. Addressee responsible for approval.

Frequency Acronyms: Submission Acronyms:

ONE/R = One Time with Revisions DAC = Days after Contract Award

MTHLY = Monthly DARC = Days after Receipt of Comments

R/ASR = Revisions as Required DARO = Days after Receipt of Order

ASREQ = As Required image6.emf

SAI SIR Section J.5 12.27.23.docx

Attachment J.5

12/27/2023 Data Item Descriptions

DATA ITEM DESCRIPTION

1. TITLE

Integrated Master Schedule

2. NUMBER

PM01-IMS

3. DESCRIPTION/PURPOSE

The Integrated Master Schedule is used to plan, manage, and control all program activities throughout the required reporting period.

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.1.2

Format: Contractor format is acceptable

Contents: The IMS must identify all contract deliverables and critical milestones (including applicable support activities) to meet SAI program activities defined in the Section C, SAI Performance Work Statement (PWS), and Section F, Deliveries or Performance.

Key Elements of Detailed Schedules. The key elements of the detailed schedules include the following:

1. Task/Activity. An element of work with duration.

2. Milestone. A specific definable accomplishment in the contract network, recognizable at a particular point in time. Milestones have zero duration and do not consume resources.

3. Duration. The length of time estimated (or realized) to accomplish a task/activity.

4. Percent Complete (Schedule). The proportion of an activity or task that has been completed to a point in time.

DATA ITEM DESCRIPTION

1. TITLE

User Manual (UM)

2. NUMBER

PM02-UM

3. DESCRIPTION/PURPOSE

The SAI User Manual provides the information necessary for end users to effectively use the SAI solution.

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.3

1. General instructions.

Substitution of existing documents: Commercial or other existing documents may be substituted for all or part of the document if they contain the required data.

2. Format Contractor format is acceptable.

3. Content. The manual shall contain the following:

a. Title page or identifier. The document shall include a title page containing, as applicable: document number; volume number; version/revision indicator; security markings or other restrictions on the handling of the document; date; document title; name, abbreviation, and any other identifier for the system, subsystem, or item to which the document applies

b. Table of contents and index. The document shall contain a table of contents providing the number, title, and page number of each titled paragraph, figure, table, and appendix, and an index providing an alphabetic listing of key terms and concepts covered in the document and the pages or paragraphs in which the terms or concepts are covered.

c. Page numbering/labeling. Each page shall contain a unique page number

Content should include the following:

1. Introduction

1.1 Overview: This paragraph shall briefly state the purpose of the solution to which this document applies. It shall describe the general nature of the system and software; summarize the operation, and maintenance

2. System Overview: Provide a general overview of the system from initiation through exit. The logical arrangement of the information should enable the user to understand the sequence and flow of the system. This section should include, but nor be limited to the following:

2.1 Cautions & Warnings

2.2 Set-up Considerations

2.3 User Access Considerations

2.4 Accessing the System

2.5 System Organization & Navigation

2.6 Exiting the System

3. Using the System: Provide a detailed description of each user function and/or feature, explaining in detail the characteristics of the required input and system-produced output. Each function/feature should be described under a separate sub-section header and should correspond sequentially to the system functions (e.g., menu items) and/or features listed in certain sub-sections found in this document. Include screen prints as needed to depict examples. This section of the User Manual may also be tailored or customized based on defined user roles, if appropriate.

3.1 <Given Function/Feature>

3.1.1 <Given Sub-Function/Sub-Feature>

4. Fault Conditions: Describe fault conditions, including error conditions that may be generated and corrective actions that may need to be taken. The following are common sub-sections that may be included as appropriate:

4.1 Error Messages: Identify the error messages that a user may receive and the likely cause(s) and/or possible corrective actions for the error. If the list is extensive, this information may be best provided in an appendix.

4.2 Support: Provide information on how the user can get emergency assistance and system support. Include the names of the responsible personnel and organization(s), telephone numbers, and email addresses of the staff who serve as points of contact for system support. Also provide instructions for how identified problems with the system are to be reported.

DATA ITEM DESCRIPTION

1. TITLE

Service Requalification Test Plan

2. NUMBER

TE01-SRQ Test Plan

3. DESCRIPTION/PURPOSE

The Service Requalification Test Plan provides Contractor’s overall test philosophy, test definition and detailed planning information for tests to be conducted by the Contractor if a modification to the service baseline is required that impacts any of the requirements defined in Attachment J-1 Minimum Requirements Document (MRD).

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.6

Format and Contents:

Format: Contractor format is acceptable.

Content:

· The SRQ Test Plan must include test sections for each test procedure to be developed. Information must be provided to the level necessary to show adequacy of the proposed test methods, test philosophy, and success criteria for verification of requirements. Specific methods for performance measurement and data reduction and analysis (DR&A) must be included. In addition, a matrix to identify the test procedure wherein each allocated requirement is planned to be addressed.

· The SRQ Test Plan must delineate how required tests, necessary to address validation of the Contractor’s and Government’s specified requirements, support the overall test program to be conducted by the Contractor: the proposed test methodologies that address the requirements as allocated to each test; and input types, test/data reduction and analysis tools, certifications, accreditations, controls, and the overall processes (e.g. certification, inspection, validation, quality, and etc.) needed to address the complete scope of testing.

The Test Plan must include, at a minimum:

4.1 Title Page. The title page must identify the title of the test plan; the title, number, and paragraph number of the applicable specification.

4.2 Objectives. Describe the objectives of the overall test plan in collective terms, i.e., the scope of requirements allocated to the test; the success criteria and general test methods; and the overall planning utilized to confirm the requirements are addressed and met.

4.3 Description of Test Item. Describe the test item as it relates to Section C and the applicable test requirements. If less than the complete system, is employed, identify the hardware and software portions that are, and are not, to be tested/configured. Include, for that part to be tested, a description of all the external components (hardware, software, and their interfaces) having a direct bearing on the planned execution of the test in terms of each role played. Provide a test bed block diagram of the test item, each external component, and the planned software versions for each block.

4.4 Success Requirements and Criteria. This section must contain detailed success criteria for each requirement verified within the scope of this plan. Success parameters must be stated in terms of tolerance limits for calculated values, and all success parameters must be directly comparable to requirements limits as stated in the MRD. For success criteria dependent upon data reduction and analysis, explain the relationships between the raw extracted data, reduced data, and how the evaluations planned satisfy the MRD requirement(s). Situations or conditions under which success must be achieved must be specified in terms of range of input data value, amount of required input data types, and identification of critical values or occurrences.

4.5 Approach. In each test section, describe the testing approach. The number of tests, location, schedule, sequence, input data types, test prerequisites, and duration must also be provided.

4.6 Support. Identify all support equipment, facilities and personnel required for each test section. Indicate the type of recording processes and devices to be used and the specific parameters to be recorded.

4.7 Scenarios. Provide a description of the scenarios to be used in each test section.

4.8 Data Reduction and Analysis. Indicate the types of data to be recorded, where recorded, and discuss the approaches, conditions, and techniques planned for data reduction and analysis in each success criteria case.

DATA ITEM DESCRIPTION

1. TITLE

Service Requalification Test Procedures (SRQTP)

2. NUMBER

TE02-SRQTP

3. DESCRIPTION/PURPOSE

1. The SRQTP documents the detailed step-by-step instructions to be followed during Contractor-conducted testing.

2. A separate SRQTP must be prepared for each required test activity.

4. DATA REQUIREMENTS

Format and Contents:

Format: Contractor format is acceptable.

The test procedure must include the step-by-step detailed procedures and background information required to verify requirements identified in the Test Plan. The test procedure must include, at a minimum, the following:

1. Title Page. The title page must uniquely identify the individual test, the contract item(s) to be tested, and the primary functions or segments to be tested.

2. Test Objective. Include references to the SAI MRD, requirements to be verified as they occur in the various procedural sections and at the appropriate point of verification.

3. Location and Schedule. The location, schedule and expected duration must be provided for pre-test readiness briefings, test conduct, data reduction and analysis efforts, and post-test TIM debriefings.

4. References. Reference documents applicable to the test must be listed. Such references must include:

a. Specification for the functions to be tested

b. Users’ manuals for the equipment and/or software

c. Users’ manuals for test and support computer program and equipment

5. Personnel and Responsibilities. Requirements and responsibilities must be provided for all essential test personnel. Responsibilities of individual contractors or agencies for supplying personnel must be provided.

6. System Configuration Description. A description of the test article including the test configuration must be provided.

7. Test Support Tools and Equipment. Specific identification of test support equipment and software (e.g. scenarios, tools, drivers, Data Reduction and Analysis software, etc.) necessary to support the test must be specified. The manufacturer and model number must be specified for all test support equipment. Manufacturer and release level must be specified for all test support software.

8. Prerequisites. This section must identify tests required to be completed as well as the support documentation, and the initial test bed conditions required to start the test.

9. Detailed Test Description. The Test Description must describe in detail how each test must verify requirements.

10. Test Input. This section must describe in detail all test inputs necessary to conduct the test. All sources used to generate the test inputs must be specified.

11. Test Operating Procedures. Detailed step-by-step procedures for conducting the test as well as expected results must be specified in this section. Procedural steps must be described in the order in which they are planned to occur with dependency of any one step on another so indicated. If more than one operating or monitoring position is involved in the test, the sequence of events for each position must be indicated. Interdependence of operating positions with respect to specific events must be described.

12. Data Reduction & Analysis (DR&A). This section must contain the requirements and procedures for reduction and analysis of test data. The information must be contained in subsections as follows.

a. Recording and Reduction Requirements. Data which must be recorded during the test by the program, manually and/or by instrumentation, shall be specified. In addition, requirements for format and content of the data resulting from the reduction/analysis process must be specified. Requirements for data recording and reduction must be specified in a manner and detail such that the resulting information will clearly show whether the test objectives have been met.

b. Data Reduction/Analysis Procedures. This subsection shall contain the procedures to be employed in reducing and analyzing data resulting from the test.

Appendix A - Test Log. This section must include a template to capture test log records for all test runs. This section must include the approach for recording test actions, summaries, and failure information and corrective action (if applicable) during any test run. The test log template must contain the following at a minimum:

a. Date and time;

b. Test identification data;

c. Written summary of test events, including reference to discrepancy or failure data and corrective action; and

d. Signature block for Contractor and Government witness signatures.

DATA ITEM DESCRIPTION

1. TITLE

Service Requalification Test Report (SRQTR)

2. NUMBER

TE03-SRQTR

3. DESCRIPTION/PURPOSE

The Test Report documents the results of a requalification test and the subsequent data analysis.

4. DATA REQUIREMENTS

Format and Contents:

Format: Contractor format is acceptable.

Content: The test report must provide the results of formal test and subsequent data analysis. The Test Report must include, at a minimum the following:

1. Title Page. The title page must uniquely identify the individual test, the contract item or item tested, and the primary functions or segments tested.

2. Test Objective. The specific test objective, including reference to the requirements designated for this test.

3. References. The reference to the applicable Test Procedures.

4. Test Description. A general description of the test article that:

a. Identifies whether a full or partial system configuration was utilized (if partial, identify specific parts included or left out, whichever is shorter, along with rationale for using partial configuration).

b. Identifies quantity of site configurable components utilized in test configuration.

c. Includes test configuration diagram(s).

d. Identifies location of the test article (i.e. factory, on-site).

5. Test Equipment. A list of all test equipment, including manufacturer, model, calibration status, and serial number. Reference may be made to the applicable Test Log entry numbers.

6. Test Tools. A list of all system, test, and Data Reduction and Analysis (DR&A) software and adaptation utilized, identifying title, release level, and release date.

7. Test Approach. A description of the test approach and success criteria utilized to verify each requirement tested. Red-lines (if any) introduced during test execution must be accounted for in these descriptions.

8. Test Matrix. A test matrix that provides a summary of test results, which contains the following information for each requirement tested in this event:

a. Full text description of each requirement.

b. Requirement number, as identified in the SAI Compliance Matrix.

c. Identification of whether the requirement has been fully or partially verified by this test event.

d. Procedure section in which the requirement is addressed (if requirement is addressed in multiple sections, a separate line item must be provided for each procedure section it is addressed in).

e. Pass/Fail status of the requirement as a result of this test event (if a requirement is addressed in multiple sections of the procedure, a pass/fail status for each section and an overall status must be provided).

f. Identify whether regression testing is planned for further verification of each requirement as a result of test failure or planned fixes resulting from a Program Trouble Report (PTR) that may affect performance of that requirement.

g. Identify any PTRs by number that were generated during this test event that impact the pass/fail status of each requirement. A full copy of each PTR listed must be included as an attachment to this document.

9. Regression Testing. Provide a complete description of any planned or actual regression test activities as a result of PTRs generated during execution of this test event due to test failures or other noted system anomalies. This description must include reference to the specific test case, section, and steps that need to be executed from the test procedure or indicate that new or additional steps must be generated to address the PTR.

10. Action Items Matrix. Include a matrix that identifies any Action Items (AIs) that have been generated as a result of this test event during:

a. Test conduct (from test log entries)

b. Test debrief

c. An identification number assigned to each AI.

d. Full text description of each AI

e. Indication of the Open/Closed status of each AI.

f. Resolution and description of action(s) taken up to the time of report submittal for each AI.

g. A PTR must be generated for each AI that remains open at the time of report submittal, with a copy of each PTR attached to the report as an appendix.

11. Test Results. Detailed test results, including the items listed below must be provided:

a. An assessment of results obtained with respect to the defined success criteria, including conclusions regarding pass/fail status of each requirement.

b. Any raw or reduced data that either provides the basis for or directly supports conclusions regarding the pass/fail.

12. Program Trouble Reports (PTRs). For each step of a test procedure where a problem occurred, identify the procedure step number, and the expected impact of the problem on the validity of preceding or following steps of the test procedure. Amplifying information (for example: diagrams) should be included. Reference may be made to the applicable PTR(s) listing the number and brief description. A copy of the PTR must be included as an appendix to this report.

13. Data Analysis. Detailed data analysis results and a complete description of post-test data analysis activities must be provided and linked with the plan and procedure sections which generated the “raw” data input, and the DR&A test procedures which produced the resultant output.

14. Test Evaluation. An overall analysis of the functional performance of the article tested must be provided. This analysis must describe the functional capability as it was demonstrated in the test, noting any specific deficiencies (making reference to PTRs) that were discovered. Other test events must be identified that address each requirement that is only partially allocated to this test.

15. Test Results Witness Signatures. The names and signatures of Contractor and Government personnel present during the test.

DATA ITEM DESCRIPTION

1. TITLE

Technical Performance Measures Report (TPMR)

2. NUMBER

SM01- TPMR

3. DESCRIPTION/PURPOSE

This Technical Performance Measures Report (TPMR) summarizes the performance of the SAI solution at each site during the reporting period. The TPMR will provide the FAA with an accurate, consistent, timely, and readily understandable summary assessment of TPMs in Attachment J-7 against the applicable requirements in Attachment J.1 MRD.

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.8.2

Format and Contents:

Format: Contractor format is acceptable. Where information is presented at the service or facility level, the data must also be provided in a standard format that allows the Government to import the information into a spreadsheet or database for query purposes.

Contents: The Technical Measures Performance Report must contain the following information at a minimum:

1. Executive Summary.

a. The section must identify the site by name.

b. Highlights of the past month’s performance;

c. Any performance issues that should be brought to the FAA’s attention; and

d. Cause of performance issues and recommended remedial actions.

2. Technical Performance Measures Summary for SAI Services. This section of the report must provide a summary of service performance.

a. Update rate

b. Latency

c. Adjusted Service Availability (as defined in Attachment J-1)

i. 1-month Adjusted Service Availability with an indication of whether the Adjusted Service Availability is lower, higher or the same compared to the previous reporting period;

ii. Previous 12-month Adjusted Service Availability;

iii. Number of outages and their duration during the reporting period;

iv. Number of outages and their duration during the most recent 12 reporting periods;

v. Contractor’s assessment and justification of excused outages.

DATA ITEM DESCRIPTION

1. TITLE

Maintenance Plan (MP)

2. NUMBER

SM02-MP

3. DESCRIPTION/PURPOSE

This Maintenance Plan identifies the Contractor’s maintenance organization(s) and describes the approach, processes, and procedures to be used to successfully maintain the system components that comprise the SAI solution.

4. DATA REQUIREMENTS

Reference: PWS Paragraph C.4.2.8.3

Format and Contents:

Format: Contractor format is acceptable.

Contents: The Maintenance Plan must contain the following information at a minimum:

1. SAI Solution and Maintenance Overview. This section of the Maintenance Plan must provide a high-level description of the SAI services, and the SAI operations and maintenance concept, including the relationships between Contractor and Government personnel.

2. Service Continuity and Restoration. The plan must address the provisions for service continuity and service restoration.

DATA ITEM DESCRIPTION

1. TITLE

Design Site Survey (DSS) Report

2. NUMBER

IM01-DSSR

3. DESCRIPTION/PURPOSE

The Design Site Survey Report (DSSR) is required to document the results of the Site Survey for each site and must be used to determine the preparations required for system installation, test, and Government…