Manufacturing resurgence in America recapped as Honda hosts MMUG Mtg
Mary Gorczynski 1100006B54 firstname.lastname@example.org | | Emneord:  tivoli service-management ibmontwitter manufacturing assetmgmt ibmsoftware honda software eam maximo ibmeam asset-management
0 kommentarer | 3.536 besøg
Today's blog comes from Sudhee Subrahmanya, Product Manager for Maximo Asset Management.
The Manufacturing resurgence in America has started and is now getting great attention link.
Maximo, being the leading asset management solution, has been used in manufacturing companies for many years now and has contributed its own little bit in bringing efficiency to the Manufacturing sector. The Maximo Manufacturing User Group met on May 22, 2012 at the Honda Manufacturing plant in Marysville OH. Representatives from many manufacturing corporations were present and the conversation with each of them was very enlightening in terms of their approach to implementing their asset management solution. With the release of the new Maximo 7.5 there are many manufacturing companies who are planning to upgrade to the newest version. Because Maximo 7.5 has many cool features that companies need and would contribute to increasing efficiency, most of the customers are planning the move.
During the user group meeting, many customers who had significant experience with Maximo provided their views on various issues. The important business guidelines while implementing or upgrading the Maximo solution are listed below:
1. Involve the stakeholders
Many large manufacturing enterprises have various locations and they also have processes that are specific to their locations. Maximo being very flexible is capable of being tailored according to ones own needs. It is important to make sure that corporations bring in the various stakeholders (such as the various manufacturing teams, middle-managers and the IT team) in at the very beginning of planning an implementation and/or migration. A leading auto manufacturer had three main divisions related to stamping, powertrain and assembly – so the representatives from each of these groups were brought in early to be part of an overall Maximo coordination team. Having such a coordination team greatly helps in getting the views from different users within the enterprise. This also helps the IT team to understand the usage and business needs of the enterprise.
2. Focus on Business Process
Time spent on understanding the business processes of various teams within the organization is very critical to gain tremendous efficiency in the solution. Identifying the various kinds of classifications and data that will be input into the system is important.
With the Maximo solution, many activities can be greatly enhanced by the use of workflow capabilities and leveraging the excellent reporting functionality. The end-users, using Maximo, can focus on their core activities while at the same time providing critical information such as costs, time spent on maintenance activities etc that will provide a comprehensive view into the overall operations. This information can then be analyzed to gain valuable insights into the operations and improve efficiency.
3. Train the users
The end-users are where the rubber meets the road. The end-users must be trained in the usage of the Maximo solution and informed about how their individual actions contribute to the overall value for the corporation. The end-users who input data into the system must be made aware of the importance of entering accurate information into the system. One manufacturer has assigned the accountability of inputting accurate data to each of the managers who oversee the local team. This has greatly helped in making sure that the teams are trained and that the end-users have an understanding of the whole process. This training also empowers and improves the confidence of the end-user technicians.
4. Plan the Reports & Start Center
Maximo provides very powerful reporting capabilities. With Maximo, a user does not have to print all the reports, but can easily email a url-link that refers to the report. This is very efficient and reduces the printing that is needed. Proper planning in reporting using the stake-holder team that was discussed earlier will help in developing common reports across the enterprise. Maximo’s multi-language capabilities can be leveraged when the reporting has to be done across multiple geographic locations.
One of the large enterprise users during the meeting mentioned how they have made the reports very actionable by sorting entries in their reports by importance (such as priority and date before which a work-order has to be completed) and also color coding the report. This allows the end-user to look at the list for the day and then identify the specific activities that he or she has to perform.
A focus on what the end-users see when they login into the Maximo system is also very important. Maximo has a very powerful and configurable Start-Center, i.e the screen which a user sees when he or she logs into the system. The Maximo team should make sure that the end-users get the information that they need in a simple manner so that they can focus on their specific responsibilities. The Start-Center must be configured by involving the local users in making sure that they have the information they need. The amount of information that is provided must be ‘just right’ like in the Goldilocks story. Too much information may overwhelm the end-user and too-little information may not be useful enough for the end-user to carry out their job.
A business manager, tasked with managing and using the Maximo solution implementation must pay attention to each of the points mentioned above.
In conclusion, the Maximo Manufacturing User Group meeting was very useful and it provided valuable insights into the various business and technical aspects of implementing and managing Maximo. Huge thanks to the Honda of America Manufacturing team, led by Rob Mundy, for providing the leadership and hosting the meeting.
The technical best-practices for a Maximo implementation are discussed in this whitepaper.