Exhibit_B_-_Not_Separately_Priced_CDRL's_(19_August_2014).pdf

Contract Data Requirements List (CDRL)

Exhibit B

Solicitation Number: FA8730-14-R-0017

AN/FMQ-22

Contractor Logistics Support (CLS)

Date: 19 August 2014

Revision 1

Contents:

1. CDRL Preparation/General Instructions

2. Revision page

3. CDRL Points Of Contact (POCs) And CDRL Distribution Requirements List

4. CDRL Table of Contents

5. DD Form 1423s

NOTE: Implementation of this CDRL will only be required in conjunction with a separately priced order placed under CLIN X004 (Special Projects).

REVISION HISTORY

Revision 1, August 2014:

Front cover amended to reflect the modification data and the revision number.

Page 3: information added – “NOTE: Implementation of this CDRL will only be required in conjunction with a separately priced order placed under CLIN X004 (Special Projects).”

CDRL POINTS OF CONTACT (POCs) AND DISTRIBUTION REQUIREMENTS LIST page removed “Matthew O’Connell” and replaced with “Omayra Del Valle.”

CDRL PREPARATION INSTRUCTIONS

1. Document of Data Requirements. Except for data requirements in the DOD Federal

Acquisition Regulation Supplement (DFARS) clauses, DD Form 1423 or the automated DD Form 1423A must be used as the sole contractual list of data to be delivered under the contract.

2. Instructions for Completing Items A through J:

A. CONTRACT LINE ITEM NO. Enter the contract line item number (CLIN) that is associated with the CDRL.

B. EXH/ATCH NO. Enter the exhibit or attachment number for the Contract Data

Requirements List (CDRL).

C. CATEGORY: TDP, __TM__OTHER__. Check the appropriate category for Technical Data Package (TDP), Technical Manual, or Other Types of data which comprise a TDP, as defined in attachment 1. Acquisition of TMs is covered by AFR 8-2, Air Force Technical Order System. Other data may be further categorized, such as provisioning, configuration management, etc. If the CDRL does not contain a specific category of data requirements, simply enter “Miscellaneous”.

D. SYSTEM/ITEM. Identify the system, item, or project by designator or name.

E. CONTRACT/PR NO. If known, enter the actual contract number: if not, enter the number of the PR or other appropriate designator.

F. CONTRACTOR. Enter the contractor’s name or acronym (inserted at award).

G and H. PREPARED BY, DATE: Enter the name, title, and office symbol of the DMO responsible for preparation of the contract data requirements list. Normally, these items are completed only on the first page of each exhibit or attachment.

I and J. APPROVED BY, DATE: Enter the name, title, and office symbol of the program manager or the designee responsible for approving the CDRL. Normally these items will be filled in only on the first page of each exhibit or attachment.

3. Instructions for Completing Items 1 through 16:

1. DATA ITEM NO. Enter the CDRL sequence number (i.e. for exhibits, enter the Exhibit Line Item Number (ELIN); for attachments, enter the data item sequence number). Reference DFARS 4.7106.) NOTE: When the CDRL contains less than 1,000 data line items, the last three digits of the exhibit line may be numbered numerically.

2. TITLE OF DATA ITEM. Enter the exact title as it appears in item 1 of the DD Form 1664.

3. SUBTITLE. If the title requires further identification, enter a subtitle. (If necessary, use item 16 for further identification of the data item).

CDRL PREPARATION INSTRUCTIONS (continued)

4. AUTHORITY (Data Acquisition Document Number). Enter the number as it appears in item 2 of the DD FORM 1664. Add/T if the DID has been tailored.

5. CONTRACT REFERENCE. Enter document and paragraph numbers that identify the task or requirement from which the data flows (contract clause, statement of work paragraph, Integrated Master Plan paragraph, etc.) to help identify the data item authorized by item 4 (see item 4 above).

6. REQUIRING OFFICE. Enter the activity responsible for advising on the technical adequacy of the data. This may be the first addressee in item 14. When data require approval (see item 8 below), this activity is responsible for determining if the data submitted should be approved as submitted, or revised to meet contract requirements.

7. DD FORM 250 REQ:

a. DD Form 250 will only be required for data listed on the CDRL, which requires government inspection and acceptance. These are:

(1) Final Air Force technical Orders.

(2) Engineering drawings, which are delivered to an Air Logistics Center Engineering Data Service Center.

(3) Data which will be used by Air Force personnel for operation, installation, or maintenance, even though equipment and/or software will not be transferred to AFLC (AFR 800-4).

b. Designate the location (contractor’s facility, or destination) for performance of government inspection and acceptance, by entering the applicable code for inspection and acceptance, as shown below:

CODE INSPECTION ACCEPTANCE

SS Source (DD Form 250) Source (DD Form 250) DD Destination (DD Form 250) Destination (DD Form 250) SD* Source (DD Form 250) Destination (DD Form 250) DS Destination (DD Form 250) Source (DD Form 250) LT Letter of Transmittal only NO No inspection or acceptance required XX Inspection and acceptance requirements specified elsewhere in the contract

S indicates the contractor's facility.

D normally indicates the primary distribution point.

*SD will be used for all engineering data that are to be delivered to an Engineering Data Service Center

8. APPROVAL CODE. Items of critical data requiring specific advance written approval prior to distribution of the final data item, such as test plans, are identified by an "A" placed in this item. Most of these data items require submission of a preliminary draft prior to publication of a final document. When block 8 is blank, approval is not required, although the Government has the inherent right to disapprove any data item.

