CDRL A002

S1000D Army Sample Data

User’s Guide

TECHNICAL PUBLICATION, IETM, AND

STANDARDS/SPECIFICATION PROGRAM
SUPPORT

to
Redstone Arsenal
AL 35898-7466

15 September 2011

W31P4Q-08-A-
Contract Number: 0025
Task Order Number: 0001
Table of contents Page
References ..................................................................................................................................... 2
1 General information........................................................................................................ 3
1.1 Gun data set contents ..................................................................................................... 3
1.1.1 XML Files ......................................................................................................................... 3
1.1.1.1 Data modules .................................................................................................................. 3
1.1.1.2 Data module lists ............................................................................................................ 3
1.1.1.3 Publication modules........................................................................................................ 4
1.1.2 Other files........................................................................................................................ 4
1.2 Reporting errors and recommending improvements. .................................................... 4
2 Acquire the Gun data set ................................................................................................ 4
2.1 Viewing the XML ............................................................................................................. 4
2.2 Locating the source data module from a PDF location ................................................... 5
3 Checking the XML against the BREX file.......................................................................... 6
4 Publishing the XML.......................................................................................................... 7
4.1 Generating a complete publication: ............................................................................... 7
4.2 Generating formatted output one DM at a time ............................................................ 9
5 Common Source Data Base (CSDB) Software and Tools ............................................... 10
5.1 Working with data in EMS‐NG ...................................................................................... 10
5.1.1 Workflow....................................................................................................................... 11
6 File list ........................................................................................................................... 13

List of tables Page

Table 1 References .................................................................................................................. 2
Table 2 Operation ‐ Preliminary requirements ....................................................................... 4
Table 3 Checking XML ‐ Preliminary requirements ................................................................. 6
Table 4 Publishing XML ‐ Preliminary requirements ............................................................... 7
Table 5 Workflow definition .................................................................................................. 12
Table 6 File list ....................................................................................................................... 13

References
Table 1 References
Document No. Title

MIL‐STD‐3031A Army Business Rules For S1000D: International Specification For

Technical Publications Utilizing A Common Source Data Base
S1000D Issue 4.0 International specification for technical publications Utilizing a
common source database

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 2
1 General information
This document describes the US Army Phun Gun (hereafter referred to as the "Gun") S1000D Sample
Data. The Gun data set was developed as a supplement to the S1000D Bike Sample Data to provide
users with additional US Army‐specific content examples.
This document provides instructions to:
a. Acquire and review the Gun data set (refer to 2).
b. Check the eXtensible Markup Language (XML) against the BREX files (refer to 3).
c. Publish a complete publication or individual Data Modules (refer to 4).
This document will also provide considerations for choosing a CSDB tool (refer to 5).
Note: All XML points to S1000D Issue 4.0 schemas in order to accommodate the
capabilities for the Common Source DataBase (CSDB) tool discussed below (refer to
5.1). Errors corrected in S1000D Issue 4.0.1 do not affect the sample data.

1.1 Gun data set contents

1.1.1 XML Files

The Gun data set includes three types of XML files.

a. Data Modules (DM)s have file names that begin with "DMC‐."
b. The Data Module Requirements List (DMRL) has a file name beginning with "DML‐."
c. Publication Modules (PM)s have file names that begin with "PMC‐."

1.1.1.1 Data modules

Each DM contains two distinct sections: 1) the identification and status section and 2) the content
section. Depending on the type of DM, the content section’s structure will vary greatly, but the
identification and status section structure is always identical.
One of these DM types is the Business Rules Exchange (BREX) file. This DM is not included as a part of
the publication content that is typically distributed to end users (but is included in the DMRL (refer to
1.1.1.2)). The BREX file is an XML file that contains all project Business Rules (BRs) which are
considered “computer‐verifiable” and identify all project‐defined values, if any, which are also
necessary for publishing. Individual DM compliance with these BRs can be checked using the BREX file
(e.g., the use of required or prohibited elements). Narrative BRs are not computer‐verifiable (e.g., page
size). The BREX file is included in the folder named “Supporting Information.”

1.1.1.2 Data module lists

A Data Module Requirements List (DMRL) and a Common Source Data Base (CSDB) Status List (CSL) are
examples of a DML. The Gun data set contains a DMRL, which is an XML file. This DMRL lists every DM
that is a part of the Gun data set. The Gun data set also includes a CSL, which is in an Excel file
(spreadsheet format). Both of these files are located in the “Supporting Information” folder.

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 3
1.1.1.3 Publication modules

