DVT SIR - DRAFT Task Order 2 - Engineering Design and Development - Clean.pdf

TASK ORDER 002 – ENGINEERING, DESIGN, & DEVELOPMENT

Screening Information Request (SIR) 693KA8-23-R00001

1 | Page Draft Task Order 2

“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.”

Task Order No: 002

TASK ORDER NAME: DVT ENGINEERING, DESIGN & DEVELOPMENT

1 BACKGROUND

The Federal Aviation Administration (FAA) has a need to replace existing Distance Measuring Equipment (DME), Very High Frequency Omnidirectional Range (VOR), and Tactical Air Navigation (TACAN) to sustain azimuth and distance measuring services for aircraft operating in the National Airspace System (NAS). This Task Order provides for the design, development, and qualification support of the DVT Systems. The DVT Systems to be procured by the FAA must be capable of operating in multiple configurations:

a) Independently.

b) Integrated with each other.

c) Integrated into the configurations deployed in the NAS.

2 SCOPE OF WORK

This Task Order is issued for the engineering, design, development, test & evaluation, procurement, and delivery of four first article DME systems, four first article TACAN Transponder systems, four first article Doppler VOR systems, and four first article Conventional VOR systems.

2.1 ENGINEERING, DESIGN, AND DEVELOPMENT

The Contractor must perform the engineering tasks supporting system design and development according to Section C of the Indefinite-Delivery, Indefinite-Quantity (IDIQ) Contract requirements. The Contractor must also document and report their engineering process, deliverables, and results in accordance with (IAW) with a series of Design Reviews. The Contractor must perform the required engineering activities to design, develop, manufacture, and support the qualification of the DME, VOR, and TACAN Systems (hereinafter “DVT Systems”) as follows:

a) DME IAW the Performance Specification – Distance Measuring Equipment (DME) Transponder System – FAA-E-37016.

b) VOR IAW Performance Specification - Very High Frequency (VHF) Omnidirectional Radio Range (VOR) System – Conventional (CVOR) and Doppler (DVOR), FAA-E- 37012.

c) TACAN Transponder IAW Performance Specification Tactical Air Navigation (TACAN) Ground Transponder System, FAA-E-7870.

2.1.1 Technical Interchange Meetings

The Contractor may conduct Technical Interchange Meetings (TIMs). Before each TIM, the Contractor must provide an electronic copy of the review briefing package, including an agenda, to the Contracting Officer Representative (COR)/Task Order Representative (TOR). TIMs must be used to resolve comments or issues prior to Design Reviews.

2.2 TECHNICAL REVIEWS

2 | Page Draft Task Order 2

“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 Contractor must conduct four joint Technical Reviews for the DME and TACAN Systems and four Technical Reviews for the Conventional and Doppler VOR systems at their facility:

a) System Requirements Review (SRR): the purpose of the SRR is to confirm that the Contractor sufficiently understands the DVT Systems’ requirements and any applicable requirements from this Task Order and has captured and traced all system-level requirements so that the Contractor can establish an initial system-level functional baseline.

b) System Design Review (SDR): the purpose of the SDR is to evaluate the optimization, correlation, completeness, and risks associated with the allocated technical requirements.

This review must also include a summary review of the systems engineering process, which produces the allocated technical baseline and system architecture for each of the DVT Systems.

c) Preliminary Design Review (PDR): the purpose of the PDR is to evaluate progress, technical adequacy, and risk resolution in the development of the allocated baseline for each of the DVT Systems.

d) Critical Design Review (CDR): 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.

Prior to each Technical Review, the Contractor must deliver for FAA review the applicable documentation required as entrance criteria IAW the delivery schedule listed in this Task Order (which takes precedence) provided in Section 3 DELIVERABLES AND DELIVERY SCHEDULE, or as specified in the applicable Contract Data Requirements List (CDRL). To close out each Technical Review, the Contractor is required to receive a formal approval from the FAA for the documentation submitted.

2.2.1 System Requirements Review (SRR)

To complete the SRR, the Contractor must demonstrate that FAA requirements have been translated into system-specific technical requirements, critical technologies are identified, required technology demonstrations are planned to ensure compatibility with design requirements, and risks are identified. The Contractor must also show that mitigation plans are in place to address identified risks.

SRR entrance criteria must be fulfilled before the conduct of the SRR meetings. The Contractor must host the DME and TACAN SRR meeting not later than four months after contract award.

The Contractor must host the VOR SRR meeting not later than five months after contract award.

2.2.1.1 SRR—Entrance Criteria:

a) FAA Approval of the SRR Meeting Agenda, CDRL A003.

b) Submission of the SRR Data, CDRL SE002.

c) Submission of the System Segment Specification (SSS), CDRL SE001.

d) Submission of the Human Factors Program Plan, CDRL F001.

e) Submission of the System Security Plan (SSP), CDRL S001.