9. DIST STATEMENT REQUIRED. References the distribution statement to be affixed to the deliverable in accordance with DODD 5230.24, Marking Technical Data Prepared By or For the Department of Defense.

10. FREQUENCY. The following are the codes used in this block:

CODE FREQUENCY

DAILY Daily WEKLY Weekly BI-WE Each 2 weeks MTHLY Monthly BI-MO Each 2 months QRTLY Quarterly ANNLY Annually SEMIA Each 6 months OTIME One time ONE/R One time and revisions R/ASR Revisions as required

* ASREQ As required DFDEL Deferred delivery ONE/P One time preliminary draft 2TIME Two separate submittals

* When ASREQ is used in Items 10, 11, 12, or 13, an explanation of the requirement will be entered in Item 16.

11. AS OF DATE (AOD). If the data will be submitted only once, enter the as of date (the cutoff date) as follows: year/month/day. If the data will be input on a recurring basis, which has been set by item 10, show the number of days between the cut-off date and the end of the input period. For instance, if the data are to be submitted 15 days before the end of the input period enter 15. If the data are to be submitted at the end of the input period enter 0. If necessary, use item 16 to explain further.

12. DATA OF FIRST SUBMISSION. Enter the date of submission as follows:

year/month/day. If the delivery of the data depends on the initiation of a specific event or milestone, identify this event or milestone. If you do not know the contract start date, enter the number of days the data is due after the contract start for example, 30 DAC (Days after Contract). If this data is not known nor needs more clarification, explain in item 16. If the data are subject to deferred delivery enter “DFDEL”. If an acronym is created to identify an event or milestone, define the acronym in item 16. NOTE: Do not insert classified dates.

13. DATE OF SUBSEQUENT SUBMISSION. If the data item will be submitted more than once, enter the dates of subsequent submission. If a draft was required, enter the date the final document is to be submitted.

14. DISTRIBUTION. Identify each addressee and give the number of copies (regular and reproducible) to be received by each one (for example, TIC-320/0). If appropriate, use office symbols, contractor initials, or DID Handbook E-4 code numbers and command initials:

in this case, attach a list explaining these codes. If reproducible copies are required, give the type of reproduction request here or in item 16 (offset, mat, vellum, negative, floppy disk, magnetic tape, etc.). If the data are not actually to be delivered to the Government or to associated contractors, enter the appropriate instruction.

15. TOTAL. Enter the total number of copies (regular or reproducible) for one delivery;

this number should be the sum of all the copies specified in item 14. If distribution fluctuates, use a not to exceed number.

16. REMARKS: Use this space to explain the following:

a. Tailored features of the DID.

b. Items 1 through 15

c. Any re-submittal schedule or special conditions involved in updating data submitted for government approval.

CDRL GENERAL INSTRUCTIONS

1. The Data Items on the DD Forms 1423 are cross-referenced thereon in Block 5, to the associated Integrated Master Plan (IMP) tasks under which the basic information is generated.

These data items shall be prepared in accordance with the applicable Data Item Descriptions (DIDs) set forth in DOD 5010.12-L, AMSDL, as tailored, or one-time DIDs.

a) Standard DIDs. These are identified in DOD 5010.12-M, and the “Assist Quick CDRL Search” Website: http://assist.daps.dla.mil/quicksearch/.

b) Tailored DIDs. These are standard DIDs which have specific modifications or tailoring applied to them. These are identified with the suffix “/T” at the end of the DID number in Block 4 (e.g. DI-MISC-80711/T).

c) One-Time DIDs. These are DIDs approved for one-time acquisition use which is associated with a unique data requirement applicable to a single contract (e.g., OT-97-xxxxx).

d) Marking of Data. DODD 5230.24, March 1987.

2. Block 10 of DD Form 1664 (DID) together with any tailoring of the DIDs contains instructions which shall be followed by the contractor in the preparation of data for delivery under this contract.

3. Data submitted in this contract shall be accompanied by a Letter of Transmittal (L\T) and be identified with the following elements:

a) Contractor

b) Contractor’s Transmittal Letter Number, including a running serial number and date

c) Contract Number

d) CDRL Data Item (Sequence) Number

e) DID number and Title

f) Revision Identification, if any

g) Block 14 (or modified) distribution list

4. Data shall be submitted for receipt by the customer in accordance with the delivery schedule specified on the individual DD Form 1423, except those due dates falling on non-working days (Saturdays, Sundays, and recognized national {legal} holidays) shall be construed to mean the next regular working day. All due dates (e.g. 30 DAC) are calendar days unless specified differently otherwise.

5. Existence of an “A” in Block 8 on the DD Form 1423 indicates written approval by the Procuring Contracting Officer (PCO) is required. Unless a different time period for approval is specified on the DD Form 1423, the Government will have 30 days from the date of receipt on the data for notifying the contractor of the approval/disapproval disposition of a data submission. In the event that a data submission is disapproved, the PCO will advise the contractor of the reasons for disapproval and a resubmission shall be accomplished within thirty (30) days unless specified differently otherwise. Approval indicates Government concurrence to proceed to the next event.

http://assist.daps.dla.mil/quicksearch/

CDRL GENERAL INSTRUCTIONS (continued)

In the absence of an “A” in Block 8, the Government has the inherent right to disapprove any data item. Approval does not ensure compliance with DID format and content requirements, since the Contractor is obligated to meet these requirements under the terms of the contract.

6. DD250s will be required upon completion of the last deliverable of each CDRL Exhibit.

7. Appropriate DODD5230.24 Distribution Statements identified in Block 9 on the DD Form 1423, and further defined in the CDRL “Remarks” Block, shall be placed on the document cover page.

