F100_IETMS_PWS_.pdf

PERFORMANCE WORK STATEMENT (PWS)

FOR

TYPE II

INTERACTIVE ELECTRONIC TECHNICAL MANUAL SYSTEM (IETMS)

F100-PW-220/220E/229

INTERMEDIATE TECHNICAL MANUALS

PREPARATION DATE: Feb 17

PREPARING ORGANIZATION: AFLCMC/LPSZB

TINKER AFB, OK 73145-3030

Table of Contents

1.0 DESCRIPTION OF SERVICES

1.1 Vision Statement

1.2 Introduction

1.3 Mission

1.4 Background

1.5 Scope

1.6 Task Order Requirement

1.7 IETMS Direct Delivery (Task 1)

1.8 Development of Rapid Action Changes (RAC) (Task 2)

1.9 Development and Sustainment of F100 Illustrated Parts Breakdown (IPB) (Task 3) ... 6

1.10 Graphic Conversion (Task 4)

1.11 IETMS Direct Support for Field (Task 5)

1.12 Travel (Task 6)

1.13 Data (Task 7)

1.14 Engine Automated Work Package (EAWP) (Task 8)

1.15 Deliverables

1.16 General Requirements

1.17 CONTRACTOR Key Personnel

1.18 Contract Management Plan -

1.19 Quality System and Quality Program Requirements

1.20 Security Requirements

1.21 Data Rights

1.22 CONTRACTOR Travel

1.23 Contracting Officer Representative (COR)

1.24 Section 508 Compliance

1.25 CONTRACTOR Manpower Reporting (CMR)

1.26 General Information

1.27 Program Progress Report

1.28 Hardware and Software Requirements

1.29 CONTRACTOR Employee General Requirements

1.30 Data Delivery

1.31 Transition Periods

2.0 Services Summary

3.0 GOVERNMENT FURNISHED INFORMATION (GFI)

APPENDIX A – GLOSSARY ............................................................................................................ A-1

APPENDIX B – Miscellaneous Data Item Descriptions .............B-Error! Bookmark not defined.

PERFORMANCE WORK STATEMENT

TYPE II INTERACTIVE ELECTRONIC TECHNICAL MANUAL SYSTEM FOR

F100-PW-220E/229 INTERMEDIATE TECHNICAL MANUALS

February 2017

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 shall be accomplished while striving to reduce costs without sacrificing safety or quality.

1.2 Introduction

The purpose of this PWS is to specify requirements for sustainment of GOVERNMENT F100- PW-220, and F100-PW-229 Turbofan Engines, Intermediate Level (I-Level) Technical Orders (TO). Deliveries shall comply with applicable military specifications and technical manual requirements for Intermediate Level maintenance Type II IETMS. Tasks include sustainment support for applicable TOs; preparation and construction of IETM-compatible Rapid Action Change (RAC) electronic files, incorporation of Time Compliance Technical Orders (TCTOs), Rapid Action Changes (RACS), AFTO Form 252s into Standard Generalized Markup Language (SGML), and delivery of Federal Desktop Core Configuration (FDCC) compliant TYPE II IETM builds to support distribution of scheduled IETM Revision Block Cycle Updates (BCU). The IETMS shall include an Engine Automated Work Package (EAWP) for field support. The EAWP shall produce analyses and reports enabling maintainers, technical support personnel, and management to evaluate and analyze the difference between desired builds, most cost effective builds, achieved builds, and to accomplish fleet reliability analysis.

Additionally, the EAWP shall enable work center supervisors, depot, and MAJCOM Headquarters personnel to review and analyze maintenance being performed at the unit level.

IETMS shall include an integrated installation program capable of providing a complete installation on the user’s computer without the requirement for network access.

See Appendices for definitions of terms, acronyms and sample forms.

1.3 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 IETMS.

1.4 Background

DoD initiatives and AFMC Instruction (AFMCI) 21-301, Maintenance, TO System Implementing Policies states “all active TOs in the USAF inventory are to be converted/digitized to electronic formats.” Tinker AFB’s TO platforms are designed to support the Air Force TO Concept of Operations (CONOPs) providing user friendly, technically accurate, and up-to-date digital technical data for multiple engines. Technical data for this IETMS has been previously converted and implemented.

1.5 Scope

Standardized digital data shall 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 shall be accurate, and complete, and is critical for the end-user to maintain, and overhaul engines to continue Operational Safety, Suitability, and Effectiveness (OSS&E) for each engine TMS.

