A009.pdf

Air Force Technical Manual Contract Requirements (TMCR) For

Replacement of Center Wing With Enhanced Service Life Wing on Select C-130J Aircraft (1C-130J-958) (Program/Modification/Military System)

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT:

Date:

08-Aug-2012

TMCR Number:

STAFFORD.WALDON.

W.1147258921

Digitally signed by STAFFORD.WALDON.W.1147258921

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=STAFFORD.WALDON.W.1147258921

Date: 2012.08.08 12:19:44 -04'00'

08-Aug-2012

WR-ALC/GRUEF TOMA DATE

HENSLEY.ANTHONY.A.1135698985

Digitally signed by HENSLEY.ANTHONY.A.1135698985

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=HENSLEY.ANTHONY.A.1135698985

Date: 2012.08.14 12:52:13 -04'00'

14-Aug-2012

WR-ALC/GRUEF FMM DATE

GELINAS.BRUCE.ALLY

N.1146478340

Digitally signed by GELINAS.BRUCE.ALLYN.1146478340

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=GELINAS.BRUCE.ALLYN.1146478340

Date: 2012.08.15 12:46:18 -04'00'

15-Aug-2012

WR-ALC/GRUEF IETM TOMA DATE

SIMONEAU.WILTON.T.

1170386538

Digitally signed by SIMONEAU.WILTON.T.1170386538

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=SIMONEAU.WILTON.T.1170386538

Date: 2012.08.15 13:08:19 -04'00'

15-Aug-2012

WR-ALC/GRUEF TECH DATA LEAD DATE

NOTE: The WR-ALC/GRUEF Tech Data Lead, Mr. Wilton Simoneau, may sign for any TOMA or FMM. It is also permissible for other TOMAS and FMMs to sign for the assigned TOMA or FMM when they are unavailable. Mr. Tim

Bullock is the only approved signature that may be used in lieu of Mr. Wilton Simoneau’s signature as Tech Data

Lead. Once Mr. Wilton Simoneau or Mr. Tim Bullock has digitally signed the TMCR Signature page, the page will be locked and no further signatures or changes allowed.

TM-86-01N 1 April 2009 1

Air Force Technical Manual Contract Requirements (TMCR) For

Replacement of Center Wing With Enhanced Service Life Wing on Select C-130J Aircraft (1C-130J-958) (Program/Modification/Military System)

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT:

Date: 24 July 2012

TMCR NUMBER: 0406

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. [T] TMCR Tailoring. Offerors MUST tailor this TMCR document, including the associated tables, matrices 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 or PWS. Proposals shall be compatible with the Air Force infrastructure and support the

C-130.1 Sustai11meut Program's 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/factshcet.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 C-J30J Sustainment program's objectives.

2.1. [S] General. This Technical Manual Contract Requirements (TMCR) document was prepared to describe the required manuals, delivery instructions, and a compilation of government approved contractor tailored standards and specifications selected for the development and sustainment of

Technical Orders (TOs) for the contract. The TMCR has been tailored by 580 ACSG to add, change or delete requirements specifically for the C-130J Sustai11me11t program, contract number

FA8504-06-D-OOO1. Supplemental (added) and tailored paragraphs are identified with the suffixes

[S] or [T], respectively, to the paragraph number.

2.2. [S] Management and Authorization. The TO Management Agency (TOMA) is the 580

ACSG. Changes to technical order requirements shall be made only with the specific approval of the Procuring Contracting Officer (PCO), 330 ACSG and 580 ACSG. All actions as expressed herein are understood to be within the scope of the contract, unless otherwise noted.

2.3. [S] Order of Precedence. In the event of a conflict between the text of this document and the references herein, government determined requirements shall take precedence.

2.4. [S] Application to Subcontractors/Vendors. The prime contractor shall ensure that all applicable TO requirements of this contract are levied on all subcontractors or vendors. The prime contractor shall ensure that subcontractors/vendors furnish operation and maintenance information applicable to the equipment being modified and/or acquired, including changes, revisions and/or source data, for inclusion of such information in applicable operation and maintenance TOs for the weapon system/equipment which the equipment supports. When a subcontractor or vendor prepares weapon system TOs, the prime contractor shall supply required interface data.

http://www.tinker.af.mil/library/factsheets/factshcet.asp?id-

2 TM-86-01N 1 April 2009

3. Commercial Manuals. For new manuals offeror shall propose the use of existing commercial manuals to the maximum 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) Government 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 commercial 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 5.6 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 mandatory requirements which are part of the Document Type Definition (DTD) structure.

