ARTS SOW--24 Mar 2011.pdf

24 March 2011

Statement of Work (SOW) for Advanced Radar/Electronic Warfare

Test Station (ARTS)

Prepared by

WR-ALC/GRNEA

AUTOMATIC TEST SYSTEMS DIVISION

460 RICHARD RAY BLVD STE 200

ROBINS AFB GA 31098

DISTRIBUTION STATEMENT A. Approved for public release: Distribution is unlimited.

THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK

Table of Contents

Table of Contents

1. SCOPE

2. APPLICABLE DOCUMENTS

2.1 Government Documents

2.1.1 Specifications, Standards, and Handbooks

2.1.2 Other Government Documents, Drawings, and Publications

2.2 Non-Government Publications

2.3 Order of Precedence

3. REQUIREMENTS

3.1 Program Management

3.1.1 Program Manager

3.1.2 Integrated Master Schedule (IMS)

3.1.3 Contractor Facilities

3.2 Program Reviews

3.2.1 Support of Reviews

3.2.2 Post-award Orientation Conference (PAOC)

3.2.3 Program Reviews

3.2.4 Technical Reviews

3.2.5 Technical Interchange Meetings

3.3 Systems Engineering

3.3.1 ARTS Station Requirements

3.3.2 Test Program Set (TPS) Requirements

3.4 Logistics

3.4.1 Technical Order (T.O.) Requirements

3.4.2 Provisioning

3.4.3 Training/Familiarization

3.4.4 Automated Computer Program Identification Numbers (ACPINs)

3.4.5 Request for Nomenclature

3.5 Testing and Evaluation

3.5.1 Design Analysis

3.5.2 Preproduction Test Procedures and Report

3.5.3 Production Acceptance Procedure and Report

3.6 Configuration Management and Control

3.6.1 Configuration Requirements

3.6.2 Engineering Change Proposals (ECPs)

3.6.3 Request for Deviation (RFD)

3.6.4 Engineering Data

3.6.5 Data Accession List

4. SECURITY INFORMATION

4.1 Base Access

4.2 Physical Security

Attachment A: List of LRUs Attachment B: List of User Locations Attachment C: CDRL Cross Reference

1. SCOPE

This SOW defines the tasks and support requirements for the procurement of the Advanced Radar/Electronic Warfare Test Station (ARTS) and associated Line Replaceable Unit (LRU) TPSs as described by Purchase Description PD10WRGBGBEA34, Revision A, hereafter referred to as the “PD”. This includes, but is not limited to the design, development, integration, documentation, testing/demonstration, and delivery of the ARTS stations, the self-test and calibration capabilities, LRU TPSs, and associated support data.

Attachment A identifies the list of LRUs of which ARTS must meet the testing requirements.

Those LRUs that shall have a TPS developed for execution on ARTS are identified and annotated in Attachment A. The LRU TPSs that will be used as part of the validation and verification testing of ARTS are also identified and annotated in Attachment A. The LRU TPS requirements listed in Attachment A are listed in prioritized sequence. TPS procurement for those LRUs annotated as “No TPS Required” in Attachment A will be a separate effort from this contract, but the ARTS must have the necessary hardware and software resources to meet the testing requirements of all LRUs listed in Attachment A.

2. APPLICABLE DOCUMENTS

The following documents are applicable to the SOW to the extent specified herein.

2.1 Government Documents.

2.1.1 Specifications, Standards, and Handbooks.

The following specifications, standards, and handbooks of the exact revision listed below form a part of this SOW to the extent specified herein.

DEPARTMENT OF DEFENSE SPECIFICATIONS

MIL-PRF-49506 Logistics Management Information

DEPARTMENT OF DEFENSE STANDARDS

EIA649 National Consensus Standard for Configuration Management MIL-STD-882D Standard Practice for System Safety

DEPARTMENT OF DEFENSE HANDBOOKS

MIL-HDBK-217F(2) Reliability Prediction of Electronic Equipment MIL-HDBK-470A Designing and Developing Maintainable Products and Systems MIL-HDBK-1568(1) Material and Processes for Corrosion Prevention and Control in

Aerospace Weapons Systems

2.1.2 Other Government Documents, Drawings, and Publications.

PURCHASE DESCRIPTIONS

PD10WRGBGBEA34 rev A Advanced Radar/Electronic Warfare (R/EW) Test Station (ARTS), dated 30 November 2010

DEPARTMENT OF DEFENSE MANUALS

TM-86-01K Air Force Technical Manual Contract Requirements TO 00-5-16 Software Managers and Users Manual for the USAF

Automated Computer Program Identification Number System

(ACPINS)

DATA ITEM DESCRIPTIONS (DIDs)

