TM-86-01R.pdf

PDF 410 KB Posted

Attached to
T4000 and T4100 Engine Trailers Winch Modification Kit Federal contract opportunity
Solicitation number
FA8533-20-R-0020
Issued by
Department of the Air Force Materiel Command Lifecycle Management Center Robins Air Force Base

View the file

Other files for this federal contract opportunity

Other files attached to T4000 and T4100 Engine Trailers Winch Modification Kit, newest first.
File Type Posted
FA8533-20-R-0020-0004.pdf PDF
A017 - Technical Manual Contract Requirements (TMCR).pdf PDF
FA8533-20-R0020 0003.pdf PDF
CDRL - Technical Manual Contract Requirements (TMCR).pdf PDF
B004 - Technical Review Data Package - Revised.pdf PDF
A016 - Logistics Product Data.pdf PDF
A011 - Conference Agenda - Revised.pdf PDF
A005 - First Article Test Procedure - Revised.pdf PDF
A008 - Notice of Revision - Revised.pdf PDF
A015 - Engineering Data for Provisioning (EDFP).pdf PDF
A013 - Corrosion Prevention and Control Plan - Revised.pdf PDF
FA8533-20-R-0020-0002.pdf PDF
A004 - Technical Review Data Package - Revised.pdf PDF
A006 - Engineering Change Proposal - Revised.pdf PDF
A012 - Conference Minutes - Revised.pdf PDF
A014 - Product Base Line Index - Revised.pdf PDF
A009 - First Article Test Report - Revised.pdf PDF
A001 - System Safety Hazard Analysis Report - Revised.pdf PDF
SOW - Revised.pdf PDF
A002 - Monthly Status Report - Revised.pdf PDF
A003 - First Article Test Plan - Revised 2.pdf PDF
A007 - Request for Variance - Revised.pdf PDF
Engine Trailer Winch Modification Kit Technical Requirements - Revised.pdf PDF
A003 - First Article Test Plan - Revised.pdf PDF
FA8533-20-R-0020-0001.pdf PDF
FA8533-20-R-0020.pdf PDF
SOW.pdf PDF
A002 - Monthly Status Report.pdf PDF
A006 - Engineering Change Proposal.pdf PDF
A003 - First Article Test Plan.pdf PDF
A013 - Corrosion Prevention and Control Plan.pdf PDF
A009 - First Article Test Report.pdf PDF
A004 - Technical Review Data Package.pdf PDF
A005 - First Article Test Procedure.pdf PDF
A011 - Conference Agenda.pdf PDF
Engine Trailer Winch Modification Kit Technical Requirements.pdf PDF
A007 - Request for Variance.pdf PDF
A001 - System Safety Hazard Analysis Report.pdf PDF
Packaging Requirements-AFMC158.pdf PDF
A012 - Conference Minutes.pdf PDF
A008 - Notice of Revision.pdf PDF
A014 - Product Base Line Index.pdf PDF
B004 - Technical Review Data Package.pdf PDF
FA8533-20-R-0020.pdf PDF
A010 - Technical Drawing Package.pdf PDF
Show all 45

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

TM-86-01R 01 June 2020 1-01: AF TMSS LinearTMs

GUEE-20-015

Air Force Technical Manual Contract Requirements (TMCR) for

T4000 and T4100 Engine Trailers Winch Modification Kit

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT: , CLIN

Date: 13 August 2020

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

1. TMCR Tailoring. Air Force (AF) TO Acquisition procedures, including procedures for tailoring this document are found in TO 00-5-3, AF Technical Order Life Cycle Management, located at http://www.tinker.af.mil/Home/TechnicalOrders.aspx. Any terms or procedures found in this document may be researched at this website. 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. 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 shall develop and deliver technical manuals in accordance with (IAW) this TMCR that support the T4000 and T4100 Engine Trailers Winch Modification Kit requirements for technically usable manuals concurrent with the program’s TO CONOPS. The Contractor may propose and submit, in writing to the PCO, additional Section 2 tailoring to propose new TO types (Table 1) and source data and TO updates (Table 2) required to support the T4000 and T4100 Engine Trailers Winch Modification Kit program’s objectives and as defined by the TMSS. The acceptance of any additionally tailored TMCR will be at the discretion of the government and is not in effect until accepted in writing by the PCO.

