PWS.docx

AIR FORCE LIFE CYCLE MANAGEMENT CENTER ROBINS AIR FORCE BASE, GEORGIA 31098-1670 PERFORMANCE-BASED WORK STATEMENT (PWS) FOR SPECIAL OPERATIONS FORCES (SOF) FIXED WING (FW) INTEGRITY PROGRAMS AND STRUCTURAL SUPPORT AND ENGINEERING SERVICES (SSES)

FD2060-20-30024

26 November 2019

Prepared by: AFLCMC/WIUAG 235 Byron Street, Suite 19A Robins AFB, GA 31098-1670

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their contractors (Administrative or Operational Use; 17-08-18). Other requests for this document shall be referred to AFLCMC/WIUAG, Robins AFB, GA 31098-1670.

TABLE OF CONTENTS

PR: FD2060-20-30024 PWS REVISION: 0

DISTRIBUTION STATEMENT C. Approved for public release.”

1.0 Description of Services

1.1 Objective: This Performance-based Work Statement (PWS) describes requirements to provide engineering services and structural support for all SOF/PR C-130’s. Requirements include engineering services, structural support, analytical engineering studies, prototyping, and structural testing as well as avionics support, studies and analyses.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the USAF by addressing, mitigating and/or alleviating structural and engineering concerns that are typical aging aircraft issues and further exacerbated by the configuration and missions and high operations tempo (OPSTEMPO) characterized by the increased number of missions for the SOF/PR C- 130 fleet. Further, this program will focus on identifying, mitigating and/or alleviating avionics, configuration, flight safety and other engineering issues. Finally, this contract will provide the SOF/PR System Program Office (SPO) with a flexible tool to address critical engineering and technical issues as they arise.

1.3 Background: This effort is a follow on/continuation of the current sustaining engineering effort currently performed by Mercer Engineering Research Center (MERC), contract number FA8509-18-F-0003. This effort has existed in various forms since 2005 and has been a sole source to MERC since that time.

2.0 Services Summary (SS):

Reference Performance Threshold

4.3.2 4.4.5 Initial “Quick Look” summary due within 5 business days of the conclusion of site survey. For actions not requiring a site survey, “Quick Look” is due 5 calendar days from date of notification.

Quality of Contract Data Requirements List (DD Form 1423-1) (CDRL) deliverable 4.2.1

No more than one rejection of any deliverable per quarter. The Government will reject a deliverable if two or more technical errors or five 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 or grammatical error. Rejections shall be corrected and resubmitted in accordance with the DD Form 1423 (CDRL).

3.0 Government Furnished Property (GFP):

3.1 Government Property: All GFP or Contractor Furnished Material (CFM), equipment, facilities and services shall be managed in accordance with Federal Acquisition Regulation (FAR) Part 45, Defense Federal Acquisition Regulation Supplement (DFARS) Part 245, and the applicable contract clauses. The Government will retain ownership of all GFP provided for this effort. Unless otherwise specified, the contractor shall return all GFP for this effort at the end of the contracted period of performance unless otherwise specified by the Contracting Officer. The contractor shall request disposition and shipping instructions from the Program Manager through a letter to the Contracting Officer or designated representative.

3.2 Government Property to be provided: Government property will be provided in accordance with the GFP attachment, attached to the Contract.

3.3 Reporting of Government Property: The Contractor shall create and maintain records of all property accountable to the contract, including GFP and Contractor-Acquired Property (CAP) in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

3.4 Loss of Government Property:

3.4.1 Definition of Loss of Government Property: “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. Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or authorized destructive testing. Unless otherwise specified, loss of Government property does not include authorized usage of low priority consumable material, such as common hardware.

3.4.2 Reporting Loss of Government Property: The Contractor shall report loss of Government property using Defense Contract Management Agency (DCMA) / Access to eTools. http://www.dcma.mil/aboutetools/

3.5 Return/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 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.

3.6 Government System(s): The Government will provide Contractor personnel access to system(s) necessary to perform tasks under the contract. Specific systems include Reliability & Maintainability Information System (REMIS), Joint Engineering Data Management Information Control System (JEDMICS) and all other Government systems required to update Automated Inspection, Repair, Corrosion & Aircraft Tracking (AIRCAT) and Aging Fleet Integrity & Reliability Management Multi-Platform (AFIRM-M).

4.0 Technical Requirements:

4.1 Period of Performance (PoP):

4.1.1 Contract/Order Period of Performance: Total PoP is 22 Jul 2020 – 21 July 2025

· Order Period 1: 22 July 2020 – 21 July 2021

· Order Period 2: 22 July 2021 – 21 July 2022

· Order Period 3: 22 July 2022 – 21 July 2023

· Order Period 4: 22 July 2023 – 21 July 2024

· Order Period 5: 22 July 2024 – 21 July 2025