DI-MGMT-80368 Status Reports DI-MGMT-81650 Integrated Master Schedule DI-ADMN-81249A Conference Agenda DI-ADMN-81250A Conference Minutes DI-SESS-81757A Design Review Information Package DI-IPSC-81431A System/Subsystem Specification (SSS) DI-MISC-80508B Technical Report – Study/Services DI-IPSC-81441A Software Product Specification DI-IPSC-81448A Firmware Support Manual DI-QCIC-80278B Calibration/Measurement Requirements Summary (CMRS) DI-MCCR-80700 Computer Software Product End Items DI-NDTI-80566A Test Plan DI-NDTI-80809B Test/Inspection Report DI-ATTS-80285C Engineering Support Data DI-MCCR-80491A Computer Software Flowchart TM-86-01 Technical Order DI-ALSS-81529 Logistics Management Information (LMI) Data Product(s) DI-MGMT-81453A Data Accession List (DAL) DI-ALSS-81557 Supplemental Data for Provisioning (SDFP) DI-ILSS-80872 Training Material DI-MISC-81454B Automated Computer Program Identification Number (ACPIN) Data and Control Record DI-CMAN-81254A Request for Nomenclature (DD61) DI-CMAN-80639C Engineering Change Proposal (ECP) DI-CMAN-80640C Request for Deviation (RFD) DI-SESS-81000D Product Drawings and Associated Lists

(Unless otherwise indicated, copies of the above specifications, standards, and handbooks are available from the Standardization Document Order Desk, 700 Robbins Avenue, Building 4D, Philadelphia PA 19111-5094.)

2.2 Non-Government Publications.

The following documents form a part of this document to the extent specified herein.

Reliability Information Analysis Center (RIAC)

NPRD-95 Nonelectronic Parts Reliability Data 1995

(Application for copies should be addressed to Reliability Information Analysis Center, 100 Seymour Rd., Suite C 101, Utica, NY 13502-1348.)

2.3 Order of Precedence.

In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

3. REQUIREMENTS

3.1 Program Management.

3.1.1 Program Manager.

The contractor shall identify to the government and maintain a single point of contact (Program Manager) for all matters under this contract. The contractor shall also ensure that all program management personnel assigned to the program shall be available, as required, to meet program objectives. The contractor shall prepare a monthly contractor’s progress, status and management report. This report shall identify the status of all portions of the contract and shall be identified in the contractor's milestone chart. The program report shall include all events such as reviews, audits, tests, identification, and delivery of the contract line items.

The contractor shall track program progress and document in the status report any activity and/or deliverable which will not be achieved as scheduled, citing the cause, contributing factors, impacts, and resolutions to get back on schedule.

(DI-MGMT-80368A, Status Report)

3.1.2 Integrated Master Schedule (IMS).

The contractor shall implement and maintain an IMS for this program. A baseline IMS shall be developed at the start of the program. A current IMS shall be developed and maintained throughout the program, using the original baseline schedule as an unchanging reference. The IMS shall be provided in Microsoft Project format as an attachment to the monthly status report (see 3.2.7).

(DI-MGMT-81650, Integrated Master Schedule)

3.1.3 Contractor Facilities.

The contractor shall arrange for full access to applicable contractor facilities and offices by government representatives conducting any business, making observations, or performing inspections required by public law or by this contract.

3.2 Program Reviews.

The contractor shall document all work performed, track the program's progress, and complete all work related to this effort. Any non-critical administrative and technical issues that arise shall primarily be resolved through phone, e-mail, and/or teleconference, while more critical issues shall be addressed through formal reviews, meetings, and audits, described in the following paragraphs. The contractor shall publish an agenda for all meetings and conferences specified in section 3. The contractor shall request from the government any items or issues to be discussed or presented at the meetings, and shall include such items in the agenda. Conference agendas shall be submitted not less than five working days prior to any meeting. The contractor shall provide a written record of the discussions, decisions, and action items identified at each meeting.

(DI-ADMN-81249A, Conference Agenda) (DI-ADMN-81250A, Conference Minutes)

3.2.1 Support of Reviews.

The contractor shall participate in and support all reviews, audits, and meetings as identified in this SOW and/or requested by the Procuring Contracting Officer (PCO).

3.2.2 Post-award Orientation Conference (PAOC).

The contractor shall attend a post-award orientation conference that will be conducted within approximately 60 days after contract award. The conference will be held at Robins AFB, GA.

3.2.3 Program Reviews.

The contractor shall conduct two Program Management reviews per year at Robins AFB. The PMRs can be conducted concurrently with other reviews, if feasible.

3.2.4 Technical Reviews.

The contractor shall conduct a technical review in accordance with DD1423, Design Review Information Package, on the first preproduction test station and all TPSs. The technical reviews shall be held at Robins AFB, GA. Each technical review shall consist of the following events (listed in the order in which they will occur):

System Requirements Review (SRR) Preliminary Design Review (PDR) Critical Design Review (CDR) Test Readiness Review (TRR)

3.2.4.1 Preproduction Station Technical Reviews.

One technical review shall be conducted on the first preproduction test station.

3.2.4.2 TPS Technical Reviews.

The TPSs, identified in Attachment A to this Statement of Work, are organized into four groups as follows:

Group I Group II

NSN 5865-01-551-7118 NSN 5865-01-545-2484

NSN 5865-01-553-2000 NSN 5865-01-257-2789

NSN 5865-01-545-4411 NSN 5865-01-257-1341

NSN 5865-01-264-3364

NSN 5895-01-497-7220

