Attachment 0024-TPG 2016-01 Rev 1 Source Data.pdf

DEPARTMENT OF THE ARMY

US ARMY TANK-AUTOMOTIVE AND ARMAMENTS COMMAND

6501 EAST 11 MILE ROAD

WARREN, MICHIGAN 48397-5000

AMSTA-LCL-IMP 11 July 2019

MEMORANDUM FOR: U.S. Army Tank-automotive and Armaments Command, Integrated Logistics Support Center (ILSC), Publications Community

SUBJECT: TACOM Equipment Publications Control Office (EPCO) definition of source data in publications contracts.

1. References (all latest versions):

a. AR 25-30 (Army Publishing Program)

b. AR 700-18 (Provisioning of U.S. Army Equipment)

c. AR 750-1 (Army Materiel Maintenance Policy)

d. MIL-STD-40051-1/2 (Preparation of Digital Technical Information for Interactive

Electronic Technical Manuals (IETMs)/Page-Based Technical Manuals (TMs))

e. MIL-HDBK-1222 (Guide to the General Style and Format of U.S. Army Work

Package Technical Manuals)

f. Product Support Manager's Guidebook to Technical Manual Contract

Development and Quality Review, Best Practices

2. Purpose:

The intent of this TACOM Publications Guidance (TPG) is to define “source data” or “source files,” which are part of the deliverables on a publications contract, used to develop future changes or revisions to the Electronic Technical Manual (ETM) or Interactive Electronic Technical Manual (IETM).

3. Definitions:

a. AR-25-30 and MIL-STD-40051-1/2 require data prepared and delivered digitally to be Extensible Markup Language (XML) tagged for new and revised technical manuals. In addition, Product Support Managers (PSMs) are required to request XML source files as part of the contract for Department of the Army (DA)-authenticated TMs. This requirement applies to DA-authenticated equipment publications for which XML constructs are supported by the U.S. AMC Logistics Data Analysis Center

(LDAC).

b. Source data, or source files, on a publications contract refer to all files used to produce the Preliminary Technical Manual (PTM) used at a Verification, as well as the Final Reproducible Copy (FRC) of an equipment publication. This includes content (text) files, XML files, graphic files, Logistics Support Analysis (LSA) data such as LSA-036 reports used to create Repair Parts and Special Tools Lists (RPSTLs) or LSA-004 report files used to develop Maintenance Allocation Charts (MACs), etc., in their original format.

TPG 2016-01, Rev 1

AMSTA-LCL-IMP

SUBJECT: TACOM Equipment Publications Control Office (EPCO) definition of source data in publications contracts.

c. DA-authenticated Commercial-Off-The-Shelf (COTS) manuals: For existing manuals not developed in XML, there is no requirement to request XML source files in the contract. Standard language in the contract will read, "If the manufacturer manual was developed in XML format, the Contractor shall provide XML source files to the government." (NOTE: XML files created strictly for commercial manuals may not comply with any of the DTDs provided by LDAC. However, it is advantageous to the Government to have those XML source files for any future work.)

d. Graphic source files include all graphics used in publication development, in both the format in which they were developed (.ai, .cgm, .psd, etc.) and the format used in the FRC (.tif, .png, .eps, .cgm, .svg, etc.). Graphics should always be developed in a vector format, with layers as necessary for line art components, leader lines, callouts, etc. When developed graphics are ready to be included into the PTM or FRC, they should be converted to a flat (single layer) format appropriate to the output media:

(1) For IETMs, ideal formats are .cgm or .svg, which are “smart” vector formats that enable hot spots.

(2) For ETMs, ideal formats are .tif, .png, or .jpg (raster formats) with resolution of 300 dpi, for the best combination of graphic resolution and file size.

e. Interactive Authoring and Display System (IADS): When using IADS to product an IETM, source files include those in 3.b through 3.d above, plus the following control files:

(1) Data Set (Dataset.xml) – contains weapon system and TM identification information as well as configurations, if applicable.

(2) TOC (TOC.xml) – generates the Table of Contents and references all component XML files contained in the TM data set.

f. Electronic Maintenance System (EMS): When using EMS to produce an ETM or IETM, source files include those in 3.b through 3.d above, plus the following control files:

(1) Configuration file (Config.xml) – contains weapon system and TM identification information.

(2) Interactive Electronic Technical Manual Layout File (IETM_layout.xml) – applicable to Linear (frame-based) interactive manuals

AMSTA-LCL-IMP

SUBJECT: TACOM Equipment Publications Control Office (EPCO) definition of source data in publications contracts.

(3) Paper Manual Layout file (Paper_layout.xml) – applicable to page-based manuals

(4) FGC List (FGC_List.xml) – if TM includes a RPSTL and group numbers/titles differ from those defined in TB 750-93-1

(5) Applicability file (applicability.xml) – may be applicable to IETMs of weapon systems with multiple models

(6) Publication Matrix file (Publish Matrix.xsl) – spreadsheet that shows what work package files to include in published document (ETM or IETM).

Sometimes called Master Task List (MTL).

g. Third-party software: IETMs sometimes include links to launch third-party programming or software.

(1) Such third-party elements are also part of the source data.

(2) The proponent is responsible for ensuring third-party elements have a current Certificate of Networthiness (CoN). (Note: CoNs for EMS products are maintained by the EMS Mission at TACOM. The CoN for IADS is maintained by the AMCOM Logistics Center (ALC).)

h. Logistics Product Data (LPD): If LPD is produced by the contractor for publication development, such data is part of the source data. LPD may include:

(1) Failure Modes Effects & Criticality Analysis (FMECA)

(2) Fault Tree Analysis (FTA)

(3) Level of Repair Analysis (LORA)

(4) Maintenance Task Analysis (MTA)

(5) Supply Chain Management (SCM)

(6) Supportability Analysis

4. Conclusion:

Source data are necessary to ensure that if the Government chooses, it is able to duplicate or update any part, or all, of the FRC from the complete set of source files.

Therefore, all files and data used to develop and produce an FRC are required when source data or source files are named as deliverables on a publications contract.

The point of contact for TACOM Technical and Equipment Publications is Steve Pheiffer, AMSTA-LCL-IMP, DSN 786-1839, e-mail: steven.e.pheiffer.civ@mail.mil.

Stephanie Drobot Equipment Publications Control Officer (EPCO)

TACOM Publications (Warren)