4.1.2 Place of Performance: The place of performance for this effort shall be primarily at the Contractor’s facility. However, the Contractor may be required to travel, as determined by the Government, to several installations, both in the Continental United States (CONUS) and Outside the Continental United States (OCONUS). Locations may include but are not limited to:

· Hurlburt Field, Florida

· Eglin Air Force Base (AFB), Florida

· Cannon AFB, New Mexico

· Kirtland AFB, New Mexico

· Robins AFB, Georgia

· Harrisburg ANGB, Pennsylvania,

· Davis-Monthan AFB, Arizona

· Elmendorf AFB, Alaska

· Moody AFB, Georgia

· Moffett Field, California

· Patrick AFB, Florida

4.2 Contract Data Requirements List (CDRL)

4.6.7, 4.6.7.1, 4.6.8, 4.6.8.5, 4.6.8.6

4.2.1 Quality of CDRL Deliverable: There shall be no more than one rejection of any deliverable. There shall be no more than two (2) total rejection(s) of deliverables per quarter. The Government will reject a deliverable if two or more technical errors or five 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 or grammatical error. The rejected deliverable shall be corrected and resubmitted within five business days of notification of Government rejection. In accordance with the associated DD Form 1423 instructions/requirements.

4.2.2 Receipt of CDRL Deliverable: CDRL deliverables shall be submitted via Wide Area WorkFlow (WAWF) to the government Program Manager listed in the CDRL. There shall be no more than one late submission(s) of any deliverable(s) per quarter. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and shall negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.3 Engineering Services Details

4.3.1 MECSIP: Provides data pertaining to structural support, analytical engineering studies, modeling, and structural testing to support All SOF/PR C-130’s. Additionally, the program will collect and analyze aircraft reliability data to further maximize weapon system safety, reliability, and availability. Existing aircraft structural models and usage databases will be updated and improved to reflect the current mission profiles, hardware configurations, and usage. This program will also include short notice/emergency structural reviews also referred to as “Quick Look” studies to respond to issues which will immediately have a negative impact on mission readiness. The Contractor shall provide for the study and analysis of other as yet unknown engineering issues found during routine maintenance and operations of SOF/PR C-130 aircraft. (A008, DI-MISC- 80508B)

4.3.2 AVIP: Provides data pertaining to avionics support, analytical engineering studies, modeling and testing to support All SOF/PR C-130’s. Additionally, the program will collect and analyze data to further maximize weapon system safety, reliability, and availability. Existing aircraft avionics models and usage databases will be updated and improved to reflect the current mission profiles, hardware/software configurations, and usage. This program will also include short notice/emergency reviews also referred to as “Quick Look” studies to respond to issues which will immediately have a negative impact on mission readiness. The Contractor shall provide for the study and analysis of other as yet unknown engineering issues found during routine maintenance and operations of SOF/PR aircraft and systems. (A007, DI-MISC- 80508B)

4.3.3 Configuration Management (CM)/ Air Worthiness (AW) / System Safety (SS): In accordance with (IAW) applicable government standards and Air Force Instructions (AFI), the Contractor shall analyze and provide recommendations for the Airworthiness, Configuration Management and System Safety Processes for all SOF/PR C-130 platforms. The Contractor shall provide for the study and analysis of other as yet unknown engineering problems found during routine maintenance and operations of the aforementioned aircraft.

4.3.4 Computer Software Product: The Contractor shall deliver any software product on media of sufficient size to contain all products from the Period of Performance. All deliverables shall be at the level of detail sufficient to provide to a developer with comparable levels of expertise for further development. Delivery will be IAW DD Form 1423-1. (A009, DI-IPSC-81488)

4.3.5 Aging Fleet Integrity and Reliability Management system (AFIRM-M): The Contractor shall modify and maintain SOF/PR C-130 AFIRM-M database to include current Time Compliance Technical Order (TCTO) and modification implementation status; Reliability- Centered Maintenance (RCM), Mechanical Structural Integrity Program (MECSIP), and other available data (especially as it relates to SOF/PR-peculiar aircraft configurations and including but not limited to IR shields, all guns, counter-measures dispensers, and SOF/PR-specific avionics/electronics/electronic warfare hardware and configurations and cybersecurity issues.) Modifications to AFIRM- M shall include automation of data pulls from the various sources to the maximum extent practical. Modification to AFIRM-M shall also include development of AFIRM-M tools for TCTO configuration status updates, reporting for SOF/PR-specific concerns such as gunfire rates and firing orbit dwell time (if practical), and other tools to support SOF engineering monthly status reporting. The Contractor shall work with the 581st SMXS/MXDPCC SEA-SIL (581st SEA-SIL) to assist in the AFLCMC/WIU-owned, contractor-sustained AFIRM-M application for induction into Organic sustainment, integration with Organic AFIRM, and elimination of redundant system capabilities and accreditation packages. This transition to Organic sustainment is required per Federal Data Center Consolidation Initiative (FDDCI). (A00B, DI-IPSC-81488)

4.4 General Contractor Responsibilities

