RFP_Attachment_20_TMCR_TM-86-01P_Change_Package.pdf

TM-86-01P 9 Dec 2014 1

Attachment 20

Air Force Technical Manual Contract Requirements (TMCR) For

A-10 TECHNICAL ORDER SUSTAINMENT SUPPORT,

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT: ___________________

Date: 5 October 2016

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

0704-0188.

SECTION 1. TECHNICAL ORDER (TO) PROGRAM REQUIREMENTS

1. TMCR Tailoring. This TMCR has been tailored by the program office, including the associated tables, matrices and Specification/Standard Interface Records (SIRs). The Contractor may propose and submit, in writing additional tailoring to the TO Manager Agency/Agent (TOMA) and Procuring

Contracting Officer (PCO) for consideration. 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 A-10 Technical Order Sustainment Support.

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, located on the Internet at https://cs3.eis.af.mil/sites/OO-EN-TO-PI/default.aspx.

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 A-10 Technical Order Sustainment Support program’s objectives.

3. Commercial Manuals. This section is Not Applicable as this effort does not intend to provide any

Commercial Manuals.

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 structure 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 unmarked 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 sug-gestions for resolution submitted through the Procuring Contracting Officer (PCO) and Mr. Len Mian, AFLCMC/WWALE, 6067 Box Elder Lane, Bldg. 1284, Hill AFB, UT 84056 (801) 586-7150.. Defi-ciencies and suggested improvements shall be submitted to the TMSS Preparing Activity (PA). Ap-proved recommendations, corrections and clarifications will be maintained with contract documenta-tion.

https://cs3.eis.af.mil/sites/OO-EN-TO-PI/default.aspx

2 TM-86-01P 9 Dec 14

5. Subsequent TO/Data Requirements. When new TO requirements are identified the Contractor shall notify the government utilizing DI-TMSS-80067B, Technical Manual (TM) Contractor Furnished Aero-nautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices, or approved contractor formats. This process shall require government review and approval of recommended additional require-ments prior to developing additional data.

