TABLE OF CONTENTS

   

LIST OF FIGURES

      

LIST OF TABLES

      

      

      

The MID DTD defines elements that can be found in common programming languages. Specifically, the MID includes elements for creating variables, expressions, functions, and for doing various kinds of branching and conditional branching. MID developers refer to the MID as a scripting (as opposed to a programming) language [3] and IETM data can be "scripted" in three different ways: by directly placing IETM data within MID-defined SGML tags, by pointing to IETM data that resides in an external source, or by querying an external source that contains IETM data.

The MID effort was initiated by Carderock Division Naval Surface Warfare Center (CDNSWC) in early 1994. With the initiation, funding was obtained and a MID committee was formed. The original MID committee included both government and industry representatives. By December 1994, the committee had produced a draft MID specification [1] (dated November 1994), the MID SGML DTD, and two limited prototype MID processing and presentation systems that both run under MS Windows 3.1. (One was written in Microsoft Visual Basic, the other in C.)

During 1995, a new MID effort led by the Naval Air Warfare Center Aircraft Division (NAWCAD) in St. Inigoes, MD began. The goal of the new MID effort has been to refine and improve the original MID DTD. Additionally, the effort intended to provide software that can process and present data encoded in accordance with the new MID DTD. Throughout this report, all references to MID-I refer to the original MID DTD, whereas all references to MID-II refer to the new MID DTD.

The existence of MID-I coupled with the development of MID-II has complicated the execution of this task. Complications arose in the assessment/analysis and in the Internet implementation because MID-II is not downwardly compatible with MID-I; MID-I is not a subset of MID-II. Also, MID-I was designed to enforce certain constraints imposed by MIL-M-87268, whereas MID-II relaxes those constraints.

After coordination with CDNSWC and NAWCAD, it was decided, due to its stability, that the original MID specification, hence MID-I, would be used for the Internet implementation and the view package development. It was also decided that both MID-I and MID-II would be used in the survey review and assessment/analysis (subtasks 1 and 2). MID-II was not considered in the view-package and software development aspects of this task because the initial approach hinged upon the ready availability of MID instance interpreter software as well as a stable target DTD for carrying out the software development.

      

At this time, a number of different IETM system architectures exist within DoD. No single, widely accepted, standard IETM system architecture is available for construction of DoD IETMs. Because of this, the first part of this analysis section is devoted to IETM system architecture issues, culminating in the presentation of a preferred high-level system architecture for IETMs.

With the proposed architecture, various competing and/or emerging approaches are described in terms of their capabilities as scripting languages (the MID is considered a scripting language). These approaches, coupled with two others that are not considered in terms of their scripting capabilities, are then compared (see Appendix A) according to the following categories:

1. MIL-M-87268 compliance;
2. MIL-D-87269 compliance;
3. Commercially available language;
4. Coupling of presentation and authoring;
5. Export facilities;
6. Import facilities;
7. Integration;
8. Level of interoperability;
9. Knowledge required by authors;
10. Language or software;
11. Military implementations;
12. Non DOD implementations;
13. Notation support;
14. Other vendor implementation;
15. Portable language;
16. Presentation or data;
17. Problem to be solved;
18. Public libraries;
19. Requirements;
20. Scripting language;
21. Specification status;
22. Stylesheet; and
23. Support for plug-ins.

3.1  Overview of IETM Architecture Issues

Meanwhile, the academic and industry proponents have radically shifted their focus from providing tools based on international and government standards to the production of tools for the Internet, and more specifically, the World Wide Web. These tools are simple to use and have been embraced by very large segments of the worldwide hypermedia communities. It is questionable if the technical and political climates in which these tools are produced can provide stable platforms that can meet the rigorous and mission-specific requirements of IETMs. What cannot be disputed is that these tools can be acquired at very low costs and that a substantial base of authoring and end-user expertise with them is growing rapidly.

Project and acquisition managers have become strident in asserting that any new systems for technical information management and production must provably contribute to the bottom line of reducing overall costs. It has become difficult to convince them that the advanced IETM standards and designs are worthwhile, particularly where these standards and designs require extensive retooling and training processes to occur before a single bit of technical data is produced or fielded. At the same time, the tools of the Internet community are evolving towards increased complexity and will soon be just as expensive to use as their DoD counterparts in the IETM community, if cheaper to acquire.

These issues have produced hysteresis in the IETM community members. Simply put, they are "frozen in the headlights." For those who must provide guidance, overall policy direction and funding for IETM systems, the following questions are most important:

1. Should IETM tools be general purpose tools (i.e., COTS) if that generality raises the overall complexity and cost of providing technical information to the end-user?

2. Should the focus of IETM standardization and production be on tools and languages expressly created to simplify the production of IETMs or on those that promise long term life-cycle payoffs?

3. What combination could satisfy the need to reduce overall costs yet still provide an effective environment for creating, managing, and delivering technical information in digital form with added levels of functionality beyond the current paper-based systems?

4. Where does the added functionality of the advanced IETM enhance the mission of the IETM and the mission of the organization it supports, and when would simpler forms be more effective (i.e., ETMs)?

5. Is it more productive to prescribe a set of architectural standards that describe an overall IETM functional architecture while leaving the issues of content description to the local subject matter experts, and specific system purchases to project and acquisition managers?

The sections below, present major points of view of the technical participants in the IETM community. This is done to enable the reader to better understand the issues confronting the community and the rationale for the architecture that is proposed. The architecture that is ultimately presented is designed to enable the acquisition of IETM tools and functionality to meet IETM requirements without sacrificing mission goals or requiring exotic, one-shot technology.

3.2  Document Architecture

The use of document architectures was presented by Dr. Charles Goldfarb at the Document Interchange Symposium of DISA in March 1993. The following quote by Dr. Goldfarb is from the minutes of that symposium.

I want to clarify several technical points by drawing a model of information flow and representation. A source document (abstract or "logical" structure) is created as a set of information you want to send to people. You can create a result document that can be perceived by others by creating a presentation form with a transformation process. Or the output might be passed on for use by another application such as a search query or database load. The result document can get transformed again, and the cycle may be repeated many times with the result document becoming a new source document for another process.

The transformation process that is operating on the document is driven by a set of specifications that tells it what the user wants it to do. A document architecture defines one or more programs that operate on a document and the form of the end result. A document architecture is a set of rules that defines source document types, the processes that operate on a document, and the form of the end result.

Figure 3.2-1 illustrates the transformation process as drawn by Dr. Goldfarb at the symposium.

3.3  Concept-Centric Views

3.3.1  Display-Centric Systems

• Performance;
• Ease of use;
• Ease of preparation; and
• Ease of integration within the chosen format.

The primary disadvantages are

• Low reuse of information;
• High cost of long term maintenance;
• Lower potential to provide enterprise-wide standardization; and
• Difficulty of integrating non-system specific data formats.

In short, the display-centric system swaps ease of creation for life-cycle maintenance costs.

3.3.2  Data-Centric Systems

• High reuse of information;
• Lower cost of long term maintenance; and
• High potential to provide enterprise-wide integration.

The primary disadvantages are

• Complexity of initial setup and fielding; and
• Necessity for a sophisticated authoring system and data management system to use to full potential.

Data-driven systems enable reuse of information. The data-driven system excels at supporting long life-cycle requirements but at the higher cost of initial setup. Without a customizable data management system, the data-driven system is not intrinsically better at data management than a display-centric system, but it is more effective than the display-centric system, when one is applied, because the properties of the information can be more directly coupled to the specific information representation of the enterprise processes and products. The degree of this effectiveness is heavily influenced by the skill of the schema designer (e.g., SGML Document Type Definition (DTD) or relational schema, or both).

3.3.3  Server-Centric System

3.3.4  Framework-Centric Systems

• The framework API enables controlled evolution of the products. As new protocols or notation processors are required, new plug-in servers can be developed.

• Using plug-ins, the footprint of the code is reduced as common libraries for common functions are used (e.g., the parser code is shared among all SGML subsystems).

• The buyer of the framework can choose plug-ins for functions required for that application of the framework. This encourages competition and functional matching. The functionality scales to the requirements for the mission.

• The framework user interface is consistent and is under some control by the author. Depending on the skill of the authors, a range of document interactions can be specified. The functionality scales to the skill of the author.

A framework-centric system subsumes other concept-centric views and architectures. It is the most flexible system architecture with respect to scalability (number of users, products, and processes to infrastructure components), long life-cycle costs, and the types and contents of information used and managed by the system.

The primary disadvantage of the framework-centric system is that the API is controlled by the framework vendor. Standardization of the IETM framework API is encouraged. For advanced IETM systems, framework-centric systems are recommended and are the focus of the functional architectures in the remainder of this report.

3.4  Document-Centric Enterprise Architectures

• Document-centric:  a metalevel for assembling tasks and scripts based on a document type to document type protocol. This level associates knowledge with information.

• Task-driven model:  the author of the document uses the information relationships expressed as scripted hyperlinks and dialogs to direct the user of the document through a series of tasks that accomplish some goal, e.g., remove and replace, assemble, inspect, place order, etc. This level applies knowledge to information.

• Distributed Transaction Processing:  the application of On-Line Transaction Processing (OLTP) to distributed network processors. This technology distributes manageable information to knowledgeable users.

In this section, the application of these concepts is discussed in terms of the framework-centric document environment.

3.4.1  Document-Centric Systems and Protocols

Document-centric systems ease the use of database technologies by integrating these technologies under a hypermedia document metaphor. Organizing and maintaining documents is a task that all business organizations do, and most, without the assistance of the Management Information Systems (MIS) departments. The failure to understand and apply this understanding is at the root of the sluggishness of client-server markets.

It is important to understand how a user of a computer system applies knowledge to the information, through the tools, to get a predictable and testable result. The user of the tool knows the business. Any attempt to market to this customer with terms that do not match the knowledge of that business will ultimately fail. Any attempt to apply the technology by the customer in terms that do not correspond to the knowledge will ultimately fail.

The computer industry consistently fails to market its technology in terms that can be understood by its customers as advantageous, or in a form that enables the customers to control their own business processes with this technology. Customers for a technology consistently fail to purchase technology based on their knowledge of the requirements of their business. While we can tritely call this a failure to communicate, it is really a failure to negotiate the best advantage, which is the ultimate form of business collaboration.

Different technical approaches to information systems provide advantages to different users of the technology:

• Relational - advantage accrues to data maintainer.
• Object-oriented - advantage accrues to data programmer.
• Hypermedia - advantage accrues to data user.
• Document-centric - advantage accrues to the organization.

A document-centric system within a framework-centric environment is flexible with respect to the different data types and methods of storing data. It is better matched to the current contracting practices in government and commercial enterprises. What has been missed in past attempts to apply document-centric approaches is the ability to tighten the granularity of document content to be appropriate to the task at hand. Because the definition of the content in a database schema or SGML content, DTD drives not only the end product but also the processes for creating that product. Closely matching its structures to the day to day business processes is fundamental to improving the products. In most cases, the SGML syntax itself is best hidden from the content provider just as a relational schema is not exposed.

To better understand these issues, we examine the knowledgeable views of each of these parties to the collaborative effort of creating and using information. In all of these views, it is assumed that the developer has made reasonable efforts to create an interface that hides the technical details of the implementation. Later, we will revisit this technical decision and ask if it can still be supported in a document-centric system. The reader should understand that these views are not discrete. It is not only possible to combine aspects of these views, under document-centric design supported by a framework architecture, but also exactly what is provided.

3.4.1.1  Relational View

As shown in Figure 3.4.1.1-1, the view of the relational database designer and maintainer is a universe of report forms, tables, and keys.

The major advantage of relational technology is that once created, it is very easy to maintain and to reorganize by adding new relationships. Another advantage is a strong standards basis in both the data models and in the query language, i.e., Structured Query Language (SQL).

The major disadvantage is that it is not easy to navigate if the organization of keys is unknown to the user, or to rebuild if a new business model is needed. Another disadvantage is the use of fixed length fields. If a user has a record value that exceeds a field length, or wants to store a non-text value such as a graphic, extensions to the relational paradigm called Binary Large Objects (BLOBs) have to be used. These are typically non-structured and are managed by the relational system by storing pointers to the BLOBs.

3.4.1.2  Object-Oriented View

The disadvantages of object-oriented systems are that they are difficult to reorganize if the base class structure is not sufficiently descriptive or sufficiently abstract, are large and sometimes do not perform as well, and cannot be reorganized by the owner of the information unless the owner of the information is a skilled object-oriented programmer. Other disadvantages are the lack of standardization for the message interfaces and provable data normalization. Industry groups such as the Object Management Group (OMG) are working to overcome these.

Too often, it is the assumption of the programming staff that the object paradigm, used to represent practically everything in the processing environment, is equally applicable to the content-providing environment. This is a misconception. It is the abstract nature of object-oriented design that prevents the content provider from attaining goals of accuracy and productivity. The object-oriented nature of the information system, like the SGML syntax and relational schema, is best hidden from the content provider. However, the object-oriented framework is used to support the content provider. Section 3.5 revisits the object-oriented approach as realized in the abstract design of framework browser systems where is it well-suited to the job of organizing information system components, if not the information itself.

An object-oriented system makes no promises with regards to the use of scripted interaction other than to provide a set of messages that can be used in a script. Because the organizational flow of messages (a formal protocol) is the basis for business collaboration, this is a major flaw of the purely object-oriented paradigm.

3.4.1.3  Hypermedia View

The major advantages of a hypermedia system are as follows:

• It is easy to navigate, as the book-metaphor presentation resembles the interface with which the user is most familiar.

• It subsumes other database types at the display level while still enabling the data to be organized and managed flexibly.

• Hyperlinks offer the opportunity to organize data semantically so that it can be reused in different media. For example, the audio prompt files for the hypermedia interface could also work with an integrated voice response system used in a call center, and in different missions, for example technical manuals and training. A semantically organized system enables reuse based on retrieving the hyperlink, then letting the client determine which target notation is appropriate and route it to the correct notation handler.

The major disadvantages are below:

• The standards for hypermedia are many and are in conflict. This is particularly true of scripting standards, APIs, and link and location models. In the World Wide Web standards, there is perceptible instability in the standards, the standards making bodies, and in the conformance of vendor designs to these standards, despite the efforts of their consortia.

• The experience with creating hypermedia is not widespread and is overvalued.

• The hypermedia system chosen varies in its ability to handle different data notations.

• Hypermedia has not proven its ability to be a stable working platform that reduces costs; therefore, acquisition managers are hesitant to commit to it early in a product's life-cycle where it is of most benefit to cost reduction.

• Hypermedia must be organized to fit the products and processes of the enterprise that uses it and deploys it. Systems such as the World Wide Web depend on fixed notations, (e.g., HTML, that cannot be adjusted to meet the requirements of a dynamic business or logistics environment).

