F16AISProductSupportIntegrationPWS.docx

PERFORMANCE WORK STATEMENT (PWS)

FOR

F-16 AVIONICS INTERMEDIATE SHOP (AIS)

PRODUCT SUPPORT INTEGRATION (PSI) PROGRAM

CONTRACT: TBD

PR NO: TBD

DATE: APRIL 2017

PREPARED BY:

NICOLE CHECKETTS

416 SCMS/GUMAA

6070 GUM LANE

BLDG 1213

HILL AFB, UT 84056-5825

CONTENTS

Section/Paragraph Title Page Number

SECTION IV GENERAL INFORMATION 10

4.1 General Work Requirement

F-16 AVIONICS INTERMEDIATE SHOP (AIS)

PRODUCT SUPPORT INTEGRATION (PSI) PROGRAM

PR NO: TBD Date: April 2017

SECTION I

DESCRIPTION OF SERVICES

1.1 SCOPE:

1.1.1 This Performance Work Statement (PWS) defines the Systems Engineering and Product Support Integration activities to be provided for the 748 Supply Chain Management Group, 416 Supply Chain Management Squadron (Hill Air Force Base). The customer will be referred to hereafter as “416 SCMS”, or simply the “Government.” References to 416 SCMS in this PWS may involve AFSC, AFLCMC, or local OO-ALC organizations, such as the 309 Maintenance Group, AFLCMC/WWN (F-16 Division), AFLCMC/WNA (ATS Division), or the 516 Software Maintenance Squadron. The requirements herein will be ordered via Task/Delivery Order to rapidly respond to aircraft procurement and sustainment requirements for USAF and European Participating Air Forces (EPAF)/Foreign Military Sales (FMS) customers. The Systems Engineering and Product Support Integrator, hereafter referred to as the “contractor”, is a non-manufacturing systems integrator who provides a single-point solution for F-16 Avionics Intermediate Shop (AIS) series Automatic Test System (ATS) requirements, to include the Advanced Computer Avionics Intermediate Shop (AdC AIS), Improved Avionics Intermediate Shop (IAIS), Versamodule Extensions for Instrumentation Improved Avionics Intermediate Shop (VXI-IAIS), Rackmount Improved Avionics Intermediate Shop (R-IAIS), AIS ATS Component, Ancillary Support Equipment (SE), and Test Program Set (TPS) system hardware and software requirements, used in support of USAF/EPAF/FMS weapon system maintenance sustainment operations selected by the AIS Systems Sustainment Program Office through subcontracts to the respective Original Equipment Manufacturers (OEMs) and other qualified sources.

1.1.2 Hereafter, references to “AIS” may include, the Advanced Computer Avionics Intermediate Shop (AdC AIS), Improved Avionics Intermediate Shop (IAIS), Versamodule Extensions for Instrumentation Improved Avionics Intermediate Shop (VXI-IAIS), and/or the Rackmount Improved Avionics Intermediate Shop (R-IAIS).

1.1.3 The contractor shall provide oversight of test system hardware and software component development and production programs. Therefore, the contractor shall not engage in test system hardware, software, or TPS development or production as a primary line of business. The contractor shall ensure that test system hardware and software are fully compatible by integrating the fabricated sub-systems with each other to ensure that there are no operational deficiencies. The contractor shall manage, direct, and control support processes using an integrated total systems approach that consists of integrating the activities of product support providers as well as performing intra-system and inter-system integration of supporting systems, subsystems, end-items, components, and facilities.

1.1.4 The contractor shall perform Product Support Integration activities to identify and resolve program management, data management, engineering, and logistics issues impacting existing operational users and potential new equipment customers. This includes, but is not limited to, the effort required to analyze, procure, fabricate, integrate, test, and install non-Radio Frequency (RF) capable as well as RF-capable, non-deployable and deployable test capabilities to support USAF Continental United States (CONUS) Homeland Defense operations, USAF and EPAF/FMS Overseas Contingency operations, and operations at the USAF Depot industrial complex at Hill AFB, Utah, and Kadena AB, Japan. The equipment capabilities may, as required, include test system hardware components, TPS ancillary Support Equipment (SE), general SE (both powered and non-powered), Support Equipment Recommendation Data (SERD) equipment, and associated software and technical data. This effort may also require analysis, design, development, prototyping, fabrication, incidental material acquisition, integration, delivery, and field support of equipment required to support aircraft program activities for USAF or EPAF/FMS customers. The scope also includes programmatic technical support for the entire acquisition and sustainment effort.

1.1.5 The contractor shall perform system sustainment and integration activities that enhance mission readiness, sustainability, reliability and maintainability of SE, Prime Mission Equipment (PME) and their related support infrastructure and associated Support Equipment. These activities include the review, assessment, definition, and resolution of technical or supportability deficiencies revealed during the operational use of fielded systems.

1.1.6 The contractor shall determine the impact on the affected product, identify and evaluate alternative solutions, determining the preferred solution; and design, integrate, and validate the preferred solution. The contractor shall then perform the removal, disassembly, inspection, failure analysis and remediation, adjustment, modification, test, assembly, and reinstallation of components and equipment following the procedures set forth in instruction manuals, Technical Orders, or contractor work instructions, ISO 9001/AS9100 procedures as appropriate.

