TM_86_01N_1April2009.docx

Air Force Technical Manual Contract Requirements (TMCR) For Sustainment and Upgrade of Select KC-135 Technical Orders

ATTACHMENT 1, T.O. CDRL SEQUENCE NUMBER A008, CONTRACT: FA8105-11-D-0002

Date: 18 April 2014 Technical Manual/Technical Order requirements contained herein have been cleared for use by OMB Paperwork Reduction Project No. 0704-0188.

Section 1. Technical Order (TO) Program Requirements

1. TMCR Tailoring. This TMCR has been tailored to meet the requirement for sustainment and upgrade of select KC-135 technical orders. It includes the development and delivery for three categories of technical order changes: (a) Category A - Non-modification related TO changes; (b) Category B - Modification related TO changes, and (c) Unique changes – Development of Technical Manual (TM) data not considered non-modification or modification related changes, purchasing of data or services, conversion of legacy data into approved digital formats or completion of similar TM efforts required to support the KC-135 weapons system. The tailoring accomplished in this TMCR is compatible with Air Force/KC-135 infrastructure and support KC-135 Integrated Data System (IDS) requirements.

2. TO Program Scope. Section 2 of this TMCR has been tailored to include required TO types (TMCR Table 1) and source data, TO updates, and TOs prepared to Non-Government Standards (NGS) (TMCR Table 2) required to support the objectives of Performance Work Specification (PWS) AFLCMC/WKDAC-SOW 14-012, entitled KC-135 Engineering Sustainment Support.

3. Commercial Manuals. No commercial manuals will be upgraded and/or sustained under this TMCR.

4. Technical Manual Specifications and Standards (TMSS) Tailoring. TM updates shall be developed in accordance with the requirements of MIL-STD-38784A, MIL-DTL-7700G, MIL-PRF-38807 and others (see TMCR Table 1) as applicable or as otherwise directed by the Government as required on individual Engineering Assignments (EAs). The TM updates shall be authored and delivered in the format or language as specified in the EA such as Direct Image Reproducibles (DIRs), Negatives, Postscript, Portable Documents Format (PDF), Indexed PDF (IPDF), Standard Generalized Mark-up Language (SGML), Extensible Mark-up Language (XML), Hyper Text Mark-up Language (HTML), or other media agreed-upon by the Government and contractor.

5. Subsequent TO/Data Requirements. The lists of applicable TMs by number that will be upgraded/sustained under the TMCR are specified in PWS AFLCMC/WKDAC-SOW 14-012, Paragraphs 3.4.15 and 3.4.16, Tables 3.4-1 and 3.4-2. This document is not applicable to any other TO, TM, or technical document.

6. TO Development. The contractor shall develop and deliver modification and non-modification driven TM changes, revisions, and/or supplements to the TMs listed in PWS AFLCMC/WKDAC-SOW 14-012, Paragraph 3.4.15 and 3.4.16, Tables 3.4-1 and 3.4.2 as directed by individual EAs. The TM data shall be developed in accordance with T.O. 00-5-1 to ensure that TOs and data are compatible with the Air Force Technical Order Concept of Operations (CONOPS) (available on the AF Portal at https://wwwd.my.af.mil/afknprod/DocView.asp?DocID=1689861) and the Enhanced Technical Information Management System (ETIMS). In addition, TOs shall be written 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 be responsible for technical integration and accuracy, grammatical editing, style and format of delivered material. The contractor shall ensure that new illustrations are line drawings. The contractor shall recommend technical manual changes, additions, deletions, or improvements of a technical nature to the TO Manager for approval and PCO notification. The Contractor shall recommend technical manual changes, additions, deletions, or improvements of a contractual nature to the PCO in writing for approval.

6.1. Page-oriented Military Specification (MILSPEC) TOs shall be formatted with text, graphics and delivery according to the TMSS specified in Section 2. The contractor shall develop TO files (tagged instances) using Standard Generalized Markup Language (SGML) according to the DTDs referenced in the appendix to MIL-STD-38784 and each applicable military detail or performance specification (MIL-DTL or MIL-PRF).

6.2. SGML-tagged TO files 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, or contact the 754 ILMT via e-mail at SGMLSupport@wpafb.af.mil). NOTE: Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible.

6.3. Deleted. Not applicable to this T.O. sustainment contract.

6.4. Deleted. Not applicable to this T.O. sustainment contract.

6.5. Deleted. Not applicable to this T.O. sustainment contract.

