SAP Plant Maintenance (PM) provides you with a comprehensive solution for all maintenance activities that are performed within a company. Identify, document, and correct failures and degradations of any assets for which you have responsibility. Plan and schedule activities to prevent or predict failures and keep assets and processes operating within design specifications.
Major Aspects of SAP Plant Maintenance Management of Technical Objects: Organize master data objects such as functional locations and equipment master records. Corrective Maintenance: Refers to the activities conducted by the maintenance organization to repair equipment of all forms within their area of responsibility Preventive Maintenance: Is a discipline that uses processes and activities that focus on the prevention of failures or performance degradation before it occur.
SAP Plant Maintenance is closely integrated with other solutions, for example, SAP Materials Management, SAP Production Management, and SAP Sales and Distribution. You can enhance SAP Plant Maintenance as well as the other SAP solutions with SAP Extended ECM.
The overall structure of a plant is reflected in the hierarchy of functional locations. A functional location represents an area at which pieces of equipment can be installed. You can manage your functional location and equipment documents easily in SAP Extended ECM (xECM) Business Workspaces.
Maintenance notifications describe the condition of a technical object or report a malfunction at a technical object and request the damage be repaired. You can manage your notification documents easily in SAP Extended ECM (xECM) Business Workspaces. In addition, in the same screen you are able to see the documents of the actual notification, of the related technical objects (functional location, equipment), and of the related maintenance orders.
Maintenance task lists describe a sequence of individual maintenance operations which must be performed repeatedly within a company. An operation specifies amongst others the documents required for the maintenance task. You can reference your documents easily in SAP Extended ECM (xECM) Business Workspaces for task lists. A maintenance order, which has been created based on a maintenance task list, takes over the referenced documents automatically.
Very often technicians require the work orders assigned to them to be printed. And it‘s not only the work itself, this print includes supporting documents managed at the work order, at the notification, at the functional, or at the equipment.
You use Incident Management to initially record and then review and complete incidents, safety observations, and near misses to fulfill your environment, health, and safety requirements on a regional and global scale.
The SAP Waste Management supports you in handling waste disposal processes, complying with national and international regulations and laws that are relevant for generation, transport, and disposal, and distributing costs proportionally among the departments within the enterprise that generated the waste.
The specification is the central data object for mapping substances, agents, packagings, waste codes, and dangerous goods classifications in the SAP component Environment, Health and Safety (EH&S). A specification is a description that uses identifiers and value assignments such as physical and chemical properties, medical advice, and details on transport and storage.
Specification Category / Possible Specification Types Substance /Real substance, listed substance Agent / Noise, dust, real substance Packaging / Box, barrel, bottle Waste code / Waste code Dangerous goods classification / Specification types according to the regulation families
Another excellent example for business relationships resides inside plant maintenance. In plant maintenance we have the technical objects ‚Functional Locations‘ and ‚Equipment‘. A plant is modeled in SAP PM in a hierarchical way by using these technical objects. Obviously, each functional location and each equipment has its own business workspace. The hierarchy, however, is a relationship that is used very often for understanding the setup of the plant and in the Extended ECM UI or in MS Outlook for navigation to the equipment and functional locations of interest.
Looking at scheduled and unscheduled maintenance the related business objects maintenance notification and maintenance order get of interest. Especially in the case of failure analysis in the sense of root cause analysis many collaboration happens between different users, e.g. a control panel operator, a plant operator, a technician and a reliability engineer. In this situation a collaborative workspace connected to a maintenance order issued for the failure analysis is a tremendous support for the failure analysis business process.
MMG was the first implementation of the PM blueprint (toolkit) in the world PM Blueprint solution materialized with feedback from a number of customers including MMG, Belgian Railways and Hydro Really quick to implement. Provides a large reduction in implementation effort. Actual implementation was really easy and surprisingly uneventful, given the ramp up nature of the product which is a credit to the development team in OT Germany. Everything worked out of the box. XECM development and configuration time reduced by 80% (excluding other related ECM and Architecture) Some unique requirements identified during testing that were fed back to the development team and have been incorporated into the later releases to help benefit all customers. I.e. relationship to General Task List in addition to Equipment Task List Due to Go Live in March 2014 (Limited by larger SAP implementation)
What it is… An integration blueprint An accelerator designed to help shorten the implementation effort and reduce the risk for the implementation of XECM for Plant Maintenance A best practice development design to meet the needs of 95% of customers as opposed to 95% of customer needs What it isn’t… An ECM design document A controlled document library design
Preferred method of implementing SAP PM integration is in conjunction with a controlled document library. Documents are unlikely to have a 1:1 relationship with SAP Objects Controlled documents need to be managed in the context of business processes It is not recommended to only implement the controlled library for asset management only Consider the design for your controlled document library in conjunction with SAP, not independently. Existing customers with controlled document libraries may require some changes or a design validation Consider SAP in your workflow approval. I.e. is the SAP object you are linking to relevant for the approval? A taxonomy will be required (At least level 1) Reporting can have a big impact on your design (consider web reports)
UI choice can have a considerable impact on your design. Incorporate your UI strategy in the design phase so the design can be adapted. The workspace design and approach has a big dependency on the number of workspace you intend using. I.e. 600,000 workspaces in a single folder The are ways to get around developing complex workspace structures (which require enhancements) to minimize the number of folders. i.e. search forms or virtual folders with real location of SAP workspaces hidden to avoid them as a navigation Consider parent vs child relationships as part of your documents location or shortcuts. I.e. 100 of the same truck = 100 equipment’s = 1 Material. If you store a manual, the logical place to store the document is at the material, not the equipment and use folder based relationships to expose it. Do not underestimate the effort for data migration. SAP adds complexity
If you are part of a larger SAP project, leave additional time for each cutover. XECM is not as simple as transports Check change objects for SAP – These are often switched off by the SAP functional consultants Switch off auto create and manually control the creation process of workspaces for migration. Can slow the SAP data takeon if you encounter CS issues. Consider the interdependencies between objects in your cutover plan for data migration Create Task Lists – Migrate Documents – Create Work Orders Note the fresh and upgrade process for each client. Refreshing the system or applying service packs may impact the SAP connection in a variety of ways. I.e. impersonation is switched off and needs to be switched on again. Limit customization where possible (impact on the ability to upgrade)
INSIGHT. INNOVATION. IMPACT.
INSIGHT. INNOVATION. IMPACT.
Controlled Documents in
Thomas Demmler (@thomasdemmler)
Director Product Management SAP Solutions
Athol Hill (@atholhillecm)
SAP Practice Lead