PWS_SSES_dated_6_Dec_2012_Final.pdf

PR#: FD2060-13-30267 PWS i

HEADQUARTERS

AIR FORCE LIFE CYCLE MANAGEMENT CENTER (AFLCMC)

ROBINS AIR FORCE BASE, GEORGIA 31098

PR NUMBER: FD2060-13-30267 DATE: 6 December 2012

PERFORMANCE-BASED WORK STATEMENT (PWS)

TYPE WORK: AGING-AIRCRAFT-RELATED ENGINEERING SERVICES FOR FIXED

WING SPECIAL OPERATIONS FORCES (SOF) STRUCTURAL SUPPORT and

ENGINEERING SERVICES (SSES)

CONTENTS

SECTION TITLE PAGE

SECTION 1 DESCRIPTION OF SERVICES 1

SECTION 2 SERVICES SUMMARY 2

SECTION 3 GOVERNMENT FURNISHED PROPERTY & SERVICES 3

SECTION 4 GENERAL INFORMATION 4

SECTION 5 APPENDICES 21

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their Contractors (Administrative or Operational Use). Other requests for this document shall be referred to AFLCMC/WIUEE, Robins AFB, GA 31098.

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 1

1.0 DESCRIPTION OF SERVICES

The Contractor shall provide continuing engineering services, structural support, analytical engineering studies, prototyping, and structural testing to support the Special Operations Forces (SOF) C-130s (AC-130, MC-130, HC-130, and EC-130). The contractor shall provide “quick look” report for critical engineering support issues correctly and without delay.

This program will benefit the Air Force by addressing structural and engineering concerns that are classical Aging Aircraft (AA) problems created by the configuration and missions of the Special Operations Forces (SOF) C-130 aircraft and the high flying hours caused by the increased number of missions. It will provide essential analysis of SOF-specific aircraft, and will also focus on identifying and solving AC-130, MC-130, HC-130 and EC-130- specific structural integrity and other engineering issues as well as providing the System Program Office (SPO) with a flexible tool to address as-yet to be determined engineering and technical issues.

Existing aircraft structural models and usage databases will be updated and improved to reflect the current mission profiles, hardware configurations, and usage. As tasked, the Contractor shall also continue the analysis of several known problematic areas on SOF C-130 aircraft. The Contractor shall conduct studies and/or data acquisition as tasked by the Government. The Contractor shall analyze and provide recommendations for the Airworthiness, Configuration Management and System Safety Processes for all SOF 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 Special Operations forces. Finally, the Contractor shall provide technical and/or engineering support to ongoing activities of SOF C-130 SPO.

The purpose of this task is to perform engineering and technical data services required to determine the stress and load characteristics and/or loading environment of specified areas of the AC-130, MC-130, HC-130 and EC-130; provide engineering and data services to define the usage and operational environment of SOF C-130’s; provide support for the SOF Mechanical Equipment and Subsystem Integrity Program (MECSIP), Avionics Integrity Program (AVIP), and Diminishing Manufacturing Sources and Material Shortages (DMSMS) programs; maintain and deliver up-to-date aircraft models, and provide other generic engineering and technical support not meeting any of the above categories as tasked by the

SPO.

Each stress and loads analysis shall include the following (as directed by the Government): an identification of the lowest margin of safety locations, locations that would be susceptible to the highest rate of structural failures such as cracking, locations that would be susceptible to critical multi-site damage, and Damage Tolerance Analysis. These services may include analytical engineering, aircraft structural engineering, and development of engineering concepts, reports, and/or prototypes. The Contractor shall therefore provide flexible technical

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 2

and engineering support as-needed to the SPO for SOF aircraft and support equipment peculiar to such aircraft.

