RFP_Attachment_12-Performance_Work_Statement.pdf

Attachment 12

Performance Work Statement (PWS) for

A-10 Technical Order Engineering Support

29 March 2016

Rev 1, 12 September 2016

Prepared by:

AFLCMC/WWALE

Fighter/Bomber Directorate

Hill AFB, Utah 84056

CHANGE RECORD

PWS

Section

Pages Revision

TOC 2 1

Acronym 1 1

1.2 2 1

2.1.3 4 1

2.1.5 5 1

2.1.7 6 1

3.0 6 1

3.0.1 6 1

3.1 6-7 1

3.2 7 1

3.2.2 8 1

3.2.3 8 1

3.3.1 8 1

3.3.2.1 9 1

3.3.5 9-10 1

3.4 10 1

3.5 10 1

3.5.1 10 1

3.6 10 1

3.7 10 1

4.0 11 1

4.1 11 1

4.2 11 1

4.3 11 1

4.4 11 1

4.5 12 1

4.6 12 1

4.7 12 1

5.0 13 1

6.0 13 1

6.1 15 1

6.1.4.2 15 1

6.1.5.2 15 1

7.1 16 1

TABLE OF CONTENTS

1.0 INTRODUCTION

1.1 Purpose

1.2 Scope

1.3 Background

2.0 REFERENCE DOCUMENTS

2.1 Government Documents

2.1.1 Department of Defense Specifications

2.1.2 DoD Standards

2.1.3 Other Government Publications

2.1.4 Air Force Instructions and Air Force Material Command Instructions

2.1.5 USAF TOs

2.1.6 Forms

2.1.7 Other Documents

3.0 REQUIREMENTS

3.0.1……Contractor Performance Objectives………………………..……………………….6

3.1 Contractor Requirements

3.2 Technical Order Support Services

3.2.1 Engineering and Logistics Support

3.2.2 Engineering Analysis and Trade Studies

3.2.3 Data and Software Assessment

3.2.4 Technical Support for Technical Order Improvement Projects

3.2.5 Technical Support to Assess Source Data

3.3 Technical Order Sustainment Services

3.3.1 Technical Order Sustainment

3.3.2 Sustainment Delivery

3.3.2.1 Routine Changes…………………………………………………………………..9

3.3.2.2 Urgent Changes……………………………………………………………………9

3.3.2.3 Emergency Changes……………………………………………………………….9

3.3.3 Time Change Technical Order (TCTO) Development Support

3.3.4 Redline Text

3.3.5 Technical Order Development

3.4 Block Cycle Update

3.5 Rapid Action Change Delivery

3.5.1 Priority out of Cycle Changes

3.6 Data Management

3.7 Interactive Wiring Diagrams

3.8 Information Assurance Training and Workforce Management

4.0 MIL-STD-1808/S1000D CONVERSION, MIGRATION, SUSTAINMENT, AND

DATA MANAGEMENT

4.1 MIL-STD-1808 Compliance

4.2 Legacy Data Cleanup

4.3 Quality Control

4.4 Compliance with latest MIL specs……………………………………………………..12

4.5 S1000D Phased Delivery of Data….………………………………………………….. 12

4.6 TeamCenter Data Incorporation………………………………………………………..12

4.7 S1000D/MIL-STD-1808 Training………………………………………………………12

5.0 SERVICE SUMMARY…………………………………………………………………13

6.0 DELIVERY SCHEDULE AND PERIOD OF PERFORMANCE

6.1 Program Management Support

6.1.1 Program Management……………………………………………………………..14

6.1.2 Program Management Plan………………………………………………………..14

6.1.3 Integrated Master Schedule………………………………………………………..15

6.1.4 Transition………...………………………………………………………………..15

6.1.4.1 Phase-In………………………………………………………………………15

6.1.4.2 Phase-Out…………………………………………………………………….15

6.1.5 Meetings…………………………………………………………………………..15

6.1.5.1 Kick-off Meeting……………………………………………………………..15

6.1.5.2 Program Status Review/Technical Interchange Meetings……………………15

6.1.5.3 Technical Order Rewrite/Flight Manual Review Conference (FMRC) Spt….16

6.1.5.4 Integrated Product Team (IPT) Meetings……………………………………16

7.0 SPECIAL CONSIDERATIONS………………………………………………………..16

7.1 Security……………………………………………………………………………….16

7.2 Access to Facilities and Property……………………………………………………..17

7.3 Base Support - Government Provided Office Space………………………………….17

7.4 Government Program and Contract Management…………………………………