1.1.7 The contractor shall perform Non-Recurring Engineering (NRE) actvities in order to develop new test capabilities and/or develop resolutions to obsolescence issues over and above Form-Fit-Function interface component replacement. For the purposes of this effort, NRE shall refer to the one-time cost to research, develop, design and test new or replacement product(s).

1.1.8 Over and Above Procedures

1.1.8.1 Non-Recurring Engineering (NRE) Services will be handled using the following Over and Above procedures. In accordance with DFARS PGI 217.77, negotiations shall be in IAW DFARS Clause 252.217.7028. Request for consideration of over and above shall be made in writing utilizing procedures identified below.

1.1.8.2 Work Requests (WRs): Is defined as a request detailing over and above work to be performed and the cost associated prior to beginning work. WRs, shall be conducted as follows: the Contractor shall identify any work that is required which would qualify as “over and above” IAW DFARS 252.217-7028. In the event that over and above work is identified, the Contractor shall prepare a Work Request (WR). The following steps shall be followed:

• Step 1- Contractor shall prepare a Work Request.

o Each Work Request shall include at a minimum the following: Contract/Delivery Order, description of the work to be completed, estimated additional cost and hours, justification for WR.

• Step 2- Contractor shall send Work Request to Hill Engineering, PM, ACO, and PCO for review.

• Step 3- Hill Engineering and PM shall review/approve work request(s) and Contracting Office shall send final approval to Contractor prior to O&A related work commencing.

1.2 TERMS EXPLAINED:

1.2.1 “ACO”: The Administrative Contracting Officer

1.2.2 “ACPINS”: Automated Computer Program Identification Number System

1.2.3 “AFTO”: Air Force Technical Order

1.2.4 “AIS”: Avionics Intermediate Shop – a set of non-Radio Frequency (RF) capable as well as RF-capable, non-deployable and deployable test equipment used to test and repair avionics components

1.2.5 “ATE”: Automatic Test Equipment

1.2.6 “ATP”: Automatic Test Procedures

1.2.7 “CMRS”: Calibration and Measurements Requirements Summary

1.2.8 “CO”: Contracting Officer

1.2.9 “Component”: An assembly or any combination of parts, subassemblies, and assemblies mounted together in manufacture, assembly, maintenance, or rebuild

1.2.10 “CONUS”: Continental United States

1.2.11 “CPIN”: Computer Program Identification Number

1.2.12 “CPP”: Counterfeit Protection Plan

1.2.13 “C&S”: Control and Support

1.2.14 “CDRL”: Contract Data Requirements List

1.2.15 “COR”: Contracting Officer Representative

1.2.16 “DMSMS”: Diminishing Manufacturing Sources and Material Shortages

1.2.17 “DR”: Deficiency Report

1.2.18 “DRSK”: Depot Readiness Support Kit

1.2.19 “DSCA”: Defense Security Cooperation Agency

1.2.20 “FMS”: Foreign Military Sales

1.2.21 “FSB”: Field Service Bulletin

1.2.22 “FSD”: Full Scale Development

1.2.23 “GFE/M”: Government Furnished Equipment/Materials

1.2.24 “GFP”: Government Furnished Property

1.2.25 “IAW”: In Accordance With

1.2.26 “ICO”: Installation and Checkout

1.2.27 “ITA”: Interface Test Adapter

1.2.28 “IUID”: Item Unique Identification

1.2.29 “LOA”: Letter of Offer and Acceptance

1.2.30 “LOR”: Letter of Request

1.2.31 “LRU”: Line Replaceable Unit

1.2.32 “MIP”: Material Improvement Project

1.2.33 “NRE”: Non-Recurring Engineering

1.2.34 “OFP”: Operational Flight Program

1.2.35 “OJT”: On-The-Job

1.2.36 “ORSK”: Operational Readiness Support Kit

1.2.37 “PME”: Prime Mission Equipment

1.2.38 “PMP”: Program Management Plan

1.2.39 “PMR”: Program Mangement Review

1.2.40 “PWS”: Performance Work Statement

1.2.41 “QASP”: Quality Assurance Surveillance Plan

1.2.42 “RESMAN”: Resource Manager

1.2.43 “RF”: Radio Frequency

1.2.44 “ROM”: Rough Order of Magnitude

1.2.45 “SCMG”: Supply Chain Management Group

1.2.46 “SCMS”: Supply Chain Management Squadron

1.2.47 “SCT”: Software Compatibility Test

1.2.48 “SE”: Support Equipment

1.2.49 “SERD”: Support Equipment Recommendation Data

1.2.50 “SGML”: Standardized General Markup Language

1.2.51 “SI”: Synthetic Instrumentation

1.2.52 “SMR”: Source, Maintenance, and Recoverability

1.2.53 “SPAR”: Software Product Anomaly Report

1.2.54 “SR”: Service Report

1.2.55 “STS”: System Test Specification

1.2.56 “TCTO”: Time Compliance Technical Order

1.2.57 “TIM”: Technical Interchange Meeting

1.2.58 “TO”: Technical Order

1.2.59 “TOMA”: Technical Order Management Agency

