You are on page 1of 25

Electronic Maintenance System (EMS)

Next Generation
Overview & Demonstration

for
CBM Workshop
November 28-29 2007

Hernan Olivas
EMS Program Manager
ONeil & Associates
Committed
Committed to
to Excellence
Excellence
Supporting
Supporting America
Americas Warfighters
Americas Warfighters
Agenda
Scope of EMS Applications
EMS Requirements-Toolset
Operational Overview
System Configuration
Autonomous Diagnostic Manager (ADM)
IETM session
Session Outputs
Supporting CLOE and CBM
Q&A
Backup
Scope of EMS Applications
The EMS NG Requirements
Recast the application to fit the need.
Repurpose product support data for use across weapons
system families and functions.
Reduce Lifecycle Cost to author and update.
Leverage the benefits by integrating traditionally isolated
systems and product information maintenance, parts,
training, ERP, warranty, and diagnostics.
Standards compliant:
40051-1 and 2 - 3008A
2361C -Mimosa (Future)
EMS NG - Toolset
EMS NG Operational Overview
EMS NG CMS

EMS NG User

EMS Web
Portal
Stage I Stage II Stage III
Developing Managing Publishing
(CDS) (CMS) (CGS)

Content in Progress

Stage IV
Content Distributed

EMS NG Viewer
Stage VI
Stage V Reporting
Presentation
System Configurations

Protocol EMS Diagnostic


Adapter Module ADM

Graphic User Interface


Autonomous Diagnostic Manager (ADM)
Context Filtering

Selecting a specific manual allow you to filter the content so that the IETM
presents only information pertinent to the system the maintainer is working on.
Diagnostics

Troubleshooting is
performed using a
fault logic tree and
intrusive
diagnostic, taking
advantage of
system buss
traffic to capture
fault codes and
measurements.
Maintenance Procedure

Maintenance procedures provide remove and replace instructions


with linking capability to additional information and parts (RPSTL).
Parts Information (RPSTL)

From the parts


information
screen the
maintainer
can add parts
to the
shopping cart.
Parts Ordering

Shopping cart allows the maintainer to associate the part to the fault
conditions and to create a form 5988-E
MIL STD 3008A Data Table 1. Equipment Type Data
1. Administration Number: Retrieved from ETM-I database, or from user, at login.
2. Bumper Number: Supplied from user at login.
3. Serial Number: Retrieved from ETM-I database, or from user, at login.

Table 2. Equipment Assignment Data


1. DODAAC: Retrieved from ETM-I database, or from, user at login.
2. Unit Identification Code (UIC): Retrieved from ETM-I database, or stored user information, at login.
3. Unit/Activity: Retrieved from stored user information at login.

Table 3. Personnel Data


1. Name: Retrieved from stored user information at login.
2. Rank: Retrieved from stored user information at login. Takes priority over Grade.
3. Grade: Retrieved from stored user information at login unless Rank is provided.
4. Job Title: Retrieved from stored user information at login.
5. Social Security Account Number (SSAN): Retrieved from stored user information at login.
6. Personnel Identifier (PID): Supplied by user at login.
7. Military Occupational Specialty (MOS): Retrieved from stored user information at login.
8. Unit/Activity: Retrieved from stored user information at login.

Table 20. IETM Fault Result Data


1. Fault data: Fault associations with parts when parts are ordered.
a. Xref attribute: used to link fault code association with parts ordered.
b. Symptom: Chosen from list of approved symptoms by user upon parts ordering
c. Description: Plain text representation of fault code.
d. Fault Code: Chosen from list of approved symptoms by user upon parts ordering.
e. Date: Time that the part was ordered.
f. How Recognized: Chosen from list of approved codes by user upon parts ordering.
g. Failure Mode: Chosen from list of approved codes by user upon parts ordering.
2. Test/Troubleshooting (Automated Test):
a. Date: System timestamp from when test was preformed.
b. Time: System timestamp from when test was preformed.
c. Test Name: Name of automated test preformed.
d. Test Description: Equipment Manufacturer and Model tested.
e. Protocol: List of protocols used in automated test.
f. Parameters: List of parameters used in automated test.
g. Measurement: List of results from automated test.
3. Test/Troubleshooting (Troubleshooting Track):
a. Date: System timestamp from when test was preformed.
b. Time: System timestamp from when test was preformed.
c. Test Type: tshoot if beginning of troubleshooting track, branch if results of a troubleshooting node.
d. Description: dest describing following parameter if troubleshooting branch .
e. Parameters: Work package number and troubleshooting track node.