3. Commercial Manuals. N/A

3.1. N/A

http://www.tinker.af.mil/Home/TechnicalOrders.aspx

3.2. N/A.

3.3. N/A

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

4.1. Questions concerning TMSS requirements may be submitted in writing with suggestions for resolution and supporting information to the PCO and to the TOMA: Becki Middlebrooks, 406SCMS/GUEE, 235 Byron St, Suite 19A, Robins AFB, GA. 31098; 478-926-2169. 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.

5. Subsequent TO/Data Requirements. When new TO requirements are identified the Contractor shall 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 shall require Government review and approval of recommended additional requirements prior to developing additional data.

6. TO Development. TOs shall be written to a scope and depth of coverage to support the T4000 and T4100 Engine Trailers Winch Modification Kit operations and maintenance concepts.

6.1. Standard Generalized Markup Language (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 Format Guidelines. For assistance with illustration requirements contact AF TMSS via (e-mail: SGMLSupport@us.af.mil).

6.2. Page-oriented Military Specification (MIL-SPEC) 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 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.

7. TO Numbering. N/A

8. Data Rights. Contractors shall 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 and 252.227. 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 TO development. Contractor shall identify any data to be delivered to the Government with other than mailto:SGMLSupport@us.af.mil

Unlimited Rights IAW DFARS 252.227-7017, Identification and Assertion of Use, Release, or Disclosure Restrictions and shall mark such data only in accordance with the applicable DFARS clause. The Contractor shall pass through and enforce all requirements in this TMCR to all sub-Contractors.

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

Contractors shall recommend the correct markings and controls for classified and restricted distribution data and TOs IAW the program’s Security Classification Guide (SCG) and Department of Defense Manual (DODM) 5200.01, Department of Defense Instruction (DODI) 5230.24, Department of Defense Directive (DODD) 5230.25, Air Force Instruction (AFI) 16-1404, 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). The Contractor shall 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 (Administrative or Operational Use) (TBD). 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/WN-SEV.

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401, et seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

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

10. TO Quality The Contractors shall 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 shall maintain a Technical Manual Quality Assurance (TMQA) Program Plan for this effort. The TMQA Program Plan shall be available for review at the TO Guidance Conference. The TMQA Program Plan shall 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. NOTE:

Quality requirements for the Joint Nuclear Weapons Publications System (JNWPS) and for Non- nuclear Explosive Ordnance Disposal (EOD) Data are contained in TO 11N-1-1 Joint Nuclear Weapons Publication System Operating Procedures, Specifications and Standards, and DODD 5160.62, Single Manager Responsibility for Military Explosive Ordnance Disposal Technology and Training, respectively. The Government will conduct performance-tests on all JNWPS and EOD TOs.

10.1. Initial Technical Order Guidance Conference (TOGC). Working through the TOMA, the Contractor shall 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 shall present a briefing on their interpretation of the basic contract, SOW/Performance Work Statement (PWS), CDRLs, DIDs, MIL-SPEC, MIL-DTL, 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 (IPR) of the data developed for this effort. 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 shall ensure that all appropriate personnel required to execute a successful TO program http://www.e-publishing.af.mil/ http://www.e-publishing.af.mil/ https://assist.dla.mil/online/start/index.cfm will either attend or participate in the IPR. IPRs will be held IAW 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. The Contractor shall develop meeting minutes after each review documenting all approved changes and concurrent agreements for Government review and approval.

This master markup 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 shall 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.

10.3. TO Delivery Requirements for In-Process Reviews. IPR TO data shall 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 shall be available for review by the Government during the IPRs. Delivery requirements are contained in Section 2, Table 3 of the TMCR.