The structural-support part of this effort is classical Aging Aircraft issues in that it (1) is concerned with life predictions and failure analyses that are a direct result of continued long-term special operations aircraft use, and (2), considers severe corrosion effects as are seen on an aircraft after a substantial time in service in austere and/or low-altitude environments on an as-required basis. As directed, the Contractor shall benefit the Air Force by updating existing SOF C-130 aircraft models, including structural models, to reflect the AC-130, MC-130, HC- 130 and EC-130 configurations and loadings, shall identify (through computer models, records surveys, Non Destructive Inspections (NDI), and other methods deemed appropriate) AC-130, MC-130, HC-130 and EC-130-specific high-fatigue and/or corrosion areas, and other areas exhibiting accelerated deterioration of structural soundness on the AC-130, MC- 130, HC-130 and EC-130, shall perform life predictions on these areas on this aging aircraft, shall assist in gathering improved usage and loading data, shall collect usage and loading data, shall improve and create databases as required to improve access to usage and life-cycle data, shall notify Government of technical data discrepancies, shall provide other engineering assistance as tasked, and shall suggest solutions to extend/maintain the weapon system’s economically viable life as the system continues to age. In addition to the above tasks the contractor shall be prompt with Mishap Notification and Reporting when it is required.

2.0 SERVICES SUMMARY (SS)

Performance Objectives

PWS Para.

Performance Threshold

Provide “quick look” report for critical engineering support issues correctly and without delay

4.3.2.2 Initial “Quick Look” summary

due within 10 calendar days of the conclusion of site survey For actions not requiring a site survey, ”Quick Look” due 10 calendar days from notification

Mishap Notification and Reporting

4.8.2 No more than one instance of

late mishap notification per year

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 3

3.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL, AND

SERVICES (GFP/GFE/GFM/GFS).

3.1 SERVICES

During the period of performance of this task, the Government will provide drawings, technical orders, technical data, and test reports as necessary on an as-available basis, for the accomplishment of this task.

3.2 PROPERTY

During the period of performance of the task order, the Government will provide the Contractor access to Government equipment required for the accomplishment of this task on an as-available basis. DFARS PGI 245-2

3.3 REPORTING LOSS OF GOVERNMENT PROPERTY (FEB 2011)

a. Definitions. As used in this clause— “Government property” is defined in the clause at FAR 52.245-1(a), Government Property. “Loss of Government property” means unintended, unforeseen, or accidental loss, damage, or destruction of Government property that reduces the Government’s expected economic benefits of the property. Loss of Government property does not include purposeful destructive testing, obsolescence, normal wear and tear, or manufacturing defects. Loss of Government property includes, but is not limited to—

(1) Items that cannot be found after a reasonable search;

(2) Theft;

(3) Damage resulting in unexpected harm to property requiring repair to restore the item to usable condition; or

(4) Destruction resulting from incidents that render the item useless for its intended purpose or beyond economical repair.

“Unit acquisition cost” means—

(1) For Government-furnished property, the dollar value assigned by the Government and identified in the contract; and

(2) For Contractor-acquired property, the cost derived from the Contractor’s records that reflect consistently applied, generally acceptable accounting principles.

b. Reporting loss of Government property.

(1) The Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application for reporting loss of Government property. Reporting value shall be at unit acquisition cost. The eTools “LTDD of Government Property” toolset can be accessed from the DCMA home page External Web Access Management application at http://www.dcma.mil/aboutetools.cfm.

(2) Unless otherwise provided for in this contract, the requirements of paragraph (b)(1) of this clause do not apply to normal and reasonable inventory adjustments, FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 4 i.e., losses of low-risk consumable material such as common hardware, as agreed to by the Contractor and the Government Property Administrator. Such losses are typically a product of normal process variation. The Contractor shall ensure that its property management system provides adequate management control measures, e.g., statistical process controls, as a means of managing such variation.

(3) The Contractor shall report losses of Government property outside normal process variation, e.g., losses due to Theft; Inadequate storage; Lack of physical security; or “Acts of God.”

(4) This reporting requirement does not change any liability provisions or other reporting requirements that may exist under this contract.

4.0 GENERAL INFORMATION

4.1 The Contractor shall provide a single task order manager with authority and responsibility for this task. The Contractor shall attend and document minutes of reviews and technical interchange meetings related to this task. The Government may delegate some of the specific technical responsibilities to Government parties who serve as the effective customer for various efforts under this order—i.e., the Contractor may, as directed by the Government task order manager, interface with persons other than the Government task order manager for the details of various efforts. (A001, DI-ADMN-81250A, A007, DI-ADMN-81249A/T)

4.1.1 MISSION-ESSENTIAL: The Functional Commander/Director has determined, by placing in writing their decision, that this requirement is not Mission Essential (M-E) in accordance with DoDI 1100.22, Policy and Procedures for Determining Workforce Mix and DFARS 237.76, Continuation of Essential Contractor Services.

