<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://www.enterprisearchitecture.management/index.php?action=history&amp;feed=atom&amp;title=Trends%3AProcess_Variance_Modelling</id>
		<title>Trends:Process Variance Modelling - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://www.enterprisearchitecture.management/index.php?action=history&amp;feed=atom&amp;title=Trends%3AProcess_Variance_Modelling"/>
		<link rel="alternate" type="text/html" href="https://www.enterprisearchitecture.management/index.php?title=Trends:Process_Variance_Modelling&amp;action=history"/>
		<updated>2026-07-05T04:24:49Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.24.2</generator>

	<entry>
		<id>https://www.enterprisearchitecture.management/index.php?title=Trends:Process_Variance_Modelling&amp;diff=5215&amp;oldid=prev</id>
		<title>Admin at 14:23, 10 January 2017</title>
		<link rel="alternate" type="text/html" href="https://www.enterprisearchitecture.management/index.php?title=Trends:Process_Variance_Modelling&amp;diff=5215&amp;oldid=prev"/>
				<updated>2017-01-10T14:23:55Z</updated>
		
		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;table class='diff diff-contentalign-left'&gt;
				&lt;col class='diff-marker' /&gt;
				&lt;col class='diff-content' /&gt;
				&lt;col class='diff-marker' /&gt;
				&lt;col class='diff-content' /&gt;
				&lt;tr style='vertical-align: top;'&gt;
				&lt;td colspan='2' style=&quot;background-color: white; color:black; text-align: center;&quot;&gt;← Older revision&lt;/td&gt;
				&lt;td colspan='2' style=&quot;background-color: white; color:black; text-align: center;&quot;&gt;Revision as of 14:23, 10 January 2017&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot;&gt;Line 1:&lt;/td&gt;