The Air Force plan and intent is to have the CONTRACTOR deliver a Type II IETMS update package at a minimum of every 120 calendar days, up to 180 calendar days. An EAWP shall document engine maintenance during Jet Engine Intermediate Maintenance (JEIM) in accordance with AFI 21-101 Chapters 2, and 4. The CONTRACTOR shall provide a detailed testing plan when changes to the EAWP are required.

1.6 Task Order Requirement

1.6.1 The CONTRACTOR shall use file types, Document Type Definition (DTD), style sheets, and graphic formats as defined in the Technical Manual Contract Requirement (TMCR).

There are eight task elements to the PWS:

Task 1 – IETMS Direct Delivery

Task 2 – Development of Rapid Action Changes

Task 3 – Development and Sustainment of F100 Illustrated Parts Breakdown (IPB) 2J- F100-24 and 2J-F100-54 in TMSS compliant Standard Generalized Markup Language (SGML) format.

Task 4 – Graphic Conversion

Task 5 – IETMS Direct Support of Field

Task 6 – Travel

Task 7 – DATA

Task 8 – Engine Automated Work Package

1.7 IETMS Direct Delivery (Task 1)

1.7.1 The IETMS is divided into TOs and Work Packages (WP), and provides necessary instructions for removal, disassembly, cleaning, inspection, repair/replacement and assembly, installation, testing, and troubleshooting. IETMS direct deliveries shall consist of two DVD-

ROMS: TO 2J-F100-1-CD-6 and TO 2J-F100-1-CD-7 (see TMCR). Each BCU delivery shall be considered an IETMS direct delivery with updates to all TOs listed within each IETMS.

The CONTRACTOR shall deliver the current IETMS configuration. No changes to IETMS software are permitted without Program Manager approval. All software used and necessary to operate IETMs/EAWP shall have Air Force Network Information Center (AFNIC) certification and be published on the Air Force Evaluated Products List (EPL) prior to deployment. In the case of new software, or software revisions, the CONTRACTOR shall contact the GOVERNMENT 12 months prior to planned deployment, and assist the GOVERNMENT in the AFNIC certification/re-certification process. This assistance may include but is not limited to; review of AFNIC requirements before submission to ensure IETMS meets AFNIC requirements, software corrections as identified by AFNIC, providing up to date software architecture documentation, and any other documentation required as requested by the GOVERNMENT. A Non-Disclosure Agreement (from the vendor, or subcontractor) shall be required when using USAF software to test new, and revised IETMS versions. The CONTRACTOR shall deliver the current Software Version Description (DI-IPSC-81442A, CDRL A005).

