TO_Support_and_Sustainment_PWS.pdf

PERFORMANCE WORK STATEMENT (PWS)

For

A-10 Technical Order Support

18 September 2012

Prepared by:

OO-ALC/GHAEH

Ogden Air Logistics Center

Hill AFB, Utah 84056 PR Number: FD2020-12-50990

REVISION RECORD

Revision Date Description Pages

Basic 13 July 2012 Final 20

1 18 Sept 2012 Revision 1 20

TABLE OF CONTENTS

Cover Page………………………………………………………………………………… 1

Revision Record…………………………………………………………………………… 2

Acronym List……………………………………………………………………………….4

1.0 Introduction…………………………………………………………………………… 5

1.1 Purpose……………………………………………………………………….…. 5

1.2 Scope…………………………………………………………………………

1.3 Background……………………………………………………………………

2.0 Reference Documemts………………………………………………………………… 5

2.1 Department of Defense (DoD) Specifications…………………………………... 5

2.2 DoD Standards…………………………………………………………………... 6

2.3 Government Publications……………………………………………………….. 7

2.4 Air Force Instruction (AFI) and AFMCI………………………………………... 7

2.5 USAF TOs………………………………………………………………

2.6 Forms………………………………………………………………………

2.7 Other Documents………………………………………………………………... 8

3.0 Requirements…………………………………………...……………………………... 9

3.1 General………….....………...………………………………………………

3.2 Technical Order……………………………...………………...………...……… 9

3.3 Sustainment Delivery……………………………………………………………. 11

3.4 Block Cycle Update…………………………………………………………….. 11

3.5 Rapid Action Change…………………………………………………………… 12

3.6 Integrated Master Schedule……………………………………………………… 12

3.7 TO Formalization……………………………………………………………….. 12

3.8 Art Work………………………………………………………………………… 13

3.9 Interactive Vectorized Files…………………………………………………….. 13

3.10 Electronic TOs...………………………………………….…….……………….. 13

3.11 Meetings………………………………………………………………………… 14

3.12 Travel Requirements..…..……………………………...………

4.0 General Informations…………………………………………………………… 15

4.1 Government Responsibility……………………………………………………... 15

4.2 Contractor Responsibility....…………………………………………………….. 15

4.3 Deliverables………….………………………………………………………….. 16

4.4 Data……..………………………………………………………………

4.5 Service Summary………………………………………………………………... 17

5.0 Administrative………………………………………………………………………

5.1 Safety.…..……………………………………………………………………….. 18

5.2 Accident/Incident Reporting and Investigation……………………………

5.3 Security………………………………………………………………………….. 18

5.4 Phase Out………………………………………………………………………... 18

6.0 Statement of Mission Essential Services…………………………………………….. 19

Appendices…………………………………………………………………………… 20

ACRONYM LIST

ACC Air Combat Command

ALC Air Logistics Center

BCU Block Cycle Update

CDRL Contract Data Requirements Lists

CGM Computer Graphics Metafile

CO Contracting Officer

CPIN Computer Program Identifivcation Number

CTOM Centralized Technical Order Management

DFARS Defense Federal Acquisition Regulation Supplement

DFOSI Display Formatting Output Specification Instances

DID Data Item Description

DoD Department of Defense

DTD Document Type Definition

ECSS Expeditionary Combat Support System

EFB Electronic Flight Bag

ETIMS Enhanced Technical Information Management System

ETO Electronic Technical Order

FMT Full Mission Trainer

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

IPDF Indexed Portable Document Format

IPR In Process Reviews

IPT Integrated Product Team

ITPS Identifying Technical Publication Sheet

JCALS Joint Computer-Aided Acquisition and Logistics Support

RAC Rapid Action Change

PLM Product Lifecycle Management

PMA Portable Maintenance Aid

PM Program Manager

PWS Performance Work Statement

QA Quality Assurance

SERP Sustainment Engineering Requirements Program

SPO System Program Office

TCM Technical Content Manager

TCTO Time Compliance Technical Order

TIM Technical Interchange Meetings

TLPS Thunderbolt Lifecycle Program Support

TMSS Technical Manual Specifications and Standards

TO Technical Order

TOGC Technical Order Guidance Conference

TOMA Technical Order Management Agency

TOPP Technical Order Process Plan

