Form1423_0924143.pdf

CONTINUATION OF DD FORM 1423-1 (DI-SESS-81000C/T) Dtd 07 May 2009

BLOCK 4: DI-SESS-81000C is tailored as follows:

Requirements: (the below paragraph numbering corresponds with the numbering in the DID)

1. Delete paragraph 1. in its entirety and replace with “1. Reference Documents: The documents apply as cited in the DD Form 1423-1 and continuation sheets."

2. General. Delete “Product Drawings/Models and Associated Lists shall meet the requirements of

MIL-DTL-31000C.” and replace with “Product Drawings/Models and Associated Lists shall meet the requirements of the DD Form 1423-1 and continuation sheets.

3. Format: Delete in its entirety and replace with “3. Format: Product Drawings/Models and Associated Lists shall be in the format as specified on this DD Form 1423-1 and continuation sheets, and shall meet the requirements of ASME Y14.1."

4. Content: delete in its entirety and replace with 4. Content: Product Drawings/Models and Associated Lists shall conform to the requirements of ASME Y14.100, Appendix B, sections B6 through B9.1 and Appendices C,D and E, in conjunction with ASME Y14.24, ASME Y14.34M, ASME Y14.35M and ASME Y14.41. They shall document directly or by reference the following (items a through q), as applicable:”

6. CAGE: Delete “TDP Option Selection Work Sheet incorporated in the contract or purchase order.” and replace with “DD Form 1423-1 and continuation sheets.”

7. Selection of drawings: Delete “The TDP Option Selection Work Sheet incorporated in the contract or purchase order will specify whether the contractor or the Government is responsible for selecting the types of drawings and associated lists.” and replace with “The contractor shall comply with ASME Y14.24, Types and Applications of Engineering Drawings.

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. Distribution statements shall be in accordance with DoD Directive

5230.24 and included on the first sheet of each drawing near the title block, and shall be as follows:

“DISTRIBUTION STATEMENT C. Distribution authorized to U.S. Government Agencies and their contractors (Administrative or Operational Use) (07 May 2009). Other requests for this document shall be referred to (782 CBSG/GBED).”

Note: Certain types of technical data preclude placing the entire notice on the document. To accommodate this problem an abbreviated version is authorized as follows:

“Statement C, Gov’t and contractors, (782 CBSG/GBED)”

EXPORT CONTROL NOTICE. The Export Control Notice shall be in accordance with DoD Directive 5230.25.

DESTRUCTION NOTICE. Mark documents with one of the following:

a. For unclassified limited documents: “DESTRUCTION NOTICE. Destroy by any method that will prevent disclosure of contents or reconstruction of the document.”

b. For classified documents: “DESTRUCTION NOTICE. Follow the procedures in DoD 5220.22- M, National Industrial Security Program Operating Manual, Chapter 5, Section 7, or DoD 5200.1R, Information Security Program, Chapter 6.”

BLOCK 10: Revisions/changes to the final delivered data shall be furnished quarterly, commencing the first quarter after destination acceptance of the final reproducible data and continue until the contract is closed. Quarterly updates shall include an updated IDL, reference A.F. Drawing 9579776. Negative reports shall be submitted to 584 CBSS /GBHAD.

BLOCK 11: 15 days before end of quarter.

BLOCKS 12 AND 13:

1. All data submittals shall contain a shipping list prepared to include as a minimum, the document number, revision level, and number of sheets/pages. Part number, noun and drawing size is optional. The data delivered shall be in the same sequence as the shipping list. Unless prior approval is granted by 584 CBSS /GBHAD, shipments of data must be for complete assemblies, i.e., LRU’s and SRU’s. Shipping list shall specify whether the shipment is updates, final or make-up.

2. When a specific revision of an engineering document has been previously furnished and approved by a USAF Engineering Data Repository in microfilm or digital form as a result of a government contract, and is required by this DD Form 1423-1, the same data shall not be resubmitted providing it meets the requirements in the DD Form 1423-1 for existing data. This data shall be identified as having been previously submitted and approved and shall include the document number, revision, and contract number under which the data were submitted. The receiving USAF Engineering Data Repository shall be identified. This action is required concurrent with all submittals.

3. Within 90 days after successful government verification of the prototypes, an Indentured Data List (IDL) per Air Force (CAGE 98752) drawing 9579776 shall be delivered.

