Enterprise Asset Management (EAM) System and Enterprise Resource Planning (ERP) Integration
Asia – Pacific Partnership April 30, 2008 Mike Hagen, Alliant Energy Dianne Davis, Alliant Energy
History § Alliant Energy (AE) was created when IES Industries Inc., Interstate Power Co. and WPL Holdings merged in April 1998 § AE currently operates 14 electricity generating stations with over 48,000 assets. These plants are maintained by a group of very knowledgeable craft workers who typically have 2530 years of experience and knowledge
Alliant Operated Fleet
Steam Turbine – 4388 MW CT – 1383 MW Hydro – 30 MW
Need for Enterprise Asset Management System § Problem Identification
§ A reengineering study was conducted in the mid 90s at WPL (Wisconsin Power & Light) and identified the following deficiencies in the existing maintenance processes:
§ The inability to view asset history § The lack of a uniform maintenance work management process across the generating facilities
§ Solution
§ In 1997 the WPL organization began developing a maintenance process model and searching for a robust yet customerfriendly enterprise asset management (EAM) system to eliminate those deficiencies. IES Industries was also undertaking a similar process
Alliant Energy EAM System
§ Solution (cont.)
§ In the midst of reviewing the process and most suitable software package, the merger was announced and the vision was enhanced to include building a commonality between the merging entities
§ The Outcome
§ The development of a uniform Process Model
§ Identify need and scope of work § Plan § Schedule § Execute § Analyze
§ The selection of the Maximo EAM System over TSW because it was more robust and customerfriendly
What is Maximo?
§ Maximo is a software based system that:
§ Automates the writing of work requests § Serves as an instrument to create and track predictive and preventative maintenance activities § Aids in the planning and scheduling of work § Tracks work history § Records all associated costs § Stores bill of materials, specification information, drawings, manuals, repair reports, etc. for assets § Provides a means to track both asset and process performance § Assists in scheduling and tracking regulatory compliance and safety tasks § Is designed to improve the efficiency of the maintenance work force and record keeping § Plays a vital role in optimizing the efficiency of work execution when fully utilized § Ultimately gives an organization the tools to make better decisions on maintaining assets
Sample Specification Data Sheet
Sample IPC/Navigator Drawing with Parts List
Maximo Goal: Improving Plant Performance
Plant performance is improved by managing the reliability of the assets, leading to significant business benefits by:
1. Increasing production output 2. Decreasing maintenance cost 3. Reducing need for capital replacement 4. Maximizing competitiveness and protecting jobs
There is more to Effective EAM than just purchasing and implementing a robust software program…A business process transformation is required to fully realize the benefits since the whole concept of proactive maintenance goes against the firefighting mentality that is present in many of the plants
Enterprise Resource Planning (ERP)
§ What is ERP?
§ ERP is a way to integrate the data and processes of an organization into one single system. Usually ERP systems will have many components including hardware and software. In order to achieve integration, most ERP systems use a unified database to store data for various functions found throughout the organization
§ Why Alliant Energy needed ERP
§ The merger brought three companies together with little to no commonality between financial, human resource and supply chain systems
§ The Solution
§ Alliant Energy chose the PeopleSoft ERP system to unify the business processes of the newly formed entity including: § Financial Systems (general ledger, project costing, accounts payable and expenses) § Human Resources and Time Entry § Supply Chain Systems (purchasing, inventory and vendor management)
The Missing Link
§ Problem: A piece was still missing
§ The organization now possessed quality EAM and ERP systems with the purchase of Maximo and PeopleSoft, but a key piece was still missing: a link between the two systems
§ The problem remedy began to take shape in 2006
§ Integrate Maximo and PeopleSoft to allow the organization to better utilize both systems by: § Sending both material and labor costs automatically back to the assets § Providing access to ‘realtime’ companywide inventory data allowing us to reduce inventory duplication and automated issuing of inventory parts from a work order § Allowing endusers to work in only one environment § Upgrade from Maximo 4.1.1 to Maximo 6.2 § Integration process would be less problematic since both applications were webbased § The organization was planning to upgrade to Oracle 10g in 2007 which was not compatible with Maximo 4.1.1 § 4.1.1 software was no longer going to be supported § Offered additional functionality
ERP and EAM Integration Goals § Develop solutions that enable a single source for labor hour
reporting § Feed all material and labor costs back to Maximo from Project Costing
• Assimilate Purchasing to allow the requisitioning process to initiate in Maximo and have the PO, receipt and invoice flow back to Maximo • Allow for the reservation of stock materials on a work order and receive costs back from any stock material issued from the storeroom that is associated with a work order • Integrate with ezBuy (Alliant Energy’s eprocurement software solution) to capture material costs purchased via eprocurement • Expense costs (credit card and other expense reporting) associated with a work order will be fed back to Maximo • Use of Maximo and ERP for labor hour reporting/time entry
§ Chart of Accounts Standardization § Use of common Project IDs
Upgrade/Integration Project Benefits
§ Increase Generating Capacity: § Generating capacity is increased through the capture of historical data from seasoned professionals. Alliant anticipates a reduction in unit down time which in turn increases availability § Improve Accuracy of Asset History: § Leads to more efficient planning and scheduling § Increased accuracy in budget estimates and asset endoflife projections will allow us to make better repair/replace decisions § Through the effective use of failure codes Alliant will be able to identify repetitive equipment failure modes § Reduce Inventory: § Reduction in inventory due to increased ability to identify necessary parts and locate them in the generating fleet § Industry average inventory reduction for this type of project 1030%
Project Benefits (cont.)
§ Reduce Labor Hours: § Time saved by integrating ERP and Maximo for labor and material acquisition through Maximo on each work order results in reduced duplicate effort and eliminates the need to learn two different applications/processes § Improve Work Planning: § Work order history and ERP integration reduces research necessary to plan and schedule work activities by accurately capturing all labor and material cost to maintain an asset § Reduce time spent Recording and Tracking Maintenance: § Time saved through autopopulating bill of materials and streamlined time entry process § Improve Scheduling of Work Orders: § Ongoing and future use of MSProject and handheld integration to reduce administrative work. Hours will be saved utilizing the ability of Maximo 6.2 to automatically integrate Maximo Work Orders into a Microsoft Project Schedule
Project Benefits (cont.)
§ Increase Wrench Time: § Unproductive time related to craftsmen receiving work orders, determining job plans, recording actions, and locating and charging out inventory will be reduced § Ease of use: § Reduce duplication of efforts and increase the auto population of as many General Ledger data fields as possible to assure user friendliness of the system § Navigator: § Assure the availability of the Navigator application to all plants providing a visual parts break down and bill of materials to planners and craft personnel § External labor reductions: § Having all labor hours and material automatically populated on each work order will facilitate the ability to increase productivity by more efficient scheduling. This increased productivity of inhouse labor will reduce contractor requirements
Integration Overview – Detailed Process Flow Diagram
Integration Details – Supply Chain
1. Manufacturers § Created or updated in ERP and published to Maximo via EAI 2. Items – Item IDs and descriptions § Created or updated in ERP and published to Maximo via EAI 3. Inventory – Quantities onhand, quantities reserved § Created or updated in ERP and published to Maximo via EAI 4. Purchase Requisitions (PR) § Created in Maximo and published to ERP via EAI § These can also be created directly in ERP and linked back to the work order via Activity ID (work order #) Note: Enterprise Application Integration (EAI) is an application that performs data transformations, enforces business rules, and routes messages to participating applications via adapters
Integration Details – Supply Chain (cont.)
5. Purchase Orders §Created in ERP as part of requisition process §Can be the result of a Maximogenerated PR or can be manually created in ERP and linked to a work order by the Activity ID (work order #) 6. Purchase Order Receipt §Generated in ERP and published to Maximo via EAI §When everything ordered on the work order is received and/or reservations are fulfilled, the work order status is updated from WMTL (waiting material) to RSCH (ready to schedule) 7. Material Reservations §Reservations created in Maximo and published to ERP via EAI §When items are added to the ‘Plans’ tab of the work order and it is approved, the Material Reservation is created and sent to ERP
Work Order Purchase Order Information and Material Reservation Screen Shot
Integration Details – Finance
8. Vendor (Companies) § Created or updated in ERP and published to Maximo via EAI 9. Project ID § Created or updated in ERP and published to Maximo via EAI § Chart of Accounts component 10. Activity IDs/Work orders § Created in Maximo and associated with ERPsupplied Project IDs § Published from Maximo to ERP via EAI § Key to autopopulation in ERP 11. Project Costing § Expenses § Labor actuals § Purchase order actuals § Inventory issues § All costs are tied back to the work order by the Activity ID
Maximo Work Order Costs Screen Shot
Integration Details – Human Resource Management System (HRMS)
12. Person Data
§Created or updated in ERP and published to Maximo via EAI
Integration Details – Other Functionality
13. ezBuy
§Data fed from ezBuy application to Maximo § Items § Inventory § Material Issue
14. ERP Autopopulation
§Autopopulation based solely on Activity ID (Work order #) §Available for the following transactions: § Finance – Expense Reporting and Account Validation § Supply Chain – Purchase Requisitions, Purchase Orders and Express Issues § HRMS – Time Entry
15. Labor Hours Report
§A report created in Maximo to retrieve a craft’s labor hours from work orders
Results
§ What results have we been able to achieve since the implementation of Maximo?
§ Increased planning is reducing asset down time through having the right parts and the right crafts at the right time to make the necessary repairs § Asset history is accessible from any location and the use of a standardized location hierarchy and naming configuration makes it easier to search for common assets § Productivity has increased as less time is wasted waiting for equipment isolation, getting parts from the storeroom, looking for drawings or repair plans or waiting for additional work § Operations (along with the asset’s criticality), not maintenance, is driving the prioritization of work
Results (cont.)
§ Success story: Putting it all together to reduce costs and improve availability
§ Circulating water pump rebuilds at Edgewater § Pump problems found early while completing the monthly vibration predictive maintenance task which reduced the cost of the repair and allowed us time to plan and schedule the rebuilds § Effective scheduling process assured us that we had the resources and available time to complete repairs § Asset history provided us with a starting point providing job plan and time, material and cost estimates that we could build upon to more accurately plan and schedule the repairs § Saved $50,000$60,000 by completing repairs inhouse and approximately 13 days of derates on the unit § We were also able to take the applied knowledge and lessons learned from the first pump rebuild and reduce the time by 17 hours on the second pump
Results (cont.)
§ What results have we been able to achieve since the Maximo upgrade and PeopleSoft Integration?
§ All costs are now tracked at the asset level and it is no longer necessary to go to multiple places to find cost information resulting in gained efficiency § Time is being saved by crafts completing their timesheets and when charging out parts in the storeroom due to autopopulation provided by the integration § Use of material reservations eliminates the need for crafts having to go get parts, charge them out and helps keep inventory counts in sync § ‘Realtime’ inventory data in Maximo with enhanced search capabilities has decreased the amount of time it takes to locate necessary items
Lessons Learned
§ The dedication of the team members can not be under emphasized. Knowing you have people that will remain focused and driven for the duration of the project makes the project both fun and successful § Having a customer on the team who is a subject matter expert will enhance and validate the final deliverable § Bringing in a knowledgeable and experienced resources can help ensure a timely and successful project § Phone conferences were utilized to reduce travel expense on the project. This did in fact reduce cost but it was often difficult to follow the meeting and required additional time to work to resolution on issues. Do not underestimate the value of meeting face to face to work through issues and drive to resolution
Lessons Learned (cont.)
§ Thoroughly document all requirements, leave no room for interpretation or misunderstanding. After making decisions it was often weeks or month before the decision was realized and we had to revisit the requirements document often to ensure we stayed within the scope of the project § The business process should be clearly defined and all technical decisions should be made to support the business process § Clearly define and document the roles and responsibilities of all the team members early in the process § Do not begin testing until development is complete, this only leads to additional effort and frustration as the design changes § Never underestimate the resources necessary or rely on a single resource for critical or required design, development or implementation work § Communication is vital to a successful implementation and integration process
So What’s Next?
§ Phase 2 of the Maximo 6.2 Upgrade List:
§ Assignment Manager § Workflow § Expand use of reporting
§ Phase 2 Integration List:
§ § § § § § Send Canceled Purchase Requisitions in ERP to Maximo Create custom script to create new Chart of Accounts (COA) entries HR interface to insert files (add new employees) Inventory interface change to get Quantity on Order Automation of the buyer updates from ERP into Maximo Attachments on purchase requisitions will be sent to ERP
§ Followup Tasks
§ Navigator Training for plants other than Edgewater
Questions?
?