PLM320 Work Clearance Management

Full text

(1)PLM320 Work Clearance Management. PLM320. Work Clearance Management. THE BEST-RUN BUSINESSES RUN SAP SAP AG 2003  SAP AG©2003. System R/3 – Enterprise 2003/Q2 Materialnummer: 50061236. © SAP AG. PLM320. Preface-1.

(2) Copyright. Copyright 2003 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. All rights reserved..  SAP AG 2003. Trademarks: Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE® is a registered trademark of ORACLE Corporation. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. © SAP AG. PLM320. Preface-2.

(3) mySAP PLM (ALM Plant Maintenance) PLM305 SAP01. 3 days. mySAP.com Overview. SAPPLM. 2 days. mySAP PLM Solution Overview. PLM300. 5 days. Plant Maintenance. 3 days. PLM310. *PLM130. 3 days. 3 days. Preventive Maintenance and Service. Classification. PLM315. **CA500. PLM316. * See also SCM Curriculum **See also HR Curriculum. 3 days. Document Management System. 3 days. Maintenance Processing: Operational Functions. ALM = Asset Life-Cycle Management. PLM120. Structuring and Managing Technical Objects. 2 days. Cross Application Time Sheet. 3 days. Maintenance Processing: Controlling and Reporting Functions. PLM320. 3 days. WCM Work Clearance Management.  SAP AG 2003. © SAP AG. PLM320. Preface-3.

(4) Course Prerequisites. LO100/PLM300 Plant Maintenance (Level 2).  SAP AG 2003. © SAP AG. PLM320. Preface-4.

(5) Target Audience. Participant Project leaders who are responsible for the implementation of WCM Project teams that implement the WCM related business processes Consultants preparing for a WCM implementation. Duration: 3 days.  SAP AG 2003. © SAP AG. PLM320. Preface-5.

(6) Course Overview. Contents Course objectives Course content Course overview diagram Main business scenario.  SAP AG 2001. © SAP AG. PLM320. 1-1.

(7) Course Objectives. At the conclusion of this course, you will be able to Describe the WCM functions Maintain WCM master data Process WCM transactions Configure WCM.  SAP AG 2001. © SAP AG. PLM320. 1-2.

(8) Course Content. Preface Unit 1. Course overview. Unit 5. Lockout / tagout. Unit 2. Introduction. Unit 6. Order processing. Unit 3. WCM objects. Unit 7. Further functions. Unit 4. Approvals. Unit 8. Customizing. Appendix.  SAP AG 2001. © SAP AG. PLM320. 1-3.

(9) Course Overview - Overview Diagram. Customizing Further functions Order processing Lockout/Tagout. M C W. Approvals WCM Objects. Course Overview Introduction.  SAP AG 2001. WCM = Work Clearance Management. © SAP AG. PLM320. 1-4.

(10) Main Business Scenario. IDES wants to ensure safety in the workplace while maintenance work is performed WCM uses a clearly defined and easily understandable process to make sure that assets/technical systems are safe.  SAP AG 2001. © SAP AG. PLM320. 1-5.

(11) Introduction. Contents General characteristics Asset management Maintenance process.  SAP AG 2001. © SAP AG. PLM320. 2-1.

(12) Introduction: Objectives. At the conclusion of this unit, you will be able to Integrate WCM with your maintenance process Describe the various structuring options.  SAP AG 2001. © SAP AG. PLM320. 2-2.

(13) Introduction - Overview Diagram. Customizing Further functions Order processing Lockout/Tagout. M C W. Approvals WCM Objects. Course Overview Introduction.  SAP AG 2001. © SAP AG. PLM320. 2-3.

(14) General Characteristics. Contents General characteristics Asset management Maintenance process.  SAP AG 2001. © SAP AG. PLM320. 2-4.

(15) Need for WCM. Maintenance crews are working in a hazardous environment (for example, high voltage, radiation exposure) Maintenance measures need to be performed while systems are operational Operation of a technical system must not be affected under any circumstances There are work-related illnesses, which require special health and safety measures.  SAP AG 2001. Inspections, repairs, or maintenance work for a technical object may only be carried out when measures to ensure work safety have been implemented. These safety measures include, for example, lockout/tagout, fire protection, radiation protection. Work Clearance Management (PM-WCM) enables you to control and monitor these activities. This means you are able to ensure safe and secure working conditions for maintenance employees, observe environmental regulations, and guarantee technical system availability.. © SAP AG. PLM320. 2-5.

(16) WCM Administration - Goals. Safety at work through Formal communication Data consistency Approval and status control Compliance with safety standards from regulatory agencies. Verification through Change documents Time stamp for all changes.  SAP AG 2001. © SAP AG. PLM320. 2-6.

(17) Asset Management. Contents General characteristics Asset management Maintenance process.  SAP AG 2001. © SAP AG. PLM320. 2-7.

(18) Basic Elements. Object links Ref. locations Equipment. Functional locations. BOMs. Classification Equipment Func. locs.. Assembly. Spare parts.  SAP AG 2001. Functional locations describe the structure of a technical system. Individual components are described as equipment. Object links represent connections between different technical systems. The hierarchy of functional locations and equipment is used to structure technical assets. Classification (classes and their characteristics) describes technical data for all kinds of objects.. © SAP AG. PLM320. 2-8.

(19) Structuring of Technical Assets. Func. location Func. location. Func. Func.location location hierarchy hierarchy. Installed Installed Equipment Equipment. Equipment. Equipment Equipment hierarchy hierarchy. Equipment. Equipment Equipment BOMs BOMs Assembly Spare parts. Assembly Assembly BOMs BOMs.  SAP AG 2001. © SAP AG. PLM320. 2-9.

(20) Structural Display Object Object links links. Documents Documents General General task task lists lists. Measurement Measurement points points. Task Task lists lists. BOMs BOMs. Maintenance Maintenance items items. Material Material stock stock. Scheduling Scheduling overview overview. Multi Multi layer layer list list. Notifications Notifications. Display Create. Objects Objects. Orders Orders. Notifications Notifications. Work Work orders orders. Display Create.  SAP AG 2001. Search for technical objects in a list or structural graphic Hierarchical search, or search in object links Display all object types (for example, functional locations, equipment, assemblies, spare parts) Easy access to all information No knowledge of numbering required. © SAP AG. PLM320. 2-10.

(21) Structure Indicator. Edit mask Hierarchy levels. Functional location key. AN-ANN-N-X-X 1 2 3 4 56. A1 A1-B A1-B02 A1-B02- 9 A1-B02- 9-C A1-B02- 9-C- 1. A = Alpha N = Numerical X = Alphanumerical. Plant System Sub-system Function Sub-function Item.  SAP AG 2001. You use the structure indicator to help you to identify a functional location. The structure indicator includes two entry fields: Edit mask Hierarchy levels You use the edit mask to control which marks are used for indicators (letters, numbers, or both). It also controls how these indicators are grouped and how they are separated. The field hierarchy levels defines where in the indicator each level ends, and how many hierarchy levels the structure can have in total. The indicator for a functional location can be up to 40 characters long (= maximum length of the the edit mask).. © SAP AG. PLM320. 2-11.

(22) Structuring - Example FL. 70 70. FL. 70 70. FL. 70 70. Block 7 LAB10. Feed water supply system Main slide valve. LAB10 LAB10- -AA005 AA005. EQ. Slide valve with drive. 1000 1255. EQ. 1000 1387. Slide valve DN200. EQ. 1000 1389. Variable speed drive. AB. 200 154. MT MT AB. Motor. 50000379 50000379 50000483 50000483 200 432. Brushes ... Control. FL = Functional location. EQ = Equipment. AB = Assembly. MT = Material.  SAP AG 2001. © SAP AG. PLM320. 2-12.

