Section C - TACAN Antenna.pdf

PART 1 - SECTION C – STATEMENT OF WORK

Screening Information Request (SIR) 693KA8-22-R-00001 i | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

1 INTRODUCTION

1.1 Background

1.2 Scope

2 DOCUMENTS

2.1 Precedence

2.2 FAA Documents

2.3 Federal, Department of Defense (DOD), Military Standards and Specifications

2.4 Other Documentation

2.5 Copies of Documents

3 REQUIREMENTS

3.1 Program Management

3.1.1 Contractor Work Breakdown Structure (CWBS)

3.1.2 Integrated Master Program Schedule (IMPS)

3.1.3 Program Management Status Reports

3.1.4 Program Risk Management

3.1.5 Meetings, Conferences, and Reviews

3.1.6 Post-Award Conference

3.1.7 Program Overview Meetings (POM)

3.1.8 Technical Interchange Meetings (TIM)

3.2 Engineering Support Services

3.3 Engineering Design and Development

3.3.1 Technical Reviews

3.3.2 Quality Assurance

3.3.3 Configuration Management Program (CMP)

3.3.4 Human Factors

3.3.5 System Security

3.3.6 System Safety Engineering

3.3.7 Environmental, Occupational Safety and Health (EOSH)

3.4 Test and Evaluation

ii | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

3.4.1 Test and Evaluation Management

3.4.2 Development Test (DT)

3.4.3 Dry Run Tests

3.4.4 Program Trouble Reports

3.4.5 Test Tool Accreditation

3.4.6 Test Readiness Review (TRR)

3.4.7 Pre-Test Briefing

3.4.8 Test Team Training Class

3.4.9 Operational Test (OT) Support

3.4.10 Site Acceptance Test (SAT)

3.5 System Hardware/Software (HW/SW) Government Support Environment

3.6 Interface Control Documents (ICDs)

3.7 National Telecommunications and Information Administration (NTIA) Certification . 31

3.8 Site Implementation

3.8.1 Site Survey, Preparation and Installation Guidelines

3.8.2 Delivery and Check-Out

3.8.3 Equipment Removal

3.8.4 Disposal of Equipment

3.8.5 Site Installation Drawings

3.9 Integrated Logistic Support (ILS)

3.9.1 ILS Management Team (ILSMT)

3.9.2 Provisioning

3.9.3 Supply Support

3.9.4 Tools and Test Equipment

3.9.5 Depot-Level Maintenance

3.9.6 Technical Data

3.9.7 System Technology

3.10 Training

3.10.1 Technical Training

3.10.2 Training Requirements

3.10.3 Training Development

iii | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

3.10.4 Validation of Training Courses

3.10.5 Training/Course Schedule

3.10.6 Training Materials, Equipment, and Facilities

1 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

1 INTRODUCTION

1.1 Background

Increasing demands on the National Airspace System (NAS), paired with the continued operations of legacy navigational aids well beyond the projected lifecycle, have elevated the requirement for Tactical Air Navigation (TACAN) supportability. The TACAN Antennas in the NAS are provided in two configurations: the Rho-Theta Antenna (RTA)-2 and Low Power

TACAN Antenna (LPTA). Obsolescence of parts for the fifty-year-old RTA-2 along with the twenty-three-year-old LPTA has given rise to a supportability issue. Through their precise rotating, both antennas provide TACAN/Azimuth advertised services. The TACAN antenna provides both azimuth and Distance Measuring Equipment (DME) advertised services to equipped military aircraft and DME advertised services to equipped civilian aircraft.

Currently, there are 430 TACANs in the NAS.

1.2 Scope

This Statement of Work (SOW) provides for the development, qualification, acquisition and implementation of the TACAN antenna systems to support azimuth and distance measuring requirements specified per FAA-E-7869, Performance Specification TACAN Antenna System and additional services as required by the Federal Aviation Administration (FAA) and Department of

Defense (DOD), Department of the Navy, Naval Air Systems Command (NAVAIR) through this contract. The Contractor, as required and directed by the FAA, performs the tasking identified within the SOW and the Task Order(s) that will define the specific performance criteria, deliverables and schedules required.

2 DOCUMENTS

2.1 Precedence

The following specifications, handbooks, standards, and drawings form a part of this SOW and are applicable to the extent specified herein. The Contractor must refer to the latest version of these documents, as of the contract award date. In the event of a conflict between this SOW and any of the applicable documents cited below, the provisions of this SOW must apply.

2.2 FAA Documents

The following documents apply. Unless otherwise stated, the latest version of these documents must apply.

FAA-E-7869, Performance Specification Tactical Air Navigation (TACAN) Antenna System, December 2021

FAA Order 6820.10, VOR, VOR/DME and VORTAC Siting Criteria, April 1986

FAA Order JO 6820.7D, Maintenance of Navigational Aids Facilities and Equipment - VOR, DVOR, VOR/DME, VORTAC, March 2018

2 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

FAA Order 1370.121B, FAA Information Security and Privacy Program & Policy, November

