TMCR_CAL_Fire_5_Nov_2018.pdf

TM-27-01 5 November 2018 1

Technical Manual Contract Requirements (TMCR) for

Installation of Retardant Delivery System (RDS) on Selected USCG HC-130H Aircraft

(1C-130H(H)-1709)

(Program/Modification/Military System)

Jeffrey Huggett AFLCMC/WLNC Program Manager (PM) DATE

Section 1. Technical Order (TO) Program Requirements

1. TMCR Tailoring. This TMCR has been tailored by the program office, including the associated ta-bles, matrices and Specification/Standard Interface Records (SIRs). The Contractor may propose and submit, in writing additional tailoring to the PM and Procuring Contracting Officer (PCO) for considera-tion. The tailored TMCR shall be attached to the CDRL D001 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 Installation of Retardant Delivery System (RDS) on Selected USCG HC-130H Aircraft Technical Order Concept of Operations. 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 pro-cedures found in this document may be researched there.

2. TO Program Scope. The Contractor may recommend additional Section 2 tailoring to propose new TO types (Table 1) and source data and TO updates (Table 2) required to support the Installation of Re-tardant Delivery System (RDS) on Selected USCG HC-130H Aircraft program’s objectives.

3. Commercial Manuals. Contractors shall recommend the use of existing commercial manuals to the maximum extent possible without impairing program support objectives. All proposed commercial manuals are subject to government review and approval.

NOTE: a) Contractors shall use Data Item Description (DID) DI-TMSS-80067, Technical Manual (TM) Contractor Furnished Aeronautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices, to provide recommendation data. b) Government activities will use MIL-PRF-32216, Evalua-tion 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 Speci-fication: Flight Manuals, Air Refueling Procedures, and Abbreviated Checklists, as an additional guide for commercial Flight Manuals.

3.1. All commercial manuals shall be delivered with either unlimited data rights or as a minimum, Government Purpose License, to allow the AF to electronically store, print, distribute and decollate the commercial manual to allow for printing.

3.2. Approved COTS Manuals shall be delivered with an Identifying TO Publication Sheet, In Ac-cordance With (IAW) MIL-PRF-32216. All PDF files of commercial data shall be non-password protected to allow the AF to decollate the manual for printing.

3.3. If the proposed COTS data is found to be insufficient after review by the government, the con-tractor shall prepare supplemental data for the COTS manual as required IAW MIL-STD-38784. If the COTS data cannot be supplemented sufficiently the contractor may be tasked to develop new TM data IAW the applicable TMSS listed in Section 2 Table 1.

2 TM-27-01 5 November 2018

4. Technical Manual Specifications and Standards (TMSS) Tailoring. TMSS are tailored by selecting between tailoring options offered in 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 or XML schema struc-ture located in Section 2 Table 1.

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. Contractors may recommend additional tailoring of the Joint-Service TMSS SIRs and provide recommended SIRs for other TMSS 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 un-marked and “(F)” TMSS requirements as modified by the tailoring options in each TMSS.

4.2. Questions concerning TMSS requirements may be resolved by written request and justified suggestions for resolution submitted through the PCO AFLCMC/WLNKA - 235 Byron Street, Suite 19A, Robins AFB, GA 31098-1670. 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. The Contractor shall propose a process for notifying the gov-ernment 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 developing additional data.

6. TO Development. 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. SGML-tagged TO files shall include required illustration (graphics) files in an approved graphics exchange format. Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible. All delivered graphics shall conform to the approved graphic creation and format guidelines listed in attachment 1. For assis-tance with illustration requirements contact AFLCMC/HIAM via (e-mail: SGMLSup-port@us.af.mil).

6.2. Page-oriented Military Specification (MILSPEC) TOs shall be formatted with text, graphics and delivered according to the TMSS specified in Section 2. The contractor shall develop TO files (tagged instances) using Standard Generalized Markup Language (SGML) according to the DTDs referenced in the appendix to MIL-STD-38784 and each applicable military detail specification (MIL-DTL). Multiple SGML file instances for a single TO document are not authorized.

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 compatibil-ity with existing systems identified in the IDS and the System Support Plan.