f) Submission of the System Engineering Master Plan (SEMP), CDRL SE007.

g) Submission of the Quality System Plan (QSP), CDRL QA001.

h) Submission of the Contractor’s Master Test Plan (CMTP), CDRL E001.

3 | Page Draft Task Order 2

“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.”

2.2.1.2 SRR—Topics to be Reviewed:

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

(subsystem).

b) Functional Analysis (top-level block diagrams), Preliminary System Architectures.

c) System Maintenance Concept.

d) Significant System Design Criteria (reliability, maintainability, logistics requirements, etc.).

e) System Engineering Planning.

f) Top-Level Technical Performance Measurement approach.

g) Human Engineering approach.

h) Information Security related to Remote Maintenance Monitoring (RMM) connectivity.

i) System Safety Architecture, Approach, and Risk.

j) Preliminary Program Master Schedule.

k) Compare the functional baseline with the FAA’s functional baseline.

l) Preliminary approach for Test & Evaluation (T&E), showing how requirements will be verified and validated down to the hardware (HW) and software (SW) subsystem level.

m) Preliminary risk and mitigation strategies.

2.2.1.3 SRR—Exit/Success Criteria:

a) FAA approval of the SRR meeting minutes, CDRL A004, and SRR Briefing materials, CDRL A005, including a summary of all the activities, discussions and action items during the meeting.

b) The process for allocation and control of the requirements throughout all levels.

c) The requirements definition with respect to top-level requirements; interfaces with external entities and between major internal elements defined.

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

e) The preliminary approaches for how requirements will be verified and validated have been identified.

f) Any significant risks have been identified and technically assessed.

g) The system requirements and program resources are sufficient to proceed to the next life cycle phase.

h) FAA approval of the functional system baseline and system architecture.

i) FAA approval of the SSS, CDRL SE001 for each applicable system.

j) FAA approval of the SRR, CDRL SE002.

k) FAA approval of the SSS, CDRL SE001.

l) FAA approval of the Human Factors Program Plan, CDRL F001.

m) FAA approval of the SSP, CDRL S001.

n) FAA approval of the SEMP, CDRL SE007.

o) FAA approval of the QSP, CDRL QA001.

p) FAA approval of the CMTP, CDRL E001.

q) Closeout of all the SRR Action Items.

2.2.2 System Design Review (SDR)

4 | Page Draft Task Order 2

“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 SDR will be conducted when the applicable system definition effort has proceeded to the point where system characteristics are defined, and configuration items (CIs) identified. This review will also include a review of the system safety analysis process, including the development of the Functional Hazard Assessment (FHA).

All SDR entrance criteria must be provided before the conduct of the SDR meeting. The Contractor must host the SDR meeting not later than four months after the completion of the SRR meeting for the applicable systems. The Contractor must establish the DVT Systems allocated baseline to complete the SDR.

2.2.2.1 SDR—Entrance Criteria:

a) FAA Approval of the SDR Meeting Agenda, CDRL A003.

b) Submission of the SDR Data, CDRL SE004.

c) Submission of the System/Subsystem Design Document (SSDD), CDRL SE003.

d) Submission of the Software Development Plan (SDP), CDRL I003.

e) Submission of the FHA, CDRL SS002.

2.2.2.2 SDR—Topics to be Reviewed:

a) Updated System Architecture.

b) Updated System Requirements.

c) Updated System Safety Requirements.

d) Subsystem HW Requirements.

e) Subsystem SW Requirements.

System and Subsystem Interface Definitions.

2.2.2.3 SDR – Exit/Success Criteria:

a) FAA approval of the SDR Meeting Minutes, CDRL A004, and SDR Briefing Materials, CDRL A005, including a summary of all the activities, discussions, and action items during the meeting.

b) FAA approval of the SSDD(s), CDRL SE003.

c) FAA approval of the FHA(s), CDRL SS002.

d) FAA approval of the SDP(s), CDRL I003.

e) FAA approval of the allocated system baseline and system architecture.

f) Closeout of all the SDR action items.

2.2.3 Preliminary Design Review (PDR)

PDR entrance criteria must be fulfilled before the conduct of the PDR meeting. The Contractor must host the PDR meeting not later than four months after the completion of the SDR meeting for the applicable systems.

2.2.3.1 PDR—Entrance Criteria:

a) Approval of the PDR Meeting Agenda, CDRL A003.

b) Submission of the Critical Task Analysis Report, CDRL F004.

c) Submission of the SW Requirements Data, CDRL I002.

d) Submission of the SW Design Descriptions, CDRL I005.

5 | Page Draft Task Order 2

“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.”

e) Submission of the HW Requirements, CDRL I011.

f) Submission of the HW Design Data, CDRL I013.

g) Submission of the PDR Data, CDRL SE005.

h) Submission of the Preliminary System Safety Assessments (PSSAs), CDRL SS003.

