PWS TruLogicRe_Acq_Type_II_IETM_Multi_TMS 20-Oct-23.pdf

CUI

PERFORMANCE WORK STATEMENT (PWS) FOR

TYPE II

INTERACTIVE ELECTRONIC TECHNICAL MANUAL (IETM)

F101-GE-102, F110-GE-100, F110-GE-129,, F118-GE-100, & F118-GE-101

INTERMEDIATE & DEPOT LEVEL TECHNICAL MANUALS SUSTAINMENT

PREPARING ORGANIZATION: AFLCMC/LPSZB TINKER AFB, OK

73145-3030

Prepared: 20 April 2023 – Version: 1.1

Last Modified: 6-Oct-2023 FD2030-24-30029

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: USAF Controlled by: AFLCMC/LPSZB CUI Category: General Procurement and Acquisition Limited Dissemination Control: FEDCON POC: Christopher Michaelis, 785-259-0471

Table of Contents

SECTION I DESCRIPTION OF SERVICES

1.1 Requirements:

1.2 Type II IETMs Delivery of Block Cycle Updates (BCUs)

1.3 Sustainment/ Incorporation/ Delivery of Change Pages (Non-Mod)

1.4 Sustainment/ Incorporation/ Delivery of ECP/MOD Pages

1.5 Development/ Delivery of Rapid Action Changes (RACs)

1.6 Travel/ Temporary Duty (TDY)

1.7 Data

1.8 Delivery of Converted IETMS Work Packages as MS Word Documents

1.9 Provide for Master Support Equipment and Consumable Table Auto- Generation

1.10 Process and Delivery of Generated Reports in MS Excel

1.11 Graphic Navigation Interface (GNI)

1.12 Calculation Sheet and EAWP Form Generation and Sustainment

1.13 IETM Enhancements

1.14 Engine Automated Work Package (EAWP) Enhancement for F110 Engine Series IETMs

1.15 Portable IETM Reference Library for F110 Engine Series IETMs

1.16 Government Furnished Equipment (GFE) Custodial Process

SECTION II SERVICES SUMMARY

SECTION III GOVERNMENT FURNISHED PROPERTY (GFP) AND EQUIPMENT

(GFE)

SECTION IV GENERAL REQUIREMENTS

SECTION V APPENDICIES

APPENDIX A – APPLICABLE DIRECTIVES/REFERENCES

APPENDIX B – LIST OF CDRLS

APPENDIX C – GLOSSARY

SECTION I DESCRIPTION OF SERVICES

This Performance Work Statement (PWS) defines the requirements for sustainment of F101-GE- 102, F110-GE-100, F110-GE-129, F118-GE-100, and F118-GE-101 Turbofan Engine Technical Manuals to include all model/configurations, Intermediate Maintenance Manual (IMM) and Depot Maintenance Manuals (DMM), and applicable shared manuals. Deliveries shall comply with applicable military specifications and technical manual requirements for IMM and DMM Type II Interactive Electronic Technical Manuals (IETM) (see Appendix A). Tasks include sustainment for applicable manuals; preparation and construction of Type II IETM-compatible Rapid Action Change (RAC) electronic files, incorporation of Time Compliance Technical Orders (TCTOs), Incorporation of change requests per Air Force Technical Order (AFTO) Recommend Changes into Standard Generalized Markup Language (SGML), and delivery of Federal Desktop Core Configuration (FDCC) compliant TYPE II IETM builds to support distribution of the scheduled IETM Revision Block Cycle Updates (BCUs).

The standardized digital data shall include an integrated installation program capable of providing a complete installation on stand-alone Department of Defense (DOD) user's computer without the requirement for network access or installation on local DOD networks. This effort covers multiple engine Type Model Series (TMS) and supports multiple organizations. All digital technical data shall be accurate and complete. This is critical for the end-user to maintain and overhaul engines to continue Operational Safety, Suitability, and Effectiveness (OSS&E) for each engine TMS. All currently tagged common technical data between F101-GE-102, F110-GE-100, F110-GE-129, F118-GE-100, and F118- GE-101 referred to as the “common data database”, must be maintained and when approved new changes that will be introduced as common data in an effort to reduce future cost of sustainment. The Air Force plan and intent is to have the contractor deliver TYPE II IETM updates every 90 calendar days for the F101-GE-102, F110-GE-100, F110-GE-129, F118-GE-100. The F118-GE-101 IMM delivery will be every 180 days.

1.1 Requirements:

Type II IETMs Build/Delivery of Block Cycle Updates (BCUs) (Para.1.2)

Sustainment/Incorporation/Delivery of Change Pages (Non-Mod) (Para.1.3)

Sustainment/Incorporation/Delivery of ECP/MOD Pages (Para. 1.4)

Development/Delivery of Rapid Action Changes (RACs) (Para. 1.5)

