standards-based ietms: the key to integrated weapon system support

Thomas Patton and John R. Quallen

ABSTRACT This paper describes the role of the DOD Interactive Electronic Technical Manual (IETM) standards in the application of electronic documentation to the TRIDENT I1 Strategc Weapon System (SWS) Program. The SWS Program integrates IETMs with SWS data providing automated operational and maintenance procedures and reference documentation at the SWS operator consoles. Integrated ship’s logistics, administration, and onboard training can also be supported.

provided that supports multiple “views” of a MIL-D-87269 compliant database, including a legacy view of the database used to minimize the operator impacts of the transition from paper to electronic documentation.

An IETM database development process is described that includes: Establishng the Baseline, the one-time low cost legacy technical manual conversion; Exploiting the Media, the incorporation of Class 4 IETM capabilities; and Maintaining the Baseline, an integrated IETM maintenance environment used for recumng maintenance of the IETM database. Authoring capabilities of the IETM Maintenance System are discussed as are other capabilities supporting workflow management, configuration control, electronic review and approval, and IETM database verification and validation.

Finally, programmatic experience is described including Navyicontractor coordination, adoption of standards, and suitability of the standards to the SWS application.

An operational environment is

Standards-Based IETMs: The Key to Integrated Weapon System Support

Introduction

he introduction of Interactive Electronic Technical Manuals (IETMs) into the arsenal of system support tools has the potential to be a blessing or a curse. They promise improved information access, timely update capability, and reduced cost, bulk, and weight.

However, the proliferation of multiple formats and classes of IETMs can se- verely limit their potential as a support tool and could even go as far as making them a sailor’s nightmare. Therefore, a series of Military Standards has been issued governing significant aspects of IETM implementation. The merit of these standards can be best attested to by the fact that they are among the few Military Standards that have been granted a waiver allowing continued use after the Acquisition Reform Act. This paper describes the application of those standards to the TRIDENT I1 Strategic Weapon System (SWS) Program and the many benefits and capabilities beyond simple IETMs that can be realized by building from the basic capability set to the full potential of integrated weapon system support using the same standards.

T

TRIDENT II IETM Program Overview In October 1997, the Strategic Systems Program (SSP) is planning to deploy IETMs for the TRIDENT 11 Fire Control System. The IETM will include description, operation, and maintenance documentation that is currently con- tained in fifty-six binders of Fire Control System and Guidance System support documentation. The documentation will be developed in a fully compliant Class 415 MIL-D-87269 DTD format and will be distributed via two media types. A magneto-optical disk cartridge will be provided to support downloading of the IETM database to the Fire Control System in support of on-line operations and maintenance. The operator interface to the Fire Control System is a Data Entry Subsystem (DESS), which consists of fully redundant, standardized POSIX compliant work stations in the Fire Control System. In addition, a CD ROM version of the IETM database will be provided to support shore based and off- line usage of electronic documentation via standard personal computers.

The primary objective of the IETM initiative is to reduce life cycle support costs by eliminating paper documentation. Other objectives include enhancing the operational environment by providing improved access to maintenance and operational documentation as well as further reductions in support costs through migration to a fully integrated, paperless, maintenance, logistics, and training support environment. Figure 1 illustrates a four phased approach to meeting these objectives for the SWS. Phase 1 provides the IETM to submarine per- sonnel using the DESS as the interface to the database and to shore-based users using a PC as the interface to the database. Phase 2 builds on Phase 1 by embedding procedural documentation into the SWS rather than merely providing access to the procedures. In Phase 2, the procedures are capable of monitoring SWS status information and using this data to step through routine decision

NAVAL E N G I N E E R S J O U R N A L May 1996 193


Reference Documentation I Integrated Procedure Support - I Interactive Lmal Access via * Access to TRIDENT - Local access

technical manuals 111 YIR DFSS

-Special information I types for improved use of technical