TORT Technical Order Review Team

USAF United States Air Force

Val/Ver Validation/Verification

1.0 INTRODUCTION

1.1 PURPOSE

The purpose of this acquisition is to establish the Contractor activities necessary to support the

A-10 System Program Office (SPO) with A-10 Technical Orders (TO). The task is broken up into two main objectives: (1) Technical Order Support and Sustainment and (2) Technical Order

Formalization. The Contractor is responsible for incorporating changes derived from AFTO

22s/252s into the existing TO baseline on a regularly scheduled Block Cycle Update (BCU).

Contractor is responsible for incorporating validated source data into the existing TO baseline for various Sustainment Engineering Requirements Program (SERP), modifications, and suite efforts.

1.2 SCOPE

This Performance Work Statement (PWS) outlines the level of effort required to meet the needs of the Government. The objectives and requirements identified within this PWS describe the

Contractor’s tasking.

1.3 BACKGROUND

Technical Orders (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 contingency and peace time environments, and by depot technicians to rebuild and rework equipment.

The A-10 SPO, Technical Support Branch (OO-ALC/GHAEH), serves as technical advisor to the warfighter for resolving complex and sophisticated equipment problems of weapon systems employed around the globe. The Contractor shall work with the Technical Order Managers of this branch to ensure the warfighter receives accurate, digitized data.

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. The Contractor shall perform all work In Accordance With

(IAW) the standard policies and procedures listed below. The Technical Order Process Plan

(TOPP) in section 2.7 (Other Documents) is for reference purposes only and shall be treated as such. This document outlines the TO process specific to the A-10.

2.1 Department of Defense (DoD) Specifications (Technical Manual Specifications and

Standards (TMSS))

DoD Specifications can be accessed through the ASSIST Quick Search web site:

http://assist.daps.dla.mil/quicksearch/.

Publication

Number

Title Basic Date Latest Chg

Number

Latest Chg

Date

MIL-DTL-7700G Flight Manuals, Air

Refueling Procedures, and Abbreviated

13 May http://assist.daps.dla.mil/quicksearch/

Checklists

MIL-DTL-87929D Technical Manuals, Operation and

Maintenance

Instructions in Work

Package Format

20 Apr 2012

MIL-PRF-38384D Checklists and Source

Data Packages, Aircraft

Weapon Delivery

15 Jul 1996

MIL-PRF-38769D Work Unit Code 1 July 1996

MIL-PRF-38804C Time Compliance

Technical Orders

1 Mar 1996 Amend 1 20 Jun 97

MIL-PRF-38807C Illustrated Parts

Breakdown

29 Nov

MIL-PRF 5096F Inspection and

Maintenance

Requirements;

Acceptance and

Functional Check Flight

Procedures and

Checklists; Inspection

Work Cards; and

Checklists

1 Mar 1996

MIL-PRF-5920G Sample Basic Weight

Checklists and Loading

Data

1 Oct 2010

MIL-PRF-8031F List of Applicable

Publications

23 Sep 2010

MIL-DTL-83495C On-Equipment

Maintenance Manual

Set

23 Aug

MIL-PRF-9854D Structural Repair 22 Nov

MIL-PRF-9977L Munitions/Weapons

Loading Procedures, Nonnuclear and Nuclear and Packages, Standard

Data: Munitions

Loading Procedures, Nonnuclear

19 Apr 2011

2.2 DoD Standards

Publication

Number

Title Basic Date Latest Chg

Number

Latest Chg

Date

MIL-STD-38784A Standard Practice for 25 Aug 2011 Notice 2

2.3 Government Publications

Title Basic Date Latest Chg

Number

Latest Chg

Date

MIL-HDBK-38790 Printing Production of

Technical Manuals

24 Feb 1997 Notice 1 Mar 2002

2.4 Air Force Instructions (AFI) and Air Force Material Command Instructions (AFMCI)

Publication Number Title Basic Date Latest Chg

Latest Chg

Date

AFI 31-401 Information Security

Program Management

01 Nov 2001

AFI 11-215 Flight Manuals

Program

22 Dec 2008 pr 2005

AFI 63-101 Acquisition

Sustainment and

Lifecycle Management

8 April 2009 4 3 August

AFMCI 23-101 Air Force Provisioning

Instruction

30 Apr1999

AFMCI 23-103 Diminishing

Manufacturing Sources and Materiel Shortages

(DMSMS) Program

24 Sep 2004

AIR FORCE

HANDBOOK 36-

Information For

Designers Of

Instructional Systems

1 Nov 2002

Manuals, Technical:

General Style and

Format Requirements

DoD 4000.25-1-M Military Standard

Requisitioning and

Issue Procedures

(MILSTRIP)

April 28

DoD 5220.22-M National Industrial

Security Program

Operating Manual

(NISPOM)

Dec 1980 N/A N/A

DOD 4104.1-R DoD Supply Chain

Material Management

23 May 2003

2.5 USAF TOs

Title Basic Date Latest Chg

Number

Latest Chg

Date

TO 0-1 United States Air Force

TO Catalog

01 Jul 2004 None None

TO 00-5-1 AF Technical Order

System

1 May 2011 None None

TO 00-5-3 AF Technical Order

Life Cycle

Management

1 Apr 2001 None None

TO 00-5-15 TCTOs 1 Jan 2010 None None

TO 00-5-18 AFTechnical order

Numbering System

31 Dec 2006 None None

2.6 Forms

If necessary, the responsible Contractor shall ensure latest revisions of all forms are completed

IAW corresponding directives as follows:

Form Number Form Title Directive Document Basic Date

AFTO 276 Special Requisition for

Air Force Technical

Order

TO 00-5-2 01 Apr

AFTO 158 Technical order

Review Comment

Sheet

13 Aug

AFTO 22 Technical Manual ™

Change

Recommedation and

Reply

29 Sep

AFTO Form 252 Technical order

Publication Change

Request

9 Nov 2011

TM-86-01

Technical Manual

Contract Requirements

– tailored for the A-10

Program

01 Apr 2009 None

2.7 Other Documents

Title Basic Date Latest Chg

Number

Latest Chg

Date

ISO 9001:2008 Quality Management

Systems -

Requirements

S1000D International

Specification for

Technical Publications utilizing a Common

Source Database

Issue 4.0 1 August

TOPP Tech Order Process Plan 20 Jul 2011

3.0 REQUIREMENTS

3.1 GENERAL

The Contractor shall ensure the TO data is based on the correct/current baseline to prevent inaccurate data from being released to the field. The Contractor shall provide assistance to A-10

SPO Technical Support Branch, as needed, to assist in determining baseline TO requirements for future projects.

3.2 TECHNICAL ORDER

3.2.1 Technical Order Support

The Contractor shall provide technical support to the A-10 SPO Technical Support Branch.

Technical Support can include:

Analysis of new TO mandates

Engineering and Logistics Support

Technical support required for technical order improvement projects

Trade Studies

Technology Roadmaps

Data and Software Analysis

Familiarization

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

3.2.1.1 Analysis of new TO mandates

The Contractor shall analyze the impacts of TO policy changes and mandates on the A-10 TO process that is driven by the Government. The Contractor shall submit a report outlining how the changes affect the A-10 TO process and recommendations on how to become compliant. An example includes the MAJCOM mandating a new Document Type Definition (DTD) and becoming S1000D compliant. The Government does not anticipate this task being utilized more than once per year. (CDRL A001)

3.2.1.2 Engineering and Logistics Support

The Contractor shall coordinate with other support entities (ex. TO Integrated Logistics Support

(ILS)) while performing tasks within this PWS. This includes integration with provisioning activities, data cleansing and Product Lifecycle Management (PLM), and organic software and hardware development activities.

3.2.1.3 Technical Support Required for Technical Order Improvement Projects

The Contractor shall investigate methods of improving and streamlining the technical order development process only when directed to do so by the Government. An example of this would be providing internal Quality Assurance (QA) processes to reduce the amount of time required of the equipment specialist to review changes. Another example of this task includes technical order rewrites to accommodate data consolidation and usability improvements. The Government anticipates utilizing this task as much as three times throughout the life of the contract. (CDRL

A002)

3.2.1.4 Trade Studies

The Contractor shall provide trade studies as requested to support PWS technical data efforts.

Examples of trade studies in support of the PWS would include alternate file format investigations, assessments of TMSS specification updates, schedule optimization of BCU with major modifications, and usability studies for alternate presentation devices. The Government anticipates utilizing this task once or twice throughout the life of the contract. (CDRL A003)

3.2.1.5 Technology Roadmaps

The Contractor shall provide technology roadmap as requested to support PWS technical data efforts. An example would include an project plan that addresses USAF tech data technology initiatives over time including Electronic Flight Bag (EFB), Expeditionary Combat Support

System (ECSS) integration, and Portable Maintenance Aid (PMA) upgrades. The Government anticipates utilizing this task once or twice throughout the life of the contract. (CDRL A004)

3.2.1.6 Data and Software Analysis

The Contractor shall provide data and software analysis associated with PWS technical elements including DTD analysis, Formatted Output Specification Instance (FOSI) analysis, schema analysis, and GFI eTO software analysis. The Government anticipates utilizing this task once or twice a year. (CDRL A005)

3.2.1.7 Familiarization

The Contractor shall provide familiarization for new technical order improvements projects as required per paragraph 3.2.1.3. Familiarization shall include all preparation and materials (i.e.

briefings, brochures, aides, etc.) needed to provide familiarization for an estimated four days.

(CDRL A006)

3.2.1.8 Source Data Review

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.

3.2.2 Technical Order Sustainment

The A-10 SPO requires Contractor support to provide updated and accurate A-10 TO production-ready material developed from sustainment, Sustainment Engineering Requirements

Program (SERP), modification, and suite efforts. Support to be provided includes:

A-10 TO and flight manual updates, TCTOs, 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

3.2.2.1 Technical Order Updates

The Contractor shall incorprate incoming changes into final tech order format IAW appropraite

TO specifications.

3.2.2.2 Creation of Technical Data

The Contractor shall convert Government provided technical source data and develop/create new technical orders as required by the A-10 SPO. An example of this type effort was the creation of the 1A-10C-8-1 Computer Program Identification Number (CPIN) TO.

3.2.2.3 Storage and Maintenance of Digital Data

The Contractor shall have the capability to store and maintain all instances/versions of technical orders that have been affected through the TO change processes. Once contract is complete, the

Contractor shall provide all the data stored on the Contractor’s database to the Government.

3.3 SUSTAINMENT DELIVERY

The Contractor shall edit and maintain TOs to support routine, urgent, and emergency changes in both electronic and hard copy IAW TO 00-5-3. (CDRL A007)

3.3.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 Urgent Changes

Urgent changes shall be completed and ready for shipping in five (5) working days.

3.3.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. To meet these requirements, the Contractor shall be capable of completing accelerated delivery to meet an emergency 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 Rapid Action Change (RAC) delivery requirements.

3.3.4 Time Compliance 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-PRF-38804C. The

Contractor QA reviewed TCTOs shall be delivered in the Enhanced Technical Information

Management System (ETIMS) compatible format to the Government. (CDRL A008)

3.3.5 Technical Order Management Authority

All response times shall begin following receipt of the change package from the TOMA. Where clarification is needed, the Contractor will contact the TOMA for direction and technical assistance through the Technical Content Manager (TCM) point of contact.

3.4 BLOCK CYCLE UPDATE (BCU)

The Contractor shall deliver a complete BCU 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 the OO-ALC/GHAEH 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 January, May, and Sepember (CDRL A007)

3.5 RAPID ACTION CHANGE (RAC) 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). (CDRL A007)

