F100_PWS_FollowOn_v4_16Oct2023.pdf

CUI

PERFORMANCE WORK STATEMENT (PWS) FOR

TYPE II

INTERACTIVE ELECTRONIC TECHNICAL MANUAL (IETM)

F100-PW-220/220E/229

INTERMEDIATE TECHNICAL MANUALS

PREPARATION DATE: 31 Jan 2023

PREPARING ORGANIZATION: AFLCMC/LPSZB

TINKER AFB, OK 73145-3030

DISTRIBUTION STATEMENT D – Distribution authorized to Department of Defense and U.S. DoD contractors only, Administrative or Operation Use, 22 March 2016. Refer other requests for this document to AFLCMC/LPSZB, Tinker Air Force Base, Oklahoma 73145.

Destruction: When no longer needed, CUI material may be disposed of by any method which will preclude its disclosure to unauthorized individuals TINKER AFB, OK 73145-3030.

Controlled by: AFLCMC Controlled by: LPSZB CUI Category: PROCUR, CTI Distribution/Dissemination Controls: FEDCON POC: Albert DeLeon, albert.deleon@us.af.mil, AFLCMC/LPSZB mailto:albert.deleon@us.af.mil

Table of Contents

SECTION I……………………………………………………………………………….…..3

1.0 Description of Services………………………………………………………………3

1.1 Vision Statement………………………………………………………………………3

1.2 Mission Essential Contractor Services……………………………………………3

1.3 Introduction…………………………………………………………………………….3

1.4 Mission…………………………………………………………………………………..3

1.5 Background……………………………………………………………………………..4

1.6 Scope…………………………………………………………………………………….4

1.7 Task Order Requirement……………………………………………………………..4

1.8 IETM Direct Delivery…………………………………………………………………..4

1.9 Development of Rapid Action Changes…………………………………………...6

1.10 Illustrated Parts Breakdown (IPB) Graphics…………………………………….6

1.11 IETM Direct Support………………………………………………………………….6

1.12 Travel……………………………………………………………………………………7

1.13 Data……………………………………………………………………………………...7

1.14 Engine Automated Work Package (EAWP)………………………………………7

1.15 Conversion S1000D…………………………………………………………………..8

1.16 Deliverables……………………………………………………………………………9

1.17 General Requirements………………………………………………………………10

1.18 CONTRACTOR Key Personnel……………………………………………………..12

1.19 Contract Management Plan…………………………………………………………12

1.20 Quality System and Quality Program Requirements…………………………..12

1.21 Security Requirements………………………………………………………………13

1.22 Data Rights…………………………………………………………………………….13

1.23 Contracting Officer Representative (COR)……………………………………….14

1.24 Response Time………………………………………………………………………..14

1.25 Program Progress Report…………………………………………………………...14

1.26 Hardware and Software Requirements……………………………………………14

1.27 CONTRACTOR Employee General Requirements………………………………15

1.28 Data Delivery…………………………………………………………………………...15

1.29 Transition Periods…………………………………………………………………….15

SECTION II…………………………………………………………………………………….17

2.0 SERVICES SUMMARY…………………………………………………………………..17

Service Summary Table……………………………………………………………………..18

SECTION III…………………………………………………………………………………….20

3.0 GOVERNMENT FURNISHED INFORMATION (GFI)……………………………...…20

Appendix A…………………………………………………………………………………….21 Appendix B…………………………………………………………………………………….26 Appendix C…………………………………………………………………………………….27 Attachment 1 “Contractor Safety Appendix C”…………………………………………28 Attachment 2 “Customer Complaint Record”…………………………………………..33

PERFORMANCE WORK STATEMENT

TYPE II INTERACTIVE ELECTRONIC TECHNICAL MANUAL FOR F100-

PW-220E/229 INTERMEDIATE TECHNICAL MANUALS

02 May 2023

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 Vision Statement

Our goal is to provide the War Fighter the most user friendly, technically accurate digital technical data to the point of use in a media format that meets the mission requirements of the operational user. This must be accomplished while striving to reduce costs without sacrificing safety or quality.

1.2 Mission Essential Contractor Services: N/A

1.3 Introduction

The purpose of this PWS is to specify requirements for sustainment and conversion of GOVERNMENT F100-PW-220, and F100-PW-229 Turbofan Engines, Intermediate Level (I-Level) Technical Orders (TO). Deliveries must comply with applicable military specifications and technical manual requirements for Intermediate Level Maintenance Type II Interactive Electronic Technical Manual (IETM) and S1000D Interactive Electronic Technical Publication (IETP) in the Technical Manual Contract Requirement (TMCR) (MIL-DTL-87268). Tasks include sustainment support for applicable TOs, Recommended Changes (RC), conversion of Type II IETM to S1000D IETP, delivery of Federal Desktop Core Configuration (FDCC) compliant Type II IETM and S1000D IETP and to support distribution of scheduled IETM/IETP Revision Block Cycle Updates (BCU).

See Appendices for definitions of terms and acronyms.

1.4 Mission

Support the warfighters by converting, integrating, and sustaining all technical data to a Department of Defense (DoD) standardized digital format for a Type II IETM and

S1000D IETP.

1.5 Background

DoD initiatives and AFMC Instruction (AFMCI) 63-101, Air Force TO System Implementing Policy, instructs compliance with the AF TO Vision “… to provide user friendly, technically accurate, and up-to-date digital technical data acquired, sustained, distributed, and available in digital format at the point of use from a single point of access for all technical data users.” Tinker AFB’s TO platforms are designed to support the Air Force TO Concept of Operations (CONOPs) providing such digital technical data for multiple engines. Technical data for this IETM has been previously converted and implemented.

1.6 Scope