4.2 GENERAL REQUIREMENTS

4.2.1 MONTHLY STATUS REPORTS (MSR)

The Contractor shall deliver MSRs in accordance with the accompanying Contract Data Requirements List (CDRL). These reports shall cover the technical support provided by the Contractor during the previous monthly reporting period, and shall individually address all current efforts. The Contractor shall, as applicable, provide updates regarding task status, deliverables, contract issues and actions, as well as anticipated future task requirements for the next reporting period. In all cases the Contractor shall address expenditure data— Funds Expenditure charts and raw data shall be provided for man-hours and expenditures. (A002, DI-MGMT-80368A)

4.2.2 TASK ORDER CLOSEOUT STATUS REPORT:

The Contractor shall submit a Task Order Closeout Status Report in lieu of a Monthly Status Report for the last full month of the period of performance. The Task Order Closeout Status Report shall include a summary of all tasks completed during the task order’s period of performance, including those tasks completed in the last month of the period of performance.

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 5

The Task Order Closeout Status Report shall include funds expenditure and manpower expenditure charts to cover the entire period of performance; furthermore, these expenditure charts shall be broken down both by month as well as by major task order sub-task. The final submission of the Task Order Closeout Status Report shall be included with the Data Accession List submission (A002, DI-MGMT-80368A)

4.2.3 FORMAL MEETINGS

The Government will clearly identify whether a meeting is considered formal. Formal meetings shall be reflected in the Integrated Master Schedule (time permitting), and for which CDRL’s for Presentation Material (A008, DI-ADMN-81373), Agendas (A007, DI-ADMN- 81249A/T), and Minutes (A001, DI-ADMN-81250A) apply. All official Technical Interchange Meetings (TIMs) are considered formal meetings. Teleconferences will not normally be considered formal meetings unless clearly identified as such ahead of time.

Note: If a kickoff meeting is conducted at the beginning of this effort, it will be considered a formal meeting.

4.2.3.1 TECHNICAL INTERCHANGE MEETINGS

The Contractor shall hold at least one TIM as requested by the Government (a kick-off meeting at the beginning of the period of performance, if conducted, does not qualify as a TIM). All TIMs shall provide status to the Government of problems found with and proposed solutions to the areas being analyzed under the study, and/or discuss other status and technical updates as appropriate. All TIMs shall be held at the Contractor’s facility, unless directed by the Government to be held at another location. (A001, DI-ADMN-81250A, A007, DI-

ADMN-81249A/T, A008, DI-ADMN-81373)

4.2.4 INTEGRATED MASTER SCHEDULE (IMS)

The Contractor shall submit an IMS at the beginning of the period of performance and monthly schedule updates/schedule status reports. These monthly schedule status reports may be incorporated with the monthly status reports, if desired. The Contractor shall update the IMS to reflect any new workload assignments by the next IMS reporting date and to include the most current and accurate estimate of schedule. In all cases, the Contractor shall coordinate updates to the IMS with AFLCMC/WIUEE. (A004, DI-MGMT-81650)

4.2.5 TRAVEL

The Contractor may be required to travel to Government installations or to other Contractor facilities. 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 program effort. The Contractor shall use the lowest cost mode of transportation commensurate with mission requirements and good traffic management principles. All trips involving travel more than 45 statute miles from Contractor’s main facility shall be documented in trip reports. The Contractor shall provide a list of any projected travel requirements in the monthly status report. Furthermore, all travel expenses are limited by the Federal Acquisition Regulation (FAR) and must comply with the Joint Travel Regulations (JTR). Routine travel requests shall be submitted for approval to the

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 6

Procurement Contracting Officer (PCO) a minimum of two (2) weeks in advance of the departure date. Urgent travel requests may be submitted for approval in a shorter timeline and will be considered on a case by case basis. (A002, DI-MGMT-80368A)

4.2.6 SECURITY REQUIREMENTS

4.2.6.1.1 General: Actual knowledge of, generation, or production of classified information is not required for performance of the contract. Cleared personnel are required to perform this service because security measures which are in force do not preclude access to classified information.

