Value Delivery Modelling Language: Difference between revisions

Revision as of 14:53, 26 August 2015

Latest revision as of 02:28, 11 November 2022

(19 intermediate revisions by 15 users not shown)

Line 1:

'''Value Delivery Modeling Language''' ('''VDML''') is a standard modeling language for analysis and design of the operation of an enterprise with particular focus on the creation and exchange of value .<ref>{{cite web|title=Value Delivery Modeling Language (VDML)|url=http://www.omg.org/spec/VDML/|website=Object Management Group|accessdate=26 August 2015|ref=OMG_spec}}</ref><ref>{{cite web|last1=Cummins|first1=Fred A.|title=Value Delivery Modeling Language (VDML): An Update|url=http://fredacummins.blogspot.be/2013/02/value-delivery-modeling-language-vdml_4878.html|website=Building the Agile Enterprise|accessdate=28 August 2015}}</ref>

{{AFC submission|t||ts=20150826145256|u=Bramnaudts|ns=118}} <!--- Important, do not remove this line before article has been created. --->

In 2009, the [[Object_Management_Group|Object Management Group]] (OMG) launched a Request for Proposal (RfP) to develop a standard for value modeling. The goal of this RfP is to integrate the different existing value models and give a complete overview of the business logic of an organisation. To reach this goal, the standard has to satisfy nine requirements:

# The [[Metamodeling|metamodel]] must satisfy the characteristics of the [[Meta-Object_Facility|Meta-Object Facility]] (MOF) metamodel. MOF is a standard developed for model-driven engineering and is structured in 4 layers. The top layer (M3 model) consists of a language that is used to construct metamodels. These metamodels are the second layer (M2 model) and they describe the third layer (M1 laer). The last layer, the data layer is used to describe real objects.

Value Delivery Modeling Language (VDML) is a standard modeling language for analysis and design of the operation of an enterprise with particular focus on the creation and exchange of value <ref>{{cite web|title=Value Delivery Modeling Language (VDML)|url=http://www.omg.org/spec/VDML/|website=Object Management Group|accessdate=26 August 2015|ref=OMG_spec}}</ref>.

# The metamodel must support the analyisanalysis of the activities of the [[Value_chain|value chain]] to support the identification of differentiators. The internal value chain should as such be part of the metamodel.

In 2009, the [[Object_Management_Group|Object Management Group]] (OMG) launched a Request for Proposal (RfP) to develop a standard for value modeling. The goal of this RfP is to integrate the different existing value models and give a complete overview of the business logic of an organisation. To reach this goal, the standard has to satisfy nine requirements:

# The [[Metamodeling|metamodel]] must satisfy the characteristics of the [[Meta-Object_Facility|Meta-Object Facility]] (MOF) metamodel. MOF is a standard developed for model-driven engineering and is structured in 4 layers. The top layer (M3 model) consists of a language that is used to construct metamodels. These metamodels are the second layer (M2 model) and they describe the third layer (M1 laer). The last layer, the data layer is used to describe real objects.

# The metamodel must support the analyis of the activities of the [[Value_chain|value chain]] to support the identification of differentiators. The internal value chain should as such be part of the metamodel.

# A capability analysis must be possible. This is closely linked to the second requirement. A capability is the possibility to execute some sort of activity. The quality of an activity is as such dependent on the capabilities of the organisation. As such the metamodel should include a way to analyse these capabilities.

# The value model should have an adequate level of detail to include both activities and capabilities on the operational level. However a value model focuses on the inputs and outputs unlike a process model such as [[Business_Process_Model_and_NotationBusiness Process Model and Notation|BPMN]].

# The value model should be able to aggregate activities at multiple levels to analyse them from different angles (e.g. strategic vs operational).

# It should be possible to couple performance- and cost aspects to the activities

Line 16 ⟶ 13:

The VDML standard integrates 7 existing value models:

* [[Value_chainValue chain|Porter's Value Chain]]

* [[Business_Model_CanvasBusiness Model Canvas|Business Model Ontology]] of Osterwalder

* [[Value_network_analysisValue network analysis|Verna Allee's Value Network Analysis]]

* E3-Value analysis

* [[Resources, events, agents (accounting model)|Resources, Events, Agents (REA)]] analysis

* Resource-Event-Agent(REA) analysis

* [[Value_stream_mappingValue stream mapping|Value Stream Mapping]]

* [[Service-oriented_architectureoriented architecture|Service-Oriented Business Architecture analysis]]

The use of VDML diagrams to support business model innovation is discussed in<ref>{{cite web|last1=Berre|first1=Arne J.|last2=de Man|first2=Henk|last3=Lindgren|first3=Peter|title=Business Model Innovation with the NEFFICS platform and VDML|url=http://ceur-ws.org/Vol-1006/paper5.pdf|accessdate=28 August 2015}}</ref>

VDML has been applied to a use case in manufacturing.<ref>{{cite web|last1=de Man|first1=Henk|last2=Berre|first2=Arne J.|title=VDML Manufacturing Use Case|url=http://files.modelbased.net/vdml/12-11-10.pdf|archive-url=https://web.archive.org/web/20160308201944/http://files.modelbased.net/vdml/12-11-10.pdf|url-status=dead|archive-date=8 March 2016|publisher=NEFFICS|accessdate=28 August 2015}}</ref> It demonstrates the use of VDML for modeling and analysis of a proposed change to an

as-is business system.

==References==

{{reflist}}

<!--- After listing your sources please cite them using inline citations and place them after the information they cite. Please see http://en.wikipedia.org/wiki/Wikipedia:REFB for instructions on how to add citations. --->

*

*

*

*

[[Category:Business analysis]]

{{AFC submission|||ts=20150826145323|u=Bramnaudts|ns=118}}