Standardized digital data must include an integrated installation program capable of providing a complete installation on a stand-alone DoD user's computer without the requirement for network access or installation on local DoD networks. All digital technical data must be accurate and complete in order to support Operational Safety, Suitability and Effectiveness (OSS&E) for each engine Type Model Series (TMS).

1.7 Task Order Requirement

The CONTRACTOR must use MIL-DTL-87268, MIL-DTL-87269, MIL-DTL-38807, MIL-STD-3048 and Technical Manual Contract Requirement (TMCR) as a basis for development of the Type II IETM and S1000D IETP.

There are eight task elements to the PWS:

Task 1 (Contract Line Item Number, (CLIN) X001) – IETM Direct Delivery

Task 2 (CLIN X002) – Development of Rapid Action Changes (RAC)

Task 3 (CLIN X003) – Illustrated Parts Breakdown (IPB) Graphics

Task 4 (CLIN X004) – IETM Direct Support

Task 5 (CLIN X005) – Travel

Task 6 (CLIN X006) – Data

Task 7 (CLIN X007) – Engine Automated Work Package (EAWP)

Task 8 (CLIN X008) – S1000D Conversion

1.8 IETM Direct Delivery (Task 1, CLIN X001)

1.8.1 The IETM is divided into TOs, Work Packages (WP), an Illustrated Parts Breakdown (IPB), and an Engine Automated Work Package (EAWP) that provides necessary instructions for removal, disassembly, cleaning, inspection, repair/replacement and assembly, installation, testing, troubleshooting and documentation.

1.8.2 IETM direct deliveries must consist of four Digital Versatile Disks (DVD’s):

TO 2J-F100-1-6-Compact Disk (CD-1), TO 2J- F100-1-7-CD-1, TO 2J-F100-1-16- CD-1 and TO 2J-F100-1-17-CD-1 (see TMCR). Each BCU delivery must be considered an IETM direct delivery with updates to all TOs listed within each IETM.

The CONTRACTOR must deliver the current IETM configuration. No replacement of IETM software is permitted without Procuring Contracting Officer (PCO) approval.

All software used and necessary to operate IETM/EAWP must have Software and Application Certification Assessments (SACA) certification and be published on the Air Force Evaluated Products List (EPL) prior to deployment. In the case of new software or software revisions, not related to routine IETM application program corrections and enhancements, the CONTRACTOR must contact the GOVERNMENT 120 calendar days prior to planned deployment and assist the GOVERNMENT in the SACA certification/re-certification process. This assistance may include but is not limited to; review of SACA requirements before submission to ensure the IETM meets SACA requirements, incorporation of software corrections as identified by SACA, providing up to date software architecture documentation and any other documentation required as requested by the GOVERNMENT. The CONTRACTOR must deliver the current Computer Software Product End Item (DI- AVCS- 80700A, Contract Data Requirements List (CDRL) A005).

1.8.3 Change requests are considered routine revisions that occur on a BCU for the Intermediate Maintenance Manual (IMM). Change requests (Recommended Changes) must be incorporated within 120 calendar days after receipt by CONTRACTOR. Any Recommended Change (RC) not incorporated after 120 calendar days must require written justification to the Contracting Officer (CO) and COR. The CONTRACTOR must incorporate GOVERNMENT provided RC/redline source data and any RACs from RCs. There must not be more than three errors (i.e., grammar, improper/omitted diagram, inoperative hyper-link) per 100 change pages of RCs. A change page may consist of: (1) Changes authorized by RC/redline source data (defined as a page or sheet that prints from a Source Data Representation (SDR) file created from IETM). (2) Incorporation or modification of graphics per RC. The CONTRACTOR must convert any non-compliant graphics to a Web Computer Graphics Metafile (CGM) upon receipt of an RC. (3) Incorporation of digital photographs per RC. The GOVERNMENT must provide CONTRACTOR digital files to complete this task as required.

1.8.4 IETM Delivery, DVD, must be provided upon BCU completion. The CONTRACTOR must provide: one Record of Incorporated Data (RID) review copy for Pre- Publication Review (PPR). A RID review must be conducted within ten (10) business days and the CONTRACTOR notified of any errors. The CONTRACTOR has five (5) business days, after notification, to correct errors. Upon completion of the RID review and if necessary, subsequent error corrections, the CONTRACTOR must provide three (3) final BCU DVD copies of each engine model (2J-F100-1-6- CD-1, TO 2J-F100-1-7-CD-1, TO 2J-F100-1-16-CD-1 and TO 2J-F100-1-17-CD-1).

1.8.5 A sheet must be defined as a page printed from a Source Data Representation (SDR) file created from IETM. A LOT must be defined as one (1) DVD delivery per TMS (Consisting of three (3) final DVDs each, plus one (1) DVD each of any new or updated CGM graphics in WebCGM format for the 2J-F100-24 and 2J-F100- 54). A LOT is limited to a maximum of 600 SDR change pages per BCU for each TO 2J- F100-1-6-CD-1, TO 2J-F100-1-7-CD-1, TO 2J-F100-1-16-CD-1 and TO 2J-

F100-1-17-CD-1.

1.8.6 The Government must fund three (3) IETMS Direct Deliveries per contract year, to be delivered by Contractor at 120 calendar day intervals.

1.9 Development of Rapid Action Changes (RAC) (Task 2, CLIN X002)

1.9.1 RACs are urgent changes that cannot wait 120 calendar days to be delivered as part of the schedule IETM revision. RACs must be formatted in Index Portable Document Format (IPDF) files that can be embedded as supplements within IETM. The CONTRACTOR must convert and package the RAC as an IETM operational supplement and deliver it via DVD-ROM or secure digital delivery to the GOVERNMENT within three (3) business days from the date the change is received by the CONTRACTOR.