7. TO Numbering. Contractors shall notify the government of manuals which require TO numbers. TO numbers are not required for manuals to be used exclusively by the Contractor’s own personnel. Re-quests for new TO numbers shall be submitted to the Equipment Specialist (ES) utilizing the TO num-bering worksheet. (Attachment 2)

8. Data Rights. Contractors shall provide Unlimited Rights for all source data and TOs prepared specif-ically for the contract. Government rights in data are specified in the Defense Federal Acquisition Regu-lation Supplement (DFARS), 252.227-7013, Rights in Technical Data, Noncommercial Items, 252.227- 7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documen-mailto:SGMLSupport@us.af.mil mailto:SGMLSupport@us.af.mil

TM-27-01 5 November 2018 3 tation, and 252.227-7015, Technical Data-Commercial Items. 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 tech-nical data.

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. Contractors shall determine the correct markings and controls for classified and restricted distribution data and TOs IAW the program’s Security Classification Guide (SCG) and DODM 5200.01, DODI 5230.24, AFI 31-401, AFI 61-204, and MIL-STD-38784 (available at http://www.e-publishing.af.mil/ or https://assist.dla.mil/online/start/index.cfm ). The markings and notices shall be reviewed during In- Process Reviews (IPR). NOTE: Distribution limitations will be determined on a case-by-case basis as TOs are developed, dependent upon TO content.

10. TO Quality. Contractors’ proposals shall describe how the government will be allowed to interact with the contractor’s TO development team. The contractors’ shall ensure TOs prepared are: a) techni-cally accurate and safe; b) written to a scope and depth of coverage sufficient to support the operations and maintenance concepts, and c) properly classified and marked with export control and distribution limitation statements. The contractor shall purpose a quality assurance program which ensures TOs are prepared IAW this contract. Recommended quality assurance methods shall be sufficiently detailed to support TO certification to include actual performance of procedures or desk-top analysis for non-procedural data. Simulation (walk-through/talk-through) should be reserved for those procedures which would activate explosive devices or present a hazard to personnel or equipment.

10.1. Guidance Conference. (T) Working through the Program Manager/Equipment Specialist, the contractor shall co-host and participate in a guidance conference for this effort to be held within 60 calendar days after award of contract. The Technical Order Status and Schedule (TOSS) will be formalized at this conference. The contractor shall present a briefing on their interpretation of the basic contract, SOW, CDRLs, Data Item Descriptions (DIDs), MIL-SPEC, MIL-STD, SIRs, this document and the planned preparation and delivery of the TOs and related data.

10.2. In-Process Reviews. The contractor shall participate and co-chair In-Process Reviews of the data developed for this effort. In-Process Reviews may be requested by the Government or by the contractor to ensure that data being developed as part of this effort is adequate and accurate and IAW contract requirements and cited specifications. The contractor shall support IPRs with the tech-nical writers, engineers and QA personnel as required or needed. IPRs will be held in accordance with TO 00-5-3 or as defined by the program office. During the IPRs the contractor will be respon-sible to maintain a master markup of the document being reviewed. This master markup will be made available at the next scheduled review. A copy of the markup will be provided to the Govern-ment or designated individual at the conclusion of the review. The contractor shall ensure all com-ments from previous IPR’s have been incorporated prior to next scheduled IPR. With the prior ap-proval of the Government the IPRs may be combined. IPRs typically consist of a 40%, 80%, Verifi-cation and Final Review. IPRs are set up at the discretion of the Government and will be addressed at the Guidance Conference.

10.3. TO Delivery Requirements for In-Process Reviews. IPR TO data shall be technically edited and reviewed according to the contractors quality assurance methods. Manuscript (handwritten) data is not acceptable for any data to be reviewed. The quality assurance checklists shall be available for review by the government during the IPRs.

10.4. TO Certification. The contractor shall certify that new TO procedures and data developed to support the program are accurate, adequate, current, and usable for their intended purpose. The Gov-ernment may witness the certification activities. The contractor shall incorporate comments generat-http://www.e-publishing.af.mil/ https://assist.dla.mil/online/start/index.cfm

