RFP_Atch_1-PWS 1 .pdf

WLSEPOC: Thomas Carlton PWS: 14-WLSE-24 WLSA POC: James Jamerson Revision: 0.0 WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 1 of 31

Performance-based Work Statement (PWS)

For

C-5 Engineering Requirements Review (ERR) Support

22 April 2015

1.0 Description of Services

1.1 Objectives

The overall objective of the C-5 ERR Support program is the sustainment of a maintenance program in support of the overall C-5 scheduled maintenance goals consistent with Maintenance Steering Group -3 (MSG-3) philosophy and the Logistics Requirement Development Processes (LRDP). This effort will provide engineering services and integrated solutions for C-5 ERR goals.

The foundational elements of the C-5 ERR Support program include: ERR engineering support, associated ERR database sustainment, maintenance data analysis and Standard Visual Work Card (SVWC) sustainment. These sustaining engineering services shall provide the C-5 organization with engineering and analysis solutions that improve the sustainment of the aircraft.

Together these services shall support fleet-wide reliability and availability requirements.

ERR support shall include input for the implementation and sustainment of processes, procedures, data analysis, and software tools for C-5 aircraft sustainment and reliability improvement. This support involves continuously analyzing Aircraft Integrated Data Environment (AIDE) data requirements, providing support of existing applications, updating all supporting documentation, conducting application testing to ensure optimal performance, and maintaining Certification and Accreditation (C&A) and compliance with the Enterprise Information Technology Data Repository (EITDR). These activities shall be integrated into a web-enabled Integrated Data Environment (IDE) to streamline the complex logistics challenges of supporting fleet readiness.

The sustainment of SVWCs shall facilitate documenting scheduled maintenance and other tasks using modern commercial best practice format and content to maximize maintainer on-aircraft time. These cards shall delineate task purpose, safety-related cautions and warnings, required parts, technical data and tools. To clarify and speed task accomplishment, the SVWCs shall extensively incorporate photographs and graphic illustrations while minimizing external Technical Order (TO) library references. Each scheduled maintenance task associated with each work card shall be maintained and updated throughout the ERR process.

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 2 of 31

The SVWCs shall be grouped into technical manuals for each scheduled maintenance interval.

The task data and SCWVs are used in support of a scheduled maintenance program that is aircraft tail number specific. These groups are sent to the Central Technical Order Repository (CTOR) where the users access the data as technical manuals for use during each scheduled maintenance visit.

1.2 Background

The United States Air Force (USAF) has developed a standard process to define maintenance requirements and support their execution. This method is called LRDP.

C-5 Engineering is responsible for successful implementation of the Engineering Requirements Review Process (ERRP) as defined by LRDP and for providing engineering support to other groups that help implement LRDP requirements. The C-5 ERR Support program is comprised of disciplined processes and procedures, organizational, and systematic operating elements designed to improve aircraft repair productivity, with the overall goal of increasing aircraft mission capability, reliability and maintainability. The program includes LRDP processes that streamline the industrial and maintenance support practices for aircraft repair, provide improved visibility of recurring repair issues for specific tail numbers in the C-5 fleet, identify solutions to correct aircraft deficiencies, provide accurate forecasting of maintenance, provide support for on-going LRDP required task reviews and establish accurate performance metrics for quality, schedule and cost. This effort will provide engineering services and integrated solutions for C-5 ERR goals.

MSG-3 is the commercial maintenance program standard approved by the Federal Aviation Administration (FAA). The USAF has chosen MSG-3 as the baseline for C-5 maintenance requirements development. The FAA directives governing the use of MSG-3 are the Continuing Analysis and Surveillance System (CASS) and Continuing Analysis Maintenance Program (CAMP) regulations which provide a continuous, structured analysis and surveillance process that monitors fleet health, evaluates the effectiveness of the scheduled maintenance program, and identifies necessary changes. LRDP adds to this by requiring on-going reviews of all maintenance tasks to ensure each task remains relevant and effective. The C-5 Program Office will review all scheduled maintenance tasks at an annual rate of 12.5% which coincides with the 8 year C-5 Programmed Depot Maintenance (PDM) cycle.

The ERRP and the Maintenance Requirements Supportability Process (MRSP) are the ways in which the USAF implements LRDP. There are several different groups that help facilitate implementation of LRDP:

• ERRP – Responsible for developing maintenance requirements, justifying their existence, and ensuring a plan for requirements supportability exists

• MRSP-Strategic (MRSP-S) – Responsible for ensuring maintenance requirements are supportable for the fleet greater than 18 months prior to aircraft induction

• MRSP-Operational (MRSP-O) – Responsible for ensuring maintenance requirements are supportable for specific tail numbers more than one month, but less than 18 months prior to induction

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 3 of 31

• MRSP-Tactical (MRSP-T) – Responsible for ensuring maintenance requirements are supportable one month prior to induction until the aircraft has completed PDM

1.3 Experience

Successful accomplishment of the objectives/tasks of this PWS will require knowledge and understanding of systems, programs and architectures related to the following areas:

• Project Management

• Information Technology (IT) and Networking compliant with DoD 8570

• Web Design, Testing, and Sustainment

• Database Design

• Configuration Management

