PWS Revision 6 APG 66_68 .pdf

CUI

PERFORMANCE WORK

STATEMENT (PWS)

AN/APG 66/68 RADAR

POST-PRODUCTION SUSTAINMENT

FOLLOW-ON SUPPORT BASIC

Indefinite Delivery Indefinite Quantity

(IDIQ)

Revision 6

5 June 2025

Prepared By:

Brenda Frost

AFLCMC/WAMI

Hill AFB, UT 84056

TABLE OF CONENTS

TITLE PAGE

Table of Contents 2

1.0 Scope 4

1.1 Purpose 4

1.2 Security Classification 4

1.3 Accident/Incident Reporting 4

1.3.1 Security of Contractor Systems 4

1.3.2 Operating Security 4

1.3.3 Freedom of Information Act 4

1.3.5 Controlled Unclassified Information 5

1.3.6 Protection of CUI 5

1.3.7 Security Classification Guide 6

1.3.8 Personnel Security 6

1.3.8.3 Security Incidents and Violations 6

1.3.9 Reporting Requirements 6

1.3.10 Proprietary Information 6

1.3.11 Confidentiality of Information 7

1.3.12 Critical Advanced Technologies 7

1.4 Accident/Incident Reporting and Investigation 7

1.5 Government Furnished Data 7

1.6 Proprietary Data 7

1.7 Definition of Terms 7

1.7.1 Core and Non-Core Terms 7

1.7.1.1 Core Tasks and Services 7

1.7.1.2 Non-Core Tasks and Services 7

1.7.2 Participating Air Forces 8

2.0 Background 8

2.1 General 8

2.2 Program Management 8

2.3 Task Approvals 9

3.0 Core Tasks 9

3.1 Contractor Tasks (Core) 9

3.2 Task Delivery Order Reports (Core) 9

3.3 Program Meetings (Core) 10

3.4 Design Process Documentation (Core) 10

3.5 DMSMS Support Management (Core) 10

3.5.1 Engineering Support for DMSMS 10

3.5.2 Integrated Logistics Support for DMSMS 10

3.5.3 DMSMS Facilitator 11

3.6 Technical Support (Core) 11

3.7 System Support and Services (Core) 11

3.7.1 Logistics Support Analysis (LSA) (Core) 11

3.7.2 Logistics Support Analysis Record (LSAR) (Core) 11

3.7.3 System Test Specifications (STS) (Core) 12

3.7.4 Technical Order Customer Interface and Assistance (Core) 12

3.7.5 Spares Provisioning Office Support and Services (Core) 12

3.8 Industrial Base (Core) 13

3.8.1 Manufacturing Capability Oversight/Assessment (Core) 13

3.8.2 Provide Industrial Engineering (I.E.) (M.E.)/Test Engineering 13

3.8.3 Storage and Maintenance of Government Furnished Equipment (GFE) 13

3.9 Program Management and Administration (PM) (Core) 14

3.9.1 Program Management Task (Core) 14

3.9.2 Contracts Management (Core) 14

3.9.3 Contracts Financial Management (Core) 14

3.10 Configuration Management (Core) 14

3.11 Data Management (Core) 15

3.11.1 Data Accession List (Core) 15

3.11.2 Configuration Data (Core) 15

3.11.3 Engineering Data (Core) 15

3.11.4 Marking of Technical Data (Core) 15

4.0 Contractor Tasks (Non-Core) 15

4.1 Contractor Tasks (Non-Core) 15

4.2 Engineering Technical Support (Non-Core) 15

4.2.1 Requirement Analysis (Non-Core) 16

4.2.2 Design Support Testing (Non-Core) 16

4.2.3 Field Failure Analysis (Non-Core) 16

4.3 Field Reliability and Supportability (Non-Core) 16

4.3.1 Technical Support (Non-Core) 16

4.3.2 On-Site Customer and Product Support (Non-Core) 16

4.3.3 System Support and Services (Non-Core) 16

4.3.4 Vendor Data Base (Non-Core) 16

4.4 System Test Specifications (STS) (Non-Core) 17

4.5 Technical Orders (Non-Core) 17

4.6 Limited Repair (Non-Core) 17

4.7 Modification Support (Non-Core) 17

4.8 Modification Kit Acquisition (Non-Core) 17

4.9 Fabrication (Non-Core) 17

5.0 DIDS/CDRLS 18

5.1 CDRLs 18

6.0 Manpower Reporting 19

6.1 Reporting Period 19

6.2 Services Summary 19

6.3 Uses and Safeguarding of Information 20

6.4 User Manuals 20

1.0 Scope - This Performance Work Statement (PWS) describes the efforts required by the Contractor to continue an F-16 Radar System Post-Production Support Program that takes into consideration the European Participating Air Force (EPAF) and Foreign Military Sales (FMS) program needs as well as those of the USAF.

1.1 Purpose - This Performance Work Statement (PWS) describes tasks to be performed by “the Contractor”. Its purpose is to provide engineering services, modification kits and replacement parts for kits (as required), software development and delivery, and comprehensive integrated logistics support to the USAF F-16 System Program Director (SPD) and System Support Manager (SSM) for the F-16 Radar System Post-Production Support Plan (PPSP). Support is available to the United States Air Force (USAF), United Stated Navy (USN), European Participating Air Forces (EPAF), Foreign Military Sales (FMS) customers.

1.2 Security Classification - The contractor shall comply with the F-16 Security Classification Guide in effect at the time this contract is accepted and the DD254 (attached) for requirements in handling, dissemination, and storage of any classified data and information associated with the performance of this PWS.

