ATCH-10 - Technical Manual Contract Requirements (TMCR).pdf

GUEE 23-15 Date: 2023-12-21

AIR FORCE TECHNICAL MANUAL CONTRACT REQUIREMENTS (TMCR)

MOBILE AIRCRAFT ARRESTING

SYSTEMS

DATA ITEM NO TBD, TBD, TBD

CONTRACT NUMBER TBD, CLIN TBD

CONTRACT TYPE: Firm-Fixed-Price (FFP) New Acquisition-(Revision)

TMCR TYPE: SGML/XML

SECTION 1. TECHNICAL ORDER (TO) PROGRAM REQUIREMENTS – TMSS

SGML/XML TMS

1. TMCR Tailoring. The Contractor may propose and submit, in writing, additional tailoring to the Technical Order Manager Agency/Agent (TOMA), Government Program Manager (PM) and Procuring Contracting Officer (PCO) as required by Section L of the RFP. The contractor may also submit additional Section 2 tailoring to propose new TO types (Table 1) and source data and TO updates (Table 2) required to support the Mobile Aircraft Arresting Systems program’s objectives. Modifications to contracts can continue to utilize the existing format until renegotiated/replaced. The acceptance of any contractor tailored TMCR will be at the discretion of the government and is not in effect until accepted in writing by the PCO or specified in the contract.

2. TO Program Scope. The Contractor must develop and deliver technical manuals in accordance with (IAW) this TMCR and the attached TMSS Tailoring Tool (section 3) that supports the Aircraft Arresting Systems requirements for technically usable manuals.

3. Technical Manual Specifications and Standards (TMSS) Tailoring. AF TMSS tailoring options and some Joint Service TMSS have been documented in preliminary Specification/Standard Interface Records (SIRS) included in Section 3. These preliminary SIRs provide the starting point for further tailoring.

Contractors may recommend additional tailoring of the Joint Service TMSS SIRs and provide recommended SIRs for other TMSS as applicable. Tailoring must not change or delete mandatory requirements which are part of the XML schema structure or Document Type Definition (DTD) located in Section 2, Table 1.

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 tailoring options in each TMSS.

3.1. Questions concerning TMSS requirements may be submitted in writing with suggestions for resolution and supporting information to the PCO and Debra Johnson,406 SCMS/GUEE 235 Byron Street, Ste. 19A Robins AFB, GA 31098-1670, 478-497-5295. Deficiencies and suggested improvements may be submitted to the TMSS Preparing Activity (PA). Recommendations, corrections and clarifications approved by the PCO, if any, will be maintained with contract documentation.

4. Subsequent TO/Data Requirements. When new TO requirements are identified the Contractor must notify the Government utilizing DI-TMSS-80067C, Technical Manual (TM) Contractor Furnished Aeronautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices, or approved Contractor formats. This process must require Government review and approval of recommended additional requirements prior to developing additional data. When approved, the Contractor must incorporate the requirements within the Technical Manual Content and Product Plan where applicable.

5. TO Development. TOs must be written to a scope and depth of coverage to support the Mobile Aircraft Arresting Systems operations and maintenance concepts.

5.1. Standard Generalized Markup Language (SGML) tagged TO files must include required illustration (graphics) files in an approved graphics exchange format. Illustration files developed and delivered for other purposes must be used in lieu of developing special TM illustration files whenever possible. All delivered graphics must conform to the approved graphic creation and format guidelines listed in Attachment 1, Graphics Format Guidelines. For assistance with illustration requirements contact AF TMSS via (e-mail: SGMLSupport@us.af.mil).

5.2. Page-oriented Military Specification (MIL-SPEC) TOs must be formatted with text, graphics and delivered according to the TMSS specified in Section 2. The Contractor must develop TO files (tagged instances) using SGML according to the DTDs referenced in the appendix to MIL-STD-38784 and each applicable military detail specification (MIL-DTL). Multiple SGML file instances for a single TO document are not authorized.

6. TO Numbering. N/A