4.1. TMSS Options. (New Data Only) 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. TMSS Issues. (New Data Only) Questions concerning TMSS requirements may be resolved by written request and justified suggestions for resolution submitted through the Procuring

Contracting Officer (PCO) and TOMA 580 ACSG/GFEAH, 235 Byron Street, Suite 19A, Robins

AFB, GA 31098-1647. Deficiencies and suggested improvements shall be submitted to the

TMSS Preparing Activity (PA). Approved recommendations, corrections and clarifications will be maintained with contract documentation.

4.3 [S] Content. Technical Manuals identified in this document are to be delivered to the government during the course of this contract. Updates to existing TOs will be prepared in a similar style and format as the basic TO. TOs identified in Section 2 of this document shall be prepared in accordance with the appropriate detail specification(s), cited in Section 2. The effective date of the documents cited in Section 2 shall be that documented in the DOD Index of

Specifications and Standards (DODISS) as of the date the contract is signed, except when the

Section 2 version is a later date. If a later revision or amendment of the specification or standard is available when the contractor starts preparation of a new Basic TO development or Revision, it shall be used if no additional cost is involved, the schedule is not impacted and the acquiring activity gives approval. The contractor shall recommend use of later-version specifications when beneficial to the government. The exception, using MIL-PRF-38804 as a guide, Time Compliance

Technical Orders (TCTOs) shall be the latest issue in effect when the TCTO is contractually authorized.

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 http://dodssp.daps.dla.mil/assist.htm)

TM-86-01N 1 April 2009 3 to contractual approval. NOTE: The recommended notification process is to use CFAE/CFE Notices

(DI- TMSS-80067).

5.1. [S] Source Data for Interim TOs. Source Data for interim technical order safety or operational supplements and interim urgent action or interim immediate action TCTOs shall be provided by approved secure electronic mail, facsimile transmission, telex, telephone or other rapid means as mutually agreed by acquiring activity and offeror.

5.2. [S] Duplication of Data. The contractor shall insure that TO requirements contained herein do not duplicate other tasks or data requirements of this or other government contracts.

6. TO Development. The offeror shall propose TO development practices and procedures that en-sure 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 coverage sufficient to support the operations and maintenance concepts, and to the Reading Grade Level (RGL) specified in MIL-STD-38784, Standard Practice for Manuals, Technical: General Style and Format Requirements. NOTE: The reading grade level will remain the same for existing manuals.

6.1. [S] Occupational Safety and Health. Using AFI 91-301 (Air Force Occupational and

Environmental Safety, Fire Protection, and Health (AFOSH) Program) and MIL-STD-38784 as guidance, the contractor shall provide occupational safety, health, and fire prevention guidance.

This guidance will include all applicable safety, health and fire prevention requirements contained in OSHA and AFOSH Standards. If there are no applicable standards, the contractor shall use other nationally recognized sources of safety guidance, such as American National Standards

Institute or National Fire Codes (published by the National Fire Protection Association).

6.2. Page Oriented TOs. 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 (tagged instances) using Standard Generalized Markup Language (SGML) according to the DTDs referenced in the appendix to MIL-STD-38784 and each applicable military detail or performance specification (MIL-DTL or MIL-PRF).

6.3. SGML Tagging. 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 Standards (TMSS) web page

(https://techdata.wpafb.af.mil/tmss/index.html, or contact the 754 ILMT via e-mail at

SGMLSupport@wpafb.af.mil). NOTE: Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible.

6.4. [T] IETMs. Interactive Electronic Technical Manuals (IETMs) shall be developed IAW

MIL- PRF-87268 Manuals, Interactive Electronic Technical General Content, Style, Format, and user interaction requirements, and MIL-PRF-87269 Performance Specification for the Support of Database, Revisable-Interactive Electronic Technical Manuals. Additional requirements for

MIL-PRF-87269 and MIL-PRF-87269 are included in the SIR found in Section 3 of this document.

6.5. [T] Non-Government Standards (NGS). The offeror may propose use of Non-Government

Standards (NGS) for development of TOs, but must justify this choice based on life-cycle cost savings to the government and compatibility with existing systems identified in the IDS and the

System Support Plan. If proposing the use of NGS, contact the Procuring Contracting Officer

(PCO) and TO Manager to request guidance.

4 TM-86-01N 1 April 2009

6.6. TMSS DTDs Modification Approval. The contractor shall contact 754 ELSG/ILMT for pre-approval before modifying or developing any new DTDs to support use of NGS, canceled TMSS, or undeveloped TMSS DTDs. If permission is granted, the offeror must submit any proposed