1.3 Security Requirements -This PWS requires a Department of Defense (DD) Form 254, Department of Defense Contract Security Classification Specification. The Contractor shall comply with the requirements specified in the DD Form 254 and this PWS regarding handling, transportation, dissemination, storage, and protection of any classified data/material/equipment developed or handled under this PWS. In addition, the Contractor shall comply with the F-16 Security Classification Guide in effect at the time of this contract.

1.3.1 Security of Contractor Systems - The Contractor shall ensure the security of information systems at the Contractor’s facility to preclude potential security incidents or violations including potential unauthorized disclosure or compromise of classified and/or controlled unclassified information.

1.3.2 Operating Security (OPSEC) - The contractor shall ensure OPSEC is incorporated into the appropriate area of the contract IAW DoD Directive 5205.02E, DoD Operations Security (OPSEC) Program and AFI 10-701, Air Force OPSEC Program. The Contractor shall flow down all OPSEC requirements to subcontractors that handle Critical Information (CI). CI is defined as specific facts about friendly intentions, capabilities, or activities needed by adversaries to plan and act effectively against friendly mission accomplishment.

1.3.3 Freedom of Information Act (FOIA) - The Contractor shall comply with DoD Directive 5400.07_AFMAN 33-302, DoD Freedom of Information Act Program, requirements. The regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding of Controlled Unclassified Information (CUI) material.

The Contractor shall comply with AFI 33-332, Air Force Privacy and Civil Liberties Program, when collecting and maintaining information protected by the Privacy Act of 1974 authorized by Title 10, United States Code, Section 8013. The Contractor shall remove or destroy official records only IAW AFI 33-322, Records Management and Information Governance Program.

1.3.5 Controlled Unclassified Information (CUI)

1.3.5.1 The contractor shall comply with DoD Instructions 5200.48_DAFI 16-1403, Controlled Unclassified Information, DoDM 5200.01, Vol 1_AFMAN16-1404, Vol 1, Air Force Information Security Program: Overview, Classification and Declassification, and DoDM 5400.07_AFMAN 33-302 Freedom of Information Act Program. The contractor shall monitor CUI aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information.

1.3.5.2 The Contractor shall distribute controlled unclassified information IAW DoD Instruction 3200.12, DoD Scientific and Technical Information Program (STIP), and DoD Instruction 2040.02, International Transfer of Technology, Articles, and Services. The Contractor shall properly mark all such documents IAW DoD Instruction 5230.24, Distribution Statements on Technical Documents. Technical documents not subject to distribution are defined in DoD Instruction 5230.24, DoD Directive 5230.25, Withholding of Unclassified Technical Data from Public Disclosure, and DoD Manual 5010.12-M, Procedures for the Acquisition and Management of Technical Data.

1.3.6 Protection of Controlled Unclassified Information (CUI)

1.3.6.1 Controlled Unclassified Information is any information that law, regulation, or government wide policy requires to have safeguarding or disseminating controls, excluding information that is classified under Executive Order 13526, Classified National Security information, December 29, 2009, or any predecessor or successor order, or the Atomic Energy Act of 1954, as amended.

1.3.6.2 Controlled Unclassified Information (CUI) is information that requires safeguarding or dissemination controls pursuant to and consistent with applicable law, regulations, and governmentwide policies but is not classified under Executive Order 13526 or the Atomic Energy Act, as amended.