1.7.2 Change requests are considered routine revisions that occur on a BCU for the Intermediate Maintenance Manual (IMM). Change requests (AFTO Form 252) shall be incorporated within 180 calendar days after receipt by CONTRACTOR. Any change requests not incorporated after 180 calendar days shall require written justification to the Contracting officer and COR. The CONTRACTOR shall incorporate GOVERNMENT provided AFTO Form 252/redline source data and any outstanding RACs. There shall not be more than three errors (i.e. grammar, improper/omitted diagram, inoperative hyper-link) per 100 change pages of AFTO Form 252’s. A BCU may consist of: (1) change pages authorized by AFTO Form 252/redline source data (defined as a page that prints from a Source Data Representation (SDR) file created from IETMS. (2) Incorporation and conversion of poor quality graphics.

The CONTRACTOR shall convert graphics to a vector format upon receipt of an AFTO Form 252, (3) Conversion of Procedural Art Graphics containing text (such as a legend) within the Graphics. (4) The CONTRACTOR shall include digital photographs. Digital, if required, shall be incorporated in the next BCU.

1.7.3 IETMS Digital Delivery (DVD-ROM) shall be provided upon BCU completion. The CONTRACTOR shall provide a BCU DVD-ROM on a single DVD-ROM or set of DVD-ROM (1 Original and two copies). A Record of Incorporated Data (RID) review shall be conducted and the CONTRACTOR notified of any errors. The CONTRACTOR has three working days, after notification, to correct errors.

1.7.4 A sheet shall be defined as a page printed from a Source Data Representation (SDR) file created from IETMS. A LOT (LO) shall be defined as one CD/DVD- ROM delivery per TMS (Consisting of 1 original and 2 copies each, plus one each CD/DVD of the 2J-F100-24, and 2J-F100-54).

1.8 Development of Rapid Action Changes (RAC) (Task 2)

1.8.1 RACs are urgent changes that cannot wait to be delivered as part of the schedule IETMs revision. RAC’s shall be formatted in IPDF files and shall be embedded as supplements within IETMs. The CONTRACTOR shall incorporate a GOVERNMENT provided AFTO Form 252 or redline source data. The CONTRACTOR shall convert and package the RAC as an IETMS operational supplement and deliver it electronically to the

GOVERNMENT within three working days from the date the change is received by the

CONTRACTOR.

1.8.2 Upon completion of the RAC, the CONTRACTOR shall produce a file, in PDF, with instructions on how to load to the current IETMs. Errors are to be corrected within three working days after the GOVERNMENT notifies the CONTRACTOR of the error.

1.8.3 RAC Development and RAC Incorporation, a LO shall consist of one RAC that does not exceed five PDF pages of text and illustrations as authored in the RAC development process.

RACs exceeding five pages of authoring shall be returned to the customer for incorporation during the next BCU.

1.8.4 RACs shall include the applicable pages, figures, or tables where incorporated or TOs, WP, steps, and step IDs or tables. In the event the CONTRACTOR is unable to comply with a delivery date, the CONTRACTOR shall request an extension, in writing, from the CO. The CONTRACTOR shall recommend an alternate delivery date and furnish sufficient justification for the delay to aid in the evaluation of the request. Failure of the parties to agree on a firm data contract delivery date shall be considered a dispute concerning a question of fact within the meaning of the FAR Clause 52-233-1 entitled “Dispute”, as implemented by the General Provision clause of the contract.

1.9 Development and Sustainment of F100 Illustrated Parts Breakdown (IPB) (Task 3)

1.9.1 Contractor shall provide SGML IPBs (2J-F100-24 and 2J-F100-54) authored in Technical Manual Specification & Standards (TMSS) compliant SGML using AF content specified DTDs. The CONTRACTOR shall acquire latest DTDs and must get PM approval before use (See TMCR). SGML IPBs shall be delivered on a separate CD/DVD and shall contain two files: F100-PW-220 SGML IPB and F100-PW-229, SGML IPB, and associated WebCGM (Computer Graphics Metafile) graphics for SGML.

1.10 Graphic Conversion (Task 4)

1.10.1 Pratt & Whitney shall supply the most current graphics files for F220 and F229 for conversion (as necessary). Graphics files shall use the most current version of Arbortext ISOView as identified in the USAF’s EPL.

1.11 IETMS Direct Support for Field (Task 5)

1.11.1 The CONTRACTOR shall provide IETMS support. The CONTRACTOR provides CONTRACTOR personnel for instruction and technical IETMS support, to include installation, work situation setups, tool conversions, troubleshooting, and technical interchange meetings to the USAF. The CONTRACTOR shall notify the SPO, regarding the ITEMS problem(s), prior to responding to IETMS field Support. It shall be funded as requirements occur.

1.12 Travel (Task 6)

1.12.1 The CONTRACTOR shall travel in support of PWS requirements upon direction by the PCO. All travel shall be approved by the PCO. The CONTRACTOR shall 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. Incurred travel and per diem charges shall be applied in accordance with the Federal and Joint Travel Regulations in effect at the time of performance of the travel. Specific travel is not limited to but may include:

� Guidance Conference

� In-Process Reviews

� Engine Automated Work Package

� IETMS setup/troubleshooting

1.13 Data (Task 7)

The CONTRACTOR shall furnish data in accordance with Contract Data Requirements Lists (CDRLs) (Appendix B), DD Form 1423, hereto. The CLIN is not separately priced; its cost is included in CLINs 0001 thru 0005.

1.14 Engine Automated Work Package (EAWP) (Task 8)

The CONTRACTOR shall provide an EAWP for CDs 2J-F100-1-CD-6 and 2J-F100-1-CD-7.

The EAWP shall meet minimum requirements as defined in the TMCR. The EAWP shall be a separately priced line item. The CONTRACTOR shall deliver the current Software Version Description (DI-IPSC-81442A, CDRL A005) defining the current EAWP configuration. No changes to the EAWP, software or data, are permitted without Program Manager approval. It is the CONTRACTOR’s responsibility to fully test EAWP operability before delivery.

1.15 Deliverables

Milestone schedules are set in accordance with each task in this PWS. In the event the CONTRACTOR cannot comply with the schedule, the CONTRACTOR shall submit, in writing, a request for extension to the Contracting Officer, and AFLCMC/LPSZB-TOMA. No extension shall be granted to any date which is more than 15 working days past the milestone scheduled delivery date.

1.15.1 Direct Delivery - The CONTRACTOR shall deliver an updated Type II IETMS to the GOVERNMENT, direct delivery BCU, for F100-PW-220/220E/229 (2J-F100-1-CD-6 and 2J- F100-1-CD-7) Engine Intermediate Maintenance Manual (IMM) data content in SGML/HTML per AFTO 252/redline markups within 120 calendar days after receipt of AFTO 252s. There shall not be more than three errors (i.e. grammar, improper/omitted diagram, inoperative hyper-link) per 100 change pages of AFTO Form 252’s. Each DVD shall include all TOs as defined on the TMCR.

- 1 Original and 2 copies of TOs 2J-F100-1-CD-6 and 2J-F100-1-CD-7

- In conjunction with every BCU, the CONTRACTOR shall deliver the following on separate CD/DVD s:

o 2J-F100-24, SGML format – 1 original copy o 2J-F100-54, SGML format – 1 original copy

1.15.2. The CONTRACTOR shall deliver an updated EAWP for both CDs (2J-F100-1-CD-6 and 2J-F100-1-CD-7) in conjunction with the direct delivery (BCU). The EAWP is integrated into TOs contained within 2J-F100-1-CD-6 and 2J-F100-1-CD-7, and delivered on the same DVD (Task 7, para 1.13). There shall be no more than one error per EAWP.

1.15.3. RACS - The CONTRACTOR shall deliver Rapid Action Changes (RAC’s) on DVD- ROM or by secure digital delivery (see Task 2, Para 1.8)

-1 RAC in media specified by TOMA

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

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

1.16.2 Hours of Operation - The CONTRACTOR is responsible for conducting business and shall be available for technical assistance between the hours of 8 a.m. – 4 p.m. CST Monday thru 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 shall, at all times, maintain a workforce for uninterrupted performance and continuity of services of all tasks outlined within this PWS.

1.16.3 CONTRACTOR Personnel - The CONTRACTOR shall 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. Employees must have a Secret Security Clearance (ANACI Tier III). The selection, hiring, assignment of duties, reassignment of duties, transfer, supervision, management, control, and termination of CONTRACTOR employees in performance of this PWS shall be the responsibility and prerogative of the CONTRACTOR. All CONTRACTOR employees who visit or are assigned to a GOVERNMENT facility shall wear appropriate attire, depending on particular job assignment, to be recognized as CONTRACTOR employees.

1.16.4 CONTRACTOR Responsibilities - The CONTRACTOR shall be responsible for grammatical editing, style and format of all TOs. This shall include grammatical editing of language and format to comply with Air Force TO specifications. The CONTRACTOR shall make use of all resources available, whether resulting from this contract or not, to ensure technical accuracy, adequacy, compatibility, completeness, and suitability for Air Force use of TOs. These resources include, but are not limited to, engine and equipment technical, engineering, design, configuration, modification, performance, and failure data;

personnel experience, expertise, and subject matter knowledge; thorough familiarity with TOs and applicable military specifications: knowledge of using command(s) requirements;

knowledge of Air Force operational, maintenance and logistics concepts for the engine and equipment involved.

1.16.5 CONTRACTOR Employee Requirements (Reference FAR 37.114) - The CONTRACTOR shall 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 shall 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.16.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 shall maintain responsibility for all aspects of task order performance and oversight, regardless of any arrangement between the Prime and its’ Sub-Contractors.

1.16.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 shall notify the PCO immediately whenever they become aware that such access or participation may result in any actual or potential OCI and shall submit a plan within five working days to the PCO to avoid or mitigate any such OCI. The CONTRACTOR’S mitigation plan shall 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.16.8 CONTRACTOR Employees - The CONTRACTOR shall not employ any person who is an employee of the U.S. GOVERNMENT. Additionally, the CONTRACTOR shall 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 shall 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 AFI 64-106 (Air Force Industrial Labor Relations Activities).

1.16.9 Mission Essential CONTRACTOR Services. N/A

1.17 CONTRACTOR Key Personnel - The CONTRACTOR shall 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 calendar days After Receipt of Order (ARO). The CONTRACTOR shall provide a contract manager and/or alternate contract manager who shall be responsible for the oversight of CONTRACTOR personnel in the performance of the tasks outlined in this PWS. The contract manager and/or alternate contract manager shall have full authority to act for the CONTRACTOR on all contract matters relating to daily operation of this contract. The contract manager or alternate shall be available between 8 a.m. – 4 p.m., CST Monday thru 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.18 Contract Management Plan - The CONTRACTOR shall provide a Contract Management Plan to the PCO and COR for review at least 10 calendar days prior to 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 shall be considered a living document and shall be updated to reflect the status of the program. At a minimum, the plan shall 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 (need to check CDRL to see if this applies)

1.19 Quality System and Quality Program Requirements

The quality system and quality program shall meet the following requirements: (DIQCIC- 81379, CDRL A002, and DI-QCIC-81187 CDRL A004).

1.19.1. See TMCR for Quality Control Plan

1.19.2. Quality System - The CONTRACTOR shall support and provide access to files as requested by the GOVERNMENT within five working days for quality audit inspections, verifications, and evaluations to ascertain conformance to requirements and the adequacy of implementing procedures. The CONTRACTOR shall allow GOVERNMENT audits to be performed on CONTRACTOR maintained files and explain any deficiencies, provided that said audits do not interfere with the CONTRACTOR’S duties. Upon completion of the GOVERNMENT’S quality audit, the CONTRACTOR shall take corrective action(s) to eliminate the cause of any deficiencies.

1.19.3. GOVERNMENT QA Surveillance Support - The CONTRACTOR shall 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 shall follow methods of surveillance specified in the QASP. The COR is the GOVERNMENT’S authorized PCO representative and shall participate in the verification/review of this contract.

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

NOTE: The COR shall inform the CONTRACTOR when discrepancies occur and shall request corrective action on a Customer Complaint Record. The GOVERNMENT COR shall make a notation of the discrepancy on their surveillance checklist recording the date and time of the discrepancy.

1.20 Security Requirements - CONTRACTOR personnel performing these services shall have, at a minimum, a favorable ANACI.

1.20.1 Physical Security. The CONTRACTOR shall maintain tapes of disks generated as a result of the preparation of TOs in traceable locations at the CONTRACTOR Facility. The CONTRACTOR shall utilize a tape and disk storage facility in a moisture proof and temperature controlled environment with dust and humidity controls to avoid damage to digital data. The CONTRACTOR shall retain tapes containing digitized and tagged TO data in the CONTRACTORS’ Storage and Maintenance Facility until delivery, full inspection, and acceptance by the GOVERNMENT.

1.20.2 Disaster Recovery. The CONTRACTOR shall utilize a proven Document

Management system to store, control, and issue versions of SGML source files and maintain historical copies of GOVERNMENT-owned SGML files. The CONTRACTOR shall establish and maintain a Disaster Recovery Program to backup, at a location other than the work site, and protect GOVERNMENT- owned SGML files and illustration data from permanent loss or destruction.

1.20.3 Information Assurance (I A) Tra in ing . CONTRACTOR personnel shall complete initial IA training (Advanced Distributed Learning System (ADLS) course – DoD IAA Cyber Awareness Challenge (ZZ133098)) before gaining access to any GOVERNMENT information system, if required, in the performance of these services. CONTRACTOR personnel shall also complete annual IA refresher training (ADLS Course ZZ133098) to ensure functional competency related to threats and system vulnerabilities, and protective measures taken to counter such disruptions. The CUSTOMER and/or GOVERNMENT Technical Point of Contact shall arrange access to the training, which shall be completed at the place of performance on the first day of the performance period and annually thereafter.

1.21 Data Rights. See TMCR.

1.21.1. GOVERNMENT Distribution - The CONTRACTOR shall provide the GOVERNMENT unlimited rights to distribute the Type II IETMs Systems to all authorized users of Propulsion Technical Data. This includes International users that have procured U.S. based weapon systems through the United States GOVERNMENT.

1.21.2. CONTRACTOR Distribution - Technical data, IETMS Viewer and software, documents and materials may NOT be provided, used, or sold by the CONTRACTOR without written permission from the PCO. The CONTRACTOR shall comply with the distribution and destruction statements on all TOs. All data and materials supplied to the GOVERNMENT shall be the sole property of the GOVERNMENT and may not be used for any other purpose.

This right does not abrogate any other GOVERNMENT rights. Under no circumstances shall the CONTRACTOR be authorized to distribute the Type II ETM systems or data to persons or organizations other than AFLCMC/LP. All requests for copies of the Type II ETM systems and data must be submitted directly to the PCO.

1.22 CONTRACTOR Travel - The GOVERNMENT may request the CONTRACTOR to travel to Tinker AFB for direct technical support of services outlined in this PWS. The CONTRACTOR is responsible for making all necessary travel arrangements. The CONTRACTOR shall obtain written approval from the PCO prior to any scheduled travel.

The CONTRACTOR shall submit a proposed itinerary to the PCO within five calendar days of scheduling any requested travel, and submit a final trip report within five calendar days of completion of travel. The CONTRACTOR shall be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR), FAR 31.205-46, and the limitation of funds specified in the contract. IAW FAR 31.205-46, the CONTRACTOR is required to submit the traveler’s name, dates of travel, location of travel, and dollar amount of travel. The GOVERNMENT reserves the right to audit, thus; the CONTRACTOR shall keep on file, all backup support documentation for travel.

