Attch_22_C001_CDRL_TMCR w Attachment.pdf

CONTRACT DATA REQUIREMENTS LIST Form Approved

(1 Data Item) 0MB No. 0704-0188

The public reponing burden for this collectlon of Information 11 utimat•d to average 110 hours per rHponH, including the time for reviewing in1truction1, aHrching existing data saun:H, gathering and maintaining th• d•t• nHded, and com�ating and ravlawin" tha collection of Information. Sand comments regarding thi1 burden Htima11 or any other aspect of this collection of information, including 1uggubon1 for rtdu�ing tha burden, to th• Department of Oafanu. Exacutiva SarvicH Directorate (0704--0188). Raspondanta should be awara that notwithstanding anv other :,.ov1sion of law. no parson shall ba subject to any penalty for falling to comply with• collection

Q'o!,::f.!�i� ��;:::�1,.;.�f:':V J:�:,.��c�:�i�t�j'��'oc:k �

• do not ratum your form to the ebove organization. Send completed fonn to the

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TOP

D. SYSTEM/ITEM

I

E. CONTRACT/PR NO.

Collapsible Fuel Tanks, !OK, SOK, 210K

1. DATA ITTM ND. 2. TITLE OF DATA ITEM

COOi Technical Manual Contract Requirement (TMCR)

4. AUTHORITY (D•t• Acquisition Document No.)

I

5. CONTRACT REFERENCE

TM-86-0IR 3.3.1

X TM OTHER

F.CONTRACTOR

3. SUBTmE

Technical Manuals

8. REQUIRING OFFICE

406 SCMS/GUEE

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

REQUIRED

DD BLK 16 TM-86-0IR b. COPIES

8. APP CODE 11. AS OF DATE 13. DA TE OF SUBSEQUENT ■. ADDRESSEE

A Blk 16 SUBMISSION Blk 16 Blk 16

18. REMARKS See TM-86-01 BLK 4:·aeneral and specific Technical Manual requi;ements are contained in the Section 2, Part B TM-86-0IR Delivery Matrix

BLK 7: The Wide Area Workflow (WA WF) is to be used for final inspection and acceptance by the 406 SCMS/GUEE.

BLK 8: Approval IAW TM-86-0IR, Para 16.

Blk 9: Distribution Statement provided in TM-86-0IR, Paragraph 9.

Final delivery due 30 days prior to production hardware delivery to USAF.

Blks 10 - 15, See TM 86-0IR

Data Call :GUEE-20-016 NSN 5430-0l -51 l-2125RN (IOK) NSN 5430-0 l -5 l 7-8580RN (50K) NSN 5430-0l-5 l l-4293RN (21 OK)

PR/MIPR # FD2060-20-31489

NOTE: TECHNICAL DATA SHALL NOT BE TRANSMITTED VIA EMAIL. ALL

TRANSMISSION OF TECHNICAL DA TA SHALL BE VIA MAIL OR EXPRESS

DELIVERY SERVICES.

15. TOTAL -

G. PREPARED BY H. DATE I. APPROVED BY

Christopher Morris Nhat Nguyen MORRJS.CHRISTOPHER.S. I 0717 °''...u, -.� IIJ 703SO ),K)IUIJS.C'IWSTOf'IIEU.llfflnOJM

DMitlOlOOIIIIU711-N'OO'

NGUYEN.NHAT.O.12288081 o.,1i.u1-it-4�

,si:

Noll\·EN NllAT D u:001111 .. • ,>n • ""' ,,. ,., Final Draft

R■g Repro

0 0

J. DATE

DD FORM 1423-1 FEB 2001 PREVIOUS EDITION MAY BE USED. Page of Pages

Adobe Profossiooal 8.0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

C

CONTRACT DATA REQUIREMENTS LIST

( 1 Data Item)

A. CONTRACT LINE ITEM NO. le. EXHIBIT I c. CATEGORY:

TDP _x__ TM __ OTHER

o. svsTEMnTEM I E. CONTRACT/PR NO. I F. CONTRACTOR Collapsible Fuel Tanks, !OK, SOK, 21OK

16. REMARKS /Conrinued/

DD FORM 1423-1, FEB 2001 Page __ of Pages

INSTRUCTIONS FOR COMPLETING DD FORM ·1423

(See DoD 5010. 12-M for detailed instructions.)