4. Within 90 days after successful government verification of the prototypes, one set of paper copies of all "final reproducible data" (reference Block 14 of the DD 1423-1) shall be delivered. A letter of transmittal shall accompany submittal. Paper copy submittal will be reviewed within 120 days after receipt of data, unless additional time is required, at which time the contractor will be notified.

a. Submittal of programming files, per Air Force (CAGE 98752) drawing 9579776, Software and memory Device Data is not required for this (paper) submission.

b. Concurrent with the paper copies the contractor shall submit representative samples of each digital data format of data for this project per Air Force (CAGE 98752) drawing 9579776, (ProEngineer Native, Neutral, HPGL, Metadata Spreadsheet, Gerber, Software/Memory Device Data, etc.).

5. Within 60 days after approval of paper copy, one set of all “final reproducible digital data” to include ProEngineer Native, Neutral, HPGL, Metadata Spreadsheet, Gerber, Software/Memory Device Data, etc.

(reference Block 14 of the DD 1423-1) shall be delivered to 584 CBSS/GBHAD, 460 Richard Ray Blvd Suite 200, Robins AFB GA 31098-1813. If changes have been required to the IDL since delivery in 3 above, resubmittal shall be required.

BLOCK 16:

1. Government Activity and Part Identification: The contractor shall comply with Air Force (CAGE 98752) drawing 9626025, titled “Air Force Drawing Requirement”. This requirement defines format requirements for the generation of Air Force drawings.

1.1. Engineering Change Orders (ECOs): When an existing Air Force drawing is revised, all ECOs shall be incorporated prior to the paper submittal for review. Concurrent with the final submittal, all ECOs shall be incorporated and a hardcopy delivered.

2. Content, format, and media requirements for delivery of Digital Engineering Data: The contractor shall comply with Air Force (CAGE 98752) drawing 9579776.

3. Engineering Data: Product Drawings/Models and Associated Lists shall document complete item design and manufacturing processes necessary to obtain and test hardware to the lowest component part that can be procured as a separate entity. This includes but is not limited to special tooling, interface hardware, special test equipment, and support equipment.

4. Engineering Drawing Practices: The contractor shall use the practices described in ASME Y14.100-2004. For clarification, the documents listed in paragraph 2 of ASME Y14.100-2004 shall be considered first tier and shall apply. ASME Y14.1-1995 is tailored as follows: Paragraph 6.2 Block L, add “Sheets shall be numbered beginning with one (1) and continue, using consecutive whole integers.” The contractor may find it useful to incorporate the concepts of MIL-HDBK- 288 into the preparation of the TDP. MIL-HDBK-288 refers to Engineering Drawing Package (EDP); this term shall be considered synonymous with TDP.

5. Control Drawings: Control drawings shall be used to specify the requirements for purchased items per DI-SESS-81000C and ASME Y14.24. The contractor shall not identify his own company as a source on control drawings, unless one additional source is also shown. A separate division of the contractor’s company, with a different manufacturers code (CAGE) may be shown, if it is actually a source. Control drawings not developed for this contract (existing drawings) shall be updated, to show current information (i.e., performance/qualification requirements, vendors/sources names and part numbers.)

6. Commercial Off-the-Shelf (COTS): Definition for a COTS item can be found in the Federal Acquisition Regulation (FAR SUBPART 2.1-Definitions) Part 2.101 and (FAR) Part 12. For clarification of this effort, any modification/tailoring of the COTS item shall require a modifying drawing be prepared and delivered to the Air Force documenting the comparison of the COTS item and the item after modification.

7. Contract Numbers: When a TDP document is prepared under a Government contract, the Government contract number under which it is prepared shall appear on the first sheet of the document original. When a TDP document is delivered under a Government contract other than the one under which it was prepared, the Government contract number under which it is delivered shall also appear on the first sheet of each copy submitted. If the document is prepared and submitted under the same contract, only the entry for the contract under which it is prepared is required.

8. Application Block: All new and revised drawings shall contain an Application Block. The Application Block is mandatory for all drawings. The Application Block shall be near the Title Block. The Application Block shall show the “Next Assembly” and “Used On”. When an item is used in more than three applications, the entry “general usage” may be used.