A critical missing piece in most academic, commercial, and freeware hypermedia systems is a methodical process for creating, testing, and maintaining the hypermedia contents and tools to support the design and deployment of these processes. Problems of persistent representation of locations for content are severe in these implementations. The environment that produces these systems is predatory and weakly administered.

It is becoming common knowledge that if you plan to wait to purchase until the standards for hypermedia systems are stable, you have elected not to purchase one. This is supported by a conclusion within [4], with respect to HTML, which states, "If a strict adherence to firmly established standards is required before the client will consider purchasing an HTML product(s), then accept that this may be the same as deciding not to purchase any product in the near future." Yet with all of the disadvantages, hypermedia systems such as the World Wide Web are experiencing explosive growth using the simplest techniques of the hypermedia disciplines. It is easy to conclude that even with all of the problems, hypermedia technology is the harbinger of business opportunities for the next decade because it provides a solution the customer finds attractive and can use.

3.4.1.4  Document-Centric View

For IETMs and business applications, a more complex document model is required that enforces relationships among the document structures, within a document and among families of documents, to ensure that the relationships and their representative structures are

• Valid:  applicable to documents of the appropriate types and the content that they are modeling;

• Prescriptive:  efficient for driving the creation of the content of these documents in the business environment; and

• Testable:  aid in testing that the content of the instances of these structures is accurate.

While the overall document model is more complex, it must be produceable and manageable. This can be provided by modularizing the document design so that these modules can be assigned to separate mission or content specialists (e.g., subject matter experts) to be created and managed, yet can be integrated automatically using pre-defined relationships among the contents of the modules.

• The concept of types of documents defined by SGML Document Type Definitions (DTDs) using PUBLIC definitions approved by communities of interest (e.g., U.S. Navy Concept of Operations (CONOPS)) and those defined for site-specific operations (e.g., local site and system CONOPS) cited as SYSTEM definitions.

• Predefined relationship models for navigating the content of these documents and for assembling views of this content automatically.

• HyTime and Document Style Semantics and Specification Language (DSSSL) properties and architectural forms to standardize the document framework.

• Configured processes that specify for the CONOPS which document is relevant to a particular task.

Because the construction and maintenance of content for such documents is a complex process, standard database technologies and work processes are used to control both the authoring and the viewing of this content. The major challenges to the use of this model are as follows:

• To provide an integrated authoring suite for the notations used that can author directly to the database under the database management system.

• To provide a rigorous methodology of content creation particularly where the content is legacy information in a conversion pipeline.

• To provide a process design tool that enables the local site to adjust these processes and the configuration of the systems to the local CONOPS.

The last task is provided for by the application of meta-editors for process design based on task-driven models to design and configure enterprise performances.

3.4.2  Task-Driven Models

Although Figure 3.4.2-1 illustrates a simplified business process, there is no difference between this model and the maintenance models of IETMs. These are task-driven models, and given a configurable modeling tool, can be supported by the same technology. In an IETM task-driven model, the actions required to maintain a complex weapon system will be divided among standard activities such as diagnose, remove, replace, test, etc. Each of these actions may require multiple accesses to the same information with each reuse of that information impacting the overall process differently.

This information may be presented by multiple media, but more importantly, the same information may be required to be available in different media. For example, if the IETM system supports a central server, it should be possible to access information by a screen display (text and graphics) or a telephone (prompt-driven audio, a.k.a., integrated voice response). Enabling the authoring of such tasks and managing this information concurrent with the evolution of the weapon system being maintained, and the enterprise which maintains it, is precisely the mission of the IETM community and its products.

• A process is always specific to the enterprise that executes it, its CONOPS. A CONOPS applied to a class of enterprise can be applied to all enterprises of that class with local site CONOPS tailoring. A generic CONOPS is a template for the operations of all instances of the class of business.

• The enterprise is specific to the product it creates, its mission.

• A product is configured according to the mission for that product and according to conditions of the environment in which the mission performance occurs (i.e., the local CONOPS).

The application of process modeling to the design of processes specific to a particular product or family of products is enterprise engineering. This is a well-known practice in logistics organizations that must analyze the actions required to maintain a system, codify these in Logistics Support Analysis Records (LSAR), and reuse them in technical manuals. All task-driven systems are, themselves, examples of event-driven models. The enterprise engineer designs task-driven systems based on an analysis of the events that influence or directly affect the task of creating and maintaining products.

3.4.3  Document Protocols

3.4.4  Distributed Transaction Processing

The performance advantages of OLTP systems accrue from the discipline of the OLTP design for transaction coherence. This is achieved by what are known as the ACID properties of each transaction:

• Atomic:  Results of a transaction are all committed or all rolled back.

• Consistent:  Any shared resource, such as a database, is always transformed from one valid state to the next valid state.

• Isolated:  Until a transaction is complete, its results are invisible to other transactions; that is, no incomplete transaction has side-effects.

• Durable:  All completed transactions are permanent and are not affected by system or media failures.

In most distributed systems capable of ACID transactions, the ACID properties are ensured by the system software, not the application software. OLTP performance is a characteristic of the system server and database management system. Where an IETM is interoperating with other systems or IETMs, OLTP characteristics are a desirable feature.

ACID properties are ensured by a technique known as a "two-phase commit" that ensures that all database updates are synchronized. In a transaction, either all updates are made or none occur.

Two-phase commits are accomplished by the use of a transaction manager program associated with each application program. The application that initiates the transaction is known as the coordinator. The other databases are participants. The coordinator directs the synchronized updates in two phases:

1. The coordinator requests that all participants respond with a status for guaranteed commit. The participants respond with their status.

2. The coordinator sends the commit message if all statuses are affirmative, or aborts if even one is not. All participants confirm the transaction.

DTP is a form of OLTP in which a single transaction can use multiple application programs and access multiple databases across a network. This enables the IETM system to fuse the views of multiple sources of information into a coherent display of information relevant to the maintenance task. It can be advantageous to enable the IETM system to display repair options based on the supply conditions at the depot, the sortie schedule, the current battlefield conditions, etc. With this capability, the IETM can become an intelligent advisor to field units during conditions of high mobility and evolving mission plans. This is the ultimate in cooperative IETM systems and Integrated Data Environments (IDEs).

It is recommended that the integration of OLTP/DTP processes into the document-centric framework for IETMs be achieved where the IETM must interoperate with distributed servers. The availability of current information in a fused view is a strategic advantage to all elements of the battle command and logistical support units.

3.5  IETM Functional Architecture

• Ambiguity:  The SGML-centered specifications in MIL-D-87269 are precise in their prescriptions for the data element contents, but ambiguous with respect to the semantics for handling these elements in an IETM system.

• Obsolescence:  The MIL-M-87268 descriptions for the IETM Graphical User Interface (GUI) were created over five years ago. They do not reflect current common practice in GUI design and implementation.

• Obscurity:  Neither specification realizes a technical architecture that is easily recognized and implemented using the common practice techniques and terminology of current computer client-server technology.

• Time to market:  The emergence of commercial technologies such as those of the World Wide Web and more robust IETM design specifications such as the U.S. Navy MID, demonstrate that unless performance specifications are realized quickly in implementations, they are never implemented widely and are soon replaced as the market moves on. However, the overall functional architecture and technical basis remain stable as do the information content definitions. It is only when these are combined in the same set, as was done for the Tri-Service IETM specifications, that they are, in part or in totality, overcome by events.

While mission-specific IETM applications can be built using the Tri-Service IETM specifications, the interpretation of their intent will be less ambiguous if couched in a functional architecture that is expressed in terms of current client-server technology. This functional architecture will enable IETM acquisitions of commercial and custom technology by comparison of candidates to the functional architecture components.

The functional architecture defines what is typically called a system framework. The framework supports an object-oriented multimedia system. While the use of the object-paradigm to represent content is debatable, the use of it to provide the underlying software framework is not. The object-oriented framework approach to software systems is a known and well-understood technology that can support IETM systems now and for the foreseeable future.

• Each component in the framework has been optimized to do a particular task efficiently yet with a design that enables expansion of its capabilities, as warranted, with a minimal impact on other components in the system.

• Common functionalities are shared throughout the framework. A typical object-oriented framework has a core class library that provides basic services common to all applications built on them. All frameworks provide classes for creating windows, handling keyboard and mouse events, reading and writing files, etc.

An advanced IETM Functional Architecture, based on a framework, is provided in Figure 3.5-1.

The IETM system architecture components are listed below:

• Editors:  content editors for notations used within the IETM system. Content editors may interact directly with the Viewing Framework (e.g., a browser) for creating document instances prior to their registration in the database management system typically for prototyping or creating private objects.

• Viewer Framework:  an IETM display management engine with applications that support display and navigation of notations such as SGML, VRML, and CGM. This can be realized as:
  1. An integrated application in which a single IETM application has the display and rendering software for all of the notations referenced within an IETM, a.k.a., the swiss-army knife application.

      

      

     

      

     Figure 3.5-1  Advanced IETM Functional System Architecture
     

      

  2. A configured application environment in which peer applications known as cooperative applications exchange messages and some data to navigate technical information.

  3. An IETM framework application that calls other applications (helpers or plug-ins) to display and render other notations. These can be called from the IETM framework application but may share common functionality such as network and database access through a management library, or may run independently.

  4. All of the above.

• Network Communications Layer:  a layer for providing interfaces to network applications. This may include proxies for multiple protocol handlers and firewall applications. Note that network layers are not required for all IETM applications. For example, Portable Maintenance Aid (PMA) applications typically run in a standalone mode. However, there are scenarios for PMAs that include the use of a central server that downloads the IETM information to the PMA prior to its use in the field. Therefore, the network interfaces can still be considered fundamental components of IETM systems.

• Database Management System (DBMS):  management software for ensuring consistency of the underlying content type databases. May include security features. Must interact through firewalls. As shown in Figure 3.5-1, the DBMS is an optional feature of an IETM system. While it may be part of the IETM delivery environment, this is an option.

• Hybrid Object/Relational Databases:  database(s) for the internal structures that store content type data. A Hybrid Object/Relational model is shown because it is capable of managing both semantic relationships and non-table objects such as SGML objects, Virtual Reality Modeling Language (VRML) objects, etc. While a database system may be part of the delivery environment, this is an option.

These components are matched for different applications. For example, authoring system support may require many of the same components as a viewing system for distributed hypermedia documents (e.g., a WWW application) given that the authoring system must support concurrent, distributed authoring tasks. The viewer used to deliver the IETM to the end user is also part of the validation tools for authoring, etc. As mentioned above, not all IETM systems use DBMS and database components.

A framework for IETMs is unique only in its focus on IETM functionalities that are not found in other multimedia systems. For example, clocks and timing are fundamental to multimedia class libraries, but interfaces to external test devices are not. Multimedia notation types (bitmaps, video, audio) must be supported by any multimedia class library and hide the details of storing, retrieving, and presenting media to the user. IETMs with a requirement for interoperating with other weapon system components must use standard notations.

This lower-level functionality of the supporting systems (e.g., communications, database management) can be divided into modular object libraries. For example, the protocol handling code for a MIME library might be in a separate dynamically linked library as might the rendering, navigation routines, and caching routines for immediate access to recently retrieved information (such as graphics). Modular function libraries and plug-ins can be useful when, for example, a notation processor such as an intelligent CGM player must perform a common function such as accessing a network through a common protocol (e.g., FTP) to retrieve information. Such combined systems are the defining aspect of framework-centric IETMs.

Common APIs and a standard message library are required to achieve this framework architecture. This should be considered in acquiring an IETM system as it affects the extensibility and maintainability of the system. The creation of a standard for IETM APIs and message libraries is a recommended future task.

3.6  Viewer Architecture

A viewer itself is typically a module in a suite of products. It provides the interactive viewing environment for a variety of information notations and integrates information services into a single presentation environment. It may retrieve documents from a file server (e.g., a database, file system, etc.) in networked and non-networked or standalone configurations. It allows the user to view information in various notations without requiring the user to manually execute separate applications or view the information in separate applications launched by the browsers (i.e., helper applications).

A viewer is a general purpose data object processor. It receives data objects from external sources, transforms the data objects into displayable information, presents the displayable information to the user, and waits for an event to occur. The viewer evaluates the event and requests the next data object to be processed. It repeats this process until a data object is processed that causes the viewer to terminate operation.

• Data Servers request data from external sources and return it for processing.

• Object Handlers process data returned by data servers and transform it into display information (e.g., a notation or protocol handler). Primitive object handlers (e.g., bitmap handlers) support complex object handlers (e.g., SGML object handlers).

• Display Servers manage display resource objects created from display information and provide responses from users.

• Object Routers route information through the viewer.

• Driver Applications initialize components based on information from the operating system and configuration files (e.g., Preferences), and control the flow of information between components.

The object-oriented framework viewer scales very well from standalone to large distributed environments. Each component can be instanced multiple times to distribute the workload of the viewer across many physical resources.

3.7  Communications Architecture

• The application programming interface to the communications layers which support multiple network protocols (e.g., HTTP, FTP, WAIS, etc.), and

• The application programming interface to the database server that may support multiple notations and implementations of the database content (e.g., SGML, CGM, HTML, VRML, etc.).

Figure 3.7-1 illustrates a sample MID IETM Distributed Network Architecture (MID IETM DNA). Note that the general requirements for an IETM browser and an IETM authoring system differ little at this high level because both are applications of distributed client-server technology.

All clients can be servers. For example, a server-to-server interaction is considered a client-server interaction. Client-server systems often require server middleware (e.g., proxies) and a two-phase commit protocol to coordinate transactions that execute on multiple servers. Clients and servers are often threaded using, for example, pipeline architectures to provide for the execution of multiple processes.

Networked client-server applications typically work as follows:

• Client front-end (e.g., IETM browser) sends database interface commands to a database communications engine.

• Database communication engine (API) passes commands over a network to the database engine at the server.

• Database engine on the server processes the request using the network file system to access physical records.

• Database engine passes results back to the database communication engine of the client.

• Client front-end processes data (e.g., display).

Some examples of systems that use client-server architectures are

1. SQL databases:  use declarative language for manipulating data. Need functions to manage the functions that manipulated the data. Stored procedure (named collection of SQL statements and procedural logic) can be invoked using triggers and rules.

2. Transaction Processing Monitors:  manage processes and programs using pieces of code called "transactions." When a transaction ends, all participants agree it closed well. It is a contract that binds a client to one or more servers and defines when a transaction starts, ends, and its units of recovery.

3.8  Scripting Languages

3.8.1  Overview

Traditionally, scripting languages have been metaphor-oriented rather than being fully capable programming languages. Examples such as the Apple HyperTalk language for the HyperCard system use card and stack metaphors with a small amount of if-then-else logic to enable the author to define the scripts that act on the hypertext information. The MIL-D-87269 specification for military IETMs uses a series of node types that include loop-nodes, node-alternatives, if-nodes, etc., to enable the author to define a database of information that can then be sequenced according to the logical conditions specified in the database.