10.4. TO Certification. The Contractor shall certify that new TO procedures and data developed to support the program are accurate, adequate, current, safe, and usable for their intended purpose. The Government may witness the certification activities. The Contractor shall 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 shall 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 shall notify the Government, as identified in the contract, at least 180 days prior to the need date, of any Government Furnished Property (GFP), Information, and/or Government Furnished Equipment (GFI/GFE) as required, to perform certification tasks. TO 00-5-1 and TO 00-5-3 shall be referenced for additional information on TO Certification requirements.

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

10.5. Verification Support. The Contractor shall 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 shall maintain a master mark-up of the document and record minute items during the Government verification process. The Contractor shall also support all post verification reviews and ensure availability until 100% task verification is attained by the Government.

10.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 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 be approved by the Contractor’s QA, be in compliance with the MIL-SPECs/DTLs/STDs, and incorporate all verification comments and corrections approved by the TOMA or program management office representative.

10.7. Technical Data Assessment (TDA). The Contractor shall 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 (ATOS, IDM, etc) or with the assistance of AFLCMC/HIAM (AF TMSS Office, SGMLSUPPORT@us.af.mil).

10.7.1. MIL-SPEC (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 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.

10.7.2. Error Resolution. The Contractor shall 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.

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

11.1. MIL-SPEC (SGML) Tagged Files. The Contractor shall parse all SGML files required for the TOs prior to Government delivery and shall 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.

12. Source Data Maintenance. Contractors shall maintain accuracy, currency and configuration of TO source data, to include GFI, throughout the contract period of performance. The Contractor shall provide the Government a Configuration Control Management Plan. The Contractor will provide a minimum of annual updates 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 shall 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.

13. TO Maintenance. Contractors shall 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 shall 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 request forms processes will be adhered to. 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.

14. Schedules. The Contractor shall 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 shall be to the system/book or TCTO level and cover all major milestones of development. Any changes to the TM Schedule and Status after the TO Guidance Conference shall be coordinated with and approved by program TOMA and PCO.

15. Time Compliance Technical Orders (TCTOs). N/A mailto:AFLCMC.PDSS.TOAPVIPR@us.af.mil

15.1. N/A

15.2. N/A

15.3. N/A

16. PROGRAM SPECIFIC REQUIREMENTS.

16.1 The Offeror shall develop and deliver TO updates in the form source data for the Engine Trailers, T4000 and T4100, Winch Modification. The updates shall contain operation, maintenance and illustrated parts breakdown data for the TOs listed in Section 2, Table 2 of this TMCR. Source data shall be delivered to update existing technical manuals listed below:

• 35D3-3-34-121

• 35D3-3-34-131

16,2 The updates shall be developed from the latest version of the published in Section 2, Table 2 of this document.

Source Data in the form of AFTO Form 158 comments (See attachment 7). Data delivered for this contract shall be digital files.

16.3 For Graphics formats, see “Graphics Format Recommendations” attachment 1 to this document, (page 15). 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.

16.4 In-Process reviews shall be held at the 70% and 100% completion point for each update under development.

Sample In-Process Completion tables are provided in Attachments 5. Comments generated during ALL development reviews shall be incorporated before scheduling the next development review, for example 70% IPR comments shall be incorporated before scheduling the 100% IPR. The Contractor shall provide technical and engineering personnel to assist Air Force personnel during the development reviews and Verification.

TABLE 1

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

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

• To use the fill-in boxes in the tables and matrices, double-click next to a box and change the “Default text” or “Default value” in the pop-up dialog box as required.

(NEW DEVELOPMENT) LINEAR TM TYPE (PUBLICATION) SELECTION TABLES.

N/A

TABLE 2

SUSTAINMENT/MODIFICATION UPDATES TM TYPE SELECTIONS

• 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. 35D3-3-34-121 Same Style and Format

2. 35D3-3-34-131 Same Style and Format

TABLE 3 – LINEAR TM DELIVERY REQUIREMENTS

FOR T4000 and T4100 Engine Trailers Winch Modification Kit

(System/Item)

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

• All SGML file delivers MUST include ALL graphic files.

• All TO files must not be password protected.

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

DELIVERY SCHEDULE

Event Number of days data required prior to event

In Process Review(s) (30 Days)

Verification

(30 Days)

Prepublication Review

(30 Days)

Final TO Distribution

(45 Days)

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

406 SCMS/GUEE

Attn: Becki Middlebrooks 285 Byron St, Ste 19A Robins AFB, Ga 31098

Paper/ Paper/ Paper/ Paper/

SGML/ SGML/ SGML/ SGML/

IPDF /1 IPDF /1 IPDF /1 IPDF /1

XML / XML / XML / XML /

Other/ Other/ Other/ Other/ Paper/ Paper/ Paper/ Paper/

SGML/ SGML/ SGML/ SGML/

IPDF / IPDF / IPDF / IPDF /

XML / XML / XML / XML /

Other/ Other/ Other/ Other/ Paper/ Paper/ Paper/ Paper/

SGML/ SGML/ SGML/ SGML/

IPDF / IPDF / IPDF / IPDF /

XML / XML / XML / XML /

Other/ Other/ Other/ Other/ Paper/ Paper/ Paper/ Paper/

SGML/ SGML/ SGML/ SGML/

IPDF / IPDF / IPDF / IPDF /

XML / XML / XML / XML /

Other/ Other/ Other/ Other/

Total Paper Copies Required:

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

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

• 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/HIS, 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.

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

Specification/Standard Interface Record for T4000 and T4100 Engine Trailers Winch Modification Kit

The TMSS Tailoring Tool will be used to specify all Project SIR 6.2 options. It can be accessed utilizing the following URL https://techdata.wpafb.af.mil/tmss/index.html. The user will attach the output of the tailoring tool under the Project SIR Requirements heading listed below.

PROJECT SIR REQUIREMENTS

https://techdata.wpafb.af.mil/tmss/index.html

GENERAL GUIDELINES

ATTACHMENT 1

Graphics Format Guidelines

• Single column graphics should not exceed 51 Picas High by 20 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)

