SlideShare ist ein Scribd-Unternehmen logo
1 von 4
SAPRODUCT IT UK LIMITED– MR. RONEN MADAR
Introduction
In the last few years I was involved with few large ERP – IT projects which were supposed to
be driven by clear and well defined practices and methodologies , To my disappointment I
found in most cases that the distance between the original business objectives and the
achievements was not realistic and furthermore I was extremely unhappy with the fact that the
people who are supposed to be the life guards of these processes do not understand the idea
of what ERP project or Harmonization project is all about to a level that they created an
extreme and unnecessary challenges to the organization they work for.
As a results of the above mentioned reasons I have decided to publish this short document
which I believe will set up a short guideline for whoever want to manage Harmonization
activities properly. The document is displayed on my profile.
ERP and BPM standards
Standardization
Harmonization means creating uniform business processes across various divisions or
locations. The expected results are processes that consistently meet their cost and
performance objectives using a well-defined practice. Standardization, thus, reduces the risk
of failure.
Through standardization, individual business units can share expenses, and will benefit from
a company-wide business process management (BPM). Corporate-wide development of
business processes lowers the total expenses, using economics of scale.
Harmonization
looking for the “prevention or elimination of differences in the technical content of standards
has the same scope” .Harmonization looks at differences between process standard, and sets
bounds to the degree of their variation.
Example: There are various standards for the procurement process, such as ASN processing,
STO processing and external direct inbound processing.
In the context of Business Process Management, harmonization defines the extent of
standards and how they fit together, but it does not attempt to make different standards
uniform.
Application of Standardization and Harmonization
A company can establish standards across various divisions and geographies. The three
levels of harmonization:
• Strategic positioning, and Strategy
• Business processes
• Information technology: Configuration of ERP systems, etc.
Standardizing Business Processes for Profitability
Standardization of Business Processes intends to improve performance and to give
management more control over operational performance. (The most popular measure for
performance is the cost of executing the process. Although it is no less important, the quality
of the results is less often considered.) Finally, the impact on other business processes and
existing IT system needs to be considered, such as the ability to apply the standard
performance measures
• The process becomes more reliable.
• Less expenses in development of new practices, and less expense in the
administration of processes.
• Process standardization is an important prerequisite for the standardization of IT systems.
Standardization and Harmonization in a Practice Example
Example, the consumer logistics company runs operations in more than 10
countries, selling goods through large retailers. In advanced countries, such as Canada, large
retailers request to provide a service bid over the internet through Portal. On the other end is
Peru, where open office face to face communications are common and where the service
provider walks in to provide service bid.
For this company, there have been 40 different sales and transportation processes in the 10
different countries with significant differences in performance.
Strict standardization attempts to make the transportation process in all countries the same.
One of the two countries will lose as the standard becomes a perfectly suitable approach for
the other country: If Canada’s Portal approach is selected as standard; Peru cannot serve its
face to face providers.
The harmonization approach analyzes requirements from all countries and creates 2 standard
sales and transportation processes:
• Portal Bid
• Through fax, letter, or via telephone
• Open office
With the harmonization approach, there are only three (rather than forty) standards for the
sales process. In contrast to a single, strict standardization, every country sees its
requirements attended through a standard specific to their needs It is also possible that some
countries might implement two or even all three sales order processes in parallel to attend to
different groups of customers.
Criteria for Standardization
• Decisions about standardization are process-specific. In the example above, the company
needed just two standard processes.
• A precondition for any process standardization is that the requirements for processes are
sufficiently similar.
Qualitative Criteria for Standardization
1. Clear decision rules for standardization
and harmonization- Business Objectives
2. Criteria when process variants
should not be standardized – Legal requirements
3. Criteria for selecting the best
standard. These should be based on process performance and process cost- SAP best
practice, Supply chain council.
• Business processes: Consider all processes of the extended value chain. Processes that
belong to different types of logistics, sales channels, or product development are hard to
standardize:
o Type of logistics: Make-to-Order, Make-to-Stock, Inbound, outbound, staging to production
o Technological readiness of the relevant parties in the extended value chain. In the
example above, Providers were not yet ready for the Portal exchange.
o Geography and compliance: Country-specific requirements in customs, import/export
restrictions, dangerous goods handling.
• Information technology: Business process design has a major impact on the configuration of
IT. Additional criteria, beyond those for business processes, involve different requirements for
hardware, operating systems or databases, and incompatible interfaces.
Quantitative Criteria for Standardization
The costs and benefits of process standardization can be quantified, provided performance
metrics are in place. Assume that for a given process there are a number of existing variants.
Should a new process variant – the standard – substitute for the existing
ones?
The cost and benefit components for standardization are:
1. The performance difference between the existing process variants and the
new standard process variant: Process performance is quantified in terms of reaching
process objectives. Process objectives are derived from the objectives of the respective
process chain.
In some cases the individual process improves, while other processes in the same value
chain suffer. Therefore, the performance difference needs to be measured on the level of the
end-to end process.
2. Expenses for developing and rolling out the standard process variant across different
geographical areas and business units or warehouses.
3. Savings that arise from maintaining just one rather than several variants of the same
process.
The total of (1) + (2) + (3) represents the benefit from standardization.
Implementation
Process standardization and harmonization require full executive support.
Organization: Many companies have set up a central department to manage business
processes: Such a department should be able to manage standardization and harmonization
efforts.
The department will review the standardization and harmonization efforts in their respective
practices.
Projects: Rather than a big corporate project, it is often better to run small projects with a
clear focus on a specific set of processes.
Improvement.
Consider using a process model such SAP best practice, it dramatically saves time and
improves the quality of work.
Define templates: Rather than defining every single piece of a process, a template just
defines the essential part of a standard and leaves a well-defined degree of freedom for local
adaptation.
Where to start: Any process can be a starting point.
• IT-standardization focuses on saving IT-costs, not on process performance.
• Standardization of the transactions changes the design of business processes. Local
businesses need to adapt to the IT template, rather than have IT support the local operations.
Such changes trigger resistance in the business.
Conclusions and Recommendations
Standardization and harmonization can greatly improve process performance, lower the costs
for process maintenance, and give senior management more control over the operations.
The two processes may look similar, but if the performance requirements are different, they
need separate standards. This is often due to different types of supply chains, sales channels,
product development, or geographies.
Standardization and harmonization need senior management support. Management
establishes standardization criteria and ensures that the focus remains on the overall
performance improvement.
A competence center can help manage standardization and harmonization as a part of its
portfolio of process improvement projects IT standardization follows process standardization,
not vice-versa.