During this decade, alternatives to metaphor-based scripting languages for multimedia have emerged from the computer industry. Some of these have taken the form of fully functional programming languages, most with an object-oriented flavor. Proponents of these languages claim that the metaphorical approach is unduly restrictive and forces the user of these languages to "shoehorn" content into forms that may not be appropriate for the content. Critics of these languages state that they are nothing more than variants of common programming languages such as C++ which force the content provider to become a programmer and the publications organization to retool its skills at great cost.

Little experience with maintaining technical information in this form can be cited to make assessments of the maintenance of such information. In other words, the major criticisms of hypermedia, based on such languages, are their high price and potentially poor life-cycle properties. To date, these criticisms are based on the instincts of the critics, not established facts. Yet the following quote from a text on the Sun Java scripting language is indicative of the design ambitions of supporters of these emerging languages:

The luxury of allowing underlying technologies to take care of everything is not to be for everyone. Someone has to develop the content and application, and deliver them. These jobs fall to the programmers and site administrators who will provide the future that Java promises. (Tim Richey, Java!, New Riders Publishing.)

How this "luxury" will impact existing technical publications organizations who are both subject matter experts and content providers for current logistics efforts has yet to be determined. It seems certain that at least one of the criticisms of these approaches is valid: the cost of providing timely technical information is going up if these approaches are adopted as IETM standards.

3.8.2  Java

• Secure (bytecode verifier, run-time memory layout, file access restrictions);
• Multi-threading;
• Just-in-time compiling;
• Memory management (garbage collecting as separate thread); and
• Array bounds checking.

The Java environment provides

• Class libraries (strings and arrays, utilities (encoding, decoding, hash tables, vectors, stacks), standard I/O and file I/O, browser utilities for HotJava, Another Window Toolkit, network (telnet, ftp, http)), browser environment, stand-alone interpreter, Javac compiler, Unicode encoding.

• Functionality by standalone applications, applets, content, and protocol handlers.

• Package support for grouping classes by relationships (e.g., all graphical objects in same package) that can then be imported into a class that uses them as compiled objects.

• Abstract classes (cannot be initialized; can be created only by subclasses that override the abstract methods with new operators) through interfaces. An interface defines a protocol for the abstract class that allows the same interface to be used for multiple classes with different implementations.

• Exception handling.

Java is an interpreted language that requires a run-time system on every computer on which the applications run. The application can run on any system that has the interpreter. The interpreter can run inside other programs such as a WWW browser or can run standalone. Any Java code is converted by the interpreter to the native machine code. It does not allow the native machine to implement different sizes for fundamental types such as integers or bytes. Java requires the Java Virtual Machine and gets good performance by compiling to an intermediate bytecode representation which is then converted to native machine language.

As of this writing, Java is new, in alpha release, and still buggy. Java includes an I/O Utility, Windowing Toolkit, Networking class libraries, and will include advanced windowing and graphical user interface classes for 2D and 3D graphics including VRML, inter-applet communication, possible ports of compilers for languages that will run on the Java Virtual Machine, and a Java API.

Compared to C++, Java does not support structures, unions, #defines, pointers, multiple inheritance, individual functions, gotos, operator overloading, and automatic type coercion.

Java is delivered by HTTP server within an HTML file, as if it were an inline reference, via the application tag (e.g., <app classpath="">).

3.8.3  Telescript

According to the Telescript literature, "Telescript is to messaging what PostScript is to printing." [WWW] It requires the Telescript Development Kit which is available through a special license from General Magic. Code Warrior Magic is the development environment. It includes a large set of class libraries; cross-platform standards for rich information types, operations performed by classes, constants and symbols, user interface tools, text, graphics, and sound. It also includes support for persistent objects, multiple active packages, operating system kernel for multitasking, and an object-oriented run-time environment (usually supported by C).

Telescript packages are collections of objects/functions. Objects are collected as clusters. A context is a list of clusters. The Telescript tool kit provides interpackage communication and a built-in set of packages.

3.8.4  Dylan

Modules group related classes, methods, and variables. Dylan methods belong to generic functions. A generic function can operate on one or more related classes and can extend across modules. Dylan provides automatic memory management; a syntax, dynamic and static type checking; incremental compilation; and first class functions and classes. Apple provides access to C and C-compatible libraries through extensions. This enables the author to write programs in Dylan and parts of other languages. Because Dylan provides automatic memory management instead of raw memory pointers, Dylan is safer than something like C or C++. This safety decreases depending on the amount of outside code used (i.e., calls to non-Dylan code modules).

Dylan is a complete object-oriented model. Everything is an object, including numbers, strings, functions, and classes. It supports multiple inheritance and polymorphism. A large library of collection types is provided. The creation of constructor and destructor methods is automatic. Type declarations are supported but are optional because values are not storage locations and are strongly typed. This facilitates rapid prototyping. For more efficient compiler-generated code, type declarations can be added which remove the necessity to do run-time checking.

3.8.5  Python

3.8.6  Script-X

The Script-X software development kit is an object-oriented development framework specifically designed for interactive multimedia applications. It provides a tool suite and 250 classes in its library. These tools are primarily programming tools that allow experienced multimedia professionals to create Script-X content. The Script-X language supports multiple inheritance, searching, load management, and network support. The language kit includes extensions for the programming tools, code samples, low level programming tools, and 2,500 pages of documentation in Portable Document Format (PDF). Script-X classes include 2D graphics and user interface libraries.

Script-X programming is interactive and is a pure object-oriented language. It borrows heavily from Dylan and has fewer but clearer symbols than C or C++ (e.g., and instead of &&). It is estimated that Script-X takes about a year to learn and use proficiently. It provides a platform-independent bytecode interpreted form similar to that now offered by Sun Java. It supports multi-threaded processes and exception handling. There is no support for private/public data members and has no interfaces to Visual Basic, Visual C++ or C++. A complete installation of the Script-X environment (code samples, documents, development environment, etc.) requires 160 megabytes of storage. The player requires three megabytes.

3.8.7  Tool Command Language/Tool Kit (TCL/TK)

Communications among applications can be supported using the TCL framework. The TCL designers advocate a two-tier language architecture. The first tier emphasizes ease of learning, ease of programming, and ease of application over performance or support for complex data structures. The second tier is a lower level language such as C, which is used for tasks where performance is a critical characteristic.

The TCL Tool Kit (TK) provides an interface to X11 windowing. The TCL extension provides an easy way to build a graphical interface to an application. TK supports a Motif look and feel. TK provides a way to send TCL scripts to other TK applications for inter-application communication.

3.8.8  Presentation Environment for Multimedia Objects (PREMO)

A strong feature of PREMO is that it provides a basis for interoperability of PREMO-conforming systems through a foundation class of objects that all PREMO applications must implement. PREMO foundation objects provide the fundamental services used by the other system components; as such, PREMO is essentially a framework specification.

The PREMO foundation classes may be subclassed to meet specific requirements. PREMO foundation class objects include the following:

• PREMOObject:  As is common practice in commercial object implementations, an abstract object, PREMOObject, is the root type for all subclasses. While it is an abstract object and therefore, non-instantiable, it encapsulates the fundamental operations or methods that are inherited by all other classes (mainly, create and destroy objects, and send and return a data value on the object type such as class sequence or the type graph). This can support life-cycle operations such as automatic garbage collection, memory management, and behavior optimization.

• Enhanced Data Objects:  A set of fundamental data objects is defined to be used to create specialized subtypes for multimedia. Examples are geometric data, color, matrices, etc., and their related operations. The fundamental operations enable data values to be set and returned.

• Controller Objects:  A set of objects is defined to control communications and coordinate cooperation among objects to accomplish a task. A hierarchy of controller objects may be defined. One example of the use of a controller object is a synchronizer using a Finite State Machine (FSM). A controller object typically registers with an event handler object.

• Event Handler Object:  A set of objects is defined that manages events for other objects. These operations include event registry, de-registry, and dispatching. An operation to dispatch an event is invoked on the event handler by the event source. The event is then propagated to all objects that have registered an interest in the event. Registry includes the event name and optionally a constraint list of key-value pairs that can be used to make a TRUE/FALSE evaluation of the need to notify a registered client.

• Producer and Porter Objects:  Producers are a set of objects for processing, producing, or transforming data. These objects may receive data and propagate data. They may be subclassed to specialize the data handling operations. Porter Object types enable interconnections to external systems and environments (e.g., input/output objects). Porter objects might be used, for example, to interface to a database, a frame grabber, a microphone, etc. A porter object might be the interface to an event handler for mouse input. Porter objects are virtual device interfaces. Producer and porter objects can be interconnected to form a task network such as is needed for a rendering pipeline.

• Aggregate Objects:  A set of objects is defined for managing aggregate lists, sets, graphs, and tables. This includes the operations of insert, delete, and replace entries. Dispatching operations to aggregate members are included. Such sets can be used to model hierarchical aggregations (e.g., trees, graphs, etc.).

3.8.9  IMPAX

IMPAX provides an architecture and models for creating an IETM viewer based on the use of a coordinate system of tiles for placing object primitives such as text, graphics, buttons, etc., while leaving the data files in their native formats. The IMPAX architecture includes associations of screen objects to precise display positions with the semantics of operation explicitly determined by the IMPAX associations. IMPAX displays are organized around the frame or page metaphor but are intended to be independent of the authoring tools used to create the data objects. The IMPAX literature states that IMPAX allows for standardizing the definition of non-authored user actions in the IETMs regardless of implementation.

In the IMPAX architecture, the data source may be a computer-aided publishing system whose output is routed to a pre-processor which then outputs an IMPAX file. This file is then passed to post-processors for each display type, for example, a laser printer, photo composition, or electronic display. An IMPAX Documentation Object is an exchange and storage unit composed of the information content in native formats (e.g., SGML, CGM, etc.) and

• A presentation document describing the presentation rules of each document entity;
• An access document containing the links between document entities; and
• A service document which describes display attributes such as fonts and colors.

Frame entities provide the partitioning of the logical document and its association to the display as boxes of content. Function entities are used to associate content to interactive operations. The passive function entities are text and illustration entities. The active function entities are data input and selection entities (i.e., widgets and dialogs). Hyperlinks are defined as data elements that represent relationships among entities (e.g., source and target).

3.8.10  Virtual Reality Modeling Language (VRML)

VRML 2.0 proposals are to be delivered in February 1996. These proposals will include the mechanisms necessary to create fully-interactive 3D networked graphics, that is, graphics with behaviors, animation support, support for multiparticipant worlds, etc. VRML proposals are expected from Silicon Graphics, Microsoft, Sony, Apple, and several other vendors of 3D systems. While VRML is considered experimental at the time of the writing of this report, work on it is progressing rapidly, and the significant interest of major computer systems vendors ensures that products to support VRML will be available.

The potential application of VRML to IETMs is promising. VRML can enable a compact 3D model of the weapon system to exist as a resource for the IETM user. This enables not only fixed views of the item under repair to be displayed, but movable views with varying degrees of simulation fidelity. By employing associative constraint techniques used in computer-aided design (CAD) systems, manipulations of the graphical model can aid in the test and repair procedure. That is, VRML is both a display language and a user interface. Combined with database operations anticipated for the higher classes of IETMs, this can provide a very powerful system.

This suggests that the VRML model may be highly advantageous for higher classes of IETMs (i.e., classes four and five), particularly where the model intelligence is available from the CAD system itself (as in collaborative design environments). Because such integration is a goal of both CALS and the PDES/Standard for thr Exchange of Product Model Data (STEP) initiatives, the application of VRML may solve problems foreseen in choosing a neutral 3D graphics format among the many existing contenders. Free translators to the VRML format from existing CAD formats such as Autocad's Drawing Exchange Format (DXF) already exist.

VRML also may be applicable to multi-participant simulations such as are needed in distributed training applications. It is already being applied to visualization applications for analyzing very large databases and can be applied to remote sensing applications. It is strongly suggested that investigations into these possibilities be conducted within DoD and its contractors.

Two issues exist with the application of VRML to IETMs:

1. The format relies on WWW addressing techniques. However, unless application-specific information (e.g., Netscape frame targets) are added to the language, this is a HyTime conforming link type (notclink). Where VRML was not designed for IETM applications, no significant technical issues prevent it from being applied as there is a provision in the standard for extension nodes to handle special application needs.

2. The VRML standards process is not provenanced by an accredited standards organization. It is maintained by a voluntary and self-appointed VRML Architecture Group and an Internet mail list. This community has proven to be remarkably effective at setting design goals and achieving them. It is probable that after the VRML 2.0 specification is released, a VRML consortium will be formed that can administer the standard.

3.8.11  MHEG

MHEG represents objects in a non-revisable form, and is unsuitable as an input format for hypermedia authoring applications. It is an output format for such tools. MHEG is not a multimedia document processing format. Instead, it provides rules for the structure of multimedia objects which permits the objects to be represented in a convenient form (e.g., video objects could be MPEG-encoded). It uses Abstract Syntax Notation 1 (ASN.1) as a base syntax to represent object structure, but allows for the use of other syntax notations. An SGML syntax is also specified.

MHEG objects (which may be textual information, graphics, video, audio, etc.) may be of four types:

1. Input object (a user control such as a button or menu);
2. Output object (graphics, audio visual display, text);
3. Interactive object (a "composite" object containing both input and output objects); and
4. Hyperobject (a "composite" object containing both input and output objects, with links between them).

MHEG supports various synchronization modes for presenting output objects in these relationships.

3.9  Aquidneck Management Associates/SoftQuad IETM Viewer

The statement of work for this project states the function of this viewer to be a generic, native-SGML IETM viewer that conforms to the requirements specified in MIL-M-87268 and MIL-D-87269. It is targeted to support a subset of the functionality defined therein with the precise subset to be determined by the contracting parties (AMA and SoftQuad). The viewer is to operate on an American Standard Code for Information Interchange (ASCII) instance that conforms to the agreed-upon subset of MIL-D-87269 and is to be extensible to client-server database architectures in the future. No provision is made for the authoring or other preparation of the test data.

While the requirements for this package are known to the authors of this report, the only information about the accomplishment of the task is anecdotal based on private conversations with members of the SoftQuad development staff. No definitive technical analysis has been made available.

      

4.1  Internet MID Processing and Retrieval Tool (IMPART)

4.1.1  IMPART Design

4.1.1.1  Design Decisions

• Demonstrate the passing and processing of MID instance data over the Internet by integrating the capabilities of a MID viewer and an HTML browser.
• Demonstrate MID processing on at least two dissimilar platforms.

Within IMPART, two principal design decisions were made that affect all other aspects of the system. The first design decision concerned the methodology by which MID instances would be passed and presented over the Internet. The second decision regarded the version of the MID that was used.

