The JIA

1
The JIA

• Joint IETM Architecture
• A new architecture to support the DoD Repair and
  Maintenance Knowledge Base for the 21st Century
• Eric L. Jorgensen
• NSWC, Carderock Division
• NAVSEA - Department of the Navy

2
Outline

• Technical description of the JIA
• Implementing the JIA in IETM Deliverables
• The Impact of JIA as an Enabler to Building a
  On-line Maintenance and Repair Knowledge Base

3
JIA Task Objective

• Develop and test a new information architecture
  and the needed interoperability standards for
  IETM development and deployment, which will
  permit dissimilar DoD weapon-system IETMs,
  regardless of the source, to be read and viewed
  on a common user-interface system with common
  access to field technical-information libraries

4
Scope of Effort

• All types of Electronic Technical Manuals (from
  paper-based electronic images to IETMs)
• All legacy and future IETMs
• Applicable to all Services

5
Tri-Service Endorsed Approach

• Build on Navy IETM Architecture (NIA)
• Identify Army, Navy, Air Force, and Marine Corps
  requirements for IETM interoperability
• Assess current/planned Service IETM programs and
  actions needed to achieve interoperability
• Develop Joint IETM Architecture (JIA)
• Conduct pilot demonstrations on Service programs
• Analyze results and modify JIA
• Develop recommended policy and interoperability
  standards

6
Background

• The DoD IETM Specifications were
• Developed to guide the transformation from paper
  to interactive electronic medium
• Industry Coordination AIA and CALS ISG
• Coordinated with Army, Navy, and Air Force
• Formally Issued in 1992 to allow inclusion in
  contracts

7
Background (Cond)

• IETM Specs were General specifications designed
  to encourage innovation and use of electronic
  documents
• They have been used in many implementations and
  have been successful in meeting original
  objectives

8
Issues with IETM Interoperability

• Initial developers developed both authoring
  system and presentation system from scratch
• Result Individual Presentation Systems could only
  display information specifically authored for
  that Presentation System

9
Proposed Approach to Solving Problems

• Needed an Approach to Solve the Interoperability
  Problem for Both Suppliers and Users
• Needed an environment in which a successful
  transition has been made from paper media to
  electronic media
• Desired a Commercial Technology Solution

10
Web-Oriented Approach

• Use World-Wide-Web/ Internet technology used in
  Private DoD Intranet
• Proven and mature Software Products
• Very High Level of User Acceptance
• High user population and High level of vendor
  support
• Evaluate Potential for DoD IETM Acquisition and
  Deployment Policy

11
Applies to the entireIETM Community

• IETM Authoring Organization
• Government Infrastructure Activity managing the
  IETMs