A Publication Module (PM) contains references to all DMs, PMs, and external publications (e.g., PDFs)
which are intended to be part of the publication output. Each of the included references must be listed
in the PM in the order it should be presented to the user. In other words, each reference (DM, PM, or
external publication) is published in the order it is listed in the PM. Since additional nested PMs may be
referenced, this highest‐level PM is often referred to as the “Parent” PM.
The Gun data set includes two PMs. “PMC‐S1000DGUN‐91005‐MM301‐00_001‐00_EN‐US.xml,” which
is the main publication. Additionally, “PMC‐S1000DGUN‐91005‐OPI01‐00_001‐00_EN‐US.xml” is
included, but contains no content. This additional PM was used for testing purposes with a Common
Source DataBase (CSDB) tool (refer to 5.1 for more information). Its existence is necessary for the
Publication Module references (element <pmRef>) within several of the included Gun data modules.

1.1.2 Other files

There are other files included in the Gun data set which are not DMs or even XML files. These are
graphics files and their file names begin with “ICN‐." An Information Control Number (ICN) is applied to
each symbol, illustration, photograph, or multimedia object within each publication. Each of the Gun
ICN files may be viewed individually in a graphic viewer. These graphics are referenced within the DMs
to be displayed in the necessary location (e.g., within a step or paragraph). Additional files include style
sheets, which are used to generate a page‐based publication. These files all end in “xsl.”
An additional folder, titled “Supporting Information,” in the Gun Zip contains the remainder of the
project deliverables, including:
a. Content selection matrices
b. Project business rules (in accordance with (IAW) the Data Item Description (DID):
DI‐TMSS‐81784, Army S1000D Project Business Rules)
Refer to 6 for a complete list of the files in the PhunGun.zip file.

1.2 Reporting errors and recommending improvements.

Any errors or recommendations for improvement should be reported to(Insert approriate e‐mail
address).

2 Acquire the Gun data set

Table 2 Operation ‐ Preliminary requirements

Tools needed 1. A text editor (e.g., Notepad) [however, an XML editor is

recommended (e.g., Altova’s XMLSpy, Parametric Technology
Corporation’s (PTC) Arbortext Editor, etc.)]
2. A graphics viewer (e.g., Internet Explorer)