4 TM-27-01 5 November 2018 ed by the certification process into the TOs prior to submitting the TOs for verification. At the com-pletion of the certification, the contractor shall submit a letter to the ES stating that certification has been completed and that any deficiencies identified during the process have been corrected. The con-tractor will ensure all necessary changes and corrections to affected manuals are accomplished in time to meet contract delivery schedule requirements. The contractor shall notify the government at least 180 days prior to the need date of any Government Furnished Information/Government Fur-nished Equipment (GFI/GFE) required to perform certification tasks. TO 00-5-1 and TO 00-5-3 shall be referenced for additional information on TO Certification requirements. Certification documenta-tion shall be provided to the government prior to verification delivery.

10.5. Verification Support. The contractor shall propose the methods, equipment and personnel required to support Government TO verification. Contractor verification support will consist of at least a Lead Technical Writer, knowledgeable on the system and a System Qualified Engineer.

10.6. TO Prepublication Reviews (PPR). PPRs are examinations of TOs to ensure incorporation of agreed upon changes from IPRs and verification, and to ensure the manual meets style and for-mat requirements. The Contractor shall prepare and deliver copies of TOs and TO updates in MIL- SPEC compliance for the PPR as shown in the delivery matrix. The TOs for PPR shall have been approved by contractor QA, be in compliance with the MIL-SPECs/standards, and incorporate all verification comments and corrections approved by the Government or program management office representative. The Government may waive the PPR depending on number and complexity of changes from verification.

10.7. Technical Data Assessment (TDA). TDA’s may be accomplished using organic TO sustain-ment environments (ATOS, IDM, etc.) or with the assistance of AFLCMC/HIAM. The TO Manager, will determine the TDA requirements for each TO type.

10.7.1. SGML TO Data. The contractor shall submit an SGML tagged TO file, associated graphics files, a PDF rendition of the SGML tagged TO file composed by the contractor and any associated companion files necessary for PDF composition. During assessment, the SGML tagged TO file will parsed against the appropriate TMSS DTD (and optionally run through the Tagging Utilization Tool (TUT)) to determine DTD compliance and correct tag usage. The SGML tagged TO file and associated graphics will be composed by the program office and the rendered PDF will be compared with the submitted PDF to check for completeness, indexing, and MIL-SPEC/STD compliant formatting.

10.7.2. Error Resolution. Errors found during the TDA shall be addressed and completed prior to each IPR. Additional TDAs may be necessary based on the amount of errors found during the ini-tial TDA. Successful TDAs in no way relieves the contractor from fixing errors found during fu-ture reviews.

11. TO Delivery. Offerors shall propose practices and procedures for secure access to or delivery of digi-tal 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 for-mats shall be according to applicable CDRLs and the tailored TM Delivery Requirements Matrices includ-ed in Section 2 of this document. Paper TO delivery is not acceptable for final delivery of TOs.

EXCEPTION: For Commercial Manuals not available digitally.

11.1. Indexed Adobe™ Portable Document Format (IPDF) Files. The contractor shall validate in-dexing of PDF TO files using the specifications contained in the Technical Order Conversion Re-quirements (TOCR).

12. Source Data Maintenance. Contractors shall maintain accuracy, currency and configuration of TOs and source data throughout the contract period of performance. Maintenance includes preparation of

TM-27-01 5 November 2018 5 source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes. Editorial and Technical Content cut-off will be the close and acceptance of the Verification minutes and closure of all action items from that Verification Review (IPR).

12.1. Web Site. The contractor shall establish a secure web site to receive/deliver Technical Orders listed in Table 2.

13. Schedules. The contractor shall include TO program events and schedules in their proposed In-tegrated Master Plan (IMP) and Integrated Master Schedule (IMS) and update the IMS throughout the period of performance. Government 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 de-termine TO development and delivery schedules throughout the acquisition phase of a program. Any change to the IMS must be coordinated with the Government. A copy of the updated IMS will be pro-vided to the Government.

15. TO Reproduction Management. Offerors shall propose practices and procedures for managing the programs Preliminary TO reproduction requirements. MIL-HDBK-38790, Printing Production of Tech-nical Manuals, may be used as guidance for TO printing format, paper weights, layout requirements, etc.