1.9.2 Upon completion of the RAC, the CONTRACTOR must provide instructions, electronically, on how to load the RAC into the current IETM. Errors are to be corrected within three (3) business days after the GOVERNMENT notifies the CONTRACTOR of the error.

1.9.3 A RAC LOT must consist of one RAC that does not exceed five (5) Portable Document Format (PDF) pages of text and illustrations as authored in the RAC development process. RACs exceeding five (5) pages of authoring must be returned to the GOVERNMENT for incorporation during the next BCU.

1.9.4 RACs must include the Step ID’s or Part Number, Figure and Index of where it is to be incorporated.

1.10 Illustrated Parts Breakdown (IPB) Graphics (Task 3, CLIN X003)

Concurrent with every BCU, the CONTRACTOR must deliver on a separate DVD, any new or updated CGM graphics in WebCGM format for the 2J-F100-24 and 2J-F100- 54 manuals contained in their respective IETM. Concurrent with every BCU, the CONTRACTOR must provide a HyperText Markup Language (HTML) (.HTML) report which includes graphic file names that have been added, changed, or deleted. Report to contain the title “IPB CGM Graphics for BCU XXX” (where XXX is the BCU revision number), either “2J- F100-24” or “2J-F100-54”, date the report was created, and three sections; (1) Updated graphics, (2) New graphics, (3) Deleted graphics. Under each section will be a list of graphic file names and the respective Change Driver.

1.11 IETM Direct Support (Task 4, CLIN X004)

The CONTRACTOR must provide IETM support to United States Air Force

(USAF) Bases as required. The CONTRACTOR provides CONTRACTOR personnel for instruction and technical IETM support, to include installation, work situation setups, troubleshooting, education and support, and technical interchange meetings to the USAF. The CONTRACTOR must notify the Contracting Officer or Contracting Officer Representative, regarding the IETM problem(s), in the next scheduled program progress report, after responding to IETM field support. (DI-MGMT-80555A, CDRL A003).

1.12 Travel (Task 5, CLIN X005)

1.12.1 Travel/Temporary Duty (TDY) - CONTRACTOR must travel in support of PWS requirements upon approval by the PCO. The CONTRACTOR must be advised of dates of travel as soon as available to the Government, minimum of seven working days prior to travel required, so the most advantageous prices may be obtained. Prior to travel, Contractor must prepare and submit to Government an estimate containing the number of days required for travel, number of personnel and method of transportation. Costs must be reimbursed in accordance with the Joint Travel Regulation (JTR) in effect at the time of performance of the travel. Receipts must be presented to PCO prior to invoicing for reimbursement of actual travel costs. Specific travel is not limited to but may include Guidance Conference, Technical Interface Meeting (TIM), Technical Support, Fact Finding, Meeting/Conference Support, EAWP review and oversight, Photoshoots, Field Service Evaluations (FSE), IETMS Setup/Troubleshooting and IETM Education and Support.

1.13 Data (Task 6, CLIN X006)

The CONTRACTOR must furnish data in accordance with CDRLs (Appendix B), DD Form 1423, hereto. The CLIN is not separately priced; its cost is included in CLINs X001 thru X004.

1.14 Engine Automated Work Package (EAWP) (Task 7, CLIN X007)

1.14.1 EAWP is integrated into the IMM and allows users to electronically document engine maintenance at Jet Engine Intermediate Maintenance (JEIM) facilities. An EAWP must document engine maintenance during Jet Engine Intermediate Maintenance (JEIM) in accordance with DAFI 21-101 Section 4.11 Propulsion Flight.

1.14.2 The CONTRACTOR must provide a detailed testing plan when changes to the EAWP are required by the government.

1.14.3 Change requests for EAWP Electronic Work Packages (EWP) (on RC) must be incorporated within 120 calendar days after receipt by CONTRACTOR.

Any change request not incorporated after 120 calendar days must require written justification to the CO or COR.

1.14.4 A change will consist of change pages authorized by RC/redline source data (defined as a page that prints from Source Data Representation (SDR) file created from IETM).

1.14.5 The CONTRACTOR must incorporate GOVERNMENT provided RC/redline source data.

1.14.6 There must not be more than one error (i.e., grammar, inoperative hyper-link) per 25 change pages of the RCs.

1.15 Conversion S1000D (Task 8, CLIN X008)

1.15.1 On request from the USAF, the CONTRACTOR will convert the current F100 IETM in incremental phases (Phase I – 229, Phase II – 220, Phase III – EAWP) as determined by the Government to MIL-STD-3048 and Aerospace and Defense Industries Association of Europe (ASD)-S1000D. Issue 4.1 compliant S1000D Interactive Electronic Technical Publication (IETP) using AF and F100 Program Business Rules/Schema and functionality matrix (Decision Point Tool).

The CONTRACTOR shall deliver sample data, data modules, all required BREX and graphics at (frequency to be determined) to assess source data compliance using the Technical Order Authoring and Publishing (TOAP) Vendor In-Process Review (VIPR) System. GOVERNMENT will provide to CONTRACTOR the AFT3 validation tool for download to ensure that deliverables are MIL-STD-3048 and S1000D Issue 4.1 compliant. CONTRACTOR shall provide validation reports in conjunction with the deliverables. The CONTRACTOR must ensure the final delivery TO configuration will include all TO changes contained in the Legacy IETM. The contractor will develop skins and functionality to satisfy all F-100 program functional requirements. (DI-TMSS-81818, CDRL A006) (DI-TMSS-81819A, CDRL A007)

1.15.2 The CONTRACTOR’s support of the S1000D Data Conversion must include the development of business rules associated with the specification, conversion of the technical data, IETP Software and Application Certification Assessments (SACA) Certification, and development and integration of the interactive functionality into the CONTRACTOR’s standard IETP viewer. Table A outlines the expectations of the S1000D Conversion process. (DI-TMSS-

81951, CDRL A008)

