Sect J Atch 8 - TMCR - TM-86-01N 24 Feb 10.doc

TM-86-01K.1 1 December 2005

TM-86-01N 1 January 2009

FA8625-10-R-6600, Attachment 8 24 Feb 2010

Air Force Technical Manual Contract Requirements (TMCR)

For The

KC-X Tanker Modernization Program

Part 1 – Engineering, Manufacturing & Development

FOR CDRL SEQUENCE NUMBER B037, EXHIBIT B

Section 1. Technical Manuals (TM)/Technical Order (TO) Program Requirements

1. TMCR Tailoring.

1.1. The Contractor shall provide their contractual comprehensive approach to the development, certification, and delivery of all TOs required to fully meet the Government’s identified technical data requirements within each paragraph in Section 1 and the associated tables in Section 2 of this TMCR. The Contractor shall also adhere to the Specification/Standard Interface Record (SIR) for the TO types, source data, TO updates, commercial manuals, and any TOs prepared to Non Government Standards (NGS) in Section 3 of this TMCR. The Contractor shall not delete any Government identified requirements, but may identify additional TOs required to support the KC-X System.

1.2. The completed contractual TMCR shall be: (1) Attached to CDRL B037 for TO delivery, (2) Included in the proposal as Exhibit B and (3) Referenced in the proposal SOW. Air Force TO Acquisition procedures and terms for this document are found in TO 00-5-3, AF Technical Order Life Cycle Management.

2. TO Program Scope. The KC-X System requires safe, current, accurate, adequate, concurrent with aircraft configuration, and technically usable TOs that support all facets of operation and maintenance of the KC-X System to include all Operation, Maintenance, Installation and Training (OMIT) Technical manual requirements for both Organizational level (O-level) and Depot level (D-level) of maintenance. It is the government’s intent to support this aircraft with an organic two-level maintenance concept utilizing O-level “blue-suit” AF maintainers and organic D-level for long-term sustainment from the on-set of this program. In accordance with T.O.00-5-3; “All new major acquisition programs must acquire TOs in a Type 2 Interactive Electronic Technical Manual (IETM) database format . . . IAW AIA-S1000D and the Air Force XML Business Rules (BR) to be published in a TMSS specification.” The Government intends to utilize the commercially available IETMs, currently in use, to support maintenance activities for the baseline non-military aircraft and engines. These commercially available IETMs will be used as the baseline maintenance IETM in the development of the KC-X IETM. NOTE: For purposes of this document, O-level Maintenance includes both the Field level infrastructure and back shops.

2.1. The Contractor shall provide all existing commercially available ITEMs for the baseline non-military aircraft in support of a Government sufficiency review IAW MIL-PRF-32216 (Evaluation of Commercial Off-The-Shelf (COTS) Manuals and Preparation of Supplemental Data) of all O-level and D-level maintenance manuals; and IAW MIL-DTL-7700G (Detail Specification: Flight Manuals, Aerial Refueling Procedures, and Abbreviated Checklists) for all Flight/Operation manuals. As part of this review, the government will identify at the Guidance conference, a sampling of tasks to be performance verified by government personnel. The Contractor shall support the government verification of these selected tasks and the integration of changes resulting from this review, thereby establishing the baseline maintenance IETM for the KC-X. The Contractor shall also provide “on-aircraft” support (engineering and TO writers) as needed for these government verifications.

2.1.1. The Contractor shall provide the Government’s review team; the same commercially-available baseline non-military aircraft and engine general familiarization training given to commercial customers; within 30 days following the TO Guidance conference. The review team will consist of three pilots, one Loadmaster/Boom Operator; in addition to two maintainers in each of the following AFSCs 2A5X1- A/C Crew chief, 2A5X3A- Com/Nav, 2A5X3B – Instruments/Flight Controls, 2A6X1 – Engines, 2A6X4 – Fuels, 2A6X5 – Hydraulics, 2A6X6 – Electrics /Environmental

2.2. The Contractor shall develop, certify and deliver all identified technical manuals in Tables 1 and 2 of Section 2 of this TMCR. Those O-level maintenance manuals and checklists identified in Table 1 shall be developed to meet the intent of the referenced MIL-STD/PRF and be incorporated into the baseline maintenance IETM, providing a seamless all-encompassing O-level maintenance IETM.