FOR GOVERNMENT PERSONNEL

Item A. Self-explanatory.

Item B. Self-explanatory.

Item C. Mark (X) appropriate category: TDP - Technical Data Package;

TM - Technical Manual ; Other - other category of data , such as "Provisioning, ""Configuration Management, 11 etc .

Item D. Enter name of system/item being acquired that data will support.

Item E. Self-explanatory (to be filled in after contract award) .

Item F. Self-explanatory (to be filled in after contract award).

Item G. Signature of preparer of CDRL.

Item H. Date CORL was prepared.

Item I. Signature of CDRL approval authority .

Item J . Date CDRL was approved.

Item 1. See DoD FAR Supplement Subpart 4 . 71 for proper numbering.

Item 2 . Enter title as it appears on data acquisition document cited in Item 4 .

Item 3. Enter subtitle of data item for further definition of data item (optional entry) .

Item 4. Enter Data Item Description (DID) number, military specification number, or military standard number listed in DoD 5010.12-L (AMSDL), or one-time DID number, that defines data content and format requirements.

Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g ., Statement of Work paragraph number) .

Item 6. Enter technical office responsible for ensuring adequacy of the data item.

Item 7 . Specify requirement for inspection/acceptance of the data item by the Government.

Item 8. Specify requirement for approval of a draft before preparation of the final data item.

Item 9 . For technical data, specify requirement for contractor to mark the appropriate distribution statement on the data (ref. DoDD 5230.24) .

Item 10. Specify number of times data items are to be delivered .

Item 11. Specify as-of date of data item, when applicable .

Item 12. Specify when first submittal is required.

Item 13. Specify when subsequent submittals are required, when applicable.

Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee . Explain reproducible copies in Item 16.

Item 15. Enter total number of draft/final copies to be delivered .

Item 16. Use for additional/clarifying information for Items 1 through 15.

Examples are: Tailoring of documents cited in Item 4 ; Clarification of submittal dates in Items 12 and 13; Explanation of reproducible copies in Item 14.; Desired medium for delivery of the data item.

00 FORM 1423-1 (BACK), FEB 2001

FOR THE CONTRACTOR

Item 17. Specify appropriate price group from one of the following groups of effort in developing estimated prices for each data item listed on the DD Form 1423.

a . Group I. Definition - Data which is not otherwise essential to the contractor's performance of the primary contracted effort (production, development, testing, and administration) but which is required by DD Form 1423.

Estimated Price - Costs to be included under Group I are those applicable to preparing and assembling the data item in conformance with Govemment requirements, and the administration and other expenses related to reproducing and delivering such data items to the Government.

b. Group II. Definition - Data which is essential to the performance of the primary contracted effort but the contractor is required to perform additional work to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, or quality of the data item.

Estimated Price - Costs to be included under Group II are those incurred over and above the cost of the essential data item without conforming to Government · requirements, and the administrative and other expenses related to reproducing and delivering such data item to the Government.

c . Group Ill . De'finition - Data which the contractor must develop for his internal use in performance of the primary contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of r.ontent , format , frequency of submittal , preparation, control , and quality of the data item.

Estimated Price - Costs to be included under Group Ill are the administrative and other expenses related to reproducing and delivering .such data item to the Government.

d. Group IV. Definition - Data which is developed by the contractor as part of his normal operating procedures and his effort in supplying these data to the Government is minimal.

Estimated Price - Group IV items should normally be shown on the DD Form 1423 at no cost.

Item 18. For each data item, enter an amount equal to that portion of the total price which is estimated to be attributable to the production or development for the Government of that item of data.

These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data , over and above those costs which would otherwise be incurred in performance of the contract if no data were required . The estimated data prices shall not include any amount for rights in data. The Government's right to use the data shall be governed by the pertinent provisions of the contract.

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

GUEE-20-016

Prepared by Christopher Morris,406 SCMS/GUEE, 478-222-7975

Air Force Technical Manual Contract Requirements (TMCR) For

Collapsible Fuel Tanks (Bladders), 10K, 50K, 210K

NSN 5430-01-511-2125RN (10K)

NSN 5430-01-517-8580RN (50K)

NSN 5430-01-511-4293RN (210K)

(Program/Modification/Military System)

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT: , CLIN

Date: 11 AUGUST 2020