3.5.1 Priority out of Cycle Changes

The Contractor shall adhere to Government direction 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 rapid action change (RAC) time limits, they will be processed as Priority Out of Cycle Changes to meet the needs of the end-users. (CDRL A007)

3.6 INTEGRATED MASTER SCHEDULE (IMS)

The Contractor shall publish individual TO change schedules to reflect program milestone accomplishment and change delivery schedules only when parallel efforts coincide with BCU releases. The Contractor shall coordinate and integrate technical data activities as they pertain to all A-10 requirements, including modifications. The IMS shall be updated in real time and include schedule performance. (CDRL A009)

3.7 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.)

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

3.7.2 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).

3.7.3 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).

3.8 ART WORK

The Contractor shall develop and modify line drawings, schematics, and diagrams. Art work shall conform IAW MIL-STD-38784 and be compatible with all deliverable requirements. All new graphics shall be delivered as vectorized CGM files.

3.9 INTERACTIVE VECTORIZED FILES

The Contractor shall develop interative vectorized files in support of intelligent wire/signal tracing products derived from existing A-10 technical order wiring schematics. Functionality will be IAW S1000DIss4.

3.10 ELECTRONIC TOs (eTOs)

The Contractor shall utilize the provided GFE eTO viewing hardware (see appendix C) to support eTO development, transformation and future sustainment. The approved eTO viewing hardware will include an image that reflects the current USAF user software and firmware configuration and updates to Standard Desktop Configuration as generated by the USAF. The