2.3. The Contractor shall investigate and incorporate typical Intermediate Level tasks that can be effectively accomplished under the O-level maintenance concept into these existing commercial IETMs baseline maintenance IETM, providing a seamless all-encompassing O-level maintenance IETM.

2.4. The Contractor shall incorporate all applicable vendor/supplier O-level operation and maintenance manuals for components such as boom, wing refueling pods, centerline refueling hose & drogue, avionics, cargo door, etc., into the baseline maintenance IETM, providing a seamless all-encompassing O-level maintenance IETM.

2.5. The Contractor shall develop, certify and incorporate all source data related to the militarization modifications of the KC-X into these baseline maintenance IETM; providing a seamless all-encompassing O-level IETM.

2.6. The Contractor shall develop, certify and incorporate Nuclear Hardness Maintenance Requirements and Procedures for all affected aircraft systems and subsystems requiring this type of protection, into the baseline maintenance IETM, providing a seamless all-encompassing O-level maintenance IETM.

2.7. The Contractor shall identify, certify and incorporate O-level user procedures for all Test, Measure, Diagnostic, Evaluation/Support Equipment (TMDE/SE), Special Tools, and portable maintenance aids or other enabling tools that simplify and improve the effectiveness of maintenance into the baseline maintenance IETM, providing a seamless all-encompassing O-level maintenance IETM.

2.8. The Contractor shall develop, certify and deliver Electronic Technical Manuals (ETMs) Flight/Operation Manuals to support all facets of Flight Operation of the KC-X system. The Contractor shall include all Aerial Refueling Operator (ARO) procedures for an all inclusive Flight/Operation Manual. The Contractor may identify Electronic Flight Bags (EFBs) for operators in lieu of MIL-DTL-7700 Flight Manuals. If EFBs are identified for use; the EFBs as delivered, must meet all data requirements addressed in MIL-DTL-7700G and the AMC Flight Manual Matrix (Attachment 1) and kept current with all TO and aircraft configuration changes.

2.9. The Contractor shall develop and implement incorporation procedures for Government originated changes, as the result of both government performance verification and Initial Operational Testing and Evaluation (IOT&E), to all Technical Manuals until the manuals are formally delivered to the Government.

2.10. For Technical Orders in development, the Contractor shall develop and implement change process that allows the incorporation a pro forma level of Government-originated (AFTO Form 22s or AFTO Form 847s) changes to flight, performance and maintenance Technical Orders. This pro forma level of changes is based upon the estimates in Attachment 2, a price per page basis, and is at least as good as the highest level of commercial customer-originated change allowances.

2.11. The Contractor shall ensure all Technical Manuals and SE/TMDE manuals are concurrent with the aircraft configuration, prior to formal delivery.

2.12. The Contractor shall implement procedures to notify the government of any Federal Aviation Administration (FAA), Original Equipment Manufacturer (OEM) and/or Vendor directed Air Worthiness Directives (ADs) or Service Bulletins (SBs) for approval prior to incorporation into delivered TOs.

2.13. The Contractor shall develop and implement on-line access, viewing, and updates to all Technical Manuals/Technical Orders which ensures currency of manuals and provides automated electronic updates to IETMs stored on maintainers’ eTools.

2.14. The Contractor shall ensure all flight/operation ETMs/EFBs and maintenance IETMs are displayed on the aircraft flight deck IAW the System Requirements Document.

2.15. The Contractor shall develop and provide an electronic subscription to the commercial Flight and Maintenance Manuals for the planned service life of the fleet.

2.16. The Contractor shall deliver Depot-level Technical Manuals (ASD/ASI S1000D, XML-tagged formatted IETM) including Suppliers/Vendors manuals for the Aircraft, Systems, Engines, and all subsystem components in support of the Government’s organic Depot level and KC-X Maintenance Review Board’s approved maintenance.

2.17. The Contractor shall develop and deliver Operations, Maintenance, Installation and Training (OMIT) technical manuals IAW Table 1 and applicable SOO paragraphs to fully support organic organizational and depot levels of maintenance.

3.