Section 1. Technical Order (TO) Program Requirements – TMSS Linear TMs

1. TMCR Tailoring (T). 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) for consideration. 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 (T). The Contractor shall develop and deliver technical manuals in accordance with (IAW) this TMCR that support the Collapsible Fuel Tanks (Bladders), 10K, 50K, 210K 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 Collapsible Fuel Tanks (Bladders), 10K, 50K, 210K 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 (T). 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)”

Prepared by Christopher Morris, 406 SCMS/GUEE, 478-222-7975 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(T). Questions concerning TMSS requirements may be submitted in writing with suggestions for resolution and supporting information to the PCO and Christopher Morris, 406 SCMS/GUEE, 235 Byron St., Suite 19A, Robins AFB, GA 31098-1670, Comm. Ph. 478-222-7975. 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 (T). TOs shall be written to a scope and depth of coverage to support the Collapsible Fuel Tanks (Bladders), 10K, 50K, 210K 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(T).

Contractors shall place the following markings and controls on the title page of the technical manual:

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, Export controlled) (Date Month Year 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 (T). 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.

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 (T). 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 at the 35 percent level of completion, the 70 percent level of completion and the verification level of completion. 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 (T). Manuscript (handwritten) data is not acceptable for any data to be reviewed. 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 (T). Contractors shall maintain accuracy, currency and configuration of TO source data, to include GFI, throughout the contract period of performance. 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 (T). 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 as required 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). The Contractor shall prepare TCTOs, ITCTOs and resulting TO updates as required in support of the Collapsible Fuel Tanks (Bladders), 10K, 50K, 210K program IAW TO 00-5-15 and MIL-DTL-38804 content requirements. TCTOs will be used to document all permanent modifications, initiate special “one time” inspections, or impose temporary restrictions on systems or equipment within specified time limits effecting the Collapsible Fuel Tanks (Bladders), 10K, 50K, 210K program. Costs for TCTO package development must be IAW with AFI 65-601Vol.1.

15.1. The Contractor shall deliver certified drafts of Immediate Action TCTOs to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The Contractor shall deliver drafts with comments incorporated within 24 hours of receipt of comments.

15.2. The Contractor shall deliver initial certified drafts of Urgent Action TCTOs to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The Contractor shall deliver final drafts with “final” customer comments incorporated, within 96 hours of receipt of comments.

15.3. The Contractor shall deliver initial certified drafts of routine safety TCTOs to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The Contractor shall deliver final drafts with “final” customer comments incorporated, within 5 business days of receipt of comments.

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

16. PROGRAM SPECIFIC REQUIREMENTS (T).

a. The contractor shall develop and deliver a new Mil Spec technical manual in Work Package format IAW Section 2, Table 1, covering the Combined Operation and Maintenance Instructions Manual with Illustrated Parts Breakdown.

b. The manual(s) shall be developed using the latest version of the development specifications listed in Table 1 and 2 of this document. Data delivered for this contract shall be digital files on

CD.

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

d. For Graphics formats, see “Graphics Format Recommendations” attachment 1 to this document, (page 11). These recommendations provide wide latitude for developing and delivering graphics. The Contractor shall select one method from these recommendations to prepare and deliver all graphics files. Graphic resolution shall be a minimum of 300 DPI. Graphics files shall be delivered as separate files regardless whether they are embedded in the documents or not. Digital photographs (halftones) shall NOT be used. All graphics shall be line artwork.

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

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

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

Collapsible Fuel Tanks (Bladders), 10K, 50K, 210K

Program (System/Component)

Title or Type of Manuals Specification Required

1. Operation and Maintenance Instructions in Work Package Format

MIL-DTL-87929

a. Combined Operation & Maintenance Instruction Manuals with Illustrated Parts Breakdown

TABLE 2

SUSTAINMENT/MODIFICATION UPDATES TM TYPE SELECTIONS

N/A

TABLE 3 – LINEAR TM DELIVERY REQUIREMENTS

FOR

COLLAPSIBLE FUEL TANKS (BLADDERS), 10K, 50K, 210K

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

Verification

(30 Days)

Prepublication Review

(30 Days)

Final TO Distribution (30 Days)

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

ATTN: CHRISTOPHER MORRIS

235 Byron St, STE 19A Robins AFB, GA 31098-1670

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/

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/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 Collapsible Fuel Tanks (Bladders), 10K, 50K, 210K.

