Cals EXPO 99 PowerPoint Presentation

1
21st Century Commerce Expo
The Night Owl Circuit
Joint IETM Interoperability Architecture
(JIA) Update Report
Wednesday, December 1, 1999
R. S. Kidwell VP/Sr. Technical Director ManTech
International
Mr. Eric Jorgensen IETM Technology Manager Naval
Surface Warfare Center
2
Our Agenda
The Night Owl Circuit

• Working Group Update Report - - - - - - R. S.
  Kidwell
• IETM Direction in the 21st Century - - - Eric
  Jorgensen

Your Questions
www.dcnicn.com
3
THAK Creator Of The Phenomenon Know As I
EATUMS
Y2K / Millemum
4
Joint IETM INTEROPERABILITY Tri-Service IETM
Technology Working Group
5
Our Government / Industry Team
Joint IETM Architecture (JIA) Government/Industry
Interoperability Team
6
Tri-Service IETM Technology Working Group A Work
In Progress

• Chartered by DUSD(L)/LRO and Supported
• by DoD/JECPO
• Purpose Provide Technology and Common approach
  for acquisition of IETMs
• Membership Army, Navy, Air Force, USMC
• Tasked to Develop Common Uniform Approach for
  Acquiring and Viewing Interoperable Technical
  Data (IETMs)

7
Current Situation
8
DoD Direction is _ _ _ Digital

• DEPSECDEF Memo of 2 July 1997 Subj Policy for
  the Transition to a Digital Environment for
  Acquisition Programs
• By the end of 2002, the overwhelming majority of
  DoD acquisition and logistics operations should
  be based on digital methodologies and products.
• In accordance with Joint Vision 2010

9
The Need for Interoperability
10
IETM Interoperability Problem

• Individual Presentation Systems can only display
  information specifically authored for that
  presentation system
• MIL PRF 87268 / MIL PRF 87269 Degree of
  Interpretation
• No standard way to electronically link to and
  easily access other ETMs
• Lack of uniform approach to sustain war-fighting
  capability in joint operations

11
Requirement for Interoperability Has Been
Identified By

• Navy F/A-18 Program at Naval Postgraduate School
  IETM Workshop in Aug 1996
• Tri-Service IETM Technology Working Group in Dec
  1996
• Joint Logistics Commanders Memo to DUSD(L) of 10
  June 1997
  

IETM
12
Joint Commanders Group for Communications
Electronics (JCG-CE) Electronic Technical
Publications Panel
Mr. S. William Lewis Panel Chairman
13
JLC Goal for IETM Interoperability

• A uniform approach which will permit dissimilar
  DoD weapon-system IETMs, regardless of the
  source, to be read and viewed on a common
  user-interface system
• Develop a uniform approach for electronically
  communicating and accessing technical DoD
  throughout DoD
• Maximize the use of Commercial Off-The-Shelf
  technology
• Develop a common user /information interface for
  Field Delivery Systems

14
IETM Interoperability

• Ability of Dissimilar Systems to be
• Linked together and
• Operate as a single entity
• Multiple levels / degrees of Interoperability
• Technical consideration(s)
• Cost/Business case model consideration(s)

15
IETM Interoperability
Levels of Information Exchange
Information Exchange
Level
Computing Environment
Distributed Global Info Apps Simultaneous
Interactions w/ Complex data Advanced
Collaboration e.g., Event-triggered global
database update Shared Databases Sophisticated
Collaboration e.g., Common Operational Picture
(COP) Heterogeneous Product Exchange Group
Collaboration e.g., Exchange of Annotated
Imagery Maps w/ overlays Homogeneous Product
Exchange e.g., FM Voice, tactical data
links, Text file transfers, e-mail,
messages Manual Gateway e.g., diskette, tape,
hardcopy exchange

• 4 Enterprise
• Interactive Manipulation
• Shared Data Applications
• 3 Domain
• Shared Data
• Separate Applications
• 2 Functional
• Minimal Common Functions
• Separate Data Applications
• 1 Connect
• Electronic Connection
• Separate Data Applications
• 0 Isolated
• Not Connected

