AIS_PSI PWS_Final.docx

PERFORMANCE WORK STATEMENT (PWS) FOR

F-16 AVIONICS INTERMEDIATE SHOP (AIS) PRODUCT SUPPORT INTEGRATION (PSI) PROGRAM

CONTRACT: TBD

DATE: 20 July 2022

PREPARED BY: NICOLE CHECKETTS 416 SCMS/GUMAA

6070 GUM LANE

BLDG 1213

HILL AFB, UT 84056-5825

Disclosure Notice - This information is furnished on the condition that it will not be released to another nation without specific authority of the Department of the Air Force of the United States, that it will be used for military purposes only, that individual or corporate rights originating in the information, whether patented or not, will be respected, that the recipient will report promptly to the United States any known or suspected compromise, and that the information will be provided substantially the same degree of security afforded it by the Department of Defense of the United States. Also, regardless of any other markings on the document, it will not be downgraded or declassified without written approval of the originating U.S. agency.

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/WAM (F-16 Division), AFLCMC/WNA (ATS Division), or the 516 Software Engineering Squadron (SWES). 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) 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 systems integrator who provides a single-point solution for F-16 Avionics Intermediate Shop (AIS) series Automatic Test System (ATS) requirements delegated to the AIS Systems Sustainment Program Office in the 416 SCMS. Requirements may include 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 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 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. The contractor shall provide functional management oversight of test system hardware and software component development and production programs. Therefore, the contractor shall not perform in AIS test system hardware, software, or TPS development or production as the primary function of product support integration. The contractor shall provide non-biased oversight, thereby delivering technically sound solutions that are cost effective and beneficial for the Government. 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.

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) activities 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.2 TERMS EXPLAINED:

“AdC AIS”: Advanced Computer Avionics Intermediate Shop “AFLCMC”: Air Force Life Cycle Management Center “AFSC”: Air Force Sustainment Center “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.

“ATE”: Automatic Test Equipment “ATP”: Acceptance Test Procedures “C&S”: Control and Support “CDRL”: Contract Data Requirements List “CMRS”: Calibration and Measurements Requirements Summary “Component”: An assembly or any combination of parts, subassemblies, and assemblies mounted together in manufacture, assembly, maintenance, or rebuild.

“COOP”: Contingency of Operations Plan “COR”: Contracting Officer Representative “CPI”: Critical Program Information “CPIN”: Computer Program Identification Number “DMSMS”: Diminishing Manufacturing Sources and Material Shortages “ETIMS”: Enhanced Technical Information Management System “EPAF”: European Participating Air Force “FMS”: Foreign Military Sales “GFE/M”: Government Furnished Equipment/Materials “GFP”: Government Furnished Property “IAW”: In Accordance With “IAIS”: Improved Avionics Intermediate Shop “ICO”: Installation and Checkout “IPPS”: Initial Provisioning Performance Specification “ISO”: International Organization for Standardization “ITA”: Interface Test Adapter “ITAR”: International Traffic in Arms Regulations “IUID”: Item Unique Identification “LOA”: Letter of Offer and Acceptance “LRU”: Line Replaceable Unit “NRE”: Non-Recurring Engineering “OEM”: Original Equipment Manufacturer “OFP”: Operational Flight Program “ORSK”: Operational Readiness Support Kit “PME”: Prime Mission Equipment “PMP”: Program Management Plan “PPS”: Provisioning Performance Schedule “PSI”: Product Support Integration “PWS”: Performance Work Statement “R-IAIS”: Rackmount Improved Avionics Intermediate Shop “ROM”: Rough Order of Magnitude “SCRM”: Supply Chain Risk Management “SCMG”: Supply Chain Management Group “SCMS”: Supply Chain Management Squadron “SE”: Support Equipment “SERD”: Support Equipment Recommendation Data “SGML”: Standardized General Markup Language “TIM”: Technical Interchange Meeting “TPS”: Test Program Set “USAF”: United States Air Force “VXI-IAIS”: Versamodule Extensions for Instrumentation Improved Avionics Intermediate Shop “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 Task Orders 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:

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