4.4.1 Meeting Agenda: The Contractor shall submit an agenda for any formal meeting. NOTE: The Government Program Manager will clearly identify whether a meeting is considered formal. Formal meetings shall be reflected in the Integrated Master Schedule. Delivery will be IAW DD Form 1423-1. (A001, DI-ADMN-81249B)

4.4.1.1 Presentation Material: The Contractor shall deliver presentation material to the Government prior to any formal meeting. NOTE: The Government Program Manager will clearly identify whether a meeting is considered formal. Formal meetings shall be reflected in the Integrated Master Schedule. Delivery will be IAW DD Form 1423-1. (A002, DI-ADMN-81373)

4.4.1.2 Conference Minutes: The Contractor shall document any formal meeting with meeting minutes. NOTE: The Government Program Manager will clearly identify whether a meeting is considered formal. Formal meetings shall be reflected in the Integrated Master Schedule. Delivery will be IAW DD Form 1423-1. (A003, DI-ADMN- 81250B)

4.4.2 Integrated Program Management Report (IPMR): The Contractor shall submit an IPMR, to include the Integrated Master Schedule (IMS), at the beginning of the period of performance and update monthly. Delivery will be IAW DD Form 1423-1. (A004, DI-MGMT-81861A)

4.4.3 Data Accession List (DAL): The Contractor shall submit the DAL to the government program manager on a form of media that is secure and large enough to contain complete product; a removable hard drive with sufficient space is acceptable. This DAL shall contain both the indexed list and an organized electronic record copy of the task order, all task order CDRL deliveries, all reports (including monthly status reports), all presentations (at Technical Interchange Meetings (TIMs) and all conceptual drawings, technical data, raw data (see Raw Data Requirements paragraph), pictures, structural models and associated data, and all other documents generated under this task order. The data contained on the DAL deliverable shall be organized by any logical fashion that that the Contractor deems necessary to allow its use by the Government as a reliable, organized, permanent record of work performed. The Contractor shall provide a signature document for the Government to acknowledge receipt, the format of the receipt is at the discretion of the Contractor. The DAL shall not include Contractor personnel security information. Delivery shall be IAW DD Form 1423-1. (A00A DI-IPSC-81437A, A009 DI-IPSC-81488)

4.4.4 Monthly Status Report (MSR): The Contractor shall deliver a final MSR by the 15th calendar day of the month following the completion of the previous month. Delivery will be IAW the DD Form 1423-1. (A006, DI-MGMT-80368A)

4.4.5 Technical Study/Services: The Contractor shall perform independent technical studies as directed by the System Program Office (SPO) to support all SOF/PR C-130 aircraft as outlined in this PWS. The intent of the studies is to provide the Government with an assessment of the specified areas of interest and an indication of the magnitude of the problem in terms of margin of safety, cycles to failure, cycles to initial detectable crack length, estimated hours to failure, estimated hours to initial detectable crack length, and/or other useful technical parameters (as appropriate to the structure or system being analyzed). This assessment shall also provide the Government with recommendations to resolve the problem areas, such as inspection intervals, potential repair methods, or, if requested, potential design changes. The Contractor shall summarize all studies in a technical report(s) as directed by the Government. These technical reports shall discuss the Contractor's analysis and any technical solution(s) being recommended. Included in each such report shall be a description of each of the assumed and/or known loads, the assumed and/or known initial flaws, and the technical references or reports (if any) that brought the Contractor to these conclusions. The Contractor shall provide the rationale and methodology used in performing the analysis as well as presenting and justifying any proposed technical solution(s). In the case of the Contractor providing structural/avionics engineering support or engineering services which the Government categorizes as Critical, the Contractor shall provide a concise, early "Quick Look" report. Initial “Quick Look” summary is due IAW DD Form 1423-1 (A005, DI-NDTI-80809B and A007, DI-MISC- 80508B)

· The problem

· Any predisposing factors

· A broad-level estimate of the severity and prevalence of the problem

· Any potential solutions the Contractor is considering at that time

· Any other early information the Contractor deems relevant to the issue

· Brief description of germane facts from a site survey, if conducted

4.4.6 Developmental Design Drawings and Associated Lists: Per Department of Defense (DoD) policy, the Contractor shall provide “paperless” electronic or digital data deliveries unless otherwise directed by the Government. Specific CDRL items contain email and physical delivery addresses for digital and/or electronic deliveries. Unless otherwise directed by the Government, all documents shall be submitted in a Microsoft Office®- compatible format. Exception: MS project files shall be exported to MS Word, MS Excel, Adobe PDF, or other common file format, at Government request, and the Government will coordinate with the Contractor for delivery of Finite Element Analysis (FEA) and other engineering models/data. At the Government’s discretion, drawings/models may be delivered in AutoCAD format or other format to be determined prior to the delivery of draft drawings. (A009, DI-SESS-81002F)

4.4.7 Engineering Data: Product Data shall reflect the approved, tested and accepted configuration of the defined delivery item. All engineering product definition data created as a result of this contract shall be considered a part of the Test Data Package. This data includes, but is not limited to, CAD data, models, model based definition data sets and Gerber data. (A009 DI-SESS-81002F)

4.4.8 Site Surveys: The Contractor shall supplement its efforts under this task with site surveys and/or tests and surveys of actual aircraft related equipment and components as required with prior approval of the government PM. The Contractor shall submit a report of the survey in accordance with the DD Form 1423-1 (A005, DI-NDTI-80809B)

4.4.9 Technical Orders: The Contractor shall reference United States Air Force (USAF) Technical Orders as additional technical data to supplement drawings in determining the details of the area to be analyzed. The Contractor shall notify the Government of any technical errors or discrepancies discovered in those Technical Orders. A brief summary of these errors shall be included in the Contractor’s report; however, the Contractor shall not modify, add to, subtract from, or publish any new or existing Technical Order, or any portion of a Technical Order in performance of this task order. (A005, DI-NDTI-80809B)

4.4.10 Raw Data Requirements: Time and/or spatial-domain tabular-type data (temperature distributions, load/stress vs. time, accelerometer vs. time, etc.) derived from instrumentation efforts shall be delivered to the Government in table format and in a Microsoft Word-compatible file type). Delivering raw numerical data as scanned images, Portable Document Format (.PDF) files, or in graph/chart format without the actual data points does not meet this requirement. Should the volume of data make it impractical to deliver by email, the Contractor shall consult with the PM for alternate digital formats and/or delivery options. The Contractor shall submit the report IAW DD Form 1423-1 (A005, DI-NDTI-80809B)