NOTE: Reproduction management for formal TO printing includes assembly of a print package (repro-duction media, a reproduction assembly sheet).

6 TM-27-01 5 November 2018

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

• Mark the TM Type Selection Tables indicating the applicable TO types and related specifications.

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

• Editorial and Technical Content cut-off will be the close and acceptance of the Verification minutes and closure of all action items from that Verification Review (IPR).

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

• Change package format deliveries will be with accompanying back-up pages. Source data deliveries will be delivered in change package format without accompanying back-up pages. No manuscript source will be accepted.

• For further information on the Air Force Vision and TO Concept of Operations (CONOPS), see AF Portal URL https://wwwd.my.af.mil/afknprod/ASPs/DocMan/DocMain.asp?Filter=OO-EN-TO-PI&FolderID=OO-EN-TO-PI- 15&Tab=0.

PART A – (NEW DEVELOPMENT) TM TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE

Installation of Retardant Delivery System (RDS) on Selected USCG HC-130H Aircraft

(1C-130H(H)-1709)

(System/Component)

Title or Type of Manuals Specification Required

1. Inspection TOs MIL-DTL-5096

a. Inspection and Maintenance Requirements (-6) Manual

b. Acceptance and Functional Check Flight (FCF) Procedures (-6CF)

Manual

c. Acceptance and Functional Check Flight (-6CL) Checklist

d. Inspection Workcards (-6WC)

e. Maintenance/Operations Checklists

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

a. Loading Instructions Manual

b. Nuclear Weapon Cargo Loading Manual

c. Checklists

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

a. Loading Data Manual

b. Sample Basic Weight Checklists

4. Flight Manuals MIL-DTL-7700

a. Flight Manual

b. Performance Data Manual

c. Mission Crew Manual

d. Supplemental Manual

e. Abbreviated Flight Crew Checklist

TM-27-01 5 November 2018 7

TMSS REQUIREMENTS FOR THE

Installation of Retardant Delivery System (RDS) on Selected USCG HC-130H Aircraft

(1C-130H(H)-1709)

(System/Component)

Title or Type of Manuals Specification Required

5. List of Applicable Publications MIL-DTL-8031

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

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

a. Nuclear Weapons Basic Information and Loading Procedures

b. Nuclear Weapons Loading Procedures

c. Non-nuclear Munitions Basic Information

d. Non-nuclear Loading Procedures

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

f. Loading Procedures Checklist

g. Single Loading Procedures Checklist

h. Integrated Loading Procedures Checklists

i. Family Group Loading Procedures Checklist

j. Nuclear Weapons Loading Procedure Checklists

k. Functional Check Procedures Checklist

l. NATO Stage B Cross-Servicing Checklists

m. End of Runway (EOR) Procedures Checklist

8. Space Operations and Support Documentation TOs -- MILSPEC (Intercontinental Ballistic Missiles) -- MILSPEC (Space)

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

a. Non-nuclear Weapon Delivery Manual

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

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

d. Aircrew Nuclear Bomb Delivery Manual (Tactical Aircraft)

e. Non-nuclear Weapon Delivery Checklist

f. Nuclear Weapon Delivery Checklist (Strategic Bomber Aircraft)

g. Aircrew Nuclear Bomb Delivery Checklist (Tactical Aircraft)

h. Non-nuclear Weapon Delivery Source Data Packages

10. Work Unit Code Manual

a. Standard WUC Manual

b. Two Chapter Manual

c. Three Chapter Manual

MIL-DTL-38769

11. Calibration Procedures MIL-DTL-38793

12. Time Compliance Technical Orders (TCTOs)

a. TCTO

b. TCTO Supplement

MIL-DTL-38804

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

14. Illustrated Parts Breakdown MIL-DTL-38807

15. On-Equipment Organizational Maintenance Manual Set MIL-DTL-83495

a. General Equipment (GE) Manual

b. General System (GS) Manuals

c. Combined GE & GS Manual

d. Job Guide (JG) Manuals

8 TM-27-01 5 November 2018

TMSS REQUIREMENTS FOR THE

Installation of Retardant Delivery System (RDS) on Selected USCG HC-130H Aircraft

(1C-130H(H)-1709)

