1.

Maximo-ERP integration Involved Software: Maximo Oracle

Maximo Enterprise Adapter MEA for Oracle: Integration between Maximo and Oracle Applications is carried using Maximo Enterprise Adapter MEA for Oracle. MEA for Oracle enables rapid integration of Maximo Asset Management with the Oracle E-Business Suite and provides ready-to-run out of the box integrations between Maximo and selected modules in Oracle E-Business Suite that are typically integrated with Maximo such as General Ledger, Purchasing and Inventory modules. The MEA for Oracle is a set of applications and predefined integration points that help you to integrate Maximo with Oracle Applications and create business flows between Maximo and your other enterprise applications The MEA facilitates data exchange between Maximo and external applications or systems in a real-time mode. Data is exchanged via interfaces, each of which acts as a communication channel between the external system and one or more integration points (points of data exchange) in Maximo. Java procedures perform the integration processing, and users can customize the processing through Java user exit procedures. Data that Maximo receives from external systems is inbound data. Data that Maximo sends to external systems is outbound data.

Integration Methodology: The integration process consists of three phases Phase 1: Requirement analysis A workshop comprises all involved parties will be held prior to the actual implementation to agree on all use cases required by the customer's business process and discuss various integration scenarios. The output of this phase will be the requirements specification document (RSD) detailing the customer's business process, functional and non-functional requirements and chosen integration scenario. The RSD will be approved by the workshop members. Phase 2: Developing a test environment Integration will be carried on a test environment prior being applied on the production system to assure achieving the required functionality, assure compliance with the customer's needs and to give the customer a chance to test the system and develop their comments. Phase 3: Developing the production environment After making sure the system is compliant with the business requirements and applying customer's comments on the test environment, implementation on the production environment is carried

Requirements Analysis

Develop Test Environment

Develop Production Environment

Maximo Integration with Oracle phases

IBM Maximo condition monitoring integration Integration with condition monitoring third party software requires gathering all involved departments in a workshop to deeply understand integration requirements and develop the roadmap to be followed in integration process, as long as this process is not out-of-the-box integration and maximo provides no integration adapters or mapping files. We shall follow one of the two following methodologies depending on workshop result assessment: 1. Integration Objects: As integration framework, service oriented architecture and web services technologies provides maximo version 7.1 with maximum support to integrate application services and coordination between maximo enterprise system and external application, integration can be configured and customized to meet customer specific business requirements will be the results of the workshop. Integration framework is designed with highly flexible business components to ensure compatibility with maximos web based infrastructure, using J2EE services architectures Smart System special development and object structure team will provide full integration solution with condition monitoring third party software. 2. Custom developments for database: Choice of following this methodology will be depending also on workshop results, variety of interface functionalities can be described and done by Smart System integration team, sets of permitted functionalities and assumptions can be followed to reduce the impact of database interfacing. Doing such job requires deep knowledge of database programming and interfacing methodologies the advantage that our team have far experience.

IBM maximo Microsoft project integration Ready to deploy IBM Maximo Adapter for Microsoft Project v7.1 allows you transfer work order and preventive maintenance data between your Maximo database and Microsoft Project. You can transfer Maximo records into Microsoft Project for forecasting and scheduling, and then transfer the schedule data back into Maximo.

Bi-directional integration between Maximo and Microsoft Project ensuring data consistency across both systems. Embedded forms, dialogs and filters in Microsoft Project allow quick access to Maximo data and added functionality related to work and resource planning. Integrates Maximo Work Orders, Preventive Maintenance (PM), Assets, Resources and Calendars with Microsoft Project. Supports the creation of work orders in Maximo from Microsoft Project. Updates Maximo with the new schedules, logic and activities from Microsoft Project. Asset calendars in Maximo can be part of resource scheduling that considers not only the availability of required working resources but the availability of the equipment as well. Customizable mapping of data attributes from Maximo's work order object to Microsoft Project task columns can be validated on entry against the Maximo data sets.