ATTACHMENT_9_AvCI_TMCR.pdf

TM-86-01N 1 April 2009 1

Air Force Technical Manual Contract Requirements (TMCR) for

T-38C Avionics System Component Development

(Program/Modification/Military System)

ATTACHMENT 9 , TO CDRL SEQUENCE NUMBER A029 , EXHIBIT A

REQUEST FOR PROPOSAL/CONTRACT: FA821115R0001

Date: 12 December 2014 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. Offerors must tailor this TMCR document, including the associated tables, matri-ces 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 pro-posal SOW. Proposals shall be compatible with the Air Force infrastructure and support the T-38C Avionics System Component Development Program’s Integrated Data System (IDS) requirements. 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.tinker.af.mil/library/factsheets/factsheet.asp?id=6082. 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 T-38C Avionics System Component Development program’s objectives.

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

NOTES: a) Contractors may use Data Item Description (DID) DI-TMSS-80067, Technical Manual (TM) Contractor Furnished Aeronautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices (located at http://dodssp.daps.dla.mil/assist.htm), to provide recommendation data. b) Govern-ment 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 commer-cial 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 man-datory requirements which are part of the Document Type Definition (DTD) structure.

4.1. AF options in some Joint-Service TMSS have been documented in preliminary SIRs included in Section 3. These preliminary SIRs provide the starting point for further tailoring. Offerors shall complete tailoring of the Joint-Service TMSS SIRs and provide recommended SIRs for other TMSS or NGS as applicable. NOTE: TMSS requirements marked “(F)” are specifically for Air Force use;

“(A)” is for Army, “(M)” is Marine Corps and “(N)” is Navy. Comply with all unmarked and “(F)” TMSS requirements as modified by the options in paragraph 6.2.

4.2. Questions concerning TMSS requirements may be resolved by written request and justified suggestions for resolution submitted through the Procuring Contracting Officer (PCO) and Shaunna http://dodssp.daps.dla.mil/assist.htm

2 TM-86-01N 1 April 2009

Johnson, AFLCMC/WLDEH, 6057 Box Elder Ln, Hill AFB, UT 84056, DSN 586-6678, Commer-cial 801-586-6678. Deficiencies and suggested improvements shall be submitted to the TMSS Pre-paring Activity (PA). Approved recommendations, corrections and clarifications will be maintained with contract documentation.

5. Subsequent TO/Data Requirements. Offerors shall propose a process for notifying the government when additional TO or source data requirements are identified subsequent to contract award. This pro-cess 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://wwwd.my.af.mil/afknprod/DocView.asp?DocID=1689861) and the Enhanced Technical Information Management System (ETIMS). In addition, TOs shall be written to a scope and depth of cov-erage 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 according to each applicable military detail or performance specification (MIL-DTL, MIL-PRF, or

MIL-STD).