(System/Component)

Title or Type of Manuals Specification Required

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

c. Special Manuals

(1) Aircraft Engine Testing and Trending Procedures

(2) Aircraft Power Package Testing Procedures

(3) Static Firing of Missile Motors

(4) System Peculiar Corrosion Control

(5) Nondestructive Inspection (NDI)

(6) Aircraft Structural Integrity Program (ASIP)

(7) ATE Operator Test Procedures

(8) Special Requirements for Storage and Maintenance Procedures;

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

(9) Parachute Packing Procedures

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

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

d. Checklists (IAW MIL-DTL-5096)

e. With Illustrated Parts Breakdown

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

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

TM-27-01 5 November 2018 9

TABLE 2

SUSTAINMENT/MODIFICATION UPDATES TM TYPE SELECTIONS

NOTES:

• Check all applicable boxes.

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

TO Number, Title, or Type of Manual

Specification

Change

Revision

Supple-ment

Supple-mental

TM

Source Data

1. TCTO 1C-130H(H)-1709** MIL-DTL-38804 TCTO

3. 1C-130H-RDS-1** Same Style and Format

4. 1C-130H-RDS-2-18** Same Style and Format

5. 1C-130H-RDS-CL-1** Same Style and Format

6. 1C-130H-2-13 Same Style and Format

* - Flight Manual ** - New TOs/TCTOs

PART B - TM DELIVERY REQUIREMENTS

FOR

Installation of Retardant Delivery System (RDS) on Selected USCG HC-130H Aircraft

(1C-130H(H)-1709) (System/Item)

TM DATA TYPE DELIVERED (SEE TABLE 2).

(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 final delivery) F - FrameMaker versions 8.0 through 10.0 file format. All

Flight Manuals – use Government furnished tags.

M - Mixed paper and digital (F, G, H, I, N or X). G - Standard Generalized Mark-up Language (SGML).

H - Hyper Text Mark-up Language (HTML) (Helicopters only) I - Indexed Portable Document Format (IPDF) File. (IPDF

- new/complete TOs or PDF - change/source package(s))

N - Native Format (i.e. – PageMaker , FrameMaker (FM), Adobe Illustrator CS6 or earlier version (AI), Portable Document Format (PDF))

X - Extensible Mark-up Language (XML) file format S – Encapsulated PostScript (EPS) file format

PAPER/ELECTRONIC PAPER TYPE - All Final Delivery(s) with graphic(s) in digital format delivery(s)) will be delivered as instructed on the delivery schedule. (See page 10) All Flight Manual Final Deliver of graphics will be individual Adobe Illustrator CS3 or later files. All change(s)/source page(s) will be 100% vector art that includes searchable text, no raster art accepted. Back-up pages may be raster art.

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

10 TM-27-01 5 November 2018

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

• AFTO Form 158s will be provided by the Contractor after every In-Process Review (IPR) within 10 working days of said review.

• TO Updates. From each IPR, will be provided to the ES 30 days prior to the next IPR.

• Editorial and Technical Content cut-off will be the close and acceptance of the Verification minutes and closure of all action items from that Verification Review (IPR).

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

• Each FM Delivery will be based on Mission Design Series (MDS) for C-130s. (See page 13 for all affected Flight Manuals on the

C-130s, excluding FMS.)

TABLE 3 - TM DELIVERY REQUIREMENTS

FOR

Installation of Retardant Delivery System (RDS) on Selected USCG HC-130H Aircraft

(1C-130H(H)-1709)

(System/Item)

DELIVERY SCHEDULE

Event/Number of days data required prior to event

Technical Review(s)

_____30____ Days

Verification

_____30____

Final TO Distribution

_____45____

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

Attn: USCG 1060 Consolidated Rd Elizabeth City, NC 27909

P/I/1 P/I/1 TBD

Attn: Lead Equipment Specialist Richard Barson

AFLCMC/WLNC

235 Byron St., Suite 19A

ROBINS AFB GA 31098

M/P/I/1 M/1 P/2 I/1

M/P/I/1

Total Copies Required:

P/I/2 M/1

P/3 M/1 I/2

M(N/I/P)/1 F/I/N/5

P/I/1