FINAL_PWS.pdf

Performance Work Statement (PWS) for A-10 Technical Order Sustainment Support

12 February 2018

Prepared by:

AFLCMC/WWALE

Fighter/Bomber Directorate

Hill AFB, Utah 84056

TABLE OF CONTENTS

1.0 INTRODUCTION

1.1 Purpose

1.2 Scope

1.3 Background

2.0 REFERENCE DOCUMENTS

2.1 Government Documents

Department of Defense Specifications DoD Standards Other Government Publications Air Force Instructions and Air Force Material Command Instructions USAF TOs Forms Other Documents

3.0 REQUIREMENTS

3.1 Contractor Requirements

3.2 Technical Order Support Services

Engineering and Logistics Support Engineering Analysis and Trade Studies Data and Software Analysis Technical Support for Technical Order Improvement Projects Technical Support to Assess Source Data

3.3 Technical Order Sustainment Services

Technical Order Sustainment Sustainment Delivery Time Change Technical Order (TCTO) Development Support Redline Text Technical Order Development

3.4 Block Cycle Update

3.5 Rapid Action Change Delivery

Priority out of Cycle Changes

3.6 Data Management

3.7 Interactive Wiring Diagrams

3.8 Technical Order Formalization

Technical Function TO Editing

SGML/XML

3.9 Art Work

3.10 Interactive Vectorized Files

3.11 Indexed Portable Document Format (IPDF) Creation

3.12 Information Assurance Training and Workforce Management

3.13 Legacy Data Cleanup

4.0 DELIVERY SCHEDULE AND PERIOD OF PERFORMANCE

4.1 Delivery Schedule

Data Program Management

Program Management Plan Integrated Master Schedule Meetings

4.2 Government Inspection and Acceptance of Deliverables

4.3 Service Summary

5.0 SPECIAL CONSIDERATIONS

5.1 Security

5.2 Access to Facilities and Property

5.3 Base Support - Government Provided Office Space

5.4 Government Program and Contract Management

5.5 Government Program Management

5.6 Government Contract Management

6.0 TRAVEL REQUIREMENTS

7.0 CONTRACTING OFFICER REPRESENTATIVE

8.0 ADMINISTRATIVE

8.1 Safety

8.2 Accident/Incident Reporting and Investigation

8.3 Security

8.4 Phase Out

8.5 Phase In

ACRONYM LIST

ACO Administrative Contracting Officer AFI Air Force Instructions AFMCI Air Force Material Command Instructions AIS Automated Information Systems BCU Block Cycle Update CAFDEx Centralized Access for Data Exchange CDRL Contract Data Requirements Lists CONOP Concept of Operations COR Contracting Officer Representative DoD Department of Defense DTD Document Type Definition ETIMS Enhanced Technical Information Management System FAT First Articles to be Test FMRC Flight Manuel Review Conference FOSI Formatted Output Specification Instance GFE Government Furnished Equipment GFI Government Furnished Information GFM Government Furnished Material GFS Government Furnished Software IAW In Accordance With ILS Integrated Logistics Support IMS Integrated Master Schedule IPT Integrated Product Team ITPS Identifying Technical Publications Sheet MSR Monthly Status Report OOC Out of Cycle Changes PLM Product Lifecycle Management PM Program Manager PNDB Part Number Database POOC Priority Out of Cycle PIWG Product Improvement Working Group PWS Performance Work Statement RAC Rapid Action Change SGML Standard Generalized Markup Language SPO System Program Office TCTO Time Compliance Technical Order TMSS Technical Manual Specifications and Standards TO Technical Order TOMA Technical Order Management Agency WBS Work Breakdown Structure XML eXtensible Markup Language

1.0 INTRODUCTION

1.1 Purpose

The purpose of this effort is to provide non-personal technical services to the A-10 System Program Office (SPO) in support of A-10 Technical Order (TO) sustainment activities, and support the goals of AFLCMC/WWALE technical order platforms. Deliver technical expertise in direct support of Air Force TO Concept of Operations (CONOPs) by providing user friendly, technically accurate, and up-to-date digital technical data at the point of use. Provide TO data that is acquired, sustained, distributed and available in digital format for all A-10 technical data users.

1.2 Scope

The PWS requirements described herein identify the contractor technical support required by the A-10 SPO Technical Support Branch. Technical and engineering data processes and services are to be provided in the following major categories:

Engineering and Logistics Support Trade Studies Data and Software Analysis Technical support required for technical order improvement projects Development of enhanced technical data tools TO Development and Sustainment

1.3 Background