4.5 Specific Contractor Responsibilities

4.5.1 As directed by the Government, the Contractor shall identify and analyze those areas known to be fatigue critical, corrosion prone, highly stressed, and/or poorly designed from a structural standpoint, as well as other areas needing study. Each of these analyses shall be submitted to the Government IAW DD Form 1423-1 (A005, DI-NDTI-80809B).

4.5.2 Structural Model: If required, the Contractor shall develop, maintain and deliver structural models of SOF/PR specific C-130 airframes.

4.5.2.1 The Contractor shall maintain and refine as needed, the Global Finite Element (FE) models for all SOF/PR C-130 aircraft.

4.5.2.2 The Contractor shall initiate development of additional Global FE models of SOF/PR C-130 airframes with one (1) major component annually.

4.5.2.3 FE models shall be used in support of engineering tasks listed in this document.

4.5.2.4 FE models shall be updated, when necessary, as a result of the studies performed.

4.5.2.5 FE models shall incorporate best practices for mesh sizing and attachments and shall conform to methods and formats used in previously developed Global C-130 models. Configuration control shall be maintained as a result of changes made to the non SOF/PR C- 130 aircraft. (A009, DI-SESS-81002F)

4.5.3Aircraft Structural Analysis: The Contractor shall evaluate current and proposed designs using analytical methods as directed by the Government Program Manager (PM). Types of analyses shall include but not limited to: Finite element analysis with static, Thermal, impact, or dynamic (shock, transient, and vibration) loading. Results of analyses shall include stress, strain, displacements, temperature, frequencies and modes of vibration. The Government anticipates seven (7) analyses and tests per year based on projections of historical needs. All analysis of designs shall be documented in a report with supporting data. (A005, DI-NDTI-80809B, A008, DI-MISC-80508B).

4.5.3.1 Repair Design, Analysis, and Testing: The Contractor shall perform failure/damage analysis of aircraft structural members to determine the underlying causes. The Contractor shall provide design, analysis, testing, modeling, and tooling support as necessary for repair or manufacture of structural components as directed by the Government based on the results of the structural analysis; the Contractor shall deliver the report IAW DD Form 1423-1 (A005, DI-NDTI-80809B)

4.5.3.2 : Flight/Ground Testing: Contractor shall support design efforts with flight testing where required. Flight testing support will include test plan generation, AF Form 1067 Modification Proposal, where required, Configuration Control Board (CCB) support (where required), instrumentation selection/installation, and test monitoring. All tests shall be documented with a test report containing results, conclusions and recommendations, and supporting data. The Contractor shall be capable of recording and processing strain, acceleration, thermal, analog, and/or data bus inputs for ground/flight testing. The Contractor shall provide independent technical review of data/reports/designs. Analysis shall include detailed analytical review of engineering methods and computations, review of design loads/stresses, review of maintenance/logistics/usage data and reports, and other engineering documents as required. (A005, DI-NDTI-80809B)

4.5.3.3 Modeling: The Contractor shall develop improved design solutions and proofs of concept. The improved design solutions shall support the following:

· Eliminate cracking causes,

· Improve damage tolerance

· Improve maintenance operations.

The contractor shall provide scanning and modeling of complex components to account for documentation gaps in loft data, contour data, and/or antiquated drawing details. The Contractor shall provide these services in support of efforts and to support modeling of components. Models shall be made available in Initial Graphics Exchange Specification (IGES) format. (A00A, DI-IPSC-81437A, A005, DI-NDTI-80809B)

