DNTS SIR Sect C_Amend 1.pdf

Dedicated Network Telecommunications System (DNTS) SIR # 693KA8-24-R-00007

PART I – SECTION C

STATEMENT OF WORK

TABLE OF CONTENTS

C.1. INRODUCTION

OVERVIEW OF TECHNICAL SOLUTION

PURPOSE

SCOPE

C.2. APPLICABLE DOCUMENTS

C.3. REQUIREMENTS

PROGRAM MANAGEMENT

DNTS Program Manager

Program Management Plan Integrated Master Schedule

Quality Control / Quality Assurance Program Reporting Meetings/Events/Conferences

CONFIGURATION MANAGEMENT

DNTS Configuration Management Lead

General Configuration Management Requirements

Configuration Management Plan

Configuration Identification Documentation Management

Product Baseline Configuration Control Configuration Status Accounting

Configuration Audits General Requirements for Configuration Audits

Functional Configuration Audit (FCA) Physical Configuration Audit (PCA)

INTEGRATED LOGISTICS SUPPORT (ILS)

DNTS ILS Manager

Integrated Logistics Support Program Integrated Support Plan Logistics Guidance Conference Logistics Management Information (LMI)

Provisioning Conference

Final Breakdown Structure Tools and Test Equipment (T&TE) List Repairs

Non-Warranty Repair Monthly Repair Status Reports

Technical Instruction Books (TIB) Diminishing Manufacturing Sources and Material Shortages (DMSMS)

Training DNTS Training Lead Environmental Occupational Safety and Health (EOSH) Training Deliverables (General) Personnel Qualification Report

Commercial Off-the-Shelf (COTS) Training Materials Training Development Plan (TDP) Task and Skills Analysis (TASA) Report Course Design Guide (CDG)

Student Achievement Tests Web Based Training (WBT) Theory of Operations and Maintenance Course

Instructor Led Training (ILT) Lab Course Course Walk-through (CWT) – Contractor’s Presentation

Operational Tryout (OTO) First Course Conduct (FCC)

BAR CODE AND ASSET TRACKING SYSTEM

Identification Markings Warranty Markings

Electrostatic Discharge (ESD) Sensitive Devices Individual Item Marking Requirements for LRU Human Readable Interpretation (HRI)

Applying Identification Bar Codes on Containers

Production, Warranty, and Repair Data Requirements FAA Scanning Process FAA Scanning Process Steps

FAA Scanning Process Pilot Run Pilot Run Definition

Criteria for a Successful Pilot Run

TESTING

DNTS Test Manager Contractor Master Test Plan

Contractor Verification Requirements Traceability Matrix Test Tool Accreditation

Program Trouble Report (PTR) Processing Factory Acceptance Test (FAT)

FAT Plan

FAT Procedures Test Readiness Review FAT Report

FAA Operational Test (OT) OT Equipment DNTS Product Familiarization OT and FF Technical Support Services

Production Acceptance Test PAT Plan

PAT Procedures PAT Report

Production Unit Test (PUT) PUT Plan PUT Procedures

PUT Report

SUPPORT SERVICES

Telephone and Online Support Services Technical Support Services (ordered by Task Order)

SOFTWARE AND EQUIPMENT

Equipment and Software Documentation

Software

C.1. INRODUCTION

The FAA Airport Cable Loop (ACL) Systems - Sustained Support (ACLSSS) Program is responsible for continually monitoring, managing, and/or replacing FAA’s on-airport cable systems, with a strategic mission to provide increased capacity and availability. On-airport ACL systems are FAA-owned and managed signal/control cable lines and equipment that transport information between airport traffic control towers (ATCT) and other FAA on-airport facilities.

This information includes essential and critical services such as radar and weather data, air-to-ground voice communication, navigational aid control and monitoring from the ATCT; as well as non-essential information such as administrative traffic and email.

The “Dedicated Network Telecommunications System” (DNTS) equipment obtained through this procurement will replace the aging legacy communications equipment most of which is deteriorating and no longer manufacturer-supported or produced.

OVERVIEW OF TECHNICAL SOLUTION

The ACLSS program will install fiber-optic cable in a ring formation to provide redundancy and telecommunications diversity. In the unlikely event that a break occurs in the cable, the ring configuration enables data to travel in the opposite direction thereby preventing a communications failure while the break is being located and repaired. Through this program; system performance, reliability, and safety are enhanced by the redundant data paths created by using a ring configuration for airport cable loops. Standardizing installation configurations and fiber optic equipment through a DNTS contract will simplify life-cycle management.

Airport Cable Loop System capabilities include:

• Transporting information such as radar, weather data, Air/Ground (A/G) communication, navigational aid control and monitoring between the air traffic control towers (ATCT) and other on-airport FAA facilities

• Future proofing by providing both legacy Time Division Multiplexed (TDM) and Ethernet services for a seamless transition

• Providing interface for external access FAA Telecommunication Infrastructure / FAA

Enterprise Network Services (FTI/FENS) when required

PURPOSE

The purpose of the Statement of Work (SOW) is to define the efforts required to deliver

Commercial-Off-The Shelf (COTS) fiber optics multiplexer equipment that meets all requirements in the Federal Aviation Administration (FAA) Synchronous Optical Network (SONET) Dedicated