1.2.60 “TORB”: Technical Order Review Board

1.2.61 “TPS”: Test Program Set

1.2.62 “USAF”: United States Air Force

1.2.63 “V&V”: Validation and Verification

1.2.64 “WAWF”: Wide Area Workflow

1.2.65 “XML”: Extensible Markup Language

SECTION II

SERVICES DESCRIPTION SUMMARY

2.1 PERFORMANCE OBJECTIVES

2.1.1 The contractor shall be responsible for the accomplishment of Product Support Integration tasks necessary to support operational requirements for existing operational users and potential new equipment customers. The following provides a summary of the primary responsibilities and duties of the Parties:

2.2 The responsible Government Program Office:

2.2.1 Will provide technical direction and approvals to the contractor

2.2.2 Will provide advance notice of program changes

2.2.3 Will authorize required Product Support Integration activities

2.2.4 Will expeditiously communicate Government concerns to the contractor

2.2.5 Will provide acceptance of Contract Data Requirements List (CDRL) item

2.2.6 Will provide Government Furnished Equipment/Materials (GFE/M) as required will pre-authorize Prime Contractor travel requirements, as required

2.3 The contractor:

2.3.1 Shall provide a single-point solution for system requirements selected by the Government

2.3.2 Shall provide on-site technical support at Hill AFB

2.3.3 Shall provide Item Unique Identification support to ensure program objectives are obtained

2.3.4 Shall provide Diminishing Manufacturing Sources and Material Shortages analyses

2.3.5 Shall provide Product Support Integration and logistics support services as required to meet sustainment objectives

2.3.6 Shall perform TPS software and hardware development or re-host as required to meet end user requirements

2.3.7 Shall perform systems integration sustaining engineering activities as requested by the Government

2.3.8 Shall perform sustainment integration support activities for 416 SCMS managed components within the Automated Test Equipment (ATE)

2.3.9 Shall perform Support Equipment Recommendation Data (SERD) Product Support Integration support activities

2.3.10 Shall perform general Support Equipment and Prime Mission Equipment Product Support Integration support activities

2.3.11 Shall have independent access to vendor SE and aircraft configuration databases to ascertain correct equipment configuration data

2.3.12 Shall travel to accomplish the PWS tasks

2.3.13 Shall generate and deliver data as requested by the Government

2.4 Performance Objectives: The below listed performance objectives will be tracked and monitored according to DCMA contract requirements and reflected in monthly status reports. Schedules will be reported and tracked in the monthly status reports and Program Management Reviews (PMRs)

SECTION III

GOVERNMENT FURNISHED PROPERTY (GFP) AND SERVICES

3.1 GFP:

3.1.1 If required to ensure ATE, ancillary equipment, or SERD equipment functionality prior to delivery, or for development activities, the Government will provide the contractor with serviceable GFE Line Replaceable Units (LRUs) applicable to the end customer’s aircraft configuration (or Interchangeable and Substitutable coded items). In the event the GFE becomes unserviceable during this effort, repair of the unserviceable GFE will be the responsibility of the Government. At the completion of this effort, these items will be dispositioned per instructions provided by the Contracting Officer Representative (COR).

3.1.2 The Government will make available, on a rent-free non-interference basis, Advanced Computer Avionics Intermediate Shop (AdC AIS), Improved Avionics Intermediate Shop (IAIS), Versa Module European Extensions for Instrumentation (VXI) IAIS, and Rackmount IAIS (R-IAIS) test stations for systems integration tasks on this program for the period of this effort if the GFP is not already accessible to the contractor under another Government contract.

3.1.3 The Government will make Government-archived technical data available to the contractor (if available) for use during Product Support Integration activities.

3.1.4 When technical work is performed on-site at Government facilities the Government will provide work space, working supplies, furniture, and access to business telephones (for business purposes only), computer databases, computer facilities, and computer time, at no cost to the contractor.

3.1.5 GFP ATTACHMENT

3.2 Services: The contractor shall furnish all material, Support Equipment, tools, general purpose test equipment, and services required to perform Product Support Integration activities under this effort (excluding exceptions cited above)

3.3 Foreign Disclosure: Foreign Disclosure Restrictions apply.

SECTION IV

GENERAL INFORMATION

4.1 GENERAL WORK REQUIREMENT

The contractor shall be responsible for the accomplishment of all systems sustaiment integration tasks necessary to support USAF and EPAF/FMS intermediate and depot maintenance level operational requirements as requested by the Government in accordance with the PWS.

4.1.1 Data

4.1.1.1 Contract Data Requirement List (CDRL): The contractor shall prepare and submit the following documents and media in support of this work effort in accordance with the CDRL Exhibits cited below.

FORM/REPORT SHORT TITLE FORM/REPORT TITLE APPLICABLE CDRL EXHIBIT

/DIRECTIVE

Monthly Status Reports Contractors Progress, Status and Management A001, DI-MGMT-80227/T Report

Engineering Drawings Product Drawings/Models and Associated Lists A002, DI-SESS-81000E

Supplemental Data for Provisioning Supplemental Data for Provisioning A003, DI-ALSS-81557/T

Computer Product End Items Computer Product End Items A005, DI-MCCR-80700/T

