Maximo Overview

  • View
    111

  • Download
    2

Embed Size (px)

Text of Maximo Overview

MAXIMO Version 6 (MXES or MAXIMO Enterprise)Tim Taber, PE Stearns & Wheler, LLC Wednesday, May 17, 2006 SOUTHEASTERN MAXIMO USERS GROUP (SMUG) MEETING

AgendaPoll What Version of Maximo Do You Use? Maximo Versions Timeline MXESArchitecture 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 1MAX 4.1.1 P7 MAX 5.2 P2A MAX 5.2 P3 MAX 5.2 P4

MAX 5.1 P3 Final Localizations Maximo Enterprise Suite

MAX 5.1 P5

MXES 6.0.01 (+ 4 Configurations)

MXES 6.0.02 (+ 4 Configurations)

OCT DEC 04

JAN MAR 05

APR JUN 05

JUL SEP 05MXES Mobile

March 25, 2005

Maximo Timeline 2MAX 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.2MAX 4.1.1 P8 (TBC)

MRO Estimated MRO Estimated Retirement Dates Retirement Dates

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

MXES Upgrade Schedule

Evolution of Maximo Extended Enterprise Suite.4.0 SeriesCentura based client-server application.

4.1 SeriesHybrid of Centura and Java. Home grown java application server MXServer. More Centura applications than Java applications.

5.0 SeriesStill 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 SeriesComplete Java based solution 100% ( excluding third party tools). Large number of applications, Help Desk, ITAM etc.

MXES ArchitectureMulti 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 asWeblogic, WebSphere.

Enables centralized systems.Multiple Orgs, Multiple Languages etc.

J2EE Verified Enterprise Application.

MXES User Interface ChangesIn 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 multilanguage. 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 EnhancementsWorkflow 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 ChangesDatabase 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

Multisite Capabilities MAXIMO 5x Model

Site 3

Organization 1

Site 2

Database/Enterprise

Site 4

Organization 2

Site 5

Site 6

Site1

Organization 3

Site 7

Viewing DataUsers 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 ApplicationsItem Master Tools Company Master Master PM Job Plans

Centralized Purchasing

PR Site 1

Receiving Site 1

Receiving Site 2 PR Site 2

PO Site 4

Invoice Site 4

PR Site 3

Receiving Site 3

Maximo 5 EAM CapabilitiesAsset Management Work Management Materials Management Item Master Storerooms Inventory Issues & Transfers Purchasing Request for Quotation Receiving Purchase Requisitions Invoices Purchase Orders Job Plans Locations Routes Equipment Work Requests Failure Codes Service Contracts Condition Monitoring Work Order Tracking Work Requests Safety Quick Reporting Labor Lock-Out/Tag-Out Tools / Crafts/ Companies Preventive Maintenance Assignment Manager

Workflow

Reporting / KPIs / Analysis

Maximo Enterprise Suite EAM CapabilitiesAsset ManagementLocations Asset Failure Codes Condition Monitoring Meters Meter Groups

Work ManagementJob 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 ManagementItem 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

Enhanced Workflow Event Driven, Context-based / Escalation Manager

Reporting / KPIs / Analysis

Asset Management EnhancementsAsset Move / Modify EnhancementsEquipment 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 statusable

Meter (and Condition Based) EnhancementsNew Meter Application w/ multiple typesContinuous - 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 EnhancementsServices EnhancementsServices Used on Job Plans and WOLump Sum and Unit Cost Services e.g. HVAC Service, Landscaping Service

Services Linked and Managed from Contracts Module

Labor and Crafts EnhancementsCraft/Labor Skill Levels (Apprentice, Journeyman, etc.) Labor can have Multiple Crafts Qualifications and Certifications Supported in WOs and Assignment Manager

Inventory EnhancementsItem Tracking by Conditione.g Tire Tread Depth; or New, Used, Rebuilt

Inventory EnhancementsItem Kitting EnhancementsItems grouped and managed in the Storeroom as a Package

Inventory EnhancementsMaterial Inspections on Receipt

Tool Management EnhancementsTool Management ModuleStocked and Rotating

Application Designer

Application DesignerNew 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 ApplicationEasily build KPI reports KPIs can be displayed on the Start Center

KPI Manager Application - Trending

Security ChangesSecurity 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 ProfileIn 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 ChangesNew 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 techno