Airport Maximo Users Group Meeting

The Wayne County Airport Authority is pleased to become the new AMUG Chair! WCAA looks forward to welcoming you this September!

Detroit Metropolitan Airport (DTW)
September 25-26, 2014

Thursday, September 25:

8:00-8:45A Session 1: Co-Hosts-Bruce Bothuel and Matt Cairns WCAA Strategic Direction (Tririga, SMS, Maximo)
9:00-9:45A Session 2: Mobile (Interpro and SEATAC)
9:45-10:00 Morning Break
10:00-11:00 Session 3: Scheduler (IBM)
11:00-12:00 Session 4: “Staying Sane in Crazy Times” (Dr. Scott Sheperd)
12:00-1:00 Lunch and Trade Show Opening: Wright Room
1:00-2:00 Session 5: IBM Road Map (IBM)
2:00-2:30 Session 6: KPI/Reports (Maven)
2:30-2:45 Afternoon Break
2:45-3:15 Session 7: Mobile (Interloc)
3:15-4:00 Session 8: Airfield Operations (WCAA)
4:00-4:30 AMUG Business Meeting (WCAA & EDI)
5:00P Bus to Detroit Tigers Game: Meet at Westin Valet Parking lobby

Friday, September 26:

8:00-9:00 Continental Breakfast: Wright Room
9:00-10:00 Session 9: Safety Management System (EDI & WCAA)
10:00-10:15 Morning Break
10:15-11:00 Session 10: Mobile (SCHAD & Massport)
11:00-11:30 Session 11: GIS implementation (McCarran Airport-Majed Khater)
11:30-12:30 Box Lunch and Attendees Round Table Discussion (Mo

Improving Service Maintenance efficiency through automation

The following was originally published at Managed Maintenance. View the original article here

Improving Service Maintenance efficiency through automation

Imporve service maitenance

The key to sending your maintenance sales totals skyward is a reliable, fool-proof, automated system to track, alert, quote and follow through on renewals.We call it improving efficiency through automation.

Let’s get right to the bottom line—as a channel partner selling service maintenance, how does automation benefit you? Let’s start with more renewals, more sales and a reliable system that delivers a source of recurring revenue.

To build this business model for recurring service maintenance sales, our foundation is MMI’s ONEview asset management software portal–our flagship product–an elegant, sophisticated technology to track all of your customers’ hardware and software assets and associated maintenance and services.

Add in ADDvantage+, our part number maintenance technology and the complement component to ONEview, and you have a complete system to proactively notify and quote impending maintenance renewals, with part numbers, pricing and service description information.

Proactive quotes

Let’s talk about how proactive quotes can increase your maintenance renewals. It’s no secret that tracking multiple renewal dates manually by spreadsheet (or notes on paper napkins) to provide an updated quote not only is labor intensive, it’s the least efficient way to run the service part of your business.

ADDvantage+ automation supplies you with the mechanism to notify you and your customer on upcoming renewals and to proactively provide quotes equipped with your branded messaging. The system does the work, not you.

For those of you who live by the details, ADDvantage+ automates a 10-step process that results in you winning renewals and gaining sales:

  1. Manufacturer sends renewal data to MMI
  2. MMI cleans and processes data to import
  3. Renewal data load to ADDvantage
  4. Notifications send to reseller to qualify renewal opportunity
  5. Reseller has option to send notification to end customer
  6. Notification and quote send to end-user
  7. Customer accepts or rejects quote
  8. Reseller completes sale and submits purchase order
  9. Distributor completes order and submits for registration

Strengthen your marketing

Automating the renewals process also brings you an additional marketing resource that can strengthen your relationship with your end customer. For example, with ADDvantage+ automation, you contact your customer 90 days out from the renewal date, and then at 30-day intervals through one month past the point of renewal.

In addition, by alerting your customers of upcoming warranty renewals through the quoting process, you may spark new hardware and/or software sales in a fresh cycle, which, of course, not only translates to new business for you but also builds trust and loyalty.

Finally, because automating renewals gives your sales people visibility into your customers’ hardware and software environments, they can leverage that data to help develop an overall account strategy with your customers, positioning you as a true trusted advisor to your clients.

Reliability Centered Maintenance (RCM) in the Facilities Environment

The following article was originally published by Reliability Web. The original article may be found here

The role of RCM in the facilities (non – production) environment as expected varies dramatically with the age and type of facility being operated and maintained thus, the type of RCM to be applied must be carefully decided to ensure both tangible and intangible benefits will be realized within the budgetary constraints of the organization. In addition, the dynamics of the organization where RCM is being considered must be considered before selecting the optimum approach. For example, an organization involved in large scale construction and/or renovation will have substantially different requirements and resultant business case than one focused on sustaining the status quo via a maintenance and minor repair approach.

The business case for RCM implementation for the majority of existing facilities where the inventory is stable is primarily based on the following cost avoidance techniques:

  • Reduction in time based maintenance hours
  • Reduced catastrophic failures and resultant costs
  • Age Exploration – OEM recommendations for example

For organizations where new construction and major revitalization are occurring, the business case also includes using the following to identify, implement, and verify (quantification) reliability issues:

  • Failure Modes and Effects Analysis
  • Commissioning
  • Operations and Maintenance tasks
  • Initial tools and training
  • Age Exploration for revitalization

Note: This paper does not address the basics of RCM and is intended as an aid to deciding the applicability and portion of RCM to apply to your facility and operating environment.

Where to Start:

  1. Determine if there is any reason to change the way you do business

While RCM, is the paraphrase others, the only truly logical and empirical approach for establishing and maintaining a maintenance program it is not for everyone and should not be pursued unless there is a factual basis which offers either tangible or intangible benefits. These benefits include only the following:

  • Reliability issues in – terms of safety, security, and mission
  • Financial return both, direct and lost opportunity costs

Building the business case and implementation strategy should be based on both strategic (global) and tactical (event) key performance indicators regardless of the type of facility being considered.

Life Cycle

Choosing the Appropriate RCM Approach

There are several ways to conduct and implement an RCM program.  The program can be based on rigorous Failure Modes and Effects Analysis (FMEA), complete with mathematically-calculated probabilities of failure based on design and/or historical data, intuition or common-sense, and/or experimental data and modeling.  These approaches may be called Classical, Rigorous, Intuitive, Streamlined, or Abbreviated.  Other terms sometimes used for these same approaches include Concise, Preventive Maintenance (PM) Optimization, Reliability Based, and Reliability Enhanced.  All are applicable.  The decision of what technique to use should be left to the end user and be based on:

  • Consequences of failure
  • Probability of failure
  • Historical data available
  • Risk tolerance

Classical/Rigorous RCM

a.  Benefits

Classical or rigorous RCM provides the most knowledge and data concerning system functions, failure modes, and maintenance actions addressing functional failures of any of the RCM approaches.  Rigorous RCM analysis is the method first proposed and documented by Nowlan and Heap and later modified by John Moubray, Anthony M. Smith, and others.  In addition, this method should produce the most complete documentation of all the methods addressed here.

b.  Concerns

Classical or rigorous RCM historically has been based primarily on the FMEA with little, if any, analysis of historical performance data.  In addition, rigorous RCM analysis is extremely labor intensive and often postpones the implementation of obvious condition monitoring tasks.

c.  Applications

The classical approach should be limited to the following three situations:

  • The consequences of failure result in catastrophic risk in terms of environment, health, or safety and/or complete economic failure of the business unit.
  • The resultant reliability and associated maintenance cost is still unacceptable after performing and implementing a streamlined type FMEA.
  • The system/equipment is new to the organization and insufficient corporate maintenance and operational knowledge exists on its function and functional failures.

Abbreviated/Intuitive/Streamlined RCM

a.  Benefits

The intuitive approach identifies and implements the obvious, usually condition-based, tasks with minimal analysis.  In addition, it culls or eliminates low value maintenance tasks based on historical data and Maintenance and Operations (M&O) personnel input.  The intent is to minimize the initial analysis time in order to realize early-wins that help offset the cost of the FMEA and condition monitoring capabilities development.

b.  Concerns

Reliance on historical records and personnel knowledge can introduce errors into the process that may lead to missing hidden failures where a low probability of occurrence exists.  In addition, the intuitive process requires that at least one individual has a thorough understanding of the various condition monitoring technologies and failure mechanisms.

c.  Applications

The streamlined approach should be utilized when:

  • The function of the system/equipment is well understood.
  • Functional failure of the system/equipment will not result in loss of life or catastrophic impact on the environment or unit business.

For these reasons, the streamlined or intuitive approach is recommended for the majority of facilities. Exceptions are where single points of failure exist and the associated risk of failure cannot be mitigated.

The streamlined or intuitive approach is recommended due to the high analysis cost of the rigorous approach, the relative low impact of failure of most facilities systems, the type of systems and components maintained, and the amount of redundant systems in place.  The streamlined approach uses the same principles as the rigorous, but recognizes not all failure modes will be analyzed.  RCM users have reviewed the various processes in use and have determined that the most economical and efficient approach is to use a combination of rigorous (formal) and intuitive analysis depending on system criticality and failure impact.

A more rigorous analysis may be warranted for those systems and components where the streamlined or intuitive RCM process has been used and the resultant reliability is still unacceptable in terms of security, safety, cost, or mission impact.

Three Approaches to RCM

1.  Globally Dispersed – Large New Construction Effort

a.  Use of generic FMEA data to construct maintenance program tasks, interval, and training programs
b.  Commissioning developed using FMEA with a concentration on identifying and addressing single points of failure
c.  Criticality and probability of failure used to determine stocking plan
d.  Roving condition monitoring teams to determine priority and scheduling of repair and PM teams
e.  Root cause failure centrally located and coordinated by system experts
f.  Metrics developed to track availability, mean time between failure, and costs
g.  Significant overhaul of design and procurement process to implement RCM
h.  Process reengineering used to identify potential opportunities

2.  Dispersed – Aging and Diminishing Inventory

a.  No FMEA performed on standard facility equipment where sufficient redundancy existed. FMEA performed on a case – by -case basis for critical program equipment
b.  Immediate implementation of condition monitoring technologies appropriate to machinery type and mission
c.  Dispersed technologists at each location
d.  Minimum central management
e.  Virtual teams to shard information
f.  Commissioning limited to condition monitoring acceptance testing
g.  Metrics developed to track availability, mean time between failure, and costs
h.  Limited changes to building specifications

3.  Centrally Located (for the most part) – Limited Revitalization

a.  Generic FMEA used and all maintenance tasks revised
b.  RCM added to position descriptions and annual performance plans
c.  Spare parts switched to Just – In – Time
d.  Dispersed first line maintenance with centralized technologists
e.  Immediate implementation of condition monitoring technologies appropriate to machinery type and mission
f.  Limited use of acceptance testing
g.  Metrics developed to track availability, mean time between failure, and costs and reported to all levels of the organization on a monthly basis
h.  On -going training program implemented – 40 hours per employee per year

In closing, there are these basic rules:

  • Pick the appropriate level of sophistication based on a business plan which addresses implementation cost, time required, return – on investment, and risk mitigation
  • Create and apply the appropriate Key Performance Indicators and make them public
  • Communicate and train everyone
  • Be shameless in promoting your program – crow about your successes and acknowledge your failures in order to build and maintain credibility
  • Do not over analyze
  • Stay the course, RCM is not a program of the quarter
  • Design and use your management software to analyze and identify areas problems
  • Do not simply add a condition monitoring technology without understanding related changes

Article submitted by Alan K. Pride, Associate Director, Smithsonian Institute

Maximo Spatial Database Federation

Originally posted on the developerWorks blog.

Maximo Spatial Database Federation

Author: Rodrigo Dombrowski, Maximo Product Designer & Architect
This article describes the Maximo Spatial architecture that integrates the IBM Maximo Asset Management database with a GIS geodatabase.

All information below is valid for Maximo Spatial 7.5 version.

Maximo Spatial integrates with the GIS database using a concept called database federation, often also called database links.

Database Federation provides the following benefits:

  • No data replication needed as GIS data can be exposed and displayed on Maximo forms
  • Distributed database transactions to ensure consistency
  • Higher performance for batch read and creation of GIS records and Maximo records
  • All Maximo framework functionality and security available when displaying and editing GIS data
  • Multiple geo databases support

Documentation about how to configure Maximo Spatial to integrate with feature class tables is available in:

Documentation about how to expose GIS data to Maximo forms is available in:

The Maximo Spatial database configuration is done independently for each feature class that the client want to integrate with Maximo. This allows supporting multiple geodatabases and feature classes in any database schema. For GIS data insert and updates Maximo Spatial requires that both databases be from the same vendor. Oracle+Oracle, or DB2+DB2, or SQLServer+SQLServer.

Configuration Overview

Configuration Overview

In some cases it is not possible to have both Maximo and GIS database from the same vendor or it is not possible to configure database links.
For these cases currently there are the following options:

Option 1 – Read only mode – No database federation (database link)

  • Same configuration process, including Database Configuration steps, but without database link
  • It makes Maximo Spatial only read-only mode for GIS data
  • Map toolbar tools like selection, query by attributes and update GIS list stays working
  • No GIS record link or cron task will be available
  • No GIS geometry creation and editing from Maximo

Option 1

Option 1

Option 2 – No federation, read/write GIS data moved to local Maximo database

Example: Maximo running on DB2 and GIS data on Oracle database

  • Full Maximo Spatial functionality for the GIS data that is moved to Maximo database
  • No federation required when GIS is on the same Maximo database instance
  • GIS data that can be read only to Spatial can stay on Oracle
  • May require additional ArcSDE license
Option 2

Option 2