4.2.6.1.2 Operations Security (OPSEC): Contractor personnel shall participate in the OPSEC program locally administered by the Air Force (AF) activity.

4.2.6.1.3 Employee Clearances: Contractor employees that need access to Government owned Automated Information Systems (AIS) requires the minimum of a Favorable National Agency Check (NAC). Submit a Standard Form 85P, Questionnaire for Public Trust Positions, (fingerprint cards if available) to the (WIUE) Security Office for processing.

4.2.6.1.4 Security Incidents and Violations: The contractor shall immediately notify the (WIUE) Security Office 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.

4.2.6.1.5 Security Education: All full time contractor employees occupying physical space on Robins Air Force Base shall comply with the (WIUE) Security Education and Awareness program. The program consists of the following components: initial training, annual refresher training, and periodic tailored training.

4.2.6.2 IDENTIFICATION CREDENTIAL REQUIREMENTS:

The employee’s contract administrator shall forward a Common Access Card (CAC) request to the appropriate Government Contracting Officer. The Government Contracting Officer will submit a letter to the Government Contracting Officers Representative (COR) requesting authorization to issue the CAC. Approved letter will be forwarded back to the employee’s contract administrator. The employee’s contract administrator will forward the CAC request to the Government Trusted Agent (TA) for processing. Electronic mail notification will be provided by the TA to contract employee once information is loaded in Contractor Validation System (CVS). Contractor has 30 calendar days to complete application process. User ID and Temporary Password will be provided – Contractor has seven (7) days to initially log into CVS system. The CAC shall be worn or prominently displayed in such a manner as to be visible at all times while performing work on or visiting the Government installation. Upon completion or termination of the contract/order or termination/transfer of the employee, the CAC shall be returned to the cognizant Military Personnel Flight (MPF) office.

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 7

4.2.6.3 PHYSICAL SECURITY:

The Contractor shall be responsible for safeguarding all Government property provided for Contractor use. At the end of each work period, Contractor personnel shall ensure that all equipment and materials provided for their use shall be secured.

4.2.6.4 CLASSIFICATION AND POSITION SENSITIVITY DESIGNATION:

This effort is unclassified; however, a minimum of a National Agency Check is required for Contractor employees requiring a CAC.

4.2.7 MEETING MINUTES AND AGENDAS

The Contractor shall document any formal meeting (see Formal Meetings and Technical Interchange Meetings sections of this PWS) with meeting minutes (A001, DI-ADMN- 81250A). Contractor shall submit agendas prior to any formal meeting (A007, DI-ADMN- 81249A/T).

4.3 TECHNICAL OBJECTIVES AND GOALS

4.3.1 All reports delivered under the Engineering and Technical Data Services paragraph and sub-paragraphs below shall comply with the guidance contained in the “Technical Reports” paragraphs and sub-paragraphs of this PWS.

4.3.2 ENGINEERING AND TECHNICAL DATA SERVICES: 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 life-style standpoint, as well as other areas needing study. Each of these analyses of these areas shall be summarized in a report (see Technical Reports paragraph) for the Government’s use, such as determining inspection intervals and potential repair designs. To preserve the work done for these analysis efforts, the Contractor shall incorporate all Finite Element (FE) models generated into the MERC-developed Global C-130 Finite Element Models. All FE models shall incorporate best practices for mesh sizing and attachment and shall conform to the methods and formats used in the MERC-developed Global C-130 Models. (A003, DI-MISC- 80508B)

4.3.2.1 ENGINEERING SUPPORT: The Contractor shall provide engineering support for tasks requiring quick response (e.g., “Quick Look”) as well as longer term engineering support for SOF C-130- related issues. This includes SOF C-130 aircraft and support equipment.

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 8

4.3.2.1.1 STRUCTURAL MODEL UPDATE: The Contractor shall develop, maintain, and, if required, deliver structural models of SOF-specific C-130 airframes. The global finite element models of the AC-130U and MC-130W developed by MERC shall be maintained and refined to support engineering investigations and critical engineering support tasks. The Contractor shall initiate development of additional Global models of SOF C-130 airframes (AC-130H, MC-130E/H, EC-130E/J, and MC-130P), as directed and prioritized by the Government.