FAA-STD-019F, Chg. 3, Lightning and Surge Protection, Ground, Bonding, and Shielding

Requirements for Facilities and Electronic Equipment, July 2020

FAA Order JO 3000.22B, Air Traffic Organization Technical Training Management, May

FAA Order 3000.57A, Air Traffic Organization Technical Operations Training and Personnel

Certification, October 2019

FAA-STD-1293D, Servicing Standards and Test Requirements for Ground Electronic

Equipment, September 2006

HF-STD-001B, Human Factors Design Standard (HFDS), December 2016

HF-STD-004A, Standard Practice—Human Factors Engineering Requirements, September

FAA-D-2494B, Technical Instruction Book Manuscript: Electronic, Electrical, and

Mechanical Equipment, Requirements for Preparation of Manuscript and Production of

Books, March 1984

FAA 6050.19G, Radio Spectrum Planning, September 2017

FAA 6000.15J, General Maintenance Handbook for NAS Facilities

FAA Order JO 1050.17A, Environmental Compliance at Air Traffic Organization Facilities, November 2012

NAS-IC-51015108-01 v0.92, FAA Interface Control Document, Remote Monitoring, and

Logging System (RMLS) To Remote Monitoring Subsystem (RMS) Using Common Message

Handling Protocol (CMHP), March 2014

FAA-E-3039A, Protocol Specification, Common Message Handling Protocol (CMHP), September 2018

FAA-STD-025F, Preparation of Interface Documentation, November 2007

FAA-C-1391E, Installation, Termination, Splicing, and Transient / Surge Protection of

Underground Electrical Distribution System Power Cables, May 2019

FAA-C-1217H Chg. 1, Electrical Work, Premises Wiring, January 2021

FAA Order 6030.20G, Electrical Power Policy, March 2019

AC 150/5370-2G, Operational Safety on Airports During Construction, December 2017

FAA Order 3900.57A, Environmental, Occupational Safety and Health (EOSH) Requirements in the Planning and Execution of Construction and Maintenance Activities at National

Airspace System (NAS) Facilities, March 2013

FAA Order 4600.27D, Personal Property Management, December 2021

FAA Order 6010.7C, Joint Acceptance Inspection (JAI), February 2022

3 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

FAA-STD-002H, Standard Engineering Drawing Preparation and Support, September 2017

FAA-STD-028C, FAA Standard Contract Training Programs, November 2000

2.3 Federal, Department of Defense (DOD), Military Standards and Specifications

MIL-STD-810H, Test Method Standard, Environmental Engineering Considerations and

Laboratory, January 2019

MIL-STD-31000B, Military Standard: Technical Data Package (TDP), October 2018

MIL-HDBK-61B, Military Handbook: Configuration Management Guidance, April 2020

MIL-PRF-81705E, Amendment 1, Performance Specification: Barrier Materials, Flexible, Electrostatic Protective, Heat-Sealable, February 2010

MIL-STD-129R, Chg. 2 Standard Practice, Military Marking for Shipment and Storage, September 2019

MIL-STD-2073-1E, Chg. 4 Department of Defense Standard Practice for Military Packaging, April 2019

MIL-HDBK-217F, Reliability Prediction of Electronic Equipment, February 1995

MIL-HDBK-470A, Department Of Defense Handbook: Designing and Developing Maintainable

Products and Systems, May 2012

2.4 Other Documentation

NIST SP 800-53 Rev. 5, National Institute of Standards and Technology (NIST) Special

Publication (SP) 800-53 Rev. 4, April 2013

ANSI/EIA-649C, National Consensus Standard for Configuration Management, February

RTCA DO-278A, Guidelines for Communication, Navigation, Surveillance, and Air Traffic

Management (CNS/ATM) Systems Software Integrity Assurance, March 2002

RTCA DO-254, Design Assurance Guidance for Airborne Electronic Hardware, April 2000

SAE ARP-4754A, Aerospace Recommended Practice: Guidelines for Development of Civil

Aircraft and Systems (SAE), December 2010

SAE ARP-4761, Aerospace Recommended Practice: Guidelines and Methods for Conducting the Safety Assessment Process on Civil Airborne Systems and Equipment, December 1996

AS9100D, Quality Management Systems—Requirements for Aviation, Space, and Defense

Organizations, September 2016

ANSI/IEEE 149, Standard Test Procedures for Antennas, 1979

GEIA-STD-0007, Logistics Product Data, November 2019

4 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

OMB Circular A-11, Policies, Laws, and Other General Requirements for Budget Estimates, Section 31.12, December 2020

29 CFR 1910, OSHA General Industry Safety and Health Standards

29 CFR 1926, OSHA Construction Industry Standards

ASTM D5118 ASTM, Standard Practice for Fabrication of Fiberboard Shipping Boxes

ASTM D6251 ASTM, Standard Specification for Wood-Cleated Panelboard Shipping Boxes

ASTM D3951-15, Standard Practice for Commercial Packaging

ISPM 15, Guidelines for Regulating Wood Packaging Material in International Trade

ISO/IEC 15438, Barcode Symbology Specifications