Weitere ähnliche Inhalte

Was ist angesagt?

Erp implementation as of january 2013
Erp implementation as of january 2013Erp implementation as of january 2013
Erp implementation as of january 2013Tannu Sharma
 
Primer on application_performance_testing_v0.2
Primer on application_performance_testing_v0.2Primer on application_performance_testing_v0.2
Primer on application_performance_testing_v0.2Trevor Warren
 
Primer on enterprise_performance_maturity_v0.2
Primer on enterprise_performance_maturity_v0.2Primer on enterprise_performance_maturity_v0.2
Primer on enterprise_performance_maturity_v0.2Trevor Warren
 
Erp Implementation Methodology Wkshp 2.0 120611
Erp Implementation Methodology Wkshp 2.0 120611Erp Implementation Methodology Wkshp 2.0 120611
Erp Implementation Methodology Wkshp 2.0 120611John Paulson
 
Enterprise system implementation strategies and phases
Enterprise system implementation strategies and phasesEnterprise system implementation strategies and phases
Enterprise system implementation strategies and phasesJohn Cachat
 
Kim Jimenez Resume
Kim Jimenez ResumeKim Jimenez Resume
Kim Jimenez ResumeKim Jimenez
 
Kim Jimenez Resume 2016
 Kim Jimenez Resume 2016 Kim Jimenez Resume 2016
Kim Jimenez Resume 2016Kim Jimenez
 
Working Procedure SAP BW Testing
Working Procedure SAP BW TestingWorking Procedure SAP BW Testing
Working Procedure SAP BW TestingGavaskar Selvarajan
 
Sachin 5 Yrs Telecom Ba Pmp Resume
Sachin 5 Yrs Telecom Ba Pmp ResumeSachin 5 Yrs Telecom Ba Pmp Resume
Sachin 5 Yrs Telecom Ba Pmp ResumeSachin P, PMP®
 