(23) Maintenance Process. Contents General characteristics Asset management Maintenance process.  SAP AG 2001. © SAP AG. PLM320. 2-13.

(24) WCM and the Maintenance Process. Work WorkClearance Clearance Management Management. Maintenance Maintenanceplan plan. Notification Notification. SCADA SCADA. Create Create order order. Plan Plan order order. Release Release order order. Work WorkClearance Clearance Management Management. Confirm Confirm order order. Complete Complete order order. History/analysis History/analysis.  SAP AG 2003. Orders are linked to WCM at order header level. For WCM-relevant orders you cannot perform the maintenance tasks until you have released them (status "Released for Execution" (EXEC)). Setting the tasks to "released" depends on the WCM architecture and whether the valuation was activated. Connecting orders to WCM is not absolutely necessary. Work clearance management enables you to carry out safety measures without an order. For example, this is the case if every change within the asset should or must be documented but the order is not needed for planning or to collect costs.. © SAP AG. PLM320. 2-14.

(25) Exercises Unit: Introduction. At the conclusion of this unit, you will be able to: • Use the structural display • Identify the permits assigned to a technical object • Create a notification or order (repeat of step from previous course) You must be able to use the functional location structuring and maintenance processing functions in IDES. This is a prerequisite for the implementation of Work Clearance Management.. 1-1. Functional location structure / Permits 1-1-1 Display the functional location structural display for your purification plant ## (## is the number of your group). How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________. 1-1-2 Identify the permits that have been assigned to pump set 2. How do you do this? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________. © SAP AG. PLM320. 2-15.

(26) 1-2. Notification / Order 1-2-1 Create a malfunction report for pump set 2. Planner group: I## Planning plant: 1000 Main work center: T-ME## How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________. 1-2-2 Create an order containing an operation for your malfunction report. Order type: PM01 Planning plant: 1000 Business area: 0001 Main work center: T-ME## How do you do proceed? ______________________________________________________ ______________________________________________________. 1-2-3 Set the order to Release (REL) without printing. Malfunction report: _______________ Order:. © SAP AG. _______________. PLM320. 2-16.

(27) Solutions Unit: Introduction. 1-1. Functional location structure / Permits 1-1-1 SAP Menu → Logistics → Plant Maintenance → Management of Technical Objects → Functional Location → Structural Display (= IH01) 1-1-2 Select pump set 2 Environment → Display object master record ( = <F6>) Extras → Permits ( = <Ctrl> + <F4>) Permit assigned: WCM. 1-2. Notification / Order 1-2-1 SAP Menu → Logistics → Plant Maintenance → Management of Technical Objects → Functional Location → Structural Display (= IH01) Select pump set 2 Goto → Create notification → Malfunction report 1-2-2 Maintenance notification → Order → Create → Direct 1-2-3 Order → Functions → Release ... (= <Ctrl> + <F1>). © SAP AG. PLM320. 2-17.

(28) WCM Objects. Contents Overview Work approval Applications Work clearance application Additional applications. Work Clearance Documents WCD template Operational WCD.  SAP AG 2001. © SAP AG. PLM320. 3-1.

(29) WCM Objects: Unit Objectives. At the conclusion of this unit, you will be able to Describe the different WCM objects Explain the differences between WCM objects Create WCM objects.  SAP AG 2001. © SAP AG. PLM320. 3-2.

(30) WCM Objects - Overview. Customizing Further functions Order processing Lockout/Tagout. M C W. Approvals WCM Objects. Course Overview Introduction.  SAP AG 2001. © SAP AG. PLM320. 3-3.

(31) Overview. Contents Overview Work approval Applications Work clearance application Additional applications. Work Clearance Documents WCD template Operational WCD.  SAP AG 2001. © SAP AG. PLM320. 3-4.

(32) Architecture. Order Work Approval Work clearance application. Order. Further applications. Operational WCD. Work Clearance Application Operational WCD. Enhanced model. Standard model.  SAP AG 2003. You can choose between the standard and enhanced model to represent your WCM architecture. The standard model includes the following WCM objects: Work clearance application Operational WCD The enhanced model includes the following additional WCM objects: Work Approval Further applications The decision which model to use is made at individual company level for each planning plant.. © SAP AG. PLM320. 3-5.

(33) Enhanced Model: Example Order Order 1001 1001. Order Order 1002 1002. Order Order 1003 1003. WAP WAP 2001 2001. WCA WCA 3001 3001. Operational Operational WCD WCD 4001 4001. Operational Operational WCD WCD 4002 4002. Order Order 1004 1004. WAP WAP 2002 2002. WCA WCA 3002 3002. ....... Operational Operational WCD WCD 4003 4003. Operational Operational WCD WCD 4004 4004. Operational Operational WCD WCD 4005 4005.  SAP AG 2001. The enhanced model is useful if you want to use the system to monitor other safety measures (for example, radiation or fire protection) in addition to lockout/tagout.. © SAP AG. PLM320. 3-6.

(34) Standard Model: Example Order Order 1001 1001. Order Order 1002 1002. Order Order 1003 1003. WCA WCA 3001 3001. Operational Operational WCD WCD 4001 4001. Operational Operational WCD WCD 4002 4002. Order Order 1004 1004. WCA WCA 3002 3002. Operational Operational WCD WCD 4003 4003. Operational Operational WCD WCD 4004 4004. Operational Operational WCD WCD 4005 4005.  SAP AG 2001. The standard model is useful if the main goal is to support lockout/tagout in the system, and other safety measures play a less important role.. © SAP AG. PLM320. 3-7.

(35) Communication. Order Order. Work WorkApproval Approval. Applications Applications. Plant Maintenance. Plant Maintenance Production. Plant Maintenance. Work clearance application. Production. Applications for Radiation protection. Work WorkClearance Clearance Documents Documents. Fire protection. Production. Operational WCD WCD template.  SAP AG 2003. Integration between Work Clearance Management and the maintenance process requires good communication between plant maintenance and other departments.. © SAP AG. PLM320. 3-8.

(36) Creation with Reference. Order Order. Work WorkApproval Approval. Filter Filterfor fordata datacopy copy (Customizing) (Customizing). WCM object. Applications Applications. Work WorkClearance Clearance Documents Documents.  SAP AG 2003. Data to be copied Header data Items (just for work clearance documents) Additional data (just for WCM objects) - Long texts - Object list - Documents - Catalogs. © SAP AG. PLM320. 3-9.

(37) Work Approval. Contents Overview Work approval Applications Work clearance application Additional applications. Work Clearance Documents WCD template Operational WCD.  SAP AG 2001. © SAP AG. PLM320. 3-10.

(38) Work Approval. Only used in the enhanced model. Order. WCM object for control and communication between orders and applications. Work Approval Work clearance application. Further applications. Umbrella WCM object for orders and applications. Operational WCD. Enhanced model.  SAP AG 2003. The work approval is a WCM object for controlling communication between maintenance orders and applications. The work approval requires safety measures designed to ensure that work on a technical system is carried out in a hazard-free environment. As a superior WCM object, the work approval may include a work clearance application with additional applications (for example, boiler inspection certificate). Work approval is only used in the enhanced model, and represents the central safety certificate. On the one hand, work approvals are assigned to orders where tehy control the status "Released for execution". On the other hand, work approvals are assigned to applications that they control and check.. © SAP AG. PLM320. 3-11.

