TM-86-01N - 27 Jan 2012.pdf

FA8102-12-R-0001

1 DEC 2011

TM-86-01N December 2011

Air Force Technical Manual Contract Requirements (TMCR) For The

NAVAIDS Family of Systems Modernization Program

FOR CDRL SEQUENCE NUMBER A023, EXHIBIT Y

SECTION 1. TECHNICAL MANUAL (TM)/TECHNICAL ORDER (TO) PROGRAM

REQUIREMENTS

1. TMCR Tailoring.

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 paragraph in Section 1 and the associated tables in Section 2 of this TMCR. The Contractor shall also adhere to the Specification/Standard Interface Record (SIR) for the TO types, source data, TO updates, commercial manuals, and any TOs prepared to Non Govern-ment Standards (NGS) in Section 3 of this TMCR. The Contractor shall not delete any Govern-ment identified requirements, but may identify additional TOs required to support the NAVAIDS Family of Systems Modernization Program.

1.2. The completed contractual TMCR shall be: (1) Attached to CDRL A023 for TO delivery, (2) Included in the proposal as Exhibit Y and (3) Referenced in the proposal SOW. Air Force TO Ac-quisition procedures and terms for this document are found in TO 00-5-3, AF Technical Order Life Cycle Management.

2. TO Program Scope. The NAVAIDS Family of Systems Modernization Program requires safe, current, accurate, adequate, and technically usable TOs that support all facets of operation and maintenance to include all Operation, Maintenance, Installation and Training (OMIT) Technical manual requirements for both Field level (F-level) and Depot level (D-level) of maintenance. It is the government’s intent to support this program with an organic two-level maintenance concept utilizing F-level “blue-suit” AF maintainers and D-level “organic” for long-term sustainment from the on-set of this program. In accordance with T.O.00-5-3; “All new major acquisition programs must acquire TOs in a Type 2 Interactive Electronic Technical Manual (IETM) database format . . .

IAW AIA-S1000D and the Air Force HTML Business Rules (BR) to be published in a TMSS spe-cification.” These commercially available IETMs will be used as the baseline maintenance IETM in the development of the NAVAIDS FAMILY OF SYSTEMS Modernization IETM. NOTE: For purposes of this document, F-level Maintenance includes both the Field level infrastructure and back shops.

2.1. The Contractor shall provide all existing commercially available ITEMs for the baseline NAVAIDS Family of Systems in support of a Government sufficiency review IAW MIL-PRF- 32216 (Evaluation of Commercial Off-The-Shelf (COTS) Manuals and Preparation of Supplemen-tal Data) of all F-level and D-level maintenance manuals. As part of this review, the government will identify at the Guidance conference, a sampling of tasks to be performance verified by gov-ernment personnel. The Contractor shall support the government verification of these selected tasks and the integration of changes resulting from this review, thereby establishing the baseline maintenance IETM for the NAVAIDS Family of Systems Program. The Contractor shall also pro-vide technical support (engineering and TO writers) as needed for these government verifications.

2.2. The Contractor shall develop, certify and deliver all identified technical manuals in Tables 1 and 2 of Section 2 of this TMCR. Those F-level maintenance manuals and checklists identified in Table 1 shall be developed to meet the intent of the referenced MIL-STD/PRF and be incorporated into the baseline maintenance IETM, providing a seamless all-encompassing F-level maintenance

IETM.

2.3. The Contractor shall investigate and incorporate typical Field Level tasks that can be effec-tively accomplished under the F-level maintenance concept into these existing commercial base-line maintenance IETMs, providing a seamless all-encompassing F-level maintenance IETM.

2.4. The Contractor shall identify, certify and incorporate F-level user procedures for all Test, Measure, Diagnostic, Evaluation/Support Equipment (TMDE/SE), Special Tools, and portable maintenance aids or other enabling tools that simplify and improve the effectiveness of mainten-ance into the baseline maintenance IETM, providing a seamless all-encompassing F-level main-tenance IETM.

2.5. The Contractor shall develop and implement incorporation procedures for Government origi-nated changes, as the result of both government performance verification and Initial Operational Testing and Evaluation (IOT&E), to all Technical Manuals until the manuals are formally deli-vered to the Government.

2.6. For Technical Orders in development, the Contractor shall develop and implement change process that allows the incorporation of Government-originated (AFTO Form 22s or AFTO Form 847s) changes to performance and maintenance Technical Orders.

2.7. The Contractor shall ensure all Technical Manuals and SE/TMDE manuals are concurrent with the NAVAIDS Family of Systems system configuration, prior to formal delivery.

