CTD Section C_AMEND 0001.docx

Statement of Work For Common Terminal Digitizer (CTD) Revision 1.1 10 Dec 2013

Table of Contents

SECTION C – STATEMENT OF WORK

DTFAWA-14-C-00047

AMENDMENT 0001

SECTION C – STATEMENT OF WORK

DTFAWA-14-C-00047

ii

Scope This Statement of Work (SOW) describes the tasks the Contractor must perform for the design, development, production, test, implementation and management of the Common Terminal Digitizer (CTD) that enables the Airport Surveillance Radar Model 8 (ASR-8) system to interface with digital automation technology in various National Airspace System (NAS) systems. The CTD must provide a digital output by converting the existing ASR-8 and Air Traffic Control Beacon Interrogator Model 5 (ATCBI-5) and Mode Select (Mode-S) outputs into a digital message format to interface with digital automation technology fielded in various NAS systems (e.g., Standard Terminal Automation Replacement System (STARS), En Route Automation Modernization (ERAM).

Background The Federal Aviation Administration (FAA) has directed the extension of the ASR-8 systems currently deployed and operating in the NAS. These primary radar systems, along with their associated secondary radar systems, have an analog output that does not support the planned NAS Terminal Automation Modernization and Replacement (TAMR) Phase 3 Segment 2 Program, which completes the convergence of all terminal radar sites to a single digital terminal automation system and enables Next Generation Air Transportation System Capability.

Applicable Documents The following specifications, handbooks, orders, standards, and drawings form a part of this SOW and are applicable to the extent specified herein.

FAA Specifications None FAA Standards

Military Standards

Other FAA Documents

FAA Order JO 6000.50D National Airspace System (NAS) Integrated Risk Management Non-Government Documents ANSI/GEIA-STD-0007-A-2010 Standard for Logistics Product Data Requirements The Contractor must utilize the practices, processes and procedures (e.g., software engineering, systems engineering, configuration management, manufacturing, quality assurance, operational support) described in this SOW, during the conduct of this effort. The CTD must be in compliance with the System Specification for the Common Terminal Digitizer, Attachment 1, which includes a Verification Requirements Traceability Matrix (VRTM), and the Interface Requirement Document (IRD) for the Common Terminal Digitizer to Standard Terminal Automation Replacement System, Attachment 2. The Contractor must be in compliance with the data requirements and deliverables identified in the Contract Data Requirements List (CDRLs), Attachment 3, as described in this SOW.

This SOW defines the tasks for the system design, test, production and delivery of the CTD. This includes:

a. Generation of the product specification

b. Design

c. Production (First Article (FA) Units and Production Units)

d. Development testing

e. Support of operational testing by the Government

f. Sparing

g. Repairing

h. Training

i. Providing support of Government installation at key sites

j. Development of repair and lifecycle capabilities for the Government

k. Drawings, manuals, and software documentation

l. Reliability, maintainability, and availability In support of Contractor development and test activities, the Government will provide access to ASR-8, ATCBI-5 and Mode S radar systems at the William J. Hughes Technical Center WJHTC at Atlantic City, New Jersey. The Contractor must coordinate with the Government program office for this effort.

Program Management Program Management Plan The Contractor must submit a Contractor’s Program Management Plan (PMP) in accordance with CDRL PM01, and must revise the plan as required. Upon Government approval, partial approval, or limited approval of the PMP, the Contractor must apply this plan without deviations. The Contractor must obtain Government approval of any deviations from the PMP, and must incorporate these approved changes immediately into the PMP or at the next revision of the PMP, at the Government’s discretion. The Contractor must identify in the PMP the Contractor’s and major subcontractor(s) management, organization, authority, responsibility, controls, testing program, methods, and procedures; and the extent to which these apply to the CTD program. The Contractor must detail in the PMP the Contractor’s methodology to ensure that the program management requirements set forth in this SOW are met. The Contractor must perform the following tasks in managing this contract, including, but not limited to:

a) Produce the schedules of work that reflect and track the delivery of products as specified by this SOW;

b) Use methods and metrics for assessing the schedule, technical performance of the work, cost, and risks of this program;

c) Assess the impact of risks and costs on successful completion of the work efforts by relating risks and costs to schedule and technical performance;

d) Identify risks and develop and implement mitigation plans for those risks as described in this SOW

e) Designate a Contractor’s Program Manager (PM) who is responsible for integrating and maintaining the total Contractor effort as described in this SOW and the PMP.

The Contractor’s PM must be prepared at all times, given reasonable notice, to present and discuss with the Government the status of contract activities.

The Contractor must conduct ongoing risk management activities during the period of the contract. The Contractor must ensure that the risk management activities are an integral part of the Contractor’s management process, as described in the PMP.