2.5 Copies of Documents

Copies of FAA specifications may be obtained from the Federal Aviation Administration, Headquarters Public Inquiry Center: APA-200, 800 Independence Avenue SW, Washington, DC 20591, 202-267-3484. Requests should fully identify material desired and cite the solicitation or Contract number.

Military Standards and Specifications can be ordered from the DOD Single Stock Point, Building 4D, 700 Robbins Avenue, Philadelphia, PA 19111-5094. Information is available on its website, https://quicksearch.dla.mil/qsSearch.aspx

3 REQUIREMENTS

The Contractor must comply with requirements for the TACAN antenna In Accordance With

(IAW) specification FAA-E-7869, Performance Specification, TACAN Antenna System

(2021) this SOW, and respective Delivery/Task Order(s).

The Contracting Officer (CO) or the designated Contracting Officer’s Representative (COR) must approve all items delivered in response to this SOW, or as described in the Task

Order(s). All references to the "Government" or "FAA" in this SOW, or as described in the

Task Order(s), mean by the authority of the CO or designee.

The Contractor must produce the data items referenced by the Contract Data Requirements

List (CDRL) titles IAW the CDRL of the same name (Attachment J-4). All data deliverables must be prepared and delivered IAW the corresponding Data Item Description specified in the

CDRL. Unless otherwise specified, the Contractor must deliver all CDRLs IAW Sections 12, 14, and 16 of the CDRL.

3.1 Program Management

The Contractor must provide the management and personnel as required to complete the activities described within the period of performance specified in the Delivery/Task Order(s). The

Contractor must designate a Project Manager to act as the primary point of contact for the FAA.

https://quicksearch.dla.mil/qsSearch.aspx

5 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

The management organization, techniques, tasks, and procedures must be documented in an approved Program Management Plan (PMP).

CDRL A001 Program Management Plan

3.1.1 Contractor Work Breakdown Structure (CWBS)

The Contractor must establish and maintain a CWBS and dictionary. The dictionary must include references to CDRL, Responsible Organization, Performing Organization, and any subcontractors performing work.

3.1.2 Integrated Master Program Schedule (IMPS)

The Contractor must develop and revise an IMPS based on a logical and efficient sequence of events designed to accomplish the effort described in the SOW within the period of performance and detailed in the Delivery/Task Orders.

The Integrated Master Program Schedule must have current program milestones and deliverables. The IMPS must include prime contractor and subcontractor activities and interdependencies. All IMPS activities must be traced to CWBS with constraints, dependencies, and relationships identified.

3.1.3 Program Management Status Reports

During all program phases, the Contractor must provide program schedule status and performance reports, highlighting both key accomplishments and risks. The contractor must provide the FAA with a monthly Contractor’s Progress, Status and Management Report

(CDRL A002).

CDRL A002 Monthly Contractor’s Progress, Status and Management Report

3.1.4 Program Risk Management

The Contractor must identify cost, schedule, operational, and technical risks and describe how it will effectively manage these risks throughout the contract and Delivery/Task Order(s) performance. The Contractor must identify its risk management techniques in the PMP, and must monitor risks and implement those mitigation and risk management techniques according to the PMP. The Contractor must present risk status and risk mitigation plans during the

Engineering Design Reviews, Program Overview Meetings (POM) and document risk status in meeting minutes.

3.1.5 Meetings, Conferences, and Reviews

The Contractor must conduct meetings, conferences, and reviews IAW this SOW, or as described in the Task/ Delivery Order(s). The Contractor must prepare and submit agendas and meeting minutes with a list of action items. When meetings or conferences are held at the

Contractor’s site, the Contractor must provide facilities and office equipment (e.g., access to telephone and fax), internet access, and access to subcontractor personnel when requested by the FAA. The Contractor must provide appropriate presentation materials, mockups, and technical data. Copies of presentation materials must be prepared for all meeting participants.

If meetings cannot be held at the Contractor’s physical location, the Contractor must conduct

6 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

the meetings using approved FAA communications platforms, such as Zoom and Microsoft

Teams, etc.

CDRL A003 Meeting Agenda

CDRL A004 Meeting Minutes

CDRL A005 Briefing Material

3.1.6 Post-Award Conference (PAC)

A post-award conference must be held at the Contractor’s facility not later than one month after contract award. The agenda must be developed jointly between the Contractor and the

FAA and must contain, at a minimum, Contract requirements, management, technical topics, logistic and training planning, and deliverable schedules to include a preliminary CWBS;

system safety program; and an IMPS.

CDRL A003 Meeting Agenda

3.1.7 Program Overview Meetings (POM)

Program Overview Meetings will be held quarterly or until the Contracting Officer deems that regularly scheduled meetings are no longer necessary. POMs will be held at the Contractor’s facility or an agreed-to alternate site.

During POMs, the Contractor must present detailed Delivery/Task Order(s) cost, schedule, technical, and risk status; discuss and update outstanding action items; review potential and actual technical and programmatic problem areas and proposed solutions; describe performance relative to milestones outlined in the IMPS, and provide a forum for highlighting activity planned for the next period.

