Exhibit E - Data Requirements List for TM86-01 20120223 v36.pdf

EXHIBIT E ~ Page 1 of 17 Pages

EXHIBIT E

CONTRACT DATA REQUIREMENTS LIST

For

FAMILY OF ADVANCED BEYOND-LINE-OF SIGHT TERMINAL

(FAB-T)

TECHNICAL MANAUALS

RFP FA8307-12-R-0003

23 February 2012

HQ ELECTRONIC SYSTEMS CENTER

AIR FORCE MATERIEL COMMAND (AFMC)

ELECTRONIC SYSTEMS CENTER (ESC)

FAMILY OF ADVANCED BEYOND-THE-LINE-OF-SIGHT TERMINALS (FAB-T) (ESC/HNT)

CONFIGURATION AND DATA MANAGEMENT

5 EGLIN STREET, HANSCOM AFB, MA 01731-1620

EXHIBIT E ~ Page 2 of 17 Pages

CDRL

SEQ NO.

TITLE/SUBTITLE DID #

E001 Air Force Technical Manual Contract Requirement TM86-01N/T

EXHIBIT E ~ Page 3 of 17 Pages

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.

B. EXHIBIT

E

C. CATEGORY:

TDP _____________ TM- ____X_______ OTHER _________

D. SYSTEM / ITEM

FAB-T Alternate Source

E. CONTRACT / PR NO.

FA8307-12-R-0003

F. CONTRACTOR

TO BE DETERMINED

1. DATA ITEM NO.

E001

2. TITLE OF DATA ITEM

Air Force Technical Manual Contract Requirement

3. SUBTITLE

See Block 16

4. AUTHORITY. (Data Acquisition Document No.)

TM86-01N/T

5. CONTRACT REFERENCE

SOW PARA 3.6.4

6. REQUIRING OFFICER

ESC/HNT (FAB-T ALTERNATE SOURCE)

7. DD 250 REQ.

SD

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

12. DATE OF FIRST SUBMISSION

14. DISTRIBUTION

ASREQ See Block 16 b. COPIES

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

SUBMISSION

a. ADDRESSEE

Draft

Final

A See Block 16 Reg Electronic

16. REMARKS See Block 16 *:

Block 3: FAB-T Organizational and Depot Level Technical

Documentation/Data - - FAB-T Technical Documentation Planning, Management, Development, Delivery, Configuration Maintenance, and Updates include the following Class 2 Operation and Depot Maintenance IETM Technical Orders, and Engineering Technical Data:

Block 4 Tailored Air Force TMCR TM-86-01N/T attached.

- All technical manuals shall be at the 60% to support the Flight Test Operational Assessment and M-DEMO

- Validated Technical Manuals shall be delivered 6 months prior to

IOT&E

- Technical Manuals corrections found during verification shall be fixed and delivered 60 days prior to IOT&E

Block 7: “S”—Inspection is at source and is to ensure this product meets this CDRL and its tasking document. Shipping list must accurately reflect the shipped product.

“D”—Acceptance is at destination. Acceptance of final data will be by approval of the Engineering Data Management Specialists.

Block 9: DISTRIBUTION STATEMENT D: Distribution authorized to DoD and US DoD contractors that support the MILSTAR and AEHF programs, due to the sensitive information (as defined in DoD 5200.1-R) associated with the MILSTAR and AEHF programs as determined in the MILSTAR/Advanced Extremely High Frequency (AEHF) Security Classification/Declassification Guide, dated 14 August 2009. Other requests for this document shall be referred to HQ AFSPC/A3M and SMC/CC through SMC/OMP.

Blocks 10, 12 &13: All data in Block 1 and Block 2 is due no later than noon East Coast Time: Data will be delivered IAW TM-86-01N/T.

Revisions as required.

Blocks 14 & 15: * All Data shall be submitted IAW Part 2 CDRL

Preparation Instructions, General Instructions and CDRL Address List (on CDRL Address List page) of the CDRL package.

ESC.HNT.DATA 1

ESC/HNTK L/T

OO-ALC/GHSO 1

AFSPC/A4SM

SMC/MCL 1

15. TOTAL See 16

17 PRICE GROUP 18 ESTIMATED TOTAL PRICE

G. PREPARED BY.

