Sec_J _Attachment_31_-_TMCR_10_01_2012.pdf

FA8629-12-R-2400

Sect J, Atch 31, TMCR

TM-86-01N (CRH) 01 October 2012

Air Force Technical Manual Contract Requirements (TMCR) For The

Combat Rescue Helicopter (CRH)

FOR CDRL SEQUENCE NUMBER

B005

1.1 SECTION 1. TECHNICAL MANUALS (TM)/TECHNICAL ORDER (TO) PROGRAM

REQUIREMENTS

1.

1.1. The contractor shall provide their contractual comprehensive approach to the development, certification and delivery of all TOs required to fully meet the Government’s identified technical data requirements within each section associated tables and appendices contained in this TMCR. No tailoring of this TMCR is allowed without prior Government approval and the contractor shall not delete any Government identified requirements but may identify additional TOs or capability required to support the CRH weapon system.

General.

1.2. The completed contractual TMCR shall be: (1) Attached to CDRLs for TO delivery (2) referenced in the System Specification.

1.3. Air Force TO acquisition procedures for this document are found in TO 00-5-3, AF TO Life Cycle Management.

2.

2.1. The CRH Platform requires technically usable TOs that are safe, current, accurate, adequate and concurrent with aircraft configuration. These TOs will support all facets of the CRH System to include; Operation, Maintenance, Installation and Training (OMIT). Additionally, these technical manuals shall meet the requirements for flight operations, Organizational level (O-level) and Depot level (D-level) maintenance. The Government intends to support this aircraft with an organic two-level maintenance concept utilizing O-level “blue-suit” three, five and seven-skill level maintainers and organic D-level personnel. All TOs will be developed to support use by AF three, five and seven-skill level personnel.

TO Program Scope.

2.2. In accordance with TO 00-5-3; “All new major acquisition programs must acquire TOs in a Type 2 Interactive Electronic Technical Manual (IETM) database format . . . IAW ASD/AIA- S1000D Issue 4.0.1 and the latest version of Published Air Force XML Business Rules (BR).”

Contractor shall refer to Section 2, Table 1 and Section 3. All references to S1000D within this TMCR are baselined on ASD/AIA 1000D Issue 4.0.1 and the AF and CRH business rules contained in Section 3 of this TMCR.

2.3. All AF flight manuals will be provided in both digital and paper formats, including use of hyper linking as practical. All maintenance TOs will be authored in IETM database structure using the S1000D process data module to support maintenance activities for the aircraft and engines. The S1000D publications module will only be used to support printing of IETM content or generation of PDF files. All usage of the publications module shall undergo formal approval from the Government.

2.4. The contractor may provide existing commercially available manuals that meet all CRH S1000D and TMSS requirements contained in this TMCR and IAW MIL-PRF-32216. The contractor shall support the Government verification of commercial manuals and the integration of government changes required resulting from this review. The contractor shall also provide “on-aircraft” support (engineering and TO writers) as needed for these

Government verifications. Commercial manuals that do not meet stated requirements shall be converted into the CRH organizational or depot level IETM at no cost to the government.

2.5. Unlimited or Limited/Restricted data rights shall be provided for all manuals, including all graphics, DTP, SGML/XML, scripts and other software products necessary to accomplish organic AF sustainment, distribution and viewing of the IETMs/TOs. If Unlimited or Limited/Restricted data rights cannot be delivered, contact: Lisa Meyer (Contracting Officer) at Commercial (937)255-4093.

2.6. The contractor shall certify all delivered technical manuals in this TMCR.

2.7. The contractor shall incorporate applicable vendor/supplier O-level operation and maintenance manuals for aircraft components into the IETM and TOs.

2.8. The contractor shall supply a complete CRH baseline IETM.

2.9. The contractor shall develop, certify, and incorporate Nuclear Hardness Maintenance Requirements and Procedures for all affected aircraft systems and subsystems requiring this type of protection into the baseline maintenance IETM.

2.10. The contractor may identify Electronic Flight Bags (EFBs) or E-Tools for operators in lieu of MIL-DTL-7700 Flight Manuals with Government approval. If identified for use; the EFBs/E- Tools as delivered, shall meet all data requirements addressed in MIL-DTL-7700G, the AF unique requirements and kept current with all TO and aircraft configuration changes.

2.11. The contractor shall develop and implement incorporation procedures for Government originated changes as the result of both Government performance verification and Initial Operational Testing and Evaluation (IOT&E) to all TOs.

2.12. For TOs in development, the contractor shall develop and implement change processes that allow the incorporation of Government-originated (AFTO Form 22s or AF Form 847s) changes to flight, performance and maintenance TOs. The contractor will be responsible for sustainment of all AF TOs and IETMS until formal delivery of all

2.13. The contractor shall ensure all TOs are concurrent with the aircraft configuration prior to formal delivery.

CRH TOs. This includes sustainment of graphics, software and infrastructure, TO content, printed output, instructions and hardware necessary to sustain CRH TOs.

2.14. The contractor shall provide all software, hardware and tools required to allow on-line access, viewing and updates to all TOs which ensures currency of data and provides automated electronic updates to TOs stored on maintainers’ e-Tools.

2.15. Flight manuals shall be distributed in an electronic format that facilitates printing for fully formatted print/book version.

2.16. The contractor shall ensure all flight/operation and maintenance TOs shall be displayed IAW additional requirements as defined in the System Specification.

2.17. The contractor shall deliver all Depot-level TOs, including supplier/vendor manuals, in ASD/ASI S1000D, XML-tagged IETM format for the aircraft, systems, engines and all subsystem components in support of the Government’s organic depot capability not later than four years after initial operational capability in accordance with 10 USC section 2464(a)(3)(B).

