Can any one explain the Capacity Planning in SAP PM
My requirnment is i will schedule the maintenance plan then automactically the orders should come based on the capacity which order should be started first .
Kindly let me know how to do it.
Just returning from SAPcentric EAM at Huntington Beach, which was a great event with more than 400 asset managers and maintenance professionals from both business and IT. In the course of this event and on other occasions I’ve often been asked where to find information about SAP’s latest innovations and also continuous improvements. Let me share some great sources of information that Paul Kurchina and I also presented during the Mastering PM at Gold Coast, Australia, as part of the Jumpstart session.
First of all, it is always a good start to just click www.sap.com/eam. When you explore our solutions you can see the various EAM solution areas
Behind the links there is a lot of further information.
But, you can also click on the Resources tab and download documents for offline reading, like the "Solution in Detail" collaterals that provide you an approx. 30 page overview on the various end-to-end solutions (bundles of the above solution areas). If you are rather looking for a complete overview, read the e-book on EAM. We are also working on a more intuitive visual representation of our portfolio, the so-called Solution Explorer. This is still in beta, but selecting your industry and area of resonsibility you will be able to visit further details on these entities.
While current product version are always visible with all details on our Service Marketplace in the Product Availability Matrix tool (http://service.sap.com/pam), roadmaps for all industries and lines of business can be found via http://service.sap.com/roadmap.
For this website you need a user that you can easily create yourself in case you are an SAP customer. Just click Registration at service.sap.com and keep your installation number ready. You can find it in your SAP system looking under System --> Status.
Now coming to recent innovations…
There is a nice overview page explaining the respective sources of information you can find at http://service.sap.com/findinnovation.
Starting from there
Last but not least, SAP even offers a free service, called the Business Function Prediction that provides you with an analysis based on your current use of the system which additional functionality might be beneficial to activate. You can find more details at http://service.sap.com/BFP.
Our Value Management professionals can also help you with different other services.
An overview on continuous improvements that we have made available through our Customer Connection Program (our collaboration model with the user groups) can be found right here on SCN. These smaller enhancements can be deployed as notes and are therefore minimal invasive for your current setup. And – as always – the EAM pages on SCN are a good place to look at, if you have additional questions.
Purpose
This process describes the use of permits during order processing. Before an order can be executed or technically completed, a planner ensures that:
Prerequisites
You define permit categories in the Customizing for Plant Maintenance and Customer Service by choosing Master Data in Plant Maintenance and
Customer Service - Basic Settings - Permits - Define Permit Categories.
These permits can be assigned to Technical Objects and / or Orders. Assignment of Permits to the PM Order can be done in 2 ways.
Permits Assignment in Technical Object:
Permits can be assigned to Technical Objects viz., Equipment & Functional Location. These permits will be called in all the PM orders which are
created with reference to these Technical Objects with the condition of Proposal tick box selected in Permits Screen.
To assign the Permits to Technical Objects in Technical Objects, follow this path.
Prerequisites: Permits should be created. Refer Transaction Code IPMD. Creation of Permits will be discussed at a later phase of this document.
This type of Permits assignment to the technical objects will be done whenever critical equipments are used & approval is required prior to all kinds of
maintenance.
Permits Assignment to Order:
Apart from assigning Permits to technical objects, Permits can be assigned directly in PM order. In some of the Technical Objects, Approval will not be
required always whenever maintenance is being done. So whenever approval required, permits can assigned in PM Order.
To facilitate this, Permits can be assigned to PM Order either manually or automatically.
Manual Assignment of Permits in PM Orders:
Menu Path: IW32 - Menu Goto - Permits.
Automatic Assignment of Permits to PM Orders:
Also Permits can be assigned to PM Order automatically based on Business Transactions.
1. Based on Cost
2. Based on Type of Activity
3. Based on Other Conditions
Based on Cost:
Here, approval will be asked from the manager or responsible person if the maintenance cost goes beyond certain limit. Here costs include Total
Planned Cost of Order, Total Estimated Costs of Order & Total Actual Costs of Order.
Scenario: (Whenever Total Planned Costs is more than limit)
Here, Permits should be created automatically whenever Total Planned Costs of Order goes beyond the limit. The following steps are to be followed.
1. Create Characteristics for the Parameters to be considered (T- Code is CT04)
a. Total Planned Costs of the Order (CSEVPERMIT – PKOSTEN)
b. If the approval is for specific type of Order (ex. Only for Preventive Maintenance), then add Order Type as another characteristic
(CSEVPERMIT – AUART)
2. Create Class by including all the created characteristics (T – Code is CL02)
Once all the required characteristics are created for the Permits configuration, Permit Class should be created.
Pre-Requisites: Permit Class should be configured in OIPG. The class name in CL02 should be same as the class mentioned in OIPG.
In the class of Permit, all the required characteristics should be assigned.
1. Creation of Permits
Once after creating Required Characteristics & Class, Permits can be configured using these details.
Transaction Code is IPMD
As shown above, Permit Code, Permit description & Permit category should be given. After that, Approval stage should be mentioned with
requirement status of approval. Approval stages are Order Release & Order TECO. Requirement statuses are
1. Warning message if permit is not issued
2. Error message if permit is not issued
3. Permit is optional
Once after defining above mentioned details, click Classification button.
Here the condition is that approval is required for the maintenance if the planned cost is more than 1000 SAR & order type is ZM03.
Usage of these Permits:
With above configured Permit, the following usage will be derived.
Whenever order is created with order type ZM03 & total planned costs goes beyond the limit of 1000 SAR, this permit will be assigned automatically
in the order. By having proper authorisation, only authorised person can issue this permit. Without having the issue of permit, Order release can be
rectified.
As per the required parameter to be considered for approval process, all the characteristics should be created & assigned the Permit class. All the
possible conditions can be referred from the table CSEVPERMIT.
Some Additional Information:
1. There are 3 different Order types (PM01, PM02 & PM03); but for all order types, approval is required if the total planned cost is more than 1000
SAR. Then there are 2 ways.
a. One, create 3 different approvals with the combination PM01 & 1000 SAR, PM02 & 1000 and PM03 & 1000.
b. Second, Create only one permit by assigning all 3 order types. Pre-Requisite to assign multiple values in Permit configuration is that Select
Multiple Values while creating Characteristics & giving appropriate no. of characters.
2. Authorisation for Permits Issue can be controlled using Authorisation Object I_SOGEN PM: Permit
Multiple values can be mentioned while defining the permits.
In fact, SAPPHIRE Orlando has been a while ago, and we are heading SAPPHIRE Madrid now. But, there are topics that are not a flash in the pan; they will influence they way we are doing business over years. PAS 55 is one of those.
PAS 55 as an asset management framework describes and defines essential key attributes and good practices for the management of physical assets. It was developed by the Institute of Asset Management in the United Kingdom, in collaboration with the British Standards Institution and along with the assistance and valuable input of many other organizations and individuals.
PAS 55 reflects a growing understanding of the importance of asset management as a driver of profitability. It also reveals an understanding of operational
risks and safety issues when asset management is not handled in a holistic manner.
The guidelines were first published in 2004 and then updated in September 2008. They consist of two parts:
PAS 55 is currently evolving into the ISO Standard 55000/1/2. For a good explanation about the relationship you can for example have a look a http://www.assetmanagementstandards.com/.
So what is the essence of all this? Still today, we see maintenance engineers and technicians, operators, reliability engineers, IH&S people out there in the field, who in many cases work in separation. PAS 55 tells another story. It's about integrating operations, maintenance execution, risk management, worker safety, and financials as a key to a holistic asset management. Moreover, it asks for one unfied responsibility in a company for asset management.
This notion is well-known in the military for decades. There are people telling you that it all starts with the configuration control of a weapon system. From there, you can take decisions about MRO strategies, spare parts, qualification of the technicians, needed infrastructure and tooling, and so on. Even from an asset-centric view you instantaneously see the link to human resources, financials, asset information, and even intangible assets like the safety culture in a company.
Now what is the role of software in this regard? Of course you could do holistic asset management using pen and paper. But, let me give you some examples of the advantages of an integrated software system:
Obviously, this does not come along with the information system itself. Let's be clear that proper asset management first of all requires a management system and then support by information technology. But, establishing the right software support today is crucial for making good asset management happen. If you like to read more about PAS 55, please have a look into the white paper that you can find on http://www.sap.com/eam.
Talking about HANA today… My assumption was that the combination of technical and business data about assets within in-memory databases will change the way we are doing asset management. Why is this?
Measuring, analyzing and controlling the performance of assets are some of the most basic steps to optimally manage the assets across their life cycle. In this context, maintenance planning and execution as well as shop floor systems collect myriads of data while assets are in service. Unfortunately, as of now this data resides in a heterogeneous landscape of disconnected systems (like operations management, SCADA, process controllers, instrumentation systems, production planning and shop floor management, quality and laboratory management, operational safety and risk management, just to name a few) that are owned and managed by various departments without any integration. Most of these systems have evolved over time and provide different levels of maturity and accuracy. Out of all these reasons, it is very difficult - if not impossible - to derive decisive knowledge.
Adding to this challenge, assets themselves are getting smarter and smarter, designed with built-in algorithms that predict their health and behavior. With large investments flowing into this area the expectations of the operators have increased dramatically, and they expect that an asset management system should provide a solution that can be used to prepare asset management strategies and programs on a continuous basis. Consequently, systems should help in achieving the best possible ways to non-intrusively inspect and maintain assets at a point in time that minimizes disruption and unplanned outages during asset operations.
This said, what is the benefit of HANA in this context?
Leveraging the low cost of main memory, new data processing capabilities, and fast access to data in a column-oriented store, analytical applications can process a huge amount of data online. In other words, data from various sources can be put into a HANA database. Thus, like first with Business Warehouse Accelerator having info cubes in memory, you can now have all data of interest stored for fast access and evaluation at a speed never imagined before. You can check out what this means having a look at production loss analysis on YouTube.
Combining the HANA DB with traditional applications like SAP ERP will even bring us to new horizons when performing ad-hoc analysis.
Collecting all data that is needed for applying predictive algorithms can now be done with HANA and various scenarios can be evaluated at unprecedented speed. Things that may have looked stochastic before, may now become explicable. For example, influencing factors like the qualification of the employees, scheduling and capacity of the respective work center, safety measures, and others can be taken into regard when looking for failure patterns. Moreover, when prioritizing maintenance work, boundary conditions like financial impact, history of similar assets, risk levels can be taken into account when deciding on the next appropriate time for inspection or maintenance. In essence, HANA is not meant to be replacing data historians collecting technical data, but to combine technical raw and aggregated data with business information, allowing an asset manager or maintenance planner taking the right decision.
The team is currently working on concepts and applications for bringing this into reality.
Please find the next blog in this series here!
As promised I would like to go into more detail about visualization. There are a lot of people agreeing that a picture tells us more than a thousand words. We started on this journey already when delivering the Maintenance Worker role with EhP 5 in 2010, based on the NetWeaver Business Client or the portal, as a one-stop-shop for information technicians need at work. By then, it was possible to embed animated repair instructions, leveraging Right Hemisphere's technology, into the job card. In the meantime, we could also demonstrate how easy it is to show additional analytics information, directly linked to the asset view, or, how to embed manufacturer information into the same plane (see SAP note 1636398, picture below shows data from Endress + Hauser). Goal is to make all information, that is needed for completing a job, available in one place. We also discovered that there had to be a more out-of-the-box integration of maps, hence delivering ESRI technology allowing for this with SP03 of EhP 6.
Ultimately, the vision is that maintenance people can see their assets on a map, manipulate respective data already there, or drill down to the plant or site environment, having a closer look, and finally looking at details of the respective equipment or component. Visual Enterprise at this end can become an alternative UI and not a separate application. Respective projects are under development.
What are other use cases that you could imagine? A change request for an equipment master record directly launched from the 3D object? Automated safety instructions for a worker entering a certain part of the plant on his mobile?
Please find the next blog in this series here!