4.5.3.4 Mishap Support: The Contractor shall support mishap investigations with analysis, data review/collection, and/or repair design. Assignment of mishap report tasks shall be at the direction of the Government PM and shall be concluded with a report detailing all analyses, data, designs, and recommendations/conclusions. (A005, DI-NDTI-80809B)

4.5.3.5 Risk Assessment and System Safety Hazard Analysis Support: The Contractor shall provide support for Risk Assessments and System Safety Hazard Analysis. Support must comply with all applicable Risk Assessment guidelines and, at the Government PM’s direction, shall be entered into the AFIRM-M and System Safety Hazard Analysis Support tracking tool.

4.5.3.6 Testing: The Contractor shall provide static and fatigue testing of samples and large components, up to 250,000 pounds capacity with test plan and test reports. The Contractor must be capable of providing fixture design to accomplish the tests. (A005, DI-NDTI-80809B)

4.5.4 Fleet Management: The Contractor shall provide development and maintenance support for the SOF/PR C-130 fleet management and aircraft tracking systems.

4.5.4.1 Survey of SOF/PR C-130 modifications: The Contractor shall update, improve, and maintain the tail-by-tail survey of SOF modifications reported through AFIRM-M. The Contractor shall survey structural and non-structural modifications to provide an accurate fleet compliance report and determine the spatial envelope information necessary for developing a geometric configuration tool. (A005, DI-NDTI-80809B)

4.5.5 SOF/PR C-130 MECSIP and AVIP Master Plan: The Contractor shall update Mechanical Equipment and Subsystems Integrity Program (MECSIP) and Avionics Integrity Program (AVIP) Master Plans that will cover the SOF related C-130 subsystems. This master plan will identify all subsystems and equipment covered by SOF MECSIP and AVIP, establish analysis prioritization, develop a SOF unique subsystem Reliability Centered Maintenance (RCM) analysis schedule, and detail how SOF RCM analyses are to be integrated with the Tactical Airlift C-130 RCM analyses. At the conclusion of development of the SOF portion of the C-130 MECSIP and AVIP Master Plans, the Contractor shall review all previous C-130 RCM analyses for SOF unique issues and recommend options to implement the approved actions. Delivery shall be IAW DD Form 1423-1 (A008, DI-NDTI-80508B)

4.5.6 MECSIP RCM / Maintenance Steering Group (MSG)-3 efforts The Contractor shall perform RCM/MSG-3 aircraft system analysis for SOF specific systems by utilizing current technical manuals, failure data, and input from field and depot maintainers to complete a Failure Mode, Effects, and Criticality Analysis (FMECA) as well as to complete a full RCM analysis for the necessary components. The Contractor shall perform full analysis of all current Preventive Maintenance actions as well as determine the high drivers of cost or aircraft downtime as identified in the FMECA. The Contractor shall investigate reliability at the system level and perform full analysis at the component level in order to identify specific problem areas and better provide detailed solutions. The contactor shall refine data analysis techniques for ranking systems/components for y further RCM analysis and recommend improvements in the maintenance work card inspections and Work Unit Code (WUC) accuracy based on RCM analysis results. The Contractor shall accomplish Air Force Technical Order (AFTO) Form 252 Technical Order Publication Change Request, for recommended Technical Order (T.O.) changes and provide these to the SOF C-130 SPO. The contractor shall complete and submit validation checklists IAW EN-SB-15-002 for all new or revised 1C-130A-36 or 1C-130J- 36 procedures. The Contractor shall provide a RCM analysis report for each system. The report shall include the recommendation for retention or deletion of every current PM in T.O. 1C-130(A/H/M) J-6, T.O. 1C-130A-6, -6 Work Cards, and Programmed Depot Maintenance (PDM) in addition to the cost and man power projected savings. The Contractor shall report on the status of each ongoing RCM analyses in the MSR.

4.5.6.1 The Contractor’s initial MECSIP RCM focus shall be to refresh the initial SOF/PR C- 130 baseline RCM analysis for example:

· 467XX – Aerial Refueling System

· 46WXX- Universal Air Refueling Receptacle Slipway Installation (UARRSI) System

4.5.6.2 During RCM of each system, the Contractor shall review Technical Order (T.O.) 1C-130A-6, 1C-130J- 6, -6 Work Cards, and C-130 PDM Work Specification requirements to confirm they describe in sufficient detail the maintenance requirements required to ensure structural and component reliability.

4.5.6.3 The Contractor shall provide statistical analyses, as required by the Government, to support resolution of reliability issues.

4.5.6.4 The Contractor shall identify changes to T.O. 1C-130A-6 and 1C-130J-06 identified through RCM analyses. All changes must comply with applicable Military Specifications (Mil Spec) Spec and Military Performance Requirements (Mil PRF) and emphasize Maintenance Data Documentation (MDD) clarity and accuracy.