1.22.1 Post Award Conference/Periodic Progress Meetings See TMCR

1.23 Contracting Officer Representative (COR) - The COR shall be identified by separate 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 shall receive a copy of the written designation. It shall 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 shall 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 Section 508 Compliance - Requirements for accessibility based on Section 508 of the Rehabilitation Act of 1973 (29U.S.C. 794d) are determined to be relevant for this effort.

The CONTRACTOR shall support the GOVERNMENT in its compliance with Section 508 throughout the development and implementation of the work to be performed. Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d) requires that when Federal agencies develop, procure, maintain, or use electronic information technology, Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who do not have disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency.

1.25 CONTRACTOR Manpower Reporting (CMR) – Section 2330a of Title 10, United States Code (10 USC 2330a), requires the Secretary of Defense to submit to Congress an annual Inventory of Contracts for Services (ICS) performed during the prior fiscal year for or on behalf of the Department of Defense (DoD). The inventory must include the number of CONTRACTOR employees using direct labor hours and associated cost data collected from CONTRACTORs. Contracting Manpower Reporting Application (CMRA) is the system utilized by the Air Force to collect and provide the Air Force's annual ICS to Congress.

The CONTRACTOR shall report all CONTRACTOR manpower (including sub-Contractor manpower) required for performance of this contract. The CONTRACTOR shall completely fill in all the information needed us inghttps://afcmra.dmdc.osd.mil to access the AF CMRA at the link for the AF CMRA system. The required information includes: (1) Contracting Office, Contracting Officer, Contracting Officer’s Technical Representative (COTR) or also known as the COR; (2) Contract number, including task and delivery order number; (3) Beginning and ending dates covered by reporting period; (4) CONTRACTOR’S name, address, phone number, e-mail address, identity of CONTRACTOR employee entering data;