(39) Work Approvals: Data Generic object services: different services are possible Status processing and audit trail: system status and user status. General data Reference object Areas of responsibility Location data Planning data. Assignment of partners: different roles possible Long text processing: several internal remarks Assignment of documents: link to document management system Assignment of permits: cross-document, interactive Use of catalog technique: catalog groups and codes.  SAP AG 2003. Assignment of technical objects: equipment and functional locations. General data Short text, use of work approval, validity period, priority, recall time, general status, overall condition, revision phase Reference object Either functional location or equipment and section. Areas of responsibility Maintenance planning plant, maintenance planner group, WCM work center, plant for work center and authorization group Location data Maintenance plant, location, room, and business area Planning data Basic date, scheduling, and actual date. © SAP AG. PLM320. 3-12.

(40) Work Approval: Status Sequence (1/2) Orders. Work approval. Applications. CRTE. CRTE. PREP. PREP. EXEC. PWP. PWP. WOCO. CLSD. CLSD.  SAP AG 2003. You can only complete (CLSD) the work approval when work is completed (WOCO) for all orders that are assigned.. © SAP AG. PLM320. 3-13.

(41) Work Approval: Status Sequence (2/2) (1). (4). CRTE CRTE PREP PREP. INAC INAC INAC INAC. REJC REJC. DLFL DLFL. REJC REJC. DLFL DLFL. CLSD CLSD. REJC REJC. (2). PREP PREP CHNG CHNG. PWP PWP. CLSD CLSD. INAC INAC. REJC REJC. (5). DLFL DLFL. (3). CHNG CHNG PREP PREP. INAC INAC. REJC REJC.  SAP AG 2003. (1) The status "Created" (CRTE) is a prerequisite for the status "Prepared" (PREP), "Object deactivated" (INAC), "Rejected" (REJC) and "Deletion Flag" (DLFL). (2) The status "Prepared" (PREP) is a prerequisite for the status "Change mode" (CHNG), "Work permit printed" (PWP), "Object deactivated" (INAC), "Rejected" (REJC) and "Deletion Flag" (DLFL). (3) The status "Change mode" (CHNG) is a prerequisite for the status "Prepared" (PREP), "Object deactivated" (INAC), and "Rejected" (REJC). (4) The status "Object deactivated" (CRTE) is a prerequisite for the status "Rejected" (REJC) and "Deletion Flag" (DLFL). (5) The status "Completed" (CLSD) or the status "Rejected" (REJC) is a prerequisite for the status "Deletion Flag" (DLFL). In some cases, there may be additional prerequisites for the individual statuses!. © SAP AG. PLM320. 3-14.

(42) Work Approval: Links. Order Order 1001 1001. Order Order 1002 1002. Order Order 1003 1003. Order Order 1005 1005. Order Order 1006 1006. WAP WAP 2002 2002. WAP WAP 2003 2003. (R3). WAP WAP 2001 2001. (R5). WCA WCA 3001 3001. WCA WCA 3002 3002. WCA WCA 4002 4002. WCA WCA 3003 3003.  SAP AG 2001. Observe the following assignment rules: You can assign a work approval to several different orders. Only one work approval may be assigned to each order. (Assignment rule R3) An application may be assigned to several work approvals (and vice versa). (Assignment rule R4) A work approval can only be assigned to one application per application type – this means, for example, that you cannot assign several work clearance applications to a work approval. (Assignment rule R5). © SAP AG. PLM320. 3-15.

(43) Work clearance application. Contents: Overview Work approval Applications Work clearance application Additional applications. Work Clearance Documents WCD template Operational WCD.  SAP AG 2003. © SAP AG. PLM320. 3-16.

(44) Work clearance application Enhanced model. Order. WCM object for control and communication between work approvals and Operational WCDs. Work Approval WC application Operational WCD. Further applications. Umbrella document for work approvals and Operational WCDs. Enhanced model. Standard model WCM object for control and communication between orders and Operational WCDs. Order WC application. Umbrella document for orders and Operational WCDs. Operational WCD. Standard model.  SAP AG 2003. The work clearance application represents the safety certificate for lockout/tagout. In the enhanced model, you use a work clearance application to control communication between work approvals and Operational WCDs. In the standard model, you use a work clearance application to control communication between orders and Operational WCDs. Direct assignment to orders enables the work clearance application to control the issuing of the status "Released for execution" in the order through the approval status.. © SAP AG. PLM320. 3-17.

(45) Work Clearance Application: Data Generic object services: different services are possible Status processing and audit trail: system status and user status. General data Reference object Areas of responsibility Location data Planning data. Assignment of partners: different roles possible Long text processing: several internal remarks Assignment of documents: link to document management system Assignment of permits: cross-document, interactive Use of catalog technique: catalog groups and codes.  SAP AG 2003. Assignment of technical objects: equipment and functional locations. General data Short text, use of application, validity period, priority, recall time, general status, overall condition, revision phase Reference object Either functional location or equipment and section. Areas of responsibility Maintenance planning plant, maintenance planner group, WCM work center, plant for work center and authorization group Location data Maintenance plant, location, room, and business area Planning data Basic date, scheduling, and actual date. © SAP AG. PLM320. 3-18.

(46) Work Clearance Application: Status Sequence (1/2) Orders or work approvals. WC application. Operational WCDs. CRTE PREP PWP TENT ?. CLSD. UNT TEST.  SAP AG 2003. Enhanced model You can only complete (CLSD) the work clearance application when all work approvals assigned have been completed (CLSD). Standard model You can only complete (CLSD) the work clearance application when work is completed (WOCO) for all orders that are assigned.. © SAP AG. PLM320. 3-19.

(47) Work Clearance Application: Status Sequence (2/2) (1). (4). CRTE CRTE PREP PREP. INAC INAC INAC INAC. REJC REJC. DLFL DLFL. REJC REJC. DLFL DLFL. CLSD CLSD. REJC REJC. (2). PREP PREP CHNG CHNG. PWP PWP. CLSD CLSD. INAC INAC. REJC REJC. TENT TENT. (5). DLFL DLFL. (3). CHNG CHNG PREP PREP. INAC INAC. REJC REJC.  SAP AG 2003. (1) The status "Created" (CRTE) is a prerequisite for the status "Prepared" (PREP), "Object deactivated" (INAC), "Rejected" (REJC) and "Deletion Flag" (DLFL). (2) The status "Prepared" (PREP) is a prerequisite for the status "Change mode" (CHNG), "Work permit printed" (PWP), "Object deactivated" (INAC), "Rejected" (REJC) and "Deletion Flag" (DLFL). (3) The status "Change mode" (CHNG) is a prerequisite for the status "Prepared" (PREP), "Object deactivated" (INAC), and "Rejected" (REJC). (4) The status "Object deactivated" (CRTE) is a prerequisite for the status "Rejected" (REJC) and "Deletion Flag" (DLFL). (5) The status "Completed" (CLSD) or the status "Rejected" (REJC) is a prerequisite for the status "Deletion Flag" (DLFL). In some cases, there may be additional prerequisites for the individual statuses!. © SAP AG. PLM320. 3-20.

(48) Work Clearance Application: Links WAP WAP 2001 2001. Order Order 1001 1001. WAP WAP 2002 2002. Order Order 1002 1002 (R1). WCA WCA 3001 3001. Operational Operational WCD WCD 4001 4001. Operational Operational WCD WCD 4002 4002. Operational Operational WCD WCD 4003 4003. Enhanced model. WCA WCA 3001 3001. WCA WCA 3002 3002. Operational Operational WCD WCD 4001 4001. Operational Operational WCD WCD 4002 4002. Standard model.  SAP AG 2001. Observe the following assignment rules: Enhanced model - An application may be assigned to several work approvals (and vice versa). (Assignment rule R4) - A work approval can only be assigned to one application per application type – this means, for example, that you cannot assign several work clearance applications to a work approval. (Assignment rule R5) - A work clearance application may be assigned to several Operational WCDs (and vice versa). (Assignment rule R2) Standard model - You can assign a work clearance application to several different orders. Only one order can be assigned to each work clearance application. (Assignment rule R1) - A work clearance application may be assigned to several Operational WCDs (and vice versa). (Assignment rule R2). © SAP AG. PLM320. 3-21.

