Attachment 1 - ATSSI II Draft PWS.docx

PERFORMANCE WORK STATEMENT (PWS)

FOR

AUTOMATED TEST SYSTEM SUSTAINMENT INITIATIVE II (ATSSI II)

PRODUCT SUPPORT SUSTAINMENT SOLUTIONS

for

Ogden Air Logistics Complex

Period of Performance:

Revision Date: 2 April 2020

Table of Contents

Introduction Purpose The purpose of this effort is to support Ogden Air Logistics Complex’s (OO-ALC) Automated Test System Sustainment Initiative (ATSSI) program for the continued development and sustainment of a Depot Technology infrastructure supportive of OO-ALC mission to perform critical test functions important to the ongoing operational safety, suitability, and effectiveness of multiple Air Force weapon systems/subsystems. This depot infrastructure is referred to as the Automated Test System Sustainment Initiative II (ATSSI II). The ATSSI II infrastructure solution provides, but is not limited to the integration, update, and consolidation of processor-based test stations (i.e., Automated Test Systems (ATS)), test fixtures, Test Program Sets (TPS), database repositories, analytical software tools, the implement the Integrated Master Plan (IMP) (See Attachment B), and associated network communication functions. Additionally, the ATSSI II will resolve current system obsolescence and performance issues while providing significant efficiency and cost improvements.

This Performance Work Statement (PWS) defines the ATSSI II activities in support of organizations within the OO-ALC and 416th Supply Chain Management Squadron at Hill Air Force Base (AFB). The customer will be referred to hereafter as the “Government.” References to the Government in this PWS may involve Air Force Sustainment Center (AFSC), Air Force Life Cycle Managmenet Center (AFLCMC), OO-ALC organizations and Geographically Seperated Units (GSU). The requirements herein will be ordered via Task/Delivery Order to rapidly respond to aircraft procurement and sustainment requirements for United States Air Force (USAF) customers. The ATSSI II Contractor, hereafter referred to as the “Contractor”, will be the systems integrator who provides a single-point solution for ATSSI II requirements Background The Government is facing operation, maintenance, performance, and infrastructure support issues for a growing number of processor-based and manual test stations. Many of these systems are obsolete, stove-piped (i.e., not properly interfaced for efficiency purposes), duplicative, require unique/costly repair solutions, and/or require specialized sustainment in order to remain operable. The Government has established the ATSSI II to integrate, update, and consolidate ATS, test fixtures, TPS, database repositories, analytical software tools, and network infrastructures. The planned objective being to implement an integrated Sustainment Initiative (SI) based on common Commercial-off-the-Shelf (COTS) and/or Government-off-the-Shelf (GOTS) solutions, whenever possible. The Government does not have the organic personnel resources necessary to implement ATSSI II.

Scope Specific aspects of the scope of work include, but are not limited to:

· Support the Electronics Maintenance Group (EMXG) ATSSI IMP (Attachment B) and developing an OO-ALC IMP, specifically documenting: 1) ATSSI Requirements, 2) “The Existing SI Model”, 3) “The Planned SI Model”, and 4) An Integrated Master Schedule (IMS)

· Infrastructure support services necessary to sustain existing and planned IT infrastructures

· System documentation necessary to ensure ATSSI II sustainability

· Program management support for the reliability and maintainability of the Depot Test Systems and associated Support Equipment (SE)

· Logistics support for software and hardware maintenance efforts for assigned depot SE to include the compliment of depot test platforms at the OO-ALC facility

· Conduct software Validation and Verification (V&V) and kit proofing

· Schedule, organize, plan and conduct Software Compatibility Tests (SCTs)

· Develop program schedules, program plans, software/hardware checklists, and equipment Acceptance Test Procedures (ATP)

· Maintain data management and analysis schedules, Configuration Management (CM) plans and documentation, create and manage maintenance data collection and analysis schedules.

· Review, evaluate, and update Air Force or commercial technical manuals

· Removal and disposition of legacy test equipment

· Assist in design efforts

· Coordinate between multiple vendors to deliver complete systems

· Installation to include some level of facility modification

· Coordinate training for equipment use and maintenance

· Perform studies and analyses

· Coordinate between various System Program Offices (SPO), Complexes and Centers as applicable

· Item Unique Identification (IUID) support

· Diminishing Manufacturing Sources and Material Shortages (DMSMS) Support

· TPS software development or re-host support The basic core of ATSSI efforts are summarized in the following categories:

1. TPS Development/Rehost

2. Build-to-Specification Hardware Manufacture

3. ATE/TPS Sustainment Facility Efforts

4. Technical Refresh of Existing Automatic Test Equipment (ATE)

5. ATE Spare Instrument Support Programs (SISP)

6. Program Management Office (PMO) Activities/Support

7. On-site Engineering/Logistics Support

8. Other General ATSSI Requirements Non-Personal Services The Government will neither supervise nor direct Contractor personnel. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual Contractor employees. The Contractor shall manage its employees and guard against any actions that are of the nature of personal services or give the perception of personal services. If the Contractor believes that any actions constitute or are perceived to constitute personal services, or are outside the scope of this PWS or any task order, the Contractor shall notify the Contracting Officer (CO) immediately.

