E016_TMCR_Attachment.pdf

Purchase Request

FD2060-14-30015

CDRL E016 Attachment 1 30 Oct 2014

Air Force Technical Manual Contract Requirements (TMCR) For

AC-130 Recapitalization Program

ATTACHMENT 1 TO CDRL SEQUENCE NUMBER E016 EXHIBIT 1

REQUEST FOR PROPOSAL/CONTRACT:

Date: 16 April 2012 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. TMCR Tailoring. Contractor MUST tailor this TMCR document, including the associated tables, matrices and Specification/Standard Interface Requirements (SIRs). The tailored TMCR shall be attached to the CDRL for TO delivery, and shall be included in the proposal as a separate exhibit, referenced in the proposal SOW. Proposals shall be compatible with the Air Force infrastructure and support the (Program Name) Program’s Integrated Data System (IDS) requirements.

United States Air Force (USAF) TO Acquisition procedures, including procedures for tailoring this document are found in TO 00-5-3, located on the World Wide Web (WWW) at http://www.tinker.af.mil/technicalorders/index.asp, under the link to “Digital Technical Orders.” Any terms or procedures found in this document may be researched there.

1.1 The Technical Order Management Agency (TOMA) is Aeronautical Systems Center (ASC)/WISML. Changes to technical order requirements shall be made only with the specific approval of the Procuring Contract Officer (PCO), ASC/WLNN. All actions as expressed herein are understood to be within the scope of the contract.

2. TO Program Scope. The system shall be designed to allow maintenance to be accomplished by United States Air Force (USAF) trained personnel. PDF files must be capable of display using portable display devices suitable for maintenance activities. Additionally, technical/training manuals must be display capable on standard desktop PCs in the administrative and staff offices of the maintenance units, MAJCOM, and support activities.

2.1. The Contractor shall tailor Section 2 to propose the TO types (Table 1) and source data, TO updates, commercial manuals (Table 2), and TOs prepared to Non-Government standards required to support the AC-130J Recapitalization program’s objectives. All Technical Manuals shall use Mil Specs listed in Table 1 as guidance for development.

2.2. [S] General. This Technical Manual Contract Requirements (TMCR) document was prepared to describe the required manuals, delivery instructions, and a compilation of the contractor tailored standards and specifications selected by the Contractor for the development and acquisition of Technical Manuals (TMs)/Technical Orders (TOs) for the contract. The TMCR has been tailored by ASC/WISML to add, change or delete requirements specifically for the USAF AC Recapitalization program, contract number (TBA). Supplemental (added) and tailored paragraphs are identified with the suffixes [S] or [T], respectively, to the paragraph number.

2.3. [S] Order of Precedence. In the event of a conflict between the text of this document and the references herein, the text of this document 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

CDRL E016 Attachment 1 30 Oct 2014 applicable to the equipment being acquired, including changes and/or revisions, 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.

3. [T] Commercial Manuals. Contractors 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.

Contractors shall propose a plan to utilize and identify known legacy information thru interoperability.