USAF will supply the Contractor with updates as required to the Standard Desktop

Configuration. It shall be the Contractor’s responsibility to use the latest software configuration to stay compliant with the USAF’s Standard Desktop Configuration.

3.10.1 eTO Transformation

For SGML deliverables, the Contractor shall perform transformation for TO files as required to make them compatible with the approved eTO viewer. The Contractor shall participate in USAF panels relating to qualification and testing of the eTO software as required by the PWS requirements.

3.10.2 eTO Stylesheet Maintenance

The Contractor shall modify eTO stylesheets as required to provide proper transformation of TO files and viewing in the approved eTO viewer.

3.10.3 eTO Viewing

The Contractor shall test software as directed on approved eTO viewing hardware to ensure there are no issues, interruptions or software incompatibilities. The Contractor shall certify that all eTOs are rendered in conformance with the Display Formatting Output Specification Instances

(DFOSIs) under the TMSS citations in paragraph 2.0.

3.10.4 Indexed Portable Document Format (IPDF) Creation

The Contractor shall perform updates and create current IPDF files for all A-10 flight and maintenance TOs as required. The Contractor shall validate indexing of PDF TO files using the specifications defined in the USAF Technical Order Conversion Requirements (TOCR) as referenced in the TM-86-01.

3.11 MEETINGS