ERP Implementation A Complete Guide
ERP Implementation A Complete GuideERP Implementation A Complete Guide
ERP Implementation A Complete Guideguest42d52b7c
 
Project Management challenges in oracle EBS/ERP implementations
Project Management challenges in oracle EBS/ERP implementationsProject Management challenges in oracle EBS/ERP implementations
Project Management challenges in oracle EBS/ERP implementationsSIVAKUMAR_G
 
Laxmi_7yrs_Telecom_software_testing
Laxmi_7yrs_Telecom_software_testingLaxmi_7yrs_Telecom_software_testing
Laxmi_7yrs_Telecom_software_testingLaxmi Mangaligiker
 
Kenneth Luster resume 2016
Kenneth Luster resume 2016Kenneth Luster resume 2016
Kenneth Luster resume 2016Kenneth Luster
 
SHERYL_AVILA_PEREZ-CV
SHERYL_AVILA_PEREZ-CVSHERYL_AVILA_PEREZ-CV
SHERYL_AVILA_PEREZ-CVSheryl Perez
 
Enterprise Resource Planning(ERP)
Enterprise Resource Planning(ERP)Enterprise Resource Planning(ERP)
Enterprise Resource Planning(ERP)Tej Kiran
 
Priyanka_Sharma_6yr_UNIX_SQL_Prod_Support_Testing
Priyanka_Sharma_6yr_UNIX_SQL_Prod_Support_TestingPriyanka_Sharma_6yr_UNIX_SQL_Prod_Support_Testing
Priyanka_Sharma_6yr_UNIX_SQL_Prod_Support_Testingpriyanka sharma
 

Was ist angesagt? (20)

Joe Ballou
Joe BallouJoe Ballou
Joe Ballou
 
Erp implementation as of january 2013
Erp implementation as of january 2013Erp implementation as of january 2013
Erp implementation as of january 2013
 
Primer on application_performance_testing_v0.2
Primer on application_performance_testing_v0.2Primer on application_performance_testing_v0.2
Primer on application_performance_testing_v0.2
 
Primer on enterprise_performance_maturity_v0.2
Primer on enterprise_performance_maturity_v0.2Primer on enterprise_performance_maturity_v0.2
Primer on enterprise_performance_maturity_v0.2
 
Erp Implementation Methodology Wkshp 2.0 120611
Erp Implementation Methodology Wkshp 2.0 120611Erp Implementation Methodology Wkshp 2.0 120611
Erp Implementation Methodology Wkshp 2.0 120611
 
Enterprise system implementation strategies and phases
Enterprise system implementation strategies and phasesEnterprise system implementation strategies and phases
Enterprise system implementation strategies and phases
 
Kim Jimenez Resume
Kim Jimenez ResumeKim Jimenez Resume
Kim Jimenez Resume
 
Kim Jimenez Resume 2016
 Kim Jimenez Resume 2016 Kim Jimenez Resume 2016
Kim Jimenez Resume 2016
 
Working Procedure SAP BW Testing
Working Procedure SAP BW TestingWorking Procedure SAP BW Testing
Working Procedure SAP BW Testing
 
Sachin 5 Yrs Telecom Ba Pmp Resume
Sachin 5 Yrs Telecom Ba Pmp ResumeSachin 5 Yrs Telecom Ba Pmp Resume
Sachin 5 Yrs Telecom Ba Pmp Resume
 
ERP Implementation A Complete Guide
ERP Implementation A Complete GuideERP Implementation A Complete Guide
ERP Implementation A Complete Guide
 
madvel_QA
madvel_QAmadvel_QA
madvel_QA
 
Project Management challenges in oracle EBS/ERP implementations
Project Management challenges in oracle EBS/ERP implementationsProject Management challenges in oracle EBS/ERP implementations
Project Management challenges in oracle EBS/ERP implementations
 
Laxmi_7yrs_Telecom_software_testing
Laxmi_7yrs_Telecom_software_testingLaxmi_7yrs_Telecom_software_testing
Laxmi_7yrs_Telecom_software_testing
 
Collaborative Quality Management
Collaborative Quality ManagementCollaborative Quality Management
Collaborative Quality Management
 
Kenneth Luster resume 2016
Kenneth Luster resume 2016Kenneth Luster resume 2016
Kenneth Luster resume 2016
 
