A001.pdf

http://dodssp.daps.dla.mil/assist.htm

2 TM-86-01N 1 April 2009 cial manuals, and MIL-DTL-7700, Detail Specification: Flight Manuals, Air Refueling Procedures, And

Abbreviated Checklists, as an additional guide for commercial Flight Manual contents.

4. Technical Manual Specifications and Standards (TMSS) Tailoring. TMSS are tailored by selecting between options offered in paragraph 6.2 of each TMSS. The tailoring is recorded in SIRs and added to

Section 3 of this document for each TMSS required. NOTE: Tailoring must not change or delete man-datory requirements which are part of the Document Type Definition (DTD) structure.

4.1. AF options in some Joint-Service TMSS have been documented in preliminary SIRs included in Section 3. These preliminary SIRs provide the starting point for further tailoring. Offerors shall complete tailoring of the Joint-Service TMSS SIRs and provide recommended SIRs for other TMSS or NGS as applicable. NOTE: TMSS requirements marked “(F)” are specifically for Air Force use;

“(A)” is for Army, “(M)” is Marine Corps and “(N)” is Navy. Comply with all unmarked and “(F)”

TMSS requirements as modified by the options in paragraph 6.2.

4.2. (T) Questions concerning TMSS requirements may be resolved by written request and justified suggestions for resolution submitted through the Procuring Contracting Officer (PCO) and WR-

ALC/GRUKA - 235 Byron Street, Suite 19A, Robins AFB, GA 31098-1647. Deficiencies and sug-gested improvements shall be submitted to the TMSS Preparing Activity (PA). Approved recom-mendations, corrections and clarifications will be maintained with contract documentation.

5. Subsequent TO/Data Requirements. Offerors shall propose a process for notifying the government when additional TO or source data requirements are identified subsequent to contract award. This process shall require government review and approval of recommended additional requirements prior to contractual approval. NOTE: The recommended notification process is to use CFAE/CFE Notices (DI-

TMSS-80067).