(49) Additional applications. Contents: Overview Work approval Applications Work clearance application Additional applications. Work Clearance Documents WCD template Operational WCD.  SAP AG 2003. © SAP AG. PLM320. 3-22.

(50) Additional applications. Order Work Approval Work clearance application. ?. Operational WCD. Enhanced model.  SAP AG 2003. Stipulate whether you want to document and track different safety measures separately in your system. If this is the case, you need additional applications. As well as a work clearance application that displays the safety certificate especially for the lockout/tagout, it can also be necessary to take additional safety measures into consideration, for example, radiation protection, fire protection, or boiler protection. These safety measures are represented in the additional applications. The additional applications can only be used in the enhanced model of Work Clearance Management. They are combined with the work clearance applications under the work approval. The additional applications are industry-specific and necessary if additional safety measures must be managed as independent WCM objects in the system. They are programmed using the ABAP workbench.. © SAP AG. PLM320. 3-23.

(51) Work Clearance Documents. Contents Overview Work approval Applications Work clearance application Additional applications. Work Clearance Documents WCD template Operational WCD.  SAP AG 2001. © SAP AG. PLM320. 3-24.

(52) Work Clearance Document.  SAP AG 2003. The work clearance document contains a detailed description of lockout/tagout. The work clearance document is the only WCM object that also has items apart from the header data. As items, specify all the technical objects that are to be processed in connection with a lockout/tagout. The WCD may include equipment, functional locations, technical objects, that are not managed in the R/3 structure, and comments. The work clearance document has a header like every WCM object. It also has the following screens: Maintenance screen Switching screen (not for WCD templates). © SAP AG. PLM320. 3-25.

(53) Work Clearance Document: Structure. WCD template. Header Header. Template library. Item Item. Cannot be used to perform lockout/tagout. Operational WCD Can be assigned to work clearance applications. Item Item. Can be used to perform lockout/tagout. Item Item. ... ...  SAP AG 2003. There are two types of WCD: WCD template The WCD template is not used itself to perform lockout/tagout. You cannot switch or assign the WCD template. The WCD template serves only as a standard template. This means that you do not always have to create a new WCD for complex technical system structures. The WCD template enables you to create a template library. A library of WCD templates makes planning a lot simpler for lockout/tagout, improving safety. The advantage of creating a WCD template is that these work clearance documents are higher quality. When you copy from another operational WCD, particular attention is needed with regard to altered untagging conditions. Operational WCD You use the Operational WCD to perform lockout/tagout - you can switch and assign the Operational WCD.. © SAP AG. PLM320. 3-26.

(54) Work Clearance Document (Header): Data Generic object services: different services are possible Status processing and audit trail: system status and user status. General data Reference object Areas of responsibility. Assignment of partners: different roles possible Long text processing: several internal remarks. Location data. Assignment of documents: link to document management system. Planning data. Assignment of permits: cross-document, interactive Use of catalog technique: catalog groups and codes.  SAP AG 2003. Assignment of technical objects: equipment and functional locations. General data Short text, use of WCD, validity period, priority, recall time, general status, overall condition, revision phase Reference object Either functional location or equipment and section. Areas of responsibility Maintenance planning plant, maintenance planner group, WCM work center, plant for work center and authorization group Location data Maintenance plant, location, room, and business area Planning data Basic date, scheduling, and actual date. © SAP AG. PLM320. 3-27.

(55) Work Clearance Document (Item): Data. Item category Technical object or short text. Status processing and audit trail: system status and user status. Operational group Data for the tagging. Long text processing: several internal remarks. Data for the untagging Additional data. Assignment of documents: link to document management system. General data.  SAP AG 2003. Item category Technical object or short text Operational group Data for the tagging Tagging condition, tagging type, and sequence of the tagging Data for the untagging Untagging condition, untagging type, and sequence of the untagging. Additional data Indicator: Physical safety required, safety category, indicator: tag required, print format and tag number. General Data Location, switching location, and commentary. © SAP AG. PLM320. 3-28.

(56) Operational WCD: System Sequence CRTE CRTE PREP PREP. Header. Item. ITG ITG PROC PROC. CONF CONF. CONF CONF. BTG BTG. ETUG ETUG. PTAG PTAG. PTST PTST. ETG ETG. TEST TEST. ITG ITG. BTUG BTUG. UNT UNT. BTG BTG. ETUG ETUG. PTAG PTAG. PTST PTST. ETG ETG. BTUG BTUG. BUG BUG. BUG BUG. EUG EUG. EUG EUG CLSD CLSD  SAP AG 2003. Progress in the operational cycle is displayed for the item and also in the Operational WCD header: If all items have the same operational status, the status is displayed in the header. If only one conflict appears during switching, this is displayed in the header.. © SAP AG. PLM320. 3-29.

(57) Operational WCD: Links. WCA WCA 3001 3001. Operational Operational WCD WCD 4001 4001. WCA WCA 3002 3002. Operational Operational WCD WCD 4002 4002. Operational Operational WCD WCD 4003 4003.  SAP AG 2001. Observe the following assignment rule: A work clearance application may be assigned to several Operational WCDs, and vice versa (assignment rule R2).. © SAP AG. PLM320. 3-30.

(58) Data flow. Graphic planning List comparison. Any Work Clearance Document. Current Work Clearance Document. Clipboard. Other Work Clearance Documents.  SAP AG 2003. You can use any work clearance document as a template for creating another work clearance document. You have the option of connecting any external systems for processing, visualizing, and maintaining work clearance documents. The most common example is connecting to a graphic planning system, with which you can process items for work clearance documents. You can compare a work clearance document with your template or with other work clearance documents. The system then compares only the items of the work clearance documents to be compared. To track changes in the template or adapt one work clearance document to another, you can copy items in the clipboard. You can copy items from other work clearance documents to the clipboard.. © SAP AG. PLM320. 3-31.

(59) WCM Objects: Summary. You are now able to Describe the different WCM objects Explain the differences between WCM objects Create WCM objects.  SAP AG 2001. © SAP AG. PLM320. 3-32.

(60) Exercises Unit: WCM Objects. At the conclusion of this unit, you will be able to: • Create a work clearance application • Create a WCD template • Create an Operational WCD based on a WCD template • Assign an Operational WCD to a work clearance application At IDES, you must first create a work clearance application for the order before performing maintenance tasks. Technical objects whose operational condition is to be changed should be listed in an Operational WCD. You can use a WCD template to speed up the creation of the Operational WCD.. 2-1. Work clearance application 2-1-1 Create a work clearance application for your order. Planning plant: 1000 Responsible work center: T-ME## How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ Work clearance application:. © SAP AG. PLM320. _______________. 3-33.

(61) 2-2. WCD template 2-2-1 Use the tagging for pump set 2 to create a WCD template. Copy the pump station and pump set 1 to the object list. Planning plant: 1000 Responsible work center: T-ME## How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ WCD template:. 2-3. _______________. Operational WCD 2-3-1 Assign an Operational WCD to your work clearance application. This Operational WCD is based on your WCD template. How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ Operational WCD:. _______________. Tagging for pump set 2. © SAP AG. PLM320. 3-34.