2.18. The contractor shall develop and deliver Operations, Maintenance, Installation and Training (OMIT) TOs IAW ASD/ASI S1000D Issue 4.0.1 XML-tagged IETM, AF BR, CRH BR, Table 1, Table 2, and applicable System Specification paragraphs to fully support organic organizational and depot levels of maintenance.

3.

3.1. The contractor shall develop and implement a process for notifying the Government when additional TOs or source data requirements are identified. This process shall require Government review and approval.

Subsequent TO/Data Requirements.

3.2. All external process requirements contained in the Functionality Matrix must interface with existing AF data systems. AF processes and systems are identified in AFI 21-101 and

AFMAN 23-110.

4.

4.1. The contractor shall describe how the Government will interact with the contractor’s TO development team.

TO Development.

4.2. The contractor shall write all TOs to a scope and depth of coverage sufficient to support the operations and maintenance concepts and to the Reading Grade Level (RGL) specified in MIL-STD-38784. The contractor shall utilize American/U.S. Standard measurement values (i.e. feet, inch pounds, gallons, knots per hour) in all manuals.

4.3. Unless otherwise directed by the Government, the contractor shall develop and deliver all TOs IAW with ASD/AIA S1000D, Issue 4.0.1, International Specification for Technical Publications Utilizing a Common Source Database, the latest version of the AF S1000D IETM XML Business Rules. All TOs shall make use of the S1000D Process Data Module (PDM) in order to be considered an IETM for CRH purposes. Use of the S1000D Publications module will only be used to allow printing of TO content in page-based format consistent with AF Business Rules or AF Technical Manual Specifications and Standards (TMSS) style and format requirements (Table 2).

4.4. The S1000D Business Rules take precedence over the TMSS specified in Section 2. Where not addressed in the business rules, the contractor shall develop TO files (XML tagged instances) according MIL-STD-38784 (Table 2) and each applicable military detail or performance specification (MIL-DTL or MIL-PRF) (Table 2).

4.5. The contractor shall include required illustration (graphics) files in an approved graphics format for all XML-tagged TO files. All CRH graphics will be provided in vector-based format and not include proprietary linking or coding. NOTE: Illustration files developed and delivered for other purposes shall be used in lieu of developing special TO illustration files whenever possible.

4.6. Changes to business rules are not allowed without contacting the TO Manager and PCO/CO for pre-approval in writing. DTDs, schemas and rule sets submitted and approved in execution of the contract shall become the property of the Government.

5.

5.1. The contractor shall address all questions concerning TMSS requirements by written request and justified suggestions for resolution submitted through the PCO and the TO Manager.

TMSS Requirements.

6.

6.1. The contractor shall notify the TO Manager of any manuals which require TO numbers. AF procedures for numbering TOs are described in TO 00-5-3 and TO 00-5-18.

TO Numbering.

7.

7.1. The contractor shall provide Unlimited or Limited/Restricted data rights for all baseline non-military aircraft and engine commercial manuals; all source data and/or TOs prepared specifically for this contract; including any TOs that are copyrighted, contain proprietary data or procedures.

Data Rights.

8.

8.1. The contractor shall determine the correct markings and controls for classified and restricted distribution data and TOs IAW DOD 5200.1-R, DODD 5230.24, AFIs 63-101, 31-401, 61- 204 and MIL-STD-38784. 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 and are dependent upon TO content.

Classification, Distribution, Destruction, Disclosure and Export Control Notices.

9.

9.1. The contractor shall develop and implement a Quality Assurance (QA) program which ensures TOs are prepared IAW this contract. QA methods shall 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 an unacceptable hazard to personnel or equipment. The contractor’s QA methods shall ensure engineering reviews are completed prior to Government verification/re-verification.

TO Quality.

9.1.1. Conferences and Technical Reviews.

9.1.1.1. The contractor shall conduct conferences and reviews to allow insight into TO development processes and ensure contract compliance. The contractor shall co-host an initial Guidance Conference within 60 days after contract award to ensure mutual understanding of TO contract requirements, schedules, points of contact, etc. The contractor shall conduct periodic In-Process Reviews (IPRs) at the 40%, 80% and 100% completion levels as referenced in TO 00-5-3 in preparation for Government verification; and a Prepublication Review (PPR) to ensure TOs are being developed according to contract requirements and that open discrepancies are cleared prior to publication. The contractor can propose alternate IPRs at the TO Guidance conference to optimize the review of TO content. All alternate IPRs shall be approved in writing by the PCO and TO manager.

9.1.2. TO Certification.

9.1.2.1. The contractor shall develop and implement their method for documenting certification that TO procedures are safe, current, accurate, adequate, concurrent with aircraft configuration and technically usable for their intended purposes. Certification shall be completed prior to the Government performing its verification of all TOs.

9.1.3. TO Verification Support.

9.1.3.1. The contractor shall develop and implement methods, equipment and personnel required to support Government TO Verification. This contractor-provided support shall consist of as a minimum:

1) Dedicated (on-aircraft) Engineer(s) knowledgeable of the baseline aircraft airframe, systems, engines and subsystems.

2) The appropriate number of technical writers/data programmers to author real-time changes to TOs as the result of the verification effort.

3) The contractor shall provide a dedicated, on-aircraft, qualified maintainer to support all AF Technical Order Verification (TOV) activities to ensure procedures are conducted safely and ensure “return to service” documentation requirements are completed.

9.1.4. TO Review Boards and Flight TO Review Boards.

9.1.4.1. The contractor shall also participate in all TO Review Boards (TORBs) and Flight Manual TO Review Boards (FTORB) s.

10.

The contractor and the program office with the assistance of 754 ELSG/ILMT will determine the TDA requirements for each TO type. The contractor shall submit an in-work sample of each type of XML-tagged TO file to the program office concurrent with the 80% IPR for TDA to verify compliance of the digital files. Repeat TDAs shall be required whenever new DTD or schemas are used for TO development. TDA in no way relieves the contractor from correcting tagging errors identified during the composing effort.