• Centralized Work Control and Standard Daily Work

• Technical Data Quality Assurance

• Knowledge of C-5 Weapon System and Processes

• Engineering Analysis using AF Form 202, 107, G081, REMIS, ROCIT and PDMSS

• Root Cause / Reliability Analysis

• Maintenance Data Collection and Correction

• Data Cleansing Techniques

• Standard Visual Work Cards for Scheduled Maintenance

• Systems Safety Analysis per Military Standard (MIL-STD)-882D, Standard Practice for

System Safety

• CBM and CBM+

• MSG-3 Maintenance Program Capabilities on aged military and commercial aircraft

• Commercial-based aircraft maintenance work cards and Serna authoring software

• Technical Order development complying with USAF regulations

• Developing technical data using Air Transport Association of America (ATA) standard conventions

• Authoring S1000D compliant technical data

• TechSight/X technical data software suite

• Maintenance and logistics expertise with military strategic airlift or similar commercial aircraft

• Enterprise Information Technology Data Repository (EITDR)

• C&A packages and processes using USAF applications

1.4 Benefit to the United States Air Force (USAF)

The benefit of this support service to the USAF is realized in the cost and schedule savings derived from successfully implementing ERRP, LRDP and MRSP.

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 4 of 31

2.0 Services Summary

Performance Objective PWS Reference

Performance Threshold

Stage 1 First Level Approval of Existing Task Reviews: Schedule and Quality

4.2.2, 4.2.3 The Contractor shall ensure at least 90% of the submissions within AIDE for ERRP Stage 1 First Level Approval are completed on time in accordance with the Government approved Work Management Plan (WMP). This metric shall apply semiannually on a per task order basis to include the midpoint and end of the period of performance (PoP). The Contractor shall ensure that no more than one ERRP Stage 1 First Level Approval submission is rejected per 6 month period by the Engineering Supervisor resulting from Contractor errors or omissions.

Task Reviews - SVWC Technical Update Status:

Schedule and Quality

4.2.2, 4.2.3 The Contractor shall ensure at least 90% of the technical data changes to SVWC(s) associated with each maintenance task review are completed on time and in “Released” status in TechSight/X in accordance with the Government approved WMP. This metric shall apply semiannually on a per task order basis to include the midpoint and end of the PoP. The Contractor shall ensure that no more than five revisions resulting from Contractor errors or omissions are required for the SVWC technical data packages that are in the TechSight/X “Released” status per 6 month period.

Stage 1 First Level Approval of New Tasks:

Schedule and Quality

4.2.4 The Contractor shall ensure at least 90% of the

submissions within AIDE for ERRP Stage 1 First Level Approval are completed on time in accordance with the Government approved WMP. This metric shall apply semiannually on a per task order basis to include the midpoint and end of the PoP. The Contractor shall ensure that no more than one ERRP Stage 1 First Level Approval submission is rejected per 6 month period by the Engineering Supervisor resulting from Contractor errors or omissions.

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 5 of 31

New Task Creation - SVWC Technical Update Status: Schedule and Quality

4.2.4 The Contractor shall ensure at least 90% of the

technical data changes to SVWC(s) associated with each maintenance task created are completed on time and in “Released” status in TechSight/X in accordance with the Government approved WMP. This metric shall apply semiannually on a per task order basis to include the midpoint and end of the PoP. The Contractor shall ensure that no more than five revisions resulting from Contractor errors or omissions are required for the SVWC technical data packages that are in the TechSight/X “Released” status per 6 month period.

Condition-Based Maintenance (CBM) Process: Schedule and Quality

4.2.5 The Contractor shall ensure the SVWC updates

are completed and in “Released” status in TechSight/X at least 60 calendar days before the aircraft arrives at the RISO 90% of the time.

The remaining 10% shall be completed and in “Released” status at least 53 calendar days before the aircraft arrives at the RISO. This metric shall apply semiannually on a per task order basis to include the midpoint and end of the PoP. The Contractor shall ensure that no more than five revisions on SVWC(s) technical data modules in the “Released” status occur per 6 month period resulting from Contractor errors or omissions.

Engineering Studies and Analysis Final Technical Report: Quality

4.2.6 The Contractor’s final conclusions and analysis

shall be submitted and accepted by the Government with no more than one revision per submission.

Work Card Sustainment 4.2.7.9 The Contractor shall ensure that no more than five revisions on SVWC(s) or data modules in the “Released” status occur per 6 month period resulting from Contractor errors or omissions.

System availability 4.2.8.2 Contractor shall ensure downtime attributed to software failures for any IDE application does not exceed one business day per any 30 calendar day period.

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 6 of 31

EITDR update 4.2.8.2.7 Contractor shall register and maintain all developed software in EITDR. Contractor shall update EITDR to reflect any upgrades or changes in application functionality within three business days of completion of each project. Contractor shall provide registration documentation to Government on registered systems in EITDR upon request.

Software application compliance with C&A

4.2.8.2.7 Contractor shall ensure all software applications

remain compliant with C&A guidelines 100% of the time.

Maintenance of Authority to Connect (ATC) and Authority to Operate

(ATO)

4.2.8.2.7 Contractor shall ensure ATC/ATO is