9. Traceability: The contractor shall prepare the TDP in such a manner to insure that all applicable documents and part or identifying numbers (PINS) i.e., Artwork, Schematics, Software/Programming Data, Test Criteria, etc., are referenced within the TDP for traceability.

9.1 If the contractor is the original equipment manufacturer (OEM) any existing detail and assembly drawings shall be revised to include changes to reflect the delivered item’s configuration.

9.2 If the contractor is not the OEM any existing detail and assembly drawings shall be revised by the contractor submitting an engineering order (EO) to include changes to reflect the delivered item’s configuration.

10. Preparation Method: American English language shall be used in the preparation of this TDP.

Dimensioning and Tolerancing shall be Decimal Inch in accordance with ASME Y14.5M-1994. Size and format of drawings shall be Decimal Inch per ASME Y14.1. All drawings shall be prepared using Third Angle Orthographic Projection method of presentation. The symbol for angle of projection shall be delineated in the Title Block of newly prepared or revised engineering data. (ASME Y14.3M-1994 figure 1-2)

11. TDP Validation: The contractor shall validate that the TDP and elements thereof conform to the contractual requirements, and that they accurately depict the item(s) developed, modified, or produced under the contract. Successful use of the TDP in producing, inspecting and testing the item(s) is considered acceptable evidence that the validation requirement has been met. All models generated from existing 2D drawings must be validated by generating another drawing based off the model and conducting a line check comparison between the original and new drawings.

12. Test Criteria: Test criteria is an inherent part of the TDP. Test criteria shall be incorporated, either directly on each TDP document or by reference, for each end item, top assembly item, configured item, and lowest assembled item IAW Air Force (CAGE 98752) drawing 9579777, titled “Clarification of Detailed Test Criteria for Electrical and Avionics Items.”

13. Associated Lists: Parts Lists per ASME Y14.34M are required. Parts Lists are required at assembly level. Parts Lists for Contractor Activity identifier CAGE code may be an integral part of a document or it may be a separate document. The identification and quantity of parts shown on the assembly drawing shall agree with the parts list.

14. Marking: Drawings shall specify requirement for marking part number identification on items as required by MIL-STD-130 and other applicable documents referenced therein. Unique Identification (UID) for item identification marking is mandatory. The drawings shall identify the content, method of application, material and location of marking on the part.

15. Printed Board Artwork Master Drawing. The printed board artwork master drawing shall include images of all artwork required to manufacture the printed board. These images will serve as a reference to those images produced from the Gerber data files IAW Air Force drawing 9579776 (CAGE 98752) titled “Digital Data Description Requirement”. Also, this drawing shall reference a unique part or identifying number (PIN) with revision data for the digital file set which includes the Gerber, test, and drill data files.

The PIN number format structure and characters shall meet the same requirements as for the part number.

These requirements are in addition to those in ASME Y14.24 and other related standards.

16. Printed Board Artwork Master, Test, and Drill NC Data. The printed board artwork master, test, and NC drill data shall be delivered IAW Air Force drawing 9579776 (Cage 98752). These requirements are in addition to those in ASME Y14.24 and other related standards.

17. Source Control Drawings: Air Force engineering will evaluate each request and notice will be promptly given regarding approval/disapproval. Letter requests shall be submitted to the requiring office in Block 6 of this DD Form 1423-1 prior to the preparation or use of a Source Control Drawing. The letter shall be marked with Distribution Statement “A” in accordance with DoD-D-5230.24. Preparation instructions are as follows:

a. Format - The Source Control Drawing Approval Request shall be in the contractor’s format.

b. Content - The request shall specify the following:

(1) Nomenclature and description of the item.

(2) The critical application(s) for which the item is to be used.

(3) Number of applications per end item.

(4) Item status as a repair part.

(5) System performance requirements requiring source qualification.

(6) Procedures and criteria required to qualify a source.

(7) Sources of supply and manufacturers’ part numbers.

(8) Cost of the item involved.

(9) Estimated cost to qualify a source.

(10) Impact on contract cost, schedule and performance if use of source control drawing is not permitted.

(11) Copy of the approved non-standard part approval request, if the DoD Parts Control Program is applicable under the contract or purchase order.

18. Existing/Legacy Data: When existing/legacy data meets the following criteria, or will be modified or revised to meet the following criteria, it shall be used in lieu of preparing new data.