NSN 5868-01-516-0698

Group III Group IV

NSN 5865-01-331-2557 NSN 5865-01-240-3755

NSN 5865-01-362-6438 NSN 5895-01-240-0091

NSN 5865-01-240-3754 NSN 5865-01-257-1244

NSN 5865-01-256-2544 NSN 5865-01-258-7062

NSN 5895-01-239-8983 NSN 5865-01-258-1133

NSN 5865-01-258-1148

The contractor may separate a TPS group into subgroups, if desired. However, a group shall not be separated into more than two subgroups, and there shall be no less than two TPSs in each subgroup. One technical review shall be conducted for each group. Should a group be separated into two subgroups, the contractor shall conduct a technical review for each subgroup.

The contractor shall prepare agendas for each technical review event as well as minutes for each event in accordance with DD1423, Conference Agenda (SOW paragraph 3.2), and DD1423, Conference Minutes (SOW paragraph 3.2). No later than seven working days subsequent to the conclusion of each event, the government will either approve or disapprove the event in writing.

The contractor shall not proceed to the next event within the technical review without government approval.

(DI-SESS-81757A, Design Review Information Package)

3.2.5 Technical Interchange Meetings.

The contractor and/or the government can request that a Technical Interchange Meeting (TIM) be held to resolve any managerial and/or technical issues/concerns that may arise during the performance period of this contract. These meetings shall be informal working sessions whose results and actions shall be documented in TIM minutes. The contractor shall prepare the minutes, but the party who called the meeting shall prepare the agenda.

3.3 Systems Engineering.

The ARTS station and associated TPSs shall meet the requirements of the PD and this SOW.

3.3.1 ARTS Station Requirements.

The contractor shall develop, integrate, document, successfully demonstrate through validation and verification, and deliver ARTS stations, to include three (3) preproduction stations with confidence test, station self-test capability, and on-station calibration capability. TPS requirements pertaining to the ARTS stations are defined in section 3.3.2 of this SOW.

3.3.1.1 ARTS Hardware Requirements.

The ARTS shall provide the necessary hardware and an interface that will accept ITAs or other interfacing technique to meet the testing requirements of the LRUs as specified in Attachment A and the requirements of the PD. The functional allocation and design specifications shall be derived by the contractor via analysis of the testing and interface requirements of the LRUs listed in Attachment A and the requirements of the PD. The contractor shall document all of the system and subsystem specifications of the ARTS in a System/Subsystem Specification document. The contractor shall document via a Technical Report the results of the requirements analysis referenced in this paragraph and the analytical data for those verifications by method of analysis IAW Section 4.0 of the PD.

(DI-IPSC-81431A, System/Subsystem Specification) (DI-MISC-80508B, Technical Report, Study/Services)

3.3.1.2 ARTS Software Requirements.

The ARTS shall provide the necessary software environment to meet the requirements of the PD.

The contractor shall document all aspects of the system software of the ARTS in a Software Product Specification. This includes, but is not limited to, all requirements and functionality identified in Section 3.2.6 of the PD. The contractor shall document via a Firmware Support Manual, where applicable, required aspects of any and all custom (non-COTS) firmware that is used as a part of ARTS. This applies to read only memories (ROMs), Programmable ROMs (PROMs), Erasable PROMs (EPROMs), and any other firmware devices (i.e. EEPROMs, FPGAs, etc).

(DI-IPSC-81441A, Software Product Specification) (DI-IPSC-81448A, Firmware Support Manual)

3.3.1.2.1 ARTS Maintenance Programs.

The contractor shall develop, integrate, demonstrate, test, and deliver a station confidence test, a station self-test TPS, and a station calibration TPS for ARTS. These shall meet the requirements and be subjected to testing IAW the PD and section 3.3.2 of this SOW. The contractor shall also develop and deliver a Calibration/Measurement Requirements Summary (CMRS) detailing the measurement requirements of the calibration TPS and ensuring traceability to the National Institute of Standards and Technology (NIST).

ARTS calibration requirements outside of the PATEC Core capabilities shall be supported by PATEC augmentation. The contractor shall design, integrate, test, and deliver any PATEC augmentation required to meet the calibration testing requirements of ARTS. The contractor shall identify the need for PATEC augmentation and shall present design specifics as part of the Design Reviews for the Calibration TPS. The PATEC augmentation shall be considered part of the Calibration TPS in regards to design and data requirements and delivery quantities.

(DI-QCIC-80278B, Calibration and Measurement Requirements Summary)

3.3.1.2.2 System Software Data Delivery and Media.

The contractor shall deliver the final system software Computer Software Configuration Items (CSCIs) on separate CD/DVD-ROMs, which shall be compatible with the CD/DVD-ROM reader used on the ARTS.

(DI-MCCR-80700, Computer Software Product End Items)

3.3.2 Test Program Set (TPS) Requirements.