2.2.3.2 PDR—Topics to be Reviewed:

a) Updated Integrated Master Program Schedule(s) including system and software critical path drivers.

b) Updated System Architecture.

c) Preliminary System Safety Analysis.

d) System Interface Requirements.

e) Verifying traceability status.

f) Critical Task Analysis.

g) Human Engineering, Human Factors.

h) Barcoding and asset tracking methodologies for Line Replaceable Units (LRUs).

i) Understanding of the guidance documents by application of the appropriate tools, internal processes, and technical support and how they will be applied/flow down of the requirements to the system design.

j) Inherent risks and analysis mitigating the risks of the program to an acceptable level.

k) Detailed descriptions of the Contractor’s program and project management controls and processes.

l) Preliminary system level design approaches that address, as a minimum, the flow down of the functional requirements to design, obsolescence, availability, maintainability, and reliability.

m) HW System/Subsystem requirements and preliminary design.

n) SW System/Subsystem requirements and preliminary design.

o) Plan for Software Aspects of the Approval (PSAA), CDRL SS005.

p) Plan for Hardware Aspects of Certification (PHAC), CDRL SS009.

2.2.3.3 PDR—Exit/Success Criteria:

a) FAA approval of the PDR Meeting Minutes, CDRL A004, and PDR Briefing Materials, CDRL A005, including a summary of all the activities, discussions, and action items during the meeting.

b) Updated risk assessment with appropriate mitigation plans.

c) FAA approval of the Critical Task Analysis Report, CDRL F004.

d) FAA approval of the SW Requirements Data, CDRL I002.

e) FAA approval of the SW Design Descriptions, CDRL I005.

f) FAA approval of the HW Requirements, CDRL I011.

g) FAA approval of the HW Design Data, CDRL I013.

h) FAA approval of the PDR Data, CDRL SE005.

i) FAA approval of the PSSA, CDRL SS003.

j) Closeout of all the PDR action items.

2.2.4 Critical Design Review (CDR)

6 | Page Draft Task Order 2

“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.”

CDR entrance criteria must be fulfilled before the conduct of the CDR meeting. The Contractor must host the CDR meeting not later than six months after the completion of the PDR meeting for the applicable systems.

2.2.4.1 CDR—Entrance Criteria:

a) Approval of the CDR Meeting Agenda, CDRL A003.

b) Submission of the CDR Data, CDRL SE006.

c) Submission of the Configuration Status Accounting Reports CDRL CM013.

d) Submission of the Reliability Analyses, CDRL E012.

e) Submission of the Human Engineering Design Approach Document (HEDAD-O) –

Operator, CDRL F002.

f) Submission of the Human Engineering Design Approach Document (HEDAD-M) –

Maintainer, CDRL F003.

g) Final submission of the SW Design Descriptions, CDRL I005.

h) Final submission of the HW Design Data, CDRL I013.

i) Final submission of the FHAs, CDRL SS002.

2.2.4.2 CDR—Topics to be Reviewed:

a) System design documents (HW design, SW design, Interface Control Documents (ICDs), etc.).

Design data to prove the design approved at the PDR was synthesized as presented in the PDR. The design data must be detailed, clear, and all inclusive.

b) Verification traceability status.

c) Reliability Demonstration Plans.

d) Maintainability Demonstration Plans.

e) System Safety Assessment and design status.

f) The final Integrated Master Program Schedule.

g) Human Engineering Design Approach.

h) Monthly Contractor’s Progress, Status, and Management Report with updated risk assessment and mitigations; and updated integrated Master Schedule to deliver first article systems.

i) HW and SW testing status.

j) Readiness to develop first articles.

2.2.4.3 CDR—Exit/Success Criteria:

a) FAA approval of the CDR Meeting Minutes, CDRL A004, and CDR Briefing Materials, CDRL A005, including a summary of all the activities, discussions, and action items during the meeting.

b) FAA approval of the system product baseline.

c) Updated risk assessments with approved mitigation plans.

d) Updated Integrated Master Program Schedule.

e) FAA approval of the Reliability Analysis, CDRL E012.

f) FAA approval of the HEDAD-O, CDRL F002.

g) FAA approval of the HEDAD-M, CDRL F003.

h) FAA approval of the SW Design Descriptions, CDRL I005.

7 | Page Draft Task Order 2

“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.”

i) FAA approval of the HW Design Data, CDRL I013.

j) FAA approval of the CDR Data, CDRL SE006.

k) FAA approval of the FHAs, CDRL SS002.

l) Closeout of all the CDR action items.

2.3 QUALITY ASSURANCE (QA)

The Contractor must have a Quality Management System (QMS) compliant with AS9100D/ISO9001, Quality Management Systems - Requirements for Aviation, Space, and Defense Organizations. The Contractor’s quality planning elements for the development and sustainability of all systems, SW, and HW must be documented in the Quality System Plan