P ~ ~ S E 1 .j TRIDENT \ Student , Integrated Logistics and A dminis tra tion

, PHASE

Integrated Training Technical Information Database *Training Delivery

Operations and * Descriptive Text Management Control maintenance

environment support System

Preventive Maintenanc Scheduling

- 1 - . I

\ * Drawings * Tables

. PartsData

. Procedures

Wiring Data

. C^..l,n","

- Onbcard or shore based

. Standalone or integrated

Student management - Syllabus control

Students - Progress assessment - Student administration

icer weapons uffl

1 I . Failure reports

Parts ordenng Scheduling

. Inventory support

PHASE 4 PHASE 3 7it** Training Delivery * F I G U R E 1. Phased Approach for Integration.

trees in order to assist the operator. Phase 3 integrates training functions into the IETM database, including cur- ricula, lesson plans, training software, and student management. Finally, Phase 4 provides electronic administrative suppor t to both submarine and shore s i tes . Administrative functions include failure report generation, parts ordering and provisioning support, and preventive maintenance scheduling.

In order to achieve these objectives with an incremental insertion strategy, the following system level attributes were considered as driving the development of the IETM requirements : W Distributed Operational Environment

Coordinated Documentation N Dual Media Period

Multi-contractor Development

Distributed Operational Environment The IETM must support system level operations or be extensible to the system level. The Fire Control System is one of several subsystems in the SWS. Other subsystems (i.e. Launcher, Guidance, Missile, and Navigation) are physically located in other compartments of the submarine. The IETM must support system level procedures that involve multiple subsystems.

194

Coordinated Documentation In a complex system (such as the SWS) that involves multiple contractors, all inter-subsystem documentation references must be coordinated at the system level. When one contractor needs to refer to information in another contractor's documentation, a coordinated reference must be used. These references may be textual reference to a figure, paragraph, or volume or may be direct electronic links. The SWS IETM implementation must support these direct links and allow independent document development.

Dual Media Period For practical considerations, there must be a phased introduction of IETMs for the TRIDENT I1 SWS. There will be a dual media period where paper and electronic technical manuals must coexist. The IETM must support a referencing system that is consistent with the existing paper to support referencing between paper and electronic documents as well as consistency between electronic documents and their paper equivalents.

Multi-Contractor Development Standards must be established for the program to ensure consistent production of IETM databases by independent

May 1996 N A V A L E N G I N E E R S J O U R N A L


contractors. In addition, a vehicle needs to be established to ensure that the style, rendering, and functionality of the documentation is consistent among SVS Subsystems.

System Design Approach LEGACY DOCUMENTATION VIEW In order to minimize insertion impacts, it was decided early in the program that it was essential that the IETM must provide a view that was consistent with the existing documentation. Consistent was defined as the IETM hav- ing a technical information database with the following characteristics common within the corresponding paper documentation:

Identical content Identical referencing system Identical structure Support of the legacy view provides many advantages

that minimize insertion impacts and include the following: The cost of rewrites by subject matter experts is elim- inated. Original source material in electronic format can be automatically converted using commercially available conversion tools to generate the IETM Technical Infor- mation Database. IETM links can be generated automatically IETM database V&V costs are minimized. The technical content can be verified using the approved paper technical manuals.

End user training costs are minimized because the user is already familiar with the organization of the documentation.

Standardization Program standards must be established in order to ensure consistent development and application of IETMs in a multi-contractor environment. Figure 2 depicts the SWS approach to standardization. The DOD IETM standards were used as a basis for standardization throughout the program. Unique SWS program characteristics mandated the implementation of an additional level of program specific requirements.

The DOD IETM database specification, MIL-D-87269, was selected because it is well suited to support the legacy view as well as providing many other advantages including:

The ability to support basic information types (text, graphics, and tables) as well as special information types (interactive procedures, parts data and wiring data) Standard generalized markup language (SGML) com- pliance and compatibility with commercial SGML development tools. Support of other views including functional, physical (organizational), and operational.

