EXHIBIT F CDRL B028 27Oct22.pdf

Exhibit F

CONTRACT DATA REQUIREMENTS LIST (CDRL)

Man-Portable TACAN Program

Contract Reference: FA8102-23-R2000

Prepared by Air Force Life Cycle Management Center Air Traffic Control and Landing Systems

(AFLCMC/HBAA)

3580 D Avenue – Bldg 201W

Tinker AFB, OK 73145

1. METHOD OF TRANSMITTAL

a. Unless otherwise noted on the CDRL Form (DD Form 1423) in Block 16, all data shall be delivered electronically via email or CD/DVD, and shall be in a software file format that is compatible with Government systems. If the required data cannot be delivered electronically, the Contractor shall distribute per Block 14 of the CDRL.

b. All data submitted by a letter of transmittal or DD Form 250 shall be delivered to the attention of the Requiring Office (Block 6) and will identify the contract number, Data Item Description number, CDRL sequence number, document number and title.

c. Unless otherwise specified in Block 16 of the CDRL, the data submittal date is interpreted as the date the Government (Block 14) receives the data or the date it is submitted electronically.

d. For each data item in the CDRL, the Contractor shall clearly state in the final transmittal letter that this is the last submittal being made and that all contractual requirements concerning the data item have been fulfilled.

2. MODIFICATION OF DATA REQUIREMENTS

a. The Data Manager (DM) is a member of the MP TACAN Replacement Program Integrated Product Team (IPT). No changes to the data requirements of this contract shall be made without coordination of the DM specific approval of the Procurement Contracting Officer (PCO).

b. Changes to Requiring Office (Block 6) and Distribution (Block 14) may be authorized and directed by a PCO letter to be incorporated by subsequent contract modification.

3. DATA APPROVAL:

Unless otherwise specified in the Remarks (Block 16) of the appropriate data item, the following definition applies to Block 8 of the CDRL:

a. The use of an “A” in Block 8 means the document identified is critical and requires written Government approval. The review cycle for data will begin on the date the last addressee receives the data, or upon submittal if delivered electronically. The Office of Primary Responsibility (OPR) designated in Block 6 of the DD Form 1423 will consolidate the evaluations performed by the data recipients with his own and respond through the PCO to the Contractor within thirty (30) working days after receipt of the data submittal, unless otherwise specified.

b. The absence of an “A” in Block 8 does not relieve the Contractor of the obligation to comply with the Data Item Description (DID) requirements.

c. Data submittal requirements shall not be considered to have been met until the CO has determined that all contractual requirements have been met regarding the identified data.

4. REVISIONS TO DATA SUBMITTALS AND RESUBMITTALS OF DATA:

Unless otherwise specified, data submittals that are disapproved by the Government shall be revised and resubmitted by the Contractor within thirty (30) days from the date of the PCO letter unless otherwise noted on the CDRL.

5. TAILORED DATA ITEMS

A slash (/) and the letter “T” (i.e. DI-E-3103A/T) added to the DID number in Block 4 of the CDRL denotes the DID has been tailored to comply with specific program requirements. If data preparation instructions contained in Block 10 of the DID conflict with those of the CDRL, the CDRL instructions will govern.

6. ACRONYMS:

ACO Administrative Contracting Officer ASREQ As Required CO Contracting Officer DAC Days After Contract Award IAW In Accordance With MTHLY Monthly ONE/R One time with revisions LT Letter of Transmittal

7. MARKING TECHNICAL DOCUMENTATION

a. Distribution Marking System:

i. In accordance with Section 1.30 of Title 10, “United States Code” a DoD distribution marking system for technical data has been established by DoD Directive 5230.24, “Distribution Statements on Technical Documents,” 18 March 1987. The intent of the system is to stem the flow of military-related technical data to our adversaries, without inhibiting technological growth or blocking the exchange of technical data that is vital to progress and innovation. All DoD components responsible for technical data are required to determine the distribution availability and arrange to mark the data appropriately before primary distribution. Distribution statements and export-control statements, supplemental to any security markings, shall be marked on all technical data to denote the extent of its availability for secondary distribution, release, and disclosure without need for additional approvals and authorizations from the controlling DoD office.