Travel/Temporary Duty (TDY) (Para. 1.6)

Data (Para. 1.7)

Delivery of Converted IETMs Work Packages as MS Word Documents (Para. 1.8)

Provide for Master Support Equipment and Consumable Table Auto-Generation (Para.

1.9) Process and Delivery of Generated Reports in MS Excel (Para. 1.10)

Graphic Navigation Interface (GNI) (Para. 1.11)

Calculation Sheet and EAWP Form Generation and Sustainment (Para. 1.12)

IETM Enhancements (Para. 1.13)

EAWP Enhancement for F110 Engine Series IETMs (Para. 1.14)

Portable IETM Reference Library (Para. 1.15)

Government Furnished Equipment (GFE) (Para. 1.16)

1.2 Type II IETMs Delivery of Block Cycle Updates (BCUs)

The CONTRACTOR shall perform the IETM build process using the current Type II common-core configuration except for the F118-GE-101 IMM which will be maintained initially as a stand-alone (non-common-core) Type II IETM. Current IETM configuration is divided into Technical Orders (TOs), Work Packages (WPs), Illustrated Parts Breakdown (IPB), Nondestructive Inspection (NDI), and Critical Alloys and Previous Metals Parts List. These manuals provide required instructions for removal, disassembly, cleaning, inspection, repair/replacement and assembly, installation, testing, and troubleshooting.

The IETM shall:

• Support Graphic Navigation Interface (GNI), Component Navigation Interface (CNI), In- Process Inspections (IPIs), Critical Measurement Calculation Sheets (CALC Sheets), Consolidated Index Navigation, Self-integrating RACs with software update capability, Engine Model/Configuration Selection at point of entry, Navigation index of TCTOs and TCTO to Engineering Change Proposal (ECP) cross reference.

• Include a navigation pane with a Table of Contents, List of Tables, List of Figures, List of Changes, and Annotations for each manual.

• Include an Access Panel located on the library window that provides a quick link to specific supporting information. The Access Panel for IMM and DMM (Excluding the F118-GE-101 DMM) IETMs shall include these same entries; Consolidated Index, TCTOs, RACs, and IETM Help. The Access Panel for IMMs shall include the following additional entries; CCM/IPI Index, Engine Automated Work Package (EAWP), CNI, and Annotations. The Access Panel for DMMs shall include the following additional entries; incorporated Special Handling (SH) Recommend Changes and Pending 202s/SH Recommend Changes Annotations (Excluding the

F118-101 DMM).

• Include an integrated FDCC compliant installation program capable of providing a complete IETM installation on the Government’s approved desk top computer system configuration without the requirement for network access. For Government Information Technology (IT) security reasons web server software may not be installed on end user computers that may be connected to a military computer network.

• Not include or require the use of a Web Server software application on individual end user computers. For security reasons, Java Applets shall not be utilized in any delivered IETM Application.

• Support stand-alone installation on an independent client computer (i.e., non-networked notebook computer) and shall support a combined install process for Intermediate and Depot Level IETMS for each engine TMS.

• Support installation on a network file system capable of supporting multiple connections to client computer systems. The networked clients shall be capable of utilizing the TO data stored on the network file system.

• Provide Boolean Global Search capability across all manuals as well as Search within a single manual and include illustration thumbnails that appear when floating over the illustration icons.

• Support Integrated RAC incorporation. RAC issued data shall integrate with existing IETM

TO text upon installation. RACs shall be distributed with an IETM Installation Program.

• Support the indexing and referencing (linking) to TCTO data. Support internal referencing (linking) across all TOs. Illustrated Parts manual hotspot linking from figure indexes to the associated part number within the parts list and from the associated part number back to the applicable figure.

• Support active change marking with automatic highlighting of change data within the TOs and provide a summary of change data since last block cycle update via List of Changes.

• Support public and private annotations and bookmark capabilities that allow the user to stop a session and mark where he/she left off for a later return.

• Have alerts, which consist of: Warnings, Cautions, and Notes. Warnings are displayed in

Red, Cautions displayed in Yellow, and Notes displayed in Blue.

• Have an IETM HELP feature that provides instruction/information for the following topics: the graphics tool, navigation tips, brief descriptions of the graphic functions, software installation, main library window, IETM navigation, technical data, special features of the IETM, and IETM improvement form.

• Provide the capability to print Tasks/Work Packages/Sections with referenced figures and tables, as well as individual figures and tables. Any printed output shall state, “Destroy Immediately After Use.”

• Include progressive features to support the production and deliveries associated with the USAF eight-way commonality data identification and tagging program for the F101-GE-102, F110- GE-100, F110-GE-129, and F118-GE-100 IMM and DMM and the F118-GE-101 IMM common-core engine technical manual programs, common Warnings, Consumable tables, and