NOTES: a) Contractor Furnished Aeronautical Equipment/Contractor Furnished Equipment (CFAE/ CFE) Notices, Data Item Description (DID) DI-TMSS-80067B (http://dodssp.daps.dla.mil/assist.htm), may be used to provide recommendation data. b) The government 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.

3.1. [S] Commercial Manual Requirements. When commercial manual requirements are identified by an approved CFE/CFAE Notice and the resulting contract modification, the Contractor shall evaluate them for acceptability prior to submitting them to the Air Force for approval.

a. The Contractor shall include recommendations for supplemental data required for each commercial manual in the CFAE/CFE Notice or letter of recommendation. All commercial manuals will be evaluated by the USAF using MIL-PRF-32216 for acceptability and usability prior to delivery.

b. If adequate commercial manuals are not available from one subcontractor or vendor, the prime contractor shall evaluate alternate sources for the data, or recommend the most cost-effective alternatives to provide long-term maintainability of the equipment acquired.

c. If the Air Force disapproves or rejects a commercial manual, the contractor may, if cost effective, recommend a manual written to an appropriate MILSPEC or supplemental data, through the Contracting Officer, on a revised CFE/CFAE notice.

d. CFE/CFAE Notices will be used to develop manuals and supplements where no suitable commercial manuals exist.

e. Updated, changed or revised commercial manuals shall be provided to the government, as specified in the approved CFE/CFAE Notices, to reflect all configurations of hardware/software delivered to the Government during the period of performance.

3.2. [S] Commercial Manual Costs. The costs of obtaining or developing adequate commercial manuals shall be negotiated on a case-by-case basis if costs are undetermined at the time this contract is approved.

3.3. [S] Commercial Manual Numbers. The USAF will assign TO Numbers to commercial manuals approved for government use. When multi-manuals are furnished by the contractor, 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.

3.4. [S] Commercial Manual Title Pages. The Contractor shall print, stamp or otherwise mark the TO number, limited rights statements, date and any other required identification on approved commercial manual title pages (when space permits) or develop Identifying Technical Publication Sheets (ITPSs) for delivery with the manuals or reproduction media to the Air Force.

3.5. [S] Previously-Approved Commercial Manuals. When recommending use of commercial manuals, the contractor shall determine if they have been previously-approved for government use.

Refer to TO 0-4-6-2, Items Cross-Reference File, Equipment Numbers to Technical Order Numbers (available through normal TO distribution channels), or the Inter-Service Technical Information http://www.ide.wpafb.af.mil/toprac/polinfo.htm

CDRL E016 Attachment 1 30 Oct 2014

Exchange System (ITIES) database (see TO 00-5-1). 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 program TOs, 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 Nicholas A. Braun, ASC/WLNN, 1895 5th St. Bldg. 46 Wright-Patterson AFB OH, 45433-7200, (937) 255-1792, nicholas.braun@wpafb.af.mil . 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. [S] Content. Technical Manuals identified in this document are to be delivered to the government during the course of this contract. Updates to existing TMs will be prepared in a same style and format as the basic USAF TM. TOs identified in Section 2 of this document shall be prepared, using as a guide, 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 TO, 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. Contractors 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-80067B).

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 electronic mail, facsimile transmission, telex, telephone or other rapid means as directed by the acquiring activity.

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

6. [T] TO Development. The manuals proposed for the AC-130J Recapitalization program will be developed from existing Lockheed Martin commercial format manuals prepared to provide operational and maintenance procedures for the MC-130J aircraft. These manuals will be tailored so that only the AC-130J aircraft configurations are covered. The manuals were developed to Lockheed Martin style and format based on USAF specifications. The manuals are similar in style and content as the manuals that are currently in use with the USAF to operate and maintain their MC-130J aircraft. The contractor shall prepare and deliver technical orders in two sets consisting of Flight and Maintenance. Computer Graphics Metafile version 4 (CGM-4) will include a deliverable for total Flight Manuals graphics (only one copy of multi-use graphics files is required, repetition of graphics file is not required) and a deliverable for the Maintenance Manuals for only AC configuration-unique graphics files, difference data graphics only. (See Attachment 1) .

http://www.ide.wpafb.af.mil/tmss/index.html

CDRL E016 Attachment 1 30 Oct 2014

6.1 [S] Interactive Electronic Technical Manuals (IETMs) shall be developed IAW MIL-PRF-87268 Manuals, Interactive Electronic Technical General Content, Style, Format, and user integration requirements, and MIL-PRF-87269 Performance Specification for the Support of Data base, Revisable- Interactive Electronic Technical Manuals. Additional requirements for MIL-PRF-87268 and MIL-PRF- 87269 are included in the SIR found in Section 3 of this document. The Contractor shall use the C-130 IETM Data Entry Tool (IDET) to input changed/updated data in accordance with the attached style guide. The Contractor shall download existing task data using the IDET import task tool and input the difference data as required. IDET Packages shall be submitted at the task level for JGs, FIs, GS, work card manuals and submit system level packages for IPBs and wiring. The Contractor shall download existing graphics and wiring diagrams and insert changes. Existing graphics may be downloaded from the IDET Ping Library, Data Courier Web, or Wire Illuminator Web. Job Guide packages can be further broken down into Install, Remove, Preparation and Required Conditions and Operational Check Out per the attached C-130 IETM style guide.