System Test Specification (STS) Test Requirements Document A006, DI-ATTS-80041A/T

Technical Reports Technical Report Study/Service A007, DI-MISC-80508B/T

SERD Reports Logistics Product Data A009, DI-SESS-81758A

Program Management Plan Program Management Plan A00C, DI-MGMT-81797 /Phase-In Transition Plan

Phase-Out Transition Plan Phase-Out Transition Plan A00D, DI-MGMT-81945

Technical Manual Contract Technical Manual Contract Requirements A00E, DI-TM-8601P/T

Requirements (TMCR)

4.1.1.2 Technical Data: The contractor shall modify technical data in accordance with the contractor’s engineering directives, internal drawings and procedures, acceptance test procedures, and other procedures as agreed upon by the contractor and the Government, and directed by the Government.

4.1.2 Security

4.1.2.1 The contractor shall comply with all requirements of the DD Form 254, Department of Defense Contract Security Classification Specification, attached to this contract.

4.1.2.2 This effort has a valid Facility Clearance with SECRET safeguarding capabilities. The contractor shall require access to For Official Use Only (FOUO) information and also require access to Program and Security Classification Guides. Contractor personnel shall receive and generate classified information, fabricate, modify, or store classified hardware, have access to classified information outside the U.S., Puerto Rico, U.S. possessions and trust territories, and have Operations Security (OPSEC) requirements. The contractor shall ensure that all technical, analyst, and managerial personnel tasked to perform duties in support of this effort have security clearances at the SECRET or higher level. Strictly administrative duties performed by contractor personnel shall not require a security clearance; however, personnel assigned these duties may require an investigation for sensitive duties.

4.1.2.3 All EPAF/FMS tasks shall be performed in accordance with International Traffic in Arms Regulations (ITAR) and Export Administration Regulations (EAR). The contractor and Directorate of Defense Trade Controls (DDTC) registered subcontractors utilizing the FMS exemption (126.6(c)) for defense services, technical exchanges, and delivery of hardware, must ensure the respective Letter of Offer and Acceptance (LOA) is valid at the time exports are performed. If the LOA expires and is unable to be renewed/extended prior to the delivery of hardware, technical data, and defense services, the EPAF/FMS customer will be responsible for ultimate delivery.

4.1.2.4 All tasks shall be performed in compliance with Technical Order 33-1-38, Cybersecurity for Automatic Test Systems and Automatic Test Equipment in FSC. Cybersecurity requirements shall be identified and defined at the Task/Delivery Order level.

4.1.3 Quality: The contractor shall establish, document, and maintain a quality system such as International Organization for Standardization (ISO) 9001:2008 as a means of ensuring that the requisite quality assurance oversight is exercised in fulfilling the requirements of this effort. The contractor shall ensure that this requirement is levied on any subcontractors used in satisfying the requirements of this effort.

4.1.4 Safety and Mishap Reporting: The contractor shall comply with safety and mishap reporting requirements as set forth in the contract.

4.2 SPECIFIC WORK REQUIREMENTS:

4.2.1 Contractor Program Management Organization

4.2.1.1 The contractor shall provide the necessary administrative, financial, quality assurance, analyst, specialist, technical, and managerial personnel and resources necessary to provide a single-point solution for system requirements. These personnel shall also provide a program management organization to manage the internal requirements, serve as the focused point of contact, and ensure all aspects of this program are adequately controlled and monitored.

4.2.1.2 The contractor shall develop and provide a Program Management Plan (PMP) in accordance with DI-MGMT-81797, Data Item Description, Program Management Plan, in their established quality system that details the activities to be performed under this effort. The PMP shall provide information on the contractor’s organization, practices and techniques to be used in managing the program, and working relationships with Original Equipment Manufacturers (OEMs) / subcontractors. The PMP shall include, but is not limited to, the plan purpose, scope, schedule, budget, performance plan, quality plan, risk plan, and any additional support plans required to complete the requirements of this effort. The PMP shall describe how the contractor will take over all contract functional areas from the outgoing contractor. It must ensure the contractor has operational control by 90 days after award. At a minimum, it shall address the following areas:

4.2.1.2.1 Evidence of working relationships with AIS OEMs (BAE Systems, San Diego, CA; and Lockheed Martin Rotary Mission Systems (LM RMS), Ft Worth, TX), and other Department of Defense contractors that could potentially be utilized as sub-contractors for the requirements of this effort

4.2.1.2.2 Identification of key personnel positions and how they will be phased-in for each of their respective areas

4.2.1.2.3 Hiring of qualified incumbent workforce and compliance with Executive Order 13495 (if applicable), or in accordance with host nation requirements

4.2.1.2.4 Approach to ensure technical experts have appropriate training and certification

4.2.1.2.5 Approach to assuming accountability of GFP / GFE (includes joint inventory with incumbent / OEM contractors)

4.2.1.2.6 Acquisition of Contractor Common Access Cards (CAC) (as required)

4.2.1.2.7 Acquisition of other facility access card(s) as applicable

4.2.1.2.8 Ensure appropriate Security clearances (if applicable)

4.2.1.2.9 Timeline for submitting contract data requirements

4.2.1.2.10 Approach to ensure open communication with incumbent contractor and the Government to include, periodic (daily, weekly, etc.) reviews documenting progress until transition is complete

