Post on 13-Oct-2014
MAXIMO Version 6(MXES or MAXIMO Enterprise)
Tim Taber, PEStearns & Wheler, LLC
Wednesday, May 17, 2006SOUTHEASTERN MAXIMO USERS GROUP (SMUG) MEETING
Agenda� Poll – What Version of Maximo Do You Use?� Maximo Versions – Timeline� MXES
� Architecture Differences� User Interface� Workflow and Database Configuration� Multi-org and Multi-site� Modules and Applications� KPI’s� Security� Reporting
� Upgrading to MXES
Maximo Version Poll
�MXES�MAXIMO 5.2�MAXIMO 5.1�MAXIMO 4.11�MAXIMO 4.1�Other
Maximo Timeline 1
OCT – DEC ‘04 JAN – MAR ‘05 APR – JUN ‘05 JUL – SEP ’05
MAX 5.2 P3
MAX 4.1.1 P7
MAX 5.2 P4MAX 5.2 P2A
Maximo EnterpriseSuite
MAX 5.1 P3 FinalLocalizations
MAX 5.1 P5 MXES 6.0.02(+ 4 Configurations)
MXES 6.0.01(+ 4 Configurations)
MXES Mobile
March 25, 2005
Maximo Timeline 2
OCT – DEC ‘05 JAN – MAR ‘06 APR – JUN ‘06 JUL – SEP ‘06
MXES Upgradesfrom MAX 4.1.1Oracle, English
MAX 5.2.06 MAX 5.2.07
MRO EstimatedRetirement Dates
5.1 Mar 20054.1.1 to 5.2 UpG Jun 20064.1.1 Dec 20065.2 Dec 2007
MRO EstimatedRetirement Dates
5.1 Mar 20054.1.1 to 5.2 UpG Jun 20064.1.1 Dec 20065.2 Dec 2007
MAX 4.1.1 P8 (TBC)
MXES Upgradesfrom MAX 5.1/5.2
All SQL Server (TBC)
MXES 6.0.03 MXES 6.0.04
“Harrier”MXES 6.1
���� FY07
MAX 4.1.1 Java Apps P7
MAX 5.2.05
MXES Upgrade Schedule
Evolution of Maximo Extended Enterprise Suite.� 4.0 Series
� Centura based client-server application.� 4.1 Series
� Hybrid of Centura and Java.� Home grown java application server – MXServer.� More Centura applications than Java applications.
� 5.0 Series� Still a hybrid of Java and Centura.� Started using commercial application servers such as weblogic and
websphere.� More java applications with a few Centura apps still pending conversion.
� 6.0 Series� Complete Java based solution – 100% ( excluding third party tools).� Large number of applications, Help Desk, ITAM etc.
MXES Architecture�Multi Tier architecture.�Clear logical separation of layers.�Built from ground up.�Built on J2EE Platform and is standards based.�Java, XML, Dynamic HTML, Java Server Pages (JSP)�Uses Commercial Application Servers such as
�Weblogic, WebSphere.
�Enables centralized systems.�Multiple Orgs, Multiple Languages etc.
�J2EE Verified Enterprise Application.
MXES – User Interface Changes� In MXES, the User Interface framework has been completely
redesigned.� It is based on XML definition and uses dynamic html.� The screen layouts are stored in the database in a xml
document format.� No need to have multiple sets of jsp pages to support multi-
language.� In multi language setup, an user can change the language
preference and the UI will display the labels and text in that language.
� No need for any java/applet on the client side, except in the case of workflow designer
MXES – UI Changes
MXES – UI Changes
Workflow and Escalation Enhancements� Workflow functionality is completely re-designed.� MXES supports all objects for workflow.� Workflow is completely Java and Browser based.� Escalation application has been added.
� Helps in automatic process monitoring.� Helps in condition monitoring such as lease expiration etc.
� Escalation application helps in applying Service Level Agreement ( SLA ).
Workflow and Escalation Enhancements
Database Configure Changes� Database configure has been completely redesigned.
� Supports the new Maximo data dictionary changes I.e. Objects, Attributes, Views.
� In order to use the new configure, one needs to understand the relationship between tables and objects.
� In MXES, all relationships are stored in the database, hence they are configurable through db configure.
� Database configure application can only setup the configuration.You cannot configure the database from the application.
� Command line utility is the only way to configure the database.� ConfigDB is available under mxes\tools\maximo.
� Maximo application server(s) have to be shutdown for configdb to run.
MXES Data Dictionary
Database Configuration Application
Mul
tisite
Cap
abili
ties –
MA
XIM
O 5
x M
odel
Site 7Site 7Site 7Site 7
Dat
abas
e/Ente
rpri
se
Org
aniz
atio
n 1
Org
aniz
atio
n 3
Org
aniz
atio
n 2
Site 6Site 6Site 6Site 6
Site1Site1Site1Site1
Site 2Site 2Site 2Site 2
Site 3Site 3Site 3Site 3
Site 4Site 4Site 4Site 4
Site 5Site 5Site 5Site 5
Viewing Data� Users no longer log into a Site
� Users log into Maximo
� View data based on security
� Users can have different privileges in different Sites
Searching for Records in MXES
Searching for Records in MXES
Sharing Data Across Organizations
Set Related Data Applications
�Item Master�Tools�Company Master�Master PM�Job Plans
Centralized Purchasing
PR – Site 1
PR – Site 2
PR – Site 3
PO – Site 4
Receiving – Site 1
Receiving – Site 2
Receiving – Site 3
Invoice – Site 4
Maximo 5 – EAM Capabilities
Asset Management
Reporting / KPIs / Analysis
Work Management Materials Management Purchasing
LocationsEquipmentFailure CodesCondition Monitoring
Request for QuotationReceivingPurchase RequisitionsInvoicesPurchase Orders
Item MasterStoreroomsInventory Issues & Transfers
Job PlansRoutesWork RequestsService ContractsWork Order TrackingWork RequestsSafetyQuick ReportingLabor Lock-Out/Tag-Out Tools / Crafts/ CompaniesPreventive MaintenanceAssignment Manager
Workflow
Maximo Enterprise Suite – EAM CapabilitiesAsset Management
Reporting / KPIs / Analysis
WorkManagement
Materials Management Purchasing
LocationsAsset Failure CodesCondition MonitoringMetersMeter Groups
Request for QuotationReceivingReceiving InspectionsPurchase RequisitionsInvoicesPurchase OrdersDesktop Requisitions
Item MasterStoreroomsInventory • Lot Management• KittingIssues & TransfersCondition CodesStocked ToolsService Items
Job PlansRoutesService RequestsService ItemsWork Order Tracking• Services on JP & WOService RequestsSafetyQuick ReportingLabor • Multi SkillsLock-Out/Tag-Out Tools /Crafts/CompaniesPreventive MaintenanceMaster PMAssignment Manager
Enhanced Workflow – Event Driven, Context-based / Escalation Manager
Contract Management
Purchase ContractsMaster ContractsWarranty ContractsLease/Rental ContractsLabor Rate ContractsPayment Schedules
Service Management
Service CatalogsSLA Management
Asset Management Enhancements� Asset Move / Modify Enhancements
� Equipment renamed to Assets� Plan and Execute Asset Moves on WOs� Plan and Execute Asset Specification Changes on WOs� One Step Asset “Swaps”� Asset Moves Across
Organizations� Assets are now status-
able
Meter (and Condition Based) Enhancements� New Meter Application w/ multiple types
� Continuous - Meter Based PMs (e.g. Hour Meter, Fuel Meter)
� Gauge - Condition Based PMs (e.g. Temperature, Pressure)
� Characteristic - Condition Based PMs (e.g. Oil Color, Flame Color)
� Meters Assigned to Assets and / or Locations
� Multiple Meters per Asset or Location
� Multiple Meters per PM
Work Management Enhancements� Services Enhancements
� Services Used on Job Plans and WO� Lump Sum and Unit Cost Services� e.g. HVAC Service, Landscaping Service
� Services Linked and Managed from Contracts Module
Labor and Crafts Enhancements� Craft/Labor Skill Levels (Apprentice, Journeyman,
etc.)� Labor can have Multiple Crafts
� Qualifications and Certifications� Supported in WOs and Assignment Manager
Inventory Enhancements� Item Tracking by Condition
� e.g Tire Tread Depth; or New, Used, Rebuilt
Inventory Enhancements� Item Kitting Enhancements
� Items grouped and managed in the Storeroom as a “Package”
Inventory Enhancements� Material Inspections on Receipt
Tool Management Enhancements� Tool Management Module
� Stocked and Rotating
Application Designer
Application Designer� New Application called App Designer has been developed.� The App Designer is a GUI based application that helps in
creating and modifying application layout without changing any code.� Drag and drop functionality.� Before MXES this had to be done by modifying the JSP
pages.� This is extremely powerful for making rapid changes to
application screens and deploying.� Since screens are multi-language enabled, single screen change
can handle all languages.
KPI Manager Application� Easily build
KPI reports
� KPI’s can be displayed on the Start Center
KPI Manager Application - Trending
Security Changes� Security is an area that has been completely redesigned in MXES.
� User authentication changes.� LDAP/ Single Sign on.� User application changes.
� Database authentication used before.� Now have Maximo internal authentication (default).� Can use external authentication through LDAP servers. Active
Directory is supported.� End users are no longer created as database users.� Pre-MXES users logged into a single site, but now an user logs
into the system.� User has a default site setting, but is allowed to access any sites/orgs that
the user has access.� Framework applies the user security to the sql statements.
Security Profile� In MXES, user does not login to a specific site. User
logs into the system.� While logging in, a profile is built.
� List of sites, sets etc. is built.� The profile contains all the security access and
authorization information.� Use MyProfile application to change settings.
� Default Insert Site� Query with default site.� Language – order of preference is profile, login page, base.� Timezone
Authentication Changes� New Maximo Authentication is introduced.
� Pre MXES, database authentication was used. Hence every Maximo user was created as a database user.
� In MXES, Maximo has it’s our own authentication ( by default ). The users are stored in MAXUSER tables and Java Encryption technology is used for password encryption.
� No more database users for every Maximo user.� Just one database user to connect to the database and access
the data.� Additionally there may be more database users for Report
admin/design purpose.
MXES Reporting
MXES Reporting ToolsPower Business Casual EnterpriseAdmin
Analyst,Engineer
ManagersPlanners
MaintenanceTech
Supervisor, Buyer
Report Producers Report ConsumersReport Producers Report Consumers
eRDPro
Parameterized Reports
Mgmt Console
Information Objects
Information Objects
Parameterized Reports
eSpreadsheet eSpreadsheetQueries
Report Admin
Developer
Admin: Report Management Tools
Actuate’s ManagementConsole
Maximo’s Report Admin App
Developer: erdPro
Power User: Information Objects
Business User: eSpreadsheet
Casual User: Queries
Use Query Wizard to create Individual, Unique Report
Enterprise User: Parameterized Reports
Maximo Report Admin Application
Maximo Lookups in Report Parameters
Maximo Query� Queries seamlessly incorporated to run like Reports
MXES Report Types
41%
18%
18%
15%
4% 4%
AnalysisListDetailQueryHierarchyCrossTab
Value Add Reports and Queries
Reports and Queries by Application
MXES Reports by Application
19%
14%
17%11%
9%
9%
8%
8%5%
Service Desk
Inventory
Work Mgmt
Asset Mgmt
Contracts
Procurement
IT Asset Mgmt
Misc
Labor
Should You Upgrade to MXES?� Ask the following questions:
� Are there features in MXES that we can’t live without?� How much do we have invested in our current version?
� Interfaces� Reports� 3rd Party (handhelds, GIS, TRM, Quickpick, etc.)� Training� Documentation� Support� Comfort Level
� How “Stable” is MXES?� How “Stable” or fool-proof is the upgrade from our version to MXES?
Should You Upgrade to MXES?� Yes – Put a plan in place to upgrade, whether it is in
the next year, or the next 3 years you should begin the planning.
Questions
�Where to get more information
Tim Taber, PEtptaber@stearnswheler.com
Contact me
http://www.mro-world.com/ugwelcome.htm
MRO User Conference
http://support.mro.comMRO Support Web Site