At the outset of the project, consideration was given to two primary methods for passing and presenting MID information over the Internet. The first method was to obtain the source code corresponding to an HTML browser and modify it so that it could process and present not only data encoded in accordance with HTML but also data encoded in accordance with the MID. The second method was to create a Common Gateway Interface (CGI) program that could process MID instances and dynamically encapsulate, within HTML tags, all data to be presented for viewing with common WWW HTML browsers.

CGI is a standard for running external programs under HyperText Transport Protocol (HTTP) servers that make up much of the WWW. CGI enables the creation of programs that can interpret information requests and then return documents, or dynamically generated documents, on the fly. With CGI, an HTTP server can provide information that is not in a form readable by a remote client (such as an SQL database, an IETM database, or even a MID instance), and act as a gateway between the two to produce information that is accessible to all clients. CGI is currently used for such things as interfacing with Wide Area Information Server (WAIS) databases, Archie databases, and also for allowing user feedback through HTML forms.

The CGI method was chosen because it could satisfy the system requirements with substantially less software development. In addition, with the CGI method, MID instance data can be "processed" and presented with any computer platform that has an HTML browser, supports the execution of a CGI script, and is connected to the Internet. At this time, such HTML browsers (e.g., Netscape and Mosaic) exist for all major computer platforms, thus, more than satisfying the second requirement listed above (demonstration on two dissimilar platforms).

The second main design decision, as listed above, regarded the version of the MID that was used. As described earlier in this document, there are two flavors of MID: MID-I and MID-II. After coordination with the Carderock Division, Naval Surface Warfare Center (CDNSWC) and NAWCAD, it was decided, due to its stability, that the original MID specification [1], hence MID-I, would be used for IMPART.

A third design decision regarded user access. The CGI method results in a client-server architecture for MID processing and presentation. All MID processing takes place on the server, whereas the resultant presentation takes place on the client. (Note that a single computer can function as both a client and the server, or the client and server could be separate machines connected via a network.) Given this client-server architecture, it was decided that IMPART would be designed such that the server machine could simultaneously process MID instances requested by multiple clients.

4.1.1.2  IMPART Architecture

4.1.1.3  CGI Program Design

First, IMPART reads the operational parameters file config.cgi, which must be located in the HTTP server's home directory (i.e., c:\httpd). This file contains the MID file path, image URL path, image file path, audio URL path, audio file path, video URL path, and video file path. A sample operational parameters file is shown below.

MID_PATH=C:\HTTPD\CGI-WIN
IMAGE_URL=IMAGES/
IMAGE_PATH=C:\HTTPD\HTDOCS\IMAGES
AUDIO_URL=AUDIO/
AUDIO_PATH=C:\HTTPD\HTDOCS\AUDIO
VIDEO_URL=VIDEO/
VIDEO_PATH=C:\HTTPD\HTDOCS\VIDEO

The value associated with MID_PATH may be any valid file path. The URL paths are relative paths below the C:\HTDOCS directory. Note that the Windows HTTPD server requires CGI scripts to be stored in or below C:\HTTPD\CGI-WIN and all other hypertext documents, images, sounds, etc., to be stored in or below C:\HTDOCS.

Next, IMPART determines the URL for itself by obtaining the IP address and executable path of the client that has invoked it. After learning the client's IP address, the software is able to develop a name for the binary data file, where information will be stored between successive script executions. To permit multiple clients to run the script simultaneously, the name of the binary data file is derived from the client's IP address.

IMPART now ascertains which CGI request method (GET or POST) was used. If the script is invoked with the GET method, and the CGI query string is null, then it is the initial execution for the client. At this point, the initial form is sent to the HTTP server, which permits the client to select a MID file in which to process. Then, the binary data file is created, all allocated memory is freed, and the script terminates. If the script is invoked with the GET method, and the CGI query string contains data, then the script was executed via a text hotspot. In this case, IMPART reads and deletes the binary data file, MID execution continues, a new binary data file is created, all allocated memory is freed, and the script terminates. If the script is started with the POST method, the binary data file is read and deleted; then IMPART proceeds to check if any input data was returned from the HTTP server. If the name of the MID file was returned from the HTTP server, the software reads, parses, and stores the MID data. Next, MID execution begins, a new binary data file is created, all allocated memory is freed, and the script terminates. If the name of the MID file was not returned from the HTTP server, the software continues executing the MID, creates a new binary data file, and the script terminates.

The binary data file discussed earlier is necessary for IMPART to retain certain information between successive runs. Various global variables and data stacks are read and written with each invocation and termination of IMPART.

When MID execution begins or continues, one infoContainer at a time is processed and sent to the HTTP server. Each time a new MID script element is encountered, the current script and its statement counter are pushed onto stacks, and the new script takes the place of the current script. A statement counter is used in conjunction with each script to keep track of the next statement in which to execute. After IMPART finishes processing the current script, it is discarded, and another script and statement counter are popped off of the stacks. This process continues until no script statements remain. At last, after the software finishes processing a MID file, the HTTP server receives a final HTML page that contains a button to restart the script, giving the user the opportunity to process another MID file.

There are 169 procedures and functions that comprise the IMPART software. The following table lists the procedure or function name, the name of the file, and a short description for each.

4.1.1.4  MID to CGI/HTML Mapping

4.1.2  IMPART Operation

4.2  View Package Selection

To add some degree of realism to the demonstration, it was decided that the view package data would be extracted from existing validated, verified, and accepted paper and/or electronic technical manuals. In addition, because IMPART is a demonstration system for use on the Internet, it was also decided that the IETM view package data would be selected from a source that was either available from publicly accessible sources or is explicitly marked as being approved for public release with unlimited distribution. Finding data that met these requirements was not difficult because of present and previous work on legacy conversion of TM/ETM data to IETM data (we have collected, and have access to, hundreds of technical manuals and technical manual data in many different formats (i.e., work packages, troubleshooting manuals, etc.) and for all single and combinations of maintenance levels (i.e., Organizational/Unit, Intermediate, and Depot)).

1. Aviation Unit and Intermediate Maintenance Manual, Technical Manual, Army OH-58D Helicopter, TM 55-1520-248-23-1, January 12, 1988.

2. Direct Support and General Support Maintenance Repair Parts and Special Tools List (Including Depot Maintenance Repair Parts and Special Tools) For Electronic Equipment Configuration Army Models: UH-1D (NSN 1520-00-859-2670), UH-1H (NSN 1520-00-087-7637), UH-1V (NSN 1520-01-043-4949), and EH-1X (Aircraft) (NSN 1520-01-042-9396) Helicopters, TM 11-1520-210-20P, May 17, 1985.

The unit maintenance manual contains maintenance tasks and descriptive information. The Repair Parts and Special Tools List (RPSTL) contains part information. In the unit maintenance manual, the OH-58D helicopter is divided into 11 primary systems where each is located in a separate chapter. Subsystems and tasks are sections within these chapters. For the demonstration, the following items (from the unit maintenance manual) were converted to a MID SGML instance:

Principles of Operation

Servicing

• Defuel helicopter with valve (a task);
• Defuel with truck (a task); and
• Drain/service engine oil system (a task).

Ground Handling, Jacking, Mooring, Hoisting, and Sling Loading

• Install helicopter covers (a task) and
• Install/Remove rotor tiedowns (a task).

Airframe

Fuselage (a subsystem)

• Remove/Install window in access door (a task);
• Remove/Install access door (a task);
• Clean, inspect, and repair engine cowl assembly (a task); and
• Isolation of water leaks (a task).

Tailboom (a subsystem)

• Clean and inspect tailboom attach bolts (a task);
• Repair touch up fin (a task); and
• Clean, inspect, and repair taillight support (a task).

Pylon (a subsystem)

• Clean and inspect pylon (a task);
• Clean and inspect corner mount (a task); and
• Clean, inspect, and repair mount bolt (a task).

Additionally, two parts tables, with their accompanying graphics, were selected from the RPSTL and placed within the same MID SGML instance. Conversion of all of these items was accomplished using an image scanner, a commercial Optical Character Recognition (OCR) package (OmniPage Pro), and a text editor. An example fault isolation scenario was also created and placed within Servicing.

4.3  Demonstration Results

IMPART is started by entering its HTTP address. In this case, the address is http://198.77.5.136/cgi-win/cgiutil.exe. IMPART obtains the path to MID files by checking MID_PATH in the operational parameters file config.cgi. The filenames of all MID files found in this directory are presented to the user. In this case, DEMO1.MID and DEMO2.MID are available for processing. Note that in this demonstration, the only difference between DEMO1.MID and DEMO2.MID is that DEMO2.MID does not contain a video clip. When viewing this screen, the user selects the MID file that is to be presented and then clicks CONTINUE.

This is the title screen for the DEMO1.MID file that was selected in the previous step. After viewing this screen, the user selects NEXT.

4.3.1  Descriptive Information

Descriptive information is the first of four types of information that is encoded in the MID file.

4.3.2  Task Information

4.3.2.1  Task Selection

4.3.2.2  Task Execution

Upon entering a task, the user is first presented with inputs required for the task, is notified of any applicable warnings, cautions, or notes, and then is presented with the task steps. In this case, the user has selected the task titled: Drain/service oil engine system. After selection, the user clicks NEXT.

4.3.3  Parts Information

4.3.4  Fault Information

4.4  IETM Specification Compliance Issues

In terms of MIL-M-87268, the requirements that are virtually impossible to meet without creating a custom browser (as opposed to using a COTS WWW browser) are those that fall within the section on "General display formats for IETMs," paragraph 3.5.1. It is possible to satisfy the requirements governing "Window layout templates for data panes," paragraph 3.5.1.1, using the frame elements in Netscape's extensions to HTML. Additionally, requirements that govern the level of detail provided with graphics (i.e., 3.3.5.3, 3.3.5.5, and 3.3.5.15) are difficult to meet without using separate graphics files for every desired level of detail. There is a new product by InterCAP Graphics Systems (a subsidiary of Intergraph Corporation), however, that may provide a way to meet such requirements in a much more elegant fashion. The product is called InterCAP Inline and operates as a plug-in to Netscape Navigator®2.0 and supports inline viewing, zooming, dynamic panning and magnification, and animation of intelligent, hyperlinked Computer Graphics Metafile (CGM) vector graphics within the Navigator 2.0 Web browser. Given its recent release, we have not had time to evaluate this product for use in this demonstration.

In terms of MIL-D-87269, it was decided that a reasonable demonstration of IMPART could be created by structuring the MID file with the TM data to correspond to the major information types in the content-specific layer for Organizational-level maintenance. In particular, the demonstration MID file for the OH-58D helicopter was designed in accordance with an OH-58D system hierarchy that may contain the following information at any level in the hierarchy:

• Tasks
  1. Inputs

     Reference Material

     Text, Hotspots

     Personnel Required

     Text, Hotspots

     Equipment

     Text, Graphics, Hotspots

     etc.

  2. Steps

  Text, Graphics, Audio, Video
  Dialogs
  Hotspots
  Alerts: Warnings, Cautions, Notes

• Descriptive Info

  Text, Graphics, Audio, Video
  Hotspots

• Fault Info

  Text, Graphics, Audio, Video
  Dialogs
  Hotspots

• Parts Info

  Text, Graphics
  Hotspots

  
  

The demonstration files are all constructed such that all textual data that is presented is contained within the MID file (i.e., a Hard MID as opposed to a Soft or Semi-soft MID). For this demonstration, the features within MID that allow for the construction of MID instances that reference external data (with the exception of standard references to graphics, audio, and video) were not implemented. Regardless of where the data actually resides, the result would appear the same on the WWW client. Implementation of the external referencing features is certainly possible by adding the appropriate functions to the CGI program.

      

The first general recommendation for improving the MID concerns MID ownership. As the MID emerges from the research environment, the U.S. Navy should identify an organization (e.g., either CDNSWC or NAWCAD) that will be officially responsible for supporting, maintaining, and promulgating the MID. The lack of a single responsible organization, coupled with the fact that the MID is not a formal specification or standard under the control of a chartered preparing activity, makes the future of the MID appear uncertain to potential implementors. An uncertain future could discourage its use.

The second general recommendation for improving the MID concerns its role. The role that the MID can or should play with other DoD TM/ETM/IETM specifications and standards in an IETM implementation must be clarified. At this time there are at least two other different IETM-related specifications and standards within the DoD that are emerging just as the MID is emerging. These are MIL-STD-2361 and the Presentation Specification (PS) coming out in the newest revision of MIL-PRF-28001. Having these different standards and specifications in addition to the DoD IETM specifications, which are undergoing conversion to performance specifications, can present a confusing picture to potential industry and government implementors. Presenting such a confusing picture is likely to further discourage vendors from developing products against any of these approaches.

5.1  Clarifications

1. Explicit specification and examples for linking and location of regions in external sources are needed. For example, what is the convention for linking to "hotzones" in graphics? ISO 10744 - HyTime provides several options including finite coordinate spaces and notation context links.

2. What are valid linkends of relationships? That is, what things may reasonably be linked with what other things? ISO 10744 - HyTime provides a reference type (reftype) attribute that was removed in the second phase of MID development. This or another solution may be needed.

3. What are the conventions (e.g., scoping rules for variable names and values) for external linking into other active hypermedia types such as another MID instance?

4. More precise rendering conventions are needed. For example, what is the MID viewer expected to do if an object on screen is related to a zone in a graphic in an unrendered infoContainer? How much of the container is the MID player expected to render? What if the zone is inside of a different MID?

5. What security conventions should be enforced by MID viewers and how are these indicated in the MID language? A security element type based on the ISO 10744 - HyTime Activity architectural form is in the current MID specification, but it has not been implemented or investigated.

6. While interest in network-enabled viewing systems is high, the requirements for IETM systems that support network interactions are undetermined. However, the application of network protocol handlers severely impacts the performance of a hypermedia viewing system and the platform on which it is hosted. An effort to add network protocol handlers to MID systems should be predicated on the determination of mission requirements and the projected network environment (e.g., Internet vs. Intelink) given the primary mission of MID as a component of IETM systems. This is a fundamental issue for all DoD hypermedia systems.

5.2  Technical Recommendations

1. Develop a specification for a MID system. This should include both authoring and viewer specifications. See "Technical Recommendations - Metafile Interactive Documents (MID II)" Loral Defense Systems - East, under Contract #3812-007 to ManTech Services Corporation, POC Nancie Lumpkins.

2. The MID system specification should be positioned within a standard hypermedia architectural framework created for IETMs, or better, under an existing effort such as PREMO. This does not require harmonization, but will require an explanation of how the current MID prototype systems relate to standards such as PREMO. Implementation of MID systems is not required to adhere to any particular design, but meeting the requirements for interoperability among IETM systems will require guidance such as can be provided by citing existing work such as PREMO. Where MID can be shown as a cooperating component for such systems, acquisition of MID-capable systems will be easier because the critical issues for MID system implementation can be clarified (e.g., the Application Programming Interface).

3. As part of the MID system specification, determine the support necessary for MID language memory management and security features. These should include automated garbage collection, transport-safe features with environment constraints to ensure that a MID instance cannot be used to create deleterious side effects (e.g., viruses).