6.2. [S] Format. TOs delivered by the contractor will be developed, written, and maintained to be in the same style and format to the equivalent/corresponding USAF TOs and produced to the same specification and quality standards. 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.3. [T] As a priced option the manuals can be prepared as SGML-tagged TO files including required illustration (graphics) files in an approved graphics exchange format (select “Guidelines” and “Graphics” on the Technical Manual Specifications and Standards (TMSS) web page (http://www.ide.wpafb.af.mil/tmss/index.html.). NOTE: Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible.

6.4. The Contractor 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 from the Air Force Preparing Activity (PA), ASC/WISM, Technical Order Section, 4375 Chidlaw Rd Suite 6, WPAFB OH 45433-5006.

6.5. [S] Occupational Safety and Health. Using AFI 91-301 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.6. [T] Flight Manuals Operational Supplements will be developed and delivered as plug and replacement change pages unless otherwise mutually agreed upon between the contractor and TOMA. Plug and replacement supplements are prepared on a contractually agreed to price-per-page basis.

6.7. Illustrated Parts Breakdown (IPB) manuals shall conform to the numbering concept utilized for the maintenance manuals.

6.8. [T] Changes required in the contractor baseline manuals to incorporate engineering, PCRs identified during OT&E, omissions, errors or deficiencies will be required at least every 180 days, ftp://ftp.jclark.com/pub/SGMLS

CDRL E016 Attachment 1 30 Oct 2014 unless wavered by the TOMA. All the above shall be reviewed during a prepublication review, hosted by the contractor, prior to delivery and distribution of the formal data.

6.9. [S] Preliminary Technical Orders (PTOs). 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 Contractor, and approved by the TOMA. PTOs and source data shall be provided or delivered for Verification, and Prepublication Reviews as specified by Section 2. In formatting technical manuals use MIL-STD- 38784 and the applicable MIL SPECs, as guides, except as noted below.

6.10. [S] PTO Format. The Contractor shall develop PTOs in the same style and format as existing manuals, for use during verification and provide them in accordance with Section 2. 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. PTOs may be issued initially in single-column, single-sided, double-spaced format on bond or computer paper, and may contain voids and photographs and/or art boards instead of line drawings, as approved by the acquisition agency on a TO-by-TO basis.

6.11. [S] Supplemental Manuals. The contractor shall furnish supplemental manuals in the same style and format as the original manual, or as required by specifications cited in Table 2.

Supplemental manuals are normally used to segregate classified from unclassified TO data. The Title Page of the supplemental manual shall contain the statement, "This manual is incomplete without TO NOXX-XXXXX-XX". Supplemental manuals differ from supplements in that they are assigned a separate TO number and are not incorporated in the referenced manual at a later date.

7. TO Numbering. Contractor shall notify the government of manuals which require TO numbers. TO numbers are not required for manuals to be used exclusively by contractor 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 (available under the link to “Digital Technical Orders” at http://www.tinker.af.mil/technicalorders/index.asp

8. [T] Data Rights. Government rights in data are specified in the Defense Federal Acquisition Regulation Supplement (DFARS), paragraphs 227-7102 through 227-7104. Contractor shall propose Unlimited Rights for all source data and TOs or portion thereof 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 If some TOs or source data are copyrighted or contain proprietary data or procedures, contractors 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.

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. Contractor shall propose methods for determining, marking and controlling classified and restricted distribution data and TOs IAW government requirements specified in DOD 5200.1-R, DODD 5230.24, AFIs 21-303, 31-401 and 61-204, and MIL-STD-38784. 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 classified

CDRL E016 Attachment 1 30 Oct 2014 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 issue updates when data classification is upgraded.

9.2. [S] Copyrights and Proprietary Data. A commercial manual, a manual written to military specifications specifically for the government or supplemental data to these manuals may contain copyrighted information and proprietary data.

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

10. [T] TO Quality. Contractor shall propose a quality assurance program which ensures TOs prepared are: a) 100% technically accurate using TO 00-5-3 as guidance; b) written to a scope and depth of coverage sufficient to support the operations and maintenance concepts, and to the ninth grade Reading Grade Level (RGL) as specified in MIL-STD-38784; c) 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 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. Contractor proposals should 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 will performance-test all JNWPS and EOD TOs.

10.1. [T] Conferences and Technical Reviews. The required conferences and technical reviews are governed by SPI Number 2000-07, Commercialization of Tech Pubs, Dated 25 October 2000.

