Attachment 8 20 March 2020.pdf

Air Force Technical Manual Contract Requirements (TMCR) For

AC-130 Precision Strike Package (PSP)

ATTACHMENT 1 TO CDRL SEQUENCE NUMBER A00 EXHIBIT A

REQUEST FOR PROPOSAL/CONTRACT

Date: 01/15/2020

Technical Manual/Technical Order requirements contained herein have been cleared for use by OMB No. 0704-0188, 21 July 1986.

SECTION 1. TECHNICAL ORDER (TO) PROGRAM REQUIREMENTS

1. Purpose. This Technical Manual Contract Requirements (TMCR), including the associated tables, matrices and attachments provide the requirements for development, certification, verification, and delivery of all Technical Orders (TOs) required to fully meet the Government-identified technical data requirements within Sections 1, 2, and all attachments of this TMCR. The TMCR shall be attached to the Contract Data Requirements List (CDRL) for TO delivery, and shall be included in the proposal as a separate exhibit, referenced in the proposal Statement of Work (SOW). United States Air Force (USAF) TO Acquisition procedures, including procedures for tailoring this document are found in TO 00-5-3 (TO Lifecycle Management), located on the World Wide Web (WWW) at http://www.tinker.af.mil/technicalorders/.

1.1 Technical Order Management Agency (TOMA). The TOMA for this effort is Air Force Life Cycle Management Center (AFLCMC)/WISM Logistics. Changes to TO requirements shall be made only with the specific approval of the Procuring Contract Officer (PCO), AFLCMC/WIKAA. All actions as expressed herein are understood to be within the scope of the contract.

1.2 TMCR Tailoring. The offeror may tailor this TMCR in order to provide USAF with insight into how the offeror will meet the purpose and scope of this document. However such tailoring shall not delete or nullify any of the requirements called out in the MILSpecs, DoD directives, etc. in this document. Paragraphs tailored by the offeror shall be identified with a [T] after to the paragraph number and prior to the first word in the paragraph.

Supplemental paragraphs (those added by the offeror) shall be identified with a [S] after to the paragraph number and prior to the first word in the paragraph.

1.3. TOs Requiring Update. Offer shall review the AC-130 TOs listed Section 2, Table 3 of this TMCR and identify which are impacted by this modification. Offeror shall then add those TOs identified to Section 2, Table 2 and delete Table 3. Offeror shall indicate, by checking the applicable box, what will be developed and delivered for each TO (i.e. source data, supplement, etc.).

2. TO Program Scope. This TMCR outlines the development, review, certification, verification and delivery of technical data (Technical Orders (TOs), Time-ComplianceTechnical Orders (TCTOs), supplements, and source data) resulting from this modification. The offeror shall ensure that all delivered technical data is safe, current, accurate, and concurrent with configuration of the AC-130 aircraft. The TOs shall support all facets of operation and maintenance of the system(s) impacted by this modification. This shall include all Operation, Maintenance, Installation and Training (OMIT) TO requirements for both Organizational level (O-level) and Depot level (D-level) of maintenance as well as necessary flight manuals (FMs). These publications shall be designed to allow maintenance and operation to be accomplished by trained USAF personnel. All TOs shall be developed in same style and format as existing manuals however the content will be In Accordance With (IAW) the MIL Specs, and USAF/DoD directives called out in this document.

2.1. Type of TOs Required. The offeror shall develop the following types of TOs as applicable;

System/Aircraft TOs: The offeror shall develop stand-alone TOs when current TOs do not cover new or unique systems associated with this modification. The TOs shall provide all instructions necessary for USAF personnel to safely maintain and operate the systems/aircraft. Examples of the TOs required include, but are not limited to, Job Guides, Fault Isolation, Illustrated Part Breakdowns, Aircrew Checklists, etc. All TOs developed for the AC-130 program shall be formatted the same as current used by USAF.

TCTO: The offeror shall develop TCTO(s) as a stand-alone document to be used by the modification team. This document will contain all information necessary to modify the system/aircraft. As with all TOs the TCTO will undergo In-Process Reviews (IPRs), certification by the offeror, verification by USAF. A sample of the TCTO format is contained in Attachment 1 of this TMCR. More information on TCTOs requirements is contained in paragraph 14 of this document.

Supplements. The offeror shall develop Supplements for the current TOs to be used by USAF until changes resulting from the modification are incorporated into the TOs. The Supplements shall provide complete information needed to operate and maintain the system, including but not limited to, aircrew checklists, Job Guides (JG), Fault Isolation (FI), Illustrated Part Breakdowns (IPBs), Wiring Diagrams (WDs), etc. More information on Supplemental Manual requirements is contained in paragraph 15 of this document.

Source Data. The offeror shall provide all Source Data needed for the Government to have existing TOs revised as a result of this modification. The Source Data shall include illustrations and wiring diagrams/schematics in addition to complete procedures and system parts information. More information on Source Data requirements is contained in paragraph 16 of this document.

