DDLS Draft SOW_Market Survey (7-11-25).docx

– Statement Of Work General Document Purpose This Statement of Work (SOW) defines the Contractor’s requirements under the Federal Aviation Administration’s (FAA) Data Communications (Data Comm) Domestic Datalink Services (DDLS) Contract.

Background The Data Comm Program is a critically important next step for improving air safety, reducing delays, increasing fuel savings, improving the environment, and providing the foundation for NextGen operations. The introduction of data communications between the FAA’s air traffic control functions and carrier aircraft represents a key phase of the transition from the current decades old analog voice system to a predominantly digital mode of communication. The Data Comm System supports the NextGen vision by providing air traffic service (ATS) data transmissions directly to pilots via aircraft avionics systems. This ATS data communications capability enables more efficient procedures and flight profiles through services such as revised departure clearances, automation of routine clearances, Traffic Flow Management reroutes, automated transfer of communications, optimized profile descents, and trajectory-based operations. These services contribute to evolving air traffic control from short-term tactical operations to the strategic managements of flights from gate-to-gate.

As used herein, the Data Comm System is the end-to-end system from the air traffic controller position to the pilots data display system in the aircraft. The Data Comm System explicitly includes FAA automation and intermediate systems in the En Route, Tower, and Terminal Radar Approach Control (TRACON) domains, FAA supplied telecommunications service, the Domestic Datalink Service, (DDLS), and the aircraft avionics suite.

Mission The Data Comm Program mission is to improve the efficiency of the Air Traffic Organization (ATO) by providing controllers with the automation tools they need to handle more traffic while providing advanced service, to increase National Airspace System (NAS) capacity, to enhance air traffic safety by reducing voice communications related operational errors, and to enable advanced operations not possible using the current voice system.

Program Goals and Objectives Data Comm Program Strategic Plan contains a description of the program’s goals and objectives.

Applicable Documents Unless specified below, the version in effect on the date of the issuance of the Screening Information Request (SIR) release is applicable.

Referenced documents are applicable to the extent specified herein. If applicability is not further specified in the text of this SOW, then the entire document is applicable.

Government Documents FAA Specifications

FAA Orders

Other FAA Documents

Other Government Documents

Non-Government Documents Industry Standards

Availability of Documents FAA Documents Copies of FAA specifications, standards, and publications may be obtained from the Contracting Officer noted in Section G. Requests should clearly identify the desired material by name and number (when applicable) and state the intended use of the material. Requested copies will be provided in digital format.

Federal Documents Copies of federal publications may be obtained from the U.S. Government Printing Office, 710 North Capitol Street, Washington DC, 20401, by calling (202) 512-0132, or through the web site http://bookstore.gpo.gov/.

National Institute of Standards and Technology (NIST) Documents Copies of National Institute of Standards and Technology documents may be obtained through the web site http://csrc.nist.gov/publications/PubsSPs.html.

American National Standards Institute (ANSI) Documents Copies of American National Standards Institute (ANSI) documents may be obtained through the web site http://webstore.ansi.org/.

Scope of Work The scope of the DDLS contract includes all services necessary to satisfy the FAA’s requirements, in a dynamic environment, for: 1) provision and operation of the DDLS and associated engineering and management professional services; 2) engineering and management professional services required to assist the FAA in troubleshooting the end-to-end Data Communication services; and; 3) professional services to manage the DDLS contract to FAA requirements.

Specific Requirements Data Communication Network Services The Contractor must supply Network Services that meet the technical requirements of the DDLNSD (Section J-1) and delivers all Data Comm ATS messages (both uplink and downlink) via a Radio Frequency (RF) link (over-the-air interface) shared with Airline Operation Center (AOC) traffic. Any contractor requests for deviations or waivers to the requirements contained in the DDLNSD will be executed in accordance with contract section H.13.1 Performance.

ATS messages must be provided, via the shared RF link(s), to and from any appropriately equipped aircraft that do not receive AOC service but that request ATS only. The Contractor may require such ATS-only aircraft operators to register with them in order to receive the service. However, in all cases, there must be no fees or costs to any aircraft operator for them to obtain the FAA supplied ATS.

The Contractor must execute the requirements of this section in a single consolidated manner, irrespective of the number of AOC CSPs subcontracted to provide the shared RF link of the DDLS, or the timing of those subcontracts.

The DDLS is delineated in this SOW into three functional components:

1. Network Service (ground-ground and air-ground network)

1. Monitoring Service

1. Service Certification The delineation of the DDLS into the functional components listed above does not imply requirements for any specific network architecture, detailed network design, or hardware/software elements. Nor does this delineation imply any staffing concept or organizational structure for the Contractor’s efforts under this contract.

DDLNSD Figure 3-1 is a functional diagram of the overall Data Comm System and illustrates the major functional components of the DDLS and the Service Delivery Points (SDPs) that are referenced herein.