7. TO Numbering. The contractor shall notify the government of manuals which require TO numbers. TO numbers are not required for manuals to be used exclusively by the contractor’s own personnel. (NOTE: DI-TMSS-80067 may be used to provide the notification.) AF procedures for numbering TOs are described in TO 00-5-3 and TO 00-5-18, AF Technical Order Numbering System, (available at http://www.tinker.af.mil/library/factsheets/factsheet.asp?id=6082/).

8. Data Rights. Government rights in data are specified in the Defense Federal Acquisition Regulation Supplement (DFARS), paragraphs 227-7102 through 227-7104. All T.O. changes/upgrades shall be delivered with Unlimited Rights; if that is not possible, the contactor shall stop work immediately and notify the contract Quality Assurance Person (QAP) in AFLCMC/WKDAC for further direction.

8.1. Deleted. Not applicable to this T.O. sustainment contract.

8.2. Deleted. Not applicable to this T.O. sustainment contract.

9. 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 KC-135’s Security Classification Guide (SCG) and DOD 5200.1-R, DODD 5230.24, AFIs 21-303, 31-401 and 61-204, and MIL-STD-38784. The contractor shall ensure TM changes, revisions, and/or supplements are marked with the appropriate classification and distribution statements.

10. TO Quality. The contractor shall be responsible for quality control of all TM changes, revisions, and/or supplements generated under this TMCR. This shall include technical integration and accuracy, grammatical editing, style and format of delivered materials.

10.1. Conferences and Technical Reviews. The contractor shall attend up to 3 Flight Manual Review Conferences (FMRC’s) per contract option year as requested by the TOMA. Each FMRC may last up to five days including travel time and will be conducted at a CONUS location. Attendance at each FMRC will be limited to 1 contractor engineer or technical writer. The contractor shall prepare minutes for each FMRC and the Government will review and approve the minutes prior to distribution. Requirements for periodic reviews to ensure TOs are being developed according to contract requirements and that open discrepancies are cleared prior to publication will be accomplished as RTIs or as specified in individual EAs as required. For eTO based programs, IPRs subsequent to the initial review need to be accomplished using the approved viewing presentation system. NOTE: PPRs are required for critical safety procedures TOs, and may be required for other complex procedures TOs.

10.2. TO Certification. The contractor shall certify that TO data delivered to the Government is accurate, adequate, current, safe and usable for the intended purpose.

10.3. Verification Support. The contractor shall assume that all TM source data provided under this TMCR for development as formal changes, revisions, and/or supplements has been validated/verified unless otherwise in the individual EA. If a conference is required to validate/verify any developed technical data, the Government will provide the aircraft, facilities, equipment, and maintenance man-power needed to accomplish it.

10.4. Technical Data Assessment (TDA – originally called First Article Testing). Not applicable to this T.O. sustainment contract.

11. TO and Source Data Maintenance. The contractor shall develop and deliver modification and non-modification driven TM changes, revisions, and/or supplements to the TMs listed in PWS AFLCMC/WKDAC-SOW 14-012, Paragraphs 3.4.15 and 3.4.16, Tables 3.4-1 and 3.4-2 as directed by individual EAs. The contractor shall maintain accuracy, currency and configuration of TOs and source data throughout the contract option year. Maintenance includes preparation of TO and source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes.

12. TO Delivery. The contractor shall deliver all TM changes, revisions, and/or supplements to AFLCMC/WKDMA as specified on the individual EAs. The delivery schedule for TM changes, revisions, and/or supplements delivered under this TMCR will be mutually agreed upon by the Government and contractor before release of the EA. The contractor shall utilize practices and procedures for secure access to or delivery of digital TO files, including those for Preliminary TOs (PTOs), source data, reproduction masters, and program support data. Practices and procedures shall be compatible with the program’s IDS. TO file delivery formats shall be according to applicable CDRLs and the tailored TM Delivery Requirements Matrices included in Section 2 of this document.

12.1. SGML-Tagged Files. The contractor shall parse and compose SGML-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.

12.2. SGML-Tagged Files for Use with the eTO Viewer. The contractor shall use the GFE ETIMS eTO Viewer/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.

12.3. Interactive Electronic Technical Manuals (IETM). IETM data base delivery shall be according to the business rules for S1000D in Section 3 of this document.

12.4. Indexed Adobe™ Portable Document Format (IPDF) Files. The contractor shall certify indexing of PDF TO files using the specifications contained in the Technical Order Conversion Requirements (TOCR) found on the Air Force Portal at https://wwwd.my.af.mil/afknprod/DocView.asp?DocID=5153963

13. Schedules. The contractor shall deliver the completed TM changes, revisions, and/or supplements in accordance with the due date specified on each individual EA. In addition, the contractor shall report the status of TM changes, revisions, and/or supplements in a monthly Technical Order Status and Schedule (TOSS) report in accordance with CDRL 004 to PWS AFLCMC/WKDAC 14-012, C/KC-135 Engineering Sustainment Support.

14. Time Compliance Technical Orders (TCTOs). The contractor shall develop and deliver TCTOs when specifically directed by an individual EA. The TCTO shall be developed in accordance with T.O. 00-5-15 using standard Air Force style and format. The contractor shall not deviate from established style and format requirements without approval of the PCO.

15. TO Reproduction Management. Deleted. Not applicable to this T.O. sustainment contract.

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

· Mark the TM Type Selection Tables indicating the applicable TO types and related specifications. For additional interface requirements see the program-specific Government Concept of Operations (GCO).

· 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 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 and DI-TMSS-80067, CFAE/CFE Notices, must be reviewed and approved by the Air Force prior to delivery.

· 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 and nuclear weapons checklists, are developed IAW MIL-PRF-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 AF Portal URL https://wwwd.my.af.mil/afknprod/ASPs/DocMan/DocMain.asp?Filter=OO-EN-TO-PI&FolderID=OO-EN-TO-PI-15&Tab=0.

PART A – TM TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE KC-135 Engineering Sustainment Support Program

a. Inspection and Maintenance Requirements (-6) Manual

|X|

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

|X|

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

|X|

d. Work cards

|X|

e. Inspection Requirements Cards

|X|

f. Flow/Sequence Charts

|X|

g. Checklists

(1) Maintenance/Operations (Non-Aircrew)

|X|

(2) Operations (Aircrew)

|X|

a. Manual

|X|

b. Checklists

|X|

a. Loading Data Manual

|X|

b. Sample Basic Weight Checklists

|X|

a. Flight Manual

|X|

b. Performance Data Manual

|X|

c. Air Refueling Manual

|X|

d. Air Refueling Checklist

|X|

a. Nuclear Weapons Basic Information and Loading Procedures

b. Nuclear Weapons Loading Procedures

c. Non-nuclear Munitions Basic

d. Non-nuclear Loading Procedures

e. Integrated Combat Turnaround Procedures

f. Non-nuclear Munitions Loading Standard Data Packages (SDPs)

g. Loading Procedures Checklists

h. Integrated Loading Procedures Checklists

i. Nuclear Weapons Loading Procedure Checklists

j. Integrated Combat Turnaround Procedures Checklists

k. NATO Stage B Cross-Servicing Checklists

8. Space Operations and Support Documentation TOs -- Commercial specification (all space systems & missiles) -- MILSPEC (Intercontinental Ballistic Missiles) -- MILSPEC (Space Systems)

a. Operations Manual

b. Operations Checklists

c. Technical Manuals and Related Checklists

a. Non-nuclear Weapon Delivery Manual (Strategic Bomber & Tactical Aircraft)

b. Nuclear Bomb Delivery Manual (Strategic Bomber Aircraft)

c. Aircrew Nuclear Weapon Delivery Manual (Strategic Bomber Aircraft)

d. Aircrew Nuclear Weapon Delivery Manual (Tactical Aircraft)

e. Non-nuclear Weapon Delivery Checklist (Strategic Bomber & Tactical Aircraft)

f. Nuclear Bomb Delivery Checklist (Strategic Bomber Aircraft)

g. Aircrew Nuclear Weapon Delivery Checklist (Tactical Aircraft)

h. Non-nuclear Weapon Delivery Source Data Packages

a. General Equipment (GE) Manual

|X|

b. General System (GS) Manuals

|X|

c. Combined GE & GS Manual

|X|

d. Job Guide (JG) Manuals

|X|

e. Fault Reporting (FR) Manual

f. Fault Isolation (FI) Manual

g. Wiring Data (WD) Manual

h. Schematic Diagram (SD) Manual

a. Maintenance Manuals

(1) Intermediate Maintenance

|X|

(2) Depot Maintenance

|X|

(3) Combined (I&D) Maintenance

|X|

(4) On Condition Maintenance

|X|

b. Operation & Maintenance Instruction Manuals

|X|

c. Special Manuals

(1) Aircraft Engine Testing and Trending Procedures

(2) Aircraft Power Package Testing Procedures

(3) Static Firing of Missile Motors

(4) System Peculiar Corrosion Control

|X|

(5) Nondestructive Inspection (NDI)

|X|

(6) Aircraft Structural Integrity Program (ASIP)

|X|

(7) ATE Operator Test Procedures

|X|

(8) Special Requirements for Storage and Maintenance Procedures; AUR Munitions/Launchers and Associated Support Equipment, Conventional Components and CMBR Agents

(9) Parachute Packing Procedures

(10) Operators Instructions (HandHeld Flight Computers)

(11) InstallationEngineering Facility (Ground C-E Equipment)

d. Checklists (IAW MIL-PRF-5096)

|X|

e. With Illustrated Parts Breakdown (see notes)

|X|

TABLE 2

ADDITIONAL TM TYPE SELECTIONS

NOTES:

· Check all applicable boxes.

· 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 manuals proposed to NGS, list the type of manual in the appropriate column and the NGS in the Specification column. Manuals proposed to an approved NGS shall meet the functional requirements of the approved TMSS for the TO type, e.g., OMMS prepared to S1000D shall meet the requirements of MIL-PRF-83495 (which serves as business rules for manual style, format, and content).

TO Number, Title, or Type of Manual

Specification Commercial Manual

Change/ Revision

Supplement Supplemental TM

Source Data

PART B - TM DELIVERY REQUIREMENTS

FOR KC-135 ENGINEERING SUSTAINMENT SUPPORT T.O.S

1. TM DATA TYPE DELIVERED CHANGE PAGES

Delivery Format Requirements Codes

Digital delivery only:

X - Extensible Mark-up Language (XML) C – Composite IPDF of Entire TO with changes incorporated

EXAMPLE: M(G) / 2 [Paper and SGML / 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

AFLCMC/WKDMA

3001 Staff Dr., Ste 2AE187E Tinker AFB, OK 73145-3019

* Delivery events and number of copies required for TM change pages will be specified on individual EAs

2. TM DATA TYPE DELIVERED TO REVISIONS

Delivery Format Requirements Codes

Digital delivery only:

X - Extensible Mark-up Language (XML) C – Composite IPDF of Entire TO with changes incorporated

EXAMPLE: M(G) / 2 [Paper and SGML / 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

AFLCMC/WKDMA

3001 Staff Dr., Ste 2AE187E Tinker AFB, OK 73145-3019

* Delivery events and number of copies required for TO revisions will be specified on individual EAs

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

NOTES:

· All TMSS applicable to this contract shall have an appropriately tailored SIR attached to this section.

· SIRs included in the untailored TMCR format represent the minimum tailoring requirements that must be included in the final contract, unless the entire SIR is not applicable; e.g., if MIL- STD-38784, is not required, the entire SIR can be deleted.

· MIL-STD-38784 must be included in all contracts/proposals for AF TMSS-developed TOs.

· Digital requirements shall not be tailored out. Tailoring shall be limited to the options expressed in paragraphs 6.2. Any requests for tailoring outside of these requirements must be coordinated with the specification Preparing Activity (PA) 754 ELSG/ILMT.

· Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available from the DoD Single Stock Point (DODSSP), Acquisition Streamlining and Standardization Information System (ASSIST) web page, http://www.dodssp.daps.dla.mil/assist.htm.

· Non-government Standards (NGS) shall be provided by the offeror. The Government will not be responsible for providing NGS.

· TMSS entries designated with A, F, M or N refer to Army, Air Force, Marine Corps or Navy requirements.

· Beneficial comments, recommendations, additions, data etc. which may be of use in improving any Air Force TMSS should be addressed to “Air Force Technical Manual Specifications and Standards Office, 754 ELSG/ILMT, Wright-Patterson AFB, OH 45433”. Do not include the street address, a building number, or a zip+4.

Standard Practice for Manuals, Technical: General Style and Format Requirements

Global: Change references to “MIL-STD-1806” to read “DODD 5230.24.”

NOTE: The <figtable> element, if included in the DTD, shall not be used in maintenance manuals.

* 4.5.1.10 Disclosure Notice. Change 1st sentence to read: “…except those with Distribution Statement A, IAW AFI 21-303 (F):”

* 4.5.1.11 Distribution Statement. Replace the last sentence with: “Include both the distribution statement letter (“A,” “B,” etc.) and wording from DODD 5230.24. Include the “Reason,” “Controlling DoD office,” and “Date of Determination” when required. If the reason is “Proprietary Data,” then each TM page containing proprietary data must be marked with the company name and the word “Proprietary” (e.g., “Boeing Proprietary”).”

4.5.1.13 Destruction Notice. Change the existing sentence to read: "...or X shall be marked with Handling and Destruction Notice "a" (below) on the cover/title..." Add a new second sentence as follows: "Unclassified TOs authorized for Public Release (Distribution Statement "A") shall be marked with disposition notice "b" (below) on the title or T-2 page."

* 4.5.1.14 Copyright Credit Line. Add “If a copyright credit line is required, include a statement of government rights to publish, reproduce, and distribute the TM.”

Time Compliance Technical Orders – Preparation

NOTE: Entries marked with an asterisk (*) will have to be manually entered and tagged in SGML files until the specification and its associated DTD and FOSI have been updated to incorporate the changes. The rescission date and statement will continue to appear in paragraph 3 of SGML-tagged TCTO files until the DTD and FOSI are updated.

e. TO update accuracy.

f. Proper function of the modified equipment.”

Specification/Standard Interface Record for ASD-S1000D Business Rules (date) International Specification for Technical Publications Utilizing a Common Source Database

TBD