(62) Solutions Unit: WCM Objects. 2-1. Work clearance application 2-1-1 SAP Menu → Logistics → Plant Maintenance → Maintenance Processing → Order → Change (= IW32) <WC application> (= <Ctrl> + <Shift> + <F9>) <Copy> (= <F5>). 2-2. WCD template 2-2-1 ... → SAP Menu → Logistics → Plant Maintenance → Work Clearance Management → WCD template → Create (= WCT1). 2-3. Operational WCD 2-3-1 ... → WC application → Change (= WCTL) Goto → Links → Work clearance document (= <Shift> + <F8>) <Create> (= <Shift> + <F5>). © SAP AG. PLM320. 3-35.

(63) Approvals. Contents Overview Approval process across WCM objects.  SAP AG 2001. © SAP AG. PLM320. 4-1.

(64) Approvals: Unit Objectives. At the conclusion of this unit, you will be able to Explain the term Approvals Differentiate between approvals and work approvals Use approvals.  SAP AG 2001. © SAP AG. PLM320. 4-2.

(65) Approvals: Overview. Customizing Further functions Order processing Lockout/Tagout. M C W. Approvals WCM Objects. Course Overview Introduction.  SAP AG 2001. © SAP AG. PLM320. 4-3.

(66) Overview. Contents Overview Approval process across WCM objects.  SAP AG 2001. © SAP AG. PLM320. 4-4.

(67) Overview. Operational WCD. WAP. .... Order. WCA.  SAP AG 2001. WCM approvals belong to the approvals for Plant Maintenance. The approvals are assigned to WCM objects at header level. It is possible to assign an approval to several WCM objects. This is not recommended. Processing depends on authorization. All activities are recorded.. © SAP AG. PLM320. 4-5.

(68) Basic Functions. Before starting the approval process Assignment to a WCM object Deleting the assignment. During the approval process Granting approval Withdrawing approval.  SAP AG 2003. The approval process begins when you set the status "Prepared" (PREP) in the WCM object. This means that you can now grant or revoke approvals, but you can no longer assign or delete approvals to a WCM object. You always assign an approval at the header level of the WCM object. This means you approve the entire WCM object and not individual items. You can assign more than one approval to a WCM object. However, each approval may only be used once for each WCM object. You can also assign an approval to more than one WCM object; however, this is not recommended for reasons of clarity.. © SAP AG. PLM320. 4-6.

(69) Additional Functions (1/3) Hierarchy level support. 1. AA. BB. CC. DD. 3. FF. EE. 2. 4. GG Approval. Hierarchy level.  SAP AG 2001. All approvals at a particular hierarchy level must be granted. Within a hierarchy level, there is no fixed order for granting approvals. © SAP AG. PLM320. 4-7.

(70) Additional Functions (2/3). Automatic withdrawal of approvals based on the hierarchy level a system status. Automatic assignment of approvals when you create a WCM object Protecting approvals from deletion Traffic light indicator for approval status Automatic granting of approvals.  SAP AG 2003. The traffic light indicator colors signify the following: Red. No required approval has been granted.. Yellow. At least one required approval has been granted, but at least one required approval is missing.. Green. All required approvals have been granted.. We recommend that exactly two approvals influence the traffic light indicator. This ensures that the relationship between colors and approvals is absolutely clear.. © SAP AG. PLM320. 4-8.

(71) Additional Functions (3/3). Blocking granting of approvals Based on existing assignments to WCM objects An assignment must exist for the approval Identify the direction This function safeguards the approval process across WCM objects Based on system or user status Status is assigned to an approval Approval can only be granted when the status assigned is active.  SAP AG 2001. Missing approval -- Approval granted. © SAP AG. PLM320. 4-9.

(72) Why can an Approval not be Granted?. A superior approval has not been granted. AA BB CC DD. Required assignments are not in place. The required system or user status is not active. Dependent approvals from assigned WCM objects have not been granted.  SAP AG 2003. Your goal is: Approval A should be granted before approval B: Assign approval A to hierarchy level 1, and approval B to hierarchy level 2. This means that approvals cannot be granted at superior hierarchy levels (for example, 2) until they have been granted at lower hierarchy levels (for example, 1). Approval may only be granted if an Operational WCD has been assigned: Activate the assignment function for the work clearance application. Ensure that there is a dependence with subordinate WCM objects (Operational WCDs). Approval for an Operational WCD can only be granted when the Operational WCD is tagged: Assign the system status Tagged (ETG) to the approval. This means the person responsible can only issue approval when the Operational WCD is tagged.. © SAP AG. PLM320. 4-10.

(73) Approval Process Across WCM Objects. Contents Overview Approval process across WCM objects.  SAP AG 2001. © SAP AG. PLM320. 4-11.

(74) Approval Process Across WCM Objects. Indicator: process relevant. Approval. Work approval. A. y Approval category Direction. Work clearance application. B. Operational WCD. y. C. y.  SAP AG 2001. The approval process transports information at all levels of the WCM object. Each level can trigger or block the approval process. Within an approval category you can specify that approval will be granted for a WCM object dependent on whether an approval has already been granted to an assigned WCM object. The dependency may be in the direction of a superior WCM object, a subordinate WCM object, or neutral. The direction defines from which direction approvals should be considered – from superior (UP) or from subordinate (DN) WCM objects. For approvals in an approval category, if a dependency from a superior WCM object to a subordinate WCM object has been defined (and the opposite is also true), these dependencies will be completely ignored. Missing approval – Approval granted. © SAP AG. PLM320. 4-12.

(75) Approval Process Across WCM Objects: Example (1/2). C. X. D. y. A B. B. X. E. y. C D E. A. X. F. y. F.  SAP AG 2001. Type x approvals are controlled from below to above – that means approvals are required at lower levels. Type y approvals are controlled from above to below – that means approvals are required at higher levels.. © SAP AG. PLM320. 4-13.

(76) Approval Process Across WCM Objects: Example (2/2). A1. ?. B. X. E. y. F1. ?. A1. A2. B. C D A2. ?. C. X. D. y. F2. ?. E. F1. F2.  SAP AG 2001. Type y approvals are controlled from below to above – that means approvals are required at lower levels. Type x approvals are controlled from above to below – that means approvals are required at higher levels.. © SAP AG. PLM320. 4-14.

(77) Approvals: Summary. You are now able to Explain the term Approvals Differentiate between approvals and work approvals Use approvals.  SAP AG 2001. © SAP AG. PLM320. 4-15.

(78) © SAP AG. PLM320. 4-16.

(79) Exercises Unit: Approvals. At the conclusion of this unit, you will be able to: • Explain the reason for approvals • Use approvals. IDES uses approvals to guarantee safe and secure work clearance management.. 3-1. At what level do you assign approvals to WCM objects? ____________________________________________________________ ____________________________________________________________. 3-2. Is it possible to assign approvals to items in a WCD? ____________________________________________________________ ____________________________________________________________. 3-3. How do you initiate the approval process? ____________________________________________________________ ____________________________________________________________. 3-4. What is the relationship between WCM approvals and permits for Plant Maintenance? ____________________________________________________________ ____________________________________________________________. 3-5. Is it possible to define dependencies between approvals: – in a WCM object? – between two WCM objects? ____________________________________________________________ ____________________________________________________________. © SAP AG. PLM320. 4-17.

(80) 3-6. What logical connection links approvals at a hierarchy level? ____________________________________________________________ ____________________________________________________________. 3-7. Do all approvals affect the approval status? ____________________________________________________________ ____________________________________________________________. 3-8. Is it possible to automate the approval process? ____________________________________________________________ ____________________________________________________________. 3-9. How can the granting of an approval be blocked? ____________________________________________________________ ____________________________________________________________. 3-10. Is it possible to copy approvals? ____________________________________________________________ ____________________________________________________________. 3-11. Is it possible to construct a reciprocal relationship between the approval processes in different WCM objects? ____________________________________________________________ ____________________________________________________________. 3-12. How does the system deal with missing approvals? ____________________________________________________________ ____________________________________________________________. 3-13. What problem may arise here? ____________________________________________________________ ____________________________________________________________. 3-14. How can you protect the reciprocal relationship between different WCM objects? ____________________________________________________________ ____________________________________________________________. 3-15. When or where are approvals granted automatically? ____________________________________________________________ ____________________________________________________________. © SAP AG. PLM320. 4-18.