(5) Estimated direct labor hours (including sub-Contractors’); (6) Estimated direct labor dollars paid this reporting period (including sub-Contractors’); (7) Total payments (including sub-Contractors’); (8) Predominant Federal Service Code (FSC) reflecting services provided by CONTRACTOR (and separate predominant FSC for each sub-Contractor if different); (9) Estimated data collection cost; (10) Organizational title associated with the Unit Identification Code (UIC) (the Air Force Requiring Activity is responsible for providing the CONTRACTOR with its UIC for the purposes of reporting this information); (11) Locations where CONTRACTOR and sub-Contractor(s) perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website); (12) Presence of deployment or contingency contract language; and (13) Number of CONTRACTOR and sub-Contractor employees deployed in theater this reporting period (by country). As part of its submission, the CONTRACTOR shall provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period shall be the period of performance not to exceed 12 months ending September 30 of each GOVERNMENT fiscal year and shall be reported by 31 October of each calendar year. CONTRACTORS may use a direct XML data transfer to the database server, or fill in the fields on the website. XML direct transfer is a format for transferring files from a CONTRACTOR’S system to the secure website without the need for separate data entries for each required data element at the website. Specific formats for XML direct transfer may be downloaded from the website. If you have questions or issues accessing the Air Force CMRA system, please contact the AF CMRA Help Desk at: (855) 723-2672 or CMRA@pentagon.af.mil