ii. Based on the technical content of the data, one of seven distribution statements defined in DoD Directive 5230.24 is to be applied to indicate the extent of secondary distribution. The seven authorized distribution statements provide options ranging from unlimited distribution to no secondary distribution without specific authority of the controlling DoD office. Distribution statements should be selected to denote the audience for which the data is intended. The statement selected shall not restrict the data any further than is actually required to protect the interests of the Government. The authority to withhold unclassified technical data from the public is found in Section 130 of Title 10, “United States Code” as implemented by DoD Directive 5230.25 “Withholding of Unclassified Technical Data from Public Disclosure,” 6 November 1984.

iii. It is the responsibility of the program office to select the correct distribution statement, to ensure that the corresponding code letter (“A”, “B”, “C”, “D”, “E”, “F”, or “X”) is in Block 9 of the DD Form 1423 or that Block 16 of the DD Form 1423 contains instructions on application of the correct distribution statement before initial distribution of the technical data. If the Contractor feels that a different statement is required, he may formally notify the contracting officer in a letter, make it a subject of discussion during negotiations or at one of the scheduled program audits or reviews.

b. Marking Technical Data:

i. All new or requested unmarked production, engineering, logistics, and scientific and technical information, regardless of its medium, physical form, or characteristics, including preliminary drafts and working papers, shall be marked with a distribution statement. This includes technical reports, blueprints, drawings, technical orders, technical manuals, plans, instructions, computer software, viewgraphs, film, technical papers, photographs, etc. If the document contains export-controlled technical data, it also must be marked with an export control warning statement. Distribution statements can be applied to technical data that contain or reveal proprietary information used.

(Location suggestions for placing the statements on the data may be obtained from MIL-STD-1806.)

ii. Technical data categorized as cryptographic/communications security, communications/electronic intelligence, and similar categories as may be designated by the Director, National Security Agency, whose distribution is limited through alternate methods, are exempt from these marking provisions.

iii. Certain types of technical data preclude placing the entire notice on the document. To accommodate this problem, each distribution statement contains an authorized abbreviation form. Abbreviated distribution statements are to be used only when space precludes placing the entire notice on the document. The use and wording of these statements are described in the following paragraphs.

c. Controlling Office: The following address shall be used for the “controlling office” for the program:

AFLCMC/HBK, 3001 Staff Dr. Ste 2AC-81A, Tinker AFB, OK 73145

d. Export-Controlled Warning Statement: Besides a distribution statement, the marking system also requires the use of a warning notice on all documents that contain export-controlled technical data. That notice may be used in conjunction with any of the six limited distribution statements (“B”, “C”, “D”, “E”, “F” and “X”.) Statement “A”, which denotes public release, cannot be used in conjunction with the export-control warning notice.

e. Destruction Notice: All unclassified technical data marked with distribution statements “B”, “C”, “D”, “E”, “F” or “X” shall be handled and destroyed as “Controlled Unclassified Information” (CUI), as described in DoD 5400.7-R. Classified data and classified limited technical data shall be handled and destroyed in accordance with the procedures in Chapter IX of DoD 5200.1-R “Information Security Program Regulation” or follow the procedures in DoD 5220.22-M “Industrial Security Manual”.

8. ELECTRONIC DATA TRANSMISSION

a. Electronic Data Transmission Statement for the CDRL:

i. The recipients will be notified by email of each submission of CDRL data. All submissions will be via email or CD/ DVD, unless other arrangements are approved by the Government. The versions of this software shall remain compatible with current program office software. The Contractor shall inform AFLCMC/HBK if any of their data deliverables cannot comply with the above electronic formats. In such cases the Contractor shall recommend, for program office approval, alternative delivery format(s).

ii. The Government review cycle for data will begin on the date the last addressee listed in Block 14 receives the data or the date it is submitted electronically.

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

PROVISIONS OF DOD DIRECTIVE 5230.25.

9. MAILING LISTS:

OFFICE SYMBOL/MAIL ADDRESS