6. TO Development. The baseline for the A-10 Technical Order Sustainment Support effort is the latest available Block Cycle Release (BCR). The TO development process shall follow the guidelines outlined in the Tech Order Process Plan (TOPP) document. The Contractor shall propose TO development prac-tices and procedures that ensure TOs and data are compatible with the Air Force Technical Order Concept of Operations (CONOPS) (https://cs3.eis.af.mil/sites//OO-EN-TO-PI/default.aspx) and the Air Force

Standard TO Management System. 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-38784A, 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, to the maximum extent practical. The Con-tractor shall develop TO change package(s) using Adobe Acrobat or Word.

6.2. Graphic updates shall be delivered as vectorized CGM. NOTE: Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible. For assistance with illustration requirements contact AFLCMC/HIAM via (e-mail:SGMLSupport@us.af.mil).

6.3. The Contractor may propose use of 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. If proposing the use of NGS, contact the Procuring Contracting Officer (PCO) and

TO Manager to request guidance from the Air Force Preparing Activity (PA), 754 ELSG/ILMT, Tech-nical Order Section, 4375 Chidlaw Rd Suite 6, WPAFB OH 45433-5006.

7. TO Numbering. This section is Not Applicable as this effort does not intend to provide any new

TOs.

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. Government data rights shall extend to the common source database, transformation style sheets, and other tools or products used to author or display technical 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://as-sist.dla.mil/online/start/index.cfm ). The markings and notices shall be reviewed during In-Process Re-views (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 maintain a Technical Manual Quality Assurance plan for this effort and shall be sufficiently detailed to support TO certification to include actual performance of pro-https://cs3.eis.af.mil/sites/OO-EN-TO-PI/default.aspx mailto:SGMLSupport@us.af.mil http://www.e-publishing.af.mil/ https://assist.dla.mil/online/start/index.cfm

TM-86-01P 9 Dec 2014 3 cedures or desk-top analysis for non-procedural data which shall be available for review at the TO Guid-ance Conference. Simulation (walk-through/talk-through) should be reserved for those procedures which would activate explosive devices or present a hazard to personnel or equipment. NOTE: Quality require-ments for the Joint Nuclear Weapons Publications System (JNWPS) and for Non-nuclear Explosive Ord-nance Disposal (EOD) Data are contained in TO 11N-1-1 and DODD 5160.62, respectively. The govern-ment will conduct performance-tests all JNWPS and EOD TOs.

10.1. Guidance Conference. Working through the TOMA, the Contractor shall co-host and participate in a Technical Order Guidance Conference (TOGC) 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 guidance conference. The Contractor shall present a briefing on their interpretation of the basic con-tract, 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 (IPR) of the data developed for this effort. In-Process Reviews may be requested by the TOMA 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 ensure all comments from pre-vious IPR’s have been incorporated prior to next scheduled IPR. With the prior approval of the TOMA the IPRs may be combined.

10.3. TO Delivery Requirements for In-Process Reviews There will be two In-Process Reviews (IPRs) and a Pre-Publication Review (PPR) to ensure TOs are being developed according to contract require-ments and that open discrepancies are cleared prior to publication. Contractor source data will be used at the IPRs. The Contractor shall ensure all comments from previous IPR’s have been incorporated prior to next scheduled IPR. With the prior approval of the TOMA the IPRs may be combined. Con-tractor engineering preliminary/final drawings/data that drive changes to the TOs shall be delivered with the TOs for review prior to the IPRs. USAF Preliminary Technical Orders (PTOs) will be used for Verification and Pre-Publication Review.

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 generated by the certification process into the TOs prior to submitting the TOs for verification. At the completion of the certification, the Contractor shall submit a letter to the TOMA stating that certification has been completed and that any deficiencies identified during the process have been corrected. The Contractor will ensure all necessary changes and corrections to affected manuals are accomplished in time to meet contract delivery schedule requirements. The Contractor shall notify the government at least 180 days prior to the need date of any Government Furnished Information/Government Furnished Equipment

(GFI/GFE) required to perform certification tasks. Technical order 00-5-1 and 00-5-3 shall be refer-enced for additional information on TO Certification requirements.

10.5. Verification Support Verification Support shall consist of the Lead Technical Writer, engineer-ing support (as required), Equipment Specialist (ES), Flight Manual Manager (FMM) (as required), TOMA (as required), and MAJCOM/field support personnel. A functional A-10C model aircraft with the necessary hardware and software, as well as any necessary on aircraft support (load crew, main-tainers, pilots, etc.), will also be required at the verification. This support should be in accordance with the A-10 Thunderbolt II, TO Life Cycle Verification Plan (TOLCVP). Contractor source data will be incorporated into the baseline TOs by the USAF prior to verification of the manuals.

4 TM-86-01P 9 Dec 14

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 format 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 TOMA or program management office representative. The

TOMA may waive the PPR depending on number and complexity of changes from verification.

11. TO Delivery. The Contractor shall propose practices and procedures for secure access to or delivery of digital TO files, source data (PDF, Word, CGM, etc.), reproduction masters, and program support data.

TO file delivery formats shall be according to applicable CDRLs and the tailored TM Delivery Require-ments Matrices included in Section 2 of this document. Paper TO delivery is not acceptable for final delivery of TOs.

12. Source Data Maintenance. Contractors shall maintain accuracy, currency and configuration of TO source data, to include GFI, throughout the contract period of performance. The Contractor is responsible for updating the TOs to include technically accurate and error free data that explains the new capabilities developed as part of the A-10 Technical Order Sustainment Support effort, including correction of prior technical data found to be in error/inaccurate and affected by this modification. Maintenance includes preparation of source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes. The Contractor shall update the source data to the latest available TO baseline as of 30 calendar days prior to final delivery of source data.

13. TO Maintenance. Contractors shall maintain TO’s by preparing emergency, urgent, routine changes/revisions or supplements and source data updates to incorporate corrections, equipment configu-ration changes, and maintenance and operational concept changes IAW TO 00-5-3.

14. Schedules. Schedule slips shall be communicated to the USAF immediately to resolve any potential schedule conflicts. NOTE: AF policy requires delivery of verified TOs prior to or concurrently with delivery of operational equipment to the field (AFI 63-101). This policy will determine TO development and delivery schedules throughout the acquisition phase of a program.

The Contractor shall develop and maintain an Integrated Master Schedule (IMS), and update the IMS throughout the period of performance for all TO development activities associated with this order for the life of the contract. The schedule shall be to the system/book or TCTO level and cover all development major milestones. Any changes after the guidance conference shall be coordinated with and approved by program TOMA.

15. Time Compliance Technical Orders (TCTOs). The Contractor shall prepare TCTO’s, ITCTO’s and resulting TO updates as required in support of A-10 Technical Order Sustainment Support TCTO’s will be used to document all permanent modifications, initiate special “one time” inspections, or impose tem-porary restrictions on systems or equipment within specified time limits effecting A-10 Technical Order

Sustainment Support. The Contractor 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. The Contractor shall perform a peer and engineering technical review prior to sub-mittal to the USAF. 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.

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

TM-86-01P 9 Dec 2014 5

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

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

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

TABLE 1

TMSS REQUIREMENTS FOR THE A-10 TECHNICAL ORDER SUSTAINMENT

SUPPORT

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

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

6 TM-86-01P 9 Dec 14

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

e. Fault Reporting (FR) Manual

f. Fault Isolation (FI) Manual

g. Wiring Data (WD) Manual

h. Schematic Diagram (SD) Manual

TM-86-01P 9 Dec 2014 7

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

19. Technical Publications Utilizing Common Source Database (CSDB)

ASD-S1000D -

International

Specification for

Technical Publications

Utilizing a CSDB

MIL-STD-3048

8 TM-86-01P 9 Dec 14

TABLE 2

ADDITIONAL TM TYPE SELECTIONS

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-38784A.”

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-DTL-83495 (which serves as business rules for manual style, format, and content).

The TOs identified in Table 2 will be discussed and agreed upon at the Technical Order Guidance Conference.

TO Number, Title, or

Type of Manual

Specification

Com-mercial

Manual

Change/

Revision

Supple-ment

Supple-mental

TM

Source

Data

1. 1A-10C-1 MIL-DTL-7700

Add all A-10C TOs listed in

RFP_Attachment_15_A-

10_List_of_Tech_Orders in this section

TM-86-01P 9 Dec 2014 9

TABLE 2

SUSTAINMENT/MODIFICATION UPDATES TM TYPE SELECTIONS

Check all applicable boxes.

TABLE 3 - TM DELIVERY REQUIREMENTS

FOR A-10C AIRCRAFT A-10 TECHNICAL ORDER SUSTAINMENT SUPPORT

Delivery Format Requirements Codes

Digital delivery only:

C - Vectorized Computer Graphics Metafile (CGM) files.

F - Portable Document Format (PDF) file.

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

final delivery) H - Hyper Text Markup Language (HTML).