a. It is furnished with rights-in-data consistent with the contract stipulations regarding data rights;

b. It is furnished at a cost to the government equal to or less than preparing new data;

c. It meets the legibility and reproducibility requirements for the TDP element of which it is to be a part;

d. It meets the design disclosure requirements of the TDP element of which it is to be a part;

Note: The contractor shall ensure the existing/legacy data contains current information, i.e. performance/qualification requirements, vendors/sources names and part numbers, etc.

e. It is identified by a Commercial or Government Entity (CAGE) Code, document number, title and applicable contract number(s);

f. Any nonstandard symbols, drawing or documentation practices used are explained in the document or in a document referenced on the document containing the nonstandard symbol or practice;

g. The TDP was prepared using American English Language.

Note: Revisions to existing Government CAGE non CAD data shall be redrawn in AutoCad and shall meet the contractual requirements for new Air Force drawings per Air Force Drawing 9626025, CAGE 98752.

19. Legibility and Reproducibility: All documents prepared or submitted shall meet the highest legibility and producibility requirements available in the commercial market controlling the media in which the data is to be delivered.

20. Referenced Documents: Documents referenced in a TDP shall be furnished as an integral part of that TDP except where the documentation meets the requirement of the paragraph titled Existing Data above, and has been furnished and approved under a previous contract in the same revision to any USAF repository.

When first tier references do not provide the technical information required by the TDP element, subordinate reference documents shall be provided until the design disclosure requirements are met. When information essential to meeting TDP design disclosure requirements (such as default surface texture values) are contained in such documents, that information shall be incorporated in a document acceptable for inclusion in the TDP.

20.1 Prohibited References/Wording: Technical Orders (TOs), pamphlets, recordings, National Stock Numbers (NSNs), To Be Determined (TBD), Statement of Work (SOW), Performance Work Statement (PWS), Statement of Objectives (SOO), and Contract Data Requirements List (CDRL), shall not be referenced within the TDP.

21. Protecting Classified Information: TDPs or parts thereof, containing classified information shall be protected and marked in accordance with the Department of Defense National Industrial Security Program Operating Manual for Safeguarding Classified Information, DoD Manual 5220.22-M. When 3D TDP data is used, the solid models shall display classification marking clearly visible when the solid model is first opened.

22. Software and Memory Device Data: Software and Memory Device drawings shall be selected per ASME Y14.24 and CAD/CAM data files shall be delivered per Air Force drawing 9579776 (CAGE 98752).

23. Contractor Quality Control System: The contractor shall develop and maintain a quality control system for the detailed examination and technical review of the TDP, to be supplied under the terms of the contract or purchase order. The quality control system shall assure conformance of the TDP to all requirements specified herein. The quality control system shall be documented and subject to review by the Air Force's representative. If the contractor's methods and procedures do not comply with the quality control system or do not attain their objectives, the quality control system shall be subject to disapproval by the Air Force.

24. TDP Quality Control System Requirements: The contractor's TDP quality control system shall address:

a. The methods and procedures to be used to control the development, maintenance and delivery of the TDP, including the use of electronic approvals or authorizations, if applicable.

b. Assignments of responsibilities and procedures for the detailed examination, review and final approval of the TDP by the contractor.

c. Qualifications of the personnel performing the examinations and reviews of the TDP.

d. Procedural flow of information and documentation within the organization for the development, review and approval processing of the TDP and components thereof.

e. Procedures for ensuring that nonstandard items used in the design have been documented as required for the TDP.

f. Methods of ensuring that approved engineering changes have been incorporated into the TDP in accordance with contract requirements.

g. Procedures for ensuring that security markings, distribution statements, and rights-in-data legends are assigned and applied in accordance with applicable specifications, standards, regulations and public laws.

h. Methods of detecting, correcting, and preventing the recurrence of deficiencies with the TDP and discrepancies between the elements and components thereof.

25. Inspection of TDP: The TDP type and elements including TDP documents prepared by subcontractors, shall be inspected for the following:

a. Compliance with the requirements of this contract.

b. Inclusion of all documents, including sub-tier references, required to meet the design disclosure requirements of the TDP.

c. Accuracy of the assignment and identification of security markings, restriction statements (for example distribution statements), export control notices, rights-in-data legends, and other special markings.

