19. TMCR.pdf

TM-86-01Q 27 Oct 2017 1-01: AF TMSS Linear TMs Data Call: GUEE-20-014

Air Force Technical Manual Contract Requirements (TMCR) for

Mobile Aircraft Arresting System NSN 1710015499539RN (Program/Modification/Military System)

, EXHIBIT ATTACHMENT , TO CDRL SEQUENCE NUMBER

REQUEST FOR PROPOSAL/CONTRACT: FA8534-21-R-0009 , CLIN

Date: May 05, 2021

SECTION 1. TECHNICAL ORDER (TO) PROGRAM REQUIREMENTS

1. TMCR Tailoring. This TMCR has been tailored by the program office, including the associated tables, matrices and Specification/Standard Interface Records (SIRs). 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) for consideration. The tailored TMCR shall be attached to the Contract Data Requirements List (CDRL) for Technical Order (TO) delivery, and shall be included in the proposal as a separate exhibit, referenced in the proposal Statement Of Work (SOW). Proposals shall be compatible with the Mobile Aircraft Arresting System NSN 1710015499539RN Technical Order Concept of Operations (TO CONOPS) if prepared. 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. 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 shall develop and deliver technical manuals in accordance with (IAW) this TMCR that supports the Mobile Aircraft Arresting System NSN 1710015499539RN requirements for technically usable manuals concurrent with the program’s TO CONOPS if prepared.

The Contractor may recommend additional Section 2 tailoring to source data and TO updates (Table 2) required to support the Mobile Aircraft Arresting System NSN 1710015499539RN program’s objectives.

3. Commercial Manuals. Contractors shall recommend the use of existing commercial manuals to the maximum extent possible without impairing program support objectives. All proposed commercial manuals are subject to Government review and approval.

3.1. The AF requests the ability to electronically store, print, distribute, update and decollate the commercial manual to allow for printing. Commercial manuals shall be delivered as Portable Document Format (PDF) unless otherwise specified.

3.2. Approved Commercial-Off-The-Shelf (COTS) Manuals shall be delivered with an Identifying TO Publication Sheet (ITPS), IAW MIL-PRF-32216, Performance Specification: Evaluation Of Commercial Off-The-Shelf (COTS) Manuals And Preparation Of Supplemental Data. All PDF files of commercial data shall be non-password protected to allow the AF to decollate the manual for printing.

3.3. If the proposed COTS data is found to be insufficient after review by the Government, the Contractor shall prepare supplemental data for the COTS manual as required IAW Military Standard (MIL-STD)-38784. If the COTS data cannot be supplemented sufficiently the Contractor may be tasked to develop new TM data IAW the applicable TMSS listed in Section 2, Table 1.

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

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. No formal Contractor action on the recommended change shall begin until formal written approval is received from the government. 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 resolved by written request and justified suggestions for resolution submitted through the PCO and Debra Johnson, 406 SCMS/GUEE, 235 Byron St, Bldg 301, Ste 19A Robins AFB, GA 31098-1670, DSN 497-5295. Deficiencies and suggested improvements shall be submitted to the TMSS Preparing Activity (PA). Approved recommendations, 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-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 Mobile Aircraft Arresting System NSN 1710015499539RN 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 be 300 dpi and 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 cognizant Defense Federal Acquisition Regulation Supplement (DFARS) provisions and clauses in providing Unlimited Rights for all source data, TO publications, and TO updates prepared specifically for the contract. Government rights in data are specified in the 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. The Government shall be given Unlimited Rights for 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. For all data delivered to the Government with other than Unlimited Rights, the Contractor shall assert their data rights IAW DFARS 252.227-7017, Identification and Assertion of Use, Release, or mailto:SGMLSupport@us.af.mil

Disclosure Restrictions. 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 Cyber Security Protection IAW AFI 33-200, Information Assurance (IA) Management, AFMAN 17-1301, Computer Security (COMPUSEC), and MPTO 00-33B-5008, Remanence Security for Information Systems. NOTE: Distribution limitations will be determined on a case-by-case basis as TOs are developed, dependent upon TO content.

