J-1_EPSE_III_TO1_PWS.docx

DOCX document 33 KB Posted

Attached to
Enterprise Product Support Engineering III Federal contract opportunity
Solicitation number
ID05170030
Issued by
GSA Federal Acquisition Service

About this file

J-1 TO1 PWS

View the file

Other files for this federal contract opportunity

Other files attached to Enterprise Product Support Engineering III, newest first.
File Type Posted
EPSE_III_RFP_-_Amendment_3.docx DOCX document
Questions_and_Answers_June_5.docx DOCX document
Questions_and_Answers_June_4_-_updated.docx DOCX document
EPSE_III_RFP_-_Amendment_2.docx DOCX document
Questions_and_Answers_June_4.docx DOCX document
EPSE_III_RFP_-_Amendment_1.docx DOCX document
Questions_and_Answers_-_May_23.docx DOCX document
J-2_EPSE_III_TO1_QASP.docx DOCX document
J-4_EPSE_III_TO2_QASP.docx DOCX document
J-4_EPSE_III_TO2_QASP_attachment_-_Objective,_Measures_and_Expectations.docx DOCX document
EPSE_III_RFP.docx DOCX document
J-3_EPSE_III_TO2_PWS_(PMB_and_Lasers).docx DOCX document
J-2_EPSE_III_TO1_QASP_attachment_-_Objective,_Measures_and_Expectations.docx DOCX document
J-4_EPSE_III_TO2_QASP_attachment_(PMB_and_Lasers).xlsx XLSX spreadsheet
J-2_EPSE_III_TO1_QASP_attachment.xlsx XLSX spreadsheet
Show all 15

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Task 01

Condition-Based Maintenance Plus

Performance Work Statement

IDIQ ID05170030001

06 Apr 2018

TASK ORDER: 001

Air Force Life Cycle Management Center (AFLCMC) Product Support Engineering Division (EZP) Department of the Air Force Wright-Patterson Air Force Base (WPAFB), OH

POCs:

Program Manager (PM):

John Hedke, AFLCMC/EZP Phone: (937) 656-6873 E-mail: john.hedke@us.af.mil

Contractor Officer Representative (COR)/ Government Technical Point of Contact (TPOC):

Gregory Schwabacher, AFLCMC/EZPT Phone: (937) 656-7903 Fax: (937) 255-7791 E-mail: gregory.schwabacher.1@us.af.mil

General Services Administration (GSA) COR/PM:

Theresa Vollink Phone: (312) 279-8145 Fax: (312) 886-3827 E-mail: theresa.vollink@gsa.gov

(X) New Task( ) Renewal( ) Revision
(X) T&M( ) Fixed Price
(X) On-Site(X) Off-Site

1. BACKGROUND: Condition Based Maintenance Plus (CBM+) is a proven methodology that promotes maintenance (Mx) upon evidence of need. Such evidence can be generated from a variety of hardware, tools, systems, and algorithms that are established to identify usage patterns and related anomalies to predict and enable Mx decision-making. CBM+ is also individualized, meaning no two assets are identical, and the interest is to treat each asset based on its actual use and not as an average. In other words, CBM+ is evidence-based Mx by tail number. CBM+ requires “big data” and systems interconnectivity to achieve maximum benefit. Adoption of CBM+ requires the integration of emerging technologies, systems, and tools (modules/algorithms/formulas) plus cross-organization coordination.

CBM+ has the ability to predict when a part will fail before it actually fails driving different maintenance practices. Today, the AF utilizes time-based approaches to determine programmed depot maintenance cycles and common field-level repairs. This approach is costly and requires each weapon system to have standard work packages that drive numerous inspections and replacement tasks. CBM+ is a different way of planning Mx activities that can reduce costs, improve readiness, enhance safety, and reduce maintenance and sustainment (M&S) burdens placed on the AF. As the AF progresses towards a cost-effective engineering mindset, all operations across the AF enterprise must be considered and evaluated to reduce life cycle costs and operational burden while also increasing worker safety and weapon system readiness.

2. SCOPE OF WORK: The overall objective of this effort is to implement CBM+ within the KC-135 weapon system support activities. To execute this Task Order, both technical and managerial activities shall be required. The Contractor shall consider program management requirements, environmental and safety requirements/savings, readiness factors, return on investment benefits, and sustainment/maintenance needs. The Contractor shall provide program schedules, program objectives, and final data results, analysis, tools, and algorithms.

3. CONTRACTOR REQUIREMENTS: The overall objective of this effort is to develop and begin implementation of a comprehensive CBM+ program plan for the KC-135 weapon system. To execute this Task Order, both technical and managerial activities shall be required. The proposal shall provide details outlining the recommended program plan and approach that will be taken to implement the plan. Details on the approach, objectives accomplished, priorities, and deliverables shall be included in the proposal. The proposal shall address both a strategic and tactical approaches to the program plan. The plan shall be comprised of two main components: (1) a strategic, top-level, five-year overarching CBM+ plan for the KC-135 (including priorities and objectives) and (2) a detailed, first-year tactical plan for KC-135 CBM+ implementation that clearly identifies activities that will be completed during the first year along with specific objectives and how the objectives will be accomplished. The proposal shall identify all tools, techniques, and capabilities that will be delivered to the Air Force. The plan should address predictive maintenance and all necessary capabilities, processes, tools, and techniques required to achieve predictive maintenance within the KC-135.