DTDs through the PCO and TO Manager to 754 ELSG/ILMT for validation of TMSS compatibility with approved electronic TO (eTO) viewing solutions. New DTDs shall not be developed in lieu of existing DTDs, including those for legacy TMSS. Rules shall be so constructed that TO output complies with the functional requirements of the associated TMSS, and shall be documented in a SIR. DTDs and rule sets submitted and approved in execution of the contract shall become the property of the Government. Direct questions about the application of

SGML tagging to digital TO files to 754 ELSG/ILMT (SGMLSupport@wpafb.af.mil).

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. [T] Data Rights. Government rights in technical data are specified in the Defense Federal

Acquisition Regulation Supplement (DFARS), paragraphs 227-7102 through 227-7104. Offerors shall propose Unlimited Rights for all source data and TOs or portions thereof first generated solely at direct charge to the contract and Unrestricted Rights to all source data and TOs or portions thereof which have previously been delivered to the Government subject to DFARS 252.227-7015 with the further right to provide these source data and TOs to the Government only with the rights granted pursuant to DFARS 252.227-7013 & -7015.

8.1. [T] If some TOs or source data are copyrighted or contain proprietary data or procedures, offerors may propose Limited Rights or Government Purpose License Rights (GPLR) only.

Proposed commercial manuals should be provided with Unrestricted 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 business rules (tailoring and application methods and procedures) and documented business processes developed for use in TO development. Government data rights shall extend to the common source database, transformation style sheets, and other tools or products used to author or dis- play NGS technical data.

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. Offerors shall determine 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.

9.1. [S] Classification of TOs. The contractor shall classify TOs in accordance with the security classification guides (SCG) provided by the acquiring activity. On small programs that do not have an SCG, the DoD Contract Security Classification Specification, DD Form 254, will be used.

Each change or revision of the SCG or DD Form 254 shall be reviewed by the contractor to determine if the classification of the manuals has been affected. Each time an update is issued to a http://www.e-publishing.af.mil/ http://dodssp.daps.dla.mil/assist.htm)

TM-86-01N 1 April 2009 5 classified manual, the security classification shall be reviewed by the contractor. As a minimum, manuals for which the contractor is responsible shall be reviewed annually. The contractor shall immediately is- sue updates when data classification is upgraded.

9.2. [S] Distribution, Destruction, Disclosure, and Export Control Notices. These notices will be applied to all newly developed technical documentation (including TOs, changes, revisions, commercial manual supplements, and source data) produced or provided under the terms of this con- tract using MIL-STD-38784 and DOD Directive 5230.24 as a guide.

10. [T]TO Quality. Offerors shall propose a quality assurance program which ensures TOs and/or source data are prepared in accordance with this contract. QA methods must include actual performance of procedures and use of desktop 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. NOTE: Quality requirements for the Joint Nuclear Weapons Publications 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. [T] Conferences and Technical Reviews. (New Data Only) Offerors shall propose sufficient conferences and reviews 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. Interactive Task Review (ITR), Source Data

Reviews (SDR), 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 accomplished using the approved viewing presentation system. The TOMA/FMM must be notified 30 days prior to any conferences or reviews. NOTE: PPRs are required for critical safety and nuclear surety procedures TOs, and may be required for other complex procedures TOs.

10.1.1. [S] Conferences and Reviews. The TOMA and the Prime Contractor shall jointly agree to convene any conferences, reviews, or inspections that are within contractual scope and are not specified elsewhere in this TMCR. The contractor shall propose dates for scheduled conferences and re- views to provide 30 calendar days notification to the TOMA. The TOMA and Prime Con-tractor shall schedule such conferences, reviews, or inspections to provide a minimum of 30 calendar days notification to all participating activities. Conferences and reviews are to control and man- age the program and to oversee the TO preparation process and shall be held at the facility of the contractor, subcontractor or vendor responsible for development of the data.

10.1.2. [S] Minutes. The Contractor shall prepare minutes for all TO related meetings. The

TOMA or designated representative will review and approve the minutes prior to distribution in accordance with the CDRL. The Contractor shall maintain a complete file of these minutes.

10.1.3. [S] In-Process Review. (New Data Only) When an IPR is required, as mutually agreed to by the Contractor and TOMA, the Contractor shall prepare and provide draft copies of

Preliminary TOs, Changes, Revisions, Supplements and source data for review 30 days prior to the scheduled In- Process review.

10.1.4. [S] Pre-Publication Reviews (PPRs). When a PPR is required the Contractor shall prepare and provide draft copies of Preliminary TOs, Changes, Revisions, Supplements, and or

6 TM-86-01N 1 April 2009 source data for pre-publication review 30 days prior to the scheduled PPR. Upon completion of the PPR and incorporation of PPR comments, the contractor shall make preparation of reproducible media for final delivery. PPRs shall be grouped by TO types, series and location.