The A-10 SPO, Technical Support Branch (AFLCMC/WWALE), serves as technical advisor to the warfighter in resolving complex and sophisticated equipment problems for A-10 Weapon Systems employed around the globe. Branch personnel manage technical aspects of major systems;

subsystems and equipment improvements; maintainability, reliability; and development of data on existing equipment and modifications. Addiotnally, the A-10 SPO, Technical Support Branch evaluates operational capability of systems/equipment, recommends tests, modifications, and corrections to design deficiencies.

TO Managers of this Branch are involved with development of information and analysis to select and present information on the specialized subject in a form and at a level suitable for the warfighter customer. They draw on a substantial knowledge of a particular subject-matter area in the development of training, operating, or maintaining manuals associated with assigned weapon systems. TOs are distributed world-wide to Air Force users and are vital elements that constitute a total weapon system. TOs are used by pilots to fly aircraft, by maintenance personnel to maintain and service equipment both in a combat and non-combat environment and are used by depot technicians to rebuild and rework equipment.

2.0 REFERENCE DOCUMENTS

The following documents are part of this PWS to the extent identified herein; applicability to the most recent version unless otherwise specified. In the event of a conflict is found, the Contractor shall seek Government direction.

2.1 Government Documents

Department of Defense Specifications Department of Defense (DoD) Specifications can be accessed through the Air Force Technical Manual Specifications and Standards web site: https://techdata.wpafb.af.mil/tmss/index.html.

Publication Number

Title Basic Date Latest Chg Number

Latest Chg Date

MIL-DTL-7700H Flight Manuals, Air Refueling Procedures, and Abbreviated Checklists

13 May 2002 25 Apr 2014

MIL-DTL-87929E Work Package 1 Feb 2002 15 Feb 2017 MIL-DTL-9977M Manuals, Technical and

Checklists:

Munitions/Weapons Loading Procedures, Nonnuclear and Nuclear and Packages, Standard Data: Munitions Loading Procedures, Nonnuclear

28 May 2015 28 May

MIL-DTL-38384E Checklists and Source Data Packages, Aircraft Weapon Delivery

September

10 Sep 2014

MIL-DTL-38769F

Work Unit Codes - Preparation of

25 Sep 2015 Amend 1 15 Sep 2017

MIL-DTL-38804E Time Compliance Technical Orders

10 Nov 2014 Amend 1 20 Apr 2017

MIL-DTL-38807D

Illustrated Parts Breakdown

17 Sep 2012 Amend 1 22 Aug

MIL-DTL- 5096G Inspection and Maintenance Requirements;

Acceptance and Functional Check Flight Procedures and Checklists; Inspection Work Cards; and Checklists

6 Feb 2014 6 Feb 2014

MIL-DTL-5920G

Sample Basic Weight Checklists and Loading Data

01 Oct 2010 Amend 1 15 May

MIL-DTL-8031H List of Applicable Publications (LOAPS) - Preparation

11 Aug 2014 11 Aug

MIL-DTL-83495D On-Equipment Maintenance Manual Set

24 Nov 2015 Amend 1 24 Nov

MIL-DTL-9854E Structural Repair (Aircraft)

10 Jan 2015 10 Jan 2015

DoD Standards

Publication Number

Title Basic Date Latest Chg Number

Latest Chg Date

MIL-STD-

38784A(1)

Standard Practice for Manuals, Technical:

General Style and Format Requirements

25 Aug 2011

11 Jul 2016

MIL-STD-1808C System Subsystem Sub- Subsytem Numbering

24 Jan 2014 Amend 1 2 Sep 2016

DLM 4000.25,

Volume 1

Concepts and Procedures

19 May 2014

Change 5 3 Oct 2017

DoDI 5220.22 National Industrial Security Program

(NISP)

18 Mar 2011 N/A N/A

DoDI 4140.01 DoD Supply Chain Material Management Procedures

14 Dec 2011 Change 1 14 Sep 2017

Air Force Instructions and Air Force Material Command Instructions

Publication Number Title Basic Date Latest Chg

Number Latest Chg Date

AFMCI 21-401 Engineering Data Storage, Distribution and Control

30 Mar 2015

AFI 31-101 Integrated Defense 15 Jul 2017

AFI 31-101

AFMC Sup

Integrated Defense 30 Nov 2016

AFMAN 31-116 Air Force Motor Vehicle Traffic Supervision

18 Dec 2015

AFMAN 31-116

Hill AFB Sup

Air Force Motor Vehicle Traffic Supervision

15 Jan 2016

AFI 16-1404 Air Force Information Security Program

29 May 2015

AFI 16-1404

AFMC Sup