1.3.6.3 The National Archives and Records Administration (NARA) CUI Registry (http://www.archives.gov/cui/registry/category-list.html) identifies approved CUI categories and subcategories, provides general descriptions for each, identifies the basis for controls, and sets out procedures for the use of CUI.

1.3.6.4 The contractor shall comply with DoDI 5200.48_DAFI16-1403, Controlled Unclassified Information, and DAFMAN 16-1404 Vol 1-3 Air Force Information Security Program. The contractor will consult the applicable security classification guide to monitor CUI aggregation for potentially generating classified information by compilation. 3.4.6.5 The Contractor shall comply with DODM 5400.07_AFMAN 33-302, DoD Freedom of Information Act (FOIA) Program, requirements.

1.3.6.5 Protection of CUI and unclassified DoD information not approved for public release on non-DoD Information Systems will be protected IAW DoD Instructions 8582.01, Security of Non-DoD Information Systems Processing Unclassified Nonpublic DoD Information. Unless specific categories of CUI require more stringent controls, non-DoD Information Systems must http://www.archives.gov/cui/registry/category-list.html) be protected using the guidelines set forth in NIST Special Publication 800-171, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations.

1.3.6.6 The Contractor shall comply with DFARS 252.204-7012 Safeguard Covered Defense Information and Cyber Incident Reporting (Dec 2019) This subpart applies to contracts and subcontracts requiring contractors and subcontractors to safeguard covered defense information that resides in or transits through covered contractor information systems by applying specified network security controls. It also requires reporting of cyber incidents. The subpart does not abrogate any existing contractor physical, personnel, or general administrative security operations governing the protection of unclassified DoD information, nor does it impact requirements of the National Industrial Security Program.

1.3.7 Security Classification Guide (SCG) - The contractor shall follow the F-16 Multi-Mission Fighter Security Classification Guide and all security classification guides of systems/information associated with the program for derivative classification, identification of the level and duration of classification for specific information elements, and public release requirements.

1.3.8 Personnel Security

1.3.8.1 The Contractor shall ensure applicable Contractor personnel have security clearances at the SECRET level for proper accomplishment of contract/order requirements. The security clearance shall be obtained in accordance with the DD Form 254, Department of Defense Contract Security Classification Specification. Contractor personnel whose clearances have been suspended or revoked shall immediately be denied access to classified information and/or CUI and classified items.

1.3.8.2 The contractor shall comply with DoD Manual 5200.02, Procedures for the DoD Personnel Security Program (PSP) and DoDMAN52002.02_AFMAN 16-1405, Air Force Personnel Security Program.

1.3.8.3 Security Incidents and Violations - The Contractor shall notify the Government Contracting Activity and the Security Assistance Program Manager (SAPM) within 48 hours of any incident involving the actual or suspected compromise/loss of classified information to enable the Government to conduct immediate assessments of potential impact pending formal inquiry/investigation. Actual or suspected compromise of Covered Defense Information will be reported IAW DFARS Clause 252.204-7012.

1.3.9 Reporting Requirements - The Contractor shall comply with AFI 71-101, Volume- 1, Criminal Investigations, and Volume-2, Protective Service Matters, requirements. Contractor personnel shall report to an appropriate authority, any information, or circumstances of which they are aware that may pose a threat to the security of DoD personnel, contractor personnel, resources, and classified or unclassified defense information. Contractor employees shall be briefed by their immediate supervisor upon initial assignment and as required thereafter.

1.3.10 Proprietary Information - Performance under this PWS may generate Government proprietary data categorized as Controlled Unclassified Information (CUI) or protected under the Privacy Act of 1974. The Contractor shall not divulge, or release data or information developed or obtained under performance of this contract, except by authorized Government personnel or upon written approval of the F-16 SPO. The Contractor shall not use, disclose, or reproduce proprietary data that bears a restrictive legend.

1.3.11 Confidentiality of Information - Unless otherwise specified, all financial, statistical, personnel, and/or technical data furnished, produced, or made available to the Contractor during the performance of this contract is considered confidential business information and shall not be used for purposes other than performance of work under this contract.

1.3.12 Critical Advanced Technologies - APG-66/68 items will be handled IAW Radar Systems Export Policy and approved Anti-Tamper (AT) plans. (A023, DI-SCRE-82399, Anti- Tamper Plan)

1.4 Accident/Incident Reporting and Investigation - Report promptly to the Administrative Contracting Officer (ACO) all available facts relating to each instance of damage to government property. When a Class A or Class B mishap involving government property occurs, the contractor shall immediately secure the accident scene and damaged item until released by the accident investigative authority as designated by the contracting F-16 Safety Office. Such release shall be accomplished through the ACO. If the government elects to conduct an investigation of the accident, the contractor shall cooperate fully and assist government personnel until the investigation is completed. (A027, DI-SAFT-81563, Accident/Incident Report)

1.5 Government Furnished Data - Data/information furnished by the United States Government shall not be released to any other government without the specific approval of the respective service, department, or government agency of the United States. The information shall be afforded the same degree of security protection as that afforded to it by the respective service, department, or government agency of the United States.

1.6 Proprietary Data - If government furnished data information of a proprietary nature is furnished to the contractor, it shall not be used or disclosed in any manner. Exceptions can only be provided in writing by the PCO

1.7 Definition of Terms

1.7.1 The terms “Core” and “Non-Core” for this PWS refer to tasks and services that are within the scope of this contract.

1.7.1.1 “Core” tasks and services – Continuous support requirements identified and priced at the beginning of each ordering period as identified in the Core task order. Core tasks and services are those defined in Section 3 of this PWS and are applicable only for participating Air Forces that have funded their cost sharing in this contract. Efforts under this section require no additional funding.

1.7.1.2 “Non-Core” tasks and services – Additional estimated technical and programmatic support to be specified in distinct task/delivery orders that fall beyond the scope of Core support. Non-Core tasks and services are described in Section 4 and only support those participating Air Forces that have funded their cost-sharing portion of the Core, Section 3, of this contract. Each task/delivery order for Non-Core support shall be accompanied by a PWS, data requirements, and funding to be obligated for the effort, as applicable. All Non-Core tasks require additional funding before any effort will be started by the contractor.

1.7.2 "Participating Air Forces" are those countries that are funded members of the Core APG 66/68 Radar Follow-On Post-Production Sustainment Support program.

2.0 Background –

2.1 General - As directed in Department of Defense Directive (DODD) 5000.2 and in accordance with the latest F-16 Program Management Directive 6075 (75), the Secretary of the Air Force directs that USAF will accomplish Post-Production Support Planning for the F-16 Weapons System. A transfer agreement for management of the F- 16 Radar between the F-16 System Program Office and the F-16 Supply Chain Management Directorate was signed on 15 May 1998. At the direction of the Logistics Operations Director this effort provides the needed post-production support for the F- 16 Radar System (APG-66/APG-68). At the F-16 Executive Program Management Review of 17- 18 Mar 93, substantial changes in national defense posture and ramifications for curtailed USAF F-16 production made focus on comprehensive long range sustainability planning imperative. A resulting Action Item was generated for initiating the F-16 Falcon 2020 program to ensure long-term support and operational capability of the F-16 after production line termination.

APG 66/68 Radar Follow-On PPS Support continues requirements, originally in production contracts, which are still required to sustain the weapon system in a post-production environment. APG 66/68 Radar Follow-On PPS Support provides a minimum core of engineering and technical expertise, specialized laboratories, data systems and unique manufacturing capabilities. APG 66/68 Radar Follow-On PPS Support ensures that continuous engineering and technical expertise remains available at the prime radar contractor to provide uncompromised combat capability for the F-16 weapon system.

2.2 Program Management - This program is co-managed by the F-16 International Programs Branch AFLCMC/WAMI.

The Contracting Officer (CO) will be responsible for contract management of the basic contract and any task/delivery order initiated under the provisions of this contract vehicle by F-16 personnel. Only the CO can make changes affecting the form, structure, and content of this basic contract. Only a CO shall direct with a contract or modification, the Contractor with direction that affects performance of tasks under this contract, or to have a material impact on costs incurred in association with this contract.

Any or the above-mentioned occurrences shall be brought to the immediate attention of the appropriate Contracting Officer for disposition and instructions before proceeding with any work thus affected. (A002, DI-MISC-80508, Technical Report - Study/Services (Cost Reporting Status)) The contractor shall identify a program manager and point(s) of contact for the purpose of managing the APG 66/68 Radar Follow-On PPS Support contract.

2.3 Task Approvals - The USAF program manager at Hill AFB will determine whether the effort fits the scope of this contract and will evaluate tasks and services. USAF program manager is identified in paragraph 2.2. After evaluation and approval, the tasking will be assigned to the contractor. Individual orders will address specific tasks and associated data requirements and will provide a comprehensive definition of the scope of work to be performed. Each order will be accompanied by a PWS. The PWS will describe the support/services and/or supplied required, data requirements, scope, and purpose of the requirement. The PWS will also list items to be provided by the Government as Government Furnished Property (GFP) or Government Furnished Equipment (GFE) and items to be provided by the contractor as Contractor Furnished Material (CFM), Contractor Furnished Equipment (CFE) or Contractor Acquired Property (CAP), as applicable. The contractor shall ensure that no duplication of effort occurs between Core tasks and additional tasks directed by specific task/delivery orders.

Tasks and services that are identified as out scope for this effort under section 3 will be covered under section 4.0 and will be funded separately as a Non-Core requirement. The USAF program manager will determine which Core and Non-Core tasks are within the scope of the contract.

3.0 Description of Predefined Core Tasks - The Core pre-defined delivery order will provide continuous sustainment support for requirements as defined by a unique PWS/Statement of Work (SOW) and will be funded and cost shared by F-16 customers. The Core PWS will describe the support/ services required, data requirements, scope, and purpose of the requirement.

3.1 Contractor Tasks (Core) - The contractor shall provide specific tasks and services during the performance period consisting of engineering services and integrated logistics support for all AN/APG-66/68 F-16 Radar configurations. The core pre-defined delivery order will provide the continuous engineering, technical support, and documentation activities as outlined by a unique PWS/Statement of Word (SOW) while maintaining the high level of reliability and maintainability. (A004, DI-MISC-80508B, Technical Report - Study/Services (Engineering Technical Support))

3.2 Task/Delivery Order Reports (Core) – The contractor shall maintain a log providing the status of all task/delivery orders. Data from this log shall be provided as a monthly status report. (A028, DI-MGMT-80368A, Status Report (Monthly Status Report))

3.3 Program Meetings (Core) - Periodic Program Management Reviews (PMR) shall be held as directed by the PM (two will occur annually). These may be held at the contractor facility, Hill AFB, or virtually. These meetings will be held for the purpose of reviewing all open task/delivery orders processed against this contract on a periodic basis. The contractor shall attend all scheduled PMR meetings related to the performance of this contract. (A019, DI- ADMN-81373, Presentation Material), (A020, DI-ADMN-81250, Meeting Minutes)

3.4 Design Process Documentation (Core) - The contractor shall review and research all Revision Notices generated against items used on the F-16 AN/APG-66 and AN/APG- 68 Radar for impact at both the component and drawing level.

The contractor shall maintain the Bill of Material (BOM) database and the Information Systems for Engineering (ISE) (or equivalent) system to monitor and update the Engineering Parts List per the Program Parts Selection List (PPSL) requirements, the Engineering Drawing/Parts Lists, and the Bill of Material. (A009, DI-SESS-81000F, Product Engineering Design Data and Associated Lists)

3.5 Diminishing Manufacturing Sources and Materiel Shortages (DMSMS) Support Management (Core) - The contractor shall support management of DMSMS issues and their impact on the reliability and maintainability of the F-16 APG 66/68 Radar. (A022, DI-MGMT-81949, Diminishing Manufacturing Sources and Material Shortages (DMSMS) Implementation Plan)

3.5.1 Engineering Support for DMSMS (Core) - The contractor shall develop impact analyses, investigate alternatives, and develop viable solutions for DMSMS piece parts. The contractor shall maintain a Radar Post-Production Sustainment Support database of all DMSMS notices issued, and make recommendations for new/alternate part(s), new sources, etc. (A021, DI-MGMT-82275A, Diminishing Manufacturing Sources and Material Shortages (DMSMS) Metrics Data)

Note: Any actions recommended as a result of DMSMS activities such as hardware redesign or Design Try-Out (DTO) will not be implemented by the contractor without prior government approval and funding authorization. This authorization will be funded as a Non-Core requirement.

3.5.2 Integrated Logistics Engineering Support (Core) - The contractor shall provide Integrated Logistics Engineering Support for resolution of DMSMS by utilizing the DMSMS, Model of Assembly Level Predictions (MAP). The contractor shall provide DMSMS profiles for APG/66-68 LRU/SRU configurations under the cognizance of the Radar Post-Production Sustainment Support program or as requested by an authorized government representative. Each profile shall be updated on the semi-annual basis. The report should be provided on each following monthly status report. The DMSMS MAP analysis will be combined with component level analysis in order to present a comprehensive profile of the DMSMS problem(s) and solution(s). (A028, DI-MGMT-80368A, Status Report (Monthly Status Report)), (A029, DI-MGMT-80368A, Status Report, (Semi Annual Status Report))

3.5.3 DMSMS Facilitator (Core) - The Contractor shall provide support for all DMSMS issues through a DMSMS facilitator. The contractor shall process information and coordinate DMSMS issues. The facilitator will act as a liaison to all Radar Post-Production Sustainment Support participants (USAF/EPAF/FMS) regarding their DMSMS activities. The facilitator shall create and maintain a customer database for all APG/66-68 Radar DMSMS issues. The database will contain information such as recommendations for solutions, USAF disposition of DMSMS issues, and any other pertinent information that is used in DMSMS resolutions. The DMSMS facilitator shall maintain a copy of the latest version of DMSMS MAP. The Contractor shall also attend, with approval, Government sponsored and/or Industry sponsored DMSMS meetings for the customer.

3.6 Technical Support (Core) - The Contractor shall provide technical support for field supportability, and design issues related to the F-16 Radar System. The Contractor shall provide responses to inquiries/requests for data and documentation regarding repair histories, in the Contractor’s facility, related to LRU/SRU, replaced components summaries, configuration information, etc. This support will consist of a coordinated effort through AFLCMC/WAMI and the Contractor. The Contractor shall provide a point of contact for Hill AFB to support both hardware and software issues. The answer to each question should not exceed eight (8) hours. Answers in excess of time specified will require additional funding through Non-Core delivery order.

3.7 System Support and Services (Core) - The contractor shall provide Logistics Systems Engineering technical support and LSA data, Spares Provisioning Office support/services and Technical Order customer support necessary to meet F-16 radar supportability requirements.

3.7.1 Logistic Support Analysis (LSA) (Core) – The contractor shall provide logistics support technical assistance and customer liaison for all logistics matters.

The contractor shall coordinate the development of support requirements with the customer and other logistics functional areas. The contractor shall perform the LSA process to identify supportability issues related to requirements associated with the changes to the design of the equipment due to hardware and software changes and include identification of potential support impact risks. Enhance supportability of the equipment changes and coordinate with all logistics disciplines the integration of logistics requirements. The contractor shall assist the program office in the coordination of logistics activities including logistics data submittal reviews with the customer and program and design review. (A024, DI-ILSS-80531, Logistic Support Analysis Plan), (A025, DI-SESS-81758A, Logistics Product Data)

3.7.2 Logistic Support Analysis Record (LSAR) (Core) – The contractor shall provide updates to the customer’s LSAR to keep it current with changes in design, maintenance concept, or operation scenario. This activity will maintain the customer’s LSAR as a valuable source of logistics data throughout the term of this order. (A025, DI-SESS-81758A, Logistics Product Data)

3.7.3 System Test Specifications (STS) (Core) - STS documents outline total testing requirement and repair procedures for the units of the system using automatic, semi-automatic, and manual test equipment and procedures. STS’s include items such as unit under test (UUT) theory of operation, schematics, and block diagrams. To maintain their value to the customer, STS’s must be updated through the system life cycle. The Contractor shall review design change documentation and provide recommendations for updates to the STSs for the F-16 Radar that are a result of revision notices originated by the Contractor. The Contractor will assess the impact on test requirements due to hardware and software changes not originated by the Contractor, and/or customer complaints. (A007, DI-NDTI-80809B, Test/Inspection Report) These impacts can result from issues such as:

A- Deficiencies and errors in of source data or when revisions to source data affects test software documentation.

B- Deficiencies and errors traceable to document preparation.

C- Deficiencies and errors discovered during continuing test software development and field operation.

Note: The Contractor shall only provide recommendations for updates to the STS.

All STS updates will be performed under separately funded Non-Core tasks.

3.7.4 Technical Order (T.O.) Customer Interface & Assistance (Core) - The Contractor shall provide a representative for (CSTO) interface and assistance regarding overall T.O. status and schedules. The contractor shall assess impact due to customer recommendations and engineering changes for impacts and recommended T.O.

updates. (A016, TM-86-01, Technical Manual Contract)

Note: The Contractor shall coordinate, host, and co-chair annual scheduled Guidance Conferences to review configurations and status to existing AN/APG-66 and AN/APG-68 manuals. The Contractor shall prepare minutes for all T.O. related meetings. USAF technical data managers will review and approve the minutes before distribution. The Contractor shall maintain a complete file of all these minutes.

(A020, DI-ADMN-81250C/T, Meeting Minutes)

3.7.5 Spares Provisioning Office Support & Services (Core) - The Contractor shall provide a point of contact for Spares Provisioning Office to respond to customer requirements for data. The Contractor will respond to requests for a source of supply, requests for procurement history, drawings and drawing expertise, research of obsolete part numbers to determine proper program usage and configuration, and coordinate and interface with subcontractors and vendors to ensure program compatibility. The Contractor shall provide documentation such as Design Change Notices (DCN's), Repairable Item Breakdown/Repairable Item List (RIB's/RIL’s), and Supplementary Provisioning Technical Documentation (SPTD). The Contractor shall maintain "country specific provisioning databases" as future spares ordering instrument, configurations control tool, Source Maintenance Recoverability Code (SMR) reference. (A012, DI-ALSS-81529, Logistics Management Information (LMI) Data Product), (A013, DI-ALSS-81530, Logistics Management Information (LMI) Summaries), (A014, DI-SESS-81874, Engineering Data for Provisioning (EDFP), (Supplementary Data Provisioning)), (A006, DI-MISC 80508B, Technical Report - Study/Services (Field Reliability and Supportability))

3.8 Industrial Base (Core) - The contractor shall provide manufacturing capability oversight and assessment.

3.8.1 Manufacturing Capability Oversight/Assessment (Core) - Provide oversight and periodic assessment of equipment and process capabilities including subcontractors, universal capital tooling, contract tooling, Numerically Controlled (NC) programming, requirement to update and modify Government Furnished Equipment (GFE) Factory Test Equipment (FTE), GFE/FTE maintenance, calibration of test equipment, and special facilities requirements. (A008, DI-MGMT-81928, Contractor's Progress and Status Report (Vendor Data Base)), (A018, DI-MGMT- 82173, Government Furnished Equipment (GFE) Inventory Report)

3.8.2 Provide Industrial Engineering (I.E.)/Manufacturing Engineering (M.E.)/Test Engineering (T.E.) (Core) - Oversight of changes affecting the contractor's industrial base capability to provide F-16 Radar System hardware.

Review of affected factory changes resulting from capital resource and productivity issues. Manage and oversee total program for industrial base and summarize in a semi-annual report a status of manufacturing capability. Changes will be reviewed for manufacturing/test impact and reporting. (A006, DI-MISC 80508, Technical Report - Study/Services (Field Reliability and Supportability), (A029, DI-MGMT- 80368A, Status Report (Semi Annual Status Report))

3.8.3 Storage and Maintenance of Government Furnished Equipment (GFE) (Core) – The following requirements apply for both the IDIQ (basic contract) and those delivery orders requiring GFE/GFM.

A. The materials that the USG provides under the basic contract will be listed in

Attachment 1 (Appendix B).

B. Individual orders shall address specific tasks and associated data requirements and shall provide a comprehensive definition of the scope of work to be performed. Each order will be accompanied by a PWS. The PWS will describe the support/services and/or supplies required, disposal instructions, data requirements, scope, and purpose of the requirement.

C. The Contractor shall maintain all GFE in a serviceable condition throughout the contract period of performance. Contractor shall store Government Furnished Equipment (GFE) and Material (GFM), agency peculiar property, Special Test Equipment and tooling that is either in use in the Contractor’s factories or laboratories or storage facility. The Contractor shall have authorized, rent free usage of the APG-66/68 GFE/GFM.

D. The contractor shall coordinate with the Government Program Manager (GPM) to ensure that available GFE/GFM is received, tracked, and returned or disposed of after contract performance to the delivery order level.

E. The Contractor shall develop a system to ensure all GFE/GFM inventory status is tracked throughout the contract period of performance and provide a monthly status and inventory report utilizing a government PIEE provided template.

(A017, DI-MGMT-80269, Status of Government Furnished Equipment (GFE)

Report), (A018, DI-MGMT-82173, Government Furnished Equipment (GFE) Inventory Report)

3.9 Program Management (PM) and Administration (Core) - The contractor shall provide Program Management (PM) and administration for the F-16 AN/APG-66/68 radar system Post-Production Program. The PM will be the single point of contact to the customer responsible for compliance of the program defined by this PWS and contractual requirements. (A001, DI-MGMT-81928, Contractor's Progress and Status Report (Program Management Test)), (A002, DIMISC-80508B, Technical Report - Study/Services (Cost Reporting Status))

3.9.1 Program Management Task (Core) - The Contractor shall provide an individual to be a dedicated Program Management (PM) representative. This effort will include, but not be limited to, an individual responsible for customer requirements to determine the scope of the effort performed from program inception until the completion of the contract. The PM Office will facilitate and coordinate all functional activities to ensure compliance with this contract. The PM will also provide customer interface for all related action items and requirements associated with Technical Interface Meetings (TIMs) and Program Management Reviews (PMRs). The PM will plan and attend all scheduled customer meetings related to the performance of this contract. Two PMR meetings will occur annually, one in-person at Hill AFB and one virtually. (A001, DI-MGMT-81928, Contractor's Progress and Status Report), (A002, DIMISC-80508B, Technical Report - Study/Services (Cost Reporting Status)), (A020, DI-ADMN-81250C/T, Meeting Minutes)

3.9.2 Contracts Management (Core) - The Contractor shall identify a Contracts Representative (CR). The CR will serve as the official and formal point of contact to administer this effort both verbally and through correspondence. The CR is responsible for maintenance of the complete, official contract file. The CR is responsible for the interpretation and flow down of contract requirements, issuance of Work Statement Authorizations, Change Notices (CN), and coordination of all contractual and legal matters with the Program Manager, Financial Manager, Engineering, and other affected functional departments.

3.9.3 Contracts Finance Management (Core) - The contractor shall identify a Financial Manager (FM). The FM will be responsible for all financial aspects throughout the performance of this program. From the initial award of contract, the contractor supports program start-up, provides financial support throughout the performance of the program, and performs closeouts upon completion of the program including a final status report at program close. (A029, DI-MGMT-80368A, Status Report, (Semi Annual Status Report))

3.10 Configuration Management (Core) - The Contractor shall provide a Configuration Manager (CM). This individual shall be responsible to coordinate the preparation and review of Revision Notices (RN’s), Specification Change Notices (SCN’s), and Engineering Change Proposals (ECP’s). The CM shall also perform Configuration Control Board (CCB) administrative tasks including preparation of agenda/minutes and Information Systems for Engineering (ISE) interface in the electronic approval of RN’s.

3.11 Data Management (Core) - The Contractor shall provide a representative for all data and data management activities in accordance with the contract. The Contractor shall maintain a data repository and shall support internal personnel in data management related issues. The Contractor shall generate and deliver data in accordance with the tasks set forth in this contract. The Program Manger shall act as a liaison and provide customer interface for all data management issues.

3.11.1 Data Accession List/Internal Data (Core) - The Contractor shall maintain a complete list of all internally controlled data generated by the Contractor as a result of this contract. (A010, DI-MGMT-81453B, Data Accession List (DAL))

3.11.2 Configuration Data (Core) - The Contractor shall maintain the configuration of all delivered hardware. Contractor drawings for revisions shall comply with the guidance of DOD-STD-100. Revision authorization shall depict approved configuration changes and the reason(s) for the change(s). (A009, DI- SESS-81000F, Product Engineering Design Data and Associated Lists)

3.11.3 Engineering Data (Core) - The Contractor shall update, revise, and maintain engineering data in support of the sustainment program. The Contractor shall deliver only internally generated new and revised engineering data that has not been supplied previously as part of a production contract. The deliverable data shall be in a form compatible with the existing Hill AFB electronic digital data storage system (A-TEAM). An index file in accordance with 9579776.

(A009, DI-SESS-81000F, Product Engineering Design Data and Associated Lists)

3.11.4 Marking of Technical Data (Core) - The contractor shall mark all technical data with appropriate distribution statements and export control-warning notices in accordance with this contract.

4.0 Undefined Tasks

Each task/delivery order requirement beyond the scope outlined in paragraph 3.1 will be defined by a unique PWS/SOW and will be funded and/or cost shared by the appropriate customer(s). Tasks may be similar to those described in previous paragraph

3.1 but are of greater magnitude or have other peculiar significance.

4.1 Contractor Tasks (Non-Core) - All tasks and services that are assigned to this section are considered Non-Core and require additional funding. Refer to paragraph 1.4 and 2.3 for further explanation. CDRL’s for any Delivery Order (D.O.) used in the contractor tasks must be called out on the individual D.O.

4.2 Engineering Technical Support (Non-Core) - The contractor will perform the following as needed as part of the post-production support. The contractor will be authorized to perform each task and the funding will be supported by individual D.O.’s.

(A004, DI-MISC-80508B, Technical Report - Study/Services (Engineering Technical Support))

4.2.1 Requirement Analysis (Non-Core) - The contractor shall perform design trade-off studies and analyses to accurately address performance requirements.

These studies shall include, but not limited to the following areas: Hardware, Software, DMSMS replacement candidates (prototype/limited production), and reliability/maintainability improvements. These studies and analyses shall determine the optimum system design approach. These studies shall also play a major role in the establishment of new requirements within the framework of existing designs. (A003, DI-MISC-80508B, Technical Report - Study/Services (Requirement Analysis))

4.2.2 Design Support Testing (Non-Core) - The contractor shall provide the engineering and test support required to ensure product integrity and reduce program risks associated with the incorporation of radar design and development changes. These changes could be a result of requirement changes, DMSMS issues, Design Tryouts (DTO’s), or other reasons. This task includes RN and DTO preparation, execution of the DTO, and the associated drafting effort.

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

4.2.3 Field Failure Analysis (Non-Core) - The contractor shall provide for support of field failure investigation requests under formal customer activities including Project Quality Deficiency Reports (PQDRs), Engineering Project Requests (EPRs), Service Reports (SRs), and Material Improvement Projects (MIPs). The contractor shall manage the tracking, analysis, and report generation. In addition, the contractor shall produce a monthly status report of the results of the investigations providing customer visibility to cost, work in process, and asset disposition. (A030, DI-MISC-80508B, Technical Report - Study/Services (Field Failure Report))

4.3 Field Reliability and Supportability (Non-Core) - The Contractor shall support investigations of field reliability issues. This will include travel, analysis, resolution development, and reporting as appropriate. (A006, DI-MISC 80508B, Technical Report - Study/Services (Field Reliability and Supportability))

4.3.1 Technical Support (Non-Core) - The contractor shall provide technical support as requested to support the software development activities performed by the Air Force. The contractor shall provide various other “hands on” technical support as requested and contracted for by the Air Force.

4.3.2 On-Site Customer and Product Support (Non-Core) - Provide on-site support by field engineers and technicians to assist the customer with analysis and evaluation to the radar system. Proper export licenses/authority must be in place.

4.3.3 System Support and Services (Non-Core) - The contractor shall provide on an as required basis the logistics support and continuous engineering services necessary to meet F-16 radar supportability requirements.

4.3.4 Vendor Data Base (Non-Core) - The contractor shall maintain as required, radar approved supplier list as the supplier base for military devices, declinations, and changes. Monitor industrial trends for overall supplier continued viability; specifically manage Diminishing Manufacturing Sources Materiel Shortage (DMSMS) situations to make sure continuous material availability. (A026, DI-MGMT-82338, Product Family Prime Vendor Support Status Report)

4.4 System Test Specifications (STS) (Non-Core) - Provide corrections and updates to the current LRU and SRU STS for F-16 Radar configurations that result from:

A- Deficiencies and errors in source data or when revisions to source data Affects test software documentation.

B- Deficiencies and errors traceable to document preparation.

C- Deficiencies and errors discovered during continuing test software development and field operation.

These documents outline total testing requirement and repair procedures for the units of the system using automatic, semi-automatic, and manual test equipment and procedures. STS include items such as unit under test (UUT), theory of operation, schematics, and block diagrams. (A007, DI-NDTI-80809B, Test/Inspection Report)

4.5 Technical Orders (Non-Core) - The contractor shall provide and deliver Technical Order (T.O.) maintenance updates (ED online) in accordance with TM-86-01 (A016, TM-86-01, Technical Manual Contract). All updates shall conform to the general style and format requirements of the manual being updated. These updates shall be furnished throughout the period of performance or fiscal year covered by the contract. T.O.

updates shall conform to T.O. Publication Change Request.

(AFMC form 252 and AFTO form 22 as provided by Hill AFB). All illustrations shall be line drawings.

4.6 Limited Repair (Non-Core) - The contractor shall provide limited repair of the GFE, GFM and STE items under evaluation, and other radar type items. (A011, DI-MISC- 80508B, Technical Report - Study/Services (Tech Report Repair & Return)), (A015, DI- MISC-81371, Maintenance Data Collection Record (MDCR))

4.7 Modification Support (Non-Core) - The contractor will support radar modifications.

Example: Aircraft that come from the Aerospace Maintenance and Regeneration Center (AMRC) and are to be reconfigured to the requirements of the customer. This will also include other modification requirements that may generate.

4.8 Modification Kit Acquisition (Non-Core) - The contractor will provide limited modification kit production and assembly.

4.9 Fabrication (Non-Core) - The contractor shall design, develop, and provide limited manufacturing/production. Manufacturing/Production may be provided to resolve critical support issues or to construct prototypes/pre-production units in sufficient specified quantities to allow for both contractor and government testing. The contractor shall also consider long term logistics support analysis concerns and life cycle cost impacts. The contractor shall provide for the limited manufacture/ production of parts, components, systems, support equipment, test equipment, etc. as necessary to meet mission critical functions as determined by the Air Force and as directed by the delivery order.

5.0 DIDS/CDRLs

5.1 Contract Data Requirements List (CDRL) – Deliverable Contract Data Requirement List

(CDRL) data generated in the performance of Delivery/Task Orders shall be submitted per DD Form 1423. Additional data items may be added in the future as required by individual Delivery Orders. New data items may be added to the basic contract for possible future use.

CDRLs are for reference to identify requirements throughout the APG 66/68 Radar Follow- On PPS Support contract. CDRL A004 will apply to all delivery orders.

CDRL DID NUMBER TITLE SUBTITLE DUE

A001 DI-MGMT-81928/T Contractor's Progress and Status

Report Program Management Test As Requested Per

Delivery Order A002 DI-MISC-80508B/T Technical Report - Study/Services Cost Reporting Status As Requested Per

Delivery Order A003 DI-MISC-80508B/T Technical Report - Study/Services Requirement Analysis As Requested Per

Delivery Order A004 DI-MISC-80508B/T Technical Report - Study/Services Engineering Technical Support As Requested Per

Delivery Order A005 DI-NDTI-80809B/T Test/Inspection Report Test/Inspection Report DTO As Requested Per

Delivery Order A006 DI-MISC 80508B/T Technical Report - Study/Services Field Reliability and Supportability As Requested Per

Delivery Order A007 DI-NDTI-80809B/T Test/Inspection Report Test Inspection STS Updates As Requested Per

Delivery Order A008 DI-MGMT-81928/T Contractor's Progress and Status

Report Vendor Data Base As Requested Per

Delivery Order A009 DI-SESS-81000F/T Product Engineering Design Data and Associated Lists Product Engineering Design Data & Associated Lists

As Requested Per Delivery Order

A010 DI-MGMT-81453B Data Accession List (DAL) Data Accession List As Requested Per Delivery Order

A011 DI-MISC-80508B/T Technical Report - Study/Services Tech Report Repair & Return As Requested Per Delivery Order

A012 DI-ALSS-81529/T Logistics Management Information (LMI) Data Product

Logistics Man Info (Data products) As Requested Per Delivery Order

A013 DI-ALSS-81530/T Logistics Management Information (LMI) Summaries

Logistics Man Info (Summaries) As Requested Per Delivery Order

A014 DI-SESS-81874 Engineering Data for Provisioning

(EDFP)

Supplementary Data Provisioning As Requested Per Delivery Order

A015 DI-MISC-81371/T Maintenance Data Collection Record

(MDCR)

Maintenance Data Collection As Requested Per Delivery Order

A016 TM86 Technical Manual Contract Technical Manual Contract As Requested Per Delivery Order

A017 DI-MGMT-80269/T Status of Government Furnished Equipment (GFE) Report

Status of Government Furnished Equipment (GFE) Report

As Requested Per Delivery Order

A018 DI-MGMT-82173 Government Furnished Equipment (GFE) Inventory Report

GFE Inventory Report As Requested Per Delivery Order

A019 DI-ADMN-81373 Presentation Material Presentation Material As Requested Per Delivery Order

A020 DI-ADMN-

81250C/T

Meeting Minutes Meeting Minutes As Requested Per Delivery Order

A021 DI-MGMT-82275A Diminishing Manufacturing Sources and Material Shortages (DMSMS) Metrics Data

DMSMS Metrics Data As Requested Per Delivery Order

A022 DI-MGMT-81949 Diminishing Manufacturing Sources and Material Shortages (DMSMS) Implementation Plan

DMSMS Implantation Plan As Requested Per Delivery Order

A023 DI-SCRE-82399 Anti-Tamper Plan Anti-Tamper Plan As Requested Per Delivery Order

A024 DI-ILSS-80531 Logistic Support Analysis Plan Logistic Support Analysis Plan As Requested Per Delivery Order

A025 DI-SESS-81758A Logistics Product Data Logistics Product Data As Requested Per Delivery Order

A026 DI-MGMT-82338 Product Family Prime Vendor Support Status Report

Product Family Prime Vendor Support Status Report

As Requested…