DRAFT_ADC_Task_Order_PWS.pdf

ATSSI Air Data Computer Task Order

10/17/2016

Air Data Computer (ADC) Rehost Effort

Task Order PWS

1 Introduction

This document describes a typical Test Program Set (TPS) Performance Work Statement (PWS) of what will be a representative task for the ATSSI contract. The purpose of this PWS is to provide a typical TPS development for offerors on the ATSSI project to propose and to demonstrate most, if not all, the criteria for evaluation for this contracting effort. This task is potentially awardable upon ATSSI contract award.

For purposes of evaluation, offerors will make several assumptions as detailed in the description of this task which may not reflect actual circumstances. As such, revisions to the bid may be necessary prior to actual award of the Air Data Computer Task Order, should the Government elect to award this effort.

2 Air Data Computer Task Order

The following requirements detail the Air Data Computer Task Order for the ATSSI contract.

2.1 Test Program Set (TPS) Development

The following sections describe the specific tasks associated with this effort. The contractor shall develop a Traceability matrix in contractor format identifying all requirements associated for each TPS developed as a part of this effort. The contractor shall review this matrix as a part of the milestone review described in 2.1.9.1.

2.1.1 TPS Development Requirements

The following paragraphs describe the requirements to develop TPSs for the items identified in

Appendix A.

2.1.1.1 ATE Configuration & Capability

The contractor shall evaluate the end items in Appendix A - to propose the best choice of test solutions/systems. The proposal shall include an evaluation of the chosen test system (including hardware components, software components, and associated documentation) to determine, what, if any, modifications are required to re-host a test capability from its legacy test equipment. The contractor shall propose potential changes to the Government as part of their proposal. At a minimum system and calibration software updates are recognized as potential requirements to add additional instrument driver functions to the system software. The contractor shall provide estimates to update the software and documentation as required.

If deemed necessary, the bidders shall provide pricing to update and deliver the

Calibration/Measurements Requirements Summary (CMRS) for the associated test systems (if required) to document changes necessary to host new TPSs. If awarded, the contractor shall coordinate with the AFMETCAL representative designated by the Government to review the changes and verify the updates at completion. (CDRL A013)

The contractor shall inform all other organizations utilizing the associated test systems of any system changes. The contractor shall provide pricing to ensure regression testing is completed after all system changes to ensure there is no impact to the existing TPS.

If awarded, the contractor shall ensure that the Air Force Metrology and Calibration

(AFMETCAL) Program Office is informed of any impacts to the ATE calibration software.

2.1.2 Test Program Set

The contractor shall bid the capability to functionally test each of the items listed in Appendix A

- on the appropriate test system solution. The contractor shall meet or exceed the test and measurement capabilities of the existing legacy test equipment.

2.1.2.1 Test Program Set Requirements

The following paragraphs detail the requirements for each TPS listed in Appendix A - . The contractor shall develop and deliver a composite list of I/O requirements associated with each

TPS included as a part of this task.

2.1.2.2 Test Program Set Design

The following paragraphs describe the required elements for successful TPS design.

2.1.2.3 Software Design and Development

The contractor shall develop TPS software to capture the test requirements for each end-item listed in Appendix A as established in the applicable O&M manual. The contractor shall develop

TPS software package to execute on the appropriate test system.

2.1.2.4 Hardware Design and Development

The contractor shall develop draft schematics, parts lists, wire lists and/or assembly drawings for all TPS required as a part of this task. The contractor shall create all hardware documentation in accordance with 2.1.2.9 of this task. The contractor shall purchase all required components, assemblies, and materials necessary and develop all necessary hardware associated with this task to provide the government with all TPS required as a part of this task. The contractor shall include all cables, connectors, and similar items required to meet the test requirements.

2.1.2.5 Technical Manuals

The contractor shall provide recommended redline markups to the current End Item Overhaul

Manuals listed in Appendix A - .

MIL-STD-38784 DoD Standard Practice for Manuals, Technical: General Style CDRL A004

The contractor shall prepare a Test Program Manual (TPM) that describes the instructions for performing automated tests for each TPS. The contractor shall use MIL-STD-38784 (Department of Defense Standard Practice for Manuals, Technical: General Style) as a guide/reference in the development of the Test Program Manuals.

2.1.2.6 TPS Software Version Description

The contractor shall deliver a Software Version Description (SVD) for the TPS software package in accordance with DI-IPSC-81442A. The contractor shall identify the computer program identification number (CPIN), program version and revision, release date and software installation procedures within the SVD.