CDRL A003 Meeting Agenda

3.1.8 Technical Interchange Meetings (TIM)

The FAA or the Contractor may request Technical Interchange Meetings between the

Contractor and the Technical Officer's Representative or their designated representatives.

Meetings may be held at either Contractor or Government facilities or may be conducted by telephone or other electronic means, if appropriate. The TIM's purpose is to discuss specific technical activities, including action items, studies, test plans, test results, design issues, technical decisions, and implementation concerns to ensure continual visibility into technological progress.

The Contractor must provide presentation materials, mockups, and technical data and any documentation necessary to conduct TIMs. Copies of all presentation materials and documentation required for the TIM must be sent to the Government before the scheduled meeting.

CDRL A003 Meeting Agenda

7 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

CDRL A005 Briefing Material

3.2 Engineering Support Services

The Contractor must provide engineering support services identified in the SOW or as described in the Delivery/Task Order(s) to perform tasks including but not limited to testing, logistics, training, field support, troubleshooting, coordination of problems that may arise after successful completion of tests and support for unique issues encountered during field installation of systems as required by the FAA.

3.3 Engineering Design and Development

The Contractor must perform all required engineering to design, develop, and support the qualification of a TACAN Antenna in accordance with Specification FAA-E-7869. The

Contractor must include the performance of specialty engineering tasks supporting antenna design and development according to the requirements in this SOW. The Contractor must also document and report its engineering process, deliverables, and results IAW with a series of

Technical Reviews.

3.3.1 Technical Reviews

The Contractor must conduct three (3) Technical Reviews as identified below. Prior to each

Review, the Contractor must provide an electronic copy of the review-briefing package, including an agenda to the COR IAW the delivery schedule for each. Also, prior to the reviews, the contractor must deliver the applicable CDRLs for FAA review IAW the delivery schedule listed for each CDRL. The FAA will provide comments IAW the CDRL instructions. Technical interchange meetings must be utilized to resolve comments or issues prior to the Technical Review.

System Requirements Review (SRR)

The Contractor must host an SRR meeting as directed under the applicable Delivery/Task

Order(s). The purpose of the SRR is to confirm that the Contractor sufficiently understands all

FAA-E-7869 requirements and any applicable requirements from this SOW and has captured and traced all system-level requirements into the CDRL SE001, System/Subsystem

Specification (SSS). Approval of the SSS establishes an initial system-level functional baseline for the Contractor. This baseline creates the functional, performance, and physical attributes of the physical elements required to satisfy all the system's functionalities.

Additional SRR data is defined in CDRL SE002.

Entrance Criteria:

a. Approval of the SRR agenda

b. A first submission of CDRL SE001, SSS including traceability tables have been delivered.

c. The preliminary allocation of SSS requirements to the next lower level system

(subsystems) completion.

d. FAA approved PMP.

e. FAA approved Quality System Plan.

8 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

f. A first submission of CDRL SS001, System Safety Program Plan (SSPP).

g. A first submission of CDRL SS002, Functional Hazard Assessment (FHA).

h. A first submission of CDRL F001, Human Factors Program Plan.

i. A first submission of CDRL S001, System Security Plans.

j. Updated risk assessment and mitigations documented and consistent with the approved

PMP and Monthly Contractor’s Progress, Status and Management Report.

Items to be Reviewed

a. System-level requirements and preliminary allocation to the next lower level-system

(subsystems).

b. Preliminary approach for Test & Evaluation showing how requirements will be verified and validated down to the subsystem level.

c. Risk and mitigation strategies.

d. Plan addressing the Software and Hardware design assurance requirements.

e. Logistics and Training Plan.

Exit/Success Criteria

a. The process for allocation and control of requirements throughout all levels, within schedule constraints, established with FAA approval.

b. The requirements definition with respect to top-level requirements established with

FAA approval; interfaces with external entities and between major internal elements defined.

c. The critical technologies identified, required technology demonstrations have been planned to ensure compatibility with design requirements,

d. The preliminary approaches for how requirements will be verified and validated down to the subsystem level has been determined with FAA approval.

e. The significant risks have been identified and technically assessed, and viable mitigation strategies are defined with FAA approval.

f. The system requirements, approved material solutions, available product/process technology, and program resources are sufficient to proceed to the next life cycle phase.

g. Closeout of all SRR Action Items.

CDRL A003 Meeting Agenda

CDRL A004 Meeting Minutes

CDRL SE001 System/Subsystem Specification (SSS)

CDRL SE002 System Requirements Review Data

Preliminary Design Review (PDR)

The Preliminary Design Review will be held at a mutually agreed upon time between the FAA and the Contractor IAW the Delivery/Task Order(s). The purpose of the PDR is to evaluate progress, technical adequacy, and risk resolution in the development of the allocated baseline.

Additional PDR data is defined in CDRL SE004.

Entrance Criteria:

a. Approval of the PDR agenda

9 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

b. The first submission of CDRL SE003, System/Subsystem Design Document (SSDD) including traceability tables delivered.