1.26 General Information - Customer Interface, CONTRACTOR personnel interfacing with customers shall conduct themselves in a professional manner.

1.26.1 Response Times - The CONTRACTOR shall respond to all requests for assistance from customers within the following timeframes:

Emergency and Work-Stoppage - Respond within two business hours after receipt of data.

Urgent - Respond within four business hours after receipt of data.

Routine - Respond within 24 business hours after receipt of data.

1.26.2 Information Requests - The CONTRACTOR shall provide responses to information and data only to the Contracting Officer, Contracting Officer Representative (COR), or

AFLCMC/LPSZB-TOMA.

1.27 Program Progress Report - The CONTRACTOR shall develop and maintain processes to evaluate and monitor progress made by the CONTRACTOR in accomplishing the requirements of this PWS. The CONTRACTOR shall develop, maintain, and deliver a Program Progress Report in January, April, July, and October. The report must include AFTO 252 number, TO number, including when applicable, TO page supplement numbers, estimated number of pages, change number and date, estimated direct image reproducible, and digital tech order DVD-ROM delivery revisions delivery date, order number, applicable notes and Publication Change Request due date. The TO Status and Schedules Report shall include all requirements received from the cutoff date of the last 90 Day BCU to the cutoff date of the next 90 day BCU delivery. Report shall list all change requests not incorporated from previous BCU or pending incorporation with reason for non-incorporation. (DI-MGMT-

80555A, CDRL A003).