Table 21. IETM Maintenance Reporting Data


1. Parts Data Ordered Data:
a. Xref attribute: Used to link part order to fault code association.
b. Part Number: Selected from RPSTL data by user at part ordering.
c. Part Name: Supplied by RPSTL data at part ordering.
d. SMR Code: Supplied by RPSTL data at part ordering.
e. CAGE Code: Supplied by RPSTL data at part ordering.
f. NSN: Supplied by RPSTL data at part ordering.
g. NIIN: Supplied by RPSTL data at part ordering.
h. Quantity: Supplied by user at part ordering.
i. Date: System datestamp of when parts where ordered.
j. Time: System timestamp of when parts where ordered.
2. Maintenance Action Preformed (Used to associate with parts ordered):
a. Type Action: IETM link to work package and work package title.
b. Date Preformed: System datestamp of when parts where ordered.
EMS Supporting CLOE & CBM
Common Logistics Operating Environment (CLOE)
& Condition-Based Maintenance (CBM)
Maintenance Data Collection - entire troubleshooting, maintenance
and parts ordering session logged and time/date stamped:
Maintainer ID
Vehicle ID
DODAAC
Symptoms At-Platform Embedded
Tests & Test Results
Diagnostic Path
Isolated Faults
Maintenance Action
Parts Consumed

Autonomous Diagnostic Manager (ADM) stand-alone application SAMS-E


serving any client: EMS, IADS, VHMS, VCS, VIDS etc. CBM Data Warehouse
Databus Protocol/Formats: J1708/J1587, J1850, J1939 (and CAN),MIL-M-
1553, RS 232 (OTC VIM), DCA
Engines DDECII, DDECIII, DDECIV (FMTV, M915) Caterpillar C-3126B, C7 Digital Logbook
(FMTV), C-12 (MTVR), C15 (HEMTT), 3126A (STRYKER)
Transmissions ATECI, ATECII (FMTV) WTEC all versions up to Gen 4), Digital PMCS
GM4L80E (HMMWV)
Antilock Braking System (ABS) Eaton and WABCO FBCB2
Central Tire Inflation System (CTIS) Eaton
MTS

VHMS
EMS NG

Q&A

Backup Slides
System Architecture
Phase III Phase II

Phase I
System Infrastructure
User Portal
System Hierarchy
Roles and Privileges
Abilities
System Administrator
Rights - Manage Vendors
(TACOM)
- Approve Documents
- Includes Rights of Lower Levels

Abilities

- Manage Projects
- Monitor Projects (Reports)
- Manage Document Groups
Vendor Administrator - Manage Document Properties
Rights
(OTC) - Manage Workflows
- Manage Roles
- Manage Users/Memberships
- Manage Permissions
- Manage System Settings
- Includes Rights of Lower Levels

Abilities

- Create/Manage Documents
Author
Rights - Manage Document Status
(Jane D.)
- Publish Documents
- Search
- Manage User Settings
Using Web Technologies
Content Development

Stryker IETM Example Shelby


London,
Ontario
Township, MI
Web Portal Authoring Sterling
Heights, MI PM Stryker
Web Review & Approval TACOM
Rock Island

TACOM LCMC
Warren, MI
Content Management System (CMS)
and Web Portal

Alexandria, VA
Goleta, CA

San Diego, Huntsville, AL


CA
Using Web Technologies
Potential Information Distribution

TACOM LCMC
Warren, MI
Web Portal

WWW distribution of content and software


User pulls information from website
Other updates are pushed to user
Changes could be posted daily
Using Web Technologies
Content Management

TACOM LCMC
Content Management Server
and Portal
EMS NG MADS Architecture