Air Force Material Command Information Security Program

17 Feb 2016

AFI 11-215 USAF Flight Manuals Program

22 Dec 2008

Number

Latest Chg Date

AFI 11-215

AFMC Sup1 I

USAF Flight Manuals Program

25 May 2011

AFI 63-101/20-101 Integrated Lifecycle Management

09 May 2017

AFI 63-101

AFMC Sup

Acquisitions and Sustainment Life Cycle Management

31 Jan 2011

AFH 36-2235V2 Information For Designers Of Instructional Systems

2 Sep 2002

USAF TOs

Latest Chg Date

TM-86-01 Q Technical Manual Contract Requirements – tailored for the A-10 Program

27 Oct 2017

TO 00-5-1 AF Technical Order System

14 Jun 2016

TO 00-5-3 AF Technical Order Life Cycle Management

15 May 2017

TO 00-5-15 TCTOs 29 Sep 2017

TO 00-5-18 AF Technical Order Numbering System

01 Oct 2015

Forms

If necessary, the responsible Contractor or TO Manager shall ensure latest revisions of all forms are completed IAW corresponding directives as follows:

Form Number Form Title Directive Document Basic Date

AFTO Form 276 Special Requisition for Air Force Technical Order

TO 00-5-2

24 Aug 2001

DD Form 1348-1A Issue Release/Receipt Document

DoD 4000.25-1-M 01 Jul 1991

AFTO Form 158 Technical Order Review Comment Sheet

13 Aug 2008

AFTO Form 22 Technical Manual Change Recommedation and Reply

09 Mar 2017

AFTO Form 252 Technical Order Publication Change Request

22 Sep 2017

Other Documents

Latest Chg Date

ISO 9001:2008 Quality Management Systems - Requirements

3.0 REQUIREMENTS

The Contractor shall provide engineering/technical services for the efforts described within Section 3 below. The Contractor shall perform all work in accordance with standard policies and procedures as listed in Section 2.0. All required deliverables are delineated in subparagraphs. The documents shall be prepared IAW the Contract Data Requirements Lists (CDRLs), DD Form 1423-1. Unless otherwise designated, all deliverable documents shall be submitted to the Government via electronic means as Microsoft compatible email attachments. The Air Force reserves the right to review and audit Contractor’s compliance to those procedures identified herein.

3.1 Contractor Requirements

The Contractor shall provide technical order consulting and support services as well as product development and sustainment services with the following skills for the effort detailed through Section 3 below.

Extensive working knowledge in all areas of TO usage, development, sustainment, distribution, management, and STINFO requirements. Extensive working knowledge of USAF technical data digitization standards, policies, procedures, and processes.

Skill with PTC Epic Editor software and screen FOSI development or equivalent Skill with PTC IsoDraw software or equivalent Skill with developing Omnimark scripts and XSL transformations or equivalent Skill with Part Number Database (PNDB) Skill with MIL-STD-1808 including legacy data Skills with iPDF Skill with developing and sustaining technical orders, technical architecture, and style formatting specifications (spec bundles) in support of A-10 Technical Orders

3.2 Technical Order Support Services

The Contractor shall assist the Government program management staff on data development, conversion/migration, sustainment, usability, distribution processes, and management activities by providing expertise related to technical data standards and processes. The Contractor shall provide support and representation for the A-10 TO Sustainment program in technical and policy functions as requested by the A-10 SPO Technical Support Branch PM. Technical Support can include, but is not limited to:

Engineering and Logistics Support Trade Studies Data and Software Analysis Technical support required for technical order improvement projects Development of enhanced technical data tools

Source data review relating to A-10 technical data management requirements

Deliverables required:

CDRL Sequence No. A004 Technical Report – Study/Services CDRL Sequence No. A005 Scientific and Technical Reports CDRL Sequence No. A010 Quality Assessment Report

Engineering and Logistics Support The Contractor shall provide assessment of source data provided in support of related A-10 aircraft modifications for technical accuracy, engineering completeness, schedule viability, and specification conformance. The Contractor shall coordinate with other support entities (i.e. TO Integrated Logistics Support (ILS)) while performing tasks. This includes integration with, data cleansing, Product Lifecycle Management (PLM), and organic software and hardware development activities. (CDRL A010)

Engineering Analysis and Trade Studies The Contractor shall provide engineering analysis and trade studies as requested by the AF TO Program Manager to support PWS technical data efforts. The Contractor shall provide support in the development and execution of digital data support strategies and data management efforts. The Contractor shall assess emerging technologies and initiatives to determine their application to existing Technical Order support requirements. These include software engineering assessments, computer hardware and software technology assessments, standardization assessments, configuration item/software documentation assessments, and accompanying life cycle cost projections. Examples of trade studies in support of the PWS would include alternate file format investigations, assessments of TMSS specification updates, schedule optimization of Block Cycle Updates (BCUs), major modifications, and usability studies for alternate presentation devices.