2.2. Delivery Media. TOs (to include TCTOs, Supplements, Source Data, etc.) shall be delivered as Indexed Portable Document Files (IPDF). In addition the offeror shall deliver the editable digital files (Word, Frame Maker, SGML, XML, etc.) as part of the final delivery package.

2.3. Order of Precedence. In the event of a conflict between the text of this TMCR and the references called out herein, this TMCR shall take precedence.

2.4. Application to Sub-offerors/Vendors. The prime offeror shall ensure that all applicable TO requirements of this contract, to include appropriate data rights (see paragraph 8 of this TMCR) are levied on all sub-offerors or vendors. The prime offeror shall ensure that sub-offerors/vendors furnish operation and maintenance information applicable to the equipment being acquired, including changes and/or revisions, for inclusion of such information in applicable operation and maintenance TOs impacted by this modification. When a sub-offeror or vendor prepares system TOs, the prime offeror shall supply required interface data.

2.5. Original Equipment Manufacturer (OEM) Interface. The prime offeror shall work with the aircraft OEM to secure needed source files related to this modification. The prime offeror and OEM shall, if required, draft and agree to a Proprietary Information Agreement (PIA) to safeguard such information. The prime offeror shall inform the TOMA when said PIA is signed.

2.6 Viewing of TOs. TOs must be capable of display using portable display devices suitable for maintenance and operational activities. This includes, but is not limited to, notebooks/laptops, slates/tablets, and standard desktop PCs in the administrative and staff offices of the maintenance units, Major Commands, and training environments.

3. Commercial Manuals. Offerors 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. The content (text and graphics) of commercial manuals shall meet the requirements of the MIL Specs called out in this document. Commercial manuals submitted for use will be evaluated for acceptability by the USAF using MIL-PRF-32216 (Evaluation of Commercial Off-The-Shelf (COTS) Manuals and Preparation of Supplemental Data) and MIL- DTL-7700 (Detail Specification: Flight Manuals, Air Refueling Procedures, and Abbreviated Checklists).

3.1. Commercial Manual Ratings. Commercial manuals submitted for use by USAF will be evaluated using MIL-PRF-32216 and MIL-DTL-7700 as stated in paragraph 3 of this TMCR.

The following are possible ratings, with applicable correction requirements, that will be used;

Acceptable: No correction required. Manual is acceptable as written.

Acceptable with Additional Data: Manual requires additional information to be acceptable. This can be in the form of Supplemental Data Sheets or making necessary changes to the manuals themselves. The method of correction shall be determined by the TOMA (see paragraph 1.1 of this TMCR).

Unacceptable: Manuals do not meet the requirements of the TMCR and Supplemental Data Sheets or minor corrections will not correct the problem. The submitted manual must be re-written to meet the requirements called out in this TMCR.

3.3. Commercial Manual Costs. The costs of obtaining or developing adequate commercial manuals shall be negotiated prior to contract approval and award.

3.4. Commercial Manual Numbers. The USAF will assign TO Numbers to commercial manuals approved for Government use. When multi-manuals are furnished by the offeror, the Air Force may assign more than one TO number, i.e., one for the operation manual, one for the maintenance manual and one for the parts identification manual. TO numbering will be accomplished IAW paragraph 7 of this TMCR.

3.5. Commercial Manual Title Pages. The Offeror shall develop, print, stamp or otherwise mark the TO number, data rights statements, date and any other required identification on approved commercial manual title pages (when space permits) or develop a new USAF style and format title page to be inserted on top of the commercial manual. If the offeror develops an USAF title page the title page shall contain a statement that clearly states the data rights marking comply with paragraph 8 of this TMCR.

3.6. Previously-Approved Commercial Manuals. When recommending use of commercial manuals, the offeror shall determine if they have been previously-approved for Government use. If previously approved the offeror shall provide the manual number, date of approval, approving agency (i.e. USAF, US Navy, US Army, etc.) and whether the manual is still active. Refer to TO 0-4-6-2 (Items Cross-Reference File, Equipment Numbers to Technical Order Numbers) which is available through normal TO distribution channels, or the Inter- Service Technical Information Exchange System (ITIES) database (see TO 00-5-1 (AF TO System)). Furnish approved commercial manual TO or TM numbers with the manual recommendation when available.

4. Technical Manual Specifications and Standards (TMSS) Tailoring. TMSS are tailored by deleting requirements not needed for TOs impacted by this modification, and by selecting between options offered. Questions and conflicts with TMSS requirements may be resolved by written request and justified suggestions for resolution submitted through the Procurement Contracting Officer (PCO) to AFLCMC/WIKAA, 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. NOTE: Tailoring must not change or delete mandatory requirements which are part of the Document Type Definition (DTD) structure.