Files needed 1. PhunGun.Zip (URL: https://www.logsa.army.mil/)

2.1 Viewing the XML

a. Create or identify a folder to contain the Gun data set.

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 4
 b. Download and extract the Gun files into the selected folder.
c. To view the XML for the sample DMs, open the XML files in the selected editor.
Note: Viewing the XML source will provide technical writers with examples for
writing S1000D/MIL‐STD‐3031‐compliant content. By reviewing the XML,
technical writers will gain a better understanding of how an S1000D DM is
constructed. Using the Gun data set will also provide additional examples
for authoring the required content IAW MIL‐STD‐3031A.

2.2 Locating the source data module from a PDF location

a. Open the Gun PDF (PMC‐S1000DGUN‐91005‐MM301‐00_001‐00_EN‐US.pdf).

b. In the footer, at the bottom right of each page, locate the data module code. All pages will
contain a data module code except for generated pages like the cover page or blank pages.
Note: All data module codes for the Gun begin with “S1000DGUN‐“ followed by a
mixture of numbers, characters, and dashes. This string of characters
represents significant information and is referred to as a data module
code.
c. Each [Gun] data module code is made up of hardware and information types. The hardware
type is identified by the model identification code, system difference code, Standard
Numbering System (SNS), disassembly code, and disassembly code variant. The information
type is identified by the information code, information code variant, and item location code.
d. When matching a data module code to its source XML file, match the model identification
code, SNS, information code, and information code variant. In most instances, these four
segments of information are enough to uniquely identify a data module. The Gun project
uses a single model identification code, “S1000DGUN.”
For example, the first data module encountered in the Gun PDF is the Safety Summary. The
Safety Summary is identified by its information code and information code variant, “012J.”
The data module code, identified in the PDF, is “S1000DGUN‐0‐00‐00‐00‐00A‐012J‐A.” This
code matches the XML file “DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐012J‐A_001‐00_EN‐US.xml.”
Review the breakdown as follows:
XML Data Module Code Comments
<dmCode> S1000DGUN‐0‐00‐00‐00‐00A‐ Data module code
012J‐A breakdown
Hardware type
@modelIdentCode S1000DGUN Model identification code
(MIC)
@systemDiffCode 0 System difference code
(SDC)
@systemCode 00 System
@subSystemCode 0 Subsystem
@subSubSystemCode 0 Sub‐subsystem
@assyCode 00 Unit or assembly
@disassyCode 00 Disassembly code (DC)
@disassyCodeVariant A Disassembly code variant
(DCV)
Information type

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 5
 @infoCode 012 Information code (IC)
@infoCodeVariant J Information code variant
(ICV)
@itemLocationCode A Item Location Code (ILC)

3 Checking the XML against the BREX file

Table 3 Checking XML ‐ Preliminary requirements

Tools needed 1. BREX validator (e.g., EZ BREX Checker (EZBC) (URL:

https://ussmg.btas.com/ssg/Library.aspx)).
[EZBC is available as follows, but is not approved for Army‐
networked computers. If you are currently not a member, please
go to https://ussmg.btas.com/default.aspx and then select (on
the left under USSIG) “Tools & Technologies Group.” Once in the
Tools & Technologies home, select “Document Library” and then
the folder “Tools” followed by “EZ Brex.” Note: The tool and
access to the website are free of charge.]
2. Text editor (e.g., Notepad)

Files needed 1. Army BREX, Rev A (URL:

https://www.logsa.army.mil/mil40051/S1000D.cfm)
2. S1000D Issue 4.0.1 BREX (URL:
http://public.s1000d.org/Downloads/Documents/Issue4.0/401def
aultBrexDM.zip)
3. Gun BREX (DMC‐S1000DGUN‐0000‐00‐00‐00‐00A‐022A‐D_001‐
00_EN‐US.xml, URL: https://www.logsa.army.mil/, in
PhunGun.Zip)

a. Setup the desired BREX validation tool.

b. Be sure to copy all BREX to folders as needed.
c. Follow the chosen BREX tool’s instructions for validating data modules.
d. Be sure data modules are validated against all applicable BREX.
Note: In this case, the Gun BREX references the Army BREX which, in turn,
references the default S1000D BREX. All data modules must be validated
against all three BREX to ensure compliance.
e. If there are BREX conflicts, the conflicting data modules must be corrected and then
revalidated against all BREX.
f. Repeat step e until no BREX conflicts are identified.

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 6
4 Publishing the XML
Table 4 Publishing XML ‐ Preliminary requirements

Tools needed 1. XML Publishing Application:

Arbortext (URL:
http://www.ptc.com/products/arbortext/epic/try.htm) or
Antenna House (URL:
http://www.antennahouse.com/product/axfo40/download.htm,
free 90 day evaluation)
2. Windows Explorer (or other file manager of choice)
3. PDF Viewer (e.g., Adobe Reader)
4. PDF creator (PDF Creator
[http://sourceforge.net/projects/pdfcreator/, free] or Adobe
Acrobat)

Files needed 1. PhunGun.Zip (URL: https://www.logsa.army.mil/)

4.1 Generating a complete publication:

a. The style sheets (files ending with XSL) are included with the Gun data located in the same
folder as the XML files.
Note: These XSL files are based off of the LOGSA‐provided style sheets. These
files have been tweaked for the Gun project.
b. If using Arbortext, proceed to step c; if using Antenna House, proceed to step d.
c. Start Arbortext (Epic) Editor.
1) Open the folder (using Windows Explorer or other file manager) containing the Gun data
set and the S1000D/MIL‐STD‐3031A style sheets.
2) Select the Gun PM (filename: PMC‐S1000DGUN‐11005‐MM301‐00_001‐00_EN‐US.xml)
and drag it to the Arbortext window. Alternatively, access the file from the Menu by
selecting File > Open, and navigate to the location of the Gun PM.
3) If there is no available Internet connection, a popup window similar to FIGURE 1 is
displayed. Select the “Open in free‐form mode without Schema/DTD” to view the raw
XML.
Note: The file cannot be validated when the Schema is not available.

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 7
 FIGURE 1. Arbortext – no Internet connection.
4) A popup window may appear, requesting the identification of a style sheet. If this
window appears, select the “X” (or “None”) to close it.

FIGURE 2. Arbortext – no stylesheet found.

5) From the toolbar, select the Printer icon (alternatively: File > Print composed…). Ensure
“Adobe PDF” is selected as the current printer. In the Stylesheet field, browse to select
the MAIN style sheet (filename: “FO‐3031‐A00‐S1000DGUN‐MAIN_001‐00_EN‐US.xsl”)
and select “OK.” Refer to FIGURE 3.
Note: There will be a slight delay to process the information, depending on
the speed of the computer.

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 8
 FIGURE 3. Arbortext – print composed view.
6) Proceed to step e.
d. Start Antenna House.
1) From the menu, select “File > Open.”
2) In the “Document” filed, browse and select the Gun PM (filename: PMC‐S1000DGUN‐
11005‐MM301‐00_001‐00_EN‐US.xml)
3) In the “Stylesheet” field, browse and select the MAIN stylesheet (filename: “FO‐3031‐
A00‐S1000DGUN‐MAIN_001‐00_EN‐US.xsl”).
4) Select “OK.” There will be a slight delay while Antenna House transforms the data. Once
completed, the publication will be viewable from within Antenna House.
e. Select the “PDF” icon from the menu. When prompted, enter a filename for the PDF
(recommend using “PMC‐S1000DGUN‐11005‐MM301‐00_001‐00_EN‐US”) and generate the
PDF.
Note: If the PDF did not open on its own, open it now to review the Gun
publication.