Subsequent TO/Data Requirements. The Contractor shall develop and implement a process for notifying the government when additional TOs or source data requirements are identified. This process shall require government review and approval of recommended additional requirements prior to contractual approval.

4. TO Development. The Contractor shall describe how the government will interact with the Contractor’s TO development team. The Contractor shall develop and implement all comprehensive TO development practices and procedures that ensure all TOs and data are compatible with the TO System of Record, the Air Force Technical Order Concept of Operations (CONOPS) and the Air Force Standard TO Management System. The Contractor shall write all TOs to a scope and depth of coverage sufficient to support the operations and maintenance concepts, and to the Reading Grade Level (RGL) specified in MIL-STD-38784, Standard Practice for Manuals, Technical: General Style and Format Requirements. The Contractor shall utilize English/Standard measurement values (i.e. Feet, inch pounds, Gallons, Knots per Hour) in the development of all manuals.

4.1. The Contractor shall develop and deliver all IETMs in accordance with ASD/AIA S1000D, issue 4, International Specification for Technical Publications Utilizing a Common Source Database and the Government’s S1000D/XML Business Rules in Section 3.

4.2. The Contractor shall format with text, graphics and delivery according to the TMSS specified in Section 2 for all TOs. The Contractor shall develop TO files (tagged instances) using eXtensible Mark-up Language (XML) according to the Document Type Definitions (DTDs) referenced in the appendix to MIL-STD-38784 and each applicable military detail or performance specification (MIL-DTL or MIL-PRF).

4.3. The Contractor shall include required illustration (graphics) files in an approved graphics exchange format (select “Guidelines” and “Graphics” on the Technical Manual Specifications and Standards (TMSS) web page (https://techdata.wpafb.af.mil/tmss/index.html) for all XML-tagged TO files. NOTE: Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible.

4.4. The Contractor shall contact the TO Manager and the 754 ELSG/ILMT for pre-approval before modifying or developing any new DTDs to support use of NGS, canceled TMSS, or undeveloped TMSS DTDs. If permission is granted, the Contractor must submit any proposed DTDs through the PCO and TO Manager to 754 ELSG/ILMT for validation of TMSS compatibility with approved electronic TO (eTO) viewing solutions. New DTDs shall not be developed in lieu of existing DTDs, including those for legacy TMSS. TMSS Rules shall be so constructed that TO output complies with the functional requirements of the associated TMSS, and shall be documented in a SIR. DTDs and rule sets submitted and approved in execution of the contract shall become the property of the Government. The Contractor shall direct questions about the application of XML tagging to digital TO files to 754 ELSG/ILMT (SGMLSupport@wpafb.af.mil).

5.

Technical Manual Specifications and Standards (TMSS). The Contractor shall address all questions concerning TMSS requirements by written request and justified suggestions for resolution submitted through the PCO and the TO Manager, 836AESG/SYL, 2590 Loop Road West, BLDG 558, Wright-Patterson AFB, OH 45433-7142, Phone: (937) 904-5710. Contractor originated deficiencies and suggested improvements shall be submitted to the TMSS Preparing Activity (PA) for approval.

6. TO Numbering. The Contractor shall notify the TO Manager of any manuals which require TO numbers. AF procedures for numbering TOs are described in TO 00-5-3 and TO 00-5-18, AF Technical Order Numbering System.

7. Data Rights. The Contractor shall provide appropriate data rights for all baseline non-military aircraft and engine commercial manuals; all source data and/or TOs prepared specifically for this contract; and any TOs that are copyrighted or contains proprietary data or procedures IAW Special Contract Clause H007 and H024; and the Statement of Objectives.

8. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. The Contractor shall determine the correct markings and controls for classified and restricted distribution data and TOs IAW the program’s Security Classification Guide (SCG) and DOD 5200.1-R, DODD 5230.24, AFIs 63-101, 31-401 and 61-204, and MIL-STD-38784. The markings and notices shall be reviewed during In-Process Reviews (IPR). NOTE: Distribution limitations will be determined on a case-by-case basis as TOs are developed and dependent upon TO content.

9. TO Quality. The Contractor shall develop and implement a Quality Assurance (QA) program which ensures TOs are prepared IAW this contract. QA methods shall include actual performance of procedures and use of desk-top analysis for non-procedural data. Simulation (walk-through/talk-through) should be reserved for those procedures which would activate explosive devices or present an unacceptable hazard to personnel or equipment. The contractor’s QA methods shall ensure engineering reviews are completed prior to government verification/re-verification.

9.1. Conferences and Technical Reviews. The Contractor shall conduct conferences and reviews to allow insight into TO development processes and ensure contract compliance. The Contractor shall co-host an initial Guidance Conference within 60 days after contract award to ensure mutual understanding of TO contract requirements, schedules, points of contact, etc. The Contractor shall conduct periodic In-Process Reviews (IPRs) at the 75%, 90%, and 100% completion levels as referenced in TO 00-5-3 in preparation for Government verification; and a Prepublication Review (PPR) to ensure TOs are being developed according to contract requirements and that open discrepancies are cleared prior to publication. For electronic TO (eTO) based programs, IPRs subsequent to the initial review need to be accomplished using the approved eTO viewing solutions.

9.2. TO Certification. The Contractor shall develop and implement their method for documenting certification that TO procedures are safe, current, accurate, adequate, concurrent with aircraft configuration, and technically usable for their intended purposes. Certification must be completed prior to the Government performing its verification of all TOs.

9.3. TO Verification Support. The Contractor shall develop and implement methods, equipment and personnel required to support government TO Verification. This Contractor-provided support shall consist of as a minimum:

1) Dedicated (on-aircraft) Engineer(s) knowledgeable of the baseline non-military aircraft airframe, systems, engines, and subsystems.

2) Dedicated (on-aircraft) Engineer(s) knowledgeable for each of the militarized systems and subsystems installed in/on the baseline non-military aircraft.