DI-IPSC-81442A, Software Version Description (SVD), CDRL A005

2.1.2.7 TPS Software Design Description

The contractor shall develop a Software Design Description (SDD) in contractor format for each

TPS. At a minimum the SDD will capture the design decisions for that TPS software as well as any pertinent information that will be useful in the support of the TPS. The Government recommends DI-IPSC-81435A as a guide for the development of the SDD.

DI-IPSC-81435A, Software Design Description (SDD), CDRL A008

2.1.2.8 Acceptance Test Procedure

The contractor shall develop an Acceptance Test Procedure using DI-NDTI-80603 as a guide that establishes the criteria for government acceptance of the TPS. The contractor shall submit the ATP at least ten days prior to the start of acceptance testing. At a minimum, the ATP shall demonstrate the suitability of the Indicator test equipment to satisfy the test requirements established in the applicable O&M Manual for each end item.

DI-NDTI-80603A, Acceptance Test Procedure, CDRL A007

2.1.2.9 Engineering Drawings

The contractor shall provide Engineering drawings sufficient information to permit Government maintenance, modification, and engineering analysis of all manufactured items. The contractor shall provide data to the COTS component level (COTS subcomponent level not necessary). For any custom changes made to COTS items, the contractor shall provide Altered Item Drawings to document these changes.

DI-SESS-81003C, Commercial Drawings and Associated Lists, CDRL A006

2.1.3 TPS Acceptance Phase

The following subparagraphs detail the requirements for acceptance of the TPS. The contractor shall address all the required components of acceptance testing described below in the ATP identified in 2.1.2.8.

2.1.3.1 Test Program Set Acceptance Test

The contractor shall sponsor TPS Acceptance activities. This testing shall be completed in accordance with the Acceptance Test Procedure 2.1.2.8. The contractor shall combine verification of the test requirements in the functional testing with FCA/PCA activities as described in 0 and 2.1.3.5.

2.1.3.2 Acceptance Test Report

The contractor shall develop a Final Acceptance Test Report that addresses the acceptance of each TPS and each test system delivered as a part of this effort.

Acceptance Test Report, CDRL A009

2.1.3.3 Test Program Manual (TPM)

The contractor shall provide the Government with the final copy of the TPM ten days prior to the start of TPS acceptance testing. The Government will have the opportunity to review the manual and then validate the test procedures in the manual against the actual operation of the TPS software during acceptance testing. The contractor shall provide the final documents within two

(2) month of receipt of the Government’s comments.

Test Program Manual, CDRL A004

2.1.3.4 Functional Configuration Audit (FCA)

The FCA shall be held in conjunction with the Acceptance Test Activities and be performed to verify the TPS is accurate, complete, compatible, and the Configuration Item (CI) has achieved the performance and functional characteristics delineated in the requirements specifications. The

FCA shall be performed jointly by the government and the contractor at a mutually agreed upon time and location, with the government chairing the audit. The contractor shall document the results of the FCA after the audit and correct all audit discrepancies. The functional baseline shall be established upon completion of and government acceptance of the FCA.

2.1.3.5 Physical Configuration Audit (PCA)

The government and the contractor shall conduct the PCA jointly in conjunction with the TPS

Acceptance Testing and FCA, with the government chairing the audit. The PCA will verify the drawings reflect the "as built" configuration of all developed or modified portions of the hardware. The contractor shall document the results of the PCA after the audit. A product baseline will be established upon completion of and government acceptance of the PCA.

2.1.4 System and TPS Delivery and Installation

The contractor shall assume full product liability for damage during shipment to the customer and throughout the installation. The contractor shall be responsible for insuring that the correct parts are ordered and received in good condition.

2.1.4.1 Site Survey

The contractor shall conduct a pre-installation meeting at least one week prior to delivery with the user, applicable facility manager, and other personnel the facility manager deems necessary to ensure minimum disruption of normal operations during installation. The contractor shall examine the installation site to determine the conditions under which the work is to be performed. The Contractor shall review the necessary preparations with the Government.

2.1.4.2 Installation and site preparation

The contractor shall provide all labor, parts, tools, equipment, materials, and other items necessary to deliver, assemble, and install the test system and TPS. The contractor shall perform the actions of delivery, setup, and the demonstration of equipment functionality in such a manner as to have the least impact on shop production.

2.1.5 Test System and TPS Software

The contractor shall deliver all TPS software developed as a part of the project. The contractor shall deliver any software modifications required to the test system software (including calibration software updates). The Data rights established for the test system software shall remain unchanged.

2.1.6 Test System Hardware