4.2 Generating formatted output one DM at a time

Follow the steps as noted under either Arbortext or Antenna House substituting the desired DM
instead of the PM.

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 9
 Note: Some information will not be displayed when generating a single DM. For
example, without the PM to provide basic information, the PMC will not
appear in the header.
Note: Whether generating output for a PM or a DM, always select the MAIN style
sheet for PDF generation.

5 Common Source Data Base (CSDB) Software and Tools

There are currently many options for CSDB software and tools, including products by: Corena,
Inmedius, O’Neil & Associates, PTC/ArborText, Raytheon, SDL, SiberLogic, WebX Systems, and more.
Only one tool, Electronic Maintenance System ‐ Next Generation (EMS‐NG) (developed by O’Neil &
Associates), was briefly reviewed for inclusion in this document.
Note: The Government‐funded Interactive Authoring and Display (IADS)
application is not a Content Management System (CMS) nor does it include
any management tools and, therefore, was not included in this
documentation. More information regarding IADS may be obtained from
the Website https://iads.redstone.army.mil or via phone at Team IADS
(256) 876‐4237.
Note: EMS‐NG was not evaluated for requirements in accordance with S1000D or
MIL‐STD‐3031A.
When selecting a CSDB tool, projects should consider the basic requirements needed for each available
tool. For example, EMS‐NG requires Internet access and recommends the use of MS‐Internet Explorer
v7. Projects with restricted permissions for Internet and software use should weigh these
requirements against current policy.

5.1 Working with data in EMS‐NG

The Gun data was used for basic testing within EMS‐NG. This allowed testing of the import feature in
EMS‐NG.
To import the Gun data into EMS‐NG, all related XML and graphic files were compressed into a single
archive (Zip file).
There are many options for creating a structure within EMS‐NG. The following include just one
possibility:
a. Create a “publication” called “S1000DGUN.”
b. Create a folder called “Upload.”
c. Select the “Upload” folder and then select “Upload file.”
d. Browse to locate and select the Zip file. Be sure to check the box marked “Unpack archive.”
Once the file upload has finished, archived files are automatically extracted. The XML files are
automatically validated and automatically registered in the CSDB, if no errors are detected. The
graphic files are also registered automatically.
Note: At the time this document was written, there were some permission issues
with file extraction from archives. Although the upload would complete,
the extraction would fail. This was reported and is likely already corrected.

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 10
 Registered CSDB files are displayed with bold file names for quick recognition.
Additional, detailed information regarding import/export is provided with the EMS‐NG documentation.

5.1.1 Workflow
From “home” menu, create a Workflow Definition named “Authoring.”
Establish a workflow definition as shown in Table 5.

5.1.1.1 Action label

Action labels are presented to the user in the To Do List. These labels should clearly communicate the
action to be performed if selected.
Note: Action labels should be entered based on the first value being the default
value.

5.1.1.2 Roles
Change roles after all states have been entered. Define groups for Authoring, Graphics, and QA.
Note: By using groups, the workflow remains the same. Group participants may
be modified as needed.

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 11
 Table 5 Workflow definition
Workflow State Name Run Mode Possible Actions / Roles / Resulting State
Type
(“Auto-run”
substituted for
all XML
Name checks) Action Label Role Result Options

Initial Auto-run None OK=>Authoring,