3) The appropriate number of technical writers/data programmers to author real-time changes to ETMs and IETMs as the result of the verification effort.

4) The contractor shall provide a dedicated, on-aircraft, qualified maintainer to support all AF TOV activities to ensure procedures are conducted safely and ensure “return to service” documentation requirements are completed.

5) Type 1 Aircrew and Maintainer Training for all Air Force personnel identified as part of the TO verification team.

9.4. Technical Order Review Boards and Flight Technical Order Review Boards. The Contractor shall also participate in all Technical Order Review Boards (TORBs) and Flight TORBs.

9.5. Technical Data Assessment (TDA). The Contractor and the program office with the assistance of 754 ELSG/ILMT will determine the TDA requirements for each TO type. The Contractor shall submit an in-work sample of each type of XML-tagged TO file to the program office concurrent with the 75% IPR, for TDA to verify compliance of the digital files to Air Force Digital Support Suites (DSS). Repeat TDAs shall be required whenever new TMSS or DTD versions are used for TO development. TDA parsing in no way relieves the Contractor from correcting tagging errors identified during the composing effort.

10. TO and Source Data Maintenance. The Contractor shall develop and implement methods for maintaining accuracy, currency and configuration of TOs and source data throughout the contract period of performance. Maintenance includes preparation of TO and source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes.

11. TO Delivery. The Contractor shall develop and implement practices and procedures for secure access to and delivery of digital TO files, including those for Preliminary TOs (PTOs), source data, reproduction masters, and program support data. TO delivery formats shall be according to Section 2, Part C, Table 3 (TM Delivery Requirements) of this TMCR. Paper TO delivery is not acceptable for final delivery of TOs.

11.1. XML-Tagged Files. The Contractor shall parse and compose XML-tagged TO document files prior to delivery to the government, and verify that content tagging has been accomplished to the levels provided in the DTD. NOTE: The government will parse the files prior to acceptance using the public domain “XMLS Parser”.

11.2. XML-Tagged Files for Use with the eTO Viewer. The Contractor shall use the Government Furnished Equipment (GFE) transformer and Digital Formatted Output Specification Instance (DFOSI) to convert tagged instances to Hypertext Markup Language (HTML) files compatible with the eTO viewer, and certify the output complies with TMSS requirements.

11.3. Interactive Electronic Technical Manuals (IETM). The Contractor shall deliver the IETM data base according to the business rules for S1000D/XML in Section 3 of this TMCR.