2.3

4.8, 4.8.1, 4.8.2 Rough Order of Magnitude (ROM) submitted 100% complete NLT 30 to 60 days after receipt of request to meet the objective. Rough Order of Magnitude (ROM) submitted 100% complete prior to 30 days after receipt of request to exceed expectations.

SECTION III

GOVERNMENT FURNISHED PROPERTY (GFP) AND SERVICES

3.1 GFP/GFE:

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, and/or each applicable Task Order, as appropriate, items will be dispositioned per instructions provided by the Contracting Officer Representative (COR).

3.1.2 The Government may make available, on a rent-free non-interference basis, AdC AIS, IAIS, VXI-IAIS, and R-IAIS test stations for systems integration tasks on this program for the period of this effort if the GFE is not already accessible to the contractor under another government contract.

3.1.3 GFP/GFE ATTACHMENT: GFP/GFE needed to meet requirements will be identified utilizing the appropriate forms (i.e., Government Furnished Property and/or Tab 34-Availability of GFE) at the Task Order level.

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

3.1.5 When technical work is performed on-site at government facilities, the Government will provide workspace, office supplies, access to computer data bases, and other resources, as defined by Task Order, at no cost to the contractor.

3.2 Services: The contractor shall furnish all material, SE, 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.

Date: 20 July 2022

SECTION IV

GENERAL INFORMATION

4.1 GENERAL WORK REQUIREMENT: The contractor shall be responsible for the accomplishment of all systems sustainment integration tasks necessary to support USAF and EPAF/FMS intermediate and depot maintenance level operational requirements, as requested by the Government, and defined at the Task Order level.

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.

/DIRECTIVE

A001, DI-MGMT-81928/T

A002, DI-SESS-81000F/T

A003, DI-SESS-81874

A004, DI-SESS-81758A/T

SERD Recommendation Data

Logistics Product Data Summaries

A005, DI-SESS-81759A/T

Calibration and Measurements Requirements Summary

Calibration and Measurements Requirements Summary (CMRS)

A006, DI-QCIC-80278C/T

Computer Software Product End Items

Computer Software Product End Items

A007, DI-AVCS-80700A/T

System Test Specification

Test Requirements Document

A008, DI-ATTS-80041/T

A009, DI-MISC-80508B/T

A010, DI-MGMT-81804A/T

A011, DI-MGMT-81949/T

A012, DI-MGMT-81948/T

Program Management Plan/Phase-In Transition Plan

Phase-Out Transition Plan

Phase-Out Transition Plan

A014, DI-MGMT-81945/T

Technical Manual Contract Requirements

Configuration Status Accounting Information

Configuration Status Accounting Information

A016, DI-SESS-80858D/T

A017, MIL-STD-38784B

Software Version Description

Software Version Description (SVD)

A018, DI-IPSC-81442A

Commercial Drawings, Models and Associated Lists

Commercial Drawings, Models and Associated Lists (CDMAL)

A019, DI-SESS-81003F/T

A020, DI-NDTI-80603A

Software Design Description

A022, DI-IPSC-81440A

A023, DI-NDTI-80809B/T

Test Reports

Acceptance Test Report (ATR)

A024, DI-QCIC-81891

Test Plans/Test Procedures

Test Plans/Test Procedures

A025, DI-SESS-81704

A026, DI-IPSC-81438A

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, in compliance with the applicable Data Item Descriptions (DIDs).

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 the contract.

4.1.2.2 This effort has a valid Facility Clearance with SECRET safeguarding capabilities. The contractor shall require access to Controlled Unclassified Information (CUI) and Program and Security Classification Guides. Contractor personnel shall receive and generate classified information, fabricate, modify, and/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. 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 applicable EPAF/FMS customer(s) will be responsible for the ultimate delivery.

4.1.3 Supply Chain Risk Management