(81) Solutions Unit: Approvals. 3-1. At WCM object header level.. 3-2. No, the assignment only takes place at header level in the WCM object.. 3-3. The WCM object must be prepared (PREP).. 3-4. WCM approvals form part of the permits for Plant Maintenance.. 3-5. Yes, you can define dependencies in a WCM object and between WCM objects.. 3-6. The AND connection – all approvals at a given hierarchy level must have been granted before approvals at the next hierarchy level can be processed.. 3-7. No, only the approval for which the corresponding flag was set.. 3-8. Yes, you can automate the approval process.. 3-9. You can use User status, for example, to block granting of approvals.. 3-10. No, you cannot copy approvals.. 3-11. Yes, you can build a reciprocal relationship.. 3-12. Missing approval = Approval granted. 3-13. If you delete an approval assignment, that corresponds to granting an approval.. 3-14. You make the assignment compulsory.. 3-15. In the change mode of the corresponding WCM object.. © SAP AG. PLM320. 4-19.

(82) Lockout/Tagout. Contents Operational cycle Checks Conflict rules. Simulations Operational protection and protected areas Adjust untagging.  SAP AG 2001. © SAP AG. PLM320. 5-1.

(83) Lockout/Tagout: Unit Objectives. At the conclusion of this unit, you will be able to Perform lockout/tagout.  SAP AG 2001. © SAP AG. PLM320. 5-2.

(84) Lockout/Tagout: Overview. Customizing Further functions Order processing Lockout/Tagout. M C W. Approvals WCM Objects. Course Overview Introduction.  SAP AG 2001. © SAP AG. PLM320. 5-3.

(85) Overview. Contents: Overview Operational Cycle Checks Conflict Rules. Simulations Operational Protection ? Protected Areas Adjust Untagging.  SAP AG 2003. © SAP AG. PLM320. 5-4.

(86) Lockout/Tagout. Order Work Approval Work clearance application. Order. Further applications. Operational WCD. WC application Operational WCD. Enhanced model. Standard model.  SAP AG 2003. This process is composed of the orderly tagging and later untagging of technical objects, so that maintenance tasks and tests can be performed safely at the technical objects. The operational processing of lockout/tagout is described with the help of the operational cycle. For a lockout/tagout that is assigned to locations, shop papers are required on site for the switching. This involves an operational list, that is a list of the individual switching actions to be performed, and so-called tags and test tags. Operational lists and tags and test tags can be printed according to the layout details of the plant concerned. Checks and simulations help you to ensure that lockout/tagout is safe and can be processed without any conflicts.. © SAP AG. PLM320. 5-5.

(87) Operational Cycle. Contents Overview Operational Cycle Checks Conflict Rules. Simulations Operational Protection. Protected Areas. Adjust Untagging.  SAP AG 2003. © SAP AG. PLM320. 5-6.

(88) Operational Condition Operational conditions give a detailed description of conditions or parameters for technical objects (for example, Open, Closed): Tagging condition = operational condition for tagging Untagging condition = operational condition for (temporary) untagging. Open. Closed  SAP AG 2001. For each operational condition you can define whether it is valid for tagging, (temporary) untagging, or for both. You can group operational conditions logically: An operational group is a logical grouping of operational conditions designed to minimize conflict rules. An operational class is a logical grouping of operational conditions based on the technical characteristics of technical objects.. © SAP AG. PLM320. 5-7.

(89) Operational Types Operational types allow use of different tags for the same operational condition (for example, red/yellow/white tags) Tagging type = operational type for tagging Untagging type = operational type for (temporary) untagging.  SAP AG 2003. Operational types help you to further define same operational conditions. The choice of conflict rules influences the use of the operational type.. © SAP AG. PLM320. 5-8.

(90) Operational Groups. ON. Electrical. OFF. Open. Mechanical. Logical grouping of operational conditions to minimize conflict rules Where conflict rules apply. Closed.  SAP AG 2001. You can assign operational conditions to several operational groups. We recommend that you only assign an operational condition to one operational group. Operational groups are not the same as Operational classes. © SAP AG. PLM320. 5-9.

(91) Operational Phase Phase in the operational cycle during which an Operational WCD item goes through several statuses in a certain order. Condition changes are recorded. There are three operational phases: Tagging phase Temporary untagging phase Untagging phase.  SAP AG 2003. The first status in the operational phase gives notices of an activity - a change of operational condition/type: Tag (BTG) Untag temporarily (BTUG) Untag (BUG) An operational tag is printed, the status following confirms the print: Tag printed (PTAG) Test tag printed (PTST) The last status confirms that the activity has been performed on location: Tagged (ETG) Temporarily untagged (ETUG) Untagged (EUG). © SAP AG. PLM320. 5-10.

(92) Operational Cycle Tagging cycle with temporary untagging phase Tagging Taggingphase phase. Temporary Temporary untagging untaggingphase phase. Untagging Untaggingphase phase. Test cycle Tagging Taggingphase phase. Temporary Temporary untagging untaggingphase phase. Tagging cycle without temporary untagging phase Tagging Taggingphase phase. Untagging Untaggingphase phase.  SAP AG 2003. The operational cycle is a cycle consisting a maximum of three operational phases. The operational cycle may be formed in various different ways: Tagging cycle with temporary untagging phase Test cycle Tagging cycle without temporary untagging phase In each operational cycle, the Operational WCD items go through several statuses in a particular order: Tagging phase = tag (BTG), tag printed (PTAG), tagged (ETG) Temporary untagging = untag temporarily (BTUG), test tag printed (PTST), temporarily untagged (ETUG) Untagging phase = untag (BUG), untagged (EUG). © SAP AG. PLM320. 5-11.

(93) Operational Cycle: Example Standard operational cycle. Reduced operational cycle. ITG ITG. ITG ITG. Initial status (ITG) Tagging phase Tag (BTG). BTG BTG. ETUG ETUG. Tag printed (PTAG) Tagged (ETG). PTAG PTAG. PTST PTST. PTAG PTAG. ETG ETG. BTUG BTUG. ETG ETG. Temporary untagging phase Untag temporarily (BTUG) Test tag printed (PTST) Temporarily untagged (ETUG). BUG BUG Untagging phase. EUG EUG. EUG EUG. Untag (BUG) Untagged (EUG).  SAP AG 2003. You can reduce the operational cycle. If you use Operational WCDs you can skip the following statuses Starting status - Tag (BTG) - Untag temporarily (BTUG) - Untag (BUG) Print status - Tag printed (PTAG) - Test tag printed (PTST) End status - Temporarily untagged (ETUG) - Untagged (EUG) The entire operational cycle is processed internally. © SAP AG. PLM320. 5-12.

(94) Operational WCD: System Sequence CRTE CRTE PREP PREP. Header. Item. ITG ITG PROC PROC. CONF CONF. CONF CONF. BTG BTG. ETUG ETUG. PTAG PTAG. PTST PTST. ETG ETG. TEST TEST. ITG ITG. BTUG BTUG. UNT UNT. BTG BTG. ETUG ETUG. PTAG PTAG. PTST PTST. ETG ETG. BTUG BTUG. BUG BUG. BUG BUG. EUG EUG. EUG EUG. POST POST. CLSD CLSD. PROT PROT.  SAP AG 2001. Progress in the operational cycle is displayed for the item and also in the Operational WCD header: If all items have the same operational status, the status is displayed in the header. If only one conflict appears during tagging/untagging, this is displayed in the header.. © SAP AG. PLM320. 5-13.