(CDRL QA001).

The Contractor must create life cycle data items to show compliance to the applicable Quality/Process Assurance development assurance objectives, as stated in the System Safety and Development Assurance Section of this Task Order. The Contractor’s QMS, Quality Plans, and other Quality/Process Assurance life cycle data items must be subject to audit by the FAA.

The Contractor must identify a main point of contact (POC) and an alternate POC at the beginning of the program to interface with the FAA on all QA matters.

CDRL QA001 Quality System Plan

2.3.1 FAA Source Inspection at the Contractor or Other Supplier Facilities The Contractor must allow the FAA to inspect the QMS at the Contractor’s facility. This inspection will ensure the Contractor’s QMS can support all contractual requirements. The Contractor must allow the FAA to inspect and test items to be delivered under this contract before shipment from the Contractor or other facilities.

2.4 CONFIGURATION MANAGEMENT (CM)

The Contractor must have a Configuration Management System (CMS) compliant with American National Standards Institute/Electronics Industries Alliance (ANSI/EIA)-649C, Configuration Management Standard. The Contractor’s CM planning elements for the development and sustainability of all systems, software, and hardware must be documented in the Configuration Management Plan (CDRL CM001).

The Contractor must create life cycle data items to show compliance to the applicable CM development assurance objectives, as stated in the System Safety and Development Assurance Section of this Task Order. The Contractor’s CMS, CM Plans, and other CM life cycle data items must be subject to audit by the FAA.

The Contractor must identify a main POC and an alternate POC at the beginning of the program to interface with the FAA on all CM matters.

CDRL CM001 Configuration Management Plan

8 | Page Draft Task Order 2

“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.”

2.4.1 Configuration Identification

The Contractor must perform configuration identification IAW ANSI/EIA-649C for all systems.

Upon approval by the FAA 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 LRU level for developed, Modified Commercial-Off-The-Shelf or Non-Developmental Items. This part number must uniquely identify the item configuration conforming to the requirements IAW

ANSI/EIA-649C.

2.4.2 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 for each system, specifically, the DME, TACAN Transponder, Doppler VOR, and Conventional VOR.

CDRL CM013 Configuration Status Accounting Reports

2.4.3 Configuration Audits

The Contractor must support joint Contractor/FAA Configuration Audits. Configuration Audits must be IAW ANSI/EIA-649C. Configuration Audits will be conducted for the DME, the TACAN Transponder, and the VORs (Doppler and Conventional combined). The Contractor must prepare and submit a Configuration Audit Plan (CM008) that describes the Contractor’s approach for conducting all the audits. CDRL CM008 must include the plans for both Functional Configuration Audit (FCA) and Physical Configuration Audit (PCA). The Configuration Audit Plan must be approved, and an agenda (CDRL A003) must be agreed to between the Contractor and the FAA before the first audit is conducted. The Contractor must prepare and submit a FCA and PCA Configuration Audit Summary Reports (CDRL CM009) for each system documenting all FCA/PCA findings for each audit conducted.

The Product Baseline must be established after the successful completion of the FCA/PCA. The Contractor is responsible for ensuring that subcontractors’, vendors’, and suppliers’ CIs are part of the audit process. FCA must be completed and approved before the start of PCA.

CDRL A003 Meeting Agenda CDRL CM008 Configuration Audit Plan CDRL CM009 Configuration Audit Summary Reports

2.4.3.1 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 each system meets the requirements stated in applicable performance specification. FCA entrance criteria must include successful completion of Operational Test and Evaluation. FCA exit criteria must include validation by the FAA that all requirements have been verified successfully.

9 | Page Draft Task Order 2

“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.”

2.4.3.2 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 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. Completion of the PCA establishes the product baseline.

2.4.4 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 systems. The approved Product Baseline Index IAW CDRL CM012 must be established after the successful completion of the FCA/PCA of each system; specifically, the DME, TACAN Transponder, Doppler VOR, and Conventional VOR. The Product Baseline Index documentation must include engineering drawings, TIB, hardware drawings, software code, software platform, ICD, specifications, and Test Program Sets. After the establishment of the Product Baseline, the FAA will manage the product baseline. The Contractor must inform the FAA of any changes to the baseline via engineering change proposals IAW Section C.3.5.

CDRL CM012 Product Baseline Index

2.5 HUMAN FACTORS

The Contractor must ensure that the systems comply with HF-STD-001B, Human Factors Design Standard; and HF-STD-004A, Standard Practice – Human Factors Engineering Requirements. These human factor requirements aim to achieve human-centered, error-resistant, error-tolerant, operationally effective, operationally suitable, and usable systems.

The Contractor must develop a Human Factors Program Plan IAW CDRL F001 that describes the Contractor’s entire human factors program for all systems, identifies its elements, and explains how the elements will be managed.