4.5.6.5 The Contractor shall identify items that should be serially tracked. Contractor shall use established process/procedures for serially tracked items and recommend refinements. Emphasis shall be placed on the following:

· Ability to add items as necessary and provide visibility into lifetime history of individual components

· Propose serialized tracking for any appropriate National Stock Numbers (NSN) identified through RCM analysis.

4.5.7 MECSIP Risk Assessment: The Contractor shall maintain an engineering risk assessment capability to ascertain, track and record existing and future structural or functional system risks. RCM analyses which result in a MIL-STD-882E, Appendix A, Table 4 value of 9 or less (Mishap Risk Category High is 1 – 5 and Mishap Risk Category Serious is 6 – 9) shall require a System Safety Hazard Analysis which shall be submitted to the Government for review and acceptance as a separate report attached to the Monthly Status Report. Each risk assessment shall include, as a minimum, the background with description of the risk, the Risk Index of the unmitigated hazard per MIL- STD-882E, recommendations for risk mitigation, and the Risk Index resulting from each recommendation.

4.5.7.1 MECSIP Monthly Reliability Report (MMRP): The Contractor shall create and maintain a MMRP for the SOF/PR C-130 fleet. This report will be SOF specific and a separate effort from the report already generated by the C-130 System Program Office. It may be expanded or modified as directed by the Government Program Manager.

4.5.8 AVIP RCM

The Contractor shall perform RCM/MSG-3 aircraft system analysis for SOF specific avionic systems by failure data, MDS, tail number and utilization. This process shall be refined to drill down to WUC levels to ascertain and define areas that require action and improvement. The contactor shall refine data analysis techniques for ranking systems/components for further RCM analysis and recommend improvements in the maintenance work card inspections and WUC accuracy based on RCM analysis results. The Contractor shall accomplish AFTO Form 252, Technical Order Publication Change Request, for recommended T.O. changes and provide these to the SOF C-130 SPO. The Contractor shall also investigate, as part of the RCM process, appropriate areas for implementing systems sensors to provide current structural health-state assessments and for driving prognostic actions to anticipate maintenance needs, in coordination with the Condition Based Maintenance (CBM+) program. The Contractor shall provide a RCM analysis report for WUC’s as identified by the government. The report shall include the recommendation for retention or deletion of every current Inspection task in the T.O. 1C-130A-6, T.O. 1C-130J-6, -6 Work Cards in addition to the cost and manpower projected savings.

4.5.8.1 The contractor’s initial AVIP RCM focus shall be to complete the SOF/PR C-130 baseline RCM analysis for systems as required by the government; for example:

· Installed Software for SOF Maintained systems

· 71XXX Navigation Systems

· 72XXX Radar Systems

· 76XXX Defensive Systems

4.5.8.2 The Contractor shall identify changes to T.O. 1C-130A-6 identified through RCM analyses. All changes must comply with applicable Military Specifications (MIL-SPEC) and Military Performance Standard (MIL-PRF) and emphasize Maintenance Data Documentation (MDD) clarity and accuracy.

4.5.8.3 The Contractor shall maintain a list of all subsystems and equipment that are to be covered by SOF AVIP to ensure that the United States Special Operations Command (USSOCOM) and Air Force Special Operations Command (AFSOC) have a single point database of the various avionic SOF systems and the applicable aircraft tail numbers.

4.5.8.4 CBRNE: The contractor shall develop and deliver a plan for SOF/PR C-130 aircraft a process/plan to address usability/decontamination of aircraft that have encountered an environment in which they have been exposed to Chemical, Biological, Radiological and Nuclear agents. The plan shall be in a format that is easily carried by aircrew and maintenance personnel in a deployed/hostile/denied airspace/location.

4.5.8.5 Preventative Maintenance Task: The contactor shall recommend improvements in scheduled preventive maintenance tasks of AVIP identified components to the SOF/PR C-130 SPO for approval.

4.5.8.6 AVIP Monthly Reliability Report (AMRP): The Contractor shall develop and maintain an AMRP for the SOF C-130 fleet. This report will be SOF specific and a separate effort from the report already generated by the C-130 System Program Office. This report may be expanded or modified as directed by the SOF C-130 Program Manager.

4.5.8.7 AVIP Risk Assessment: The Contractor shall maintain an engineering risk assessment capability to monitor existing and future functional system risks. RCM analyses which result in a MIL-STD-882E, Appendix A, Table 4 value of 9 or less (Mishap Risk Category High is 1 – 5 and Mishap Risk Category Serious is 6 – 9) shall require a System Safety Hazard Analysis which shall be submitted to the Government for review and acceptance at the appropriate level. Each risk assessment shall include, as a minimum, the background with description of the risk, the Risk Index of the unmitigated hazard per MIL-STD-882E, recommendations for risk mitigation, and the Risk Index resulting from each recommendation.