TPSs consist of the test software, interface devices and associated hardware, and associated documentation required to test UUTs on the ARTS station. The TPS requirements identified in the following subsections also apply to the station confidence test, station self-test TPS, and station calibration TPS as described in section 3.3.1.2.1. Note that certain TPSs are associated with the preproduction effort, as specified in Attachment A. The contractor shall develop and “ship in place” ATE Development Environments (ADEs) to be used for TPS development efforts. The contractor shall deliver quantities to satisfy the total requirement as stated in the contract. These ADE systems shall be delivered to government POC at conclusion of contract.

3.3.2.1 TPS Procurement.

The contractor shall design, develop, document, successfully demonstrate, and deliver TPSs for those LRUs annotated as TPS required in Attachment A. Each LRU TPS shall be developed for execution on the ARTS and shall provide Unit Under Test (UUT) functional testing and fault detection and isolation in accordance with the PD and this SOW.

The part numbers (P/N) listed in Attachment A reflect the existing UUT configurations at the time of contract award. Upon receipt of the GFE UUT, the contractor shall verify the exact configuration of the UUT and the associated technical documentation. Should the contractor identify a UUT and/or documentation that are not the same configuration as listed in Attachment A, it shall promptly notify the point of contact in the government’s Contracting Office.

3.3.2.2 Unit Under Test (UUT) Interface Test Adapters (ITAs).

To test each UUT, the contractor shall design, fabricate, and deliver appropriate ITAs, along with their associated cables, support hardware, and documentation. Existing legacy holding fixtures for the UUTs shall be reused. The contractor shall design each ITA to test as many UUTs as possible without significantly increasing the footprint of the ITA. Each ITA may host as many TPSs as feasible to benefit from commonality; however, each TPS must be independent and completely documented for stand-alone operation.

ITAs shall be designed to be "passive" to the maximum extent possible IAW the PD.

Government approval is required for the development of electronically active ITAs. Any active ITA candidates shall be identified by the contractor for approval no later than PDR, and government approval shall be established prior to CDR.

The contractor shall demonstrate each ITA's compliance during Final Integration Acceptance Test (FIAT) with the associated TPS(s) and documentation. Successful ITA compliance will comprise, as a minimum, the end-to-end running of both the ITA self-test and the corresponding UUT TPS(s) on the ARTS, without encountering any failures or interruptions.

3.3.2.3 TPS Software.

The contractor shall produce all necessary software to ensure complete operation and maintenance of all TPSs and provide related machine, source, object, and executable code. All software and/or firmware shall be designed, produced, documented, tested, and delivered to provide thorough UUT fault isolation and repair capabilities by implementing LRU "functional" and SRU "diagnostic" testing to the level required in the PD. Existing ATLAS code from the legacy TPSs shall not be reused. All TPS or firmware code written shall be capable of normal operation, despite various CPU speeds on the ARTS. Any firmware developed in support of the TPS shall be in the native language of the chip set used. The contractor shall document via a Firmware Support Manual, where applicable, required aspects of any and all custom (non- COTS) firmware that is used as a part of any TPS. This applies to read only memories (ROMs), Programmable ROMs (PROMs), Erasable PROMs (EPROMs), and any other firmware devices (i.e. EEPROMs, FPGAs, etc).

(DI-IPSC-81448A, Firmware Support Manual)

3.3.2.3.1 Fault Detection and Fault Isolation (FD/FI).

The contractor shall demonstrate TPS Fault Detection and Fault Isolation (FD/FI) capabilities by inserting faults into the UUTs. The contractor will provide the government with an LRU fault list for each TPS, each containing at least 25 fault insertion candidates, and conforming to guidelines set forth in the ESD. The contractor will also provide the government an ITA fault list containing at least 10 faults. During Final Integration Acceptance Testing (FIAT), the government will select up to 10 different independent non-destructive faults from each of the TPS LRU fault list and 3 independent non-destructive ITA faults, or may substitute from both lists at its discretion. The government also reserves the right to increase the number of fault insertions up to 25 for the LRU and 10 for the ITA and may include non-destructive faults outside the contractor’s list of 25 or list of 10. The contractor shall insert these faults into the UUT/ITA as prescribed in the Test Plan established in paragraph 3.3.2.5.1. The faults shall be detected and isolated IAW the PD. After the successful completion of the fault detection/isolation routines, the faults shall be removed and the TPS shall be re-run commencing at the point of failed test entry point at the operator and government discretion. After the successful completion of the fault detection/isolation routines the TPS shall be re-run successfully end-to-end.

FD/FI capability shall be provided to the next replaceable level of the UUT. The following fault analysis criteria shall be used:

a. Ability to determine if the UUT is performing within its specified set of operational parameters. (i.e. application of functional or diagnostic testing)

b. Fault isolation capability shall apply to those faults for which isolation is allowed by both the physical and electrical design of the unit.

c. Faults shall be considered individually and shall be permanent. (i.e. either open or short. Intermittent faults shall not be included).

d. The level of fault isolation shall be to the smallest ambiguity group possible using electronic measurements during normal UUT operation and must meet the requirements established in the PD.

3.3.2.4 TPS Logistics.

3.3.2.4.1 UUT Availability/Maintenance.

At least one (1) of each UUT listed in Attachment A shall be made available to the contractor for dedicated use in TPS development/integration. Use of these UUTs will be coordinated with the government. The contractor shall contact the government regarding all damages and/or failures encountered with the UUTs. The government shall be responsible for returning the UUT to a serviceable condition or replacing it with a serviceable asset.