12. Schedules. The Contractor shall include all TO program events and schedules in their Integrated Master Plan (IMP) and Integrated Master Schedule (IMS), and update the IMS throughout the period of performance. NOTE: AF policy requires delivery of verified TOs prior to or concurrently with delivery of operational equipment to the field (AFI 63-101, Technical Orders). This policy will determine TO development and delivery schedules throughout the acquisition phase of a program.

13. Engineering Change Proposals/Contract Change Proposals/Time Compliance Technical Orders (ECPs/CCPs/TCTOs). The Contractor shall develop and implement practices and procedures for related TO updates when tasked as part of the approval process for Engineering Change Proposals/Contract Change Proposals/Time Compliance Technical Orders (ECPs/CCPs/TCTOs) to configured ITEM. Costs for TCTO package development must be included in ECP Costs – not included as direct proposal costs. NOTE: ECPs are reviewed and approved by the Government’s Configuration Control Board (CCB). When the CCB decides that a TCTO is the appropriate method of implementation, the Contractor may be requested to develop the TCTO package for Air Force coordination and approval. See TO 00-5-15, Air Force Time Compliance Technical Order Process for a detailed description of TCTO processes.

14. TO Reproduction Management. The Contractor shall develop and implement a Reproduction Management process for digital media consisting of reproduction of the digital file on magnetic/optical media and distribution according to ID labels. Reproduction Management may also include configuration control and storage of reproduction masters.

Section 2. TM/TO Type and Delivery Requirements

NOTES:

· The TM Type Selection Tables indicating the applicable TO types and related specifications have been marked within minimum requirements.

· All page-based TOs developed under this contract must conform to the general style and format requirements of MIL-STD-38784; IETMs must conform to S1000D, Issue 4, and its business rules.

· Check the ASSIST database, http://dodssp.daps.dla.mil/assist.htm, for updated versions of the required TMSS prior to initiating any work on this proposal/contract.

· Manuals delivered using this table must be reviewed and approved by the Air Force prior to delivery.

· Illustrated Parts Breakdowns (IPBs) are developed IAW MIL-PRF-38807, except that MIL-DTL-87929 will also be used for IPBs combined with work packages.

· All checklists, except aircrew, are developed IAW MIL-DTL-5096.

· MIL-PRF-83495 requires MIL-HDBK-863 to be levied on engineering data for preparation of end item wiring data and schematic diagrams.

· Delivery requirements are indicated in the TM Delivery Requirements matrices.

· For further information on the Air Force Vision and TO Concept of Operations (CONOPS), see URL https://techdata.wpafb.af.mil/toprac/polinfo.htm.

PART A – TABLE 1

TMSS REQUIREMENTS FOR THE KC-X MODERNIZATION PROGRAM

Title or Type of Manuals

Specification Required

1. Inspection TOs MIL-DTL-5096

a. Inspection and Maintenance Requirements (-6) Manual

b. Acceptance and Functional Check Flight (FCF) Procedures (-6CF)

c. Acceptance and functional Check Flight (-6CL) Checklist

d. Workcards

e. Inspection Requirements Cards

f. Flow/Sequence Charts

g. Checklists

(1) Maintenance/Operations (Non-Aircrew)

(2) Operations (Aircrew)

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

2. Cargo Aircraft Loading and Offloading TOs

(including Hazardous cargo IAW AFMAN 24-204)

a. Manual

b. Checklists

MIL-PRF-5288

3. Weight and Balance (Aircraft) MIL-PRF-5288

a. Loading Data Manual T.O. 1-1B-50

b. Sample Basic Weight Checklists

FORMCHECKBOX

4. Flight Manuals (see notes) MIL-DTL-7700

a. Flight Manual

b. Performance Data Manual

c. Air Refueling Manual

d. Air Refueling Checklist

FORMCHECKBOX

FORMCHECKBOX

5. List of Applicable Publications MIL-PRF-8031 FORMCHECKBOX

PART A – TM/TO Type Selection Tables

PART A – TABLE 1

TMSS REQUIREMENTS FOR THE KC-X PROGRAM

Title or Type of Manuals

Specification Required

6. Structural Repair Manuals MIL-PRF-9854 FORMCHECKBOX

7. Work Unit Code Manual MIL-PRF-38769 FORMCHECKBOX