ERROR=>Graphics Needed,
Needs User Group: LOGSA (Vendor :
Authoring Submit SKIP=>Graphics Needed,
Action LOGSA) Authoring Group
OK=>Graphics Needed,

Group: LOGSA (Vendor : ERROR=>Illustrator ,

Yes
Needs User LOGSA) Authoring Group OK=>Illustrator ,
Graphics Needed
Action Group: LOGSA (Vendor : ERROR=>XML Syntax ,
No
LOGSA) Authoring Group OK=>XML Syntax ,

Needs User Group: LOGSA (Vendor : ERROR=>Edit Number2,

Illustrator Send to Edit2
Action LOGSA) Graphics Group OK=>Edit Number2,

ERROR=>Editor QA,
Needs User Group: LOGSA (Vendor :
Edit Number2 Submit SKIP=>Editor QA,
Action LOGSA) Authoring Group
OK=>Editor QA,

Group: LOGSA (Vendor : ERROR=>Illustrator ,

Reject
Needs User LOGSA) Authoring Group OK=>Illustrator ,
Editor QA
Action Group: LOGSA (Vendor : ERROR=>XML Syntax ,
Approve
LOGSA) Authoring Group OK=>XML Syntax ,

ERROR=>Edit Number2,
XML Syntax Auto-run Auto SKIP=>Finished,
OK=>XML Schema,

ERROR=>Edit Number2,
XML Schema Auto-run Auto SKIP=>Finished,
OK=>XML Link,

ERROR=>Edit Number2,
XML Link Auto-run Auto SKIP=>Finished,
OK=>QA Checks,

Group: LOGSA (Vendor : ERROR=>Finished,

Fail
Needs User LOGSA) QA Group OK=>Edit Number2,
QA Checks
Action Group: LOGSA (Vendor : ERROR=>Finished,
Pass
LOGSA) QA Group OK=>Complete,

ERROR=>Finished,
Complete Auto-run None
OK=>Finished,

Needs User
Finished
Action

a. From the “home” menu, create a workflow called “Gun Authoring.”

b. Select all files in Upload folder and select “copy.”
c. In the accordion menu, select “Workflow List > Gun Authoring” and then select “Insert Into
Workflow.”
d. Then select “Modify.” Select personnel involved and “start” a workflow.
e. The state table will then indicate the status of each file.

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 12
 f. Once a workflow has been started, open the To Do List for a list of available jobs. Process
each file as indicated by the workflow definition (e.g., edit, submit, no graphics, etc.). Refresh
the state table as needed to see the workflow progress.
g. If a file fails one of the automatic checks (e.g., schema, link) and no inWork increment is
desired, there is a workaround, as follows:
Warning: Performing these steps will lose the entire file history and is not
recommended; however, it is good information to know and can
be attempted with the Gun data for learning purposes.
1) Select the file in EMS and unregister the file for the CSDB.
2) Upload and overwrite the modified/corrected file.
Note: It is very important to remember to overwrite the existing
file.
3) Once the upload is complete, register the file once again in the CSDB.
There are too many features within EMS‐NG to cover in this document. This document is to provide a
brief overview of some features to consider when selecting a project CMS.
This also provides some information for importing the existing Gun data into EMS‐NG. Projects with
existing data should consider an import feature when selecting a CMS.

6 File list
Table 6 contains a list of all the files that are included in the Gun data set.

Table 6 File list

File type Filename Notes

Supporting
21 files
Information

1. Operator and Field Maintenance Manual for Content matrix