3.3.2.4.2 Acquiring Government Documentation.

The government will coordinate the contractor’s data requirements of the UUT needed for TPS development. The government will provide the contractor access to all the available data and the contractor shall be responsible for the collection, management, and disposition of the data.

3.3.2.4.3 Configuration Management.

The TPS software, hardware, technical documentation, and engineering data shall conform to the contractor’s Configuration Management (CM) policies and procedures.

3.3.2.5 TPS Test, Acceptance, and Delivery.

3.3.2.5.1 TPS Final Integration Acceptance Testing (FIAT).

Final Integration Acceptance Testing (FIAT) shall be conducted on the first production unit of each TPS, to demonstrate that they meet the design criteria cited in this SOW, using contractor-prepared and government-approved Test Plans/Procedures. The contractor shall notify the government no later than 30 days prior to the scheduling of each FIAT. FIAT will consist of a Functional Configuration Audit (FCA) and Physical Configuration Audit (PCA) for each TPS at the contractor’s facility. These audits may be conducted and scheduled by groups of TPSs when possible to facilitate progress, and illustrate consistency and commonality among TPS designs. All PCAs shall visually inspect and compare the final TPS's ITA and cable sets to fabrication schematics, along with ARTS install/interconnect drawings. FCAs will functionally check the entire TPS for operational integrity, including Fault Detection/Fault Isolation IAW 3.3.2.3.1 and the PD. As a minimum, FIAT shall include:

a. Verification of ARTS calibration and execution of self-test.

b. Complete installation of all TPS(s) files and programs onto the ARTS.

c. End-to-end execution of the ITA’s alignment and self-test if applicable.

d. End-to-end execution of the appropriate UUT TPS(s).*

e. Fault-isolation execution of the appropriate UUT TPS(s).*

f. End-to-end re-execution of the appropriate UUT TPS(s).

*Each TPS shall be able to identify 100% of all detectable faults.

FIAT will be conducted using preproduction ARTS stations. The contractor shall apply the appropriate ITAs, corresponding UUTs, Operator Instructions (OI), and Test Program (TP) Software. The UUT used will have been provided by the government as per section 3.3.2.4.1.

The contractor shall document each TPS's FIAT outcomes and findings on separate Test Reports and provide them to the government per paragraph 3.3.2.5.2.

(DI-NDTI-80566A, Test Plan)

3.3.2.5.2 Test Reports.

The contractor shall provide a Test Report for each TPS, which includes a record of all work performed and accomplished during the associated FIAT, along with results and historical information (i.e. location, personnel, resources, time, and data). New reports shall be generated for each repeated FIAT, in the event that the TPS in question was unable to pass the initial FIAT without subsequent rework.

(DI-NDTI-80809B, Test/Inspection Reports)

3.3.2.5.3 TPS Delivery.

The contractor shall manufacture and deliver multiple TPS copies to satisfy the total requirement as stated in the contract. After each TPS production group (i.e. batch of TPS copies) is completed, they will be shipped to the organizations specified in Attachment B. Each TPS copy will be shipped with its respective ITA, cables, and any ancillary components.

(DI-MCCR-80700, Computer Software Product End Items)

3.3.2.5.4 Engineering Support Data (ESD) and Detailed (Diagnostic) Flowchart.

The contractor shall prepare, maintain, and deliver an ESD and detailed diagnostic flowchart for each TPS. The ESD shall provide all the necessary design, manufacturing, testing and quality assurance details to enable the government to perform organic development, operation, maintenance, modification, procurement, and manufacture of the TPSs. The detailed diagnostic flowchart shall depict processing being performed in the sequence of operation and all branch and decision points, which fulfill the objectives of each of the major steps of the program.

Specific sections of this document will address and support TPS requirements generation and TPS engineering drawing sets, which shall be separately produced and delivered to facilitate understanding and use of the TPS. The ESD shall be developed incrementally, with appropriate sections made available to the government for review at corresponding reviews specified in paragraph 3.2.3. Government approval will be necessary for any source control items identified.

(DI-ATTS-80285C, Engineering Support Data) (DI-MCCR-80491A, Computer Software Flowchart)

3.4 Logistics.

3.4.1 Technical Order (T.O.) Requirements.

The contractor shall submit Operation and Operator Maintenance Instruction; Maintenance and Overhaul; and Illustrated Parts Breakdown (IPB) manuals in accordance with TM-86-01, Air Force Technical Manual Contract Requirements. Separate Technical Orders shall be created for the ARTS station and for each TPS.

(TM-86-01, Technical Order)

3.4.1.1 T.O. Verification.

Technical order verification shall be in accordance with TM-86-01.

3.4.2 Provisioning.

The contractor shall identify and recommend logical spare/repair parts sufficient to meet system/equipment operation and supportability in accordance with the Air Force Initial Provisioning Performance Specification (IPPS). MIL-PRF-49506 should be used as a guide.

Format must be consistent with the existing government Provisioning data system (D220). This data shall be identified for the ARTS station and for the TPSs.