AFLCMC/HBK (ATCALS)

3001 Staff Drive, Post 2AC-81A Tinker AFB, OK 73145 Attn: ATCALS Contract Officer

AFLCMC/HBAA

3580 D Ave, Bldg 201W, RM 74 Tinker AFB, OK 73145 AFLCMC.HBAAA.Navaids@us.af.mil Attn: Ms. Cathy Tassell mailto:Cathy.Tassell@us.af.mil

CONTRACT DATA REQUIREMENTS LIST

TABLE OF CONTENTS

CDRL

No. Authority CDRL Title - Subtitle

B028 TM-86-01R Technical Orders (TO)

DD FORM 1423-1, FEB 2001

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

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

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

H. DATE J. DATE

Page of Pages

5015 F

MP TACAN Replacement Program

B028 Technical Orders (TO)

TM-86-01R (TMCR) SOW Para. 8.4.1., 9.1.2., 9.1.9.3., 12.2. AFLCMC/HBAA

DD

A A

AS REQ

N/A

SEE BLOCK16

SEE BLOCK16

AFLCMC/HBK 1

AFLCMC/HBAAA 1

0 0 2

Block 7: DD250 is required for finalized submissions only.

Block 12, 13 &14: Multiple submissions shall be provided by the Contractor. Unless otherwise notes, each submission shall consist of one copy in paper format and a second copy in electronic format (See TMCR for format requirements) and shall be delivered to

AFLCMC/HBAA:

Field Level Operation and Maintenance TOs submissions:

• First submission shall be prior to or concurrent with the first technical data review and shall be at no less than a 30% completion level.

• Second submission shall be prior to or concurrent with the second technical data review and shall be at no less than a 70% completion level.

• Third submission shall be prior to the start of the OUE and shall be at no less than a

90% completion level.

• Prior to beginning production, the contractor shall submit a finalized version of all required field level operation and maintenance TOs that are 100% complete and government approved.

Block 14: Electronic Media compatible with Microsoft Office Suite 2016 is required.

"Repro" copy defined as electronic media.

G. PREPARED BY

j

Adobe Professional 8.0

FA8102-23-R2000

Joseph M. Griffin, GS-12 William P. Parker II, NH-04 10/26/2022 10/27/2022

1366949700C Bill signature

1366949700C sig

TM-86-01R 10 AUG 2022 1-01: AF TMSS LinearTMs

Air Force Technical Manual Contract Requirements (TMCR) for

MAN PORTABLE TACAN

(Program/Modification/Military System)

ATTACHMENT 1, TO CDRL SEQUENCE NUMBER B028 , EXHIBIT F

REQUEST FOR PROPOSAL/CONTRACT: FA8102-23-R2000 , CLIN 015

Date:

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 or the RFP 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 must develop and deliver technical manuals in accordance with (IAW) this TMCR that support the Man Portable TACAN 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 Man Portable TACAN 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. Contractors must 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. Contractors must use Data Item Description (DID) DI-TMSS-80067C, Technical Manual (TM) Contractor Furnished Aeronautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices, to provide recommendation data. A copy is available through ASSIST at http://quicksearch.dla.mil/qsSearch.aspx.

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

3.2. Approved Commercial-Off-The-Shelf (COTS) Manuals must 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 must 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 must prepare supplemental data for the COTS manual as required IAW Military Standard http://www.tinker.af.mil/Home/TechnicalOrders.aspx http://quicksearch.dla.mil/qsSearch.aspx

(MIL-STD)-38784. If the COTS data cannot be supplemented sufficiently the Contractor will develop new TM data IAW the applicable TMSS listed in Section 2, Table 1.

4. Technical Manual Specifications and Standards (TMSS) Tailoring. AF TMSS tailoring options and some Joint Service TMSS have been documented in preliminary Specification/Standard Interface Records (SIRS) included in Section 3. These preliminary SIRs provide the starting point for further tailoring.

Contractors may recommend additional tailoring of the Joint Service TMSS SIRs and provide recommended SIRs for other TMSS as applicable. Tailoring must not change or delete mandatory requirements which are part of the Document Type Definition (DTD) located in Section 2, Table 1.