maintained with no lapse in authority.

3.0 Government Property and Services

3.1 Contractor Responsibility

The Contractor shall be responsible for Government property in their possession in accordance with the Federal Acquisition Regulation (FAR) and applicable supplements including, but not limited to, FAR Part 45, Government Property; FAR 52.245-1, Government Property; and Defense Federal Acquisition Regulation Supplement (DFARS) Part 245, Government Property.

The FAR and applicable supplements can be accessed at the site below.

http://farsite.hill.af.mil

3.1.1 Federal Acquisition Regulation (FAR) 45.101, Government Property / Definitions

The term “Government property” means all property owned or leased to the Government. It includes both Government-furnished property and contractor-acquired property. “Contractor-acquired property” means property acquired or otherwise provided by the Contractor for performing a contract and to which the Government has title.

3.2 Government Property to Be Provided

Government property will be provided as follows:

3.2.1 Base Support: the Government will provide access to work-card software (e.g., TechSight/X and Serna), legacy data systems, facilities, key personnel, computers and monitors, printers, copy machines, shredders, fax machines, required office space, supplies/equipment, manuals, and regulations, comparable to that provided Government employees for the http://farsite.hill.af.mil/

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 7 of 31 accomplishment of the objectives/tasks on Robins Air Force Base (RAFB). Additionally, the Government will provide Class A phone lines.

3.2.2 The Government will provide access to aircraft, as required, in order for the Contractor to perform analysis. Aircraft will be made available based on fleet requirements and with the approval of Air Mobility Command (AMC), Air Force Reserve Command (AFRC), and 402nd Maintenance Wing (402 MXW).

3.3 Loss of Government Property

3.3.1 Definition of the Loss of Government Property

Definition of Loss of Government Property: In accordance with DFARS 252.245-7002, Reporting 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, theft, loss due to lack of security, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.3.2 Reporting the Loss of Government Property

In accordance with DFARS 252.245-7002, the Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application to report loss of Government property at the site below. The reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract/order.

http://www.dcma.mil/aboutetools.cfm

3.4 Return of Government Property

All property provided by the Government remains the property of the Government and shall be returned to the Government upon completion of the contract/order. All Government property shall be returned to the Government in the condition provided unless approved in advance by the Procuring Contracting Officer (PCO). All material generated under the contract/order becomes the property of the Government and shall be returned to the Government upon completion of the contract/order. All Department of Defense (DoD) Form 1423, Contract Data Requirements List (CDRL), deliverables become the property of the Government upon receipt.

http://www.dcma.mil/aboutetools.cfm

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 8 of 31

3.5 Government Systems

The Government will provide access to components/systems, as required, in order for the Contractor to perform analysis. Components/systems will be made available based on fleet requirements and with the approval of the responsible organization at Warner Robins-Air Logistics Complex (WR-ALC), Ogden Air Logistic Complex (OO-ALC), Oklahoma City Air Logistic Complex (OC-ALC) and any other Government agency.

3.5.1 Government Information Systems Access and Data

The Government will provide Contractor personnel access to systems required to perform tasks under the contract. The Government will provide system access subject to approval of the Department of Defense (DD) Form 2875, System Authorization Access Request (SAAR). Upon completion/termination of the contract or transfer/termination of Contractor personnel, applicable system accounts will be closed.

The Government will provide access to Government data systems and data archived by the C-5 organization. The Contractor can obtain Point of Contact (POC) information, for any system listed below, from the COR. The Contractor shall collect and collate data from the following systems and other systems as necessary:

• G081 (Core Automated Maintenance System for Transport Aircraft)

• REMIS (Reliability & Maintainability Information System)

• GCSS (Global Combat Support System)

• PDMSS (Programmed Depot Maintenance Schedule System)

• EDW (Enterprise Data Warehouse) / (AFDS) Air Force Data Services as available

• G021 (Quality Deficiency Reports Repository)

• ROCIT (Role Oriented Consolidation Information Tool)

• PDMSS (Programmed Depot Maintenance Scheduling System)

• TechSight/X and Serna technical data software

• EIDTR (Enterprise Information Technology Data Repository)

• AIDE (Aircraft Integrated Data Environment)

• AFDS (Air Force Data Services)

• MIMS (Mission Impaired Capability Awaiting Parts (MICAP) Information Management

System)

• C-5 Programmed Depot Maintenance (PDM) Non-Destructive Inspection (NDI)

Database

• 202 Database (PDM Initiated Engineering Assistance Request)

• 107 Database (Field Initiated Engineering Assistance Request)

• 339 Database (Defense Logistics Agency (DLA) Initiated Engineering Assistance

Request)

• PDM CANN (Cannibalization) Database

• Wholesale and Retail Supply Systems

• MADARS (Malfunction Detection, Analysis and Recording System)

• Aircraft Health Management System (AHMS)

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 9 of 31

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance

The period of performance for the contract will extend 60 months with one 12 month basic ordering period and four 12 month optional ordering periods. .

4.1.2 Place of Performance

These services will be performed at RAFB and at the Contractor’s facility.

4.2 Engineering Requirements Review (ERR) Support

4.2.1 ERR Regulation Compliance