Network Telecommunications System (DNTS) Specification (FAA-P-2978) for the Airport Cable

Loop (ACL) Program.

SCOPE

The Contractor must provide all necessary resources, equipment, engineering, logistics support, maintenance/operator training, spares provisioning and maintenance program, and the documentation for implementation, maintenance, and operation of the Dedicated Networks

Telecommunications System (DNTS).

C.2. APPLICABLE DOCUMENTS

The Contractor must ensure all work is in full compliance with regulations expressed in the following procedures, orders, and programs unless otherwise directed by the Contracting Officer’s

Representative (COR). In the event of a conflict between this SOW and any of the applicable documents cited within, the requirements of the SOW take precedence.

In providing the Dedicated Networks Telecommunications System required under this contract, the Contractor must comply with the applicable FAA orders, directives, and policies listed below.

The Contractor is responsible for reviewing all applicable documents and understanding their impact on the delivery of the required services. Applicable documents are subject to revision, and it is the Contractor’s responsibility to ensure that the most current version of each document is used and that new applicable documents are adopted, as required.

DOCUMENT

NUMBER

DOCUMENT TITLE

N/A FAA Asset Identification Process and Procedure Guide

N/A Categories of eLearning Technology and their Impact on Performance and

Proficiency.

N/A FAA eLMS Content Integration Guide.

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

Equipment, Requirements for Preparation of Manuscript and Production of

Books

FAA-Order

3000.22

Air Traffic Organization Outcomes-Based Technical Training

FAA-Order

JO 3000.57

Air Traffic Organization Technical Operations Training and Personnel

Certification

FAA-Order

6000.15

General Maintenance Handbook for National Airspace System (NAS) Facilities

FAA-P-2978 Dedicated Networks telecommunications System (DNTS) Product Description

FAA-STD-

Configuration Management

FED-STD-05 Standard Guides for Preparation of Proposed Item Logistics Data Records

GEIA-STD-

0007-A

Logistics Product Data Handbook (SAE)

C.3. REQUIREMENTS

The Contractor must furnish the necessary personnel, equipment, facilities, materials, and other necessary resources to produce, test, and deliver the items as described in the SOW. All such items must be supplied in conformance with the terms and conditions of this SOW and the complete contract, including references. The contractor must perform the terms of this contract under the technical direction of the Contracting Officer’s Representative (COR). Performance must be .in accordance with individual Task/Delivery Orders and contractor must be solely responsible for the management of its subcontracts.

The Contractor must ensure all Contract Data Requirement Lists (CDRLs) are submitted in accordance with each of the CDRL requirements (frequency, data of first submission, etc.) and each CDRL’s associated Data Item Deliverable (DID) requirements as specified in Attachment J-

2 – DNTS CDRLs and DIDs.

The Contractor must also work with the FAA in partnership to achieve a DNTS In-Service

Decision (ISD) so that all FAA-required equipment, testing, training, and logistics requirements are met. The In-Service Decision (ISD) authorizes deployment of a solution into the operational environment. No Production equipment will be ordered until ISD is achieved. See Attachment

J-4 for DNTS ISD checkpoints.

PROGRAM MANAGEMENT

The Contractor must provide the required personnel and facilities to manage and administer the work required under the contract. This contract requires program management, planning, testing and testing management, configuration management, logistics planning and logistics management, quality assurance, scheduling, and coordination activities. These activities include the internal and external management activities necessary for basic contract performance, reporting progress, managing risk, demonstrating results, and coordinating technical activities with the FAA.

DNTS Program Manager

The Contractor must assign a Program Manager (PM), who has overall responsibility for controlling and coordinating all work to be performed under this contract. The PM must have the resources and the authority to ensure program execution and must be the single focal point within the Contractor’s activity for all contract requirements, to include oversight over all other functional area leads and/or focal points identified in the contract requirements. The PM must serve as the single focal point for all required Contractor and subcontractor activities.

If subcontractors (including teaming partners) are used, the Contractor must be responsible for ensuring that all requirements are fulfilled for subcontracted items.

Program Management Plan

The Contractor must develop, deliver, and maintain a Program Management Plan (PMP) to describe the Contractor's methods for managing, executing, and controlling this contract. The

Contractor must prepare and submit a draft version of the PMP and its addendums with the agenda for the Post Award Conference (PAC).

Deliverable CDRL

Project Management Plan (PMP) including a Contract

Work Breakdown Structure

A001

The Contractor must include a Contract Work Breakdown Structure (CWBS) in the PMP as well as the following PMP addendums:

PMP Addendum CDRL SOW Ref

Quality Systems Plan A003 C.3.1.4

Configuration Management Plan A004 C.3.2.3

Integrated Support Plan L001 C.3.3.3

Integrated Master Schedule

The Contractor must develop, deliver, and maintain an Integrated Master Schedule (IMS), consistent with the Contract Work Breakdown Structure (CWBS) defined in the PMP.

The Contractor must prepare and submit a draft version of the IMS with the agenda for the Post

Award Conference (PAC).

Integrated Master Schedule (IMS) A002