PROJECT SIR REQUIREMENTS

MIL‐DTL‐87929E

Date: 08‐March‐2017 Title: Manuals, Technical ‐ Operation and Maintenance Instructions in Work Package Format (For USAF Equipment)

Applicable Specification 6.2 Option Specification/Standard Interface Records (SIRs)

Yes MIL‐DTL‐87929E Manuals, Technical ‐ Operation and Maintenance Instructions in Work Package Format (For USAF Equipment)

Yes MIL‐DTL‐87929E a. Title, number, and date of this specification.

Title: Manuals, Technical ‐ Operation and Maintenance Instructions in Work Package Format (For USAF Equipment)

Number: MIL‐DTL‐87929E Date: 08‐March‐2017

Yes MIL‐DTL‐87929E b. Manual is to be prepared in single or double column format (see 3.1).

Additional Info: In the SIR field, programs shall specify if the manual shall be single or double column format. If the program cannot specify, state the following in the SIR field: "To be determined by the vendor

Manual is to be prepared in single column format.

with final approval by the program."

No MIL‐DTL‐87929E c. Whichever format is required, (electronic presentation or print presentation), the unique requirements herein apply (see 3.1.1).

Additional Info: This information should be derived from the desired output specified in the TMCR.

Derived by the output specified in the TMCR.

No MIL‐DTL‐87929E d. The type, quantity and breakout of manuals comprising a maintenance manual set (see 3.2.1).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

Already specified in Table 1 of the TMCR.

No MIL‐DTL‐87929E d.1. Organizational level maintenance (O‐Level) (see 3.2.1.2).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

Already specified in Table 1 of the TMCR.

No MIL‐DTL‐87929E d.2. Intermediate level maintenance (I‐Level) (see 3.2.1.1).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

Already specified in Table 1 of the TMCR.

No MIL‐DTL‐87929E d.3. Depot level maintenance (D‐Level) (see 3.2.1.3).

Additional Info: This is already answered by choosing the

Already specified in Table 1 of the TMCR.

manual types in Table 1 of the

TMCR.

No MIL‐DTL‐87929E d.3.(a) Horizontal or vertical maintenance (engines and missiles) (see 3.2.1.3).

Additional Info: In the SIR field, programs shall specify if the horizontal or vertical disassembly and assembly maintenance concept shall be supported. Otherwise, state the following in the SIR field:

"The depot maintenance information shall not support the horizontal or vertical disassembly and assembly maintenance concept."

The depot maintenance information shall not support the horizontal or vertical disassembly and assembly maintenance concept.

No MIL‐DTL‐87929E d.3.(b) Maintenance concept (conditional maintenance or total overhaul) (see 3.2.1).

Additional Info: This 6.2 option can be ignored as the specification already details the maintenance concept for depot maintenance.

Already defined in MIL‐DTL‐87929E.

No MIL‐DTL‐87929E d.4. Combined I‐ and D‐Level maintenance manuals (see 3.2.1.4).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

Already specified in Table 1 of the TMCR.

No MIL‐DTL‐87929E d.5. On‐condition maintenance instruction manual (engine only), (see 3.2.1.5).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

Yes MIL‐DTL‐87929E d.6. If a manual set is to be prepared (see 3.2.1.6).

Additional Info: In the SIR field, programs shall specify if separate manuals are required for each major assembly.

Otherwise, state the following in the SIR field: "Separate manuals are not required for each major assembly."

Separate manuals are not required for each major assembly.

Yes MIL‐DTL‐87929E d.7. If manuals are to be prepared for major accessories (see 3.2.1.7).

Additional Info: In the SIR field, programs shall specify manuals are required for major accessories. Otherwise, state the following in the SIR field:

"Manuals are not required for major accessories."

Manuals are not required for major accessories.

No MIL‐DTL‐87929E d.8. Combined operation and maintenance (see 3.2.2).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

Already specified in Table 1 of the TMCR.

Yes MIL‐DTL‐87929E e. If a master list of containers is required (see 3.4.3.3.4).

Additional Info: In the SIR field, programs shall specify if a master list of containers is required. Otherwise, state the following in the SIR field: "A master list of containers is not required."

A master list of containers is not required.

Yes MIL‐DTL‐87929E f. If repair of special tools and test equipment is to be included (see 3.4.3.3.5).