The contractor shall identify to the Government any ancillary equipment required for use with the TPS and the test system to test the respective end-item that will not be provided with the

TPS.

2.1.7 Logistics Support and Training

The following paragraphs define the logistics support and training associated with this task.

2.1.7.1 Training

The contractor shall provide on-site demonstrations covering the operation of each type of TPS developed under this task following acceptance of the TPS and verification of the Test

Procedures Manual. The demonstrations shall be completed concurrent with delivery and on-site acceptance of the TPS.

2.1.7.2 Computer Program Identification Number (CPIN)

The contractor shall submit a CPIN request for each TPS Software Configuration Item. The contractor shall deliver the TPS software in accordance with T.O. 00-5-16 and 00-5-17.

Computer Program Identification Number, CDRL A010

2.1.8 Government Furnished Items

2.1.8.1 Government Furnished Information

The Government will provide all Technical Orders (TO), Overhaul Manuals, Test Equipment operation and maintenance manuals, and any other Government owned information as is feasible. Should some of the aforementioned information be unavailable to the Contractor (i.e.

“B” Distribution Statement TOs), the Government will advise the Contractor on status and availability of such data. The Contractor and Government will then negotiate an acceptable course for mitigating the limitations of data availability as necessary.

For access to these documents please e-mail

Don.hoover.1@us.af.mil

Brady.smith@us.af.mil

2.1.8.2 Government Furnished Equipment

The Government will provide two (2) ‘A’ condition assets to the contractor for functional and integration testing.

2.1.8.3 GFE Availability Risk Mitigation

As specified in Section 2.1.8.2, the Government intends to provide two ‘A’ condition assets to the contractor. However, there is a possibility that due to mission support issues for the warfighter, availability of such assets will be not possible, delayed or not within the Contractor’s proposed schedule. The Contractor shall use the proposed GFE risk mitigation plan specified in

Section L 3.1.3, to propose a GFE risk mitigation plan for TPS development of this Air Data

Computer Task Order.

For the purposes of this Air Data Computer Task Order, the Contractor shall assume that items numbered 1 and 2 in Appendix A are available at this time for functional and integration testing.

It shall be assumed that items number 3 and 4 in Appendix A are not currently available and will not be available in the foreseeable future.

2.1.9 Milestones

The following section describes the anticipated milestones for the TPS development.

mailto:Don.hoover.1@us.af.mil mailto:Brady.smith@us.af.mil

2.1.9.1 Requirements Review

As part of the requirements review, the Contractor shall develop a Traceability Matrix, per

Section 2.1. This matrix will be reviewed during this milestone. The I/O table identified in

Section 2.1.2.1 shall also be reviewed at this milestone.

2.1.9.2 Preliminary/Critical Design Review

The Contractor shall take into account the following factors to include, but not necessarily be limited to:

Complexity

Lack of Information

Availability of Documentation

Availability of Parts

Clarity of Data

Need for review of process with technician

These factors will determine the need for separate Preliminary Design Reviews and Critical

Design Reviews. Should it be deemed acceptable, these two milestones can be combined.

The PDR/CDR shall be a milestone/meeting to present the plan forward that the Contractor will make in development of the TPS. Any issues, risk, design factors, limitations, etc. will be presented at this meeting for review and/or approval of the Government.

2.1.9.3 Functional Configuration Audit

Details of this milestone can be found in Section 2.1.3.4. This milestone can be combined with the Physical Configuration Audit.

2.1.9.4 Physical Configuration Audit

Details of this milestone can be found in Section 2.1.3.5. This milestone can be combined with the Functional Configuration Audit.

2.1.9.5 Final Delivery/Selloff

The Contractor shall deliver, install, and provide any support, training, and maintenance instruction as required for each TPS. Final Delivery shall occur at Hill AFB, unless prior arrangements with the Government have been made in advance of the intended activity.

The Government estimates that the Period of Performance (PoP) for this effort will be 12 months and will utilize CLIN’s 0001, 0002, 0005, 0006, and 0007. If the contractor believes that other

CLIN’s should be utilized please reflect this in the Air Data Computer Task Order Pricing

Matrix.

Appendix A - List of End Items

Number Part Number National Stock # Noun

1 4007513-904 5998-01-004-4346 CCA, Air Data Computer A3

2 4007211-901 5998-00-259-2965 CCA, Air Data Computer A4/5

3 4007209-901 5998-00-259-2964 CCA, Air Data Computer A6

4 4007207-902 5998-01-071-8430 CCA, Air Data Computer A7