When accomplishing tasks related to this program, the Contractor shall ensure compliance with the following guidance:

• WLS Operating Instruction (OI) 62-101, C-5 ERR Process

• C-5 MRSP-S Process Guide 03August2012

• C-5 MRSP-O Process Guide 23August2013

• 402 AMXG Tactical Process Guide 17May2013

• WLS OI 62-201, C-5 MSG-3 Policy and Procedure

• AFMCI 90-205, Logistics Requirements Determination Process

4.2.2 Review of Existing Maintenance Tasks

The Contractor shall accomplish annual task reviews on 12.5% of 3,000 scheduled maintenance tasks to ensure all tasks remain relevant and effective. The reviews shall be accomplished in accordance with the LRDP Handbook and the AFLCMC WLS Operating Instruction (OI) 62-

101. The Contractor shall utilize the maintenance task prioritization list, which is automatically generated within AIDE, shall utilize the task prioritization process outlined in AFLCMC WLS OI 62-101; shall considering bundling of tasks for efficiencies and shall also coordinate with the Government to establish which specific pre-existing maintenance tasks shall be reviewed by the Contractor during each period of performance. Within 30 calendar days of each order award date, the Contractor shall submit a Work Management Plan (WMP) in accordance with paragraph 4.3.1.3.

Submissions for Stage 1 First Level Approval

In developing the delivery schedule for the WMP, the Contractor shall ensure that all submissions within AIDE for ERRP Stage 1 First Level Approval occur no later than 300 calendar days after the order award date. Furthermore, in order to allow the Government sufficient time to assess each maintenance task review submitted within the period of performance, the Contractor shall plan within the WMP, to the extent feasible, a monthly

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 10 of 31 submission rate for ERRP Stage 1 First Level Approval of approximately 11% of total number of tasks being reviewed, excluding the 30 calendar days of the order period of performance and excluding the last 60 calendar days of the order period of performance. The 11% submission rate is an approximate guide to ensure a steady month to month tempo of review submissions. The Government understands that the submission rate for ERRP Stage 1 First Level Approval is dependent on the complexity of the tasks being reviewed and understands there may be variations from the 11% guide. The Contractor shall ensure at least 90% of the submissions within AIDE for ERRP Stage 1 First Level Approval are completed on time in accordance with the Government approved WMP. This metric shall apply semiannually on a per task order basis to include the midpoint and end of the PoP. The Contractor shall ensure that no more than one ERRP Stage 1 First Level Approval submission is rejected per 6 month period by the Engineering Supervisor resulting from Contractor errors or omissions.

SVWC Status

In developing the delivery schedule for the WMP, the Contractor shall plan, to the extent possible, that the technical data changes to SVWC(s) resulting from each maintenance task review, are accomplished and are in “Released” status in TechSight/X within 60 calendar days of ERRP Stage 1 First Level Approval and, not withstanding, the “Released” status shall be achieved no later than 15 calendar days prior to the end of the order period of performance. The 60 calendar day time frame is an approximate guide to ensure a steady month to month tempo.

The Government understands that the number of days in which the “Released” status is achieved by the Contractor is dependent on the complexity of the tasks being reviewed and understands there may be variations. The Contractor shall ensure at least 90% of the technical data changes to SVWC(s) associated with each maintenance task review are completed on time and in “Released” status in TechSight/X in accordance with the Government approved WMP. This metric shall apply semiannually on a per task order basis to include the midpoint and end of the PoP. The Contractor shall ensure that no more than five revisions resulting from Contractor errors or omissions are required for the SVWC technical data packages that are in the TechSight/X “Released” status per 6 month period.

(CDRL A007, DI-MGMT-81911/T, Work Management Plan, CDRL C001, DI-MISC- 80711A/T, Scientific and Technical Reports)

4.2.3 Additional Reviews of Existing Maintenance Tasks

Per the policy stated in LRDP Handbook, the goal is for the C-5 Program Office to complete reviews on 20% of the existing scheduled maintenance tasks on an annual basis. Task orders for up to an additional 7.5% reviews of the approximately 3,000 existing scheduled maintenance tasks may be awarded on an annual basis. If task orders are awarded for additional reviews, the Contractor shall accomplish additional reviews in accordance with section 4.2.2 of this PWS excluding the first sentence of PWS section 4.2.2.

(CDRL A007, DI-MGMT-81911/T, Work Management Plan, CDRL C001, DI-MISC- 80711A/T, Scientific and Technical Reports)

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 11 of 31

4.2.4 Creation of New Maintenance Tasks

Task orders for the creation of new maintenance tasks may be awarded on an as needed basis to support the objectives of this PWS. Specific requirements for each task order will be provided by the Government PCO to the Contractor in a sub-PWS. The PCO will submit a request for proposal along with the corresponding sub-PWS to the Contractor. Each task order will be negotiated separately. The Contractor shall accomplish the creation of new maintenance tasks ensuring the new tasks are relevant and effective. The creation of new tasks shall be accomplished in accordance with the LRDP Handbook and the AFLCMC WLS Operating Instruction (OI) 62-101. Within 30 calendar days of each order award date, the Contractor shall submit a Work Management Plan (WMP) in accordance with paragraph 4.3.1.3.