The CWBS relationship, for each activity, must be identified. However, a Microsoft Project user-defined field (e.g., Text1) can be used for this purpose. The Contractor must manage the execution of the contract using the IMS as the day-to-day planning and execution tool, and to assess program progress in meeting program requirements. The Contractor must report on program progress consistent with the IMS at each program management review and at the COR’s request. The Contractor must revise the IMS, when necessary, to reflect current and changing contract milestones and deliverables. The IMS must include all activities and dependencies of the prime contractor, subcontractor and interrelated Government activities (e.g., Operational Test).

All contractor schedule information delivered to the Government or presented at program reviews must originate from the IMS. To manage schedule risks, the Contractor must perform appropriate analyses of all IMS tasks, report potential or existing problem areas, and recommend corrective actions to eliminate or reduce schedule impact to the program.

Quality Control / Quality Assurance

The Contractor must have quality control over all aspects of this contract, including the production process and work by its subcontractors and vendors.

In accordance with Section E (Inspection and Acceptance, AMS Clause 3.10.4-2) of the contract, the Contractor must develop, deliver, and maintain a Quality System Plan (QSP) that describes the quality systems and processes that will be used to measure and ensure the quality of services and products. The Contractor must review and update the approved QSP upon any changes to the contract (e.g., additional duties, staffing changes, new quality assurance measures) or when directed by the COR. The Government reserves the right to either reject or to require correction of nonconforming supplies in accordance with AMS clause 3.10.4-2, Inspection of Supplies - Fixed

Price

Quality System Plan (QSP) A003

Program Reporting

The Contractor must monitor and report on all performance under this contract, including the performance of its subcontractors and major suppliers, by identifying appropriate program measures to monitor the program’s cost, schedule, and technical objectives.

The Contractor must prepare and submit a Monthly Program Status Report (MPSR) that provides the status of all contract milestones, actions, issues, and risks based on the deliverables identified in this Contract. The Contractor must provide a MPSR that documents the activities of the previous reporting period and identifies planned activities for the following reporting period. The Contractor must ensure that report data is maintained for the life of the contract and that no entry is deleted without Government approval. The Contractor must include a summary of medium and high risks as part of the Monthly Program Status Report. If corrective measures are required as a result of factory acceptance or other testing or from configuration audits, the Contractor must include the status of these corrective actions as an addendum to the Monthly Program Status Report.

Monthly Program Status Report (MPSR) A009

Meetings/Events/Conferences

Unless otherwise directed by the Government, the Contractor must host all required meetings, events, and conferences at the Contractor’s facility within the 48 contiguous states. The Contractor provided facility must adequately accommodate a government team of no more than twenty-five

(25) representatives. If a meeting is to be held virtually, the Contractor must provide a mutually agreed upon virtual conferencing platform.

The Contractor must prepare and deliver to the Government an agenda prior to each conference and meeting. The Contractor must record, prepare, and deliver meeting/event/conference minutes subsequent to each scheduled conference and meeting. In addition to the standard agenda and minute requirements specified in the CDRL and Data Item Deliverable, the Contractor must provide other additional materials as specified in the Statement of Work section for that meeting, conference, or event.

Contractor administrative support must be provided when meetings or conferences are held at a contractor or subcontractor facility. Such support may consist of providing facility access requirements, office equipment, and clerical support.

The Contractor must ensure participation of required Contractor and subcontractor personnel to answer the Government’s technical and contractual questions.

Meeting Agenda A007

Meeting Minutes A008

The Contractor must host and administratively support the following meetings/events/conferences at the Contractor’s or Sub-contractor’s facility within the 48 contiguous states:

a) Post Award Conference (PAC). The Contractor must plan, host, and participate in a PAC following contract award. The Government will determine the actual date of the PAC, which will occur no later than 30 calendar days after the contract award date. The PAC is held to achieve a clear and mutual understanding of all contract requirements. The PAC is not a substitute for the Contractor fully understanding the work requirements at the time an offer is submitted, nor is it to be used to alter the contract terms and conditions. The

PAC agenda is set by the Contactor but approved by the FAA. During the PAC, the

Contractor must brief the plans and schedule for satisfying each SOW requirement and provide a list of all the COTS documentation that will be delivered with the software and equipment. The Contractor must include the finalized list of the COTS documentation as part of the PAC meeting minutes.

The Contractor must ensure PAC participants include all Contract key personnel, subcontractor representatives, and any administrative support personnel required to facilitate the meeting.

b) Logistics Guidance Conference (LGC). The LGC will take place as part of the PAC

C.3.3.4. Included in the LGC are the Provisioning Guidance Conference (PGC) and the

Training Guidance Conference (TGC).

c) Factory Acceptance Test. Specific requirements for FAT are described in Section

C.3.4.3

d) Functional Configuration Audit (FCA). Specific requirements for the FCA are described in Section C.3.2.9.2.

e) Physical Configuration Audit (PCA). Specific requirements for the PCA are described in Section C.3.2.9.3.

f) Provisioning Conference. Specific requirements for the Provisioning Conference are described in Section C.3.3.5.1.

g) Program Management Reviews (PMRs). During the PMRs, the Contractor must report program status regarding all deliverables, schedule, cost, and performance including the status of all open issues, actions, and risk. The Government anticipates ordering at least two PMRs per year prior to In-Service Decision to ensure In-Service Review milestones are on schedule.