The TOMA may waive the PPR review on a TO-by-TO basis.

10.1.4.1 [S] Source Data Reviews (SDR). When a SDR is required the contractor shall prepare and provide source data for review 30 days prior to the scheduled SDR. Upon completion of the

SDR and incorporation of SDR comments, the contractor shall prepare for final delivery as directed by the government on reproducible media or integration into the IDET.

10.1.5 [S] Interactive Task Review (ITR) The contractor shall integrate government Central

Technical Order Control Unit (CTOCU) personnel into the development process. During the maturity of the IETM database, the contractor is responsible for the development of all the data, and CTOCU personnel will evaluate the data during the development. The contractor will provide CTOCU personnel access to the developmental IETM database. ITRs will be conducted to ensure developmental issues have been resolved and to verify all requirements have been met.

The contractor shall host and co-chair ITRs to ensure that the IETM database and additional data development is being developed in accordance with the contract and cited specifications. ITR intervals and completion criteria will be as stated in paragraph 10.1.1.1. Additional ITRs may be required based on the contractor's or government's evaluation of the IETM database and additional data development process or the criticality and complexity of the material covered. Reviews will be con- ducted to evaluate database content and functionality in terms of relationships between data elements within the database. (New Data Only) The contractor shall make a copy of the development data- base available to the government 30 days prior to the scheduled ITR. This database shall have the contractor’s Engineering (when applicable) and Quality Assurance review comments incorporated into the database prior to delivery for the scheduled review. Additionally, copies of the Database Discrepancy Reports will be available to the government at the scheduled review. All data presented for ITR will have the contractor’s Quality Assurance and engineering signatures (when appropriate) and meet full MIL-Spec requirements. The contractor shall support

ITRs with TO writers, engineers (if required), and any additional personnel that may have an impact on the IETM database preparation. A complete listing of source data used to develop the IETM data-base shall be at each ITR.

This requirement may be waived by the TOMA on an event-by-event basis.

10.1.5.1 (S) ITR Requirements for the IETM database

1. Initial Review. To meet criteria for the Initial Review, the IETM IDET must contain 80% of the required tasks for that system (i.e., if the system contains 100 tasks, 80 of those tasks would be present in the database for the Initial Review). The Initial Review will be delivered in con-junction with the 80% IPR paper TO submittals. These tasks include:

a. Preparations

b. Restorations

c. General Instructions

d. Removals

e. Installations

f. Operational Checkouts

g. Fault Reporting Procedures

TM-86-01N 1 April 2009 7

h. Fault Isolation Procedures

i. Parts Data

j. Available functionality

In addition to 80% of the tasks, the database will contain a percentage of the data required to support those tasks. The following is a breakdown of that supporting data:

a. 100% of all consumables for 80% of the tasks authored

b. 100% of all Warnings, Cautions, and Notes for 80% of the tasks authored

c. 100% of parts data for 80% of the tasks being authored

d. 100% of descriptive information modules for 80% of the tasks authored

e. 100% of wiring data for 80% of the tasks authored

f. 100% of wiring diagrams for 80% of the tasks authored

2. (S) Pre-Integration Review. The requirements for a Pre-Integration Review are the same as the initial re- view except for the percentage of data present in the database at the time of the ITR. The Pre-

Integration Review will be delivered in conjunction with the Verification IPR copy of the paper TO submittals.

NOTE: If a contractor’s digital IETM format does not merge into the IETM database it will/may be sent back to the contractor for corrections.

10.2. [T] TO Certification. Offerors shall propose their method for documenting certification that TO procedures are accurate, adequate, current, and usable for their intended purposes. Offerors shall notify the government at least 180 days prior of the need for any Government Furnished

Information/Government Furnished Equipment (GFI/GFE) required to perform certification tasks.

10.2.1. [S] Validation. The contractor shall prove the technical accuracy and adequacy of all newly developed TO data through validation, using TO 00-5-3 as guidance. The government will be invited to witness the validation of ECPs and Modifications. Fault reporting, fault isolation and flight data shall be validated by desktop analysis. Structures and Non-Destructive Inspection

(NDI) data shall also be validated by desktop analysis unless a "new" procedure is developed.

Flight manuals shall be validated via the LMAS Flight Manual Committee review. Flight Crew

Checklists shall not require validation because the data are condensed versions of the data in the flight manual.