UAS SWSGRAPHIC IETM DATABASE SOFTWARE STANDARDS DEVELOPMENT PROCESS (MIL-0-87269

COMPLIANTi

w v

T IETM

C (MILZ1-87270 COMPLIANT)

__-_ - I--.....------

ETM DATABASE DESIGN SW DEVELOPMENT

F I G U R E 2. SWS Standardization Process.

NAVAL ENGINEERS JOURNAL May 1996 195

Standards-Based ETMs: The Key to Integrated Weapon System Suppod

The ability to incrementally migrate to Integrated Class 5 capability, including expert system based diagnostics, training, and logistics support. The SWS graphics standards were developed to stand-

ardize all windows-based applications throughout the program. They incorporate the MIL-M-87268 IETM man- machine interface requirements and also impose additional design requirements like motif style, standardized menu layouts, and standard window design.

The SWS Database Design Document was developed to ensure consistent development of IETM databases between multiple developers. This standard incorporates the MIL-D-87269 IETM DTD as well as imposing additional database design constraints to ensure consistent interpre- tation within the program. Other IETM databases are also defined as needed to support style control and revision change bar indications.

The IETM System Specification defines the requirements for the User Access System (UAS), which presents the IETM material to the user. This standard ensures that the rendering and functionality of IETM material is consistent between platforms. This document also speci- fies the requirement to develop a Quality Assurance Pro- gram Plan in accordance with MIL-Q-87270 to ensure a consistent standard of IETM database testing and verification by independent developers.

Platform Independence Development of a database using the SWS database design document ensures that the Technical Information Data- base as a configured item is identical across a number of standardized delivery platforms. In addition, development of the User Access System software in accordance with the SWS UAS System Specification assures a consistent look and feel between different platforms.

IETM Development Environment Figure 3 depicts the approach to conversion and maintenance of existing technical manuals.

Establishing the Baseline- Conversion of Legacy Data The first step is to establish an IETM database baseline based on the existing, customer approved, paper documentation. Existing electronic source files are configured and reviewed for consistency to facilitate automatic conversion. The source material is then automatically converted into a MIL-D-87269 DTD compliant database that represents a legacy view of the electronic documentation. In addition to creating the equivalent legacy view, tagging elements are used to provide a high degree of interaction with procedures and parts and wiring data. The database is then tested and verified with the approved paper technical manuals for acceptance by the customer.

Exploiting the Media-Addition of Integrated, Interactive Features Once the legacy baseline is approved, additional '269 tagging can be applied to exploit the features of a class 415 IETM. Additional views are constructed by implementing tagging structures that reference elements in the legacy view. From a configuration management viewpoint, these additions are treated just like changes to the paper documentation, recjuiring the change proposal and approval process.

Maintaining the Basel ine-I ETM Database Maintenance Environment Database maintenance at this point consists of maintaining the '269 IETM database with a mix of commercially available and special purpose SGML editing and conversion tools.

Conclusion SYSTEM EFFECTIVENESS Since electronic documentation is available at the SWS, the time associated with retrieving documents and ac-

WCUMENTATION

F I G U R E 3. Technical Manual Conversion and Maintenance.

196 May 1996 NAVAL E N G I N E E R S JOURNAL


cessing information is greatly reduced. This reduction in time accessing information reduces the time to perform maintenance, therefore improving mean time to repair and SWS availability.

DATABASE CONVERSION AND MAINTENANCE Database conversion costs are minimal because existing documentation is converted to MIL-D-87269 via an automated process.

Documentation maintenance costs are significantly reduced because the whole process can be managed elec- tronically, simplifying location and modification of affected documentation.

LIFE CYCLE IMPACTS Further substantial cost savings are made possible by eliminating the costs associated with the production and handling of paper documentation. Specific areas of cost savings include: H Elimination of change pages and the need for change

page insertion. w Dramatic reduction in warehousing costs associated

with the storage of paper based on the fact that the equivalent of 20 to 30 cubic feet of typical t echca l manual binders can be stored on a single CD ROM. Reduction in printing and distribution costs.

IETM SPECIFICATIONS ASSESSMENT The DOD IETM specifications provide a good basis for standardization on a given program. However, additional definition is needed to guarantee consistent application in a multi-developeriuser environment. This definition includes the following: rn A single User Access System capable of consistent ren-

w A vehicle for electronic global control over IETM style. w A forum that can be used by developers and users to

dering of IETMs in a multi-platform environment.

standardize IETM application for their program.

C O M M E N T S B Y

Eric L. Jorgensen TECHNOLOGY MANAGER, IETM PROGRAMS FLEET USER SYSTEMS BRANCH NAVAL SURFACE WARFARE CENTER. CARDEROCK DIVISION

his reviewer has been directly involved with many T weapon system programs in the Navy, which are using IETMs based on the DOD IETM MILSPECS (soon to be converted to Performance Specifications), some- times called Class 4 Electronic Technical Manuals. Most of these programs are either targeted at new weapon

w Additional guidelines and specifications used to resolve all ambiguity associated with IETM development and display.

ACKNOWLEDGMENTS The authors wish to acknowledge the staff at SP23, par- ticularly SP231 and SP232, for their vision and support for this effort. Also, a special thanks to Mr. Gerald Delisle for his contributions to the development and application of this technology

Thomas Patton is a Senior Project Engineer at Lockheed Martin Defense Systems in Pittsfield, Massachusetts. In his current assignment, he is leading a groundbreaking project for the development and integration of electronic technical manuals with the TRIDENT I I Fire Control System. In previous assign- ments, MI: Patton has led the development and deployment of integrated electronic training and maintenance systems for ship- board weapon systems and aircrafl training. These efforts include pioneering research into the application of interactive video disc technology and computer aided courseware. MI: Patton holds BSEE and MSEE degrees in Electrical Engineering from Villanova UniuersiJ? He has presented several papers on the subjects of cmputer based training, maintenance, and computer graphics.

John R. Quallen is currently the Program Manager for Fleet Ballistic Missile (FBM) Systems Software and Support Equip- ment at Lockheed Martin Defense Systems in Pittsfield, Massachusetts. In addition to his present role in the development of a Class 4 Interactive Electronic Technical Manual (IETM) for the TRIDENT Strategic Weapon System Program, MI: Qual- len hns previous experience in the development of a fully integrated documentation and expert maintenance system for the Phalanx Program. He is currently a member ofthe FBM IE TM Standards Committee and the IETM Working Group. MI: Quallen holds a BS and a Master of Engineering degree in Elec- trical Engineering from Rensselaer Polytechnic Institute. His early experience includes hardware design for the TRIDENT Strategic Weapon System Program as well as management of both Hardware Design and Systems Engineering organizations for the BSY-2 and Phalanx Programs.

systems, such as F-18 EiE or a major revision of the technical documentation for a constantly changing system, such as the AEGIS Weapon System (AWS). These programs have been able to justify the historically high expense of converting the paper-based documentation to a MIL-SPEC IETM Class 4 capability. They can justify that expense with the expected higher technician performance in maintenance and training. However, the benefits of the capability described by Messrs. Quallen and Patton include aspects not stressed in the other programs and, to no little extent, reflect a unique major contribution of this effort to the Navy.

The unique nature of the Strategic Weapon System (SWS) IETM database lies in its being developed 1) to

