D003_TM86-01R.pdf

TM-86-01R 01 June 2020 GUEE-21-17 1-01: AF TMSS Linear TMs

Air Force Technical Manual Contract Requirements (TMCR) for

144 kW Universal Load Bank (ULB)

NSN 6150-01-695-3297

(Program/Modification/Military System)

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT: , CLIN

Date: 23 August 2021

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 144 kW Universal Load Bank (ULB), NSN 6150-01-695-3297 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 144 kW Universal Load Bank (ULB), NSN 6150-01-695-3297 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

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.

4.1. Questions concerning TMSS requirements may be submitted in writing with suggestions for resolution and supporting information to the PCO and TO Manager: Nancy R Middlebrooks, 406 SCMS/GUEE, 235 Byron St, Bldg 301, Suite 19A, Robins AFB, GA. 31098; 478-926-2169.

D003 D

FD2060-21-31511 0004AY

TM-86-01R 01 June 2020 1-01: AF TMSS Linear TMs

GUEE-21-17

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 144 kW Universal Load Bank (ULB), NSN 6150-01-695-3297 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. Contractors shall notify the Government, in writing, of manuals which require TO numbers. TO numbers are not required for manuals to be used exclusively by the Contractor’s own personnel. Requests for new TO numbers shall be submitted to the TOMA utilizing the TO numbering worksheet (Attachment 2, Request for Technical Order Number).

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 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, Department of Defense Manual (DoDM) 5200.01, Volume 1-3/Air Force Manual 16-1404, Volume 1-3, 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).

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 D - Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use, Export Controlled) (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/WNZ.

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.

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

16. PROGRAM SPECIFIC REQUIREMENTS.

a. To support 144kW Universal Load Bank (ULB), NSN 6150-01-695-3297:

1) The Offeror shall develop and deliver one Mil-Spec technical manual with combined

Operation and Maintenance Instructions and Illustrated Parts Breakdown. The new technical manual shall be in work package format and in SGML.

b. Mil-Spec technical manual shall be developed using the latest version of the development specifications listed in Table 1 of this document. Data delivered for this contract shall be in the form of electronic PDF files of the TO, and should be submitted along with all SGML files.

c. In-Process reviews shall be held at the 35% and 70% completion point for each manual under development.

d. Comments generated during all development reviews shall be incorporated before the next scheduled development review.

e. For all new technical manual development, a TO Numbering Request Form shall be submitted to the TO Manager in order to have a TO Number assigned for the new manuals.

f. All electronic PDF files delivered on this project shall be non-password protected and allow unlimited access to view, print and decollate the data from the files.

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

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

TABLE 1

TMSS REQUIREMENTS FOR THE

144 kW Universal Load Bank (ULB), NSN 6150-01-695-3297 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 -- MIL-SPEC (Intercontinental Ballistic Missiles) MIL-PRF-38311

TABLE 1

TMSS REQUIREMENTS FOR THE

144 kW Universal Load Bank (ULB), NSN 6150-01-695-3297 Program

(System/Component)

Title or Type of Manuals Specification Required

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

144 kW Universal Load Bank (ULB), NSN 6150-01-695-3297 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. Combined Operation & Maintenance Instruction Manuals w IPB

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. Operation and Maintenance Instructions in Chapter style MIL-DTL-38784

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)

TABLE 1

TMSS REQUIREMENTS FOR THE

144 kW Universal Load Bank (ULB), NSN 6150-01-695-3297 Program

(System/Component)

Title or Type of Manuals Specification Required

(7) ATE Operator Test Procedures

(8) Special Requirements for Storage and Maintenance Procedures;

AUR Munitions/Launchers and Associated Support Equipment, Conventional Components and CMBR Agents

(9) Parachute Packing Procedures

(10) Operators Instructions (Hand-Held Flight Computers)

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

d. Checklists (IAW MIL-DTL-5096)

e. With Illustrated Parts Breakdown

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

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

TABLE 2

SUSTAINMENT/MODIFICATION UPDATES TM TYPE SELECTIONS

N/A

TABLE 3 – LINEAR TM DELIVERY REQUIREMENTS

FOR

144 KW UNIVERSAL LOAD BANK (ULB), NSN 6150-01-695-3297

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

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

Verification

(45 Days)

Prepublication Review

(45 Days)

Final TO Distribution

60 Days

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

Nancy Middlebrooks

406 SCMS/GUEE

235 Byron St Bldg 301, Suite 19A Robins AFB, GA. 31098

Paper/

SGML/ Y

IPDF / Y

XML /

Other/

Paper/

SGML/ Y

IPDF / Y

XML /

Other/

Paper/

SGML/ Y

IPDF / Y

XML /

Other/

Paper/

SGML/ Y

IPDF / Y

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Total Copies Required: 2 2 2 2

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

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 definitions – 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 required 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 sampling inspections shall be at the discretion of the Contractor, and in accordance with commercially acceptable 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.”

5. Replace with: “5. PACKAGING.”

“5.1 Packaging Requirements. For acquisition purposes, the packaging requirements shall be as specified in the contract or order. When the actual packaging of material is to be performed by DoD personnel, these personnel need to contact the responsible packaging activity to determine packaging requirements. Packaging requirements are maintained by the Inventory Control Point’s packaging activity 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 responsible 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 Information.”

“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 144 kW Universal Load Bank (ULB), NSN 6150-01-695-3297

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

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) 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): (Do not use to create graphics for sgml TOs) 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

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

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

22. COMMENTS:______________________________________________________________________

* = Mandatory Field