(DI-ALSS-81529, Logistics Management Information (LMI) Data Product(s)) (DI-ALSS-81557, Supplemental Data For Provisioning (SDFP))

3.4.3 Training/Familiarization.

The contractor shall provide on-site training to each customer location listed in Attachment B.

The Government will order the on-site training in a delivery order issued against the contract.

The contractor shall provide 40 hours of training for up to ten (10) people, and provide training materials which shall be available to the customer at the time of the scheduled training. The training topics shall include materials required of the student, operating instructions, routine inspection, calibration, troubleshooting, and repair.

(DI-ILSS-80872, Training Materials)

3.4.4 Automated Computer Program Identification Numbers (ACPINs).

In order for the contractor to request a Computer Program Identification Number (CPIN) from the government, all custom and/or commercial software packages shall be labeled independently and described thoroughly on AF Form 1243s according to T.O. 00-5-16 guides. The contractor shall assign a CPIN for each system software CSCI and each TPS, and any other software configuration entity to be delivered to the government to support the ARTS testing of the UUTs in Attachment A.

(DI-MISC-81454B, Automated Computer Program Identification Number Data and Control Record)

3.4.5 Request for Nomenclature.

Once the baseline configuration for ARTS and the ITA for each respective TPS has been established, the contractor shall submit completed DD Form 61 (where applicable) to request nomenclature assignment for ARTS and each ITA.

(DI-CMAN-81254A, Request for Nomenclature (DD61))

3.5 Testing and Evaluation.

3.5.1 Design Analysis.

A design analysis of the ARTS system and each subsystem shall be performed to verify compliance with this SOW and the PD and ensure the testing and interface requirements of the LRUs listed in Attachment A are met. An initial design analysis shall be provided at the SRR;

updated versions of the analysis shall be provided at the PDR and CDR, at the start of preproduction testing, and with the preproduction test report.

(DI-MISC-80508B, Technical Report – Study/Services)

3.5.2 Preproduction Test Procedures and Report.

Three preproduction units of the ARTS station shall be developed. The contractor shall develop detailed preproduction test procedures via a test plan which must be approved by the government. For the first preproduction unit, the test procedures shall address all station requirements identified in the PD and this SOW, as well as station confidence, self-test, and calibration TPSs. Test procedures for the second preproduction unit shall consist of executing station confidence, self-test, and calibration TPSs at a minimum. Test procedures for the third preproduction unit shall include the procedures for TPS FIAT as noted in paragraph 3.3.2.5.1, which shall test the first three (3) TPSs as annotated in Attachment A. The test procedures shall include data record sheets, charts, graphs, identification of test instruments by manufacturer, model number, and serial number.

After approval of preproduction test procedures, the contractor shall schedule the testing to be conducted. The contractor shall notify the government of the dates and times of preproduction testing 30 days prior to the start of testing. Preproduction testing of all three preproduction testers will be performed at the contractor’s facility. The contractor shall submit a separate test report for each preproduction unit upon completion of the preproduction testing for the respective preproduction unit.

Upon government acceptance of the preproduction units, the units shall be considered to have been “shipped in place” and shall remain at the contractor’s facility to serve as manufacturing standards and to facilitate TPS development. The government will advise the contractor of the shipping addresses for the preproduction units close to the expiration date of the contract.

(DI-NDTI-80566A, Test Plan) (DI-NDTI-80809B, Test/Inspection Report)

3.5.3 Production Acceptance Procedure and Report.

The contractor shall test each production ARTS station by successfully executing the government-approved end-to-end station confidence test and station self-test. The contractor shall enclose an acceptance test report for each production item.

(DI-NDTI-80809B, Test/Inspection Report)

3.5.3.1 Production Delivery and Installation.

The contractor shall perform delivery and setup of each production ARTS station at the locations identified in Attachment B. This shall include the physical transportation, unpacking, installation, and setup of the station(s) to include execution of station confidence test and station self-test. The contractor shall ensure that the production unit(s) is/are ready for operational use upon completion of delivery and installation.

3.6 Configuration Management and Control.

3.6.1 Configuration Requirements.

After the preproduction item acceptance, the contractor shall establish the configuration baseline for ARTS. The accepted preproduction items shall serve as the manufacturing standard.

3.6.2 Engineering Change Proposals (ECPs).

After the master drawing baseline is established, the contractor shall incorporate all changes via approved ECPs.

(DI-CMAN-80639C, Engineering Change Proposal (ECP))

3.6.3 Request for Deviation (RFD).

The contractor shall prepare an RFD whenever a departure from the contractually-specified baseline is proposed for a specific number of units or for a specific time.

(DI-CMAN-80640C, Request for Deviation (RFD))

3.6.4 Engineering Data.

The contractor shall develop, produce, and maintain a Technical Data Package (TDP) that accurately depicts the final product. The TDP shall provide the necessary design, engineering, manufacturing, testing, and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product, without additional design engineering effort or recourse to the original design activity. Product data shall reflect the approved, tested, and accepted configuration of the defined delivered item. All engineering product definition data created as a result of this contract shall be considered a part of the TDP. This data includes, but is not limited to CAD data, models and model based definition data sets, and Gerber data. The TDP requirement applies to the ARTS station and each TPS.