NOTE: TMSS requirements marked “(F)” are specifically for Air Force use; “(A)” is for Army, “(M)” is Marine Corps and “(N)” is Navy. Comply with all unmarked and “(F)” TMSS requirements as modified by the tailoring options in each TMSS.

4.1. Questions concerning TMSS requirements may be submitted in writing with suggestions for resolution and supporting information to the PCO and Eddie Edgerton, HBAAC, 3580 D Avenue, Tinker AFB, OK 73145. 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 must 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 requires Government review and approval of recommended additional requirements prior to developing additional data.

6. TO Development. TOs must be written to a scope and depth of coverage to support the Man Portable TACAN operations and maintenance concepts.

6.1. Standard Generalized Markup Language (SGML) tagged TO files must include required illustration (graphics) files in an approved graphics exchange format. Illustration files developed and delivered for other purposes must be used in lieu of developing special TM illustration files whenever possible. All delivered graphics must 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 must be formatted with text, graphics and delivered according to the TMSS specified in Section 2. The Contractor must 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 must 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 must be submitted to the TOMA utilizing the TO numbering worksheet (Attachment 2, Request for Technical Order Number).

8. Data Rights. Contractors must 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, 252.227 and DFARS 252.227-7018 Rights in Noncommercial Technical Data and Computer mailto:SGMLSupport@us.af.mil