c. Identify all functional requirements of FAA-E-7869 and derived requirements in a matrix format.

d. Demonstrate understanding of the guidance documents by applying appropriate tools, internal processes, and technical support and how they will be applied/flow down the requirements to the system design.

e. A second submission of the FHA.

f. Identify all inherent risks and provide analysis mitigating the risks of the program to an acceptable level.

Items to be Reviewed:

a. Definition of the functional baseline of the product.

b. Comparison of the current SSS baseline with the FAA’s functional baseline.

c. Presentation of the preliminary system-level design approaches in a similar format that addresses, at a minimum, functional requirements, risk, schedule, safety, obsolescence, availability, maintainability, and reliability.

d. Presentation of the updated Integrated Master Program Schedule.

e. Presentation of the second submission of the FHA.

f. Presentation of the updated SSPP.

Exit/Success Criteria:

a. The SSDD is completed with FAA approval.

b. The risk assessment with appropriate mitigation plans approved by the FAA.

c. The updated program schedule including system and software critical path drivers approved by the FAA

d. The Logistics and Training Plan updating program sustainment development efforts and schedules is established with FAA approval.

e. Closeout of all PDR Action Items or agreement to defer actions to the Critical Design

Review.

CDRL A003 Meeting Agenda

CDRL A004 Meeting Minutes

CDRL SE003 System/Subsystem Design Document (SSDD)

CDRL SE004 Preliminary Design Review Data

Critical Design Review (CDR)

The Critical Design Review will be held at a mutually agreed time between the FAA and the

Contractor IAW the Delivery/Task Order(s). The purpose of the CDR is to determine whether the detailed design meets the specified requirements in the appropriate developmental baseline and whether the design is complete and ready to be implemented via comprehensive hardware and software code and test. Additional CDR data is defined in CDRL SE005.

Entrance Criteria

a. Approval of the CDR agenda

b. First submission of CDRL SS003, Preliminary System Safety Assessment (PSSA)

10 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

c. First submission of CDRL E012, Reliability Analysis

d. First submission of CDRL CM013, Configuration Status Accounting Report (CSAR)

e. Submission of CDRL SS005, Plan for Software Aspects of Approval (PSAA)

f. Submission of CDRL SS009, Plan for Hardware Aspects of Approval (PHAA)

g. Submission of CDRL F002, Human Engineering Design Approach Document-Operator

h. Submission of CDRL F003, Human Engineering Design Approach Document-Maintainer

Items to be Reviewed During CDR

a. Presentation of the updated PMP that addresses all areas of development, quality and

Configuration Management (CM) control, Hardware (HW)/Software (SW), and logistic supportability based on PDR approval.

b. Presentation of the design data to validate the design approved at the PDR. The design data must be detailed, precise, and all-inclusive to assure all lower-level requirements are met, all safety requirements have been addressed, and the level of risk has been identified and assessed, and if required, Contractor’s plans to mitigate the risks.

c. Presentation of the initial design documents (HW/SW, SW Source Code, Interface

Control Documents (ICDs), Human Factors, etc.) for discussion to demonstrate how they relate to the requirements and how they were incorporated in the system design.

d. Presentation of the final FHA.

e. Presentation of the PSSA.

f. Presentation of the initial plans to conduct a Reliability Demonstration, and a

Maintainability Demonstration.

g. Presentation of the final Integrated Master Program Schedule.

h. Presentation of the final SSPP.

Exit/Success Criteria

a. Establishment of the system Product Baseline.

b. The updated risk assessment with appropriate approved mitigation plans approved.

c. The updated program development schedule including fabrication, test and evaluation, and software coding, critical path drivers approved.

d. The completed Logistics and Training Plan approved.

e. Submission of approved CDR Meeting minutes

f. Closeout of all CDR Action Items

CDRL A003 Meeting Agenda

CDRL SE005 Critical Design Review Data

3.3.2 Quality Assurance (QA)

During the entire product lifecycle, the Contractor must use a quality assurance process based on AS9100D, Quality Management Systems - Requirements for Aviation, Space, and Defense

Organizations, that satisfies the applicable objectives of RTCA/DO-278A for software and

RTCA/DO-254 for hardware. The Contractor’s quality assurance procedures must be documented in the Quality System Plan (CDRL QA001) and may be used to verify item compliance and delivery requirements. The Contractor’s quality assurance processes must be subject to audit by the FAA and the applicable certifying authority.

11 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released

CDRL QA001 Quality System Plan

Documentation, Records, and Corrective Action

The contractor’s documentation, records, and corrective action processes must be in accordance with the applicable objectives of RTCA/DO-278A and RTCA/DO-254, as determined in the PSSA (CDRL SS003).

Inspection and Testing Documentation

The Contractor’s final acceptance test procedures, acceptable to the FAA, must be used to verify item compliance with this contract’s requirement.

Corrective Action

The Contractor must take prompt action to correct conditions that have resulted or could result in the submission of supplies that do not conform to FAA-E-7869.

Drawings, Changes, and Configuration Control