NAVAL ENGINEERS JOURNAL May 1996 197

Slandards-Eased IETMs: The Key lo fnfegraied Weapon Sysfem Support

improve the configuration accountability and management of the SWS data; and 2) to manage contractors in a common source. The first element, configured management, is to reduce the major cost in the life-cycle maintenance of a Technical Information Database. Regarding the sec- ond element, the SWS program is one of the few in the DOD to have obtained a satisfactory solution to the very difficult problem of funneling the contribution of independent technical information source data contractors into one common manageable whole.

These benefits are being achieved and are significant even though the information is being displayed primarily, at this time, in a “legacy view,” i.e., something that is not very different from the paper technical manuals. The unique situation with the SWS program paper TMS is that they are of exceptionaly high quality and familiarity to the users. The benefits of truly interactive TMs would not be as great in the FBM program than they are for much of the rest of the fleet. The contribution of this paper in my thinking is demonstrating how significant those life cycle cost reduction benefits really are to the Navy They have additionally achieved these benefits and converted to their IETM specification compliant database at much less of a cost than most of the other systems with which this reviewer has been involved.

This reviewer stresses the above unique contributions as ones that the rest of the Navy should examine and evaluate. The presentation system developed to support the database capability is expandable to the capability of other Navy IETM systems, largely by augmenting the underlying data. In other words, the capability has built into it the capability to migrate to more interactive display without reauthoring the underlying information. This is a major contribution and is largely a spinoff of using the MIL- D-87269 data structure, even for the legacy-data view Thus the approach has laid the foundation for acheving the other benefits of IETMs without fully implementing that capability when it is not needed. This also may serve as a model for the rest of the Navy.