DDLS Architecture and Design The Contractor must architect, design, and engineer the Network Service and Monitoring Service of the DDLS to meet or exceed all functional and performance requirements levied by the DDLNSD, applicable Interface Requirements Documents (IRDs) (see Sections J-x), and this SOW. The Contractor must provide the resulting architecture and design to the FAA for approval. This tasking must be accomplished by the Contractor, as applicable, throughout all incremental expansions and upgrades of the DDLS over its lifetime.

The Contractor must demonstrate that its architecture, design, and engineering for these services provides all required functionality and that the resulting services meet or exceed all required performance requirements.

Architectural Requirements for Expandability and Upgradability The FAA will order appropriate DDLS service, as needed, to provide the performance and functions required to meet immediate through planned long-term operational needs. The DDLS architecture and design must provide an evolutionary path from the least to the most stringent functional and performance requirements while meeting the requirements of the DDLNSD, Section 3.2.2, Upgradeability.

The FAA intends to incrementally order DDLS services with various service profiles for specific geographical areas and operational domains. The architecture and design of the DDLS must provide for incremental deployment of service and the implementation of different service profiles (both quality of service and service type, specifically FANS 1/A+), for each defined and ordered service volume (see Section B). The architecture and design of the DDLS must provide incremental deployment and implementation without interruption of previously implemented DDLS services or impact to the quality of these services.

Architectural Requirements for SDPs The Contractor’s architecture, design and engineering must reflect the requirement that all SDPs be located at FAA facilities (Salt Lake and Atlanta) United States of America (CONUS). For information and requirements related to the SDPs, see DDLNSD, Figure 3-1.

Operational Traffic SDPs The FAA will make available two interfaces with its domain for operational traffic. One will be located in Atlanta, Georgia and the other one will be located in Salt Lake City, Utah.

The Contractor’s design must identify the quantity and specific location(s) of the Network Service and Monitoring Service SDPs associated with each FAA provided facility.

Test Traffic SDPs The Contractor must define, in their architecture and design, co-located Network Service and Monitoring Service test traffic SDPs to provide the FAA with access to the DDLS, via the William J. Hughes Technical Center’s (WJHTC’s) labs, for testing purposes. The co-located SDPs must meet the requirements of the relevant IRD(s).

Traffic from implemented test sites (see Attachment J-x) will be directed to the FAA’s test domain via the test traffic SDPs.

Although test traffic must be delivered to a separate test traffic SDP, it must be transported via the Contractor’s primary production network (both ground-ground and air-ground portions). The FAA does not plan to require or use a segregated test network to transport data to the test traffic SDP.

The FAA will provide telecommunications service, between the WJHTC labs and the associated Contractor hosted test traffic SDPs. The Contractor must provide the agency with a recommended service type, from the available telecommunication services portfolio described in the FTI Telecommunications Services Description (FTSD), for the Government provided connectivity between the WJHTC and the test traffic SDPs.

Design Reviews The Contractor must present design reviews, as necessary, to provide the FAA with assurance that the DDLS design will meet all of its requirements to include initial deployment/implementation, performance upgrades, and additions of service type (e.g., FANS 1/A+ etc).

The Contractor’s DDLS Deployment and Implementation Plan (see Section C.4.1.2.1 and CDRL TBD) must identify the number and schedule of design reviews and demonstrate that these design reviews provide the FAA with sufficient opportunity for architecture and design evaluation and oversight without negative impact to planned Data Comm Program milestones and objectives.

During the design reviews, the Contractor must present a detailed system architecture and design, supporting engineering information, and quantitative analysis that clearly demonstrates the ability of the proposed design to meet or exceed all of the FAA’s requirements. During the design reviews, the Contractor must present to the FAA the input data, analysis methodology, and results used to create the DDLS design and their relationship to meeting or exceeding all of the FAA requirements. In addition, the Contractor must identify the design risks and their risk mitigation plans.

The Contractor must provide all design review presentation material and supporting documentation; generate and deliver design review agendas, generate and deliver design review Meeting Minutes; and generate, maintain, and deliver a design review Action Item List (CDRL TBD).

The requirements of this section also apply to any test beds ordered by Task Order under Section 4.1.3.5.2.

Technical Interchange Meetings The Contractor must participate in, and host when requested by the FAA, Technical Interchange Meetings (TIMs) with the FAA, associated contractors, and other stakeholders to ensure that the DDLS meets its requirements and technically integrates into the Data Comm System, and the NAS overall, as intended. The Contractor must generate and deliver TIM Meeting Minutes and must generate, maintain, and deliver a TIM Action Item List (CDRL TBD).

The Contractor must propose a minimum schedule for TIM meetings in the DDLS Deployment and Implementation Plan. However, additional meetings may be held if called for by the Contractor or must be held if requested by the FAA.