CONFIGURATION MANAGEMENT

DNTS Configuration Management Lead

The Contractor must appoint a DNTS Configuration Management Lead to serve as the primary point of contact for all configuration management functions. The Configuration Management Lead must meet the requirements specified in Section H Clause 3.8.2-17 Key Personnel and Facilities.

General Configuration Management Requirements

The Contractor must have configuration management control over all contract deliverables including the production process. The Contractor must ensure configuration management control encompasses all DNTS hardware, software, firmware, documentation, test and support equipment, training/courseware, and manuals delivered in the contract. The Contractor must have sufficient visibility and control of deliverables to ensure only Government-approved changes to the product baseline will be required for the entire contract term.

The Contractor must maintain configuration control over work performed by its subcontractors and vendors to include, but not limited to, configuration identification (hardware, software, and documentation), establishment and control of configuration baselines (Functional Configuration

Audit and Physical Configuration Audit), configuration status accounting, and audits.

Configuration Management Plan

The Contractor must develop, deliver, and maintain a Configuration Management Plan (CMP) that is integrated into the PMP. Within the CMP, the Contractor must describe its configuration control process and supporting systems. The Contractor must implement and maintain a Configuration

Management Program for all DNTS hardware, software, and documentation throughout the life of the contract in accordance with the approved Configuration Management Plan.

Configuration Management Plan (CMP) A004

Configuration Identification

The Contractor must maintain a system to identify, bar code, label, serialize, and mark Hardware

Configuration Items (HWCI) and Software Configuration Items (SWCI) to provide traceability from delivery of the first FAA production unit to the final unit delivered under this contract. The identification process of HWCI and SWCI must be detailed in the Configuration Management

Plan.

Documentation Management

The Contractor must deliver and manage all documentation delivered under this contract to include all HWCI and SWCI documentation as well as all data items (e.g., CDRLs) delivered under the contract such as test procedures, meeting minutes, lists, training course materials, etc. The

Contractor must manage the documentation in accordance with the Configuration Management

Plan.

The Contractor must identify by titling, labeling, numbering, identifying publication date, identifying originator (e.g., the Original Equipment Manufacturer (OEM) by name) of the documentation, and cataloging all documentation. The procedures used must accomplish the following:

a) Identify the specific version of HWCI, and/or SWCI to which a document applies; and,

b) Uniquely identify the document number, edition, date, change status, and other identification details of each document.

Product Baseline

The Contractor must maintain the Product Baseline after successful completion of the Factory

Acceptance Test (FAT), described in Section C.3.5.3, Functional Configuration Audit (FCA), described in Section C.3.2.9.2, and the Physical Configuration Audit (PCA), defined in Section

C.3.2.9.3. The Product Baseline is established prior to Production Acceptance Testing (PAT), described in Section C.3.4.5.

The software/firmware versions and components comprising the Lowest Replaceable Unit (LRU) must form the basis of the Product Baseline identified in the Final Breakdown Structure, described in Section C.3.3.6. A LRU is the lowest level subassembly that can be replaced during site level maintenance activities. The Government will review for approval the results of FAT, FCA, and the PCA for the establishment of the Product Baseline. The Product Baseline results in the identification of an established Government accepted baseline of hardware and software versions.

The Configuration Status Accounting Report (CSAR), described in Section C.3.2.8, must be part of the Product Baseline documents submitted for review and is the mechanism for tracking changes to the Product Baseline.

Configuration Status Accounting Report (CSAR) A006

Configuration Control

The Contractor must ensure configuration control encompasses all hardware, software, and documentation. The Contractor must maintain an internal Configuration Control Board (CCB) to support baseline management of the Product Baseline. The Contractor must maintain traceability, currency of the baselines, and consistency among all project documentation, hardware, and software.

Changes generated by the Contractor after the Product Baseline has been established, which provide the same form, fit and function, will not require formal approval by the Government. This type of change, known as a Class II change, must be determined in concert with the Government.

All changes that affect any of the Product Baseline documents or the Logistics Management

Information (LMI) will require Government approval. Any such changes, known as Class I changes, must be submitted to the Contracting Officer as Engineering Change Proposals (ECPs).

An accepted Class I change may require successful Contractor re-performance of Factory

Acceptance Test (FAT) as described in Section C.3.4.3. Class I and Class II changes are defined in FAA-STD-021A paragraphs 80.4.1.and 80.4.2.

Engineering Change Proposal (ECP) A005

The Contractor must submit the proposed changes prior to implementing any changes into the system design. FAA configuration control over system functional performance will be in effect from formal approval of the FCA. FAA configuration control over the physical form, fit, and function will be in effect from the formal PCA approval until the warranty expiration of the ultimate units delivered IAW this contract.

Configuration Status Accounting

The Contractor must generate Configuration Status Accounting Reports (CSAR), to document changes to the Product Baseline. The CSAR identifies the configuration items, status of changes, and provides the supporting documentation reflecting these changes. The CSAR must provide traceability of any change through the change control process. The first submission of the CSAR must be generated for the Product Baseline as part of establishing the baseline.

Configuration Status Accounting Reports (CSAR) A006

Configuration Audits

General Requirements for Configuration Audits

The Contractor must host a Functional Configuration Audit (FCA) and a Physical Configuration