&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot;&gt;Line 1:&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class='diff-marker'&gt;&amp;#160;&lt;/td&gt;&lt;td style=&quot;background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;{{DISPLAYTITLE: Process Variance Modelling}}&lt;/div&gt;&lt;/td&gt;&lt;td class='diff-marker'&gt;&amp;#160;&lt;/td&gt;&lt;td style=&quot;background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;{{DISPLAYTITLE: Process Variance Modelling}}&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class='diff-marker'&gt;&amp;#160;&lt;/td&gt;&lt;td style=&quot;background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;== The Process Variance Modelling Trend ==&lt;/div&gt;&lt;/td&gt;&lt;td class='diff-marker'&gt;&amp;#160;&lt;/td&gt;&lt;td style=&quot;background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;== The Process Variance Modelling Trend ==&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class='diff-marker'&gt;−&lt;/td&gt;&lt;td style=&quot;color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;Business process variance should be seen as a viable way of allowing small differences in the way the core business functions are performed. It is advisable to only introduce variation in those business processes that represent the core-differentiating competencies of the organisation. This will allow an enterprise to develop its own practice and deliver unique value to clients and other stakeholders. For non-core and core-competitive competencies, best practice and industry best practice should suffice&lt;del class=&quot;diffchange diffchange-inline&quot;&gt;. Business process variance can be modelled three different ways, depending on what is expected thereof. If the aim is only to capture slight differences in the inputs, outputs, controls and mechanisms of processes, it will be adequate to only create variances at the process activity or task levels. However, if the actual steps of the variant processes are different, true process variances can be used by presenting all the variances together in a single model or document or separate distinct process may even be developed&lt;/del&gt;. &amp;#160;&lt;/div&gt;&lt;/td&gt;&lt;td class='diff-marker'&gt;+&lt;/td&gt;&lt;td style=&quot;color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;Business process variance should be seen as a viable way of allowing small differences in the way the core business functions are performed. It is advisable to only introduce variation in those business processes that represent the core-differentiating competencies of the organisation. This will allow an enterprise to develop its own practice and deliver unique value to clients and other stakeholders. For non-core and core-competitive competencies, best practice and industry best practice should suffice.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class='diff-marker'&gt;&amp;#160;&lt;/td&gt;&lt;td style=&quot;background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;/td&gt;&lt;td class='diff-marker'&gt;&amp;#160;&lt;/td&gt;&lt;td style=&quot;background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class='diff-marker'&gt;−&lt;/td&gt;&lt;td style=&quot;color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;The modelling approach taken has a major impact on the management of the business processes and variances. When certain commonality between the master process and its variants is important, additional business process management techniques are necessary to maintain this traceability. This will require that a great deal of attention is given to establishing and maintaining the traceability links between the variants. Separate and distinctive processes introduce more process content, but standard business process management is applied because traceability to the master process is unnecessary. When introducing process variance, caution should be taken and the amount of variation should be minimised. If the development and modelling is not sufficiently controlled, the amount of additional and unnecessary content will very quickly become unmanageable. However, if it is done well, it is an excellent way for organisations to acknowledge and embrace its unique value enablers, without losing out on the many benefits of business process modelling and management.&lt;/div&gt;&lt;/td&gt;&lt;td class='diff-marker'&gt;+&lt;/td&gt;&lt;td style=&quot;color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&lt;ins class=&quot;diffchange diffchange-inline&quot;&gt;Business process variance can be modelled three different ways, depending on what is expected thereof. If the aim is only to capture slight differences in the inputs, outputs, controls and mechanisms of processes, it will be adequate to only create variances at the process activity or task levels. However, if the actual steps of the variant processes are different, true process variances can be used by presenting all the variances together in a single model or document or a separate distinct process may even be developed.&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot;&gt;&amp;#160;&lt;/td&gt;&lt;td class='diff-marker'&gt;+&lt;/td&gt;&lt;td style=&quot;color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&amp;#160;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot;&gt;&amp;#160;&lt;/td&gt;&lt;td class='diff-marker'&gt;+&lt;/td&gt;&lt;td style=&quot;color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;The modelling approach taken has a major impact on the management of the business processes and variances. When certain commonality between the master process and its variants is important, additional business process management techniques are necessary to maintain this traceability. This will require that a great deal of attention is given to establishing and maintaining the traceability links between the variants. Separate and distinctive processes introduce more process content, but standard business process management is applied because traceability to the master process is unnecessary.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot;&gt;&amp;#160;&lt;/td&gt;&lt;td class='diff-marker'&gt;+&lt;/td&gt;&lt;td style=&quot;color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&amp;#160;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot;&gt;&amp;#160;&lt;/td&gt;&lt;td class='diff-marker'&gt;+&lt;/td&gt;&lt;td style=&quot;color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;When introducing process variance, caution should be taken and the amount of variation should be minimised. If the development and modelling is not sufficiently controlled, the amount of additional and unnecessary content will very quickly become unmanageable.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot;&gt;&amp;#160;&lt;/td&gt;&lt;td class='diff-marker'&gt;+&lt;/td&gt;&lt;td style=&quot;color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&amp;#160;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot;&gt;&amp;#160;&lt;/td&gt;&lt;td class='diff-marker'&gt;+&lt;/td&gt;&lt;td style=&quot;color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;However, if it is done well, it is an excellent way for organisations to acknowledge and embrace its unique value enablers, without losing out on the many benefits of business process modelling and management.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class='diff-marker'&gt;&amp;#160;&lt;/td&gt;&lt;td style=&quot;background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;/td&gt;&lt;td class='diff-marker'&gt;&amp;#160;&lt;/td&gt;&lt;td style=&quot;background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class='diff-marker'&gt;&amp;#160;&lt;/td&gt;&lt;td style=&quot;background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;[[Category: Solution Trends]]&lt;/div&gt;&lt;/td&gt;&lt;td class='diff-marker'&gt;&amp;#160;&lt;/td&gt;&lt;td style=&quot;background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;[[Category: Solution Trends]]&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/table&gt;</summary>
		<author><name>Admin</name></author>	</entry>

	<entry>
		<id>https://www.enterprisearchitecture.management/index.php?title=Trends:Process_Variance_Modelling&amp;diff=5213&amp;oldid=prev</id>
		<title>Admin: Created page with &quot;{{DISPLAYTITLE: Process Variance Modelling}} == The Process Variance Modelling Trend == Business process variance should be seen as a viable way of allowing small differences...&quot;</title>
		<link rel="alternate" type="text/html" href="https://www.enterprisearchitecture.management/index.php?title=Trends:Process_Variance_Modelling&amp;diff=5213&amp;oldid=prev"/>
				<updated>2017-01-10T14:20:05Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;{{DISPLAYTITLE: Process Variance Modelling}} == The Process Variance Modelling Trend == Business process variance should be seen as a viable way of allowing small differences...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{DISPLAYTITLE: Process Variance Modelling}}&lt;br /&gt;
== The Process Variance Modelling Trend ==&lt;br /&gt;
Business process variance should be seen as a viable way of allowing small differences in the way the core business functions are performed. It is advisable to only introduce variation in those business processes that represent the core-differentiating competencies of the organisation. This will allow an enterprise to develop its own practice and deliver unique value to clients and other stakeholders. For non-core and core-competitive competencies, best practice and industry best practice should suffice. Business process variance can be modelled three different ways, depending on what is expected thereof. If the aim is only to capture slight differences in the inputs, outputs, controls and mechanisms of processes, it will be adequate to only create variances at the process activity or task levels. However, if the actual steps of the variant processes are different, true process variances can be used by presenting all the variances together in a single model or document or separate distinct process may even be developed. &lt;br /&gt;
&lt;br /&gt;
The modelling approach taken has a major impact on the management of the business processes and variances. When certain commonality between the master process and its variants is important, additional business process management techniques are necessary to maintain this traceability. This will require that a great deal of attention is given to establishing and maintaining the traceability links between the variants. Separate and distinctive processes introduce more process content, but standard business process management is applied because traceability to the master process is unnecessary. When introducing process variance, caution should be taken and the amount of variation should be minimised. If the development and modelling is not sufficiently controlled, the amount of additional and unnecessary content will very quickly become unmanageable. However, if it is done well, it is an excellent way for organisations to acknowledge and embrace its unique value enablers, without losing out on the many benefits of business process modelling and management.&lt;br /&gt;
&lt;br /&gt;
[[Category: Solution Trends]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>	</entry>

	</feed>