Technical Data Assessment (TDA).

11.

11.1. The contractor shall develop and implement 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.

TO and Source Data Maintenance.

12.

12.1. The Contractor shall develop and implement practices and procedures for secure access to and delivery of, digital TO files including those for Preliminary TOs (PTOs), source data, reproduction masters and program support data. TO delivery shall be according to TO Delivery Requirements contained within this TMCR.

TO Delivery.

12.1.1. XML-Tagged Files.

12.1.1.1. The Contractor shall parse and compose XML-tagged TO document files prior to delivery to the government and verify content tagging has been accomplished to the levels provided in the DTD or XML schema.

13.

13.1. The Contractor shall include all TO program events and schedules in their Integrated Master

Plan (IMP), 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 63-101, Technical Orders). This policy will determine TO development and delivery schedules throughout the acquisition phase of a program.

Schedules.

14.

14.1. The Contractor shall develop and implement practices and procedures for related TO updates when tasked as part of the approval process for Engineering Change Proposals, Contract Change Proposals and Time Compliance Technical Orders (ECPs/CCPs/TCTOs). Costs for TCTO package development shall be included in ECP Costs – not included as direct proposal

Engineering Change Proposals/Contract Change Proposals/Time Compliance Technical Orders (ECPs/CCPs/TCTOs).

costs. NOTE: ECPs are reviewed and approved by the Government’s Configuration Control Board (CCB). When the CCB decides that a TCTO is the appropriate method of implementation, the contractor may be requested to develop the TCTO package for Air Force coordination and approval. See TO 00-5-15, Air Force Time Compliance Technical Order Process for a detailed description of TCTO processes.

14.2. TO Reproduction Management. The contractor shall develop and implement a reproduction management process for digital media consisting of reproduction of the digital file on magnetic/optical media and distribution. Reproduction management may also include configuration control and storage of master TOs.

SECTION 2. TM/TO TYPE AND DELIVERY REQUIREMENTS

NOTE:

The TM Type Selection Tables indicate the applicable TO types for CRH TOs. In case of a conflict, the S1000D specification and AF S1000D BR take precedence over content specific requirements contained in applicable TMSS specifications.

TABLE 1 - TMSS REQUIREMENTS FOR THE CRH MODERNIZATION PROGRAM

1. Inspection TOs

a. Inspection and Maintenance Requirements (-6) Manual

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

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

d. Work cards

e. Inspection Requirements Cards

f. Flow/Sequence Charts

g. Checklists

(1) Maintenance/Operations (Non-Aircrew)

(2) Operations (Aircrew)

MIL-DTL-5096

2. Cargo Aircraft Loading and Offloading TOs

a. Manual

b. Checklists

MIL-DTL-5288J

3. Weight and Balance (Aircraft)

a. Basic Weight Checklist and Loading Data

b. Sample Basic Weight Checklists

c. Tabular performance manual

MIL-PRF-5920F

TO 1-1B-50

4. Flight Manuals

a. Flight Manual (-1)

b. Pilot/ Copilot CL-1

c. Air/Ground Ops CL-2

d. Performance Data Manual

e. Air Refueling Checklist

MIL-DTL-7700G

5. List of Applicable Publications MIL-DTL-8031G

6. Structural Repair Manuals MIL-DTL-9854D

7. Munitions/Weapons Loading Procedures, Non- nuclear and Nuclear

a. Non-nuclear Munitions Basic

b. Non-nuclear 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

MIL-PRF-9977

8. Work Unit Code Manual

With Accompanying Software Tables for Work Unit Codes, How Malfunction Codes, When Discovered Codes, Type Maintenance Codes and Action Taken Codes

MIL-PRF-38769

9. Calibration Procedures MIL-PRF-38793

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

11. Aircraft Battle Damage Assessment and Repair TOs MIL-DTL-87158C

12. Illustrated Parts Breakdown MIL-PRF-38807

13. On-Equipment Organizational Maintenance manual Set

a. General Equipment (GE) Manual

b. General System (GS) Manual

c. Combined GE & GS Manual

d. Job Guide (JG) Manuals

MIL-PRF-83495

e. Fault Reporting (FR) Manual

f. Fault Isolation (FI) Manual

g. Wiring Data (WD) Manual

h. Schematic Diagram (SD) Manual

14. Operation and Maintenance Instructions in Work Package Format

a. Maintenance Manuals

1. Depot Maintenance

2. On Condition Maintenance

b. Operation & Maintenance Instruction Manuals

c. Special Manuals

a. Aircraft Engine Testing and Trending Procedures

b. Aircraft Power Package Testing Procedures

c. System Peculiar Corrosion Control

d. Nondestructive Inspection (NDI)

e. Aircraft Structural Integrity Program (ASIP)

f. ATE Operator Test Procedures

g. Special Requirements for Storage and Maintenance Procedures;

Munitions/Launchers and Associated Support Equipment, Conventional Components and agents.

h. Operators Instructions (Hand Held Flight Computers)

i. Installation Engineering Facility (Ground C-E Equipment)

d. Checklists (IAW MIL-PRF-5096)

MIL-DTL-87929B

15. Commercial Manuals (Evaluate according to MIL-PRF-32216) (If applicable ) MIL-PRF-32216

16. Aircraft Cross-servicing Guide MIL-DTL-22202 17.Support Equipment / Test, Measure, Diagnostic, Equipment SE/TMDE) MIL-STD-1839D 18.Concurrent Aircraft Servicing Checklists MIL-DTL-22202D

TABLE 2

ADDITIONAL TO REQUIREMENTS:

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

• TOs delivered using this table will be reviewed and approved by the TOMA prior to delivery.

• MIL-PRF-83495 requires MIL-HDBK-863 to be levied on engineering data for preparation of end item wiring data and schematic diagrams.