Audit (PCA) at the Contractor's facility. The Contractor must ensure that these audits include all hardware, firmware, software, and documentation. The Contractor must submit the audit reports

(IAW with Section 10 of the Government-approved Configuration Management Plan) describing conduct and results of each audit as an attachment to the meeting minutes for the audits. The report must catalog any discovered deficiencies and provide conclusions and recommendations as well as planned corrective actions. The Government will disapprove the audit if identification of major discrepancies for example, but not limited to, unbaselined (missed requirement traceability) specifications, invalid or unverified requirements and uncorrected test failures are found. The

Government will indicate whether the audit is approved without conditions, approved with contingencies, or disapproved. Production orders will not be placed until all deficiencies are resolved and the audits are approved by the Government. The Government will not schedule audits until the prerequisite material or contract requirement is successfully completed.

Functional Configuration Audit (FCA)

The purpose of the FCA is to ensure that the system meets the functional performance requirements defined in the Product Specification (FAA-P-2978). The Government will review the FAT results prior to conducting the FCA. FCA must be conducted within 60 calendar days after the successful completion of the Factory Acceptance Test (FAT) and acceptance of the FAT Report, described in Section C.3.4.3.4. The FCA is one of several meeting types outlined in Section C.3.1.6.

Production orders will not be placed until the Government has approved the Contractor’s proposed corrective actions for any unresolved FCA deficiencies.

Physical Configuration Audit (PCA)

The purpose of the PCA is: 1) to review top level design documentation for each LRU to validate that the Contractor has adequate engineering drawings to continue production of the hardware, software, and documentation; and 2) to identify the baselined physical characteristics of the various devices and control changes (for FAA support purposes). The Physical Configuration

Audit (PCA) Baseline is established at the external perimeter of the primary LRUs, and includes all appurtenances, appliances, ancillary equipment, etc. that are part of the delivered device and/or that may be replaced for support purposes. The overall objective of this baselining is to permit reliable configuration control by the FAA over the deployed equipment while avoiding unnecessary Government involvement in internal system design.

The Physical Configuration Audit (PCA) must be conducted no more than 60 days after the successful completion of FCA, described in Section C.3.2.9.2, on the equipment that passed the

FAT. The Contractor must provide technically competent personnel to disassemble the equipment as necessary, and to respond to Government queries during the PCA.

Prior to conducting the PCA, the Contractor must resolve all action items assigned at FCA and provide documentary evidence of the resolution. The Government will not place production orders until all proposed corrective actions are approved. The PCA is one of several meeting types outlined in Section C.3.1.6.

INTEGRATED LOGISTICS SUPPORT (ILS)

DNTS ILS Manager

The Contractor must appoint a DNTS ILS Manager, who serves as the primary point of contact for all logistics issues. The DNTS ILS Manager must meet the requirements specified in Section

H Clause 3.8.2-17 Key Personnel and Facilities.

Integrated Logistics Support Program

The Contractor must establish and maintain an Integrated Logistics Support (ILS) Program IAW the requirements contained herein.

The Contractor must conduct ILS meetings to resolve logistics-related problems. Meeting support must include formulation/submission of agenda items, reports of the Contractor’s Integrated

Logistics Support work, administrative support, and attendance by Contractor personnel

Unless otherwise agreed to by the Government, ILS meetings must be held in conjunction with each Program Management Review.

The Contractor must submit specific ILS meeting agenda topics and ensure participation (e.g., status briefings) of the Contractor/subcontractor personnel responsible for the ILS agenda topics.

The Government will determine whether the Contractor’s subcontractor participation in scheduled meetings is required.

Integrated Support Plan

As ordered by the Government, the Contractor must deliver an Integrated Support Plan (ISP) that details the Contractor’s plan for managing the ILS program for the program life cycle. The ISP will include the Contractor’s Logistics Management Information Data Products as described in

Section C.3.3.5. The Contractor must be responsible for ensuring that all subcontractors and vendors comply with the ISP requirements.

Integrated Support Plan L001

Logistics Guidance Conference

As part of the Post Award Conference described in C.3.1.6, the Contractor must host a Logistics

Guidance Conference (LGC). The purpose of the LGC is to ensure the Contractor understands all

Integrated Logistics Support tasks. Included in the LGC will be a Provisioning Guidance

Conference (PGC) and a Training Guidance Conference (TGC). The purpose of the PGC is to ensure contractors’ understanding of the provisioning requirements. The purpose of the TGC is to ensure contractors’ understanding of the training requirements. The Contractor must ensure the participation of appropriate Contractor/subcontractor personnel responsible for preparing the logistics deliverables specified in the contract.

Logistics Management Information (LMI)

The Contractor must prepare, maintain and submit to the Government the LMI Data Products deliverable. The Contractor must ensure that the LMI data products represent the physical top-down breakdown system design configuration including systems, subsystems, components, assemblies, subassemblies, cables and cable assemblies, support and test equipment, and training equipment required for the DNTS. Data submitted must be to the component level for all developmental items and to the LRU level for all commercial off-the-shelf (COTS) and non-developmental items. Any modification to a COTS item may disqualify it as COTS and may require LMI data to the component level. The Government will determine the level of LMI data required for COTS modified items. The Contractor must identify system LRUs (e.g., printed circuit boards, modules, disk drives, cables and cable assemblies, power supplies, etc.) during the