Submissions for Stage 1 First Level Approval

In developing the delivery schedule for the WMP, the Contractor shall ensure that all submissions within AIDE for ERRP Stage 1 First Level Approval occur no later than 60 calendar days prior to the task order end date. Furthermore, in order to allow the Government sufficient time to assess each maintenance task created within the period of performance, the Contractor shall plan within the WMP, to the extent feasible, a monthly submission rate for ERRP Stage 1 First Level Approval to ensure a steady month to month tempo of submissions. The Government understands that the submission rate for ERRP Stage 1 First Level Approval is dependent on the complexity of the tasks being created. The Contractor shall ensure at least 90% of the submissions within AIDE for ERRP Stage 1 First Level Approval are completed on time in accordance with the Government approved WMP. This metric shall apply semiannually on a per task order basis to include the midpoint and end of the PoP. The Contractor shall ensure that no more than one ERRP Stage 1 First Level Approval submission is rejected per 6 month period by the Engineering Supervisor resulting from Contractor errors or omissions.

SVWC Status

In developing the delivery schedule for the WMP, the Contractor shall plan, to the extent possible, that the technical data changes to SVWC(s) or creation of new SVWC resulting from each maintenance task created, are accomplished and are in “Released” status in TechSight/X within 60 calendar days of ERRP Stage 1 First Level Approval and, not withstanding, the “Released” status shall be achieved no later than 15 calendar days prior to the end of the order period of performance. The 60 calendar day time frame is an approximate guide to ensure a steady month to month tempo. The Government understands that the number of days in which the “Released” status is achieved by the Contractor is dependent on the complexity of the tasks being created and understands there may be variations. The Contractor shall ensure at least 90% of the technical data changes to SVWC(s) associated with each maintenance task created are completed on time and in “Released” status in TechSight/X in accordance with the Government approved WMP. This metric shall apply semiannually on a per task order basis to include the midpoint and end of the PoP. The Contractor shall ensure that no more than five revisions resulting from Contractor errors or omissions are required for the SVWC technical data packages that are in the TechSight/X “Released” status per 6 month period.

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 12 of 31

(CDRL A007, DI-MGMT-81911/T, Work Management Plan, CDRL C001, DI-MISC- 80711A/T, Scientific and Technical Reports)

4.2.5 Conditioned-Based Maintenance (CBM) Tailoring of Scheduled Maintenance Tasks

Task orders for tail number specific CBM tailoring of the fleetwide scheduled maintenance task packages may be awarded on an as needed basis to support the objectives of this PWS. Specific requirements for each task order will be provided by the Government PCO to the Contractor in a sub-PWS. The PCO will submit a request for proposal along with the corresponding sub-PWS to the Contractor. Each task order will be negotiated separately.

The Contractor shall update the SVWCs per the tail number specific tailoring generated by the Government in AIDE for Regional Isochronal (RISO) maintenance. The Contractor shall complete the SVWC updates within AIDE at least 60 calendar days before the aircraft arrives at the RISO for scheduled maintenance. The Contractor shall ensure the SVWC updates are completed and in “Released” status in TechSight/X at least 60 calendar days before the aircraft arrives at the RISO 90% of the time. The remaining 10% shall be completed and in “Released” status at least 53 calendar days before the aircraft arrives at the RISO. This metric shall apply semiannually on a per task order basis to include the midpoint and end of the PoP. The Contractor shall ensure that no more than five revisions on SVWC(s) technical data modules in the “Released” status occur per 6 month period resulting from Contractor errors or omissions.

(CDRL C001, DI-MISC-80711A/T, Scientific and Technical Reports)

4.2.6 Engineering Studies and Analysis

Task orders for engineering studies and analysis may be awarded on an as needed basis to support the objectives of this PWS. Specific requirements for each task order will be provided by the Government PCO to the Contractor in a sub-PWS. The sub-PWSs will primarily support sections 4.2.7.2 Product Improvement Analysis, 4.2.7.3 Maintenance Data Analysis, 4.2.7.6 Aircraft Availability and Supplier Support, and 4.2.7.7 ERR Organization and Communication.

The PCO will submit a request for proposal along with the corresponding sub-PWS to the Contractor. Each task order will be negotiated separately. The Contractor’s final conclusions and analysis shall be submitted and accepted by the Government with no more than one revision per submission.

(CDRL C002, DI-MISC-80711A/T, Scientific and Technical Reports)

4.2.7 Existing and New Maintenance Review Tasks

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 13 of 31

In performance of the review of existing maintenance tasks and creation of new maintenance tasks in PWS sections 4.2.2, 4.2.3, 4.2.4 and 4.2.5, the Contractor shall perform the tasks in this PWS section 4.2.7.

4.2.7.1 ERR Support Tasks

As part of the ERR Program, the Contractor shall:

1) Ensure maintenance tasks are accomplishing their primary intent and the assigned maintenance interval is appropriate through analysis of maintenance data and associated task tracking numbers;

2) Make the appropriate updates or revisions to the Scheduled Maintenance Program Database (SMPDB) within AIDE and the resulting changes as applicable to the tasks in TechSight/X as tasks are revised;

3) Incorporate scheduled maintenance tasks from outside sources into the C-5 scheduled maintenance program as required due to updates and modification to the aircraft configuration;