Inherently Governmental Functions The Contractor shall not perform any inherently Governmental functions as defined by Federal Acquisition Regulation (FAR) Subpart 7.5. All program decisions shall be the sole responsibility of the Government.

The Contractor shall not counsel, mentor, make judgments and/or discretionary decisions or perform any other activities related to supervision of Government personnel.

If the Contractor believes that any actions constitute or are perceived to constitute inherently Governmental functions, the Contractor shall notify the CO immediately.

Reference documents Documents and electronic files will be made available to the Contractor as needed, based on distribution statements. The Contractor will have access to Government offices, computer-based test stations, database repositories, analytical software tools, networks, and facilities in accordance with (IAW) Section 6.0 of this PWS. Consequently, all required reference documentation will be readily available for use during the performance of assigned tasks.

Basic Services The basic core services of the ATSSI efforts, as outlined in Section 1.3, are designated in detail in the following Section. Any and/or all of the items in Section 3.0 will be implemented according to task order following the basic ATSSI II award and are subject to available funding and at the convenience of the Government.

Test Program Sets (TPS) Development/Rehost A Test Program Set (TPS) is defined as all the hardware and software required to provide an integrated solution to test, troublshoot, repair, and recertify Air Force weapon system assets. This section will provide a detail of all the requirements needed to perform a TPS development. The elements of this development process will be designated at a task order level, and as required by individual TPS developments.

Test Program Sets (TPS) Requirements Analysis and Review The development process for a TPS involves a thorough investigation of the technical specifications and requirements needed to develop that TPS. In order to reduce risk to the TPS development process, the Government requires a detailed review and documentation of the end item and tester characteristics prior to the TPS development. The tester characteristics may include Input/Output (I/O) requirements, Test Accuracy Ratios (TAR), and any unique test requirements that each end-item may have. Section 3.1.1.1 defines the work needed to accomplish the investigation, and analyses.

NOTE: The information resulting from the TPS Requirements Reviews will be used by the Government to select appropriate test solutions, including potential ATS on which these end items may be rehosted and to provide documentation and information necessary to accomplish such tasks. SE recommendations shall be made IAW Section 3.3.5.1.

Requirements Determination and Analysis The Contractor shall perform analysis on each Unit Under Test (UUT) and provide the following:

· Requirements Traceability Matrix that identifies all testing, alignment, troubleshooting procedures associated with the legacy test procedures, and that traces the TPS test procedures to the existing test procedures used by the legacy test equipment

· I/O requirements with TAR values for the Legacy tester and tester alternatives included in the analysis

· Tester (ATE) Resource Matrix

· Unique test requirements for each TPS/UUT

(Contract Data Requirements List (CDRL) A001, Technical Report–Study/Services) Formal Requirements Review Upon completion of the TPS Requirements Analysis, the Contractor shall conduct a formal Requirements Review to present and deliver the information generated as part of Section 3.1.1.1 The Contractor shall also provide an assessment at the Requirements Review of each end item to assist in future ATE selection. The Requirements Review will be held as a teleconference, unless prior arrangements with the Government have been made in advance to conduct the review face-to-face.

The Contractor shall conduct a formal Requirements Review to present the information generated as part of Section 3.1.1.1 and provide:

· An assessment of each end item to assist in future ATE selection.

· An assessment report detailing each end item’s TAR requirements.

· An assesment of instruments and devices required to calibrate the system. The Contractor shall provide a briefing deck delineating the results of the TAR assessment/evaluation. The briefing shall provide enough detail to allow the Government to select appropriate ATE on which to rehost the end item.

· This SE recommendation shall adhere to the Selection Criteria identified in Section 3.3.5.1.

· A minimum of two (2) ATE systems shall be presented for comparison as part of the briefing deck.

Upon completion of the Requirements Review, the Contractor shall update and deliver the data package to address Government inputs, concerns and required changes.

(CDRL A001, Technical Report–Study/Services) Travel In order to thouroughly investigate the requirements of the items, the Contractor may need to travel to the Government facility to fully vet the item under consideration. Travel for this effort shall comply with the guildelines outlined in Section 3.8.1.

TPS Development TPS Software and Hardware Design and Development The following paragraphs descibe the TPS development phases and milestones required for TPS development efforts performed under ATSSI II. There are five (5) phases, each with a corresponding Milestone and Exit Criteria that must be adhered to for Government acceptance of the TPS.

Any and all travel associated with this process shall adhere to the travel requirements outlined in Section 3.8.1.

The Contactor shall provide for proper documentation of all TPS efforts. Reference documents for proper documentation include (but are not limited to):

· MIL-DTL-38807D

· MIL-DTL-87829

· T.O. 00-5-1

· T.O. 00-5-3

· T.O. 00-5-16

When directed by the Government at the Task Order level, the Contractor shall generate documentation in Structured Generalized Markup Language (SGML) format. Where SGML is not required, the Contractor shall deliver documentation in Contractor format.

