<?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%3AInformation_%26_Process_Modelling</id>
		<title>Trends:Information &amp; Process 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%3AInformation_%26_Process_Modelling"/>
		<link rel="alternate" type="text/html" href="https://www.enterprisearchitecture.management/index.php?title=Trends:Information_%26_Process_Modelling&amp;action=history"/>
		<updated>2026-07-06T17:23:33Z</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:Information_%26_Process_Modelling&amp;diff=5219&amp;oldid=prev</id>
		<title>Admin: Created page with &quot;{{DISPLAYTITLE: Information &amp; Process Modelling}} == The Information &amp; Process Modelling (IPM) Trend == Information &amp; Process Modelling is also called the anti-pattern informa...&quot;</title>
		<link rel="alternate" type="text/html" href="https://www.enterprisearchitecture.management/index.php?title=Trends:Information_%26_Process_Modelling&amp;diff=5219&amp;oldid=prev"/>
				<updated>2017-01-10T14:38:53Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;{{DISPLAYTITLE: Information &amp;amp; Process Modelling}} == The Information &amp;amp; Process Modelling (IPM) Trend == Information &amp;amp; Process Modelling is also called the anti-pattern informa...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{DISPLAYTITLE: Information &amp;amp; Process Modelling}}&lt;br /&gt;
== The Information &amp;amp; Process Modelling (IPM) Trend ==&lt;br /&gt;
Information &amp;amp; Process Modelling is also called the anti-pattern information modelling. The need to support information models with a more flexible process execution by avoiding well known restrictions present in conventional BPM and workflow technology.&lt;br /&gt;
&lt;br /&gt;
The trend around information modelling in the market is about the challenge around process and information modelling and how one can produce adequate ‘as-is’ and ‘to-be’ process models that incorporate information models. The anti-pattern information modelling is often incorrectly understood to be only concerned with data modelling. The answer to this misunderstanding is not an easy one, and is one of the biggest challenges around the mistake that most BPM and BPMN concepts do not consider the process in its full context.&lt;br /&gt;
&lt;br /&gt;
A process always has a context. Not considering its context to the purpose and goal perspective of the business is devastating. It keeps away the context that so many are looking for - the value perspective. Not considering the context to the business competencies can have the effect that nobody knows which processes are a part of the core differentiating competencies, and which ones support the core competitive competencies of the organization.&lt;br /&gt;
&lt;br /&gt;
It doesn’t matter how much we analyse the process in itself, because it cannot reveal this information. The same is true for services. While we all know that activities (i.e. processes) are needed to create services, most organizations don’t know which process creates which kind of service. Therefore, their processes models are not considering the most vital aspects of the various value offerings to the consumers of the processes (e.g. employees and/or customers).&lt;br /&gt;
&lt;br /&gt;
Modelling the processes without considering its relevant context results in process models the executives and many others from the business or even architecture teams can’t use. Too sadly, we see to many BPM programs/ projects within organizations that limit their as-is’ and ‘to-be’ process models’ in this way. In order to structure the x-BPMN process groups, we categorize the relevant process context into Layers.&lt;br /&gt;
&lt;br /&gt;
[[Category: Solution Trends]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>	</entry>

	</feed>