6. TO Development. The offeror shall propose TO development practices and procedures that ensure TOs and data are compatible with the Air Force Technical Order Concept of Operations (CONOPS) (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 cov-erage 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.

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 graph-ics 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 deli-vered for other purposes shall be used in lieu of developing special TM illustration files whenever possible.

6.3. (T) Interactive Electronic Technical Manuals (IETMs) shall be developed IAW MIL-PRF-

87268 Manuals, Interactive Electronic Technical General Content, Style, Format, and user interac-tion requirements, and MIL-PRF-87269 Performance Specification for the Support of Data base, Revisable-Interactive Electronic Technical Manuals. Additional requirements for MIL-PRF-87269 and MIL-PRF-87269 are included in the SIR found in Section 3 of this document. Contact the Pro-

TM-86-01N 1 April 2009 3 curing Contracting Officer (PCO) and IETM TO Manager to request guidance from the Air Force

Preparing Activity (PA), 754 ELSG/ILMT, Technical Order Section, 4375 Chidlaw Rd Suite 6, WPAFB OH 45433-5006.

6.4. The offeror may propose use of other Non-Government Standards (NGS) for development of

TOs, but must justify this choice based on life-cycle cost savings to the government and compatibili-ty with existing systems identified in the IDS and the System Support Plan.

6.5. The contractor shall contact 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 offeror 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 so-lutions. New DTDs shall not be developed in lieu of existing DTDs, including those for legacy

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 ap-proved in execution of the contract shall become the property of the Government. Direct questions about the application of SGML tagging to digital TO files to 754 ELSG/ILMT (SGMLSup-port@wpafb.af.mil).

7. TO Numbering. Offerors shall notify the government of manuals which require TO numbers. TO numbers are not required for manuals to be used exclusively by the offeror’s own personnel. (NOTE:

DI-TMSS-80067 may be used to provide the notification.) AF procedures for numbering TOs are de-scribed 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. Offerors shall propose Unlimited

Rights for all source data and TOs prepared specifically for the contract.

8.1. If some TOs or source data are copyrighted or contain proprietary data or procedures, offerors may propose Limited Rights or Government Purpose Rights (GPR) only. Proposed commercial ma-nuals should be provided with at least GPR or Limited Rights. Copyrights shall be according to

DFARS paragraphs 227-7103, 7105 or 7106.

8.2. Specifically, if an NGS is proposed, the government shall be given unlimited rights for all busi-ness rules (tailoring and application methods and procedures) and documented business processes developed for use in TO development. Government data rights shall extend to the common source database, transformation style sheets, and other tools or products used to author or display NGS technical data.

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. Offerors shall de-termine 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 21-303, 31-401 and 61-204, and MIL-STD-38784 (available at http://www.e-publishing.af.mil/ or http://dodssp.daps.dla.mil/assist.htm). 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, dependent upon TO content.

10. TO Quality. Offerors shall propose a quality assurance program which ensures TOs are prepared

IAW this contract. Recommended QA methods must include actual performance of procedures and use of desk-top analysis for non-procedural data. Simulation (walk-through/talk-through) should be re-served for those procedures which would activate explosive devices or present a hazard to personnel or equipment. Offerors’ proposals shall describe how the government will be allowed to interact with the http://www.e-publishing.af.mil/

4 TM-86-01N 1 April 2009 contractor’s TO development team. NOTE: Quality requirements for the Joint Nuclear Weapons Pub-lications System (JNWPS) and for Non-nuclear Explosive Ordnance Disposal (EOD) Data are contained in TO 11N-1-1 and DOD Directive 5160.62, respectively. The government will performance-tests all

JNWPS and EOD TOs.

10.1. (T) Conferences and Technical Reviews. Offerors shall propose sufficient conferences and reviews to allow insight into TO development processes and ensure contract compliance. Offerors should host an initial Guidance Conference or Technical Interchange Meeting (TIM) within 60 days of contract award to ensure mutual understanding of TO contract requirements, schedules, points of contact, etc. Periodic In-Process Reviews (IPRs) ensure TOs are being developed according to con-tract requirements and that open discrepancies are cleared prior to publication. IPRs typically con-sist of a 40%, 80%, Verification and Final Review. IPRs are set up at the discretion of the

TOMA/FMM and will be addressed at the Guidance Conference. The TOMA/FMM must be noti-fied 30 days prior to any conferences or reviews. For eTO based programs, IPRs subsequent to the initial review need to be accomplished using the approved viewing presentation system.

10.1.1 (T) Interactive Task Review (ITR)

The contractor shall integrate government Central Technical Order Control Unit (CTOCU) person-nel into the development process. During the maturity of the IETM database, the contractor is re-sponsible for the development of all the data, and CTOCU personnel will evaluate the data during the development. The contractor will provide CTOCU personnel access to the developmental IETM database. ITRs will be conducted to ensure developmental issues have been resolved and to verify all requirements have been met.

The contractor shall host and co-chair ITRs to ensure that the IETM database and additional data development is being developed in accordance with the contract and cited specifications. ITR intervals and completion criteria will be as stated in paragraph 10.1.1.1. Additional ITRs may be required based on the contractor's or government's evaluation of the IETM database and addi-tional data development process or the criticality and complexity of the material covered. Re-views will be conducted to evaluate database content and functionality in terms of relationships between data elements within the database. The contractor shall make a copy of the develop-ment database available to the government 30 days prior to the scheduled ITR. This database shall have the contractor’s Engineering (when applicable) and Quality Assurance review com-ments incorporated into the database prior to delivery for the scheduled review. Additionally, copies of the Database Discrepancy Reports will be available to the government at the scheduled review. All data presented for ITR will have the contractor’s Quality Assurance and engineering signatures (when appropriate) and meet full MIL-Spec requirements. The contractor shall sup-port ITRs with TO writers, engineers (if required), and any additional personnel that may have an impact on the IETM database preparation. A complete listing of source data used to develop the IETM database shall be at each ITR. This requirement may be waived by the TOMA on an event-by-event basis.

10.1.1.1 (T) ITR Requirements for the IETM database

1. (T) Initial Review. To meet criteria for the Initial Review, the IETM IDET must contain 80% of the required tasks for that system (i.e., if the system contains 100 tasks, 80 of those tasks would be present in the database for the Initial Review). The Initial Review will be delivered in conjunc-tion with the 80% IPR paper TO submittals. These tasks include:

a. Preparations

TM-86-01N 1 April 2009 5

b. Restorations

c. General Instructions

d. Removals

e. Installations

f. Operational Checkouts

g. Fault Reporting Procedures

h. Fault Isolation Procedures

i. Parts Data

j. Available functionality

In addition to 80% of the tasks, the database will contain a percentage of the data required to sup-port those tasks. The following is a breakdown of that supporting data:

a. 100% of all consumables for 80% of the tasks authored

b. 100% of all Warnings, Cautions, and Notes for 80% of the tasks authored

c. 100% of parts data for 80% of the tasks being authored

d. 100% of descriptive information modules for 80% of the tasks authored

e. 100% of wiring data for 80% of the tasks authored

f. 100% of wiring diagrams for 80% of the tasks authored

2. (T) Pre-Integration Review. The requirements for a Pre-Integration Review are the same as the initial reveiw except for the percentage of data present in the database at the time of the ITR. The

Pre-Integration Review will be delivered in conjunction with the Verification IPR copy of the pa-per TO submittals.

NOTE: If a contractor’s digital IETM format does not merge into the IETM data-base it will/may be sent back to the contractor for corrections.

10.2. TO Certification. Offerors shall propose their method for documenting certification that TO procedures are accurate, adequate, current, safe and usable for their intended purposes. Offerors shall notify the government at least 180 days prior of the need for any Government Furnished Infor-mation/Government Furnished Equipment (GFI/GFE) required to perform certification tasks.

10.3. (T) Verification Support. Offerors shall propose the methods, equipment and personnel re-quired to support government TO Verification. This support should consist of at least a Lead Tech-nical Writer, knowledgeable on the system and a System Qualified Engineer.

10.4. Technical Data Assessment (TDA – originally called First Article Testing). The program office, with the assistance of 754 ELSG/ILMT and the contractor, will determine the TDA requirements for each TO type. The contractor will submit an in-work sample of each type of SGML-tagged TO file to the program office concurrent with the first IPR, for TDA to verify compliance of the digital files to

Air Force DSSs. Additional TDAs may be required based on initial results. The TDA parsing in no way relieves the contractor from correcting tagging errors that are noted during the composing effort.

Repeat TDAs shall be required whenever new DSS or DTD versions are used for TO development.

The contractor shall deliver a representative percentage of Indexed Portable Document Format (IPDF)

TO files to verify indexing compliance with the Technical Order Conversion Requirements (TOCR)

(on the AF Portal at https://wwwd.my.af.mil/afknprod/DocView.asp?DocID=5153963).

11. (T) TO and Source Data Maintenance. Offerors shall propose 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

6 TM-86-01N 1 April 2009 configuration changes, and maintenance and operational concept changes. Editorial and Technical Con-tent cut-off will be the close and acceptance of the 80% minutes and closure of all action items from that

In-Process Review (IPR).

12. TO Delivery. Offerors shall propose 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. Paper TO delivery is not acceptable for final delivery of

TOs. EXCEPTION: For Commercial Manuals not available digitally.

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. NOTE: The government will parse the files prior to acceptance us-ing the public domain “SGMLS Parser” (ftp://ftp.jclark.com/pub/SGMLS).

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 accord-ing to the business rules for S1000D in Section 3 of this document.

12.4. Indexed Adobe™ Portable Document Format (IPDF) Files. The contractor shall validate 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. (T) Schedules. Offerors shall include TO program events and schedules in their proposed Inte-grated 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 21-303, Technical Orders). This policy will determine TO development and delivery schedules throughout the acquisition phase of a program. Any change to the IMS must be coordinated with the TOMA/FMM. A copy of the updated IMS will be pro-vided to the TOMA/FMM.

14. Time Compliance Technical Orders (TCTOs). Offerors shall propose practices and procedures to develop AF TCTOs and related TO updates when tasked as part of the approval process for Engineering

Change Proposals (ECPs) to configured items. 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 appro-priate 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, (available at http://www.tinker.af.mil/library/factsheets/factsheet.asp?id=6082/00-5-15-WA-

1/00-5-15.PDF) for a detailed description of TCTO processes.

15. (T) TO Reproduction Management. Offerors shall propose practices and procedures for managing the program’s Preliminary TO reproduction requirements. MIL-HDBK-38790, Printing Production of

Technical Manuals, may be used as guidance for TO printing format, paper weights, layout require-ments, etc. NOTE: Reproduction management for formal TO printing includes assembly of a print package (reproduction media, a reproduction assembly sheet).

ftp://ftp.jclark.com/pub/SGMLS

TM-86-01N 1 April 2009 7

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.

Editorial and Technical Content cut-off will be the close and acceptance of the 80% minutes and closure of all action items from that In-Process Review (IPR).

Delivery requirements are indicated in the TM Delivery Requirements matrices.

Change package format deliveries will be with accompanying back-up pages. Source data deliveries will be delivered in change package format without accompanying back-up pages. No manuscript source will be accepted.

FrameMaker files will be delivered with version 7.0 or higher for Flight Manuals using GFE furnished CD-ROM with supporting DTDs & FOSIs.

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.

https://wwwd.my.af.mil/afknprod/ASPs/DocMan/DocMain.asp?Filter=OO-EN-TO-PI&FolderID=OO-EN-TO-PI-15&Tab=0 https://wwwd.my.af.mil/afknprod/ASPs/DocMan/DocMain.asp?Filter=OO-EN-TO-PI&FolderID=OO-EN-TO-PI-15&Tab=0

8 TM-86-01N 1 April 2009

PART A – TM TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE Installation of Electronic Propeller Control System (EPCS) On Selected C-130

Aircraft (1C-130-2065)(Effort 2) Program

(System/Component)

Title or Type of Manuals Specification Required

1. Inspection TOs MIL-PRF-5096

a. Inspection and Maintenance Requirements (-6) Manual

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

Manual

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)

2. Cargo Aircraft Loading and Offloading TOs MIL-PRF-5288

a. Manual

b. Checklists

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

a. Loading Data Manual

b. Sample Basic Weight Checklists

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

a. Flight Manual

b. Performance Data Manual

c. Air Refueling Manual

d. Air Refueling Checklist

5. List of Applicable Publications MIL-PRF-8031

6. Structural Repair Manuals (for Aircraft) MIL-PRF-9854

7. Munitions/Weapons Loading Procedures, Non- nuclear and Nuclear MIL-PRF-9977

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)

ANSI/AIAA-R024-1993

MIL-PRF-38311

MIL-PRF-38314

a. Operations Manual

b. Operations Checklists

TM-86-01N 1 April 2009 9

TMSS REQUIREMENTS FOR THE Installation of Electronic Propeller Control System (EPCS) On Selected C-130

Aircraft (1C-130-2065)(Effort 2) Program

(System/Component)

Title or Type of Manuals Specification Required

c. Technical Manuals and Related Checklists

9. Nuclear and Non-nuclear Weapon Delivery and Aircrew Procedures Manuals and Checklists

MIL-PRF-38384

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

10. Work Unit Code Manual MIL-PRF-38769

11. Calibration Procedures MIL-PRF-38793

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

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

14. Illustrated Parts Breakdown MIL-PRF-38807

15. On-Equipment Organizational Maintenance Manual Set (see notes) MIL-PRF-83495

a. General Equipment (GE) Manual

b. General System (GS) Manuals

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

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

a. Maintenance Manuals

(1) Intermediate Maintenance

(2) Depot Maintenance

(3) Combined (I&D) Maintenance

(4) On Condition Maintenance

b. Operation & Maintenance Instruction Manuals

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

(5) Nondestructive Inspection (NDI)

(6) Aircraft Structural Integrity Program (ASIP)

10 TM-86-01N 1 April 2009

TMSS REQUIREMENTS FOR THE Installation of Electronic Propeller Control System (EPCS) On Selected C-130

Aircraft (1C-130-2065)(Effort 2) Program

(System/Component)

Title or Type of Manuals Specification Required

(7) ATE Operator Test Procedures

(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 (Hand-Held Flight Computers)

(11) Installation - Engineering Facility (Ground C-E Equipment)

d. Checklists (IAW MIL-PRF-5096)

e. With Illustrated Parts Breakdown (see notes)

17. Commercial Manuals (Evaluate according to MIL-PRF-32216)

18. Aircraft Cross-servicing Guide MIL-DTL-22202

19. Interactive Electronic Technical Manuals (IETM - Contact Bruce Gelinas,

(478) 222-1267 or DSN 472-1267, for IDET Updater Tool.)

MIL-PRF-87268

MIL-PRF-87269

ASD-S1000D (Ref.

only)

TM-86-01N 1 April 2009 11

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

Com-mercial

Manual

Change/

Revision

Supple-ment

Supple-mental

TM

Source

Data

1. 1C-130-2-WA-2**

ASD-S1000D

MIL-PRF-87268

MIL-PRF-87269

SD

2. 1C-130A-6WC-13

Same Style and Format

CHANGE

3. 1C-130A-6WC-14

Same Style and Format

CHANGE

4. 1C-130H-2-34FI-10-1

Same Style and Format

CHANGE

5. 1C-130H-2-34FI-40-6

Same Style and Format

CHANGE

6. 1C-130H-2-34JG-10-1

Same Style and Format

CHANGE

7. 1C-130H-2-61JG-10-1

Same Style and Format

CHANGE

8. 1C-130H-2-70GS-00-1

Same Style and Format

CHANGE

9. 1C-130H-2-76JG-00-1

Same Style and Format

CHANGE

10. 1C-130H-4-33-1 Same Style and Format

CHANGE

11. 1C-130H-4-34-1 Same Style and Format

CHANGE

12. 1C-130(L)H-1CL-2*

Same Style and Format

CHANGE

13. 1C-130E(H)-6CF-1*

Same Style and Format

CHANGE

*-Flight Manual

**- IETMS

***-New TOs/TCTOs

12 TM-86-01N 1 April 2009

PART B - TM DELIVERY REQUIREMENTS

FOR INSTALLATION OF ELECTRONIC PROPELLER CONTROL SYSTEM (EPCS) ON SELECTED C-130

AIRCRAFT (1C-130-2065)(EFFORT 2)

(System/Item)

TM DATA TYPE DELIVERED (SEE TABLE 2).

(TMSS/Change/Supplement/etc.)

(Replicate form for each TM type required.)

Delivery Format Requirements Codes

Digital delivery only:

P - Paper (draft or manuscript only. Cannot be used for final delivery)

F - FrameMaker 7.0 or higher (For FMs - use GFE furnished CD-ROM with supporting DTDs & FOSIs.)

G - Standard Generalized Mark-up Language (SGML).

M - Mixed paper and digital (F, G, H, I, N or X) H - Hyper Text Mark-up Language (HTML) (Helicopters only)

E – IETM in IDET format

I - Indexed Portable Document Format (IPDF) File. (IPDF

- new/complete TOs or PDF - change/source packages)

N - Native Format (i.e. – PageMaker, FrameMaker, Portable Document Format (PDF))

X - Extensible Mark-up Language (XML)

All Final Delivery of graphics will be ISO Draw 6.0 or higher as Computer Graphic Metafile (CGM/4) for

E/F/G/H/I/X EXAMPLE: M(G/P)/2 [Paper and SGML/2 copies]

All change/source pages will be 100% vector art format, no raster art accepted. Back-up pages may be raster art.

All IETMs deliveries will be in IDET format. Contact Bruce Gelinas for IDET Updater Tool.

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

AFTO Form 158s will be provided by the Contractor after every In-Process Review (IPR).

TO Updates. From each IPR, will be provided to the TOMA/FMM 30 days prior to the next IPR.

Editorial and Technical Content cut-off will be the close and acceptance of the 80% minutes and closure of all action items from that In-Process Review (IPR).

The IETM Initial Review will be delivered in conjunction with the 80% IPR copies and the Pre-Integration Review will be delivered in conjunction with the verification copies. Contact Bruce Gelinas, (478) 222-1267 or DSN 472-1267, for

IDET Updater Tool.

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

Technical

Review(s)

(30 Days)

Verification

(30 Days)

Final TO

Distribution

(45 Days)

Enter Office Symbol and Address Enter delivery requirements code/copy quantities required

Attn: Willie Curry (Maint. Man. Only)

WR-ALC/GRUEF

235 Byron St., Suite 19A

ROBINS AFB GA 31098

P/1 P/I/1 M(N/I/P)1

Attn: Suzanne Dunn-Poorman (Flt. Man. Only)

WR-ALC/GRUEF

235 Byron St., Suite 19A

ROBINS AFB GA 31098

F/1 F/1 F/I/1

TM-86-01N 1 April 2009 13

Attn: Bruce Gelinas (IETMs Only)

WR-ALC/GRUEF

235 Byron St., Suite 19A

ROBINS AFB GA 31098

E/1

P/2

E/1

P/2 E/1

Attn: Kris Riddle (Equip. Specialist)

WR-ALC/GRBEA

235 Byron St., Suite 19A

ROBINS AFB GA 31098

P/1 P/I/1 P/I/1

Total Copies Required: P/4

E/1

F/1

E/1

F/1

P/2 P/I/2

E/1

F/I/1

M(N/I/P)1

P/I/1

14 TM-86-01N 1 April 2009

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 in-cluded in the final contract, unless the entire SIR is not applicable; e.g., if MIL-DTL-22202D is not required, the entire SIR can be deleted.

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

Most specification “Acquisition Requirements” list the same two items for paragraphs 6.2a and 6.2b. For this contract enter:

6.2a. The title, number and date of each specification will be listed in the heading of the applicable SIR.

6.2b. The issue of the DODISS used in this contract is (enter date).

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.

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-DTL-22202D, 31 March 1999

Supplement 1, 31 March 1999

Manual, Technical, Aircraft Cross-Servicing Guide, Preparation of

The requirements of 6.2 are met in this SIR (see below).

1.1 In addition to paper delivery, when this specification is used to develop digital delivery files (document type defi-nitions – DTDs) contact the PA for additional instructions.

2.3 Ensure the listing for STANAG/ASCC Air Standard Documents is current. List applicable STANAG/ASCC Air

Standards below.

(List STANAG/ASCC Air Standard Documents here.)

2.2.1 (Added) “Other government documents, drawings, and publications.

DEPARTMENT OF DEFENSE

DOD 5200.1-R DoD Information Security Program Regulation

DOD 5220.22-M National Industrial Security Program Operating Manual

4. Replace with: “4. VERIFICATION.

“All cross-servicing guides shall meet the requirements of sections 3 and 5 of this specification, as re-quired by the acquiring activity. The requirements set forth in this specification shall become a part of the contractor’s overall inspection system or quality program. The absence of any requirements in this specification shall not relieve the contractor of the responsibility of ensuring that all products or supplies submitted to the government for acceptance comply with all requirements of the contract. Use of sam-pling inspections shall be at the discretion of the contractor, and in accordance with commercially ac-ceptable quality assurance procedures. However, use of sampling in QA procedures does not authorize submission of known defective material, either indicated or actual, nor does it commit the government to accept defective material.”

http://www.dodssp.daps.dla.mil/assist.htm

TM-86-01N 1 April 2009 15

5. Replace with: “5. PACKAGING.

“5.1 Packaging Requirements. For acquisition purposes, the packaging requirements shall be as spe-cified in the contract or order. When the actual packaging of material is to be performed by DoD per-sonnel, these personnel need to contact the responsible packaging activity to determine packaging re-quirements. Packaging requirements are maintained by the Inventory Control Point’s packaging activ-ity within the Military Department’s System Command. Packaging data retrieval is available from the

Military Department’s or Defense Agency’s automated packaging files, CD-ROM products, or the re-sponsible packaging activity.

“5.1.1 Encoded Computer Products. Packaging of encoded computer products for delivery shall be in accordance with the requirements of MIL-STD-1840.

“5.1.2 Classified Material. Classified material shall be packaged and identified in accordance with

DOD 5200.1-R, DOD 5220.22-M, and the implementing Service regulations.”

6.2a Title, number, and date of the specification are listed above.

6.2b Issue of DODISS: (fill in issue of DODISS applicable to this contract)

6.2c Packaging requirements (see above).

6.2d Verification requirements (see above).

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-STD-38784, 2 July 1995

Notice 1, 15 November 2000

Notice 2, 1 December 2000

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

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

3.2.8 Continuous Tone Artwork. Delete paragraph.

3.2.9 Copy Freeze Date. Delete paragraph.

3.2.10 Cutline. Delete paragraph.

3.2.20 Layout Page. Delete paragraph.

4.2.1.2.1 Oversize Reproducible Copy. Delete paragraph.

4.2.7.1 Table Cutline (see 3.2.10). Delete paragraph.

4.2.8.1 Illustration Cutline (see 3.2.10). Delete paragraph.

4.2.8.3 Amend as follows: “4.2.8.3 Illustration legends (see 3.2.23). Legends shall be headed by the word “Le-gend” followed by the number of the figure to which it is applicable (see Figure 6). The entire legend shall be indented 5 spaces. If the legend is continued, the figure number and title shall be repeated, followed by a dash and the word “Continued.” Only that information which is necessary to clearly identify the items shall be included in the legend. Where methods such as the tabular presentation technique (as in an Illu-strated Parts Breakdown/Repair Parts and Special Tools List) are used, no legends are required.”

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

* 4.5.1.10 Disclosure Notice. Change 1 st 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 pro-prietary data must be marked with the company name and the word “Proprietary” (e.g., “Boeing Proprie-tary”).”

4.5.1.13 Destruction Notice. Change the existing sentence to read: "...or X shall be marked with Handling and De-struction 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" (be-low) on the title or T-2 page."

4.5.1.13.a. Designate existing paragraph as "a. HANDLING AND DESTRUCTION NOTICE..."

Add: "See TO 00-5-1 for specific destruction procedures."

16 TM-86-01N 1 April 2009

4.5.1.13.b (Added) b. “DISPOSITION NOTICE - Refer to TO 00-5-1 for disposition instructions.”

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

4.5.3 List of Effective Pages. Change the first sentence to read: “A List of Effective Pages shall be prepared in ac-cordance with Figure 13. Page borders shall be optional.”

4.6.2 Photographs/line drawings. Delete paragraph.

4.6.3.1 Retouching. Delete paragraph.

4.6.3.2 Prescreened photographs. Delete paragraph.

4.6.4 Continuous Tone Artwork (see 3.2.8). Delete paragraph.

4.6.5 Combination Artwork. Delete paragraph.

4.6.12 Color in Illustrations. Delete the first sentence: “Unless otherwise specified (see 6.2), color shall not be used.”

4.6.12.1 Separation of Colors. Delete paragraph.

4.6.12.2 Register Marks. Delete paragraph.

4.6.20 Crop and Size Marks. Delete.

4.6.21 Mounting of Artwork. Delete paragraph.

4.6.22 Identifying Artwork. Delete paragraph.

4.6.23 Covering of Artwork. Delete paragraph.

4.6.24 Review of Illustrations. Delete paragraph.

4.7.1 Advanced Change Pages. Delete paragraph.

4.7.2 Changes to Cover and Title Page. In the first sentence, delete the phrase “Except for silk screened or otherwise expensive covers”.

4.7.3.4 Transmittal Cover Sheets. In the last sentence, delete the phrase “i.e. reproducible copy, negatives, magnetic tape, disk, etc.”.

4.7.3.5 Changes to Illustrations. Delete paragraph.

4.9.2 Safety Supplements (see Figure 37). Change first sentence to read: Safety supplement “SS” borders and the words “SAFETY SUPPLEMENT” at the top and bottom of the supplement shall be in red. Other text, letter-ing, numbering, etc, shall be in black.”

Figure 5, Example Typical RDC Page. Delete.

Figure 25 Cropping and Sizing of Illustrations. Delete.

Figure 26, Identification, Marking, and Protective Covering of Artwork. Delete.

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-PRF-38804C, 1 March 1996

Amendment 1, 20 June 1997

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.

Amendment 1 Delete entirely.

2.2.2 Change “AFM 67-1” to “AFMAN 23-110.”

3.5.2g Add new line: “g. Rescission Date (see 3.5.2.6.1)” Renumber following paragraphs to “h” through “l”.

3.5.2.4 Change 1

st sentence to read: “…supplement thereto (see 3.6) provided by the acquiring activity on an AFMC

Form 873 (see 6.5).”

3.5.2.5 Change 1

st sentence to read: “…acquiring activity on an AFMC Form 873 (see 6.5).”

TM-86-01N 1 April 2009 17

3.5.2.6 Change 1

st sentence to read: “…acquiring activity on an AFMC Form 873 (see 6.5).” Change last sentence to read: : “The year, month, and day shall be in the YYYYMMDD format (see Figures 1 through 6).”

3.5.2.6.1 (Added) “Rescission Date. The contractor shall enter the TCTO rescission date in the upper right corner of the first page immediately below the TCTO issue date. The rescission date will be specified on the AFMC Form 873 (see 6.5). The date will be in the YYYYMMDD format.”

3.5.2.8 Add to the end of the paragraph: “See TO 00-5-15 for additional guidance.”

3.5.2.9.1d Change to read: “…reinstating and establishing a new rescission date for rescinded TO…”

3.5.2.9.4 Change “AFMC/AFCC” to “AFMC/AFCA/AFSPC”

3.5.3.3 Change “proofing” to “verification” (4 places)Change last sentence to read: “…waived, the office symbol, e-mail address and Defense Switched Network (DSN) phone number of the approving official shall…”

3.5.5.3 Replace “a” through “d” with the following:

a. (Added) Routine Safety Inspection Organizational/Intermediate Level TCTOs. “Not later than (#) days after receipt of this TCTO. Affected system/equipment shall be removed from service if this TCTO is not ac-complished within the specified number of days, or 60 days prior to the TCTO rescission date, whichever comes first. The specified number of days for accomplishment shall be provided on the AFMC Form 873

(see 6.5).

b. Routine Action, Organizational/Intermediate Level, Safety TCTO. "Not later than ____ days after receipt of (this TCTO) (kits) (parts) (special tools). Failure to accomplish this TCTO by the preceding specified number of days, or 60 days prior to the TCTO rescission date, whichever comes first, shall automatically re-strict operations or shall be justification for withdrawing affected system/equipment from service until com-pliance is accomplished. The specified number of days for accomplishment shall be provided on an AFMC

Form 873 (see 6.5).

c. Routine Action, Organizational/Intermediate Level TCTO. Organizational/Intermediate level TCTOs hav-ing a compliance period in terms of days shall read: "Not later than ____ days after receipt of (this TCTO)

(kits) (parts) (special tools). Failure to accomplish the work by expiration of the compliance period, or 60 days prior to the TCTO rescission date, whichever comes first, shall be justification for withdrawing the af-fected system/equipment from service until compliance is accomplished. The specified number of days and requirements for accomplishment shall be provided on an AFMC Form 873 (see 6.5).

d. Routine Action, Organizational/Intermediate Level, Based Upon Maintenance Practice. When the time period for accomplishment cannot be specified as a certain number of days after receipt of the TCTO, kits, parts or special tools, the TCTO may specify compliance at the time a known maintenance event occurs, such as "At the time of removal from Emergency War Order (EWO) status (or During scheduled modernization ac-tion). If not complied with by (date), or 60 days prior to the TCTO rescission date, whichever comes first, the system/equipment shall be removed from active service until compliance with the TCTO is accomplished.

The preceding phrase is an example of the type to be used and may be expanded or worded to the individual requirement as needed. Use of the phrases "upon failure," "upon accumulation" or "when reaching" are not authorized for any TCTO. The required statement shall be provided on an AFMC Form 873 (see 6.5).

e. Routine Action, Depot Level. These modifications require specified accomplishment at a time designated by the acquiring activity by means of the AFMC Form 873 (see 6.5) at overhaul, contractor team, force mod-ernization, AFMC schedule or whatever other phrase that is most appropriate.

3.5.5.4 Add new sentence as follows: “The required statements shall be provided on an AFMC Form 873 (see 6.5).”

3.5.5.5 (Added in Amendment 1) Delete.

3.5.7.1.1.1 Change 4th and 5th lines to read: “…concept waived by (insert name/rank/office symbol/DSN phone number and e-mail address of the Lead Command POC authorizing a waiver of the complete…”

3.5.7.2 Change “proofing” to “verification” (2 places)

3.5.7.2.1 (Added) “For Inspection TCTOs, the AFSCs and manhours shall be based on Maintenance Data Collection

(MDC) records. The equivalent work phases will be:

a. Equipment preparation.

18 TM-86-01N 1 April 2009

b. Access work area.

c. Perform inspection.

d. Close work area.

e. Operational check and documentation.”

3.5.7.2.1 (Existing) Renumber as 3.5.7.2.2.

3.5.10.1.4 Change last line to read “...with the criteria established in AFI 21-103, Chapter 9 (-21 TOs).

3.5.11.1 Change 1

st sentence to read: “…the name, organization and office symbol, DSN telephone number, and e-mail address of the POC responsible…”

Change 2 nd sentence to read: “…and the information for the POC authorizing…”

3.6 Delete the last sentence (“All supplements shall be assigned a new data code number.”)

3.6.1 Change 1

st sentence to read: “…supplement, or it explicitly changes the TCTO rescission date.”

3.6.6 Delete “, IF APPROVED BY THE MAJCOM,” in the NOTE text.

4.1 Change title to “Contractor Prototyping.”

4.1b Change to read: “…perform the prototyping functions specified…”

4.1d Change to read: “…review any of the prototyping functions, when…”

4.1.1 Change “verification” to “prototyping” (2 places)

4.1.1d, e & f (Added) “d. Form, fit and function of TCTO kits and modified components.

e. TO update accuracy.

f. Proper function of the modified equipment.”

5.2 Replace with: “Bill of Materials. TCTO kits shall contain a Bill of Materials listing all of the items required to ac-complish the TCTO. As a minimum, the format of the Bill of Material shall be as follows:”

6.2l Change to read: “Issue and Rescission dates (see 3.5.2.6 & 3.5.2.6.1).”

6.2x Delete.

6.4.8 Change “verification” to “prototyping” (2 places)

6.4.8a Add “Includes validating the form, fit, and function of any kits involved, accuracy of associated TO updates, and proper operation of the modified equipment.”

6.5 Change 1

st sentence to read: “…are contained in TO 00-5-15, Air Force Time Compliance Technical Order

Process.”

6.6 Add “prototyping” and “supplement” to key word list.

Figures 3, 4 & 5 Change “Proofing” to “Verification” in each figure.

Standardization Interface Record for MIL-DTL-87268C, 22 January 2007

Manuals, Interactive Electronic Technical -

General Content, Style, Format, and User-Interaction Requirements

Note: Minimum tailoring requirements for para 6.2 are defined below. The acquiring activity shall complete the tai-loring of para 6.2 requirements and insert them as required below.

c. The IETM content shall be baselined to support the 5- through 7-skill level (see AFMAN 36-2108) (see 3.3.1).

e. Separately developed skill level tracks shall be provided in such a manner that the novice user is prohibited from accessing the higher skill level track (see 3.3.2).

g. US standards of measurement shall be used throughout the IETM (3.3.4.5b.).

h. A "permitted word" list(s), shall not be used (see 3.3.4.7). Style of writing shall be as specified in MIL-STD-

38784.

j. Nomenclature shall be as specified in the specification (see 3.3.5.7).

TM-86-01N 1 April 2009 19

k. The human figures used in graphics shall be presented in a gender neutral form and clothing shall depict the uni-form associated with the maintenance being performed (see 3.3.5.9).

l. Wire lists, schematics, and wiring diagrams referenced by an associated text pane shall be as specified herein (see

3.3.5.12).

m. Locator graphics shall be an automated part of procedural and descriptive information (see 3.3.5.14).

r. The footer bar shall be located as specified in 3.5.1.3 and figure 5.

w. Step numbering shall be one level for on-equipment tasks; procedural data for general tasks shall follow MIL-STD-

38784 (see 3.6.1.2.3).

Standardization Interface Record for MIL-DTL-87269C, 22 January 2007

Amendment 1 14 February 2002

Data Base, Revisable—Interactive Electronic Technical Manuals, For The Support Of

INTRODUCTION

This specification shall be used in conjunction with document 87269-e for new acquisition. Existing IETMs programs do not require modification to comply with 87269-e, unless so directed by the PCO.

Note: To ensure portability of existing IETM architectures to future IETM system requirements, careful con-sideration should be given to compliance with emerging IETM functionalities.

If a program manager is considering conversion of existing MILSPEC ETM (Type 1) data to IETM (Type 2)

(see definitions below), a comprehensive analysis of complete TO program requirements against the 87269-e, a functionality matrix and associated handbook must be developed and documented. How the program data will be used and accessed by the user is essential in this first stage. Costs will then have to be determined for con-version of existing TO data to the proposed target format.

Next, any additional functionality that needs to be available within the presentation system must be identified and added to the decision documents. Sustainment costs and processes for managing the data can then be folded into the equation. A business determination to move to Type 2 data can then be made, if the expense to convert is justified by reduced life-cycle costs or increased functionality for the user.

Assistance in business process analysis and acquisition guidance is available from the Technical Manual Speci-fications & Standards (TMSS) Section, 754 ELSG/ILMT. However, the acquisition authority or TO manager is far more familiar with the data and system to be supported and will do the major portion of this work.

Some initial steps that can be taken include, though are not limited to:

1. Looking closely at the method used to distribute and display the data at the point of use

2. Deciding how the…