Additional Info: In the SIR field, programs shall specify if repair instructions for special tools and test equipment shall be included. Otherwise, state the

Repair instructions for special tools and test equipment shall not be included.

following in the SIR field:

"Repair instructions for special tools and test equipment shall not be included."

Yes MIL‐DTL‐87929E g. If instructions for local manufacture of tools/equipment are to be included (see 3.4.3.3.6).

Additional Info: In the SIR field, programs shall specify if instructions for local manufacture of tools/equipment shall be included. Otherwise, state the following in the SIR field:

"Instructions for the local manufacture of tools/equipment shall not be included."

Instructions for the local manufacture of tools/equipment shall not be included.

No MIL‐DTL‐87929E h. If IPB is to be included (see 3.4.3.5).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

Already specified in Table 1 of the TMCR.

Yes MIL‐DTL‐87929E i. If an inspection interval is required for weapons release equipment in ready storage (see 3.5.7.1).

Additional Info: In the SIR field, programs shall specify the inspection frequency for weapons release equipment in ready storage. If the program cannot specify, state the following in the SIR field: "To be determined by the vendor with final approval by the program."

To be determined by the vendor with final approval by the program.

No MIL‐DTL‐87929E j. If specialized manuals are required (see 3.6).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

Already specified in Table 1 of the TMCR.

No MIL‐DTL‐87929E j.1. Aircraft Engine Testing and Trending Procedures Manual (see Appendix B).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

Already specified in Table 1 of the TMCR.

Yes MIL‐DTL‐87929E j.1.(a) If testing and trending procedures is to be a WP in the engine maintenance manual(s) (see appendix B.2.1).

Additional Info: In the SIR field, programs shall specify if engine testing and trending procedures shall be a WP in the engine maintenance manual(s) instead of its own manual. Otherwise, state the following in the SIR field: "Engine testing and trending procedures shall not be a WP in the engine maintenance manual(s)."

Engine testing and trending procedures shall not be a WP in the engine maintenance manual(s).

No MIL‐DTL‐87929E j.2. Aircraft Power Package (Engine Installation Hardware Configuration) Testing Procedures Manual (see appendix C).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

Already specified in Table 1 of the TMCR.

No MIL‐DTL‐87929E j.3. Static Firing of Missile Motors Manual (see appendix D).

Additional Info: This is already manual types in Table 1 of the

TMCR.

No MIL‐DTL‐87929E j.4. System Peculiar Corrosion Control Manual (see appendix E).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

Already specified in Table 1 of the TMCR.

No MIL‐DTL‐87929E j.5. Nondestructive Inspection (NDI) Manual (see appendix F).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

Already specified in Table 1 of the TMCR.

No MIL‐DTL‐87929E j.6. Aircraft Structural Integrity Program (ASIP) Manual (see appendix G).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

Already specified in Table 1 of the TMCR.

No MIL‐DTL‐87929E j.6.(a) If detailed system information for flight data gathering programs is to be included (see G.3.1.4).

Additional Info: In the SIR field, programs shall specify if detailed system information for flight data gathering programs shall be included and which ones are applicable. Otherwise, state the following in the SIR field: "System information for flight data gathering programs shall not be included."

System information for flight data gathering programs shall not be included.

No MIL‐DTL‐87929E j.7. ATE Operator Test Procedures Manual (see appendix H).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

No MIL‐DTL‐87929E j.8. Specialized Storage and Maintenance Procedures; AUR Munitions and Associated Support Equipment, Conventional Components, and CMBR Agents (see appendix I).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

Already specified in Table 1 of the TMCR.

No MIL‐DTL‐87929E j.8.(a) If the table of contents is to contain second level subordinate paragraphs (see I.3.2.c).

Additional Info: In the SIR field, programs shall specify if second level subordinate paragraphs shall listed in the table of contents. Otherwise, state the following in the SIR field: "The table of contents shall not contain second level subordinate paragraphs."

The table of contents shall not contain second level subordinate paragraphs.

No MIL‐DTL‐87929E j.8.(b) If other inspections are to be included and, if so, the categories and types (see I.3.5.5.1.8).

Additional Info: In the SIR field, programs shall specify if any additional inspections, along with their categories and types, shall be included. Otherwise, state the following in the SIR field: "Only the inspections listed in the specification shall be included."