4.1.3.1 The contractor shall identify, assess, plan for, and mitigate actual or potential threats, vulnerabilities, and disruptions to the USAF’s supply chain throughout its lifecycle to ensure mission effectiveness. The contractor shall inform and include the Government in any mitigations or alterations to the program. The Supply Chain Risk Management (SCRM) plan shall address the broad spectrum of supply chain risks that have the potential to: jeopardize the integrity of products, services, people, and technologies; compromise intellectual property; disrupt the flow of product, materiel, information, and finances needed for continued USAF operations; and drive materiel cost increases to the program.

4.1.3.2 The contractor shall develop and execute processes for identifying supply chain risks as early as possible, to include: the persistent and comprehensive tracking, monitoring, and re-evaluation of supply chain risks and their corresponding mitigation actions; and communicating supply chain risks to affected stakeholders and the Government. The contractor shall notify the Government in writing of identified actual and potential supply chain risks (A028, DI-MGMT-81889, Risk Management Status Report).

4.1.3.3 The contractor's SCRM program and processes shall apply to the prime and their suppliers, subcontractors, associated integrators, and vendors, spanning the entirety of the supply chain, from the raw material stage to delivery of a finished product and/or service.

4.1.3.4 As part of the overall SCRM approach, the contractor shall establish, document, and maintain documentation about subcontractors/vendors for all parts that will be used for government contracts. The contractor shall continuously monitor their sources of supply for unknown, unauthorized, non-certified, or unqualified sources providing parts or services from any sub-tier supplier within the contractor’s supply chain. The contractor shall investigate and submit findings to include root causes, impacts, and corrective action (A028, DI-MGMT-81889, Risk Management Status Report).

4.1.4 Contingency of Operations

4.1.4.1 The contractor shall include a SCRM plan detailing the offeror’s supply chain risk management approach, providing specific emphasis on the risks associated with the following: Continuity of Operations, Foreign Influence, and Cybersecurity.

4.1.4.2 The contractor shall detail the specific supply chain risk and provide a management and mitigation plan identifying how the offeror will ensure Supply Chain Risk Management is effective over the life of the contract.

4.1.4.3 The contractor shall develop and/or update a Continuity of Operations Plan (COOP), also known as a Business Operations Plan, which outlines the processes and actions to prepare for, and respond to, unplanned natural and man-made disruptions to mission essential operations and provide it to the Government. The COOP will address disruptions caused by the following:

4.1.4.3.1 Natural causes possible in the local vicinity (winter weather, earthquakes, hurricanes, fires, flooding, wind, pandemics, etc.)

4.1.4.3.2 Man-made causes (cyber-attacks, electrical outages, strikes affecting workforce, civil unrest, modes of transportation, and receiving/shipping goods, etc.)

4.1.4.4 In the event of disruption, the COOP will explain the following contingencies:

4.1.4.4.1 How work will continue in the same or alternate facility(ies)

4.1.4.4.2 Ability to use and/or augment the current workforce.

4.1.4.4.3 Ability to repair/restore key infrastructure (machinery, computers, logistics, etc.)

4.1.4.4.4 How to maintain communication with the Government and others in the supply chain

4.1.4.5 The contractor shall provide essential records management for personnel working on USAF contracts. Records will be accessible to key members of the organization. The contractor shall ensure continuous records management support (training, etc.) despite any change in personnel.

4.1.4.6 If required, the contractor shall prepare for the continuation of essential DoD services during crisis IAW DFARS 252.237-7023, DFARS 252.237-7024, and other applicable references as necessary. In a state of emergency, if the Government deems necessary, the contractor shall provide all services necessary to ensure mission accomplishment. On occasion, services may be required to support activation, or exercise of contingency plans outside normal duty hours.

4.1.5 Foreign Influence

4.1.5.1 The contractor shall disclose any Foreign Ownership, Control, or Influence for the purpose of initial or continued facility clearance eligibility. A Standard Form 328 Certificate Pertaining to Foreign Interest shall be submitted to the Government cognizant security office specified in each DD254.

4.1.5.2 The contractor shall provide information regarding Foreign Ownership, Control, or Influence. The contractor shall provide an update on its financial health and potential Foreign Ownership, Control, or Influence when a merger or acquisition occurs.