Support Equipment Tables. Common data highlighting shall be displayed in the IETM to show common data across the dataset down to the word level.

The IETM installation program shall automatically provide an IETM application icon on the desktop. The display shall include a readily viewable indication of IETM Title and Revision number and Revision date.

The IETM CD-ROM/DVDs shall be printed with a smudge-proof heat transfer label. The IETM CD- ROM/DVDs shall be accompanied by jewel case front and rear covers per applicable directives.

The CONTRACTOR shall deliver upon Government request, an electronic version of the CD and cover art at each delivery to eliminate the need to scan images during reproduction process. The IETM CD surface art, jewel case covers, installation banners, IETM user interface, or any recommended changes shall be submitted to the TOMA for approval. Any changes shall be documented as a formal change request for each IETM deliverable.

The CONTRACTOR shall deliver the current Type II IETMS common-core configuration (as applicable) to the Government for each scheduled IETM Revision Cycle. The Delivery of IETMs and IETM updates supports the Type II IETM on the Enhanced Technical Information Management System (ETIMS) digital WA-1 format for the F101-GE-102, F110-GE-100, F110-GE-129, F118-GE- 100, and F118-GE-101. In addition, F110-GE-100, F110-GE-129 will be delivered on CD- ROM/DVDs. The CONTRACTOR shall deliver four master Type II IETM CD-ROM/DVDs per engine TMS Intermediate and Depot level Technical Manuals (complete with Installation Program Software) to the Government for each scheduled IETM deliverable. In addition, the CONTRACTOR shall deliver via the DoD Safe Site; an electronic version of the latest DataAggregator® IETM system software as needed and/or the current revision of the IETM dataset, specifically configured to support hosting of the IETM system on ETIMS. BCUs are planned and intended to take place on a 90-calendar day basis for F101-GE-102, F110-GE-100/129, F118-GE-100 engine TMS (IMM and DMM) and F118-GE-101(IMM) will take place on a 180-calendar day basis. Refer to Attachment 1 for a list of IETM engine manuals. The cost shall reflect a price per IETM build to include four IETM CDs/DVDs, including a separate electronic delivery for ETIMS per TMS for every BCU.

There shall be no requirement for the Government to purchase additional software licenses to view or operate IETM desktop application.

No major changes to the IETMs software shall be permitted without Government approval. All software used and necessary to operate IETMs shall 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, the CONTRACTOR shall notify the Contracting Officer and TOMAs providing the latest software version at least 6 months prior to plan deployment. This will 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 IETMs meets SACA 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 shall be required when using USAF software to test new, and revised IETMs versions. Minor changes/versions do NOT require re-certification.

The CONTRACTOR shall provide the TOMA, the latest version of viewer software as a separate executable file via electronic secure means (DoD Safe Site).

The CONTRACTOR shall provide IETM support. Upon Government request, the CONTRACTOR provides necessary assistance 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 TOMA, regarding any IETM problem(s), prior to responding to a request for IETM field Support. CONTRACTOR is NOT responsible for providing field support for USAF network, server, and SDC/Microsoft Enterprise issues.

1.3 Sustainment/ Incorporation/ Delivery of Change Pages (Non-Mod)

CONTRACTOR shall incorporate digital revision requests as part of the IETM build. Pages are priced at price per page. An IETM page is defined as one page of what appears when “print preview” is selected from the browser toolbar while using the IETM. Manual rewrites, as agreed to by Government and CONTRACTOR, may consist of one or more work packages within a Technical Order. The Government will provide a mixture of redline markup data developed from the previous version of the IETM system and Recommended Changes (RCs) to be used as source data for revision incorporation. MS Word, SGML, PDF, or other mutually agreed to file formats will be provided for the incorporation of new work packages or TOs. Source data for new illustrations will be provided in either full scale TIF, JPEG, or PDF file formats. Only Government provided source data may be incorporated into IETM. When source data is incorporated any changes affecting indexing, subsequent paragraph numbering, and other formatting will be made at no additional charge to the Government.

1.4 Sustainment/ Incorporation/ Delivery of ECP/MOD Pages

CONTRACTOR shall incorporate digital revision requests to incorporate modification data related to incorporation of Engineering Change Proposals (ECPs) and Class 1 Change in Design (CID).

Requests are part of the IETM build and is priced at price per page. An IETM page is defined as one page of what appears when “print preview” is selected from the browser toolbar while using the IETM. The Government will provide a mixture of redline markup data developed from the previous version of the IETM system and Recommended Changes to be used as source data for revision incorporation. Only Government provided source data may be incorporated into IETM. When source data is incorporated any changes affecting indexing, subsequent paragraph numbering, and other formatting will be made at no additional charge to the Government.

1.5 Development/ Delivery of Rapid Action Changes (RACs)