Conferences and technical reviews in excess of those covered by the SPI will be priced as an option.

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 reviews to provide 30 calendar days notification to the TOMA. The TOMA and Prime Contractor shall schedule such conferences, reviews, or inspections to provide a minimum of 14 calendar day notification to all participating activities. Conferences and reviews are to control and manage 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. Development and review of IETM changes shall take place after government PPR comments are generated for PDF deliverables. Review of IETM changes shall be electronic and performed online in the IDET environment. The IDET review process shall consist of two reviews: Initial and Pre-Integration.

10.1.1.1 (T) ITR Requirements for the IETM

1. (T) Initial Review. To meet criteria for the Initial Review, The task in IDET must contain 80% of the source data of the required change (i.e. 80% of an installation task is complete). Review is to be accomplished by the IETM Technical Order Management Authority (TOMA) for Style and Format and by the Technical Content Manager (TCM) for technical content.

2. (T) Pre-Integration Review (ready to parse). The requirements for Pre-Integration Review are the same as initial review except for the percentage of data present in the IDET database at the time of the ITR. The Pre-Integration Review shall contain 100% of the source data required for the change.

The Pre-Integration Review is the final technical content review by the TCM before the task is

CDRL E016 Attachment 1 30 Oct 2014 parsed into the IETM. Customer approval of Pre-Integration Reviews shall constitute completion of IETM delivery requirements.

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.2.1 [T] IPR Review comments recorded on AFTO Form 158 shall be provided by the contractor within 10 working days of said review.

10.1.3. [S] Guidance Conference. Not required by SPI, will be priced as option. The Contractor shall host an initial Guidance Conference or Technical Interchange Meeting (TIM) within 60 days of start of TO development to ensure mutual understanding of TO contract requirements, schedules, points of contact, etc.

10.1.3. [S] In-Process Reviews (IPR). Not required by SPI, will be priced as option. 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, and Supplements for review prior to the preparation of reproducible media.

10.1.4. [S] Pre-Publication Reviews (PPRs). The Contractor shall prepare and provide draft copies of Preliminary TOs, Changes, Revisions, and Supplements for review prior to the preparation of reproducible media. PPRs shall be grouped by TO types, series and location. The TOMA may waive the review on a TO-by-TO basis.

10.2. TO Certification. Contractor shall propose their method for documenting certification that TO procedures are accurate, adequate, current, and usable for their intended purposes.

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. Fault reporting, fault isolation and flight data shall be validated by desk-top analysis. Structures and Non-Destructive Inspection (NDI) data shall also be validated by desk top analysis unless a "new" procedure is developed. Flight manuals shall be validated via the LM 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 AC-130J procedures not previously validated prior to incorporation. AC-130J unique systems with procedures previously validated on other weapon system platforms or MC-130 configurations will be evaluated for differences introduced during integration on the AC-130J platform. Such procedures will be subject to re-validation of the data, as required. Validation entails the actual performance by contractor personnel of all operating and maintenance (O&M) procedures, including but not limited to system 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 damage to system/equipment or injury to personnel may occur, and if approved by the TOMA, validation of these instructions may be by simulation. All other data 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.

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

CDRL E016 Attachment 1 30 Oct 2014

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 and the documented policy contained in 00-5-19.

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 desk top analysis must be approved by the TOMA or a designated representative.

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

10.2.7. [S] Validation Scheduling. Schedules should be established by system, task, or by component, and should be consonant with attainment 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" (provide explanation). When contracting paper and IETM media simultaneously, Contactor is not required to perform validation of IETM.

10.3. Verification Support. Contractor shall propose the methods, equipment and personnel required to maintain the aircraft (i.e. towing, applying power, etc.) to support government TO Verification.

This support should consist of at least one technical writer familiar with the TO(s) being verified, a sufficient number of engineers (telephone stand by) to resolve problems during verification to preclude delays during the process and sufficient mission and support equipment to complete all tasks being verified. When contracting paper and IETM media simultaneously, Contactor is not required to perform Verification of IETM. IETM Verification shall be the responsibility of the IETM TOMA and shall be accomplished by comparing IETM dataset display media to the content and intent of Verified paper media.