Only the inspections listed in the specification shall be included.

No MIL‐DTL‐87929E j.8.(c) If a humidity indicator inspection cycle table is required (see I.3.5.5.1.8.2).

Additional Info: In the SIR field, programs shall specify if a humidity indicator inspection cycle table shall be included.

Otherwise, state the following in the SIR field: "A humidity indicator inspection cycle table shall not be included."

A humidity indicator inspection cycle table shall not be included.

No MIL‐DTL‐87929E j.8.(d) If a depot related data and special instructions WP is to be included and, if so, what appropriate data is to be included (see I.3.5.11).

Additional Info: In the SIR field, programs shall specify if a depot related data and special instructions WP shall be included and what information it shall contain. Otherwise, state the following in the SIR field: "The depot related data and special instructions WP shall not be included."

The depot related data and special instructions WP shall not be included.

No MIL‐DTL‐87929E j.8.(e) If procedures for containers will not be included (see I.3.3).

Additional Info: In the SIR field, programs shall specify if procedures for containers shall not be included. Otherwise, state the following in the SIR field: "Procedures for containers shall be included."

Procedures for containers shall be included.

No MIL‐DTL‐87929E j.8.(f) If WPs 110 00 through 997 00 or SWPs are to be used and if so, the arrangement and breakout to be used (see I.3.5, I.3.5.b.4).

Additional Info: In the SIR field, programs shall specify if WPs 110 00 through 997 00 or SWPs

To be determined by the vendor with final are required and what information they shall contain.

If the program cannot specify, state the following in the SIR field: "To be determined by the vendor with final approval by the program."

No MIL‐DTL‐87929E j.8.(g) If other WP/SWPs are to be included and the type of information required (see I.3.5.b, I.3.5.12).

Additional Info: This 6.2 option can be ignored as it is a repeat/summary of other 6.2 options (j.8.(d), j.8.(f), j.8.(m), and j.8.(n)).

Not applicable.

No MIL‐DTL‐87929E j.8.(h) If a configuration table is to be included and if so, the required column headings (see I.3.5.1.4).

Additional Info: In the SIR field, programs shall specify if any additional column headings are required for the configuration table. Otherwise, state the following in the SIR field: "No additional columns are required for the configuration table."

No additional columns are required for the configuration table.

No MIL‐DTL‐87929E j.8.(i) If special tools will be illustrated elsewhere in the manual or not illustrated (see I.3.5.3.4).

Additional Info: In the SIR field, programs shall specify if special tools will be illustrated in another WP or not illustrated at all. Otherwise, state the following in the SIR field:

"Special tools shall be illustrated in this WP."

Special tools shall be illustrated in this WP.

No MIL‐DTL‐87929E j.8.(j) If test equipment will be illustrated elsewhere in the manual or not illustrated (see I.3.5.3.5).

Additional Info: In the SIR field, programs shall specify if test equipment will be illustrated in another WP or not illustrated at all. Otherwise, state the following in the SIR field: "Test equipment shall be illustrated in this WP."

Test equipment shall be illustrated in this

WP.

No MIL‐DTL‐87929E j.8.(k) If sample size for periodic inspections (PI) will be other than specified (see I.3.5.5.1.3).

Additional Info: In the SIR field, programs shall specify if sample size for periodic inspections shall be other than as instructed in the specification. Otherwise, state the following in the SIR field: "Sample size for periodic inspections shall be as instructed in the specification."

Sample size for periodic inspections shall be as instructed in the specification.

No MIL‐DTL‐87929E j.8.(l) Whether the IPB will be prepared as a separate WP or as a separate manual (see I.3.5.8.2).

Additional Info: This is already answered by choosing the manual types in Table 1 of the

TMCR.

Already specified in Table 1 of the TMCR.

No MIL‐DTL‐87929E j.8.(m) If a Testing/Reprogramming WP is to be included (see I.3.5.9).

Additional Info: In the SIR field, programs shall specify if a testing/reprogramming WP shall be included. Otherwise, state the following in the SIR field: "The testing/reprogramming WP shall not be included."

The testing/reprogramming WP shall not be included.

No MIL‐DTL‐87929E j.8.(n) If a Contingency Procedures WP is to be included (see I.3.5.10).

Additional Info: In the SIR field, programs shall specify if a contingency procedures WP…