Phase I - TPS Requirements Review The Government will provide the Contractor with the data package provided from the TPS Requirement Analysis Review (Reference 3.1.1). After reviewing the requirements analysis data package, the Contractor shall recommend to the Government the need for conducting a Preliminary Design Review (PDR) to discuss findings from the Requirements Review data package.

Milestone 1 – Preliminary Design review (PDR) During the Requirements Review phase, the Contractor shall present the case for a separate PDR. If it is deemed necessary by the Government to conduct a PDR; at a minimum, the following items shall be reviewed:

· Requirements Traceability Matrix

· I/O table(s)

· TAR table for Government recommended ATE

· ATE Resource table

· Preliminary software and hardware designs that the Contractor intends to use in development of the TPS

· Additional test hardware required

· Risk Management Framework (RMF) Authorization to Operate (ATO) process

· Any issues, risk, design factors, limitations, etc., requiring review and/or approval by the Government

· Action Items generated during the review

(CDRL A002, Conference Agenda) (CDRL A003, Conference Minutes)

Phase I Exit Criteria Successful completion of Action Items assigned to the Contractor during the PDR.

Phase II - Software and Hardware Design and Development The Contractor shall design and develop all TPS to meet performance requirements of MIL-PRF-32070 and MIL-PRF-49503.

Software The Contractor shall design and develop TPS software that captures the test requirements of the end-item as established in the applicable Technical Order (T.O.), Test Program Manual (TPM), Test Requirements Document (TRD), or Legacy ATE TPS Software.

As part of the software development, the Contractor will provide a method for the Government to access test data that will be used to determine if Government assets meet the above requirements, as outlined in section 7.1.3.

Test Program Hardware (TPH) The Contractor shall design and develop schematics, proposed room layouts, fabrication drawings, Bill of Materials (BOM), wire lists and/or assembly drawings for each element of the TPS Test Program Hardware (TPH).

Milestone 2 - Critical Design Reviews (CDR) Upon completion of the TPS (software and hardware) design and development the Contractor shall schedule and conduct a Critical Design Review (CDR). The PDR (per Section 3.1.2.1.2) may be combined with the CDR, at the direction of the Government. The Contractor shall include the following factors during this review, but not necessarily be limited to:

· Test Program Software Complexity

· TPH Complexity

· Calibrated items required as part of the TPH

· TPH Self-test and Diagnostics

· TPH Maintainability and Accessibility

· Government Furnished Equipment (GFE) Availability

· Requirements Traceability Matrix

· I/O table(s)

· TAR table for selected ATE

· ATE Resource table

· Safe-To-Turn-On Tests for the UUT

· Review of Functional Test Procedures compared to the requirements traceability matrix

· Review of the non-baselined 1st Article Hardware Design

· Risk Management Framework (RMF) Authorization to Operate (ATO) Process Plan

· Technical Manual Request documentation

· Any issues, risk, design factors, limitations, etc., requiring review and/or approval by the Government

· Action Items generated during the review

· Draft Technical Data Package (TDP) to include draft technical manuals, engineering drawings, BOM, wire lists, assembly drawings for each element, etc.

· Recommended redline markups to the current end-item overhaul manuals

(CDRL A002, Conference Agenda) (CDRL A003, Conference Minutes) (CDRL A004, General Style and Format Requirements for Technical Manuals/Technical Manual Contract Requirements, Test Program Manual and Test Program Hardware Manual) (CDRL A005, Commercial Drawings/Models and Associated Lists, Engineering Drawings) (CDRL A006, Product Engineering Design Data and Associated List, Engineering Drawings) (CDRL A007, Technical Manual(TM) Contractor Furnished Aeronautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notice) (CDRL A008, Technical & Management Work Plan, RMF ATO Process Plan)

Phase II Exit Criteria Successful completion of Action Items assigned to the Contractor during the CDR.

Phase III - Initial TPS Software and Hardware Integration Upon completion of the CDR and approval from the Government to proceed, the Contractor shall enter the TPS Integration Phase. During this phase, the Contractor shall integrate the TPS mock-up hardware and software to ensure that it appropriately tests the UUT per the Requirements Traceability Matrix.

Milestone 3 - TPS “BETA TESTING” The Beta-Testing Milestone is incorporated to allow the Contractor the opportunity to demonstrate the rehosted TPS to the appropriate stakeholders to ensure that all of the test requirements have been captured. In addition, it provides the Contractor the opportunity to troubleshoot failing tests in the maintenance shop with the technician. Upon completion of the TPS Integration Phase, the Contractor shall:

· Arrange a site visit after completion of the mock-up phase of the TPS development with the Government to provide “beta testing” of the mock-up unit.

· Conduct beta testing of the TPS (hardware and software) at the Government facility. Due to the disruption to the Production shop, these testing events must be coordinated with repair shop technicians. The Contractor shall schedule these events at least 30 days prior.

· Determine the functionality of the TPS to provide adequate testing on the UUT.

· Request feedback from the technicians on perceived weaknesses in the software, Interface Test Adapter (ITA), process, and functionality of the TPS.

