RFP_Attachment_16-Task_Order__1_PWS.pdf

Attachment 16

Performance Work Statement (PWS) for

A-10 Technical Order Engineering Support

Task Order #1

13 September 2016

Rev 1, 4 October 2016

Prepared by:

AFLCMC/WWALE

Fighter/Bomber Directorate

Hill AFB, Utah 84056

CHANGE RECORD

PWS

Section

Pages Revision

3.3.1 3 1

CONTRACTOR REQUIREMENTS

PWS paragraph 3.1, IAW basic PWS.

KICK-OFF MEETING

6.1.5.1 Kick-off Meeting

The Contractor shall support a kickoff meeting no later than ten (10) working days upon contract award.

TRANSITION

6.1.4.1 Phase-In

If there is a change in Contractor, the new Contractor shall coordinate with the incumbent contractor to establish a secure method for receiving and storing the entire historic TO baseline

(SGML, CGM, PDF, and all A-10-tailored DSS files) for the A-10 TO Library. The new

Contractor shall coordinate with the incumbent Contractor to receive workload familiarization, and create a low-risk transition with no break in service. The new Contractor shall take possession of Government work in progress files (pending PCRs and attachments, not otherwise tasked to the incumbent Contractor) immediately upon receipt of an executed contract. The Contractor’s PMP shall describe a reasonable timeline for the transition. The timeline shall not be impacted based on differences between incumbent and new Contractors’ software. (CDRL A006)

PROGRAM MANAGEMENT SUPPORT

6.1.1 Program Management

a. The Contractor shall provide for management, planning, financial, and administrative support services, to include schedule, status, and cost reporting for all efforts supported under this task order. The Contractor shall assume responsibility for all technical, cost, schedule, quality, and configuration control program elements for this effort.

b. The Contractor shall generate and maintain documentation libraries, and shall support program reviews.

CDRL Sequence No. A003 Contractors Progress, Status and Management Report

c. The Status Report shall contain:

1) Progress of the previous period

2) Status of contract milestones

3) Sustainment deliverable schedules status by TO for this current period

4) Resource expenditures for the project, issues/concerns, and associated recommendations.

d. Contractor shall provide a Government-accessible web-based system for electronic delivery of all CDRLs, as well as real-time status reporting of all deliverables

6.1.2 Program Management Plan (PMP)

The Contractor shall provide and maintain a PMP. The initial PMP shall reflect the current status of the program. The Contractor’s PMP is a supplemental part of the overall TOLCMP. The PMP will include as a minimum, the Contractor’s:

a. Integrated document showing technical, cost and schedule data as they relate to the

PWS. It shall also provide information on the contractor’s organization, practices and techniques to be used in managing the program

b. Issues/concerns and associated program recommendations

c. Staffing profile

d. Quality Assurance Plan

e. Method proposed for electronic delivery for interim deliveries

f. Transition (phase-in/phase-out)

Deliverables required:

CDRL Sequence No. A006 Program Management Plan

6.1.3 Integrated Master Schedule

The Contractor shall provide an Integrated Master Schedule to reflect TO program milestone accomplishment and change delivery schedules. The Contractor shall coordinate and integrate technical data activities as they pertain to all A-10 Technical Orders including modifications, S1000D migration/conversion, SERP efforts, and rewrites. (CDRL A007)

TECHNICAL ORDER SUSTAINMENT SUPPORT

3.3.1 Technical Order Sustainment

The Contractor shall provide support in the conversion, integration, development and/or incorporation of Technical Order sustainment and modification requirements as identified by individual task order. The Contractor shall provide conversion services to update from paper or electronic source data into a format specified by the TO Manager and/or government technical manager designee(s). The Contractor shall assist in source data exchange with TO modification contractors to support modification schedules by providing tagging guidelines and TO source files when required by the System Program Manager/TOMA. The Contractor shall furnish all labor, equipment, and other services necessary to deliver the required products. Support to be provided includes:

A-10 TO and flight manual updates

Sustainment Delivery

Preparation of flight manual supplements, maintenance manual supplements, Identifying

Technical Publications Sheet (ITPS)

Creation of technical data

Storage and maintenance of digital data and other files generated under this PWS

Rapid Action Changes (RACS)

The contractor shall provide a tailored draft Technical Manual Contract Requirement (TMCR), in accordance with TO 00-5-3, 60 days post receipt of TO sustainment and/or modification task order

(CDRL A008). The Government will provide the contractor an initial TMCR for tailoring.

3.4 Block Cycle Update (BCU)

The Contractor shall deliver a complete BCU required by the TOMA for a June 2017 Block

Cycle Release (BCR). For pricing purposes, the A-10 averages about 78 books updated per BCR.

See the A-10 List of Technical Orders (RFP attachment 15).

The Contractor shall provide a secure means for two-way pre-publication transmittal (i.e., SharePoint) from Contractor to Government and Government to Contractor for the BCU to

AFLCMC/WWALE via the TOMA. Inspection and acceptance shall be IAW TO 00-5-1. The final publication deliverable shall be via CD/DVD. Because the next block cycle’s timeline overlaps with the June 2017 BCU, the Contractor shall be required to receive and store files

(pending Proposed Change Requests (PCR) and attachments) related to the subsequent block cycle.

BI-WEEKLY STATUS SUPPORT

6.1.4.2 Program Status Reviews/Technical Interchange Meetings

a. The Contractor shall attend regular (bi-weekly) program status reviews, as approved by the

Government Program Manager. The purpose of these meetings shall be to brief the progress of each assigned task, and to solicit input and concurrence of work performed.

The Contractor shall generate presentation materials as required to aid in the discussion of technical issues and shall support Technical Interchange Meetings/Reviews. The

Contractor shall provide review agendas, meeting minutes, and track Action Items associated with the aforementioned meetings/reviews. Review agendas shall include narrative review of work accomplished during the reporting period and/or significant events, deliverable process status, problems encountered, anticipated activities for the next reporting period, description of any travel or unique services provided funds and man-hour expenditure status. (CDRLs A001, A002, A003, A004)

b. Deliverables required:

CDRL Sequence No. A001 Conference Agenda

CDRL Sequence No. A002 Conference Minutes

CDRL Sequence No. A003 Contractors Progress, Status and Management Report

CDRL Sequence No. A004 Technical Report (Action Items)

CDRL Sequence No. A006 Program Management Plan

Period of Performance:

12 Months ARO