1.28 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 shall be submitted 14 calendar days after the date of contract award. The IETMS database shall be able to run on systems which are configured with latest Microsoft application and Internet Explorer for standard desktop operation. Future operating system changes shall be provided by AFLCMC/LPSZB. In the event that future changes impact the IETMS software so as to require modification of the software to keep it in compliance with the Standard Desktop Core Configuration, then the GOVERNMENT shall fund the modification and related tasks by the CONTRACTOR.

mailto:CMRA@pentagon.af.mil

1.29 CONTRACTOR Employee General Requirements - The CONTRACTOR shall require CONTRACTOR employees, who are required to communicate with GOVERNMENT personnel to have the ability to clearly speak, read and write the English language.

CONTRACTOR employees shall identify themselves as CONTRACTOR personnel by introducing themselves or being introduced as CONTRACTOR personnel and displaying distinguishing badges or other visible identification in order to meet with GOVERNMENT personnel. In addition, CONTRACTOR personnel shall appropriately identify themselves as CONTRACTOR employees in telephone conversations and in formal and informal written correspondence.

1.29.1 Key Personnel Qualification Requirements - The CONTRACTOR shall require key personnel identified below meet the following requirements:

1.29.2 Contract Manager -The CONTRACTOR shall provide a Contract Manager and alternate, who shall be responsible for the performance of the work and who shall have full authority, to act for the CONTRACTOR on all matters relating to the performance of this contract. The Contract Manager shall develop, maintain, and deliver a Management Plan. The Contract Manager shall:

- Be responsible for all work performed under this PWS.

- Provide in writing to the PCO, within 10 working 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:

- Develop, maintain, and deliver an organizational chart, which reflects key personnel with a line of responsibility between the organizational elements.

- Develop, maintain, and deliver a cross-utilization chart, which identifies each task against specific positions or elements within the organization, if cross-utilization is to be used.

- Be available, to be contacted by telephone during business hours to discuss issues pertaining to the services provided and attend meetings requested by the PCO, COR, or QA Personnel.

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

- Develop, maintain, and deliver a contact list of individuals who can address routine questions and provide data and status information during business hours.

- Deliver all plans, reports, correspondence, briefings, and other documents required by this PWS, including forms, CDRLs, and required notifications in Microsoft Office format or IPDF. All such documents shall be delivered via e-mail unless otherwise directed and approved by the PCO.

- Support conference calls as coordinated by the PCO with all necessary parties and provide agenda’s to the COR. 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.30 Data Delivery - All technical order data must be delivered by traceable means, such as a shipping/tracking number, and delivered at destination (3001 Staff Drive 2AA2 -109B, Tinker AFB, Oklahoma 73145-3002).

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

1.31.1 Phase-In-Period Requirements - During the 15 day phase-in transition period the CONTRACTOR shall:

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

• Complete a physical inventory of GOVERNMENT furnished data.

• Complete the phase-in-joint inventory no later than 10 working days prior to the end of the phase-in-period.

• The CONTRACTOR and a GOVERNMENT COR shall conduct an inventory of all data. The CONTRACTOR shall notify the Contracting Officer in writing within five working days upon completion of the inventory. The CONTRACTOR shall provide an inventory report identifying the accuracy and condition of the data provided by the GOVERNMENT and identifies any missing or unsuitable data.

1.31.2 Phase-Out Period Requirements - The CONTRACTOR shall be responsible for all work performed under this PWS during the phase-out-period. The CONTRACTOR shall ensure the following phase-out requirements are accomplished within 60 calendar days prior to contract end date. The CONTRACTOR shall cooperate fully to permit an orderly changeover of the workload and delivery of GOVERNMENT owned data. The CONTRACTOR shall participate and complete the phase out joint inventory no later than 10 working days prior to the end of the last performance period. The CONTRACTOR and a GOVERNMENT COR shall conduct a joint inventory of all GOVERNMENT property. During the joint inventory, the CONTRACTOR and GOVERNMENT COR shall jointly determine the working order and condition of all property. The CONTRACTOR shall document the condition of all GOVERNMENT property and notify the Contracting Officer in writing within five working days of completion of the joint inventory. The CONTRACTOR shall resolve any discrepancies between the joint inventory and official GOVERNMENT records.

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 shall be allowed by the GOVERNMENT before contract performance is considered unsatisfactory.

c. Explain QA methods the GOVERNMENT shall use to evaluate the CONTRACTOR's performance in meeting contract requirements.

2.2 The GOVERNMENT’s primary QA procedures are based on technical review of the data, customer complaints, and spot inspections of the recurring critical output products of the contract.

SERVICE SUMMARY TABLE

Performance Requirement PWS Paragraph

Requirement Threshold