4) Assemble business cases and conduct technical analysis for proposed maintenance program changes, proposed revisions to existing maintenance tasks or proposed new maintenance tasks, or Government proposed new maintenance tasks;

5) Accomplish tasks in accordance with Logistics Requirement Determination Process (LRDP), Chapter 13, Engineering Requirements Review;

6) Ensure expeditious processing of TO changes.

The Contractor shall identify problems and/or deficiencies that require configuration or procedural changes and evaluate performance improvements to ensure the functional systems meet operational requirements. The Contractor shall perform activities including, but not limited to, analysis of aircraft systems to establish weapon system baselines, functional and physical configuration audits, analysis and support of Air Force Instruction (AFI) 63-101, Life Cycle Systems Engineering. The Contractor shall maintain OSS&E requirements while performing analysis. All engineering analysis affecting OSS&E shall be accomplished by appropriately accredited personnel in possession of Accreditation Board for Engineering and Technology (ABET) accredited degrees, state issued Engineering-in-Training certifications and/or state issued Professional Engineer licenses.

(CDRL C001, DI-MISC-80711A/T, Scientific and Technical Reports)

4.2.7.2 Product Improvement Analysis

The Contractor shall perform preliminary and in-depth engineering analysis for all Work Unit Codes (WUCs) that are identified as poor performers in order to determine the need for product improvements and recommend further engineering analysis and resolutions that can be implemented for fleet-wide sustainment and/or be implemented as part of the C-5 scheduled maintenance program.

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 14 of 31

4.2.7.3 Maintenance Data Analysis

The Contractor shall identify, collect, and analyze C-5 diagnostic, reliability and maintainability data, engineering disposition data, and deficiency reporting data from various sources with the goal of improving mission capability of the fleet. The Contractor shall perform these engineering activities in accordance with Failure Mode, Effects and Criticality Analysis (FMECA) requirements per Society of Automotive Engineers (SAE) Aerospace Information Report 4845 (SAE AIR4845) and system safety and hazard analysis per MIL-STD-882D.

4.2.7.4 PDM Bill of Materials (BOM) Update

As identitied through review or creation of maintenance tasks, As required, the Contractor shall update or create the Bill of Materials (BOM) to support the maintenance program implementation.

4.2.7.5 Integration with Maintenance Requirements Review Board (MRRB) The Contractor shall integrate and update the maintenance-derived tasks and maintenance interval recommendations within AIDE which the Government will utilized for incorporation into the MRRB Brochure/Work Spec. The Contractor shall provide technical data necessary to facilitate transition and incorporate the maintenance program into the MRRB Brochure/Work Spec.

4.2.7.6 Aircraft Availability and Supplier Support

The Contractor shall analyze C-5 parts support provided by various suppliers. Suppliers include all Air Force Sustainment Center (AFSC) Sources of Supply (SOS) locations, the applicable DLA Support Centers, as well as, major modification program prime contractors. The Contractor shall identify parts supportability issues affecting or that will be affecting maintenance tasks. The Contractor shall determine whether new requirements part lists are supportable or when they are predicted to be supportable. The Contractor shall provide findings for each maintenance task reviewed or created.

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 15 of 31

4.2.7.7 ERR Organization and Communication

The implementation and sustainment of an ERR Program requires extensive communication channels to be in place, as well as flexible processes and infrastructures to support the various stages of current maintenance data analysis and reviews (of Structural Significant Items (SSI), Other Structural Items (OSI), Maintenance Significant Items (MSI) and Zonal tasks as they relate to both structures and systems analysis consistent with MSG-3 philosophy). The Contractor shall support the C-5 ERR by investigating reliability deficiencies that are identified throughout the fleet. The Contractor shall maintain Operational Safety, Suitability and Effectiveness (OSS&E) in accordance with Air Force Materiel Command (AFMC) AFLCMC/WLS requirements while performing analysis. The Contractor shall implement a robust reliability program for the C-5 aircraft by utilizing appropriate tools and processes to improve overall fleet reliability, implementing best practices from the commercial aviation industry, and using current DoD guidelines and industry philosophies to implement and sustain scheduled maintenance process solutions for the fleet. The Contractor shall maintain membership with Airlines for America (A4A), formerly known as Air Transport Association of America (ATA) in order to ensure timely updates to the MSG-3 logic flow.

4.2.7.8 Configuration Management

The Contractor shall perform and maintain configuration management per DoD 5000.2-R Mandatory Procedures for Major Defense Acquisition Programs (MDAPS) and Major Automated Information System (MAIS) Acquisition Programs; AFI 63-101/20-10 Integrated Life Cycle Management; AFMCI 63-1201 Implementing Operational Safety, Suitability, & Effectiveness (OSS&E) and Life Cycle Systems Engineering; RAFBI 63-104 Configuration Management; and Galaxy Division OI 63-01 Configuration Management via Configuration Control Board. The Contractor shall perform activities including, but not limited to, analysis of aircraft systems to establish weapon system baselines, functional and physical configuration audits, analysis and support of the government Configuration Control Board (CCB).

4.2.7.9 Work Card Sustainment