4.1.5.3 Foreign contractor participation is excluded at the prime and subcontractor level, unless authorized through a current approved National Interest Determination (NID). It is solely the responsibility of the contractor to obtain necessary certification from the U.S. Department of State and to comply with the federal laws and regulations. Questions must be directed to the U.S. Department of State’s Directive of Defense Trade Controls.

4.1.6 Cybersecurity

4.1.6.1 The contractor shall develop and implement a cybersecurity protection of supply chain information plan and provide a copy to the Government. The contractor shall conduct early and continuous monitoring throughout the contract to prevent or reduce impacts of cyber vulnerabilities where adversaries are able to exploit, steal, alter, manipulate, interrupt, or destroy system functionality, information, or technology. The contractor’s plan shall address the following:

4.1.6.2 Make specific reference to those aspects of the National Institute of Standards and Technology Special Publication (NIST SP) 800-161, Supply Chain Risk Management Practices for Federal Information Systems and Organizations, that represent the contractor’s implemented processes and practices.

4.1.6.3 Include a description of how the contractor shall protect the supply chain from exploitation due to the insertion of counterfeits/malware, unauthorized production, tampering, theft, insertion of malicious software and hardware, functionality alteration, and any other elements that would allow adversaries to gain unauthorized access to data, alter data, interrupt communications, or otherwise disrupt operations.

4.1.6.4 Inform the Government of any instances of unauthorized access and/or compromise to the contractor’s digital information, parts, and/or components.

4.1.6.5 Make specific reference to those aspects of NIST SP 800-53 that represent the processes and practices the contractor will implement. The plan and processes shall apply to the prime and their suppliers, subcontractors, associated integrators, and vendors, spanning the entirety of the supply chain from raw the material stage to delivery of a finished product.

4.1.6.6 The contractor and any subcontractors shall provide to the Government a system security plan (or extract thereof) and any associated plans of action developed to satisfy the adequate security requirements of DAFRS 252.204-7012, and in accordance with NIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, in effect at the time the solicitation is issued or as authorized by the Contracting Officer, to describe the contractor’s unclassified information system(s)/network(s) where covered defense information associated with the execution and performance of this contract is processed, is stored, or transmits.

4.1.6.7 The contractor shall develop/update an incident-handling capability plan that utilizes guidance provided in NIST SP 800-61, Revision 2, Computer Security Incident Handling Guide, consisting of the following:

4.1.6.7.1 Incident response policy and plan

4.1.6.7.2 Procedures for performing incident handling and reporting.

4.1.6.7.3 Guidelines for communicating with outside parties regarding incidents.

4.1.6.7.4 Incident team structure and staffing model.

4.1.6.7.5 Relationships and lines of communication between the incident response team and other groups, both internal and external

4.1.6.7.6 Services the incident response team should provide.

4.1.6.7.7 Staffing and training the incident response team

4.1.6.8 Any incident reported to Defense Industrial Base Cybersecurity Program shall also be rapidly reported to the responsible Contracting Officer.

4.1.6.9 The contractor shall provide information to obtain a Defense Intelligence Agency-Threat Assessment Center (DIA-TAC) Report when Critical Components are known based on Functional Thread Analysis. The contractor shall trace the Bill of Materials to the lowest critical components. The contractor shall update design via system engineering processes to ensure above-medium risk components are not in the system.

4.1.6.10 The contractor shall ensure all hardware, with special emphasis on lowest Critical Components and components containing Critical Program Information (CPI), are from trusted sources and are manufactured by approved personnel as documented in the contractor Security Plan. The contractor shall develop a SCRM plan documented in the contractor Security Plan, IAW the current version of Committee on National Security System Directive (CNSSD) No. 505 and NIST SP 800-61, to mitigate supply chain risk.

4.1.6.11 The contractor shall ensure that no critical components procured are on the Section 806 (National Defense Authorization Act for Fiscal Year 2011 (Public Law 111-383)) and Section 2339a (Title 10, United States Code) Lists in the Supplier performance Risk System (SPRS). The contractor shall develop and implement a Counterfeit Parts Prevention Program in compliance with Defense Federal Regulation (DFAR) 252.246-7007 Contractor Counterfeit Electronic Part Detection and Avoidance System, using SAE AS5553, SAE AS6171, SAE AS6081, and Independent Distributors of Electronics Association (IDES) Standard {IDEA-STD-1010B}) or similar practices to prevent the inclusion of counterfeit pards or parts with malicious logic. The contractor shall perform acceptance testing on lowest CCs and components containing CPI in accordance with the Counterfeit Parts Prevention Program.

