Content deleted Content added
m fixed misspelling |
Gabisofiaaa (talk | contribs) No edit summary |
||
Line 6:
}}
[[File:BPMN-AProcessWithNormalFlow.svg|alt=|thumb|400x400px|Example of business process modeling of a process with a normal flow with the [[Business Process Model and Notation]]]]
'''Business process modeling''' ('''BPM'''), mainly used in [[business process management]]; [[software development]] or [[systems engineering]], is the action of capturing and representing [[business processes|processes]] of an enterprise (i.e. [[modeling]] them), so that the current business processes may be analyzed, applied securely and consistently, improved, and automated. BPM is typically
== Overview ==
Line 197:
Consequently, business process modeling for TCT must support adequate documentation of barriers, barrier handling and measurement.
Six Sigma is designed to prevent errors and improve the [[Process capability index|process capability]] so that the proportion of process outcomes that meet the requirements is 6σ - or in other words, for every million process outcomes, only 3.4 errors occur. Hermann J. Schmelzer and Wolfgang Sesselmann explain: «Companies often encounter considerable resistance at a level of 4σ, which makes it necessary to redesign business processes in the sense of business process re-engineering (design for Six Sigma).»<ref name="SCHMELZER" /> <sup>(Chapter 6.3.4 Six Sigma) ← automatic translation from German</sup> For a reproducible measurement of process capability, precise knowledge of the business processes is required and business process modeling is a suitable tool for design for Six Sigma. Six Sigma therefore uses business process modeling according to [[SIPOC]] as an essential part of the methodology and business process modeling using SIPOC has established itself as a standard tool for Six Sigma.
Line 205:
''Martin Kugler'' lists the following requirements for business process modeling in this context:<ref name="KUGLER">Martin Kugler: ''Supply Chain Management und Customer Relationship Management - Prozessmodellierung für Extended Enterprises'' in Jörg Becker, Martin Kugler and Michael Rosemamm (publisher): ''Prozessmanagement: Ein Leitfaden zur prozessorientierten Organisationsgestaltung'', 2. corrected and expanded edition, Springer, Berlin/Heidelberg/New York 2002, ISBN 3-540-00107-7</ref> <sup>(Chapter 14.2.1 Requirements for inter-company business process modeling) ← automatic translation from German</sup>
* Employees from different companies must comprehend business process models, highlighting the critical importance of familiarity with modeling techniques. Acceptance of business process modeling is bolstered by the simplicity of representation. Models should be clear, easy to understand, and as self-explanatory as possible. Standardization of the presentation of inter-company business process models across different companies is essential to ensure consistent comprehensibility and acceptance, particularly given the varied representations used within different organizations. It is imperative to employ an industry-neutral modeling technique to accommodate the diverse backgrounds of companies along the value chain (supplier, manufacturer, retailer, customer), which typically span different industries.
== Topics ==
Line 221 ⟶ 218:
==== Identify business processes ====
The effort involved in analysing the as-is processes is repeatedly criticised in the literature, especially by proponents of business process re-engineering (BPR), and it is suggested that the definition of the target state should begin immediately.
Line 283 ⟶ 280:
The definition of a business process includes: What result should be achieved on completion? What activities are necessary to achieve this? Which objects should be processed (orders, raw materials, purchases, products, ...)? Define start and end point. Definition of operational goals.
Depending on the prevailing corporate culture, which may either be more inclined towards embracing change or protective of the status quo, and the effectiveness of communication, defining business processes can prove to be either straightforward or challenging. This hinges on the willingness of key stakeholders within the organization, such as department heads, to lend their support to the endeavor. Within this context, effective communication plays a pivotal role.
In elucidating this point, Jörg Becker and Volker Meise elucidate that the communication strategy within an organizational design initiative should aim to garner support from members of the organization for the intended structural changes. It is worth noting that business process modeling typically precedes business process optimization, which entails a reconfiguration of process organization - a fact well understood by the involved parties. Therefore, the communication strategy must focus on persuading organizational members to endorse the planned structural adjustments.»<ref name="BECKER-MEISE" /> <sup>(Chapter 4.15 Influencing the design of the regulatory framework) ← automatic translation from German</sup> In the event of considerable resistance, however, external knowledge can also be used to define the business processes.
[[File:VAC PLM with SCRUM.png|thumb|Value chain diagram with exemplary representation of "product life cycle management" with SCRUM]]
|