• For commercial manual supplemental data only, under the specification heading, enter “Same style and format,” “MIL-PRF-38807” (for IPB data), or “MIL-STD-38784. Approved commercial manuals shall meet the functional requirements of the approved TMSS for the TO type, e.g., OMMS prepared to S1000D shall meet the requirements of MIL-PRF-83495

• The contractor shall develop and deliver applicable source data for use by firefighter and rescue personnel in the event of an incident. The CRH program will use this and other contractor data to provide information on installed HAZMAT to the Air Force Civil Engineer Support Agency for inclusion in the Air Force TO 00-105E-9, Aerospace Emergency Rescue and Mishap Response Information.

• The contractor shall develop and deliver source data for all applicable TO 00-20 series manuals that are affected by maintenance documentation and record-keeping requirements for O-level Air Force maintainers.

• The contractor shall develop and deliver source data for AFM 23-110 to include all FAA parts documentation and record-keeping requirements for the Air Force Supply system. The contractor shall develop and deliver a tailorable Flight Crew Training Manual (FCTM) (including software for tailored version) for use by Aircrew Training System.

• If available, the contractor shall provide commercially available Flight Operations Engineering Performance Software that should be the typical tabulated performance data and fleet performance tracking to include tailoring for CRH configuration and performance and with a user’s manual based upon the Ops engineering performance software programs (tabulated data, course monitoring, etc.).

• If available, the contractor shall provide commercially available Flight Operations Engineering Training Course Manuals.

• If available, the contractor shall provide commercially available Maintenance Engineering Training Course Manuals.

• If available, the contractor shall provide Flight Safety Training Manuals and FAA mandated training manuals (e.g. wind shear, takeoff safety, etc). The contractor shall provide CRH source data to the Joint Services Aircraft Servicing Guide IAW AFI 91-202, Section 9.7 and TO 00-25-172.

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

TABLE 2

ADDITIONAL TO TYPE SELECTIONS

TO Number, Title, or

Type of Manual

Specification

Commercial Manual

Change/ Revision

Supple-ment

Supple-mental

TM

Source Data

1. 00-105E-9, Aerospace Emergency Rescue and Mishap Response Information (Emergency Services)

MIL-STD-

38784

2. CRH Aircraft Incident /Accident Investigation Manual

3. Short Term Aircraft Storage

TO

4. Applicable OO-20 Series TOs

5. AFM 23-110

6. Flight Crew Training Manual (tailorable) including software for tailored version

7. Performance Engineer’s Handbook

8. Flight Operations Engineering Performance Software

9. Flight Operations Engineering Training Course Manuals

10. Maintenance Engineering Training Course Manuals

11. Flight Safety Training Manuals

12. Human Factors in Maintenance Manuals

13. Joint Services Aircraft Servicing Guide IAW AFI 91- 202, Section 9.7 and TO 00- 25-172

14. Training Devices Instructional Manuals

15. Training Devices Maintenance Manuals

16. Training Devices TOs/COTS Documents

17. Training Devices Operation Instructions Manuals

18. Training Devices Software Users Manuals (SUM)

19. Training Devices Commercial Manuals List

20. Commercial Manuals List

TABLE 3

TO DELIVERY REQUIREMENTS FOR CRH PROGRAM

TO DATA TYPE DELIVERED

Delivery Format Requirements Codes:

Digital delivery only P - Paper (draft or manuscript only. Cannot be used for final delivery)

D - Digital

M - Mixed paper and digital

NOTES:

• Delivery format requirements codes indicate the media/file format to be delivered for each program event.

• TCTO requirements are specified in the contract vehicle approving the TCTO.

• When on-line access is a contractual requirement, copy quantity will normally be Ø (zero).

• For NGS or non-standard instances, delivery shall include the associated DTDs, FOSIs/Style Sheets, XML schemas, etc.

DELIVERY SCHEDULE

Event Number of days data required prior to event

Technical Review(s) (30 Days)

Verification( 30 Days)

Prepublication Review

(30 Days)

Final TO Distribution (30 Days)

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

AFMC/AFLCMC/WISL

1895 5th St. Bldg. 46 Wright-Patterson AFB. OH.

45433-7200 (Mx Manuals)

M/2 M/2 M/2 M/2

WR-ALC /GRUEF

235 Byron St., Suite 19A Warner Robins AFB GA (Mx Manuals)

M/6 M/6 M/6 M/6

ACC (Mx Manuals) 216 Sweeny Blvd, Suite 109Langley AFB VA 23665

M/2 M/2 M/2 M/2

WR-ALC/GRUBS

235 Byron St., Suite 19A Warner Robins AFB GA(Flight Manual)

M/2 M/2 M/2 M/1

ACC (Flight Manuals) 216 Sweeny Blvd, Suite 109 Langley AFB VA 23665

M/2 M/2 M/2 M/2

413 FLTS/CC

ATTN: Maj Kevin M Wiley or Mr. Byron Johnson 320 Tully St, Bldg 90343 Hurlburt Field, FL 32544

M/2 M/2 M/2 M/2

ACC 28 TES/D0G ATTN: Michael T. Thornton

CIV AF

203 W D Ave BLDG 351 Building 351 Eglin, Fl 32542

M/2 M/2 M/2 M/2

Total Copies Required: M18 M/18 M/18 M/17

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

Standardization Interface Record for ASD-S1000D, Issue 4.0.1, Business Rules - International Specification for Technical Publications Utilizing a Common Source Database

S1000D Business Rules Proposal Cross-Reference

S1000D Business Rule Category CRH TMCR Reference Comments General (S1000D Para. 2.1) TMCR Para. 4.3 TMCR Para. 4.4 TMCR Para. 4.6 TMCR Para. 7.1 TMCR Para. 12.