7. Data Rights. Contractors must comply with 10 U.S.C. 2320 and Defense Federal Acquisition Regulation Supplement (DFARS) provisions and clauses. The Government’s rights in technical data are specified in DFARS 252.227-7013, Rights in Technical Data-Noncommercial Items, 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, and 252.227-7015, Technical Data-Commercial Items and other applicable provisions and clauses from DFARS 227, 252.227, and DFARS 252.227-7018 Rights in Noncommercial Technical Data and Computer Software – Small Business Innovation Research (SBIR). In accordance with those clauses and provisions, the Contractor grants the Government Unlimited Rights, as defined therein, in all source data, TO publications, TO updates, and TO-related documents prepared specifically for the contract. The Contractor also grants the Government Unlimited Rights in all Government-funded business rules (tailoring and application methods and procedures) and documented business processes developed under the contract for the purpose of or for use in TO development. The contractor is required to deliver TO data with the data rights license required by the applicable DFARS clauses. Contractor must identify any data to be delivered to the Government with other than Unlimited Rights IAW DFARS 252.227-7017, Identification and Assertion of Use, Release, or Disclosure Restrictions and must mark such data only in accordance with the applicable DFARS clause. The Contractor must pass through and enforce all requirements in this TMCR to all sub-Contractors.

7.1. The Government shall have unlimited rights in technical data that are created exclusively with Government funds in the performance of a contract that does not require the development, manufacture, construction, or production of items, components, or processes; form, fit, and function data; necessary for installation, operation, maintenance, or training purposes (other than detailed manufacturing or process data.

8. Classification, Distribution, Destruction, Disclosure, Export Control Notices, and Cyber Security.

Contractors must recommend the correct markings and controls for classified and restricted distribution data and TOs IAW the program’s Security Classification Guide and Department of Defense Manual (DODM) 5200.01V2 AFMAN 16-1404V2, Department of Defense Instruction (DODI) 5230.24, Department of Defense Directive (DODD) 5230.25, DoDI 5200.48, Controlled Unclassified Information, DAFI 61-201, Management of Scientific and Technical Information (STINFO), and MIL- STD-38784 (available at https://www.esd.whs.mil/dd/dod-issuances/, http://www.e-publishing.af.mil/ or https://quicksearch.dla.mil/qsSearch.aspx). The markings and notices must be reviewed during In-mailto:SGMLSupport@us.af.mil https://www.esd.whs.mil/dd/dod-issuances/ http://www.e-publishing.af.mil/ https://quicksearch.dla.mil/qsSearch.aspx

Process Reviews (IPR). The Contractor must also apply policy and procedures for Cybersecurity Program Management IAW AFI 17-130, AFMAN 17-1301, Computer Security (COMPUSEC)

NOTE: Distribution limitations will be determined on a case-by-case basis as TOs are developed, dependent upon TO content.

DISCLOSURE NOTICE - This information is furnished upon the condition that it will not be released to another nation without the specific authority of the Department of the Air Force of the United States, that it will be used for military purposes only, that individual or corporate rights originating in the information, whether patented or not, will be respected, that the recipient will report promptly to the United States, any known or suspected compromise, and that the information will be provided substantially the same degree of security afforded it by the Department of Defense of the United States. Also, regardless of any other markings on the document, it will not be downgraded or declassified without written approval of the originating United States agency.

DISTRIBUTION STATEMENT C - Distribution authorized to U.S. Government Agencies and their contractors (Export Controlled) (01 December 2023). Other requests for this document shall be referred to 406 SCMS/GUEE, Robins AFB, GA 31098. Questions concerning technical content shall be referred to AFLCMC/WNZEC.

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Section 2751 of Title 22, United States Code) or the Export Control Reform Act of 2018 (Chapter 58 Sections 4801-4852 of Title 50, United States Code). Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25 and DoD Instruction 2040.02.

HANDLING AND DESTRUCTION NOTICE - Comply with distribution statement and destroy by any method that will prevent disclosure of contents or reconstruction of the document.

9. TO Quality. The Contractor must ensure prepared TOs are: a) technically accurate and safe; b) written to a scope and depth of coverage to support the operations and maintenance concepts; c) properly classified and marked with export control and distribution limitation statements. The Contractor must maintain a Technical Manual Quality Assurance (TMQA) Program Plan for this effort. The TMQA Program Plan must be available for review at the TO Guidance Conference. The TMQA Program Plan must be sufficiently detailed to support TO certification to include actual performance of procedures or 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 a hazard to personnel or equipment.

9.1. Initial Technical Order Guidance Conference (TOGC). Working through the TOMA, the Contractor must co-host and participate in a guidance conference for this effort. The TOGC will be held within 60 calendar days after contract award. The Technical Manual Schedule and Status will be formalized at this conference. The Contractor must present a briefing on their interpretation of the basic contract, SOW/Performance Work Statement, CDRLs, Data Item Descriptions (DIDs), MIL- SPEC, MIL-DTL, MIL-STD, SIRs, this document and the planned preparation and delivery of the TOs and related data.

9.2. In-Process Reviews. The Contractor must participate and co-chair In-Process Reviews (IPR) of the data developed for this effort IAW the TOMA-provided IPR checklists. In-Process Reviews are to ensure that data being developed as part of this effort is adequate and accurate and IAW contract requirements and cited specifications. The Contractor must ensure that all appropriate personnel required to execute a successful TO program will either attend or participate in the IPR. IPRs will be held IAW with TO 00-5-3 or as defined by the program office. During the IPRs the Contractor will be responsible to maintain a master markup or documented list of approved changes for the content being reviewed. The Contractor must develop meeting minutes after each review documenting all approved changes and concurrent agreements for Government review and approval. This master markup or documented list of approved changes will be made available at the next scheduled review.

A copy of the markup will be provided to the TOMA or designated individual at the conclusion of the review. The Contractor must ensure all comments from previous IPRs have been incorporated prior to the next scheduled IPR. With prior approval of the TOMA, IPRs may be combined.

9.3. TO Delivery Requirements for In-Process Reviews. IPR TO data must be technically edited and reviewed according to the TMQA Program Plan. Manuscript (handwritten) data is not acceptable for any data to be reviewed. The TMQA Program Plan checklists must be available for review by the Government during the IPRs. Delivery requirements are contained in Section 2 of the TMCR.

9.4. TO Certification. The Contractor must certify that new TO procedures and data developed to support the program are safe, accurate, adequate, current, and usable for their intended purpose. The Government may witness the certification activities. The Contractor must incorporate comments generated by the certification process into the TOs prior to submitting the TOs for verification. At the completion of the certification, the Contractor must submit a letter to the TOMA through the Government PCO and PM stating that certification has been completed, the certification method used, and that any deficiencies identified during the process have been corrected. The Contractor will ensure all necessary changes and corrections to affected manuals are accomplished in time to meet contract delivery schedule requirements. The Contractor must notify the Government, as identified in the contract, at least 180 days prior to the need date, of any Government Furnished Property (GFP), Government Furnished Information (GFI), and/or Government Furnished Equipment (GFE) as required, to perform certification tasks. Technical Order 00-5-1 and 00-5-3 must be referenced for additional information on TO certification requirements.

9.4.1. The Contractor must propose opportunities to perform TO certification activities in conjunction with Government verification IAW TO 00-5-3, where applicable.

9.5. Verification Support. The Contractor must support Government verification activities as required by the TOMA and the program Technical Order Life Cycle Verification Plan (TOLCVP). Contractor verification support will consist of on station technical writing and engineering support. The Contractor must maintain a master mark-up of the TM or list of approved changes and record meeting-minute items during the Government verification process. The Contractor must also support all post verification reviews and ensure availability until 100% task verification is attained by the Government.

9.6. TO Prepublication Reviews (PPR). PPRs are examinations of TOs that ensure incorporation of agreed upon changes from previous reviews and verification activities. The Contractor must prepare and deliver copies of TOs and TO updates in contract compliance (MIL-SPEC or as otherwise identified) for the PPR as shown in the delivery matrix. The TOs for PPR must be approved by the Contractor’s QA, be in compliance with the contract specification/DTLs/STDs, and incorporate all verification comments and corrections approved by the TOMA or program management office representative.

9.7. Technical Data Assessment (TDA). The Contractor must submit in-work samples of each specified TM type deliverable to the Government for specification and standardization compliance review. TDAs may be accomplished by using organic TO sustainment environments with the assistance of AFLCMC/GBS (AF TMSS Office, SGMLSUPPORT@us.af.mil).

9.7.1. MIL-SPEC (SGML) TO Data. The Contractor must submit an SGML tagged TO file, associated graphics files, a PDF rendition of the SGML tagged TO file composed by the Contractor and any associated companion files necessary for PDF composition. During assessment, the SGML tagged TO file will be parsed against the appropriate TMSS DTD (and optionally run through the Tagging Utilization Tool (TUT)) to determine DTD compliance and correct tag usage. The SGML tagged TO file and associated graphics will be composed by the program office and the rendered PDF will be compared with the submitted PDF to check for completeness, indexing, and MIL- SPEC/DTL/STD compliant formatting.

9.7.2. Error Resolution. The Contractor must correct any errors found during the TDA prior to each IPR. Additional TDAs may be necessary based on the amount of errors found during the initial TDA. Completion of a TDA in no way relieves the Contractor from the requirement to fix errors found during future reviews.

10. TO Delivery. TO file delivery requirements are located in Section 2, Table 3 of this document.

10.1. MIL-SPEC (SGML) Tagged Files. The Contractor must parse all SGML files required for the TOs prior to Government delivery and must verify the SGML is compliant with the appropriate DTD.

NOTE: The Government will parse the files prior to acceptance using the SGML parser agreed upon prior to submission. Additional resources can be obtained via AFMC AFLCMC/LZP by submitting a request to AFLCMC.PDSS.TOAPVIPR@us.af.mil.

11. Source Data Maintenance. Contractors must maintain accuracy, currency and configuration of TO source data, to include GFI, throughout the contract period of performance. The Contractor must provide the Government a Configuration Control Management Plan. The Contractor will provide a minimum of annual updates frequently throughout the life of the contract as directed in writing from the PCO.

Maintenance includes preparation of source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes. Additionally, the Contractor must ensure the accuracy, currency, and configuration of applicable data provided by their sub-Contractors as it effects the technical baseline.

NOTE: Contractors will protect GFI provided for the purposes of TO development IAW DFARS 252.204-7000 Disclosure of Information and DFARS 252.227-7025, Limitations on the Use or Disclosure of Government Furnished Information Marked with Restrictive Legends.

12. TO Maintenance. Contractors must maintain TOs by preparing emergency, urgent, routine changes/revisions or supplements and source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes IAW TO 00-5-3. The Contractor must assist the Government, where applicable, by incorporating and delivering approved changes to the technical data in the field NLT the specified time limits within TO 00-5-3 for Urgent, Work Stoppage, or Emergency changes originating from an approved Recommended Change (RC) process and/or Publication Change Request (PCR) in the Enhanced Technical Information Management System (ETIMS). In the event of non-ETIMS access, AFTO FORM 22, 252 policy or other approved change mailto:AFLCMC.PDSS.TOAPVIPR@us.af.mil request forms processes will be adhered to (IAW TO 00-5-1). The specified time limits upon receipt of specified change requests is 40 calendar days for urgent changes/revisions, 72 hours for work stoppage changes/revisions, and 48 hours for emergency changes/revisions.

13. Schedules. The Contractor must develop and maintain an Integrated Technical Manual Schedule and Status throughout the period of performance for all TO development activities associated with this order for the life of the contract. The schedule must be to the system/book or TCTO level and cover all major milestones of development. Any changes to the Integrated Technical Manual Schedule and Status after the TO Guidance Conference must be coordinated with and approved by program TOMA and PCO.

14. Time Compliance Technical Orders (TCTOs). The Contractor must prepare TCTOs, ITCTOs and resulting TO updates as required in support of Mobile Aircraft Arresting Systems IAW TO 00-5-15 and MIL-DTL-38804 content requirements. TCTOs will be used to document all permanent modifications, initiate special “one time” inspections, or impose temporary restrictions on systems or equipment within specified time limits effecting Aircraft Arresting Systems. Costs for TCTO package development must be IAW with AFI 65-601Vol.1.

14.1. The Contractor must deliver Immediate Action TCTO drafts with comments incorporated within 24 hours of receipt of comments.

14.2. The Contractor must deliver Urgent Action TCTO final drafts with “final” customer comments incorporated, within 48 hours of receipt of comments.

14.3. The Contractor must deliver routine safety TCTO final drafts with “final” customer comments incorporated, within 5 working days of receipt of comments.

14.4. The Contractor must deliver routine TCTO final drafts with “final” customer comments incorporated, within 5 working days of receipt of comments.

15. PROGRAM SPECIFIC REQUIREMENTS.

a. The Offeror shall develop and deliver new MIL-SPEC technical manuals IAW Section 2, Table 1, covering the:

1. Illustrated Parts Breakdown (IPB)

2. Depot Overhaul Instructions

b. The manual(s) shall be developed using the latest version of the development specifications listed in Table 1 of this document. Data delivered for this contract shall be digital files. Formal revisions shall be developed for review and TO verification by the government in IAW Section 2 Table 2.

c. SGML files shall be reviewed by the Air Force during the development process to ensure compliance with the approved DTDs. The contractor shall submit copies of their SGML Instance, PDF file of their SGML Instance and separate graphics files use with the SGML Instance for each In-Process review.

d. For Graphics formats, see “Graphics Format Recommendations” attachment 1 to this document, (page 14). These recommendations provide wide latitude for developing and delivering graphics. The Contractor shall select one method from these recommendations to prepare and deliver all graphics files. Graphic resolution shall be a minimum of 300 DPI.

Graphics files shall be delivered as separate files regardless whether they are embedded in the documents or not. Digital photographs (halftones) shall NOT be used. All graphics shall be line artwork.

e. In-Process reviews shall be held at the 35% and 70% completion point for each manual under development. Sample In-Process Completion tables are provided in Attachments 2 & 3.

f. Comments generated during ALL development reviews shall be incorporated before scheduling the next development review, for example 35% IPR comments shall be incorporated before scheduling the 70% IPR. The Contractor shall provide technical and engineering personnel to assist Air Force personnel during the development reviews and verification.

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

TECHNICAL MANUAL TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE Aircraft Arresting Systems Program

Title or Type of Manuals Specification Required

1. Time Compliance Technical Orders (TCTOs) MIL-DTL-38804

a. TCTO ☒

b. TCTO Supplement ☒

2. Illustrated Parts Breakdown MIL-DTL-38807 ☒

3. Operation and Maintenance Instructions in Chapter style MIL-DTL-38784

a. Maintenance Manuals

(1) Organizational Maintenance

(2) Intermediate Maintenance

(3) Depot Maintenance X

(4) Combined (I&D) Maintenance

(5) 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)

TABLE 2

SUSTAINMENT/MODIFICATION UPDATES TM TYPE SELECTIONS

NOTES:

• Check all applicable boxes.

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

TO Number, Title, or Type of Manual Specification Change Revision

Supple-ment

Supple-mental

TM

Source Data

1. 35E8-2-5-3

2. 35E8-2-5-4

3. 35E8-2-10-3

4. 35E8-2-10-4

TABLE 3 – SGML/XML TM DELIVERY REQUIREMENTS

FOR AIRCRAFT ARRESTING SYSTEMS

NOTES:

• For Paper and CD/DVD media delivery indicate required quantity

• For all other media types indicate (Y)es or (N)o

• TCTO/SB requirements are specified in the contract vehicle approving the TCTO/SB.

• All SGML/XML file delivers MUST include ALL graphic files.

• All TO files must not be password protected.

DELIVERY SCHEDULE

Event Number of business days data required prior to event In Process Review(s) (30 Days)

Verification

(30 Days)

Prepublication Review

(30 Days)

Final TO Delivery (45 Days)

Enter physical mailing address, electronic delivery location or web access point

406 SCMS/GUEE

Attn: Debra Johnson 235 Byron Street, Ste. 19A, Robins AFB, GA 31098-1670

Paper/ 0

SGML/ Y

(I)PDF / Y

XML / N

CD-DVD/ 0

Paper/ 0

SGML/ Y

(I)PDF / Y

XML / N

CD-DVD/ 0

Paper/ 0

SGML/ Y

(I)PDF / Y

XML / N

CD-DVD / 0

Paper/ 0

SGML/ Y

(I)PDF / Y

XML / N

CD-DVD / 0

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

NOTES:

• All TMSS applicable to this contract must 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-DTL-22202D is not required, the entire SIR can be deleted.

• Utilize the TMSS Tailoring Tool located at https://techdata.wpafb.af.mil/tmss/index.html by selecting all applicable TMSS requirements, and the desired tailoring options expressed in paragraphs 6.2. Attach the TMSS Tailoring Tool spreadsheet output in the specified section listed below.

• Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available from Acquisition Streamlining and Standardization Information System (ASSIST) web page, https://assist.dla.mil/online/start/index.cfm.

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

• Comments (recommendations, additions, deletions) and any pertinent data which may be in use in improving Air Force

TMSS documents should be submitted to AFLCMC/GBS 4170 Hebble Creek Road, Bldg. 280, Door 15, Area A, Wright-Patterson AFB, Oh 45433-5653 or by email to; SGMLsupport@us.af.mil. Do not include the street address, a building number or a zip+4.

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-STD-38784B 16 November 2020

a. Title, number, and date of this standard.

b. If volume number will be included with the page number (see 4.7.4.1.2).

c. (A) (M) (N) If foldout pages may be prepared (see 4.7.6.1).

d. (M) (N) If foldout pages will be interspersed within text pages or fall at the end of the chapter instead of at the end of the manual (see 4.7.6.1F).

e. If a maximum of four, five, or six levels of subordinate paragraph will be used (see

4.7.11.5.1.2).

f. (F) (N) If use of contract number will be other than as specified in this document (see 4.9.1.3).

g. If volume notice is required (see 4.9.1.7).

h. If an LOC will be prepared in addition to an LEP (see 4.9.4).

i. If contractor format and/or additional columns may be used on verification status page(s) (see

4.9.5).

j. (F) (M) (N) If submittal and routing instructions for TM improvement reports is required (see

4.9.10).

k. If photographs may be used (see 4.11.2).

l. If color photographs may be used (see 4.11.2).

m. If color photographs may be used in illustrations (see 4.11.9).

n. If a nomenclature cross reference is required (see 4.11.13.2).

o. If the change date will be other than as specified in this document (see 4.12.2).

p. If a change symbols will be other than as specified in this document (see 4.12.9).

q. If changed text highlighting will be used instead of vertical change bars (see 4.12.9).

r. (F) (N) Whether 8½ by 11 inch and larger manuals will be single or double column (see 5.3.1a).

s. If a supplement distribution statement will be other than as specified in this document (see

5.4.2.5).

Department of Defense Standard Practice for Manuals, Technical:

General Style and Format Requirements https://techdata.wpafb.af.mil/tmss/index.html https://assist.dla.mil/online/start/index.cfm mailto:SGMLsupport@us.af.mil

TIME COMPLIANCE TECHNICAL ORDERS (TCTO) – MIL-DTL-38804F 03-JUNE-2021

and TCTO Supplements.

a. Title, number, and date of this specification.

ILLUSTRATED PARTS BREAKDOWN – MIL-DTL-38807D 27-MARCH-2020

a. Title, number, and date of this document.

b. If TMs are to be prepared in single or subdivided format, or as a chapter of a maintenance/operation or overhaul manual (see 1.1).

c. If serialization tables are to be provided whenever two or more configurations of the equipment covered by the IPB exist and not all subcomponents are interchangeable between configurations (see 3.5.2).

d. If all HCIs are to be marked with the HCI symbol, and if **HCI** may be used in lieu of the HCI symbol (see 3.5.10).

e. If changes or substitutions of HCI are required (see 3.5.10.1).

f. If all ESDS parts are to be marked with the ESDS symbol, and if **ESDS** may be used in lieu of the ESDS symbol (see 3.5.11).

g. If a manufacturers list is to be provided (see 3.5.13).

h. If reference designations are to follow, or be placed immediately below the applicable index number on the illustrations (see 3.6.6.9).

i. If MPL pages are to show group or system titles beneath the publication number (see 3.6.7).

j. If multiple SMR columns will be displayed (see 3.6.7.7.1).

k. If s separate power package buildup manual is being procured (see 3.6.10.3).

l. If spacing between listing is to be other than that specified in this specification (see 3.7.2).

m. If SSSN is to be used in chapter 4 and, if used, whether it is to be in conjunction with or in lieu of the reference designator (see 3.8).

ATTACHMENT 1

Graphics Format Guidelines

GUIDELINES:

Encapsulated Post Script (EPS):

• Raster based images will not be saved as EPS but will be saved as TIFF images.

• EPS files must not be a mix of vector and raster images. Vector based images must be saved as

EPS.

• Vector based images saved as EPS will include illustrations containing both vector and raster images.

• Any source data (photos used for tracing etc.); used in aiding of creation of EPS (templates, etc.)

will be deleted from illustration prior to saving/exporting.

• If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues.

Tagged Image File Format (TIFF):

• Black and white raster images should only be saved as Bitmap and not Grayscale, RGB or

CMYK.

• Grayscale or Color images (screenshots, etc.) will be saved as such (Grayscale, RGB or CMYK) and will not be bitmap converted using a halftone screen.

• To further aid in file size reduction for storage purposes, images should be compressed using

Group 4 compression when saving/exporting.

Computer Graphics Metafile (CGM):

• Raster based images will not be saved as CGM.

• Any source data used in aiding of creation of CGM (templates, etc.) will be deleted from illustration prior to saving/exporting.

• CGM files must not be a mix of vector and raster images. Vector only.

• If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues.

• Unless Version 4 is specifically required for hotspots and/or hyper linking, CGMs should be exported as version 3 to increase cross platform compatibility.

DWG File Format:

• Raster based images will not be saved as DWG.

• DWG files must not be a mix of vector and raster images. Vector only.

• Any source data used in aiding of creation of DWG (templates, etc.) will be deleted from illustration prior to saving/exporting.

• If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues.

Joint Photographic Expert Group (JPEG):

(Caution: JPEG 2000 files are not to be used at all due to platform display issues.)

• JPEG File format should be used as last resort. Color screenshots/photos should be saved as

TIFFs due to possible system compatibility issues.

• B&W Bitmaps should not be saved as JPEGs.

Portable Network Graphics (PNG): (Do not use to create graphics for sgml TOs)

• Used for raster graphics

• Supports lossless data compression

Bitmap (BMP):

• Used for raster graphics

Scalable Vector Graphics (SVG):

• Two-dimensional vector and mixed vector/raster graphics

ATTACHMENT 3

AFTO FORM 158

TECHNICAL ORDER REVIEW COMMENT SHEET

TO NUMBER: TITLE: RECEIVED DATE:

TOTAL PAGES:

Name of Reviewer: DATE OF REVIEW:

COMPLETE DATE:

Section Para/Fig/Page Comments:

AFTO FORM 158