4.1. Content. TOs identified in this document are to be delivered to the Government during the course of this contract. Updates to existing TOs shall be prepared in the same style and format as the basic USAF TOs. TOs identified in Section 2 of this document shall be prepared IAW the appropriate detail specification(s), cited in this TMCR. If a later revision or amendment of a specification or standard is available when the offeror starts preparation of the technical data, it shall be used if no additional cost is involved, the schedule is not impacted, and the acquiring activity gives approval. The offeror shall recommend use of later-version specifications when beneficial to the Government. The exception, using MIL- PRF-38804 (Time Compliance Technical Orders - Preparation) 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. The offeror 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. NOTE: The recommended notification process is to use CFAE/CFE Notices (DI-TMSS-80067).

6. TO Development. The TOs this modification shall be tailored so that only the AC-130 aircraft configurations are covered. The offeror shall prepare and deliver technical orders for the AC-130. All illustrations shall be delivered as Computer Graphics Metafile version 4 (CGM-4).

6.1. Format. TOs delivered by the offeror will be developed, written, and maintained to be in the same style and format as the current TOs. Flight Manual and Wiring Diagram TOs will be provided in both electronic and hard copy. Maintenance TOs will be provided in electronic version only. Electronic copies will be formatted in Indexed Adobe Portable Document Format (IPDF) on CD-ROM or other digital media acceptable for processing by WR-ALC and the Defense Printing Service.

6.2. Use of Non-Government Standards (NGS). The offeror may propose use of 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 from the Air Force Preparing Activity (PA), AFLCMC/HIAM (TMSS), Technical Order Section, 4375 Chidlaw Rd Suite 6, WPAFB OH

45433-5006 (SGMLSUPPORT@US.AF.MIL).

6.3. Occupational Safety and Health. Using AFI 91-301 (Air Force Occupational and Environmental Safety, Fire, Protection, and Health (AFOSH) Standards) and MIL-STD- 38784 (DoD Standard Practice for Manuals, Technical: General Style and Format) as guidance, the offeror 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. The offeror shall provide electronic copies of all applicable Material Safety Data Sheets (MSDS) for products called out and used as a result of this modification. If there are no applicable standards, the offeror 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.4. Flight Manual Operational Supplements. FM operational supplements shall be developed and delivered as plug and replacement change pages unless otherwise mutually agreed upon between the offeror and TOMA/Flight Manual Manager (FMM).

6.5. Illustrated Parts Breakdown (IPB). IPBs developed and delivered for this modification shall conform to the numbering concept utilized for the current AC-130 maintenance manuals.

6.6. Maintenance Manual Supplements. The offeror shall furnish supplements in the same style and format as the original manual, or as required by specifications cited in Table 2. The Title Page of the supplemental manual shall contain the statement, "This manual is incomplete without TO NOXX-XXXXX-XX".

7. TO Numbering. Offeror shall notify the Government of manuals which require TO numbers. TO numbers are not required for manuals to be used exclusively by offeror personnel.

(NOTE: DI-TMSS-80067B may be used to provide the notification.) AF procedures for numbering TOs are described in TO 00-5-3 and TO 00-5-18 (Air Force TO Numbering System) (available under the link to “Digital Technical Orders” at http://www.tinker.af.mil/technicalorders/).

8. Data Rights. Government rights for technical data is specified in the Defense Federal Acquisition Regulation Supplement (DFARS), paragraphs 227-7102 through 227-7104. Offeror shall propose Unlimited Rights for all technical data, or portion thereof, generated specifically for this modification and Unrestricted Rights to all technical data, or portions thereof, which have previously been delivered to the Government subject to DFARS 252.227-7015.

8.1. Copyrighted and Proprietary Data. If some technical data is copyrighted or contains proprietary data or procedures, offerors may propose Limited Rights or Government Purpose License Rights (GPLR) only. Proposed commercial manuals should be provided with at least GPLR or Limited Rights. Copyrights shall be according to DFARS paragraphs 227-7103, 7105 or 7106.

8.1.1. Markings. Only the pages containing copyrighted or proprietary data shall be marked as such, not an entire TO, TCTO, supplement, or source data package. Data developed exclusively for this Government funded modification shall not be marked with any copyrighted or proprietary statements.

8.2. Non-Government Standard (NGS). 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 display 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. Classification of TOs. The offeror shall classify technical data IAW the security classification guides (SCG) provided by the acquiring activity. Each time an update is issued to a classified TO, the security classification shall be reviewed by the offeror. As a minimum, technical data for which the offeror is responsible shall be reviewed annually. The offeror shall immediately issue updates when technical data classification is upgraded.

9.2. Distribution, Destruction, Disclosure, and Export Control Notices. These notices will be applied to all technical data (including TOs/TMs, TCTOs, Supplements, and source data) produced or provided as a result of this modification. Contact the TOMA (see paragraph 1.1 of this TMCR) for correct markings.

9.3. Copyrights and Proprietary Data. See paragraph 8.1 of this TMCR.

10. TO Quality. Offeror shall propose a quality assurance program which ensures TOs prepared are; a) 100% technically accurate IAW TO 00-5-3; b) written to a scope and depth of coverage sufficient to support the operation and maintenance concepts; c) to the ninth grade Reading Grade Level (RGL) as specified in MIL-STD-38784; and d) properly classified and marked with export control and distribution limitation statements DODD 5230.24.