With Accompanying Software Tables for Work Unit Codes, How Malfunction Codes, When Discovered Codes, Type Maintenance Codes, and Action Taken Codes

8. Calibration Procedures MIL-PRF-38793 FORMCHECKBOX

9. Time Compliance Technical Orders (TCTOs) MIL-PRF-38804 FORMCHECKBOX

10. Aircraft Battle Damage Assessment and Repair TOs MIL-PRF-87158 FORMCHECKBOX

11. Illustrated Parts Breakdown MIL-PRF-38807 FORMCHECKBOX

12. On-Equipment Organizational Maintenance manual Set (see notes) MIL-PRF-83495

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

b. General System (GS) Manual

c. Combined GE & GS Manual

d. Job Guide (JG) Manuals

e. Fault Reporting (FR) Manual

f. Fault Isolation (FI) Manual

g. Wiring Data (WD) Manual

h. Schematic Diagram (SD) Manual

13. Operation and Maintenance Instructions in Work Package Format MIL-DTL-87929

(1) System Peculiar Corrosion Control FORMCHECKBOX

(2) Nondestructive Inspection (NDI) FORMCHECKBOX

(3) Aircraft Structural Integrity Program (ASIP) FORMCHECKBOX

(4) Propulsion System Integrity Program (PSIP) FORMCHECKBOX

(5) Avionics Integrity Program (AVIP) FORMCHECKBOX

(6) Mechanical Equipment and Subsystem Integrity Program (MESIP) FORMCHECKBOX

(7) Weapon System Integrity (WSI) FORMCHECKBOX

(8) ATE Operator Test Procedures FORMCHECKBOX

(9) Operators Instructions (Hand-Held Flight Computers) FORMCHECKBOX Installation-Engineering Facility (Ground C-E Equipment) FORMCHECKBOX Checklists (IAW MIL-DTL-5096) FORMCHECKBOX

a. With Illustrated Parts Breakdown (see notes) FORMCHECKBOX

14. Commercial Manuals MIL-PRF-32216 FORMCHECKBOX

15. Aircraft Cross-servicing Guide MIL-DTL-22202 FORMCHECKBOX

16. Interactive Electronic Technical Manuals (IETMs) ASD/AIA S1000D FORMCHECKBOX

17. Support Equipment / Test, Measure, Diagnostic, Equipment SE/TMDE) MIL-DTL-87929 FORMCHECKBOX

18. Concurrent Aircraft Servicing Checklists MIL-DTL-5096 FORMCHECKBOX

PART B – TABLE 2

ADDITIONAL TM/TO TYPE SELECTIONS

NOTES:

· These manuals and or source data shall be developed and delivered in AIA S1000D, issue 4, or XML digital format.

· The technical manuals called out in this table, with the exception of item numbers 1,3,6,7, and 16, are tailored manuals or data that is commercially available to all airframe customers as called out in the Data Catalog.

· For commercial manual supplemental data only, under the specification heading, enter “Same style and format,” “MIL-PRF-38807” (for IPB data), or “MIL-STD-38784.”

· For existing MIL-SPEC manuals not being updated to latest specification requirements, enter “Same style and format” under the specification heading.

· For NGS manuals, list the type of manual in the appropriate column and the NGS in the Specification column. Approved NGS manuals shall meet the functional requirements of the approved TMSS for the TO type, e.g., OMMS prepared to S1000D, Issue 4, shall meet the requirements of MIL-PRF-83495 (which serves as business rules for manual style, format, and content).

1. The Contractor shall develop and deliver applicable source data for use by firefighter and rescue personnel in the event of an incident. The KC-X program will use this and other contractor data to provide information on installed HAZMAT to the Air Force Civil Engineer Support Agency for inclusion in the Air Force Technical Order 00-105E-9, Aerospace Emergency Rescue and Mishap Response Information.

2. The Contractor shall develop and deliver a FAA required Extended-range Twin-engine Operations/Long-range Operation Procedures (ETOPs/LROPs) commercial manual.

3. The Contractor shall identify KC-X impacts, incorporate these impacts into and deliver the ATP-56B in place of the Air Refueling Manual.