8. The contractor shall apply export control warning statements IAW MIL-STD-1806 to CDRL items identified as “TDP” in item C of each DD Form 1423-1.

9. The contractor shall address all letters of transmittal to the Procuring Contracting Officer.

10. Increases or decreases to CDRL quantities shall be in accordance with the Special Provision titled “Modification of Data Requirements”.

11. Data should be delivered by electronic media whenever possible. All data, electronic or otherwise specified, must comply with the distribution statements indicated in Block 9 of the DD Form 1423.

12. Requirements for periodic revisions to data, where no changes have occurred since the last submission, shall be satisfied by a record transmittal letter/form from the Contractor stating that “no changes have occurred since the last submission”. In such cases, the Contractor shall identify the data in question, the reporting period, and the transmittal letter and number of the prior data transmittal. Government disposition will not be provided for record transmittals;

however, the Government reserves the right to non-concur with the reported negative status.

CDRL POINTS OF CONTACT (POCs) AND DISTRIBUTION REQUIREMENTS LIST

NAME

EMAIL CDRLS

Distribute All CDRL submissions to the following POCS

Jeff Green (AN/FMQ-22 Program Manager)

Jeffery.Green.3@us.af.mil All

Kenneth Haile (Procuring Contracting Officer)

Kenneth.Haile.1@us.af.mil All

Matthew Smith (Contracts Specialist)

Matthew.Smith.96@us.af.mil All

William Drury (Configuration and Data Manager)

William.Drury.1@us.af.mil All

Oscar “Butch” Seefried (Logistics Manager)

Oscar.Seefried.ctr@us.af.mil B001

Laura Horstmann (Lead Engineer)

Laura.Horstmann.1@us.af.mil B002 & B003

Omayra Del Valle (Information Assurance)

Omayra.delvalle.ctr@us.af.mil B003

Derek Lung Derek.Lung.ctr@us.af.mil B003 (Test Manager)

AFWA /A5/8 AFWA/A5/A8@offutt.af.mil All

Daniel Musameh Daniel.Musameh@us.af.mil B002 & B003 mailto:Jeffery.Green.3@us.af.mil mailto:Kenneth.Haile.1@us.af.mil mailto:Matthew.Smith.96@us.af.mil mailto:William.Drury.1@us.af.mil mailto:Oscar.Seefried.ctr@hanscom.af.mil mailto:Laura.Horstmann.1@us.af.mil mailto:Omayra.delvalle.ctr@us.af.mil mailto:Derek.Lung.ctr@us.af.mil mailto:AFWA/A5/A8@offutt.af.mil mailto:Daniel.Musameh@us.af.mil

CDRL TABLE OF CONTENTS

Sequence Data Item Title/ Number Description (DID) Subtitle

B001 TM-86-01M/T Commercial Off-the-Shelf (COTS) Manual and

Associated Supplemental Data

B002 DI-ADMN-81306 Program Protection Implementation Plan (PPIP)

B003 DI-MISC-80711A/T Scientific and Technical Reports, Comprehensive

DIACAP Package

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

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 Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contractor Officer for the Contract/PR No. Listed in Block E.

A. CONTRACT LINE ITEM NO.

0006, 1006, 2006, 3006, 4006, 5006

B. EXHIBIT

B

C. CATEGORY:

TOP _____________ TM- _____________ OTHER LOGISTICS

D. SYSTEM / ITEM

AN/FMQ-22

E. CONTRACT / PR NO.

TBD

F. CONTRACTOR

TBD

1. DATA ITEM NO.

B001

2. TITLE OF DATA ITEM

Commercial Off-the-Shelf (COTS) Manual and Associated Supplemental Data

3. SUBTITLE

COTs

4. AUTHORITY (Data Acquisition Document No.)

TM-86-01M/T

5. CONTRACT REFERENCE

PWS PARAs 6.7 & 7.3.3

6. REQUIRING OFFICER

AFLCMC/HBAW

7. DD 250 REQ.

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

12. DATE OF FIRST SUBMISSION

14. DISTRIBUTION

DS SEE BLOCK

SEE BLOCK 16 b. COPIES

8. APP CODE C 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE

Draft

Final

A SEE BLOCK

SEE BLOCK 16 Reg Repro

16. REMARKS SEE BLOCK 16

Block 9: Distribution authorized to Department U.S. Government Agencies and their contractors (Administrative or Operational Use) (July 2014). Other requests shall be referred to AFLCMC/HBAW, 75 Vandenberg Drive, Building 1630, Hanscom AFB, MA.

Blocks 10, 11, 12, & 13:

Draft submittal for revisions due NLT thirty (30) calendar days after change is identified.

Final submittal adjudicating government comments and Validation and Verification comments due with thirty (30) calendar days.

Revisions as required.

Block 14: Initial and subsequent submittals (to include all revisions) shall be provided electronically via email to: (See CDRL Points Of Contact (POCs) And Distribution Requirements List).

The data should be in a format compatible with Microsoft Office 2000 or later, Microsoft Project 2000 or later as applicable.

15. TOTAL SEE BLOCK 16

G. PREPARED BY

Bill Drury, GS-12, Configuration/Data Manager

H. DATE

30 July 14

I. APPROVED BY

Jeff Green, GS-12, AN/FMQ-22 Program Manager

J. DATE

30 July 14

DD Form 1423–1, JUN 90 Previous editions are obsolete Page __1__ of __1__ Pages .

TM-86-01

Air Force Technical Manual Contract Requirements (TMCR) for

AN/FMQ-22

ATTACHMENT TO CDRL SEQUENCE NUMBER B001, EXHIBIT B