Recommended QA methods include actual performance of procedures and use of desk-top analysis for non-procedural technical 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. Offeror proposals should describe how the Government will be allowed to interact with the Offeror’s TO development team.

10.1. Conferences and Technical Reviews. The offeror shall convene a TO Guidance Conference within 60 days of contract award. The TO Guidance Conference should be conducted at the contractors facility unless an alternate location is approved by the TOMA.

In addition there will be three (3) In-Process Reviews (IPRs) to be conducted at the 40% (may be waived by TOMA only) and 80% milestones during development, and a final Pre- Publication Review to be conducted, after all technical data is certified and verified, approximately 60 days prior to final delivery of the technical data. The 80% IPR and the Certi/Ver shall be conducted at the Modification Facility, the location where the aircraft is being modified - unless waived by the TOMA. A 30 day advance copy is required to be sent to the government prior to these reviews, to allow appropriate time for government subject matter experts to review an provide comments. A waiver/change in these delivery dates must be approved by the offeror and the TOMA, at the TO Guidance conference.

10.1.1. Conferences and Reviews. The offeror shall propose dates for scheduled conferences and reviews to provide a minimum of 30 calendar day’s notification to the TOMA. The TOMA and offeror shall schedule such conferences, reviews, or inspections to provide a minimum of 30 calendar day notification to all participating activities.

Conferences and reviews are to control and manage the program, to oversee the TO preparation process, and shall be held at the facility of the offeror. The offeror shall have members of their technical publications writing team are in attendance in order to ensure all understand contract requirements and expectations.

10.1.2. Minutes. The Offeror shall prepare minutes and record all comments for all TO related meetings, conferences, and reviews. The TOMA or designated representative will review and approve the minutes prior to distribution in accordance with the CDRL. A final copy shall be provided IAW DI-ADMN-81250A. The offeror shall maintain a complete file of minutes; minutes may be made accessible to the Government via email within 10 workdays of said meeting, conference, or review.

10.2. TO Certification. Offeror shall propose their method for documenting certification that TO procedures are accurate, adequate, current, usable for their intended purposes, and developed IAW this TMCR. Offerors shall notify, via contract letter, 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. Certification. The offeror shall prove the technical accuracy and adequacy of all newly-developed technical data through certification IAW TO 00-5-3. The Government will be invited to witness the certification. Fault reporting, fault isolation and flight technical data may, with prior approval of the TOMA, be certified by desk-top analysis.

Structures and Non-Destructive Inspection (NDI) technical data may also, with prior approval of the TOMA, be certified by desk top analysis unless a "new" procedure is developed.

10.2.2. Certification Methodologies. Certification can take any one or a combination of three acceptable methods for accomplishment, depending on the type of equipment or instructions being demonstrated. The methods are performance, desk-top analysis, and simulation. Additional information regarding these methods can be found in TO 00-5-3.

Certification of performance/task type procedures by simulation and/or desk top analysis must be approved by the TOMA or a designated representative.

10.2.3. Certification Update Incorporation. Certification of preliminary technical data shall be accomplished in time to incorporate updates resulting from certification before delivery of the TOs to the Government for verification.

10.2.4. Certification. Offeror shall provide documentation of certification efforts to the TOMA. The offeror may certify existing technical data as "current and accurate, previously certified" (records required) or "current and accurate, certified through use" (provide explanation).

10.3. TO Verification. TO verification shall be conducted where the aircraft is being modified and the AF team will require access to the aircraft. TO verification will be accomplished on production configured aircraft (i.e. Kit Proof Install aircraft) unless waivered by the TOMA. USAF AFMC AFLCMC/WIU shall propose the methods, equipment and personnel required to maintain the aircraft (i.e. towing, applying power, etc.) to support Government TO Verification. This shall consist of the following;

a) Technical writer(s) familiar with the technical data (to include both maintenance and flight manuals) being verified shall be available during verification. The technical writers will generate red-line mark-ups of the technical data being verified in order to make corrections in sufficient time to meet development schedules and milestones.

b) Engineer(s) (telephone stand by acceptable with prior approval of the TOMA) to resolve problems found during verification. This will eliminate delays during the process and sufficient mission and support equipment to complete all tasks being verified.

c) Dedicated, on-aircraft, qualified maintainer to support all Government verification activities to ensure procedures are conducted safely and ensure "return to service" documentation requirements are completed.

d) All support equipment (SE) called out in the TO as required to perform the task/procedure. SE other than what is called out cannot be used unless the SE is listed as an acceptable alternate.

e) Type 1 aircrew and maintainer training for all Air Force personnel identified as part of the TO verification team.