· Incorporate any recommendations by technicians that are within scope of this PWS.

· Document and submit any out of scope recommendations to the Government for analysis and evaluation.

(CDRL A009, Test Procedures, Acceptance Test Procedures) (CDRL A010, Acceptance Test Report) Phase III Exit Criteria Successful completion of the Beta Testing Event.

Phase IV - 1st Article Hardware (H/W) Fabrication and Final TPS Integration Upon completion of the Beta Testing event, the Contractor shall enter the Final TPS Integration Phase. During this phase, the Contractor shall fabricate the 1st Article TPH, develop the Acceptance Test Procedures (ATP), and complete the final TPS integration testing based on feedback from the Beta Testing event. Final integration testing shall be completed using the 1st Article H/W.

Milestone 4 – Test Readiness Review (TRR) The Contractor shall conduct an internal Test Readiness Review (TRR) to ensure that the TPS software and Hardware are ready to begin the Acceptance Test Phase. The TRR should include but not limited to the following:

· Successful end-to-end functional testing of the TPS software

· Sucessful fault insertion detection, if specified in the ATP (See section 3.1.3.5 for definition of the ATP)

· Review of the 1st Article TPH drawing package

· Quality Control inspection of the TPH and validation that the TPH drawings and hardware are in agreement

· Developed Acceptance Test Procedures

· Completed TDP Documentation (Software Version Description (SVD), Software Design Description (SDD), TPM/TPH Manuals, ATP)

· Validated Software Drawing

· Adherence to Risk Management Framework (RMF) Authorization to Operate (ATO) process

The Contractor shall provide the completed TRR checklist, detailing the results of the review, to the Government for review/acceptance.

(CDRL A009, Test Procedures, Acceptance Test Procedures) (CDRL A001, Technical Report–Study/Services) Phase IV Exit Criteria Government accepts the results of the TRR.

TPS Acceptance Phase – Phase V Upon completion of the initial TPH build and final TPS integration testing at the Contractor’s facilities, the Contractor will enter the TPS Acceptance Phase. The following subparagraphs detail the requirements for acceptance of the TPS. The Contractor shall address all required components of acceptance testing described in the ATP.

Milestone 5 - Functional Configuration Audit (FCA) / Physical Configuration Audit (PCA) Upon completion of the 1st Article H/W fabrication and final TPS Integration testing, the Contractor shall:

· Deliver draft TDP Documentation (Software Version Description (SVD), Software Design Description (SDD), TPM/TPH Manuals, Engineering Drawings, and CPIN)

· Convene a joint Functional Configuration Audit (FCA)/Physical Configuration Audit (PCA) with the Government to verify that the TPS is accurate, complete, compatible, and the Configuration Item (CI) has achieved the performance and functional characteristics delineated in the requirements specifications.

· Perform the FCA/PCA jointly with the Government and the Contractor at a mutually agreed upon time and location, with the Government chairing the audit. Preference will be for this to be held at the Contractor’s facility.

· Document the results of the FCA/PCA for each audit and correct all audit discrepancies.

· Establish the TPS software, hardware, and TDP baselines after all audit discrepancies have been resolved and accepted by the Government.

· If necessary, update ATP

(CDRL A011, Software Version Description SVD) (CDRL A012, Software Design Description(SDD)) (CDRL A004, General Style and Format Requirements for Technical Manuals/Technical Manual Contract Requirements, Test Program Manual and Test Program Hardware Manual) (CDRL A005, Commercial Drawings/Models and Associated Lists, Engineering Drawings) (CDRL A006, Product Engineering Design Data and Associated List, Engineering Drawings) (CDRL A013, Computer Program Identification Number(CPIN) Catalog Information) (CDRL A014, Configuration Audit Plan) (CDRL A015, Configuration Audit Summary Report and Certification) (CDRL A009, Test Procedures, Acceptance Test Procedures)

Upon successful completion of the FCA/PCA Milestone, the Contractor can schedule the TPS Acceptance Test event.

Milestone 6 - TPS Acceptance Test Upon successful completion of the FCA/PCA events and establishing the TPS Software, documentation, and hardware baselines, the Contractor shall:

· Conduct TPS Acceptance activities at Government facility in the respective UUT Maintenance shop with the designated stakeholders IAW the ATPs.

· When possible, TPS Acceptance testing shall be performed on at least two UUTs and at least two ATEs to ensure test repeatability.

· Deliver final TDP Documentation (Software Version Description (SVD), Software Design Description (SDD), TPM/TPH Manuals, Engineering Drawings, and CPIN)

(CDRL A010, Acceptance Test Report) (CDRL A011, Software Version Description SVD) (CDRL A012, Software Design Description) (CDRL A004, General Style and Format Requirements for Technical Manuals/Technical Manual Contract Requirements, Test Program Manual and Test Program Hardware Manual) (CDRL A005, Commercial Drawings/Models and Associated Lists, Engineering Drawings) (CDRL A006, Product Engineering Design Data and Associated List, Engineering Drawings) (CDRL A013, Computer Program Identification Number(CPIN) Catalog Information)