REQUEST FOR PROPOSAL/CONTRACT: FA8730-14-R-0017

Date: 30 JULY 2014

SECTION 1. TECHNICAL ORDER (TO) PROGRAM REQUIREMENTS

1. TMCR Tailoring. Offerors must tailor this TMCR document, including the associated tables, matrices and Specification/Standard Interface Records (SIRs). The tailored TMCR shall be attached to the CDRL for TO delivery, and shall be included in the proposal as a separate exhibit, referenced in the proposal PWS. Air Force TO Acquisition procedures, including procedures for tailoring this document, are found in TO 00-5-3, AF Technical Order Life Cycle Management. Any terms or procedures found in this document may be researched there.

2. TO Program Scope. The offeror shall tailor Section 2 to propose the TO types (Table 1) and source data, TO updates, commercial manuals, and TOs prepared to Non-Government Standards (NGS) (Table 2) required to support the AN/FMQ-22 program’s objectives.

3. Commercial Manuals. Offerors shall propose the use of existing commercial manuals to the maximum extent possible without impairing program support objectives. The proposal will describe the method used to recommend and submit specific manuals to the government for review and approval.

NOTES: a) Contractors may use Data Item Description (DID) DI-TMSS-80067, Technical Manual (TM) Contractor Furnished Aeronautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices (located at http://quicksearch.dla.mil/), to provide recommendation data. b) Government activities will use MIL-PRF-32216, Evaluation of Commercial Off-The-Shelf (COTS) Manuals and Preparation of Supplemental Data, as a guide for review and acceptance of all recommended commercial manuals.

4. Technical Manual Specifications and Standards (TMSS) Tailoring. TMSS are tailored by selecting between options offered in paragraph 6.2 of each TMSS. The tailoring is recorded in SIRs and added to Section 3 of this document for each TMSS required. NOTE: Tailoring must not change or delete mandatory requirements which are part of the Document Type Definition (DTD) structure.

4.1. AF options in some Joint-Service TMSS have been documented in preliminary SIRs included in Section 3. These preliminary SIRs provide the starting point for further tailoring. Offerors shall complete tailoring of the Joint-Service TMSS SIRs and provide recommended SIRs for other TMSS or NGS as applicable. 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 options in paragraph 6.2.

4.2. Questions concerning TMSS requirements may be resolved by written request and justified suggestions for resolution submitted through the Procuring Contracting Officer (PCO). Deficiencies and suggested improvements shall be submitted to the TMSS Preparing Activity (PA). Approved recommendations, corrections and clarifications will be maintained with contract documentation.

5. Subsequent TO/Data Requirements. Offerors shall propose a process for notifying the government when additional TO or source data requirements are identified subsequent to contract award. This http://quicksearch.dla.mil/ process shall require government review and approval of recommended additional requirements prior to contractual approval. NOTE: The recommended notification process is to use CFAE/CFE Notices (DI-

TMSS-80067).

6. TO Development. The offeror shall propose TO development practices and procedures that ensure TOs and data are compatible with the Air Force Technical Order Concept of Operations (CONOPS) and the Enhanced Technical Information Management System (ETIMS). In addition, TOs shall be written to a scope and depth of coverage sufficient to support the operations and maintenance concepts, and to the Reading Grade Level (RGL) specified in MIL-STD-38784, Standard Practice for Manuals, Technical:

General Style and Format Requirements.

7. TO Numbering. Offerors shall notify the government of manuals which require TO numbers. TO numbers are not required for manuals to be used exclusively by the offeror’s own personnel. (NOTE:

DI-TMSS-80067 may be used to provide the notification.) AF procedures for numbering TOs are described in TO 00-5-3 and TO 00-5-18, AF Technical Order Numbering System.

8. Data Rights. Government rights in data are specified in the Defense Federal Acquisition Regulation Supplement (DFARS), paragraphs 227-7102 through 227-7104. Offerors shall propose Unlimited Rights for all source data and TOs prepared specifically for the contract.

8.1. If some TOs or source data are copyrighted or contain proprietary data or procedures, offerors may propose Limited Rights or Government Purpose Rights (GPR) only. Proposed commercial manuals should be provided with Unlimited Rights. Copyrights shall be according to DFARS paragraphs 227-7103, 7105 or 7106.