10.3.1. Verification Status Page. The offeror shall generate a Verification Status Pages (VSPs) for all technical data, except IPR copies and non-procedural manuals such as IPBs and WUC manuals, which are delivered with unverified technical data. The offeror shall list all functions, paragraphs, sections and procedures in the TO which require verification. The offeror shall update the information contained on the VSP throughout the verification process until all technical data contained in a TO has been verified. The VSPs shall be formatted and numbered in same style and format as VSPs in existing manuals. Refer to MIL-STD-38784 for additional information. VSPs shall remain in the TOs until all procedures have been verified.

10.3.1.1. Title Pages. The title page of TOs, TCTOs, supplements, and source data containing unverified technical data shall have a Warning stating “This manual contains unverified procedures. Refer to the Verification Status Page(s) prior to performing any operation or maintenance procedures.”

10.4. Verification Forms. The Government will complete an AFTO Form 27 once comments are incorporated. A separate AFTO Form 27 (Preliminary Technical Order (PTO) Publication Change Request (PCR)/TO Verification Record/Approval) will be completed on each TO or portion of a TO and checklist verified to document discrepancies and the overall results of the verification. The form will be submitted to the TO for approval. When approved by the TOMA, the AFTO Form 27 recommending formalization will be used as authority to prepare the formal TO.

10.5. Conflicts. Conflicts concerning whether or not to develop and incorporate updates shall be resolved by the Technical Order Review Board (TORB) or Flight Technical Order Review Board (FTORB) prior to implementation. This review panel should consist of personnel from activities involved in the modification program, as determined by the TOMA. After review, coordination and approval, the changes will be sent to the contractor for update of the technical data package involved. Additional information concerning TORBs/FTORBs can be found in TO 00-5-3.

11. TO and Source Data Maintenance. Offeror shall propose methods for maintaining accuracy, currency and configuration of TOs and source data throughout the contract period of performance. This includes preparation of TO and source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes.

11.1. TO Updates. The offeror shall maintain the currency of technical data developed and/or delivered under this contract by preparing changes, revisions and supplements. In addition updates shall be prepared for technical data affected by, but not developed as a part of, this contract. All updates shall conform to the same style and format requirements of the technical data being updated.

11.1.1. Data Included in 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 technical data, and to expand and improve on data coverage and to include information developed as a result of the contract. 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, Service Bulletins, etc.

11.1.2. Updates Resulting From Warranty Changes. The offeror 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 updates shall either be included with the next routine update, or, if applicable, developed as emergency or urgent updates.

11.2. Categories of Updates.

11.2.1. Routine Updates. Routine updates are those non-urgent updates which shall be required at least every 180 days. Offeror shall comply with response times for Routine PCRs in accordance with 00-5-1 or AFI 11-215 (USAF Flight Manuals Program) as appropriate. Acceptance of the initial data by the Government in no way relieves the offeror of the requirement to submit these updates.

11.2.2. Emergency and Urgent Updates. When required, the offeror shall assist the TOMA with the development, preparation, coordination, and distribution of Emergency and Urgent updates. These updates shall be Service Bulletins, Airworthiness Directives, Interim Operational or Safety Supplements (IOSs or ISSs, message format), formal Operational or Safety Supplements. Offeror shall comply with response times for Emergency and Urgent PCRs in accordance with 00-5-1 or AFI 11-215 as appropriate.

Emergency and Urgent updates apply to both preliminary and formal technical data.

11.3. TOMA Directed Changes. The offeror shall incorporate Government-furnished publication change request resolutions and source data that do not meet with offeror concurrence. In such cases, the Government shall execute a release absolving the offeror of responsibility and liability for the technical content of the changes. However, the offeror will be held liable for the accuracy of the change during incorporation.

11.4. Interactive Electronic Technical Manual (IETM) Changes. The offeror shall be responsible for identifying changes that impact the AC/HC/MC-130J IETM. Changes shall be submitted for review, approval, and incorporation via the IETM Data Entry Tool (IDET).

The offeror shall be responsible for securing access to IDET and completing all necessary training. The HC/MC-130J TOMA and/or AC-130 TOMA, as applicable, will provide the IETM/IDET POC information prior to, or at the TO Guidance Conference.

11.5 Verification Team Requirements. The offeror will provide the Government verification team with internet (Wi-Fi), landline, and printer access at all conferences and reviews.

12. TO Delivery. Offerors shall propose practices and procedures for secure access to or delivery of digital TO files, including those for Preliminary TOs (PTOs), source data, reproduction masters, and program support data. TO file delivery formats shall be according to applicable CDRLs and the tailored TO Delivery Requirements Matrices included in Section 2 of this document. Flight Manual and Wiring Diagram TOs will be provided in both electronic and hard copy. Maintenance TOs will be provided in electronic version only.

12.1. SGML-Tagged Files. SGML-tagged files (if used) shall be parsed and composed by the offeror prior to delivery to the Government, and the offeror shall 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. Adobe™ Indexed Portable Document Format (IPDF) Files. The offeror shall validate indexing of IPDF files using the specifications contained in the Technical Order Conversion Requirements (TOCR) found at http://www.ide.wpafb.af.mil/toprac/working.htm.