the S1000D Gun.docx
2. Project BR Decisions for Phun Gun.doc Project BRs, IAW DID
3. TABLE C‐I ‐ Information generation.xls Project BR Matrix
4. TABLE C‐II ‐ Authoring.xls Project BR Matrix
5. TABLE C‐III ‐ Identification and status.xls Project BR Matrix
6. TABLE C‐IV ‐ Common constructs.xlsx Project BR Matrix
7. TABLE C‐V ‐ Content section, schema Project BR Matrix
specific.xls
8. TABLE C‐VI ‐ Applicability, attribute values, Project BR Matrix
and training.xls
9. TABLE C‐VII ‐ CSDB, DMC, ICN, and DM Project BR Matrix
lists.xls

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 13
File type Filename Notes
10. TABLE C‐VIII ‐ Comment, version control Project BR Matrix
and interchange.xls
11. TABLE C‐IX ‐ PM, BREX, and information Project BR Matrix
management.xls
12. TABLE C‐X ‐ Content.xls Project BR Matrix
13. TABLE C‐XI ‐ Page‐based presentation.xls Project BR Matrix
14. TABLE C‐XII ‐ IETP presentation.xls Project BR Matrix
15. TABLE C‐XIII ‐ Information processing.xls Project BR Matrix
16. TABLE C‐XIV ‐ SNS and information codes.xls Project BR Matrix
17. DML‐S1000DGUN‐07GB6‐S‐2011‐ CSL (spreadsheet)
00003_001‐00.XLS
18. DMC‐S1000DGUN‐0000‐00‐00‐00‐00A‐ Project BREX
022A‐D_001‐00_EN‐US.xml
19. DMC‐S1000DGUN‐0000‐00‐00‐00‐00A‐ (Formatted, easy‐to‐read) Project
022A‐D_001‐00_EN‐US.pdf BREX
20. DML‐S1000DGUN‐07GB6‐C‐2011‐ DMRL (XML)
00001_001‐00.xml
21. PMC‐S1000DGUN‐91005‐MM301‐00_001‐ Maintenance Manual
00_EN‐US.pdf

Graphics 23 files

1. ICN‐07GB6‐2028A‐001‐01.jpg Currently not used, using table.

(Graphic is included for project
testing.)
2. ICN‐07GB6‐2028B‐001‐01.jpg Currently not used, using table.
(Graphic is included for project
testing.)
3. ICN‐07GB6‐BELTASSY1‐001‐01.jpg Used in four DMs
4. ICN‐07GB6‐BELTASSY2‐001‐01.jpg Used in three DMs
5. ICN‐07GB6‐BELTASSY3‐001‐01.jpg Used in three DMs
6. ICN‐07GB6‐BELTASSY4‐001‐01.jpg Used in one DM
7. ICN‐07GB6‐BII01‐001‐01.jpg Used in one DM
8. ICN‐07GB6‐CI001‐001‐01.jpg Used in two DMs
9. ICN‐07GB6‐COEI1‐001‐01.jpg Used in one DM
10. ICN‐07GB6‐DARTS1‐001‐01.jpg Used in one DM
11. ICN‐07GB6‐DARTS2‐001‐01.jpg Used in one DM

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 14
File type Filename Notes
12. ICN‐07GB6‐GUNLOAD1‐001‐01.jpg Used in four DMs
13. ICN‐07GB6‐GUNLOAD2‐001‐01.jpg Used in two DMs
14. ICN‐07GB6‐GUNLOAD3‐001‐01.jpg Used in three DMs
15. ICN‐07GB6‐GUNLOAD4‐001‐01.jpg Used in two DMs
16. ICN‐07GB6‐GUNLOAD5‐001‐01.jpg Used in three DMs
17. ICN‐07GB6‐GUNLOAD6‐001‐01.jpg Used in one DM
18. ICN‐07GB6‐RCVRASSY‐001‐01.jpg Used in one DM
19. ICN‐07GB6‐SLIDEASSY1‐001‐01.jpg Used in two DMs
20. ICN‐1L6T4‐AUTHENT‐001‐01.jpg Authentication graphic
21. ICN‐1L6T4‐EXPLOSION‐001‐01.jpg Hazard icon
22. ICN‐1L6T4‐EYEPROTECT‐001‐01.jpg Hazard icon
23. ICN‐1L6T4‐FLYNGPARTS‐001‐01.jpg Hazard icon

Contents 49 files

1. PMC‐S1000DGUN‐91005‐MM301‐00_001‐ Parent Publication Module for