4. Standard sets of relationship element types should be derived for application profiles of MID for publications domains such as training and simulation. Requirements for these may be derived by interaction with the domain subject matter experts and extant specifications such as those of the Distributed Interactive Simulation (DIS) community. Others should include emerging public domain languages such as the Virtual Reality Modeling Language (VRML). VRML is also an opportunity to investigate the requirements for interoperability without control of the target Application Programming Interface (API), which is the case for use of proprietary COTS systems (e.g., Netscape).

5. The original MID specification cited HyQ as a document query language. Recently, HyQ has been replaced by SGML Document Query Language (SDQL), which is part of the DSSSL standard. Two efforts should be funded together or separately. The first is an investigation of the requirements to support DSSSL (DSSSL On-line) in MID and SDQL. The second is an investigation of the requirements to support a standard alternative such as SQL3.

6. Rendering stylesheet conventions for MID should be developed. If these can be based on the DSSSL standard, this is the best option. If not, a MID stylesheet specification should be created based on best practices. Extensibility of the stylesheet metaphor to handle properties other than rendering may be considered as part of this effort. A commercial example of such systems includes Microsoft Visual Basic.

7. Recommendations from the MID Design Team should be solicited on the desirability and feasibility of developing a MID bytecode representation.

8. Other examples of MID applications should be developed. A primary candidate is a MID application for use with the US Army MIL-STD-2361 document type definitions.

9. As part of the MID system specification, an effort to develop MID production scenarios is warranted. These would enable an acquisition or project manager to determine the tools and skill mixes required for using a MID system for IETM and other on-line document production.

10. As prototype MID system components become available (MID Viewer, Authoring, Conversion and Document Management Utilities), user testing should commence for selected projects with different profiles. These should include new projects, projects with legacy data, projects with different skill mixes, and projects with fielded weapon systems. Prior harmonization of MID with other standards and specifications is not a requirement for implementing this recommendation, as the MID language is reasonably complete, and such harmonization efforts will only slow the insertion of MID technology and its adoption by the target user communities.

11. Initial notation support for the MID should be developed as part of a U.S. Navy effort to determine which standard and commercial graphics and other media notations best fit the U.S. Navy Concept of Operations (CONOPS) for IETMs. This will affect the standardization of MID link and location models and the development of MID application profiles and system production scenarios.

      

[2]  "The Metafile for Interactive Documents (MID), A Data Structure for Interoperability Between Dissimilar IETM Databases and IETM Presentation Systems," by Eric L. Jorgensen, Carderock Division Naval Surface Warfare Center, CDNSWC/TM-18-94/10, March 1994.

[3]  "Midscript: An SGML/HyTime Scripting Language," by Neill Kipp, HyTime Conference 1994.

[4]  "Document Interchange Support for Intelink," Defense Information Systems Agency, Center for Standards, December 7, 1995.

APPENDIX A:  TECHNICAL COMPARISON MATRICES

      

Is there any conformance to MIL-M-87268?

February 7, 1996

A.2  MIL-D-87269 Compliance

Is there any conformance to MIL-D-87269?

February 7, 1996

A.3  Commercially Available Language

Does the Approach use a language that has publicly available parsers/compilers?

February 7, 1996

A.4  Coupling of Presentation and Authoring

Insert a number into the answer_field from 1-10 (where 10 is the most) that indicates the connectivity of the presentation to the authoring system. Discuss any other pertinent information on this subject within the description.

February 7, 1996

A.5  Export Facilities

With the Approach, what can be exported? (executable, data or both)

February 7, 1996

A.6  Import Facilities

What can be imported into the Approach? (executable, data or both)

February 7, 1996

A.7  Integration

Determine a number from 1-10 (where 10 is the most) that indicates the amount of effort needed to integrate the approach into common operating environments.

February 7, 1996

A.8  Level of Interoperability

What is the level of interoperability? Choose a number from 1-10 (where 10 is the best) that best indicates the amount of effort required to provide interoperability between dissimilar systems.

February 8, 1996

A.9  Knowledge Required by Authors

What is the level of knowledge required for authors? Enter a number from 1-10 (where 10 is most complex) that represents complexity of knowledge required by authors. Elaborate on any specific knowledge needed by the author within the description.

February 8, 1996

A.10  Language or Software

Is the language or software used represented by a language specification or by executable software?

February 8, 1996

A.11  Military Implementations

List the military agencies who are implementing the Approach.

February 8, 1996

A.12  Non DOD Implementations

List the Non-DOD agencies who are implementing the Approach.

February 8, 1996

A.13  Notation Support

Is there a capability for support of other notations, such as video, graphics, audio, etc.?

February 8, 1996

A.14  Other Vendor Implementation

List the major vendors who are implementing the Approach.

February 8, 1996

A.15  Portable Language

Is the language used standardized with commonly available parsers/compilers, so that a product can be moved from one application to another?

February 8, 1996

A.16  Presentation or Data

Does the product deal with data, or presentation of the data, or both?

February 8, 1996

A.17  Problem To Be Solved

What is the problem the Approach is trying to solve in terms of architecture?

February 8, 1996

A.18  Public Libraries

Does the Approach provide for the use of publicly available libraries?

February 8, 1996

A.19  Requirements

What are the Requirements in terms of the Architecture?

February 8, 1996

A.20  Scripting Language

Is scripting part of the Approach?

February 8, 1996

A.21  Specification Status

List the current status, if any, of the specification within ANSI/ISO/ISG that the approach is trying to standardize.

February 8, 1996

A.22  Stylesheet

Does the Approach use a Stylesheet? If so, is the stylesheet imbedded or implied?

February 8, 1996

A.23  Support for Plug-ins

Does support exist for multiple protocols?

February 8, 1996

APPENDIX B:  MID DEMONSTRATION FILE

      

9 2 9
11 2 UNUSED
13 1 13
14 18 UNUSED
32 95 32
127 1 UNUSED

160 5 32
165 1 UNUSED
166 88 38
254 1 127
255 1 UNUSED

American Standard Code for
Information Interchange (ASCII)//ESC 2/8 4/2"

RS 10
SPACE 32
TAB SEPCHAR 9

UCNMSTRT ""
LCNMCHAR "-."
UCNMCHAR "-."
NAMECASE GENERAL YES

ENTITY NO

SHORTREF NONE

NAMELEN 32
ATTCNT 80

OTHER CONCUR NO SUBDOC NO FORMAL YES

APPINFO "HyTime"
>
<?HyTime VERSION "ISO/IEC 10744:1992" HYQCNT=32>
<?HyTime MODULE base exidrefs>
<?HyTime MODULE measure>
<?HyTime MODULE locs anydtd coordloc HyQ multloc query relloc>
<?HyTime MODULE links manyanch>

<!--

DOC NAME: demo1.mid
PROJECT: OSD CALS/IDE Task 5 - MID Demonstrations
AUTHOR: Christopher Ables
DATE: March 13, 1996
DESCRIPTION: MID file used for the Internet MID demonstration

-->
<!DOCTYPE mid SYSTEM "mid.dtd" [

<!NOTATION midnot SYSTEM >
<!ENTITY GR0000 SYSTEM "GR0000.JPG" NDATA bitmap>
<!ENTITY GR1010 SYSTEM "GR1010.JPG" NDATA bitmap>
<!ENTITY GR1011 SYSTEM "GR1011.JPG" NDATA bitmap>
<!ENTITY GR1012 SYSTEM "GR1012.JPG" NDATA bitmap>
<!ENTITY GR1045 SYSTEM "GR1045.JPG" NDATA bitmap>
<!ENTITY GR1047 SYSTEM "GR1047.JPG" NDATA bitmap>
<!ENTITY GR1051 SYSTEM "GR1051.JPG" NDATA bitmap>
<!ENTITY GR1052 SYSTEM "GR1052.JPG" NDATA bitmap>
<!ENTITY GR1089 SYSTEM "GR1089.JPG" NDATA bitmap>
<!ENTITY GR1093 SYSTEM "GR1093.JPG" NDATA bitmap>
<!ENTITY GR2009 SYSTEM "GR2009.JPG" NDATA bitmap>
<!ENTITY GR2010 SYSTEM "GR2010.JPG" NDATA bitmap>
<!ENTITY GR2011 SYSTEM "GR2011.JPG" NDATA bitmap>
<!ENTITY GR2024 SYSTEM "GR2024.JPG" NDATA bitmap>
<!ENTITY GR2061 SYSTEM "GR2061.JPG" NDATA bitmap>
<!ENTITY GR2062 SYSTEM "GR2062.JPG" NDATA bitmap>
<!ENTITY GR2210 SYSTEM "GR2210.JPG" NDATA bitmap>
<!ENTITY GR2276 SYSTEM "GR2276.JPG" NDATA bitmap>
<!ENTITY GR2282 SYSTEM "GR2282.JPG" NDATA bitmap>
<!ENTITY GR2299 SYSTEM "GR2299.JPG" NDATA bitmap>
<!ENTITY GR2309 SYSTEM "GR2309.JPG" NDATA bitmap>
<!ENTITY GR21845 SYSTEM "GR21845.JPG" NDATA bitmap>
<!ENTITY GR21846 SYSTEM "GR21846.JPG" NDATA bitmap>
<!ENTITY GR_FIG5A SYSTEM "GR_FIG5A.JPG" NDATA bitmap>
<!ENTITY GR_FIG5B SYSTEM "GR_FIG5B.JPG" NDATA bitmap>
<!ENTITY GR_FIG6A SYSTEM "GR_FIG6A.JPG" NDATA bitmap>
<!ENTITY GR_FIG6B SYSTEM "GR_FIG6B.JPG" NDATA bitmap>
<!ENTITY VIDEO1 SYSTEM "APACHE.AVI" NDATA video>
]>

<mid>

<script><statements>
<gosub target=I00>
</statements></script>

<infoContainer id=I00>
<titlebar>Army OH-58D Helicopter</titlebar>
<clientarea><pane><text>
Army Model OH-58D Helicopter

Technical Manual
TM 55-1520-248-23-1

Aviation Unit and Intermediate Maintenance Manual</text></pane>
<pane><graphic><graphicPrimitive source=GR0000></graphic></pane>
<pane><text>
Headquarters, Department of the Army
12 January 1988

Approved for public release; distribution is unlimited.</text></pane>
<footerbar><button next>
<script><statements><gosub target=I01></statements></script>
</footerbar></clientarea></infoContainer>

<infoContainer id=I01>
<vardecl><type>String<name>Choice1</vardecl>
<titlebar>Army OH-58D Helicopter</titlebar>
<clientarea><pane><text>
Aviation Unit and Intermediate Maintenance Manual
Technical Manual
Army OH-58D Helicopter
TM 55-1520-248-23-1
</text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice1
<case><expression><constant>Tasks
<statements><goto target=I02><break></statements></case>
<case><expression><constant>DescInfo
<statements><gosub target=I03><gosub target=I17><gosub target=I21><gosub target=I22>
<gosub target=I23><gosub target=I24><gosub target=I25><gosub target=I26><break>
</statements></case>
<case><expression><constant>FaultInfo
<statements><goto target=I02><break></statements></case>
<case><expression><constant>PartsInfo
<statements><goto target=I02><break></statements></case>
<case><expression><constant>Subsystems
<statements><goto target=I06><break></statements></case></switch></statements>
</script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice1</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Tasks</label><script><statements>
<expression><assign><variable><name>TempChoice1<expression><constant>Tasks
</assign></statements></script></button>
<button><label>Descriptive Info</label><script><statements>
<expression><assign><variable><name>TempChoice1<expression><constant>DescInfo
</assign></statements></script></button>
<button><label>Fault Info</label><script><statements>
<expression><assign><variable><name>TempChoice1<expression><constant>FaultInfo
</assign></statements></script></button>
<button><label>Parts Info</label><script><statements>
<expression><assign><variable><name>TempChoice1<expression><constant>PartsInfo
</assign></statements></script></button>
<button><label>Subsystems</label><script><statements>
<expression><assign><variable><name>TempChoice1<expression><constant>Subsystems
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice1<expression><variable><name>TempChoice1
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I02>
<titlebar>Demonstration MID File</titlebar>
<clientarea><pane><text>
DEMONSTRATION MID FILE ONLY

The selection you have chosen is not available in the current MID file.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I03>
<titlebar>Army OH-58D Helicopter Descriptive Info</titlebar>
<clientarea><pane><text>
The OH-58D helicopter is a fully integrated surveillance/target
acquisition/designation system with sufficient power margin to
provide agility and total maneuverability in the nap-of-the-earth
environment.
Its mast mounted sight and other integrated electronics and
instrumentation provide standoff acquisition and recognition of
targets during day or night operations in all types of weather,
with reduced crew workload under combat conditions.</text></pane>
<pane><video><script><statements><gosub target=video1></statements></script></video></pane>
<pane><graphic><graphicPrimitive source=GR1010></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I04>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
Applicable Configurations:
All</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next><script><statements>
<gosub target=I114><gosub target=I115><gosub target=I82>
<gosub target=I116><gosub target=I117><gosub target=I118>
<gosub target=I119><gosub target=I120><gosub target=I121>
<gosub target=I122><gosub target=I123><gosub target=I124>
<gosub target=I125><gosub target=I126><gosub target=I127>
<gosub target=I128><gosub target=I129><gosub target=I130>
<gosub target=I131><gosub target=I132><gosub target=I133>
<gosub target=I134><gosub target=I135><gosub target=I136>
<gosub target=I137>
</statements></script></footerbar></clientarea></infoContainer>