1.15.3 Deliverables – See paragraph 1.16.2 for required S1000D IETP deliverables.

Table A – Expectations for S1000D Conversion

Conversion must be to the S1000D Issue 4.1 IAW MIL-STD 3048.

Data delivery shall be MIL-STD-3048 compliant S1000D source data, BREX, graphics file and S1000D IETP A master schedule must be developed between Pratt & Whitney (P&W) and United States Government (USG) for Technical Data conversion.

Illustrated Part Breakdown (IPB) must be converted in accordance with final IPB solution that accepts and displays compatible S1000D source data.

The Contractor must complete milestones and provide deliverables in accordance with F100 Master Schedule.

Converted Technical Data must be fully functioning and have all current capabilities and interoperability as defined in the functionality matrix.

The Contractor must provide a proof-of-concept demonstration of S1000D IETP to USG for approval.

The Contractor must conduct quality review of converted technical data prior to USG final delivery.

The Contractor will support in-person validation and verification as required.

Convert current F100 Interactive Electronic Technical Manual (IETM) to S1000D IETP format using business rules and schema developed during S1000D effort and MIL-STD-3048B as a guide by leveraging current P&W S1000D resources.

Ensure solution can be utilized on the .mil network and comply with SACA certification requirements.

Provide beta copy for SACA certification and update software as required to pass certification.

1.16 Deliverables

CONTRACTOR is required to establish Direct Delivery schedule for Tasks 1, 3 and 8 (IETM Direct Delivery, IPB graphics and S1000D Conversion) publication dates.

In the event the CONTRACTOR cannot comply with the schedule, the CONTRACTOR must submit, in writing, a request for extension to the Contracting Officer, and AFLCMC/LPSZB Technical Order Management Agent/Agency (TOMA). No extension must be granted to any date which is more than 15 business days past the milestone scheduled delivery date. See Appendix C for 120-day milestone BCU schedule.

1.16.1 Direct Delivery - The CONTRACTOR must provide to the GOVERNMENT a direct delivery BCU of an updated Type II IETM Engine Intermediate Maintenance Manual (IMM) for the F100-PW-220/220E/229 (2J-F100-1-6-CD-1, TO 2J-F100-1-7-CD-1, TO 2J-F100-1-16-CD-1, TO 2J-F100-1-17-CD-1) within 120 calendar days after receipt of RCs. Data must include changes per RC/redline markups and IPB graphics. Each DVD must include all TOs as defined on the TMCR. Graphics must include all graphics as defined in Task 3.

1.16.1.1. Deliverables must include:

• One (1) RID review copy and three (3) final copies of TOs 2J-F100-1-6-CD-1, TO

2J-F100-1-7-CD-1, TO 2J-F100-1-16-CD-1 and TO 2J-F100-1-17-CD-1 in DVD format.

• In conjunction with every BCU, after the RID Review, the CONTRACTOR must deliver the following on separate DVD:

• 2J-F100-24, Updated/changed Graphics and IPB Report

• 2J-F100-54, Updated/changed Graphics and IPB Report

1.16.1.2. After GOVERNMENT receipt of the final copies, there must be no more than three errors (i.e., grammar, improper/omitted diagram, inoperative hyper-link) per 100 change pages. This includes the IMM (2J-F100-1-6-CD-1, TO 2J-F100-1-7-CD-1, TO 2J-F100-1-16-CD-1 and TO 2J-F100-1-17-CD-1), IPB Graphics (2J-F100-24 and 2J-F100-

54) and S1000D IETPs (2J-F100-1-16-CD-1 and 2J-F100-1-17-CD-1). Errors identified by the GOVERNMENT must be corrected within three (3) business days.

1.16.2 S1000D IETP - The CONTRACTOR must provide to the GOVERNMENT a direct delivery BCU consisting of one (1) RID review copy and three (3) final copies of two (2) fully functioning S1000D IETP CD/DVDs for the F100-PW-220/220E/229 (2J-F100-1-16- CD-1 and 2J-F100-1-17-CD-1) within 120 calendar days after receipt of RCs. Data must include changes per RC/redline markups and IPB graphics. Each DVD must include all TOs as defined on the TMCR. It is the Government’s intent to develop electronic distribution of IETP via ETIMS in the future. The conversion effort shall take this into consideration. (Task 8)

1.16.3 EAWP - The CONTRACTOR must deliver an updated EAWP for all IETM/IETP CDs (2J-F100-1-6-CD-1, 2J-F100-1-7-CD-1, 2J-F100-1-16-CD-1 and 2J-F100-1-17-CD-1) in conjunction with the direct delivery (BCU). The EAWP is integrated into TOs contained within 2J-F100-1-6-CD-1, TO 2J-F100-1-7-CD-1, TO 2J-F100-1-16-CD-1 and TO 2J-F100-1-17-CD-1 and delivered on the same DVD (Task 7).

1.16.4 RACS - The CONTRACTOR must deliver Rapid Action Changes (RAC’s) via DVD-ROM or secure digital delivery. Method of delivery will be determined by TOMA at time of requirement. (Task 2)

1.17 General Requirements. General requirements apply to all task orders unless otherwise stated.

1.17.1 Place of Performance - Services outlined in this PWS must be performed at the CONTRACTOR Facility and all deliverables, in traceable means, delivered at destination, Tinker AFB, Oklahoma.

1.17.2 Hours of Operation - The CONTRACTOR is responsible for conducting business and must be available for technical assistance between the hours of 8 a.m. – 4 p.m. Central Standard Time (CST) Monday through Friday except Federal holidays and when the GOVERNMENT facility is closed due to local or national emergencies, administrative closings, or similar GOVERNMENT directed facility closings. The CONTRACTOR must always maintain a workforce for uninterrupted performance and continuity of services of all tasks outlined within this PWS.