The Contractor must meet all system requirements in the System Specification and its associated VRTM and the IRD. The Contractor must develop an Integrated Master Schedule (IMS) that accomplishes all tasks identified within this SOW and supports the CTD Contract Requirements.

CDRL: PM01 Program Management Plan (PMP) Project Control The Contractor must continuously monitor the technical performance of this contract, and of all subcontracts, and provide the Government with an assessment of program progress or problems at Program Management Reviews (PMRs), Technical Interchange Meetings (TIMs), and in the Progress, Status and Management Report. The Contractor must use a schedule performance measurement and reporting system. The Contractor must ensure the management methods and procedures provide visibility into, and timely progress reporting on, all contracted efforts for internal management and Government oversight purposes.

The Contractor must apply metrics to assess the cost, schedule, and performance of the work and risks. The Contractor must be responsible for developing the criteria for successful completion of each measure. The Contractor must not consider data as actuals until the criteria for counting actuals have been successfully met. The Contractor must describe the additional metrics in the PMP per paragraph 4.1 of this SOW. The Contractor must provide program metrics information in accordance with the Progress, Status and Management Report (PSMR) and report their status at PMRs.

CDRL: PM02 Progress, Status and Management Report (PSMR) Meetings, Reviews and Conferences Post Award Conference The Contractor must plan for, host, support, and participate in a Post Award Conference to be held at the Contractor’s site within 30 days of contract award on a date agreed to by the Government. At this conference, the Contractor must address the plans, schedules, and work efforts for this Contract. To successfully complete the Post Award Conference, the Contractor must:

a. Submit draft CDRL items PM01, PM02, SE01, PM03

b. The Contractor must submit conference presentation materials and minutes electronically to the Government within 5 days of the completion of the conference.

CDRL: PM01 Program Management Plan (PMP) CDRL: PM02 Progress, Status and Management Report (PSMR) CDRL: SE01 System Safety Program Plan (SSPP) CDRL: PM03 Integrated Master Schedule (IMS)

Preliminary Interface and Design Review The Contractor must conduct a Preliminary Interface/Design Review (IDR) within 60 days from contract award on a date agreed to by the Government. The Contractor must provide the documentation for review 15 working days prior to the scheduled meeting in order to facilitate understanding of the design and discussion points for the meeting. At the Preliminary IDR, the Contractor must include, but not be limited to providing the status on:

· Tasks identified in Section 4.0 (e.g. design, interface design with existing systems)

· Reliability, Maintainability and Availability

· Design Test and Evaluation (DT&E) Approach

· System Safety Assessment

The Contractor must submit presentation materials and minutes electronically to the Government within 5 days of the completion of the preliminary IDR review.

Final Interface and Design Review The Contractor must conduct a Final Interface and Design Review (IDR) at the Contractor’s site. The IDR must be held within 6 months of contract award on a date agreed to by the Government. The Contractor must provide the documentation for review 15 working days prior to the scheduled meeting in order to facilitate understanding of the design and discussion points for the meeting. At the Final IDR, the Contractor must include, but not be limited to:

· Tasks identified in Section 4.0 (e.g. design, interface design with existing systems)

· Reliability, Maintainability and Availability,

· Design Test and Evaluation (DT&E) Approach

· System Safety Assessment

The Contractor must submit the IDR package, which includes but is not limited to all presentation materials, minutes and action item listing, electronically to the Government within 10 days of the completion of the review. The closure of any action item must be with the Government’s concurrence.

Logistics Guidance Conference The Contractor must plan, host, and support a Logistics Guidance Conference (LGC) to be convened at the Contractor’s facility in conjunction with the Post Award Conference. The Contractor’s Logistics Support Manager must co-chair the meeting with the Government’s designated logistics’ lead. Contractor logistics personnel must present briefings that indicate the Contractor’s approach to accomplishing logistics tasks. The Contractor must support the conference with the required resources (e.g., briefings, manpower) necessary to discuss in detail all support considerations. The Contractor must also clarify provisioning requirements and issues (e.g., provisioning deliverables, data requirements, technical documentation, and data for provisioning) at the LGC. The Contractor must include the following subjects, to include, but not be limited to:

a) Maintenance Planning;

b) Manpower and Personnel;

c) Supply Support;

d) Support Equipment;

e) Technical Data;

f) Training and Training Support;

g) Computer Resources Support;

h) Packaging, Handling, Storage and Transportation;

i) Facilities;

j) Integrated Logistics Support (ILS) Management.

k) Integrated Support Plan (ISP) The Contractor must submit presentation materials and minutes electronically to the Government within 5 days of the completion of the review.