10.4 [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.5 Minutes For TO Events/Reviews. The results of each TO events/reviews will be fully documented by minutes. Comments from individual TO reviews (IPR/Ver/PPR) shall be recorded real time and documented on AFTO Form 158, TO Review Comment Sheet (or equivalent form).

The Government will complete AFTO Form 27s, as required. Following the guidance of TO 00-5-3, Contractor shall prepare minutes that summarize TO events/reviews findings for all TO-related meetings (to include actions items and completed AFTO Form 158s) for approval prior to completion of each meeting. The acquisition TOMA and other key players will review and indicate

CDRL E016 Attachment 1 30 Oct 2014 concurrence with the minutes prior to closure of the meeting; a final copy shall be provided IAW DI- ADMN-81250A. Contractor shall maintain a complete file of minutes; minutes may be made accessible to the Government via email within 10 workdays of said review.

11. TO and Source Data Maintenance. Contractor 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 TO Changes, revisions and supplements. In addition, when specified in Section 2, Part B, updates shall be prepared for TOs affected by, but not developed as a part of, this contract. All updates shall conform to the same style and format requirements of the manual being updated. These updates shall be furnished throughout the period of performance. TO updates incorporate engineering change data, PCRs identified during OT&E, omissions, errors or deficiencies and will be required at least every 180 days, unless waivered by the TOMA. Changes may be more frequent if warranted and when mutually agreed to. Changes delivered in less than the 180 day cycle will be considered as next 180 day delivery and will not reset the 180 day cycle. Changes in excess of two per year are subject to additional cost.

11.2.1. [S] Types of TO Updates.

11.2.1.1. [S] TO Changes. A TO Change shall be prepared in the same style and format as the basic manual.

11.2.1.2. [S] Revisions. A revision is a new edition of an existing TO incorporating all previous and current changes and supplements. A revision is normally issued 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 offeror recommendation IAW AFMC MANUAL 21-1.

11.2.1.3. [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 formal supplement. The TOMA will determine development of supplements or source data on a case-by-case basis. The Contractor shall prepare TOMA directed out-of-cycle routine supplements on a contractually agreed price-per-page basis.

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

CDRL E016 Attachment 1 30 Oct 2014 correction of typographical errors, parts identification, rescission of TCTOs, Service Bulletins etc.

Technical errors and omissions found in data that are part of the baseline Lockheed Commercial Manuals 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 acquisition agency Configuration Control Board (CCB), and AFTO Forms 22, 27 and 847 must be approved by the Technical Order Review Board (TORB) or Flight Technical Order Review Board (FTORB) prior to implementation.

11.2.3.1. [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 update cycle.

11.2.3.2. [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 updates will not be separately priced. They shall either be included with the next routine update, or, if applicable, developed as emergency or urgent updates.

11.2.4. [S] Categories of Updates.

11.2.4.1. [S] Routine Updates. Routine updates are those non-urgent TO Changes and revisions which shall be required at least every 180 days. Contractor shall comply with response times for Routine PCRs in accordance with 00-5-1 or AFI 11-215 as appropriate. 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.

11.2.4.2. [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 Service Bulletins, Airworthiness Directives, Interim Operational or Safety Supplements (IOSs or ISSs, message format), formal Operational or Safety Supplements, or interim or formal TO Field Change Notices (ITOFCNs or TOFCNs).

Contractor 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 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 request 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 technical content of the changes. However, the contractor will be held liable for the accuracy of the change during incorporation. The Contractor shall prepare TOMA directed changes on a contractually agreed price-per-page basis.

12. TO Delivery. Contractors 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

CDRL E016 Attachment 1 30 Oct 2014 program support data. Practices and procedures shall be compatible with the program’s IDS (found in (specify RFP location of 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. 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. [T] SGML-Tagged Files. As a priced option 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. 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 at http://www.ide.wpafb.af.mil/toprac/working.htm.

12.3. [S] 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 delivery as directed by contract CDRL documents. All subsequent TO updates are expected to be delivered in digital format unless otherwise directed by the Acquiring TOMA via CDRL callouts. Delivery of paper media may be required to support training or development testing activities.

12.4. [S] Submittal Procedures. Reproduction media for TOs shall cite the appropriate contract number and be submitted with assembly instructions to the printing control activity or as specified by the TOMA.

12.5. [S] TO Update Delivery. Routine updates to maintain the currency and accuracy of Lockheed Commercial Manuals or Mil-Spec TOs shall be submitted every 180 days unless waivered by the TOMA. 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 accuracy) TO updates and 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.

12.6. [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 60 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-arounds 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.7. [T] Digital media delivered 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 Document Automation and Production Service (DAPS).

13. Schedules. Contractor 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 acquisition phase of a program.

13.1. Changes to the Technical Publications portion of the IMS must be coordinated with the TOMA/FMM and an updated copy will be provided to the TOMA/FMM.

http://www.ide.wpafb.af.mil/toprac/working.htm http://www.dodssp.daps.dla.mil/assist.htm

CDRL E016 Attachment 1 30 Oct 2014

14. Time Compliance Technical Orders (TCTOs). Contractor 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, AFMCI 21-302 and AFMCMAN 21-1 (available under the links to “Digital Technical Orders” and “Publications” at http://www.tinker.af.mil/technicalorders/index.aspfor a detailed description of the TCTO system.

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 from which the requirements were derived.

14.1.1. [S] ECP Driven Efforts. When directed by an ECP, the contractor shall develop and furnish TCTOs, using MIL-PRF-38804C as a guide, and the AFMC Form 873 will be provided by the government. TCTO data shall be encoded (tagged) according to MIL-STD-1840, it’s associated MILSPECs as guidance. 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.1.2. [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 design 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 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. [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.2.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). The "Before" and "After" data will remain in the applicable manuals 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.2.2. [S] Companion Update Delivery. These updates will normally be developed as TO supplements in order to meet response times required by the TCTOs. They will be incorporated in the affected TOs during the next routine TO maintenance cycle.

14.3. [S] TCTO Prototyping and Validation. All TCTOs and Companion Updates will undergo a kit proofing, performed by the contractor. Kit proofing is the validation of all information and procedures in the TCTO/Update, including actual performance of kit installation into a configured end item, if required.

14.4. [S] TCTO Review and Approval. After validation and/or contractor prototyping, the contractor shall furnish preliminary copies of TCTOs and Companion Updates for review, TCTO proofing and

CDRL E016 Attachment 1 30 Oct 2014 verification, and government approval prior to preparation of reproduction media. Distribution of Preliminary TCTOs will be established by the contractual document authorizing the TCTO.

Contractor TCTO prototyping and validation may be accomplished with Air Force kit proofing and verification with approval of the TOMA.

14.5. [S] Copies of TCTOs for Kits. As required in appropriate ECP and appropriate contract CDRL actions.

14.6. [S] TCTO Delivery.

14.6.1. [S] 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 20 calendar days prior to the date that kits are scheduled for delivery to the Government.

14.6.2. [S] TCTO Only. When the contractor 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 contractor shall deliver reproduction media for immediate and urgent action TCTOs as soon as the information is available.

14.6.3. [S] Companion Updates. When a TCTO results in new or changed TO, reproduction media for the new material shall be delivered prior to, or concurrently, with the TCTO. The following delivery schedule shall apply:

14.6.3.1. [S] Routine. Reproduction media for routine updates where "Before" and "After" data is reflected shall be delivered as soon as the data is verified by the government (normally during TCTO proofing), and can precede the TCTO. As a minimum, they shall be delivered concurrently with the TCTO reproduction media. Reproduction media for updates reflecting only "After" data must be delivered concurrently with the TCTO data. Updates deleting "Before" data shall be included with the first routine TO update (11.2.4.1 and 12.5) after notification of TCTO completion is received.

14.6.3.2. [S] Immediate and Urgent Action. Updates shall be delivered to the government in supplement format in accordance with the timelines of 00-5-1. The government will transmit the Supplements to all affected TO users.

15. TO Reproduction Management. Contractor 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 magnetic/optical media and distribution according to ID labels.

16 [S] General. The following paragraphs provide detailed TO development and delivery requirements for the AC-130J Recapitalization Program, including requirements for source data and updates.

16.1 [S] Baseline Technical 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-M-83495 and MIL-M-38784C (guidance documents).

Manuals are to be developed from the Lockheed Commercial baseline and be customized for USAF unique and…