Network Vulnerability and Survivability Reviews The Contractor must participate in and, when appropriate, host periodic Network Vulnerability and Survivability Reviews (NVSRs) with the FAA, associated contractors, and other stakeholders to:

a) Review the DDLS Network and Monitoring Services architecture, design, and configuration

b) Identify vulnerabilities and risks that endanger the functions or performance of the network

c) Proactively develop and implement recommendations to improve availability, resiliency, and survivability of the network The NVSR must hold its first instance within ninety (90) DACCA. It must meet quarterly and may meet more frequently, if requested by the Government, based on the perceived or actual level of risks and threats to the network. The Contractor must generate and deliver NVSR agendas, meeting minutes and presentation material and must generate, maintain, and deliver a NVSR Action Item List (CDRL TBD). The Contractor must generate and deliver engineering studies, white papers, and trade-off analyses, as required, to document the results of the NSVR (CDRL TBD).

DDLS Deployment and Implementation The following sections describe the DDLS deployment and implementation requirements.

DDLS Deployment and Implementation Plan The Contractor must generate and maintain, for the life of the contract, a DDLS Deployment and Implementation Plan (CDRL TBD) that provides a rational, logical, and cost effective detailed plan for the development, test, and deployment of the DDLS and its implementation into service. The contents of this plan must reflect the FAA’s program and notional milestone structure shown in the Data Comm Strategic Plan. This plan must contain those portions of the Contractor’s Integrated Master Schedule (IMS) related to DDLS design, test, deployment, implementation, and all prerequisite tasks necessary to achieve DDLS operational implementation. The schedule portion of the DDLS Deployment and Implementation Plan must support the Data Comm System Integrated Program Schedule (IPS) milestones. The Contractor will be provided access to the Data Comm System IPS upon contract award.

It is expected that this plan will remain a “living document” and continue to be expanded and updated to reflect the growth and upgrading of DDLS to accommodate the expansion of Data Comm System services and the growth of data traffic. This plan must also be updated to reflect applicable changes to the Data Comm System IPS. The DDLS Deployment and Implementation Plan must be delivered separately, as required by the CDRL; however its content must also be rolled up and reflected in the Master Data Comm System Implementation Plan required by Section C.4.2.5.1.

DDLS Installation into FAA Facilities The FAA anticipates a requirement for Contractor DDLS equipment to be installed in FAA facilities. If the FAA approved design requires any Contractor DDLS equipment to be installed into FAA facilities, then the following subsections apply to such installations.

The requirements in Sections C.4.1.2.2.6 through C.4.1.2.2.11 do not apply to test bed equipment provided under Section C.4.1.3.5 and installed in an FAA laboratory environment.

Installation Labor and Material The Contractor must provide all labor and installation material necessary to install this equipment.

Installation material may include, at a minimum, the following:

a) Racks, cabinets, ladder rack, cable trays, and mounting hardware for DDLS equipment

b) All cabling and wiring to any demarcation or interface points

c) All power and ground cables, connectors, as necessary, to connect to FAA electrical power panels and grounding buses

d) Installation tools and test equipment Upon completion of installation activities, the Contractor must clean-up and dispose of all shipping crates, packing materials, scrap material, and related items not required for DDLS operation and leave the facility in the state of cleanliness in which it was found.

Hazardous Materials Safety Data Sheet If hazardous material or components are brought into FAA sites, the Contractor must maintain a Material Safety Data Sheet (CDRL A0002-MSDS) on-site and make it available for review by the FAA.

Contractor Requirements for Access to FAA Owned Facilities The Contractor will be granted access to specific FAA facilities where DDLS equipment is to be installed per the approved design. The Contractor must coordinate access to these facilities through the COR or the COR’s designated site representative. The Contractor must initiate the request to the FAA for access to a facility for installation activities at least twenty-one (21) days in advance of the requested access date.

Access to FAA facilities will be granted to permit timely performance of contract requirements. However, Contractor personnel must be prepared to work outside normal day shift hours, if conditions at the facility so require, as determined by the FAA’s COR.

When in a FAA facility, Contractor personnel must:

a) Display an identification badge that clearly identifies personnel as an employee of the Contractor

b) Observe security regulations in effect for the particular premises involved

c) Comply with all rules and regulations of the site, particularly in the areas of security, health, and safety

d) Not interfere with any Air Traffic Control (ATC) operational activities Regulatory Compliance Requirements for DDLS Installations into FAA Owned Facilities DDLS installations in FAA-owned facilities must comply with the following:

a) DDLNSD, Section 3.2.3, "Use of FAA Facilities”

b) Code of Federal Regulations (CFR), Title 40, Protection of Environment