The CONTRACTOR shall provide packaging and distribution of RACs for the IETMS. The CONTRACTOR shall convert and package the RAC complete with the IETM executable file and deliver it electronically to the Government within two business days of request and receipt of a complete source data package. This requirement will be used to process and deliver urgent TO revisions. These shall be delivered as an electronic executable file with instructions via approved electronic secure file transfer system. RACs are urgent changes that cannot wait until the next scheduled BCU/IETM Build. The term RAC includes the installation program, technical writing, authoring associated with production and updating an IETM. RACs will be formatted to allow seamless merging with the basic affected TO on the IETMS already installed on an operating system. The contents of a RAC will be incorporated during the next IETM BCU at no additional cost to the Government. If more than one RAC is required during a single RAC delivery, multiple RACs may be loaded via one RAC number. RAC events are limited to no more than one IETM technical order manual and 10 changed pages that cover the following criteria: (1) multiple Work Packages (WPs) and/or multiple figures in an IPB, (2) one In- Process Inspection (IPI) within a TO, (3) one Critical Calculation Measurement (CCM) Sheet within a TO, (4) one safety, urgent or interim TCTO/TCTO supplement. An IETM page is defined as one page of what appears when “print preview” is selected from the browser toolbar while using the IETM. The cost shall reflect a price per RAC processed for each IETM system.

RACs exceeding ten pages of authoring shall be charged as a second RAC, so forth and so on.

1.6 Travel/ Temporary Duty (TDY)

CONTRACTOR shall travel in support of PWS requirements upon approval 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. Prior to travel, Contractor must prepare and submit to the Government, an estimate containing the number of days required for travel, number of personnel, and method of transportation. Costs shall 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, and Field Service Evaluations (FSE).

1.7 Data

The CONTRACTOR shall furnish data in accordance with Contract Data Requirements Lists (CDRLs) (Appendix B), DD Form 1423-1, hereto. The CLIN is not separately priced.

1.8 Delivery of Converted IETMS Work Packages as MS Word Documents

Upon request, the CONTRACTOR shall convert Technical Manual Work Packages from IETMs to a Microsoft (MS) Word editable document for the F101-GE-102, F110-GE-100, F110-GE-129, F118- GE-100, and F118-GE-101Engine Series IETM Programs. The conversion of technical manual work packages to MS Word shall be priced as each WP to be converted.

1.9 Provide for Master Support Equipment and Consumable Table Auto- Generation

The CONTRACTOR shall perform the modifications required to enable the auto-generation, formatting, and integration of additional information into the current Support Equipment Item List and the current Consumable Materials Item List. This additional Government-identified data shall be automatically updated during each IETM build process so that the data remains current at each BCU.

This task is specific to the F101-GE-102, F110-GE-100, F110-GE-129, F118-GE-100, and F118-GE- 101Engine Series IETMs.

Prior to the start of the task, the CONTRACTOR shall provide the Government a copy of the current Support Equipment Item List and the current Consumable Materials Item List in Excel format. The Government will update the Excel files with any required additional information, such as supplier information. The Government will provide the CONTRACTOR the revised Excel file at the start of the task.

1.10 Process and Delivery of Generated Reports in MS Excel

The CONTRACTOR shall provide any one of four individual reports to be delivered in MS Excel editable format document from pertinent data collected from the technical manual library for the F101-GE-102, F110-GE-100, F110-GE-129, F118-GE-100, and F118-GE-101Engine Series IETM Programs. The following reports shall be provided upon Government request: Consolidated Support Equipment Table, Consolidated Consumables Table, IPB manuals Parts List, and Consolidated Artwork Table which identifies individual art numbers and the locations used within the technical manuals. The individual reports are to be priced as each (one report of choice, one delivery event of the chosen report) per each TMS.

1.11 Graphic Navigation Interface (GNI)

The CONTRACTOR shall perform a full engine photoshoot at a suitable CONUS location; perform photograph/graphic processing; update the IETM interface for the GNI; create the required map files for linking the GNI to the subject matter; perform testing and verification of a fully updated GNI.

The task is specific to the F101-GE-102, F110-GE-100, F110-GE-129, F118-GE-100, and F118-GE- 101 Engine Series IETM Programs.

The Government will arrange for the availability of a properly configured engine at a suitable location with local engine support personnel for the photoshoot. The Government will include the CONTRACTOR in the coordination process. The revised GNI will mirror the functionality of the existing GNI. The CONTRACTOR shall ensure the GNI is fully functional before delivering a review copy to the Government. Once approved, the revise GNI shall be rolled out in the subsequent BCU delivery. The CONTRACTOR shall provide a fixed cost for performing one engine configuration GNI update as specified. CONTRACTOR travel will be performed IAW the travel section.

1.12 Calculation Sheet and EAWP Form Generation and Sustainment