The Contractor’s quality program must provide for procedures that assure the latest applicable drawings, specifications, computer software/firmware, and instructions are used in all phases and activities related to this SOW.

Nonconforming Materials and Supplies

The Contractor must establish and maintain an effective system for controlling nonconforming material and supplies, including software/firmware (if applicable).

FAA Source Inspection at the Contractor or Other

Supplier Facilities

The FAA must have the right to inspect the quality system at the Contractor’s facility. This inspection will ensure that the Contractor’s quality system can support the SOW requirements.

The FAA must have the right to inspect and/or test items to be delivered under this SOW before shipment from the Contractor or other facilities.

3.3.3 Configuration Management Program (CMP)

The Contractor must develop and implement a comprehensive Configuration Management

Program and deliver Configuration Management Plan (CDRL CM001). The CMP must comply with ANSI/EIA-649C, the National Consensus Standard for Configuration

Management, the requirements of this SOW and Delivery/Task Orders.

The Contractor must ensure the CM process for software meets the objectives in RTCA/DO-

278A for the software assurance level assigned to each software configuration item. The

Contractor must ensure the CM process for hardware meets the objectives in RTCA/DO-254 for the assurance level assigned to each required electronic hardware item.

The Contractor must identify the single focal point that will serve as the primary point of contact for all communication on CM-related issues.

CDRL CM001 Configuration Management Plan (CMP)

12 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

Configuration Identification (CI)

The Contractor must perform configuration identification IAW EIA-649C. Upon approval by the Government of the CIs, the Contractor must manage the CIs to maintain the integrity and traceability of its configuration, including all components provided by subcontractors.

The Contractor must assign a discrete part/item identification number at the Line Replacement

Unit (LRU) level for developed, modified Commercial-Off-The-Shelf (COTS) or Non-

Developmental Items (NDIs). This part number must uniquely identify the item configuration conforming to the requirements IAW EIA-649C.

Configuration Change Management

The Contractor must implement configuration change management procedures IAW

ANSI/EIA-649C to ensure proposed changes are documented, evaluated and adjudicated.

The Contractor must use hardware and software configuration change management processes complying with the requirements of RTCA/DO-254 and RTCA/DO-278A. Safety artifacts must be integrated into the product baseline to document the system configuration baseline's safety compliance.

Configuration change management must manage configuration changes, and variances. The

Contractor must notify the FAA prior to implementing a change or variance that affects the delivered item’s approved Functional, Allocated, or Product Baselines. The contractor must submit Specification Change Notice IAW CDRL CM005 for approval prior to implementation. The Contractor must submit Engineering Change Proposals (ECPs) IAW

CDRL CM003 for approval prior to implementation of any change. Proposed changes to any baseline must include assessing impact and identifying changes to the safety artifacts. Any proposed change, or variance requires advance approval from the FAA.

CDRL CM003 Engineering Change Proposal

CDRL CM005 Specification Change Notice

Configuration Status Accounting (CSA)

The Contractor must maintain a CSA information system to report the status of each

CI/Protocol Control Information. The Contractor must ensure that the CSA information is available for review by the FAA, as requested. The Contractor must generate Configuration

Status Accounting Reports IAW CDRL CM013.

CDRL CM013 Configuration Status Accounting Report

Configuration Audits

Configuration Audits must be IAW EIA-649C.

The Contractor must support joint Contractor/FAA configuration audits for the TACAN

Antenna. The Contractor must prepare and submit a Configuration Audit Plan (CM008), which describes the Contractor’s approach for conducting the audits. The audit plan must be approved, and an agenda (CDRL A003) must be agreed to between the Contractor and the

FAA before the audits. The Contractor must prepare and submit a Functional Configuration

13 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

Audit (FCA)/Physical Configuration Audit (PCA) Configuration Audit Summary Report

(CDRL CM009) documenting all FCA/PCA findings.

CDRL A003 Meeting Agenda

CDRL CM008 Configuration Audit Plan

CDRL CM009 Configuration Audit Summary Report

The Product Baseline must be established after the successful completion of the FCA/PCA.

The Contractor is responsible for ensuring that sub-contractors’, vendors’, and suppliers’ CIs are part of the audit process. FCA must be completed and approved before the start of PCA.

Functional Configuration Audit (FCA)

The Contractor must support an FCA conducted by the FAA at the Contractor’s facility. The

FCA must be conducted on the first production article against the approved requirements verification test matrix. The FCA will audit and validate that the actual performance of the

TACAN Antenna meets the requirements stated in FAA-E-7869.

FCA entrance criteria must include successful completion of Operational Test and Evaluation

(OT&E).

FCA exit criteria must include validation by the Government that all requirements have been verified successfully.

Physical Configuration Audit (PCA)

The Contractor must support a PCA conducted by the FAA at the Contractor's facility of a first production article used for the FCA. The PCA validates that the Contractor’s product configuration documentation (including computer-aided-design (CAD) models, drawings, training manuals, technical data, and software source code) accurately reflects the validated product. The PCA validates the exact, complete, and accurate documentation representing the intended design used to establish the Product Baseline.