1.17.3 CONTRACTOR Labor Hours – The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The contractor is required to completely fill in all required data fields in the Service Contract Report (SCR) at https://www.SAM.gov/.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September.

While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the SAM.gov service desk.

1.17.3.1 Uses and Safeguarding of Information – Information from the secure https://www.sam.gov/ website is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor’s name and contract number associated with the data.

1.17.4 CONTRACTOR Personnel - The CONTRACTOR must not employ persons for work on this contract if such employee is identified to the CONTRACTOR by the Contracting Officer as a potential threat to the health, safety, security, well-being or operational mission of the installation and its population. The selection, hiring, assignment of duties, reassignment of duties, transfer, supervision, management, control and termination of CONTRACTOR employees in performance of this PWS must be the responsibility and prerogative of the

CONTRACTOR.

1.17.5 CONTRACTOR Employee Requirements (Reference Federal Acquisition Regulation (FAR) 37.114) - The CONTRACTOR must identify themselves as a CONTRACTOR when attending meetings, answering GOVERNMENT telephones and working in other situations where their CONTRACTOR status is not obvious to third parties (e.g., clients, vendors, customers, public contacts, etc.) to avoid creating an impression in the minds of members of the public or Congress that they are GOVERNMENT officials. The CONTRACTOR must also ensure that all documents or reports produced by the CONTRACTOR are suitably marked as CONTRACTOR products or that CONTRACTOR participation is appropriately disclosed.

1.17.6 Sub-Contractor Management - The Prime CONTRACTOR may

subcontract portions of individual task orders to Sub-Contractor(s) based upon areas of expertise to establish a strong technical capability to meet diverse task order requirements. The Prime CONTRACTOR must maintain responsibility for all aspects of task order performance and oversight, regardless of any arrangement between the Prime and its Sub-Contractors.

1.17.7 Organizational Conflict of Interest (OCI) - CONTRACTOR and Sub- Contractor personnel performing work under this contract may receive, have access to, or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications, or work statements, etc.) or perform evaluation services which may create a current or subsequent OCI as defined in FAR Subpart 9.5. The CONTRACTOR must notify the PCO immediately whenever they become aware that such access or participation may result in any actual or potential OCI and must submit a plan within five (5) business days to the PCO to avoid or mitigate any such OCI. The CONTRACTOR’S mitigation plan must be determined to be acceptable solely at the discretion of the PCO, and in the event the PCO unilaterally determines any such OCI cannot be satisfactorily avoided or mitigated, the PCO may affect other remedies as necessary, including prohibiting the CONTRACTOR from participation in subsequent contracted requirements which may be affected by the OCI.

1.17.8 CONTRACTOR Employees - The CONTRACTOR must not employ any person who is an employee of the U.S. GOVERNMENT. Additionally, the CONTRACTOR must not employ any person who is an employee of the Department of the Air Force, either military or civilian, unless such person seeks and receives approval according to DoD 5500.7 Standards of Conduct. The CONTRACTOR must not employ any person who is an employee of the Department of the Air Force if such employment would be contrary to the policies in Air Force Instruction (AFI) 64-106 (Air Force Industrial Labor Relations Activities).

1.18 CONTRACTOR Key Personnel - The CONTRACTOR must provide a list of key personnel (i.e., contract manager/alternate contract manager, technical support, etc.) to the PCO and Contracting Officer’s Representative (COR) no later than five

(5) business days after contract execution. The CONTRACTOR must notify the Government of any change in Contractor key personnel within five business days of the effective change. The CONTRACTOR must provide personnel who must be responsible for the performance of the tasks outlined in this PWS and who must have full authority to act for the CONTRACTOR on all matters relating to daily operation of this contract. Personnel responsible must be available between 8 a.m.

– 4 p.m., CST Monday through Friday except Federal holidays and when the GOVERNMENT facility is closed due to local or national emergencies, administrative closings, or similar GOVERNMENT directed facility closings.

1.19 Contract Management Plan - The CONTRACTOR must provide a Contract

Management Plan to the PCO and/or COR for review at least ten (10) business days after the performance start date describing the technical approach, organizational resources and management controls to be employed to meet the cost, performance and schedule requirements throughout contract execution. The Contract Management Plan must be considered a living document and must be updated to reflect the status of the program. At a minimum, the plan must include:

(DI-MGMT-80004A, CDRL A001).

• Technical approach

• System Backup and Disaster Recovery Plan

• Issues/concerns and associated recommendations

• Delivery Schedule requirements

• Security/data breach

1.20 Quality System and Quality Program Requirements - The Contractors must ensure prepared TOs are a) technically accurate and safe; b) written to a scope and depth of coverage to support the operations and maintenance concepts; c) properly classified and marked with export control and distribution limitation statements. The Contractor must maintain a Technical Manual Quality Assurance (TMQA) Program Plan for this effort. The TMQA Program Plan must be available for review at the TO Guidance Conference. The TMQA Program Plan must be sufficiently detailed to support TO certification to include actual performance of procedures or desk-top analysis for non-procedural data. Simulation (walk-through/talk-through) should be reserved for those procedures which would activate explosive devices or present a hazard to personnel or equipment. (DI-

TMSS-81817, CDRL A004).

1.20.1. Initial Technical Order Guidance Conference (TOGC) - Working through the TOMA, the Contractor must co-host and participate in a guidance conference for this effort. The TOGC will be held within 60 calendar days after contract award.

The Technical Manual Schedule and Status will be formalized at this conference.

The Contractor must present a briefing on their interpretation of the basic contract, SOW/Performance Work Statement (PWS), CDRLs, Data Item Description (DIDs), MIL-SPEC, MIL-STD, SIRs, this document and the planned preparation and delivery of the TOs and related data.