c) FAA Order 3900.19B Occupational Safety and Health Program (Chapter 10, 11, 13, 14, 15) The Contractor must address how their deployment approach will comply with these requirements during DDLS design reviews and in the DDLS Deployment and Implementation Plan ((CDRL A0001-D&IP, see Section C.4.1.2.1).

Equipment Disposal The Contractor must dispose of any Contractor owned equipment installed in any FAA facility at the end of its life cycle or if it is to be decommissioned and disposed of for any other reason. The equipment must be disposed of in accordance with local, state, and Federal environmental and disposal regulations Site Surveys The Contractor must prepare a Site Survey Plan (CDRL A0003-SSP) to describe their approach for conducting site surveys for DDLS installations into FAA facilities and to define the scope and content of the resulting site survey products to specifically include the Site Specific Implementation Plan (SSIP).

The Contractor must coordinate and conduct site surveys for DDLS equipment installations at FAA facilities in accordance with the approved Site Survey Plan.

Site surveys must identify any required site/facility preparation, preliminary data gathering (e.g., facility floor plans and availability of space, RF surveys, primary power and grounding features, lighting), and coordination activities necessary to ensure the suitability of the site.

During the site surveys, the Contractor must determine that the maximum external dimensions of any individual DDLS equipment or equipment crate or package allows for ease of transportation through the building from the equipment delivery point to its final location to include consideration of: turning radii, proximity to existing equipment, ramps, corridors, elevators, door openings, and other related factors. The Contractor must verify building through-routes during each site survey.

Site Specific Implementation Plan The Contractor must generate, and deliver to the FAA for approval, a SSIP (CDRL TBD) for each installation into a FAA facility. The SSIP must document, as a minimum, the site survey results, site preparation requirements, equipment installation to be performed, and site test and implementation actions.

The Contractor must validate the accuracy of any FAA provided site documentation obtained during the site survey to the extent that it affects DDLS equipment deployment and implementation. Inconsistencies or errors in any FAA provided documentation must be annotated in the SSIP.

Site Preparation The FAA will perform all required site preparation or facility modifications of FAA facilities.

Delivery of DDLS Equipment for Installation into FAA Facilities The Contractor must deliver to the site all equipment, installation material, tools, test equipment, documentation, etc., needed to complete the installation. The Contractor must have personnel at the FAA site to receive and position all equipment and material shipments. Delivery, in this instance, explicitly includes movement of the equipment, materials, etc. to the actual installation location within the FAA facility. The Contractor must provide tools (such as lift bed trucks, hand trucks, dollies, etc.) and labor necessary for placement of the equipment and installation material at the installation location within the site. The Contractor must also supply any moving pads, floor protection, or other material, as needed, to ensure that placement of the equipment into its installation site does not result in any damage to the FAA facility.

The Contractor must provide notice of delivery to the COR or their identified FAA site representative at least twenty-one (21) days prior to the actual delivery.

DDLS Equipment Installation into FAA Facilities The Contractor must perform turn-key DDLS equipment installation, site acceptance testing, and implementation for all installations into FAA facilities in accordance with the approved SSIP.

The Contractor must restore any damage to the FAA’s facilities resulting from the Contractor’s delivery, installation, and implementation activities. In such cases, the Contractor must restore the facility to a condition at least as good as it was prior to the damage.

Equipment/Power Integrity Test The Contractor must perform an Equipment/Power Integrity Test prior to connecting any equipment to a power receptacle fed from, or hard wired to, a FAA site designated critical power panel as determined during the site survey. The Contractor must verify, via application of power from a non-critical power source, that all DDLS equipment designated for connection to a critical power panel performs appropriately and that no DDLS equipment has been damaged during shipment or installation. The Contractor must provide a temporary branch feeder(s) or “extension cord(s)” that has the required receptacle on one end to mate with the plug on the equipment being tested. The Contractor must hard wire the other end of the “extension cord” into a Government determined power panel. The Contractor must then turn the power on to the equipment being tested and monitor the test for a minimum of 15 minutes or until the equipment exhibits the proper performance characteristics. Once verified and witnessed by the Government on-site representative, the Contractor must connect the tested equipment to the designated critical power receptacle(s).

Installation Punch List Upon completion of the installation of equipment into an FAA facility, the Contractor must participate in an inspection of the installation with the FAA’s site representative. All deficiencies or uncompleted miscellaneous installation related work, either identified by the FAA site representative or known to exist by the Contractor, must be documented by the Contractor in a Site Installation Punch List (SIPL) (CDRL A0005-SIPL). The Contractor must close all punch list items, to the satisfaction of the FAA’s site representative, prior to the site being accepted by the FAA.

As-Built Drawings The Contractor must provide As-Built Drawings (CDRL A0006-ABD) for each FAA site where DDLS equipment is installed.

Discontinuation of Service Upon discontinuation of service, the Contractor must remove all DDLS equipment, installation material, and related items from FAA site(s) within sixty (60) days unless otherwise mutually agreed to, in writing, by the Contractor and the FAA Contracting Officer. The Contractor must restore the facility to a condition as least as good as it was prior to installation of their equipment.

DDLS Test and Evaluation The Contractor must plan, document, manage, and conduct a DDLS test and evaluation (T&E) program as described in the following sections. The Contractor’s DDLS T&E program must:

a) Reflect the guidance of the applicable provisions of the FAA’s Acquisition Management System (AMS) Test and Evaluation Guidelines