Software – Small Business Innovation Research (SBIR). 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. The contractor is required to deliver TO data with the data rights license required by the applicable DFARS clauses. Contractor must 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 must mark such data only in accordance with the applicable DFARS clause. The Contractor must 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 must 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.01V2_AFMAN 16-1404V2, Department of Defense Instruction (DODI) 5230.24, Department of Defense Directive (DODD) 5230.25, DoDI 5200.48, Controlled Unclassified Information, DAFI 61-201, Management of Scientific and Technical Information (STINFO) and MIL-STD-38784 (available at http://www.e-publishing.af.mil/ https://www.esd.whs.mil/DD/admin_inst/,or https://assist.dla.mil/online/start/index.cfm). The markings and notices must be reviewed during In- Process Reviews (IPR). The Contractor must also apply policy and procedures for Cybersecurity Program Management IAW AFI 17-130, AFMAN 17-1301, Computer Security (COMPUSEC) NOTE:

Distribution limitations will be determined on a case-by-case basis as TOs are developed, dependent upon TO content.

10. TO Quality The Contractors must 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 must maintain a Technical Manual Quality Assurance (TMQA) Program Plan for this effort. The TMQA Program Plan must be available for review at the TO Guidance Conference. The TMQA Program Plan must 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 must 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 must 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 must 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 must 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 http://www.e-publishing.af.mil/ https://www.esd.whs.mil/DD/admin_inst/ https://assist.dla.mil/online/start/index.cfm program office. During the IPRs the Contractor will be responsible to maintain a master markup of the document being reviewed. The Contractor must 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 must 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 must be technically edited and reviewed according to the TMQA Program Plan. Manuscript (handwritten) data is not acceptable for any data to be reviewed. All tech data must be in TO format. At the 30, 70 and 90% review, all TOs must be delivered in order to perform a full IPR. Figure 1 states the percentage the Technical Orders must be at for each IPR. The TMQAP checklists shall be available for review by the government during the IPRs. All symbols will be NEMA or ANSI compliant.

Figure 1 IPR Requirements

TECH ORDER SECTION 30% 70% 90%

-- ALL TOs—(except IPB) Percent Complete Cover/Title Page with TO number 75% 100% List of Effective Pages (Front Matter) - 75% 100% Verification Status Page (Front Matter) 100% Table of Contents (Front Matter) - 75% 100% List of Illustrations (Front Matter) - 75% 100% List of Tables (Front Matter) - 75% 100% Introduction 75% Safety Summary (as applicable) 75%

--INSPECTION WORKCARDS--

Front Matter 50% 100% Section I 50% 100% Section II 50% 100%

--ILLUSTRATED PARTS BREAKDOWN—(IPB)--

Cover/Title Page with TO Number 75% List of Effective Pages - 75% 100% Table of Contents - 75% 100% Forward 100% Maintenance Parts List 35% 75% 100% Numerical Index - 75% 100% Reference Designator Index - 75% 100%

--WIRING DATA (WD)/SCHEMATIC DIAGRAM (SD) MANUALS--

Standard IC Symbols (NEMA/ANSI compatible) 100% Illustration Index - 75% 100% Wire List 25% 75% 100%

10.4 Certification. The Contractor must 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 must 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 must 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 must notify the Government, as identified in the contract, at least 180 days prior to the need date, of any Government Furnished Property (GFP), Government Furnished Information, and/or Government Furnished Equipment (GFI/GFE) as required, to perform certification tasks. TO 00-5-1 and TO 00-5-3 must be referenced for additional information on TO Certification requirements.

10.4.1. The Contractor must 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 must 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 must maintain a master mark-up of the document and record minute items during the Government verification process. The Contractor must 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 must 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 must 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 must 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 with the assistance of AFLCMC/HIAM (AF TMSS Office, SGMLSUPPORT@us.af.mil).

10.7.1. MIL-SPEC (SGML) TO Data. The Contractor must 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

Schematics 25% 75% 100%

--OPERATION & MAINTENANCE INSTRUCTION MANUALS--

General Information 50% 75% 100% Installation 25% 70% 100% Preparation for Use and Reshipment 25% 70% 100% Operation 25% 70% 100% Theory of Operation 50% 100% Maintenance including Checkout, Troubleshooting, and Replacement 25% 75% 100%

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 must 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 must parse all SGML files required for the TOs prior to Government delivery and must 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 must maintain accuracy, currency and configuration of TO source data, to include GFI, throughout the contract period of performance. The Contractor must 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 must 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 must 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 must 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 must 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 must 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 must be coordinated with and approved by program TOMA and PCO.

15. Time Compliance Technical Orders (TCTOs). The Contractor must prepare TCTOs, ITCTOs and resulting TO updates as required in support of Man Portable TACAN 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 mailto:AFLCMC.PDSS.TOAPVIPR@us.af.mil time limits effecting Man Portable TACAN. Costs for TCTO package development must be IAW with AFI 65-601Vol.1.

15.1. The Contractor must 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 must deliver drafts with comments incorporated within 24 hours of receipt of comments.

15.2. The Contractor must 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 must deliver final drafts with “final” customer comments incorporated, within 96 hours of receipt of comments.

15.3. The Contractor must 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 must deliver final drafts with “final” customer comments incorporated, within 5 business days of receipt of comments.

15.4. The Contractor must 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 must deliver final drafts with “final” customer comments incorporated, within 10 business days of receipt of comments.

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

• Separate IPB TO required and not included in Operations and Maintenance Manual.

• Wiring Data (WD) and Schematic Diagram (SD) Manuals shall be combined.

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

Table 1 TMSS Requirements for the Man Portable TACAN 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. Flight Operation Manuals MIL-DTL-7700 Flight Manuals

a. Flight Manual ☐

b. Performance Data Manual ☐

c. Mission Crew Manual and Associated Checklists ☐

d. Fanfold Checklists ☐

e. Supplemental Manual ☐

f. Abbreviated Flight Crew Checklist ☐

g. Non-nuclear Weapon Delivery Manual ☐

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

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

j. Aircrew Nuclear Bomb Delivery Manual (Tactical Aircraft)

k. Non-nuclear Weapon Delivery Checklist ☐

l. Nuclear Weapon Delivery Checklist (Strategic Bomber Aircraft)

m. Aircrew Nuclear Bomb Delivery Checklist (Tactical Aircraft)

n. Non-nuclear Weapon Delivery Source Data Packages ☐

Weight and Balance (Aircraft)

a. Loading Data Manual ☐

TMSS Requirements for the Man Portable TACAN Program

(System/Component) Title or Type of Manuals Specification Required

b. Sample Basic Weight Checklists ☐

4. List of Applicable Publications MIL-DTL-8031 ☒

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

6. 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 ☐

7. Space Operation and Support Documentation (Intercontinental Ballistic Missiles) MIL-PRF-38311 ☐

8. Work Unit Code Manual MIL-DTL-38796

a. Standard WUC Manual ☒

b. Two Chapter Manual ☐

c. Three Chapter Manual ☐

9. Calibration Procedures MIL-DTL-38793 ☐

10. Time Compliance Technical Orders (TCTOs) MIL-DTL-38804

a. TCTO ☒

b. TCTO Supplement ☒

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

12. Illustrated Parts Breakdown MIL-DTL-38807 ☒

13. 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 ☒

TMSS Requirements for the Man Portable TACAN Program

(System/Component) Title or Type of Manuals Specification Required

14. Operation and Maintenance Instructions 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) ☐

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

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