10.2.2. [S] Validation Requirements. Validation shall be accomplished on all new data prior to in-corporation and/or delivery to the government. Validation entails the actual performance by con-tractor personnel of all operating and maintenance (O&M) procedures, including but not limited to sys- tem and support equipment operation, weapons loading, delivery, and cargo tie-down, and maintenance including check-out, calibration, alignment, disassembly and reassembly instructions for scheduled/unscheduled removal and replacement instructions and associated checklists. No malfunctions shall be introduced into systems or equipment to prove troubleshooting procedures.

In exceptional cases, when injury to personnel or damage to system/equipment may occur, and if approved by the TOMA, validation of these instructions may be by simulation. All other da- ta such as Illustrated Parts Breakdowns (IPBs), schematic diagrams, wiring data and descriptive data contained in all manuals will be checked against current engineering source data. Validation includes revalidation of data changed during modification programs.

8 TM-86-01N 1 April 2009

10.2.3. [S] Validation of Explosive Ordnance Disposal (EOD) Data. The government will arrange for validation of this data.

10.2.4. [S] Validation of Security Classification and Markings. Contractor personnel shall refer to the applicable Security Classification Guide (SCG) or DD Form 254 during validation to ensure classified data included in the TOs has been properly identified. Classified data shall be marked

IAW the current edition of AFI 31-401/DOD 5200.1-R, Information Security Program

Regulation.

10.2.5. [S] Validation Methodologies. Validation can take any one or a combination of three acceptable methods for accomplishment, depending on the type of equipment or instructions being demonstrated. This can be accomplished using TO 00-5-3 as a guide. Validation of performance/task type procedures by simulation and/or desktop analysis must be approved by the

TOMA.

10.2.6. [S] Validation Update Incorporation. Validation of PTOs and/or source data shall be accomplished in time to incorporate updates resulting from validation before delivery to the government for verification.

10.2.7. [S] Validation Scheduling. Schedules should be established by system, task, or by component, and should be concurrent with standup of organic capabilities.

10.2.8. [S] Certification. Contractor shall provide documentation of validation efforts to the

TOMA. The contractor may certify existing TOs and data as "current and accurate, previously validated" (records required) or "current and accurate, validated through use" and provide an explanation of methods and actions performed. NOTE: In some instances, i.e., engine test cells, avionics stations, large fuel component test sets, the government will not physically deliver these items to the contractor, but will make arrangements with the appropriate government activity for the con- tractor to use the equipment for TO validation

10.3. [T] Verification Support. Offerors shall propose the methods, equipment and personnel required to support government TO Verification. (New Data Only) The contractor shall provide onsite technical support during scheduled Air Force verification effort at the verification site.

Verification site will be determined by the TOMA or designated representative in accordance with asset availability. This support should be consistent with program needs and may include a Lead

Technical Writer, knowledgeable on the system and a System Qualified Engineer. The contractor shall make available any source data required to support verification. This data includes, but is not limited to, engineering data, Interface Control Documents and Air Force provided provisioning documentation, if available.

10.3.1. [S] Verification Status Page Requirements. The contractor shall insert Verification Status

Pages (VSPs) in all TOs, (except IPR copies and non-procedural manuals such as IPBs and

WUC manuals), which are delivered with unverified data. The Contractor shall also update the information contained thereon throughout the term of the contract as directed by the TOMA.

MIL-STD-38784 shall be used as a guide for VSP formatting and numbering. The contractor shall list all functions, paragraphs, sections and procedures in the manual which require verification. VSPs shall remain in the TOs until all procedures have been verified.

10.3.2. [S] Verification Comment Incorporation. The contractor shall incorporate TOMA approved verification comments and PCRs (or justify non-compliance), and update VSPs in

PTOs prior to delivery for prepublication review or next PTO update. When the prepublication review is waived, incorporation and update shall be completed prior to developing reproduction media.

TM-86-01N 1 April 2009 9

10.4. Technical Data Assessment (TDA – originallycalled First Article Testing). The program office, with the assistance of 754 ELSG/ILMT 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 first IPR, for TDA to verify compliance of the digital files to Air Force DSSs. Additional TDAs may be required based on initial results. 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 a representative percentage of

Indexed Portable Document Format (IPDF) TO files to verify indexing compliance with the