LMI/Provisioning process. All items must be listed in the LMI submissions in the proper top down break down format. The Contractor must update the LMI during the Government’s Functional and Physical Configuration Audits (FCA/PCA) and during the Provisioning Conference (PC) as required.

The Contractor must make maximum use of previously collected and analyzed data, and documentation prepared for COTS hardware and software components whenever possible.

Modified COTS items must be explicitly identified as modified COTS in the LMI.

The Contractor must adhere to the data definitions, edits, and data formats as described in

Appendix B of GEIA-STD-0007-C.

As required by the COR, the Contractor may be requested to present LMI Data Products for review at program reviews, logistics reviews/meetings or via electronic means.”

Logistics Management Information Data Products L002

Provisioning Conference

The Contractor must host and support a Provisioning Conference(s) no later than 60 calendar days after Government receipt of the initial LMI data. The Conference must be held at the Contractor’s facility unless otherwise specified by the Government. The Contractor must ensure the participation of DNTS knowledgeable contractor/subcontractor personnel.

During the Provisioning Conference, the Contractor must:

a) Ensure all DNTS Government-approved drawings (e.g., approved during a physical configuration audit) are available for Government to use as references. The Government will not copy or remove any proprietary data from the Contractor’s facility unless the

Contractor is required to submit such data as part of other contractual submissions.

b) Provide copies of the Government-approved FCA/PCA documentation available for use as a reference.

c) Provide, for Government examination for the duration of the conference, samples of all systems, assemblies, and parts listed in the approved Product Baseline.

d) Ensure the participation of contractor personnel with detailed knowledge of the subject matter they represent (e.g., provisioning, provisioning and technical documentation, hardware/software maintenance, engineering and system design).

At any time during the term of the contract or any extension thereof, the Government reserves the right to order additional Provisioning Conferences and updates to LMI data that may be required to support the Provisioning Conference.

Final Breakdown Structure

The Contractor must prepare, maintain, and deliver a top-down Final Breakdown Structure (FBS) to the LRU level on all hardware, The Contractor must deliver the preliminary FBS after successful completion of FAT and prior to the PCA. The Final Breakdown Structure is developed by sequencing all parts comprising the end item in a lateral and descending family tree/generation breakdown. This breakdown must consist of the end item, including all components, listing every assembly, subassembly, and parts, which can be disassembled, reassembled/replaced. All parts are listed in relation to the end item, component, assembly, or installation system in which they are contained and to their own further sub-subassemblies and parts. This relationship is shown by means of an indenture code. The Final Breakdown Structure shows the relationship of all items to one another. The Contractor must update the breakdown structure during the Government’s audits

(FCA and combined PCA/Provisioning Conference). After the PCA, the Contractor must deliver the Final Breakdown Structure to the Government for approval.

Final Breakdown Structure (FBS) L003

Tools and Test Equipment (T&TE) List

As ordered by the Government, the Contractor must prepare and deliver to the Government a Tools and Test Equipment (T&TE) List to identify items that may be used for maintenance of the DNTS.

The Contractor must ensure:

• The T&TE List identifies both common and special items, that are not an integral part of the DNTS but are required to inspect, test, calibrate, service, and repair DNTS;

• The T&TE List identifies the tools and test equipment required to perform authorized site maintenance tasks (e.g., fault isolation and replacement to the LRU level); and

• The T&TE is consistent with the names used in DNTS technical documentation and training course materials, e.g., the Technical Instruction Book, course design guide, etc.

Tools and Test Equipment (T&TE) List L004

Repairs

The Contractor must have the capability and expertise necessary to repair all repairable items and components.

For all repairable items and/or LRU(s), the Contractor must furnish repair services in accordance with the provisions of: 1) this Section (C.3.3.8 inclusive of sub-sections), 2) Section H.3, Warranty, and 3) Attachment J-5 Contractor DNTS Warranty Terms. In the event of a conflict between the J-5 Contractor Warranty Terms and Contract Sections C.3.3.8 or H.3, the requirements in C.3.3.8 and H.3 take precedence.

The Contractor must furnish all qualified labor, supervision, materials, equipment, tools, appliances, and services to repair components of the equipment. The FAA Logistics Center

(FAALC) will manage and store exchange and repair (E&R) spares to support sites.

Repairable items and components will be shipped to the Contractor facility for repair directly from the FAA Logistics Center (FAALC). The FAALC Item Manager will furnish shipping instructions for repaired items. Unless otherwise directed by the Government, the Contractor must ship the repaired LRU to the FAALC in Oklahoma City, OK.

The Contractor must follow the repair requirements identified herein.

a) Contractor repair procedures must include the following:

1) Cleaning, visual inspection, bench tests, and fault isolation;

2) Disassembly as necessary to identify and accomplish required repairs or to establish the item as serviceable;

3) Reassembly, calibration, functionality testing, acceptance inspection, and preparation for shipment.

4) All repaired LRUs must successfully pass Production Unit Testing (PUT), as described in C.3.4.6, prior to being returned to the Government.