Program Management Reviews The Contractor must conduct Program Management Reviews at the Contractor’s facility. The PMRs will be held on a quarterly basis from the IDR through FA acceptance and then on a semi-annually basis through the end of the contract period. During the PMRs, the Contractor must review plans for accomplishing IMS and must present, but not be limited to: cost, schedule, and technical performance status of the contract, program risks and status of risk-mitigation measures, production status, logistics support, implementation status and status of action items, CDRL deliveries, Engineering Change Proposals, Government Furnished Property (GFP), Government Furnished Equipment (GFE) and Government/Contractor correspondence.

The Contractor must submit presentation materials and minutes electronically to the Government within 5 days of the completion of each review.

Technical Interchange Meetings The Contractor must conduct and/or support TIMs as required throughout the contract period. TIMs may be requested by either The Contractor or the Government to address a specific program or technical issue. The Contractor must submit presentation materials and minutes electronically to the Government within 3 days of the completion of each TIM.

Provisioning Conference The Contractor must conduct a review of the provisioning requirements relative to the production baseline system and conduct a Provisioning Conference with the Government. The provisioning conference must be held no later than 30 days after the completion of the Physical Configuration Audit (PCA).

Test Readiness Reviews The Contractor must schedule and conduct a Test Readiness Review (TRR) to ensure readiness to enter test prior to In-plant DT&E and On-site DT&E as identified in Sections 4.3.5 and 4.3.6. At the TRR, the Contractor must present a review of all configuration items applicable to the test and include all applicable tests, the identification and availability of resources and personnel, the configuration control/validation of test tools and test items and any other items deemed necessary to the successful conduct of testing.

The Contractor must submit presentation materials and minutes electronically to the Government within 5 days of the completion of each review.

Post-Test Reviews The Contractor must hold post-test reviews following the completion of each formal test to review test data and preliminary results. The Contractor must include summaries of the minutes of the reviews (including Action Items and Deficiencies identified during the review by the Government and Contractor) and resolution of the entries in the Deficiency Report (DR) Database, as applicable (including any necessary re-testing results) in the final version of the DT&E Report.

CDRL TE01: Development Test and Evaluation (DT&E) Report Cost Management The Contractor must apply internal cost management control systems and provide the Government with timely and auditable data on a monthly basis that reports product-oriented contract status. The Contractor must conduct continuous cost management assessment. The Contractor must provide a Progress, Status and Management Report. The Contractor must present cost/schedule performance at each PMR.

CDRL: PM02 Progress, Status and Management Report (PSMR) Schedule Planning and Control The Contractor must establish an IMS based on a logical and efficient sequence of events designed to meet the requirements of the CTD Contract. The Contractor must include both planned dates and actual completion dates, and measured progress of individual schedule elements in the IMS. The Contractor must use the FAA WBS Version 5.0, Sections 3 and 4 as described in the FAA Acquisition System Toolset (FAST) at http://fast.faa.gov in developing the schedule. The Contractor must maintain and update the schedule to a minimum level 4 unless otherwise specified. If the schedule is broken down by CLIN, the Contractor must not count the level representing the CLIN as one of the four minimum levels, so that correspondence down to a minimum of the four levels in FAA WBS Version 5.0 can be maintained.

CDRL: PM02 Progress, Status and Management Report (PSMR) CDRL: PM03 Integrated Master Schedule Subcontract Management The Contractor must document and implement subcontractor management. The Contractor’s Subcontractor Management Plan must be described in the PMP.

CDRL: PM01 Program Management Plan (PMP) Data Management The Contractor must maintain a Data Accession List. The Contractor must list internal data generated in compliance with contractual tasks and subcontractor-generated data on the Data Accession List. When requested by the Government, the Contractor must make available for Government review those internal documents used for design and management.

CDRL: PM04 (Data Accession List/ Internal Data) Risk Management The Contractor must maintain a risk management program to assess risks associated with achievement of technical, cost, and schedule requirements, using Air Traffic Organization Program Management Organization Risk, Issue and Opportunity Management Plan as guidance. The Contractor must document and implement risk management in the PMP. Specific risk management functions must, at a minimum:

· Identify known and potential risks, issues and opportunities

· Assess risks, including a relative ranking by program impact and the establishment of critical thresholds

· Define methods or alternatives to mitigate or minimize these risks, including the identification of criteria upon which programmatic decisions can be based

· Track and report risk mitigation progress CDRL: PM01 Program Management Plan (PMP) Configuration Management The Contractor must use an internal Configuration Management system for the control of all configuration documentation, software, physical media, and physical parts representing or comprising the CTD in accordance with FAA-STD-021A throughout the contract period (pre-production, including FA units, through production). The Contractor’s internal CM system must be described in the PMP. The Contractor must maintain this system and related procedures throughout this Contract. The Contractor must use and maintain configuration baselines and their documentation. Incremental product baselines may be permitted if approved by the Government.

CDRL: PM01 Program Management Plan (PMP) Engineering Change Proposal Preparation The Contractor must prepare an Engineering Change Proposal (ECP) to define the CTD product baseline.