4.1.6.12 The contractor shall implement DoD Trusted Systems and Networks (TSN) strategies that integrate robust systems engineering, SCRM, security, counterintelligence, intelligence, cybersecurity, hardware and software assurance, and information systems security engineering disciplines to manage risks to system integrity and trust IAW DODI 5200.44, Protection of Mission Critical Functions to Achieve TSN.

4.1.6.13 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 Order level.

4.1.7 Quality

4.1.7.1 The contractor shall establish, document, and maintain a quality system, such as International Organization for Standardization (ISO) 9001:2015, 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. The contractor shall maintain Capability Maturity Model Integration (CMMI) Level 3 Certification (appraised and maintained at Level 3) throughout the duration of this effort.

4.1.8 Safety and Mishap Reporting

4.1.8.1 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/or 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 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 be responsible for any subcontract management necessary to integrate work performed and shall be responsible and accountable for subcontractor performance. The contractor will manage work distribution to ensure there are no Organizational Conflict of Interest considerations. The contractor may add subcontractors to their team only after notification to the Contracting Officer and Contracting Officer Representative.

4.2.1.3 The contractor shall develop and provide a Program Management Plan (PMP) in accordance with A013, DI-MGMT- 81797/T, Data Item Description, Program Management Plan. The PMP shall provide information on the contractor’s organization, practices, and techniques to be utilized in managing both the program and working relationships with OEMs and/or 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 45 days after the current support task ends. At a minimum, the PMP shall address the following areas:

4.2.1.3.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/or other Department of Defense contractors that could potentially be utilized as sub-contractors for the requirements of this effort.

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

4.2.1.3.3 Approach to ensure technical experts have appropriate training and certification.

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

4.2.1.3.5 Acquisition of contractor Common Access Cards (as required)

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

4.2.1.3.7 Issuance of appropriate Security clearances (as applicable)

4.2.1.3.8 Timeline for submitting contract data requirements.

4.2.1.3.9 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.4 The PMP shall include a Phase-In Transition Plan which outlines how the contractor will establish operational control 45 days after current support task ends. The contractor shall process all changes to the established plan following their documented quality procedures. Any subsequent changes and/or amendments to the established PMP throughout the Period of Performance shall be in accordance with A013, DI-MGMT-81797/T, Data Item Description, Program Management Plan, and shall be documented in the corresponding Monthly Status Reports (A001, Monthly Status Report; A013, Program Management Plan/Phase-In Transition Plan).

4.2.1.5 The contractor shall be required to participate in a government-scheduled Kick-Off Meeting after contract award. The kick-off meeting shall be presentative of the management plan at Task Order submission. Key prime contractor personnel shall participate in the Kick-Off Meeting. The purpose of the Kick-Off Meeting is to:

4.2.1.5.1 Aid both the Government and contractor personnel in achieving a clear and mutual understanding of all requirements.

4.2.1.5.2 Identify and resolve potential problems. The contractor shall be prepared to discuss any contract requirements calling for 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.6 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 compliance 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 Sustainment Center (AFSC) facilities, Air Force Life Cycle Management Center (AFLCMC) facilities, the contractor facilities, or at field sites when required by Task Order.

4.2.1.7 The contractor shall provide Rough Order of Magnitude (ROM) estimates as requested by 416 SCMS to support anticipated sustaining engineering tasks not previously identified, at no cost to the Government. The ROMs shall include, at a minimum, draft pricing and availability data to 416 SCMS for use during development of FMS Letters of Request 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.8 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.9 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 deficiencies.

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

4.2.1.11 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 ATE components and TPS hardware.

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