12.3. Special Delivery Requirements. All Maintenance and Flight Manuals will be delivered in both CD-ROM and/or paper copy for the initial Aircraft G-File. All subsequent TO updates are expected to be delivered in digital format unless otherwise directed by the TOMA. Delivery of paper media may be required to support training or development testing activities.

12.4. Delivery Dates. TOs, TCTOs, Supplements, and Source Data shall be delivered as required by this TMCR. When scheduled delivery dates cannot be met, the offeror shall request an extension from the PCO, at least 60 workdays prior to the original dates. The request shall indicate why the delivery dates cannot be met, and provide an offeror recommended schedule and/or suggested work-around to support Air Force requirements.

This provision does not constitute authorization for the offeror to deviate from the delivery requirements set forth in the contract schedule.

13. Schedules. Offeror shall include TO program events and schedules in their proposed Integrated Master Plan (IMP) and Integrated Master Schedule (IMS). The offeror shall 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 acquisition phase of a program.

13.1. IMS Changes. Changes to the Technical Publications portion of the IMS must be coordinated with the HC/MC-130J TOMA/FMM or AC-130 TOMA/FMM, as applicable, and an updated copy will be provided to the appropriate TOMA/FMM.

14. Time Compliance Technical Orders (TCTOs). Offeror shall propose practices and procedures to develop AF TCTOs required as part of this contract. 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 part of the overall TCTO development.

14.1. Forms. The acquiring activity will furnish the offeror two copies of a completed AFMC Form 873 (Time Compliance Technical Order Requirements). As soon as the necessary retrofit design information is available, the offeror 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 prescribed 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.2. Companion Update Development. The offeror shall prepare updates and/or source data to correct all technical data whose contents are affected by TCTO equipment or procedures modifications.

14.2.1. Companion Update Procedures. The updates delivered in support of this modification will normally be a two time requirement. The affected technical data 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). The "Before" and "After" data will remain in the applicable technical data until the prime ALC verifies that the modification is completed, after which a second update removes the "Before" data and references to the TCTO.

14.3.

14.4. TCTO Review and Approval. After certification, the offeror shall furnish preliminary copies of TCTOs and companion updates for review, TCTO proofing and verification, and Government approval prior to preparation of reproduction media. Distribution of Preliminary TCTOs will be established by the contractual document authorizing the TCTO.

TCTO verification will be accomplished on production configured aircraft (i.e. Kit Proof Install aircraft) unless waivered by the TOMA. Offeror TCTO certification may be accomplished with verification approval the TOMA and Government program manager.

14.5. TCTO Delivery.

14.6.1. TCTO and Kits. When a TCTO and its kits are to be furnished by the same source, reproduction media shall be delivered no later than 30 calendar days prior to the date that kits are scheduled for delivery to the Government.

14.6.2. TCTO Only. When the offeror is responsible only for preparation of the TCTO (no kits required or kits to be delivered by another source), the reproduction media must be delivered no later than 20 calendar days prior to the need date specified in the contractual document(s) approving the TCTO. The offeror shall deliver reproduction media for immediate and urgent action TCTOs as soon as the information isavailable.

14.6.3. Companion Updates. When a TCTO results in new or changed technical data, reproduction media for the new material shall be delivered prior to, or concurrently, with the TCTO.

14.6. TCTO Type. The offeror shall contact the HC/MC-130J TOMA or AC-130 TOMA, as applicable, to determine if the modification will require a Records or DetailedTCTO.

15. Supplements. Offeror shall prepare supplements to enable USAF personnel to operate and maintain the system until such time as the new source data is incorporated into the existing aircraft technical data. The supplements shall be stand-alone to cover the all aspects of the modification. The supplements shall conform in style and format with the existing manual.

Additional information concerning source data can be found in TO 00-5-3 andMIL-STD-38784.

16. Source Data. The offeror shall provide all source data needed to update TOs impacted by the modification. The source data shall include detailed step-by-step procedures covering operation and maintenance of the system. The offeror shall also provide detailed illustrations (in CGM format) to enhance the content of the technical data being provided. Source data shall be subject to review at IPRs, verification and pre-publication review and as such shall be part of the review package submitted prior to these events. Additional information concerning source data can be found in TO 00-5-3 and MIL-STD-38784.

17. Automated Computer Program Identification Numbering (ACPIN) System. Offeror shall inform the TOMA of any software being developed for this modification so that a Computer Program Identification Numbering (CPIN) can be assigned. CPINs are covered by TO 00-5-16 (Software Managers and User’s Manual for the USAF Automated Computer Program Identification Number System). All electronic media, unless excluded by the PM/SPO, in direct support of a USAF or FMS weapon system that contains strategic data (operating system, PROM data, RAM data, UART logic, component drivers, etc.) that, if not available would impede the functional operation and support of a weapon system should have a CPIN assigned in ACPINS.