M - Mixed paper and digital (G, H or I)

W – Word Documents (As Required)

I - Indexed Portable Document Format (IPDF) File.

T - Redlined Tagged Image File Format (TIFF).

X - Extensible Markup Language (XML).

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

For Paper media delivery indicate required quantity

For all other media types indicate (Y) = Yes or (N) = No

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

DELIVERY SCHEDULE

Event Number of days data required prior to event

In Process

Review(s)

(10 Working

Days)

Verification

(5 Days)

Prepublication

Review

(10 Days)

Final TO

Distribution

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

AFLCMC/WWALE

Attn: Tammy Heslop

6067 Box Elder Lane, Bldg 1284

Hill AFB, UT 84056-5811

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

C /

W/

AFLCMC/WWALE

Attn: Len Mian

6067 Box Elder Lane, Bldg 1284

Hill AFB, UT 84056-5811

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

C /

W/

10 TM-86-01P 9 Dec 14

Total Paper Copies Required: I/C/W-

TM-86-01P 9 Dec 2014 11

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-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-16) AFLCMC/HIAM.

Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available from

Acquisition Streamlining and Standardization Information System (ASSIST) web page, https://as-sist.dla.mil/online/start/index.cfm.

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

Comments (recommendations, additions, deletions) and any pertinent data which may be in use in improving Air Force

TMSS documents should be submitted to AFLCMC/HIAM, 4170 Hebble Creek Road, Bldg. 280, Door 15, Area A, Wright-Patterson AFB, Oh 45433-5653 or by email to; SGMLsupport@us.af.mil. Do not include the street address, a building number or a zip+4.

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-DTL-22202D, 31 March 1999; Supplement 1, 31

March 1999

Manual, Technical, Aircraft Cross-Servicing Guide, Preparation of

The requirements of 6.2 are met in this SIR (see below).

1.1 In addition to paper delivery, when this specification is used to develop digital delivery files (document type defi-nitions – DTDs) contact the PA for additional instructions.

2.3 Ensure the listing for STANAG/ASCC Air Standard Documents is current. List applicable STANAG/ASCC Air

Standards below.

(List STANAG/ASCC Air Standard Documents here.)

2.2.1 (Added) “Other government documents, drawings, and publications.”

DEPARTMENT OF DEFENSE

DODM 5200.1 DOD Information Security Program

DOD 5220.22-M National Industrial Security Program Operating Manual

4. Replace with: “4. VERIFICATION.”

“All cross-servicing guides shall meet the requirements of sections 3 and 5 of this specification, as re-quired 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 sup-plies 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 author-ize submission of known defective material, either indicated or actual, nor does it commit the govern-ment to accept defective material.”

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

12 TM-86-01P 9 Dec 14

5. Replace with: “5. PACKAGING.”

“5.1 Packaging Requirements. For acquisition purposes, the packaging requirements shall be as speci-fied in the contract or order. When the actual packaging of material is to be performed by DoD per-sonnel, these personnel need to contact the responsible packaging activity to determine packaging re-quirements. Packaging requirements are maintained by the Inventory Control Point’s packaging activ-ity within the Military Department’s System Command. Packaging data retrieval is available from the

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

“5.1.1 Encoded Computer Products. Packaging of encoded computer products for delivery shall be in accordance with the requirements of MIL-STD-1840C, Automated Interchange of Technical Infor-mation.”

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

DODM 5200.1, DOD 5220.22-M, and the implementing Service regulations.”

6.2a Title, number, and date of the specification are listed above.

6.2b Issue of DODISS: (fill in issue of DODISS applicable to this contract) 6.2c Packaging requirements (see above).

6.2d Verification requirements (see above).