The CONTRACTOR shall provide for the generation of new Critical Calculation Measurement (CCM) Sheets and EAWP forms as well as the sustainment of pre-existing calculation sheets and EAWP forms. This task is specific to the F101-GE-102, F110-GE-100, F110-GE-129, F118-GE-100, and F118-GE-101 Engine Series.

For new CCM sheets or EAWP forms, the Government will provide source data to the CONTRACTOR which details the calculations and the associated fields for the new document.

For sustainment of existing forms, the CONTRACTOR shall inform the Government prior to beginning the change process, whether the required change is textual, or programming related.

The CONTRACTOR shall provide EAWP sustainment services as required. The Government will provide recommended changes to EAWP submitted in conjunction with scheduled BCU source data deliveries.

The CONTRACTOR shall provide fixed costs for the creation of new CCM sheets and EAWP forms, sustainment of existing CCM sheets and EAWP forms for textual changes, and sustainment of existing CCM sheets and EAWP forms for programming changes.

1.13 IETM Enhancements

The CONTRACTOR shall support the Government with the identification/implementation of IETM system improvements/enhancements that will increase the efficiency, usability and reliability of the IETM architecture. Enhancements may also be used to expand upon current system functionality in order to provide additional time-saving maintenance features, security updates, SDC compatibility modifications, system installation or improve the accuracy of maintenance-action recording/documentation. Upon request the CONTRACTOR shall modify the IETM and/or framework applications, document structures and other components as needed to provide the desired enhancement to the overall system. The Government may request cost and schedule estimates in the form of Rough Order of Magnitude (ROM) in order to evaluate the feasibility of proceeding with IETM enhancement.

1.14 Engine Automated Work Package (EAWP) Enhancement for F110 Engine Series IETMs

EAWP Enhancement. The CONTRACTOR shall provide a technology enhancement for the F110 engine series Engine Automated Work Package (EAWP) program. The current EAWP program has been superseded by technology and security advancements since its initial release. The EAWP program shall be updated accordingly to operate within an EAWP- enabled version of the DataAggregator® IETM framework and an EAWP-enabled IETM system. The F110 Engine Series IMM IETM systems (F110-GE-100 and the F110-GE-129) shall be modified to incorporate the EAWP Enhanced functionality.

The CONTRACTOR shall ensure the EAWP Enhanced version will collect form data by association with Job Control Number and Engine Serial Number. All resident data is required to be stored on a separate EAWP server. EAWP Session Packaging and the administration of enrolled technicians shall be controlled by a CONTRACTOR-provided EAWP Server Application. The EAWP Enhanced shall be modeled to ensure that all EAWP forms created to support the individual engine programs will have the ability to be auto-populated when possible, using information gathered from COMPREHENSIVE ENGINE MANAGEMENT SYSTEM (CEMS) E407 reports. The EAWP application shall have the ability to import this data.

The Government will provide final direction and updates to existing EAWP form data and content for new forms at the beginning of the task. The source data will be provided to the CONTRACTOR in MS Word document format. Details of form data will be discussed at the EAWP Enhancement Guidance Conference.

EAWP IETM system/server application deficiencies will be reported to the CONTRACTOR as technical support inquiries.

The CONTRACTOR shall support one trip to Tinker AFB to participate in a post-award Guidance Conference for the EAWP Enhancement program. The goal of this conference will be to discuss schedule, responsibilities, implementation, testing and test site coordination, fact finding, and other program-related topics. In addition, the CONTRACTOR shall support a three-day on-site field test of the system to ensure that all functions of the IETM and the EAWP Admin Server are operating normally. Any discrepancies identified as the result of testing shall be corrected by the CONTRACTOR and a Pre-Publication Review (PPR) copy shall be provided for Government review.

Computer hardware and network resources for the individual engine shops will be provided by the Government.

Delivery of a PPR copy of the initial engine program will occur as a result of the EAWP Enhancement effort. Formal delivery of the completed EAWP Enhanced shall occur as part of the subsequent scheduled Block Cycle Update (BCU) final delivery.

The EAWP Enhancement effort for the F110 Engine Series IETMs shall reflect a firm fixed price for the complete task. The EAWP Enhancement task is a one-time (non-recurring) effort.

1.15 Portable IETM Reference Library for F110 Engine Series IETMs

The Government often relies on prior versions of TOs to perform technical research or investigations.

The IETM Block Cycle Updates (BCUs) are purposely designed to overwrite the previous version during the installation process thus preventing the capability to host multiple revisions on the same computer. The Government requires a single dedicated notebook computer to be uniquely configured to enable the hosting of multiple revisions of IETMs for the F110-GE-100 and F110-GE-129 Intermediate and Depot Level Manuals. The contractor shall provide the technical services required to configure and populate a Government-owned notebook computer with IETMs from the contractor’s archive. The Government will provide a list of the desired IETMs to be loaded onto the computer hard drive, limited by space available. The Government will grant the contractor administrative privileges on the device for the duration of the task. The Government asset and accessories will be provided to the contractor for setup, loading and testing. All work shall be performed at the contractor facility. The asset and accessories shall be returned to the Government upon completion of the task.