The Contractor shall deploy and sustain 1C-5A-6WC/1C-5M-6WC SVWCs using commercial concepts and best practices including the use of graphics and specific job instructions. There are approximately 3000 SVWCs making up these technical manuals. The SVWCs shall comply with the general technical data manual requirements of MIL-STD-38784 in an 8.5” X 11” page format. All TO references contained within SVWCs shall be recorded as a part of the scheduled maintenance task data in TechSight/X so that future TO updates and revisions can be incorporated into the work cards. When a revision is accomplished to a SVWC or data module during the sustainment process and the revision is complete, the Contractor shall place the

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 16 of 31

SVWC/data module in the “Released” status in TechSight/X. The Contractor shall ensure that no more than five revisions on SVWC(s) or data modules into the “Released” status occur per 6 month period resulting from Contractor errors or omissions. Sustainment of the SVWCs shall consist of the following:

1) Revise SVWCs data modules residing in TechSight/X to comply with TO revisions as shown on Air Force Technical Order (AFTO) 252 forms completed by the equipment specialist owning the source data. On average, the TO revisions as shown on AFTO 252 forms result in the need to perform approximately 96 SVWC revisions per month;

2) Keep the xsl style sheets and xsd schemas in TechSight/X updated to meet required updates to the style and format of the technical manual and the SVWC;

3) Use circuit breaker data on tasks to populate auto generated tables on the SVWC;

4) Keep parts and tooling data on SVWC current with updates to ERR and technical manual updates;

5) Create and maintain existing S1000D data modules that contain data reused on multiple

SVWCs;

6) Accomplish other tasks within the scope of this requirement as concurred by COR and authorized by the PCO.

4.2.8 IDE

In performance of the annual task orders for PWS section 4.2.2 Review of Existing Maintenance Tasks, the Contractor shall also perform the requirements in this PWS section 4.2.8. The Contractor shall deliver all software license(s), toolset(s), associated documentation, source code, test scripts and executable images generated under PWS sections 4.2.8.1 through 4.2.8.3.7. The Contractor shall deliver a software transistion plan.

(CDRL C003, DI-MCCR-80700/T, Computer Software Product End Items) (CDRL C004, DI-IPSC-81488/T, Computer Software Product) (CDRL C005, DI-IPSC-81429/T, Software Transition Plan (STRP))

4.2.8.1 Condition-Based Maintenance (CBM) Process

The Contractor shall maintain and update the database within AIDE to facilitate aircraft specific CBM actions to be accomplished by the use of SVWCs. The Contractor shall ensure that the database updates incorporate relevant revision to the LRDP Handbook, to AFLCMC WLS OI 62-101 and to WLS ERR policy and procedures. The Contractor shall ensure that the database provides the Government engineer ability to tailor the fleet maintenance requirements package for each tail number. The database shall provide: (1) The relationship between each Regional Isochronal (RISO)/PDM visit and the version of the SVWCs used during that visit; (2) The relationship between a specific scheduled maintenance task, in the published technical manual, and the specific RISO/PDM visit the task was accomplished; (3) The capability for reporting

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 17 of 31 date of compliance on a specific scheduled maintenance task being accomplished during RISO or PDM; (4) The capability to import and display compliance of time, cycle, operation or condition limited requirements of the scheduled maintenance program from the appropriate maintenance data collection system by aircraft or item serial number. The Contractor shall ensure the processes and tools within AIDE provide the ability to accurately generate tail number-specific maintenance tasks at least 60 calendar days before the aircraft arrives at the RISO for scheduled maintenance.

4.2.8.2 IDE Sustainment

For customer disruptions due to software failures, system downtime attributed to software failures or any IDE application shall not exceed one business day per any 30 calendar day period.

For customer support, the Contractor shall respond to submitted customer requests within three business days of requirement notification. For EITDR registration, the Contractor shall provide registration documentation to the Government on registered systems in the EITDR within three business days of completion of each registration. For C&A compliance, the Contractor shall comply with USAF and WR-ALC mandate regarding connectivity of systems and applications to network 100% of the time. Certification for 8570-M Information Assurance Management -3 (IAM - 3)/Information Assurance Technical -3 (IAT -3) Certified Information Systems Security Professional (CISSP) is required. The Contractor shall ensure downtime attributed to software failures for any IDE application does not exceed one business day per any 30 calendar day period.

(CDRL C001, DI-MISC-80711A/T, Scientific and Technical Reports)

4.2.8.2.1 Data Requirements Analysis

The Contractor shall enhance, update, and sustain the C-5 maintenance database that contains all Inspection and Maintenance (I&M) requirements for structures, systems and zonal applicability across all C-5 inspection zones, consistent with MSG-3 philosophy. The Contractor shall ensure that the data requirement updates incorporate relevant revision to the LRDP Handbook, to AFLCMC WLS OI 62-101 and relevant revisons to WLS ERR policy and procedures. The C-5 Maintenance Database shall be used throughout the life of the contract to update maintenance tasks and provide decision support data for each requirement including Force Structural Maintenance Program (FSMP) references, maintenance failure statistics, reliability data, maintainability factors and economic factors. Database fields shall include SVWC data, as well as, current approved interval, Failure Effect Category (FEC), recommended threshold intervals for each applicable FEC and decision support data references. Project details in terms of technical risk, cost, and schedule shall be provided and reviewed during Technical Interchange Meetings (TIMs) to determine whether any priority changes/modifications/additions may be required to meet war fighter needs.

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 18 of 31