Phase V Exit Criteria Upon successful completion of the Acceptance Testing event and receipt of the final Software, Hardware, and TDP, the Government will sign and return the Contractor provided DD-250 Inspection and receiving report to the Contractor. At this point, the Government will consider the TPS delivered.

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 CO have been made in advance of the intended activity.

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

Final Delivery/Selloff of all artifacts shall be no later than (NLT) 30 calendar days prior to end of Period of Performance or NLT the date specified in the Task Order.

The Contractor shall correct all defects in workmanship and component failure for a period of one (1) year from the date of the Final Delivery. The Contractor will address all deficiencies in the original workmanship and components for the stated period at no additional cost to the Government, this will include all shipping charges if applicable. The Contractor will not be required to cover damages to the deliverables due to neglect or misuse by the Government.

TPS Development/Rehost Deliverables TPS Requirements Traceability Matrix The Contractor shall develop and deliver the TPS Requirements Traceability Matrix that traces the TPS test procedures to the existing test procedures used by the legacy test equipment.

(CDRL A001, Technical Report–Study/Services) Software Version Description (SVD) Document The Contractor shall deliver a SVD Document for each TPS software package. The SVD shall identify the Computer Program Identification Number (CPIN), program version and revision, release date and software installation procedures within the SVD Documents.

(CDRL A011, Software Version Description (SVD)) TPS Software Design Description (SDD) The Contractor shall develop a SDD document in Contractor format that at a minimum will capture the design decisions for that TPS software as well as any pertinent information that will be useful in the support and maintenance of the TPS.

(CDRL A012, Software Design Description(SDD)) TRR Checklist Prior to scheduling the formal Audits and Acceptance Testing Events, the Contractor shall develop and deliver a TRR Checklist that documents the completed actions (pass/fail) from the Contractor’s Internal Test Readiness event.

(CDRL A016, Technical Report–Study/Services, TRR Checklist)

ATP

The Contractor shall develop and deliver an ATP that (at minimum) demonstrates the suitability of the TPS to satisfy the test requirements established in the applicable Test Procedures, Operation and Maintenance (O&M) Manual, and /or TRD. Submit the ATP to the Government at least ten days prior to the start of TPS acceptance testing.

(CDRL A009, Test Procedures, Acceptance Test Procedures) Acceptance Test Report The Contractor shall develop a Final Acceptance Test Report that documents the findings from the Acceptance Testing events (FCA/PCA and Final Acceptance Testing).

(CDRL A010, Acceptance Test Report) Recommended Redline Markups to the current End-Item Overhaul Manuals The Contractor shall make required red-line markups to the current End-Item Overhaul Manuals and submit them to the appropriate stakeholders including the Equipment Specialist and Technical Order Management Agency (TOMA).

(CDRL A001, Technical Report–Study/Services) Test Program Manual (TPM) The Contractor shall develop and deliver a TPM that describes the instructions for performing automated tests for each TPS. The Contractor shall use MIL-STD-38784 (Department of Defense (DoD) Standard Practice for Manuals, Technical: General Style) as a guide/reference in the development of the TPMs.

The Contractor shall provide the Government with the final copy of the TPM for review, IAW the applicable CDRL and Task Order requirements, 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 update the TPM that incorporate comments provided by the Government.

The Contractor shall deliver final documents IAW the applicable CDRL and Task Order requirements.

(CDRL A004, General Style and Format Requirements for Technical Manuals/Technical Manual Contract Requirements, Test Program Manual and Test Program Hardware Manual) TPH O&M Manual The Contractor shall develop and deliver a TPH O&M Manual for each TPS that describes the maintenance instructions for maintaining and repairing the TPH. The Contractor shall use MIL-STD-38784 (DoD Standard Practice for Manuals, Technical: General Style) as a guide/reference in the development of the TPMs.

The Contractor shall provide the final copy of the developed TPH O&M Manual ten (10) days prior to the start of TPS acceptance testing. The Government will have the opportunity to review the manual and then validate the maintenance procedures, graphics, and BOM in the manual against the actual TPH drawings during the PCA. The Contractor shall provide the final documents IAW the applicable CDRL and Task Order requirements.

(CDRL A004, General Style and Format Requirements for Technical Manuals/Technical Manual Contract Requirements, Test Program Manual and Test Program Hardware Manual) Engineering Drawings The Contractor shall provide Engineering Drawings with sufficient information to permit Government maintenance, modification, re-procurement/re-manufacture, and engineering analysis of all manufactured items. All engineering drawings generated shall adhere to best commercial practices and shall, at a minimum, follow American Society of Mechanical Engineers (ASME) Y14 standards. Engineering drawings generated shall be prepared for incorporation into Joint Engineering Data Management Information Control System (JEDMICS) repositories. The data provided shall be to the COTS component-level; subcomponent level details are not required for the COTS items.

The Contractor shall provide Altered Item Drawings to document all custom changes made to COTS items.

The Contractor shall create engineering documentation packages (which include corrections/updates to T.O.s), engineering drawings, schematics, and associated technical data) for the TPS.