Ref ISR Architecture Framework, Version 2.0 DoD
C4 ISR Working Group
16
Opportunities Provided by Interoperable IETMs

• Provide user with single interface to all
  Information needed to perform job
• IETM Become Integrated Applications
• Effective support of Joint Operations as required
  by Joint Vision 2010
• Building blocks for Integrated Logistics
  Information and Support Systems
• Support emerging telecommunication technologies,
  e.g., telemaintenance

17
Technical Approach The Joint IETM
Interoperability Architecture JIA
18
Technical Approach

• Use WWW/Internet technologies, approach, and
  experience which has made successful transition
  from paper to electronic media
• Deploy on dedicated DoD Intranets
• Use standard URL format to electronically
  facilitate IETMs accessibility to all authorized
  users
• Consistent with increasing DoD use of Web
  technology in C3, Paperless Contracting,
  Logistics Information Systems, etc.

19
Project Scope

• Applicable to all Services
• All ETM/IETM Formats currently in use (e.g., PDF,
  Raster, HTML, AIMSS, QUILL, JIMIS, TechSight,
  etc)
• Legacy new IETMs
• Legacy IETMs are major concern due to hundred
  million dollar investment

20
Project Objectives

• Demonstrate technical feasibility of making
  legacy IETMs Web-enabled
• Recommend IETM interoperability policy applicable
  to DoD legacy and new IETMS
• Develop Handbook to guide implementation

21
Project Approach

• Build on Navy IETM Architecture
• Assess current/planned Service IETM programs and
  actions needed to achieve interoperability
• Develop Joint IETM Architecture (JIA)
• Conduct pilot demonstrations on Service programs
• Develop recommended policy and interoperability
  standards

22
The Joint IETM Interoperability Architecture (JIA)
Objective2
Objective1
To Create a High Level Joint IETM Architecture
to Guide and Standardize IETM Acquisition, Managem
ent, Display, And Interoperability Legacy
Programs/New Acquisition Programs
Utilize the Principles of Object
Technology Objects/Object Encapsulation To
Capture, Maintain And Distribute IETM VIA
www/ Internet Technologies
23
Object Orientation
Object
An Object is a Representation of a Real
World Person, Place, Thing, or Event Cars
Coffee Machine Ducks Trees
Encapsulation
A Process or Technique in which Data is Packaged
Together with its Corresponding Procedures
(Software Re-usability)
24
Object Definition

• Valid objects in IETM environment may include
• Maintenance or operation procedure
• Parts list and tools required for a procedure
• Engineering drawing, illustration
• Interactive dialog box
• Document, page
• Combination (view package)

25
The Object Challenge
Object Size
Delivery of encapsulated objects is made
more Difficult when the objects to be delivered
are very large. The encapsulation method must
provide A capability to create parts of an IETM
that are Manable in size.
Granularity / Chunking / Fragmentation
Concept for Object Encapsulation Prototype for
Interactive Electronic Technical Manuals
Pilot test that view object encapsulation of IETM
as a series of processes
26
The Joint IETM Interoperability Architecture (JIA)
Infrastructure
Encapsulated Object
IETM Data
IETM Data
IETM Data
Authoring Systems
Client/Server Architecture VIA www / Internet
Technologies
27
JIA End User Profiles
Network Connection
Shore/Aircraft/Ship
Occasionally Connected User
Aircraft/Ship/Soldier
IETP/IETM
Soldier
CD-ROM
28
Service Demonstration Programs
29
Service Demonstration Programs
Apache Longbow
JSTARS IMIS
AAAV
NSSN
F/A-18A
LM - 2500
Other Demo Programs AN/PPS-5, EPLRS, E-6B,
LINK-16, F-22, AF MPTO, TMSS, TAOC,
Diode Test Set
30
Military Service Position Paper
31
Military Service Position Paper

• Identifies 16 major projected benefits resulting
  from JIA implementation
• Provides implementation recommendations
• Endorsed by designated Service Representatives of
  Army, Navy, Air Force, and Marine Corps

Apache
32
Benefits
33
Benefits

• Accommodates Online Training
• Accommodates Use of Paper-Based and Electronic
  Legacy Data
• Ability to View/Use Someone Elses Data
• Framework for Application Interface to Other
  Software Systems