6.2. New illustrations shall be provided in vectorized cgm format. A new illustration may be re-quired due to lack of existing data or if there are more than three changes to an existing graphic. If there are three or less changes on an existing graphic, a red-lined PDF annotating changes is ac-ceptable.

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. Offerors shall notify the government of manuals which require TO numbers. TO numbers are not required for manuals to be used exclusively by the offeror’s own personnel. (NOTE:

DI-TMSS-80067 may be used to provide the notification.) AF procedures for numbering TOs are de-scribed in TO 00-5-3 and TO 00-5-18, AF Technical Order Numbering System, (available at http://www.tinker.af.mil/library/factsheets/factsheet.asp?id=6082/).

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

8.1. If some TOs or source data are copyrighted or contain proprietary data or procedures, offerors may propose Limited Rights or Government Purpose Rights (GPR) only. Proposed commercial manuals should be provided with 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 busi-ness 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.

TM-86-01N 1 April 2009 3

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. Offerors shall de-termine 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. TO Quality. Offerors shall propose a quality assurance program which ensures TOs are prepared IAW this contract. Recommended QA methods must include actual performance of procedures and use of desk-top analysis for non-procedural data. Simulation (walk-through/talk-through) should be re-served for those procedures which would activate explosive devices or present a hazard to personnel or equipment. Offerors’ proposals shall describe how the government will be allowed to interact with the contractor’s TO development team. NOTE: Quality requirements for the Joint Nuclear Weapons Pub-lications 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. Offerors shall propose sufficient conferences and re-views to allow insight into TO development processes and ensure contract compliance. Offerors should host an initial Guidance Conference or Technical Interchange Meeting (TIM) within 60 days of contract award to ensure mutual understanding of TO contract requirements, schedules, points of contact, etc. Periodic In-Process Reviews (IPRs) and Prepublication Reviews (PPR) ensure TOs are being developed according to contract requirements and that open discrepancies are cleared prior to publication. For eTO based programs, IPRs subsequent to the initial review need to be accom-plished 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. Offerors shall propose their method for documenting certification that TO procedures are accurate, adequate, current, safe and usable for their intended purposes. Offerors shall notify the government at least 180 days prior of the need for any Government Furnished Infor-mation/Government Furnished Equipment (GFI/GFE) required to perform certification tasks.

10.3. Verification Support. Offerors shall propose the methods, equipment and personnel required to support government TO Verification. This support should consist of at least engineering support (as required), Equipment Specialist (ES), Flight Manual Manager (FMM) (as required), TO Manager (as required), and MAJCOM/field support personnel (as required).

11. TO and Source Data Maintenance. Offerors shall propose methods for maintaining accuracy, cur-rency and configuration of TOs and source data throughout the contract period of performance. Mainte-nance includes preparation of TO and source data updates to incorporate corrections, equipment config-uration changes, and maintenance and operational concept changes.

12. TO Delivery. Offerors shall propose practices and procedures for secure access to or delivery of digital TO files, including those for Preliminary TOs (PTOs), source data, reproduction masters, and program support data. TO file delivery formats of source data for maintenance manuals, Flight manuals, and TCTOs shall be in a Microsoft Office Product or PDF format and shall be according to applicable CDRLs and the tailored TM Delivery Requirements Matrices included in Section 2 of this document. Pa-per TO delivery is not acceptable for final delivery of TOs. EXCEPTION: For Commercial Manuals not available digitally.

13. Schedules. Offerors shall include TO program events and schedules in their proposed Integrated Master Plan (IMP) and Integrated Master Schedule (IMS), and update the IMS throughout the period of performance. NOTE: AF policy requires delivery of verified TOs prior to or concurrently with deliv-http://www.e-publishing.af.mil/

4 TM-86-01N 1 April 2009 ery 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). Offerors shall propose practices and procedures to develop AF TCTOs and related TO updates when tasked as part of the approval process for Engineering Change Proposals (ECPs) to configured items. Costs for TCTO package development must be included in ECP Costs – not included as direct proposal costs. NOTE: ECPs are reviewed and approved by the Government’s Configuration Control Board (CCB). When the CCB decides that a TCTO is the appro-priate 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 Pro-cess, (available at http://www.tinker.af.mil/library/factsheets/factsheet.asp?id=6082/00-5-15-WA-1/00- 5-15.PDF) for a detailed description of TCTO processes.

TM-86-01N 1 April 2009 5

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

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

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

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

• Check the ASSIST database, http://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-DTL-38807, except that MIL-DTL-87929 will also be used for IPBs combined with work packages.

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

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

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

• 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 – TM TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE T-38 AVIONICS SYSTEM COMPONENT DEVELOPMENT Program

(System/Component)

Title or Type of Manuals Specification Required

1. Inspection TOs MIL-DTL-5096

a. Inspection and Maintenance Requirements (-6) Manual

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

Manual

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

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

6 TM-86-01N 1 April 2009

TMSS REQUIREMENTS FOR THE T-38 AVIONICS SYSTEM COMPONENT DEVELOPMENT Program

(System/Component)

Title or Type of Manuals Specification Required

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

a. Nuclear Weapons Basic Information and Loading Procedures

b. Nuclear Weapons Loading Procedures

c. Non-nuclear Munitions Basic

d. Non-nuclear Loading Procedures

e. Integrated Combat Turnaround Procedures

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

g. Loading Procedures Checklists

h. Integrated Loading Procedures Checklists

i. Nuclear Weapons Loading Procedure Checklists

j. Integrated Combat Turnaround Procedures Checklists

k. NATO Stage B Cross-Servicing Checklists

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

ANSI/AIAA-R024-1993

MIL-PRF-38311

MIL-PRF-38314

a. Operations Manual

b. Operations Checklists

c. Technical Manuals and Related Checklists

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

MIL-PRF-38384

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

b. Nuclear Bomb Delivery Manual (Strategic Bomber Aircraft)

c. Aircrew Nuclear Weapon Delivery Manual (Strategic Bomber

Aircraft)

d. Aircrew Nuclear Weapon Delivery Manual (Tactical Aircraft)

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

Tactical Aircraft)

f. Nuclear Bomb Delivery Checklist (Strategic Bomber Aircraft)

g. Aircrew Nuclear Weapon Delivery Checklist (Tactical Aircraft)

h. Non-nuclear Weapon Delivery Source Data Packages

10. Work Unit Code Manual MIL-PRF-38769

11. Calibration Procedures MIL-PRF-38793

12. Time Compliance Technical Orders (TCTOs) MIL-DTL-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

TM-86-01N 1 April 2009 7

TMSS REQUIREMENTS FOR THE T-38 AVIONICS SYSTEM COMPONENT DEVELOPMENT Program

(System/Component)

Title or Type of Manuals Specification Required

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

8 TM-86-01N 1 April 2009

TABLE 2

ADDITIONAL TM TYPE SELECTIONS

NOTES:

• Check all applicable boxes.

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

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

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

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

TO Number, Title, or

Type of Manual

Specification

Com-mercial Manual

Change/ Revision

Supple-ment

Supple-mental

TM

Source Data

1. 1T-38C-1 (FM) MIL-DTL-7700G

2. 1T-38C-1-1 (FM) MIL-DTL-7700G