7.4.1 Government Program Management……………………………………………..17

7.4.2 Government Contract Management……………………………………………...17

8.0 TRAVEL REQUIREMENTS

9.0 CONTRACTING OFFICER REPRESENTATIVE

ACRONYM LIST

ACO Administrative Contracting Officer

AFI Air Force Instructions

AFMCI Air Force Material Command Instructions

AIS Automated Information Systems

BCU Block Cycle Update

BCR Block Cycle Release

CAC Common Access Card

CDRL Contract Data Requirements Lists

CONOP Concept of Operations

COR Contracting Officer Representative

DoD Department of Defense

DSS Digital Support Suite

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

OFP Operational Flight Program

OOC Out of Cycle Changes

PCO Procurement Contracting Officer (Government)

PCR Proposed Change Request

PLM Product Lifecycle Management

PM Program Manager

PMP Program Management Plan

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, support the goals of AFLCMC/WWALE technical order platforms, and 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 that is acquired, sustained, distributed and available in digital format for all 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 Assessment

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 for resolving complex and sophisticated equipment problems of 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. Finally, they evaluate operational capability of systems/equipment and recommend 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.

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-87929D Work Package 1 Feb 2002 20 Apr 2012

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

MIL-DTL-38384E Checklists and Source

Data Packages, Aircraft

Weapon Delivery

10 Sep 2014

MIL-DTL-38769F Work Unit Codes -

Preparation of

25 Sep 2015

MIL-DTL-38804D Time Compliance

Technical Orders

10 Nov 2014 Amend 1 10 Nov 2014

MIL-DTL-38807D Illustrated Parts

Breakdown

17 Sep 2012

MIL-DTL- 5096G Inspection and

Maintenance

Requirements;

Acceptance and

Functional Check Flight

Procedures and

Checklists; Inspection

Work Cards; and

Checklists

6 Feb 2014

MIL-DTL-5920G Sample Basic Weight

Checklists and Loading

Data

15 May 2015 Amend 1 15 May 2015

MIL-DTL-8031H List of Applicable

Publications (LOAPS) -

Preparation

11 Aug 2014

MIL-DTL-83495D On-Equipment

Maintenance Manual Set

24 Nov 2015

MIL-DTL-9854E Structural Repair

(Aircraft)

10 Jan 2015

MIL-DTL-87268D Manuals, Interactive

Electronic Technical -

General Content, Style, Format, and User-

Interaction Requirements

22 Sep 2014

DoD Standards

Publication

Title Basic Date Latest Chg

Number

Latest Chg

Date

MIL-STD-38784A Standard Practice for

Manuals, Technical:

General Style and

Format Requirements

25 Aug 2011

DLM 4000.25,

Volume 1

Concepts and

Procedures

13 Jul 2012 Change 2 23 Oct 2015

DoDi 5220.22 National Industrial

Security Program

(NISP)

18 Mar 2011

DoDMi 4140.01 DoD Supply Chain

Material Management

Procedures

10 Feb 2014

Other Government Publications

Publication Number Title Basic Date Latest Chg

Latest Chg

Date

MIL-HDBK-38790 Printing Production of

Technical Manuals

24 Feb 1997 Notice 2 19 Jan 2013

MIL-HDBK-863A Handbook for Wiring

Data and System

Schematic Diagrams

Preparation of

13 Oct 2015

PDF Digital Weapons

Checklist Requirements

12 Sep 2016

Air Force Instructions and Air Force Material Command Instructions

Latest Chg

Date

AFMCI 21-401 Engineering Data

Storage, Distribution and Control

12 Mar 2015 30 Mar 2015

AFI 31-101 Air Force Installation

Security Notice (FOUO)

01 Mar 2003 8 Oct 2009

AFMAN 31-116 Air Force Motor

Vehicle Traffic

Supervision

9 May 2012

AFI 16-1404 Information Security

Program Management

29 May 2015

Latest Chg

Date

AFI 11-215 Flight Manuals Program 22 Dec 2008

AFI 63-101/20-101 Integrated Lifecycle

Management

7 Mar 2013 Change 2 18 Sep 2015

AFMCI 23-103 Diminishing

Manufacturing Sources and Materiel Shortages

(DMSMS) Program

13 Oct 2000

AFH 36-2235V2 Information For

Designers Of

Instructional Systems

2 Sep 2002

USAF TOs

Latest Chg

Date

TM-86-01N Technical Manual

Contract Requirements – tailored for the A-10

Program

01 Apr 2009

TO 00-1 United States Air Force

TO Catalog

01 Jul 2004