<infoContainer id=I06>
<vardecl><type>String<name>Choice2</vardecl>
<titlebar>Army OH-58D Helicopter Subsystems</titlebar>
<clientarea><pane><text>Army OH-58D Helicopter Subsystems</text></pane>
<footerbar><button next>
<script><statements><switch><expression><variable><name>Choice2
<case><expression><constant>Service
<statements><goto target=I07><break></statements></case>
<case><expression><constant>Ground
<statements><goto target=I08><break></statements></case>
<case><expression><constant>Airframe
<statements><goto target=I09><break></statements></case>
<case><expression><constant>Alighting
<statements><goto target=I10><break></statements></case>
<case><expression><constant>Power
<statements><goto target=I11><break></statements></case>
<case><expression><constant>Rotors
<statements><goto target=I12><break></statements></case>
<case><expression><constant>Drive
<statements><goto target=I13><break></statements></case>
<case><expression><constant>Hydraulic
<statements><goto target=I14><break></statements></case>
<case><expression><constant>Instrument
<statements><goto target=I15><break></statements></case>
<case><expression><constant>Electrical
<statements><goto target=I16><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>tempChoice2</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Servicing</label><script><statements>
<expression><assign><variable><name>tempChoice2<expression><constant>Service
</assign></statements></script></button>
<button><label>Ground Handling, Jacking, Mooring, Hoisting, and Sling Loading</label>
<script><statements>
<expression><assign><variable><name>tempChoice2<expression><constant>Ground
</assign></statements></script></button>
<button><label>Airframe</label><script><statements>
<expression><assign><variable><name>tempChoice2<expression><constant>Airframe
</assign></statements></script></button>
<button><label>Alighting Gear</label><script><statements>
<expression><assign><variable><name>tempChoice2<expression><constant>Alighting
</assign></statements></script></button>
<button><label>Power Plant</label><script><statements>
<expression><assign><variable><name>tempChoice2<expression><constant>Power
</assign></statements></script></button>
<button><label>Rotors</label><script><statements>
<expression><assign><variable><name>tempChoice2<expression><constant>Rotors
</assign></statements></script></button>
<button><label>Drive Train System</label><script><statements>
<expression><assign><variable><name>tempChoice2<expression><constant>Drive
</assign></statements></script></button>
<button><label>Hydraulic System</label><script><statements>
<expression><assign><variable><name>tempChoice2<expression><constant>Hydraulic
</assign></statements></script></button>
<button><label>Instrument Systems</label><script><statements>
<expression><assign><variable><name>tempChoice2<expression><constant>Instrument
</assign></statements></script></button>
<button><label>Electrical System</label><script><statements>
<expression><assign><variable><name>tempChoice2<expression><constant>Electrical
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice2<expression><variable><name>tempChoice2
</assign></statements></script></button></popupdialog></clientArea></infoContainer>

<infoContainer id=I07>
<vardecl><type>String<name>Choice3</vardecl>
<titlebar>Army OH-58D Helicopter Servicing</titlebar>
<clientarea><pane><text>
Army OH-58D Helicopter Subsystems
Servicing</text></pane>
<pane><text><hotspot target=I06 semantic=goto>GO BACK TO 'SUBSYSTEMS'</hotspot></text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next>
<script><statements><switch><expression><variable><name>Choice3
<case><expression><constant>Tasks
<statements><goto target=I77><break></statements></case>
<case><expression><constant>DescInfo
<statements><goto target=I02><break></statements></case>
<case><expression><constant>FaultInfo
<statements><gosub target=I700><break></statements></case>
<case><expression><constant>PartsInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>Subsystems
<statements><gosub target=I02><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice3</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Tasks</label><script><statements>
<expression><assign><variable><name>TempChoice3<expression><constant>Tasks
</assign></statements></script></button>
<button><label>Descriptive Info</label><script><statements>
<expression><assign><variable><name>TempChoice3<expression><constant>DescInfo
</assign></statements></script></button>
<button><label>Fault Info</label><script><statements>
<expression><assign><variable><name>TempChoice3<expression><constant>FaultInfo
</assign></statements></script></button>
<button><label>Parts Info</label><script><statements>
<expression><assign><variable><name>TempChoice3<expression><constant>PartsInfo
</assign></statements></script></button>
<button><label>Subsystems</label><script><statements>
<expression><assign><variable><name>TempChoice3<expression><constant>Subsystems
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice3<expression><variable><name>TempChoice3
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I08>
<vardecl><type>String<name>Choice4</vardecl>
<titlebar>Army OH-58D Helicopter Ground Handling</titlebar>
<clientarea><pane><text>
Army OH-58D Helicopter Subsystems
Ground Handling, Jacking, Mooring, Hoisting, and Sling Loading</text></pane>
<pane><text><hotspot target=I06 semantic=goto>GO BACK TO 'SUBSYSTEMS'</hotspot></text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice4
<case><expression><constant>Tasks
<statements><goto target=I99><break></statements></case>
<case><expression><constant>DescInfo
<statements><goto target=I02><break></statements></case>
<case><expression><constant>FaultInfo
<statements><gosub target=I500><break></statements></case>
<case><expression><constant>PartsInfo
<statements><gosub target=I400><break></statements></case>
<case><expression><constant>Subsystems
<statements><gosub target=I02><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice4</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Tasks</label><script><statements>
<expression><assign><variable><name>TempChoice4<expression><constant>Tasks
</assign></statements></script></button>
<button><label>Descriptive Info</label><script><statements>
<expression><assign><variable><name>TempChoice4<expression><constant>DescInfo
</assign></statements></script></button>
<button><label>Fault Info</label><script><statements>
<expression><assign><variable><name>TempChoice4<expression><constant>FaultInfo
</assign></statements></script></button>
<button><label>Parts Info</label><script><statements>
<expression><assign><variable><name>TempChoice4<expression><constant>PartsInfo
</assign></statements></script></button>
<button><label>Subsystems</label><script><statements>
<expression><assign><variable><name>TempChoice4<expression><constant>Subsystems
</assign></statements></script></button>
</pickOne><button ok><script><statements>
<expression><assign><variable><name>Choice4<expression><variable><name>TempChoice4
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I09>
<vardecl><type>String<name>Choice5</vardecl>
<titlebar>Army OH-58D Helicopter Airframe</titlebar>
<clientarea><pane><text>
Army OH-58D Helicopter Subsystems
Airframe</text></pane>
<pane><text><hotspot target=I06 semantic=goto>GO BACK TO 'SUBSYSTEMS'</hotspot></text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice5
<case><expression><constant>Tasks
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>DescInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>FaultInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>PartsInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>Subsystems
<statements><gosub target=I57><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice5</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Tasks</label><script><statements>
<expression><assign><variable><name>TempChoice5<expression><constant>Tasks
</assign></statements></script></button>
<button><label>Descriptive Info</label><script><statements>
<expression><assign><variable><name>TempChoice5<expression><constant>DescInfo
</assign></statements></script></button>
<button><label>Fault Info</label><script><statements>
<expression><assign><variable><name>TempChoice5<expression><constant>FaultInfo
</assign></statements></script></button>
<button><label>Parts Info</label><script><statements>
<expression><assign><variable><name>TempChoice5<expression><constant>PartsInfo
</assign></statements></script></button>
<button><label>Subsystems</label><script><statements>
<expression><assign><variable><name>TempChoice5<expression><constant>Subsystems
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice5<expression><variable><name>TempChoice5
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I10>
<vardecl><type>String<name>Choice9</vardecl>
<titlebar>Army OH-58D Helicopter Alighting Gear</titlebar>
<clientarea><pane><text>
Army OH-58D Helicopter Subsystems
Alighting Gear</text></pane>
<pane><text><hotspot target=I06 semantic=goto>GO BACK TO 'SUBSYSTEMS'</hotspot></text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice9
<case><expression><constant>Tasks
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>DescInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>FaultInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>PartsInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>Subsystems
<statements><gosub target=I02><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice9</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Tasks</label><script><statements>
<expression><assign><variable><name>TempChoice9<expression><constant>Tasks
</assign></statements></script></button>
<button><label>Descriptive Info</label><script><statements>
<expression><assign><variable><name>TempChoice9<expression><constant>DescInfo
</assign></statements></script></button>
<button><label>Fault Info</label><script><statements>
<expression><assign><variable><name>TempChoice9<expression><constant>FaultInfo
</assign></statements></script></button>
<button><label>Parts Info</label><script><statements>
<expression><assign><variable><name>TempChoice9<expression><constant>PartsInfo
</assign></statements></script></button>
<button><label>Subsystems</label><script><statements>
<expression><assign><variable><name>TempChoice9<expression><constant>Subsystems
</assign></statements></script></button>
</pickOne><button ok><script><statements>
<expression><assign><variable><name>Choice9<expression><variable><name>TempChoice9
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I11>
<vardecl><type>String<name>Choice10</vardecl>
<titlebar>Army OH-58D Helicopter Power Plant</titlebar>
<clientarea><pane><text>
Army OH-58D Helicopter Subsystems
Power Plant</text></pane>
<pane><text><hotspot target=I06 semantic=goto>GO BACK TO 'SUBSYSTEMS'</hotspot></text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice10
<case><expression><constant>Tasks
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>DescInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>FaultInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>PartsInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>Subsystems
<statements><gosub target=I02><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice10</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Tasks</label><script><statements>
<expression><assign><variable><name>TempChoice10<expression><constant>Tasks
</assign></statements></script></button>
<button><label>Descriptive Info</label><script><statements>
<expression><assign><variable><name>TempChoice10<expression><constant>DescInfo
</assign></statements></script></button>
<button><label>Fault Info</label><script><statements>
<expression><assign><variable><name>TempChoice10<expression><constant>FaultInfo
</assign></statements></script></button>
<button><label>Parts Info</label><script><statements>
<expression><assign><variable><name>TempChoice10<expression><constant>PartsInfo
</assign></statements></script></button>
<button><label>Subsystems</label><script><statements>
<expression><assign><variable><name>TempChoice10<expression><constant>Subsystems
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice10<expression><variable><name>TempChoice10
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I12>
<vardecl><type>String<name>Choice11</vardecl>
<titlebar>Army OH-58D Helicopter Rotors</titlebar>
<clientarea><pane><text>
Army OH-58D Helicopter Subsystems
Rotors</text></pane>
<pane><text><hotspot target=I06 semantic=goto>GO BACK TO 'SUBSYSTEMS'</hotspot></text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice11
<case><expression><constant>Tasks
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>DescInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>FaultInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>PartsInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>Subsystems
<statements><gosub target=I02><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice11</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Tasks</label><script><statements>
<expression><assign><variable><name>TempChoice11<expression><constant>Tasks
</assign></statements></script></button>
<button><label>Descriptive Info</label><script><statements>
<expression><assign><variable><name>TempChoice11<expression><constant>DescInfo
</assign></statements></script></button>
<button><label>Fault Info</label><script><statements>
<expression><assign><variable><name>TempChoice11<expression><constant>FaultInfo
</assign></statements></script></button>
<button><label>Parts Info</label><script><statements>
<expression><assign><variable><name>TempChoice11<expression><constant>PartsInfo
</assign></statements></script></button>
<button><label>Subsystems</label><script><statements>
<expression><assign><variable><name>TempChoice11<expression><constant>Subsystems
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice11<expression><variable><name>TempChoice11
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I13>
<vardecl><type>String<name>Choice12</vardecl>
<titlebar>Army OH-58D Helicopter Drive Train System</titlebar>
<clientarea><pane><text>
Army OH-58D Helicopter Subsystems
Drive Train System</text></pane>
<pane><text><hotspot target=I06 semantic=goto>GO BACK TO 'SUBSYSTEMS'</hotspot></text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice12
<case><expression><constant>Tasks
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>DescInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>FaultInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>PartsInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>Subsystems
<statements><gosub target=I02><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice12</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Tasks</label><script><statements>
<expression><assign><variable><name>TempChoice12<expression><constant>Tasks
</assign></statements></script></button>
<button><label>Descriptive Info</label><script><statements>
<expression><assign><variable><name>TempChoice12<expression><constant>DescInfo
</assign></statements></script></button>
<button><label>Fault Info</label><script><statements>
<expression><assign><variable><name>TempChoice12<expression><constant>FaultInfo
</assign></statements></script></button>
<button><label>Parts Info</label><script><statements>
<expression><assign><variable><name>TempChoice12<expression><constant>PartsInfo
</assign></statements></script></button>
<button><label>Subsystems</label><script><statements>
<expression><assign><variable><name>TempChoice12<expression><constant>Subsystems
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice12<expression><variable><name>TempChoice12
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I14>
<vardecl><type>String<name>Choice13</vardecl>
<titlebar>Army OH-58D Helicopter Hydraulic System</titlebar>
<clientarea><pane><text>
Army OH-58D Helicopter Subsystems
Hydraulic System</text></pane>
<pane><text><hotspot target=I06 semantic=goto>GO BACK TO 'SUBSYSTEMS'</hotspot></text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice13
<case><expression><constant>Tasks
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>DescInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>FaultInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>PartsInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>Subsystems
<statements><gosub target=I02><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice13</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Tasks</label><script><statements>
<expression><assign><variable><name>TempChoice13<expression><constant>Tasks
</assign></statements></script></button>
<button><label>Descriptive Info</label><script><statements>
<expression><assign><variable><name>TempChoice13<expression><constant>DescInfo
</assign></statements></script></button>
<button><label>Fault Info</label><script><statements>
<expression><assign><variable><name>TempChoice13<expression><constant>FaultInfo
</assign></statements></script></button>
<button><label>Parts Info</label><script><statements>
<expression><assign><variable><name>TempChoice13<expression><constant>PartsInfo
</assign></statements></script></button>
<button><label>Subsystems</label><script><statements>
<expression><assign><variable><name>TempChoice13<expression><constant>Subsystems
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice13<expression><variable><name>TempChoice13
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I15>
<vardecl><type>String<name>Choice14</vardecl>
<titlebar>Army OH-58D Helicopter Instrument Systems</titlebar>
<clientarea><pane><text>
Army OH-58D Helicopter Subsystems
Instrument Systems</text></pane>
<pane><text><hotspot target=I06 semantic=goto>GO BACK TO 'SUBSYSTEMS'</hotspot></text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice14
<case><expression><constant>Tasks
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>DescInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>FaultInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>PartsInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>Subsystems
<statements><gosub target=I02><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice14</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Tasks</label><script><statements>
<expression><assign><variable><name>TempChoice14<expression><constant>Tasks
</assign></statements></script></button>
<button><label>Descriptive Info</label><script><statements>
<expression><assign><variable><name>TempChoice14<expression><constant>DescInfo
</assign></statements></script></button>
<button><label>Fault Info</label><script><statements>
<expression><assign><variable><name>TempChoice14<expression><constant>FaultInfo
</assign></statements></script></button>
<button><label>Parts Info</label><script><statements>
<expression><assign><variable><name>TempChoice14<expression><constant>PartsInfo
</assign></statements></script></button>
<button><label>Subsystems</label><script><statements>
<expression><assign><variable><name>TempChoice14<expression><constant>Subsystems
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice14<expression><variable><name>TempChoice14
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I16>
<vardecl><type>String<name>Choice15</vardecl>
<titlebar>Army OH-58D Helicopter Electrical System</titlebar>
<clientarea><pane><text>
Army OH-58D Helicopter Subsystems
Electrical System</text></pane>
<pane><text><hotspot target=I06 semantic=goto>GO BACK TO 'SUBSYSTEMS'</hotspot></text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice15
<case><expression><constant>Tasks
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>DescInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>FaultInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>PartsInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>Subsystems
<statements><gosub target=I02><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice15</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Tasks</label><script><statements>
<expression><assign><variable><name>TempChoice15<expression><constant>Tasks
</assign></statements></script></button>
<button><label>Descriptive Info</label><script><statements>
<expression><assign><variable><name>TempChoice15<expression><constant>DescInfo
</assign></statements></script></button>
<button><label>Fault Info</label><script><statements>
<expression><assign><variable><name>TempChoice15<expression><constant>FaultInfo
</assign></statements></script></button>
<button><label>Parts Info</label><script><statements>
<expression><assign><variable><name>TempChoice15<expression><constant>PartsInfo
</assign></statements></script></button>
<button><label>Subsystems</label><script><statements>
<expression><assign><variable><name>TempChoice15<expression><constant>Subsystems
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice15<expression><variable><name>TempChoice15
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I17>
<titlebar>Army OH-58D Helicopter Descriptive Info</titlebar>
<clientarea><pane><text>

