TM-86-01N_NDI.pdf

TM-86-01N 27 Aug 13 1 NDI Rewrite

Air Force Technical Manual Contract Requirements (TMCR) for

1F-15A-36 Non-Destructive Inspection (NDI) Rewrite

ATTACHMENT TO CDRL SEQUENCE NUMBER:

REQUEST FOR PROPOSAL/CONTRACT:

Date: 27 Aug 13 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 (T). This TMCR document, including the associated tables, matrices and Specifica-tion/Standard Interface Records (SIRs) have been tailored specifically, for the NDI Rewrite Program Requirements. Proposals shall be compatible with the Air Force infrastructure and support the NDI Re-write. Air Force TO Acquisition procedures, including procedures for tailoring this document, are found in TO 00-5-3, AF Technical Order Life Cycle Management. A copy is available upon request from the TO Manager. Any terms or procedures found in this document may be researched there.

2. TO Program Scope (T). The Offeror may recommend tailoring for 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 NDI Rewrite program’s objectives. All recommended tailoring shall be submitted through the Air Force PCO for consideration and/or approval/disapproval. No tailoring shall be made to these requirements without prior approval of the TM Manager and Primary Con-tracting Officer (PCO).

3. Commercial Manuals (T). N/A

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 (T). N/A

4.2 (T). Questions concerning TMSS requirements may be resolved by written request and justified suggestions for resolution submitted through the Procuring Contracting Officer (PCO) and TO Man-ager. 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 (T). Offerors shall propose a process for notifying the govern-ment when additional TO or source data requirements are identified subsequent to contract award. This process shall require government review and approval of recommended additional requirements prior to contractual approval. NOTE: The recommended notification process is to use CFAE/CFE Notices (DI-

TMSS-80067).

2 TM-86-01N 27 Aug 13

Prepared by Tim Martin\AFLCMC/WWQA\478-926-7039

6. TO Development (T). The Offeror shall propose TO development practices and procedures that ensure TOs and data are compatible with the NDI Rewrite Program objectives. In addition, TOs shall be written to a scope and depth of coverage sufficient to support the operations and maintenance concepts specified in MIL-STD-38784A, Standard Practice for Manuals, Technical: General Style and Format Require-ments.

6.1. Page-oriented Military Specification (MIL-SPEC) TOs shall be formatted with text, graphics and delivery according to the TMSS specified in Section 2. The contractor shall develop TO files (tagged instances) using Standard Generalized Markup Language (SGML) according to the DTDs referenced in the appendix to MIL-STD-38784A and each applicable military detail or performance specification (MIL-DTL or MIL-PRF). All deliveries of SGML data shall be in a single file instance. Multiple file instances are not authorized.

6.2 (T). SGML-tagged TO files shall include required illustration (graphics) files in an approved graphics exchange format. Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible. (See Graphics Format Rec-ommendations sheet Attachment 1 to this document)

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). If some TOs or source data are copyrighted or contain proprietary data or procedures, Offe-rors 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 252-7103, 7015 or 7016.

8.2 (T). N/A

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices (T). The offeror shall use the below statements for each TO developed.

DISTRIBUTION STATEMENT D - Distribution authorized to Department of Defense and U.S.

DoD contractors only (Critical Technology) (XX Month XXXX). Refer other requests for this document to AFLCMC/WWQA, 235 Byron Street, Suite 19A, Robins AFB GA. 31098-1670.