Donna Jansky, Data Mgr, ESC/HNT

H. DATE

23 Feb 12

I. APPROVED BY.

Douglas Dalessio, Program Manager, ESC/HNT

J. DATE

23 Feb 12

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

EXHIBIT E ~ Page 4 of 17 Pages

Air Force Technical Manual Contract Requirements (TMCR) for

FAB-T Organizational Level Operation & Maintenance Manual (including IPB) IETM

Class 2 Documentation

ATTACHMENT 1 TO CDRL SEQUENCE NUMBER E001 EXHIBIT E

REQUEST FOR PROPOSAL/CONTRACT: FA8307-12-R-0003

Date: 9 January 2012

Technical Manual/Technical Order requirements contained herein have been cleared for use by OMB Paperwork Reduction

Project No. 0704-0188.

The TMCR must be referenced in RFP section J. If some or all of the TO program requirements are included in RFP Section L

(Instructions to Offeror), remove them from the TMCR. URLs are either public access sites, or are on the Air Force Portal – contractors may access the Portal using an External Certificate Authority (ECA) when sponsored by a DoD activity. Delete this note prior to placing the TMCR in the RFP.

Section 1. Technical Order (TO) Program Requirements

1. TMCR Tailoring. Offeror 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 SOW. Proposals shall be compatible with the Air Force infrastructure and support the

Family of Beyond Line-of-Sight Terminals (FAB-T) Program’s Continuous Acquisition and Logistics support (CALS) implementation strategy. (enter RFP location of IDS). Air Force TO Acquisition procedures, including procedures for tailoring this document, are found in TO 00-5-3, AF Technical Order Life Cycle management, located on the Internet at http://www.toindex-s.wpafb.af.mil 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 FAB-T program’s objectives Page-oriented Military Specification (MILSPEC) TOs must be formatted with text, graphics and delivery according to MIL-STD-38784 and applicable performance or detail (MIL-PRF or MIL-DTL) specifications. The Offeror may propose use of Non-Government

Specifications or Standards (NGS) for development of TOs, but must justify this choice based on life-cycle cost savings to the government and compatibility with existing systems identified in the System Support Plan.

3. Commercial Manuals. Offeror 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. Commercial manuals will be reviewed and approved IAW MIL-PRF-32216 and are procured with “unlimited” rights to reproduce IAW DFARS 252.227-7013(a)(15).

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://dodssp.daps.dla.mil/assist.htm), 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, and MIL-DTL-7700, Detail Specification: Flight Manuals, Air Refueling Procedures, And Abbreviated Checklists, as an additional guide for commercial Flight Manual contents.

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. Offeror 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) and to Lisa Cummings,OO-ALC/GHSO at http://www.toindex-s.wpafb.af.mil/ http://www.toindex-s.wpafb.af.mil/ http://dodssp.daps.dla.mil/assist.htm