4.2.1.3 The contractor shall process all changes to the established plan following their documented quality procedures. The contractor shall develop the PMP within 45 days of contract award and document completion of this activity in the corresponding monthly status reports (A00C, Program Management Plan / Phase-In Transition Plan)

4.2.1.4 Unless otherwise instructed by the Contracting Officer Representative (COR), the contractor shall participate in a Government-scheduled Kick-Off Meeting after contract award. Key Prime Contractor personnel shall participate in the Kick-Off Meeting. The purpose of the Kick-Off Meeting is to (1) aid both the Government and contractor personnel in achieving a clear and mutual understanding of all requirements, and (2) identify and resolve potential problems. The contractor shall be prepared to discuss any contract requirements requiring clarification. The Government, with mutual input from the contractor, will schedule the Kick-Off Meeting to be conducted within 30 days of contract award. The contractor shall prepare a tentative agenda for the Kick-Off Meeting and submit this agenda to the COR within 30 days of contract award. The contractor shall incorporate any COR comments into the agenda prior to the Kick-Off Meeting. Within 10 business days after Kick-Off meeting conclusion, the contractor shall provide meeting minutes.

4.2.1.5 The contractor shall provide system level support for problem resolution and sustainment activities to ensure operational capability of existing ATE. This support includes component design and specialty engineering; data management; and configuration management activities. This support shall also include analysis of deficiencies not previously identified during operational use of fielded equipment. Support and sustainment activities shall be provided at Air Force Life Cycle Management Center (AFLCMC) and Air Force Sustainment Center (AFSC) facilities, the contractor’s facility, or at field sites when required by 416 SCMS.

4.2.1.6 The contractor shall provide Rough Order of Magnitude (ROM) estimates as requested by 416 SCMS to support anticipated sustaining engineering tasks not previously identified. The ROMs shall include, at a minimum, draft pricing and availability data to 416 SCMS for use during development of FMS Letters of Request (LOR) and Letters of Offer and Acceptance (LOA). To ensure the ROMs accurately depict LOR and LOA requirements, the contractor shall possess the ability to independently identify and validate end user requirements through review of vendor configuration databases.

4.2.1.7 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.

4.2.1.8 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.

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

4.2.1.10 The contractor shall analyze different logistics support approaches for candidate systems and, if necessary, conduct Non-Recurring Engineering (NRE) activities to develop sustainment alternatives for the ATE components and TPS programs.

4.2.1.11 The contractor shall travel as required to attend Program Management Reviews (PMRs), Working Group meetings, Technical Interchange Meetings (TIMs), quality oversight activities, and design reviews. Reference paragraph 4.2.10 for travel guidelines.

4.2.1.12 The contractor shall develop and provide a Phase-Out Transition Plan in accordance with DI-MGMT-81945, Phase-Out Transition Plan, providing a detailed description of the transfer of full assumption of duties to the follow-on contractor. The Phase-Out Transition Plan shall describe how the contractor will support the transition from incumbent to follow-on contractor. It must ensure the follow-on (incoming) contractor has operational control by 90 days after award. At a minimum, it shall address the following areas:

4.2.1.12.1 Identification of work in progress with steps remaining in order to complete work

4.2.1.12.2 Property accountability and property book transfer

4.2.1.12.3 GFP / GFE Inventory and transfer (includes joint inventory with incumbent / OEM contractors)

4.2.1.12.4 Certified complete and accurate list of all service employees (defined in the Service Contract Act of 1965, 41 USC 357(b)) and Executive Order 13495, to include seniority

4.2.1.12.5 Removal of Contractor Property

4.2.1.12.6 Data and information transfer

4.2.1.12.7 Deletion of password access to Government systems