TMCR Table 1 TMCR Table 2 Product Definition (S1000D Para. 2.2) TMCR Para. 6.1

Maintenance Philosophy and Concepts of Operation(S1000D Para. 2.3) TMCR Para. 2.1 TMCR Para. 2.2 Appendix Draft TO CONOPS Security (S1000D Para. 2.4) TMCR Para. 8.1 Business Process (S1000D Para. 2.5) TMCR Para. 9.1.1 TMCR Para. 13.1 TMCR Para. 14.1 Data Creation (S1000D Para. 2.6) TMCR Para. 2.3 TMCR Para. 2.4 TMCR Para. 2.10 TMCR Para. 2.12 TMCR Para. 2.17 TMCR Para. 2.18 TMCR Para. 3.1 TMCR Para. 4.2 TMCR Para. 4.5 Data Exchange (S1000D Para. 2.7) Para 2.4.1

Data Integrity and Management (S1000D Para. 2.8) TMCR Para. 2.5 TMCR Para. 2.6 TMCR Para. 2.7 TMCR Para. 2.8 TMCR Para. 2.9 TMCR Para. 2.11

TMCR Para. 2.13 TMCR Para. 4.1 TMCR Para. 9.1 TMCR Para. 9.1.2.1 TMCR Para. 9.1.3.1 TMCR Para. 9.1.4.1 Para 12.1 Legacy Data (S1000D Para. 2.9)

Data Output (S1000D Para. 2.10) TMCR Para. 2.13 TMCR Para. 2.14 TMCR Para. 2.15 TMCR Para. 2.16 TMCR Para. 14.2 TMCR Table 3

Appendix A - CRH Functionality Matrix

Functionality C om pl ex ity

P ag e

C om pl ex ity

IE

T

P

R eq ui re m en t

A ll in fo rm at io n se ts

C re w op er at or

D es cr ip tio n an d op er at io n

M ai nt en an ce p ro ce du re s

Fa ul t i so la tio n

N on

-d es tr uc tiv e te st in g

C or ro sio n co nt ro l

St or ag e

W ir in g di ag ra m s

Il lu st ra te d pa rt s d at a

M ai nt en an ce p la nn in g

M as s a nd b al an ce ec ov er y

E qu ip m en t

W ea po n lo ad in g

C ar go lo ad in g

St or es lo ad in g

R ol e ch an ge

B D

A

Il lu st ‘d to ol su pp or t e qu ip

Se rv ic e bu lle tin s

M at er ia l d at a

C om m on in fo d at a

Access

Login 2 2 Viewer A

Suspend and restart 1 1 Viewer A

Exit 1 1 Viewer A

Annotation

Action complete indicator (checkbox) 1 1 X X X X X X X X X

Global data annotation 2 2 Viewer A

Local data annotation 2 2 A

Personal annotation 1 1 Viewer A

Redlining text 3 3 Viewer A

Redlining graphics 3 3 Viewer A

Delivery and distribution

Printed publication 1 5 X X

Physical media 1 1 A

Network distribution 2 2 A

Diagnostics and prognostics

Diagnostics - User determined entry to data

1 1 X X X

Diagnostics - Software driven entry to data

2 2 X X

Dynamic diagnostics 5 X X X

Wire/Fluid system tracing 4 4 X X X

System simulation 4 4 X X X X X X X X X X X

Prognostics 5

External processes

Transmittal 3 3 A

Retrieval 2 2 A

Parts ordering 3 3 X X X X

Deficiency / Improvement report transmittal

3 3 A

Maintenance data collection 3 3 X X X X X X X X X X

Operator debriefing 3 3 X X X

Resource scheduling 3 3 X X X

Knowledge management 5

Graphics

Pan, zoom, expand, magnify 1 1 Viewer A

Assembly/Disassembly 2 2 X X X X X X

Locator graphics 1 1 A

3D modeling 4 4

Linking

External references 2 2 A

Internal reference 1 1 A

Hot reference 2 2 A

Link to separate parts data 2 2 X X X X X X X X X X

TOC, lists of figures, tables and photos 1 1 A

Hot spotting 3 3 A

Navigation and tracking

Next and previous 1 1 Viewer A

Return (Chronological) 1 1 Viewer A

History of traversed links 1 1 Viewer A

User creation of bookmarks 1 1 Viewer A

System/Subsystem navigation 1 1 Viewer A

Restore initial navigation view 1 1 Viewer

Audit trail 2 2 Viewer X X X X X X X X X X X X

Graphical navigation 2 2 A X

Dialog-driven interaction 3 3 X X X

Voice-Activated commands 3 3

Search - Full text 1 1 Viewer A

Search - User defined boolean 1 1 Viewer A

Search - Across multiple databases/files 4 3 Viewer A

Search - Context 2 2 Viewer A

Search - Key word 2 2 Viewer A

Filter content per applicability 2 1 A

Simultaneous display of multiple objects

2 2 A

Tear off window 2 2 Viewer A

Printing

Print screen 1 1 Viewer A

Data module specific printing 1 2 Viewer A

Print linked data 2 2 A

Fully formatted/book version 4 5 X

Special content

Front matter 1 1 A

Supporting technical data 2 2 A

Warnings and cautions 1 1 A

Emergency procedures 2 2 X X X X X X X

Photos 1 1 A

Audio 2 2

Motion video 3 3

Animation 4 4 X X X X X X X X X X

Content sensitive help (Tech data) 1 1 A

Context sensitive help (Viewer) 2 2 Viewer A

User training 3 3 Viewer A

Updates

Passive change indications and markings

1 1 A

Active change indications and markings 2 2 A

Full change 1 1 A

Block cycle and urgent changes 2 2 A

Near real time updates 2 2 A

User operation mode

Web browser viewable 3 3 A

Stand alone mode 1 1 A

Network connectivity 2 2 A