The Contractor must develop a Human Engineering Design Approach Document – Operator that provides the data to evaluate the extent to which all systems having an interface with operators meets human performance requirements and human engineering criteria.

The Contractor must develop a Human Engineering Design Approach Document – Maintainer that provides the data to evaluate the extent to which all systems (hardware and software) having an interface with maintainers meet human performance requirements and human engineering criteria.

10 | Page Draft Task Order

“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 Contractor must develop a Critical Task Analysis Report that describes the results of critical tasks performed to provide a basis for evaluation of the design of all systems, verifying that human factors technical risks have been minimized and solutions are in hand.

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

2.6 SYSTEM SAFETY AND DEVELOPMENT ASSURANCE

The Contractor must produce system life cycle data IAW SAE Aerospace Recommended Practice (ARP)4754A, Guidelines for Development of Civil Aircraft and Systems, Table A-1, to show compliance to Functional Development Assurance Level A (FDAL-A) objectives for all ranging and azimuth services of all DVT systems. The intent is to produce the objective evidence (life cycle data compliance packages) necessary to show compliance to the development assurance guidance documents (SAE ARP4754A, RTCA/DO-278A, RTCA/DO-254, Design Assurance Guidance for Airborne Electronic Hardware) at the applicable DALs.

The Contractor must follow the guidance of SAE ARP4754A, from the onset of development planning throughout completion of the development process and produce a separate life cycle data compliance package for each system. Planning documents may cover more than one system.

The Contractor must identify a main POC and an alternate POC at the beginning of the planning process to interface with the FAA on all safety and development assurance matters.

The Contractor must develop and submit a System Safety Program Plan (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 develop and submit an FHA IAW CDRL SS002 for each system. 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. The required FDALs are based on the FAA’s safety assessments1, and these documents are the basis for the FHA.

The Contractor must develop and submit a Preliminary System Safety Assessment (PSSA) IAW CDRL SS003 for each system. 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.

1 The applicable documents include the Operational Safety Assessments (OSA) and the Preliminary Hazard Analyses (PHA) for the DVT system (Distance Measuring Equipment (DME), Very-High Frequency Omnidirectional Range (VOR), and TACAN.)

11 | Page Draft Task Order

“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 Contractor must develop and submit a System Safety Assessment (SSA) IAW CDRL SS004 for each system. The SSA must collect, analyze, and document verification that the system meets the safety requirements of the PSSA.

CDRL SS001 SSPP

CDRL SS002 Functional Hazard Assessment

CDRL SS003 PSSA

CDRL SS004 System Safety Assessment

2.6.1 Hardware Development Assurance

The Contractor must apply RTCA/DO-254 IAW the version of FAA Advisory Circular (AC) 20- 152A, Development Assurance for Airborne Electronic Hardware, in place during the planning process and produce hardware life cycle data IAW RTCA/DO-254, Table A-1, to show compliance to the applicable DAL objectives, as determined by the Item Development Assurance Level (IDAL) assignment process. The Contractor must create life cycle data compliance packages for applicable hardware components of each system. Planning documents may cover more than one hardware component.

The Contractor must develop and submit a PHAC IAW CDRL SS009 for each system that requires the developer to have a development assurance program consistent with RTCA/DO-254.

The PHAC describes the proposed development activities and artifacts to comply with the requisite level of rigor for each complex electronic hardware item.

The Contractor must develop and submit a Hardware Accomplishment Summary (HAS) IAW CDRL SS010 for each system to demonstrate compliance with the approved PHAC.

The Contractor must develop and submit a Hardware Configuration Index (HCI) IAW CDRL SS011 for each system to completely identify both the hardware configuration and embedded logic.

The Contractor must develop and submit a Hardware life cycle Environment Configuration Index (HECI) IAW CDRL SS012 for each system to identify the configuration of the life cycle environment for the hardware and embedded logic.

CDRL SS009 PHAC

CDRL SS010 HAS

CDRL SS011 HCI

CDRL SS012 HECI

2.6.2 Software Development Assurance

The Contractor must produce software life cycle data IAW RTCA/DO-278A, Tables A-1 through A-10, to show compliance to applicable DAL objectives, as determined by the IDAL assignment process. The Contractor must create a life cycle data compliance package for applicable software components for each system. Planning documents may cover more than one software component.

12 | Page Draft Task Order

“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 Contractor must develop and submit a PSAA IAW CDRL SS005 for each system, which requires the developer to have a development assurance program consistent with 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 and submit a Software Accomplishment Summary (SAS) IAW CDRL SS006 for each system to demonstrate compliance with the approved PSAA.

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

The Contractor must develop and submit a Software life cycle Environment Configuration Index (SECI) IAW CDRL SS008 for each system to identify the tools and environment used to build and test the approved software.

CDRL SS005 PSAA

CDRL SS006 SAS

CDRL SS007 SCI

CDRL SS008 SECI

2.6.3 Compliance Reviews

The Contractor must conduct Compliance Reviews with FAA participation to review the life cycle data items and ensure compliance with the applicable DAL objectives of SAE ARP 4754A, RTCA DO-278A and DO-254. The agendas, dates, and locations of the Compliance Reviews will be agreed upon by the Contractor and FAA. The FAA plans to retain the services of Designated Engineering Representatives (DERs) to ensure the process and life cycle data items meet the required objectives. A DER is an individual, appointed IAW 14 Code of Federal Regulations (CFR) section 183.29, Designated Engineering Representatives, who holds an engineering degree or equivalent, who possesses technical knowledge and experience, and meets the qualification requirements of FAA Order 8100.8D, Designee Management Handbook.

Once all issues/comments are successfully addressed as determined by the FAA, within 30 days the FAA will issue a letter of approval to the Contractor (1) stating what review was completed,

(2) listing life cycle data items reviewed and version of each data item where issues/comments were successfully addressed, (3) stating what objective evidence was produced to ensure each life cycle data item complies with the applicable design assurance objective(s), (4) giving decision on the approval of the data items, and (5) giving approval to move forward in the life cycle process or completion of the compliance package.

The Contractor must create and maintain a Master Data List (MDL) of life cycle data items for each system and associated HW and SW. The intent of the MDL is to track all program life cycle data items in one location. It is a living document and must be a workbook in Microsoft Excel format. The MDL must meet the following standards at a minimum:

• MDL must include:

13 | Page Draft Task Order

“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.”

o separate worksheets for each system, hardware component, and software component.

o Column headers: (System, Hardware, or Software) Life Cycle Data Items, Specific

Data Item Name, Configuration ID, and Current Version.

• The top of each worksheet will state the name and location of the company responsible for development of the system, HW component, or SW component.

• Each worksheet will contain applicable life cycle data items and their current revision statuses (e.g., DRAFT, NOT STARTED, Rev A).

The MDL must be available for review by the FAA during all Compliance Reviews.

The following Compliance Reviews of the system, SW, and HW life cycle data must be conducted to ensure compliance with the development assurance objectives:

a) Planning Review: To be conducted after initial planning process is complete. System compliance package should be reviewed first, prior to associated HW and SW compliance packages, in which the order will be determined by the Contractor and FAA.