8.2. Specifically, if an NGS is proposed, the government shall be given unlimited rights for all business rules (tailoring and application methods and procedures) and documented business processes developed for use in TO development. Government data rights shall extend to the common source database, transformation style sheets, and other tools or products used to author or display NGS technical data.

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. Offerors shall determine the correct markings and controls for classified and restricted distribution data and TOs IAW the program’s Security Classification Guide (SCG) and DOD 5200.1-R, DODD 5230.24, AFIs 21-303, 31-401 and 61-204, and MIL-STD-38784 (available at http://www.e-publishing.af.mil/ or http://quicksearch.dla.mil/). The markings and notices shall be reviewed during In-Process Reviews (IPR). NOTE: Distribution limitations will be determined on a case-by-case basis as TOs are developed, dependent upon TO content.

10. TO Quality. Offerors shall propose a quality assurance program which ensures TOs are prepared IAW this contract. Recommended QA methods must include actual performance of procedures and use of desk-top analysis for non-procedural data. Simulation (walk-through/talk-through) should be reserved for those procedures which would present a hazard to personnel or equipment. Offerors’ proposals shall describe how the government will be allowed to interact with the contractor’s TO development team.

10.1. Conferences and Technical Reviews. Offerors shall propose sufficient conferences and reviews to allow insight into TO development processes and ensure contract compliance. Offerors should host an initial Guidance Conference or Technical Interchange Meeting (TIM) within 60 days of contract award to ensure mutual understanding of TO contract requirements, schedules, points of contact, etc. Periodic In-Process Reviews (IPRs) and Prepublication Reviews (PPR) ensure TOs are being developed according to contract requirements and that open discrepancies are cleared prior to publication.

http://www.e-publishing.af.mil/

10.2. TO Certification. Offerors shall propose their method for documenting certification that TO procedures are accurate, adequate, current, safe and usable for their intended purposes. Offerors shall notify the government at least 180 days prior of the need for any Government Furnished Information/Government Furnished Equipment (GFI/GFE) required to perform certification tasks.

10.3. Verification Support. Offerors shall propose the methods, equipment and personnel required to support government TO Verification. This support should consist of at least technical support to resolve problems during verification, program-peculiar equipment and supplies, maintenance of TO configuration, incorporation of Government comments, and participation on TO Review Boards (TORBs).

10.4. Technical Data Assessment (TDA – originally called First Article Testing). The program office, with the assistance of AFLCMC/HIAM and the contractor, will determine the TDA requirements for each TO type. The contractor will submit an in-work sample of each type of SGML-tagged TO file to the program office concurrent with the first IPR, for TDA to verify compliance of the digital files to Air Force DSSs. Additional TDAs may be required based on initial results. The TDA parsing in no way relieves the contractor from correcting tagging errors that are noted during the composing effort.

Repeat TDAs shall be required whenever new DSS or DTD versions are used for TO development.

The contractor shall deliver a representative percentage of Indexed Portable Document Format (IPDF) TO files to verify indexing compliance with the Technical Order Conversion Requirements (TOCR).

11. TO and Source Data Maintenance. Offerors shall propose methods for maintaining accuracy, currency and configuration of TOs and source data throughout the contract period of performance.

Maintenance includes preparation of TO and source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes.

12. TO Delivery. Offerors shall propose practices and procedures for secure access to or delivery of digital TO files, including those for Preliminary TOs (PTOs), source data, reproduction masters, and program support data. Practices and procedures shall be compatible with the program’s IDS. TO file delivery formats shall be according to applicable CDRLs and the tailored TM Delivery Requirements Matrices included in Section 2 of this document. Paper TO delivery is not acceptable for final delivery of TOs.

12.1. Indexed Adobe™ Portable Document Format (IPDF) Files. The contractor shall validate indexing of PDF TO files using the specifications contained in the Technical Order Conversion Requirements (TOCR).

13. Schedules. Offerors shall include TO program events and schedules in their proposed Integrated Master Plan (IMP) and Integrated Master Schedule (IMS), and update the IMS throughout the period of performance. NOTE: AF policy requires delivery of verified TOs prior to or concurrently with delivery of operational equipment to the field. This policy will determine TO development and delivery schedules throughout the acquisition phase of a program.

14. Time Compliance Technical Orders (TCTOs). Offerors shall propose practices and procedures to develop AF TCTOs and related TO updates when tasked as part of the approval process for Engineering Change Proposals (ECPs) to configured items. Costs for TCTO package development must be included in ECP Costs – not included as direct proposal costs. NOTE: ECPs are reviewed and approved by the Government’s Configuration Control Board (CCB). When the CCB decides that a TCTO is the appropriate method of implementation, the contractor may be requested to develop the TCTO package for Air Force coordination and approval. See TO 00-5-15, Air Force Time Compliance Technical order Process, for a detailed description of TCTO processes.

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

• Mark the TM Type Selection Tables indicating the applicable TO types and related specifications. For additional interface requirements see the program-specific Government Concept of Operations (GCO).

• All page-based TOs developed under this contract must conform to the general style and format requirements of MIL-

STD-38784; IETMs must conform to S1000D and its business rules.

• Check the ASSIST database, http://quicksearch.dla.mil/, for updated versions of the required TMSS prior to initiating any work on this proposal/contract.

• Manuals delivered using this table and DI-TMSS-80067, CFAE/CFE Notices, must be reviewed and approved by the Air

Force prior to delivery.

• IPBs are developed IAW MIL-PRF-38807, except that MIL-DTL-87929 will also be used for IPBs combined with work packages.

• All checklists, except aircrew and nuclear weapons checklists, are developed IAW MIL-PRF-5096.

• MIL-PRF-83495 requires MIL-HDBK-863 to be levied on engineering data for preparation of end item wiring data and schematic diagrams.

• Delivery requirements are indicated in the TM Delivery Requirements matrices.

PART A – TM TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE AN/FMQ-22 PROGRAM

Title or Type of Manuals Specification Required

1. Inspection TOs MIL-PRF-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. Workcards

e. Inspection Requirements Cards

f. Flow/Sequence Charts

g. Checklists

(1) Maintenance/Operations (Non-Aircrew)

(2) Operations (Aircrew)

2. Cargo Aircraft Loading and Offloading TOs MIL-PRF-5288

a. Manual

b. Checklists

3. Weight and Balance (Aircraft) MIL-PRF-5920

a. Loading Data Manual

b. Sample Basic Weight Checklists

4. Flight Manuals (see notes) MIL-DTL-7700

a. Flight Manual

b. Performance Data Manual

c. Air Refueling Manual

d. Air Refueling Checklist

5. List of Applicable Publications MIL-PRF-8031

6. Structural Repair Manuals (for Aircraft) MIL-PRF-9854

7. Munitions/Weapons Loading Procedures, Non- nuclear and Nuclear MIL-PRF-9977

a. Nuclear Weapons Basic Information and Loading Procedures

b. Nuclear Weapons Loading Procedures

c. Non-nuclear Munitions Basic

d. Non-nuclear Loading Procedures

e. Integrated Combat Turnaround Procedures

f. Non-nuclear Munitions Loading Standard Data Packages (SDPs)

g. Loading Procedures Checklists

h. Integrated Loading Procedures Checklists

i. Nuclear Weapons Loading Procedure Checklists

j. Integrated Combat Turnaround Procedures Checklists

k. NATO Stage B Cross-Servicing Checklists

8. Space Operations and Support Documentation TOs -- Commercial specification (all space systems & missiles) -- MILSPEC (Intercontinental Ballistic Missiles) -- MILSPEC (Space Systems)

ANSI/AIAA-R024-1993

MIL-PRF-38311

MIL-PRF-38314

a. Operations Manual

b. Operations Checklists

c. Technical Manuals and Related Checklists

9. Nuclear and Non-nuclear Weapon Delivery and Aircrew Procedures Manuals and Checklists

MIL-PRF-38384

a. Non-nuclear Weapon Delivery Manual (Strategic Bomber & Tactical Aircraft)

b. Nuclear Bomb Delivery Manual (Strategic Bomber Aircraft)

c. Aircrew Nuclear Weapon Delivery Manual (Strategic Bomber

Aircraft)

d. Aircrew Nuclear Weapon Delivery Manual (Tactical Aircraft)

e. Non-nuclear Weapon Delivery Checklist (Strategic Bomber &

Tactical Aircraft)

f. Nuclear Bomb Delivery Checklist (Strategic Bomber Aircraft)

g. Aircrew Nuclear Weapon Delivery Checklist (Tactical Aircraft)

h. Non-nuclear Weapon Delivery Source Data Packages

10. Work Unit Code Manual MIL-PRF-38769

11. Calibration Procedures MIL-PRF-38793

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

13. Aircraft Battle Damage Assessment and Repair TOs MIL-PRF-87158

14. Illustrated Parts Breakdown MIL-PRF-38807

15. On-Equipment Organizational Maintenance Manual Set (see notes) MIL-PRF-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

16. Operation and Maintenance Instructions in Work Package Format MIL-DTL-87929

a. Maintenance Manuals

(1) Intermediate Maintenance

(2) Depot Maintenance

(3) Combined (I&D) Maintenance

(4) On Condition Maintenance

b. Operation & Maintenance (organizational/field level) Instruction

Manual MIL-PRF-32216A

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-PRF-5096)