CDRL: TD01 Engineering Change Proposal Deviation/Waiver The contractor must request government approval for deviations and waivers to depart from any CTD System Specification requirement. The deviation or waiver must be prepared in contractor format.

CDRL: SE02 Deviations and Waivers Configuration Status Accounting Reports The Contractor must generate Configuration Status Accounting Reports (CSARs) to ensure that delivered documentation accurately describes and represents the hardware and software configurations. The Contractor must document the configuration identification and determine the status of change proposals, deviations, and waivers with status accounting reports. The Contractor must establish and describe any automated tools used to accomplish status accounting in the PMP. The Contractor must provide the CSARs to the Government. The Contractor must use the CSARs to provide traceability of any change through the change control process.

CDRL: PM05 Configuration Status Accounting Report (CSAR) Configuration Audits The Contractor must conduct Functional and Physical Configuration Audits (FCAs and PCAs) and provide minutes including any required corrective action. The delivered CTD systems must be in accordance with the PCA approved product baseline that reflects all changes resulting from DT&E and OT&E to meet contractual requirements.

CDRL: PM06 Configuration Audit Summary Report (FCA) CDRL: PM06 Configuration Audit Summary Report (PCA) Quality Assurance The Contractor must establish and maintain a Quality Assurance Program (QAP) in accordance with ISO 9001:2008 Quality Management Systems – Requirements. The Contractor’s Quality Assurance Program must be described in the PMP.

CDRL: PM01 Program Management Plan (PMP) Systems Engineering The Contractor must execute a systems engineering process for requirements management to ensure traceable validation, integration, testing, and verification of the system requirements.

The contractor must update all applicable documents that involve requirements as necessary when, with Government approval, requirements are changed or added to.

System Requirements The Contractor must prepare a CTD Product Specification documenting the entire set of System Specification and appropriate derived requirements. The derived requirements shall define the top-level requirements identified in the System Specification and shall represent the Contractor’s design approach. The derived requirements must include but not be limited to CTD external and operator-accessible control functionality, subassembly test requirements and production and depot repair processes in support of the requirements identified in this SOW. The Contractor must identify each major CTD functional element and define the critical top-level requirement that must be achieved by that element.

The Contractor must generate and maintain a VRTM to provide an audit trail from requirements of the System Specification to the contractor’s design implementation requirements and subsequent verification methods. The VRTM must be an appendix to the CTD Product Specification and all other subordinate contractor specification documents.

Where practical, the contractor’s system requirements must be met through the use of Commercial Off the Shelf (COTS) or Non-Developmental Items (NDI) items, when such products meet project needs, meet mission operational and environmental requirements, and are cost effective over the entire cycle of the project.

The Contractor must ensure that all requirements from the Product Specification/VRTM and various Interface Control Documents (ICDs) are added to the Contractor’s test pans. The Contractor must further trace the requirements in the Product Specification and VRTM into lower level test plans and procedures as necessary to ensure 100% verification coverage.

CDRL: SE03 Product Specification with VRTM System Identification and Selection All Contractor provided equipment (hardware, electronic, electrical, software, etc.) must be in accordance with the CTD System Specification and subordinate contractor-developed Product Specification.

Interface Control Documentation The Contractor must provide ICDs as a part of the systems engineering process.

The Contractor must prepare ICDs in accordance with FAA-STD-025F and submit to the Government for review and approval. The Contractor must participate in technical discussions with the Government to develop the technical data necessary to define the interface and interface verification methods.

The Contractor must prepare the CTD to STARS CD-2 ICD to fulfill the requirements of the IRD including a VRTM as an appendix.

The Contractor must generate additional ICDs describing the CTD interfaces to the ASR-8, ATCBI-5, and Mode S radar systems providing full functional, physical and electrical specifications, including in each a VRTM as an appendix.

The contractor must ensure all ICD requirements are referenced in the contractor test plans for 100% verification coverage.

CDRL: SE04 Interface Control Document (ICD) Test and Evaluation Test Program Description The Contractor must plan, conduct, and document an integrated test and evaluation program, in conformance with this SOW and the Government-approved PMP using the Acquisition Management System Test & Evaluation Process Guidelines as guidance. In the test program, the Contractor must verify that the CTD meets all performance requirements including the physical, functional and interface requirements as stated in the System Specification and the Contractor’s generated product specification and its associated VRTM. The Contractor must develop test schedules, test plans, and test procedures to meet the testing requirements of this SOW. The Contractor must conduct tests and generate test reports, as required by this SOW. The Contractor must integrate test schedules into the overall IMS. The Government reserves the right to witness Contractor testing during any test phase or level. The Contractor must furnish equipment, space, and personnel required to perform Contractor-conducted tests. The Contractor must coordinate testing to be performed, and ensure that there is minimal redundancy of effort or data. The Contractor must have the responsibility for integration, control, and coordination of Contractor and subcontractor testing.