Design data and calculations used for Engineering Analysis and Trade Studies shall be documented and up to five (5) trade studies may be requested during the base contract period of performance.

(CDRL A004)

Data and Software Analysis The Contractor shall provide engineering and design expertise in supporting USAF TMSS implementations, and shall provide recommendations on A-10 TMSS use cases representing Air Force interests. The Contractor will provide data and software analysis associated with PWS technical elements including document type definition (DTD) analysis, formatted output specification instance (FOSI) analysis, schema analysis, and GFI software analysis. Design data and calculations used for software analysis shall be documented and up to ten (10) analyses may be requested during the base contract period of performance. (CDRL A005)

Technical Support for Technical Order Improvement Projects The Contractor shall provide technical support for Technical Order improvement projects to include technical order rewrites to accommodate data consolidation and usability improvements.

The Contractor shall provide subject matter expertise to accommodate these efforts and up to ten

(10) TO Improvement Projects may be requested annually. (CDRL A005)

Technical Support to Assess Source Data The Contractor shall assess the source data provided in support of A-10 aircraft modifications for technical accuracy, engineering completeness, schedule viability, and specification conformance.

The Government anticipates utilizing this task three to five times a year. (CDRL A005, A010)

3.3 Technical Order Sustainment Services

Technical Order Sustainment The Contractor shall provide support in the conversion, integration, development, and/or incorporation of Technical Order sustainment and modification requirements. 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 Creation of technical data Digitization of existing technical data Preparation of TCTOs Sustainment Delivery Preparation of flight manual supplements, maintenance manual supplements, Identifying

Technical Publications Sheet (ITPS)

Sustainment Delivery The Contractor shall edit and maintain TOs to support routine, urgent, and emergency changes in both electronic and hard copy (CD/DVD overnight) IAW TO 00-5-3. (CDRL A009)

3.3.2.1 Routine Changes

Routine changes shall be denoted on the receipt of AFTO Form 252s. Routine deliveries shall be delivered as an update package only during the BCU delivery unless an out-of-cycle delivery is requested by the Technical Order Management Authority (TOMA).

3.3.2.2 Urgent Changes

Urgent changes shall be completed and ready for shipping in ten (10) working days. The Contractor shall be notified prior to issue for an accelerated delivery work order and of any unique Rapid Action Change (RAC) delivery requirements.

3.3.2.3 Emergency Changes

Periodically, emergency TO update requirements dictate that accelerated delivery time parameters are necessary to satisfy using command priority operation and maintenance schedules. The Contractor shall deliver an emergency change within two (2) days for safety of personnel/damage to equipment or three (3) days for work stoppage after receipt of Government furnished source data. The Contractor shall be notified prior to issue for an accelerated delivery work order and of any unique RAC delivery requirements.

Time Change Technical Order (TCTO) Development Support The Contractor shall provide TCTO development support for routine, urgent, and emergency type requirements IAW T.O. 00-5-1, T.O. 00-5-3, T.O. 00-5-15, and MIL-DTL-38804E. The Contractor QA reviewed TCTOs shall be delivered in the Enhanced Technical Information Management System (ETIMS) compatible format to the Government. (CDRL A009)

Redline Text Redline text changes that are identified as a result of Government pre-publication reviews or additional changes required to other TO as a result of BCUs, Out of Cycle Changes (OOCs), RACs or other

Government-directed changes will be provided to the Contractor for final update to the TO prior to delivery (CDRL A009).

Technical Order Development The Contractor shall create Technical Order data using SGML/XML, or other AF approved standards, with appropriate TMSS DTDs. The Contractor shall prepare line drawings, schematics, and diagrams for incorporation into the Technical Order data. The Contractor is responsible for incorporating changes derived from AFTO 22/AFMC 252s into the existing TO baseline. The Contractor is responsible for incorporating validated source data into the existing TO baseline from various Centralized Access for Data Exchange (CAFDEx), modifications, and A-10 Suite upgrades. The Contractor shall parse and compose SGML/XML-tagged TO document files prior to delivery to the Government.

The Contractor shall verify that tagging has been accomplished to the levels provided in the DTDs and the content fulfills directives in specifications and standards. Composed instances shall be compatible with output composed by TMSS FOSIs. The Contractor shall prepare and deliver all First Articles to be Tested (FAT) by the Tech Data Office at Wright-Patterson AFB for compliance with Air Force TMSS requirements and report findings to the Government. (CDRL A005)

