Maintenance Record Virtual Exchange United States Navy MRVEUSN

1
Maintenance Record Virtual Exchange United
States Navy (MRVE-USN)

• Prototype Demonstration

Mark Persinger, Systems Engineer ManTech
International Wednesday, Sept 22nd 2004 AFEI
Enterprise Integration Expo
2
What is MRVE-USN About?

• Developing an electronic exchange of H-60
  Seahawk Helicopter maintenance-related
  information between Naval Aviation Command
  (NAVAIR) and Sikorsky Aircraft Corporation (SAC)
  with a longerterm goal of includingother
  stakeholders fromthe H-60 community and
  eventually other weapon platforms

3
Outline

• Purpose and Objectives of MRVE-USN
• Enterprise Information Interoperability (EII)
• ManTech Enterprise Information Interoperability
  Methodology (MEIIM)
• Navy Maintenance Background
• As-Is Architecture
• To-Be System Architecture
• Developing an EII exchange
• EII example of supporting a business process
• Illustration of a data exchange
• The Bigger Picture
• Conclusions

4
Purpose of MRVE-USN

• Future Logistics Enterprise (FLE) calls for more
  effective approaches to dealing with
• enterprise integration
• application interface maintenance
• total information systems life-cycle management
• Effort sponsored by the Office of the Assistant
  Deputy Under Secretary of Defense to further the
  discipline of Enterprise Information Integration
  (EII) and is part of the Logistics Enterprise
  Virtual Exchange Layer (LEVEL)

5
Objectives of MRVE-USN

• Near Term
• Show the electronic automation of this
  information exchange
• Demonstrate the principles of the EII discipline
  by
• Focusing upon the metadata, context, and
  semantics of the data to create an accurate
  information exchange that is context sensitive
• Creating a loosely-coupled solution that causes
  minimal intrusion into legacy systems
• Showing the use of Commercial-Off-The-Shelf tools
  to facilitate this exchange
• Long Term
• Building an EII environment for the H-60
  community, and beyond

6
About EII

• Enterprise Information Interoperability (EII) is
  the capability to exchange information between
  disparate and heterogeneous applications based on
  semantics and context.
• Key characteristics of EII include
• The use of design time and run time metadata
  (ontologies, virtual models, or neutral models).
• Information interoperability engineering, which
  leverages the metadata from the previous bullet.
• Context sensitivity, which assumes that datas
  meaning is always bound to a particular context
  or perspective (usage and/or environment).

7
EII Advantages

• Enables true information exchange that allows
  application systems and user agents to access and
  operate with information in its native form and
  context.
• Enables interoperability among applications in a
  loosely coupled, non-invasive manner with minimal
  intrusion to legacy applications.
• Helps companies better leverage their existing
  Information Technology (IT) investments.
• Dramatically reduces the time and cost to
  collaborate and exchange information.
• Significantly reduces the risk of implementation
  failure.

8
Electronic Logistics Information Trading Exchange
(ELITE)

• MRVE-USN builds upon the ELITE which provides an
  electronic exchange of maintenance record
  information between the Aviation and Missile
  Command (US Army) (AMCOM) and Sikorsky Aircraft
  Corporation

9
Methodology for Developing MRVE-USN
www.meiim.com
10
Navy Maintenance

• Naval Aviation Maintenance Program (NAMP)
  dictates the keeping and use of extensive
  maintenance records to promote aircraft
  performance and safety
• Certain components are deemed so essential to the
  performance and/or safety of the aircraft that
  they are removed and replaced at regularly
  scheduled intervals (Life Limited Items)
• As an example for this demonstration, we will
  focus upon on the information contained on just
  one Navy maintenance form

11
Navy Maintenance (Continued)

• The information concerning the use and
  maintenance history of these components are
  tracked with a form known as the OPNAV 4790-28A
  Scheduled Removal Component Card (SRC Card)
• Each serialized component has its own SRC Card
  and while in use the card is kept in the Aircraft
  Logbook of the Aircraft on which it has been
  installed
• The card accompanies the component throughout its
  lifecycle. From creation, repair, use on other
  aircraft, to its disposal.

12
SRC Card Data
13
SRC Card Data Page 2
14
Supporting Component Repair Business Process