4.5.9 Operational Safety, Suitability, & Effectiveness (OSS&E) Support: Operational Safety, Suitability, & Effectiveness (OSS&E) Support: The Contractor shall conduct System Safety Investigations (SSI) as required to identify and evaluate risk hazards in accordance with MIL-STD-882 and Air Force Pamphlet (AFPAM) 90-902, Operational Risk Management (ORM) Guidelines and Tools, for SOF/PR C-130 structural and functional systems (to include, but not limited to structural members, mounting hardware, avionics, and software) to meet AFI 91-202 guidance. Contractor shall support the SOF/PR, Common C-130 System Safety Managers in maintaining and improving the System Safety Management System (SSMS) in order to enhance performance and improve the processes of system safety within the C-130 community.

4.5.9.1 Air Worthiness and Configuration Management Analyses: The Contractor shall conduct Air Worthiness analyses (AWI) as required to identify and evaluate air worthiness deficiencies in SOF/PR C-130 aircraft which do not meet Air Force Policy Directive AFPD 62- 6, AFI 62-601 and MIL-HDBK-516 Expanded guidance.

The Contractor shall conduct Configuration Management analyses (CMI) as required to identify and evaluate configuration deficiencies which do not meet AFI 63-131, AFI 63-1201 Section 1.1.3, AFMCI 63-1201, and EIA-649-B, RAFBI 63-104 guidance. The Contractor shall support the SOF/PR, Common C-130 Configuration Managers in maintaining and improving the Configuration Management System (CMS) in order to enhance performance and improve the processes of configuration management within the C-130 community. (A005, DI-NDTI-80809B)

4.5.9.2 Gun and Countermeasure Dispenser Flight Loads Survey: To support acquisition of new and updating of existing loads data critical to performing repairs, designing modifications, and assessing fatigue and maintenance schedules, the Contractor shall complete a survey of existing loads data for the 25mm GAU-12/U, 30mm Bushmaster II, 40mm L/60 BOFORS, 105mm M102 and any additional weapons systems specified by the Government. Any countermeasure loads not deemed sufficient for analysis purposes shall be identified and tested to complete the data set. As directed, a flight loads survey shall be conducted in which loads and strains for firing and dispensing in various flight configurations are directly measured. The data shall be used to quantify fatigue and fracture models, and the update inspection intervals of structure affected by the gunfire and counter-measure events. Report will be IAW DD Form 1423-1 (A005, DI-NDTI-80809B)

4.5.9.3 Load/Environment Spectra Survey (L/ESS) Support: The Contractor shall support Government efforts for L/ESS data recording, retrieval, archiving, and analysis. The Contractor shall provide independent review of the L/ESS program. Contractor shall support planning, design, installation, validation, and maintenance of data retrieval, storage, and assessment requirements as tasked (A005, DI-NDTI-80809B)

4.6 Packaging: The Contractor shall package and mark material in accordance with the contract (basic and/or order, as applicable) in accordance with the attached Air Force Materiel Command (AFMC) Form 158, Packaging Requirements. The Contractor shall package and mark material in accordance with other applicable Government regulations including, but not limited to, those regarding security, safety and environmental concerns.

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 electronic parts susceptible to electrostatic discharge damage 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), and MIL- HDBK-263B, Military Handbook / Electrostatic Discharge Control Handbook for Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices).

In accordance with MIL-STD-2073-1E, Standard Practice for Military Packaging, shipping containers received, which meet the requirements of the AFMC Form 158 and are suitable for return shipment of serviceable assets, shall be reclaimed and stored for reutilization. Unsuitable shipping containers shall be disposed of and replaced with new containers that meet the requirements of the AFMC Form 158.

4.7 Counterfeit Electronic Parts: The Contractor shall establish and maintain a counterfeit electronic part detection and avoidance system to mitigate the risk of counterfeit electronics parts being installed in end items or otherwise entering the USAF/DoD inventory. The system shall incorporate processes/procedures to address the requirements listed in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the task order. The Government's review of the Contractor’s system will be accomplished as part of the evaluation of the Contractor’s purchasing system in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

4.9 Travel: The Contractor may be required to travel to Government installations or to other Contractor facilities. Routine travel requests shall be submitted to the Government PM for review no later than 10 Business Days prior to the date of departure; routine requests that do not meet this minimum requirement will not be approved. Urgent travel requests may be submitted for approval in a shorter timeline and will be considered on a case by case basis; urgency of travel will be determined by the Government. All travel requests must be approved by the PCO prior to departure. The Contractor shall provide a list of any projected travel requirements in the monthly status report. Trips, as well as number and types of personnel, shall be limited to the minimum required to accomplish work requirements. The Contractor shall be responsible for arranging all travel of Contractor personnel during the period(s) of performance. The Contractor shall use the lowest cost mode of transportation commensurate with mission requirements and good traffic management principles. All travel expenses are limited by the FAR and must comply with the Joint Federal Travel Regulations (JFTR). All trip reports shall be documented in the monthly status report, not as a separate standalone document. Detailed recommendations and courses of action resulting from travel, will be due to the government NO LATER THAN 30 Days after travel.