(DI-SESS-81000D, Product Drawings and Associated Lists)

3.6.4.1 Engineering Data Guidance Conference.

The contractor shall support and co-chair a Guidance Conference for engineering data within 60 days after contract award to be held at Robins AFB, GA. The Conference shall be convened on a date agreed upon by the government and the contractor. The contractor shall prepare an agenda and record the minutes of the Guidance Conference. The contractor shall address, discuss, and provide status on the following:

a. Understanding of all Contract Data Requirements List (CDRL) requirements, applicable Data Item Descriptions (DIDs), specifications and standards.

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

d. The contractor's drafting practices, procedures, and TDP drawing formats.

e. The contractor's quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.

f. The role of subcontractors and vendors who may deliver TDP documents under this contract.

g. The contractor's configuration management system, including methods for releasing documents, approving documents, and incorporating changes into documents.

h. Digital TDP deliverables.

Note: The Guidance Conference may be held in conjunction with other meetings or conferences.

3.6.4.2 In-Process Review (IPR) of the TDP.

The contractor shall support and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP. The review shall be held at Robins AFB, GA at a date to be determined by the government. The IPR shall be conducted only after the contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality so that government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 50 percent completion point and, when possible, shall be held in conjunction with other reviews (e.g., PDR or CDR). The contractor shall notify the government a minimum of 30 days prior to the anticipated date of completion. The IPR shall focus on the contractor's progress in the preparation of the TDP. The contractor shall support and provide the necessary resources: meeting agenda, conference room if necessary, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The contractor shall correct all discrepancies identified in the IPR. All subcontractor and vendor data shall be made available for review. If the quantity of subcontractor or vendor data is of sufficient magnitude, the government may schedule a separate IPR at the subcontractor's or vendor's facility.

3.6.4.3 Relationship of the Contractor with Subcontractors and Vendors.

The contractor shall levy on subcontractors and sub vendors the same requirements for TDPs as are levied on them by this contract. This requirement shall apply at all tiers of subcontractor/vendor levels associated with the program.

3.6.4.4 Engineering Data Updates and Revisions.

The contractor shall (and shall cause subcontractors and vendors to) update and maintain engineering data for the item(s) designed, developed, modified, and produced by this contract for the life of this contract and shall incorporate all changes in accordance with the following:

a. All engineering changes shall be incorporated into the applicable engineering data within 90 days after engineering release and government concurrence or at intervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.

b. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review.

c. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of final media (this includes all Engineering Orders (EOs) generated as a result of the preliminary data review).

3.6.5 Data Accession List.

The contractor shall maintain an overall project Data Accession List. This list shall identify all data that the contractor has developed during the performance period of this SOW. The government will have full access to this data, and may request copies of the data as desired.

(DI-MGMT-81453A, Data Accession List)

4. SECURITY INFORMATION

4.1 Base Access.

Entrance onto the installations identified in Attachment B may differ. The government will identify a point of contact for each installation subsequent to contract award.

4.2 Physical Security.

The contractor shall be responsible for safeguarding all government property provided for contractor use. At the end of each work period, contractor personnel shall ensure that all equipment and materials provided for their use shall be secured.

Attachment A: List of LRUs

LRU NAME NSN PART NO. TPS Requirement

TWF R/P (RP) 5865-01-551-7118 435097-6

TPS Required p/o ARTS testing Group I

BAND 8 RFS 5865-01-553-2000 435029-12

TPS Required p/o ARTS testing Group I

JAMMER LOGIC B (JLB) 5865-01-545-4411 442600-6

TPS Required p/o ARTS testing Group I

JAMMER LOGIC A (JLA) 5865-01-545-2484 442590-6

TPS Required

Group II

BAND 7 RFS 5865-01-257-2789 442001-3

TPS Required

Group II

BAND 6 RFS 5865-01-257-1341 442000-3

TPS Required

Group II

ENCODER 5865-01-264-3364 440314-4

TPS Required

Group II

GENERATOR, REFERENCE

SIGNAL (WAVEFORM

GENERATOR, WFG-8)

5895-01-497-7220 435030-7 TPS Required

Group II

DF ENCODER (DFE) 5868-01-516-0698 0065001-7

TPS Required

Group II

BAND 5 AFT TX (TX5A) 5865-01-331-2557 435098-6

TPS Required

Group III

BAND 6 TX (TX6) 5865-01-362-6438 001-006822-011

TPS Required

Group III

BAND 7 TX (TX7) 5865-01-240-3754 001-006824-006

TPS Required

Group III

RX BANDS 4-8 5865-01-256-2544 435019-5

TPS Required

Group III

FREQ CHANNELIZER (FCH) 5895-01-239-8983 447719-1

TPS Required

Group III

CONT INTERFACE UNIT

(CIU)

5865-01-258-1148 442654-4 TPS Required

Group III

BAND 6 DRIVER (DR6) 5865-01-240-3755 001-006821-006

TPS Required

Group IV