DRAFT

i

Appendix B – CRH TO Concept of Operations

Combat Rescue Helicopter (CRH)

Technical Order (TO) Concept of Operations (CONOPS) ii

TABLE OF CONTENTS

1 Executive Summary 2 General CRH TO Program Information 3 TO Development 4 User Requirements

4.1 TO Sustainment

4.2 TO Distribution

4.3 IETM User Interface/Viewer

4.4 Other Requirements

4.5 Classification and Security

5 RESPONSIBILITIES

5.1 AFLCMC/WISLTOMA will:

5.2 ALC will:

5.3 MAJCOMs will:

5.4 AETC will:

5.5 TO Users will:

APPENDIX A – Draft Integrated Process Team (IPT)Charter . ........................ A-10 APPENDIX B - Acronym List ..............................................................................B-1

1 EXECUTIVE SUMMARY

This CONOPS describes the CRH Technical Order (TO) future, one that is leading edge and depends heavily on the use and integration of technologies. Successful integration of these technologies is critical to the success of the CRH fleet. This strategy is one in which digital TO information will be rapidly authored, sustained and distributed. This strategy demands absolute currency of the TOs in the users’ possession. It demands that TO changes and updates are rapidly identified, evaluated, approved and incorporated using web-based methodologies.

This approach will minimize supplements and different revisions in simultaneous use. The user will have extremely accurate information and links to supporting data (e.g., drawings, training courseware, etc.) at the point of use. The users at every level will have intuitive tools based upon Commercial-Off- The-Shelf (COTS) open systems technologies that will operate on existing AF systems.

In May 2011, HQ AF mandated that all AF TOs be acquired to the S1000D standard in Interactive Electronic Technical Manual (IETM) format, using DoD and AF Business Rules (BR). S1000D is capable of providing Type 1 (Linear/Electronic Technical Manual (ETM)) and Type 2 (Non- Linear/IETM) functionality from a Common Source Data Base (CSDB).

The CRH TO program will electronically distribute, use and sustain maintenance IETMs at the Organizational (O) and Depot (D) levels. AF flight manuals will be distributed in paper and digital formats.

Benefits of Type 2 IETMs are increased maintenance effectiveness and aircraft availability. Substantial life-cycle sustainment cost savings will be realized from the increased efficiencies of Type 2 IETM when compared to Type 1 ETM data.

1.1 GENERAL CRH TO PROGRAM INFORMATION

For the purposes of this CONOPS, the term IETM will specifically refer to CRH O & D-level data. The term flight manuals identify only the data necessary to operate the CRH. The term TOs refers to all technical data necessary to operate, sustain and maintain the CRH aircraft.

IETM will make full use of the S1000D Process Data Module (PDM) and AF BRs. TOs created using the S1000D Publications Module (PM) shall be referred to as ETMs.

CRH TOs will contain content targeted towards AF three, five and seven skill levels. The IETM will filter data presented based on maintainer skill level wherever possible. All TOs will be written to the 9th grade reading level as specified in MIL-STD-38734.

TOs that contain restricted information shall have appropriate access security controls and guidelines established.

All TOs will be distributed electronically via a single web-based interface. The web-based interface will use the Air Force Portal or Enhanced Technical Information Management Systems (ETIMS) to provide an interface for all CRH TO data.

Users will access TOs via an “Electronic-Tool” (E-Tool) compatible with the Air Force Standard Desktop configuration. E-tools can consist of a ruggedized laptop, tablet, desktop computer, or specialized tools. All E-tools will meet AF security requirements and be reliable, durable and easy to use and accommodate a wide range of environment operating conditions.

The TO shall support operations while connected (AF enterprise) and disconnected (stand-alone). Each operating location will automatically download the most current data version from the main portal at regular intervals. This will ensure up to date technical data is available at both CONUS and OCONUS locations. The typical disconnected mode scenario will be a remote deployed location with limited to no internet connectivity. The ability to update TOs via DVDs or other physical medium shall be available.

It is the responsibility of the contractor to ensure that CRH TOs are compatible with AF maintenance data collection systems and procedures without modification. The E-tool will serve as the focal point for maintenance data collection, supply data and parts ordering.

CRH TO system architecture will be interoperable with DoD Automated Information Systems (AIS) and be Defense Information Infrastructure - Common Operating Environment (DII-COE) compliant. This includes AF Global Combat Support System (GCSS).

CRH TOs will be authored to permit full re-use of technical data by functions such as training courseware and Advanced Distributed Learning (ADL)/Sharable Content Object Reference Model (SCORM) specifications.

Maintainers should be able to access SCORM-based training materials while using the CRH IETM within a maintenance procedure. Training materials should be integrated with the IETM wherever possible through integration of a Learning Management System and the IETM Common Source Data Base (CSDB). This capability can be a mix of training materials (i.e., Computer Based Training (CBT), Videos, 3-D solids, etc.).

Certified and verified TOs will be delivered concurrent with CRH Operational Test and Evaluation

(OT&E).

Change recommendation processes, such as the AFTO 22 process, will be accomplished electronically.

The costs and schedule required to develop and field technical data, including applicable E-tools and related distribution/management tools, shall be included in the overall TO program estimates.

2 TO DEVELOPMENT

All IETM data will be created in standard, neutral and non-proprietary eXtensible Mark-up language (XML). Computer Graphics Metafile (CGM) Level 4.0 (or later) with standardized hot-spotting methodologies or other industry standard formats shall be used to develop TO graphics. Associated S1000D Business Rules, documents, authoring guides, state tables, style sheets, processing instructions and other data or software used to create, display, transform or manage TOs shall be delivered digitally in native usable format along with PDF files. All developed TOs, training courseware, E-tools and related data shall be non-proprietary.