(95) Checks. Contents. Overview Operational Cycle Checks Conflict Rules. Simulations Operational Protection. Protected Areas. Adjust Untagging.  SAP AG 2003. © SAP AG. PLM320. 5-14.

(96) General Checks For each operational step, the system checks if The user has authorization Tagging/untagging is blocked by an approval Tagging/untagging is blocked by operational protection This is a valid operational step.  SAP AG 2001. Checks help you to ensure that lockout/tagout is safe and that it avoids conflicts. Some checks are optional, some compulsory. You can deactivate optional checks in Customizing.. © SAP AG. PLM320. 5-15.

(97) Further Checks: Overview. Tagging phase BTG. PTAG. Temporary untagging phase ETG. BTUG. PTST. ETUG. Untagging phase BUG. EUG. Reference object Time frame Completeness and correctness Test Cycle Untagging Conflict. Tagging phase Tag (BTG) Tag printed (PTAG) Tagged (ETG). Temporary untagging phase Untag temporarily (BTUG) Test tag printed (PTST) Temporarily untagged (ETUG). Untagging phase Untag (BUG) Untagged (EUG).  SAP AG 2001. © SAP AG. PLM320. 5-16.

(98) Check: Reference Object Prerequisite When the operational process begins, a reference object log is kept in the system until the Operational WCD is completed. Check For each technical object to be tagged/untagged, the system checks if this object is already a reference object in a processed Operational WCD. Every agreement is displayed..  SAP AG 2003. Optional check to see if the object to be tagged/untagged is not already a reference object in an active lockout/tagout situation. The check is for information purposes only and does not affect tagging/untagging. You can deactivate the check.. © SAP AG. PLM320. 5-17.

(99) Check: Time Frame Prerequisite At the start of a new operational phase, the system logs the chosen operational condition/type. This entry is only deleted once the operational condition/type is confirmed. Check The system checks if there are existing entries for technical objects to be tagged/untagged. A technical object cannot have different operational conditions..  SAP AG 2003. Optional check whether a technical object (that should be tagged/untagged and thereby obtain a new operational condition/type) does not already have another operational condition/type within an operational group not yet confirmed in the system. You cannot ignore the check. You can alter or deactivate the check.. © SAP AG. PLM320. 5-18.

(100) Check: Completeness and Correctness Prerequisite Unlike the tagging condition/type, the untagging condition/type must first be maintained for (temporary) untagging. Check The system checks at the start of the (temporary) untagging phase if the untagging condition/type has been maintained..  SAP AG 2003. Compulsory check If the required untagging condition/type has been maintained for a technical object. At the latest, you must maintain this by the time of (temporary) untagging. You cannot ignore the check.. © SAP AG. PLM320. 5-19.

(101) Check: Test Cycle Prerequisite All work clearance applications assigned are either complete, or they permit a test cycle - this means a test cycle is allowed for the Operational WCD. The system checks if a test cycle is possible for the Operational WCD..  SAP AG 2003. Compulsory check The system checks if a test cycle is permitted for the Operational WCD. You cannot ignore the check. Special authorization is required to do that.. © SAP AG. PLM320. 5-20.

(102) Check: Untagging Prerequisite All work clearance applications assigned are complete - this means the Operational WCD is untaggable. Check The system checks if the Operational WCD is untaggable..  SAP AG 2003. Compulsory check The system checks if the Operational WCD can be untagged. You cannot ignore the check. Special authorization is required to do that.. © SAP AG. PLM320. 5-21.

(103) Check: Conflict Prerequisite A conflict record is written at the start of a new tagging phase. You can only delete this entry when the item is (temporarily) untagged. Check At the beginning of an operational phase, the desired operational condition/type for a technical object is checked against all conflict records. This check is based on general or user-defined conflict rules..  SAP AG 2003. Compulsory check If required operational conditions/types for a technical object can be switched within an operational group. In case of conflict, you can Cancel switching and deal with the conflict or Ignore the conflict and go ahead with the switching. Special authorization is required to do that. In the case of a conflict that you have ignored, the system assigns the status conflict (CONF) to the technical object. The system always assumes that the switch was performed. For example: the operational condition/type A generates conflicts. If you ignore these conflicts, then A is the new operational condition/type for the system. If the technical object for which the conflict occurred is untagged during the switching, then the conflict is automatically withdrawn.. © SAP AG. PLM320. 5-22.

(104) Conflict Rules. Contents: Overview Operational Cycle Checks Conflict Rules. Simulations Operational protection. Protected areas. Adjust Untagging.  SAP AG 2003. © SAP AG. PLM320. 5-23.

(105) Conflict Rules. General conflict rules. User-defined conflict rules.  SAP AG 2001. The conflict check is based on the conflict rules. Conflict rules apply to tagging and untagging. You can decide whether to use the general or user-defined conflict rules. The decision is taken at company level for each planning plant. The conflict rules only apply within an operational group.. © SAP AG. PLM320. 5-24.

(106) General Conflict Rules If the user does not define conflict rules, the system compares the current and target operational types. The result is either N =. Note. E. Error message (Different). =. (Same). Consequences The operational type cannot be overwritten Operational conditions have no impact on the conflict check You cannot define asymmetric conflict rules.  SAP AG 2001. For operational group E (= electrical) we have two different operational conditions: (ON/OFF) Two different operational types are required for these operational conditions: (1, 2). © SAP AG. PLM320. 5-25.

(107) User-Defined Conflict Rules If the user defines conflict rules, the system compares the current and target operational conditions/types. The result is either N =. Note. W =. Warning. E. Error. =. Consequences You can overwrite the operational type Operational conditions influence the conflict check You are able to define asymmetric conflict rules The system interprets missing conflict rules as errors.  SAP AG 2003. For operational group E (= electrical) we have two different operational conditions: (ON/OFF) There are three different operational types for these operational conditions: (RED, YELLOW, WHITE) 2 x 3 = 6 possible combinations from operational condition/type When performing conflict checks, the system will compare current operational condition/type and target operational condition/type. In this case, that means a possible 6 x 6 = 36 conflict rules.. © SAP AG. PLM320. 5-26.

(108) Simulations. Contents: Overview Operational Cycle Checks Conflict Rules. Simulations Operational Protection. Protected Areas. Adjust Untagging.  SAP AG 2003. © SAP AG. PLM320. 5-27.

(109) Simulations. What would happen if ...?.  SAP AG 2001. You can run each check as a simulation. There are simulations without a corresponding check. You can start each simulation manually. Some simulations start automatically.. © SAP AG. PLM320. 5-28.

(110) Operational Protection. Protected Areas. Contents: Overview Operational Cycle Checks Conflict Rules. Simulations Operational Protection. Protected Areas. Adjust Untagging.  SAP AG 2003. © SAP AG. PLM320. 5-29.

(111) Operational Protection This ensures that the operational condition of a technical object in an Operational WCD may only be changed from specific Operational WCDs. Once operational protection has been set, you can only change operational condition from Operational WCDs that are directly linked as a result of superior work clearance applications (= protected areas). The operational protection only applies within an operational group..  SAP AG 2003. Operational protection enables you, for example, to shield the change in Operational condition of an Operational WCD item against other Operational WCDs for test purposes. Usage defines if an Operational WCD is able to set operational protection. The operational protection always applies to the technical object and the operational group assigned to it.. © SAP AG. PLM320. 5-30.