b) Design/Development Readiness Review: To be completed when the requirements, design, code (if applicable), and integration are sufficiently complete. System, HW, and SW compliance packages may be reviewed in any order, as determined by the Contractor and FAA.

c) Verification Readiness Review: To be completed prior to verification, when the verification process is sufficiently complete and mature. System, HW, and SW compliance packages may be reviewed in any order, as determined by the Contractor and FAA.

d) Compliance Completion Review: To be conducted after completion of verification and the accomplishment summaries. System, HW, and SW compliance packages may be reviewed in any order, as determined by the Contractor and FAA.

2.7 ENVIRONMENTAL, OCCUPATIONAL SAFETY, AND HEALTH (EOSH)

The Contractor must develop EOSH plans describing their approach to protecting the environment and the safety and health of FAA or Contractor personnel in CDRL EO38 Personnel Safety Hazard Analysis Report. The EOSH plans must detail how the Contractor will apply EOSH principles, criteria, and techniques as part of a formalized process to assess, identify, and mitigate the potential for environmental impacts, property damage, and incidents that may cause harm to personnel.

CDRL EO38 Personnel Safety Hazard Analysis Report

2.8 TEST AND EVALUATION

The Contractor must develop, plan, conduct, and document a Development Test (DT) T&E Program IAW Section C of the IDIQ Contract and this Task Order, and IAW the following three FAA Performance Specifications: FAA-E-37016, Distance Measuring Equipment (DME) Transponder System; FAA-E-37012, Very High Frequency (VHF) Omnidirectional Radio Range (VOR) System – Conventional (CVOR) And Doppler (DVOR); and, FAA-E-7870, Tactical Air Navigation (TACAN) Ground Transponder System (hereinafter referred to as the “DVT Specifications”). The T&E Program must verify that each of the specified DVT Systems meet

14 | Page Draft Task Order

“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 physical, functional, interface, and performance requirements identified in the DVT Specifications, and the requirements of Section C of the IDIQ Contract and this Task Order.

The Contractor must conduct the DT activities described herein IAW FAA-approved plans and procedures. The Contractor must record and document all data relevant to verification of the requirements, and must perform any required data reduction, processing, and analysis. The Contractor must allow the FAA to witness all formal test conduct in person and via videoconference; inspect all test setup or test device; audit the configuration of the unit under test; and provide access to any data or information recorded during the test.

The Contractor must provide four sets of DVT First Article Systems, with each set containing:

one First Article DME system; one First Article CVOR system; one First Article DVOR system;