SHERYL_AVILA_PEREZ-CV
SHERYL_AVILA_PEREZ-CVSHERYL_AVILA_PEREZ-CV
SHERYL_AVILA_PEREZ-CV
 
Enterprise Resource Planning(ERP)
Enterprise Resource Planning(ERP)Enterprise Resource Planning(ERP)
Enterprise Resource Planning(ERP)
 
AMAR_Resume_latest
AMAR_Resume_latestAMAR_Resume_latest
AMAR_Resume_latest
 
Priyanka_Sharma_6yr_UNIX_SQL_Prod_Support_Testing
Priyanka_Sharma_6yr_UNIX_SQL_Prod_Support_TestingPriyanka_Sharma_6yr_UNIX_SQL_Prod_Support_Testing
Priyanka_Sharma_6yr_UNIX_SQL_Prod_Support_Testing
 

Ähnlich wie Standardizing Business Processes for Profitability

Doug Groves Shell S O A Symposium
Doug  Groves    Shell  S O A  SymposiumDoug  Groves    Shell  S O A  Symposium
Doug Groves Shell S O A SymposiumSOA Symposium
 
MIS Session 6
MIS Session 6MIS Session 6
MIS Session 6sant190
 
Cap gemini business process transformation to deliver world class outcomes
Cap gemini business process transformation to deliver world class outcomesCap gemini business process transformation to deliver world class outcomes
Cap gemini business process transformation to deliver world class outcomesLoren Moss
 
benchmarking-12517018313111-phpapp01.pdf
benchmarking-12517018313111-phpapp01.pdfbenchmarking-12517018313111-phpapp01.pdf
benchmarking-12517018313111-phpapp01.pdfbehaylu3
 
benchmarking-12517018313111-phpapp01.pdf
benchmarking-12517018313111-phpapp01.pdfbenchmarking-12517018313111-phpapp01.pdf
benchmarking-12517018313111-phpapp01.pdfbehaylu3
 
Pmac It Project Management 2010
Pmac It Project Management 2010Pmac It Project Management 2010
Pmac It Project Management 2010nseiersen
 
CRM Implementations and Upgrades
CRM Implementations and UpgradesCRM Implementations and Upgrades
CRM Implementations and UpgradesPeter Ware PMP
 
Capturing and documenting business processes and rules for agility
Capturing and documenting business processes and rules for agilityCapturing and documenting business processes and rules for agility
Capturing and documenting business processes and rules for agilityMichael Moyal - BPM Consultant
 
Fail to prepare - Softworld 2011
Fail to prepare -  Softworld 2011Fail to prepare -  Softworld 2011
Fail to prepare - Softworld 2011Sageukofficial
 
Fail to prepare, prepare to fail: implementing ERP and CRM systems
Fail to prepare, prepare to fail: implementing ERP and CRM systemsFail to prepare, prepare to fail: implementing ERP and CRM systems
Fail to prepare, prepare to fail: implementing ERP and CRM systemsSageukofficial
 
Fei It Alignement With With Business V2
Fei It Alignement With With Business V2Fei It Alignement With With Business V2
Fei It Alignement With With Business V2Dr.Adel Ghannam
 
Transforming Finance and Accounting to Optimize Financial Close
Transforming Finance and Accounting to Optimize Financial CloseTransforming Finance and Accounting to Optimize Financial Close
Transforming Finance and Accounting to Optimize Financial CloseCognizant
 
Business process re- engineering
Business process re- engineeringBusiness process re- engineering
Business process re- engineeringAshutosh Sharma
 

Ähnlich wie Standardizing Business Processes for Profitability (20)

Doug Groves Shell S O A Symposium
Doug  Groves    Shell  S O A  SymposiumDoug  Groves    Shell  S O A  Symposium
Doug Groves Shell S O A Symposium
 
Benchmarking
BenchmarkingBenchmarking
Benchmarking
 
Beanchmarketing
BeanchmarketingBeanchmarketing
Beanchmarketing
 
MIS Session 6
MIS Session 6MIS Session 6
MIS Session 6
 
Cap gemini business process transformation to deliver world class outcomes
Cap gemini business process transformation to deliver world class outcomesCap gemini business process transformation to deliver world class outcomes
Cap gemini business process transformation to deliver world class outcomes
 