PCA entrance criteria must include all design and product documentation. At a minimum, the following documents must be audited: Production Test Report, Technical Instruction Books

(TIBs), Specifications, Drawings, Support Equipment Manuals, Product Baseline Index, and

Logistics Management Information (LMI). PCA exit criteria establishes the product baseline.

Product Baseline

The Contractor must maintain the configuration baselines and the required documentation to support these baselines IAW EIA-649-1 for all identified CIs for the TACAN Antenna system.

The approved Product Baseline IAW CDRL CM012 must be established after the successful completion of FCA/PCA.

CDRL CM012 Product Baseline Index

The Product Baseline Index documentation must include engineering drawings, TIB, hardware drawings, software code, software platform, ICD, specifications, and Test Program Sets (TPS).

14 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.”

The FAA will manage the product baseline after it has been established by the Contractor. The contractor must inform the FAA of any changes to the baseline via engineering change proposals in accordance with 3.3.3.2

3.3.4 Human Factors

The Contractor must ensure that the TACAN Antenna System complies with FAA-E-7869;

HF-STD-001B, Human Factors Design Standard (HFDS); and HF-STD-004A, Standard

Practice – Human Factors Engineering Requirements to achieve human-centered, error-resistant, error-tolerant, operationally effective, operationally suitable, and usable systems.

The Contractor must review applicable standards and propose relevant Human Factors requirements IAW CDRL F001, this SOW, or as described in the Delivery/Task Order(s).

CDRL F001 Human Factors Program Plan

CDRL F002 Human Engineering Design Approach Document – Operator

CDRL F003 Human Engineering Design Approach Document – Maintainer

CDRL F004 Critical Task Analysis Report

3.3.5 System Security

The TACAN antenna system must be designed IAW FAA Order 1370.121B, FAA

Information Security and Privacy Program to ensure proper operation and protect against unauthorized access to the system and information.

The TACAN antenna system provides navigation support that is Efficiency-Critical and rated

Federal Information Processing Standards (FIPS) 199 High. In cooperation with the FAA, the

Contractor must review security controls, determine applicability to the TACAN Antenna system and the security of the FAA, and appropriately apply the control IAW NIST SP 800-53

Rev. 5.

CDRL S001 System Security Plan

3.3.6 System Safety Engineering

Systems safety engineering is integral to systems development. Accordingly, the Contractor must establish and implement a System Safety Program that plans, coordinates, and manages design safety activities to ensure acceptable safety risk. SAE Aerospace Recommended

Practices (ARPs) 4754A and 4761 guide system development with safety interdependency in the context of demonstrating compliance for certification of civil aircraft and systems. While some of the language is not relevant to the ground-based systems, the methodology contained therein can be applied to the development of the TACAN Antenna system to ensure the process is driven by a systematic assessment of safety. The methodology of ARP 4754A and

4761 serves as the basis for the SOW systems safety engineering requirements.

The Contractor must develop and submit a SSPP IAW CDRL SS001 that details the program scope, safety organization, program milestones, requirements and criteria, safety assessments, safety data, verification of safety requirements, auditing and monitoring program, training, accident and incident reporting, and interfaces. The Contractor must identify a system safety

Point of Contact (POC) to provide the engineering services described in this section. Guidance for the SSPP can be found in ARP 4754A, Table 1, and Section 5.1.5.

15 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released

The Contractor must develop a FHA IAW CDRL SS002. The FHA must identify and classify the failure conditions of system functions according to their severity. The FHA is iterative and becomes more defined and fixed as the system is developed.

In addition to the associated requirements in FAA-E-7869, the system-level Functional

Development Assurance Level (FDAL) for the provision of TACAN range services must be

Level A. The system-level FDAL for the provision of TACAN azimuth service must be Level

A.

The required FDALs are based on the FAA’s safety assessments1, and FDAL definitions are found in ARP 4754A. Guidance for the FHA can be found in SAE ARP 4761, Appendix A.

The Contractor must develop a PSSA IAW CDRL SS003.

The PSSA must identify and capture all system safety requirements necessary to mitigate failures and errors. Safety requirements categories include independence, monitoring, availability, integrity, maintainability, and development assurance. Guidance for the PSSA can be found in SAE ARP 4761, Appendix B.

The Contractor must develop a System Safety Assessment (SSA) IAW CDRL SS004. The

SSA must collect, analyze, and document verification that the TACAN Antenna System meets the safety requirements of the PSSA. Guidance for the SSA can be found in SAE ARP 4761, Appendix C.

Pursuant to the system-level FDALs (Level A) and the associated Catastrophic failure conditions1, the Contractor must include a Common Cause Analysis (CCA) as part of the FHA

(CDRL SS002) and the PSSA (CDRL SS003).

The CCA is a tool for assessing the necessity for independence requirements to satisfy the requisite level of safety. The CCA evaluates dependencies at the functional, system, and item level to determine the effect on failure conditions having classifications of Hazardous or

Catastrophic.