e. With Illustrated Parts Breakdown (see notes) MIL-DTL-38807D

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

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

19. Interactive Electronic Technical Manuals (IETM - Contact 754 ELSG/ILMT for guidance.)

ASD-S1000D -

International Specification for Technical Publications Utilizing a Common Source Data Base

TABLE 2

ADDITIONAL TM TYPE SELECTIONS

NOTES:

• Check all applicable boxes.

• For commercial manual supplemental data only, under the specification heading, enter “Same style and format,” “MIL-

PRF-38807” (for IPB data), or “MIL-STD-38784.”

• For existing MIL-SPEC manuals not being updated to latest specification requirements, enter “Same style and format” under the specification heading.

• For manuals proposed to NGS, list the type of manual in the appropriate column and the NGS in the Specification column. Manuals proposed to an approved NGS shall meet the functional requirements of the approved TMSS for the TO type, e.g., OMMS prepared to S1000D shall meet the requirements of MIL-PRF-83495 (which serves as business rules for manual style, format, and content).

TO Number, Title, or

Type of Manual

Specification

Com-mercial Manual

Change/ Revision

Supple-ment

Supple-mental

TM

Source Data

1. 31M1-4-48-2, Operations and Organizational Maintenance Manual with Illustrated Parts Breakdown, AN/FMQ-22

MIL-PRF-

32216A

MIL-DTL-

38807D

2.

3.

4.

5.

PART B - TM DELIVERY REQUIREMENTS

FOR AN/FMQ-22

TM DATA TYPE DELIVERED:

1. OPERATIONS AND ORGANIZATIONAL MAINTENANCE MANUAL WITH ILLUSTRATED PARTS

BREAKDOWN (IPB).

2. TIME COMPLIANT TECHNICAL ORDERS (TCTO)

Delivery Format Requirements Codes Digital delivery only:

P - Paper (draft or manuscript only. Cannot be used for G - Standard Generalized Mark-up Language (SGML).

final delivery) H - Hyper Text Mark-up Language (HTML) M - Mixed paper and digital (G, H or I) I - Indexed Portable Document Format (IPDF) File.

X - Extensible Mark-up Language (XML)

• Delivery format requirements codes indicate the media/file format to be delivered for each program event.

• TCTO requirements are specified in the contract vehicle approving the TCTO.

• When on-line access is a contractual requirement, copy quantity will normally be Ø (zero).

• For NGS or non-standard TMSS instances, delivery shall include the associated DTDs, FOSIs/Style Sheets, XML schemas, etc.

DELIVERY SCHEDULE

Event Number of days data required prior to event Technical Review(s)( 30 Days)

Verification (30 Days)

Prepublication Review(10

Days)

Final TO Distribution(5

Days) Enter Office Symbol and Address Enter delivery requirements code/copy quantities required

AFLCMC/HBAW, Attn: Oscar Seefried 75 Vandenberg Dr, Bldg 1630 Hanscom AFB, MA 01731-2103

I / 1 I / 1 I / 1 I / 1

AFLCMC/HBZBG, Attn: Brenda Lund 6039 Wardleigh Rd, Bldg 1206 Hill AFB, UT 84056-5838