17.1. CPIN Assignment. CPIN assignment is accomplished by direct on-line data entry to the ACPINS or by AF Forms 1243 (ACPINS Data and Control Record). All CPINs are assigned and processed through the ACPINS database. Contact the TOMA for additional information.

17.2. Software Management Systems Section Responsibilities. The Software Management Systems Section at the Oklahoma City Air Logistics Center, Tinker Air Force Base, Oklahoma is the System Program Office (SPO) with Program Management responsibility for the ACPINS database. The ACPINS SPO is responsible for development, overall maintenance, control, user access, function and configuration management of the ACPINS.

The Software Management Systems Section may be reached at: OCALC/ENGLB, 7851 Arnold Street, Suite 205, Tinker AFB OK 73145-9147, toll free 1-888-742-4461, OCALC.ACPINS.workflow@tinker.af.mil.

18. TO Reproduction Management. Offeror shall propose practices and procedures for managing the program’s reproduction requirements. NOTE: Reproduction management for digital media consists of reproduction of the digital file on CD-ROM and distribution according to ID labels. CD-ROM labels shall contain all Classification, Distribution, Destruction, Disclosure, and Export Control Notice information as required in paragraph 9 of this TMCR.

SECTION 2.

PART A - TM TYPE AND DELIVERY REQUIREMENTS

NOTES: (IF REQUIRED)

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

Check the ASSIST database, http://dodssp.daps.dla.mil/assist.htm, for updated versions of the required TMSS prior to initiating any work on this proposal/ contract.

Manuals delivered using this table and DI-TMSS-80067, CFAE/CFE Notices, must be reviewed and approved by the Air Force prior to delivery.

Aircraft Battle Damage Assessment and Repair TOs only required if 1C-130J-39 is developed.

IPBs are developed in same style and format as existing manuals however the content will be IAW MIL-PRF- 38807 (Technical Manuals - Illustrated Parts Breakdowns).

All checklists, except aircrew and nuclear weapons checklists, are developed in same style and format as existing manuals however the content will be IAW MIL-PRF-5096 (Technical Manuals - Inspection and Maintenance Requirements).

MIL-PRF-83495 (Technical Manuals - On-Equipment Maintenance Manuals Set) requires DOD-STD-863 (Wiring and System Schematic Diagrams) 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.

For further information on the Air Force Vision and TO Concept of Operations (CONOPS), see URL http://www.ide.wpafb.af.mil/toprac/polinfo.htm.

TABLE 1

TMSS REQUIREMENTS FOR THE AC-130 PSP Modification Program

Title or Type of Manuals : Specification Required

AC / HC / MC

1. Inspection TOs MIL-PRF-5096

a. Inspection and Maintenance Requirements (-6) Manual

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

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

d. Workcards

e. Inspection Requirements Cards

f. Flow/Sequence Charts

g. Checklists

(1) Maintenance/Operations (Non-Aircrew)

(2) Operations (Aircrew)

(h) System Peculiar Corrosion Control

(i) Nondestructive Inspection (NDI)

TABLE 1

TMSS REQUIREMENTS FOR THE AC-130 PSP Modification Program

Title or Type of Manuals : Specification Required

AC / HC / MC

2. Cargo Aircraft Loading and Offloading TOs MIL-PRF-5288

a. Manual

b. Checklists

3. Weight and Balance (Aircraft) MIL-PRF-5920

a. Loading Data Manual

b. Sample Basic Weight Checklists

4. Flight Manuals (see notes) MIL-PRF-7700

a. Flight Manual

b. Performance Data Manual

5. List of Applicable Publications MIL-PRF-8031

6. Structural Repair Manuals (for Aircraft) MIL-PRF-9854

7. Munitions/Weapons Loading Procedures MIL-PRF-9977

a. Munitions Basic

b. Loading Procedures

c. Integrated Combat Turnaround Procedures

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

e. Loading Procedures Checklists

f. Integrated Loading Procedures Checklists

g. Integrated Combat Turnaround Procedures Checklists

h. NATO Stage B Cross-Servicing Checklists

8. Mobile Training Sets (MTS) and Part Task Trainer TOs MIL-PRF-9994

a. Single Manual

b. Single Manual w/IPB

c. General/Systems Trainer Manuals

d. General/Systems Trainer Manuals w/IPB

e. Part Task Trainer Manuals

9. Air Refueling Procedures MIL-PRF-38413

a. Manual

b. Checklist

10. Work Unit Code Manual MIL-PRF-38769

11. Calibration Procedures MIL-PRF-38793

TMSS REQUIREMENTS FOR THE AC-130 PSP Modification Program

Title or Type of Manuals : Specification Required

AC / HC / MC

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

13. Aircraft Battle Damage Assessment and Repair TOs(see notes) MIL-PRF-87158

14. Illustrated Parts Breakdown (see notes) MIL-PRF-38807