TO 00-5-1 AF Technical Order

System

01 Oct 2014

TO 00-5-3 AF Technical Order Life

Cycle Management

01 Apr 2015

TO 00-5-15 TCTOs 22 Sep 2014

TO 00-5-18 AF Technical Order

Numbering System

01 Oct 2015

PDF Flight Manual

Hyperlinking

Requirements

12 Sep 2016

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 01 Apr 2001

DD Form 1348-1A Issue Release/Receipt

Document

DoD 4000.25-1-M 1 Jul 1991

AFTO Form 158 Technical Order Review

Comment Sheet

13 Aug 2008

Form Number Form Title Directive

Document

Basic Date

AFTO Form 22 Technical Manual

Change Recommedation and Reply

15 May 2013

AFTO Form 252 Technical Order

Publication Change

Request

27 Jun 2012

Other Documents

Latest Chg

Date

S1000D International

Specification for

Technical Publications utilizing a Common

Source Database

Issue 4.1 1 Aug 2008

MIL-STD-1808C DoD Interface Standard

System Subsystem Sub-

Subsystem Numbering

24 Jan 2014 Change 1 2 Sept 2016

TOCR Technical Order

Conversion

Requirements

Revision 2 17 Oct 2009

TOLCMP Tech Order Life Cycle

Management Plan

25 Feb 2014

Currently, TMSS is not accessible by non-CAC holders. For access to TMSS material, non-

CAC holders shall contact the TO Program Manager requesting the specific material required, and the TO Program Manager will provide the appropriate material. CAC holders will have access to the TMSS website and will be able to maintain a normal relationship with TMSS website and TMSS personnel. The contractor will be granted CACs as required, see Section 7.1.

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.0.1 Contractor Performance Objectives

A-10 SPO will issue task orders for servicies in support of this PWS. When performing individual task orders, the contractor shall utilize an integrated approach to efficiently meet all requirements of each task order.

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 throughout

Section 3. The contractor shall perform tasks in accordance with separately issued task orders, as specified therein.

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

Skill with PTC IsoDraw software

Skill with developing Omnimark scripts and XSL transformations

Skill with Part Number Database (PNDB)

Skill with S1000D formatting, editing, and publishing using viewers such as Arbortext®

IETP

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

The Government will not dictate use of specific software for technical data digitalization, nor will specific software be provided by the Government. Knowledge of programs discussed above is required due to already existing software infrastructures. TO conversion from the currently utilized software to the contractor’s preferred software may be required during the performance of this contract. If the contractor’s software is not the current TO sustainment software, a contractor validation and a government verification shall be required.

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 as identified by individual task order. 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 not limited to:

Engineering and Logistics Support

Trade Studies

Data and Software Assessment

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

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.

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) with major modifications, and usability studies for alternate presentation devices.

Design data and calculations used for Engineering Analysis and Trade Studies shall be documented. (CDRL A004)

Data and Software Assessment

The Contractor shall provide engineering and design expertise in supporting USAF TMSS Digital