3.4 Block Cycle Update

The Contractor shall deliver a complete Block Cycle Update (BCU) for routine changes as required by TOMA. The Contractor will provide a secure means for two-way transmittal from Contractor to Government and Government to Contractor of the BCU to AFLCMC/WWALE via the TOMA.

Inspection and acceptance shall be IAW with CDRL requirements. The final deliverable shall be CD/DVD. A-10 SPO is currently on three (3) BCUs a year which is subject to change as directed by the TO Program Manager. The BCUs fall on February, June, and October. (CDRL A009)

3.5 Rapid Action Change Delivery

The Contractor shall prepare RACs in conformance with USAF TMSS and A-10 TO policy (TO 00-5-3). RACs are intended to fulfill urgent and emergency update requirements to electronic technical manuals when published information is required to be fielded prior to a scheduled BCU.

RACs shall be delivered by the Contractor through secure electronic processes (per paragraph 3.4).

The Government anticipates utilizing a RAC delivery no more than thirty (30) times during a twelve month period. (CDRL A009)

Priority out of Cycle Changes The Contractor and the Government will collaborate on the prioritization of large tech order changes that cannot wait until normal BCU dates due to immediate need requirements. As these large workloads are prohibitive to meet normal RAC time limits, they will be processed as Priority Out of Cycle changes (POOC) to meet the needs of the end-users. The government anticipates utilizing a Priority out of Cycle delivery no more than twenty (20) times during a twelve month period. (CDRL A009)

3.6 Data Management

The Contractor shall establish and maintain a complete, comprehensive data repository for all A- 10 technical data to include an archive section for prior version of the technical data. The Contractor shall design, develop, and deliver a method for secure delivery of interim, review, and final deliverables. (CDRL A005)

3.7 Interactive Wiring Diagrams

The Contractor shall create and maintain vectorized interactive wiring diagrams in accordance with current publications of the 1A-10C-2-110-1 and 1A-10C-2-110-1-1 technical orders. The Contractor shall provide fully functional interactive wiring diagrams compatible with a standard web browser. (CDRL A005)

3.8 Technical Order Formalization

The Contractor shall provide:

Digitization of existing technical data and changes to TO’s Conversion of paper tech manuals to digital form (PDF, SGML, HTML, eTO, etc.)

Technical Function

The Contractor shall assist the Government program management staff, as required, on data conversion/migration, usability, distribution processes, and management activities by providing expertise related to technical data standards and processes. The Contractor shall provide support and representation for the A-10 program in technical and policy functions as requested by the A- 10 SPO Technical Support Branch PM. (CDRL A005)

TO Editing The Contractor shall perform editing for all A-10 flight and maintenance TOs as a part of routine maintenance to the manuals. The A-10 Technical Support Branch shall supply technical markups as source data that the Contractor shall use to create an update package. The Contractor shall deliver all data IAW the PWS. The Contractor shall establish and maintain a complete, comprehensive data repository for all A-10 technical data per paragraph 3.2.2.3. The Contractor shall edit TOs using SGML source data taken from a Government approved TO repository (ex.

ETIMS). (CDRL A005)

SGML/XML

The Contractor shall create the manuals using SGML/XML, with appropriate TMSS and/or DTDs. The Contractor shall parse and compose SGML/XML-tagged TO document files prior to delivery to the Government. The Contractor shall verify that tagging has been accomplished to the levels provided in the DTDs and the content fulfills directives in specifications and standards.

Composed instances shall be compatible with output composed by TMSS Formatting Output Specification Instances (FOSIs). (CDRL A005)

3.9 Art Work

The Contractor shall develop and modify line drawings, schematics, and diagrams. Art work shall conform IAW MIL-STD-38784A(1) and be compatible with all deliverable requirements.

Allnew graphics shall be delivered as vectorized CGM files. (CDRL A005)

3.10 Interactive Vectorized Files

The Contractor shall develop interactive vectorized files in support of intelligent wire/signal tracing products derived from existing A-10 technical order wiring schematics.. (CDRL A005)

3.11 Indexed Portable Document Format (IPDF) Creation

The Contractor shall develop interactive vectorized files in support of intelligent wire/signal tracing products derived from existing A-10 technical order wiring schematics. (CDRL A005)

3.12 Information Assurance Training and Workforce Management

The Contractor shall comply with all computer and network access requirements and instructions including DoD Directive 8570.1, Information Assurance Training, Certification, and Workforce Management.