• User Operational Sites
• Site Electronic Library (using a Site Server)
• End-User (viewing the IETM on a Workstation or
  PEDD

12
IETM Interoperability

• Develop a New IETM Architecture for Fielded
  Weapon System Support Information
• Ability to Include and Interoperate IETM Data
  Bases and Additional Functions to Support
• Maintenance including Parts Ordering
• Equipment Operations
• Job Site Training
• Need to Confederate and Include Existing Legacy
  Information into Interoperable System

13
Interoperability Definition

• The ability to use someone elses IETM for
• Cross-referencing
• Inclusion of portions in your IETM
• Building a composite IETM out of different parts
  (yours and theirs)
• The ability to view anyones IETM on one common
  browser

14
Overview of the JIA

• Architecture to facilitate DoD wide fielding of
  Intranet Web- enabled IETMs
• Applicable to Lifecycle of IETM
• Acquisition/Development
• Deployment on DoD Networks/Webs
• Feedback
• Update at User Location

15
Specifications forInteroperability

• Object Encapsulation (IETM View Package)
• Intranet Server and Database Interface
• Electronic Addressing Model and Registry
• Common Browser

16
Applicability of the JIA

• All types of Electronic Technical Manuals (from
  paper-based electronic images to IETMs)
• All legacy and future IETMs
• Applicable to all Services
• Applicable to Lifecycle of IETM
• Acquisition/Development
• Deployment on DoD Networks/Webs
• Feedback
• Update at User Location

17
Selected Web-OrientedApproach for JIA

• Use World-Wide-Web/ Internet technology deployed
  on dedicated DoD Intranet
• Proven and mature software products available
• Very high level of user acceptance
• High user population and high level of vendor
  support

18
Authoring Process
Encapsulated Web Object Creation Process
Electronic Delivery to NAVAIR Customer
Encapsulated Web Object
Encapsulated Web Object
Authoring 2 Data Base
Authoring 2
Encapsulated Web Object Creation Process
Aerospace Contractor 2
19
Infrastructure Process
GCSS - Navy Intranet
Infrastructure Server and Management Site (e.g.,
NATEC)
Encapsulated Web Objects
Encapsulated Web Objects
Receive Delivered Web Objects from IETM Authoring
Activity
Site Repository
Distribute to User Site via CD/ROM
20
User Site Process
Encapsulated Web Objects
1 User-1 Device-1 Browser for All IETMs
GCSS - Navy Intranet
User Workstation
Site Server e.g., Optimized NALCOMIS
Portable User Device
Encapsulated Web Objects Via CD/ROM
Personal Server
The User Site Intranet Web
21
Payoffs

• Substantial savings are possible by eliminating
  duplication of servers and data bases and by
  employing high-payoff centeral applications only
  made possible by Global Connectivity and Central
  site Currency Management over a DoD Web.
• Can achieve an IDE using the DII in Web-mode
  without the investment cost of developing an IDE

22
Benefits to User

• One HW/SW interface per user accesses all NAVAIR
  IETMs regardless of data format or authoring
  system.
• Single point and click access to any referenced
  IETM irrespective of format.
• No system administrator needed to load IETM
  Software on user device.
• Can employ Off-the-Shelf/0ut-of-the-Box PEDDs or
  PC workstations.
• Rich search capability for all IETMs no matter
  what the run-time format.

23
Benefits to Infrastructure Administrators

• Entire IETM encapsualted as a single digital-data
  package which can be managed, stored, and
  forwarded as a single item of supply
• No specialized IETM subject-matter computer
  expert needed to manage infrastructure
• Easy to mount a central server for entire
  community using DII/Navy Intranet as distribution
  medium
• Easy to integrate with other non-IETM Web Sites
  for related logistics information

24
Benefits to IETM Developers

• Can develop interoperable IETMs without being
  restricted to a particular IETM authoring system
• free to choose most cost effective system - No
  need for custom system to meet program
  requirements
• can choose from multiple low cost and
  commercially available (COTS) authoring
  capabilities
• readily available labor pool of experienced
  authors familiar with Web-based software
• Can develop hybrid IETMs using low cost and
  available PDF or HTML without reauthoring for
  included legacy information such as standard
  procedures, boiler-plate, OEM data for a part,
  etc.

25
Benefits to Programs

• No longer any excuse for needing customer funded
  custom IETM authoring systems!
• JIA project team has been working with Industry
  to be sure that adequate JIA compliant COTS IETM
  authoring systems are available
• This was one of the principal NAVAIR problems and
  requirements that kicked off the NIA/JIA study
• No special HW/SW Spec needed to procure user
  devices
• Permits buying Portable Devices later in
  procurement time line. In procuring computer
  devices this means much more Bang for the Buck!

26
Need Total JIA Adoption

• Adoption of the JIA in the DoD IETM Community
  will result in
• Program Managers can make IETM decisions based on
  business factors
• Infrastructure Managers can build a COTS based
  infrastructure that will accommodate the expected
  variety of IETMs without major custom
  modifications for each IETM
• Users can get all the IETM information they need
  through one system one familiar Web-Browser
  interface

27
DII Future Vision

• The Largest DoD-Wide Payoff from Interoperable
  IETMs will come from the use of the Defense
  Information Infrastructure employing true Global
  Connectivity
• DoD Can Use the New Web-Based Jia to Build a True
  Integrated Data Environment - The JIA is not for
  IETMs only!

28
Potential of Integrating IETM and Training
29
Single Product Support Data Base

• Include All Information Needed to Maintain,
  Train, and Operate Weapon System
• Accessible On-Line at Equipment Site
• Does Not Require Monolithic System
• Need Capability to Draw Different Functional
  Views from Common Data Base
• (Training, Job Aiding, Technical Reference, Parts
  Info, Configuration Management, etc.)

30

Interface with Other Job Aids

• Real-Time Link to Information Not Available at
  Job Site
• Consult with Shore-based Help desk
• Communicate with Manufacturer Technical
  Representative at Factory
• Order Parts On-Line
• Link to Diagnostic Testers
• Access to a Virtual Environment for Maintenance
  Training (I.e., Simulation)

31
(No Transcript)
32
Summary

• Employ Web-Based Approach to Integrate IETM,
  Just-in-Time Training, Parts Ordering, Other
  Lifecycle Support Info into Single Data Base
  Accessible at Job Site
• Benefits
• Seamless Parts and Diagnostic Support
• Reduced Classroom Training
• More Current Training Tailored to Job
• Increased Job Performance Uptime

33
Future Work

• Need to determine how to effectively implement
  and secure maximum benefit from Joint IETM
  Architecture (JIA) compliant maintenance
  information applications by converting them to
  active applications on the emerging Defense
  Information Infrastructure consistent with
  DII/COE, GCSS, and JCALS capabilities and
  requirements.

34
Solution Needed

• Unite isolated intranets and stand-alone
  applications, which implement the JIA, by
  employing them on the Defense Information
  Infrastructure (DII). Global JIA compliant
  networked solutions will be produced by
  converting to and/or building on the emerging DoD
  Infrastructure with applications and servers
  operating as part of the Global Combat Support
  System (GCSS). First priority -
• On-Line Distribution and Update

35
AS-IS Model
IETM Management Activity
36
IETM Management Activity
TO-BE Model
DII/JCALS/GCSS
GOALS Much Less Computer Administration, Much
Faster Distribution, More Current Data in Field
37
E-MailJORGENSENEL_at_NSWCCD.NAVY.MIL