15. On-Equipment Organizational Maintenance Manual Set MIL-PRF-83495

a. General Equipment (GE) Manual

b. General System (GS) Manuals

c. Combined GE & GS Manual

d. Job Guide (JG) Manuals

e. Fault Reporting (FR) Manual

f. Fault Isolation (FI) Manual

g. Wiring Data (WD) Manual

h. Schematic Diagram (SD) Manual

16. Operation and Maintenance Instructions in Work Package Format MIL-DTL-87929

a. Maintenance Manuals

(1) Organizational Maintenance

(2) Depot Maintenance

(3) Combined (O&D) Maintenance

(4) On Condition Maintenance

b. Operation & Maintenance Instruction Manuals

c. Special Manuals

(1) Aircraft Engine Testing and Trending Procedures

(2) Aircraft Power Package Testing Procedures

(3) Static Firing of Missile Motors

(4) System Peculiar Corrosion Control

(5) Nondestructive Inspection (NDI)

(6) Aircraft Structural Integrity Program (ASIP)

(7) ATE Operator Test Procedures

(8) Special Requirements for Storage and Maintenance Procedures;

AUR Munitions/Launchers and Associated Support Equipment, Conventional Components and CMBR Agents

(9) Parachute Packing Procedures

(10) Operators Instructions (Hand-Held Flight Computers)

(11) Installation-Engineering Facility (Ground C-E Equipment)

d. Checklists (IAW MIL-PRF-5096)

e. With Illustrated Parts Breakdown (see notes)

17. Commercial Manuals (Evaluate according to MIL-PRF-32216

TMSS REQUIREMENTS FOR THE AC-130 PSP Modification Program

Title or Type of Manuals : Specification Required

AC / HC / MC

18. Aircraft Cross-servicing Guide MIL-DTL-22202

NOTES:

TABLE 2

ADDITIONAL TM TYPE SELECTIONS

This table is used to identify manuals not listed in Table 3 ofthis TMCR.

Additional manuals not listed in Table 2 and 3 may be affected and added to Table 2.

Check all applicable boxes.

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

STD-38784.”

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

TO Num

Type ber, Title, or of Manual Specifi n

Com-mercial catio Manual

Change/ Revision

Supple-ment

Supple-mental

TM

Source Data

1. 11W1-25-2 Same S and

Fo tyle rmat

2. 11W1-33-10-2 Same S and

F

3. 11W1-12-17-2

S and

F

4. 11W1-12-19-2

S and

F

5. 11W-15-21-2

S and

F

6. 00-105E-12

S and

F

TABLE 3

AC MANUAL LISTING

NOTE: This table contains a list of applicable AC-130 flight and maintenance TOs. Edit this list to identify which TOs are impacted by this modification. Delete all non-impacted TOs.

C-130(A)J Flight Manuals

MANUAL TITLE

C-130(A/H/M)J Maintenance Manuals

MANUAL TITLE

1C-130(A/H/M)J-2-29GS-00-1 General System, Hydraulic Systems

PART B - TM DELIVERY REQUIREMENTS FOR

AC-130 PROGRAM

PRECISION STRIKE PACKAGE (PSP) MODIFICATION

TM DATA TYPE DELIVERED TMSS/CHANGE/SUPPLEMENT/ETC.

(Replicate form for each TM type required.)

Delivery Format Requirements Codes Paper (draft or manuscript only. Cannot be used for final Digital delivery only:

delivery) G - Standard Generalized Mark-up Language (SGML).

I- Indexed Portable Document Format (IPDF) or PDF

Mixed paper and digital (M,I) X - EXtensible Markup Language (XML).

Native files for Maintenance, Flight, IPB, and Graphics C – Computer Graphics Metafile (CGM) Version 4

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 (e.g., EDCS) is a contractual requirement, copy quantity will normally be Ø (zero).

DELIVERY SCHEDULE

Event Number of days data required prior to event

Technical Review(s) (30Days)

Verification

Prepublication Review

(30Days)

Final TO Distribution

Enter Office Symbol and Address

Enter delivery requirements code/copy quantities required

AFLCMC/WISS Logistics

ATTN: AC-130 TOMA

1895 5th St. Bldg. 46 – Area B Wright-Patterson AFB OH 45433-7200 AC-130 – ALL Manuals

I/1

N,I,C/2

AFLCMC/WIUEG

ATTN: Bruce Gelinas 235 Byron St. Suite 19A Robins AFB GA 31098 AC-130 – IETMs Only

N,I,C/1

AFLCMC/WIUEG FMM

ATTN: Bill Mason 235 Byron St. Suite 19A

AC-130 – Flight Manuals Only

N,I,C/1

AFLCMC/WIUAD Equipment Specialist ATTN: Helmuth Ramster 235 Byron St. Suite 19A

AC-130 – ALL Manuals

Total Copies Required: I/4 I/4 I/4 N/I/C/4

Attachment 1: Sample TCTO

Attachment 1 (cont.): Sample TCTO