WARNING - This document contains technical data whose export is restricted by the Arms Ex-port Control Act (Title 22, U.S.C. 2751, et seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401, et seq. Violation of these export-control laws is subject to severe criminal penalties. Dissemination of this document is controlled under DoD Directive 5230.25.

TM-86-01N 27 Aug 13 3

HANDLING AND DESTRUCTION NOTICE - Destroy by any method that will prevent disclo-sure of contents or reconstruction of the document.

10. TO Quality (T). Offerors shall propose a quality assurance program which ensures TOs are pre-pared 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 reserved 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.

10.1. Conferences and Technical Reviews (T). Offerors shall propose sufficient conferences and reviews to allow insight into TO development processes and ensure contract compliance. Offerors shall participate in an initial Guidance Conference or Technical Interchange Meeting (TIM) within 30 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. 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 (T). Offerors shall propose the methods, equipment and personnel re-quired to support government TO Verification. This support should consist of at least engineering and technical publications personnel available to resolve questions resulting from verification activi-ties.

10.4. Technical Data Assessment (TDA – originally called First Article Testing) (T). The TO Manag-er, will determine the TDA requirements for each TO type. The contractor will submit an SGML-tagged TO file, separate graphics files, and a PDF rendition of the composed SGML File to the program office concurrent with each IPR, for TDA to verify compliance of the digital files to Air Force DSSs. Additional TDAs will be required at each succeeding review. The TDA parsing in no way relieves the contractor from correcting tagging errors that are noted during the composing effort.

Repeat TDAs shall be required whenever new DSS or DTD versions are used for TO development.

The contractor shall deliver the SGML files, Graphics Files, and the IPDF output from these files for each review.

11. TO and Source Data Maintenance. Offerors shall propose methods for maintaining accuracy, cur-rency and configuration of existing AF TOs and source data throughout the contract period of perfor-mance. 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 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 shall be according to applicable CDRLs and the tailored TM Delivery Requirements Matrices included in Section 2 of this document.

4 TM-86-01N 27 Aug 13

Prepared by Tim Martin\AFLCMC/WWQA\478-926-7039

12.1. SGML-Tagged Files (T). The contractor shall parse and compose SGML-tagged TO docu-ment files prior to delivery to the government, and verify that content tagging has been accomplished to the levels provided in the DTD. NOTE: The Government will perform completeness checks of all SGML data prior to acceptance. Any data failing final acceptance shall be returned to the con-tractor for correction then returned to the Air Force for additional testing to the Government.

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 indexing of PDF TO files using the specifications contained in the Technical Order Conversion Re-quirements. A copy is available upon request from TO Manager.

13. Schedules (T). The Offeror shall include Technical Order program events and schedules in their proposed Integrated Master Plan (IMP) and Integrated Master Schedule (IMS). Update the IMS throughout the period of performance of this contract. NOTE: AF policy requires delivery of verified TOs prior to or concurrently with delivery of operational equipment to the field (AFI 63-101, Ac-quisition and Sustainment Lifecycle Management). This policy will determine TO development and de-livery schedules 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.

A. The Offeror shall develop and deliver MIL-SPEC technical manuals covering all Technical Manuals affected, IAW Section 2, TO types (Table 2) in SGML format to support NDI rewrite.

B. The manual(s) shall be developed using the latest version of the development specifications listed in Table 2 of this document. Data delivered for this contract shall be digital files.

C. SGML files shall be reviewed by the Air Force during the development process to ensure compliance with the approved DTDs. The contractor shall submit copies of their SGML Instance, PDF file of their SGML Instance and separate graphics files use with the SGML Instance for each In-Process review.

D. For Graphics formats, see “Graphics Format Recommendations” Attachment 1 to this document, (page 10). These recommendations provide wide latitude for developing and delivering graphics. The Contractor shall select one method from these recommendations to prepare and deliver all graphics files.

Graphic resolution shall be a minimum of 300 DPI. Graphics files shall be delivered as separate files regardless whether they are embedded in the documents or not.

E. In-Process reviews shall be held at the 35% and 75% completion point for each manual under devel-opment. Sample In-Process Completion tables are provided on page 11, Attachment 2.

F. Comments generated during ALL development reviews shall be incorporated before scheduling the next development review, for example 35% IPR comments shall be incorporated before scheduling the

TM-86-01N 27 Aug 13 5

75% IPR. The Contractor shall provide technical and engineering personnel to assist Air Force person-nel during the development reviews and Verification.

NOTE: Contractors are responsible for selecting SGML and composition tools for this program.

AF DTDs will work with most COTS SGML editing systems (except Framemaker) however, the FOSIs were developed to work with Datalogic Composing software ONLY. If the Contractor wishes to use any other composing software product, the Contractor is responsible for ensuring all formatted outputs are compatible with the DTL specification listed in Section 2, Table 1 of this document. Structured Framemaker files are unacceptable and shall not be submitted as an SGML delivery to the Air Force.

6 TM-86-01N 27 Aug 13

Prepared by Tim Martin\AFLCMC/WWQA\478-926-7039

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

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

PART A – TM TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE NDI Rewrite Program

NOT APPLICABLE

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

TM-86-01N 27 Aug 13 7

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

• 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

Specifications

Com-mercial Manual

Change/ Revision

Supple-ment

Supple-mental

TM

Source Data

1. 1F-15A-36

MIL-STD-

38784A and

MIL-DTL-

87929D

8 TM-86-01N 27 Aug 13

Prepared by Tim Martin\AFLCMC/WWQA\478-926-7039

PART B - TM DELIVERY REQUIREMENTS

FOR 1F-15A-36 Non-Destructive Inspection (NDI) Rewrite

TM DATA TYPE DELIVERED REVISION.

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(6 0 Days)

Enter Office Symbol and Address

Enter delivery requirements code/copy quantities required

AFLCMC/WWQA

Attn: Tim Martin 235 Byron St. Ste 19A Robins AFB, GA 31098-1670

G/I / 2

G/I / 2 G/I / 2

G/I / 1

Total Copies Required: 2 2 2 1

TM-86-01N 27 Aug 13 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 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-38784A 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-38784A, 25 August 2011

Department of Defense Standard Practice for Manuals, Technical:

General Style and Format Requirements

• 4.2.1c(1) Technical manuals shall be 8-1/2 x 11 inches formatted in double column format.

• 4.6.2 Photographs. Delete paragraph.

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

10 TM-86-01N 27 Aug 13

Prepared by Tim Martin\AFLCMC/WWQA\478-926-7039

Attachment 1 Graphics Format Recommendations

GENERAL GUIDELINES

• Single column graphics should not exceed 51 Picas High by 18 Picas Wide.

• Full page graphics should not exceed 51 Picas High by 42 picas Wide.

• Fold Out graphics should not exceed 51 Picas High (width on foldouts is not important).

• Recommend 300 DPI for all graphics to help decrease file/PDF sizes due to there being really no discernable quality difference over 600 DPI.

• Directorates must know what graphic file types they can utilize and sustain with software availa-ble on hand and request file types to match.

• The 5 most common graphics file types are: EPS, TIFF, CGM, JPEG & DWG. Each is ad-dressed below:

EPS:

• Raster based images will not be saved as EPS.

• EPS files shall not be a mix of vector and raster images. Vector only.

• Any source data (photos used for tracing etc.), used in aiding of creation of EPS (templates, etc.)

will be deleted from illustration prior to saving/exporting.

• If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues.

TIFF:

• B&W raster images should only be saved as Bitmap and not Grayscale, RGB or CMYK.

• Grayscale or Color images (screenshots, etc.) will be saved as such (Grayscale, RGB or CMYK) and will not be bitmap converted using a halftone screen.

• To further aid in file size reduction for storage purposes, images should be compressed using

Group 4 compression when saving/exporting.

CGM:

• Raster based images will not be saved as CGM.

• Any source data used in aiding of creation of CGM (templates, etc.) will be deleted from illustra-tion prior to saving/exporting.

• CGM files shall not be a mix of vector and raster images. Vector only.

• If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues..

• Unless Version 4 is specifically required for hotspots and/or hyper linking, CGMs should be ex-ported as version 3 to increase cross platform compatibility.

DWG:

• Raster based images will not be saved as DWG.

• DWG files shall not be a mix of vector and raster images. Vector only.

• Any source data used in aiding of creation of DWG (templates, etc.) will be deleted from illustra-tion prior to saving/exporting.

• If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues.

JPEG:

• JPEG File format should be used as last resort. Color screenshots/photos should be saved as

TIFFs due possible system compatibility issues.

• B&W Bitmaps should not be saved as JPEGs.

TM-86-01N 27 Aug 13 11

Attachment 2 IPR Completion Percentage Guide

In-Process Review Level: 35% 75% TO Section Percent Complete

TO Title Page 100% - Front Matter - 75% Introduction 100% - General Information 50% 90% Installation Instructions 25% 70% Operation Instructions 25% 70% Theory of Operation 50% 100% Maintenance Instructions 25% 75% Checkout and Troubleshooting - 75% Circuit Diagrams/Illustrations 25% 75% Parts Lists 35% 80%

Section 1. Technical Order (TO) Program Requirements