4.2.1.12.8 Installation clearance actions (including turn in of vehicle passes, Installation badges, and Common Access Cards (CAC)

4.2.1.12.9 Other actions required to ensure continuity of operations

4.2.1.12.10 Critical path schedule for risk mitigation of the transition period

4.2.1.12.11 Clean-Up of contractor work areas

4.2.1.12.12 Security debriefings for incumbent personnel holding security clearances

4.2.1.12.13 Account closure (involves preparation of administrative documentation and archive of data to the Government

4.2.1.13 The contractor shall develop the Phase-Out Transition Plan explaining actions required (to include the aforementioned functional areas) to complete the total transition effort within a 60 calendar day transition period.

4.2.2 Hill AFB Site Sustaining Engineering Support

4.2.2.1 The contractor shall provide logisticians, analysts, specialists, or sustaining engineering technical experts, as needed for on-site direct mission support at Hill AFB, UT and other Government facilities in support of USAF and EPAF/FMS programs. The contractor shall ensure that personnel assigned to these engineering tasks are fully knowledgeable of AFSC and/or AFLCMC-managed requirements for USAF and EPAF/FMS avionics intermediate and depot maintenance level ATE, TPSs, SE, and PME, as well as related operational support infrastructure requirements.

4.2.2.2 The contractor shall act as a liaison for ATE, TPS, and system questions with contractors, Hill AFB Avionics Integration Support Facility (AISF), and Hill AFB Depot personnel. Liaison services shall include attendance at meetings, reviews, and the preparation of engineering information needed to support AFSC and/or AFLCMC (DI-SESS-81000E, Product Drawings/Models and Associated Lists).

4.2.2.3 The contractor shall monitor the operational status of fielded ATE, TPS, SE, and PME equipment. The contractor shall coordinate field site requests for assistance in resolving issues relating to test system operations, request failure data for analysis of reported problems, provide engineering assistance (organic or contractor), identify failure trends, and recommend appropriate hardware, software, or Technical Order changes.

4.2.2.4 The contractor shall coordinate Software Product Anomaly Report (SPARs) from weapon system field sites, Hill AFB AISF, Hill AFB Depot, and contractor engineering and testing facilities. These reports, at a minimum, include problems related to test station operations, diagnostics, calibration, self-test software, or ATE, TPS, SE or PME software. The contractor shall generate deficiency and problem reports based on impact and severity to the test system. The contractor shall review, and categorize reports for work by the responsible engineering facility for sustaining engineering investigation and analysis. The contractor shall coordinate and schedule software Verification and Validation testing, testing facilities, and configuration of software releases incorporating remedies to reported anomalies. The contractor shall also edit, test, and review operating software loading instructions for inclusion in the appropriate Technical Order.

4.2.2.5 The contractor shall create Field Service Bulletin (FSB) and Time Compliance Technical Order (TCTO) instructions for hardware modifications, enhancements, and operating software releases. The contractor shall prepare kit build-up documentation; schedule, coordinate, and support field kit proofs; coordinate release of final TCTOs; and monitor and report TCTO accomplishments (DI-TM-8601P/T Technical Manual Contract Requirements).

4.2.2.6 The contractor shall develop and maintain hardware and software acquisition and sustainment plans, and provide the hardware, software and documentation identified in the plans. The contractor shall draft, process, and disseminate the information on AF Forms 1243, CPIN/AFCRI Data and Control Record Part 1, and AFMC Forms 873, Time Compliance Technical Order Requirements, as required to support hardware and software requirements; generate Computer Program Identification Number (CPIN) labels; manage ATE and software Material Improvement Project (MIP) bucket changes; and manage related Line Replaceable Unit (LRU) software changes affecting AFLCMC and/or AFSC-managed equipment (DI-MCCR-80700/T, Computer Product End Items).

4.2.2.7 The contractor shall organize, schedule, and participate in Software Compatibility Tests (SCTs) and software Validation and Verification (V&V) activities; provide technical inputs, as well as develop and maintain software program schedules, plans, checklists, documentation and procedures; schedule, organize, and conduct Technical Order (TO) risk reduction activities; coordinate software kit-proofs; sustain software programs with respect to the corrective maintenance, performance improvement, and adaptive maintenance within the bounds of existing system specifications; and identify and provide manuscripts for ATE TOs impacted by aircraft LRU software updates and hardware related procedures.

4.2.2.8 The contractor shall review software documentation for adequacy, completeness, and consistency; monitor software documentation delivery schedules; and identify software problems and/or improvements.

4.2.2.9 The contractor shall provide practical familiarization training to USAF and EPAF/FMS equipment end-users consistent with current Air Education and Training Command (AETC) and Defense Security Cooperation Agency (DSCA) requirements (DSCA Manual 5105.38-M, C10.17.18.2).

4.2.2.10 The contractor shall analyze failure data, perform trend analysis for AFSC-managed equipment, and provide technical reports, as requested by the Government, in compliance with DI-MSC-80508B/T, Technical Report Study/Services.

4.2.3 Item Unique Identification (IUID) Support

4.2.3.1 The contractor shall provide logisticians, analysts, specialists, or sustaining engineering technical experts, as needed, to implement an IUID capability and provide technical direct mission support for AFSC-managed weapons systems and commodities. The contractor shall execute a plan for the implementation of the IUID capability. This plan shall, at a minimum, include:

4.2.3.1.1 Developing and implementing an On-The-Job (OJT) training strategy for affected personnel

4.2.3.1.2 Providing IUID Item Identification and Valuation technical support to AFSC and/or AFLCMC in accordance with DFARS 252.211-7003

4.2.3.1.3 Maintaining and updating TOs, Work Control Documents, Process Orders, and engineering documentation affected by IUID implementation

4.2.3.1.4 In conjunction with Depot maintenance personnel, identifying and procuring materials and equipment, to include (but not limited to): readers, scanners, marking equipment, and modems to ensure compliance with MIL-STD-130N, Department of Defense Standard Practice: Identification Marking of U.S. Military Property and DOD Directive 5000.1, The Defense Identification System

4.2.3.1.5 Developing a process outline for ensuring IUIDs are captured in the Air Force Serial Database, Wide Area Workflow (WAWF), or manually entered into the IUID Registry at https://www.bpn.gov.iuid

4.2.3.1.6 The contractor shall provide and maintain a tabular master list of assets that have been appropriately marked with IUID information as well as those assets that still require IUID information marking in accordance with DI-MGMT-81804A, Item Unique Identification (IUID) Marking Activity, Validation and Verification Report.

4.2.3.2 The contractor shall develop, maintain, and update depot, intermediate, and organizational-level TOs for PME and Support Equipment components affected by IUID implementation. As part of the implementation process, the contractor shall draft, coordinate, and disseminate the information on Air Force Technical Order (AFTO) Forms 22 and AFTO Forms 252 (for MIP changes and field/depot generated TO change requests), and analyze the effects of potential changes (DI-TM-8601P/T, Technical Manual Contract Requirements).

4.2.3.3 The contractor shall classify SE technical data change recommendations, analyze the influence of SE changes on current maintenance operations; evaluate AFTO Forms 22, draft AFTO Forms 252, prioritize SE change data implementation; and support SE TO Review Board (TORB) and mid-TORB activities as requested by the Government (DI-TM-8601P/T, Technical Manual Contract Requirements).

4.2.3.4 The contractor shall complete, track, and maintain the status of action items; document technical activities, update and maintain schedules and guides relating to IUID activities; monitor scheduled milestones, and provide the program status to the Government (DI-MGMT-80227/T, Monthly Status Report).

4.2.4 Diminishing Manufacturing Sources and Material Shortages (DMSMS) Analysis Support

4.2.4.1 The contractor shall develop and provide a plan to implement the requirements of the AIS Systems Sustainment Program for identifying and managing the loss, or impending loss, of manufacturers or suppliers of parts and/or material required for sustained operational availability of the AIS System(s), to include ATE and TPS system components (DI-MGMT-81949, Diminishing Manufacturing Sources and Material Shortages (DMSMS) Implementation Plan). The contractor shall provide logisticians, analysts, specialists, or sustaining engineering technical experts, as needed, for direct mission support addressing DMSMS resolution for AFSC-managed weapon system components to include AIS, TPS, PME and associated SE hardware.

4.2.4.2 DMSMS support shall include a Counterfeit Prevention Plan (CPP) which establishes and maintains an acceptable counterfeit electronic part detection and avoidance system for AIS ATE components, TPS components, and other hardware items identified to satisfy DMSMS requirements. The CPP shall comply with DFAR-252.246-7007, and include provisions to enforce CPP adherence for all subcontractors utilized in completing work identified in this PWS.

4.2.4.3 The DMSMS Implementation Plan may utilize obsolescence / DMSMS data delivered to the Government via sustainment contracts in order to develop a total systems approach in identifying and resolving obsolescence. The DMSMS Implementation Plan shall be for each system configuration and shall include the methodologies, processes, tools, resources and strategies required to provide sustained operational availability for all program systems. It shall include the interfaces between the contractor and OEMs / subcontractors as well as other entities, both industry and government.

4.2.4.4 The contractor shall identify both the reactive and proactive obsolescence management processes that will be used for DMSMS resolution. Once implemented, in accordance with DI-MGMT-81948, Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan, the contractor shall implement a proactive DMSMS Management process. The management process approach shall include reactive and proactive management strategies that address life cycle obsolescence issues related to the system. ANS/Techamerica STD-0016-2012, SD-22 Guidebook, and MIL-STD-3018 may be used for guidance. The contractor shall research and analyze component provider capabilities to ensure that production of legacy hardware can be continued. In the event required component resources cannot be sourced to meet production or sustainment requirements, the contractor shall take all actions required to mitigate the shortfalls. This support shall include, but not be limited to:

4.2.4.4.1 Researching, identifying, analyzing, testing, and qualifying replacement components for use in the production and sustainment of legacy hardware (to include DMSMS monitoring of COTS items)

4.2.4.4.2 Updating technical documentation to ensure all replacement components are fully documented

4.2.4.4.3 Developing, fabricating, testing, and qualifying replacement end-items if component part mitigation techniques are not viable in ensuring out-year support for the legacy hardware

4.2.4.4.4 Providing Cost Avoidance and Program Performance Metrics results

4.2.4.4.5 Tracking software obsolescence and life-cycle supportability, including de-support and upgrade information and requirements for software, firmware, as well as licensing tracking

4.2.4.4.6 Providing health assessment reports for systems, sub-systems, and piece part components

4.2.5 Systems Integration Logistics Support

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

4.2.5.2 As required, the contractor shall develop non-RF and RF-capable, non-deployable and deployable test capabilities; update kit provisioning documentation, and submit the developed documentation to the Government using provisioning systems, processes, and procedures acceptable to the Government. The contractor shall ensure that Source, Maintenance, and Recoverability (SMR) codes assigned to ATE components, TPSs, ancillary SE, PME, and non-RF and RF-capable non-deployable and deployable test capabilities; and update kit components identical to those assigned to like components. The contractor shall provide provisioning documentation in accordance with DI-ALSS-81557/T, Supplemental Data for Provisioning, and identify those submissions in the appropriate monthly status report (DI-MGMT-80227/T, Monthly Status Report).

4.2.5.3 The contractor shall update TOs to reflect changes to TPSs, SE, PME, update kits, and non-RF and RF-capable, non-deployable and deployable test capabilities. The contractor shall minimize non-RF and RF-capable, non-deployable and deployable test capability and update kit supportability impacts to current users by coordinating the updates with the 416 SCMS prior to incorporation. The contractor shall submit the TO change data to the Government as directed by 416 SCMS in accordance with AFMCI 21-301 and TO 00-5-3 (DI-TM-8601P/T, Technical Manual Contract Requirements). The contractor shall document TO change data submissions in the appropriate monthly status report.

4.2.5.4 The contractor shall develop or update the Calibration and Measurement Requirements Summary (CMRS) for the non-RF and RF-capable, deployable and non-deployable test capabilities. The contractor shall deliver the CMRS to the Government in accordance with DI-QCIC-80278B, Calibration and Measurement Requirements Summary (CMRS), and as specified in the Delivery Order, via letter of transmittal. The contractor shall document CMRS submission in the appropriate monthly status report (DI-MGMT-80227/T, Monthly Status Report).

4.2.5.5 The contractor shall submit new or updated SERD data, after contract award, in accordance with DI-SESS-81758A, Logistics Product Data, for the weapon system(s) being supported. The contractor shall document SERD change data submittals in the appropriate monthly status report (DI-MGMT-80227/T, Monthly Status Report).

4.2.5.6 The contractor shall update all affected aircraft, AIS, TPS, SE, PME and LRU TOs to reflect any changes necessitated as a result of SERD development and/or software updates. The contractor shall document SERD change data submittals in the corresponding monthly status reports (DI-MGMT-80227/T, Monthly Status Report).

4.2.5.7 The contractor shall update Automated Computer Program Identification Numbering System (ACPINS) with TPS and Operational Flight Program (OFP) load-file Computer Program Identification Numbers (CPIN) data, applicability information, and other data required for the SERD to be produced (DI-MCCR-80700/T, Computer Product End Items). The contractor shall update ACPINS with the relevant information as soon as possible after contract award to ensure that appropriate software can be requisitioned and distributed by the Government prior to SERD equipment delivery. The contractor shall document ACPINS update data submittals in the corresponding monthly status reports (DI-MGMT-80227/T, Monthly Status Report).

4.2.5.8 The contractor shall prepare and submit engineering drawings and logistics technical documentation in accordance with DI-SESS-81000E, Product Drawings/Models and Associated Lists.

4.2.5.9 The contractor shall review and provide the Government with weapon system AIS, TPS, SE, PME, LRU and SERD configuration data as required to ensure that the appropriate hardware and software will be delivered to new and existing test capability end item users (DI-SESS-81253, Configuration Status Accounting Information).

4.2.6 TPS Software Development or Re-Host Support

4.2.6.1 The contractor shall provide logisticians, engineers, analysts, specialists, or sustaining engineering technical experts, as needed for direct mission support of software development for testing AFSC managed weapon system components. The contractor shall ensure that personnel assigned to this task are fully knowledgeable of legacy intermediate and depot maintenance level test equipment and its related support infrastructure requirements.

4.2.6.2 In accordance with DI-MCCR-80700/T, Computer Product End Items, the contractor shall research, develop, update, integrate, test, and deliver any necessary TPS and Operational Flight Program (OFP) load file software so that the capabilities being procured will function with the non-deployable and deployable test capabilities currently possessed by the end user activity. The contractor shall ensure that updates to TPS software include incorporation of all outstanding Software Product Anomaly Report (SPARs) against the software baseline currently being updated and are in compliance with the most recent System Test Specification (DI-ATTS-80041A/T, Test Requirements Document). The contractor shall research, develop (if required), update, integrate, test, and deliver all OFP load file software for customer weapon system components for which OFPs have been formally released as part of this or previous test capability procurements.

4.2.6.3 The contractor shall coordinate all F-16 AIS system TPS development and OFP load file development activity with 516 SMXS/MXDEE to ensure that TPS development and OFP load file development activities are not duplicated.

4.2.6.4 When submitting updated or newly developed TPS or OFP load file software, the contractor shall ensure that the software submittal package contains the following:

4.2.6.4.1 Two executable disks for Ogden-managed software or three executable disks for Oklahoma City or Warner Robins-managed software

4.2.6.4.2 One source disk for Ogden-managed software or two source disks for Oklahoma City or Warner Robins-managed software

4.2.6.4.3 One document disk for Ogden-managed software or two document disks for Oklahoma City or Warner Robins-managed software

4.2.6.4.4 Software Configuration Management (SCM) Delivery Record

4.2.6.4.5 Engineering Change Notice/Parts List (ECN/PL) Worksheet

4.2.6.4.6 Software Quality Assurance (SQA) Confirmation Report

4.2.6.4.7 Listing of SPARs incorporated into the software

4.2.6.4.8 Source File listing

4.2.6.4.9 Computer Program Requirements Matrix (CPRM) File

4.2.6.4.10 LRU End-To-End Run Sheet for each station configuration impacted by the Computer Program Identification Number (CPIN)

4.2.6.4.11 Automated Computer Program Identification Number System (ACPINS) Master CPIN Report

4.2.6.5 The contractor shall develop or update technical data impacted by TPS development or re-host support activities. This support shall include, but not be limited to:

4.2.6.5.1 Updating all affected aircraft, LRU, SE TOs to reflect any changes necessitated as a result of software updates.

4.2.6.5.2 Updating the ACPINS with TPS and OFP load file CPIN data, applicability information, and other data as appropriate for the software to be delivered.