4.2.1.13 The contractor shall develop and provide a Phase-Out Transition Plan in accordance with A014, DI-MGMT-81945/T, 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 45 days after the current support task ends. At a minimum, it shall address the following areas:

4.2.1.13.1 Identification of work in progress with steps remaining in order to complete work.

4.2.1.13.2 Property accountability and property book transfer

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

4.2.1.13.4 Removal of contractor property

4.2.1.13.5 Data and information transfer

4.2.1.13.6 Deletion of password access to government systems

4.2.1.13.7 Installation clearance actions (including turn-in of vehicle passes, installation badges, and Common Access Cards)

4.2.1.13.8 Other actions required to ensure continuity of operations.

4.2.1.13.9 Critical path schedule for risk mitigation of the transition period

4.2.1.13.10 Clean-Up of contractor work areas

4.2.1.13.11 Security debriefing for incumbent personnel holding security clearances.

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

4.2.1.14 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, and/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, 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. Support provided by the contractor shall be captured in the corresponding Monthly Status Report(s) (A001, DI-MGMT-81928/T, Monthly Status Report).

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 (for both organic and contract efforts), identify failure trends, and recommend appropriate hardware, software, or Technical Order changes. Support provided by the contractor shall be captured in the corresponding Monthly Status Report(s) (A001, DI-MGMT-81928/T, Monthly Status Report).

4.2.2.4 The contractor shall coordinate Software Product Anomaly Reports (SPARs) from weapon system field sites, Hill AFB Avionics Integration Support Facility, 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 (A015, TM-86-01R/T Technical Manual Contract Requirements). Support provided by the contractor shall be captured in the corresponding Monthly Status Report(s) (A001, DI-MGMT-81928/T, Monthly Status Report).

4.2.2.5 The contractor shall provide technical assistance to the government to create Field Service Bulletin (FSB) and Time Compliance Technical Order 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 Time Compliance Technical Orders; and monitor and report Time Compliance Technical Orders accomplishments (A015, TM-86-01R/T Technical Manual Contract Requirements). Support provided by the contractor shall be captured in the corresponding Monthly Status Report(s) (A001, DI-MGMT-81928/T, Monthly Status Report).

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 AFTO 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 (A007, DI-AVCS-80700A/T, Computer Software Product End Items, A018, DI-IPSC-81442A, Software Version Description, A021, DI-IPSC-81435B, Software Design Description, A022, DI-IPSC-81440A, Software Test Report, A026, DI-IPSC-81438A, Software Test Plan, A027, DI-IPSC-81439A, Software Test Description). Support provided by the contractor shall be captured in the corresponding Monthly Status Report(s) (A001, DI-MGMT-81928/T, Monthly Status Report).

4.2.2.7 The contractor shall organize, schedule, and participate in Software Compatibility Tests 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. When directed by the Government, the contractor shall schedule, organize, and conduct Technical Order risk reduction activities; coordinate software kit-proofs; and sustain software programs with respect to corrective maintenance, performance improvement, and adaptive maintenance tasks performed within the bounds of existing system test specifications. Finally, the contractor shall provide required data for ATE TOs impacted by aircraft LRU software and hardware updates (A015, TM-86-01R/T Technical Manual Contract Requirements). Support provided by the contractor shall be captured in the corresponding Monthly Status Report(s) (A001, DI-MGMT-81928/T, Monthly Status Report).

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 requirements (Defense Security Cooperation Agency Manual 5105.38-M, C10.8.4).

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 A009, DI-MISC-80508B/T, Technical Report- Study/Services; A020, DI-NDTI-80603A, Test Procedure; A023, DI-NDTI-80809B/T, Test /Inspection Report; A024, DI-QCIC-81891, Acceptance Test Report; A025, DI-SESS-81704, Test Plans/Test Procedures).

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 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 Ensuring government readers, scanners, marking equipment, and modems are in 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 appropriate Air Force Serial Databases/Systems identified at the Task Order level.

4.2.3.1.6 Providing and maintaining 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 A010, DI-MGMT-81804A/T, Item Unique Identification (IUID) Marking Activity, Validation and Verification Report.

4.2.3.2 The…