and one First Article TACAN system. IAW the Supply Support paragraphs of Task Order 3 of the IDIQ Contract, the Contractor must provide all site spares, expendable items, and consumable items for all of the First Article DVT Systems for the duration of the DVT T&E program, including the FAA’s Operational Test (OT) program.

The First Article DVT Systems must be used to verify that each system conforms to the DVT Specifications, and any additional Contract requirements. Three sets of First Article DVT Systems must be used for System Test; the fourth set of First Article DVT Systems will be used for vendor engineering support at the Contractor facility.

After the Contractor completes all required DT activities, the FAA will conduct OT using DVT First Article Systems at the FAA OT Site and OT Key Sites. The Contractor must deliver the following DVT First Article Systems for usage during FAA OT: three DME systems; two CVOR systems; two DVOR systems; and two TACAN systems.

The Contractor must repair or replace all failed components, failed LRUs, and failed subsystems for each of the DVT Systems throughout the DT and OT T&E Programs.

2.8.1 Test and Evaluation Management

The Contractor must develop and maintain a CMTP IAW CDRL E001 that describes the overall approach and management of the DVT T&E Program as described in Section C of the IDIQ Contract and this Task Order, including all reviews, tests, and demonstrations. The CMTP must include a regression testing section that addresses the approach and management of additional verification activities in response to a system failure, or in response to a modification of the system design or components after DT has started. The regression testing section must address the overall approach used to determine the retesting scope. The CMTP also must include provisions that, for each of the DVT Systems, address:

a) Individual test activities.

b) Test schedules.

c) Required resources.

d) Configuration management during testing.

e) Roles and responsibilities.

f) Test safety.

15 | Page Draft Task Order

“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.”

g) Program trouble reporting and resolution.

h) Contractor Verification Requirements Traceability Matrix (CVRTM).

The Contractor must assign a single DVT Test Manager with the responsibility and authority to manage all Contractor testing of all the DVT Systems.

The Contractor must conduct and manage DT by splitting the test program into two groups. The first test group must include all testing of the CVOR and DVOR systems. The second test group must include all testing of the DME and TACAN systems.

The Contractor must assign a single Test Lead to manage all DT testing of the CVOR and DVOR systems. The Contractor must assign a separate Test Lead to manage all DT testing of the DME and TACAN systems.

The Contractor’s DVT Test Manager must support FAA Operational Testing of all DVT Systems as described herein. The Contractor’s DVT Test Manager must inform the FAA at least 30 calendar days before all formal tests.

The Contractor must record and report test failures and anomalies for each of the DVT Systems using Program Trouble Reports (PTRs) as described in Section C of the IDIQ Contract and this Task Order.

2.8.1.1 Contractor Verification Requirements Traceability Matrix The Contractor must develop and maintain an individual CVRTM for each of the DVT Systems IAW CDRL E002, which includes:

a) All DVT system requirements in each of the DVT Specifications, and Section C of the IDIQ Contract and this Task Order.

b) All requirements cited as references in the requirements documents, and derived requirements identified via other CDRLs in Section C of the IDIQ Contract and this Task Order.

Each CVRTM must be updated to incorporate any Contract modifications or further refinement of Contractor-derived requirements.

CDRL E001 Contractor’s Master Test Plan CDRL E002 Contractor’s Verification Requirements Traceability Matrix

2.8.2 Development Test

The Contractor must conduct DT to verify that each of the DVT Systems meet all the physical, functional, interface, and performance requirements of the DVT Specifications, Section C of the IDIQ Contract, and this Task Order. DT must consist of:

a) System Test.

b) Production Acceptance Test.

c) Type Test.

d) Regression Test.

16 | Page Draft Task Order

“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.”

e) Site Acceptance Test.

All test activities must be conducted at the Contractor’s facilities or FAA-approved test facilities.

2.8.2.1 System Test

The Contractor must conduct System Test to verify that each of the completely assembled and functioning DVT Systems meet the allocated requirements from the DVT Specifications, Section C of the IDIQ Contract, and this Task Order. System Test must consist of:

a) Qualification Test.

b) Reliability Demonstration.

c) Maintainability Demonstration.

d) Fail-Safe Demonstration.

Three sets of First Article DVT Systems must be used for System Test. Two of those sets of First Article DVT Systems must be used for Qualification Test, and those same two sets of First Article DVT Systems must be used for the Reliability Demonstration. The third set of First Article DVT Systems must be used for the Maintainability and Fail-Safe Demonstrations.

2.8.2.1.1 Qualification Test

The Contractor must conduct Qualification Test on each of the DVT Systems to verify the performance of each system meets the requirements in the DVT Specifications, Section C of the IDIQ Contract, and this Task Order. The Contractor must conduct Qualification Test to verify requirements for environmental conditions, electrical power, signal-in-space performance, Electromagnetic Compatibility (EMC)/Electromagnetic Interference (EMI), human factors, system functionality, and security.

