MIL-DTL-87269D
3.1.5 The Interchange Layer Part 2. The Interchange Layer Part 2 is the holding area for a harmonized set
of common content entity, element and structure declarations and DTD fragments that employ the semantics
and primitive elements found in the generic layer to implement interactive presentation models. The common
elements and data structures contained in this area are provided as building blocks for content-speciic layer
data model developers and as harmonized pathways for the migration of ETM content that was developed
employing the harmonized entities, elements, and structures found in Part 1 of this layer. Data model
developers are free to use all or part of the entity, element and data models provided in this document
by commenting out undesired content. Data model developers are advised however that commenting out
of any table or list models provided in this area will also necessitate the removal of their entity
declarations from the generic layer. IETM table and list functionality is dependent upon the presence of
both this Part 2 Harmonized IETM Interchange Model Area DTD and the generic layer DTD in the
Content-speciic Layer DTD Content Data Model.
3.1.6 The bottom layer. The bottom layer, the content speciic layer (CSL), shall employ the generic layer
when deining elements for weapon system speciic TI. Many content speciic layers can be developed in
accordance with the generic layer. An example CSL DTD is available for download. (See Appendix A.1.1.)
3.2 The CDM generic layer. The CDM generic layer is the DoD standard for any IETM technical
information data base procured using this speciication. In addition, unless otherwise speciied by the
procuring activity, the content speciic layer Document Type Deinition (DTD) (see 6.2b.)The IETMDB can
be invoked by a procuring activity in either one of two modes as follows, depending on whether a database
is (1) speciied for interchange and delivery to the Government, or (2) being developed and maintained for
the subsequent preparation of IETMs, but not actually delivered to the Government.
a. Database interchange requirements. When speciied, IETMDBs which are to be delivered to the
Government under this speciication shall be structured and tagged in accordance with the DTDs
and the tag set descriptions referenced in Appendix A (see 6.2c.).
b. Database structuring and data element naming requirements. Unless otherwise speciied, a
deliverable instance created under this speciication shall be structured in accordance with the
hierarchical relationships deined in the CDM DTDs referenced in Appendix A, and created and
named using the tag set descriptions contained in the referenced DTD. When a tagged instance is
not speciied for delivery, the contractor shall maintain the ability to map the internal element
names to the speciied content speciic DTD names (see 6.2d.).
3.3 Format free technical information. The IETMDB shall consist of an assemblage of data elements,
including a listing of the speciic attributes possessed by the data elements; and a list of explicit relationships
providing logical links among the data elements. The relationships incorporated into the database, by the
IETMDB author, shall provide the basis of the technical structure of the IETMs and other logistic support
TI which will be extracted from it. The IETMDB shall not contain format directions in the sense of
arrangement of text and graphics on a display screen for presentation to the end user. The IETMDB itself
shall require a "format" (database structure) but this speciication does not impose structural requirements on
the actual Database Management System (DBMS) methodology to be employed (i.e., the database may be
either relational or object oriented). The exterior view of the database to be used for updating, adding cross
references, producing tagged output iles, etc. shall conform to requirements of this speciication.
3.3.1 Data portability. Formatting requirements shall be eliminated from the IETMDB to reduce the overall
magnitude of database and data interchange standardization effort. This shall also permit the use of a less
complex DBMS by the contractor which is, in turn, less expensive and easier to modify. The "format-free"
nature of the IETMDB shall provide the Government the capability to:
a. Acquire or access the data in a variety of ways (IETMs, other types of logistics reports,
training TI, etc.).
b. Subsequently format and style the data in a variety of ways for electronic display options.
3.3.2 Integration support. IETMDBs shall provide direct, on-line data access to a variety of users and to
a number of automated logistic support and management information systems throughout the services.
4
For Parts Inquires call Parts Hangar, Inc (727) 493-0744
© Copyright 2015 Integrated Publishing, Inc.
A Service Disabled Veteran Owned Small Business