4. The Contractor shall develop and deliver a KC-X Incident/Accident Investigation Manual based on the existing commercial Airplane Recovery Manual but supplemented with additional data per National Transportation and Safety Board (NTSB) guidance on aircraft systems and performance background data. This manual is required by the NTSB to be a separate stand-alone commercial-formatted manual, not a supplement to the existing manual. It must reflect the final configuration of the aircraft including the militarization modifications.

5. The Contractor shall develop and deliver a Short Term (not to exceed 360 calendar days) Aircraft Storage manual.

6. The Contractor shall develop and deliver source data for all applicable TO 00-20 series manuals that are affected by FAA maintenance documentation and record-keeping requirements for O-level Air Force maintainers.

7. The Contractor shall develop and deliver source data for AFM 23-110 to include all FAA parts documentation and record-keeping requirements for the Air Force Supply system.

8. The Contractor shall develop and deliver a tailorable Flight Crew Training Manual (FCTM) (including software for tailored version) for use by Aircrew Training System personnel based upon the FCTM furnished to commercial customers tailored for KC-X operations.

9. The Contractor shall develop and deliver a Tanker Airlift Command Center (TACC) Dispatcher Planning Manual based upon the commercial Flight Planning Manual.

10. The Contractor shall provide Performance Engineer’s Handbook (PEH) updated to reflect KC-X configuration and performance based upon the PEH furnished to commercial customers.

11. The Contractor shall provide Flight Operations Engineering Performance Software that should be the typical tabulated performance data and fleet performance tracking software made available to commercial customers to include tailoring for KC-X configuration and performance and with a user’s manual based upon the Ops engineering performance software programs furnished to commercial data (tabulated data, course monitoring, etc.).

12. The Contractor shall provide Flight Operations Engineering Training Course Manuals that are the same commercially offered course manuals updated to reflect any KC-X unique applications based upon the commercial offerings of Ops engines courses tailored for KC-X applications.

13. The Contractor shall provide Maintenance Engineering Training Course Manuals that are the same as the commercially offered course manuals from the maintenance planning and development manuals updated for any KC-X unique applications.

14. The Contractor shall provide Flight Safety Training Manuals that are the same as the commercially available FAA/EASA mandated training manuals (e.g. wind shear, takeoff safety, etc).

15. The Contractor shall provide Human Factors in Maintenance (HFIM) Manuals that are the same as the manuals and training material for the initial training course and for implementing the HFIM program at the unit level based upon the FAA/EASA requirements for HFIM implementation by commercial customers.

16. The Contractor shall provide KC-X source data to the Joint Services Aircraft Servicing Guide IAW AFI 91-202, Section 9.7 and TO 00-25-172.

TO Number, Title, or Type of Manual

Specification Commercial Manual

Change/ Revision

Supplement Supplemental TM

Source Data

1. 00-105E-9, Aerospace Emergency Rescue and Mishap Response Information (Emergency Services)

MIL-STD-38784

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

3. ATP-56B

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

4. KC-X Aircraft Incident /Accident Investigation Manual

NTSB Regulation

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

5. Short Term Aircraft Storage Manual

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

6. Applicable OO-20 Series TOs

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

7. AFM 23-110

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

8. Flight Crew Training Manual (tailorable) including software for tailored version

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

9. TACC Dispatcher Planning Manual

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

10. Performance Engineer’s Handbook

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

11. Flight Operations Engineering Performance Software

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

12. Flight Operations Engineering Training Course Manuals

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

13. Maintenance Engineering Training Course Manuals

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

14. Flight Safety Training Manuals

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

15. Human Factors in Maintenance Manuals

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

16. Joint Services Aircraft Servicing Guide IAW AFI 91-202, Section 9.7 and TO 00-25-172

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

FORMCHECKBOX

PART C - TABLE 3

TM/TO DELIVERY REQUIREMENTS

FOR

KC-X TANKER MODERNIZATION PROGRAM

TM/TO DATA TYPE DELIVERED

Delivery Format Requirements Codes:

Digital delivery only:

M - Mixed paper and digital (X)

EXAMPLE: M(X) / 2 [Paper and XML / 2 copies]

NOTES:

· Delivery format requirements codes indicate the media/file format to be delivered for each program event.