1.20.2. GOVERNMENT Quality Assurance (QA) Surveillance Support - The CONTRACTOR must support GOVERNMENT QA surveillance to periodically evaluate the CONTRACTOR’S performance in accordance with the GOVERNMENT’S Quality Assurance Surveillance Plan (QASP). For those requirements listed in Section II, Service Summary, QA Personnel must follow methods of surveillance specified in the QASP. The COR is the GOVERNMENT’S authorized PCO representative and must participate in the verification/review of this contract.

1.20.3. Customer Complaint Record Template - When the CONTRACTOR receives a Complaint Record from the COR, the CONTRACTOR must initial next to the defective performance observation indicating acknowledgment of deficiency on the Customer Complaint Form. The CONTRACTOR must complete the Customer Complaint Form and return the complaint form within five business days after receipt.

1.21 Security Requirements

1.21.1. Physical Security - As a result of the preparation of TOs taking place, the CONTRACTOR must maintain back-up in traceable locations at the CONTRACTOR Facility.

1.21.2. Disaster Recovery - The CONTRACTOR must utilize a proven Document Management system to store, control, and issue versions of GOVERNMENT source data and maintain historical copies. The CONTRACTOR must establish and maintain a Disaster Recovery Program to backup, at a location other than the work site, and protect GOVERNMENT source and illustration data.

1.22 Data Rights - Contractors must comply with 10 U.S.C. 2320 and cognizant

Defense Federal Acquisition Regulation Supplement (DFARS) provisions and clauses in providing Unlimited Rights for all source data, TO publications and TO updates prepared specifically for the contract. The Contractor must pass through and enforce all requirements in this TMCR to all sub-Contractors.

1.22.1 GOVERNMENT Distribution - The CONTRACTOR must provide the GOVERNMENT unlimited rights to distribute the Type II IETM and S1000D IETM to all authorized users of Propulsion Technical Data. This includes, but not limited to, contractors and international users that have procured U.S.

based weapon systems through the United States GOVERNMENT.

1.22.2 CONTRACTOR Distribution - The CONTRACTOR must comply with the distribution and destruction statements on all TO Title Pages. All media containing data and materials supplied to the GOVERNMENT must be the sole property of the GOVERNMENT. CONTRACTOR must deliver updated Jet Engine Intermediate Maintenance (JEIM) Technical Orders via the P&W IETM system, which includes the GOVERNMENT funded Federal Desktop Core Configuration (FDCC) compliant TYPE II IETM, to support the distribution schedule IETM Revision Block Cycle Updates (BCU), see Appendix C.

1.23 Contracting Officer Representative (COR) - The COR must be identified in a designation letter. “Contracting Officer's Representative,” means an individual designated in accordance with subsection 201.602-2 of the Defense Federal Acquisition Regulation Supplement and authorized in writing by the PCO to perform specific technical or administrative functions. If the PCO designates a COR, the CONTRACTOR must receive a copy of the written designation. It must specify the extent of the COR's authority to act on behalf of the PCO. The COR is not authorized to make any commitments or changes that must affect price, quality, quantity, delivery, or any other term or condition of the contract. The COR monitors all technical aspects of the contract and assists in contract administration.

The COR is not authorized to change any of the terms and conditions of the resulting order.

1.24 Response Time - The CONTRACTOR must respond to CO or COR for all requests for assistance from customers within the following timeframe: Emergency and Work Stoppage – Respond within 24 hours after receipt of notification.

1.25 Program Progress Report - The CONTRACTOR must develop and maintain processes to evaluate and monitor progress made by the CONTRACTOR in accomplishing the requirements of this PWS. The CONTRACTOR must develop, maintain, and deliver a Program Progress Report to align with the three 120-day BCU deliveries per year schedule. The report must include RC number, TO number, including when applicable, TO page supplement numbers, estimated number of pages, change number and date, and digital tech order DVD delivery revisions delivery date, order number, applicable notes and Publication Change Request due date. The TO Status and Schedules Report must include all requirements received from the cutoff date of the last 120 Day BCU to the cutoff date of the next 120-day BCU delivery. Report must list all change requests (RCs) not incorporated from previous BCU or pending incorporation with reason for non-incorporation. (DI-MGMT-80555A, CDRL A003).

1.26 Hardware and Software Requirements - The CONTRACTOR is required to provide a notification to AFLCMC/LPSZB for “minimal system requirements” and for network and any other applications. This notification must be submitted ten (10) business days after the date of contract award. The IETM database and S1000D IETP must be able to run on systems which are configured with latest government approved Microsoft operating systems for standard desktop operation. Future Federal Desktop Core Configuration changes must be provided by AFLCMC/LPSZB. If future changes impact the IETM or S1000D software that require modification of the software to keep it in compliance with the Federal Desktop Core Configuration, then the CONTRACTOR must complete the modification.

1.27 CONTRACTOR Employee General Requirements

1.27.1 The CONTRACTOR must:

• Be responsible for all work performed under this PWS.

• Provide in writing to the PCO, within ten (10) business days after contract award, the names and telephone numbers of Contract Manager.

• Select, hire, assign duties, reassign duties, transfer, supervise, manage, control, and terminate CONTRACTOR employees in performance of this

PWS.

• Maintain a program management structure to accomplish administrative planning and integration of program requirements to optimize workflow actions by organizing, directing, and controlling overall program requirements, to include the following:

• Be available, to be contacted by email or telephone during business hours to discuss and resolve critical issues pertaining to the services provided and to perform work on the installation if approved by the PCO.

• Support conference calls as coordinated by the PCO with all necessary parties.

• Establish and maintain a risk management program for the purpose of early identification of program risk and mitigation of risk such that contract performance is not impacted.