d. Inclusion of contract numbers and contractor identifications.

e. Legibility and reproducibility.

f. TDP components have not been prepared for requirements, which could be met by existing standardization documents.

g. Completeness and accuracy of the TDP documents, including required quality assurance information, in describing design of the item, its subassemblies, and component parts. The design to be described by the TDP documents is that configuration of the item the Government has approved, tested, or accepted.

h. Both Type 2D and Type 3D TDPs shall open in the appropriate software without regeneration errors or warnings.

i. Compliance with IUID regulations.

TM-86-01M 1 August 2006 1

Air Force Technical Manual Contract Requirements (TMCR) for

11W1-7-17-2/11W1-7-17-4 F-15 Intermediate Maintenance Instructions/Illustrated Parts Breakdown 20MM Linear Feed System 634L680 Automatic Lubricator 175F479

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT:

Date: 28 Apr 2009 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, ma-trices 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 (11W1- 7-17-2/11W1-7-17-4 F-15 Intermediate Maintenance Instructions/Illustrated Parts Breakdown, 20MM Linear Feed System 634L680 Automatic Lubricator 175F479)

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 11W1-7-17-2/ 11W1-7-17-4, F-15 Intermediate Maintenance Instructions/ Illu-strated Parts Breakdown 20MM Linear Feed System 634L680 Automatic Lubricator 175F479 program objectives.

3. Commercial Manuals. (T) N/A

4. Technical Manual Specifications and Standards (TMSS) Tailoring. TMSS are tailored by selecting between options offered in para 6.2 of each TMSS. The tailoring is recorded in SIRs and added to Sec-tion 3 of this document for each TMSS required. NOTE: Tailoring must not change or delete mandato-ry 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 com-plete 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 require-ments as modified by the options in paragraph 6.2.

4.2. Questions concerning TMSS requirements may be resolved by written request and justified sugges-tions for resolution submitted through the PCO and (Gregory Doss, 569 ACSS/GFIA, 235 Byron St., 31098-1670, phone 478-327-6377). Deficiencies and suggested improvements shall be submitted to the TMSS Preparing Activity (PA). Approved recommendations, corrections and clarifications will be maintained with contract documentation.

5. Subsequent TO/Data Requirements. Offerors shall propose a process for notifying the government when additional TO or source data requirements are identified subsequent to contract award. This process shall require government review and approval of recommended additional requirements prior to contractual approval.