The plans should leverage best practices and already existing pockets of excellence that minimize cost and risk to the AF while also accelerating implementation. Cybersecurity considerations should be included in the plan as well as leverage on-going efforts across the Air Force for data analysis and storage. The plan(s) shall include all project details, timelines for implementation; deliverables, identify areas of potential risk, and recommendations for execution.

The Contractor shall complete all aspects & components laid out within the scope in order to implement the CBM+ program on the KC-135 fleet. The Contractor shall accomplish tasks in coordination with Airworthiness Bulletin (AWB) 1015, as required. All raw and summarized data, test results, and coding shall be unrestricted and submitted electronically with final test reports, provided to the AF in Microsoft Word, Excel, and PowerPoint presentation formats. Any deviations must be approved by the government PM.

The CBM+ plan(s) should identify all components, tools, requirements, and strategic funding necessary for implementation including projected schedule. The Contractor shall identify all areas of risk and gaps within the plan and coordinate the approach and timeline with all stakeholders. The Contractor shall begin implementing program/or recommended approach after coordination and approval.

4. DELIVERABLES:

Data Item Number
PWS Section
Data Item Title
Description

Due Date (in calendar days where appropriate)

Status Report
Objectives, technical performance, cost, schedule, trips, include all sub-contractor data & reporting
Due with the monthly invoice submittal No Later Than (NLT) 10th day of the month
Funds and Man-Hour Expenditure Report
Breakdown costs identified in MSR with quick reference charts
Due with the monthly invoice submittal NLT 10th day of the month
Contract Funds Status Report (CFSR)
All efforts
Quarterly
004
3
Program Plan with Integrated Master Schedule (IMS)
All efforts with quick reference charts
NLT 30 days after kickoff meeting, or as required by EZP
005
3
Scientific and Technical Reports
All efforts with quick reference charts
NLT 6 months after kickoff meeting
006
3
AWB-1015 Documentation
Documentation required to maintain conformance to requirements of AWB-1015 CET process
As required by EZP
007
3
KC-135 CBM+ Program Implementation Plan
Reference Paragraph 2
NLT 45 days prior to contract completion, or as required by EZP
008
3
Final Scientific and Technical Reports Leveraging and Building Upon Previous USAF CBM+ Efforts
Final Technical Report and deliver unrestricted electronic data, test results, and coding compatible with current Air Force databases, raw and summarized
Draft Final provided NLT 45 days prior to contract completion. Final provided NLT 5 days prior to contract completion.

Invoices

10 days following the monthly financial report (Submitted to ITSS)

5. MEETING ATTENDANCE/TRAVEL: Throughout the period of performance, the Contractor shall coordinate all meeting attendance and travel directly with EZP personnel; this includes any travel requests and the level of effort per month that shall be allocated to this support. The Contractor shall report all findings, recommendations, and efforts related to authorized travel to EZP personnel, as appropriate. The EZP point of contact for this effort shall be the Program Manager. The Contractor shall participate in regular progress meetings and travel to events deemed necessary to provide support efforts described above. It is anticipated that travel to USAF sites may include, but is not limited to:

· Altus Air Force Base, Oklahoma

· Barksdale Air Force Base, Louisiana

· Fairchild Air Force Base, Washington

· Guam Air Force Base, Guam

· Hill Air Force Base, Utah

· Minot Air Force Base, North Dakota

· McConnell Air Force Base, Kansas

· Robins Air Force Base, Georgia

· Tinker Air Force Base, Oklahoma

· Washington DC

· Wright Patterson Air Force Base, Ohio

Additional travel to commercial vendor sites and test facilities, and MAJCOMs is expected. Some international travel may also be required in support of technical evaluation efforts.

The Contractor shall abide by all Air Force safety and conduct policies when conducting travel. The Contractor shall coordinate with AFLCMC to ensure the proper Government documentation is in place, such as CAC cards and/or clearances pending the type of efforts and programs the Contractor is asked to support.

5.1. Kick-Off Meeting: Within 15 business days of award, the Contractor shall coordinate a kickoff meeting, at which time all parties involved in the Task Order execution shall be represented and roles/responsibilities clearly outlined. During the kickoff meeting, the Contractor shall be prepared to discuss the Task Order. The intent of the technical activity area kick-off meeting is to review the sub-task schedule, objectives of each technical activity area, and review roles and responsibilities of the players.

5.2. Meetings: The Contractor shall plan to participate in monthly and quarterly progress meetings, detailing the progress, issues, needs, and/or unforeseen items that occur. The Contractor shall be responsible for coordinating and scheduling all meetings; however, the PM shall maintain approval authority for date, time, and location of all meetings. The Contractor shall prepare agenda, briefing materials, brief project status and technical data, and coordinate in advance of any meeting for PM approval. The government PM has authority to attend or not attend any scheduled meetings. The Contractor shall capture and track all action items, decisions, and minutes from all meetings and telecoms. A detailed review of each technical activity area shall be required.

6. GOVERNMENT FURNISHED FACILITIES AND INFORMATION: N/A.

7. PLACE OF PERFORMANCE: Contractor and DoD facilities (e.g. WPAFB OH and Tinker AFB OK).

8. SECURITY CLASSIFICATION: None

9. PERIOD OF PERFORMANCE: 12 months

10. SPECIAL INSTRUCTIONS: All terms listed in the base IDIQ PWS are applicable.

File details come from the government source that posted it.