Professional Documents
Culture Documents
Maximo Overview
Maximo Overview
Tim Taber, PE Stearns & Wheler, LLC Wednesday, May 17, 2006 SOUTHEASTERN 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 KPIs 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
MAX 4.1.1 P7 MAX 5.2 P2A MAX 5.2 P3 MAX 5.2 P4
MAX 5.1 P5
OCT DEC 04
JAN MAR 05
APR JUN 05
JUL SEP 05
MXES Mobile
Maximo Timeline 2
MAX 4.1.1 Java Apps P7
5.1 5.1 4.1.1 to 5.2 UpG 4.1.1 to 5.2 UpG 4.1.1 4.1.1 5.2 5.2
MAX 4.1.1 P8 (TBC)
Mar 2005 Mar 2005 Jun 2006 Jun 2006 Dec 2006 Dec 2006 Dec 2007 Dec 2007
MAX 5.2.05
MAX 5.2.06
MAX 5.2.07 MXES Upgrades from MAX 4.1.1 Oracle, English MXES Upgrades from MAX 5.1/5.2 All SQL Server (TBC) Harrier MXES 6.1 FY07
MXES 6.0.03
MXES 6.0.04
OCT DEC 05
JAN MAR 06
APR JUN 06
JUL SEP 06
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.
MXES UI Changes
MXES UI Changes
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.
Site 3
Organization 1
Site 2
Database/Enterprise
Site 4
Organization 2
Site 5
Site 6
Site1
Organization 3
Site 7
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
Centralized Purchasing
PR Site 1
Receiving Site 1
PO Site 4
Invoice Site 4
PR Site 3
Receiving Site 3
Workflow
Work Management
Job Plans Routes Service Requests Service Items Work Order Tracking Services on JP & WO Service Requests Safety Quick Reporting Labor Multi Skills Lock-Out/Tag-Out Tools /Crafts/Companies Preventive Maintenance Master PM Assignment Manager
Materials Management
Item Master Storerooms Inventory Lot Management Kitting Issues & Transfers Condition Codes Stocked Tools Service Items
Purchasing
Contract Management
Service Management
Request for Quotation Purchase Contracts Receiving Service Catalogs Master Contracts Receiving Inspections SLA Management Warranty Contracts Purchase Requisitions Lease/Rental Contracts Invoices Labor Rate Contracts Purchase Orders Payment Schedules Desktop Requisitions
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
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.
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 its 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
Business
Managers Planners
Casual
Supervisor, Buyer
Enterprise
Maintenance Tech
Mgmt Console Report Admin eRDPro Information Objects Information Objects eSpreadsheet eSpreadsheet Queries Parameterized Parameterized Reports Reports
Report Producers
Report Consumers
Developer: erdPro
Maximo Query
Queries seamlessly incorporated to run like Reports
18%
How Stable is MXES? How Stable or fool-proof is the upgrade from our version to MXES?
Questions
Where to get more information
MRO Support Web Site MRO User Conference Contact me http://support.mro.com http://www.mroworld.com/ugwelcome.htm Tim Taber, PE tptaber@stearnswheler.com