Thomas Jussen, Mirko Kloppenburg                                   Best Practice in Process ManagementLufthansa Technik AG...
OverviewIntegration of normative and legislative requirements into processes                     Questions answered by wor...
How to connect requirements and processes?Common practice: Registration of all “relevant” requirements in     management ...
How to check conformity?Two different approaches:a) Annual conformity evaluation of all processesb) Conformity check befor...
How to decide about relevance of requirements?Possible criteria to consider integration of requirements:     Certificate ...
How to get information about changing requirements?Common practice: Subscription of update services (e.g., Global Norm, Q...
OverviewIntegration of normative and legislative requirements into processes                     Questions answered by wor...
Follow our blog to receive updates:                                                                          http://www.BP...
Upcoming SlideShare
Loading in …5
×

BPinPM - Integration of Requirements

605 views

Published on

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
605
On SlideShare
0
From Embeds
0
Number of Embeds
168
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

BPinPM - Integration of Requirements

  1. 1. Thomas Jussen, Mirko Kloppenburg Best Practice in Process ManagementLufthansa Technik AGManagement System, HAM TQ32/D Integration of requirements into processesWeg beim Jäger 19322335 Hamburg Hamburg, March 2012
  2. 2. OverviewIntegration of normative and legislative requirements into processes Questions answered by workshop key findings:  How to connect requirements and processes?  How to check conformity?  How to decide about relevance of requirements?  How to get information about changing requirements?Best Practice in Process ManagementIntegration of requirements – February 2012, Page 2Copyright© Lufthansa Technik AG. All rights reserved.Subject to restrictions and disclaimer on last page.
  3. 3. How to connect requirements and processes?Common practice: Registration of all “relevant” requirements in management system database (e.g., into interpreted tasks, objects, etc.) Assignment of requirements to processes (e.g., processes, activities, documents, roles, organizational units) Proof of conformity by system-based reportsPromising practice: Integration of interpreted requirements into process descriptions allows employees to be in compliance to requirements based on management systemBest Practice in Process ManagementIntegration of requirements – February 2012, Page 3Copyright© Lufthansa Technik AG. All rights reserved.Subject to restrictions and disclaimer on last page.
  4. 4. How to check conformity?Two different approaches:a) Annual conformity evaluation of all processesb) Conformity check before publishing of every single processBest Practice in Process ManagementIntegration of requirements – February 2012, Page 4Copyright© Lufthansa Technik AG. All rights reserved.Subject to restrictions and disclaimer on last page.
  5. 5. How to decide about relevance of requirements?Possible criteria to consider integration of requirements: Certificate / approval necessary External audits foreseeable Training of employees does not cover requirements Risk assessment indicates necessity Application of requirement not obviousTypes of requirements: normative (e.g., ISO, EN, OHSAS) legislative (e.g., foreign trade law, aviation law, explosives law)All participants refuse integration of customer-specific requirements!Best Practice in Process ManagementIntegration of requirements – February 2012, Page 5Copyright© Lufthansa Technik AG. All rights reserved.Subject to restrictions and disclaimer on last page.
  6. 6. How to get information about changing requirements?Common practice: Subscription of update services (e.g., Global Norm, QUMedia SARA, WEKA) Contracting of external experts (e.g., for international requirements) Continuous communication with authority, norm association etc. Integration into development process of laws and norms (e.g., by commenting on drafts)Promising practice: Update of local requirements in management system by local expertsBest Practice in Process ManagementIntegration of requirements – February 2012, Page 6Copyright© Lufthansa Technik AG. All rights reserved.Subject to restrictions and disclaimer on last page.
  7. 7. OverviewIntegration of normative and legislative requirements into processes Questions answered by workshop key findings:  How to connect requirements and processes?  How to check conformity?  How to decide about relevance of requirements?  How to get information about changing requirements?Best Practice in Process ManagementIntegration of requirements – February 2012, Page 7Copyright© Lufthansa Technik AG. All rights reserved.Subject to restrictions and disclaimer on last page.
  8. 8. Follow our blog to receive updates: http://www.BPinPM.net For additional information, please contact: Mirko.Kloppenburg@BPinPM.net Lufthansa Technik AG, HAM TQ32/D Weg beim Jäger 193 22335 Hamburg, Germany Thank you for your attention.Copyright© Lufthansa Technik AG. All rights reserved.The information contained in this presentation is proprietary to Lufthansa Technik AG and is disclosed in confidence. The presentationand the information contained herein shall be kept strictly confidential and shall not be used, disclosed to others or reproduced withoutthe express written consent of Lufthansa Technik AG. Nothing contained in this publication shall constitute any warranty, guarantee orliability for LufthansaManagement its subsidiaries and affiliates but is for information purposes only. Accordingly, Lufthansa Technik AGBest Practice in Process Technik AG,Integration of requirements – February 2012, Page 8its subsidiaries and affiliates neither expressly nor conclusively accept responsibility or liability for the actuality, accuracy andCopyright© Lufthansa Technik AG. All and reserved.completeness of the statementsrights information contained in this publication.Subject to restrictions and disclaimer on last page.

×