Responsibility for the technical content of CRH TOs and associated processes resides with AFLCMC/WISL who is responsible for complying with public law, AF, and DOD policies associated with creation of digital TO data and TO management. AFLCMC/WISL can modify, change and update existing processes to fit the digital environment and to meet customer requirements.

TOs shall be developed to conform to the maintenance level and task involved. TO content shall include, but is not limited to:

• System Description

• LRU/LRM theory of operation

• Interface descriptions

• Component removal/installation procedures

• Preventative maintenance procedures

• Emergency response procedures

• Aircraft operation procedures and checklists

• Repair/Replacement procedures

• Fault isolation procedures

• Fault reporting manuals

• Wiring diagrams

• Work unit code manuals

• Illustrated Parts Breakdown

IETM data shall be certified by the contractor and verified by AF personnel.

3 USER REQUIREMENTS

The following specific TO improvement requirements have been identified:

• Increase TO functionality to improve user productivity over paper based TOs

• Decrease TO sustainment costs

• Increase TO interoperability with AF systems

• Standardize operations across the Air Force

• Reduce TO Distribution Office (TODO) functions

• Improve aircraft configuration control

• Reduce TO supplements

• Minimize paper libraries and warehouses

• Minimize TO distribution times

• Minimize shipping of physical products (i.e., paper/CDs/DVDs, etc.)

• Manage TO effectivity based on aircraft tail numbers

Delivered TOs shall have interactive capability as detailed in the TMCR IETM Functionality Matrix.

References to existing AF commodity/commercial manuals or Methods and Procedures Technical Orders (MPTO) may not require full integration into the IETM beyond a simple link to the TO.

3.1 TO SUSTAINMENT

CRH TOs will be managed by the contractor until transfer to the appropriate sustaining ALC. All TO change requests will be submitted and processed electronically. After TO delivery, the TOMA will be responsible for approval, incorporation and configuration management of TOs. The TO configuration management plan, developed during production of TOs, will continue to be implemented during sustainment. Changes to TOs will be made available through network distribution using AF architectures and systems. Only TO difference data will be distributed when making updates to the TOs or the CSDB.

3.2 TO DISTRIBUTION

All TO data and changes will be distributed on-line using a web-based capability. After user validation and login, the aircraft tail number on which maintenance will be performed will be entered. This single point of access will provide all of the necessary data required to perform the required tasks, including real-time links, where possible, to AF maintenance data collection systems, AF standard supply systems, and other AF information systems. The CRH TOMA will ensure the organization/contractor responsible for TO sustainment acts as the single "hot line" point of contact for issues related to all aspects of the TO maintenance operations. The sustainment process will consist of a comparison of updated TO data against the source TO data currently on the E-tools. Outdated TO data will automatically be replaced with the most current version. For normal operations, this will be performed real time. This includes accessing, storing and updating data stored in other data formats.

This concept of automating TO data updates minimizes distributing physical TOs to the field. To ensure data currency and if TO tasks are printed, the TO system will allow the printing of the current date and disposition instructions on the tasks.

3.3 IETM USER INTERFACE/VIEWER

There are two key aspects to TO viewing. The first is the IETM viewer (E-tool) and the second is the “User Interface” that displays the technical data. An “E-Tool” is defined as any portable electronic device used to provide a user interface to the technical data. The user interface is the actual software and graphical display on the E-Tool.

The provided solution will, through AF architectures, update the data on each E-Tool and replace it with the current data. Data shall be automated and performed at regular intervals while the E-Tool is connected to the network. The CRH TO IPT will develop processes to manage E-Tool updating consistent with AF policy on TO use and interoperability.

All TO data will be transferred directly from the server to the E-Tool’s primary storage device (i.e. hard disk or other type of non-volatile memory). This will include transactional maintenance data to be cached and transmitted when connected to the AF network.

The E-Tool will provide the entire range of functions, including document navigation, viewing and submission of electronic change requests. Change requests will reside on the E-Tool and be submitted electronically to the technical content manager for action.

E-Tools will meet user requirements for ease of use, durability, security, reliability and functionality in all operational environments specified in the CRH System Specification. Hardware and operating systems may vary, however the user interface will be uniform to ensure ease of use, maintainer familiarity and standardization.

3.4 OTHER REQUIREMENTS

System architecture solutions shall be interoperable with other Air Force and DoD automated information systems and include provisions for periodic automated backups and redundancy of TO data.

There may be a number of physical or logical repositories for IETM technical data, but they will be accessible through a single web interface that is transparent to the user.

The system will allow for global and personal annotations and comments as defined in the S1000D specification. All AF TO review activities will have access to engineering and logistics source data through a secure web based portal.

4 CLASSIFICATION AND SECURITY

Electronic TOs will not contain classified data and separate paper based TOs will be provided to support classified data. TOs will reference documents containing classified data.

5 RESPONSIBILITIES

This section defines CRH TO lines of authority and responsibilities. Additional refinements may occur after the TO Integrated Process Team (IPT) has been established. To achieve this CONOPS, responsibilities will be established and communicated.

The following responsibilities represent an initial draft to outline authorities and responsibilities that will support this TO CONOPS. Some of the responsibilities are already identified in Air Force and DoD policy, but have such great impact on achieving the end-state, that they are being restated within this CONOPs.

5.1 AFLCMC/WISLTOMA WILL:

• Document and clarify TO requirements. This also includes developing the draft Technical Order Management Plan (TOMP), determine TO types and depth of coverage required, review/approve/disapprove Contractor Furnished (Aeronautical) Equipment (CFAE/CFE) Notices and ensuring TOs meet ACC plans/requirements.

• Manage coordination of operational equipment, facilities, support equipment, spares, consumables and qualified personnel required to perform verification of TOs in accordance with established schedules. Review and coordinate on test plans to ensure that sufficient time and resources are allocated for TO verification.

• Initiate and coordinate pre-acquisition planning for acquisition and/or maintenance of TOs.