2 TM-86-01M 1 August 2006

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) (http://www.ide.wpafb.af.mil/toprac/polinfo.htm) 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-38784, Stan-dard 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 contractor shall develop TO files (tagged instances) using Standard Generalized Markup Language (SGML) ac-cording 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 Stan-dards (TMSS) web page (http://www.ide.wpafb.af.mil/tmss/index.html.). NOTE: Illustration files de-veloped and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible.

6.3. (T) N/A

6.4. (T) N/A

6.5. (T) N/A

7. TO Numbering. (T) N/A

8. Data Rights. (T) Offerors shall propose Unlimited Rights for all source data and TOs prepared spe-cifically for the contract.

8.1. (T) N/A

8.2. (T) N/A

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. (T) Offerors shall include an “D” Distribution Statement IAW DoD 5230.24, on the title page of each manual being devel-oped The markings and notices shall be reviewed during In-Process Reviews (IPR).

DISTRIBUTION STATEMENT D – Distribution authorized to the Department of defense and U.S. DoD contrac-tors only (Critical Technology) (15february 2006). Other requests for this document shall be referred to 569 ACSS/GFIA, 235 Byron Street, Suite 19A, Robins AFB, GA 31098-1670

10. TO Quality. Offerors shall propose a quality assurance program which ensures TOs are prepared IAW this contract. 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 equip-ment. Offerors’ proposals shall describe how the government will be allowed to interact with the con-tractor’s TO development team.

10.1. Conferences and Technical Reviews. (T) Technical reviews of the Manuals will be held in accor-dance with Section 2, Part B of this document.

10.2. TO Certification. (T) Offerors shall propose offer written confirmation of their method for docu-menting certification that TO procedures are accurate, adequate, current, and usable for their intended purposes.

TM-86-01M 1 August 2006 3

10.3. Verification Support. (T) Offerors shall propose the methods, equipment and personnel required to support government TO Verification. This support should consist of at least (Technical manual and Engineering support

10.4. Technical Data Assessment (TDA – originally called First Article Testing). The program office, with the assistance of 569 ACSS/GFIA 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 IPR, for TDA to verify compliance of the digital files to Air Force DSSs. The contractor shall deliver a representative percentage of Indexed Portable Document Format (IPDF) TO files to verify indexing compliance with the Technical Order Conversion Require-ments (TOCR). Repeat TDAs shall be required whenever new DSS or DTD versions are used for TO development.

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

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

12. TO Delivery. (T) Offerors shall propose Delivery Requirements IAW Matrices included in Section 2 of this document.

12.1. SGML-Tagged Files. (T) 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.

12.2. SGML-Tagged Files for Use with the eTO Viewer. (T) N/A

12.3. Interactive Electronic Technical Manuals (IETM). (T) N/A

12.4. Indexed Adobe™ Portable Document Format (IPDF) Files. (T) The contractor shall validate in-dexing of IPDF TO files using the specifications contained in the Technical Order Conversion Require-ments (TOCR).

13. Schedules. (T) Offerors shall include TO program events and program management schedules NOTE: AF policy requires delivery of verified TOs prior to or concurrently with delivery of operation-al equipment to the field (AFI 21-303). This policy will determine TO development and delivery sche-dules throughout the acquisition phase of a program.

14. Time Compliance Technical Orders (TCTOs). (T) N/A

15. TO Reproduction Management. (T) N/A

16. Program Specific Requirements. (T) The Offeror shall propose the complete Revision for the 11W1-7-17-2, F-15 Intermediate Maintenance Instructions 20MM Linear Feed System 634L680 Auto-matic Lubricator 175F479 and 11W1-7-17-4, Illustrated Parts Breakdown 20MM Linear Feed System Part Number 634L680 into Work Package Format IAW MIL-DTL-87929 with Illustrated Parts Break-down incorporated. The T.O. source data shall be prepared and submitted in accordance with the CDRL and this document. The contractor shall host and conduct a T.O. Guidance Conference and Reviews in accordance with the CDRL within 60 days of the contract award to discuss any issues or concerns the Offeror may have with the requirements. This meeting may be face-to-face or teleconference depending upon the complexity of the issues to be discussed. The contractor shall develop and maintain T.O. Status and Schedule (TOSS) and present TOSS at all design reviews, program reviews and in-process reviews.

The T.O. source data shall be approved and validated on the F-15 aircraft by the Government prior to final submittal. The contractor shall host a minimum of two in-process reviews. The new source data shall be submitted in digital format in accordance with CDRL.

4 TM-86-01M 1 August 2006

16.1 (T) New manuals delivered for this contract shall be a mixture of both paper based and digital documents during the development and both a paper copy and digital files in SGML formats for final delivery. Data delivered for TCTOs shall be in native format. NOTE: Native format refers to the desk-top publishing system used to develop the documents i.e., Framemaker, Microsoft Word, Word Perfect, etc. All Graphics files shall be delivered as either Group 4 compressed TIF format for raster graphics or, Autocad for vector graphics. Graphic resolution shall be a minimum of 600 DPI. Graphics files shall be delivered as separate files regardless whether they are embedded in the documents or not. Digi-tal photographs (halftones) shall NOT be used. All graphics shall be line artwork. In-Process reviews shall be held at the 35% and 70% completion point for each manual under development. Comments generated during ALL development reviews shall be incorporated before scheduling the next develop-ment review, for example 35% IPR comments shall be incorporated before scheduling the 70% IPR. All electronic files delivered on this project shall be unprotected and allow unlimited access to change/modify/or capture the data from the files.

TM-86-01M 1 August 2006 5

AFTO FORM 124, 19970401 (IMT-V1) PREVIOUS EDITION IS OBSOLETE.

COMPUTATION OF TECHNICAL ORDER READING GRADE LEVEL

1. T.O. TITLE: F-15 Intermediate Maintenance Instructions 20MM Linear Feed System 634L680 Automatic Lubricator 175F479

2. T.O. NUMBER

11W1-7-17-2

3. T.O. DATE

4. NUMBER OF PAGES OF TEXT IN T.O 7. T.O. MANAGER /OFFICE SYMBOL/DSN

569 ACSS/GFIA

235 Byron Street Suite 19A Robins AFB, GA 31098-1670

5. READING GRADE LEVEL IAW MIL-STD-38784

6. COMPUTED OVERALL GRADE LEVEL OF T.O.

8. TO COMPUTE READING GRADE LEVEL (RGL) OF T.O., USE "READABILITY" CRITERIA PRESCRIBED BY MIL-STD-38784 OR RECORD THE

COMPUTER-DERIVED RGL WHEN AVAILABLE.

SAMPLE NUMBER A

PAGE NUMBER OF

SAMPLE B

NUMBER OF WORDS

IN SAMPLE C

NUMBER OF

SENTENCES IN

SAMPLE D

NUMBER OF

SYLLABLES IN

SAMPLE E

SAMPLE GRADE

LEVEL F

9. PROJECT OFFICER GRADE OFFICE SYMBOL PHONE

10. SIGNATURE DATE

6 TM-86-01M 1 August 2006

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

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

• 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 requirements to be levied on engineering data for preparation of end item wiring data and schematic diagrams.

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

PART A – TM TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE 11W1-7-17-2, F-15 Intermediate Maintenance Instructions with Illustrated

Parts Breakdown

Title or Type of Manuals Specification Required

1. Inspection TOs MIL-DTL-87929

2. Work Unit Code Manual MIL-PRF-38769

3. Time Compliance Technical Orders (TCTOs) MIL-PRF-38804

4. Illustrated Parts Breakdown MIL-DTL-87929

TM-86-01M 1 August 2006 7

TABLE 2

ADDITIONAL TM TYPE SELECTIONS

NOTES:

• Check all applicable boxes.

• 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. 11W1-7-17-2 MILDTL87929

2.

3.

4.

5.

6.

7.

8.

9.

10.

11.

12.

13.

14.

15.

16.

17.

18.

19.

PART B - TM DELIVERY REQUIREMENTS

8 TM-86-01M 1 August 2006

FOR 11W1-7-17-2, F-15 INTERMEDIATE MAINTENANCE INSTRUCTIONS 20MM LINEAR FEED

SYSTEM 634L680 AUTOMATIC LUBRICATOR 175F479

TM DATA TYPE DELIVERED CHANGES .

(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 Review(s) (30 Days)

Verification (30 Days)

Prepublication Review

(30 Days)

Final TO Distribution (60 Days)

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

569ACSS/GFIA

Attn: Gregory Doss 235 Byron ST.

ROBINS AFB GA 31098-1670

P / 1 P / 1 P / 1 M(G) / 1

782 CBSG/GBED

Attn: Mark McMullan 460 Richard Ray Blvd. STE 200 Robins AFB, Ga 31098-1813

P / 1 P / 1 P / 1 M(G) / 1

782 CBSG/GBLE

Attn: George Dobney 460 Richard Ray Blvd. STE 200 Robins AFB, Ga 31098-1813

P / 1 P / 1 P / 1 M(G) / 1

Total Copies Required: 3 3 3 3

TM-86-01M 1 August 2006 9

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 in-cluded in the final contract, unless the entire SIR is not applicable

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

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

STANDARDIZATION 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

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

10 TM-86-01M 1 August 2006

5. Replace with: “5. PACKAGING.

“5.1 Packaging Requirements. For acquisition purposes, the packaging requirements shall be as spe-cified 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 ac-tivity 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).

STANDARDIZATION 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 “Le-gend” 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 Illu-strated 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 1st 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 pro-prietary data must be marked with the company name and the word “Proprietary” (e.g., “Boeing Proprie-tary”).”

4.5.1.13 Destruction Notice. Change the existing sentence to read: "...or X shall be marked with Handling and De-struction 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" (be-low) 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."

TM-86-01M 1 August 2006 11

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

* 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 ac-cordance 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 other-wise 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, letter-ing, 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.

STANDARDIZATION 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 1st 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 1st sentence to read: “…acquiring activity on an AFMC Form 873 (see 6.5).”

12 TM-86-01M 1 August 2006

3.5.2.6 Change 1st 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).”

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 ac-complished 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 re-strict operations or shall be justification for withdrawing affected system/equipment from service until com-pliance 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 hav-ing 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 af-fected 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…