1.28 Data Delivery - All technical order data must be delivered by secure traceable means, such as a shipping/tracking number, and delivered at designated destination in the contract.

1.29 Transition Periods - The CONTRACTOR must ensure a transition is accomplished during both the phase in and phase-out periods as follows:

1.29.1 Phase-In-Period Requirements - During the thirty (30) day phase-in transition period the CONTRACTOR must:

• Complete workforce requirements, including hiring of personnel, to assure satisfactory performance beginning on the contract start date in accordance with PWS.

• Complete an inventory of GOVERNMENT furnished source data.

• Complete the phase-in joint inventory no later than ten (10) business days prior to the end of the phase-in-period.

• The CONTRACTOR and a GOVERNMENT COR must conduct an inventory of all data. The CONTRACTOR must notify the Contracting Officer in writing within five (5) business days upon completion of the inventory. The CONTRACTOR must provide an inventory report identifying the accuracy and condition of the data provided by the GOVERNMENT, as well as any missing or unsuitable data.

1.29.2 Phase-Out Period Requirements - The CONTRACTOR must be responsible for all work performed under this PWS during the phase-out- period.

The CONTRACTOR must ensure the following phase-out requirements are accomplished within sixty (60) calendar days prior to contract end date. The CONTRACTOR must cooperate fully to permit an orderly changeover of the workload and delivery of GOVERNMENT owned data. The CONTRACTOR must participate and complete the phase-out joint inventory no later than ten (10) business days prior to the end of the last performance period.

SECTION II

2.0 SERVICES SUMMARY - CONTRACTOR service requirements are

summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

2.1 The purpose of this section is to:

a. List contract requirements considered most critical to acceptable contract performance.

b. Show the maximum allowable degree of deviation from perfect performance for each requirement, and an Acceptable Quality Level (AQL) that must be allowed by the GOVERNMENT before contract performance is considered unsatisfactory.

SERVICE SUMMARY TABLE

Performance Requirement PWS Paragraph

Requirement Threshold

SS-1 The CONTRACTOR must deliver an updated Type II IETM, direct delivery BCU, for F100-PW-

220/220E/229 (2J-F100-1-6-CD-1, TO 2J-F100-1-7-

CD-1, TO 2J-F100-1-16-CD-1 and TO 2J-F100-1-17- CD-1) Engine Intermediate Maintenance Manual (IMM) data content in SGML/HTML per Recommended Change (RC)/redline markups and IPB graphics. Each DVD must include all TOs as defined on the TMCR.

Deliverables must include one (1) RID review copy and three (3) final copies of TOs 2J-F100-1-6-CD-1, TO 2J-F100-1-7-CD-1, TO 2J-F100-1-16-CD-1 and TO 2J-F100-1-17-CD-1 in DVD format.

In conjunction with every BCU, after the RID Review, the CONTRACTOR must deliver the following on separate DVD:

2J-F100-24, Updated/changed Graphics and IPB Report 2J-F100-54, Updated/changed Graphics and IPB Report

1.16.1 & 1.16.1.1

Documents delivered within 120 calendar days of receipt of Recommended Changes (RCs).

No more than three errors (i.e., grammar, improper/omitted diagram, inoperative hyper-link) per 100 change pages corrected within three business days

SS-2 The CONTRACTOR must provide to the GOVERNMENT a direct delivery BCU consisting of one (1) RID review copy and three (3) final copies of two (2) fully functioning S1000D IETP CD/DVDs for the F100-PW-220/220E/229 (2J-F100-1-16-CD-1 and 2J-F100-1-17-CD-1) within 120 calendar days after receipt of RCs. Data must include changes per RC/redline markups and IPB graphics. Each DVD must include all TOs as defined on the TMCR.

1.16.2 Documents

delivered within 120 calendar days of receipt of Recommended Changes (RCs).

No more than three errors (i.e., grammar, improper/omitted diagram, inoperative hyper-link) per 100 change pages corrected within three business

SS-3 - The CONTRACTOR must deliver an updated EAWP for CDs (2J-F100-1-6-CD-1, TO 2J-F100-1-7-CD-1, TO 2J-F100-1-16-

CD-1 and TO 2J-F100-1-17-CD-1) in conjunction with the direct delivery (BCU).

The EAWP is integrated into TOs contained within 2J-F100-1-6-CD-1, TO 2J-F100-1-7- CD-1, TO 2J-F100-1-16-CD-1 and TO 2J- F100-1-17-CD-1 and delivered on the same

DVD.

1.16.3 No more than one

error (i.e., grammar, inoperative hyper-link) per 25 change pages, correctable within three business days

SS-4 RACS - The CONTRACTOR must deliver Rapid Action Changes (RACs) on DVD-ROM or by secure digital delivery.

Method of delivery will be determined by TOMA at time of requirement.

1.16.4 No more than one

error (i.e., grammar, improper/omitted diagram, inoperative hyper-link) per RAC, correctable within one business day.

SECTION III

3.0 GOVERNMENT FURNISHED INFORMATION (GFI)

All data provided by the Government to the Contractor for the Contractor to input and process will always remain the property of the Government. Technical data input and processed during the performance of task order(s) must always be maintained in a readable and readily retrievable format. All media containing software provided under this contract must become the property of the government.

The contractor may not use or disclose data provided by the Government for any purpose or in any manner not specifically authorized or required by the task order.

APPENDIX A – GLOSSARY

ADMINISTRATIVE CONTRACTING OFFICER (ACO): “Administrative contracting officer (ACO)” refers to a contracting officer who is administering contracts.

CHANGE PAGE: A TO page that has been changed because of a Recommended Change (RC); any change to a page from one word to the entire page to include tables and/or illustrations.