• Accommodates Global Access to Technical
  Information
• Reduced Dependency On, And Maintenance of,
  Custom/Proprietary Authoring and Delivery Systems
  
• Single-User Interface to All Needed Technical
  Data
• Utilizes Planned DoD Communications Security

34
Benefit To IETM User

• Each user needs only one interface to access all
  IETMs regardless of data format or authoring
  system.
• Single point and click access to any referenced
  IETM irrespective of format.
• No computer-system administration needed to load
  IETM Software on user device.
• Rich search capability for all IETMs no matter
  what the run-time format.

35
DoD Working Group Summary
36

• IETM Interoperability Handbook
• Formal Coordination of Handbook by May 2000.
• Army LOGSA is Preparing Activity

Based On
37
Technical Approach Compatible with Existing DoD
Initiatives

• Global DII
• DoD Community-Specific Intranets
• GCSS Services
• JCALS
• GNIE enabler
• JTA
• PKI

NSSN
38
IETM Systemic Test Demo(s)

• Capabilities Needed to Implement the
• JIA Information Technology Architecture
• Infrastructure

• Information Content Delivery (PUSH)
• Software Object Delivery
• Browser Identification and Detection
• Information Content Addressing (linking)
• Server Fail Over Process

39
IETM Object Encapsulation
Can We View It As A Structured Process With Cost
Estimation / Metrics?

• The Challenge
• Data Types
• Object Size
• Infrastructure
• Run Time Environment
• Interface Definition
• Encapsulation Languages / Models
• XML
• COM, COM
• DOM
• Prototype

40
JIA To Achieve Minimum 30 IETM Life-Cycle
Reduction

• JIA Will Achieve 30 Minimum Reduction in Time
  and
• Cost of Deploying and Using IETMs
• Reduce Acquisition and Maintenance Costs with
  Common
• Viewer - Buy Once/Use Many Times Free
  Versus Seat
• Management (400 per month)
• Recovery of Investment Cost in Legacy Data for
  Timely
• Distribution to End-User 35 reduction cost
  per page for
• electronic over Life-Cycle
• Interoperability Factor Provides for two or
  more Dissimilar IETM
• Applications to be Viewed by End-User one
  versus all
• Reduced Time and Cost for Distributing and
  Maintaining IETMs
• average 120 days versus 5 days
  emergency 3 days versus
• hours

41
Change in DoD IETM Business Practices
As-Is
To-Be The JIA

• Standalone Customized
• (Proprietary) Limited Capability
• with No Degree of Integration
• or Interoperability
• High and Unpredictable
• Life-Cycle Cost
• Non-Existent IETM Life-Cycle
• Change Distribution
• Independent Limited
• Security
• Field Deployable in Stand Alone
• Mode Only

• Facilitate Fully Integrated
• Application and Multiple
• Levels of Interoperability
• for the End User
• Predictable and Mainstream
• Acceptable Life-Cycle Costs
• Timely IETM Life-Cycle
• Change Distribution
• Fully Operative Secure
• Networks
• Networked and Mobile User
• Support (Portable Electronic
• Display Device)

F-22
42
JIA Has Global Applicability

• DoD (CONUS, Overseas, all Services)
• Other Government Departments
• Private sector
• International

43
Actions Needed

• The Tri-Service IETM Technology Working Group
  recommends that to obtain full benefits from the
  JIA it will be necessary for the Services and DoD
  to take at a minimum the following actions
• Issue JIA Policy at the DoD Level
• Issue JIA Military Handbook
• Draft JIA Annex to DoD JTA
• Assign allocation authority for Electronic
  Addressing to each Service
• Develop Individual Service JIA Implementation
  Strategies
• Apply to Suitable Existing/Planned Infrastructure
  (i.e., Service Component of DII)

44
21st Century Commerce Expo
The Night Owl Circuit
Joint IETM Interoperability Architecture
(JIA) Update Report
Wednesday, December 1, 1999
Thank You Ladies and Gentlemen
R. S. Kidwell VP/Sr. Technical Director ManTech
International
Mr. Eric Jorgensen IETM Technology Manager Naval
Surface Warfare Center