· TCTO requirements are specified in the contract vehicle approving the TCTO.

· When on-line access is a contractual requirement, copy quantity will normally be ( (zero).

· For NGS or non-standard TMSS instances, delivery shall include the associated DTDs, FOSIs/Style Sheets, XML schemas, etc.

DELIVERY SCHEDULE

Event Number of days data required prior to event Enter Office Symbol and Address

Enter delivery requirements code/copy quantities required

836 AESG/SYL

2590 Loop Road West, BLDG 558

Wright-Patterson AFB, OH 45433-7142

Section 3. Specification/Standard Interface Records (SIRs) Standardization Interface Record for ASD-S1000D, Issue 4, Business Rules - International Specification for Technical Publications Utilizing a Common Source Database

3. Refer to the RFP Technical Reference Library for the following documents:

3.1 S1000D Finalized Business Rules.pdf

3.2 S1000D Tag Description Tables (TDT).pdf

3.3 MIL-DTL-S1000D-BR.pdf (Detail Specification Air Force Business Rules for S1000D Issue 4.0 -International Specification for Technical Publications Utilizing A Common Source Data Base)

3.4 XML BREX file name: DMC-USAF-A-00-00-00-00A-022A-D 001-00 EN-US

ATTACHMENT 1

AIR MOBILITY COMMAND FLIGHT MANUAL MATRIX

The purpose of the AMC Flight Manual matrix is to identify requirements for tailoring the prospective KC-X offerors' commercial flight manuals. This matrix provides required tailoring efforts. It is expected that the offerors' commercial flight manuals already comply with the intent of the remainder of MIL-DTL-7700G. If this is not the case, the offeror shall identify any gaps in coverage by paragraph. While select portions of MIL-DTL-7700G are provided in this document, in the essence of brevity, not all of the detail specification is listed. Reference MIL-DTL-77000G for full paragraph descriptions. This document does not replace requirements referenced in the Air Force Technical Manual Contract Requirements (TMCR), FA8625-10-R-6600, Attachment 8, section 2.1.

When specified (see 6.2), a status page shall be provided as part of the change package. This status page shall be similar to the status page for the flight manual supplements (see Figure 2), with the following exceptions: A. The lead in statement shall read:

This page is published with each change package for Flight Manual Program publications. It contains a listing or the affected Flight Manual and its related Supplements and Checklists current on the date of this publication. However, formal Safety and Operational Supplements that are issued after the publication of this change, will contain a more current version of the status page. Changes or revisions that are in production are shown in parentheses.

B. The status page for changes shall be located immediately following the final page of the List of Effective Pages. It shall be numbered with an alphanumeric number which follows sequentially the last page of the List of Effective Pages. The page number and change designator shall be located as specified in MIL-STD-38784.

page starting with an introduction paragraph.

A. For flight manuals: The words "TECHNICAL MANUAL" shall be replaced by FLIGHT MANUAL.

B. For performance data manuals: The words "TECHNICAL MANUAL" shall be replaced by Flight Manual Appendix 1 Performance Data.

C. For supplemental manuals: the words "TECHNICAL MANUAL" shall be replaced by: Supplemental Flight Manual.

A. Predeparture - Names of flight crew, destination, altitude of flight, time of flight, use of equipment, location of emergency exits, introduction to alarm bell and other ITEM (such as smoking on military flights).

B. Over-water - Emergency equipment, location of safety jackets, and other ITEM.

C. Arrival - Advice during descent pertaining to seat belts, local time, no smoking, and like ITEM.

This briefing must address minimum FAA required ITEM

B. Normal flight characteristics

C. Dive recovery characteristics

D. Flight with asymmetric loads

E. Abnormal flight characteristics

F. Stalls

G. Departures

H. Spins

I. Engine operation

J. Engine out

K. Air Refueling capability as both a tanker and receiver Should add loss of pod in-flight

Part 1 - General. This part will contain the following general information and operational procedures which encompass air refueling operations by all types of aircraft:

A. Command and control or tanker/receiver forces

B. General tanker/receiver responsibilities. Information to specific aircraft types/models will also be included

C. Refueling airspace requirements. D. Weather restrictions

E. Communications requirements.

F. Visual signals