3.11.1 Kick-off Meeting

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

3.11.2 Bi-Weekly Status

The Contractor shall support bi-weekly telecoms that reflect all aspects of program status, such as document status, development status, completion of applicable IMS milestones and any open issues. (CDRL A009)

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

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

3.11.5 Integrated Product Team (IPT) Meetings

The Contractor shall provide support for technical efforts tasked under this PWS. 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 IAW para 3.11.

3.12 TRAVEL REQUIREMENTS

The Contractor may have to travel in support of the PWS requirements. The Contractor shall inform the Government as soon as available to ensure the most advantageous price may be obtained. The Contractor shall complete the ‘Travel Request Form’ found in appendix D. The form shall go through the TO Program Manager and obtain approval from the Government

Contracting Officer (CO) prior to traveling. Airfare for travel and per diem shall be billed IAW

FAR 31.205-46. The Contractor is responsible for making all necessary travel arrangements.

Actual travel expenses are limited by Government travel regulations. Per year, estimated travel requirements are below, except for the kick-off meeting.

Travel

Requirement

Frequency Travel Length Location Contractor

Personnel

Kick-off Meeting One (1) Trip Five (5) Working

Days

Hill AFB, UT Three (3)

Personnel

TO Rewrite Four (4) Trips Ten (10) Working

Days

Hill AFB, UT Three (3)

Personnel

TO IPT Support Two (2) Trips Five (5) Working

Days

Hill AFB, UT Four (4)

Personnel

CTOM Conference Two (2) Trips Five (5) Working

Days

Hill AFB, UT One (1)

Personnel

FMRC One (1) Trip Five (5) Working

Days

Hill AFB, UT One (1)

Personnel

Familiarization Two (2) Trip Four (4) Working

Days

Hill AFB, UT One (1)

Personnel

4.0 GENERAL INFORMATION

4.1 GOVERNMENT RESPONSIBILITIES

4.1.1 Contract Management

Only the Contracting Officer has authority to make changes affecting this contract. The

Contractor shall not act upon conversations, 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 unless specifically approved in writing by the Government

CO.

4.1.2 Contracting Officer Representative (COR)

The Contracting Officer Representative (COR) is the authorized Government representative who will perform assessments of the contractor’s performance. Subsequent to contract award, a letter identifying the COR and his/her duties and authority will be promptly furnished to the successful offeror.

4.1.2.1 The COR will identify discrepancies and will request corrective action. The COR will make a notation of the discrepancy and resolution.