Guidance for the CCA can be found in SAE ARP 4761, Section 4.4. The CCA is iterative, initiating with the FHA, to ensure design decisions appropriately address independence requirements.

CDRL SS001 System Safety Program Plan (SSPP)

CDRL SS002 Functional Hazard Assessment

CDRL SS003 Preliminary System Safety Assessment (PSSA)

CDRL SS004 System Safety Assessment

1 The applicable documents include the Distance Measuring Equipment (DME), Very-High Frequency Omnidirectional Range (VOR), TACAN

(DVT) Operational Safety Assessment (OSA) (version 1.0, December 2020) and the TACAN Antenna Functional Fault Hazard Assessment (FFHA) (TBD). These documents are provided as attachments J-6 and J-7, respectively.

16 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released

Software and Electronic Hardware Assurance

The Contractor must acquire/develop, document, test, and manage all system hardware and software provided or developed under this SOW, or as described in the Delivery/Task

Order(s).

The software and electronic hardware items must be developed to the level of rigor necessary to satisfy the required Item Development Assurance Levels (IDALs) of the PSSA, which are derived from the specified Level A system-level FDALs.

The IDALs correlate to the standardized levels for software and hardware assurance found in

RTCA/DO-278A and RTCA/DO-254, respectively. The Contractor must satisfy the applicable objectives for each software and electronic hardware item, as dictated by the assurance level assigned to that item in the PSSA.

Similar to the SAE ARPs referenced above, RTCA/DO-254 was developed in the context of demonstrating compliance for certification of airborne systems. A parallel application of the design assurance process rigor will provide an appropriate level of consideration towards obtaining approval for the TACAN Antenna system.

The Contractor must develop a Plan for Software Aspects of Approval (PSAA) IAW CDRL

SS005, which requires the developer to have a development assurance program that meets the requirements of RTCA/DO-278A.

The PSAA describes the proposed development activities and artifacts to comply with the requisite level of rigor for each software item. The Contractor must develop a Software

Accomplishment Summary (SAS) IAW CDRL SS006 to demonstrate compliance with the approved PSAA.

The Contractor must submit a Software Configuration Index (SCI) IAW CDRL SS007 to capture the software product's baseline configuration.

The Contractor must submit a Software life cycle Environment Configuration Index (SECI)

IAW CDRL SS008 to identify the tools and environment used to build and test the approved software.

The Contractor must develop a Plan for Hardware Aspects of Approval (PHAA) IAW CDRL

SS009, which requires the developer to have a development assurance program consistent with

RTCA/DO-254. The PHAA describes the proposed development activities and artifacts to comply with the requisite level of rigor for each electronic hardware item.

The Contractor must submit a Hardware Accomplishment Summary (HAS) IAW CDRL

SS010 to demonstrate compliance with the approved PHAA.

The Contractor must submit a Hardware Configuration Index (HCI) IAW CDRL SS011 to

17 | Page Screening for Information 693KA8-22-R-00001— Section C-Statement of Work

“This contract may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released completely identify both the hardware configuration and embedded logic.

The Contractor must submit a Hardware life cycle Environment Configuration Index (HECI)

IAW CDRL SS012 to identify the configuration of the life cycle environment for the hardware and embedded logic.

CDRL SS005 Plan for Software Aspects of Approval (PSAA)

CDRL SS006 Software Accomplishment Summary (SAS)

CDRL SS007 Software Configuration Index (SCI)

CDRL SS008 Software Life Cycle Environment Configuration Index (SECI)

CDRL SS009 Plan for Hardware Aspects of Approval (PHAA)

CDRL SS010 Hardware Accomplishment Summary (HAS)

CDRL SS011 Hardware Configuration Index (HCI)

CDRL SS012 Hardware Life Cycle Environment Configuration Index (HECI)

Development Assurance Support

The Contractor may obtain the services of a consultant to ensure development assurance requirements are met. The consultant may validate the Contractor’s system safety program and safety assessments (i.e., FHA, PSSA, and SSA). Furthermore, the consultant’s support may ensure that the software and complex hardware have been designed and developed IAW RTCA/DO-

278A and RTCA/DO-254 to the degree to which the standards are applicable, as assigned in the

Contractor’s PSSA and IAW the Delivery/Task Order(s). The FAA reserves the right to audit the assurance activity at any time.

The primary responsibilities of the consultant are to:

a. Ensure the Contractor designs operational systems that manage hazard-related risks and provide service with rigorous safety methods employed.

b. Assist in the development of the PSAA and PHAA to ensure alignment with applicable objectives of RTCA/DO-278A and RTCA/DO-254.

c. Perform Design Assessments and Performance Assessments based on system safety principles.

d. Validate the performance of the Contractor’s programs for continued operational safety.

Software/Hardware Assurance Reviews

The Government will conduct reviews of software and electronic hardware development processes and associated data to assure that the product complies with the approved plans and procedures while satisfying the applicable objectives of RTCA/DO-278A and RTCA/DO-254.

The Contractor must provide access to supporting data and artifacts, including but not limited to those prescribed in the PSAA and PHAA.