Support Suite (DSS) changes, and shall provide recommendations on A-10 TMSS DSS use cases representing Air Force interests. The Contractor shall provide data and software assessment associated with PWS technical elements including document type definition (DTD), formatted output specification instance (FOSI), schema, and GFI software. Design data and calculations used for software assessment shall be documented. (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. (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.

(CDRL A005)

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 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/TO Management Agent (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 IAW TO 00-5-3.

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 task order 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 five (5) working days. The Contractor shall be notified prior to task order issuance identifying an accelerated task 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 task order issuance identifying an accelerated task 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-PRF-38804C. The Contractor

QA reviewed TCTOs shall be delivered in the Enhanced Technical Information Management System

(ETIMS) compatible format to the Government.

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.

Technical Order Development

The Contractor shall create Technical Order data using SGML/XML, or other adopted 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 (aircraft modifications and A-10

Operational Flight Program (OFP) Suite upgrades) into the existing TO baseline maintained in

Enhanced Technical Information Management System (ETIMS). 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 the appropriate specifications and standards. Composed instances shall be compatible with the appropriate TMSS DSS. The Contractor shall prepare and deliver all First Articles Test (FAT) by TMSS at Wright-Patterson AFB for compliance with Air

Force requirements and report findings to the Government. (CDRL A005)

3.4 Block Cycles

The Contractor shall deliver a complete Block Cycle Update (BCU) required by the TOMA as identified by individual task order. 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. A-10 SPO is currently on three (3) Block Cycle Releases (BCR) a year which is subject to change as directed by the TO

Program Manager. The BCRs typically fall on February, June, and October. Because the block cycle timelines overlap, the Contractor shall be required to receive and store files (Government work in progress files - pending Proposed Change Requests (PCR) and attachments) related to the subsequent block cycles.

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) as identified by individual task order. 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 three (3) times during a twelve month period.

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 identified by individual task order. 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-five (25) times during a twelve month period.

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 as identified by individual task order. 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 as identified by individual task order. The Contractor shall provide fully functional interactive wiring diagrams compatible with a standard web browser. (CDRL A005)

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

4.0 MIL-STD-1808 Conversion/S1000D, Migration, Sustainment, and Data

Management

The contractor shall update the current TO Life-Cycle Management Plan (TOLCMP), in accordance with TO 00-5-3, prior to the migration and conversion to MIL-STD-1808/S1000D.

(CDRL A006)

The contractor shall provide a PWS revision to this section (4.0) which will consider requirements as discussed below in sections 4.1-4.7. (CDRL A006)

The Contractor shall convert the current A-10 TO library from SGML to S1000D specifications for publication as identified by individual task order. The contractor shall correct any existing legacy errors or duplication of data as part of the conversion to S1000D.

4.1 MIL-STD-1808 Compliance

The contractor shall migrate the current library up to current MIL-STD-1808 compliance as identified by individual task order. The contractor shall correct any legacy issues to ensure the

MIL-STD-1808, System Subsystem Sub-Subsystem Numbering (SSSN) is implemented correctly and accurately to the entire A-10 maintenance TO library.

4.2 Legacy Data Cleanup

Contractor shall provide a plan for legacy data conversion to ASD S1000D version 4.1 as identified by individual task order. Conversion plan shall provide the following:

a. MIL-DTL-3048, USAF S1000D Business Rules

b. S1000D Business Rules Exchange (BREX)

c. Data module (DM) development and sustainment

d. Data Module Requirements List (DRML) development and sustainment

e. Publication Module development and sustainment

f. Common Source Database (CSDB) Management

g. Legacy applicability tagging that conforms to USAF Business Rules

h. Size of data modules (should be the smallest reusable object, typically follows the break-down of the weapon system’s SNS)

i. Identify potential reuse of data modules

j. Appropriate graphic standard as written by S1000D

k. Distribution and delivery of S1000D

4.3 Quality Control

The contractor shall develop a data validation and reconciliation process to ensure that all required legacy data has been accurately converted to MIL-STD-1808 in USAF compliant

S1000D version 4.1 as identified by individual task order. The contractor shall ensure a comprehensive process that tests the data as it is migrated through different stages to determine whether the converted data is an accurate translation of the existing legacy data sources. (CDRL

A006)

4.4 Compliant with latest MIL Specs.

The contractor shall follow all specification requirements/business rules in S1000D and MIL-

STD-3048 as identified by individual task order. Contractor shall ensure all project level business rules are documented and maintained that cover decision points in S1000D and in MIL-

STD-3048 as well as any other decision point relevant to TO development and delivery for the program.

4.5 S1000D Phased Delivery of Data

The sustainment releases will be combined and incorporated in the first phase of S1000D delivery as identified by individual task order. During the S1000D conversion all modification and sustainment TO changes will be frozen. The second phase delivery will incorporate all aircraft modification and any new sustainment data accumulated during the period while S1000D migration and conversion was in progress. The contractor shall provide all MIL-STD-1808 and

S1000D final data to the government per the Technical Manual Contract Requirements (TMCR) for sustainment after final migration and conversion has taken place. (CDRL A008)

4.6 TeamCenter Data Incorporation

The contractor shall meet the minimum requirements to ensure current data and S1000D data is compatible with USAF TeamCenter PLM environment delivery and creation/updating as identified by individual task order:

A. All S1000D data deliverables in this PWS shall be formatted for import into the A-10

TeamCenter environment using the TeamCenter Content Management module and the

“A-10 Data Exchange Specification” 12-A10DOC-002. Data delivery schedule/frequency requirements are found in the CDRL for each specific task.

a. The contractor shall analyze the A-10 Data Exchange Standard, the TeamCenter

Content Management module requirement and the S1000D requirements to ensure the necessary data elements and structure exist in the A-10 Data Exchange

Specification and the A-10 TeamCenter environment to adequately manage the

TOs and S1000D TO content developed under this effort. The contractor shall propose a implementation plan and changes to the A-10 Data Exchange Standard to be able to store, modify and use these technical orders under CM control in the

A-10 TeamCenter environment (including 252 processing) CDRL (A006).

4.7 S1000D/MIL-STD-1808 Training

The contractor shall provide S1000D MIL-STD-3048, Business Rules/BREX, S1000 Interactive

Electronic Technical Publishing (IETP), and familiarization training for government verification teams as identified by individual task order.

5.0 SERVICE SUMMARY

Performance

Objectives PWS Para. Performance Threshold

Work Performance

Requirements

3.0 All actions accomplished IAW Government-

approved contractor quality assurance plan with

98 percent accuracy.

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.

Incorporated TO

Changes

Routine Changes

AFTO Form 252 with 96 % accuracy.

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

Urgent Changes

5 calendar days from receipt of AFTO Form 252 with 95% accuracy.

Deficiencies to be corrected to 100% 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% accuracy.

Deficiencies to be corrected to 100% upon receipt of errors form the TOMA.

DELIVERY SCHEDULE AND PERIOD OF PERFORMANCE

6.0 Contact Data Requirements Lists (CDRLs)

Paragraph Description CDRL Due Date

6.1.4.2 Conference Agenda A001 2 working days before

milestone/conference/meeting

6.1.4.2 Conference Minutes A002 5 working days after

milestone/conference/meeting

3.3.2, 3.3.3, 3.3.4, , 3.4, 3.5, 3.5.1, 6.1.4.2, Contractor’s Progress, Status, and Management

Report

A003 Bi-weekly, as identified by individual task order

3.2, 3.2.2, 6.1.4.2

Technical Report –

Study/Services

A004 As requested

3.2, 3.2.3, 3.2.4, 3.2.5, 3.3.5, 3.6, 3.7

Scientific and Technical

Report

A005 As requested

Paragraph Description CDRL Due Date

4.0, 4.1-4.7 Program Management Plan

(PWS Revision)

A006 45 calendar days after individual task order award

4.0, 6.1.2, 6.1.2, 6.1.4.1, 6.1.4.2

Program Management

Plan/TOLCMP Update

120 calendar days after contract award and/or as identified by individual task order

6.1.3 Integrated Master Schedule A007 10th of each month for

previous calendar month support

4.5 Technical Manual Contract

Requirements (TMCR)

A008 36 months after task for

S1000D/MIL-STD-1808

migration/conversion has started

6.1 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 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 Status Report shall contain:

1) Progress of the previous month

2) Status of contract milestones