5.0 General Information:

5.1. Continuation of Mission-Essential Services During a Crisis: The Functional Commander (FC) or civilian equivalent has determined these services are not mission-essential and services will not continue in the event of a crisis. (i.e. Government Closing)

5.1.1 To avoid duplication of effort, the Contractor shall establish a single point of contact for all issues affecting this Contract. Contractor personnel shall communicate needs and meeting requests through the established Contractor POC only who will in-turn communicate needs for communication and meeting requests to Government PM.

5.1.2 Formal Meetings: The Contractor shall hold one Technical Interchange Meeting (TIM) per PoP. All TIMs shall provide status to the Government status and technical updates as appropriate of all ongoing tasks as well as problems found in the analyzed area to include proposed solutions. All TIMs shall be conducted at the Contractor’s facility unless directed by the Government. The TIM will take the place of the MSR for the month it is held; i.e. if the TIM is held in January, no MSR will be required for February. The TIM will be reported IAW DD Form 1423-1. Regardless of the meeting’s purpose, if it is deemed a formal meeting by the Government, the Contractor shall provide meeting agenda, presentation material and conference minutes IAW DD Form 1423-1 (A001, DI-ADMN-81249B; A002, DI-ADMN-81373; A003, DI-ADMN-81250B)

5.2. Security Requirements

5.2.1 Security Regulations: The Contractor shall ensure personnel, information, system, property, facility and security requirements are met. The Contractor shall comply with security regulations including, but not limited to, Department of Defense (DoD) 5200.2-R, Personnel Security Program; DoD 5220.22- M, National Industrial Security Program Operating Manual (NISPOM), DoD Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program, DoD Manual 5205.02-M.

5.2.2 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The Contractor shall comply with DoDD 5205.02E and DoD Manual 5205.02-M to protect United States (U.S.) Government interests. The Contractor shall ensure Contractor personnel who perform work on a Government facility comply with the OPSEC procedures of the facility.

5.2.3 Security Incident or Violation: The contractor shall immediately notify the unit security manager and the Government PM, of any actual security violation, security incident, or of any indication of a potential unauthorized disclosure or compromise of classified or sensitive but unclassified information.

5.2.4 Access to Government System(s): The Government will provide contractor/subcontractor personnel access to system(s) necessary to perform tasks under the contract/order. The Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified or classified Government Automated Information System (AIS) have the respective background check or security investigation conducted. At a minimum, the Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified AIS have a National Agency Check with Inquiries (NACI) conducted. Upon completion/termination of the contract/order or transfer/termination of contractor/subcontractor personnel, the Contractor shall ensure the system account(s) are closed.

5.2.5 Access to Government Facility or Military Installation:

5.2.5.1 Access to Robins Air Force Base (AFB): The Contractor shall ensure contractor/subcontractor personnel who require access to Robins AFB comply with the security requirements of the installation. The Contractor shall provide the Government PM with a list of all contractor/subcontractor personnel requiring access to Robins AFB, the contract/order number and the period of performance. The Contractor shall also provide, if possible, the location of the work site and the days/hours during which the contractor/subcontractor personnel will require access to Robins AFB. The Government PM will work with the unit Security Manager to ensure personnel have the proper clearance prior to forwarding to PCO. In all cases, the PCO must approve access prior to work beginning.

5.2.5.2 Access to Government Facility or Military Installation: The Contractor shall ensure contractor/subcontractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation.

5.2.6 Common Access Card (CAC)

5.2.6.1 The Contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, for DoD facility entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order. The Contractor shall provide a list of contractor/subcontractor personnel who require a CAC to the PCO. The Government will provide the Contractor instruction on how to complete a Contractor Verification System (CVS) application and notify the Contractor of approval/disapproval of contractor/subcontractor personnel application. Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility [usually the Military Personnel Flight (MPF)].

5.2.6.2 The Contractor shall immediately report a lost or stolen CAC as directed by local Government policy. The Contractor shall notify the PCO of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list within five business days. The Contractor shall return a CAC within five business days once contractor/subcontractor personnel no longer require computer network/system access and/or facility access. The Contractor shall return an expired CAC within five business days after the expiration date. The Contractor shall return any and all CACs within five business days after completion/termination of the contract as directed by local Government policy.

5.3 Safety Requirements:

5.3.1 Contractor Compliance: The Contractor shall comply with Government Safety and Health regulations including, but not limited to, Public Law 91-596, Occupational Safety and Health Act (OSHA), and DoDD 4715.1E, Environmental, Safety, and Occupational Health (ESOH). OSHA and ESOH requirements shall be incorporated into the Contractor’s safety program.

5.3.2 Mishap Notification/Investigation: The Contractor shall report mishaps including damage to DoD property; occupational illness to DoD military or civilian personnel; injury to on- or off-duty DoD military personnel; injury to…