I / 1 I / 1 I / 1 I / 1

AFLCMC/HBZET, Attn: Tim Rotert 6061 Gum Ln, Bldg 1228 Hill AFB, UT 84056-5826

I / 1 I / 1 I / 1 I / 1

AFWA/A5/8, Attn: Todd Allen 101 Nelson Dr Offutt AFB, NE 68113

I / 1 I / 1 I / 1

Total Copies Required: 4 4 4 3

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

• All TMSS applicable to this contract shall have an appropriately tailored SIR attached to this section.

• SIRs included in the untailored TMCR format represent the minimum tailoring requirements that must be included in the final contract, unless the entire SIR is not applicable; e.g., if MIL-DTL-22202D is not required, the entire SIR can be deleted.

• MIL-STD-38784A must be included in all contracts/proposals for AF TMSS-developed TOs.

• Most specification “Acquisition Requirements” list the same two items for paragraphs 6.2a and 6.2b. For this contract enter:

6.2a. The title, number and date of each specification will be listed in the heading of the applicable SIR.

6.2b. The issue of the DODISS used in this contract is (enter date).

• Digital requirements shall not be tailored out. Tailoring shall be limited to the options expressed in paragraphs

6.2. Any requests for tailoring outside of these requirements must be coordinated with the specification Preparing Activity (PA) 754 ELSG/ILMT.

• Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available from the DoD Single Stock Point (DODSSP), Acquisition Streamlining and Standardization Information System (ASSIST) web page, http://quicksearch.dla.mil/.

• Non-government Standards (NGS) shall be provided by the offeror. The Government will not be responsible for providing NGS.

• TMSS entries designated with A, F, M or N refer to Army, Air Force, Marine Corps or Navy requirements.

• Beneficial comments, recommendations, additions, data etc. which may be of use in improving any Air Force TMSS should be addressed to “Air Force Technical Manual Specifications and Standards Office, 754 ELSG/ILMT, Wright- Patterson AFB, OH 45433”. Do not include the street address, a building number, or a zip+4.

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-STD-38784A, 25 August 2011

Standard Practice for Manuals, Technical: General Style and Format Requirements

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-DTL-38804D, 24 May 2012

Time Compliance Technical Orders – Preparation

Form Approved OMB No. 0704-0188

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 Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contractor Officer for the Contract/PR No. Listed in Block E.

A. CONTRACT LINE ITEM NO.

0006, 1006, 2006, 3006, 4006, 5006

B. EXHIBIT

B

C. CATEGORY:

TOP _____________ TM- _____________ OTHER PM

D. SYSTEM / ITEM:

AN/FMQ-22

E. CONTRACT / PR NO.

TBD

F. CONTRACTOR

TBD

1. DATA ITEM NO.

B002

2. TITLE OF DATA ITEM

Program Protection Implementation Plan

3. SUBTITLE

PPIP

4. AUTHORITY (Data Acquisition Document No.) DI-ADMN-81306

5. CONTRACT REFERENCE

PWS Para 4.1

6. REQUIRING OFFICER

9. DIST

STATEMENT

12. DATE OF FIRST

14. DISTRIBUTION

DS SEE BLOCK 16 SEE BLOCK 16 b. COPIES

8. APP CODE C 11. AS OF DATE 13. DATE OF SUBSEQUENT

A SEE BLOCK 16 SEE BLOCK 16 Reg Repro

16. REMARKS

SEE BLOCK 16

Block 9: Distribution Statement C: Distribution authorized to U.S. Government Agencies and their contractors (Administrative or Operational Use) (July 2014).

Other requests shall be referred to AFLCMC/HBAW, 75 Vandenberg Drive, Bldg.

1630, Hanscom AFB, MA 01731. Destruction Notice: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Blocks 10, 11, 12, & 13: Initial submitted due NLT thirty (30) calendar days after contract award. The Government will review and provide comments NLT ten (10) calendar days. The Contractor will incorporate Government comments and resubmit NLT seven (7) calendar days. Subsequent submittals due as required by changes to the Program Protection Plan (PPP).

Block 14: Initial and subsequent submittals (to include all revisions) shall be provided electronically via email to: (See CDRL Points Of Contact (POC) and Distribution Requirements List).

The data should be in a format compatible with Microsoft Office 2000 or later, Microsoft Project 2000 or later, as applicable.

Bill Drury, GS-12, Configuration/Data Manager

H. DATE

30 July 14

I. APPROVED BY

Jeff Green, GS-12, AN/FMQ-22 Program Manager

J. DATE

DD Form 1423–1, JUN 90 Previous editions are obsolete Page __1__ of __1__ Pages .

Form Approved OMB No. 0704-0188

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 Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contractor Officer for the Contract/PR No. Listed in Block E.

A. CONTRACT LINE ITEM NO.

0006, 1006, 2006, 3006, 4006, 5006

B. EXHIBIT

B

C. CATEGORY:

TOP _____________ TM- _____________ OTHER IA

D. SYSTEM / ITEM

AN/FMQ-22

E. CONTRACT / PR NO.

TBD

F. CONTRACTOR

TBD

1. DATA ITEM NO.

B003

2. TITLE OF DATA ITEM

Scientific and Technical Reports

Comprehensive DIACAP Package

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80711A/T

5. CONTRACT REFERENCE

PWS PARAs 5.2, 5.3.3, 5.35, & 5.3.6

6. REQUIRING OFFICER

. DIST STATEMENT

SEE BLOCK 16 b. COPIES

8. APP CODE

A

C 11. AS OF DATE

SEE BLOCK

3. DATE OF SUBSEQUENT