The contractor shall provide instructions for maintaining the device as new revisions are encountered.

The contractor shall provide a firm-fixed-price for this one-time effort.

1.16 Government Furnished Equipment (GFE) Custodial Process

The CONTRACTOR shall host a GFE workstation to be used for USAF Standard Desktop Configuration (SDC) IETM compatibility monitoring and testing. This workstation must undergo periodic update via AFNet in order to ensure the latest versions of SDC are available to support this task. Travel to a local USAF location may be required on a monthly (or as needed) basis to ensure updates are maintained. Associated Fixed Costs shall be applied quarterly in conjunction with the BCU schedule.

SECTION II SERVICES SUMMARY

The following section specifies the Performance Objectives and Performance Elements for the contract.

PERFORMANCE

OBJECTIVE

PWS

PAR

PERFORMANCE THRESHOLD

SS-1. Type II IETMs Build and Delivery of Block Cycle Updates (BCUs)

Incorporates all Government provided changes.

Incorporates New ECP/TCTOs with indexing and linking to ECP/TCTO cross reference list.

Provide hotspot linking from figure indexes to the appropriate part number in the IPB.

Provides markings to IETMs to indicate changes from previous version. All changes are appropriately marked and summarized in a 'Summary of Changes" file accessed by a button on the home page.

Provides the ability to print Tasks/Work Packages/Sections with referenced figures and tables and shall contain the statement “Destroy after Use" on each page.

Provide the ability to identify any commonality test/data while reading the paragraphs, tables, or figures.

Provide the ability to make (private and/or public) annotations down to the paragraph, subparagraph, figure, or table level to IETMs.

1.2 Minimum is 95% error free

SS-2.

Sustainment/Incorporation/ Delivery of Change Pages (Non- Mod)

CONTRACTOR shall incorporate digital revision requests as part of the IETM build.

Provide hot spot linking from referenced figure numbers to appropriate figure.

indicate changes from previous version by having all appropriately marked and summarized in the “Summary of Changes’ file accessed by a

1.3 Incorporates only Government provided changes with zero errors of incorporated data.

All other services shall have a minimum is 95% error free

SS-3.

Sustainment/Incorporation/ Delivery of ECP/MOD Pages

Provide hot spot linking from appropriate figure.

Provides markings to IETMs to indicate changes from previous version by having all appropriately marked and summarized in the “Summary

1.4 Incorporates only Government provided changes with zero errors

SS-4 Delivery of Rapid Action Changes (RACs)

Incorporates only Government provided changes with zero errors

Provide hot spot linking from appropriate figure.

indicate changes from previous version by having all appropriately marked and summarized in the “Summary

1.5 Not to exceed 48 hours after receipt of notification and appropriate funding documents zero error

SS-5. Delivery of Converted IETM Work Packages as MS Word Documents

1.8 Zero errors of converted data

SS-6. Provide for Master Support Equipment and Consumable Table Auto- Generation

1.9 Automatically updated during each IETM build process

so that the data remains current at each BCU 95% of the time, goal is 100%

SS-7. Process and Delivery of Generated Reports in MS Excel

1.10 Zero errors of converted data

SS-8. Graphic Navigation Interface (GNI)

Revised GNI will mirror full functionality of existing GNI

1.11 Minimum 5% errors

SS-9. Engine Automated Work Package (EAWP) Enhancement for F110 Engine Series IETMs

EAWP will support individual engine programs and maintains full functionality of IETM

1.14 Minimum 5% errors

SS-10. Calculation Sheet and EAWP Form Generation and Sustainment

Incorporates all Government provided changes

1.13 Minimum is 95% of the time.

SECTION III GOVERNMENT FURNISHED PROPERTY (GFP) AND EQUIPMENT (GFE)

3.1 Government Inventory

The contractor shall perform an inventory of all Government property to include material and equipment not later than 30 calendar days after contract start and on a quarterly basis IAW CDRL 0004. Physical Inventory reports shall be submitted to the COR. The report shall detail the results of the inventory, any items not accounted for and items that are lost, damaged, or destroyed beyond use.

(See Atch 2 - CFO Report Template)

The contractor shall maintain records evidencing receipt, accountability, preventative maintenance and disposal as defined within the Government property clauses. All GFP shall be included in the attached spreadsheet. (See Atch 1 – GFP List)

SECTION IV GENERAL REQUIREMENTS

This section describes general requirements for this effort.

4.1 Change Source Materials