EXHIBIT E ~ Page 5 of 17 Pages lisa.cummings@hill.af.mil , OO-ALC, Ogden, UT. 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. Offeror shall propose a process for notifying the government when additional TO or source data requirements are identified subsequent to contract award. This 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) (on the AF Portal at https://techdata.wpafb.af.mil/toprac/polinfo.htm) 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.

6.1. Page-oriented Military Specification (MILSPEC) TOs shall be formatted with text, graphics and delivery according to the TMSS specified in Section 2. The contractor shall develop TO files (tagged instances) using

Standard Generalized Markup Language (SGML) according to the DTDs referenced in the appendix to MIL-STD-

38784 and each applicable military detail or performance specification (MIL-DTL or MIL-PRF).

6.2. SGML-tagged TO files shall include required illustration (graphics) files in an approved graphics exchange format (select “Guidelines” and “Graphics” on the Technical Manual Specifications and Standards (TMSS) web page

(https://techdata.wpafb.af.mil/tmss/index.html, or contact the 754 ILMT via e-mail at SGMLSupport@wpafb.af.mil).

NOTE: Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible.

6.3. The Offeror may propose use of other Non-Government Standards (NGS) for development of TOs, but must justify this choice based on life-cycle cost savings to the government and compatibility with existing systems identified in the IDS and the System Support Plan.

6.4. The contractor shall contact 754 ELSG/ILMT for pre-approval before modifying or developing any new DTDs to support use of NGS, canceled TMSS, or undeveloped TMSS DTDs. If permission is granted, the Offeror must submit any proposed DTDs through the PCO and TO Manager to 754 ELSG/ILMT for validation of TMSS compatibility with approved electronic TO (eTO) viewing solutions. New DTDs shall not be developed in lieu of existing DTDs, including those for legacy TMSS. Rules shall be so constructed that TO output complies with the functional requirements of the associated TMSS, and shall be documented in a SIR. DTDs and rule sets submitted and approved in execution of the contract shall become the property of the Government. Direct questions about the application of SGML tagging to digital TO files to 754 ELSG/ILMT (SGMLSupport@wpafb.af.mil).

7. TO Numbering. Offeror 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, (available at https://www.my.af.mil/etims/ETIMS/index.jsp)

8. Data Rights. Government rights in data are specified in the Defense Federal Acquisition Regulation Supplement

(DFARS), paragraphs 227-7102 through 227-7104. Offeror 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, Offeror may propose

Limited Rights or Government Purpose Rights (GPR) only. Proposed commercial manuals should be provided with at least GPR or Limited 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.

mailto:lisa.cummings@hill.af.mil

EXHIBIT E ~ Page 6 of 17 Pages

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. Offeror 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://dodssp.daps.dla.mil/assist.htm). 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. Technical Documentation/data Quality. Offeror shall propose a quality assurance program which ensures TOs prepared are: a) 100% technically accurate; b) 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; c) compatible with JCALS and ETIMS; and d) properly classified and marked with export control and distribution limitation statements. Recommended QA methods 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 activate explosive devices or present a hazard to personnel or equipment. Offeror's proposal should describe how the government will be allowed to interact with the contractor’s TO development team. 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 and DOD Directive 5160.62, respectively. The government performance-tests all JNWPS and

EOD TOs.

10.1. Conferences and Technical Reviews. Offeror shall propose sufficient conferences and reviews to allow insight into TO development processes and ensure contract compliance. Offeror 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) (30%, 60%, and 90%

IPRs) and Prepublication Reviews (PPR) ensure TOs are being developed according to contract requirements and that open discrepancies are cleared prior to publication. For eTO based programs, IPRs subsequent to the initial review need to be accomplished using the approved viewing presentation system. NOTE: PPRs are required for critical safety and nuclear surety procedures TOs, and may be required for other complex procedures TOs.

10.2. TO Certification. Offeror shall propose their method for documenting certification that TO procedures are accurate, adequate, current, safe and usable for their intended purposes. Offeror 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. Offeror shall propose the methods, equipment and personnel required to support government TO Verification. This support should consist of at least an Air Force Operator/User/Representative, a desktop or on-equipment procedural checkout for val/ver, with Prime Contractor and/or subcontractors present and supporting/assisting the TO verification. Offeror shall propose methods and procedures for maintaining TO configuration, incorporation of Government comments and participation in TO review boards.

10.4. Technical Data Assessment (TDA – originally called First Article Testing). The program office, with the assistance of 754 ELSG/ILMT 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) (on the AF Portal at https://techdata.wpafb.af.mil/toprac/working.htm).

11. TO and Source Data Maintenance. Offeror 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. Offeror 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. TO file http://www.e-publishing.af.mil/

EXHIBIT E ~ Page 7 of 17 Pages 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. EXCEPTION: Commercial manuals should be in PDF format with government rights to reproduce...

12.1. SGML-Tagged Files. The contractor shall parse and compose SGML-tagged TO document files prior to delivery to the government, and verify that content tagging has been accomplished to the levels provided in the DTD.

NOTE: The government will parse the files prior to acceptance using the public domain “SGMLS Parser”

(ftp://ftp.jclark.com/pub/SGMLS).

13. Schedules. Offeror 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 (AFI 21-303, Technical Orders). This policy will determine TO development and delivery schedules throughout the acquisition phase of a program.

14. Time Compliance Technical Orders (TCTOs). Offeror 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, (available ahttps://www.my.af.mil/etims/ETIMS/index.jsp AFMCI 21-

302 and AFMCMAN 21-1 for a detailed description of the TCTO system available at http://www.e-publishing.af.mil/ or http://dodssp.daps.dla.mil/assist.htm) for a detailed description of TCTO processes.

ftp://ftp.jclark.com/pub/SGMLS https://www.my.af.mil/etims/ETIMS/index.jsp http://www.e-publishing.af.mil/

EXHIBIT E ~ Page 8 of 17 Pages

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.

Check the ASSIST database, http://dodssp.daps.dla.mil/assist.htm, 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.

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.

For further information on the Air Force Vision and TO Concept of Operations (CONOPS), see AF Portal URL https://techdata.wpafb.af.mil/toprac/polinfo.htm.

PART A – TM TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE FAB-T Program

(System/Component)

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

EXHIBIT E ~ Page 9 of 17 Pages

TMSS REQUIREMENTS FOR THE FAB-T Program

(System/Component)

Title or Type of Manuals Specification Required

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

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

EXHIBIT E ~ Page 10 of 17 Pages

TMSS REQUIREMENTS FOR THE FAB-T Program

(System/Component)

Title or Type of Manuals Specification Required

16. Operation and Maintenance Instructions MIL-PRF-38807

a. Maintenance Manuals

(1) Intermediate Maintenance

(2) Depot Maintenance

(3) Combined (I&D) Maintenance

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

e. With Illustrated Parts Breakdown (see notes)

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

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

EXHIBIT E ~ Page 11 of 17 Pages

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.

TO Number, Title, or

Type of Manual

Specification

Com-mercial

Manual

Change/

Revision

Supple-ment

Supple-mental

TM

Source

Data

1. TO FAB-T Operation &

Maintenance Manual (O-

Level (IETM Class 2) including Illustrated Parts

Breakdown (prime contractor)

38784 (current rev)

2. TO FAB-T Data Set

Manager (DSM) Operation &

Maintenance Manual including Illustrated Parts

Breakdown (O-Level

(IETM Class (2)

38784 (current rev)

3. Work Unit Code Manual (O-level and depot level IETM class 2)

4. Inspection and Maintenance

Requirement Manual (O-level and depot level IETM class 2)

5.

6.

7.

8.

9.

10.

11.

12.

13.

14.

15.

EXHIBIT E ~ Page 12 of 17 Pages

PART B - TM DELIVERY REQUIREMENTS

FOR FAB-T

(System/Item)

TM DATA TYPE DELIVERED TMSS .

(TMSS/Change/Supplement/etc.)

(Replicate form for each TM type required.)

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)

EXAMPLE: M(G) / 2 [Paper and SGML / 2 copies]

NOTES:

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

Reviews

30%, 60%, 90%

Verification

(30 Days)

Prepublication

Review

(30Days)

Final TO

Distribution

(30 Days)

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

OO-ALC/84 CBSG/XT

OO-ALC/GHSO

6021 Gum Lane/Bldg 1228

Hill AFB, UT 84056-5826

G/I/1

AFSPC/A4SM

150 Vandenburg St. Suite 1105

Peterson, AFB, CO 80914-4370

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

SMC/MCL

1050 East Stewart Avenue, Building 2025

Peterson AFB, CO 80914-4370

M/I/1

ESC/HNT

5 Eglin St.

Hanscom, AFB, MA. 01731

Total Copies Required: 4 4 4 4

EXHIBIT E ~ Page 13 of 17 Pages

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.

MIL-STD-38784 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. For this contract enter:

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

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://www.dodssp.daps.dla.mil/assist.htm.

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

DOD 5200.1-R DoD Information Security Program Regulation

DOD 5220.22-M National Industrial Security Program Operating Manual

4. Replace with: “4. VERIFICATION.

“All cross-servicing guides shall meet the requirements of sections 3 and 5 of this specification, as required by the acquiring activity. The requirements set forth in this specification shall become a part of the contractor’s overall inspection system or quality program. The absence of any requirements in this specification shall not relieve the contractor of the responsibility of ensuring that all products or supplies submitted to the government for acceptance comply with all requirements of the contract. Use of sampling inspections shall be at the discretion of the contractor, and in accordance with commercially acceptable quality assurance procedures.

However, use of sampling in QA procedures does not authorize submission of known defective material, either indicated or actual, nor does it commit the government to accept defective material.”

http://www.dodssp.daps.dla.mil/assist.htm

EXHIBIT E ~ Page 14 of 17 Pages

5. Replace with: “5. PACKAGING.

“5.1 Packaging Requirements. For acquisition purposes, the packaging requirements shall be as specified in the contract or order. When the actual packaging of material is to be performed by DoD personnel, these personnel need to contact the responsible packaging activity to determine packaging requirements. Packaging requirements are maintained by the Inventory Control Point’s packaging activity within the Military

Department’s System Command. Packaging data retrieval is available from the Military Department’s or

Defense Agency’s automated packaging files, CD-ROM products, or the responsible packaging activity.

“5.1.1 Encoded Computer Products. Packaging of encoded computer products for delivery shall be in accordance with the requirements of MIL-STD-1840.

“5.1.2 Classified Material. Classified material shall be packaged and identified in accordance with DOD

5200.1-R, 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 MIL-STD-38784, 2 July 1995

Notice 1, 15 November 2000

Notice 2, 1 December 2000

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

Global: Change references to “MIL-STD-1806” to read “DODD 5230.24.”

3.2.8 Continuous Tone Artwork. Delete paragraph.

3.2.9 Copy Freeze Date. Delete paragraph.

3.2.10 Cutline. Delete paragraph.

3.2.20 Layout Page. Delete paragraph.

4.2.1.2.1 Oversize Reproducible Copy. Delete paragraph.

4.2.7.1 Table Cutline (see 3.2.10). Delete paragraph.

4.2.8.1 Illustration Cutline (see 3.2.10). Delete paragraph.

4.2.8.3 Amend as follows: “4.2.8.3 Illustration legends (see 3.2.23). Legends shall be headed by the word “Legend” followed by the number of the figure to which it is applicable (see Figure 6). The entire legend shall be indented 5 spaces. If the legend is continued, the figure number and title shall be repeated, followed by a dash and the word

“Continued.” Only that information which is necessary to clearly identify the items shall be included in the legend.

Where methods such as the tabular presentation technique (as in an Illustrated Parts Breakdown/Repair Parts and

Special Tools List) are used, no legends are required.”

NOTE: The <figtable> element, if included in the DTD, shall not be used in maintenance manuals.

* 4.5.1.10 Disclosure Notice. Change 1 st sentence to read: “…except those with Distribution Statement A, IAW AFI 21-303

(F):”

* 4.5.1.11 Distribution Statement. Replace the last sentence with: “Include both the distribution statement letter (“A,” “B,” etc.) and wording from DODD 5230.24. Include the “Reason,” “Controlling DoD office,” and “Date of

Determination” when required. If the reason is “Proprietary Data,” then each TM page containing proprietary data must be marked with the company name and the word “Proprietary” (e.g., “Boeing Proprietary”).”

4.5.1.13 Destruction Notice. Change the existing sentence to read: "...or X shall be marked with Handling and Destruction

Notice "a" (below) on the cover/title..." Add a new second sentence as follows: "Unclassified TOs authorized for

Public Release (Distribution Statement "A") shall be marked with disposition notice "b" (below) on the title or T-2 page."

4.5.1.13.a. Designate existing paragraph as "a. HANDLING AND DESTRUCTION NOTICE..." Add:

"See TO 00-5-1 for specific destruction procedures."

4.5.1.13.b (Added) b. “DISPOSITION NOTICE - Refer to TO 00-5-1 for disposition instructions.”

EXHIBIT E ~ Page 15 of 17 Pages

* 4.5.1.14 Copyright Credit Line. Add “If a copyright credit line is required, include a statement of government rights to publish, reproduce, and distribute the TM.”

4.5.3 List of Effective Pages. Change the first sentence to read: “A List of Effective Pages shall be prepared in accordance with Figure 13. Page borders shall be optional.”

4.6.2 Photographs/line drawings. Delete paragraph.

4.6.3.1 Retouching. Delete paragraph.

4.6.3.2 Prescreened photographs. Delete paragraph.

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

4.6.5 Combination Artwork. Delete paragraph.

4.6.12 Color in Illustrations. Delete the first sentence: “Unless otherwise specified (see 6.2), color shall not be used.”

4.6.12.1 Separation of Colors. Delete paragraph.

4.6.12.2 Register Marks. Delete paragraph.

4.6.20 Crop and Size Marks. Delete.

4.6.21 Mounting of Artwork. Delete paragraph.

4.6.22 Identifying Artwork. Delete paragraph.

4.6.23 Covering of Artwork. Delete paragraph.

4.6.24 Review of Illustrations. Delete paragraph.

4.7.1 Advanced Change Pages. Delete paragraph.

4.7.2 Changes to Cover and Title Page. In the first sentence, delete the phrase “Except for silk screened or otherwise expensive covers”.

4.7.3.4 Transmittal Cover Sheets. In the last sentence, delete the phrase “i.e. reproducible copy, negatives, magnetic tape, disk, etc.”.

4.7.3.5 Changes to Illustrations. Delete paragraph.

4.9.2 Safety Supplements (see Figure 37). Change first sentence to read: Safety supplement “SS” borders and the words

“SAFETY SUPPLEMENT” at the top and bottom of the supplement shall be in red. Other text, lettering, numbering, etc, shall be in black.”

Figure 5, Example Typical RDC Page. Delete.

Figure 25 Cropping and Sizing of Illustrations. Delete.

Figure 26, Identification, Marking, and Protective Covering of Artwork. Delete.

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-PRF-38804C, 1 March 1996

Amendment 1, 20 June 1997

Time Compliance Technical Orders – Preparation

NOTE: Entries marked with an asterisk (*) will have to be manually entered and tagged in SGML files until the specification and its associated DTD and FOSI have been updated to incorporate the changes. The rescission date and statement will continue to appear in paragraph 3 of SGML-tagged TCTO files until the

DTD and FOSI are updated.

Amendment 1 Delete entirely.

2.2.2 Change “AFM 67-1” to “AFMAN 23-110.”

3.5.2g Add new line: “g. Rescission Date (see 3.5.2.6.1)” Renumber following paragraphs to “h” through “l”.

3.5.2.4 Change 1

st sentence to read: “…supplement thereto (see 3.6) provided by the acquiring activity on an AFMC Form 873

(see 6.5).”

3.5.2.5 Change 1

st sentence to read: “…acquiring activity on an AFMC Form 873 (see 6.5).”

3.5.2.6 Change 1

st sentence to read: “…acquiring activity on an AFMC Form 873 (see 6.5).” Change last sentence to read: :

“The year, month, and day shall be in the YYYYMMDD format (see Figures 1 through 6).”

EXHIBIT E ~ Page 16 of 17 Pages

3.5.2.6.1 (Added) “Rescission Date. The contractor shall enter the TCTO rescission date in the upper right corner of the first page immediately below the TCTO issue date. The rescission date will be specified on the AFMC Form

873 (see 6.5). The date will be in the YYYYMMDD format.”

3.5.2.8 Add to the end of the paragraph: “See TO 00-5-15 for additional guidance.”

3.5.2.9.1d Change to read: “…reinstating and establishing a new rescission date for rescinded TO…”

3.5.2.9.4 Change “AFMC/AFCC” to “AFMC/AFCA/AFSPC”

3.5.3.3 Change “proofing” to “verification” (4 places)Change last sentence to read: “…waived, the office symbol, e-mail address and Defense Switched Network (DSN) phone number of the approving official shall…”

3.5.5.3 Replace “a” through “d” with the following:

a. (Added) Routine Safety Inspection Organizational/Intermediate Level TCTOs. “Not later than (#) days after receipt of this TCTO. Affected system/equipment shall be removed from service if this TCTO is not accomplished within the specified number of days, or 60 days prior to the TCTO rescission date, whichever comes first. The specified number of days for accomplishment shall be provided on the AFMC Form 873 (see 6.5).

b. Routine Action, Organizational/Intermediate Level, Safety TCTO. "Not later than ____ days after receipt of (this

TCTO) (kits) (parts) (special tools). Failure to accomplish this TCTO by the preceding specified number of days, or

60 days prior to the TCTO rescission date, whichever comes first, shall automatically restrict operations or shall be justification for withdrawing affected system/equipment from service until compliance is accomplished. The specified number of days for accomplishment shall be provided on an AFMC Form 873 (see 6.5).

c. Routine Action, Organizational/Intermediate Level TCTO. Organizational/Intermediate level TCTOs having a compliance period in terms of days shall read: "Not later than ____ days after receipt of (this TCTO) (kits) (parts)

(special tools). Failure to accomplish the work by expiration of the compliance period, or 60 days prior to the TCTO rescission date, whichever comes first, shall be justification for withdrawing the affected system/equipment from service until compliance is accomplished. The specified number of days and requirements for accomplishment shall be provided on an AFMC Form 873 (see 6.5).

d. Routine Action, Organizational/Intermediate Level, Based Upon Maintenance Practice. When the time period for accomplishment cannot be specified as a certain number of days after receipt of the TCTO, kits, parts or special tools, the TCTO may specify compliance at the time a known maintenance event occurs, such as "At the time of removal from Emergency War Order (EWO) status (or During scheduled modernization action). If not complied with by

(date), or 60 days prior to the TCTO rescission date, whichever comes first, the system/equipment shall be removed from active service until compliance with the TCTO is accomplished. The preceding phrase is an example of the type to be used and may be expanded or worded to the individual requirement as needed. Use of the phrases "upon failure," "upon accumulation" or "when reaching" are not authorized for any TCTO. The required statement shall be provided on an AFMC Form 873 (see 6.5).

e. Routine Action, Depot Level. These modifications require specified accomplishment at a time designated by the acquiring activity by means of the AFMC Form 873 (see 6.5) at overhaul, contractor team, force modernization, AFMC schedule or whatever other phrase that is most appropriate.

3.5.5.4 Add new sentence as follows: “The required statements shall be provided on an AFMC Form 873 (see 6.5).”

3.5.5.5 (Added in Amendment 1) Delete.

3.5.7.1.1.1 Change 4th and 5th lines to read: “…concept waived by (insert name/rank/office symbol/DSN phone number and e-mail address of the Lead Command POC authorizing a waiver of the complete…”

3.5.7.2 Change “proofing” to “verification” (2 places)

3.5.7.2.1 (Added) “For Inspection TCTOs, the AFSCs and manhours shall be based on Maintenance Data Collection (MDC) records. The equivalent work phases will be:

a. Equipment preparation.

b. Access work area.

c. Perform inspection.

d. Close work area.

e. Operational check and documentation.”

EXHIBIT E ~ Page 17 of 17 Pages

3.5.7.2.1 (Existing) Renumber as 3.5.7.2.2.

3.5.10.1.4 Change last line to read “...with the criteria established in AFI 21-103, Chapter 9 (-21 TOs).

3.5.11.1 Change 1

st sentence to read: “…the name, organization and office symbol, DSN telephone number, and e-mail address of the POC responsible…”

Change 2 nd sentence to read: “…and the information for the POC authorizing…”

3.6 Delete the last sentence (“All supplements shall be assigned a new data code number.”)

3.6.1 Change 1

st sentence to read: “…supplement, or it explicitly changes the TCTO rescission date.”

3.6.6 Delete “, IF APPROVED BY THE MAJCOM,” in the NOTE text.

4.1 Change title to “Contractor Prototyping.”

4.1b Change to read: “…perform the prototyping functions specified…”

4.1d Change to read: “…review any of the prototyping functions, when…”

4.1.1 Change “verification” to “prototyping” (2 places)

4.1.1d, e & f (Added) “d. Form, fit and function of TCTO kits and modified components.

e. TO update accuracy.

f. Proper function of the modified equipment.”

5.2 Replace with: “Bill of Materials. TCTO kits shall contain a Bill of Materials listing all of the items required to accomplish the

TCTO. As a minimum, the format of the Bill of Material shall be as follows:”

6.2l Change to read: “Issue and Rescission dates (see 3.5.2.6 & 3.5.2.6.1).”

6.2x Delete.

6.4.8 Change “verification” to “prototyping” (2 places)

6.4.8a Add “Includes validating the form, fit, and function of any kits involved, accuracy of associated TO updates, and proper operation of the modified equipment.”

6.5 Change 1

st sentence to read: “…are contained in TO 00-5-15, Air Force Time Compliance Technical Order Process.”

6.6 Add “prototyping” and “supplement” to key word list.

Figures 3, 4 & 5 Change “Proofing” to “Verification” in each figure.