10. TO Quality. Contractor proposals shall describe how the Government will be allowed to interact with the Contractor’s TO development team. 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- 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 support IPRs with technical writers, engineers and QA personnel. 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 http://www.e-publishing.af.mil/ https://assist.dla.mil/online/start/index.cfm

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 at least 180 days prior to the need date of any Government Furnished Information/Government Furnished Equipment (GFI/GFE) 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/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.

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/STD compliant formatting.

10.7.2. 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 initial TDA. Successful TDAs in no way relieves the Contractor from fixing 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 public domain SGML parser (http://www.jclark.com/sp/).

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 unless the Government determines otherwise. 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.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, or other approved change request form. 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

15.1. N/A

15.2. N/A

15.3. N/A

15.4. N/A

http://www.jclark.com/sp/

16. PROGRAM SPECIFIC REQUIREMENTS.

a. The Offeror shall develop and deliver a revision to Illustrated Parts Breakdown (IPB), TO 35E8-

2-10-4 IAW Section 2, Table 2.

b. A 100% In-Process Review (IPR) shall be submitted for review and approval before the formal delivery.

c. Data delivered for this contract shall be digital files in SGML and IPDF.

d. 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 during the government IPR.

e. For Graphics formats, see “Graphics Format Recommendations” attachment 1 to this document, (pages 13 and 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.

f. Comments generated during the 100% IPR shall be incorporated before the formal delivery.

NOTE: Contractors are responsible for selecting SGML and composition tools for this program.

AF DTDs will work with most COTS SGML editing systems (except Framemaker) however, the FOSIs were developed to work with Datalogic Composing software ONLY. If the Contractor wishes to use any other composing software product, the Contractor is responsible for ensuring all formatted outputs are compatible with the DTL specification listed in Section 2, Table 1 of this document. Structured Framemaker files are unacceptable and shall not be submitted as an SGML delivery to the Air Force. The Air Force DOES NOT profess to recommend one software product over another. Contractor’s are solely responsible for software selection.

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

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

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

TABLE 1

TMSS REQUIREMENTS FOR THE Mobile Aircraft Arresting System NSN 1710015499539RN

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

TABLE 1

TMSS REQUIREMENTS FOR THE Mobile Aircraft Arresting System NSN 1710015499539RN

Program (System/Component)

Title or Type of Manuals Specification Required

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 -- MIL-SPEC (Intercontinental Ballistic Missiles) -- MIL-SPEC (Space)

MIL-PRF-38311

MIL-PRF-38314

a. Operations Manual

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

TABLE 1

TMSS REQUIREMENTS FOR THE Mobile Aircraft Arresting System NSN 1710015499539RN

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) Organizational Maintenance

(2) Intermediate Maintenance

(3) Depot Maintenance

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

(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

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-10-4 MIL-DTL-38807

TABLE 3 – LINEAR TM DELIVERY REQUIREMENTS

FOR Mobile Aircraft Arresting System NSN 1710015499539RN (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) ( Days)

Verification

( 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: Debra Johnson 235 Byron Street, Suite 19A Robins AFB, GA 31098-1670

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/ X

IPDF / X

XML /

Other/

Paper/

SGML/ X

IPDF / X

XML /

Other/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Total Paper Copies Required:

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.

• 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/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 Mobile Aircraft Arresting System NSN 1710015499539RN

PROJECT SIR REQUIREMENTS

• SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-STD-38784A, 11 July 2016

• Department of Defense

• Standard Practice for Manuals, Technical:

• General Style and Format Requirements

• 4.2.1c(1) Technical manuals shall be 8-1/2 x 11 inches formatted in single column format.

• 4.6.2 Photographs/line drawings. Delete paragraph.

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

• SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-DTL-38807D, 22 August 2017

• Detail Specification

• Technical Manuals, Illustrated Parts Breakdown

• 6.2l Manufacturer List is not required (paragraph 3.5.13).

• 6.2m Reference Designators not applicable (paragraph 3.6.6.9).

• 6.2n Paragraph 3.6.7 not applicable.

• 6.2o Multiple SMR columns not required. (Paragraph 3.6.7.7.1).

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

ATTACHMENT 1

Graphics Format Guidelines

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

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

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 – N/A

Attachment 3 – N/A

Attachment 4 – N/A

Sample Government License Agreement

ATTACHMENT 5 - N/A

ATTACHMENT 6 – N/A

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