C O M M E N T S B Y

Wayne Honea NAVAL SURFACE WARFARE CENTER-PHD DIVISION

he paper “Standards-based IETMs: The Key to T Integrated Weapon System Support” outlines a well thought-out plan to develop and implement a Class 4 functional IETM with the TRIDENT I1 Strategic Weapon Sys- tem (SWS) Program. This paper identifies many of the life cycle issues that must be considered prior to the devel-

opment of an IETM. The four phased approach of 1) developing reference data, 2) Integrated Procedure Support, 3) Integrated Training and, 4) Integrated Logistics and Administration Support identifies a loacal progression of producing a Class 4 IETM which then migrates to Class 5 functionality by it being interfaced to other systems databases such as expert systems. The paper presents an important message that Class 1 through 4 ETMsiIETMs can be interfaced to expert systems thereby allowing the Class 1-4 ETMiIETM to functionally perform as a Class 5 IETM.

It is also notable that the SWS IETM implementation attempts to minimize the reauthoring of legacy data when populating the MIL-D-87269 database. This, as the paper points out, will minimize validation and verification costs and ease transition to existing fleet and training users. Also, the use of existing displays (DESS) which support the Fire Control System minimizes costs and solves many issues regarding accessibility, storage, and maintenance of IETM displays.

Although there are other issues involved in implementing IETMs, this paper presents a well thought-out plan of developing, implementing, and maintaining an IETM into the fleet.

A U T H O R ’ S R E P L Y

The authors would like to thank Mr. Jorgensen and Mr. Honea for taking their time to review and comment on our paper. They are two experts in the field with substantial breadth of experience between them. It is significant that they both feel that the process being applied to the TRI- DENT program represents a unique approach to low cost development of Class 4 IETMs. The key to achieving Class 4 capability at a reasonable program cost is to avoid significant re-authoring of the legacy data which is already available. Based on a typical experience to date, re-authoring of technical data drives costs to the $100 to $400 per page range. The approach described in this paper results in costs an order of magnitude less than that for initial conversion. Follow-on maintenance costs for either approach will be similar since the maintainabihty is primarily a function of the data structure. Another benefit of this data structure is the ability to migrate to advanced functions in a controlled manner based on unique program needs and consistent with available funding.

The use of standards in the Trident program has re- sulted in an unprecedented degree of compatibility between contractors and program branch offices which would seem to be beneficial if applied at a higher level within the U. S. Navy. The authors welcome further interchange with Mr. Jorgensen and Mr. Honea in order to pursue further application of standards to a broader base.

198 Mav 1996 NAVAL ENGINEERS JOURNAL

standards-based ietms: the key to integrated weapon system support

Documents