SEE BLOCK 16 Reg Repro

16. REMARKS SEE BLOCK 16

Block 4: DD Form 1664 Block 10 is tailored as follows: Delete Paragraphs 10.1 through 10.3 and replace with the following: “Use content and format defined in the following documents: DoDD 8500.01E, DoDI 8500.2, AFI 33-210, DoDI 8510.01.

Contractor is to prepare a Comprehensive DIACAP Package consisting of the following documents as a minimum: System Identification Profile (SIP), DIACAP Scorecard & Implementation Plan; System Security Plan (SSP); Ports, Protocols and Services (PPS); Topology Diagram. Additional “artifact” documents may be required to address ongoing C&A concerns or documentation. The data should be in a format compatible with Microsoft Office 2010, Microsoft Excel 2010 or Microsoft Visio 2010, as applicable.

Block 9: Distribution authorized to Department U.S. Government Agencies and their contractors (Administrative or Operational Use) (July 2014). Other requests shall be referred to AFLCMC/HBAW, 75 Vandenberg Drive, Building 1630, Hanscom AFB, MA. Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

BLOCKS 10, 11, 12 & 13:

System Identification Profile (SIP)

1st submission is due NLT seven (7) calendar days after contact award.

Government will review and provide comments NLT seven (7) calendar days.

Finals submission is due NLT seven (7) calendar days after receipt of Government comments.

As required, the contractor shall provide updates to the documents if the system is going through a full (ATO) effort.

SIP will be sent for review 30 calendar days prior to the official submission to AFNIC and/or the PIT Office. The Government will review and provide comments NLT seven (7) calendar days. The final submission is due NLT seven (7) calendar days after receipt of Government comments. The SIP be finalized with a caveat that any changes suggested by AFNIC and/or the PIT Office will be incorporated into the SIP.

For the No Significant Impact process (NSI)/CCB, the SIP will need to be updated with any new findings and changes until NSI approval.

DIACAP Implementation Plan (DIP):

1st Submission is due NLT fourteen (14) calendar days after contact award.

Government will review and provide comments NLT fourteen (14) calendar days

Bill Drury, GS-12, Configuration/Data Manager

H. DATE

30 Jul 14

I. APPROVED BY

Jeff Green, GS-12, AN/FMQ-22 Program Manager

J. DATE

30 Jul 14

DD Form 1423–1, JUN 90 Previous editions are obsolete Page __1__ of __3__ Pages .

Form Approved OMB No. 0704-0188

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 Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contractor Officer for the Contract/PR No. Listed in Block E.

A. CONTRACT LINE ITEM NO.

0006, 1006, 2006, 3006, 4006, 5006

B. EXHIBIT

B

C. CATEGORY:

TOP _____________ TM- _____________ OTHER IA

D. SYSTEM / ITEM:

AN/FMQ-22

E. CONTRACT / PR NO.

TBD

F. CONTRACTOR

TBD

1. DATA ITEM NO.

B003

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80711A/T

5. CONTRACT REFERENCE

PWS PARAs 5.2, 5.3.3, 5.35, & 5.3.6

6. REQUIRING OFFICER

SEE BLOCK 16 b. COPIES

8. APP CODE C 11. AS OF DATE

SEE BLOCK

16. REMARKS SEE BLOCK 16

2nd submission is due NLT seven (7) calendar days after receipt of Government comments. Government will review and provide comments NLT seven (7) calendar days.

3rd submission is due NLT seven (7) calendar days after receipt of Government comments. Government will review and provide comments NLT seven (7) calendar days.

Final submission is due NLT seven (7) calendar days after receipt of Government comments.

As required, the contractor shall provide updates to the DIP if the system is going through a full DIACAP (ATO) effort. DIP will be sent for review 30 calendar days prior to the official submission to AFNIC and/or the PIT Office. The Government will review and provide comments NLT seven (7) calendar days. The final submission is due NLT seven (7) calendar days after receipt of Government comments. The DIP be finalized with a caveat that any changes suggested by AFNIC and/or the PIT Office will be incorporated into the DIP.

For the No Significant Impact process (NSI)/CCB, the DIP will need to be updated with any new findings and changes until NSI approval.

Ports, Protocols and Service (PPS) and Topology:

1st submission is due NLT thirty (30) calendar days after contract award.

Government will review and provide comments NLT fourteen (14) calendar days.

The 2nd submission is due NLT fourteen (14) calendar days after receipt of Government comments. Government will review a provide comments NLT fourteen

(14) calendar days. The 3rd submission is due NLT fourteen (14) calendar days after receipt of Government comments. Finals submission is due NLT seven (7) calendar days after receipt of Government comments.

As required, the contractor shall provide updates to the PPS if the system is going through a full DIACAP (ATO) effort. PPS will be sent for review 30 calendar days prior to the official submission to AFNIC. The Government will review and provide comments NLT seven (7) calendar days. The final submission is due NLT seven

(7) calendar days after receipt of Government comments. The PPS be finalized with a caveat that any changes suggested by AFNIC and/or the C2 PIT Office will be incorporated into the PPS.

For the No Significant Impact process (NSI)/CCB, the PPS and Topology will need to be updated with any new findings and changes until NSI approval.

[ SEE CONTINUATION SHEET ]

Bill Drury, GS-12, Configuration/Data Manager

H. DATE

30 Jul 14

I. APPROVED BY

Jeff Green, GS-12, AN/FMQ-22 Program Manager

J. DATE

30 Jul 14

DD Form 1423–1, JUN 90 Previous editions are obsolete Page __2_ of __3__ Pages .

Form Approved OMB No. 0704-0188

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 Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503.