00_EN‐US.xml Operator and Field Maintenance
Manual
2. PMC‐S1000DGUN‐91005‐OPI01‐00_001‐ Parent Publication Module for
00_EN‐US.xml Operator Manual (empty ‐ used
for reference testing only)
3. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐000B‐ Equipment description and data,
A_001‐00_EN‐US.xml descriptive
4. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐00SA‐ List of effective data modules,
A_001‐00_EN‐US.xml descriptive
5. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐001A‐ Title page, descriptive
A_001‐00_EN‐US.xml
6. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐010A‐ General data, descriptive
A_001‐00_EN‐US.xml
7. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐010B‐ General information, descriptive
A_001‐00_EN‐US.xml
8. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐012J‐ Safety summary, descriptive
A_001‐00_EN‐US.xml
9. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐017B‐ References, descriptive
A_001‐00_EN‐US.xml
10. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐018B‐ How to use, descriptive
A_001‐00_EN‐US.xml

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 15
File type Filename Notes
11. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐018D‐ MAC introduction, descriptive
A_001‐00_EN‐US.xml
12. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐018F‐ PMCS introduction, descriptive
A_001‐00_EN‐US.xml
13. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐023B‐ Reporting errors and
A_001‐00_EN‐US.xml recommending improvements,
descriptive
14. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐023C‐ Authentication page, descriptive
A_001‐00_EN‐US.xml
15. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐042F‐ Theory of operation, descriptive
A_001‐00_EN‐US.xml
16. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐067C‐ Ammunition marking, descriptive
A_001‐00_EN‐US.xml
17. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐070D‐ Expendable and durable items list,
A_001‐00_EN‐US.xml descriptive
18. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐104C‐ Additional Authorization List
A_001‐00_EN‐US.xml (AAL), descriptive
19. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐105C‐ Basic Issue Items (BII) list,
A_001‐00_EN‐US.xml descriptive
20. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐105D‐ Components of End Item (COEI)
A_001‐00_EN‐US.xml list, descriptive
21. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐111A‐ Controls and indicators,
A_001‐00_EN‐US.xml descriptive
22. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐120G‐ Procedures to activate
A_001‐00_EN‐US.xml ammunition, procedural
23. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐131A‐ Normal operation procedures,
A_001‐00_EN‐US.xml procedural
24. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐142B‐ Unusual environment/weather,
A_001‐00_EN‐US.xml procedural
25. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐200B‐ PMCS, checklist
A_001‐00_EN‐US.xml
26. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐258A‐ Other procedures to clean,
A_001‐00_EN‐US.xml procedural
27. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐300B‐ Test and inspection, procedural
A_001‐00_EN‐US.xml
28. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐525A‐ Ammunition unloading,
A_001‐00_EN‐US.xml procedural

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 16
File type Filename Notes
29. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐710C‐ Assembly of equipment,
A_001‐00_EN‐US.xml procedural
30. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐725A‐ Ammunition loading, procedural
A_001‐00_EN‐US.xml
31. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐810C‐ Preparation for storage or
A_001‐00_EN‐US.xml shipment, procedural
32. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐840B‐ Unpacking, procedural
A_001‐00_EN‐US.xml
33. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐870B‐ Checking unpacked equipment,
A_001‐00_EN‐US.xml checklist
34. DMC‐S1000DGUN‐0‐00‐00‐00‐00A‐916A‐ MAC, schedule
A_001‐00_EN‐US.xml
35. DMC‐S1000DGUN‐0‐00‐AA‐00‐00A‐280A‐ Inspect, procedural
A_001‐00_EN‐US.xml
36. DMC‐S1000DGUN‐0‐00‐AB‐00‐00A‐280A‐ Inspect, procedural
A_001‐00_EN‐US.xml
37. DMC‐S1000DGUN‐0‐00‐AC‐00‐00A‐271A‐ Adjust, procedural
A_001‐00_EN‐US.xml
38. DMC‐S1000DGUN‐0‐00‐AD‐00‐00A‐271A‐ Adjust, procedural
A_001‐00_EN‐US.xml
39. DMC‐S1000DGUN‐0‐00‐AD‐00‐00A‐280A‐ Inspect, procedural
A_001‐00_EN‐US.xml
40. DMC‐S1000DGUN‐0‐00‐AD‐00‐00A‐710A‐ Assembly procedure, procedural
A_001‐00_EN‐US.xml
41. DMC‐S1000DGUN‐0‐00‐AE‐00‐00A‐272A‐ Align, procedural
A_001‐00_EN‐US.xml
42. DMC‐S1000DGUN‐0‐00‐AE‐00‐00A‐280A‐ Inspect, procedural
A_001‐00_EN‐US.xml
43. DMC‐S1000DGUN‐0‐00‐AE‐00‐00A‐520A‐ Removal procedure, procedural
A_001‐00_EN‐US.xml
44. DMC‐S1000DGUN‐0‐00‐AE‐00‐00A‐685A‐ Repair, procedural
A_001‐00_EN‐US.xml
45. DMC‐S1000DGUN‐0‐00‐AE‐00‐00A‐685C‐ Replace, procedural
A_001‐00_EN‐US.xml
46. DMC‐S1000DGUN‐0‐00‐AG‐00‐00A‐271A‐ Adjust, procedural
A_001‐00_EN‐US.xml
47. DMC‐S1000DGUN‐0‐00‐AG‐00‐00A‐272A‐ Align, procedural
A_001‐00_EN‐US.xml

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 17
File type Filename Notes
48. DMC‐S1000DGUN‐0‐00‐AG‐00‐00A‐685C‐ Replace, procedural
A_001‐00_EN‐US.xml
49. DMC‐S1000DGUN‐0‐00‐AH‐00‐00A‐271A‐ Adjust, procedural
A_001‐00_EN‐US.xml