CDRL: PM01 Program Management Plan (PMP) Test and Evaluation Management The Contractor must assign and identify in the PMP a Test Manager with responsibility for the integration, control, oversight, and coordination of all Contractor and subcontractor testing. The Contractor’s Test Manager must coordinate all testing to be performed.

Test Conduct The Contractor must establish a formal test program. The Contractor must be responsible for the conduct of the DT&E and Production Acceptance Test (PAT) portions of the overall test program. The Contractor must include the appropriate tests for all equipment, software, and interfaces. The Contractor must:

a) Document all problems identified in DRs,

b) Retain these in the DR database, and

c) Track them from discovery through resolution.

The Contractor must conduct DT&E tests with a test unit that conforms to the product configuration baseline. The Contractor must conduct PAT with a unit which conforms to the product configuration baseline.

Test Program Requirement Verification The Contractor must revise and re-brief the Government on the contents of the requirements mapping as appropriate in the IDR and the TRR before the beginning of DT&E.

The Contractor must identify in the VRTM the method(s) used to verify each requirement, in accordance with the CTD System Specification.

First Article Units The Contractor must produce a quantity of two FA units; one each for In-plant DT&E and On-site DT&E at the WJHTC as specified in this SOW. The FA units must be configured with two identical redundant sets of CD-2 formatted surveillance data via two independent 56 kbps synchronous RS-422 physical interfaces (ASR-11 style interface), one set of CD-2 formatted surveillance data via one set of four 9600 kbps synchronous RS-422 physical interfaces (ASR-9 style interface) and two identical redundant sets of ASTERIX formatted surveillance data via two independent Ethernet physical interfaces (ASTERIX interface)(Reference CTD System Specification paragraph 3.1.9.2.1, 3.1.9.2.2 and 3.1.9.1.1, respectively). The FA units must include two maintenance controls. The Contractor must deliver a site spares kit, site consumables, peculiar support and test equipment, 2 sets of TIBs and applicable on-site documentation/manuals with each FA unit.

The Contractor must be responsible for the FA units through successful completion of Government conducted OT&E. The Contractor must repair and maintain the CTD FA units to the approved product baseline through In-Plant and On-Site DT&E.

Production Acceptance Testing The Contractor must perform PAT on each FA Unit and each delivered CTD system to verify that end-items conform to the CTD System Specification and the Contractor’s generated product specification, are free from manufacturing defects, and conform to the product configuration baseline. The Contractor must ensure compliance to system-level hardware and software requirements.

CDRL: TE02 Production Acceptance Test (PAT) Plans and Procedures CDRL: TE03 Production Acceptance Test (PAT) Report In-Plant DT&E The Contractor must allow government witnessing of all in-plant testing of the CTD to verify the system meets all performance requirements as specified in the Government approved Test Plan and Procedures for this effort. In-Plant testing must consist of the portion of the DT&E testing as defined by the Government approved DT&E tailored VRTM.

CDRL: TE04 Development Test and Evaluation (DT&E) Plans and Procedures CDRL: TE01 Development Test and Evaluation (DT) Report On-Site DT&E Test The Contractor must deliver, install and optimize the FA system, components, and other deliverables for testing at the WJHTC in Atlantic City, NJ. The Contractor must conduct the DT&E testing to verify compliance with the System Specification and the Contractor generated product specification requirements. The Contractor must allow government witnessing of all on-site testing of the CTD to verify the system meets all performance requirements as specified in the Government approved Test Plan and Procedures for this effort. The Contractor and the government will review the test results to determine any necessary corrective activity, and if required the Contractor must perform regression testing and demonstration necessary to demonstrate compliance with all CTD requirements.

CDRL: TE04 Development Test (DT) Plans and Procedures CDRL: TE01 Development Test (DT) Report CDRL: SE05 Technical Report/Study (Optimization) Operation Test and Evaluation As a result of Government conducted OT&E, the Contractor must make corrections to FA units that may be necessary to correct deficiencies against the requirements of the contract. The Contractor must prepare a DR, documented in the DR database, to describe each problem detected in hardware, software, or documentation that has been placed under configuration control. The Contractor must submit the corrective action planned for each identified discrepancy and identify the proposed regression testing, or future modification(s) to the testing program required to validate the successful corrective action in accordance with an approved schedule.

If tasked under Contractor Services, the Contractor must provide the following services to support the Government conduct of Operational Test and Evaluation (OT&E):

· Systems engineering

· Hardware engineering

· Communications hardware and software