4.3.2.1.2 Aircraft Structural Analysis: The Contractor shall perform Finite Element Analysis (FEA) of designs and components in support of modification programs or Configuration Control Board review.

Failure/damage analysis of aircraft structural members shall be performed to determine the underlying causes. Corresponding recommendations shall be made per the Government’s request for repairs, modifications, inspections, and maintenance procedure updates.

4.3.2.1.3 Repair Design, Analysis, Testing: The Contractor shall provide design, analysis, testing, prototyping, and tooling support as necessary for repair or manufacture as directed by the Government Aircraft Structural Integrity Program (ASIP) Manager and authorized by the

PCO.

4.3.2.1.3.1 The Contractor shall perform testing (failure analysis, fatigue testing, vibration testing, static testing, strain and deflection measurements, shock, vibration, flight regime, etc.), as required, to evaluate specific design and repair configurations as directed by the Government ASIP Manager. The Contractor shall provide testing on load frames capable of approximately 250,000 lb. capacity and shall provide data acquisition units to monitor and record all test results. The Contractor shall support design efforts with flight testing where required. Flight testing support will include test plan generation, Form 1067 support (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/recommendations, and supporting data.

4.3.2.1.3.2 The Contractor shall evaluate current and proposed designs using analytical methods as directed by the Government ASIP Manager. Types of analyses may include finite element analysis with static, thermal, impact, or dynamic (shock, transient, and vibration) loading. Results of analyses may include stress, strain, displacements, temperature, and frequencies and modes of vibration. All analysis of designs shall be documented in a report with supporting data. (A003, DI-MISC-80508B)

4.3.2.1.3.3 The Contractor shall develop improved design solutions and proofs of concept as directed by the Government ASIP Manager. The improved design solutions may be to eliminate cracking causes, improve damage tolerance, or improve maintenance operations.

3D scanning and modeling of complex components may be required to account for documentation gaps in loft data, contour data, and/or antiquated drawing details. The

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 9

Contractor shall provide the capability to scan such parts in support of efforts and to support modeling of components at Government ASIP Manager’s direction. Models shall be made available in IGES format, if requested.

4.3.2.1.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 ASIP Manager and shall be concluded with a report detailing all analyses, data, designs, and recommendations/conclusions. (A003, DI-

MISC-80508B)

4.3.2.1.5 Risk Assessments: The Contractor shall provide support for Risk Assessments at the direction of the Government ASIP Manager. Support must comply with all applicable Risk Assessment guidelines and, at the Government ASIP Manager’s direction, shall be input into the Aging Fleet Integrity and Reliability Management (AFIRM) Risk Assessment tracking tool. A Risk Assessment report shall be generated outlining the supporting data and analyses.

4.3.2.1.6 Testing: The Contractor shall provide static and fatigue testing of samples and large components, up to 250,000 lb. capacity with test plan and test reports. The Contractor must be capable of providing fixture design to accomplish the tests.

4.3.2.1.6.1 The Contractor shall perform ground/flight test planning and execution, where required. The Contractor shall support with test plans, Form 1067 Modification Proposal (where applicable), CCB presentation support (where applicable), instrumentation installation, and data collection/review. 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. (A003, DI-MISC-80508B)

4.3.2.2 Critical Engineering Support: Where required, The Contractor shall provide safety critical support to the ASIP office. In the case of the Contractor providing structural support or engineering services which the Government categorizes as Critical, the Contractor shall provide a concise, early "Quick Look" report summarizing all of the following (as applicable):

• 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 (A005, DI-NDTI- 80809B)

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 10

4.3.2.2.1 At the beginning of the Critical effort, the Contractor shall provide this "Quick Look":

• To those individuals identified by the Government

• In an electronic format compatible with Microsoft Office

• Within ten (10) calendar days from the start date defined in the Technical Reports

CDRL (A003, DI-MISC-80508B)

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

4.3.2.3.1 Aging Fleet Integrity and Reliability Management system (AFIRM): The Contractor shall modify and maintain SOF C-130 AFIRM database to include current Time Compliance Technical Order (TCTO) and modification implementation status; Reliability- Centered Maintenance (RCM), MECSIP, and other available data (especially as it relates to SOF-peculiar aircraft configurations and including but not limited to IR shields, all guns, counter-measures dispensers, and SOF-specific avionics/electronics/electronic warfare hardware and configurations.) Modifications to AFIRM shall include automation of data pulls from the various sources to the maximum extent practical. Modification to AFIRM shall also include development of AFIRM tools for TCTO configuration status updates, reporting for SOF-specific concerns such as gunfire rates and firing orbit dwell time (if practical), and other tools to support SOF engineering monthly status reporting. Requirements for hosting and deployment via .mil networks shall be established; access to .mil networks will be provided by the Government in accordance with the implementation of those requirements to the maximum extent possible.

4.3.2.3.2 Survey of SOF C-130 modifications: The Contractor shall continue to update, improve, and maintain the tail-by-tail survey of SOF modifications reported through AFIRM.

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.

4.3.2.4 SOF C-130 MECSIP and AVIP Master Plan

The Contractor shall develop an addendum to the current Tactical Airlift C-130 MECSIP and AVIP Master Plans that will cover the SOF related C-130 subsystems. This addendum will identify all subsystems and equipment that are to be covered by SOF MECSIP and AVIP, establish analysis prioritization, develop a SOF unique subsystem 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.

4.3.2.5 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

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 11

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 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 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 Technical Order (T.O.) changes and provide these to the SOF C- 130 SPO. 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 the T.O.

1C-130A-6, -6 Work Cards, and PDM in addition to the cost and man power projected savings. The Contractor shall report on the status of each ongoing RCM analysis monthly in the MSR. Subsequent option years shall be discussed and agreed upon for continued analysis.

(A002, DI-MGMT-80368A)

4.3.2.5.1 The contractor’s initial RCM focus shall be to complete the initial SOF C-130 baseline RCM analysis for the following systems:

• 467XX – Aerial Refueling System

• 46WXX- UARRSI System

4.3.2.5.2 During RCM of each system, the Contractor shall review the 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 preventative maintenance requirements required to ensure structural and component reliability.

4.3.2.5.3 The Contractor shall provide Weibull analyses, as necessary, to support resolution of reliability issues.

4.3.2.5.4 The Contractor shall identify changes to T.O. 1C-130A-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.3.2.5.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.

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 12

4.3.2.5.6 MECSIP Risk Assessment

The Contractor shall maintain an engineering risk assessment capability to maintain existing and future structural or functional system risks. RCM analyses which result in a MIL-STD- 882D, 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 an initial risk assessment 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-882D, recommendations for risk mitigation, and the Risk Index resulting from each recommendation (not sure what CDRL goes here, I think A003, DI-MISC-80508B is correct. Might need to check with Frank to verify though.)

4.3.2.5.7 MECSIP Monthly Reliability Report (MMRP)

The Contractor shall create and maintain a MMRP for the SOF C-130 fleet. This report shall be expanded or modified as directed by the SOF C-130 Program Manager.

Deliverable - Monthly Reliability Reports shall be provided as an attachment to the Monthly Status Report.

4.3.2.5.8 MECSIP Community of Practice (CoP)

The Contractor shall maintain an electronic bulletin board/forum IAW MIL-STD-1798B that facilitates continuous feedback and communication with field users and depot engineering.

The emphasis should be on ease of access and topic indexing for historical reference. If required, Contractor shall coordinate this effort with necessary Air Force Life Cycle Management Center Information Technology (AFLCMC IT) department(s).

4.3.2.6 AVIP RCM Efforts

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 Work Unit Code (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 each system. The report shall include the recommendation for retention or deletion of every current PM in the T.O. 1C-130A-6, T.O. 1C-130J-6, -6 Work Cards, and PDM in addition to the cost and man power projected savings.

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 13

4.3.2.6.1 The contractor’s initial AVIP RCM focus shall be to complete the SOF C-130 baseline RCM analysis for the following systems:

• 71XXX Navigation Systems

• 72XXX Radar Systems

• 76XXX Defensive Systems

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

4.3.2.6.3 The Contractor shall maintain a list of all subsystems and equipment that are to be covered by SOF AVIP to ensure that the USAF have a single point database of the various avionic SOF system and the applicable aircraft tail numbers.

4.3.2.6.4 The Contractor shall identify items that should have a Unique Identification (UID) marked for future serial tracking. The Contractor shall use established Tactical Airlift SPO process/procedures for recommending UID marking. Emphasis shall be placed on the use of RCM for the:

• Identification of components and assemblies necessary for accurate tracking of the reliability of aircraft systems and subsystems

• Identification of potential bad actor components

4.3.2.6.5 Preventative Maintenance Task

The contactor shall recommend improvements in scheduled preventive maintenance tasks of AVIP identified components to the SOF C-130 SPO for approval. The Contractor shall appropriately submit and track approved recommendations until implemented.

4.3.2.6.6 AVIP Monthly Reliability Report (MMRP)

The Contractor shall create and maintain a MMRP for the SOF C-130 fleet. This report shall be expanded or modified as directed by the SOF C-130 Program Manager. Deliverable - Monthly Reliability Reports shall be provided as an attachment to the Monthly Status Report.

A002, DI-MGMT-80368A

4.3.2.6.7 AVIP Community of Practice (CoP)

The Contractor shall maintain an electronic bulletin board/forum IAW MIL-STD-1798B that facilitates continuous feedback and communication with field users and depot engineering.

The emphasis should be on ease of access and topic indexing for historical reference. If required, Contractor shall coordinate this effort with necessary AFLCMC IT department(s).

4.3.2.7 Drawings/Engineering Data: The Contractor may create engineering drawings, drawing packages, and/or models such as those required to document a concept, build a prototype, present an idea to the Government, or investigate the manufacturability of a potential design. (A009, DI-SESS-81002E)

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 14

4.3.2.8 Site Surveys: The Contractor shall supplement its efforts under this task with site surveys and/or tests and surveys of actual aircraft and/or aircraft-related equipment and components. Most of these activities shall be performed at AFLCMC; however, the Contractor may conduct these activities at Hurlburt Field, Florida, Cannon AFB, New Mexico or other locations as required by the Government. If required, travel of Contractor personnel shall be in accordance with (IAW) the Travel Paragraph of this PWS.

A report shall be submitted summarizing each site survey, with a level of detail commensurate to the length of the specific site survey effort (redundant trips within the local area, e.g.

successive trips to AFLCMC for the same issue, and/or multiday trips, may be summarized in a single report). (A005, DI-NDTI-80809B)

4.3.2.9 Studies: The Contractor shall perform independent technical studies to support AC- 130, MC-130, HC-130 and EC-130 Detailed Area Analysis efforts (to include those 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 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 to the Government 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). Further requirements for technical reports are located in the Technical Reports section of this PWS and CDRL authorities (A003, DI-MISC-80508B) and (A005, DI-NDTI-80809B)

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

4.3.2.11 Load/Environment Spectra Survey (L/ESS) Support: The Contractor shall support Government efforts for L/ESS data recording, retrieval, archiving, and analysis. The

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 15

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. Contractor shall provide usage monitoring on select aircraft as an interim bridge to the long-term permanent L/ESS installation. Finally, the Contractor shall prepare a brief white paper summarizing the benefits that would accrue to the user from the implementation of the interim L/ESS recording system.

4.3.2.12 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 (A003, DI-MISC- 80508B as applicable); 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.

4.3.2.13 DATA MANAGEMENT:

4.3.2.13.1 Delivery Method: Per Department of Defense (DoD) policy, every attempt shall be made by the Contractor to 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. (A009, DI-SESS-81002E)

4.3.2.13.2 File Format: 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. (A009, DI-SESS-81002E)

4.3.2.13.3: Drawing Format: 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-81002E)

4.3.2.13.4 Data Accession List (DAL): Consistent with CDRL of this contract, immediately prior to the conclusion of the period of performance of this task order, the Contractor shall submit to the Government’s technical point of contact (POC) a DAL on one or more compact disks(CD’s). 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 TIMs and otherwise), all conceptual drawings, all technical data, all raw data (see Raw Data Requirements paragraph), all pictures, all structural models and associated data, and all other documents generated under this task order. Where data transmitted previously was transmitted on letter or other format containing a signature, the signature page (material) shall be contained on the disk in Adobe® Acrobat™, .jpeg, .gif, or other common computer graphical format. The data contained on the DAL CD shall be

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 16