b) Be coherent with the FAA’s overall Data Comm T&E program described in the Data Comm System Test and Evaluation Master Plan (TEMP, Attachment J-x)

c) Support the program components described in the Data Comm Program Strategic Plan The Contractor’s T&E program must address the FAA’s plans to incrementally implement additional air traffic services (e.g., Tower and En Route,), additional types of service (e.g., FANS 1/A+ etc.), and higher performance requirements (e.g., Quality of Service (QOS) and capacity requirements). See the Data Comm Program Strategic Plan for further information on this incremental implementation approach.

The Contractor’s DDLS T&E program structure must reflect an iterative spiral testing approach to verify and validate that the DDLS meets all physical, functional, interface, integration, and performance requirements prior to implementation of these additional services and more stringent requirements into the field for operational use.

The Contractor must update all required T&E documentation, as required, to reflect this spiral testing approach required by the incremental introduction of additional services and more stringent performance requirements into (e.g., Contractor Master Test Plan, Verification Requirements Traceability Matrix, Test Plans and Procedures, etc) and conduct the associated additional testing and reporting.

The Contractor must conduct testing and provide test support at the Contractor facility, the WJHTC, and at operational sites where the Data Comm System is deployed, as applicable. The scope of these testing and test support activities includes both laboratory and field testing, as required.

The Contractor must coordinate and manage all Contractor and subcontractor DDLS test and test support activities.

Contractor’s DDLS Master Test Plan The Contractor must prepare a Contractor’s Master Test Plan (CMTP) (CDRL A0007-CMTP) that describes the Contractor’s plan for testing of the DDLS. The CMTP must include delineate any Government furnished items and efforts required to execute the Contractor’s DDLS test program.

Upon Government approval of the CMTP, the Contractor must adhere to the requirements of the CMTP for all Contractor DDLS test activities.

Verification Requirements Traceability Matrix The CMTP must include a Verification Requirements Traceability Matrix (VRTM) derived from the VRTMs contained in the DDLNSD, PGWFEP-DCNSPR IRD. The Contractor must allocate all requirements from the DDLNSD, and applicable IRDs, to at least one verification requirement in the VRTM. The initial CMTP VRTM must contain, at a minimum, a listing of all DDLS and applicable IRD requirements, and the method of verification to be used (i.e., test, demonstration, analysis, or inspection).

The Contractor must maintain the VRTM as a living document and must update/expand it with references to the specific test plan/procedure that will be used for each given verification requirement, the pass/fail criteria for each test, test results as verification activities are completed, and additional verification requirements, if any are identified.

Individual test plans, procedures, and reports must clearly indicate the correlation between the relevant test document and the specific VRTM requirement(s) being verified.

DDLS Test Schedules The Contractor must generate schedules for all testing in the CMTP. These schedules must be integrated into the CMTP, the Contractor’s IMS, and DDLS Deployment and Implementation Plan.

Test Plan Working Group Meetings The Contractor must participate in, and host when requested by the FAA, Test Plan Working Group (TPWG) meetings with the FAA, contractors, and other stakeholders to plan and manage the DDLS test program and to resolve any technical or management issues pertaining to DDLS testing. The Contractor must generate and deliver TPWG Meeting Minutes and must generate, maintain, and deliver a TPWG Action Item List (CDRL A0051-MAPMMMAIL).

The Contractor must propose a minimum schedule for TPWG meetings in the DDLS Test Schedule included as part of the CMTP. However, additional meetings may be held if called for by the Contractor or must be held if requested by the FAA.

Formal Tests The Contractor must conduct the following categories of Formal Tests:

a) Functional Qualification Tests

b) Service Acceptance Tests

c) DDLS Interface Tests Functional Qualification Tests The Contractor must conduct Functional Qualification Tests (FQTs) on the Network and Monitoring Services. The Contractor must conduct FQTs in accordance with the approved CMTP, test plans, and test procedures.

FQTs must successfully verify that the Contractor’s design meets or exceeds all requirements of the DDLS, as documented in the approved CMTP VRTM. All test plans, procedures, and test cases must be directly traceable to CMTP VRTM requirements.

Service Acceptance Tests The Contractor must perform Service Acceptance Tests (SATs) for all newly implemented instances of DDLS services, prior to acceptance by the FAA. SAT must include test cases sufficient to verify that the instance of implemented service is operating correctly and in accordance with the performance baseline established during FQT. In the case of the Network Service, incremental expansion of Network Service geographical coverage, additions of service type (e.g., FANS 1/A+ and ATN service), or changes to a volume’s service profile, would constitute a “new service” and SAT testing must be performed on the newly added or changed service.