3. 1T-38C-1CL-1 (FM) MIL-DTL-7700G

4. 1T-38C-1-1CL-1 (FM) MIL-DTL-7700G

5. 1T-38C-2-1 MIL-STD-38784

6. 1T-38C-2-1-1 MIL-STD-38784

7. 1T-38C-2-1CL-1 MIL-STD-38784

8. 1T-38C-2-2 MIL-STD-38784

9. 1T-38C-2-2CL-1 MIL-DTL-5096

10. 1T-38C-2-2CL-2 MIL-DTL-5096

11. 1T-38C-2-2CL-3 MIL-DTL-5096

12. 1T-38C-2-2CL-4 MIL-DTL-5096

13. 1T-38C-2-2CL-5 MIL-DTL-5096

14. 1T-38C-2-2CL-6 MIL-DTL-5096

15. 1T-38C-2-3 MIL-STD-38784

16. 1T-38C-2-3CL-2 MIL-DTL-5096

17. 1T-38C-2-3CL-3 MIL-DTL-5096

18. 1T-38C-2-4 MIL-STD-38784

19. 1T-38C-2-5 MIL-STD-38784

20. 1T-38C-2-5CL-1 MIL-DTL-5096

21. 1T-38C-2-6 MIL-STD-38784

TM-86-01N 1 April 2009 9

Supple-

22. 1T-38C-2-6-2 MIL-STD-38784

23. 1T-38C-2-7 MIL-STD-38784

24. 1T-38C-2-8 MIL-STD-38784

25. 1T-38C-2-8CL-1 MIL-DTL-5096

26. 1T-38C-2-9 MIL-STD-38784

27. 1T-38C-2-10 MIL-STD-38784

28. 1T-38C-2-11 MIL-STD-38784

29. 1T-38C-2-12 MIL-STD-38784

30. 1T-38C-2-13 MIL-STD-38784

31. 1T-38C-23 MIL-STD-38784

32. 1T-38C-34-1-1 MIL-DTL-7700

33. 1T-38C-34-1-1CL-1 MIL-DTL-5096

34. 1T-38C-36 MIL-STD-38784

35. 1T-38C-38 MIL-STD-38784

36. 1T-38C-3 MIL-STD-38784

37. 1T-38C-4-1 MIL-PRF-38807

38. 1T-38C-4-2 MIL-PRF-38807

39. 1T-38C-4-3 MIL-PRF-38807

40. 1T-38C-4-4 MIL-PRF-38807

41. 1T-38C-4-5 MIL-PRF-38807

42. 1T-38C-4-6 MIL-PRF-38807

43. 1T-38C-4-7 MIL-PRF-38807

44. 1T-38C-4-8 MIL-PRF-38807

45. 1T-38C-4-11 MIL-PRF-38807

10 TM-86-01N 1 April 2009

Supple-

46. 1T-38C-4-12 MIL-PRF-38807

47. 1T-38C-4-13 MIL-PRF-38807

48. 1T-38C-5 MIL-STD-38784

49. 1T-38C-6 MIL-DTL-5096

50. 1T-38C-6CF-1 (FM) MIL-DTL-5096

51. 1T-38C-6CL-1 (FM) MIL-DTL-5096

52. 1T-38C-6WC-1 MIL-PRF-5096

53. 1T-38C-6WC-3 MIL-PRF-5096

54. 1T-38C-6WC-4 MIL-PRF-5096

55. 1T-38C-6WC-5 MIL-PRF-5096

56. 1T-38C-06 MIL-PRF-38769

57. 1T-38C-01 MIL-PRF-8031

58. 1T-38C-17 MIL-STD-38784

59. 1T-38C-21 MIL-STD-38784

60. 1T-38C-3-2 MIL-STD-38784

61. TCTO TBD MIL-PRF-38804

TM-86-01N 1 April 2009 11

PART B - TM DELIVERY REQUIREMENTS

FOR T-38

(System/Item)

TM DATA TYPE DELIVERED SOURCE DATA .

(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 - Portable Document Format (PDF) 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 Review(s) (15 Days)

Verification (15 Days)

Prepublication Review(15

Days)

Final TO Distribution (15 Days)

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

AFLCMC/WLDMA

6064 Dogwood Ave Hill AFB, UT 84056

1 / 1 1 / 1 1 / 1 1 / 1

AFLCMC/WLDEH

6057 Box Elder Lane Hill AFB, UT 84056

1 / 1 1 / 1 1 / 1 1 / 1

Total Copies Required: 2 2 2 2

12 TM-86-01N 1 April 2009

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 includ-ed in the final contract, unless the entire SIR is not applicable; e.g., if MIL-DTL-22202D is not required, the en-tire 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 and 6.2b. For this contract enter:

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

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

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

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

• Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available from the DoD Single Stock Point (DODSSP), Acquisition Streamlining and Standardization Information System (ASSIST) web page, http://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-STD-38784, 25 August 2011

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

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

Time Compliance Technical Orders – Preparation http://www.dodssp.daps.dla.mil/assist.htm

Section 1. Technical Order (TO) Program Requirements