5) The Contractor must integrate repair process activity into the bar code scanning activities IAW C.3.6 and must include such data in accordance with the bar code scanning reporting requirements in C.3.6.4 for the life of the contract.

b) The Contractor must conduct all repairs in accordance with the Contractor’s established shop methods and procedures developed for the equipment.

c) When the Contractor determines that an item is beyond the Contractor’s ability to repair or the cost to replace the item is less than the repair cost, the Contractor must promptly notify the FAA Contracting Officer or designated representative and submit a rationale for that determination IAW Section C.3.3.8.1. If the FAA Contracting Officer or designated representative agrees that an item cannot be repaired, since the non-repairable item is

Government property, the FAA Contracting Officer or designated representative will provide disposition instructions for the item to the Contractor and may request a replacement in lieu of repair.

d) The Contractor must complete any Government approved modification to items (e.g., firmware updates, etc.) delivered under the contract and not previously accomplished at the time of repair. Each modified item or LRU must meet form, fit, and function of the item that it replaces and be two-way interchangeable, i.e., unmodified items must operate in place of modified items. Modified items must operate in place of unmodified items.

e) The Contractor must be responsible for the initial lay-in of piece parts and for obtaining replenishment units and spare piece parts required for use in the repair of failed items.

These parts must remain the property of the Contractor until incorporated into the repaired items at which time they become Government property. All parts removed during any repair become the property of the Contractor.

f) Upon receipt of a failed LRU from the Government, the Contractor must document the receipt and the initial determination of the LRU for warranty or non-warranty repair using the Monthly Repair Status Report described in Section C.3.3.8.2.

g) The Contractor must maintain the Government provided IFS Purchase Order that accompanies the failed LRU and report the information in the Monthly Repair Status

Report described in Section C.3.3.8.2.

h) For the FAALC receipt of a repaired LRU, the Contractor must prepare the Packing

List/Shipping Report/Invoice that includes the following information: the Contract

Number/Delivery Order Number, Part Number, Serial Number, Item Description, and

National Stock Number.

i) After inspection by the QRO, the Contractor must ship the repaired LRU to the FAALC with a clean copy of the Packing List/Shipping Report/Invoice, shipping label, and instructions inside the container within the contractual turnaround time (TAT). The contractual turnaround time is defined in Section H under Warranty and Repairs.

j) The Contractor must invoice for Cannot Duplicate/No Fault Found actions via the Cannot

Duplicate CLIN (TBD) of Section B.

Non-Warranty Repair

The Contractor must follow the repair requirements identified in Section C.3.3.8. This section applies to each unit determined not to be under warranty. This determination must be made based on the criteria established in Section H.3, Warranty, of the contract.

a) The Contractor must electronically send a copy of the relevant Delivery Order and provide supporting information to the FAA COR. This information must be in sufficient detail to demonstrate that the cause of the failure was outside the warranty conditions based on the criteria established in Section H.3, Warranty, of the contract.

b) The transportation costs for non-warranty repairs will be reimbursed to the Contractor, for shipment from the FAA to the Contractor’s repair facility and from the Contractor’s facility to the FAA depot via the Non-Warranty Repair CLINs (TBD).

c) The turn-around-time for repair of the non-warranty repairs must be the same time as warranty repairs (refer to Clause H.3 (g)) after receipt of a response from the FAA

Contracting Officer.

d) In the event a repair is required to return a defective LRU back into warranty status, the Contractor must bill the Non-Warranty Repair CLINs (TBD), for the repair costs.

e) Should a defective LRU be determined to be out of the scope of the warranty repair by the Contractor, the Contractor must provide a fixed repair quote to the FAA

Contracting Officer to determine if the LRU is to be returned to warranty status.

Monthly Repair Status Reports

As ordered by the Government, the Contractor must develop and deliver a Monthly Repair Status

Report, as specified by that includes the repair information for warranty and non-warranty repair actions.

Monthly Repair Status Report L005

Technical Instruction Books (TIB)

The Contractor must develop and provide technical instruction books meeting the requirements of

FAA-D- 2494B (March 14, 1984), Appendix I, as a minimum. The Contractor must deliver one copy of the Technical Instruction Book with each item of hardware. The Contractor must specify an individual who will serve as a point of contact for all technical instruction book issues.

The Contractor must grant the Government unlimited rights to the TIB data, which includes the right to use, disclose, reproduce, prepare derivative works, distribute copies to the public, and perform publicly and display publicly, in any manner and for any purpose, and to have or permit others to do so.

Technical Instruction Book L006

Diminishing Manufacturing Sources and Material Shortages (DMSMS)

The Contractor must implement a DMSMS program for the monitoring and surveillance of

DMSMS issues, obsolete parts and components used in the manufacture and repair of all hardware, and software delivered IAW the DNTS contract, including but not limited to the DNTS system equipment, equipment for repair of the DNTS system, all support and test equipment, ancillary equipment, any special test equipment, and Faulted Modules.

The Contractor must notify the FAA of any Diminishing Manufacturing Sources and Material

Shortages (DMSMS) issues that could impact the ability to maintain and sustain the DNTS

Program for the entire term of the contract including option periods. The Contractor must submit a DMSMS Report on an annual basis, as ordered. The Contractor must provide recommended mitigation strategies for resolving DMSMS issues.

Diminishing Manufacturing Sources and Material Shortages

