Value Delivery Modelling Language

Last updated

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. [1] [2]

In 2009, the 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:

Object Management Group technology standards consortium

The Object Management Group (OMG) is a computer industry standards consortium. OMG Task Forces develop enterprise integration standards for a range of technologies.

  1. The metamodel must satisfy the characteristics of the 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.
  2. The metamodel must support the analysis of the activities of the value chain to support the identification of differentiators. The internal value chain should as such be part of the metamodel.
  3. 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.
  4. 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 BPMN.
  5. The value model should be able to aggregate activities at multiple levels to analyse them from different angles (e.g. strategic vs operational).
  6. It should be possible to couple performance- and cost aspects to the activities
  7. The relationships with other organisations such as competitors and strategic alliances should be included.
  8. The events that trigger an activity should be included in the metamodel
  9. The user should be able to include its own specifications.

The VDML standard integrates 7 existing value models:

A value chain is a set of activities that a firm operating in a specific industry performs in order to deliver a valuable product for the market. The concept comes through business management and was first described by Michael Porter in his 1985 best-seller, Competitive Advantage: Creating and Sustaining Superior Performance.

The idea of the value chain is based on the process view of organizations, the idea of seeing a manufacturing organization as a system, made up of subsystems each with inputs, transformation processes and outputs. Inputs, transformation processes, and outputs involve the acquisition and consumption of resources – money, labour, materials, equipment, buildings, land, administration and management. How value chain activities are carried out determines costs and affects profits.

Business Model Canvas

Business Model Canvas is a strategic management and lean startup template for developing new or documenting existing business models. It is a visual chart with elements describing a firm's or product's value proposition, infrastructure, customers, and finances. It assists firms in aligning their activities by illustrating potential trade-offs.

Value network analysis (VNA) is a methodology for understanding, using, visualizing, optimizing internal and external value networks and complex economic ecosystems. The methods include visualizing sets of relationships from a dynamic whole systems perspective. Robust network analysis approaches are used for understanding value conversion of financial and non-financial assets, such as intellectual capital, into other forms of value.

The use of VDML diagrams to support business model innovation is discussed in [3]

VDML has been applied to a use case in manufacturing. [4] It demonstrates the use of VDML for modeling and analysis of a proposed change to an as-is business system.

Related Research Articles

Unified Modeling Language general-purpose, developmental, modeling language in the field of software engineering

The Unified Modeling Language (UML) is a general-purpose, developmental, modeling language in the field of software engineering that is intended to provide a standard way to visualize the design of a system.

The XML Metadata Interchange (XMI) is an Object Management Group (OMG) standard for exchanging metadata information via Extensible Markup Language (XML).

Meta-Object Facility

The Meta-Object Facility (MOF) is an Object Management Group (OMG) standard for model-driven engineering. Its purpose is to provide a type system for entities in the CORBA architecture and a set of interfaces through which those types can be created and manipulated. The official reference page may be found at OMG's website.

Model-driven architecture (MDA) is a software design approach for the development of software systems. It provides a set of guidelines for the structuring of specifications, which are expressed as models. Model-driven architecture is a kind of domain engineering, and supports model-driven engineering of software systems. It was launched by the Object Management Group (OMG) in 2001.

In product development and process optimization, a requirement is a singular documented physical or functional need that a particular design, product or process aims to satisfy. It is commonly used in a formal sense in engineering design, including for example in systems engineering, software engineering, or enterprise engineering. It is a broad concept that could speak to any necessary function, attribute, capability, characteristic, or quality of a system for it to have value and utility to a customer, organization, internal user, or other stakeholder. Requirements can come with different levels of specificity; for example, a requirement specification or requirement "spec" refers to an explicit, highly objective/clear requirement to be satisfied by a material, design, product, or service.

Metamodeling

A metamodel or surrogate model is a model of a model, and metamodeling is the process of generating such metamodels. Thus metamodeling or meta-modeling is the analysis, construction and development of the frames, rules, constraints, models and theories applicable and useful for modeling a predefined class of problems. As its name implies, this concept applies the notions of meta- and modeling in software engineering and systems engineering. Metamodels are of many types and have diverse applications.

Extended Enterprise Modeling Language

Extended Enterprise Modeling Language (EEML) in software engineering is a modelling language used for Enterprise modelling across a number of layers.