BAND 7 DRIVER (DR7) 5895-01-240-0091 001-006823-006

TPS Required

Group IV

ADVANCED TRACKING

UNIT (ATU)

5865-01-257-1244 442655-4 TPS Required

Group IV

RX THRESHOLD CONTROL

(RTC)

5865-01-258-7062 435034-5 TPS Required

Group IV

BANDS 4/5 RFS 5865-01-258-1133 435026-8

TPS Required

Group IV

RECEIVER,

COUNTERMEASURE (IR-5)

5865-01-454-0015 440313-5 TPS Required

Group IV

BAND 8 DRIVER/TX

(DR/TX8)

5865-01-240-0092 001-006812-011 TPS Required

Group V

BAND 5 FWD 5865-01-257-2861 435025-4

TPS Required

Group V

BAND 4 FWD TX 5865-01-256-6556 435023-4

TPS Required

Group V

BAND 4 AFT TX 5865-01-258-7063 435024-7

TPS Required

Group V

BAND 7 ADR (ADR7) 5821-01-239-9984 0062001-3

No TPS Required.

Station functionality only

BAND 6 TX ANT AFT (TA6A) 5985-01-217-7376 0072001-2

No TPS Required.

Station functionality only

RX BANDS 1-3 5865-01-258-7061 435018-6

No TPS Required.

Station functionality only

BAND 8 TX ANT AFT (TA8A) 5985-01-240-8402 0077001-2

No TPS Required.

Station functionality only

BAND 8 TX ANT FWD (TA8F) 5985-01-240-3271 0078001-5

No TPS Required.

Station functionality only

BANDS 6/7/8 ADR

(ADR6-8)

5985-01-240-4224 0064001-6 No TPS Required.

Station functionality only

BAND 6 TX ANT FWD (TA6F) 5985-01-217-7425 0073001-2

No TPS Required.

Station functionality only

BAND 6 ADR (ADR6) 5985-01-238-7922 0061001-2

No TPS Required.

Station functionality only

BAND 7 TX ANT (TA7) 5985-01-335-4937 0074002-3

No TPS Required.

Station functionality only

BAND 8 ADR (ADR8) 5985-01-240-4223 0063001-3

No TPS Required.

Station functionality only

Attachment B: List of User Locations

Unit Address

Dyess AFB Bldg 5005

542 2nd Street Dyess AFB, TX 79607

Ellsworth AFB

28 MXG

1750 Bergstrom Dr.

Ellsworth AFB, SD 57706

Georgia Air National Guard (GaANG)

116 MXS

Bldg 645

740 Page Rd Robins AFB, GA 31098

WR-ALC Depot

402 EMXG

Bldg 645

740 Page Rd Robins AFB, GA 31098

Attachment C: CDRL Cross Reference

Applicable

DID

DID Title

SOW

Paragraphs Applicability

Station TPS DI-MGMT-80368 Status Reports 3.1.1 X X

DI-MGMT-81650

Integrated Master Schedule

(IMS)

3.1.2 X X

DI-ADMN-81249A Conference Agenda 3.2, 3.6.4.1, 3.6.4.2

X X

DI-ADMN-81250A Conference Minutes 3.2, 3.6.4.1, 3.6.4.2

X X

DI-SESS-81757A

Design Review Information Package

3.2.4 X X

DI-IPSC-81431A

System/Subsystem Specification (SSS)

3.3.1.1 X

DI-MISC-80508B

Technical Report – Study/Services

3.3.1.1, 3.5.1 X

DI-IPSC-81441A Software Product Specification 3.3.1.2 X DI-IPSC-81448A Firmware Support Manual 3.3.1.2, 3.3.2.3 X X

DI-QCIC-80278B

Calibration/Measurement Requirements Summary

(CMRS)

3.3.1.2.1 X

DI-MCCR-80700

Computer Software Product End Items

3.3.1.2.2, 3.3.2.5.3 X X

DI-NDTI-80566A Test Plan 3.3.2.5.1, 3.5.2 X X

DI-NDTI-80809B Test/Inspection Report 3.3.2.5.2, 3.5.2, 3.5.3

X X

DI-ATTS-80285C Engineering Support Data 3.3.2.5.4 X

DI-MCCR-80491A Computer Software Flowchart 3.3.2.5.4 X

TM-86-01 Technical Order 3.4.1 X X

DI-ALSS-81529

Logistics Management Information (LMI) Data Product(s)

3.4.2 X X

DI-MGMT-81453A Data Accession List (DAL) 3.6.5 X X

DI-ALSS-81557

Supplemental Data for Provisioning (SDFP)

3.4.2 X X

DI-ILSS-80872 Training Material 3.4.3 X

DI-MISC-81454B

Automated Computer Program Identification Number (ACPIN) Data and Control Record

3.4.4 X X

DI-CMAN-81254A Request For Nomenclature 3.4.5 X X

(DD61)

DI-CMAN-80639C

Engineering Change Proposal

(ECP)

3.6.2 X

DI-CMAN-80640C Request for Deviation (RFD) 3.6.3 X

DI-SESS-81000D

Product Drawings & Associated Lists

3.6.4 X X