(CDRL A005, Commercial Drawings/Models and Associated Lists) (CDRL A006, Product Engineering Design Data and Associated List, Engineering Drawings) The Contractor shall prepare and deliver updated documents according to the guidelines and specifications identified by the relevant stakeholders for the system. The Government will provide stakeholder requirements at least 90 days prior to needed delivery dates.

Computer Program Identification Number (CPIN) The Contractor shall submit a CPIN request for each TPS Software CI and deliver the TPS software IAW T.O. 00-5-16.

(CDRL A013, Computer Program Identification Number (CPIN) Catalog Information) Build-to-Specification Hardware Manufacture The Contractor shall produce build-to-specification hardware items and ATE that do not require Non-recurring Engineering (NRE) Services. These include build-to-print copies of test equipment. The Contractor shall build and deliver test equipment, Interface Test Adapters (ITA), or other SE items to all applicable (and most current) drawing specifications and software configurations. These hardware items will be identified on individual task orders. These items will be subject to inspection per section 7.8.2 and 7.9 verifying all items meet the proposed Quality Control Plan (QCP) delivered for the task order (see section 7.6.3).

Validation/Verification of Build-To-Specification Hardware Acceptance of each build-to-specifciation item will be performed on a case-by-case basis, depending on the complexity and nature of each end item. Unless identified in task order, this acceptance will take place at the specified delivery point on Hill AFB.

(CDRL A009, Test Procedures, Acceptance Test Procedures) (CDRL A010, Acceptance Test Report) ATE/TPS Sustainment Facility (ATSF) Upon initiation of a task order, the Contractor shall set up an ATE/TPS Sustainment Facility (ATSF) located at Hill AFB for continued sustainment of TPS and ATE items as identified in the task order. Several of the following sections (up to inclusion of all of them) will be utilized to support the efforts of the ATSF and may be spread over several task orders at the direction and convenience of the Government.

System Integration Activities The Contractor shall ensure that discrete vendor system sub-elements are fully compatible by integrating the fabricated systems and sub-systems with each other to ensure that no operational deficiencies are identified.

The Contractor shall evaluate the possible solutions sets for system and subsystem integration deficiencies, select the most cost-effective solution set, and direct the appropriate vendor to remedy the deficiency.

The Contractor shall model and analyze different SE hardware/software technical solutions to optimize solutions.

The Contractor shall analyze different logistics support approaches for candidate systems and, if necessary, conduct NRE activities to develop sustainment alternatives for the ATE components and TPS programs.

General Support Equipment (SE) and Prime Mission Equipment (PME) Product Support Integration Activities The Contractor shall provide all necessary logisticians, engineers, analysts, specialists, technicians and sustaining engineering technical experts, as needed, to conduct general SE and PME systems integration activities. General SE and PME systems integration activities shall include, but is not limited to, activities necessary to ensure that the end-user can fully employ weapon system operational capabilities.

General Support Equipment (se) The Contractor shall analyze weapon system requirements and report analysis finding to the Government as required,and as specified in future task orders. If directed by the Government, the Contractor shall fabricate, integrate, test, and deliver general SE that satisfies the operational needs of USAF customers. General SE may include, but is not limited to, hardware and software for infrastructure improvements, ground handling, and aircraft servicing equipment.

Systems Integration Logistics Support The Contractor shall provide logisticians, engineers, analysts, specialists, or sustaining engineering technical experts, as needed, to provide Product Support Integration logistics direct mission support.

Logistics Product Data (LPD) As required, the Contractor shall develop test capabilities; provide data for and participate in the provisioning process, Engineering Data for Provisioning (EDFP) and Logistics Product Data (LPD) and the Initial Provisioning Performance Specification (IPPS). The Contractor shall ensure Source, Maintenance, and Recoverability (SMR) codes are assigned to ATE components, TPSs, ancillary SE, PME, and non-Radio Frequencey (RF) and RF-capable non-deployable and deployable test capabilities; and update kit components identical to those assigned to like components. Provisioning activities shall be documented in the appropriate MSR.

Submitting Engineering Data for Provisioning (EDFP) and Logistics Product Data (LPD) Schedules and requirements for submitting the EDFP and LPD shall be IAW applicable CDRLs. Order precedence for EDFP shall be in accordance to the IPPS.

(CDRL A017, Engineering Data for Provisioning) (CDRL A018, Logistics Product Data) Provisioning LPD will be submitted in a format compatible with Air Force Material Command (AFMC) Automated Provisioning System (D220) as required by the IPPS including attachments. The schedule for submitting the LPD shall be IAW the Provisioning Performance Schedule (PPS) (AFMC 718) which will be completed at the Provisioning Guidance Conference (PGC).

Systems Integration Sustaining Engineering Activities The Contractor shall provide logisticians, engineers, analysts, specialists, or sustaining engineering technical experts, as needed to perform sustaining engineering activities for AFSC weapon system customers. The Contractor shall ensure that personnel assigned to this task are fully knowledgeable of AFSC depot maintenance level test equipment and its related support infrastructure requirements.