Ensure that all affected commands and agencies identify and document TO-related requirements.

• Perform all acquisition TO management functions as directed in TO 00-5-3, TO 00-5-1, AF TMSS, DoD 5000.2-R, AFPD 21-3 and all pertinent directives.

• Manage TO financial policy and budget funding for all acquisition, conversion and modification programs.

• Establish processes to review and formalize TOs, review and approve TOs and Preliminary Technical Order (PTO) change requests. Establish controls to ensure that verified TOs are distributed prior to or concurrently with deployment of operational assets. Work with contractor on establishment of TO distribution, security and architecture plans.

• Prepare TO inputs to all applicable contractual documents and other program documentation.

• Participate in contract fact finding and negotiations as required. The TO Manager is responsible for evaluating contractor proposals to ensure that exit criteria for TO verification are adequately defined in the Integrated Master Plane (IMP), that adequate resources and Government Furnished Equipment (GFE) are planned for incremental verification and costs are reasonable and supported by the proposal.

• Coordinate contractor recommended changes to AF BRs with HQ AF via AFMC/A4, for possible incorporation into the TMCR.

• Ensure all waivers and deviations to TO MIL-PRFs and MIL-STDs are controlled, documented and forwarded to the preparing activity (PA) for approval or disapproval.

• Plan, conduct and co-chair with the contractor all TO conferences, meetings, reviews and other joint agency efforts related to the TO acquisition program.

• Coordinate with the using command and support agencies to ensure their participation in all TO acquisition activities. Request contracting officer representation in meetings with the contractor as required.

• Ensure TO development processes have adequate checks and balances and procedures to cover standardization of writing. Ensure prime contractors levy QA requirements on vendors and subcontractors.

• Provide the Responsible Test Organization with TOs to use during Operational Test and Evaluation (OT&E). Support Air Education and Training Command (AETC) with PTOs and ADL/SCORM related S1000D data modules.

• Coordinate with other SPO functions, ALCs and the using command(s) to ensure that TOs are compatible with equipment used in the maintenance and operation of systems and commodities.

• Ensure that TO technical content, method of presentation, style and level of writing are in line with the established maintenance concept, skills and training of personnel who will operate and maintain the equipment. That is, they comply with the Training System Specification (TSS) and System Specification and applicable TO standards.

• Manage an Air Force verification program with the contractor. Develop a TO Verification Plan (TOVP) not less than 120 days prior to the scheduled start of verification. Involve all appropriate Government and contractor agencies.

• Review and in coordination with the using command and support agencies, recommend contractual approval or disapproval of CFAE/CFE Notices (DI-TMSS-80067) recommending program manuals.

• Ensure existing source data is used to the maximum extent possible and is not duplicated for TO development. Review source data to detect errors, deficiencies and nonessential material.

5.2 ALC WILL:

• Work with AFLCMC/WISL TOMA to ensure the TOs meet customer technical data requirements.

• Work with AFLCMC/WISL TOMA to acquire, convert and sustain digital technical data in the most efficient, timely and cost effective manner.

• Work with AFLCMC/WISL TOMA to develop standardized TO sustainment processes.

• Budget for technical data sustainment that will support the end-state of this CONOPS in coordination with MAJCOM.

• Work with AFLCMC/WISL TOMA to transition TOs, e-tools and necessary support systems to allow organic ALC sustainment.

• Work with AFLCMC/WISL TOMA to establish a single office/help desk for CRH TOs.

5.3 MAJCOMS WILL:

• Participate in all Technical Interchange Meetings (TIM)s.

• Advocate technical data sustainment and TO infrastructure requirements.

• Ensure appropriate TO sustainment funding levels throughout the Program Objective

Memorandum (POM) and budget exercises to support this CONOPS. Funding will include technical refresh cycle for e-tool and other hardware/software.

• Establish and chair MAJCOM level TO working group to recommend TO policy improvements if needed.

• Institutionalize TO policy for the MAJCOM.

• Fund required training of personnel to meet this CONOPS.

• Provide representatives to the Air Force TO related IPT meetings and working groups.

5.4 AETC WILL:

• Work with AFLCMC/WISL to develop a consolidated TO data creation strategy to ensure that training data can be effectively reused by ADL/SCORM based training.

• Sustain computer-based training for digital TOs.

• Incorporate digital TO training in initial skills course curriculum.

5.5 TO USERS WILL:

• Participate in all Technical Interchange Meetings (TIM)s.

• Unless otherwise dictated, only print individual tasks to meet mission requirements.

• Ensure printed tasks contain appropriate disposition instructions.

• Destroy printed copies after completing task or use equivalent procedures to ensure configuration control is maintained.

• Use only approved E-Tools.

APPENDIX A

CRH TO Integrated Process Team (IPT)

Draft Charter

1 PURPOSE.

The CRH TO IPT will focus on implementation of the S1000D specification within the CRH TO technical data program. A team effort is desirable to achieve a usable and cost effective TOs and ADL/SCORM courseware data.

Specific areas of focus are:

• Ensure a common understanding of AF S1000D Business Rules (BR).

• TO creation processes and procedures.

• TO management processes and procedures.

• TO viewing processes and procedures.

• TO distribution processes and procedures.

• Integrating TO data with ADL/SCORM and CBM+ requirements.

• Clarification of CRH functionality matrix requirements.

2 BACKGROUND.

AFLCMC/WISL is responsible for the development, sustainment and fielding of the technical data associated with the CRH weapon system acquisition. An IETM has been selected to support the CRH weapon system O-level and D-level TO requirements. Many aspects of the CRH program are unique and take advantage of new techniques for weapon system data re-use, structures, storage and interoperability.

3 OBJECTIVES.

Determine vendor understanding of digital TO requirements found in TMCR, CRH functionality matrix and S1000D BRs.