3.13 Legacy Data Cleanup

The Contractor shall adhere to MIL-STD-1808 when creating new technical orders corresponding to the appropriate system or category.

4.0 DELIVERY SCHEDULE AND PERIOD OF PERFORMANCE

4.1 Delivery Schedule

Paragraph Description CDRL Due Date

4.1.5.2 Conference Agenda A001 2 working days before

milestone/conference/meeting

4.1.5.2 Conference Minutes A002 5 working days after

milestone/conference/meeting 4.1.2, 4.1.5.2 Contractor’s Progress, Status, and Management Report

A003 10th of each month for previous calendar month support

3.2, 4.1.5.2 Technical Report – Study/Services

A004 As requested

3.2 Scientific and Technical

Report

A005 As requested

4.1.3 Program Management

Plan/PWS Revision

A006 45 calendar days after contract award

4.1.4 Integrated Master Schedule A007 10th of each month for

previous calendar month support

2.1.5 Technical Manual Contract

Requirements (TMCR)

A008 30 days after contract award

3.3.2, 3.3.3, 3.3.4, 3.4, 3.5, 3.5.1

Technical Order Improvement Report and Reply

A009 BCU delivered 3 times a year with RACs and Priority Out of Cycles submitted as required

3.2, 3.2.1, 3.2.5

Quality Assessment Report A010 As Requested

Data

All data generated under the tasks defined within this PWS or any subsequent task order shall be developed for the A-10 aircraft at U.S. Government expense and the U.S. Government shall have unlimited rights in all such data as defined in DFARS 227.7103-5 and DFARS 252.227- 7013(a)(15). All such documents shall be marked 'unlimited rights' as follows:

UNLIMITED RIGHTS

Contract No.

Contractor Name Contractor Address

The Government's rights to use, modify, reproduce, release, perform, display, or disclose these technical data are unlimited. No restrictions apply.

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 contract. 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 Monthly Status Report shall contain:

1) Progress of the previous month

2) Status of contract milestones

3) Sustainment deliverable schedules status by TO for current, previous and next periods

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

Program Management Plan The Contractor shall provide and maintain a Management Plan. The established Management Plan shall be updated throughout the program to reflect the current status. The Management Plan will include as a minimum:

a. Issues/concerns and associated recommendations

b. Staffing profile

c. Quality Assurance Plan

d. Method proposed for electronic delivery for interim deliveries

CDRL Sequence No. A006 Program Plan (Program Management Plan)

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, SERP efforts, and rewrites. (CDRL A007)

Meetings

4.1.5.1 Kick-off Meeting

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

4.1.5.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 conference agendas, meeting minutes, and track Action Items associated with the aforementioned meetings/reviews. (CDRLs A001, A002, A003, A004)

b. The Contractor shall include, at a minimum, the following information in the Monthly

Status Report (MSR); 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. (CDRL A003)

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 Study/Services (Action Items)

4.1.5.3 Technical Order Rewrite/Flight Manual Review Conference (FMRC) Support The Contractor shall support tech order rewrite efforts for all A-10 flight and maintenance TOs as required. The Contractor shall provide real-time updates to the SGML and graphic sets during the rewrite/FMRC sessions.

4.1.5.4 Reviews

The Contractor shall participate and support Government held In-Process Reviews (IPRs), program reviews, Technical Interchange Meetings (TIMs), and inspection to successfully complete technical support requirements tasked under this PWS. The Contractor shall provide the capability of onsite real time SGML editing and publishing if requested to support time critical (defined as a Rapid Action Changes and priority out of cycle change) Government events.

4.1.5.5 Integrated Product Team (IPT) Meetings

The Contractor shall support Biannual IPT’s at the local contractor facility. The goal of the IPT is to provide all members early insight into technical and schedule problems as well as the Contractor’s actions taken to initiate/manage adequate resolution plans.

4.2 Government Inspection and Acceptance of Deliverables

The Government Program Manager will have the right to reject or require correction of any deficiencies found in deliverables. In the event of rejection of any deliverable, the Contractor will be notified in writing by the Government Program Manager of the specific reasons why the deliverable was rejected. The Contractor shall have seven (7) calendar days, or as outlined in the table in Section 4.1 (whichever is shorter), to correct the rejected deliverable and resubmit to the

Government Program Manager for re-inspection. If no comments are provided within 30 calendar days of deliverable receipt, the deliverable will be deemed to have been accepted by the Government.

4.3 Service Summary

The Contractor shall be evaluated based on the below items.

Performance Objectives

PWS. Para. Performance Threshold

Method of Surveillance

Work Performance Requirements

