Attachment 12 - Performance-Based Work Statement Rev 3_25 Aug 2021_CURRENT 2 (1).pdf
PDF 832 KB Posted
- Solicitation number
- FA852820D0009
About this file
This Performance Work Statement (PWS) details Contractor Logistics Support (CLS) and sustainment requirements for the U-2 AN/ALQ-221 Electronic Warfare Suite (EWS). The primary objective is to provide and support an electronic warfare system that delivers situational awareness and self-protection capabilities for the U-2 weapon system, enabling it to operate effectively in contested environments. Critical performance requirements include maintaining a 95% system availability, providing accurate inventory management with 98% accuracy, and ensuring high-quality technical deliverables with strict limits on rejections and late submissions.
The contract covers comprehensive logistics support activities including spare parts procurement, specialized repair activities, bonded stock management, engineering support, technical publications maintenance, and software updates. The work will be performed at CONUS and OCONUS locations, with the basic Indefinite Delivery/Indefinite Quantity (IDIQ) contract consisting of five one-year ordering periods and an optional six-month extension. Key technical requirements encompass engineering tasks such as design changes, failure analysis, system performance monitoring, threat analysis, and periodic software reprogramming to maintain the U-2 EWS's operational effectiveness.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| REQUEST FOR INFORMATION Electronic Warfare System (EWS) Contractor Logistics Support (CLS).docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
CUI
PR: FD2399-20-00103 PWS REVISION: 3 1
Performance Work Statement for
U-2 Electronic Warfare Suite (EWS)
Support and Sustainment
Purchase Request: FD2399-20-00103
Original: 21 Oct 2019 Revision #1: 10 Dec 2020 Revision #2: 2 June 2021
Revision #3: 25 August 2021
DISTRIBUTION STATEMENT E: - Distribution authorized to DoD Components only (Critical Technology and Direct Military Support) (1 March 2018). Other requests for this document shall
Controlled by: AFLCMC Controlled by: Information Protection CUI Category: CUI Basic Distribution/Dissemination Controls: Distribution E POC: Kacie McInvale, DSN 468-8333
PR: FD2399-20-00103 PWS REVISION: 3 2
be referred to AFLCMC/HBGA, 235 Byron St, Suite 19A, Robins AFB, GA 31098-1670.
Questions concerning technical content should be referred to AFLCMC/HBGEA.
1.0 Description of Services:
1.1 Objective(s):
This Performance Work Statement (PWS) describes the requirements for Contractor Logistics Support (CLS) and Sustainment of the U-2 AN/ALQ-221 Electronic Warfare Suite (EWS).
The objective of all requirements included in this PWS is to provide and support the AN/ALQ- 221 EWS system that provides situational awareness and self-protect capability to the U-2 Weapon system such that it can survive in a contested operational environment. CLS requirements in this PWS include sustainment, design, development, integration, test, and procurement. Activities that are over and above normal day to day support and sustainment will be individually solicited, proposed and negotiated as outlined in specific task descriptions.
Individual task orders for these efforts will be processed accordingly.
1.2 Benefit to United States Air Force (USAF):
This acquisition will benefit the United States Air Force (USAF) by providing global Intelligence, Surveillance, and Reconnaissance (ISR) capabilities to combatant commanders and other customers with an uninterrupted stream of multi-intelligence. This capability will provide real-time information to be shared amongst military services allowing for reduced decision-loop time, and the ability to identify/locate time sensitive targets.
1.3 Background:
The mission of AFLCMC/HBGA is to defend the United States (U.S.) and protect its interests through air and space power. To help achieve that mission, the AN/ALQ-221 EWS provides high altitude, interception and analysis of radio frequency signals, to support the Warfighter’s vision of Global Vigilance, Reach, and Power.
2.0 Services Summary:
2.1 Performance Objectives:
The Critical Performance Objectives are shown in Table 1.
Table 1. Critical Performance Objectives
Performance Objective
PWS
Para
Performance Threshold
Maintain System Availability and provide Monthly Report
4.3 The Contractor shall maintain the availability of U-2 EWS systems at a minimum 95% at all times over the entire period of performance.
PR: FD2399-20-00103 PWS REVISION: 3 3
Provide accurate inventory of GFP
3.3.1 Inventories shall result in 98% accuracy; 100% accuracy for classified or sensitive property. Discrepancies shall be resolved within 45 calendar days upon completion of inventory.
Provide Quality CDRL Deliverables
4.2.1 There shall be no more than one (1) rejection of any
deliverable. There shall be no more than two (2) total rejections of deliverables per quarter.
Provide On-time CDRL Deliverables
4.2.2 CDRL deliverables shall be delivered according to the
instructions on each respective DD1423. There shall be no more than two (2) late submissions of deliverables per quarter.
Provide Surge resolution and mitigation planning
4.3.2.1 A serviceable asset shall be shipped within ten (10)
calendar days after surge is identified and an asset is in-plant for repair.
Provide MICAP resolution and mitigation planning
4.3.2.2 A serviceable asset shall be shipped within two (2)
calendar days after Mission Impaired Capability Awaiting Parts (MICAP) identified, if serviceable asset is in-plant.
Provide On-time Material Deliverables
4.3.4 There shall be no more than two (2) scheduled line items per Purchase Directive (PD)/Work Order (WO)/Bonded Stock Request (BSR) delivered after the Estimated Delivery Date (EDD).
Provide Quality Depot Level Maintenance Services (DLMS) team IMDS reporting
4.4.1.4.k All Maintenance Actions will be completely and accurately documented in the AF Integrated Maintenance Documentation System (IMDS) in a timely manner ensuring documentation errors are maintained at 3% or less per month.
Provide timely responses to requests for information (RFI) from PM
4.6.3 At a minimum, 95% of the time, Contractor shall
acknowledge receipt within one business day; evaluate time needed to collect data within 2 business days and submit response by mutually agreed upon suspense date.
Contractor Manpower Reporting
5.7.2 Within 30 calendar days of contract/order award, the
Contractor shall establish a record for the contract/order in eCMRA including Order Data, Contact Data and Location Data. The Contractor shall provide a count of
PR: FD2399-20-00103 PWS REVISION: 3 4
contractor/subcontractor personnel performing services for each fiscal year and report all contractor/subcontractor labor hours required for performance of services for each fiscal year. All data shall be reported no later than October 31 of the following fiscal year.
Adherence to Contractor Quality Management System
(QMS)
5.9 100% compliance with the QMS is required.
3.0 Government Property:
Government property includes Government Furnished Property (GFP), Government Furnished Material (GFM), Government Furnished Equipment (GFE), special tooling, special test equipment, etc. GFP includes assets furnished for repair, maintenance, overhaul or modification.
3.1 Contractor Responsibility:
The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) part 45 and as specified in the contract/order.
3.2 Government Property to be Provided:
Government Furnished Material (GFM) and Government Furnished Equipment (GFE) may be provided to support this effort. In such cases, the GFM and GFE clauses of the contract will identify specifics and disposition instructions. Additionally, if Government facilities are provided, they will be specified in the Delivery/Task Orders (D/TOs). A designated Government Manager will provide the Contractor access to all Government information, facilities, material, equipment, services, etc., as required to accomplish individual D/TOs. Reference Contract Attachment 1, Property Management.
3.3 Financial Improvement Audit Readiness (FIAR):
The Contractor shall be compliant with the FIAR strategy, IAW the Chief Financial Officers (CFO) Act of 1990, which mandates accountability of GFP maintained in Contractor facilities.
FIAR directs the transfer of excess and obsolete Special Tooling/Special Tooling equipment (ST/STE) to 309 Aerospace Maintenance and Regeneration Group (AMARG). ST/STE items are jigs, dies, fixtures, molds, patterns, taps, gauges, other equipment and manufacturing aids, and the single or multipurpose integrated test units engineered, designed, fabricated, or modified to accomplish special purpose testing in performing a contract.
3.3.1 Inventory of GFP:
The Contractor shall conduct a 100% inventory of GFP within 45 calendar days of contract award and within 45 calendar days prior to contract completion. Inventories shall include Depot
PR: FD2399-20-00103 PWS REVISION: 3 5
Level Maintenance Services (DLMS) maintained GFP accounts. Inventories shall result in 98% accuracy; 100% accuracy for classified or sensitive property. Discrepancies include, but are not limited to, missing assets, missing documentation, missing disposition instructions, etc.
Discrepancies shall be resolved within 45 calendar days upon completion of inventory.
The Contractor shall conduct a 100% inventory of GFP annually or as required by the Government IAW AFI 63-103 and DoDI 5000.64. The annual inventory shall include DLMS maintained GFP accounts. Annual inventories shall result in 98% accuracy; 100% accuracy for classified or sensitive property. Discrepancies include but are not limited to missing assets, missing documentation and missing disposition instructions. Discrepancies shall be resolved within 45 calendar days upon completion of inventory.
3.3.2 Management of GFP:
The Contractor shall report to the Government Property Administrator and Material Manager materials and equipment obtained from sources other than AFLMC/HBG within 10 calendar days after receipt.
Contractor shall acknowledge receipt of all Government property by signing and dating the shipping document (DD Form 1348-1), and assigning a control number/serial number (if applicable).
Government property will be returned on DD Form 1149 (receiving/shipping document).
Government property acquired by the Contractor to be incorporated into an end item shall be reported under the top assembly number by way of DD250 via WAWF at time of delivery. If deliverable end item is to be retained at Contractor’s plant, a Government control number shall be assigned to the top assembly number on the DD250 via WAWF and forwarded to AFLMC/HBG property administrator.
3.4 Reporting of Government Property:
The Contractor shall create and maintain records of all Government property accountable to the contract, including Government-Furnished Property (GFP) and Contractor - Acquired Property (CAP) in accordance with FAR 52.245-1(f)(1)(iii), Government Property. (A012, Equipment Inventory Records)
The Contractor shall record GFP in the Item Unique Identification (IUID) Registry in accordance with Defense Federal Acquisition Regulation Supplement (DFARS) 211.274-4, Policy for reporting of Government-Furnished property; DFARS 252.211-7007, Reporting of Government- Furnished Property; and Department of Defense Instruction (DoDI) 4161.02, Accountability and Management of Government Contract Property.
3.5 Loss of Government Property:
3.5.1 Definition of Loss of Government Property:
PR: FD2399-20-00103 PWS REVISION: 3 6
“Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.
3.5.2 Reporting Loss of Government Property:
The Contractor shall report loss of Government property using Defense Contract Management Agency (DCMA) / Access To eTools.
3.6 Return or Retention of Government Property:
All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.
4.0 Technical Requirements:
4.1 Place of Performance:
These services shall be performed at CONUS and OCONUS locations.
4.1.1 Contract Ordering Periods and Periods of Performance:
The basic IDIQ contract consists of five (5) each one year ordering periods and includes the short option to extend clause for a one time extension of this contract for an additional six (6) month ordering period.
The Period of Performance (PoP) for orders released against the basic contract is designated at the funded order and CLIN level.
4.2 Contract Data Requirements Lists (CDRL):
See 6.5 Appendix D, Table of CDRLs
PR: FD2399-20-00103 PWS REVISION: 3 7
4.2.1 Quality of CDRL Deliverable:
There shall be no more than one (1) rejection of any deliverable. There shall be no more than two (2) total rejections of deliverables per quarter. The Government will reject a deliverable if one (1) or more technical errors or three (3) or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is defined as a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within five (5) calendar days of notification of Government rejection.
4.2.2 Receipt of CDRL Deliverable(s):
CDRL deliverables shall be delivered according to the instructions on each respective DD1423.
There shall be no more than two (2) late submissions of deliverables per quarter. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.
4.3 Integrated Logistics Support:
The Contractor shall maintain the availability of U-2 EWS systems at a minimum 95% at all times over the entire period of performance. (A011, CDM Production Report – U-2 EWS Integrated Logistics Support Register).
Contractor shall submit a Request for Variance (A030, Request for Variance).
4.3.1 Spare Parts:
The specific spare parts will be procured in accordance with procedures set forth in contract Attachment 2, Procedures for Initial and Follow-On Spares and Support Equipment. The categories of items to be procured are as follows:
a. Airborne Sustainment Spares
b. Initial Spares
c. Support Equipment
d. Kits
As applicable, the Contractor shall enter weekly Spare Status into Contractor Automated Logistics Management Support System (CALMSS) and any price changes via contractor status updates into CALMSS as set forth in contract Attachment 2, Procedures for Initial and Follow- On Spares and Support Equipment.
Contractor shall meet requirements as indicated in PWS Attachment 2, Procedures for Initial and Follow-On Spares and Support Equipment.
PR: FD2399-20-00103 PWS REVISION: 3 8
4.3.2 Specialized Repair Activity (SRA):
The Contractor shall have the material and services to inspect, repair, modify and test an estimated minimum level of units, as identified in the D/TO of the fielded equipment that are being returned for repair and/or modification. The Contractor shall examine and bring to the Government’s attention methods to economically reduce SRA Turn-Around Time (TAT) without adversely impacting SRA or System Mean Time Between Failure (MTBF). The Contractor shall input weekly SRA status and appropriate cost data into CALMSS. Reference contract Attachment 3, Specialized Repair Activity Procedures, for administration of this item. Refer to contract Attachment 1, Property Management.
4.3.2.1 Surge Items:
A serviceable asset shall be shipped within ten (10) calendar days after surge is identified and an asset is in-plant for repair.
4.3.2.2 MICAP Items:
A serviceable asset shall be shipped within two (2) calendar days after MICAP identified, if serviceable asset is in-plant.
4.3.3 Bonded Stock:
The specific Bonded Stock parts will be procured in accordance with procedures set forth in contract Attachment 2, Procedures for Initial and Follow-on Spares and Support Equipment.
Refer to contract Attachment 1, Property Management. The categories of items to be procured are as follows:
a. Bonded Stock
b. Initial Spares
c. Support Equipment
As applicable, the Contractor shall enter weekly Bonded Stock Inventory into the Contractor Automated Logistics Management Support System (CALMSS).
Contractor shall meet requirements as indicated in PWS Attachment 2, Procedures for Initial and Follow-on Spares and Support Equipment (A014, Consumable Parts Bondroom/Inv &Parts Usage Report)
4.3.4 Material Delivery:
There shall be no more than two (2) scheduled line items per Purchase Directive (PD)/Work Order (WO)/Bonded Stock Request (BSR) delivered after the EDD. Any late item shall be delivered by a revised EDD acceptable to the Government. If a revised EDD is not accepted by the Government, then the item will be considered late if it is not delivered by its original or
PR: FD2399-20-00103 PWS REVISION: 3 9
previously accepted revised EDD. The Contractor shall make their best effort in providing a realistic and accurate EDD at all times.
4.3.5 Item Unique Identification:
4.3.5.1 Marking Requirement:
Item Unique Identification is required for all items to be delivered to the Department of Defense (DoD) that meet the criteria established by the FAR.
4.3.5.2 Reporting in IUID Registry:
4.3.5.2.1 Transmission of Government property must be recorded in the IUID Registry. The Contractor is required to develop an IUID Marking Plan. The Government is required to record the transfer of GFP to the Contractor. The Contractor is required to record the receipt of GFP from the Government. The Contractor is required to record the return of GFP to the Government. (A019, IUID Marking Plan)
4.3.5.2.2 The Government or Contractor/Subcontractor personnel responsible for causing a “life cycle event” (i.e., abandoned, consumed, destroyed by accident, destroyed by combat, donated, exchanged – repair, exchanged – sold, exchanged – warranty, expended – experimental/target, expended – normal use, leased, loaned, lost, reintroduced, retired, scrapped, sold – foreign government, sold – historic, sold – nongovernment, sold – other federal, sold – state/local, and stolen) will update the item record in the IUID Registry. (A020, IUID Marking Activity, Validation and Verification Report)
4.3.6 Packaging:
4.3.6.1 The Contractor shall package and mark material for movement, shipment, receipt and storage in a manner that ensures the protection and preservation of the material for shipment to and storage at the destination. The Contractor shall package and mark material IAW the contract (basic or order, as applicable) Air Force Materiel Command (AFMC) Form 158, Packaging Requirements; MIL-STD-129P, Department of Defense Standard Practice/Military Marking for Shipment and Storage; MIL-STD-130N, Department of Defense Standard Practice/Identification Marking of U.S. Military Property; and MIL-STD-2073-1E, Standard Practice for Military Packaging.
Bonded Stock and Ship-in-Place items going into Bonded Stock shall be packaged and stored at BAE Systems’ facility using BAE Systems’ or Best Commercial Practice. Ship-in-Place items shipped from the BAE Systems facility are to be shipped via MIL-STD-2073-1E IAW Attachment 15. Ship-in-Place items that are to be issued to the floor immediately do not require packaging.
PR: FD2399-20-00103 PWS REVISION: 3 10
Part numbered LRU and Ground Support Equipment (GSE) items may be shipped in their Government approved packaging IAW with MIL-STD2073-1E, paragraph 5.4 Minimal Packaging Requirements, Code F in Appendix J, Table J-IXb.
4.3.6.2; The Contractor shall ensure that classified material is packaged, marked and delivered in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual
(NISPOM).
4.3.6.3 The Contractor shall ensure that Electrostatic Discharge (ESD) programs comply with electrostatic discharge protections for all ESD sensitive components in accordance with MIL- STD-1686C, Department of Defense Standard Practice / Electrostatic Discharge Control Program for Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices); MIL-HDBK- 263B, Military Handbook / Electrostatic Discharge Control Handbook for Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices); and MIL-HDBK-773A, Electrostatic Discharge Protective Packaging, dated 30 Jun 05.
4.3.7 Counterfeit Electronic Part Detection and Avoidance System:
4.3.7.1 The Contractor shall establish and maintain a counterfeit electronic part detection and avoidance system to mitigate the risk of counterfeit electronic parts being installed in end items or otherwise entering the USAF/DoD inventory.
4.3.8 Diminishing Manufacturing Sources and Material Shortages (DMSMS):
4.3.8.1 The Contractor shall provide DMSMS support as required for the U-2 EWS Program.
This support shall include, but not be limited to, proactive management of the Component Obsolescence Database, continuous assessment of component availability for customer systems and support for DMSMS component issues, alerting the customer of DMSMS issues specifically affecting their systems and providing recommendations to the customer for resolving DMSMS issues based on cost, risk and other critical management factors. Investigate DMSMS issues identified in the semi-annual DMSMS Report or as identified in Spare and Repair activities utilizing In-Plant Engineering expertise as required in paragraph 4.5.1.
4.3.8.2 The Contractor shall track, through vendor polls, etc., the qualified manufacturers/distributors of parts contained in the current and past configuration. The Contractor shall maintain a proactive obsolescence prediction capability for the systems vendor status.
4.3.8.3 Maintain a DMSMS management program to identify, develop and implement resolution plans for DMSMS problems. The program will address the following key elements:
a. Active DMSMS predictions based on close vendor liaison and early notification for U-2 EWS and associated support equipment.
b. Active DMSMS predictions and solutions for the U-2 EWS and associated support equipment.
PR: FD2399-20-00103 PWS REVISION: 3 11
c. A set of executable solutions options with recommendations for implementation.
d. Provide DMSMS updates in support of Requirement Working Group Meeting when requested.
e. Co-chair DMSMS Working Group that meets on a semi-annual basis.
f. ROM or BE’s will be provided to support DMSMS solution recommendations at the request of the PCO.
g. Notify the Government in a timely fashion of any and all common and unique item
DMSMS issues if and when they are discovered by the DMSMS team.
h. At the request of the Government PCO, the Contractor will propose hardware redesigns as a result of investigation of DMSMS identified in the semi-annual DMS Report or as identified in Spare and Repair activities.
i. Resolution of DMSMS issues as per direction of program office.
Contractor shall submit (A015, Bill of Materials (BOM) for Logistics and Supply Chain Risk Management Report; A017, GIDEP).
4.3.9 Production and Material Procurement:
Additional scope may be negotiated on independent task orders as required. CDRLs listed in 6.5 Appendix D, Table of CDRLs are available for use. Specific CDRLs required shall be identified at the task order level in the task description of each independent task order; (A012, Equipment Inventory Records).
4.4 Depot Level Maintenance Services (DLMS):
4.4.1 Routine, In-Scope DLMS Support:
DLMS are required to meet DLMS Requirements, as identified in contract Attachment 4, Work Description Document (WDD), and contract Attachment 5, U-2 Airborne Requirements Operations Tempo (OPS TEMPO) [Ops Tempo document updated annually by ACC]. DLMS travel will be IAW contract Attachment 6, U-2 Air Depot Level Maintenance Services (DLMS) Travel and Labor Policy/Allowances. Status of Forces Agreement requirements will be jointly coordinated between USG & Contractor IAW Attachment 7, Status of Forces Agreement (SOFA) Requirements for U.S. – Republic of Korea.
4.4.1.2 The Government will act as a sponsor for the Contractor at overseas locations in order to assist securing Visas, drivers’ licenses and other work related documents which are necessary in order to perform their duties pursuant to the contract.
4.4.1.3 The DLMS personnel shall perform tasks on a best effort basis to support the U-2 Airborne Requirements Operations Tempo within the allocated number of shifts (a “shift” is defined as eight consecutive hours of support). (A009, Status Report – Weekly Status Report)
4.4.1.4 The following tasks will be performed on a routine basis by assigned DLMS personnel:
PR: FD2399-20-00103 PWS REVISION: 3 12
a. Local maintenance leadership will determine priorities based on operational requirements.
b. Provide technical support to Air Force maintainers to assist as required for On-Equipment troubleshooting, repair, and support of the fielded AN/ALQ-221 Mission Equipment system, and defined ALQ-221 associated Ground Support Equipment (GSE) to include preflight and post flight support.
c. Provide post-mission data analysis to Pilots for the Electronic Warfare (EW) Suite as required.
d. Support On-Equipment and Off-Equipment PACERWARE actions. All PACERWARE and SERENE BYTE activity will be IAW AFI 10-703 Beale AFB Supplement.
e. Maintain the following Support/Test equipment: Advanced Flight Line Test Set II (AFLTS II), Radio Frequency Line Test Set (RFLTS), Ground Support Unit (GSU) II, Special Print And Display Equipment (SPADE) III, Advanced Defensive System Test Station (ADSTS), Low Band System Test Station (LBSTS), Direction Finding System Test Station (DFSTS), Power Distribution Unit (PDU), Memory Loader Verifier (MLV), Antenna Monitor Box, Low Band (LB) and High Band (HB) Preflight Coupler set.
f. Acquiring existing or new Support Equipment will be accomplished per AFMAN 23-122, AFH 23-123 and applicable supplements. Equipment is managed via Equipment Accounts, Standard of Allowances, and authorizations in Air Force Equipment Management System (AFEMS). Allowance and equipment account change requests can be submitted online through the AFEMS (TACR) or manually on AF Form 601. Detailed instructions for submitting change requests are contained in AF Form 601 Preparation, AFH 23-123, Vol 2, Pt 1, Ch 5.
g. Off-Equipment Time Compliance Technical Orders (TCTO Modification Kits are installed within the prescribed time).
h. The DLMS personnel shall work with and support the Squadron Intelligence Section (during normal shift hours) and PACERWARE changes for “On” and “Off” equipment reprogramming, IAWAFI 10-703 Beale AFB Supplement.
i. The DLMS personnel shall debrief the pilot on EW system operation to assist in isolating system malfunctions and processing equipment activations. The DLMS personnel shall analyze mission recordings to assist in isolating system malfunctions and processing equipment activations.
j. Technical support to operational locations continues at levels commensurate with the operational activity when real world conditions require it. This includes support of military activity during real world activities and hostilities as directed by the local commander. In accordance with, maintenance DLMS personnel are identified as mission essential/emergency essential. Contractors deployed to both high threat and imminent danger areas will be issued Personal Protective Equipment (PPE) and Chemical Warfare Defense Ensemble (CWDE) as determined by the responsible area Commander.
k. The DLMS personnel shall support Maximum Economical Field Level Repair (MEFLR) by troubleshooting all Line Replacement Units (LRUs) down to the lowest level Shop Replacement Unit (SRU)/component. Up to 96 hours may be required for troubleshooting and repair of an LRU before turning Due in From Maintenance (DIFM) item into supply.
All Maintenance Actions will be completely and accurately documented in the AF Integrated Maintenance Documentation System (IMDS) in a timely manner ensuring documentation errors are maintained at 3% or less per month.
PR: FD2399-20-00103 PWS REVISION: 3 13
l. For those Back-Shop Custodial duties that are required to be transitioned from the AF, maintenance shall occur once all assets are accounted for and are in operational status or replacement parts are on order and can be tracked through the Air Force Supply system.
a. Custodial duties are defined as follows:
i. DLMS EW Shop Tech Order Monitor and Custodian
ii. DLMS EW Shop Security Monitor and Custodian
iii. DLMS EW Shop Training Monitor and Custodian
iv. DLMS EW Shop TCTO Monitor and Custodian
v. DLMS EW Shop Supply Monitor and Custodian
vi. DLMS EW Shop Precision Measurement Equipment Lab (PMEL) Monitor and Custodian
vii. DLMS EW Shop Equipment Account Monitor and Custodian
viii. DLMS EW Shop Special Purpose Recoverable Authorized to Maintenance
(SPRAM) Monitor and Custodian
ix. DLMS EW Shop Composite Tool Kit (CTK) Monitor
4.4.1.5 Reserved
4.4.2 Non-Routine, In-Scope DLMS Support:
Additional scope may be negotiated on independent task orders as required. CDRLs listed in 6.5 Appendix D, Table of CDRLs are available for use. Specific CDRLs required shall be identified at the task order level in the task description of each independent task order.
As directed by local maintenance supervision or the Government Program Office, the Contractor shall provide technical support to AF maintainers for On-Equipment troubleshooting, repair, and support of the fielded AN/ALQ-221 Mission Equipment System, and defined ALQ-221 associated Ground Support Equipment (GSE) to include preflight and post flight support surging to 24 hours per day/7 days per week for a maximum of 30 calendar days in support with a minimum of 90 calendar days before additional support can be made available. Support required beyond 30 days will require notification from ACC/A4CQ and direction from AFLCMC/HBGA (PCO and PM).
4.4.3 Levels and Types of Support:
The following levels and types of support shall be performed to accomplish Paragraph 4.4.1:
a. All On-Equipment Maintenance is the responsibility of AF maintainers with technical support from DLMS personnel if troubleshooting assistance is required.
b. Phase Support as required.
a. Appropriate Lockheed Martin Aeronautical (LMA) support is available
b. Aircraft is properly de-paneled and access to the EW System specific cables and connectors are provided.
c. Contractor shall submit status reports, monthly. (A008, Status Report - Technical
Progress Report; A009, Status Report – Weekly Status Report)
PR: FD2399-20-00103 PWS REVISION: 3 14
4.4.4 Data Integrity Teams (DIT):
4.4.4.1 The purposes of the DIT include: (1) Ensuring the unit has complete and accurate data in the Management Information System (MIS) and aircraft forms (AFTO Form 781s), (2) identifying and quantifying problems within the unit preventing complete and accurate documentation, and (3) identifying and correcting the root causes for poor data integrity.
4.4.4.2 The contractor shall ensure that they maintain accurate maintenance records in the MIS and participate in the DIT process as required. As required, compare all Non-Real-Time Services (NRTS) actions and turnarounds in IMDS-CDB/G081 with those in the ILS-S to ensure they match. G081 users will request these reports from LRS. Work with supply to resolve conflicts.
4.5 Engineering:
4.5.1 In-Plant Engineering:
4.5.1.1 The objectives (IAW contract Attachments 1, Property Management, Attachment 3, Specialized Repair Activity Procedures and Attachment 8, Routine In-Plant Support) are as follows:
a. Provide technical assistance including Design Change Notices, Test Plan and Procedure Updates and failure analysis for depot repair and support for the AN/ALQ-221 System, Electronic Warfare Suite Data Recorder (EWSDR), and Support/Test Equipment defined in General Support Paragraph 4.3.2. (A044, Test Plan; A045, Test Procedures; A046, Acceptance Test Report; A051, Technical Report – DCN)
b. Ensure that Material Deficiency Reports (MDRs), design and quality assurance deficiencies and failures of systems and components are resolved to required performance parameters. (A013, Deficiency Report)
c. Ensure that Engineering Change Plans (ECPs), flight testing, TCTOs, modifications, and engineering studies improve operational mission performance.
d. Ensure system performance and reliability data are collected and maintained to indicate system availability, reliability, and maintainability.
e. Contractor shall participate in the Government Industry Data Exchange Program
(GIDEP). (A017, GIDEP)
f. Enhance field and depot technical support.
g. Provide technical assistance to Contract Field Service Representatives.
h. Ensure systems, support equipment, and airframe interface requirements are properly established and implemented.
i. Perform threat analysis and report within five (5) calendar days of an AFLCMC/HBG request or as directed. (A024, Technical Report –Study/Services)
j. Provide support to associate contractors for periodic updating/re-programming of software using results of threat analysis tasks.
k. Perform operational analysis of mission recorder data to determine if observed anomalies are equipment or environmentally related. Analysis will be performed within 24 hours of identification of incident and access to data. Ensure that results of these analysis tasks provide the appropriate solution when required.
PR: FD2399-20-00103 PWS REVISION: 3 15
l. Investigate embedded software issues that are identified in fielded Prime and Support Equipment. Support software updates via the TCTO Process.
m. Coordinate identified system problems with associate Contractors, AFLCMC/HBG and 36th EWS. Maintain a master list of the coordinated system problems as the basis for Block Cycle software and system operational deficiency updates. Provide this list at the semi-annual EWS Working Group meetings and upon specific request from the Customer community.
n. Provide Engineering Support to the 36th EWS for periodic Threat Warning Data Base Updates at the Contractor’s facility. Troubleshoot in-plant GFE issues and support the repair required.
o. Provide in-plant infrastructure support to include lab coordination and lab security.
p. With the guidance of the Government Program Office, preliminary analysis of the necessary EWS changes associated with Operational Change Requests (OCRs), and Modification Proposals (AF Form 1067).
q. Full support and fielding of three (3) Urgent Operational Change Request (OCR) software modifications, integrations, test and verifications at the Contractor facility and external facilities as noted on the task order(s). (A025, Specifications Requirement Verification Matrix; A035, Software Test Description; A036, Software Test Plan; A037, Software Test Report; A038, Interface Design Document; A039, Interface Control Document; A040, Software Version Document; A041, System/Subsystem Specification;
A043, Computer Software Product End Items; A046, Acceptance Test Report; A052, Training Materials, A056, Technical Report – Static Code Analysis; A057, Technical Report- System Test Report/Final Test Report )
r. Agile Software: The Contractor shall release a PACERWARE software update for fielded software on a one every three months release cycle. PACERWARE software updates are defined as software only updates in order for the system to keep pace with threats in the operational environment or to correct any identified deficiencies. The Contractor shall use the principles of agile software development for PACERWARE software updates. The Contractor’s ability to maintain the required release cycle is dependent on Government test facility availability and configuration management processes. Update candidates can be sourced from a variety of sources including OCRs, Program Executive Reviews (PERs), Mission Data Optimization (MDO) test events, and Electronic Warfare Working Groups (EWWG) action items. All updates are dynamic.
Update candidates and acceptance criteria require Government PMO collaboration and concurrence before entering work in the release cycle. Collaboration with the Government throughout the release cycle is required. (A025, Specification Requirement Verification Matrix; A032, Software Development Plan; A033, Software Design Description;A034, Software Requirements Specification (SRS); A035, Software Test Description; A036, Software Test Plan; A037, Software Test Report; A038, Interface Design Document; A039, Interface Control Document; A040, Software Version Document; A041, System/Subsystem Specification; A043, Computer Software Product End Items; A046, Acceptance Test Report; A052, Training Material; A055, Software Management Plan, A056, Technical Report – Static Code Analysis; A057, Technical Report- System Test Report/Final Test Report)
s. Provide prioritized list semi-annually of all changes proposed to be worked during software release effort, as well as quarterly updates on status of effort. Any required
PR: FD2399-20-00103 PWS REVISION: 3 16
updates received, including MDO findings during yearly effort will be prioritized for the next update.
t. The Contractor shall provide configuration management support in accordance, including, but not limited to, collection, review, tracking and archiving of Configuration Control Documents, development of automated databases to track hierarchical components, maintenance of product data, support to Configuration Control Boards, performance of Functional Configuration Audits and Physical Configuration Audits, evaluation of Configuration Management Single Process Initiative (CMSPI), and concept papers. (A021, Supplier’s Configuration Management Plan; A023, Configuration Management Report)
u. Investigation of Program Exception Reports (PERs) identified in the EWS Data Base.
Root causes are to be identified and recommendations for implementing solutions and/or improvements will be coordinated with the Electronic Warfare Multi-functional Team (EWMFT) to determine a path forward based upon schedule and the complexity of the hardware and software updates.
v. Support semi-annual Mission Data Optimization (MDO) events. The purpose of the event is reprogramming and evaluating performance of EWS System. This will allow onsite incremental improvements to programming and repeat testing. Prior to the MDO event, the Contractor shall preprogram the EWS System with candidate techniques developed by Contractor engineers along with Government input. During testing, the Contractor, along with 36 EWS/EWM personnel shall modify and combine preprogrammed techniques and program new techniques to result in the most effective combination (this is the optimization referenced in MDO). If there will not be 2 (or more) events scheduled within the PoP, JAM plans may be provided in lieu of MDO support. JAM plans will be provided to the 36 EWS/EWM. Contractor shall provide a test report documenting findings and recommended improvements. This information will be consolidated by 36 EWS/EWM in a final test report. (A030, Request for Variance; A057, Technical Report – System Test Report/Final Test Report)
4.5.1.2 The Contractor is not required to submit and receive action item approval for the sustaining activities called out herein for In-Plant Engineering. Action Item efforts are deemed to have an approximate duration of 40 – 80 hrs. All other In-Plant engineering tasking not covered by the sustaining activities called out herein requires submittal and approval of a Request/Authorization for In-Scope Tasking (RAIT) regardless of dollar value or contract mod IAW (A008, Status Report – Technical Progress Report; A029; Technical Report – Study/Services, RAITS.
4.5.1.3 The Contractor shall support Working Group, Design Reviews, and Technical Interchange Meetings (TIMs) as required. The Contractor shall submit conference agenda reports, conference minutes, and material presented at meetings. (A005, Conference Agenda;
A006, Conference Minutes; A007, Presentation Material)
4.5.2 Technical Publications: (00-5-3; 00-5-1; 00-5-18)
4.5.2.1 Provide Technical Publications, Design & Drafting and Configuration Management in support of documentation, hardware and software configuration items. (A047, Product
PR: FD2399-20-00103 PWS REVISION: 3 17
Drawings/Models and Associated Lists; A048, Air Force Technical Manual Contract Requirements; A049, Commercial Off-the-Shelf (COTS) Manuals and Associated Supplemental Data)
4.5.2.2 The Contractor shall establish and maintain a technical publications program to include quality assurance, validation, and verification of the ALQ-221 Electronic Warfare technical publications IAW Attachment 9, Configuration/Technical Requirements. (A048, Air Force Technical Manual Contract Requirements).
4.5.2.3 The Contractor shall have the material and tools necessary for maintenance of, revisions to and updating of technical manuals, data, and other documentation pertaining to the fielded systems. The Contractor shall submit the final versions within forty-five (45) calendar days of change initiation.
4.5.2.4 The Contractor shall maintain the technical order/technical manual (TO/TM) database, as well as any other databases required to support technical manuals delivered IAW (A048, Air Force Technical Manual Contract Requirements).
4.5.2.5 Time Compliance Technical Order (TCTO) Support. (MIL-PRF 38804C; 00-5-15)
4.5.2.6 All Routine Action TCTOs shall be submitted to the BAE Sharepoint and will be downloaded by AFLCMC/HBG personnel, after e-mail notification to wralc.lr.tcto@us.af.mil, and routed to AFLCMC/LT for review and approval. Classified documentation will be sent via SIPRNET. After approval to release is given, the contractor shall put the documentation of the Military Service Data Distribution System (MSDDS) and notify the DLMS personnel.
4.5.2.7 The Contractor shall perform technical data validation and verification of TCTOs IAW (A048, Air Force Technical Manual Contract Requirements). The Contractor shall conduct technical manual planning, and perform in-process reviews for technical data as required.
4.5.3 Variable Engineering:
Additional scope may be negotiated on independent task orders as required. CDRLs listed in 6.5 Appendix D, Table of CDRLs are available for use. Specific CDRLs required shall be identified at the task order level in the task description of each independent task order.
4.6 Program Management:
The Contractor shall provide an appropriate level of Program Management required to support all PWS and associated attachment requirements. The program shall be managed to ensure that costs do not exceed the negotiated contract value and continuity of support is maintained. The Contractor shall notify the Government in a timely manner of significant cost and/or support issues. Timely is considered to be enough time such that the Government has the ability to respond with implementation of mitigation actions before the identified issues occur. The Contractor shall maintain a list of all documentation associated with the program. The Contractor shall submit funds reports, progress reports, and maintain a System Matrix Report, PR: FD2399-20-00103 PWS REVISION: 3 18 formerly the LRU Matrix Report. (A001, Data Accession List; A002, Contract Fund Status Report; A003, Contractor’s Progress, Status and Management Report; A016, Integrated Program Management Report; A018, Technical Report – Study/Services).
4.6.1 The Contractor shall support requests for Rough Orders of Magnitude (ROMs) according to the following schedule.
a. Urgent = As specifically directed by the Government Program Office
b. High Priority = submitted within 15 calendar days
c. Medium Priority = submitted within 30 calendar days
d. Low Priority = submitted within 45 calendar days
4.6.2 The Contractor shall support Basis of Estimates (BOEs) and Requests for Proposal (RFPs).
Request priority will be directed by PM/PCO with Contractor coordination.
4.6.3 The Contractor shall provide a timely response for all Requests for Information (RFI). At a minimum, 95% of the time, Contractor shall acknowledge receipt within one business day;
evaluate time needed to collect data within 2 business days and submit response by mutually agreed upon suspense date.
4.6.4 The Contractor shall support quarterly Program Management Reviews (PMRs), semi-annual Working Group, and TIMs as required. The Contractor shall submit conference agenda reports, conference minutes, and material presented at meetings. (A005, Conference Agenda;
A006, Conference Minutes; A007, Presentation Material)
4.6.5 Variable Program Management:
Additional scope may be negotiated on independent task orders as required. CDRLs listed in 6.5 Appendix D, Table of CDRLs are available for use. Specific CDRLs required shall be identified at the task order level in the task description of each independent task order.
4.7 Travel:
The Contractor shall identify all travel-related costs associated with the fulfillment of meeting this Performance-Based Work Statement. See contract Attachment 6 for DLMS Travel Policy.
Refer to contract Attachment 4, Work Description Document for additional DLMS personnel travel considerations. All travel, both CONUS and OCONUS, must be submitted via a Travel Request Form (contract Attachment 6) within 72 hours and approved by AFLCMC/HBG Program Manager (PM) and PCO for reporting/tracking procedures. A Letter of Authorization (LOA) must be submitted and approved via the Synchronized Pre-deployment and Operational Tracker (SPOT) system at https://spot.dmdc.mil prior to all OCONUS travel.
5.0 General Information:
5.1 Continuation of Mission-Essential Services During a Crisis:
PR: FD2399-20-00103 PWS REVISION: 3 19
5.1.1 Designation of Services as Mission-Essential:
In accordance with DFARS 237.7602(a), The Continuation of Essential Contractor Services, DFARS 252.237-7023(a)(2), and AFI 10-403, Deployment Planning and Execution, paragraph 1.9.1.33.2, the Functional Director has identified all or a portion of the Contractor service performed under the contract as Mission Essential (ME) / Emergency Essential (EE) critical.
Details for ME/EE service can be found in contract Attachment 4, Work Description Document
(WDD).
5.1.2 Mission Essential Functions:
The Government has identified all or a portion of the Contractor service performed under the contract as essential Contractor services in support of mission essential functions.
5.1.2.1 The Contractor-provided services that have been determined to be essential contractor services in support of mission essential functions are listed in contract Attachment 4, Work Description Document (WDD). In accordance with DFARS 237.7602(b), DFARS 252.237- 7023(c) (1), and DFARS 252.237-7024(b), Notice of Continuation of Essential Contractor Services, the Contractor shall provide a written plan for continuing the performance of essential contractor services identified in the paragraph above. (A004, Technical Report – Study/Services)
a. The Contractor shall identify in the plan the provisions made for the acquisition of essential personnel and resources, if necessary, for continuity of operations for up to 30 calendar days or until normal operations can be resumed.
b. The plan must, at a minimum, address:
i. Challenges associated with maintaining essential Contractor services during an extended event, such as a pandemic that occurs in repeated waves;
ii. The time lapse associated with the initiation of acquisition of essentials personnel and resources and their actual availability on site;
iii. The components, processes, and requirements for the identification, training, and preparedness of personnel who are capable of relocating to alternate facilities or performing work from home;
iv. Any established alert and notification procedures for mobilizing identified “essential contractor service” personnel; and
v. The approach for communicating expectations to contractor employees regarding their roles and responsibilities during a crisis.
5.1.2.2 The Contractor shall maintain and update its plan as necessary and adhere to its requirements throughout the contract term. The Contractor shall not materially alter the plan without the Government PCO’s consent.
5.1.2.3 As directed by the Government PCO, the Contractor shall participate in training events, exercises, and drills associated with Government efforts to test the effectiveness of continuity of operations procedures and practices.
5.1.2.4 In accordance with DFARS 252.237-7023(d) (2), in the event the Contractor anticipates not being able to perform any of the essential contractor services identified on contract
PR: FD2399-20-00103 PWS REVISION: 3 20
Attachment 4, Work Description Document (WDD) during a crisis situation, the Contractor shall notify the Government PCO or other designated representative as expeditiously as possible and use its best efforts to cooperate with the Government in the Government’s efforts to maintain the continuity of operations. The Government reserves the right in such crisis situations to use Federal employees of other agencies or contract support from other contractors or to enter into new contracts for essential contractor services.
5.1.2.5 In accordance with DoD Instruction (DoDI) 1100.22, Policy and Procedures for Determining Workforce Mix, Enclosure 2, paragraph 5.b, and AFI 10-403, paragraph 1.9.1.33.1, the [Functional] Commander will develop a contingency plan if there is a reasonable doubt that the Contractor will continue to provide mission-essential services during a crisis.
The Contractor shall segregate and separately identify all costs incurred in continuing performance of essential services in a crisis situation. The Contractor shall notify the Government PCO of an increase or decrease in costs within ninety (90) calendar days after continued performance has been directed by the Government PCO, or within any additional period that the PCO approves in writing, but not later than the date of final payment under the contract.
5.1.2.6 The Contractor shall include the substance of mission essential information in subcontracts for the…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .