A101_DID_Open_Skies_Digital_Visual_Imaging_System_(DVIS)_TM-86-01P_Rev.1.pdf

TM-86-01P 9 Dec 2014 1

Air Force Technical Manual Contract Requirements (TMCR) for

Open Skies Digital Visual Imaging Systems (Program/Modification/Military System)

ATTACHMENT 1 , TO CDRL SEQUENCE NUMBER A101 , EXHIBIT CET# CMP3-OC-0018

REQUEST FOR PROPOSAL/CONTRACT:

Date: 2 Feb 2015

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 by the program office, including the associated ta-bles, matrices and Specification/Standard Interface Records (SIRs). The Contractor may propose and submit, in writing additional tailoring to the TO Manager Agency/Agent (TOMA) and Procuring Con-tracting Officer (PCO) for consideration. The tailored TMCR shall be attached to the CDRL for TO de-livery, and shall be included in the proposal as a separate exhibit, referenced in the proposal SOW. Pro-posals shall be compatible with the (OC-135) Open Skies Digital Visual Imaging Systems requirements located (CET CMP3-OC-0018). Technical Order Concept of Operations. Air Force TO Acquisition procedures, including procedures for tailoring this document, are found in TO 00-5-3, AF Technical Or-der Life Cycle Management, located on the Internet at http://www.tinker.af.mil/technicalorders/index.asp. A copy may also be obtained from the Program TO Manager. Any terms or procedures found in this document may be researched there.

2. TO Program Scope. The Contractor may recommend additional Section 2 tailoring to propose new TO types (Table 1) and source data and TO updates (Table 2) required to support the Open Skies Digital Visual Imaging Systems program’s objectives.

3. Commercial Manuals. No commercial manuals will be used under this TMCR.

4. Technical Manual Specifications and Standards (TMSS) Tailoring. TMSS are tailored by selecting between tailoring options offered in 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 mandatory requirements which are part of the Document Type Definition (DTD) structure or XML schema struc-ture located in Section 2 Table 1.

4.1. Deleted. Not applicable to this contract.

4.2. Questions concerning TMSS requirements may be resolved by written request and justified sug-gestions for resolution submitted through the Procuring Contracting Officer (PCO) and (Rich McCormick, AFLCMC/WKDMA, Bldg. 3001 post 2AE1 88G, 405-736-1865). 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. When new TO requirements are identified the Contractor shall notify the government utilizing DI-TMSS-80067B, Technical Manual (TM) Contractor Furnished Aer-onautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices, or approved contractor formats. This process shall require government review and approval of recommended additional re-quirements prior to developing additional data.

http://www.tinker.af.mil/technicalorders/index.asp

2 TM-86-01P 9 Dec 14

6. TO Development. TOs shall be written to a scope and depth of coverage sufficient to support the Open Skies Digital Visual Imaging Systems operations and maintenance concepts.

6.1. Deleted. Not applicable to this contract.

6.2. SGML-tagged TO files shall include required illustration (graphics) files in an approved graphics exchange format. Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible. All delivered graphics shall conform to the approved graphic creation and format guidelines listed in attachment 1. Graphics shall be provided as CGM Vector as stated in attachment 1. For assistance with illustration require-ments contact AFLCMC/HIAM via (e-mail: SGMLSupport@us.af.mil).

6.3. Page-oriented Military Specification (MILSPEC) TOs shall be formatted with text, graphics and delivered 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 specification (MIL-DTL). Multiple SGML file instances for a single T.O. document are not authorized.

7. TO Numbering. Contractors 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. Re-quests for new TO numbers shall be submitted to the TOMA utilizing the TO numbering worksheet.

(Attachment 2)

8. Data Rights. Contractors shall provide Unlimited Rights for all source data and TOs prepared specif-ically for the contract. Government rights in data are specified in the Defense Federal Acquisition Regu-lation Supplement (DFARS), 252.227-7013, Rights in Technical Data, Noncommercial Items, 252.227- 7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documen-tation, and 252.227-7015, Technical Data-Commercial Items. The government shall be given unlimited rights for all business 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 tech-nical data.

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. Contractors shall determine the correct markings and controls for classified and restricted distribution data and TOs IAW the program’s Security Classification Guide (SCG) and DODM 5200.01, DODI 5230.24, AFI 31-401, AFI 61-204, and MIL-STD-38784 (available at http://www.e-publishing.af.mil/ or https://assist.dla.mil/online/start/index.cfm ). 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. Contractors’ proposals shall describe how the government will be allowed to interact with the contractor’s TO development team. The contractors’ shall ensure TOs prepared are: a) techni-cally accurate and safe; b) written to a scope and depth of coverage sufficient to support the operations and maintenance concepts, and c) properly classified and marked with export control and distribution limitation statements. The contractor shall maintain a Technical Manual Quality Assurance Program (TMQAP) plan for this effort. The TMQAP shall be available for review at the TO Guidance Confer-ence. The TMQAP shall be sufficiently detailed to support TO certification to include actual perfor-mance of procedures or desk-top analysis for non-procedural data.

10.1. Guidance Conference. Working through the TOMA, the contractor shall co-host and partici-pate in a guidance conference for this effort to be held within 60 calendar days after award of con-tract. The Technical Order Status and Schedule (TOSS) will be formalized at this conference. The contractor shall present a briefing on their interpretation of the basic contract, SOW, CDRLs, Data mailto:SGMLSupport@us.af.mil http://www.e-publishing.af.mil/ https://assist.dla.mil/online/start/index.cfm

TM-86-01P 9 Dec 2014 3

Item Descriptions (DIDs), MIL-SPEC, MIL-STD, SIRs, this document and the planned preparation and delivery of the TOs and related data.

10.2. In-Process Reviews. The contractor shall participate and co-chair In-Process Reviews of the data developed for this effort. In-Process Reviews may be requested by the TOMA or by the con-tractor to ensure that data being developed as part of this effort is adequate and accurate and IAW contract requirements and cited specifications. The contractor shall support IPRs with the technical writers, engineers and QA personnel as required or needed. IPRs will be held in accordance 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 of the document being reviewed. This master markup will be made avail-able at the next scheduled review. A copy of the markup will be provided to the TOMA or designat-ed individual at the conclusion of the review. The contractor shall ensure all comments from previ-ous IPR’s have been incorporated prior to next scheduled IPR. With the prior approval of the TOMA the IPRs may be combined.

10.3. TO Delivery Requirements for In-Process Reviews. IPR TO data shall be technically edited and reviewed according to the TMQAP. Manuscript (handwritten) data is not acceptable for any da-ta to be reviewed. The TMQAP checklists shall be available for review by the government during the IPRs. For IETM based programs, IPRs subsequent to the initial review may be accomplished us-ing the approved viewing presentation system.

10.4. TO Certification. The contractor shall certify that new TO procedures and data developed to support the program are accurate, adequate, current, and usable for their intended purpose. The Gov-ernment may witness the certification activities. The contractor shall incorporate comments generat-ed by the certification process into the TOs prior to submitting the TOs for verification. At the com-pletion of the certification, the contractor shall submit a letter to the TOMA stating that certification has been completed 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 shall notify the government at least 180 days prior to the need date of any Government Furnished Information/Government Fur-nished Equipment (GFI/GFE) required to perform certification tasks. Technical order 00-5-1 and 00- 5-3 shall be referenced for additional information on TO Certification requirements.

10.5. Verification Support. The contractor shall support USAF verification activities as required by the TOMA and the program Verification Plan. Contractor verification support will consist of on sta-tion technical writing or engineering support and maintain a master mark-up of the document and record minute items during the Air Force verification process. The contractor shall also support all post verification reviews.

10.5.1. Deleted. Not applicable to this contract.

10.6. TO Prepublication Reviews (PPR). PPRs are examinations of TOs to ensure incorporation of agreed upon changes from IPRs and verification, and to ensure the manual meets style and format requirements. The Contractor shall prepare and deliver copies of TOs and TO updates in MIL-SPEC compliance for the PPR as shown in the delivery matrix. The TOs for PPR shall have been approved by contractor QA, be in compliance with the MIL-SPECs/standards, and incorporate all verification comments and corrections approved by the TOMA or program management office representative.

The TOMA may waive the PPR depending on number and complexity of changes from verification.

10.7. Technical Data Assessment (TDA). TDA’s may be accomplished using organic TO sustainment environments (ATOS, IDM, etc.) or with the assistance of AFLCMC/HIAM. The TO Manager, will determine the TDA requirements for each TO type.

10.7.1. SGML TO Data. The contractor shall 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

4 TM-86-01P 9 Dec 14 companion files necessary for PDF composition. During assessment, the SGML tagged TO file will 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 com-pared with the submitted PDF to check for completeness, indexing, and MIL-SPEC/STD compli-ant formatting.

10.7.2. Deleted. Not applicable to this contract.

10.7.3. Error Resolution. Errors found during the TDA shall be addressed and completed prior to each IPR. Additional TDAs may be necessary based on the amount of errors found during the ini-tial TDA. Successful TDAs in no way relieves the contractor from fixing errors found during fu-ture reviews.

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

11.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 in compliance with the appropriate DTD. NOTE: The government will parse the files prior to ac-ceptance using the public domain “SGMLS Parser” (http://jclark.com/sp/).

11.2. SGML Tagged Files for Use with the eTO Viewer. The contractor shall use the GFE ETIMS eTO Viewer/Transformer to convert tagged instances to Hypertext Markup Language (HTML) files compatible with the eTO viewer, and certify the output complies with TMSS requirements. Working through the TOMA the contractor may obtain copies of the ETOV software from the AF Center for Electronic Distribution of Systems (AFCEDS) at https://ceds.gunter.af.mil/AISHome.aspx?AIS=24.

11.3. Deleted. Not applicable to this contract.

12. Source Data Maintenance. Contractors shall maintain accuracy, currency and configuration of TO source data, to include GFI, throughout the contract period of performance. Maintenance includes prep-aration of source data updates to incorporate corrections, equipment configuration changes, and mainte-nance and operational concept changes.

13. TO Maintenance. Contractors shall maintain TO’s by preparing emergency, urgent, routine chang-es/revisions or supplements and source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes IAW TO 00-5-3.

14. Schedules. The contractor shall develop and maintain an Integrated Technical Order Status and Schedules (TOSS) throughout the period of performance for all TO development activities associated with this order for the life of the contract. The schedule shall be to the system/book or TCTO level and cover all development major milestones. Any changes to the TOSS after the guidance conference shall be coordinated with and approved by program TOMA. NOTE: DI-TMSS-81812, Technical Manual Schedule and Status Report, may be used as a guide to prepare the TOSS.

15. Time Compliance Technical Orders (TCTOs). The contractor shall prepare TCTO’s and resulting TO updates as required in support of Open Skies Digital Visual Imaging Systems. TCTO’s 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 Open Skies Digital Visual Imaging Systems. Costs for TCTO package development must be in accordance with AFI 65-601Vol.1.

15.1 Deleted. Not applicable to this contract.

15.2 Deleted. Not applicable to this contract.

https://ceds.gunter.af.mil/AISHome.aspx?AIS=24

TM-86-01P 9 Dec 2014 5

15.3 Deleted. Not applicable to this contract.

15.4 The contractor shall deliver certified drafts of routine TCTO’s to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The contractor shall deliver final drafts with “final” customer comments incorporated, within 10 business days of receipt of com-ments.

6 TM-86-01P 9 Dec 14

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

• Mark the TM Type Selection Tables indicating the applicable TO types and related specifications.

PART A – (NEW DEVELOPMENT) TM TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE (Open Skies Digital Visual Imaging Systems) Program

(System/Component)

Title or Type of Manuals Specification Required

1. Inspection TOs MIL-DTL-5096

a. Inspection and Maintenance Requirements (-6) Manual

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

Manual

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

d. Inspection Workcards (-6WC)

e. Maintenance/Operations Checklists

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

a. Loading Instructions Manual

b. Nuclear Weapon Cargo Loading Manual

c. Checklists

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

a. Loading Data Manual

b. Sample Basic Weight Checklists

4. Flight Manuals MIL-DTL-7700

a. Flight Manual

b. Performance Data Manual

c. Mission Crew Manual

d. Supplemental Manual

e. Abbreviated Flight Crew Checklist

5. List of Applicable Publications MIL-DTL-8031

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

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

a. Nuclear Weapons Basic Information and Loading Procedures

b. Nuclear Weapons Loading Procedures

c. Non-nuclear Munitions Basic Information

d. Non-nuclear Loading Procedures

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

f. Loading Procedures Checklist

g. Single Loading Procedures Checklist

h. Integrated Loading Procedures Checklists

i. Family Group Loading Procedures Checklist

j. Nuclear Weapons Loading Procedure Checklists

k. Functional Check Procedures Checklist

l. NATO Stage B Cross-Servicing Checklists

m. End of Runway (EOR) Procedures Checklist

8. Space Operations and Support Documentation TOs -- MILSPEC (Intercontinental Ballistic Missiles) -- MILSPEC (Space)

MIL-PRF-38311

MIL-PRF-38314

a. Operations Manual

TM-86-01P 9 Dec 2014 7

TMSS REQUIREMENTS FOR THE (Open Skies Digital Visual Imaging Systems) Program

(System/Component)

Title or Type of Manuals Specification Required

b. Operations Checklists

c. Technical Manuals and Related Checklists

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

Manuals and Checklists

MIL-DTL-38384

a. Non-nuclear Weapon Delivery Manual

b. Aircrew Nuclear Bomb Delivery Manual (Strategic Bomber Aircraft)

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

d. Aircrew Nuclear Bomb Delivery Manual (Tactical Aircraft)

e. Non-nuclear Weapon Delivery Checklist

f. Nuclear Weapon Delivery Checklist (Strategic Bomber Aircraft)

g. Aircrew Nuclear Bomb Delivery Checklist (Tactical Aircraft)

h. Non-nuclear Weapon Delivery Source Data Packages

10. Work Unit Code Manual

a. Standard WUC Manual

b. Two Chapter Manual

c. Three Chapter Manual

MIL-DTL-38769

11. Calibration Procedures MIL-DTL-38793

12. Time Compliance Technical Orders (TCTOs)

a. TCTO

b. TCTO Supplement

MIL-DTL-38804

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

14. Illustrated Parts Breakdown MIL-DTL-38807

15. On-Equipment Organizational Maintenance Manual Set MIL-DTL-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

8 TM-86-01P 9 Dec 14

TMSS REQUIREMENTS FOR THE (Open Skies Digital Visual Imaging Systems) Program

(System/Component)

Title or Type of Manuals Specification Required

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)

(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-DTL-5096)

e. With Illustrated Parts Breakdown

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

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

19. Technical Publications Utilizing Common Source Database (CSDB)

a. Style Sheets

b. Business Rules Exchange (BREX)

c. Data Module Requirements List (DMRL)

d. Authoring Guides

e. Style Guides

f. Graphics and Textual Contractor Developed Business Rules Document

g. Viewing Guidelines

h. Process Documentation

ASD-S1000D -

International Specification for Technical Publications Utilizing a CSDB

MIL-STD-3048

TM-86-01P 9 Dec 2014 9

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. Operational Supplements (Flight Manual)

AFI 11-215 (see attached)

2. Operational Supplements (FM Checklists)

AFI 11-215 (see attached)

3.

4.

5.

6.

7.

8.

9.

10.

11.

12.

13.

14.

15.

16.

17.

18.

19.

20.

10 TM-86-01P 9 Dec 14

TABLE 3 - TM DELIVERY REQUIREMENTS

FOR OPEN SKIES DIGITAL VISUAL IMAGING SYSTEMS

(System/Item)

NOTES:

• For Paper media delivery indicate required quantity

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

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

If “Other” is selected, define media type and quantities: ________________

DELIVERY SCHEDULE

Event Number of days data required prior to event

In Process Review(s) (15 Days)

Verification

(15 Days)

Prepublication Review

(15 Days)

Final TO Distribution

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

AFLCMC/WKDMA,

Attn: Richard McCormick 3001 Staff Dr. Ste 2AE1 87E, Tinker AFB, OK 73145-3019

Paper/ Y

SGML/ N

IPDF / N

XML / N

Other/

Paper/ Y

SGML/ N

IPDF / N

XML / N

Other/

Paper/ Y

SGML/ Y

IPDF / N

XML / N

Other/

Paper/ Y

SGML/ Y

IPDF / N

XML / N

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Total Paper Copies Required: 2 4 2 1

TM-86-01P 9 Dec 2014 11

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-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. For this contract enter:

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

• 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-16) AFLCMC/HIAM.

• 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/HIAM, 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-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

DODM 5200.1 DOD Information Security Program 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.”

https://assist.dla.mil/online/start/index.cfm mailto:SGMLsupport@us.af.mil

12 TM-86-01P 9 Dec 14

5. Replace with: “5. PACKAGING.”

“5.1 Packaging Requirements. For acquisition purposes, the packaging requirements shall be as speci-fied 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-1840C, Automated Interchange of Technical Infor-mation.”

“5.1.2 Classified Material. Classified material shall be packaged and identified in accordance with DODM 5200.1, 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-3048 24 July 2013

Chg 1, 10 Sep 2013

Air Force Business Rules for the Implementation of S1000D

TM-86-01P 9 Dec 2014 13

ATTACHMENT 1

Graphics Format Recommendations

GENERAL GUIDELINES

• Single column graphics should not exceed 51 Picas High by 18 Picas Wide. (Paper only)

• Full page graphics should not exceed 51 Picas High by 42 picas Wide. (Paper only)

• Fold Out graphics should not exceed 51 Picas High (width on foldouts is not important). (Paper only)

EPS:

• Raster based images will not be saved as EPS.

• EPS files shall not be a mix of vector and raster images. Vector only.

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

TIFF:

• B&W 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.

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 illustra-tion prior to saving/exporting.

• CGM files shall 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 ex-ported as version 3 to increase cross platform compatibility.

DWG:

• Raster based images will not be saved as DWG.

• DWG files shall 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 illustra-tion 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.

JPEG:

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

TIFFs due possible system compatibility issues.

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

14 TM-86-01P 9 Dec 14

ATTACHMENT 2

REQUEST FOR TECHNICAL ORDER NUMBER

1. *PRIME SYSTEM APPLICATION (If Applicable or N/A)_______________________________

2. *CONTRACT NUMBER/ PURCHASE REQUEST (PR) NUMBER: _____________________

3. *MISSION DESIGN SERIES/NOMENCLATURE (Name Of Equipment) __________________

4. *FEDERAL STOCK CLASS:_______________________________________________________

5. *PART NUMBER(s):______________________________________________________________

6. *NSN/FSN: (or temp NSN) __________________________________________________________

7. *PUBLICATION TYPE (Opn & Maint with IPB, Overhaul, WUC, IPB, LOAP, etc.)

8. *SUGGESTED TECHNICAL ORDER NUMBER:_____________________________________

9. *RECOMMENDED TITLE OF MANUAL (Leave Blank if Classified) ____________________

10. *CLASSIFICATION OF MANUAL: ________________________________________________

11. *CLASSIFICATION OF TITLE: ___________________________________________________

12. *KIND OF EQUIPMENT (Airborne / Ground / Not Applicable):___________________________

13. *TEST EQUIPMENT? Yes / No

14. PROGRAM ELEMENT CODE (PEC): ________________________________________________

15. LEAD COMMAND: _______________________________________________________________

16. DOES MANUAL EXIST FOR SAME/SIMILAR EQUIPMENT? Yes / No

17. EXISTING MANUAL TO NUMBER: _________________________________________________

18. COMMERCIAL OFF THE SHELF (COTS) ITEM: Yes / No

19. CONTRACTOR INFORMATION: (If Applicable)

a. NAME OF VENDOR: _____________________________________________________

b. ADDRESS: _____________________________________________________________

c. MANUFACTURER'S CODE: ______________________________________________

d. POINT OF CONTACT: ____________________________________________________

20. FOREIGN MILITARY SALES (FMS) YES ___ NO ____ (If YES, complete item 20)

20. COUNTRY CODES (For CSTO/FMS manuals): (See TO 00-5-19) __________________________

21. COMMENTS:______________________________________________________________________

* = Mandatory Fields

Section 1. Technical Order (TO) Program Requirements