16. 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. ☐ ☐ ☐ ☐ ☐

2. ☐ ☐ ☐ ☐ ☐

3. ☐ ☐ ☐ ☐ ☐

4. ☐ ☐ ☐ ☐ ☐

5. ☐ ☐ ☐ ☐ ☐

6. ☐ ☐ ☐ ☐ ☐

7. ☐ ☐ ☐ ☐ ☐

8. ☐ ☐ ☐ ☐ ☐

9. ☐ ☐ ☐ ☐ ☐

10. ☐ ☐ ☐ ☐ ☐

11. ☐ ☐ ☐ ☐ ☐

12. ☐ ☐ ☐ ☐ ☐

13. ☐ ☐ ☐ ☐ ☐

14. ☐ ☐ ☐ ☐ ☐

15. ☐ ☐ ☐ ☐ ☐

16. ☐ ☐ ☐ ☐ ☐

17. ☐ ☐ ☐ ☐ ☐

18. ☐ ☐ ☐ ☐ ☐

19. ☐ ☐ ☐ ☐ ☐

20. ☐ ☐ ☐ ☐ ☐

TABLE 3 – LINEAR TM DELIVERY REQUIREMENTS

FOR MAN PORTABLE TACAN

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

• SGML must be provided with 30% delivery to ensure compatibility.

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

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

TOMA AND PM

3580 D Avenue Bldg 201W Tinker AFB, OK 73145

Paper/

SGML/ X

IPDF / X

XML /

Other/

Paper/

SGML/

IPDF / X

XML /

Other/

Paper/

SGML/ X

IPDF / X

XML /

Other/

Paper/

SGML/ X

IPDF / X

XML /

Other/ PCO Paper/

SGML/

IPDF /X

XML /

Other/

Paper/

SGML/

IPDF / X

XML /

Other/

Paper/

SGML/

IPDF /X

XML /

Other/

Paper/

SGML/

IPDF /X

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Total 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.01_AFMAN 16-1404 DOD Information Security Program DOD 5220.22-M National Industrial Security Program Operating Manual

4. Replace with: “4. VERIFICATION.”

“All cross-servicing guides must meet the requirements of sections 3 and 5 of this specification, as required by the acquiring activity. The requirements set forth in this specification must become a part of the Contractor’s overall inspection system or quality program. The absence of any requirements in this specification must 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 must 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.”

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

5. Replace with: “5. PACKAGING.”

“5.1 Packaging Requirements. For acquisition purposes, the packaging requirements must 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 must be in accordance with the requirements of MIL-STD-1840C, Automated Interchange of Technical Information.”

“5.1.2 Classified Material. Classified material must be packaged and identified in accordance with DODM 5200.01_AFMAN 16-1404, 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 (program name)

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

PROJECT SIR REQUIREMENTS

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

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 must 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 must 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 must 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): (Caution: JPEG 2000 files are not to be used at all due to platform display issues.)

• JPEG File format should be used as last resort. Color screenshots/photos should be saved as TIFFs due to possible system compatibility issues.

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

Portable Network Graphics (PNG):

• Used for raster graphics

• Supports lossless data compression

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

Bitmap (BMP):

• Used for raster graphics

Scalable Vector Graphic (SVG)

• Two-dimensional vector and mixed vector/raster…