Report

L008

Training

As ordered by the FAA, the Contractor must develop and deliver training materials for a DNTS

Operations and Maintenance Course (O&MC) designed for Government personnel who operate, maintain, and perform troubleshooting with fault isolation for system restoration of the DNTS.

The Contractor must develop O&MC training materials for both Instructor Led Training (ILT) and

Web-Based Training (WBT). Both training modalities share the same course objectives; however, the ILT course should be developed for lab-based, hands-on training while the WBT must be developed as a remote learning alternative.

The FAA (not the Contractor) will provide Government instructors to teach the Contractor-developed ILT course and the FAA (not the Contractor) will implement the Contractor-developed

WBT into FAA’s e-Learning Management System (e-LMS).

The Contractor must ensure that all training materials are submitted to the FAA COR and approved by the FAA Safety and Technical Training Representative.

DNTS Training Lead

The Contractor must appoint a DNTS Training Lead to serve as the primary point of contact for all training requirements. The DNTS Training Lead must meet the requirements specified in

Section H Clause 3.8.2-17 Key Personnel and Facilities.

Environmental Occupational Safety and Health (EOSH)

All training developed or revised by the Contractor must meet or exceed the appropriate

Occupational Safety and Health Administration (OSHA) regulations (see OSHA 29 CFR 1910).

OSHA safety regulations must be integrated into course content, as appropriate. All instruction must emphasize each person’s accident prevention responsibilities, both as an individual and as a representative of the Government. Safety precautions related to training on the operations, maintenance, and/or troubleshooting of the equipment must be a prominent part of the training.

Training Deliverables (General)

All training must be developed using Instructional Systems Design methodologies. The Contractor must provide training services in accordance with the provisions of FAA Order 3000.22, Air

Traffic Organization Technical Training Management. Details for these requirements and any points of clarity will be provided in the task order and answered during the Contractor-hosted

Training Guidance Conference (TGC).

Personnel Qualification Report

The Contractor must provide a Personnel Qualification Report that provides the roles and qualifications of Contractor personnel who will be involved in the development and/or delivery of training.

Personnel Qualification Report M001

Commercial Off-the-Shelf (COTS) Training Materials

The Contractor must provide a COTS training materials report that describes any existing, commercially available training materials and its suitability for DNTS training. The Contractor must present the COTS training materials report during the TGC.

The Contractor must ensure all training materials required by this section are free from all encumbrances that prohibit their reproduction or use by the FAA for training purposes, including integration into the FAA’s electronic Learning Management System (eLMS) as well as any other applicable learning systems for the storage, delivery, and records management of the training.

These encumbrances include but are not limited to copyrighted materials, registered documentation, and software.

COTS Training Material Report M002

Training Development Plan (TDP)

The Contractor must provide a Training Development Plan that describes the Contractor’s plan and strategy for accomplishing all DNTS training requirements in the Contract.

Training Development Plan M003

Task and Skills Analysis (TASA) Report

The Contractor must provide a Task and Skills Analysis Report that identifies the specific tasks and skills required for Government personnel who operate, maintain, and perform troubleshooting with fault isolation for system restoration of the DNTS.

Task and Skills Analysis Report M004

Course Design Guide (CDG)

The Contractor must provide a Course Design Guide that includes all information needed to develop the course, including objectives, testing techniques, tools and equipment, teaching strategies, and content.

Course Design Guide M005

Student Achievement Tests

The Contractor must provide Student Achievement Tests based on the Government approved training requirements identified in the Tasks and Skills Analysis (TASA) Report and consistent with objectives and content in the technical outline of the Course Design Guide (CDG) The

Contractor must develop a minimum of three examination items for each objective identified in the CDG.

Web Based Training (WBT) Operations and Maintenance Course (O&MC)

The Contractor must deliver content for a WBT O&MC to be integrated by the FAA into FAA’s eLMS platform IAW CDRL M007. Training must be developed using Instructional Systems

Development methodologies described in FAA Order 3000.22, Air Traffic Organization Technical

Training Management, FAA Order 3000.57, Air Traffic Operations Technical Operations and

Personnel Certification, and operations and maintenance requirements of the Technical Instruction

Book. The Contractor must ensure that training materials comply with Section 508 of the

Rehabilitation Act of 1973 as amended (29 U.S.C 794) and requirements of FAA Order 3000.22.

Details for these requirements will be answered during the Contractor hosted Training Guidance

Conference (TGC).

The learning level for the E-Learning Operations and Maintenance Course must be Level 2 IAW

Categories of eLearning Technology and their Impact on Performance and Proficiency.

The integration of the E-Learning Operations and Maintenance Course and Operator Briefing into the eLMS must be in accordance with FAA eLMS Content Integration Guide. Final acceptance of the WBT O&MC is dependent on successful integration into eLMS and the Contractor must work with the FAA to resolve any course integration issues.

To the extent possible, the Contractor must use materials developed for the Instructor-led

Operations and Maintenance Course to design the web-based training course.

Instructor Led Training (ILT) Operations and Maintenance Course (O&MC)

The Contractor must provide an ILT O&MC Lab course with instructor and student guide training materials. The Contractor must provide an ILT Lab course that includes simulation hands-on type activities that meet the…