• PNG graphics will not run with the Air Force software utilized to parse SGML files.

• Avoid creating art as PNG and saving in various formats which will fail.

Encapsulated Post Script (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.

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 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 exported as version 3 to increase cross platform compatibility.

DWG File Format:

• 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 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):

• 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):

• Used for raster graphics

• Supports lossless data compression

• PNG files do not run thru the parser for the SGML files.

Bitmap (BMP):

• Used for raster graphics

Scalable Vector Graphic (SVG)

• Two-dimensional vector and mixed vector/raster graphics

ATTACHMENT 2

REQUEST FOR TECHNICAL ORDER NUMBER

Attachment 3

IDENTIFYING TECHNICAL PUBLICATION SHEET

FOR COMMERCIAL MANUAL

Attachment 4

SAMPLE GOVERNMENT LICENSE AGREEMENT

ATTACHMENT 5

IPR Completion Percentage Guide General Style & Format manuals

In-Process Review Level Percent Complete TO Section 35% 70% TO Title Page 100% - Front Matter - 75% Introduction 100% - General Information 50% 90% Installation Instructions 25% 70% Operation Instructions 25% 70% Theory of Operation 50% 100% Maintenance Instructions 25% 75% Checkout and Troubleshooting - 75% Circuit Diagrams/Illustrations 25% 75% Parts List 35% 80%

ATTACHMENT 6

Sample Work Package Format IPR Completion Chart

ATTACHMENT 7

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

Air Force Technical Manual Contract Requirements (TMCR)
(NEW DEVELOPMENT) LINEAR TM TYPE (PUBLICATION) SELECTION TABLES.
N/A
NOTES:
If “Other” is selected, define media type and quantities:
GENERAL GUIDELINES
Encapsulated Post Script (EPS):
Tagged Image File Format (TIFF):
Computer Graphics Metafile (CGM):
DWG File Format:
Joint Photographic Expert Group (JPEG):
Portable Network Graphics (PNG):
Bitmap (BMP):
Scalable Vector Graphic (SVG)
REQUEST FOR TECHNICAL ORDER NUMBER

File details come from the government source that posted it. Updated .