Enabling Data and Analytics
for Enterprise Asset management (EAM)
Devang Patel & Arun Narayanan
SEAL Consulting Inc
Agenda:
What is EAM?
Business Challenges / Benefits
Why EAM?
Architecture
EAM Data Collection / Practice Area(s)
Input Data Set
What is EAM?
Enterprise asset management (EAM) is a broad term vendors use to describe software that provides managers with a way to view company-owned assets holistically.
The goal is to enable managers to control and pro-actively optimize operations for quality and efficiency.
In earlier years, EAM was simply called maintenance scheduling software.
EAMs facilitate operations by automating requests for upgrades, regular maintenance and decommissioning or replacement.
Assets in terms of EAM include all assets except financial assets like stocks or bonds, but typically refer to maintainable equipment.
Business Challenges / Benefits
In Depth value, analysis, & insight on current EAM process.
An opportunity to improve Business Processes surrounding,
Standard Data Processes.
Improvise Source(s) of Data by standardizing processes,
from which data is collected.
Opportunity for customers to Improve/Improvise
Maintenance Process.
Visualize Equipment Downtime at a manufacturing Plant.
Output the report with downtime/shutdown for each of the
Equipment during Production.
Why EAM - Solution?
With proper EAM Process, it allows customers the
ability to assess the true state of their organization
with one common deliverable, a comprehensive
report identifying improvement opportunities with
asset data, maintenance processes and SAP
system issues.
Proper and more consistent way of managing
Enterprise Data.
Reduced downtime at a production plant or
Reference - Architecture
SAP
Maximo
SLA
Non-SAP
Source Specific Template Source Specific Template Source Specific Template Source Specific TemplateM
AP
SAP Data Services
SAP
Best
Practices
Business
Rules
Filters
SAP HANA
Dynamic
Reporting
Tool
(Xcelcius
Dashboards
)
RDBMS
EAM – Implementation Focus Areas
Data Capture
Capturing missing equipment information through the physical verification/inventory of plant equipment using handheld computers pre-loaded with equipment data.
Capturing missing equipment information located in unstructured sources . . . Process & Instrumentation Diagrams, Process Flow Diagrams, engineering drawings, etc.
Consolidating and Organizing Data
Defining and implementing equipment hierarchies standards.
Defining and implementing appropriate equipment in a consistent ways to name equipment, noun/modifier, equipment class, etc.
Adding missing equipment attributes, for example, OEM part number, physical characteristics, etc.
Adding unique identifiers to equipment using barcode and RFID technologies.
Combining and standardizing multiple databases.
Building Bill of Materials.
Data Cleansing
Completeness: Descriptions, Manufacturer, Model, Part Number, etc.
Consistency: Standard abbreviations and terms, naming conventions
Conformity: Checks against the data dictionary with comparison to standards
Duplication: Exact matches, exact substitutions, & functional equivalents.
Data Migration
Data mapping between any combination of source and target: JD Edwards to SAP, Maximo to SAP, Maximo to Oracle, Legacy Mainframe to SAP, etc.
Mergers & Acquisitions: Speeding business integration