1. AIRFRAME

The basic airframe consists of a fuselage (1), tailboom (BR), and pylon (3).

a. The fuselage houses the crew station and electronic
components. It serves as a platform for the engine,
transmission, and main rotor system.

b. The tailboom serves as a platform for the tail rotor
gearbox as well as the vertical fin, horizontal stabilizer,
segmented tail rotor driveshaft, and bearing supports.
The control tubes to the tail rotor are contained in the
tailboom.

c. The pylon provides a cover for the power plant,
transmission, hydraulic reservoir, and engine oil tank.
Access covers and sight windows are provided for the
components. Two pylon beam assemblies provide support
for the transmission.</text></pane>
<pane><graphic><graphicPrimitive source=GR1011></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I21>
<titlebar>Army OH-58D Helicopter Descriptive Info</titlebar>
<clientarea><pane><text>
2. LANDING GEAR
The landing gear consists of two tubular main skid tubes
and two curved crosstube assemblies. The landing gear is
attached to the fuselage with four strap assemblies.
Provisions are made on the skid tubes for installing ground
handling wheels, and two rings are provided for towing.
Each skid tube is provided with replaceable skid shoes
which are highly resistant to wear caused by normal ground
contact of the helicopter.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I22>
<titlebar>Army OH-58D Helicopter Descriptive Info</titlebar>
<clientarea><pane><text>
3. POWER PLANT
The helicopter is equipped with an internal combustion
turboshaft Allison engine, model T703-AD-700 The four major
components of the engine are the compressor section,
combustion section, power turbine section, and the power
and accessories gearbox.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I23>
<titlebar>Army OH-58D Helicopter Descriptive Info</titlebar>
<clientarea><pane><text>
3. POWER PLANT
(1) Compressor Section. The compressor section is a single-
stage, single-entry centrifugal flow compressor and is directly
coupled to a two-stage turbine drive. Compressed air exits the
compressor section through the scroll assembly (1).</text></pane>
<pane><graphic><graphicPrimitive source=GR1012></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I24>
<titlebar>Army OH-58D Helicopter Descriptive Info</titlebar>
<clientarea><pane><text>
3. POWER PLANT
(2) Combustion Section. The single combustion section
consists of a combustion liner, an outer case, a fuel injector
(2), and one igniter plug (3). Compressed air is delivered to
the combustion section by means of the discharge tubes (4).</text></pane>
<pane><graphic><graphicPrimitive source=GR1012></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I25>
<titlebar>Army OH-58D Helicopter Descriptive Info</titlebar>
<clientarea><pane><text>
3. POWER PLANT
(3) Power Turbine Section. The power turbine section
consists of the two-stage power turbine drive and two-stage
gas producer turbine drive.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I26>
<titlebar>Army OH-58D Helicopter Descriptive Info</titlebar>
<clientarea><pane><text>
3. POWER PLANT
(4) Power and Accessories Gearbox. The power and accessories
gearbox (5) consists of the gas producer turbine drive
geartrain and the power turbine drive geartrain All engine
components, including the engine mounted accessories, are
installed on the gearbox. The power and accessories gearbox
incorporates two monopole pickup units to sense and control
gas producer turbine and power turbine speed. Components and
accessories driven by the gas producer drive train are the
engine fuel pump (6), fuel control unit (FCU) (7), pressure
and scavenge oil pump, and the starter-generator drive. The
power turbine drive train drives two spare drive pads, the ac
generator (8), and supplies the power output for main rotor
(9) and tail rotor drive (10).</text></pane>
<pane><graphic><graphicPrimitive source=GR1012></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I57>
<vardecl><type>String<name>Choice16</vardecl>
<titlebar>Army OH-58D Helicopter Airframe Subsystems</titlebar>
<clientarea><pane><text>
Army OH-58D Helicopter Airframe Subsystems</text></pane>
<pane><text><hotspot target=I09 semantic=goto>GO BACK TO 'AIRFRAME'</hotspot></text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice16
<case><expression><constant>Fuselage
<statements><gosub target=I58><break></statements></case>
<case><expression><constant>Tailboom
<statements><gosub target=I59><break></statements></case>
<case><expression><constant>Pylon
<statements><gosub target=I60><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice16</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Fuselage</label><script><statements>
<expression><assign><variable><name>TempChoice16<expression><constant>Fuselage
</assign></statements></script></button>
<button><label>Tailboom</label><script><statements>
<expression><assign><variable><name>TempChoice16<expression><constant>Tailboom
</assign></statements></script></button>
<button><label>Pylon</label><script><statements>
<expression><assign><variable><name>TempChoice16<expression><constant>Pylon
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice16<expression><variable><name>TempChoice16
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I58>
<vardecl><type>String<name>Choice17</vardecl>
<titlebar>Army OH-58D Helicopter Airframe, Fuselage</titlebar>
<clientarea><pane><text>
Army OH-58D Helicopter Airframe
Fuselage</text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice17
<case><expression><constant>Tasks
<statements><goto target=I178><break></statements></case>
<case><expression><constant>DescInfo
<statements><goto target=I02><break></statements></case>
<case><expression><constant>FaultInfo
<statements><gosub target=I500><break></statements></case>
<case><expression><constant>PartsInfo
<statements><gosub target=I401><break></statements></case>
<case><expression><constant>Subsystems
<statements><gosub target=I02><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice17</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Tasks</label><script><statements>
<expression><assign><variable><name>TempChoice17<expression><constant>Tasks
</assign></statements></script></button>
<button><label>Descriptive Info</label><script><statements>
<expression><assign><variable><name>TempChoice17<expression><constant>DescInfo
</assign></statements></script></button>
<button><label>Fault Info</label><script><statements>
<expression><assign><variable><name>TempChoice17<expression><constant>FaultInfo
</assign></statements></script></button>
<button><label>Parts Info</label><script><statements>
<expression><assign><variable><name>TempChoice17<expression><constant>PartsInfo
</assign></statements></script></button>
<button><label>Subsystems</label><script><statements>
<expression><assign><variable><name>TempChoice17<expression><constant>Subsystems
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice17<expression><variable><name>TempChoice17
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I59>
<vardecl><type>String<name>Choice18</vardecl>
<titlebar>Army OH-58D Helicopter Airframe, Tailboom</titlebar>
<clientarea><pane><text>
Army OH-58D Helicopter Airframe
Tailboom</text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice18
<case><expression><constant>Tasks
<statements><goto target=I179><break></statements></case>
<case><expression><constant>DescInfo
<statements><goto target=I02><break></statements></case>
<case><expression><constant>FaultInfo
<statements><gosub target=I500><break></statements></case>
<case><expression><constant>PartsInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>Subsystems
<statements><gosub target=I02><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice18</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Tasks</label><script><statements>
<expression><assign><variable><name>TempChoice18<expression><constant>Tasks
</assign></statements></script></button>
<button><label>Descriptive Info</label><script><statements>
<expression><assign><variable><name>TempChoice18<expression><constant>DescInfo
</assign></statements></script></button>
<button><label>Fault Info</label><script><statements>
<expression><assign><variable><name>TempChoice18<expression><constant>FaultInfo
</assign></statements></script></button>
<button><label>Parts Info</label><script><statements>
<expression><assign><variable><name>TempChoice18<expression><constant>PartsInfo
</assign></statements></script></button>
<button><label>Subsystems</label><script><statements>
<expression><assign><variable><name>TempChoice18<expression><constant>Subsystems
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice18<expression><variable><name>TempChoice18
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I60>
<vardecl><type>String<name>Choice19</vardecl>
<titlebar>Army OH-58D Helicopter Airframe, Pylon</titlebar>
<clientarea><pane><text>
Army OH-58D Helicopter Airframe
Pylon</text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice19
<case><expression><constant>Tasks
<statements><goto target=I180><break></statements></case>
<case><expression><constant>DescInfo
<statements><goto target=I02><break></statements></case>
<case><expression><constant>FaultInfo
<statements><gosub target=I500><break></statements></case>
<case><expression><constant>PartsInfo
<statements><gosub target=I02><break></statements></case>
<case><expression><constant>Subsystems
<statements><gosub target=I02><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice19</vardecl>
<prompt>Select an area of interest:</prompt>
<pickOne><button><label>Tasks</label><script><statements>
<expression><assign><variable><name>TempChoice19<expression><constant>Tasks
</assign></statements></script></button>
<button><label>Descriptive Info</label><script><statements>
<expression><assign><variable><name>TempChoice19<expression><constant>DescInfo
</assign></statements></script></button>
<button><label>Fault Info</label><script><statements>
<expression><assign><variable><name>TempChoice19<expression><constant>FaultInfo
</assign></statements></script></button>
<button><label>Parts Info</label><script><statements>
<expression><assign><variable><name>TempChoice19<expression><constant>PartsInfo
</assign></statements></script></button>
<button><label>Subsystems</label><script><statements>
<expression><assign><variable><name>TempChoice19<expression><constant>Subsystems
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice19<expression><variable><name>TempChoice19
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I77>
<vardecl><type>String<name>Choice77</vardecl>
<clientarea><pane><text>
Army OH-58D Helicopter Servicing
Tasks</text></pane>
<pane><text><hotspot target=I07 semantic=goto>GO BACK TO 'SERVICING'</hotspot></text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice77
<case><expression><constant>DefuelValve
<statements><gosub target=I78><gosub target=I79><gosub target=I80>
<gosub target=I81><gosub target=I82><gosub target=I83><gosub target=I84>
<gosub target=I85><gosub target=I86><gosub target=I87><gosub target=I88>
<gosub target=I89><gosub target=I90><gosub target=I91><gosub target=I92>
<gosub target=I93><gosub target=I94><gosub target=I95><gosub target=I96>
<gosub target=I97><gosub target=I98><break></statements></case>
<case><expression><constant>DefuelTruck
<statements><gosub target=I78><gosub target=I100><gosub target=I101>
<gosub target=I83><gosub target=I84><gosub target=I85><gosub target=I86>
<gosub target=I102><gosub target=I103><gosub target=I104><gosub target=I105>
<gosub target=I106><gosub target=I107><gosub target=I108><gosub target=I109>
<gosub target=I110><gosub target=I111><gosub target=I112><gosub target=I113>
<break></statements></case>
<case><expression><constant>Oil
<statements><gosub target=I04><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice77</vardecl>
<prompt>Select a task:</prompt>
<pickOne><button><label>Defuel helicopter with valve</label><script><statements>
<expression><assign><variable><name>TempChoice77<expression><constant>DefuelValve
</assign></statements></script></button>
<button><label>Defuel with truck</label><script><statements>
<expression><assign><variable><name>TempChoice77<expression><constant>DefuelTruck
</assign></statements></script></button>
<button><label>Drain/service engine oil system</label><script><statements>
<expression><assign><variable><name>TempChoice77<expression><constant>Oil
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice77<expression><variable><name>TempChoice77
</assign></statements></script></button></popupDialog></clientarea></infoContainer>

<infoContainer id=I78>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
Applicable Configurations:
All</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I79>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
Tools:
Aircraft Mechanic Tool Kit
1-3/4 Inch Crowfoot (B6)
Nipple (Work Aid)
Hose Assembly (Work Aid)
Suitable Fuel Containers
Portable Fire Extinguisher</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I80>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
Parts:
Packing</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I81>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
Materials:
Lockwire (D4)</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I82>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
Personnel Required:
66S Scout Helicopter Technical Inspector
67S Scout Helicopter Repairer</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I83>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
References:
FM 10-68</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I84>
<titlebar>WARNING</titlebar>
<clientarea><pane><text>
WARNING!

Fuel spills/splashes can cause injury to personnel
through contact with skin or vapors entering the
respiratory system. Personnel who are subjected
to splashed and sprayed fuel should remove their
clothing as soon as possible and wash down/shower
with large amounts of water. Contaminated clothing
shall not be placed near potential ignition sources.
Use caution during defueling. Aircraft fuel is
highly flammable and easily ignited by static or
friction sparks, hot exhaust pipes, lighted
cigarettes, electrical devices, or similar ignition
sources. Fuel spillage presents an extreme fire
hazard.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I85>
<titlebar>WARNING</titlebar>
<clientarea><pane><text>
WARNING!

TOXIC AND FLAMMABLE FUELS

Turbine fuels and fuel fumes are flammable. They
cause drying and irritation of skin or eyes.

- Handle only in well-ventilated areas away from
heat and open flame.
- Store in approved metal safety containers.
- Avoid prolonged or repeated contact with skin.
- Do not take internally.
- Wash contacted areas of skin after handling.
- Get immediate medical attention for eyes and
irritated skin.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I86>
<titlebar>CAUTION</titlebar>
<clientarea><pane><text>
CAUTION!