• Consider a component that is currently on an H-60
  Seahawk
• The part fails or reaches its scheduled life and
  can be repaired by the manufacturer
• The part and its accompanying SRC Card that
  contains important life-cycle information are
  returned to SAC for repair

15
As-Is System Architecture

• Currently this maintenance information is
  exchanged between the manufacturer Sikorsky and
  NAVAIR in paper format
• This requires manual entry of information by both
  organizations

16
To-Be System Architecture

• MRVE-USN uses a Level Adapter (LA) to facilitate
  the exchange of information

Navy
Sikorsky
LA
SAMS Sikorsky Aircraft Maintenance System
WFS Wholesale Foundation Server
17
Level Adapters (LA)

• Synonymous with an EXA in the ELITE
• Comprised of components including
• Interoperability
• Validation
• Security
• Transport
• Also can include Information Applications
• Example web interfaces, portals, etc.

18
Supporting Component Repair Business Process
(Continued)
LA
Step 1 The information set is transmitted to
the LA.
Step 2 SAC receives the information set from
the LA.
19
Methodology for Developing MRVE-USN
20
Developing an EII Exchange
21
COTS Tool - MetaMatrix
22
Databases used for this demo

• Two Oracle Databases were developed for this demo
  to act as information sources
• One representing what a NAVAIR database
  containing maintenance information may look like
• Sikorsky currently uses IN and OUT database
  tables to handle Army Maintenance data and this
  model is likely to be used for an exchange with
  NAVAIR
• In both databases it is assumed that these tables
  would be emptied after each transfer thus acting
  as temporary data holders just for the exchange

23
Physical Model of Each Information Source
Mock NAVAIR (WFS) Database with SRC Information
24
Transforming Physical to Virtual
Sikorsky SAMS Database for SRC Information
25
Virtual Model of Each Information Source
26
Adding Context
27
Physical Model of SAMS
Sikorsky SAMS Database for SRC Information
28
Virtual Model of SAMS
29
Transforming Physical to Logical
30
Creating a Virtual Model to accommodate the
exchange
31
SRC Information from NAVAIRs WFS
Section I Identification Data
Section II Installation Data
Section III Removal Data
Section V Repair / Rework / Overhaul
32
Example of NAVAIR Submitting Information to
Exchange using Web Interface
33
Procedure to Transfer Information
Transfer Information from NAVAIR to SAMS
INSERT INTO MOCKSAMS.NAVAIR4790IN
(MOCKSAMS.NAVAIR4790IN.NMNCLTR,
MOCKSAMS.NAVAIR4790IN.PART_NUMBER,
MOCKSAMS.NAVAIR4790IN.SERIAL_NUMBER,
MOCKSAMS.NAVAIR4790IN.CAGE, MOCKSAMS.NAVAIR4790IN.
REPLACEMENT_INTERVAL
34
Supporting Component Repair Business Process
(Continued)
LA
Step 1 The information set is transmitted to
the LA.
Step 2 SAC receives the information set from
the LA.
35
Transfer Repair Information to NAVAIR from SAMS
36
SAC Repair and Return

• SAC repairs component and updates maintenance
  information and electronically sends the updated
  maintenance information back to NAVAIRs database
  (Steps 3 4)

37
SAC Updates Component Information in SAMS
Section I Identification Data
Section II Installation Data
Section III Removal Data
Section V Repair / Rework / Overhaul
38
Sikorsky Submitting Information to Exchange
39
Information Inserted into NAVAIR Database (WFS)
Section I Identification Data
Section II Installation Data
Section III Removal Data
Section V Repair / Rework / Overhaul
40
The Bigger Picture
Can extend to other weapon platforms and
organizations
Once implemented, SAC will have electronic access
to Army and Navy H-60 maintenance information
Also models created in MRVE-USN and ELITE pave
the way for Army-Navy information collaboration
41
Conclusions

• MRVE-USN furthers the development of an EII
  environment for the H-60
• Information richness, structure, context
• Automation of this information exchange produces
  long term time savings and errors
• Minimal Intrusion into legacy systems is required
  for implementation
• Show the use of Commercial-Off-The-Shelf tools to
  facilitate this exchange