PBL Follow-On_PWS_5-8-24.docx

E-3G Airborne Warning and Control System (AWACS) Block 40/45 Enterprise Performance Based Logistics (PBL) Contract

FA8102-24-D-00XX

E-3G Airborne Warning and Control System (AWACS) Performance Based Logistics (PBL) Follow On

Performance Work Statement (PWS)

OASIS Contract Number: XXXXXXXXXXXXXX Task Order Number: FA8102-25-F-XXXX Solicitation Number: FA8102-24-R-XXXX Program Number - USAFE3G-613BK58J4

1 Apr 2025

BASIC

AFLCMC/HBS

3001 Staff Drive STE 2AH1 98C Tinker Air Force Base, OK 73145

DOCUMENT CHANGE RECORD

E-3G Airborne Warning and Control System (AWACS) Block 40/45 Enterprise Performance Based Logistics (PBL) PWS Solicitation #: FA8102-24-R-XXXX Task Order #: FA8102-25-F-XXXX Program Number - USAFE3G-613BK58J4

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors only (Critical Technology), 1 April 2025. Other requests shall be referred to AFLCMC/HBS, 3001 Staff Drive. STE 2AH1-100B, Tinker AFB OK 73145.

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979 (Title 50, U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

HANDLING AND DESTROYING UNCLASSIFIED/LIMITED DISTRIBUTIONS DOCUMENTS. Unclassified/Limited Distribution documents shall be handled using the same standard as “Controlled Unclassified Information (CUI)” material and will be destroyed by any method that will prevent disclosure of contents or reconstruction of the document.

Contents

Tables and Figures Table 1. Performance Incentive Metrics for Tinker AFB and PACAF Mission Support ………………… Table 2. Meetings & Reviews………………………………………………………………………..……..…….29

Figure 1. Graphical Depiction of Product Support Management Services

PROGRAM OVERVIEW

Objective The objective of this contract is to provide performance-based life cycle sustainment for the E-3G Airborne Warning and Control System (AWACS) Block 40/45 Enterprise (herein referred to as the Block 40/45 Enterprise), Internet Protocol Enabled Communications (IPEC), and Secure Iridium Communications (SIC). The objective of this requirements set is to provide for sustainment of existing parts and new parts identified as engineering solutions for supply chain, Diminishing Manufacturing Sources & Material Shortages (DMSMS), and Reliability, Availability, Maintainability - Cost (RAM-C) issues.

E-3G AWACS Block 40/45 Description The E-3G AWACS provides a highly mobile, flexible, survivable theater Battle Management (BM), Wide Area Surveillance, and Command and Control (C2) capability. It is capable of detecting, identifying, and tracking airborne and maritime targets at extended ranges as well as identifying air/ ground emitters. Gathered data is processed to enable AWACS to relay "big picture" information to C2 agencies and friendly aircraft. AWACS provides worldwide response to situations requiring immediate on-scene BM/C2 using embedded real-time surveillance for employment of U.S. and allied combat air forces. AWACS is critical to gaining and maintaining battle-space air superiority. AWACS coordinates with both tactical and C2 assets in theater to execute the air mission.

The Block 40/45 Enterprise upgrade replaces the mission computing system (MCS) on the Block 30/35 E-3B/C with an Information Technology (IT) infrastructure network utilizing predominantly business and industrial grade Commercial-Off-the-Shelf (COTS) hardware and software. The Block 40/45 Enterprise is defined by the Block 40/45 Enterprise functional and physical baselines which encompass the Block 40 (with APY-1 radar)/ Block 45 (with APY-2 radar), configured Avionics Integration Support Facility (AISF), Aircraft Systems, Ground Support System (GSS), Deployable Ground Systems (DGS), Pacific Air Forces (PACAF) Ground Support System (PGSS) and associated Peculiar Support Equipment (PSE).

At the time of contract award, there will be multiple aircraft and ground system software configurations in operation. Due to DMS issues related to COTS materials, combined with the constraints of a five (5)-year Programmed Depot Maintenance (PDM) cycle for each aircraft, there will be a mix of 4.0 software configurations in operation at the initiation of this contract.

Functional/ Physical Configuration Baselines The Functional and Physical Configuration Baselines for support equipment discussed in this section provided by the government, is defined by the list of system Program Documents, and will be made available (Bidder’s library).

Block 40/45 Enterprise The Block 40/45 Enterprise program applies to 16 U.S. AWACS aircraft, which operate out of three (3) locations: Tinker AFB, OK; JBER, AK, and Kadena AB, Japan. The Block 40/45 Enterprise includes:

Mission Computing System (MCS) The MCS is the Block 40/45 computing infrastructure on each aircraft. There are seventeen (17) Operator Workstations (OWS) which host software applications. The OWSs are connected to the network infrastructure mounted in two electronics cabinets (E74 and E77).

Ground Support System (GSS) The GSS provides mission planning, post-mission processing, Onboard-Offboard Media (OOM) generation, mission data storage, and Electronic Support Measures (ESM) database generation. There will be two (2) GSS units at Tinker AFB, PACAF locations at JBER, AK and Kadena AB, Japan will utilize PGSS installed in fixed racks. It will contain additional storage capacity when compared to a DGS.

Deployable Ground System (DGS) The DGS is a transportable variant of the GSS. There will be up to ten (10) total DGSs in operation, one of which will be located at the E-3G AISF for the AFSC Software Engineering Directorate (AFSC/SW) utilization.

Pacific Air Forces (PACAF) Ground Support System (PGSS) The GSS provides mission planning, post-mission processing, Onboard-Offboard Media (OOM) generation, mission data storage, and Electronic Support Measures (ESM) database generation. There will be two (2) PGSS, one locati at JBER, AK and Kadena AB, Japan will utilize PGSS installed in fixed racks. It will contain additional storage capacity when compared to a DGS.

558 Software Engineering Squadron (SWES) / Avionics Integrated Support Facility (AISF) The 558 SWES, located at Tinker AFB, provides software maintenance and sustainment for the Block 40/45 Enterprise. Software maintenance includes adaptive, corrective, and perfective type changes to the configured software, as well as integration of new capability for development, production, and fielding.

Supporting the 558 SWES in software sustainment, is an aircraft representative configured lab, known as the AISF. The AISF contains a DMS 4.0 shipset of aircraft equipment and a GSS.

Secure Iridium Communications (SIC) The SIC program and associated equipment is an integral part of the transition to a Net Centric Capable (NCC) AWACS. SIC provides a 40/45 E-3G secure chat solution to satisfy CENTCOM, NORTHCOM, SOUTHCOM, and PACOM operational requirements. SIC is based on a satellite communication device that provides Beyond Line-Of-Sight (BLOS) connectivity, IP support, and a narrow bandwidth capability for data and voice collaboration.

Functional/ Physical Configuration Baseline The Functional and Physical Configuration Baselines for support equipment discussed in this section provided by the government, is defined by the list of system Program Documents, and will be made available (Bidder’s library).

Internet Protocol Enabled Communication (IPEC) The purpose of IPEC is to provide the Block 40/45 aircraft with Secret Internet Protocol Router Network (SIPRNet) connectivity for Air Tasking Order (ATO), Airspace Control Order (ACO), ATO and ACO updates, chat, e-mail, and web browsing.

The IPEC system also provides improved performance and capability over the current SIC system and provides the network connectivity for the future network enablement of the Block 40/45 Enterprise. SIC is an Iridium satellite-based communications system which provides Beyond Line-of-Sight Internet Protocol (IP) connectivity enabling E-3G participation in Area of Responsibility Tactical Chat. IPEC's objective is to quickly provide the communication capability while making best use of existing Diminishing Manufacturing Sources Replacement of Avionics for Global Operations Inmarsat terminal design, reuse of some SIC components and new equipment added as part of the IPEC solution. When outside of Inmarsat coverage areas, legacy SIC capability will be provided. A secure/ non-secure Integrated Services Digital Network (ISDN) voice connection will also be provided to allow fault isolation as well as off board telephone.

The IPEC modification implements SIPRNet capability on the Block 40/45 Enterprise. IPEC provides a wideband communications capability to connect to the Department of Defense Information Network (DODIN) and will support net-centric operations and warfare. IPEC provides permanent, International Maritime Satellite (INMARSAT)-based, IP-enabled communications package supporting warfighter identified requirements for higher bandwidth SIPRNet and multi-domain networks. IPEC utilizes a commercially derived COTS based system provided sufficient IP bandwidth to simultaneously support SIPRNet connectivity for chat, ATOs, ACO updates, and e-mail with attachments. It will also support integration of additional IP datalinks [such as the DRAGON Inmarsat Swift Broadband (ISB) capability].

The IPEC system configuration and operations includes IPEC Aircraft Systems and Ground Systems. The Aircraft Systems consist of the permanently installed IPEC system. Ground systems are comprised of the Mission Support System (MSS). The Ground Systems allow for the upload of IPEC related information into the aircraft pre-mission, as well as the download of mission information off the aircraft for post-mission Mission Support Systems (MSS) The MSS is an IPEC support system comprised of two MaxVision MAXPAC computers, one (1) with 512GB Solid State Drive (SSD) and the other with no SSD and a General Dynamics Data at Rest (DaR) 400 640GB Hard Drive. The MAXPAC without the SSD works in conjunction with the DaR-400 for RED side (classified) operations while the MAXPAC with SSD is for BLACK side (non-classified) operations. The system allows for the upload of IPEC related information into the aircraft pre-mission. It also allows for downloading of mission information off the aircraft for post-mission analysis.

APPLICABLE DOCUMENTS

In the event of conflict between documents referenced herein, the contents of this PWS will be considered the superseding requirements. The following documents (will be provided via disc/appendix) are the baseline for this PWS and are provided as a guideline. Any updates to the baseline can be acquired at the following websites.

Documents Government documents listed in Applicable Documents are available at the following websites:

· Defense Technical Information Center http://www.dtic.mil/ dtic/

· Quick Search ASSIST http://quicksearc h.dla.mil/ qsSearch.aspx Industry documents listed in in this PWS may be purchased online.

Program Specific Documents listed in Applicable Documents are available upon request to the Government Procuring Contracting Officer (PCO).

CONTRACT REQUIREMENTS

Requirements Metrics The contractor shall take all actions necessary to achieve the performance payment metrics listed in Table 1. Success or failure to achieve objectives will result in monetary results as outlined in Contract Performance Payment Plan Attachment, applied on a quarterly basis. Success or failure to achieve performance thresholds in Table 3 that are not included in the performance payment plan will be reflected in the annual Contract Performance Assessment Report (CPAR). The contractor shall perform all maintenance and support to GSS IAW Performance metrics, Table 1, T.O.s, and any applicable government regulations or guidance.

· The GSS and PGSS operational availability will be tracked at the workstation level

· The contractor shall measure the metrics outlined in Table 1. The Government’s Maintenance Tracking Log, other specified maintenance tracking system, and contractor provided tracking system will be the primary means for verifying metrics.

· Exceptions to contracted metrics include hours lost due to site power failure, emergency weather evacuations, facility failure, scheduled downtime, or other circumstances beyond the Contractor's control.

· The MCS, IPEC, SIC, and DGS MICAP performance payment metrics will exclude any MICAP hours associated with parts in which the contractor is not the source of supply.

The contractor shall notify the Contracting Officer Representative (COR) via email within 24 hours of the event that affects any contract metric and submit written notification to the PCO within three (3) business days for any metric exception associated with performance payment (see Table 1).

The COR will approve any non-performance payment metric execution and the PCO will provide exception hour approvals for performance payment metrics.

Table 1. Performance Metrics for Tinker AFB and PACAF Mission Support

Operational Availability (Ao) For GSS Calculation:

Full Mission Capable (FMC) = Uptime Partial Mission Capable (PNC) = Uptime Non-Mission Capable (NMC) = Downtime.

Quarterly

Total MICAP Rate (TNMCS + TPMCS)

Calculation :

MICAP shipping hours per quarter.

Quarterly

Reported Data The contractor shall track and provide the results using the metrics listed in Table 1 and report the results using the formula/calculations specified. Contracted Metrics for Tinker AFB and PACAF Mission Support and Table 2. Reportable Metrics for Tinker AFB and PACAF Mission Support are also included in the CPAR analysis. However, Table 2 metrics are not included in the performance payment.

The contractor shall meet and report the metrics identified in Table 1 on a monthly basis. (A001/ DI MGMT-80368A) Operation Definition Operation is defined as ensuring that the systems are powered, configured, and available to complete daily tasks. Organic function means implementation and fulfillment of daily tasks is considered a Government function.

Day to day Operation of the GSS, DGS, and PGSS is an organic function, it will not be the responsibility of the Contractor.

Support GSS Support Support is defined as assisting the customer with operational usage including system administration tasks the User encounters during operation. Such system administration tasks include:

· User account setup

· User access issues

· User account issues

· Password resets, as required The contractor shall support the GSS / components (Mission Planning Cell, Post Mission Processing Cell, Maintenance Data Processing Center, Central Data Processing Center).

The contractor shall respond to requests as soon as possible, but within one (1) hour of initial contact.

The GSS at Tinker AFB is expected to be operationally available 24 hours per day, seven (7) days per week, year- round.

The contractor shall maintain and repair GSS.

Aircraft MCS Support

MCS

The contractor shall support Block 40/45 MCS aircraft.

Required System Access Utilize Government’s Maintenance Information Systems (MIS) (i.e., IMDS/G081), (or other specified maintenance tracking log) to capture system status changes. (will require NIPR and/or SIPRNET access)

· Technical Order Authoring and Publishing (TOAP)

· Basing & Logistics Analytics Data Environment (BLADE)

· Reliability and Maintainability Information Systems (REMIS)

· WEB Supply Discrepancy Report (WEBSDR)

· Joint Deficiency Reporting System (JDRS)

· ADVANA

· Installation and Mission Support Center (IMCS D043/D143)

· Joint Engineering Data Management Information & Control System (JEDMICS)

· Software License Asset Management (SL/AM)

· Dynamic Object Oriented Requirements System (DOORS)

· Procurement Integrated Enterprise Environment (PIEE)

· Supplier Performance Risk System (SPRS)

· Ground Support System (GSS) Maintenance

· dcma.mil/wbt/sir (Shipping Instruction Request) Maintenance Maintenance is defined as the actions required to preserve and restore each of the systems to an FMC status. The contractor shall maintain the GSS IAW 3.5 to achieve the performance metrics specified in Table 1.

maintenance activities The following maintenance activities include (not an all-inclusive list):

· Corrective actions to restore system functionality.

· Preventive maintenance actions (i.e., cleaning, testing, battery replacement). Applicable documents will be available in bidder’s library.

· Parts replacement/ substitution Software and Licensing Procurement Responsibility The contractor shall procure, renew, manage, and maintain commercial off the shelf (COTS) software program licenses used on each of the E-3G DMS 4.0 aircraft and associated ground systems.

The contractor shall maintain a database which tracks all required COTS software licenses, and renewals for each license as required to keep current.

The contractor shall import/provide updates semiannually, (or more frequently when requested by Government) to the Government SL/AM database tool which tracks all required COTS software licenses, and renewals for each license as required to keep current. Each aircraft systems software licenses shall be grouped and managed by assigned aircraft tail number. Each ground system software licenses shall be grouped and managed by standard designator code and serial number. During execution, the Government will provide the Contractor with written notice from the PCO of new or replacement software licenses required to the support aircraft and ground systems. (A002, DI-FNCL-82162, A003/DI-PSSS-82046) Deficiency Reporting, Investigating, and Resolution Air Force Joint Deficiency Report System (JDRS) is available to all programs and systems. It provides a comprehensive and standardized software tool to create, process, and manage Deficiency Reports (DR). Users will access JDRS via a web-browser interface at: https://jdrs.mil. JDRS Access.

Deficiency data is restricted by user access controls. Access will be approved on a need-to-know basis. Once approved, JDRS users are required to authenticate using the Common Access Card (CAC). Role-specific training must be accomplished prior to requesting a JDRS account. Training information is found at https://cs2.eis.af.mil/sites/11891/default.aspx. Prospective users must apply for JDRS "Site Access" by completing an online "New User Registration" process found at https://jdrs.mil. Additionally, non-Government employees require a Common Access Card (CAC) to access system.

The contractor shall utilize Air Force JDRS (TO 00-35D-54 "Deficiency Reporting Investigation and Resolution") from initiation to closure on Government Furnished Property (GFP), Government Furnished Equipment (GFE), and CFE, for issues that warrant generation of a deficiency report, to:

· Deficiency Report

· Investigate root cause

· Provide recommended corrective action

· Status deficiencies Contractor-Inventory Control Point (C-ICP) C-ICP Management The contractor shall establish and maintain wholesale warehouses and provide wholesale level supply support. As a rule, all components procured and managed by the contractor will be managed as Government Furnished Property (GFP) and those identified on Spares Support List (SSL) in a C-ICP to deliver capabilities required by this contract. The SSL is the authorizing document for C-ICP managed inventory. C-ICP support will include:

· Inventory Management

· Asset Management

· Maintenance Activities

· Supplier Management

· Packaging, Handling, Storage and Transportation (PHS&T)

· Configuration Management (CM)

· Logistics Reassignment

· Unique Spare Parts/ Support Equipment Supply Management SSL Delivery The contractor shall deliver the SSL quarterly via the Contract Data R Technical Report – Study/Services requirements List (CDRL). This CDRL must include Contractor-recommended changes to SSL. (A004/ DI-MISC-80508B) Pricing Guidance The Contractor will ensure accurate pricing of property IN ACCORDANCE WITH (IAW) DoD and Air Force policy (DoD 7000.14R and Accountable Property System of Record (APSR), DoDI 5000.64) directives with supported documentation. Documents supporting accountability and/or financial information will be maintained for 10 years.

Warehouse Capabilities The contractor shall operate a warehouse with capability to handle and store classified/unclassified property and comply with the requirements of DD Form 254. Disposal of classified/unclassified consumable/repairable components will be IAW the assigned demilitarization. DEMIL Codes may be found at http://dtic.mil/whs/directives/corres/pdf/416028m_vol2.pdf and DoD manual 4160.28, Vol2.

Warehouse Operation The contractor shall operate the established warehouse.

C-ICP Requirements The contractor shall be responsible for C-ICP requirements for Block 40/45 DMS 4.0 assets.

Repair of Unclassified and Classified items The contractor shall determine, procure, repair, service, store, receive and dispose of classified and unclassified recoverable and expendable designated peculiar items / consumables pertaining to the Block 40/45 Enterprise, IPEC, and SIC in which the contractor is the source of supply.

Stock Replenishment The contractor shall be responsible for the procurement, replenishment, repair, and service of stocked items in the C-ICP inventory, as listed in SSL.

Internal Controls System The contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession as per 10 U.S.C 4324(d).

Procedures Maintenance The contractor shall maintain the procedures identified 15.

Physical Inventory The contractor shall perform semi-annual physical inventory IAW with DFARS PGI 245.103-73.

The contractor shall maintain a current record of the physical inventory as it progresses and report IAW provided instructions. (A005/ DI-PSSS-80727A/T) Periodic Inspections The contractor shall conduct monthly 5% or greater spot-checks and conduct physical inventories IAW DoD and Air Force policy directives.

Results Submission The contractor shall submit results from all inventories performed. (A006/ DIMGMT-80259) Inventory Accuracy The contractor shall perform property control and maintain a 98% or better inventory accuracy for unclassified components and 100% accountability for classified components.

C-ICP Inventory Disposition The contractor shall disposition C-ICP inventory through Scrap or Disposal when it is determined not beneficially repairable, in excess, or obsolete. Considerations such as lead time for new procurement, out of production items, mission requirements and Operations Tempo, must be considered prior to determining that an asset is beyond economical repair.

The contractor shall consider other considerations and their effect on performance prior to disposing of any asset determined as beyond economical repair. All classified parts will be disposed of quarterly (or whenever determined) using NSA/CSS POLICY MANUAL 9-12 STORAGE DEVICE SANITIZATION AND DESTRUCTION MANUAL dated 4 December 2020 (or the most current manual) and methods described in AFMAN 17-1301 COMPUTER SECURITY (COMPUSEC), Section 5.

The contractor shall maintain a record of all disposition actions which at a minimum, includes a destruction report including serial numbers, detailed chain of custody, and Certificate of Destruction (CoD).

Performance Considerations The contractor shall notify the Government within ten (10) business days requesting disposition on disposing of assets. The Government has five (5) business days to respond to the disposition request of any asset determined to be beyond economical repair.

Scrap Material The contractor shall notify the Government within ten (10) business days from the time the requirement arises to scrap material at Source of Repair (SOR). Government has five (5) business days to respond to disposition request. If disposition request is disapproved, the Contractor will issue disposed property to the Air Force for processing to Defense Reutilization and Marketing Service (DRMS).

Disposition Actions The contractor shall maintain a record of disposition actions and report the disposition actions quarterly.

Classified Material Handling The contractor shall submit disposal of material request, to include contractor sanitization procedures, to PCO within five (5) business days of identification. The PCO has five (5) business days to provide the Contractor with disposition decision letter. Disposal of classified/ unclassified consumable/ repairable components will be IAW with the assigned demilitarization (DEMIL) code. DEMIL Codes may be found at http://dtic.mil/whs/directives/corres/pdf/416028m_vol2.pdf and DoD Manual 4160.28, Vol 2 dated 9 March 2017 The contractor shall comply with the requirements of DoD Contract Security Classification Specification DD Form 254 to handle, and store classified material.

The contractor shall maintain 100% inventory accuracy for classified components.

Inventory Management inventory management to the Block 40/45 Enterprise, IPEC, and SIC spares The contractor shall provide inventory management to the Block 40/45 Enterprise, IPEC, and SIC spares. Inventory Management includes all elements of inventory management:

· Requisition processing

· Storage

· Shipment

· Delivery

· Pick-up

· Receiving

· Shipping

· In-transit visibility/ tracking/ reporting

· Property accountability

· Handling of classified material Inventory Management System (IMS) The contractor shall utilize an Inventory Management System (IMS), IAW 3.8.1, capable of interfacing with DoD and Air Force systems through the Defense Logistics Agency’s Defense Automated Addressing System (DAAS) using Defense Logistics Management Standards (DLMS) transactions. This includes maintaining accountability records in the Air Force Accountable Property System of Record (APSR), the Defense Property Accountability System (DPAS), for property in the contractor’s possession. Contractors that do not have an IMS capable of interfacing with DPAS can use the Self-Service module to maintain accountability records.

The Contractor’s IMS is required to contain records for the program’s parts that provide comprehensive logistics, procurement, and technical data required to accomplish supply support analysis, parts ordering, property accountability, and funds control.

The contractor shall capture (in their IMS) the following for each asset:

· Part number

· Source of Supply (SOS)

· SOR

· Item Unique Identification (IUID) number

· Asset usage data

· Repair data

· Warranty data

· Cost data

· Special PHS&T requirements The contractor shall ensure these part records are structured in the IMS to maintain:

· Part configuration control

· Approved part substitution and interchangeability identification

· Serialized item control

· Notice of special handling requirements

· Record item consumption data Contractor Accountability The contractor shall remove components from Contractor accountability by reducing the inventory balance in the IMS after an item is physically scraping in place at Source of Repair (SOR) or issuing disposed of property at the Main Operating Base to the Air Force for processing. (A007/ DI-MGMT-81947B,) The contractor shall maintain a record of disposition actions and report IAW reporting instructions.

The contractor shall comply with all inventory reporting requirements for DoD's Financial Improvement and Audit Remediation requirements. This includes, but not limited to, accurately reporting all transactions required to maintain accountability records for contractor managed and possessed GFP in the Government's APSR. (A008/ DI-MGMT-80438B,) The contractor shall maintain accurate and auditable records. (A008/ DI-MGMT-80438B) The contractor shall provide key supporting documentation for transactions within two (2) business days upon request. (A008/ DI-MGMT-80438B) The contractor shall adhere to policies for contractor managed and possessed CFP IAW DoD and Air Force Policy directives.

Contractor Supported Weapon System (CSWS) Data Exchange (DE)/ D375 CSWS DE is the bridge between CLS activities and Air Force legacy systems that do not allow commercial access. It is the single automated source of mission essential packaging, shipping, and transportation data, repair destination routing, asset ownership, and stock balances on C-ICP managed assets to the warfighter. Access to CSWS DE is available through the AF Portal and requires a valid CAC/PKI, DD 2875, sponsor letter and non-disclosure statement. Forms are available through the application owner identified on the AF Portal. Refer to the Interface Requirements Agreement (IRA) for interfacing with DoD supply systems. The CSWS DE D375 Home Page is https://www.my.af.mil/cswsdeprod/CSWSWeb. Access to the Home Page is available once all forms are completed and the user's AF Portal ID is associated with the D375 user account.

The contractor shall gain and maintain access to CSWS DE/ D375.

The contractor shall complete all training materials available on the Training & Documentation page to become familiar with the workings of the application and its functionality. This includes:

· CSWS Student Training Course Guide

· CSWS DE Simulation tool

· CSWS DE Checklists

· CSWS DE User's Manual The contractor shall enter required data as identified in the CSWS DE Student Training Course Guide and the CSWS DE Checklists on the Training & Documentation page within D375. This includes but is not limited to:

· Basic management data

· Asset Data

· Item management and equipment specialist data

· Packaging and transportation data

· Logistics reassignment data

· Spares computation data Asset Management Wholesale Level Stock Control Functions The contractor shall accomplish the following wholesale level stock control functions:

· Requirements and requisitioning (to provide item identification)

· Validate requirements

· Record and track acquisitions

· Respond to various priorities

· Issue appropriate procurement release authority

· Accomplish requisitions IUID labels The contractor shall provide IUID labels to applicable parts, IAW DFARS 252.211-7003 and DoDI 8320.04 and update the IUID registry in the DoD Wide Area Workflow (WAWF). The contract shall mark items IAW MIL-STD-130N. (A009/ DI-MGMT-81803, A010/ DI-MGMT- 81804A) The contractor shall affix IUID labels to applicable parts.

The contractor shall manage CAP/ GFP SE using the same processes as items on the SSL, with the exception that the location where SE is stored will vary depending on the requirements specified in Peculiar Support Equipment.

Maintenance Activities The contractor shall process Life Limited Parts for inspection, testing, re-certification (or disposal) of the Block 40/45 Enterprise, IPEC, and SIC items, at required intervals, in the C-ICP and Point of Supply (POS) Inventory.

The contractor shall record inspections, testing, re-certification, repair, parts replacement/substitution, or condemnations in their IMS. Periodic Maintenance Inspection (PMI) items include:

· Shelf-life items

· Parts requiring functional test and certification

· Parts requiring hardware in storage maintenance (battery replacement)

· Parts requiring capacitor maintenance (capacitor reform) The contractor shall include the following, for items having shelf-life limitations and/or marking requirements:

· Maximum allowable age or shelf-life limitations as specified by the supplier or manufacturer

· Any temperature, humidity, or other unique storage conditions The contractor shall perform activities including:

· Capacitor Maintenance (capacitor reform)

· Hardware in Storage Maintenance (battery replacement)

· Hardware Sanitization

· Rework

· Inspections

· Parts Replacement/ Substitution

· Unclassified/ Classified Repair

· Firmware Reloads and Updates The contractor shall perform Capacitor Maintenance (capacitor reform) on hardware items IAW Drawing No. 775-50159U.

The contractor shall perform Hardware in Storage Maintenance (battery replacement) on hardware items IAW Drawing No. 775-50154AC.

The contractor shall perform procedures 775-51002B when transferring sanitized components which brings them to unclassified state, per DoD sanitization procedures, to depots and/or commercial vendors for repair, and for submission to Government ORMS for disposition as residual to contract requirements.

The procedures reference the applicable sections to be performed of MPTO 00-33B-5008 for the removal of the classification label from the hardware once the sanitization procedure has been performed.

Supplier Management Approved Purchasing System The contractor shall:

· Perform supplier management and procurement actions

· Execute their approved purchasing system to perform supplier selection

· Issue purchase contracts

· Procure parts

· Execute repair activities that prevent introduction of counterfeit and altered assets into the 40/45 supply and equipment inventory The contractor shall manage selected suppliers for quality, schedule, and cost; as well as flow down the terms and conditions of the prime contract to the SOS and SOR selected to receive subcontracts.

The contractor shall fund buys for stock replenishment and back orders IAW direction from PCO.

The contractor shall provide the government new supplier sources for any item on SSL within 5 working days of the change. The government has 5 working days to respond and accept or deny the new source.

Packaging, Handling, Storage, and Transportation (PHS&T) The contractor shall maintain facilities that meet environmental controls required to ensure the equipment is stored within the proper design limits.

The contractor shall follow modes and procedures for handling, storing, and transporting Block 40/45 Enterprise, IPEC, and SIC components outlined in Section 5 of each System Security Plan (SSP). Criteria which require that components be given special consideration include:

· Shock mitigation

· A clean environment

· Humidity control

· Temperature control

· Special security The contractor shall use best commercial practices, IAW American Society for Testing and Materials (ASTM) Standards D3951-18, Standard Practice for Commercial Packaging, when no special requirements are identified.

The contractor shall verify the requisition number DoD Activity Address Code (DoDAAC) against authorized DoDAACs (to be provided by the Government as GFE prior to preparing components for shipment.

The contractor shall deliver the components and corresponding DD Form 1348-1 shipment document to the requesting DoDAAC.

The contractor shall deliver components utilizing the Defense Transportation System. Components must include the following information:

· DoDAAC of location components are being shipped

· Dimensions and weight of the container

· National Stock Number (NSN)

· Transportation Account Code (TAC)

· Any additional data required by the Defense Transportation System (DTS) The contractor shall notify the PMO of requisitions received against unauthorized DoDAACs / users. The PMO will instruct the Contractor to either support the new user or reject or disregard the requisition.

The contractor shall employ personnel in the C-ICP warehouse that are trained in handling the various types of property and in inventory management control, including:

· Variable shelf-life requirements

· Static sensitive devices

· Hazardous materials

· Warehouse equipment operation The contractor shall store inventory using best commercial practices.

Delivery The contractor shall provide processing and status of customer requisitions.

The contractor shall respond to customer requisitions within established delivery time parameters determined by requisition priority, IAW C-ICP Performance Metrics.

The contractor shall verify backorders for acquisition, processed, and given precedence according to the need date and priority reflected on the requisition.

The contractor shall provide wholesale level supply support to respond to requisitions received for operational aircraft and ground systems.

The contractor shall deliver any item authorized on the SSL, to the requesting DoDAAC, upon receipt of a requisition.

The contractor shall prepare a DD Form 1348 for all requisitions.

The contractor shall deliver components against CONUS requisitions with approved DoDAACs.

The contractor shall deliver components against OCONUS requisitions with approved DoDAACs.

Lost and Received Items Lost Items The contractor shall notify the Government PCO of replenishment part purchases when an inventory item is confirmed lost via Financial Liability Investigation (FLI), IAW DAFMAN 17-203, paragraph 2.7.2. The contractor shall submit the FLI to the PCO for disposition prior to replenishing established stock levels due to a lost asset.

Received Items The contractor shall perform the required receiving inspection process for all components procured or returned from repair/parts replacement.

The contractor shall follow the processes outlined below:

Check parts received into the C-ICP for proper conformity, serviceability, documentation.

Complete a damage assessment for those items that do not meet the aforementioned Retain parts not meeting requirements until discrepancies are corrected, or disposition is determined by QA personnel Disposition parts on hold to return to service/ supplier, or disposal Product Support Integration (PSI) Annual Services PSI Annual Services PSI Annual Services is designed to capture the annually reoccurring functions necessary to achieve and improve the performance metrics of the mission support work. Figure 1. Graphical Depiction of Product Support Management Services contains a broadly summarized graphical representation of the content of this annual work. The graphic depicts key ongoing management and engineering responsibilities as well as what is expected of the Contractor. It also details the processes the Contractor must follow to make changes to the Block 40/45 Enterprise, IPEC and SIC approved baselines. The Contractor's performance will be measured by a Quality of Service metric, which will be an evaluation of the Contractor's ability to manage and optimize these areas to achieve the performance metrics in the mission support areas and support the Government's role of PSI.

Figure 1. Graphical Depiction of Product Support Management Services Enterprise RAM-C Initiative The contractor shall perform sustaining engineering activities to update Government Furnished Information (GFI) Logistics Management Information, to build a data collection and performance management process for tracking and reporting enterprise-wide Key Performance Indicators (KPls) / RAM-C data elements to include Total Lifecycle Sustainment Cost, Reliability, Availability, and Maintainability measures. Refer to DoD-RAM-C Manual "Department of Defense Reliability, Availability, Maintainability, and Cost Rationale Report Manual", and DoDI 5000.02 "Operation of the Defense Acquisition System" for guidance on planning and implementing RAM-C.

The contractor shall identify improvements to RAM-C performance and disposition improvements as well as issues negatively impacting or anticipated to negatively impact the Block 40/45 Enterprise, IPEC, and SIC systems reliability, availability, maintainability, and cost performance. Refer to MIL-HBK-502A and/or equivalent (such as SAE/TA STD 0017 or ASD/AIA S3000L) Supportability Analysis (SA) or Product Support Analysis (PSA) for analytical functions using sustaining engineering to identify and develop product support improvements that reflect in RAM-C targets and optimize support cost and performance.

The contractor shall maintain a SA/ PSA using MIL-HBK-502A as a guide for both critical NMC and operation/ support cost drivers, as well as longer term technical refresh candidates. The process will:

· Track all RAM-C driver events

· Manage the Program Incident Report (PIR) / DR process

· Perform lead root cause analysis of in-service problems

· Recommend process and/or design changes The contractor shall utilize the Corrective, Perfective, Adaptive, and Enhancement methodology for Enterprise PSA / RAM-C Management process based on the following definitions:

· Corrective: Performance issues resulting in NMC time

· Perfective: System performance issues (Grips) reported by operators but did not drive NMC time

· Adaptive: Update hardware due to obsolescence, DMS, and COTS hardware and software supportability issues The contractor shall conduct PSA / RAM-C trending, modeling, and reporting for Technical Baseline and Operations Support by evaluating:

· Aircraft availability

· Sortie rate

· Operational effectiveness analysis

· Training readiness

· Cost saving initiatives

· Implementation concepts (for stakeholder recommendations) The contractor shall document their PSA /RAM-C analysis in an annual impact analysis report which must include: (A011/ DI-SESS-81759A)

· Optimized, best value Technical Baseline Integrated Release (IR) Fielding short and long range technical refresh execution plan

· Recommendations for optimizing system performance (RAM, functional effectiveness, etc.) and reducing costs

· Recommendations on cost effective tradeoffs

· Alternatives and modifications to existing or proposed requirements to resolve identified issues.

· Contractor assessment of program-wide risks

· Evaluation of emerging requirements with respect to existing and future capability enhancements and their impact on Weapon System sustainment

· Input identifying changes to facilities requirements, hardware, simulators, emulators and diagnostic equipment

· Input utilizing actual data from previous IR projects to estimate the anticipated areas of change in the Block 40/45 Enterprise, IPEC, and SIC software present evaluations, associated trade-offs (including budgetary cost, schedule and performance)

· Recommendations to the Government at SWGs, IR Systems Engineering Management Team (SEMT) Working Groups (WG) and IR SEMTs

· The Contractor shall use GEIA-STD-0007B, Logistics Product Data, GEIA-HB-0007, Logistics Product Data Handbook and TA-HB-0007-1A, Handbook and Guide for Logistics Product Data Reports as reference documents.

· The contractor shall classify the level of PSA / RAM-C impact and develop prioritized list of change recommendations to mitigate the issues. (A012/ DI-MISC-80048) (NOTE: Measurement, identification of issues and recommendations of mitigations will not be limited to hardware.)

· The contractor shall develop a prioritized list of change recommendations to mitigate issues identified above. (A012/ DI-MISC-80048) The contractor shall consider the following in PSA / RAM-C Assessments:

· Elements that interface with the Block 40/45 Enterprise, IPEC and SIC systems

· System reliability, maintainability and task analyses

· Individual system component impacts

· Cost, schedule and technical performance

· Impacts on test configurations of the Block 40/45 Enterprise, IPEC and SIC systems

· Program Incident Report (PIR)

· Deficiency Reports (DRs)

· Software Change Requests (SCR) The contractor shall develop a modeling and simulation environment using the Logistics Product Data (LPD) to provide analytical analysis support for (See Paragraph 15.2.5):

· Integrated Release

· Reliability

· Maintainability

· Built -In-Test (BIT) (to the extent available by commercial products)

· Supportability cost savings

· DMSMS

· Operational effectiveness improvement efforts The contractor shall maintain a mathematical model to track the reliability of the Block 40/45 Enterprise, IPEC and SIC systems in real time/ future points in time when an approved parts replacement/ substitution has been implemented.

The contractor shall utilize this model identified in 3.15 to determine if the physical Block 40/45 Enterprise, IPEC and SIC Systems are meeting its reliability requirement.

The contractor shall provide recommendations, via a contracts letter to the PCO, to improve the system, if they do not meet reliability requirements from this model from 3.15.

The contractor shall provide analyses and/or recommendations that include issues corrective, perfective, adaptive, and enhancement in nature.

The contractor shall manage an Enterprise PSA / RAM-C system where the Government can access and view all data.

The contractor shall track mitigation resolutions for critical NMC drivers (i.e. corrective and adaptive issues), performance degraders (i.e., perfective issues) and longer-term candidates (i.e., enhancements).

The contractor shall institute Enterprise PSA and RAM-C Management sustaining engineering activities described in Section 15.2.

The contractor shall provide CM of the functional and physical Block 40/45 Enterprise, IPEC and SIC systems configuration baselines, as defined by the documents listed in Program Specific Documents.

Data Management and Collection System The contractor shall maintain a Data Management and Collection System compatible with GEIA-STD-00007 or equivalent (such as Power log J). The system wall includes maintaining and updating:

· Sl000D: International Specification for Technical Publications

· Technical Order Source Data

· Provisioning Data

· Support Equipment Recommendations Data The contractor shall update their Data Management and Collection System [referred to as Logistics Product Data)] for RAM-C improvements as well as DMSMS, and other configuration changes. LPD will be source data for sustaining engineering recommendations and inputs to Government's internal Operational Suitability Safety & Effectiveness (OSS&E) Checklists. The GEIA-STD-00007 data system is capable of tracking numerous baselines that are supported in the PBL contract. (A013/ DI-SESS-81758A; A014/ DI-MGMT-81949) Functional Configuration/ Mission Performance The Government will provide the Contractor with quarterly Dynamic Object-Oriented Requirements Management System (DOORS) database archive updates of any Government-initiated changes to the Government-approved Block 40/45 Enterprise, IPEC and SIC systems functional configuration baselines.

The Contactor shall update and maintain DOORS with the authorized E-3G Block 40/45 Enterprise, IPEC and SIC systems specifications baselines. (A029/ DI-IPSC-81431A) Physical Baseline Configuration and Engineering Data/ Data Access The Government will provide the Contractor with quarterly drawings and STEP model updates of any Government-initiated changes to the Government-approved Block 40/45 Enterprise, IPEC and SIC systems physical configuration baselines.

The Contractor shall deliver technical data packages (e.g. data, drawings and documentation) associated with baseline changes under this…