3) Sustainment deliverable schedules status by TO for this 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

6.1.2 Program Management Plan (PMP)

The Contractor shall provide and maintain a PMP. The established PMP shall be updated throughout the program to reflect the current status as identified by individual task order. 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)

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)

6.1.4 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)

6.1.4.2 Phase-Out

If there is a change in Contractor, the incumbent Contractor will provide familiarization, to the

Government and/or the follow-on Contractor. The Contractor’s PMP shall describe a low-risk transition method that will demonstrate the ability to provide the expertise and experience to accomplish the required tasks during the transition with no break in service. The Contractor shall prepare and submit a phase-out transition method that details a clear and orderly transition of workload and responsibility to future Contractor(s) or Government organization. During the phase-out familiarization period, the incumbent Contractor shall be fully responsible to provide services as specified within this PWS through the end of the period of performance. (CDRL A006)

6.1.5 Meetings

6.1.5.1 Kick-off Meeting

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

6.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 Status Report;

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

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

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

6.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 calendar days, or as outlined in the table in Section 7.0 (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.

7.0 SPECIAL CONSIDERATIONS

7.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 may require 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, as directed. 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.

Contractor personnel who will require access to DoD computer network systems and/or require the use of a Common Access Card (CAC) for installation entry control or physical access to facilities during normal business hours when government personnel are present shall request a

CAC through the A-10 TO Program Manager.

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 and/or contractor personnel stop working on this project they shall have 5 business days to terminate all their network user account and to return all access cards and base identification badges.

7.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 working days prior to the need date.

7.3 Base Support – Government Provided Office Space

No base support is anticipated with this contract. All work efforts shall be performed at the

Contractor’s site and/or contractor personnel will spend minimal time at the Government’s location.

7.4 Government Program and Contract Management

7.4.1 Government Program Management

AFLCMC/WWALE will provide the Government TO Program Manager for this contract. The

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

7.4.2 Government Contract Management

Responsibility for contracting activities rests solely with the Government Procurement Contracting

Officer (PCO). 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

PCO.

8.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/S1000D) 3 2 5

TO Rewrite 2 3 5

TO IPT Support 4 2 5

FMRC 1 1 5

PIWG Support 2 1 5

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