All IETM technical data changes will be the result of a Government approved/transmitted RC or an approved Request for Clarification (RFC) Government response. An IETM page is defined as one page of what appears when print preview is selected from the browser toolbar while using the IETM. The CONTRACTOR shall be responsible for grammatical editing, style, and format. If an RC is found in error such as but not limited to, conflict with any of referenced directive, conflict with other directed changes that are to be made simultaneously, paragraph or figure numbering error, inaccurate, or incomplete; CONTRACTOR shall submit correction recommendations on an RFC form to the TOMA for approval.

4.2 Duplication of Data

Changes to common technical data annotated as such in each of the different TMS IETMs shall not be separately charged for a change that affects same data in the other IETMs manuals.

Changes to support equipment tables and consumable tables are currently linked to all text locations and shall not be separately charged.

4.3 Contractor action without separate direction

When RCs change affects table of contents, front matter, numerical index, consumable material list or other auto-generated components the CONTRACTOR shall update/change without need of further authorization.

4.4 Contractor Archives

The CONTRACTOR shall maintain archives of previous IETM builds, RCs, correspondence, conference minutes, quality assurance data, Record of Incorporated Data (RID), etc. resulting from this contract.

4.5 Classification of Data

All requirements to be performed under this PWS shall maintain a security classification no higher than UNCLASSIFIED.

4.6 Security Requirements

The Contractor shall ensure Contractor personnel with access to unclassified information systems, including e-mail, shall have at a minimum a favorable National Agency Check (NAC).

Contractor personnel shall not be authorized access to or be permitted to work on classified and/or sensitive projects and/or programs without a proper security clearance and a need-to-know.

Contractor personnel with NAC/clearances that have been suspended or revoked shall immediately be denied access.

Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer unclassified and/or sensitive information in accordance with DoD 5220.22-M.

Access to Government System: The Contractor shall ensure a Common Access Card (CAC) is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, for DoD facility entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order. The Contractor shall provide a list of contractor/subcontractor personnel who require a CAC to the PCO. The Government will provide the Contractor instruction on how to complete a Contractor Verification System (CVS) application and notify the Contractor of approval/disapproval of contractor/subcontractor personnel application.

Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility.

The Contractor shall immediately report a lost or stolen Common Access Card (CAC) as directed by local Government policy. The Contractor shall notify the Procuring Contracting Officer (PCO) of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list within five business days. The Contractor shall return a CAC within five business days once contractor/subcontractor personnel no longer require computer network/system access and/or facility access. The Contractor shall return an expired CAC within five business days after the expiration date. The Contractor shall return all CACs within five business days after completion/termination of the contract as directed by local Government policy.

4.7 Access to Government Facilities

The Contractor shall ensure Contractor personnel who require access to Wright-Patterson AFB, Tinker AFB, or other Government facilities comply with the security procedures of the facility.

The Contractor shall ensure an ID card is obtained by all contractor/subcontractor personnel who require recurring access to a Government facility, but not local area network (LAN) access. The Contractor shall submit a letter to the PCO listing all contractor/subcontractor personnel requiring access to the facility. The PCO will approve the request and forward it to the issuing/registration office for processing. Contractor/subcontractor personnel shall report to the issuing/registration office to obtain the ID card(s).

The Contractor shall submit a letter to the PCO immediately if contractor/subcontractor personnel no longer require access, upon transfer/termination of contractor/subcontractor personnel or upon completion/termination of the contract/order. The letter shall identify the name(s) and social security number(s) of the contractor/subcontractor personnel. The Contractor shall return the ID card(s) to the issuing/registration office upon expiration, upon transfer/termination of contractor/subcontractor personnel, or once contractor/subcontractor personnel no longer require access to the facility. The Contractor shall return all ID cards to the issuing/registration office within five business days of completion/termination of the contract.

Uses and Safeguarding of Information: Information from the secure web site 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.

4.8 Network Access

Network access is a privilege extended to contractor employees. It will be granted only after all criteria have been met and may be suspended for cause as defined in AFMAN16-1405. Network access will be approved In Accordance With (IAW) DoDMAN5200.02. Every individual who has access to the AF network (af.mil) domain, specialized systems and mission systems is a network user.

Before becoming an AF network user, an individual must be trained and licensed. This process of training and licensing ensures that every AF network user is trained and aware of the basic principles of network security and their role in Information Assurance (IA).” Every AF network user must possess a current and favorable Tier 1 or higher and Local Files Check (LFC). The Tier 1 is a requirement for working on Government installations and any costs associated with obtaining the Tier

1 shall be the responsibility of the contractor.

4.9 Rights in Data

Commercial Software: The contractor shall provide an End User License Agreement (EULA) for all delivered commercial computer software. The EULA shall identify any restrictions levied upon the Government pertaining to the use and distribution of the software. A copy of the EULA shall be included with the contractor’s proposal.