RF Coverage testing must be performed as part of SAT or as ordered by Task Order, as described below RF Coverage Testing The Contractor must conduct RF Coverage Testing as part of SAT, as described in the following sections. RF Coverage Testing, in conjunction with RF Coverage Analysis (see Section C.4.1.10.1.1.2), must provide the FAA with a high degree of confidence that the implemented Network Service meets the coverage requirements specified in the DDLNSD, Sections 4.1.1 and 4.1.3.(b).

A test plan, procedure, and report must be generated, in accordance with Section C. 4.1.3.2.4, for each service volume that is RF Coverage Tested.

In addition to the requirements of the relevant CDRL/DID, RF Coverage Test Plans must include identification of the exact areas and altitudes (if applicable) to be tested, the test sample rate and/or sample grid size, the pass/fail criteria, a technical description of the test set up and data collection suite, and a description of all data reduction and analytical techniques to be used on the raw data to generate coverage test results.

In addition to the requirements of the relevant CDRL/DID, RF Coverage Test Report(s) must document the actual RF coverage (in three dimensions), as determined by test in the areas and altitudes specified by the approved test plan. The report must include tabular data, as well as graphical coverage plots and maps, indicating the projected (from RF Coverage Analysis, Section C.4.1.10.1.1.2) and tested received signal strength. If the test equipment RF parameters do not agree with the assumed aircraft equipment utilized in the link budget of the projected coverage calculations, separate projections need to be provided (in addition to those assumed for aircraft equipment) normalized for the test conditions, to allow a clear comparison of projected versus measured under the same link budget conditions.

Upon the FAA’s request, the Contractor must supply the agency with all collected raw field data.

As part of RF Coverage Testing, the Contractor must assist the FAA in coordinating with relevant federal and municipal organizations for access to airport surfaces and aloft airspaces for the purposes of planning and executing this testing.

Successful completion of RF Coverage Testing of selected service volumes, or parts of service volumes, does not relieve the Contractor from meeting all DDLNSD requirements for RF coverage and performance over all ordered service volumes. Any RF Coverage shortfalls or performance deficiencies discovered during or after Coverage Testing, that have not already been documented as an acceptable exception, must be corrected by the Contractor at no additional cost to the FAA.

Airport Surface (Tower) RF Coverage Drive Testing The Contractor must conduct RF Coverage Drive Testing at the surface level for each airport where DDLS Tower Service has been implemented. Testing must be performed on each airport’s movement and non-movement surface areas (see DDLNSD, 4.1.1.1) that the Contractor’s RF Coverage Analysis projections (see Section C.4.1.10.1.1.2) indicate will demonstrate 9db or less of margin over the recommended operational coverage field strength defined in ICAO Annex 10, Volume III, Part 1, Section 6.2.2.

RF Coverage Drive Testing must also include all movement and non-movement areas where there is a foreseeable potential for multi-path interference, RF shadowing, and other modes of signal degradation due to the effects of physical structures (e.g., buildings and hangars), geographical features, or interaction with other RF emitters.

For each airport, at least 95% of the collected drive test data points must meet or exceed the minimum margin requirements specified in DDLNSD, 4.1.3(b) in order to successfully pass SAT.

As ordered by Task Order, the Contractor must perform additional RF Coverage Drive Testing of airport surface areas. Specifics of the additional RF Coverage Drive Testing, if any is ordered, will be delineated in the individual Task Order(s).

Aloft Airspace (En Route) RF Coverage Flight Testing As ordered by Task Order, the Contractor must conduct RF Coverage Flight Testing within En Route service volumes as part of SAT.

Any issued Task Order(s) will either delineate specific volumes (areas and altitudes) to be flight tested or will require that the Contractor propose, for FAA approval, the volumes (geographical areas and altitudes) to be flight tested in their RF Coverage Flight Test Plans.

If the Contractor must propose the volumes to be tested, these volumes must be selected to include those with the lowest projected system signal margin (based on the Contractor’s RF Coverage Analysis) and those where significant geography may impact RF coverage and performance (e.g., mountains).

The Contractor must supply all personnel, aircraft, avionics, test equipment, materials, and other miscellaneous hardware and software necessary to plan, conduct, and report on RF Coverage Flight Testing.

To successfully pass RF Coverage Flight Testing, 95% of the collected data points within the tested airspace must meet or exceed the minimum system margin requirements specified in the DDLNSD, Section 4.1.3(b) DDLS Interface Tests The Contractor must conduct testing, as required, to verify and validate that each implemented SDP, both for Network and Monitoring Services, meets the requirements of the applicable FAA provided IRDs (see Attachment J-x). This testing will be accomplished for each newly established SDP and each time a new service type is implemented through an existing SDP.