Style sheets 31 files

1. FO‐3031‐A00‐S1000DGUN‐APPLIC_001‐
00_EN‐US.xsl
2. FO‐3031‐A00‐S1000DGUN‐
ATTRIBUTES_001‐00_EN‐US.xsl
3. FO‐3031‐A00‐S1000DGUN‐CHECKLIST_001‐
00_EN‐US.xsl
4. FO‐3031‐A00‐S1000DGUN‐COMMON_001‐
00_EN‐US.xsl
5. FO‐3031‐A00‐S1000DGUN‐CONTENT_001‐
00_EN‐US.xsl
6. FO‐3031‐A00‐S1000DGUN‐CREW_001‐
00_EN‐US.xsl
7. FO‐3031‐A00‐S1000DGUN‐
DESCRIPTIVE_001‐00_EN‐US.xsl
8. FO‐3031‐A00‐S1000DGUN‐DMODULE_001‐
00_EN‐US.xsl
9. FO‐3031‐A00‐S1000DGUN‐DOCBOOK‐FO‐
RTF_001‐00_EN‐US.xsl
10. FO‐3031‐A00‐S1000DGUN‐DOCBOOK‐
FORMAL_001‐00_EN‐US.xsl
11. FO‐3031‐A00‐S1000DGUN‐DOCBOOK‐
PI_001‐00_EN‐US.xsl
12. FO‐3031‐A00‐S1000DGUN‐DOCBOOK‐
TABLE_001‐00_EN‐US.xsl
13. FO‐3031‐A00‐S1000DGUN‐FAULT_001‐
00_EN‐US.xsl
14. FO‐3031‐A00‐S1000DGUN‐FIGURE_001‐
00_EN‐US.xsl
15. FO‐3031‐A00‐S1000DGUN‐IDSTATUS_001‐
00_EN‐US.xsl
16. FO‐3031‐A00‐S1000DGUN‐INLINE_001‐
00_EN‐US.xsl

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 18
File type Filename Notes
17. FO‐3031‐A00‐S1000DGUN‐IPD_001‐00_EN‐
US.xsl
18. FO‐3031‐A00‐S1000DGUN‐LISTS_001‐
00_EN‐US.xsl
19. FO‐3031‐A00‐S1000DGUN‐MAIN_001‐ The MAIN style sheet for
00_EN‐US.xsl generating page‐based
publications
20. FO‐3031‐A00‐S1000DGUN‐PAGESETS_001‐
00_EN‐US.xsl
21. FO‐3031‐A00‐S1000DGUN‐PARA_001‐
00_EN‐US.xsl
22. FO‐3031‐A00‐S1000DGUN‐
PROCEDURAL_001‐00_EN‐US.xsl
23. FO‐3031‐A00‐S1000DGUN‐
PROHIBITED_001‐00_EN‐US.xsl
24. FO‐3031‐A00‐S1000DGUN‐
PUBLICATION_001‐00_EN‐US.xsl
25. FO‐3031‐A00‐S1000DGUN‐REFS_001‐
00_EN‐US.xsl
26. FO‐3031‐A00‐S1000DGUN‐REQCONDS_001‐
00_EN‐US.xsl
27. FO‐3031‐A00‐S1000DGUN‐SCHEDULE_001‐
00_EN‐US.xsl
28. FO‐3031‐A00‐S1000DGUN‐TABLE_001‐
00_EN‐US.xsl
29. FO‐3031‐A00‐S1000DGUN‐TECHREP_001‐
00_EN‐US.xsl
30. FO‐3031‐A00‐S1000DGUN‐WCN_001‐
00_EN‐US.xsl
31. FO‐3031‐A00‐S1000DGUN‐TOC_001‐00_EN‐
US.xsl
Total files: 124

Applicable to: All

BTAS‐2011‐0056_‐_S1000D Sample Data Users Guide.docx 2011‐09‐15 Page 19