4.2.8.2.2 Support of Existing Applications

Maximum care shall be taken to avoid duplication of effort in support and deployment of applications to the IDE through the use of state-of-the-art Information Technology (IT) techniques and tool sets. The Contractor shall ensure all systems modified or upgraded under the contract, are entered into the EITDR. The Contractor shall provide documentation, on registered systems in the EITDR, to the Government within three business days of completion of each project. The Contractor shall provide timely support of and maintenance of all applications listed in Table 1 below. These applications may be modified to provide additional capability based upon customer feedback or receipt of additional requirements. The Contractor shall procure and maintain the current software annual maintenance licenses for TechSight/X at the current minimum level of 50 users for use on Government computers. The Contractor shall procure and maintain the current software annual editor maintenance licenses for Serna at the current minimum level of 25 users for use on Government computers.

Table 1- Existing C-5 Applications

Program Name Purpose Aircraft Integrated Data Environment (AIDE) Framework

Application framework to support C-5 applications

Form 107 C-5 Form 107 System

C-5 MICAP

Information Management System

(MIMS)

C-5 Mission Impaired Capability Awaiting Parts (MICAP) Information Management System

TechSight/X C-5 Standard Visual Work Card (SVWC) Authoring System

Condition Based Maintenance Program

(CBMP)

Provides a method to track the SVWCs that are delivered for use on individual aircraft tail numbers

4.2.8.2.3 Application Requirements and Analysis

The Contractor shall perform requirements analysis to gather the system-level requirements for each system integration project assigned by the customer. The analysis should be accomplished through customer feedback or other methods of communication. The system-level requirements shall be captured in the System Requirements Specification (SRS).

4.2.8.2.4 System Design

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 19 of 31

Based upon analysis, the Contractor shall identify changes required in design methodology to the customer to ensure the design complies with and fulfills the requirement.

4.2.8.2.5 Supporting Documentation

All required upgrades shall be appropriately documented and maintained within the program.

Documentation shall be supplied to the customer upon request. A baseline version of the application shall be maintained for configuration management purposes.

4.2.8.2.6 Application Testing

The Contractor shall test the functionality of each system integration application based on criteria established in the SRS. Necessary modifications and corrections identified during verification testing shall be documented and incorporated into the system prior to proceeding to system deployment. The Contractor shall deploy applications to the web production server and database server, as applicable.

4.2.8.2.7 Application C&A and the EITDR

The Contractor shall register and maintain all developed software in the EITDR. The Contractor shall update the EITDR to reflect any upgrades or changes in application functionality within three business days of completion of each project. The Contractor shall provide registration documentation to the Government on registered systems in the EITDR upon request.

The Contractor shall ensure all software applications remain compliant with C&A guidelines 100% of the time. The Contractor shall establish supporting documentation and provide application configuration details in the support of the DoD Information Assurance (IA) C&A process and maintenance of the Authority to Connect/Authority to Operate (ATC/ATO). The Contractor shall ensure ATC/ATO is maintained with no lapse in authority. The Contractor shall comply with the USAF and WR-ALC mandate regarding connectivity of systems and applications to the network 100% of the time.

4.2.9 Integrated Master Schedule

The Contractor shall maintain an Integrated Master Schedule (IMS) which purpose is to optimize aircraft availability with respect both scheduled and unscheduled maintenance cycles and

WLSK POC: Jill Thornton Date: 22 April 2015

PR: FD2060-16-92801/REV 0 Page 20 of 31 schedules. In addition to the IMS, the Contractor shall develop, modify and implement AA action plans using maintenance historical data to achieve IMS and AA goals.

(CDRL C001, DI-MISC-80711A/T, Scientific and Technical Reports)

4.3 Other Support Tasks

4.3.1 Program Management

The Contractor shall assign a qualified Program Manager to plan and execute the tasks required for each task order. The Program Manager shall be the single point of contact to the Government. The Program Manager assigned shall:

a. Understand in detail the contractual requirements, terms and conditions of the task.

b. Assign, track progress and review performance of task on a periodic basis.

c. Review all deliverables for accuracy and completeness.

d. Hold a Kick Off Meeting (KOM) within 30 calendar days of task order award.

(CDRL A003, DI-ADMN-81249A, Conference Agenda; CDRL A006, DI-ADMN-81250A, Conference Minutes)

4.3.1.1 Status Reports

The Contractor shall submit monthly status reports for each task order. The Contractor shall provide a summary and status of work being performed during the reporting period to include funds expended; progress in relation to schedule and cost; technical progress and any issues and concerns with associated recommendations. If applicable to the task order, the Contractor shall document WMP progress in the monthly status report including documentation of any Stage 1 First Level Disapprovals. (CDRL A001, DI-MGMT-80368A/T, Status Report)

4.3.1.2 Technical Interchange Meetings (TIMs)

The Contractor shall hold and conduct requirements reviews and technical interchange meetings (TIMs), as necessary, with the Government.