· Software Engineering Deficiency Report The Contractor must implement a tracking system to help identify, report, monitor, and resolve all hardware, firmware, interface, documentation, and software problems. The Contractor must describe this system in the PMP. The Contractor must include all problems identified by both the Contractor and the Government. The Contractor must track DRs through the contract period of performance. The Contractor must maintain a DR database in which each failure or problem discovered is fully documented from initial discovery through to final disposition. The Contractor must include the overall status of the DRs and the Contractor’s plans for DR resolution in the PMR and TIM discussions, with significant problems covered in depth. The Contractor must deliver the database to the Government at the end of the contract. The Contractor must maintain in the DR database the master copy of all DRs.

CDRL: PM01 Program Management Plan (PMP) CDRL: SE06 Deficiencies Report (DR) Database Reliability, Maintainability and Availability The Contractor must maintain a program to ensure that the Reliability, Maintainability and Availability (RMA) requirements of this SOW are satisfied. The Contractor must provide reliability and availability analyses of the CTD hardware and associated components. The Contractor must ensure that reliability briefings at the IDR, appropriate TIMs and PMRs and reliability predictions and reliability model, identify individual subsystem reliability allocations and identify their rollup relationship to achieving the overall system reliability. The Contractor must use this information in conjunction with other planning factors to identify site spare requirements.

The Contractor must document the overall methodology for conducting the RMA program, including the process(es) for tracking failed hardware and using the failure data for reliability purposes, in a Reliability Model in accordance with CDRL RM01. The Contractor must analyze failures and present failure data and discuss engineering remedies and actions at TIMs and PMRs. As part of DT&E, the Contractor must perform a maintainability demonstration using MIL-HDBK-470 as guidance and in accordance with CDRL RM02. The Contractor must make available all COTS manuals and draft Technical Instruction Books (TIB) prior to the start of the demonstration. The Contractor must perform the Maintainability demonstration on a complete final assembly, with all subsystems connected and operational, and with baselined (Production) software as resident and operational for all production units. The Contractor must submit to the Government a list of a sufficient quantity of proposed maintenance actions for approval to verify the RMA requirements. The Contractor must provide pre-faulted modules in support of the maintainability demonstration.

CDRL: RM01 Reliability Model CDRL: RM02 Maintainability Demonstration Plan and Report System Safety The Contractor must conduct program safety assessments in accordance with the Safety Management System Manual V.2.1 and ATO-S 2008-12 V1.5 FAA Safety Risk Management Guidance for System Acquisitions. Procedures and policies must be implemented and periodically reviewed in accordance with FAA policy and recognized best practices. System Safety Management must be in accordance with FAA Order 8000.369A, Safety Management System Guidance; FAA Order 8040.4A, Safety Risk Management Policy; and JO 1000.37A, Air Traffic Organization Safety Management System .

System Safety Program Plan The Contractor must provide a System Safety Program Plan (SSPP) that details the program scope, safety organization, program milestones, requirements and criteria, hazard analyses, safety data, safety verification, audit program, training, accident/incident reporting, and interfaces.

CDRL: SE01 System Safety Program Plan (SSPP) System Safety Working Group Support If tasked under Contractor Services, the Contractor must support Government system safety working groups as required. The Contractor must support reviews of submitted safety analyses and assessments at Government product team system safety working groups (SSWGs).The Contractor must support quarterly Safety Action Reviews conducted by the Government product teams Safety Risk Management Panel (SRMP), as requested.

Security program Personnel Security The Contractor must implement Personnel Security in accordance with FAA Order 1600.1, Personnel Security Program.

Information Systems Security The Contractor must implement the CTD interface equipment information security in accordance with OMB Circular A-130, Management of Federal Information Resources, FAA Order 1370.82, Information Systems Security Program, FAA Order 1370.104, Digital Signature Policy; FAA Order 1370.95, Wide Area Network Connectivity Security; and FAA Order 1370.44, Use of FAA Telecommunications Infrastructure (FTI) Services in the National Airspace System (NAS).

General Engineering Services If exercised, the Contractor must furnish services that include, but are not limited to, engineering/technical support (including training support), systems engineering analysis, site survey, and installation support as requested by the Government. The Contractor must prepare and submit a technical report that fully documents the results of the study or analysis performed.

CDRL: SE05 Technical Report/Study (General Engineering Services) Support Logistics Support The National Airspace Integrated Logistics Support effort begins at Contract Award and evolves throughout the development and test of the CTD.

The following paragraphs describe the logistics requirements.

Logistics Program Management Integrated Support Plan The Contractor must develop and use an ISP in accordance with CDRL LS01.

CDRL: LS01 Integrated Support Plan (ISP) Subcontractor/Vendor Control The Contractor must be responsible for assuring that the performance of all ILS deliverables and activities comply with the requirements of the Contract and in accordance with Section 4.1.6 regardless of source.