SS-1 The CONTRACTOR shall deliver an updated Type II IETMs, direct delivery BCU, for F100- PW-220/220E/229 (2J-F100-1-CD-6 and 2J- F100-1-CD-7) Engine Intermediate Maintenance Manual (IMM) data content in SGML/HTML per AFTO Form 252/redline markups. Each CD/DVD shall include all TOs as defined on the TMCR.

- 1 Original and 2 copies of CDs 2J-F100-1- CD-6 and 2J-F100-1-CD-7

- In conjunction with every BCU, the CONTRACTOR shall deliver the following on separate CDs:

o 2J-F100-54 SGML format - 1 original copy o 2J-F100-24 SGML format- 1 original copy

1.15.1 Documents

delivered within 120 calendar days of receipt of AFTO 252s.

No more than three errors (i.e.

grammar, improper/omitted diagram, inoperative hyper-link) per 100 change pages corrected within three working days

SS-2 1.15.2 The CONTRACTOR shall deliver an updated EAWP for both CDs (2J-F100-1-CD-6 and 2J-F100-1-CD-7) in conjunction with the direct delivery (BCU). The EAWP is integrated into TOs contained within 2J-F100-1-CD-6 and 2J-F100-1-CD-7, and delivered on the same DVD (Task 7, para 1.13).

1.15.2 No more than one

error (i.e. grammar, improper/omitted diagram, inoperative hyper-link) per EAWP, correctable within three working days

SS-3 RACS - The CONTRACTOR shall deliver Rapid Action Changes (RAC’s) on CD/DVD-ROM or by secure digital delivery (see Task 2, Para 1.8)

-1 RAC in media specified by TOMA

1.15.3 No more than one

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

SS-4 Illustrated Parts Breakdown (IPB) shall be authored in TMSS compliant SGML using AF content specified DTD. The CONTRACTOR shall acquire latest DTDs and must get PM approval before use. (See TMCR). SGML IPBs shall be delivered on a separate CD/DVD and shall contain two files: F100-PW-220 SGML IPB, and F100-PW-229, SGML IPB, and associated WebCGM (Computer Graphics Metafile) graphics for SGML.

1.9 No more than

one error (i.e.

grammar, improper/omitted diagram, inoperative hyper-link) per hundred pages correctable within three working days

3.0 GOVERNMENT FURNISHED INFORMATION (GFI)

All data provided by the Government to the Contractor for the Contractor to input and process will remain at all times the property of the Government. Technical data input and processed during the performance of task order(s) must at all times be maintained in a readable and readily retrievable format. Technical data received, created or edited shall be made available to the government upon request during the contract period of performance. All software provided under this contract shall become the property of the government. Therefore, source code for all systems, scripts, tools, etc., developed as part of this contract must be provided at contract completion or upon request from the government at any time during the period of performance. 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.

GOVERNMENT-Furnished Property (“GFP”) shall be defined as “any records, files, documents, and work papers provided by the GOVERNMENT or generated by the CONTRACTOR in support of the contract “The CONTRACTOR shall maintain and dispose of all GFP according to the requirements of the Air Force Manual (AFMAN) 33-363. The CONTRACTOR shall prepare and present a Property Control System (written procedures) to the GOVERNMENT Property Administrator (PA) within 30 calendar days (DI-MGMT-80004A, CDRL A001) after contract award or at the pre-performance conference; whichever is sooner. The CONTRACTOR’S procedures shall be organized with functions and functional segments in accordance with Appendix A of DoDI 4161.02. If changes occur in the property control procedures after submission to the GOVERNMENT PA, then the CONTRACTOR shall submit said changes to the PA for review and approval, prior to implementation of such changes.

SECTION III

A-1

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 as a result of an AFTO 252, any change to a page from one word to the entire page to include tables and/or illustrations.

COMMON TO: TO that is applicable to more than one book set or CD/DVD for any Type Model Series (TMS) engine.

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 as long as 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.

DEFECT: Any non-conformance with requirements specified in the contract.

DEFECTIVE SERVICE: A service output not meeting the standard of performance specified in the contract for that service.

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.

ELECTRONIC TECHNICAL MANUAL (ETM): Technical Manual authored in a linear fashion for

A-2 the purpose of page or inline presentation (Type I). ETMs may have a wide range of functionality ranging from indexed raster, hypertext linking, multimedia, interactivity between the data and the user, procedural guidance, navigational directions, and supplemental information. ETMs may also contain logistic-support functions supplemental to maintenance actions and are displayed IAW TMSS specifications.

END USER: Any user authorized for distribution of USAF standard propulsion tech data.

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.

ENHANCE…