organized by CDRL, task order phase, major task order component, and/or any other 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 DAL shall be delivered to the Government’s POC on as many compact disk(s) as shall be required to contain the information. The DAL shall not include Contractor personnel security information. (A006, DI-MGMT-81453A and A00A, DI-IPSC-81488)

4.3.2.13.5 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 AFLCMC/WIUEE for alternate digital formats and/or delivery options. (A003, DI-MISC-80508B) Note: The Contractor need not include any report or “summary” material with this early raw data submission other than any verbiage required to explain sensor locations and types, (thermocouple, lateral accelerometer, strain gauge, etc.), appropriate engineering units (micro strain, temperature, displacement, acceleration, etc.), and background conditions (time, location, ambient temperature, other atmospheric and solunar data, etc.)

4.3.2.14 Operational Safety, Suitability, & Effectiveness (OSS&E) Support

4.3.2.14.1 System Safety

4.3.2.14.1.1 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 C- 130 structural and functional systems to meet AFI 91-202 guidance. (A003, DI-MISC- 80508B)

4.3.2.14.1.2 Contractor shall support the SOF/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.3.2.14.2 Air Worthiness

4.3.2.14.2.1 Contractor shall conduct Air Worthiness Investigations (AWI) as required to identify and evaluate air worthiness deficiencies in SOF C-130 aircraft which do not meet AFPD 62-6, AFI 62-601 and MIL-HDBK-516 Expanded guidance. (A003, DI-MISC- 80508B)

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 17