Test Plans, Procedures and Reports For all Formal Tests, the Contractor must generate and deliver test plans (CDRL TBD), detailed test procedures (CDRL A0009-TPR), and test reports (CDRL A0010-TR). All test plans, procedures, and test cases must be directly and clearly traceable to CMTP VRTM requirements.

Test Readiness Reviews The Contractor must prepare for and conduct Test Readiness Reviews (TRRs) either the day before or the day of conducting any Functional Qualification or DDLS Interface Testing. The Contractor must notify the Government of the date and location for any TRR no later than thirty (30) days prior to the start of that TRR.

During the TRR, the Contractor must present information sufficient to transfer knowledge to the FAA test team on the following:

1. Design of the article under test (e.g., network architecture and design)

1. Test environment (e.g., test fixtures, simulators, etc)

1. Test objectives, procedures, and test criteria

1. Test equipment to be used and its settings

1. Test points for data collection

1. Any deviations or differences between the test article and the article intended for field deployment The Contractor must present sufficient information to demonstrate that the testing is valid for its purposes and transfer sufficient knowledge to the FAA test team such that they can provide competent, and informed, observation and oversight of the testing. If the knowledge transfer portion of the TRR is determined by the Contractor to be sufficiently lengthy that it interferes with the TRR, it may be held as a separate meeting, but in all cases must precede the TRR.

The Contractor must generate and deliver presentation material and data (CDRL A0051-MAPMMMAIL) sufficient to document the above tasking.

Test Conduct The Contractor must notify the FAA of readiness to test at least fourteen (14) calendar days prior to the start of each instance of a Formal Test.

The Contractor must conduct tests in accordance with the approved CMTP, test plans, procedures, and schedules.

The FAA reserves the right to monitor and/or witness, on a non-interference basis, the preparation and conduct of any or all test activities.

All raw test data generated or collected by the Contractor during DDLS testing must be made available to the FAA, upon request.

At the start of all Formal Tests (i.e., FQT, SAT, and DDLS Interface Test), the Contractor must provide a pre-test briefing to the FAA’s observers, to include discussion of the test overview and objectives, test configuration, test sequence, and test limitations.

Upon completion of each Functional Qualification Test and DDLS Interface Test, the Contractor must conduct a debriefing TIM with the FAA observers to review the test results to specifically include test failures, discrepancies, instances of non-compliance, unexplained anomalies, and the resulting trouble tickets (if any). The Contractor must generate minutes (CDRL TBD) of these TIMs and include any data presented or reviewed as attachments to the minutes.

During testing, any failure, discrepancy, or unexplained anomaly must be entered into the Contractor’s trouble ticket system and documented in the test report.

Any test failures, discrepancies, or anomalies that, upon analysis, are attributed to elements of the NAS outside the Contractor’s responsibility, must be annotated in the Contractor’s trouble ticket System with a “NAS” notation so that they can be taken by the FAA for action.

Test Completion Formal Tests are considered successfully completed only when all of the following criteria are met:

a) The Contractor has received written FAA approval of the applicable test plan and procedures

b) FAA representative(s) have witnessed, or have been given, via written notification, the opportunity to witness, the actual test

c) The test is conducted to a successful outcome in accordance with the FAA approved plans and procedures to include successful regression testing, if applicable

d) The test report, including all data analysis, test results, and corrective actions has been completed, delivered, and approved by the FAA or designated FAA representative(s) Retest of DDLS Formal Test Requirements The FAA will determine if a retest is required for any given test failure, discrepancy, or unexplained anomaly detected during Formal Testing based upon its evaluation of test data, data analysis, and test reports. If retesting is required, the FAA will notify the Contractor of the specific requirement(s) requiring retest.

Before retesting, the Contractor must determine the root cause for the failure, discrepancy, non-compliance, or anomaly and implement the necessary corrective actions to ensure a high probability of successful retest.

Retest requirements and results will be documented in the CMTP VTRM and will be validated by the FAA.

Regression Testing of DDLS Formal Test Requirements The Contractor must correct all Formal Test failures and discrepancies and then verify, through regression testing, that the implemented corrections do not negatively impact any other system functions or performance. For all regression testing, the requirements for test procedures, test conduct, test reports, and test completion apply.

Test Laboratories, Equipment, and Tools The Contractor must provide all necessary facilities, test beds, test equipment, test fixtures, tools, and miscellaneous material needed for all Contractor conducted Formal Tests. Such test equipment must be calibrated, fully operational, and available to support all required testing.

Any Contractor developed test tools (e.g., simulation applications, hardware simulators, traffic generators, and diagnostic tools), used in the course of DDLS testing, must be made available to the FAA for Government validation and for the FAA’s use in support of any independent Government testing of the DDLS and the Data Comm System.