benchmarking-12517018313111-phpapp01.pdf
benchmarking-12517018313111-phpapp01.pdfbenchmarking-12517018313111-phpapp01.pdf
benchmarking-12517018313111-phpapp01.pdf
 
benchmarking-12517018313111-phpapp01.pdf
benchmarking-12517018313111-phpapp01.pdfbenchmarking-12517018313111-phpapp01.pdf
benchmarking-12517018313111-phpapp01.pdf
 
Pmac It Project Management 2010
Pmac It Project Management 2010Pmac It Project Management 2010
Pmac It Project Management 2010
 
CRM Implementations and Upgrades
CRM Implementations and UpgradesCRM Implementations and Upgrades
CRM Implementations and Upgrades
 
Erp (Re) Implementation
Erp (Re) ImplementationErp (Re) Implementation
Erp (Re) Implementation
 
Unit v
Unit vUnit v
Unit v
 
Capturing and documenting business processes and rules for agility
Capturing and documenting business processes and rules for agilityCapturing and documenting business processes and rules for agility
Capturing and documenting business processes and rules for agility
 
Benchmarking
BenchmarkingBenchmarking
Benchmarking
 
Benchmarking
BenchmarkingBenchmarking
Benchmarking
 
Benchmarking final
Benchmarking finalBenchmarking final
Benchmarking final
 
Fail to prepare - Softworld 2011
Fail to prepare -  Softworld 2011Fail to prepare -  Softworld 2011
Fail to prepare - Softworld 2011
 
Fail to prepare, prepare to fail: implementing ERP and CRM systems
Fail to prepare, prepare to fail: implementing ERP and CRM systemsFail to prepare, prepare to fail: implementing ERP and CRM systems
Fail to prepare, prepare to fail: implementing ERP and CRM systems
 
Fei It Alignement With With Business V2
Fei It Alignement With With Business V2Fei It Alignement With With Business V2
Fei It Alignement With With Business V2
 
Transforming Finance and Accounting to Optimize Financial Close
Transforming Finance and Accounting to Optimize Financial CloseTransforming Finance and Accounting to Optimize Financial Close
Transforming Finance and Accounting to Optimize Financial Close
 
Business process re- engineering
Business process re- engineeringBusiness process re- engineering
Business process re- engineering
 