Supply Support Provisioning Data The Contractor must prepare and deliver the Provisioning Technical Documentation in Logistics Management Information (LMI) format in accordance with ANSI/GEIA-STD-0007-A-2010 Standard for Logistics Product Data, 90 working days prior to the Provisioning Conference. At a minimum, the Contractor will provide the standard excel spreadsheet for provisioning used with ECPs.

Logistics Management Information Requirements The Contractor must develop and deliver to the Government, LMI data products that a requiring authority needs in order to develop internal materiel management processes. The data products must represent the system design configuration to the component level including systems, subsystems, components, assemblies, subassemblies, cable assemblies, support and test equipment and training equipment required for the CTD.

CDRL: LS02 Logistics Management Information (LMI) Data Product Organic Depot Parts Lay-In As a result of the provisioning conference, the Government may choose to procure initial organic depot parts lay-in for CTD depot repair.

Site Spares and Consumables The Contractor must develop and submit a list of site spares that consists of LRUs, removable modules, common and bulk items, expendable components and any other parts necessary to perform site maintenance to meet the CTD RMA requirements. The Contractor must also identify all site consumables required for operation and maintenance of the CTD system.

CDRL: LS03 Recommended List of Site Spares CDRL: LS04 Recommended List of Site Consumables Technical Data Technical Drawings and Documentation The Contractor must develop technical drawings and data for the implementation and life cycle support of the CTD. The drawings and data will be utilized by the Government in order to operate and maintain the CTD at ASR-8 locations, provide CTD system supply support (depot), second level engineering support for operational sites, and hardware or software modifications required addressing operational issues encountered throughout the life cycle of deployed CTD systems.

The Contractor must develop an engineering drawing tree that will identify all items to be delivered as part of the drawing package.

CDRL: TD02 Engineering Drawing Tree

Product Drawings: For developed items, the Contractor must provide products drawings in accordance with MIL-PRF-28000B, Initial Graphic Exchange Specification Class 2 & 3 and associated lists must be in accordance with MIL-DTL-31000C, paragraph 3.6.2.3.

CDRL: TD03 Product Drawings

COTS Drawings: For all commercial items associated with the CTD, the Contractor must provide all vendor-supplied commercial drawings, technical documentation and source control documents.

CDRL: TD11 COTS Drawings

COTS Hardware Description Document: The Contractor must develop a COTS hardware description document for use in provisioning and baselining the system. This document must be developed to the LRU level and contain sufficient data (such as input/output specifications, performance specifications, dimensions) to provide the Government the information needed to procure the items from commercial and other sources.

CDRL: TD04 COTS Hardware Description Document

COTS Manuals: For all COTS (hardware and software) associated with the CTD, the Contractor must provide all vendor supplied commercial drawings, technical documentation and source control documents. COTS manuals must conform to the requirements of FAA Order 2494B, Appendix I. The Government will be provided with reproduction rights on all deliverable COTS documentation.

The Contractor must provide the following COTS Manuals content at a minimum:

· Operator/User’s Instructions

· Hardware/Repair

· Installation Requirements

· Diagnostics/Diagnostic Interpretations

· Installation/Removal/Maintenance Instruction

· Schematics/Wiring Diagrams

· Parts Lists/Catalog

CDRL: TD05 COTS Manuals/Information

Computer Software (Software/Firmware Artifacts) If exercised, the Contractor must deliver computer software, to include software and firmware source code, programmable device configuration files, and supporting documentation conforming to FAA-STD-026A to permit Government ongoing software and firmware maintenance for the life cycle of the system. Note: If exercised, the computer software delivery will be in conjunction with the Program Support Facility, Section 8.1.

Technical Instruction Books Provision of Technical Instruction Books For any non-COTS (developed) items the Contractor will provide separate TIBs. Each TIB must comply with the requirements set forth in the latest version of FAA-D-2494B. Each developed TIB will be subject to validation and Government verification procedures outlined in FAA-D-2494B. TIBs will be developed and delivered using an editable format such as Microsoft Word or equivalent.

The contractor shall develop and deliver a CTD System Manual which will describe how all of the equipment described in the NDI and COTS technical manuals are integrated into a single operational system. This manual will provide information not contained within the NDI and COTS manuals. Information to be provided will include system interconnect diagrams and block diagrams, system operating procedures, system level fault isolation procedures, system BITE/FI techniques, system theory of operation, and all information required for organizational level O&M. References will be made to the appropriate NDI and COTS technical manuals for specific preventive maintenance and corrective maintenance activities where appropriate. Any parts lists contained in the system manual will be appropriate to a system level technical manual, with any equipment breakdown parts lists referenced within the NDI and COTS technical manuals.

The Contractor must host in-process reviews of all TIBs at the Contractor’s facility. The Contractor must conduct these reviews at 25%, 75%, and final completion. The Contractor must provide drawings, illustrations, and support materials to assist in review. The Contractor must incorporate comments from the reviews into the training courses prior to course conduct.