4.3.2.14.2.2 Contractor shall support the SOF/Common C-130 Airworthiness Managers in maintaining and improving the Air Worthiness Management System (AWMS) in order to enhance performance and improve the processes of air worthiness within the C-130 community. (A003, DI-MISC-80508B)

4.3.2.14.3 Configuration Management

4.3.2.14.3.1 Contractor shall conduct Configuration Management Investigations (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-A, RAFBI 63-104 guidance.

(A003, DI-MISC-80508B)

4.3.2.14.3.2 Contractor shall support the SOF/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. (A003, DI-MISC-80508B)

4.4 SPECIFIC REQUIREMENTS

4.4.1 TECHNICAL REPORTS: The Contractor shall document tests, data, analysis details, engineering assumptions, results and conclusions in reports that are consistent with professional technical writing practices. Such reports shall provide an executive summary of the objectives, findings, and conclusions/recommendations, with more detailed discussion in subsequent sections that are concisely worded and logically organized. The Contractor shall consider improving the readability of reports containing cumbersome analysis by inserting the bulk of such analysis into appendices, with important results included in the main body of the report. Where applicable, all methodology used in analysis shall be thoroughly explained.

Where applicable, equations shall be shown, sample calculations provided, and all terms and variables contained within equations shall be clearly defined and traced. As necessary, all empirical relationships, empirical stress concentration factors, empirical safety/uncertainty factors, etc. shall be clearly stated as such and the source shall be cited. Boundary conditions, loads, initial conditions, assumptions, and any other precursory information germane to an analysis shall be thoroughly explained along with their rationale in all reports. Properties used as inputs for calculations (material strengths, fastener strengths, etc.) shall be clearly presented. (A003, DI-MISC-80508B)

4.4.2. CONTRACTOR SERVICES

The Contractor shall work with the Government to analyze and develop corrective actions and tools for the Aging Aircraft Sustainment effort.

4.5 INSPECTION OF SERVICES:

4.5.1 The Contractor shall provide and maintain an inspection system acceptable to the Government covering the services under this contract. Complete records of all inspection

FD2060-13-30267 PWS PREPARED BY: AFLCMC/WIUE/ 18

work performed by the Contractor shall be maintained and made available to the Government during contract performance and for as long afterwards as the contract requires.

4.5.2 The Government has the right to inspect and test all services called for by the contract, to the extent practicable al all places and times during the term of the contract. The Government shall perform inspections and tests in a manner that will not unduly delay the work.

4.5.3 If any of the services performed do not conform to contract requirements, the Government may require the Contractor to perform the services again in conformity with contract requirements, for no additional fee. When the defects in services cannot be corrected by re-performance, the Government may –

4.5.3.1 Require the Contractor to take necessary action to ensure that future performance conforms to contract requirements; and

4.5.3.2 Reduce any fee payable under the contract to reflect the reduced value of the…