Standardizing Business Processes for Profitability

  • 1. SAPRODUCT IT UK LIMITED– MR. RONEN MADAR Introduction In the last few years I was involved with few large ERP – IT projects which were supposed to be driven by clear and well defined practices and methodologies , To my disappointment I found in most cases that the distance between the original business objectives and the achievements was not realistic and furthermore I was extremely unhappy with the fact that the people who are supposed to be the life guards of these processes do not understand the idea of what ERP project or Harmonization project is all about to a level that they created an extreme and unnecessary challenges to the organization they work for. As a results of the above mentioned reasons I have decided to publish this short document which I believe will set up a short guideline for whoever want to manage Harmonization activities properly. The document is displayed on my profile. ERP and BPM standards Standardization Harmonization means creating uniform business processes across various divisions or locations. The expected results are processes that consistently meet their cost and performance objectives using a well-defined practice. Standardization, thus, reduces the risk of failure. Through standardization, individual business units can share expenses, and will benefit from a company-wide business process management (BPM). Corporate-wide development of business processes lowers the total expenses, using economics of scale. Harmonization looking for the “prevention or elimination of differences in the technical content of standards has the same scope” .Harmonization looks at differences between process standard, and sets bounds to the degree of their variation. Example: There are various standards for the procurement process, such as ASN processing, STO processing and external direct inbound processing. In the context of Business Process Management, harmonization defines the extent of standards and how they fit together, but it does not attempt to make different standards uniform. Application of Standardization and Harmonization A company can establish standards across various divisions and geographies. The three levels of harmonization: • Strategic positioning, and Strategy • Business processes • Information technology: Configuration of ERP systems, etc. Standardizing Business Processes for Profitability Standardization of Business Processes intends to improve performance and to give management more control over operational performance. (The most popular measure for performance is the cost of executing the process. Although it is no less important, the quality of the results is less often considered.) Finally, the impact on other business processes and existing IT system needs to be considered, such as the ability to apply the standard performance measures
  • 2. • The process becomes more reliable. • Less expenses in development of new practices, and less expense in the administration of processes. • Process standardization is an important prerequisite for the standardization of IT systems. Standardization and Harmonization in a Practice Example Example, the consumer logistics company runs operations in more than 10 countries, selling goods through large retailers. In advanced countries, such as Canada, large retailers request to provide a service bid over the internet through Portal. On the other end is Peru, where open office face to face communications are common and where the service provider walks in to provide service bid. For this company, there have been 40 different sales and transportation processes in the 10 different countries with significant differences in performance. Strict standardization attempts to make the transportation process in all countries the same. One of the two countries will lose as the standard becomes a perfectly suitable approach for the other country: If Canada’s Portal approach is selected as standard; Peru cannot serve its face to face providers. The harmonization approach analyzes requirements from all countries and creates 2 standard sales and transportation processes: • Portal Bid • Through fax, letter, or via telephone • Open office With the harmonization approach, there are only three (rather than forty) standards for the sales process. In contrast to a single, strict standardization, every country sees its requirements attended through a standard specific to their needs It is also possible that some countries might implement two or even all three sales order processes in parallel to attend to different groups of customers. Criteria for Standardization • Decisions about standardization are process-specific. In the example above, the company needed just two standard processes. • A precondition for any process standardization is that the requirements for processes are sufficiently similar. Qualitative Criteria for Standardization 1. Clear decision rules for standardization and harmonization- Business Objectives 2. Criteria when process variants should not be standardized – Legal requirements 3. Criteria for selecting the best standard. These should be based on process performance and process cost- SAP best practice, Supply chain council. • Business processes: Consider all processes of the extended value chain. Processes that belong to different types of logistics, sales channels, or product development are hard to standardize: o Type of logistics: Make-to-Order, Make-to-Stock, Inbound, outbound, staging to production o Technological readiness of the relevant parties in the extended value chain. In the example above, Providers were not yet ready for the Portal exchange. o Geography and compliance: Country-specific requirements in customs, import/export restrictions, dangerous goods handling. • Information technology: Business process design has a major impact on the configuration of IT. Additional criteria, beyond those for business processes, involve different requirements for
  • 3. hardware, operating systems or databases, and incompatible interfaces. Quantitative Criteria for Standardization The costs and benefits of process standardization can be quantified, provided performance metrics are in place. Assume that for a given process there are a number of existing variants. Should a new process variant – the standard – substitute for the existing ones? The cost and benefit components for standardization are: 1. The performance difference between the existing process variants and the new standard process variant: Process performance is quantified in terms of reaching process objectives. Process objectives are derived from the objectives of the respective process chain. In some cases the individual process improves, while other processes in the same value chain suffer. Therefore, the performance difference needs to be measured on the level of the end-to end process. 2. Expenses for developing and rolling out the standard process variant across different geographical areas and business units or warehouses. 3. Savings that arise from maintaining just one rather than several variants of the same process. The total of (1) + (2) + (3) represents the benefit from standardization. Implementation Process standardization and harmonization require full executive support. Organization: Many companies have set up a central department to manage business processes: Such a department should be able to manage standardization and harmonization efforts. The department will review the standardization and harmonization efforts in their respective practices. Projects: Rather than a big corporate project, it is often better to run small projects with a clear focus on a specific set of processes. Improvement. Consider using a process model such SAP best practice, it dramatically saves time and improves the quality of work. Define templates: Rather than defining every single piece of a process, a template just defines the essential part of a standard and leaves a well-defined degree of freedom for local adaptation. Where to start: Any process can be a starting point. • IT-standardization focuses on saving IT-costs, not on process performance. • Standardization of the transactions changes the design of business processes. Local businesses need to adapt to the IT template, rather than have IT support the local operations. Such changes trigger resistance in the business. Conclusions and Recommendations Standardization and harmonization can greatly improve process performance, lower the costs for process maintenance, and give senior management more control over the operations. The two processes may look similar, but if the performance requirements are different, they need separate standards. This is often due to different types of supply chains, sales channels, product development, or geographies. Standardization and harmonization need senior management support. Management
  • 4. establishes standardization criteria and ensures that the focus remains on the overall performance improvement. A competence center can help manage standardization and harmonization as a part of its portfolio of process improvement projects IT standardization follows process standardization, not vice-versa.