One of the two sets of First Article DVT Systems used in Qualification Test must be used to verify all environmental requirements, electrical power requirements, and signal-in-space requirements. The signal-in-space requirements must be tested after the electrical and environmental tests are complete. The second set of First Article DVT Systems used for Qualification Test must be used to verify the EMC/EMI, human factors, system functional requirements, and security.

The Contractor must develop a Qualification Test Plan (CDRL E009) for each of the DVT Systems that addresses:

a) Test description.

b) Test approach.

c) Test management.

d) Requirements under evaluation.

e) Test activity sequence.

f) Logistical constraints.

g) Roles and responsibilities.

h) Resources, including test equipment and third-party test facilities.

i) Test entrance and exit criteria.

17 | Page Draft Task Order

“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 Contractor must develop Qualification Test Procedures (CDRL E010) for each of the DVT Systems that details the test setup for each system, identifies all requirements being verified, and includes step-by-step instructions with pass/fail criteria for each requirement.

The Contractor must develop the Qualification Test Report (CDRL E011) for each of the DVT Systems that summarizes results of all tests, describes the test activities as conducted, identifies all PTRs opened during the test and other test anomalies, and reports the pass/fail status of each requirement.

CDRL E009 Qualification Test Plan CDRL E010 Qualification Test Procedures CDRL E011 Qualification Test Report

2.8.2.1.2 Reliability Analysis and Demonstration

The Contractor must perform a serial reliability analysis (CDRL E012) that verifies that each of the DVT Systems meet the Mean Time Between Failures requirements from the DVT Specifications. The Contractor’s reliability analysis must be IAW Department of Defense Handbook Reliability Prediction of Electronic Equipment, MIL-HDBK-217F, Notice 2.

The Contractor must also conduct a Reliability Demonstration on each of the DVT Systems to support verification of the reliability-related requirements. The Contractor must conduct the demonstration using the same two sets of First Article DVT Systems that underwent Qualification Test. Each Reliability Demonstration must be conducted in a sealed environmental chamber. The chamber must be sealed at the start of the demonstration to prevent unauthorized access.

The demonstration must be divided into three phases using the following duration, temperature, and humidity profiles developed IAW MIL-STD-810H:

2.8.2.1.2.1 DME and TACAN

1. Hot Temperature Phase: The starting temperature of 23°C ±2°C must be maintained for

12 hours and then increase to 50°C ±5°C over 2 hours. The 50°C temperature must be maintained for 925 hours. The temperature must then decrease to 23°C ±2°C over 2 hours and must be maintained for 12 hours. The humidity in the chamber must be maintained at a constant relative humidity of 54% ±5% for the duration of the Hot Temperature Phase.

2. Middle Temperature Phase: The temperature of 23°C ±2°C must be maintained for 1848 hours. The humidity in the chamber must be maintained at a constant relative humidity of 50% ±5%.

3. Cold Temperature Phase: The starting temperature of 23°C ±2°C must be maintained for 12 hours and then decrease to -10°C ±5°C over 2 hours. The -10°C temperature must be maintained for 925 hours. The temperature must then increase to 23°C ±2°C over 2 hours and must be maintained for 12 hours. The humidity in the chamber must be maintained at a constant relative humidity of 10% ±5%.

18 | Page Draft Task Order

“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.”

2.8.2.1.2.2 Conventional VOR

1. Hot Temperature Phase: The starting temperature of 23°C ±2°C must be maintained for

12 hours and then increase to 50°C ±5°C over 2 hours. The 50°C temperature must be maintained for 781 hours. The temperature must then decrease to 23°C ±2°C over 2 hours and must be maintained for 12 hours. The humidity in the chamber must be maintained at a constant relative humidity of 54% ±5% for the duration of the Hot Temperature Phase.

2. Middle Temperature Phase: The temperature of 23°C ±2°C must be maintained for 1559 hours. The humidity in the chamber must be maintained at a constant relative humidity of 50% ±5%.

3. Cold Temperature Phase: The starting temperature of 23°C ±2°C must be maintained for 12 hours and then decrease to -10°C ±5°C over 2 hours. The -10°C temperature must be maintained for 781 hours. The temperature must then increase to 23°C ±2°C over 2 hours and must be maintained for 12 hours. The humidity in the chamber must be maintained at a constant relative humidity of 10% ±5%.

2.8.2.1.2.3 Doppler VOR

1. Hot Temperature Phase: The starting temperature of 23°C ±2°C must be maintained for

12 hours and then increase to 50°C ±5°C over 2 hours. The 50°C temperature must be maintained for 666 hours. The temperature must then decrease to 23°C ±2°C over 2 hours and must be maintained for 12 hours. The humidity in the chamber must be maintained at a constant relative humidity of 54% ±5% for the duration of the Hot Temperature Phase.

2. Middle Temperature Phase: The temperature of 23°C ±2°C must be…