If helicopter is being defueled due to an
accident or incident or if fuel is suspected
of being contaminated, the fuel shall be tested
before disposal. Do not return drained fuel
to storage area unless it has passed through a
filter or separator.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I87>
<titlebar>Defuel Helicopter With Valve</titlebar>
<clientarea><pane><text>
1. Ground helicopter to ground stake.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I88>
<titlebar>Defuel Helicopter With Valve</titlebar>
<clientarea><pane><text>
2. Ground fuel container to ground stake.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I89>
<titlebar>Defuel Helicopter With Valve</titlebar>
<clientarea><pane><text>
3. Ground helicopter to fuel container.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I90>
<titlebar>Defuel Helicopter With Valve</titlebar>
<clientarea><pane><text>
4. Position fireguard with portable fire
extinguisher close to defueling operation.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I91>
<titlebar>Defuel Helicopter With Valve</titlebar>
<clientarea><pane><text>
5. Cut lockwire to plug (1) in defueling valve (2).</text></pane>
<pane><graphic><graphicPrimitive source=GR1045></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I92>
<titlebar>Defuel Helicopter With Valve</titlebar>
<clientarea><pane><text>
6. Remove plug (1) and discard packing (3).</text></pane>
<pane><graphic><graphicPrimitive source=GR1045></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I93>
<titlebar>Defuel Helicopter With Valve</titlebar>
<clientarea><pane><text>
7. Install MS24393D12 nipple or equivalent (4)
in MIL-H-8794 flexible hose (5).</text></pane>
<pane><graphic><graphicPrimitive source=GR1045></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I94>
<titlebar>Defuel Helicopter With Valve</titlebar>
<clientarea><pane><text>
8. Place free end of hose (5) in fuel container.</text></pane>
<pane><graphic><graphicPrimitive source=GR1045></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I95>
<titlebar>Defuel Helicopter With Valve</titlebar>
<clientarea><pane><text>
9. Open defueling valve (2) by installing nipple (4)
into valve (2).</text></pane>
<pane><graphic><graphicPrimitive source=GR1045></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I96>
<titlebar>Defuel Helicopter With Valve</titlebar>
<clientarea><pane><text>
10. After defueling, remove nipple (4) from
defueling valve (2).</text></pane>
<pane><graphic><graphicPrimitive source=GR1045></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I97>
<titlebar>Defuel Helicopter With Valve</titlebar>
<clientarea><pane><text>
11. Install plug (1) with packing (3). Secure
plug (1) with lockwire (D4).</text></pane>
<pane><graphic><graphicPrimitive source=GR1045></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I98>
<titlebar>Defuel Helicopter With Valve</titlebar>
<clientarea><pane><text>
INSPECT</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I99>
<vardecl><type>String<name>Choice99</vardecl>
<titlebar>Army OH-58D Helicopter Ground Handling</titlebar>
<clientarea><pane><text>
Army OH-58D Helicopter
Ground Handling</text></pane>
<pane><text><hotspot target=I08 semantic=goto>GO BACK TO 'GROUND HANDLING'</hotspot></text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next><script><statements>
<switch><expression><variable><name>Choice99
<case><expression><constant>Covers
<statements><gosub target=I78><gosub target=I138>
<gosub target=I139><gosub target=I140><gosub target=I141>
<gosub target=I142><gosub target=I143><gosub target=I144>
<gosub target=I145><break></statements></case>
<case><expression><constant>Tiedowns
<statements><gosub target=I78><gosub target=I146><gosub target=I147>
<gosub target=I148><gosub target=I149><gosub target=I150><gosub target=I151>
<gosub target=I152><gosub target=I153><gosub target=I154><gosub target=I155>
<gosub target=I156><gosub target=I157><gosub target=I158><gosub target=I159>
<gosub target=I160><gosub target=I161><gosub target=I162><gosub target=I163>
<gosub target=I164><gosub target=I165><gosub target=I166><gosub target=I167>
<gosub target=I168><gosub target=I169><gosub target=I170><gosub target=I171>
<gosub target=I172><gosub target=I173><gosub target=I174><gosub target=I175>
<gosub target=I176><gosub target=I177><break></statements></case>
</switch></statements></script></button></footerbar>
<popupdialog><userInteraction><vardecl><type>String<name>TempChoice99</vardecl>
<prompt>Select a task:</prompt>
<pickOne><button><label>Install helicopter covers</label><script><statements>
<expression><assign><variable><name>TempChoice99<expression><constant>Covers
</assign></statements></script></button>
<button><label>Install/Remove rotor tiedowns</label><script><statements>
<expression><assign><variable><name>TempChoice99<expression><constant>Tiedowns
</assign></statements></script></button></pickOne>
<button ok><script><statements>
<expression><assign><variable><name>Choice99<expression><variable><name>TempChoice99
</assign></statements></script></button></popupdialog></clientarea></infoContainer>

<infoContainer id=I100>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
Tools:
Defueling Truck</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I101>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
Personnel Required:
67S Scout Helicopter Repairer
76W Petroleum Supply Specialist</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I102>
<titlebar>Defuel With Truck</titlebar>
<clientarea><pane><text>
1. Ground helicopter and defueling truck to ground stake (FM 10-68).</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I103>
<titlebar>Defuel With Truck</titlebar>
<clientarea><pane><text>
2. Attach defueling hose ground wire to helicopter (FM 10-68).</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I104>
<titlebar>Defuel With Truck</titlebar>
<clientarea><pane><text>
3. Remove filler cap (1) from fuel
receiver (2). Insert latch tool (3)
between fuel receiver (2) and latch (4)
to open module (5).</text></pane>
<pane><graphic><graphicPrimitive source=GR1047></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I105>
<titlebar>CAUTION</titlebar>
<clientarea><pane><text>
CAUTION!

Do not damage inside surface of fuel cell by forcing hose.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I106>
<titlebar>Defuel With Truck</titlebar>
<clientarea><pane><text>
4. Correctly insert defueling hose (6)
into fuel cell to touch bottom of cell.</text></pane>
<pane><graphic><graphicPrimitive source=GR1047></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I107>
<titlebar>Defuel With Truck</titlebar>
<clientarea><pane><text>
5. Start pumping fuel from helicopter.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I108>
<titlebar>Defuel With Truck</titlebar>
<clientarea><pane><text>
6. As the fuel flow stops, shut down pump.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I109>
<titlebar>Defuel With Truck</titlebar>
<clientarea><pane><text>
7. Remove defueling hose (6) from helicopter fuel cell.</text></pane>
<pane><graphic><graphicPrimitive source=GR1047></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I110>
<titlebar>Defuel With Truck</titlebar>
<clientarea><pane><text>
8. To complete defueling, drain remaining
fuel into a suitable container.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I111>
<titlebar>Defuel With Truck</titlebar>
<clientarea><pane><text>
9. Pull filler cap (1) until module (5)
is fastened to the latch (4).</text></pane>
<pane><graphic><graphicPrimitive source=GR1047></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I112>
<titlebar>Defuel With Truck</titlebar>
<clientarea><pane><text>
10. Connect filler cap (1) to fuel receiver (2).</text></pane>
<pane><graphic><graphicPrimitive source=GR1047></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I113>
<titlebar>Defuel With Truck</titlebar>
<clientarea><pane><text>
11. Leave helicopter grounded unless it is to be moved.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I114>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
Tools:
Aircraft Mechanic Tool Kit
Suitable Container</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I115>
<titlebar>Initial setup</titlebar>
<clientarea><pane><text>
Materials:
Oil (D2 or D3)
Lockwire (D4)</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I116>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
References:
TM 55-2840-256-23</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I117>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
Equipment Condition:
Aft Fairing Removed</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I118>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
1. Open oil tank filler cap (1).</text></pane>
<pane><graphic><graphicPrimitive source=GR1051></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I119>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
2. Place suitable container beneath drain tube (2).</text></pane>
<pane><graphic><graphicPrimitive source=GR1051></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I120>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
3. Turn drain valve (3) 90 degrees counterclockwise
and allow oil to drain into container.</text></pane>
<pane><graphic><graphicPrimitive source=GR1051></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I121>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
4. Service engine oil system at each oil change (TM 55-2840-256-23).</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I122>
<titlebar>NOTE</titlebar>
<clientarea><pane><text>
NOTE!

Mixing of oils not in the same group (MIL-L-7808
Group (D3) and MIL-L-23699 Group (D2)) is permitted
only in an emergency. Use of mixed oils (oil not
in the same group) in an engine is limited to 5
hours total running time during one overhaul period.
Adequate maintenance records must be maintained to
ensure that the 5-hour limit is not exceeded.

Oil level should be checked within 30 minutes of
engine shutdown.

Normal tank capacity of oil tank is 11.2 pints.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I123>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
5. Check oil level by observing sight glass (4) on oil tank (5).</text></pane>
<pane><graphic><graphicPrimitive source=GR1051></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I124>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
6. Oil is required when oil level falls below the top of sight glass.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I125>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
7. If oil is required, remove filler cap (1) and
service with lubricating oil (D2 or D3).</text></pane>
<pane><graphic><graphicPrimitive source=GR1051></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I126>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
8. Install filler cap (1).</text></pane>
<pane><graphic><graphicPrimitive source=GR1051></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I127>
<titlebar>NOTE</titlebar>
<clientarea><pane><text>
NOTE!

See step 9 for servicing of lines and pump.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I128>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
9. Servicing engine when lines and pump are dry:</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I129>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
9(a). Refer to steps 1 through 7 in preceding steps.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I130>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
9(b). Disconnect lines (6 and 7) from standoff clamps (8).</text></pane>
<pane><graphic><graphicPrimitive source=GR1052></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I131>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
9(c). Loosen oil inlet port elbow (9).</text></pane>
<pane><graphic><graphicPrimitive source=GR1052></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I132>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
9(d). Lower lines (6 and 7) and allow oil from
engine oil tank to enter lines.</text></pane>
<pane><graphic><graphicPrimitive source=GR1052></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I133>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
9(e). When oil seeps from inlet port elbow (9), retighten elbow.</text></pane>
<pane><graphic><graphicPrimitive source=GR1052></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I134>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
9(f). Raise lines (6 and 7) and install standoff clamps (8).</text></pane>
<pane><graphic><graphicPrimitive source=GR1052></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I135>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
9(g). Fill oil tank completely and clean oil from
engine deck where seepage occurred.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I136>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>INSPECT</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I137>
<titlebar>Drain/service engine oil system</titlebar>
<clientarea><pane><text>
FOLLOW-ON MAINTENANCE

Install aft fairing.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I138>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
Tools:
Maintenance Platform
Engine Exhaust Cover (Loose Equipment)
Engine Inlet Covers (2) (Loose Equipment)
Pitot Cover (Loose Equipment)</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I139>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
Personnel Required:
67S Scout Helicopter Repairer (1)</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I140>
<titlebar>NOTE</titlebar>
<clientarea><pane><text>
NOTE!

Protective covers must be installed at
locations shown when helicopter is
parked or moored.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I141>
<titlebar>Install Helicopter Covers</titlebar>
<clientarea><pane><text>
1. Install engine exhause cover (1) over the
exhause ejector. Slide cover (1) down until
it bottoms out on the exhaust ejector.</text></pane>
<pane><graphic><graphicPrimitive source=GR1089></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I142>
<titlebar>Install Helicopter Covers</titlebar>
<clientarea><pane><text>
2. Install engine inlet covers (2).</text></pane>
<pane><graphic><graphicPrimitive source=GR1089></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I143>
<titlebar>Install Helicopter Covers</titlebar>
<clientarea><pane><text>
3. Install pitot cover (3).</text></pane>
<pane><graphic><graphicPrimitive source=GR1089></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I144>
<titlebar>Install Helicopter Covers</titlebar>
<clientarea><pane><text>
4. Extend lanyards (4) from pitot cover (3)
along left and right sides of fuselage and
fasten to engine inlet covers (2).</text></pane>
<pane><graphic><graphicPrimitive source=GR1089></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I145>
<titlebar>Install Helicopter Covers</titlebar>
<clientarea><pane><text>
5. When not installed, stow protective covers
in aft electrical compartment (5).</text></pane>
<pane><graphic><graphicPrimitive source=GR1089></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I146>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
Tools:
Polyester Rope (AR) 1/2 inch diameter
Wand Assembly (Loose Equipment)
Sock Assemblies (4) (Loose Equipment)</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I147>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
Personnel Required:
67S Scout Helicopter Repairer (2)</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I148>
<titlebar>Initial Setup</titlebar>
<clientarea><pane><text>
References:
TM 1-1520-250-23-1</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I149>
<titlebar>NOTES</titlebar>
<clientarea><pane><text>
NOTES!
Tiedowns form main rotor blades consist of
two FWD and two AFT blade socks and polyester
rope 1/2 inch diameter. A wand assembly is
provided as an aid to install the socks.

Polyester rope; 1/2 inch diameter, is to be
used in place of tiedown lines.

Main rotor blades may be manually rotated
clockwise or counterclockwise to position
blade for tiedown.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I150>
<titlebar>Install/Remove Rotor Tiedowns</titlebar>
<clientarea><pane><text>
1. Position blades (1) at 45-degree angle to
fuselage so that tiedown lines (2) can be secured.</text></pane>
<pane><graphic><graphicPrimitive source=GR1093></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I151>
<titlebar>Install/Remove Rotor Tiedowns</titlebar>
<clientarea><pane><text>
2. Unfold wand assembly (3) as follows:</text></pane>
<pane><graphic><graphicPrimitive source=GR1093></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I152>
<titlebar>Install/Remove Rotor Tiedowns</titlebar>
<clientarea><pane><text>
2(a). Unwind strap (4) holding spreader arms (5) against upper tube (6).</text></pane>
<pane><graphic><graphicPrimitive source=GR1093></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I153>
<titlebar>Install/Remove Rotor Tiedowns</titlebar>
<clientarea><pane><text>
2(b). Unlock lock (7) and rotate lower tube (8) 180 degrees.</text></pane>
<pane><graphic><graphicPrimitive source=GR1093></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I154>
<titlebar>Install/Remove Rotor Tiedowns</titlebar>
<clientarea><pane><text>
2(c). Slide lock (7) down upper tube (6) and engage lower tube (8).</text></pane>
<pane><graphic><graphicPrimitive source=GR1093></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I155>
<titlebar>Install/Remove Rotor Tiedowns</titlebar>
<clientarea><pane><text>
2(d). Lock wand assembly (3) in extended position.</text></pane>
<pane><graphic><graphicPrimitive source=GR1093></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I156>
<titlebar>Install/Remove Rotor Tiedowns</titlebar>
<clientarea><pane><text>
3. Install FWD BLADES sock (9) on wand assembly (3) as follows (Detail B):</text></pane>
<pane><graphic><graphicPrimitive source=GR1093></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I157>
<titlebar>Install/Remove Rotor Tiedowns</titlebar>
<clientarea><pane><text>
3(a). Open spreader arms (5).</text></pane>
<pane><graphic><graphicPrimitive source=GR1093></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I158>
<titlebar>Install/Remove Rotor Tiedowns</titlebar>
<clientarea><pane><text>
3(b). Spring spreader arms (5) toward each other and
insert spreader arm guides (10) into grommets (11) of
FWD BLADES sock (9).</text></pane>
<pane><graphic><graphicPrimitive source=GR1093></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I159>
<titlebar>NOTE</titlebar>
<clientarea><pane><text>
NOTE!

Rings are preadjusted to give forward and
aft blades moderate tension when secured.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I160>
<titlebar>Install/Remove Rotor Tiedowns</titlebar>
<clientarea><pane><text>
3(c). Each tiedown line (2) for forward blades has
a ring (12) near each end with flag labeled FWD BLADES.</text></pane>
<pane><graphic><graphicPrimitive source=GR1093></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I161>
<titlebar>Install/Remove Rotor Tiedowns</titlebar>
<clientarea><pane><text>
3(d). Securely tie the straps of the boot to the 1/2
inch diameter polyester rope near the boot.</text></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>

<infoContainer id=I162>
<titlebar>Install/Remove Rotor Tiedowns</titlebar>
<clientarea><pane><text>
3(e). Each tiedown line (2) for aft blades has a
ring (13) near end with flag labeled AFT BLADES.</text></pane>
<pane><graphic><graphicPrimitive source=GR1093></graphic></pane>
<pane><text><hotspot target=I00 semantic=goto>RESTART CURRENT MID</hotspot></text></pane>
<footerbar><button next></footerbar></clientarea></infoContainer>