Other Test Activities and Support As ordered by Task Order, the Contractor must provide support to the FAA for test planning, engineering and test execution, test reporting, and development of test issue resolution/corrective action for test activities not already covered in other sections herein. The following general types of testing may be included in these Task Orders:

a) Lab testing (both at Contractor’s facilities and at the WJHTC)

b) System testing of the DDLS integrated within the overall Data Comm System

c) FAA Flight testing related to DDLS functions at the WJHTC and field locations DDLS Installation Checkout Test Prior to any Formal Testing, the Contractor must perform Installation Checkout Tests. Installation Checkout Tests must include tests or checks that verify that the network element is correctly powered, configured, interfaced, and is properly communicating to adjacent elements in the network or with the SDPs.

DDLS Test Bed This section describes the requirements for the engineering and supply of DDLS test beds, system mock-ups, and emulators needed to conduct the DDLS test program contained in the approved CMTP.

Test Bed Plan The Contractor must generate a Test Bed Plan (CDRL TBD) that presents recommendations on the quantity, location, composition, and architecture of the test beds required to conduct the complete Data Comm System and DDLS test program described in the FAA’s TEMP and the approved CMTP. This plan will encompass, at a minimum, requirements for test beds at the WJHTC and the Contractor’s facilities.

The Contractor must, with FAA coordination, audit existing relevant test bed capabilities at the WJHTC to determine what, if any, existing test bed equipment, facilities, fixtures, test equipment, etc. can be incorporated and used for the required test bed(s). The plan must present the results of this audit.

The plan must clearly identify and distinguish those portions of the recommended test bed architecture that can be satisfied by integrating existing Government capability and elements, identified in the audit referenced above, and those which must be acquired along with a recommended source for their acquisition.

Test Bed Design and Implementation The Contractor must design, engineer, supply, install, integrate, and test/validate the ordered test beds and/or expansions, enhancements, or additions to existing test beds to support the Data Comm System and DDLS test program described in the FAA’s TEMP and the approved CMTP. The Contractor must present its test bed design, in accordance with Section C.4.1.1.3, Design Reviews, for the test bed or test bed expansions/enhancements/additions. The Contractor must obtain the FAA COR’s signed approval of the design prior to taking any further steps in the fulfillment of the ordered test bed. The ordered test beds may be one or more of those recommended by the Contractor in the Test Bed Plan or may be an architecture supplied by the FAA.

DDLS Demo and Prototyping Tasks As ordered by Task Order, the Contractor must plan, design, and execute DDLS demonstrations and design and supply prototype items.

Configuration Management The Contractor must develop a Configuration Management Plan (CMP) (CDRL A0012--CMP) reflecting the guidance and principles of ANSI/EIA-649-A, “National Consensus Standard for Configuration Management” and FAA Order 1800.66, “Configuration Management Policy”. Upon FAA approval of the CMP, the Contractor must implement its provisions.

The Contractor must maintain rigorous configuration management of all hardware, software, firmware, configuration settings, adaptations, processes, tools, and documentation comprising or associated with the DDLS. Introduction of configuration changes must not degrade or negatively impact performance. This configuration information must be made available to the FAA at the FAA’s request to verify compliance with the requirements of this section.

The Contractor must employ automated tools for configuration management, to the maximum extent reasonable, in order to minimize the possibility of human error in making configuration changes.

Configuration Management Baseline and Baseline Review The Contractor must establish a preliminary baseline for the configuration of the DDLS prior to entering FQT. Upon successful completion of FQT, the Contractor must host a Baseline Review Meeting and present the tested configuration and associated documentation to the FAA for review and approval. Upon FAA approval, the Contractor must establish a configuration baseline freeze and all subsequent changes to the baseline must be via the Engineering Change Proposal (ECP) process.

Engineering Change Proposals The Contractor must submit an ECP (CDRL A0013-ECP) for any proposed configuration changes to the DDLS, with the exception of items managed by the CSPs, after the configuration baseline freeze has been established, including at a minimum, hardware upgrades, software changes, firmware revisions, architectural changes, performance optimization changes, value engineering changes, availability improvement changes, and any changes to network element configuration settings to include route tables and network IP addresses. The Contractor must obtain concurrence from the FAA prior to instituting the change. Any changes to the DDLS made by the Contractor that results in service degradation/deficiencies, or that impairs interoperability within the Data Comm System, must be rectified at no cost to the FAA.

An ECP must be submitted for any expansion of coverage, addition of sites, introduction of new services, or upgrades of service made after the establishment of the configuration baseline freeze.

The FAA reserves the right to require pertinent testing, simulation and modeling, or other methods of verification/validation, prior to concurring on an ECP to ensure that DDLS functions and performance will not be negatively impacted by implementation of the requested change.

Method of Procedure The Contractor must generate, and submit a Method of Procedure (MOP) for each submitted ECP in accordance with (CDRL A0045-MOP).