2.8. The Contractor shall implement procedures to notify the government of any Federal Aviation Administration (FAA), Original Equipment Manufacturer (OEM) and/or Vendor directed Service Bulletins (SBs) for approval prior to incorporation into delivered TOs.

2.9. The Contractor shall deliver Depot-level Technical Manuals (ASD/ASI S1000D, XML-tagged formatted IETM) including Suppliers/Vendors manuals for the NAVAIDS Family of Systems and all subsystem components in support of the Government’s organic Depot level and NAVAIDS Family of Systems Maintenance Review Board’s approved maintenance.

2.10. The Contractor shall develop and deliver Operations, Maintenance, and Installation technical manuals IAW Table 1 and applicable SOW paragraphs to fully support field/organizational and depot levels of maintenance.

2.11. The Contractor shall develop and submit Technical Order update change packages for any government accepted TOs affected by Contractor initiated ECPs for deficiencies during the Sus-tainment Support period.

3. Subsequent TO/Data Requirements. The Contractor shall develop and implement a process for no-tifying the government when additional TOs or source data requirements are identified. This process shall require government review and approval of recommended additional requirements prior to contractual approval.

4. TO Development. The Contractor shall describe how the government will interact with the Con-tractor’s TO development team. The Contractor shall develop and implement all comprehensive TO development practices and procedures that ensure all TOs and data are compatible with the TO System of Record, the Air Force Technical Order Concept of Operations (CONOPS) and the Air Force Stan-dard TO Management System. 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, Standard Practice for Manuals, Technical: General Style and Format Requirements. The Contractor shall utilize English/Standard measurement values (i.e.

Feet, inch pounds, Gallons, Knots per Hour) in the development of all manuals.

4.1. The Contractor shall develop and deliver all IETMs in accordance with ASD/AIA S1000D, is-sue 4, International Specification for Technical Publications Utilizing a Common Source Database and the Government’s S1000D/HTML Business Rules in Section 3.

4.2. The Contractor shall format with text, graphics and delivery according to the TMSS specified in Section 2 for all TOs. The Contractor shall develop TO files (tagged instances) using Hyper Text Mark-up Language (HTML) according to the Document Type Definitions (DTDs) referenced in the appendix to MIL-STD-38784 and each applicable military detail or performance specification (MIL-DTL or MIL-PRF).