(112) Protected Areas Operational WCDs from which it is possible to change the operational status of a technical object (after operational protection has been set). The protected area includes all Operational WCDs that are directly linked as a result of superior work clearance applications..  SAP AG 2003. A technical object can be switched within the protected area, but outside the protected area a technical object cannot be switched. The protected area is displayed on the switching screen.. © SAP AG. PLM320. 5-31.

(113) Protected Areas: Example (1/2). WCA WCA 3001 3001. (1). Operational Operational WCD WCD 4001 4001. WCA WCA 3002 3002. Operational Operational WCD WCD 4002 4002. Operational Operational WCD WCD 4003 4003. Operational Protection. (2). Operational Operational WCD WCD 4004 4004. Protected area. WCA WCA 3001 3001. Operational Operational WCD WCD 4001 4001. WCA WCA 3002 3002. Operational Operational WCD WCD 4002 4002. Operational Operational WCD WCD 4003 4003. Operational Operational WCD WCD 4004 4004.  SAP AG 2003. (1) An operational protection is set for an item of operational WCD 4001. Because of the assigned work clearance application 3001, both operational WCDs 4001 and 4002 form the protected area. (2) An operational protection is set for an item of operational WCD 4002. Because of the assigned work clearance application 3001 and 3002, the operational WCDs 4001, 4002, and 4003 form the protected area.. © SAP AG. PLM320. 5-32.

(114) Protected Areas: Example (2/2). (3). WCA WCA 3001 3001. Operational Operational WCD WCD 4001 4001. (4). Operational Operational WCD WCD 4002 4002. WCA WCA 3001 3001. Operational Operational WCD WCD 4001 4001. WCA WCA 3002 3002. Operational Operational WCD WCD 4003 4003. Operational Operational WCD WCD 4004 4004. WCA WCA 3002 3002. Operational Operational WCD WCD 4002 4002. Operational Operational WCD WCD 4003 4003. Operational Operational WCD WCD 4004 4004.  SAP AG 2003. (3) An operational protection is set for an item of operational WCD 4003. Because of the assigned work clearance application 3002, the operational WCDs 4002 and 4003 form the protected area. (4) An operational protection is set for an item of operational WCD 4004. As there is no work clearance application assigned to the operational WCD, operational WCD 4004 forms the protected area.. © SAP AG. PLM320. 5-33.

(115) Adjust Untagging. Contents: Overview Operational Cycle Checks Conflict Rules. Simulations Operational Protection. Protected Areas. Adjust Untagging.  SAP AG 2003. © SAP AG. PLM320. 5-34.

(116) Adjust Untagging Operational WCD Technical Object. Untagging condition. P1 V1 V2. ON Open. Untagging type. P1 V1 V2. Technical Object Untagging Untagging condition type P1 V1 V2. Technical Operational Operational object condition type. ON Open. ON Closed Closed. Operational condition. Operational type. ON Closed Closed. 2 1 1. 2 1 1.  SAP AG 2003. You can compare the untagging condition/type with the current operational condition/type. The following prerequisites apply: We are dealing with an Operational WCD. The Operational WCD is either "Prepared" (PREP) or in "Change mode" (CHNG). The item is not in the temporary untagging phase or untagging phase. The system knows the current operational condition/type for the item.. © SAP AG. PLM320. 5-35.

(117) Lockout/Tagout: Summary. You are now able to Perform lockout/tagout.  SAP AG 2001. © SAP AG. PLM320. 5-36.

(118) Exercises Unit: Lockout/Tagout. At the conclusion of this unit, you will be able to: • Carry out tagging • Carry out untagging. Before you begin lockout/tagout, we recommend you run a test for the entire process.. 4-1. Tagging 4-1-1 Activate the approval process for your work clearance application and Operational WCD. How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ 4-1-2 Perform all necessary tasks so tagging can begin. How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ 4-1-3 Carry out tagging. How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________. © SAP AG. PLM320. 5-37.

(119) 4-2. Plant Maintenance 4-2-1 Arrange for the maintenance work to be carried out. How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ 4-2-2 Confirm that maintenance work has been carried out. How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________. 4-3. Untagging 4-3-1 Perform all necessary tasks so untagging can begin. How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ 4-3-2 Carry out untagging. How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ 4-3-3 When untagging has been performed, complete your Operational WCD. How do you do proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________. © SAP AG. PLM320. 5-38.

(120) Solutions Unit: Lockout/Tagout. 4-1. Tagging 4-1-1 Set status Prepared (PREP) for the work clearance application ... → WC application → Change (= WCTL) WC application → Functions → Prepare → Set (= <Ctrl> + <F1>) + Set status Prepared (PREP) for the Operational WCD ... → Operational WCD → Change (= WCT7) Operational WCD → Functions → Prepare → Set (= <Ctrl> + <F1>) 4-1-2 Grant approval TECH1 to the work clearance application ... → WC application → Change (= WCTL) Goto → Approvals... (= <F7>) Grant approval TECH1 4-1-3 Tag Operational WCD ... → Operational WCD → Change (= WCT7) Goto → Switching operation (= <Ctrl> + <Shift> + <F2>) Carry out tagging. © SAP AG. PLM320. 5-39.

(121) 4-2. Plant Maintenance 4-2-1 Approving a work clearance application ... → WC application → Change (= WCTL) Approval TECH2 is granted automatically Set status Released for execution (EXEC) in order SAP Menu → Logistics → Plant Maintenance → Maintenance Processing → Order → Change (= IW32) <Released for execution> (= <Ctrl> + <Shift> + <F10>) 4-2-2 Setting status Work complete (WOCO) in the order SAP Menu → Logistics → Plant Maintenance → Maintenance Processing → Order → Change (= IW32) <Work complete> (= <Ctrl> + <Shift> + <F11>). 4-3. Untagging 4-3-1 Set status Complete (CLSD) for the work clearance application ... → WC application → Change (= WCTL) <Yes> 4-3-2 Untag Operational WCD ... → Operational WCD → Change (= WCT7) Goto → Switching operation (= <Ctrl> + <Shift> + <F2>) Carry out untagging 4-3-3 Set status Complete (CLSD) for the Operational WCD Operational WCD → Functions → Complete (= <Ctrl> + <F2>). © SAP AG. PLM320. 5-40.

(122) Order Processing. Contents Activating WCM Example.  SAP AG 2001. © SAP AG. PLM320. 6-1.

(123) Order Processing: Unit Objectives. At the conclusion of this unit, you will be able to Activate WCM Use WCM.  SAP AG 2001. © SAP AG. PLM320. 6-2.

(124) Order Processing: Overview. Customizing Further functions Order processing Lockout/Tagout. M C W. Approvals WCM Objects. Course Overview Introduction.  SAP AG 2001. © SAP AG. PLM320. 6-3.

(125) Activating WCM. Contents: Activating WCM Example.  SAP AG 2003. © SAP AG. PLM320. 6-4.

(126) WCM and the Maintenance Process. Work WorkClearance Clearance Management Management. Maintenance Maintenanceplan plan. Notification Notification. SCADA SCADA. Create Create order order. Plan Plan order order. Release Release order order. Work WorkClearance Clearance Management Management. Confirm Confirm order order. Complete Complete order order. History/analysis History/analysis.  SAP AG 2003. Orders are linked to WCM at order header level. For WCM-relevant orders you cannot perform the maintenance tasks until you have released them (status "Released for Execution" (EXEC)). Setting the tasks to "released" depends on the WCM architecture and whether the valuation was activated. Connecting orders to WCM is not absolutely necessary. Work clearance management enables you to carry out safety measures without an order. For example, this is the case if every change within the asset should or must be documented but the order is not needed for planning or to collect costs.. © SAP AG. PLM320. 6-5.

No results found