Technical Order Conversion Requirements (TOCR) (on the AF Portal at https://wwwd.my.af.mil/afknprod/DocView.asp?DocID=5153963).

11. TO and Source Data Maintenance. 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.

11.1. [S] Update Approval. All Commercial Manuals updates shall be validated, reviewed and approved by the TOMA prior to publishing. All updates to Military Specification TOs shall be validated, reviewed, verified, and approved by the TOMA prior to publishing. Verification may be waived by the TOMA for routine updates. The Contractor shall provide the TOMA with adequate visibility into the content of approved change requests (i.e. Change Request summary).

11.2. [S] TO Updates. The contractor shall maintain the currency of TOs developed and/or delivered under this contract by preparing source data, TO Changes, revisions and supplements as required to support program operational concept and/or as identified in Section 2. All updates shall conform to the general style and format requirements of the manual being updated. These updates shall be furnished throughout the period of performance. Changes will be required at least every 180 days.

11.2.1. [S] Types of TO Updates.

11.2.1.1. [S] Source Data. As required by program concepts, the contractor shall recommend best practices for source data delivery to the USG. The contractor will be responsible for the development of data compatible with the IETM (1C-130-2-WA-2) using USG provided tools. For

TCTOs, all source data delivery will be 100% vector art format in CGM/4 format.

11.2.1.2. [S] TO Changes. A TO Change shall be prepared in a similar style and format as the basic manual.

11.2.1.3. [S] Revisions. A revision is a new edition of an existing TO incorporating all previous and current changes and supplements. A revision is normally recommended by the offeror when the pages affected by existing changes, including pages currently requiring change, total 70 percent or more of the TO. The TOMA will determine revision (versus change) of a TO based on AFMCMAN 21-1.

11.2.1.4. [S] Supplements. A supplement is used in situations where formal updates are not suitable or practical; e.g., when time and circumstances do not permit issuance of formal updates or the inclusion of additional data in the manuals. The contractor shall furnish source data for, or develop interim supplements in emergency situations when time does not permit issuance of a change or for- mal supplement. The TOMA will determine development of supplements or source data on

10 TM-86-01N 1 April 2009 a case- by-case basis. The Contractor shall prepare TOMA directed out-of-cycle routine supplements on a contractually agreed basis.

11.2.1.5 [S] IETM Changes. An IETM change shall be prepared in IDET.

11.2.2. [S] Material Included in TO Updates. Updates shall be submitted to correct any existing technical or typographical errors or omissions in the text; to include additional or changed information as a result of hardware configuration, design and modification changes, or authorized substitution of parts, assemblies and/or components on the equipment covered by the TOs; and to expand and improve on data coverage and to include information developed as a result of experience. The requirement for updates to be furnished does not authorize deletion or changes of existing information unless specifically reviewed by the TOMA, except when such changes reflect correction of typographical errors, parts identification, rescission of TCTOs, Service Bulletins etc. Technical errors and omissions found in technical data delivered by

Lockheed to the USG will be corrected as required in a manner consistent with the urgency of the deficiency.

11.2.3. [S] Sources of TO Updates. Updates may result from internal or external TO reviews, Engineering Change Proposals (ECPs), Time Compliance Technical Orders (TCTOs), AFTO

Forms 22/27, AF Forms 847, and/or AFMC Forms 252. ECPs and TCTOs must be approved by the sustainment Configuration Control Board (CCB), and AFTO Forms 22, 27 and 847 must be approved by the Technical Content Manager (TCM) or Flight Manual

Manager (FMM) prior to implementation.

11.2.4. [S] Categories of Updates.

11.2.4.1. [S] Routine Updates. The cost of the original material shall be considered to cover these updates. Acceptance of the initial data by the government in no way relieves the contractor of the requirement to submit these updates. Routine updates are those non-urgent TO Changes and revisions. Contractor shall comply with response times for Routine PCRs in accordance with TO

00-5-1 or AFI 11-215 as appropriate.

11.2.4.2. [S] Updates Resulting from Class I (Major) and Class II (Minor) Configuration Hardware or

Software Changes. The contractor shall submit TO Changes and/or revisions to reflect Government approved configuration, design and modification changes to the production articles. The cost of updates as a result of Class I changes, being undetermined at the start of the contract, shall be negotiated as they are required, either as a part of the applicable Engineering Change Proposal (ECP) or as otherwise agreed upon. The cost of the original TOs shall include updates caused by Class II changes. Updates resulting from Class II modifications shall be submitted in the next routine up- date cycle.

11.2.4.3. [S] TO Updates Resulting From Warranty Changes. The contractor shall develop and deliver updates and/or source data to reflect configuration, design and modification changes to production hardware and software accomplished under the terms of the contract warranty. These shall be provided as no-cost updates. They shall either be included with the next routine update, or, if applicable, developed as Emergency or Urgent updates.

11.2.4.4. [S] Emergency and Urgent TO Updates. When required, the contractor shall assist the

TOMA with the development, preparation, coordination and distribution of Emergency and

Urgent updates. These updates shall be Airworthiness Directives, formal Operational or Safety

Supplements. Contractor shall comply with response times for Emergency and Urgent PCRs in accordance with TO 00-5-1 or AFI 11-215 as appropriate. Emergency and Urgent updates apply to

TM-86-01N 1 April 2009 11 both preliminary and formal TOs. NOTE: Interim Message Changes (IMCs) (AFI 33-360 Vol.

1) are not authorized for TO updates.

11.3. [S] TOMA Directed Changes. The Contractor shall incorporate Government-furnished publication change requests resolutions and source data that do not meet with Contractor concurrence. In such cases, the Government shall execute a release absolving the Contractor of responsibility and liability for the content of the changes.

11.4. [S] Preliminary Technical Orders (PTOs). PTOs and source data shall be provided or delivered for Verification, and Prepublication Reviews as specified by Section 2. In formatting, use MIL-STD-38784 and the applicable detail (content) MIL SPECs, as guides, except as noted be- low.

11.4.1. [S] PTO Format. The Contractor shall develop PTOs and provide them in accordance with mutually agreed upon practices and procedures. These PTOs shall be prepared from source data, e.g., engineering and other data developed during research and development. They shall be developed using the applicable detail specifications as a guide so that the conversion from preliminary to formal TOs is minimal.

11.4.2 [S] PTOs for Verification. The contractor shall prepare PTOs in the same Style and

Format as existing manuals, for use during verification.

11.4.3 [S] PTOs for Prepublication Review. The contractor shall prepare PTOs for prepublication review(s) as approved by the TOMA. The PTOs shall have been approved by contractor QA and incorporate all verification comments and corrections as agreed upon by the Con- tractor, and approved by the TOMA.

11.5. [S] Inspection and Acceptance. Inspection and acceptance of the technical order reproduction media furnished will be performed by the TOMA or designated representative responsible for inspection and acceptance of deliverables as required by this TMCR.

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. Practices and procedures shall be compatible with the program’s IDS. TO file delivery formats shall be according to applicable CDRLs and the tailored TM Delivery Requirements

Matrices included in Section 2 of this document. Paper TO delivery is not acceptable for final delivery of TOs. EXCEPTION: For Commercial Manuals not available digitally.

12.1. SGML-Tagged Files. 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. NOTE: The government will parse the files prior to acceptance using the public domain “SGMLS Parser”

(ftp://ftp.jclark.com/pub/SGMLS).

12.2. SGML-Tagged Files for Use with the eTO Viewer. The contractor shall use the GFE

ETIMS eTO Viewer/Transformer and Digital Formatted Output Specification Instance (DFOSI) to convert tagged instances to Hypertext Markup Language (HTML) files compatible with the eTO viewer, and certify the output complies with TMSS requirements.

12.3. [T] Interactive Electronic Technical Manuals (IETM). All IETM deliveries will be in

IDET format per Section 2, Part B of this document. IETM data base delivery shall be according to the SIR for MIL-PRF-87269 in Section 3 of this document.

12 TM-86-01N 1 April 2009

12.4. Indexed Adobe™ Portable Document Format (IPDF) Files. The contractor shall validate indexing of PDF TO files using the specifications contained in the Technical Order Conversion

Requirements (TOCR) found on the Air Force Portal at https://wwwd.my.af.mil/afknprod/DocView.asp?DocID=5153963.

12.5. [S] Program Specific Requirements. The following paragraphs provide detailed TO development and delivery requirements for the C-130J programs, including requirements for source data and updates.

12.5.1. [S] Formatting and Delivery Requirements. Digital media delivered will be in a format acceptable for processing by WR-ALC and the Document Automation and Production Service

(DAPS).

12.5.2. [S] BaselineTechnical Manuals. Baseline maintenance technical manuals delivered in support of this TMCR are to be in the Lockheed Commercial Format. This format is presumed to be based upon the information contained in MIL-PRF-83495 and MIL-STD-38784 (guidance documents).

Manuals are to be developed from the Lockheed Commercial baseline and be customized for USAF unique and peculiar equipment resulting in a complete manual set covering the aircraft configuration.

12.5.3. [S] Prepare Print Orders. The contractor is not required to do the printing. The contractor will prepare orders using digital reproduction media using MIL-STD-1840 as a guide. Digital media shall be CD/DVDs. Digital media delivered will be in a format acceptable for processing by

WR- ALC and the Document Automation and Production Service (DAPS). Contractor shall deliver print package CD/DVDs or electronic media for formal delivery.

12.5.4. [S] Flight Manuals.

12.5.4.1. [S] Operational Supplements. Upon option exercise C-130J Flight Manuals Operation-al Supplements will be developed and delivered as plug and replacements change pages unless other- wise mutually agreed upon between the contractor and Flight Manual Manager (FMM).

This will al- low changed pages to be inserted directly into applicable section.

12.5.5 [S] Illustrated Parts Breakdown (IPB) Manuals. Breakdown Manuals shall conform to the numbering concept utilized for the maintenance manuals.

12.5.6 [S] New Manuals. Development of new manuals or mil-spec conversion of commercial manuals may be required. When new manuals are contracted for, the contract modification will identify military specifications and/or performance specifications required for development.

12.5.7 [S] TO Changes. Changes required in the baseline manuals to incorporate engineering change data, PCRs identified during OT&E, omissions, errors or deficiencies will be required in accordance with TO 00-5-1 or AFI 11-215 as appropriate., unless waivered by the TOMA.

12.6. [S] Submittal Procedures. Reproduction media for TOs shall cite the appropriate contract number and be submitted with an AFMC FORM 254, Reproduction Assembly Sheet (RAS), to the TOMA.

12.7. [S] TO Update Delivery. Updates to correct errors affecting safety or urgent and emergency deficiencies shall be submitted, within the guidelines of TO 00-5-1 as soon as all relevant data are available. The contractor shall submit validated (Contractor validated or Contractor certified for ac- curacy) TO updates and/or source data covering Class I equipment modifications IAW the

Section 2 requirements for verified PTOs. Updates resulting from Class II modifications shall be included in the next scheduled routine update.

TM-86-01N 1 April 2009

12.8. [S] Commercial Manuals. Commercial manuals shall be delivered as specified in the related contract or approved CFAE/CFE Notice. When reproduction media is specified, it may consist of a copy of the manual suitable for Direct Image Copying and/or a digital copy on contractor format digital media and/or DVD. Digital media delivered will be in a format acceptable for processing by WR-ALC and the Document Automation and Production Service

(DAPS).

12.9. [S] Delivery Dates. Commercial Manuals, TOs, PTOs, and source data shall be delivered as required by the contract. When these dates cannot be met, the contractor shall request an extension from the PCO, at least sixty workdays prior to the original dates. The request shall indicate why the delivery dates cannot be met, and provide a contractor recommended schedule and suggested work- around to support Air Force organic requirements. This provision does not constitute authorization for the contractor to deviate from the delivery requirements set forth in the contract schedule.

12.10 [S] Final Delivery. Upon submittal of the final product, the contractor shall certify in the transmittal document that all known and contractually required improvements have been incorporated and they completely cover the equipment as produced. A copy of the letter of transmittal shall be forwarded to the PM (i.e. DD-250 or commercial equivalent) as directed in the CDRL.

12.11 [S] Packaging Requirements. Deliveries required by this TMCR shall be packaged using

MIL-STD-38784 and/or MIL-STD-1840 as guidance.

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 delivery of operational equipment to the field (AFI 21-303). This policy will determine TO development and delivery schedules throughout the sustainment 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 appropriate 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 Process, (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.

14.1. [S] TCTO Development. TCTOs shall be developed at the direction of the System Program

Office (SPO) or Program Manager (PM) for the purpose of modifying systems or equipment, disseminating safety information, and/or performing one-time inspections. TCTOs and companion updates to other affected TOs shall be directed and funded by the ECP or CCP from which the requirements were derived.

14.2. [S] ECP/CCP Driven Efforts. When directed by an ECP/CCP, the contractor shall develop and furnish TCTOs IAW the documented policy contained in 00-5-15 using MIL-PRF-38804C as a guide, and the AFMC Form 873 will be provided by the government. This includes source data for interim TCTOs that the Government will distribute, Supplements and TO Changes to manuals for which other agencies are responsible

14 TM-86-01N 1 April 2009

14.3. [S] Forms. The acquiring activity will furnish the contractor two copies of a completed

AFMC Form 873, "Time Compliance Technical Order Requirements." As soon as the necessary retrofit de- sign information is available, the contractor shall execute and submit AFMC Form 874, "TCTO Supply Data Requirement," with one copy of the AFMC Form 873 attached, to the address provided on the AFMC Form 873. The preparation instructions for AFMC Form 874 are pre-scribed by AFMCI 21-301, Air Force Technical Order System. The government should provide approval of the AFMC Form 874 within 45 days of submittal.

14.4. [S] Companion Update Development. The contractor shall prepare updates and/or source data to correct all TOs whose contents are affected by TCTO equipment or procedures modifications.

14.4.1. [S] Companion Update Procedures. The updates delivered in support of a modification will normally be a two time requirement. The affected manuals will retain instructions applicable to the equipment before modification ("Before" data) and will be updated to add instructions applicable to the equipment after modification ("After" data).