3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10,3.11, 3.12, 3.13, 4.1, 4.2, 8.3, 8.4, 8.5 Appendix 1 (CDRLs)

All actions accomplished as per ISO 9001 with 98 percent accuracy.

Customer Complaint /Feedback AFTO Form 158

CDRL Deliverables 3.2, 3.3.2, 3.3.3, 3.3.4, 3.4, 3.5, 3.6, 3.7, 3.8.1, 3.8.2, 3.8.3, 3.9, 4.1, 4.2

90% reporting accuracy. 90% on time receipt of deliverables.

100% inspection

Incorporate TO Changes (Para. 3.4, 3.5, 3.5.1)

3.3.2, 3.3.3, 3.3.4, 3.4, 3.5, 3.6, 3.7, 3.8

Routine Changes

(BCU)

AFTO Form 252 with 95 percent accuracy.

Deficiencies to be corrected to 100 percent within 10 working days.

Urgent Changes 10 calendar days from receipt of AFTO Form 252 with 95 percent accuracy.

Deficiencies to be corrected to 100 percent upon receipt of errors from the

TOMA.

Emergency/Rapid Action Changes 2 calendar days from receipt of AFTO Form 252 for safety changes and 3 calendar days for work stoppage, with 95 percent accuracy.

100% Surveillance

Deficiencies to be corrected to 100 percent upon receipt

Out of Cycle Changes for Mods Routine: 104 working days from receipt of deliverables.

Accelerated: 69 working days from receipt of deliverables

5.0 SPECIAL CONSIDERATIONS

5.1 Security

Contractor personnel shall not release or remove system documentation, data, or reports generated by or through use of Government systems. All requests for information shall be forwarded to AFLCMC/WWALE, ATTN: A-10 TO Program Manager.

This effort requires access to, and storage of, classified information and equipment on Government approved facilities and databases. Therefore, this contract will require the contract personnel to obtain a security clearance. A security clearance of SECRET will be required for all personnel having access to the classified data and a DD Form 254 shall be submitted.

The A-10 TO Program Manager will assist contractor personnel in processing the necessary DoD forms to obtain installation or area badges for access to Government facilities.

The Contractor shall not divulge any information regarding files, data, processing activities/functions, user IDs, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. Contractor personnel shall abide by all Government rules, procedures, and standard of conduct. Contractors requiring access to Government Automated Information Systems (AIS) shall have background investigations and security awareness training completed, after task order award but prior to AIS access. When the period of performance is complete or and contractor personnel leave work on this project they will have five (5) working days to terminate all their network user account and to return all access cards and base identification badges.

5.2 Access to Facilities and Property

Access to Government facilities is limited. Therefore, the Contractor shall coordinate required access/usage times and dates through the A-10 TO Program Manager at least fifteen (15) working days prior to the need date. Control of the facilities shall remain with the Government.

5.3 Base Support - Government Provided Office Space

No base support is anticipated with this Task Order. All work efforts shall be performed at the Contractor’s site and/or contractor personnel will spend minimal time at the Government’s location.

5.4 Government Program and Contract Management

5.5 Government Program Management

AFLCMC/WWALE will provide the Government Program Manager for this contract. The Government Program Manager will provide the Contractor access to all technical data required to perform approved tasking. Only the Government Program Manager or their designee has authority to review and approve contract deliverables (see paragraph 4.3).

5.6 Government Contract Management

Responsibility for contracting activities rests solely with the Government Contracting Officer. No conversation, recommendations, or direction, whether given directly by, or implied by Government personnel, that will affect the scope, schedule, or price of the program covered by this PWS, shall be acted upon by the Contractor unless specifically approved by the Government Contracting Officer.

6.0 TRAVEL REQUIREMENTS

Travel will be required in support of the above requirements. Annual travel needs are estimated as follows.

Purpose - Destination No. Persons No. Trips No. Days Kick-off Meeting (Sustainment) 3 2 5 TO Rewrite 2 3 5 TO IPT Support 4 2 5

FMRC 1 1 5

PIWG Support 2 1 5

The Contractor may be required to travel to support the objectives of this PWS.

7.0 CONTRACTING OFFICER REPRESENTATIVE

The overall Program Management (PM)/Contracting Officer Representative (COR) responsibilities for this task order reside with the following office:

Office Symbol: AFLCMC/WWALE Street Address: 6067 Box Elder Ln Building Number: 1284 Hill AFB, UT 84056-5811 801-586-7150

The Contractor will be notified by letter at time of award of the Primary and Alternate CORs assigned to this task order.

8.0 ADMINISTRATIVE

8.1 Safety