The British Ministry of Defence Architecture Framework (MODAF) is an architecture framework which defines a standardised way of conducting enterprise architecture, originally developed by the UK Ministry of Defence.

ATLAS Transformation Language programming language

ATL is a model transformation language and toolkit developed and maintained by OBEO and AtlanMod. It was initiated by the AtlanMod team. In the field of Model-Driven Engineering (MDE), ATL provides ways to produce a set of target models from a set of source models.

QVT

QVT (Query/View/Transformation) is a standard set of languages for model transformation defined by the Object Management Group.

The UML profile for Enterprise Distributed Object Computing (EDOC) is a standard of the Object Management Group in support of open distributed computing using model-driven architecture and service-oriented architecture. Its aim is to simplify the development of component based (EDOC) systems by providing a UML-based modeling framework conforming to the MDA of the OMG.

Business architecture

In the business sector, business architecture is a discipline that "represents holistic, multidimensional business views of: capabilities, end‐to‐end value delivery, information, and organizational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders.

Visual Paradigm software

Visual Paradigm (VP-UML) is a UML CASE Tool supporting UML 2, SysML and Business Process Modeling Notation (BPMN) from the Object Management Group (OMG). In addition to modeling support, it provides report generation and code engineering capabilities including code generation. It can reverse engineer diagrams from code, and provide round-trip engineering for various programming languages.

Knowledge Discovery Metamodel (KDM) is a publicly available specification from the Object Management Group (OMG). KDM is a common intermediate representation for existing software systems and their operating environments, that defines common metadata required for deep semantic integration of Application Lifecycle Management tools. KDM was designed as the OMG's foundation for software modernization, IT portfolio management and software assurance. KDM uses OMG's Meta-Object Facility to define an XMI interchange format between tools that work with existing software as well as an abstract interface (API) for the next-generation assurance and modernization tools. KDM standardizes existing approaches to knowledge discovery in software engineering artifacts, also known as software mining.

Capability management is a high-level integrative management function, with particular application in the context of defense.

The Semantics of Business Vocabulary and Business Rules (SBVR) is an adopted standard of the Object Management Group (OMG) intended to be the basis for formal and detailed natural language declarative description of a complex entity, such as a business. SBVR is intended to formalize complex compliance rules, such as operational rules for an enterprise, security policy, standard compliance, or regulatory compliance rules. Such formal vocabularies and rules can be interpreted and used by computer systems. SBVR is an integral part of the OMG's model-driven architecture (MDA).

ArchiMate

ArchiMate is an open and independent enterprise architecture modeling language to support the description, analysis and visualization of architecture within and across business domains in an unambiguous way.

Capability management is the approach to the management of an organization, typically a business organization or firm, based on the "theory of the firm" as a collection of capabilities that may be exercised to earn revenues in the marketplace and compete with other firms in the industry. "Capability Management" seeks to manage the stock of capabilities within the firm to ensure its position in the industry and its ongoing profitability and survival.

The OMG Structured Metrics Metamodel (SMM) specification defines a standard Metrics Metamodel. It is a publicly available specification from the Object Management Group (OMG). SMM specifies a metamodel for defining, representing and exchanging both measures and measurement information related to any structured information model, such as the OMG Meta Object Facility (MOF™) standard, defining an XMI interchange format between metric extraction tools. It is used to maintain metrics by a number of other OMG specifications such as the Knowledge Discovery Metamodel and the Value Delivery Metamodel.

Target operating model is a description of the desired state of the operating model of an organisation. When working on the operating model, it is normal to define the "as is" model and the "to be" model. The Target Operating Model is the "to be" model. It is possible to produce a Target Operating Model for a business or a function within a business or a government department or a charity.

References

  1. "Value Delivery Modeling Language (VDML)". Object Management Group. Retrieved 26 August 2015.
  2. Cummins, Fred A. "Value Delivery Modeling Language (VDML): An Update". Building the Agile Enterprise. Retrieved 28 August 2015.
  3. Berre, Arne J.; de Man, Henk; Lindgren, Peter. "Business Model Innovation with the NEFFICS platform and VDML" (PDF). Retrieved 28 August 2015.
  4. de Man, Henk; Berre, Arne J. "VDML Manufacturing Use Case" (PDF). NEFFICS. Archived from the original (PDF) on 8 March 2016. Retrieved 28 August 2015.