Government-Owned Data: The Government retains all rights and title to all technical content (TO and TO-Related Data, Technical Illustrations, Form Data, and Video Files). The contractor receives no rights or ownership of any technical data content provided by or developed for the Government.

Government Distribution: The Contractor shall ensure that the Government is granted adequate authorization to redistribute the IETM system software as required to support all Government-related For Official Use capacities. The software shall not require per-seat licensing or fees.

Contractor Distribution. Under no circumstances shall the contractor be authorized to distribute the IETM systems or data to persons or organizations other than the TOMAs specified by the Contracting Officer. All requests for copies of the IETM systems and data must be submitted directly to the Contracting Officer.

4.10 Transition

Phase-In: 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 the 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.

Phase-Out: All contractor related actions to complete phase-out at the end of the contract will be completed upon notification by the PCO and will deliver all TMSS-compliant TM SGML data and baseline TIFF/JPG illustrations no later than 45 calendar days from the end of contract period.

4.11 Mission Essential Contractor Services: N/A

4.12 Contractor Manpower Reporting

. 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 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 (https://www.fsd.gov/fsd-gov/home.do)."

*Reporting Period: Contractors are required to input data by 31 October of each year.

Uses and Safeguarding of Information: Information from the secure web site 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.

User Guide: Data for Air Force service requirements must be input at www.sam.gov. A quick start user guide is available at on the SAM.gov website at https://www.fsd.gov/sys_attachment.do?sys_id=95849fed1be769100ca4a97ae54bcbba.

SECTION V APPENDICIES

APPENDIX A – APPLICABLE DIRECTIVES/REFERENCES

AFMAN16-1405_DoDMAN5200.02 - Air Force Personnel Security Program

AFMCI 63-1201 – Implementing Operational Safety, Suitability, and Effectiveness (OSS&E) and Life Cycle Systems Engineering

DoD 2010.12-M – Procedure for Acquisition and Management of Technical Data

DoDI 5230.24 – Distribution Statements on Technical Documents

MIL-DTL-87268 - Interactive Electronic Technical Manuals, General Content, Style, Format, and User-Interaction Requirements

MIL-DTL-87269 - Data Base, Revisable - Interactive Electronic Technical Manuals, for the Support of

MIL-DTL-38807D - Technical Manuals - Illustrated Parts Breakdown

Mil-PRF-87929 - MANUALS, TECHNICAL, OPERATION AND MAINTENANCE http://www.sam.gov/ https://www.fsd.gov/fsd-gov/home.do) http://www.sam.gov/ https://www.fsd.gov/sys_attachment.do?sys_id=95849fed1be769100ca4a97ae54bcbba

INSTRUCTIONS

MIL-STD-38784 - A STANDARD PRACTICE FOR MANUALS, TECHNICAL: GENERAL

STYLE AND FORMAT REQUIREMENTS

Technical Orders:

00-5-1 00-5-3

APPENDIX B – LIST OF CDRLS

CDRL A001_Conference Agenda CDRL A002_Conference Minutes CDRL A003_Report of Technical Manual Costs CDRL A004_Physical Inventory Report

ATTACHMENT

Attachment 1 _ CFO Report Template.xls

APPENDIX C – 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 a Recommended Change, any change to a page from one word to the entire page to include tables and/or illustrations.

COMMOM DATA DATABASE: Author once and use many times across four engine type programs and up to eight different manual sets.

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 (KO): 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.

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

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.

EXTERNAL CERTIFICATION AUTHORITY (ECA) PROGRAM: The DoD Public Key Infrastructure (PKI) sponsors the ECA program. It consists of a Root Certification Authority (Root CA) maintained at the same facility that operates the DoD PKI Root CA and Subordinate CAs maintained by vendors. Vendors wishing to become ECA shall pass a rigorous process that ensures their certificates are interoperable with the DoD PKI and that their policies and procedures are sufficient to meet requirements specified in the ECA Certificate Policy (CP), which has been approved by the DoD Certificate Policy Management Working Group (CPMWG). Once a vendor is approved to operate as an ECA, the vendor is issued a Subordinate CA certificate from the ECA Root CA. If an ECA vendor leaves the ECA program, the Subordinate CA certificate for that vendor is revoked.

ECA vendors recoup the cost of managing their ECAs by charging fees to issue certificates.

FORMAT: The layout of a publication per Military Specification (MIL-SPEC).

HYPERTEXT MARKUP LANGUAGE (HTML): Format of files published on the World Wide Web.

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 ASSESSMENT: Process measuring success towards achieving defined performance objectives or goals defined within the performance thresholds in the services summary or the process of assessing progress towards achieving the objectives/goals developed in a performance plan or partnering agreement.

PERFORMANCE INDICATOR: Measurable characteristic of an output of a work process.

Generally synonymous with attribute.

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.