The Contractor shall protect Government property to prevent damage during the period of time the property is under the control or possession of the contractor.

The Contractor shall include a clause in all sub-contracts to require subcontractors to comply with the safety provision of this contract.

The Contractor shall include a clause in all sub-contracts to require subcontractors to comply with the safety provision of this contract. The Contractor shall comply with all safety provisions technical specifications, technical publications, Federal Occupational Safety and Health Administration (OSHA) Standards (Title 29 CFE, part 1910). If there is no applicable OSHA Standard, Air Force Occupational Safety and Health Standard (AFOSH) or applicable nationally recognized sources of safety, health, and fire prevention standards referenced will be used in the work requirements of this contract.

8.2 Accident/Incident Reporting and Investigation

The Contractor shall report promptly to the Contracting Officer or Administration Contracting Officer, all available facts relating to each instance of damage to Government property IAW appendix B.

If the Government elects to conduct an investigation of the accident, the Contractor shall cooperate fully and assist Government personnel until the investigation is completed.

The Contractor shall include a clause in each of his applicable subcontracts to require subcontractor's cooperation and assistance in accident reporting and investigation.

8.3 Security

Contractor personnel shall not release or remove system documentation, data, or reports generated by or through use of Government systems. All requests for information shall be forwarded to the A-10 SPO through the CO.

The Contractor shall not divulge any information regarding files, data, processing activities/functions, user IDs, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. Contractor personnel shall abide by all Air Force rules, procedures, and standards of conduct. When the period of performance is complete and/or Contractor personnel leave work on this project they will have five (5) days to terminate all their network user accounts and to return all access cards and base identification badges.

8.4 Phase Out

If there is a change in Contractor, the incumbent Contractor will provide familiarization and entire historic TO baseline (SGML, CGM, PDF, and all A-10-tailored DSS files) for the A- 10 TO library, to the new Contractor. During the phase-out familiarization period, the incumbent Contractor will be fully responsible to provide services as specified within this PWS to complete the work in progress on executed task orders.

8.5 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 will obtain familiarization from the incumbent contractor, and create a low-risk transition plan that will demonstrate the ability to provide the expertise and experience to accomplish the required tasks during the transition with no break in service. At the completion of the 6 month phase-in familiarization period, the new Contractor will be fully responsible to provide services as specified within this PWS. This 6 month timeline shall not be impacted based on differences between incumbent and new Contractors’ software, which is critical if the new SGML will require retagging, validation and verification.

Appendix 1

Contract Data Requirements Lists (CDRLs)

Performance Work Statement (PWS) for

A-10 Technical Order Engineering Support

20 December 2017

Prepared by:

AFLCMC/WWALE

Fighter/Bomber Directorate

Hill AFB, Utah 84056

All CDRLs for this PWS are included as a separate attachment. The following CDRLs are required as part of this tasking. The delivery schedule is defined in Section 4.2.

A001 Conference Agenda A002 Conference Minutes A003 Contractor’s Progress, Status, and

Management Report A004 Technical Report – Study/Services A005 Scientific and Technical Report A006 Program Management Plan (PMP) A007 Integrated Master Schedule (IMS) A008 Technical Manual Contract

Requirements (TMCR) A009 Technical Order Improvement Report and Reply A010 Quality Assessment Report

BLOCKS 9: DISTRIBUTION STATEMENT “D” Distribution authorized to Department of Defense (DoD) and DoD contractors for administrative or operational use determined XX April.

Other requests for a copy of this document shall be referred to the BLK 6 Requiring Office on the DD Form 1423 that governs this submittal.

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751 et seq.) or Executive Order 12470. Violations of these export laws are subject to severe criminal penalties.

The above Distribution Statement and Warning Notice shall be displayed or affixed to the data in a conspicuous position.

BLOCKS 9: DISTRIBUTION STATEMENT “E” - Distribution authorized to DoD Components only for unclassified and classified technical data. Direct Military Support – The document contains export-controlled technical data of such military significance that release for purposes other than direct support of DoD approved activities may jeopardize an important operational military advantage of the United States. Designation of such data is made by competent authority in accordance with DoD Directive 5230.25 (12 Feb 2018). Other requests for this document shall be referred to AFLCMC/WWALE, 6067 BOX ELDER LANE, Hill AFB, UT 84056-5811.

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec. 2751 et seq.) or the Export Administration Act of 1979, as amended (Title 50, U.S.C., App. 2401 et seq.). Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25

HANDLING AND DESTRUCTION NOTICE: Handle in compliance with distribution statement and destroy by any method that will prevent disclosure of the contents or reconstruction of the document.