COMPUTER SOFTWARE: Computer programs, source code, source code listings, object code listings, design details, algorithms, processes, flow charts, formulae and related material that would enable the software to be reproduced, recreated, or recompiled, but excludes computer databases or computer software documentation (see DFARS 252.227-7014(a)(4)). This definition does not expressly mention firmware as being a type of computer software. Nevertheless, the software portion of firmware is encompassed by the broad definition of the term “computer program” i.e., “a set of instructions, rules, or routines recorded in a form that is capable of causing a computer to perform a specific operation or series of operations.”

CONTRACTING OFFICER (CO): A person with the authority to enter into, administer, and/or terminate contracts and make related determinations and findings. The term includes certain authorized representatives of the contracting officer acting within the limits of their authority as delegated by the contracting officer.

CONTRACTING OFFICER'S REPRESENTATIVE (COR): An individual, including a contracting officer’s technical representative (COTR), designated and authorized in writing by the contracting officer to perform specific technical or administrative functions. This individual has authority to provide technical direction to the CONTRACTOR if that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

CONTRACTOR: A supplier or vendor awarded a contract to provide specific supplies or service to the GOVERNMENT. The term used in this contract refers to the prime.

DELIVERABLE: Anything that can be physically delivered and may include non-manufactured things such as meeting minutes or reports.

DOCUMENT TYPE DEFINITION (DTD): A DTD clearly defines the structural components (SGML tags) of a TO in terms of elements, attributes and entities; for titles, paragraphs, tables, graphics, footnotes, etc. A specific DTD defines the structure of a TO type based on the governing specification. An SGML TO document (instance) is produced by inserting SGML tags into the document unformatted text, following the constructs (rules) of the specific TMSS DTD.

CUI

ENGINE AUTOMATED WORK PACKAGE (EAWP): EAWP integrated into the IMM and allows users to electronically document engine maintenance at Jet Engine Intermediate Maintenance (JEIM) facilities.

ENTERPRISE INFORMATION TECHNOLOGY DATA REPOSITORY (EITDR): The EITDR provides automated Information Technology (IT) Portfolio Management and other IT management processes, a common access point to gather, view, load, update, query, report and store pertinent data from disparate systems needed to complete their individual missions.

EITDR serves as a single point of user entry for Air Force (AF) IT data and has electronic interface to other DoD/AF systems requiring the data.

GOVERNMENT FURNISHED INFORMATION: GFI lists and describes data and information in the possession of or acquired by the GOVERNMENT and made available to the CONTRACTOR.

INTERACTIVE ELECTRONIC TECHNICAL MANUAL (IETM): An “information oriented” digital technical manual whose format and style are optimized for computer presentation. IETM organization facilitates easy user access to technical information while the display device provides interactive procedural guidance, navigational directions, and supplemental information. An IETM facilitates the interchange of maintenance manual information with logistic support data supplemental to maintenance, such as maintenance data collection, training documentation, supply interface and data presentation control.

INTERACTIVE ELECTRONIC TECHNICAL PUBLICATION (IETP): A set of information needed for the description, operation and maintenance of the S1000D Product, optimally arranged and formatted for interactive screen presentation to the end user on an electronic display system.

INDEXED PORTABLE DOCUMENT FORMAT (IPDF): Permits indexing so user can move quickly between TO chapters, sections, figures, and tables, or move to specified words or character strings.

KEY PERSONNEL: CONTRACTOR personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS.

LOT: All the deliverables associated with an indicated performance objective.

MARKUP: Any addition, deletion, or change to the content of the TO.

PERFORMANCE OBJECTIVE: Outcome associated with successful contract performance in a specific area. This is a critical success factor in achieving the organization’s mission, vision and strategy, which, if not achieved, would likely result in a significant decrease in customer satisfaction or risk mission failure. Obtaining multi- services/sub-services performed at a certain measurable standard and consistently ensures success in achieving critical mission objectives.

PERFORMANCE THRESHOLD: Minimum performance level of a performance objective required by the GOVERNMENT.

PHYSICAL SECURITY: Actions preventing loss or damage of GOVERNMENT property and/or GFI.

PROCURING CONTRACTING OFFICER (PCO): A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the GOVERNMENT. Note: The only individual who can legally bind the GOVERNMENT. The CONTRACTOR must submit in writing to the PCO any issues such as: extensions, conflict of interest, etc. The PCO must be identified at the Guidance Conference.

RAPID ACTION CHANGE (RAC): Priority changes to TOs, issued to resolve deficiencies of an Emergency or Urgent nature (see TO 00-5-1) that cannot wait for the next scheduled BCU. A RAC is normally no more than 5 pages.

QUALITY ASSURANCE (QA): GOVERNMENT procedures verifying services being performed by the CONTRACTOR are performed according to acceptable standards.

QUALITY ASSURANCE SURVEILLANCE PLAN (QASP): An organized written document specifying the surveillance methodology used for surveillance of CONTRACTOR performance.

QUALITY CONTROL: All necessary measures taken by the CONTRACTOR to ensure the quality of an end product or service meets contract requirements.

STANDARD GENERALIZED MARKUP LANGUAGE (SGML): (MIL-PRF-28001).

SGML is a computer-processable syntax for describing the logical and content structures of a document. Using an SGML document type definition (DTD), a specification can rigorously and strictly define the structure of a class of documents such as job guides, flight manuals, fault isolation procedures, etc. SGML describes the format and structure of the text in a document, not how the document must appear as an output.

TASK ORDER: An order for services placed against an established contract or with GOVERNMENT sources.

TECHNICAL DATA: Recorded information, regardless of form or method of recording, of scientific or technical nature (including computer software documentation), excluding computer software or data incidental to contract administration, such as financial and/or management information.

TECHNICAL MANUAL SPECIFICATIONS AND STANDARDS (TMSS): Specifications that are performance based and standardized.