IBM Software Group Maximo Webcast Series Maximo Integration Basics Frank Vanderham, PhD Ontracks Consulting April 30, 2008 Trouble seeing or hearing us? Call 780-293-6307 2007 IBM Corporation
Outline The benefits of integration why and when integrate? Technologies used in system integration The Maximo Enterprise Adapter (MEA) Best practices the Integration Project Q&A Trouble seeing or hearing us? Call 780-293-6307
Why Integrate? Maximo is part of your company s landscape of applications Not one system provides (today) all functionality to conduct business While the applications are different, the data they need is NOT Financial System / ERP Inventory Reordering Fuel Gauges Condition Monitoring Reliability Centered Maintenance (RCM) Trouble seeing or hearing us? Call 780-293-6307
Enterprise Asset Management Maturity Levels -All Business Processes -Service Level Agreements -Service Management -One System All Processes -Asset & Services Management -Enterprise Wide Business Alignment -Reliability -Condition -Predictive Level 4 Level 5 Value -Fire fighting -Run to fail -Work Mgmt -Preventive -Spares parts Level 3 Level 2 Proactive Service Oriented Enterprise Value Level 1 Chaotic Reactive Maturity Trouble seeing or hearing us? Call 780-293-6307
Benefits of Integration automated or not Maximize your existing, previously made investments Keep best-of-breed applications Advance your EAM Maturity Level However Mind the following key principles: Trouble seeing or hearing us? Call 780-293-6307
Key Principles to System Integration Avoid manual data re-entry SOX, CSOX Keep within each system s key functionality, don t stretch Interface, don t Assimilate Understand Maximo s breadth of functionality Migrate where possible Decide which system owns what data Keep It Simple
System Integration Technologies We will review a number of three-letter and four-letter words For a given project, you may only need one technology We will review the out-of-the-box MEA shortly API JDBC SOAP TCP/IP ODBC XML OPC HDA WSDL DCOM XSD Class Java NIC.NET RMI HTTP SQL
A brief primer in System Integration UI System B B s Storage?? Physical Connection Serial Ethernet Network (USB, etc.) UI (UI = User Interface) System A A s Storage
Protocol layers the language spoken UI System B B s Storage?? Network Communication (TCP/IP) Application Communication Application Programming Interface (API) Socket APIs (proprietary) Microsoft COM/DCOM HTTP UI System A A s Storage
Procedure Call layers the conversation spoken UI System B B s Storage!! Network Communication (TCP/IP) Application Communication Remote Procedure Call Web Services Client / Server OPC Client / Server UI System A ODBC / JDBC A s Storage Request / Response Message
Web Services Ethernet and USB have standardized the way machines are physically connected Web Services has standardized the language AND the conversation machines have to communicate Maximo is fully Web Services-enabled Web Services is the standard for business system integration
Real-time systems: OPC Web Services are typically not available for real-time system integration Real-time systems are notoriously proprietary and slow to adopt changing standards OPC is now the de-facto standard for real-time data communication Most process control software systems support OPC Data historians (OSI PI, Honeywell PHD, Aspentech IP.21, etc.) Vibration Analysis PLC / DCS
Maximo Enterprise Adapter (MEA) Opens up Maximo to the outside world Supports external systems read + write Web Services Interface Tables Flat / XML Files JMS Queues / EJB Provides very basic to complex integration features Allows pre- and post-processing of data before sending/receiving
Maximo MEA Out-of-the-Box Capabilities For the following examples: No programming required All configuration done with standard Maximo Web application Integration using files (comma separated, XML) Inbound: provides bulk-loading of data capability into Maximo Integration using Interface Tables Low cost, 1 st pass upgrade option from older versions of Maximo using database tables
File-based Integration with the MEA - Outbound 1. User approves WO Maximo 2. MEA processes WO and generates file File with WO Information External System 3. External System picks up new file
File-based Integration with the MEA - Inbound 3. MEA processes file and generates WO records Maximo 2. User performs Data Load in Maximo File with WO Information External System 1. External System generates new file You can use this method to bulk-load data into Maximo
Interface Tables with the MEA - Outbound 1. User approves WO Maximo 2. MEA processes WO and generates row(s) in MXWO_IFACE table 3. MEA Generates new row for TRANSID in MXOUT_INTER_ TRANS table 5. External System reads MXWO_IFACE External System 4. External System polls MXOUT_INTER _TRANS Maximo tables are never used directly!
Interface Tables with the MEA - Inbound Maximo 4. MEA reads MXWO_IFACE and generates WO Record(s) 3. MEA polls MXIN_INTER_TRANS for new TRANSID 1. External System writes to MXWO_IFACE table External System 2. External System writes TRANSID to MXIN_INTER_TRANS table Maximo tables are never written to directly!
Why not write to Maximo tables directly? Not supported Not upgradeable Re-implementing Maximo business logic
MEA Terminology Maximo Notify Query Outbound Inbound Notify Response External System External Systems Interfaces Integration Objects Business Objects DB Tables Files, Web Services, JMS Queues Processing, Sending / Receiving <Workorder /> Work Order Location Job Plan WORKORDER Table
Let s demonstrate
Best Practices - the Integration Project (1/2) Decide which system is the master record or owner of the data Avoid middle-man solutions such as data warehouses Data replication must be minimized or (preferably) eliminated Keep transactions down to single request response Avoid chattering Plan and document your integration project Identify and document all systems Identify and document business processes between those systems Don t integrate end-of-life applications, migrate them Maximo may be able to replace their functionality without customization Keep it Simple! Create and complete separate projects for different systems
Best Practices - the Integration Project (2/2) Set up a proper environment with three systems Develop Test Production Train the team on the technologies used Maximo MEA Java Web Services, XML, WSDL
Thank you for your attendance. Are you looking for information or assistance on Maximo Integration? Maximo Integration Workshop - $3,995 This three day, on-site workshop covers: Hands-on Training Your Target system(s) evaluation Assessment of Requirements and Feasibility Project Plan OR: a customized solution to match your requirements. Contact Ontracks at info@ontracksconsulting.com or +1 (780) 916-3639