Test Capability Development The Contractor shall, research, analyze, develop, integrate, test, demonstrate, and deliver any necessary studies, analyses, proof-of-concept documentation, and technical reports as required to support test capability development. This support shall include, but not be limited to:

· Developing new software protocols for use with legacy ATE, TPS, SE, PME, Line Replaceable Unit (LRU), Shopr Replaceable Unit (SRU) and Support Equipment Recommendation Data (SERD) software Engineering Trade Studies The Contractor shall perform engineering trade studies supporting the following:

· Technology Assessment/Qualification

· Feasibility Analysis

· Alternatives Analysis (including build, buy, upgrade, etc.)

· Cost/Benefit Analysis

· Hardware/Software Consolidation and/or Integration

· Operational Software

· SE

· Transportation and Material Handling Equipment

· Data Systems and Automated Tools

· ATE; including Test Sets Test Stations

· Trade Study Reports as required by task order

· Requirements Review

(CDRL A001, Technical Report, Study/Service Report) Technical Services The Contractor shall provide follow-on sustaining engineering technical services for hardware and software delivered as part of the ATE, TPS, SE, PME, LRU, SRU, and SERD equipment. Follow-on technical services are generally defined as those tasks required to provide continued support to AFSC for overall management of assigned equipment. This includes the resolution of field and factory identified problems. Specifically, the effort will, at a minimum, include the following:

a. Providing technical review, investigation and development of proposed solutions for hardware and software problems identified by USAF and Contractor personnel

b. Reviewing and evaluating of ATE, TPSs, SE, PME, LRUs, SRU, SERDs and recommending changes, as required, for complete and efficient support

c. Providing a capability to identify revisions to ATE, TPS, SE, PME, LRU, SRU, and SERD hardware and software as necessary to implement test requirements not originally determined to be necessary for ATE, TPS, SE, PME, LRU, SRU, and SERD testing. These additional requirements may be identified during factory or depot usage and evaluation, or whenever a determination is made that additional capability is required. Changes to hardware may result from vendor System Test Specification (STS) and/or Test Requirements Document (TRD) changes due to revised testing requirements

(CDRL A001, Technical Report, Study/Service Report) Service Reports (SRs) and Deficiency Reports (DRs) The Contractor shall review Service Reports (SRs) and Deficiency Reports (DRs) and analyze associated exhibits for cause(s) of failure(s). The analysis may entail teardown and testing of ATE, TPS, SE, PME, LRU, SRU, and/or SERD items.

(CDRL A001, Technical Report, Study/Service Report) Software Maintenance Facility The Contractor shall provide laboratory facilities, test equipment and associated items for the purpose of evaluation, investigation, testing, validation, and related engineering activities. These requirements will be specified per task order.

ATE Systems and SERD Sustainment Integration Support Activities The Contractor shall provide all necessary logisticians, engineers, analysts, specialists, technicians and sustaining engineering technical experts, as needed, to research, analyze, design, develop, fabricate, integrate, test, deliver, and install test capability hardware and software as well as complete all necessary NRE and logistics data development activities associated with SERD development. The Contractor shall ensure that personnel assigned to this task are fully knowledgeable of legacy ATE, and USAF Depot maintenance level test equipment, SERDs, and their related support infrastructure requirements.

The Contractor shall ensure, to the maximum extent possible, that all test capability equipment is identical to that currently possessed by other weapon system customers in order to minimize the sustainment costs for the delivered equipment, e.g., ATE systems, TPSs SE, PME, K400C Aircraft Generator, Variable Speed Constant Frequency, Integrated Drive Generator, and Constant Speed Drive test stands.

Support Equipment (SE) Selection Criteria The Contractor shall use the following order of priority in preparing SE recommendations to promote standardization and nonproliferation of SE.

1. Identify the weapons system’s support/test requirements,

2. Define the various support/test alternatives,

3. Analyze the alternatives, and

4. Present alternative solution options for the appropriate ATS support alternative (see below for ATS selection process).

a) Service’s Designated ATS Family

b) DoD Designated ATS Family

c) Commercial tester

d) Current weapon system/Service ATS

e) Other DoD inventory ATS

f) New development ATS

5. If existing items are selected, they may not be “free” to the Contractor. The Contractor might have to procure sufficient quantities to support their TPS design approach.

6. There must be a current data package available to procure the items.

7. The current status of logistics support is a consideration.

8. Coordinate these considerations with the Government.