4.1.3 Government Furnished Information/Equipment (GFI/GFE)

The TOMA will provide a complete and comprehensive update package with all necessary information to complete the tasks within this PWS. Digital source data shall be provided to the

Contractor by the TOMA where available, upon contract award. (Appendix C)

4.2 CONTRACTOR RESPONSIBILITES

The Contractor shall assume responsibility for all technical, schedule, and configuration control program elements for the TO sustainment program.

4.2.1 Quality Management

The Contractor shall have an ISO 9001 certified, 2008 or later, quality assurance program that will ensure deliverables produced as a result of this contract shall meet all Government requirements and stated military specification requirements as identified herein. Unacceptable quality may result in potential safety issues, create work stoppages, and compromise the using activities' ability to accomplish mission objectives; therefore, all work shall be of the highest standards IAW ISO 9001.

4.3 DELIVERABLES

All products developed under this contract shall be considered Government work and shall have no license encumbrances.

4.3.1 CDRLs

The Contractor shall prepare and deliver data in accordance with CDRLs. All Data Item

Descriptions (DID) in the Contractor Data Requirements List, as contained in the following table, shall be used as guides in developing the data.

Distr.

Stmt

CDRL Deliverable Name Data Item Description

(DID)

PWS

Para

D A001

Technical Manual

Research and Analysis

Source Data (Analysis of

TO Mandates)

DI-TMSS-81354 3.2.1.1

D A002

Technical Manual

Research and Analysis

Source Data (TO

Improvement Projects)

DI-TMSS-81354 3.2.1.3

D A003 Scientific and Technical

Reports (Trade Studies)

DI-MISC-80711A 3.2.1.4

D A004

Scientific and Technical

Reports (Technology

Roadmaps)

DI-MISC-80711A 3.2.1.5

D A005 Software Development

Plan (SDP)

DI-IPSC-81427A 3.2.1.6

D A006 Instructional Media

Package

DI-SESS-81526B 3.2.1.7

E A007

Technical Order

Improvement Report and

Reply

DI-TMSS-80229D

3.3, 3.4, 3.5, 3.5.1

E A008

Technical Compliance

Technical Order -

Preparation

MIL-PRF-38804C 3.3.4

Distr.

Stmt

CDRL Deliverable Name Data Item Description

(DID)

PWS

Para

D A009 Integrated Master

Schedule

DI-MGMT-81650

3.6, 3.11.2

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

4.5 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.0 All actions accomplished as per

ISO 9001 with 98 percent accuracy.

Customer Complaint /

Feedback AFTO Form

CDRL Deliverables 3.2.1.1, 3.2.1.3, 3.2.1.4, 3.2.1.5, 3.2.1.6, 3.2.1.7, 3.3, 3.3.4, 3.4, 3.5, 3.5.1, 3.6, 3.11.2

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

100% inspection

Incorporate TO Changes

3.3 Routine Changes

AFTO Form 252 with 95 percent accuracy.

Deficiencies to be corrected to

100 percent within 10 working days.

Urgent Changes

5 calendar days from receipt of

AFTO Form 252 with 95 percent accuracy.

100% Surveillance

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.

Deficiencies to be corrected to

100 percent upon receipt of errors from the TOMA.

5.0 ADMINISTRATIVE

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

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

5.1.2 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, use Air Force Occupational Safety and Health Standard (AFOSH) or applicable nationally recognized sources of safety, health, and fire prevention standards referenced in the work requirements of this contract.

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

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

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

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

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

5.4 PHASE OUT

If there is a change in Contractor or if the operation reverts to organic, the incumbent Contractor will provide familiarization, to the Government or the follow-on Contractor, whichever the case may be. The Contractor shall describe 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. During the phase-out familiarization period, the incumbent Contractor will be fully responsible to provide services as specified within this PWS.

6.0 STATEMENT OF MISSION ESSENTIAL SERVICES

IAW DODI 3020.37, this requirement is not considered mission essential.

APPENDICES

Appendix A - Technical Order Process Plan (Source Data)

Appendix B - Safety, Fire Protection And Health Specification Industrial Safety Requirements

Appendix C – Government Furnished Property

Appendix D – Travel Form

Appendix E – Labor Categories

Appendix F – CLIN 0001 Tasks