CDRL: TD06 Technical Instruction Books (TIB) Technical Instruction Books Validation and Verification The Contractor must validate all TIBs prior to submittal to the Government for verification. The Government will conduct a verification of each instruction book submission prior to Government approval of each. The Contractor must provide labor, tools, software, equipment, facilities, and any other engineering, technical, or administrative support necessary to the Government, as may be required, during the verification of the manuals. The Contractor must use existing factory or fielded equipment for validation and verification.

CDRL: TD07 Technical Instruction Books Validation Plan Support/Test Equipment Manuals Separate, stand-alone instruction books must be provided for the operation, description, maintenance, and repair of any Contractor furnished peculiar support and test equipment. The instruction books may be in the original equipment manufacturer’s format. Electronic media, programs or documentation required for data analysis must be provided with electronic test equipment.

CDRL: TD08 Support/Test Equipment Manuals Packaging, Handling, Storage and Transportation Packaging, handling, storage and transportation (PHS&T) must be in accordance with FAA order 4600.27B Personal Property Management. .

Support and Test Equipment The Contractor must identify any common support equipment, peculiar support equipment, common test equipment, special tools or special test equipment required for operation, maintenance, alignment, or adjustment of the CTD at the site level.

CDRL: LS05 List of recommended Support and Test Equipment Training The Government will develop and deliver resident (lecture with lab exercises) training to provide Technical Operations personnel with the knowledge necessary to provide onsite CTD maintenance. The Government will make maximum use of Contractor delivered existing and COTS training programs and materials.

Contractor Documentation The Contractor must conduct a Task and Skills Analysis (TASA) to identify requirements. The Contractor must document results in a TASA Report in accordance with FAASTD-028C. The Contractor must prepare a COTS Training Materials Report for all COTS materials proposed for training for a course in accordance with FAA-STD-028C.

CDRL: TP01 Task and Skills Analysis (TASA) Report CDRL: TP02 Commercial Off-The-Shelf Training Materials Report CTD Unit for Technical Operations Specialist Training The Contractor must produce, perform PAT and deliver a CTD unit to support Government Developed Training Program. The CTD unit must be configured with two identical redundant sets of CD-2 formatted surveillance data via two independent 56 kbps synchronous RS-422 physical interfaces (ASR-11 style interface), one set of CD-2 formatted surveillance data via one set of four 9600 kbps synchronous RS-422 physical interfaces (ASR-9 style interface) and two identical redundant sets of ASTERIX formatted surveillance data via two independent Ethernet physical interfaces (ASTERIX interface). The CTD unit must include two maintenance controls panels. The Contractor must deliver any identified unique support and test equipment and site spares that include one each of every designated LRU in the CTD system.

CDRL: TE03 Production Acceptance Test (PAT) Report Maintenance Interim Contractor Depot Logistics Support The Contractor must provide Interim Contractor Depot Logistics Support (ICDLS) for CTD. The Contractor must ensure that this includes stocking, storing, issuing, and shipping of expendable, consumable and repairable items. The Contractor must replace those items covered by warranty at no cost to the Government. The Contractor must establish the ICDLS in support of the Government’s conduct of OT&E.

Lay-In of ICDLS Spares The Contractor must lay-in and maintain a quantity of spares to include LRU and specialized/long lead time components) to support the required system RMA and ICDLS.

Exchange and Repair The Contractor must repair, as required, all repairable Exchange and Repair (E&R) LRUs returned from FAA field sites. The Contractor must ensure that this repair cost does not exceed 65% of the cost of a new item, unless approved by the Contracting Officer.

The Contractor must furnish all labor, tools, test equipment, parts, software, and any other technical or administrative support necessary to provide the required ICDLS.

The Contractor must perform supply support in accordance with standard FAA practices. The Contractor must track LRU failures by site, part number, and serial number. The Contractor must document replaced piece parts associated with failed LRUs.

The Contractor must provide depot level support 7 days a week, 24 hours a day, to meet a priority one request from the field. The government will designate the priority as follows:

Priority 1 is used when either the prime or standby equipment is inoperative or when a facility is operating at a reduced performance that adversely affects Traffic Control operations. Shipment to the designated facility is to be within 24 hours, including weekends and holidays, after notification by the Government's authorized representative.

Priority 2 is used when a facility is operating with substandard equipment or operating conditions indicate imminent facility failures or outage. Shipment to the designated facility is to be received within 48 hours after receipt of notification by the Government's authorized representative.

Priority 5 is used with a routine requirement or stock replenishment. Shipment to the designated facility is to be received within eight days after receipt of notification by the Government's authorized representative.

Organic Depot Support Facility and Training Transition of Depot Support Facility If exercised, the Contractor must furnish all labor, tools, test equipment, hot test bench, parts, software,…