(CDRL A001, Technical Report, Study/Service Report) ATS Selection Process In order to avoid any Contractor Bias, the ATS support alternative evaluation and selection will be performed according to the documented process found in DoD ATS Selection Process Guide (2009), located on the Office of the Under Secretary of Defense for Acquisition, Technology and Logistics web page (http://www.acq.osd.mil/ats/). The Contractor will follow this process utilizing information from the IMP to determine appropriate ATS Selection recommendations and shall submit it to the Government for evaluation and ATE selection. The Contractor shall adhere to the RMF ATO process and if necessary, develop a RMF ATO Process Plan. Once the Government determines the selection, the Contractor shall then proceed to development (or Subcontracting) of that chosen ATS support alternative.

(CDRL A008, Technical and Management Work Plan, RMF ATO Process Plan)

Configuration Supportability The Contractor shall analyze the ATE, TPS, SE, PME, LRU, SRU, SERD items, and IPC data configurations and determine what actions should be taken to ensure supportability for these configurations until the forecasted end-of-life for the associated weapon system. If directed by the Government, the Contractor shall implement all actions required to modernize ATE, TPS, SE, PME, LRU, SRU, and SERD items, to include the replacement of computer processors and peripheral equipment, update of required operating system as well as test software, upgrade of computer- controlled RF measurement and stimulus equipment, and upgrade of ITA and ancillary equipment hardware and software. If necessary, these activities may include NRE for hardware and software development. The Contractor shall also update and deliver any necessary technical documentation to reflect the modernized equipment configuration. This documentation includes, at a minimum, the update of engineering drawings, provisioning documentation, software documentation, and T.O.s as directed by the Government.

(CDRL A019, Configuration Status Accounting information) Test Capability The Contractor shall fabricate, test, deliver, and install Contractor-provided ATE, TPSs, SE, PME, LRUs, SRUs, and SERDs, as required, to provide an automated test capability to USAF end users.

Operational Readiness Support Kit (ORSK) The Contractor shall fabricate, test, and deliver Operational Readiness Support Kit (ORSK) equipment needed to implement an automated test capability at customer facilities. The Contractor shall compute ORSK composition based on a 5-day work week, two 8-hour shifts per duty day, 90-day repair turn-around-time (includes shipping and handling time), and a 95% probability that ORSK content shall enable uninterrupted operations for a 90-day period.

Depot Readiness Support Kit (DRSK) The Contractor shall fabricate, test, and deliver Depot Readiness Support Kit (DRSK) equipment needed to implement an automated test capability at customer facilities. Composition of the DRSK shall be as directed by the technical customer.

Installation and Checkout (ICO) The Contractor shall perform Installation and Checkout (ICO) for any Contractor-provided equipment fabricated under this PWS when requested by the Government. ICO shall consist of installation at the ultimate delivery location, electrical checkout, and repair of deficient initial installation Contractor-provided equipment. ICO will be deemed complete when the equipment has successfully completed self-test. If the Government directs shipment of any Contractor-provided equipment to temporary locations prior to installation at the ultimate delivery location, i.e., other vendor facilities for use in support of TPS development or LRU/SRU integration, the Contractor will not be required to repair deficient equipment discovered during the subsequent ICO. In the event the Government is unable to ship and set-up the Contractor-provided equipment within 90 calendar days of its scheduled installation date, the Contractor will not be required to perform ICO for that equipment.

Depot Test Capability The Contractor shall develop either a material or non-material test capability for use at USAF depot maintenance facilities. This development may necessitate NRE activities for hardware and software development. The resultant capability must be compatible with the test capability ATE and ancillary SE currently possessed or planned to be possessed by that activity. To ensure SERD compatibility with end user PME, the Contractor shall possess the capability to independently identify and validate end user PME configuration data through review of vendor configuration databases. When discrepancies between Government and vendor equipment configurations are identified, the Contractor shall notify the Government of the discrepancies and aid the Government in correcting the deficient data. The maximum number of simultaneous test operations at each location is one unless otherwise specified by the Government. The Contractor shall, to the maximum extent possible, leverage existing material and non-material solutions to minimize costs associated during SERD development. If a material solution is selected, the Contractor shall procure or develop, integrate, test, and deliver all Contractor-provided equipment to enable testing of the LRUs/SRUs possessed by the end user. Integration activities shall include, at a minimum, qualification of parts to correct obsolescence conditions; and TPS integration support activities for existing and newly developed members of the legacy system of ATE, TPSs, SE, PME, LRU, SRU, and SERDs.

Technical Order (T.O.) Updates The Contractor shall update TOs to reflect changes to TPSs, SE, PME, and update kits test capabilities. The Contractor shall minimize test capability and update kit supportability impacts to current users by coordinating the updates with the Government prior to incorporation. The Contractor shall submit the T.O. change data to the Government as directed by the Government IAW Air Force Materical Command Instruction (AFMCI) 21-301 and TO 00-5-3. The Contractor shall document T.O. change data submissions in the appropriate MSR.

(CDRL A020, Technical Order Improvement Report and Reply, Technical Order Updates) Failure and trend analysis When applicable and as identified by task order, the Contractor shall analyze failure data, perform trend analysis for AFSC-managed equipment, and provide technical reports, as requested by the Government.

(CDRL A001, Technical Report- Study/Services) Configuration Data When applicable and as identified by task order, the Contractor shall review and provide the Government with ATE, TPS, SE, PME, LRU, SRU, SERD configuration data, and IPC data as required to ensure that the appropriate hardware and software will be delivered to new and existing test capability end item users.

(CDRL A021, Configuration Status Accounting (CSA) Information) Software Product Anomaly Report (SPAR) When applicable and as identified by task order, the Contractor shall coordinate Software Product Anomaly Report (SPAR) from Hill AFB Depot, and Contractor engineering and testing facilities.