4.3. The Contractor shall include required illustration (graphics) source files in an approved graph-ics exchange format (select “Guidelines” and “Graphics” on the Technical Manual Specifications and Standards (TMSS) web page (https://techdata.wpafb.af.mil/tmss/index.html) for all HTML-tagged TO files. NOTE: Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible.

4.4. The Contractor shall contact the TO Manager and the 754 ELSG/ILMT for pre-approval be-fore modifying or developing any new DTDs to support use of NGS, canceled TMSS, or undeve-loped TMSS DTDs. If permission is granted, the Contractor must submit any proposed DTDs through the PCO and TO Manager to 754 ELSG/ILMT for validation of TMSS compatibility with approved electronic TO (eTO) viewing solutions. New DTDs shall not be developed in lieu of ex-isting DTDs, including those for legacy TMSS. TMSS Rules shall be so constructed that TO out-put complies with the functional requirements of the associated TMSS, and shall be documented in a SIR. DTDs and rule sets submitted and approved in execution of the contract shall become the property of the Government. The Contractor shall direct questions about the application of HTML tagging to digital TO files to 754 ELSG/ILMT (HTMLSupport@wpafb.af.mil).

5. Technical Manual Specifications and Standards (TMSS). The Contractor shall address all ques-tions concerning TMSS requirements by written request and justified suggestions for resolution submitted through the PCO and the TO Manager, Carolyn Pullen, OC-ALC/GKAAB, 3580 D.

Avenue, Bldg 201-W, Tinker AFB, OK 73145, Phone: (405) 739-7717. Contractor originated de-ficiencies and suggested improvements shall be submitted to the TMSS Preparing Activity (PA) for approval.

6. TO Numbering. 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, AF Technical Order Numbering System.

7. Data Rights. The Contractor shall provide appropriate data rights for all baseline NAVAIDS Fami-ly of Systems commercial manuals; all source data and/or TOs prepared specifically for this con-tract; and any TOs that are copyrighted or contains proprietary data or procedures IAW CDRL A023; and the Statement of Work. The Contractor shall provide a signed document that allows the duplication and distribution of all Commercial Manuals. Distribution statement ‘C’ will be used whenever possible. Proprietary pages within commercial manuals, and/or Tech Orders must be in-dividually marked.

8. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. The Contractor shall determine the correct markings and controls for classified and restricted distribution data and TOs IAW the program’s Security Classification Guide (SCG) and DOD 5200.1-R, DODD 5230.24, AFIs 63-101, 31-401 and 61-204, and MIL-STD-38784. The markings and notices shall be reviewed during In-Process Reviews (IPR). NOTE: Distribution limitations will be deter-mined on a case-by-case basis as TOs are developed and dependent upon TO content.

9. TO Quality. 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 present an unaccepta-ble hazard to personnel or equipment. The contractor’s QA methods shall ensure engineering re-views are completed prior to government verification/re-verification.

9.1. Conferences and Technical Reviews. 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 as specified in SOW. The Contractor shall conduct periodic In-Process Reviews (IPRs) at the 75%, 90%, and 100% completion levels as referenced in TO 00-5-3 in preparation for Government verification; and a Prepublication Review (PPR) to en-sure TOs are being developed according to contract requirements and that open discrepancies are cleared prior to publication. For electronic TO (eTO) based programs, IPRs subsequent to the ini-tial review need to be accomplished using the approved eTO viewing solutions.

9.2. TO Certification. The Contractor shall develop and implement their method for documenting certification that TO procedures are safe, current, accurate, adequate, concurrent with NAVAIDS Family of Systems system configuration, and technically usable for their intended purposes. Certi-fication must be completed prior to the Government performing its verification of all TOs.

9.3. TO Verification Support. 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 Engineer(s) knowledgeable of the baseline NAVAIDS Family of Systems and subsystems.

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

9.4. Technical Order Review Boards and Flight Technical Order Review Boards. The Contractor shall also participate in all Technical Order Review Boards (TORBs) and Flight TORBs.

9.5. Technical Data Assessment (TDA). The Contractor and the program office with the assistance of OC-ALC/GKAAB will determine the TDA requirements for each TO type. The Contractor shall submit an in-work sample of each type of SGML-tagged TO file to the program office con-current with the 35% IPR, for TDA to verify compliance of the digital files to Air Force Digital Support Suites (DSS). Repeat TDAs shall be required whenever new TMSS or DTD versions are used for TO development. TDA parsing in no way relieves the Contractor from correcting tagging errors identified during the composing effort.

10. TO and Source Data Maintenance. 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 incor-porate corrections, equipment configuration changes, and maintenance and operational concept changes.

11. TO Delivery. 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 formats shall be according to Sec-tion 2, Part B, Table 2 (TM Delivery Requirements) of this TMCR. Paper TO delivery is not ac-ceptable for final delivery of TOs. EXCEPTION: For Commercial Manuals not available digital-ly.

11.1. SGML-Tagged Files. The Contractor shall parse and compose SGML-tagged TO document files prior to delivery to the government, and verify that content tagging has been accomplished to the levels provided in the DTD.

11.2. SGML-Tagged Files for Use with the eTO Viewer. The Contractor shall use the Govern-ment Furnished Equipment (GFE) ETIMS eTO Viewer/Transformer and Digital Formatted Output Specification Instance (DFOSI) to convert tagged instances to Hypertext Markup Language (HTML) files compatible with the eTO viewer, and certify the output complies with TMSS re-quirements.

11.3. Interactive Electronic Technical Manuals (IETM). The Contractor shall deliver the IETM data base according to the business rules for S1000D/HTML in Section 3 of this TMCR.

12. Schedules. The Contractor shall include all TO program events and schedules in their 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 develop-ment and delivery schedules throughout the acquisition phase of a program.

13. Engineering Change Proposals/Contract Change Proposals/Time Compliance Technical Orders (ECPs/CCPs/TCTOs). The Contractor shall develop and implement practices and procedures for related TO updates when tasked as part of the approval process for Engineering Change Propos-als/Contract Change Proposals/Time Compliance Technical Orders (ECPs/CCPs/TCTOs) to confi-gured ITEM. Costs for TCTO package development must be included in ECP Costs – not in-cluded 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 me-thod 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. TO Reproduction Management. The Contractor shall develop and implement a Reproduction Management process for digital media consisting of reproduction of the digital file on magnet-ic/optical media and distribution according to ID labels. Reproduction Management may also in-clude configuration control and storage of reproduction masters.

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

The TM Type Selection Tables indicating the applicable TO types and related specifications have been marked within minimum requirements. For additional interface requirements see the program-specific Government Concept of Operations (GCO).

All page-based TOs developed under this contract must conform to the general style and format requirements of MIL- STD-38784; IETMs must conform to S1000D, Issue 4, and its business rules.

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

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

Illustrated Parts Breakdowns (IPBs) are developed IAW MIL-PRF-38807, except that MIL-DTL-87929 will also be used for IPBs combined with work packages.

All checklists, except aircrew, are developed IAW MIL-PRF-5096.

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

Delivery requirements are indicated in the TM Delivery Requirements matrices.

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

Part A – TM/TO Type Selection Tables.

Table 1

TMSS Requirements for the NAVAIDS FAMILY OF SYSTEMS Modernization Program

Title or Type of Manuals Specification Required

1. Inspection TOs MIL-PRF-5096

a. Inspection and Maintenance Requirements (-6) Manual

b. Workcards – Inspection… (Scheduled Periodic Inspection -6WC-1)

c. Checklists

(1) Maintenance/Operation (Non-Flight crew)

2. List of Applicable Publications MIL-PRF-8031

3. Work Unit Code Manual ………….(Change package to existing Legacy TO) MIL-PRF-38769

4. Calibration Procedures MIL-PRF-38793

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

6. Illustrated Parts Breakdown………..(Down to *FL replacement components) MIL-PRF-38807

7. On-Equipment Organizational Maintenance Manual Set (see notes) MIL-PRF-83495

a. General Equipment (GE) Manual………….(Equipment / LRU Level)

b. General System (GS) Manuals ……………………….(System Level)

c. Job Guide (JG) Manuals..(*FL step-by-step Maintenance Instruction)

d. Fault Reporting (FR) Manual…………….(Combine with FI Manual)

e. Fault Isolation (FI) Manual …..(*FL - Malfunction / Troubleshooting)

f. Wiring Data (WD) Manual…..…(Combine with Schematic Diagrams)

g. Schematic Diagram (SD) Manual…..…. (Combine with Wiring Data)

*FL – Field Level

Table 1

TMSS Requirements for the NAVAIDS FAMILY OF SYSTEMS Modernization Program

Title or Type of Manuals Specification Required

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

a. Maintenance Manuals

(1) Depot Maintenance

(a) With Illustrated Parts Breakdown (down to component / hardware level)

b. Checklists (IAW MIL-PRF-5096)

(1) Maintenance/Operation (Non-Flight crew)

9. Commercial Manuals (Evaluate according to MIL-PRF-32216)

10. Interactive Electronic Technical Manuals (IETM - Contact 754 ELSG/ILMT for guidance.)

ASD-S1000D -

International Specification for Technical Publications Utilizing a Common Source Data Base

TABLE 2

ADDITIONAL TM TYPE SELECTIONS

NOTES:

None of the applicable boxes below are checked.

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

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

For manuals proposed to NGS, list the type of manual in the appropriate column and the NGS in the Specification column. Manuals proposed to an approved NGS shall meet the functional requirements of the approved TMSS for the TO type, e.g., OMMS prepared to S1000D shall meet the requirements of MIL-PRF-83495 (which serves as business rules for manual style, format, and content).

TO Number, Title, or

Type of Manual

Specification

Com-mercial Manual

Change/ Revision

Supple-ment

Supple-mental

TM

Source Data

1. 31R-1-06-1 Work Unit Code Manual

Same style and format – Framemaker software

2.

3.

4.

5.

6.

7.

8.

9.

10.

PART B

TM/TO DELIVERY REQUIREMENTS

FOR NAVAIDS FAMILY OF SYSTEMS MODERNIZATION PROGRAM

TM/TO DATA TYPE DELIVERED

Delivery Format Requirements Codes

Digital delivery only:

P - Paper (draft or manuscript only. Cannot be used for G – Standard Generalized Mark-up Language (SGML) final delivery) H - Hyper Text Mark-up Language (HTML) M - Mixed paper and digital (G, H or I)

EXAMPLE: M(G) / 2 [Paper and SGML / 2 copies]

NOTES:

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

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

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

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

DELIVERY SCHEDULE

Event Number of days data required prior to event Technical Review(s) (15 Days)

Verification (30 Days)

Prepublication Review

(30 Days)

Final TO Distribution (45 Days)

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

OC-ALC/GKAAA

M(G) / 2 M(G) / 2 M(G) / 2 M(G) / 2

OC-ALC/GKAAB

OC-ALC/GKAKB

Total Copies Required: 6 6 6 6

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

Standardization Interface Record for ASD-S1000D, Issue 4, Business Rules - International Speci-fication for Technical Publications Utilizing a Common Source Database

3. Refer to the RFP Technical Reference Library for the following documents:

3.1 S1000D Finalized Business Rules.pdf

3.2 S1000D Tag Description Tables (TDT).pdf

MIL-DTL-S1000D-BR.pdf (Detail Specification Air Force Business Rules for S1000D Issue 4.0 - International Specification for Technical Publications Utilizing A Common Source Data Base)