Smart City EnterprisePLUS [E+] - User contributions [en]

Business Process

2021-07-29T06:29:18Z

Admin: Created page with "{{#lead-mw-content: MetaObjectDescriptions|getPageContent|{{FULLPAGENAME}} }} === Best Practice Reference Content === *Enterprise_Standards:Strategy_Management_Reference_Co..."

{{#lead-mw-content: MetaObjectDescriptions|getPageContent|{{FULLPAGENAME}} }}

=== Best Practice Reference Content ===
*[[Enterprise_Standards:Strategy_Management_Reference_Content|Strategy Management Reference Content]]
*[[Enterprise_Standards:Performance_Modelling_Reference_Content|Performance Modelling Reference Content]]
*[[Enterprise_Standards:Owner_Modelling_Reference_Content|Owner Modelling Reference Content]]
*[[Enterprise_Standards:Requirement_Modelling_Reference_Content|Requirement Modelling Reference Content]]
*[[Enterprise_Standards:Cost_Modelling_Reference_Content|Cost Modelling Reference Content]]
*[[Enterprise_Standards:Measurement_%26_Reporting_Modelling_Reference_Content|Measurement & Reporting Modelling Reference Content]]
*[[Enterprise_Standards:Data_Modelling_Reference_Content|Data Modelling Reference Content]]
*[[Enterprise_Standards:Governance_%26_Compliance_Reference_Content|Governance & Compliance Modelling Reference Content]]
*[[Enterprise_Standards:LEAD_Enterprise_Architecture_Reference_Content|LEAD Enterprise Architecture Reference Content]][[Category:Objects Inner]]

File:E+ GBI Production & GBS Retailer Case.pdf

2021-03-17T08:14:24Z

Admin: Admin uploaded a new version of File:E+ GBI Production & GBS Retailer Case.pdf

== Licensing ==
{{[[LEADing Practice IP::LEADing Practice IP]] }}

File:E+ Bug Reporting Template.docx

2021-02-12T11:57:55Z

Admin:

== Licensing ==
{{[[LEADing Practice IP::LEADing Practice IP]] }}

Main

2021-02-12T11:56:49Z

Admin:

<h1 style="color: #087dc1; margin-top: 0px;">Welcome to the '''SMART City E+ Tool'''</h1>

<hr style="margin-top: -5px; height: 10px; border: 0; box-shadow: 0 10px 10px -10px #fcaf17 inset;">

<div style="margin: 0 40px 0 0; width: 55%; float: left;">
Each city is different. Each city must therefore meet specific essentials and challenges. These can be urban challenges, their infrastructure, the government services, mobility, prosperity, the growing population (or its ageing), the environment, good governance, etc. Each city therefore needs to identify, model and develop their own smart city concept. The SMART City E+ tool is a new breed of integrated modelling and architecture tool. It is offered as a Software as a Service (SaaS) solution, and consists of 2 major application components:

#A SMART City Modelling Software component where the expert can create and work with many different types of modelling and architecture components; and
#A Knowledge Management system where the SMART City models, views and standards can be posted for anybody within and across the teams. You can also publish content and pages where citizens can comment on the program, project, initiative or concept. This provides a whole new SMART City development and continuous improvement possibility between the city and the citizens. Who feel they are part of developing and enhancing the SMART City concept, providing a whole new experience to modelling, publishing, referencing, commenting and continuous improvements in a collaborative and user-friendly environment.

== The SMART City '''Modelling Software''' Component ==
To transform itself into a smart city, any city has to direct its objectives, program and projects along a SMART City direction, considering multiple dimensions:

*'''SMART City Strategy''': one of the most basic, but also relevant areas, is defining the directional components. Specifying the smart city vision, strategy and objectives. This also sets the basis for the SMART City initiatives and thereby the portfolio management.
*'''Urban Planning''': It can be labelled as the structural scaffolding of a smart city; its maintenance system as well as the adjusted blueprint concept of the city. A smart city is an urban development concept to incorporate multiple information and communication technology (ICT) and Internet of Things (IoT) solutions.
*The '''SMART Economy''': it is a city that wants to position itself as a capital of the new economy and innovation as well as a centre that draws people to it.
*'''SMART Government''': it is a city whose public services have entered the digital era with efficient online services, wifi and the use of digital data produced in the city.
*The '''SMART Environment''': it is a city which reconciles its roles as a living space, for mobility, an economic centre… while reducing its footprint on the planet (reduced consumption of energy and natural resources and reduced polluting emissions).
*'''SMART Mobility''': it is the city which organises itself to offer an alternative to car congestion and pollution by promoting the effectiveness of means of collective and sustainable travel.
*The '''SMART Population''': it is a city which fosters the development of its citizens by levelling out inequalities and encouraging them to acquire skills.
*The '''SMART Living Environment''': it is a city which pushes itself up to the highest level in terms of health and safety for example.
*'''SMART Technology''' usage: Smart cities all share the characteristic of acting on their services and activities to make them more efficient. The ways they achieve this are very diverse, but they often have in common to use of digital technology resources (or ICTs, information and communication technologies). The degree of integration of ICTs in the urban functions is sometimes even considered as the criterion that marks out smart cities from other cities.
</div>

<div style="width: 35%; margin-right: 20px; float: left;">
<div style="padding: 20px; margin: 20px 0 20px 0; width: 100%; background-color: #f5f5f5; border: 2px solid #d2d3d5">
'''UPDATES & TUTORIALS'''
<hr style="margin-top: -5px; height: 10px; border: 0; box-shadow: 0 10px 10px -10px #fcaf17 inset;">

Here you can find a list of quick links that takes you directly to the tutorial page of each subject. Please find the list of tutorial subjects below:
*[[Media:Working_with_Objects_in_E+.pdf|Download Working with Objects in E+]]
*[[Media:E+_Bug_Reporting_Template.docx|Download the Bug Reporting Template]]
*[[Media:LEADing_Practice_-_Best Practice_&_Tips_&_Tricks_.pdf|Download the Best Practice & Tips & Tricks]]
*[[LEAD_Reference_Content:E%2B_GBI_Production_%26_GBS_Retailer_Case|E+ GBI Production & GBS Retailer Case]]
*[[LEAD_Reference_Content:Working_with_KM_%26_Templates|Working with KM & Templates]]
*[[LEAD_Reference_Content:Working_with_the_EnterprisePLUS_Modelling_Tool|Working with the EnterprisePLUS Modelling Tool]]
*[[LEAD_Reference_Content:Creating_Maps_%26_Matrices|Creating Maps & Matrices]]
</div>
</div>
[[File:SMART City-01.png|600 px|link=|alt=|center]]
</div>

<div style="clear: both;"></div>

SMART cities, except for a few rare smart cities created from scratch, all have a past during which regulations or customs have gradually developed… sometimes obsolete, sometimes counterproductive and often out of phase with the simplicity of internet enabled concepts and services. Wherever you are at the moment, we know that It is extremely critical to develop the As Is and To Be state of various SMART City programs, projects and initiatives. The SMART City E+ tool has as the first tool incorporated standards from ISO, OMG, LEADing Practice and IEEE to support the following standards:

'''Modelling Standards needed with SMART City development:'''

*Value Modelling Notations (VMN) – the ability to capture and documents the smart city value components such as citizen value proposition, services as well as also document and relate relevant programs that need to be considered.
*Strategy Modelling Notations (StMN) Value Modelling Notations (VMN) – the ability to capture and documents the smart city vision, mission, strategy, objectives, and goals that need to be considered.
*Planning Modelling Notations (PLMN) – it can capture urban planning, financial plans, detailed development plans and relate them all together (as needed)
*Policy Modelling Notations (PoMN) – documents and relate relevant policies, guidelines, procedures and rules that need to be considered.
*Reporting Modelling Notations (RPMN) – interlink performance measures, such as KPIs, PPIs, SPIs together and relate them to relevant reports.
*Risk Modelling Notations (RiMN) – capture and document applicable risk factors and components
*Rule Modelling Notations (RuMN) – document appropriate rules, that can relate to functions, processes, services, devices, infrastructure. Making this an advanced rule repository that can relate to all the other important subjects
*Quality Modelling Notations (QMN) – documents and define your quality aspects and relate them to any applicable component.
*Requirement Modelling Notations (ReMN) – you can document your requirements and sort them by groups of various stakeholders, from users, groups, executives or citizens.
*Capability Modelling Notations (CMN) – the ability to document As Is capabilities, measure the maturity of the capability and define the needed To Be capabilities.
*Blockchain Modelling Notations (BcMN) – Create your models and Blockchain concepts, allowing digital information to be distributed but not copied, blockchain technology created the backbone of a new type of SMART City interaction.
*Service Modelling Notations (SMN) – defining and modelling the existing as well as the needed service model is one of the foundational components of developing a new smart city concept
*Business Process Modelling Notations (BPMN) – document, capture and model your smart city flows and processes.
*Robotic Automation Modelling Notations (RAMN) – the ability to define where and when Robotic Automation makes sense and adds value is bringing the smart city to a whole new level and advanced modelling and development
*Application Modelling Notations (AMN) - Smart cities are all about automation and information sharing. The ways they achieve this are very diverse, but they often have in common to use of the ability to model where what needs to be automated and or integrated.
*Data Modelling Notations (DMN) – Data integration and sharing is the backbone of any smart city, the ability to develop data sequence and date distribution models are very important. But also, the ability to relate these components to all of the above discussed aspects.
*Platform Modelling Notations (PMN) - The degree of integration of the existing (As Is) platforms as well as the definition and development of new platform technology (To Be) needed is sometimes even considered as the criterion that marks out what your smart city will be able to do.
*Infrastructure Modelling Notations (IMN) – Interaction of existing infrastructure (As Is) and the enhancement, or new development of the cities infrastructure are at the heart of any smart city development. All enabled by SMART City E+
*Industry 4.0 Modelling Notations (I4MN) – how to make use of the industry 4.0 technology and internet of things in order to lift the cities technology capabilities, are foundational important components.

We listed some of the important and unique capabilities of the SMART City E+ tool, but in addition to the above mentioned modelling techniques, can it develop enterprise architecture views, among them:

*Business Architecture Notations (BAN)
*Information Architecture Notations (IAN)
*Technology Architecture Notations (TAN)
*Enterprise Architecture Notations (EAN)

The E+ software tools thereby uniquely satisfies the most common enterprise modelling and architecture needs that a SMART City would need. What males the tool unique is that these components are all integrated.

== The '''Knowledge Management''' system ==
The combination of a Modelling Software and Knowledge Management system is what differentiates SMART City E+ tool, from any other modelling, engineering and architecture tool. It is the combination of where the smart city modeller, engineer and/or architect can share the views/models created with each other as well as with others who don’t need to have the software access i.e. citizens. This can include uploading training content, quality parameters, own developed standards as well as time aspects, measures, reports, policies, procedures etc to a specific function, process or service. Or even upload the specific smart city program, project or initiative, so that citizens can comment on them. Making it a continuous improvement cycle. The SMART City E+ knowledge management component thereby creates and addresses the real knowledge issues around a smart city. KM Users and citizens can comment, provide feedback/suggestions to the uploaded content/views. As the SMART City E+ KMS content related back to the smart city objects and view (models), can the content be continuously be improved. While traditional content management databases contain only text and documents which computers can neither understand nor evaluate, the SMART City E+ KMS adds semantic annotations that allow any content to function as a collaborative database that recognizes cross relations. Making sure that there is a semantic relationship between the relevant subjects. The reason the SMART City E+ citizen users are free, is that we believe that there is no, need for costly users, when all they need to do is to view, follow instructions, provide input, document changes and also offer feedback. Making the SMART City E+ tool an effective and cheap tool for collaborative SMART City development.

== The E+ Demo Case ==

If you wish a SMART City E+ tool demo, please click on the button below and fill out your email address. We are happy to share with you the knowledge and insight we have around the development of a SMART City, and how to use a tool for this.
__NOTOC__

Main

2021-02-12T11:55:23Z

Admin:

<h1 style="color: #087dc1; margin-top: 0px;">Welcome to the '''SMART City E+ Tool'''</h1>

<hr style="margin-top: -5px; height: 10px; border: 0; box-shadow: 0 10px 10px -10px #fcaf17 inset;">

<div style="margin: 0 40px 0 0; width: 55%; float: left;">
Each city is different. Each city must therefore meet specific essentials and challenges. These can be urban challenges, their infrastructure, the government services, mobility, prosperity, the growing population (or its ageing), the environment, good governance, etc. Each city therefore needs to identify, model and develop their own smart city concept. The SMART City E+ tool is a new breed of integrated modelling and architecture tool. It is offered as a Software as a Service (SaaS) solution, and consists of 2 major application components:

#A SMART City Modelling Software component where the expert can create and work with many different types of modelling and architecture components; and
#A Knowledge Management system where the SMART City models, views and standards can be posted for anybody within and across the teams. You can also publish content and pages where citizens can comment on the program, project, initiative or concept. This provides a whole new SMART City development and continuous improvement possibility between the city and the citizens. Who feel they are part of developing and enhancing the SMART City concept, providing a whole new experience to modelling, publishing, referencing, commenting and continuous improvements in a collaborative and user-friendly environment.

== The SMART City '''Modelling Software''' Component ==
To transform itself into a smart city, any city has to direct its objectives, program and projects along a SMART City direction, considering multiple dimensions:

*'''SMART City Strategy''': one of the most basic, but also relevant areas, is defining the directional components. Specifying the smart city vision, strategy and objectives. This also sets the basis for the SMART City initiatives and thereby the portfolio management.
*'''Urban Planning''': It can be labelled as the structural scaffolding of a smart city; its maintenance system as well as the adjusted blueprint concept of the city. A smart city is an urban development concept to incorporate multiple information and communication technology (ICT) and Internet of Things (IoT) solutions.
*The '''SMART Economy''': it is a city that wants to position itself as a capital of the new economy and innovation as well as a centre that draws people to it.
*'''SMART Government''': it is a city whose public services have entered the digital era with efficient online services, wifi and the use of digital data produced in the city.
*The '''SMART Environment''': it is a city which reconciles its roles as a living space, for mobility, an economic centre… while reducing its footprint on the planet (reduced consumption of energy and natural resources and reduced polluting emissions).
*'''SMART Mobility''': it is the city which organises itself to offer an alternative to car congestion and pollution by promoting the effectiveness of means of collective and sustainable travel.
*The '''SMART Population''': it is a city which fosters the development of its citizens by levelling out inequalities and encouraging them to acquire skills.
*The '''SMART Living Environment''': it is a city which pushes itself up to the highest level in terms of health and safety for example.
*'''SMART Technology''' usage: Smart cities all share the characteristic of acting on their services and activities to make them more efficient. The ways they achieve this are very diverse, but they often have in common to use of digital technology resources (or ICTs, information and communication technologies). The degree of integration of ICTs in the urban functions is sometimes even considered as the criterion that marks out smart cities from other cities.
</div>

<div style="width: 35%; margin-right: 20px; float: left;">
<div style="padding: 20px; margin: 20px 0 20px 0; width: 100%; background-color: #f5f5f5; border: 2px solid #d2d3d5">
'''UPDATES & TUTORIALS'''
<hr style="margin-top: -5px; height: 10px; border: 0; box-shadow: 0 10px 10px -10px #fcaf17 inset;">

Here you can find a list of quick links that takes you directly to the tutorial page of each subject. Please find the list of tutorial subjects below:
*[[Media:LEADing_Practice_-_Best Practice_&_Tips_&_Tricks_.pdf|Download the Best Practice & Tips & Tricks]]
*[[Media:E+_Bug_Reporting_Template.docx|Download the Bug Reporting Template]]
*[[LEAD_Reference_Content:E%2B_GBI_Production_%26_GBS_Retailer_Case|E+ GBI Production & GBS Retailer Case]]
*[[LEAD_Reference_Content:Working_with_KM_%26_Templates|Working with KM & Templates]]
*[[LEAD_Reference_Content:Working_with_the_EnterprisePLUS_Modelling_Tool|Working with the EnterprisePLUS Modelling Tool]]
*[[LEAD_Reference_Content:Creating_Maps_%26_Matrices|Creating Maps & Matrices]]
</div>
</div>
[[File:SMART City-01.png|600 px|link=|alt=|center]]
</div>

<div style="clear: both;"></div>

SMART cities, except for a few rare smart cities created from scratch, all have a past during which regulations or customs have gradually developed… sometimes obsolete, sometimes counterproductive and often out of phase with the simplicity of internet enabled concepts and services. Wherever you are at the moment, we know that It is extremely critical to develop the As Is and To Be state of various SMART City programs, projects and initiatives. The SMART City E+ tool has as the first tool incorporated standards from ISO, OMG, LEADing Practice and IEEE to support the following standards:

'''Modelling Standards needed with SMART City development:'''

*Value Modelling Notations (VMN) – the ability to capture and documents the smart city value components such as citizen value proposition, services as well as also document and relate relevant programs that need to be considered.
*Strategy Modelling Notations (StMN) Value Modelling Notations (VMN) – the ability to capture and documents the smart city vision, mission, strategy, objectives, and goals that need to be considered.
*Planning Modelling Notations (PLMN) – it can capture urban planning, financial plans, detailed development plans and relate them all together (as needed)
*Policy Modelling Notations (PoMN) – documents and relate relevant policies, guidelines, procedures and rules that need to be considered.
*Reporting Modelling Notations (RPMN) – interlink performance measures, such as KPIs, PPIs, SPIs together and relate them to relevant reports.
*Risk Modelling Notations (RiMN) – capture and document applicable risk factors and components
*Rule Modelling Notations (RuMN) – document appropriate rules, that can relate to functions, processes, services, devices, infrastructure. Making this an advanced rule repository that can relate to all the other important subjects
*Quality Modelling Notations (QMN) – documents and define your quality aspects and relate them to any applicable component.
*Requirement Modelling Notations (ReMN) – you can document your requirements and sort them by groups of various stakeholders, from users, groups, executives or citizens.
*Capability Modelling Notations (CMN) – the ability to document As Is capabilities, measure the maturity of the capability and define the needed To Be capabilities.
*Blockchain Modelling Notations (BcMN) – Create your models and Blockchain concepts, allowing digital information to be distributed but not copied, blockchain technology created the backbone of a new type of SMART City interaction.
*Service Modelling Notations (SMN) – defining and modelling the existing as well as the needed service model is one of the foundational components of developing a new smart city concept
*Business Process Modelling Notations (BPMN) – document, capture and model your smart city flows and processes.
*Robotic Automation Modelling Notations (RAMN) – the ability to define where and when Robotic Automation makes sense and adds value is bringing the smart city to a whole new level and advanced modelling and development
*Application Modelling Notations (AMN) - Smart cities are all about automation and information sharing. The ways they achieve this are very diverse, but they often have in common to use of the ability to model where what needs to be automated and or integrated.
*Data Modelling Notations (DMN) – Data integration and sharing is the backbone of any smart city, the ability to develop data sequence and date distribution models are very important. But also, the ability to relate these components to all of the above discussed aspects.
*Platform Modelling Notations (PMN) - The degree of integration of the existing (As Is) platforms as well as the definition and development of new platform technology (To Be) needed is sometimes even considered as the criterion that marks out what your smart city will be able to do.
*Infrastructure Modelling Notations (IMN) – Interaction of existing infrastructure (As Is) and the enhancement, or new development of the cities infrastructure are at the heart of any smart city development. All enabled by SMART City E+
*Industry 4.0 Modelling Notations (I4MN) – how to make use of the industry 4.0 technology and internet of things in order to lift the cities technology capabilities, are foundational important components.

We listed some of the important and unique capabilities of the SMART City E+ tool, but in addition to the above mentioned modelling techniques, can it develop enterprise architecture views, among them:

*Business Architecture Notations (BAN)
*Information Architecture Notations (IAN)
*Technology Architecture Notations (TAN)
*Enterprise Architecture Notations (EAN)

The E+ software tools thereby uniquely satisfies the most common enterprise modelling and architecture needs that a SMART City would need. What males the tool unique is that these components are all integrated.

== The '''Knowledge Management''' system ==
The combination of a Modelling Software and Knowledge Management system is what differentiates SMART City E+ tool, from any other modelling, engineering and architecture tool. It is the combination of where the smart city modeller, engineer and/or architect can share the views/models created with each other as well as with others who don’t need to have the software access i.e. citizens. This can include uploading training content, quality parameters, own developed standards as well as time aspects, measures, reports, policies, procedures etc to a specific function, process or service. Or even upload the specific smart city program, project or initiative, so that citizens can comment on them. Making it a continuous improvement cycle. The SMART City E+ knowledge management component thereby creates and addresses the real knowledge issues around a smart city. KM Users and citizens can comment, provide feedback/suggestions to the uploaded content/views. As the SMART City E+ KMS content related back to the smart city objects and view (models), can the content be continuously be improved. While traditional content management databases contain only text and documents which computers can neither understand nor evaluate, the SMART City E+ KMS adds semantic annotations that allow any content to function as a collaborative database that recognizes cross relations. Making sure that there is a semantic relationship between the relevant subjects. The reason the SMART City E+ citizen users are free, is that we believe that there is no, need for costly users, when all they need to do is to view, follow instructions, provide input, document changes and also offer feedback. Making the SMART City E+ tool an effective and cheap tool for collaborative SMART City development.

== The E+ Demo Case ==

If you wish a SMART City E+ tool demo, please click on the button below and fill out your email address. We are happy to share with you the knowledge and insight we have around the development of a SMART City, and how to use a tool for this.
__NOTOC__

Information Flow

2020-07-15T08:33:36Z

Admin: Created page with "{{#lead-mw-content: MetaObjectDescriptions|getPageContent|{{FULLPAGENAME}} }} === Reference Content === *Enterprise_Standards:Strategy_Management_Reference_Content|Strategy..."

{{#lead-mw-content: MetaObjectDescriptions|getPageContent|{{FULLPAGENAME}} }}

=== Reference Content ===
*[[Enterprise_Standards:Strategy_Management_Reference_Content|Strategy Management Reference Content]]
*[[Enterprise_Standards:Growth%3A_Core_Differentiating_%26_Core_Competitive_Reference_Content|Growth: Core Differentiating & Core Competitive Reference Content]]
*[[Enterprise_Standards:Performance_Management_Reference_Content|Performance Management Reference Content]]
*[[Enterprise_Standards:Planning_Management_Reference_Content|Planning Management Reference Content]]
*[[Enterprise_Standards:Production_Management_Reference_Content|Production Management Reference Content]]
*[[Enterprise_Standards:Portfolio_Management_Reference_Content|Portfolio Management Reference Content]][[Category:Objects Inner]]

File:Working with Objects in E+.pdf

2020-03-03T11:46:31Z

Admin:

== Licensing ==
{{[[LEADing Practice IP::LEADing Practice IP]] }}

File:Creating Maps & Matrices.pdf

2020-03-03T11:46:01Z

Admin:

== Licensing ==
{{[[LEADing Practice IP::LEADing Practice IP]] }}

File:Working with E+ Modelling Tool 2.mp4

2020-03-03T11:44:12Z

Admin:

== Licensing ==
{{[[LEADing Practice IP::LEADing Practice IP]] }}

LEAD Reference Content:Working with the EnterprisePLUS Modelling Tool

2020-03-03T11:44:11Z

Admin:

{{DISPLAYTITLE: Working with the EnterprisePLUS Modelling Tool}}
= Working with E+ Modelling Tool 1 =
This video showcases different ways of woring with the E+ modelling tool and its canvas, and demonstrates techniques, modelling principles, workflows and varios "How-To's".

<html5media height='1024' width='768'>File:Working_with_E+_Modelling_Tool_1.mp4</html5media>

= Working with E+ Modelling Tool 2 =
This video showcases different ways of woring with the E+ modelling tool and its canvas, and demonstrates techniques, modelling principles, workflows and varios "How-To's". Continued from previous video.

<html5media height='1024' width='768'>File:Working_with_E+_Modelling_Tool_2.mp4</html5media>

= Working with E+ Modelling Tool 3 =
This video showcases different ways of woring with the E+ modelling tool and its canvas, and demonstrates techniques, modelling principles, workflows and varios "How-To's". Continued from previous video.

<html5media height='1024' width='768'>File:Working_with_E+_Modelling_Tool_3.mp4</html5media>

= Working with E+ Modelling Tool 4 =
In this presentation, we show you how to identify, define and create objects for use with the E+ Modelling Tool.

'''Tutorial Document''': [[Media:Working_with_Objects_ in_ E+.pdf|Download the Working with Objects in E+ presentation.]]

[[Category: Tutorials]]

LEAD Reference Content:Creating Maps & Matrices

2020-03-03T11:42:25Z

Admin: Created page with "{{DISPLAYTITLE: Creating Maps & Matrices}} = Creating Maps & Matrices = In this presentation, we will explain in detail the basics of creating and working with maps and matri..."

{{DISPLAYTITLE: Creating Maps & Matrices}}
= Creating Maps & Matrices =

In this presentation, we will explain in detail the basics of creating and working with maps and matrices.

'''Tutorial Document''': [[Media:Creating_Maps_&_Matrices.pdf|Download the '''Creating Maps & Matrices''' presentation.]]

[[Category: Tutorials]]

File:Working with E+ Modelling Tool 1.mp4

2020-03-03T11:41:29Z

Admin:

== Licensing ==
{{[[LEADing Practice IP::LEADing Practice IP]] }}

LEAD Reference Content:Working with the EnterprisePLUS Modelling Tool

2020-03-03T11:41:21Z

Admin: Created page with "{{DISPLAYTITLE: Working with the EnterprisePLUS Modelling Tool}} = Working with E+ Modelling Tool 1 = This video showcases different ways of woring with the E+ modelling tool..."

{{DISPLAYTITLE: Working with the EnterprisePLUS Modelling Tool}}
= Working with E+ Modelling Tool 1 =
This video showcases different ways of woring with the E+ modelling tool and its canvas, and demonstrates techniques, modelling principles, workflows and varios "How-To's".

<html5media height='1024' width='768'>File:Working_with_E+_Modelling_Tool_1.mp4</html5media>

= Working with E+ Modelling Tool 2 =
This video showcases different ways of woring with the E+ modelling tool and its canvas, and demonstrates techniques, modelling principles, workflows and varios "How-To's". Continued from previous video.

<html5media height='1024' width='768'>File:Working_with_E+_Modelling_Tool_2.mp4</html5media>

= Working with E+ Modelling Tool 3 =
This video showcases different ways of woring with the E+ modelling tool and its canvas, and demonstrates techniques, modelling principles, workflows and varios "How-To's". Continued from previous video.

<html5media height='1024' width='768'>File:Working_with_E+_Modelling_Too_3.mp4</html5media>

= Working with E+ Modelling Tool 4 =
In this presentation, we show you how to identify, define and create objects for use with the E+ Modelling Tool.

'''Tutorial Document''': [[Media:Working_with_Objects_ in_ E+.pdf|Download the Working with Objects in E+ presentation.]]

[[Category: Tutorials]]

LEAD Reference Content:Working with KM & Templates

2020-03-03T11:40:23Z

Admin: Created page with "{{DISPLAYTITLE: Working with the EnterprisePLUS Modelling Tool}} = Working with KM & Templates = In this presentation, we show you: #how the new features and functions in the..."

{{DISPLAYTITLE: Working with the EnterprisePLUS Modelling Tool}}
= Working with KM & Templates =
In this presentation, we show you:
#how the new features and functions in the '''Knowledge Management''' system
#how to add content to KM pages
#how to create new models based on templates
#how to import models from other file formats within the '''Modelling Tool'''.

'''Tutorial Document''': [[Media:Working_with_KM_amd_Templates.pdf|Download the "Working with KM & Templates" tutorial document.]]

[[Category: Tutorials]]

File:Working with E+ Modelling Tool 3.mp4

2020-03-03T11:39:57Z

Admin:

== Licensing ==
{{[[LEADing Practice IP::LEADing Practice IP]] }}

File:Working with KM amd Templates.pdf

2020-03-03T11:37:46Z

Admin:

== Licensing ==
{{[[LEADing Practice IP::LEADing Practice IP]] }}

File:LEADing Practice - Best Practice & Tips & Tricks .pdf

2020-03-03T11:37:29Z

Admin:

== Licensing ==
{{[[LEADing Practice IP::LEADing Practice IP]] }}

Main

2020-03-03T11:37:07Z

Admin:

<h1 style="color: #087dc1; margin-top: 0px;">Welcome to the '''SMART City E+ Tool'''</h1>

<hr style="margin-top: -5px; height: 10px; border: 0; box-shadow: 0 10px 10px -10px #fcaf17 inset;">

<div style="margin: 0 40px 0 0; width: 55%; float: left;">
Each city is different. Each city must therefore meet specific essentials and challenges. These can be urban challenges, their infrastructure, the government services, mobility, prosperity, the growing population (or its ageing), the environment, good governance, etc. Each city therefore needs to identify, model and develop their own smart city concept. The SMART City E+ tool is a new breed of integrated modelling and architecture tool. It is offered as a Software as a Service (SaaS) solution, and consists of 2 major application components:

#A SMART City Modelling Software component where the expert can create and work with many different types of modelling and architecture components; and
#A Knowledge Management system where the SMART City models, views and standards can be posted for anybody within and across the teams. You can also publish content and pages where citizens can comment on the program, project, initiative or concept. This provides a whole new SMART City development and continuous improvement possibility between the city and the citizens. Who feel they are part of developing and enhancing the SMART City concept, providing a whole new experience to modelling, publishing, referencing, commenting and continuous improvements in a collaborative and user-friendly environment.

== The SMART City '''Modelling Software''' Component ==
To transform itself into a smart city, any city has to direct its objectives, program and projects along a SMART City direction, considering multiple dimensions:

*'''SMART City Strategy''': one of the most basic, but also relevant areas, is defining the directional components. Specifying the smart city vision, strategy and objectives. This also sets the basis for the SMART City initiatives and thereby the portfolio management.
*'''Urban Planning''': It can be labelled as the structural scaffolding of a smart city; its maintenance system as well as the adjusted blueprint concept of the city. A smart city is an urban development concept to incorporate multiple information and communication technology (ICT) and Internet of Things (IoT) solutions.
*The '''SMART Economy''': it is a city that wants to position itself as a capital of the new economy and innovation as well as a centre that draws people to it.
*'''SMART Government''': it is a city whose public services have entered the digital era with efficient online services, wifi and the use of digital data produced in the city.
*The '''SMART Environment''': it is a city which reconciles its roles as a living space, for mobility, an economic centre… while reducing its footprint on the planet (reduced consumption of energy and natural resources and reduced polluting emissions).
*'''SMART Mobility''': it is the city which organises itself to offer an alternative to car congestion and pollution by promoting the effectiveness of means of collective and sustainable travel.
*The '''SMART Population''': it is a city which fosters the development of its citizens by levelling out inequalities and encouraging them to acquire skills.
*The '''SMART Living Environment''': it is a city which pushes itself up to the highest level in terms of health and safety for example.
*'''SMART Technology''' usage: Smart cities all share the characteristic of acting on their services and activities to make them more efficient. The ways they achieve this are very diverse, but they often have in common to use of digital technology resources (or ICTs, information and communication technologies). The degree of integration of ICTs in the urban functions is sometimes even considered as the criterion that marks out smart cities from other cities.
</div>

<div style="width: 35%; margin-right: 20px; float: left;">
<div style="padding: 20px; margin: 20px 0 20px 0; width: 100%; background-color: #f5f5f5; border: 2px solid #d2d3d5">
'''UPDATES & TUTORIALS'''
<hr style="margin-top: -5px; height: 10px; border: 0; box-shadow: 0 10px 10px -10px #fcaf17 inset;">

Here you can find a list of quick links that takes you directly to the tutorial page of each subject. Please find the list of tutorial subjects below:
*[[Media:LEADing_Practice_-_Best Practice_&_Tips_&_Tricks_.pdf|Download the Best Practice & Tips & Tricks]]
*[[LEAD_Reference_Content:E%2B_GBI_Production_%26_GBS_Retailer_Case|E+ GBI Production & GBS Retailer Case]]
*[[LEAD_Reference_Content:Working_with_KM_%26_Templates|Working with KM & Templates]]
*[[LEAD_Reference_Content:Working_with_the_EnterprisePLUS_Modelling_Tool|Working with the EnterprisePLUS Modelling Tool]]
*[[LEAD_Reference_Content:Creating_Maps_%26_Matrices|Creating Maps & Matrices]]
</div>
</div>
[[File:SMART City-01.png|600 px|link=|alt=|center]]
</div>

<div style="clear: both;"></div>

SMART cities, except for a few rare smart cities created from scratch, all have a past during which regulations or customs have gradually developed… sometimes obsolete, sometimes counterproductive and often out of phase with the simplicity of internet enabled concepts and services. Wherever you are at the moment, we know that It is extremely critical to develop the As Is and To Be state of various SMART City programs, projects and initiatives. The SMART City E+ tool has as the first tool incorporated standards from ISO, OMG, LEADing Practice and IEEE to support the following standards:

'''Modelling Standards needed with SMART City development:'''

*Value Modelling Notations (VMN) – the ability to capture and documents the smart city value components such as citizen value proposition, services as well as also document and relate relevant programs that need to be considered.
*Strategy Modelling Notations (StMN) Value Modelling Notations (VMN) – the ability to capture and documents the smart city vision, mission, strategy, objectives, and goals that need to be considered.
*Planning Modelling Notations (PLMN) – it can capture urban planning, financial plans, detailed development plans and relate them all together (as needed)
*Policy Modelling Notations (PoMN) – documents and relate relevant policies, guidelines, procedures and rules that need to be considered.
*Reporting Modelling Notations (RPMN) – interlink performance measures, such as KPIs, PPIs, SPIs together and relate them to relevant reports.
*Risk Modelling Notations (RiMN) – capture and document applicable risk factors and components
*Rule Modelling Notations (RuMN) – document appropriate rules, that can relate to functions, processes, services, devices, infrastructure. Making this an advanced rule repository that can relate to all the other important subjects
*Quality Modelling Notations (QMN) – documents and define your quality aspects and relate them to any applicable component.
*Requirement Modelling Notations (ReMN) – you can document your requirements and sort them by groups of various stakeholders, from users, groups, executives or citizens.
*Capability Modelling Notations (CMN) – the ability to document As Is capabilities, measure the maturity of the capability and define the needed To Be capabilities.
*Blockchain Modelling Notations (BcMN) – Create your models and Blockchain concepts, allowing digital information to be distributed but not copied, blockchain technology created the backbone of a new type of SMART City interaction.
*Service Modelling Notations (SMN) – defining and modelling the existing as well as the needed service model is one of the foundational components of developing a new smart city concept
*Business Process Modelling Notations (BPMN) – document, capture and model your smart city flows and processes.
*Robotic Automation Modelling Notations (RAMN) – the ability to define where and when Robotic Automation makes sense and adds value is bringing the smart city to a whole new level and advanced modelling and development
*Application Modelling Notations (AMN) - Smart cities are all about automation and information sharing. The ways they achieve this are very diverse, but they often have in common to use of the ability to model where what needs to be automated and or integrated.
*Data Modelling Notations (DMN) – Data integration and sharing is the backbone of any smart city, the ability to develop data sequence and date distribution models are very important. But also, the ability to relate these components to all of the above discussed aspects.
*Platform Modelling Notations (PMN) - The degree of integration of the existing (As Is) platforms as well as the definition and development of new platform technology (To Be) needed is sometimes even considered as the criterion that marks out what your smart city will be able to do.
*Infrastructure Modelling Notations (IMN) – Interaction of existing infrastructure (As Is) and the enhancement, or new development of the cities infrastructure are at the heart of any smart city development. All enabled by SMART City E+
*Industry 4.0 Modelling Notations (I4MN) – how to make use of the industry 4.0 technology and internet of things in order to lift the cities technology capabilities, are foundational important components.

We listed some of the important and unique capabilities of the SMART City E+ tool, but in addition to the above mentioned modelling techniques, can it develop enterprise architecture views, among them:

*Business Architecture Notations (BAN)
*Information Architecture Notations (IAN)
*Technology Architecture Notations (TAN)
*Enterprise Architecture Notations (EAN)

The E+ software tools thereby uniquely satisfies the most common enterprise modelling and architecture needs that a SMART City would need. What males the tool unique is that these components are all integrated.

== The '''Knowledge Management''' system ==
The combination of a Modelling Software and Knowledge Management system is what differentiates SMART City E+ tool, from any other modelling, engineering and architecture tool. It is the combination of where the smart city modeller, engineer and/or architect can share the views/models created with each other as well as with others who don’t need to have the software access i.e. citizens. This can include uploading training content, quality parameters, own developed standards as well as time aspects, measures, reports, policies, procedures etc to a specific function, process or service. Or even upload the specific smart city program, project or initiative, so that citizens can comment on them. Making it a continuous improvement cycle. The SMART City E+ knowledge management component thereby creates and addresses the real knowledge issues around a smart city. KM Users and citizens can comment, provide feedback/suggestions to the uploaded content/views. As the SMART City E+ KMS content related back to the smart city objects and view (models), can the content be continuously be improved. While traditional content management databases contain only text and documents which computers can neither understand nor evaluate, the SMART City E+ KMS adds semantic annotations that allow any content to function as a collaborative database that recognizes cross relations. Making sure that there is a semantic relationship between the relevant subjects. The reason the SMART City E+ citizen users are free, is that we believe that there is no, need for costly users, when all they need to do is to view, follow instructions, provide input, document changes and also offer feedback. Making the SMART City E+ tool an effective and cheap tool for collaborative SMART City development.

== The E+ Demo Case ==

If you wish a SMART City E+ tool demo, please click on the button below and fill out your email address. We are happy to share with you the knowledge and insight we have around the development of a SMART City, and how to use a tool for this.
__NOTOC__

Project

2019-10-28T13:45:32Z

Admin: Created page with "{{#lead-mw-content: MetaObjectDescriptions|getPageContent|{{FULLPAGENAME}} }}"

{{#lead-mw-content: MetaObjectDescriptions|getPageContent|{{FULLPAGENAME}} }}

Program

2019-10-28T13:45:18Z

Admin: Created page with "{{#lead-mw-content: MetaObjectDescriptions|getPageContent|{{FULLPAGENAME}} }}"

{{#lead-mw-content: MetaObjectDescriptions|getPageContent|{{FULLPAGENAME}} }}

Portfolio

2019-10-28T13:45:03Z

Admin: Created page with "{{#lead-mw-content: MetaObjectDescriptions|getPageContent|{{FULLPAGENAME}} }}"

{{#lead-mw-content: MetaObjectDescriptions|getPageContent|{{FULLPAGENAME}} }}

GDPR Compliance

2019-10-07T11:11:35Z

Admin: Created page with "{{DISPLAYTITLE: GDPR Compliance Statement}} = Definition = The EU General Data Protection Regulation (GDPR) is a privacy and data protection regulation in the European Union..."

{{DISPLAYTITLE: GDPR Compliance Statement}}

= Definition =
The EU General Data Protection Regulation (GDPR) is a privacy and data protection regulation in the European Union effective from May 25 2018.
The GDPR imposes new obligations on organisations that control or process personal data and introduces new rights and protections for EU citizens.

== EnterprisePLUS (E+) GDPR Compliance Statement ==
We are committed to ensuring that your privacy is protected and we strictly adhere to the provisions of all relevant Data Protection Legislation, including GDPR, ensuring all personal data is handled in line with the principles outlined in the regulation that state:

Personal data shall be:

#Processed lawfully, fairly and in a transparent manner in relation to the data subject.
#Collected for specified, explicit and legitimate purposes and not further processed in a manner that is incompatible with those purposes.
#Adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed.
#Accurate and, where necessary, kept up to date.
#Kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed.
#Processed in a manner that ensures appropriate security of the personal data, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage, using appropriate technical or organisational measures.

== EnterprisePLUS (E+) GDPR Compliance Commitment ==
LEADing Practice respect our customers, software users and learner’s rights to data privacy and protection and as such we have revised our internal policies, procedures, working practices in order to meet the requirements of the GDPR.
We place a high priority on protecting and managing data in accordance with accepted standards and indeed helping our customers utilise our standards, reference content, artefacts, tool and services to the same end.
LEADing Practice are committed to compliance with the GDPR as both a processor and controller of personal data and have established a working group to lead our GDPR implementation project and ensure compliance on an ongoing basis.

== EnterprisePLUS (E+) GDPR Contact Person ==
If you have any further questions please speak to your GDPR account manager Ulrik Foldager at '''ufo@leadingpractice.com''' or contact '''info@leadingpractice.com'''.

File:SMART City-01.png

2019-03-08T11:35:57Z

Admin: Admin uploaded a new version of File:SMART City-01.png

== Licensing ==
{{[[LEADing Practice IP::LEADing Practice IP]] }}

Urban Planning

2019-01-30T13:48:51Z

Admin: Created page with "{{#lead-mw-content: MetaObjectDescriptions|getPageContent|{{FULLPAGENAME}} }}"

{{#lead-mw-content: MetaObjectDescriptions|getPageContent|{{FULLPAGENAME}} }}

SMART City KM:Main

2019-01-30T09:49:07Z

Admin:

{{DISPLAYTITLE: SMART City KM}}
Number of articles in ''' SMART City KM''': {{NUMBEROFARTICLES}}

Organizational Rule

2019-01-24T11:49:02Z

Main

2019-01-21T09:07:17Z

Admin:

<h1 style="color: #087dc1; margin-top: 0px;">Welcome to '''EnterprisePLUS'''</h1>

<hr style="margin-top: -5px; height: 10px; border: 0; box-shadow: 0 10px 10px -10px #fcaf17 inset;">

The EnterprisePLUS software tools (Enterprise+ or E+) is a new breed of integrated modelling and architecture tool. It is offered as a Software as a Service (SaaS) solution, and consists of 2 major application components:
#A Modelling Software component where the expert can create and work with many different types of modelling and architecture components; and
#A Knowledge Management system where the models, views and standards can be posted for anybody within the enterprise. This provides a whole new experience to publishing, referencing, commenting and continuous improvements in a collaborative and user-friendly environment.

== The '''Modelling Software''' Component ==

Various enterprise modelling and enterprise architecture concepts and disciplines have become a normal part of daily work. It doesn’t matter if it's about documenting the existing As-Is state or designing the future To-Be state, the need for modelling and architecting aspects of the enterprise is always relevant.

E+ has as the first tool incorporated standards from ISO, OMG, LEADing Practice and IEEE to support the following standards:

'''Enterprise Modelling Standards:'''
*Value Modelling Notations (VMN)
*Strategy Modelling Notations (StMN)
*Planning Modelling Notations (PLMN)
*Policy Modelling Notations (PoMN)
*Reporting Modelling Notations (RPMN)
*Risk Modelling Notations (RiMN)
*Rule Modelling Notations (RuMN)
*Quality Modelling Notations (QMN)
*Requirement Modelling Notations (ReMN)
*Capability Modelling Notations (CMN)
*Blockchain Modelling Notations (BcMN)
*Service Modelling Notations (SMN)
*Business Process Modelling Notations (BPMN)
*Robotic Automation Modelling Notations (RAMN)
*Application Modelling Notations (AMN)
*Data Modelling Notations (DMN)
*Platform Modelling Notations (PMN)
*Infrastructure Modelling Notations (IMN)
*Industry 4.0 Modelling Notations (I4MN)

'''Enterprise Architecture Standards:'''
*Business Architecture Notations (BAN)
*Information Architecture Notations (IAN)
*Technology Architecture Notations (TAN)
*Enterprise Architecture Notations (EAN)

The E+ software tools thereby uniquely satisfies the most common enterprise modelling and architecture needs.

== The '''Knowledge Management''' system ==

The combination of the E+ modelling and Knowledge Management System is what differentiates E+, from any other enterprise modelling, engineering and architecture tool. It is the combination of where the enterprise modeller, engineer and/or architect can share the views/models created with others who don’t need to have the software access. This can include uploading training content, quality parameters, own developed standards as well as time aspects, measures, reports, policies, procedures etc to a specific function, process or service.

The E+ knowledge management thereby creates and addresses the real knowledge issues inside the organization. KM Users can comment, provide feedback/suggestions to the uploaded content/views. As the E+ KMS content related back to the E+ objects and view (models), can the content be continuously be improved. While traditional content management databases contain only text and documents which computers can neither understand nor evaluate, the E+ KMS adds semantic annotations that allow any content to function as a collaborative database that recognizes cross relations. Making sure that there is a semantic relationship between the relevant subjects. The reason the E+ KMS users are cheaper than the E+ modelling user licenses, is based on that the E+ KMS users are viewing and using the system. There is no need for costly users, when all the need to do is to view, follow instructions, provide input, document changes and also offer feedback.

== The '''E+ Demo Case''' ==

We have a lot of different self-study tutorials that help you work with E+. Here you can find a basic description tutorial of how to get started.

'''Tutorial Document''': [[Media:E+ GBI Production & GBS Retailer Case.pdf|Download the E+ GBI Production & GBS Retailer Case Model.]]

__NOTOC__

LEAD Reference Content:Maturity Reference Content

2019-01-15T13:55:48Z

Admin:

{{DISPLAYTITLE:Maturity Reference Content}}
= Maturity Reference Content =
In order for organizations to perform well in a global competitive world, it is important to identify the competitive advantages that they can benefit from. Models to assess status and identify improvement opportunities, and in particular maturity models, that can help organizations assessing their current competencies in a structured way to implement changes and improvements, has become essential.

A maturity model can be described as a structured collection of elements that describe certain aspects of maturity in an organization. A maturity model may provide, for example:

*a place to start;
*the benefit of a community’s prior experiences;
*a common language and a shared vision;
*a framework for prioritizing actions; and
*a way to define what improvement means for your organization.

A maturity model can also be used as a benchmark for comparison and as an aid to understanding.

There are a lot of different maturity approaches on the market, the most known is CMM and CMMI, however the narrow focus makes these maturity models and approaches limited to real essential architecture and business improvement (e.g. cross business effectiveness and efficiency). In 2009, four universities therefore joined their combined forces to further innovate and develop the maturity models. These four Universities were a part of the Global University Alliance which consists of more than 900 universities. Out of all these universities, four Universities (both IT Universities and Business Schools) dedicated their time and resources in three different countries with vested research interest in business process management, strategy modelling, economics, business modelling, value management, performance management, service aspects, information and technology modelling. They brought together a rich blend of both academic and industry experience to contribute to a maturing field in Business and IT. The research and development team was lead by Mark von Rosing (Copenhagen Business School and IT University, Denmark), Siavash Moshiri (Sheffield Business School, United Kingdom) and Karin Gräslund (Wiesbaden Business School, Germany).

The maturity model development had the following focus:
*Practical as well as academic research.
*Best practice from different Industry leaders - to be a foundation of best practice standardization.
*Competency development maturity models where a company can focus not only on capabilities but on competencies (capabilities and resources).
*Integration of different maturity model.
*Cross-disciplinary integration of Enterprise Modelling concepts e.g. business model, all value aspects, services, process, information, applications, data, platforms, infrastructure, cloud as well as for transformation and innovation modelling.
*Modelling from As-Is and To-Be development and the identification of Core Competitive and Core Differentiated areas as well as value areas/drivers.
*Effective use of its maturities as they are rated with their Revenue and Cost: High, Medium or Low. To ensure the cost to achieve a higher maturity level would not exceed the possible gain. This may effectively “blind” an organization to the most effective use of its capabilities and resources.

During 2010, more people from the industry joined, among these were development members who work for SAP, IBM, Danish Defense, Government of Canada, Artos Origin, and The Open Group (who develops TOGAF) gave input, feedback and QA to build the cross integrated maturity models, some of these with more business focus while others with more application or technology focus.

The LEADing Practice Maturity Reference Content consist today of the following:

#Business Model Maturity
#Process Maturity
#Value Maturity
#Service Maturity
#Cloud Maturity
#Information Maturity
#Application Maturity
#Data Maturity
#Platform Maturity
#Infrastructure Maturity

[[File:POSTER-LEAD-Maturity-Reference-Method.png|frame|center|900px|link=http://{{SERVERNAME}}/images/c/cd/POSTER-LEAD-Maturity-Reference-Method.png|LEADing Practice Maturity Reference Content poster]]

[[Category: Maturity Assessment]]

Main

2019-01-15T13:22:19Z

Admin:

<h1 style="color: #087dc1; margin-top: 0px;">Welcome to '''EnterprisePLUS'''</h1>

<hr style="margin-top: -5px; height: 10px; border: 0; box-shadow: 0 10px 10px -10px #fcaf17 inset;">

<div style="margin: 0 40px 0 0; width: 65%; float: left;">
The EnterprisePLUS software tools (Enterprise+ or E+) is a new breed of integrated modelling and architecture tool. It is offered as a Software as a Service (SaaS) solution, and consists of 2 major application components:
#A Modelling Software component where the expert can create and work with many different types of modelling and architecture components; and
#A Knowledge Management system where the models, views and standards can be posted for anybody within the enterprise. This provides a whole new experience to publishing, referencing, commenting and continuous improvements in a collaborative and user-friendly environment.

== The '''Modelling Software''' Component ==

Various enterprise modelling and enterprise architecture concepts and disciplines have become a normal part of daily work. It doesn’t matter if it's about documenting the existing As-Is state or designing the future To-Be state, the need for modelling and architecting aspects of the enterprise is always relevant.

E+ has as the first tool incorporated standards from ISO, OMG, LEADing Practice and IEEE to support the following standards:

'''Enterprise Modelling Standards:'''
*Value Modelling Notations (VMN)
*Strategy Modelling Notations (StMN)
*Planning Modelling Notations (PLMN)
*Policy Modelling Notations (PoMN)
*Reporting Modelling Notations (RPMN)
*Risk Modelling Notations (RiMN)
*Rule Modelling Notations (RuMN)
*Quality Modelling Notations (QMN)
*Requirement Modelling Notations (ReMN)
*Capability Modelling Notations (CMN)
*Blockchain Modelling Notations (BcMN)
*Service Modelling Notations (SMN)
*Business Process Modelling Notations (BPMN)
*Robotic Automation Modelling Notations (RAMN)
*Application Modelling Notations (AMN)
*Data Modelling Notations (DMN)
*Platform Modelling Notations (PMN)
*Infrastructure Modelling Notations (IMN)
*Industry 4.0 Modelling Notations (I4MN)

'''Enterprise Architecture Standards:'''
*Business Architecture Notations (BAN)
*Information Architecture Notations (IAN)
*Technology Architecture Notations (TAN)
*Enterprise Architecture Notations (EAN)

The E+ software tools thereby uniquely satisfies the most common enterprise modelling and architecture needs.

== The '''Knowledge Management''' system ==

The combination of the E+ modelling and Knowledge Management System is what differentiates E+, from any other enterprise modelling, engineering and architecture tool. It is the combination of where the enterprise modeller, engineer and/or architect can share the views/models created with others who don’t need to have the software access. This can include uploading training content, quality parameters, own developed standards as well as time aspects, measures, reports, policies, procedures etc to a specific function, process or service.

The E+ knowledge management thereby creates and addresses the real knowledge issues inside the organization. KM Users can comment, provide feedback/suggestions to the uploaded content/views. As the E+ KMS content related back to the E+ objects and view (models), can the content be continuously be improved. While traditional content management databases contain only text and documents which computers can neither understand nor evaluate, the E+ KMS adds semantic annotations that allow any content to function as a collaborative database that recognizes cross relations. Making sure that there is a semantic relationship between the relevant subjects. The reason the E+ KMS users are cheaper than the E+ modelling user licenses, is based on that the E+ KMS users are viewing and using the system. There is no need for costly users, when all the need to do is to view, follow instructions, provide input, document changes and also offer feedback.

== The '''E+ Demo Case''' ==

We have a lot of different self-study tutorials that help you work with E+. Here you can find a basic description tutorial of how to get started.

'''Tutorial Document''': [[Media:E+ GBI Production & GBS Retailer Case.pdf|Download the E+ GBI Production & GBS Retailer Case Model.]]
</div>

<div style="width: 25%; margin-right: 20px; float: left;">
[[File:E+ 4 FLSmidth-01.png|300 px|link=|alt=|center]]
</div>

<div style="clear: both;"></div>

__NOTOC__

LEAD Reference Content:Cost Modelling Reference Content

2019-01-15T13:17:54Z

Admin: Created page with "{{DISPLAYTITLE: Cost Modelling Reference Content}} = Cost Modelling Reference Content = The LEADing Practice Cost Reference Content provides cost ontology with its specific co..."

{{DISPLAYTITLE: Cost Modelling Reference Content}}
= Cost Modelling Reference Content =
The LEADing Practice Cost Reference Content provides cost ontology with its specific cost descriptions, semantic relations and correlations. It is based on a collection of best and leading practice around cost modelling, cost engineering and cost architecture disciplines all related to cost identification, cost planning, cost creation, cost realization as well as cost management and cost governance.

The Cost Reference Content is therefore and essential part for any practitioner working with and around cost aspects. It provides a structural way of thinking, working, modelling, implementation and governance around cost definitions e.g. external forces influencing and impacting the cost drivers. As well as an overview of the key cost aspects of the organisation and how they relate to the various strategies, critical success factors, goals, business area and groups, the business owners, stakeholders and their cost requirements as well as a way of cost modelling, cost engineering and cost architecture, where the Cost Reference Content provides a way of analysing, appraising, approximating, assessing and capturing cost related objects to enable innovation and transformation.

'''Documentation''': [[Media:LEADing Practice Cost Modelling REFERENCE CONTENT-LEAD-ES20012BC.pdf|Download the Cost Modelling Reference Content document]]

[[Category: Cost]]

SMART City KM:Category

2019-01-15T13:08:33Z

Admin: Created page with "{{PAGESINCATEGORY: Category}}"

LEAD Reference Content:Geographical Information System (GIS) Reference Content

2019-01-15T11:41:44Z

Admin:

{{DISPLAYTITLE:Geographical Information System (GIS) Reference Content}}
= Geographical Information System (GIS) Reference Content =
The LEADing Practice Geographic Information System (GIS) Reference Content is the result of research, industry expert and academic consensus and agreement.

A Geographic Information System (GIS) is a computer system designed to capture, store, manipulate, analyse, manage, and present all types of geographical data. Since GIS provides spatial data entry, management, retrieval, analysis, and visualization functions, the implementation of a GIS is often driven by jurisdictional (such as a country, region and/or city), purpose or application requirements.

Our research reveals that there is more in common in developing a GIS architecture and GIS solution than what is commonly believed, and that it is more the GIS implementation itself that may be custom-designed for an organization. Hence, the GIS requirements and blueprinting is the value and cost saving aspect in the GIS deployment.

What typically goes beyond a GIS is a spatial data infrastructure, a concept that has no such restrictive boundaries. To be able to integrate the various data, information, systems and infrastructure, the LEADing Practice GIS reference content is both agnostic and vendor neutral, designed to standardize, integrate, tailor and implement multiple data, information, systems and infrastructure by any organization (e.g. government, agency, department and/or enterprise), both large and small, regardless of its various frameworks, methods, products/services or activities.

<u>The LEADing Practice GIS artefacts are developed in the following ways:</u>
*Research and analyze various GIS concepts and identify what works, again and again (best practice), and what are unique practices applied by leading organizations (leading practices).
*Identify common and repeatable patterns for creating interactive queries (user-created searches), analyse spatial information, edit data in maps and present the results (this provides the basis for the GIS reference content).
*Develop the GIS Reference Content that increase the level of re-usability and replication.
*Build Geographic Information System accelerators within the standards, enabling to adopt and reproduce the best practices and leading practices.

We realize that organizations apply various GIS concepts, therefore we have ensured that our GIS standards have an integrated and standardized concept. Based on what works very good, we have developed GIS reference content that has a structured Way of Thinking, Way of Working, Way of Modelling, Way of Implementing and Way of Governance with full semantic relations between information and data objects, meta models (object groups, meta objects), architecture rules, artefacts (maps, matrices and models) and accelerators (content).

All together describing the set of procedures an organization needs to follow in order to replicate what works good around geographic concepts, GIS requirement gathering, GIS blueprinting, the GIS application mapping and modelling as well as the data and information integration concepts.

Below are some examples of the Geographic Information System Reference Content:
{|class="wikitable" style="width:100%;border:0px;" |
|class="thead" style="background-color:rgb(195, 217, 255);width: 50%;text-align:left;" |
'''Standard/Artefact'''
|class="thead" style="background-color:rgb(195, 217, 255);width: 30%;text-align:left;" |
'''Reference Content'''
|class="thead" style="background-color:rgb(195, 217, 255);width: 20%;text-align:left;" |
'''ID #'''
|-
|[[Media:Government-GIS-Way-of-Thinking.pdf|Architecture GIS Modelling - Way of Thinking]]
|GIS Reference Content
|LEAD-ES30005EM
|-
|[[Media:The-LEADing-Practice-GIS-Structural-Way.pdf|Architecture GIS Modelling - Structural Way]]
|GIS Reference Content
|LEAD-ES30005EM
|-
|GIS Portfolio Management
|Portfolio Management Reference Content
|LEAD-ES10019AL
|-
|[[Media:The-GIS-Architectural-Alignment-Model.pdf|GIS Architectural Alignment Model]]
|Alignment & Unity Reference Content
|LEAD-ES60001AL
|-
|GIS Categorization & Classifying Management
|Categorization & Classifying Reference Content
|LEAD-ES30007ES
|-
|[[Media:Government-GIS-Strategy-Goal-Tasks.pdf|GIS Business Architecture Tasks]]
|Business Architecture Reference Content
|LEAD-ES40002PGBCPSI
|-
|GIS Requirement Management
|Enterprise Requirement Reference Content
|LEAD-ES20003PG
|-
|[[Media:GIS-Strategy-Goal-Templates.pdf|GIS Business Layer - Strategy Artefacts]]
|Business Architecture Reference Content
|LEAD-ES40002PGBCPSI
|-
|GIS Stakeholder Model
|Stakeholder Reference Content
|LEAD-ES20002EX
|-
|GIS Operating Model
|Operating Model Reference Content
|LEAD-ES20010BC
|-
|GIS Service-Oriented Model
|Service Model Reference Content
|LEAD-ES20008BCBS
|-
|[[Media:Government-GIS-Application-Architecture-Artifacts.pdf|GIS Application Architecture Artefacts]]
|Application Architecture Reference Content
|LEAD-ES40006SAID
|-
|[[Media:GIS-Application-Map.pdf|Example of a GIS Application Map]]
|Application Reference Content
|LEAD-ES50011SAIDBCBP
|-
|[[Media:Government-GIS-Way-of-Modelling-Tasks.pdf|GIS Data Architecture Tasks]]
|Data Reference Content
|LEAD-ES50016DISABC
|-
|[[Media:GIS-Data-Map.pdf|Example of a GIS Data Map]]
|Data Reference Content
|LEAD-ES50016DISABC
|-
|GIS Channel Management
|Channel Reference Content
|LEAD-ES20016AL
|-
|[[Media:Government-GIS-Platform-Architecture-Artifacts.pdf|Example of GIS Platform Architecture Artefacts]]
|Platform Architecture Reference Content
|LEAD-ES40009PL
|-
|[[Media:GIS-Platform-Map.pdf|Example of a GIS Platform Map]]
|Platform Architecture Reference Content
|LEAD-ES40009PL
|-
|[[Media:GIS-Infrastructure-Rule-Matrix.pdf|Example of a GIS Infrastructure Rule Matrix]]
|Infrastructure Architecture Reference Content
|LEAD-ES40010IL
|-
|[[Media:Government-GIS-Way-of-Implementation.pdf|GIS - Way of Implementation (description)]]
|Implementation Reference Content
|LEAD-ES50023AL
|-
|[[Media:Government-GIS-Structural-Way-of-Implementation.pdf|GIS - Way of Implementation (overview)]]
|Implementation Reference Content
|LEAD-ES50023AL
|-
|[[Media:Government-GIS-Way-of-Governance.pdf|GIS - Way of Governance (description)]]
|Governance Reference Content
|LEAD-ES10018GO
|-
|[[Media:Government-GIS-Structural-Way-of-Governance.pdf|GIS - Way of Governance (overview)]]
|Governance Reference Content
|LEAD-ES10018GO
|-
|GIS Agile Concept
|Agile Reference Content
|LEAD-ES30006ES
|-
|[[Media:LEAD-GIS-Lifecycle.pdf|GIS Lifecycle]]
|Lifecycle Management Reference Content
|LEAD-ES30002AL
|}

[[Category: Geographical Information System]]

LEAD Reference Content:Main

2019-01-15T08:50:13Z

Admin:

{{DISPLAYTITLE: Solution Topic}}
Number of articles in '''LEAD REFERENCE CONTENT''': {{NUMBEROFARTICLES}}

SMART City KM:Main

2019-01-15T08:49:37Z

Admin:

{{DISPLAYTITLE: FLSMIDTH KM}}
Number of articles in '''FLSMIDTH KM''': {{NUMBEROFARTICLES}}

LEAD Reference Content:Maturity Reference Content

2019-01-14T13:26:46Z

Admin: Created page with "{{DISPLAYTITLE:Maturity Reference Content}} = Maturity Reference Content = In order for organizations to perform well in a global competitive world, it is important to identif..."

{{DISPLAYTITLE:Maturity Reference Content}}
= Maturity Reference Content =
In order for organizations to perform well in a global competitive world, it is important to identify the competitive advantages that they can benefit from. Models to assess status and identify improvement opportunities, and in particular maturity models, that can help organizations assessing their current competencies in a structured way to implement changes and improvements, has become essential.

A maturity model can be described as a structured collection of elements that describe certain aspects of maturity in an organization. A maturity model may provide, for example:

*a place to start;
*the benefit of a community’s prior experiences;
*a common language and a shared vision;
*a framework for prioritizing actions; and
*a way to define what improvement means for your organization.

A maturity model can also be used as a benchmark for comparison and as an aid to understanding.

There are a lot of different maturity approaches on the market, the most known is CMM and CMMI, however the narrow focus makes these maturity models and approaches limited to real essential architecture and business improvement (e.g. cross business effectiveness and efficiency). In 2009, four universities therefore joined their combined forces to further innovate and develop the maturity models. These four Universities were a part of the Global University Alliance which consists of more than 900 universities. Out of all these universities, four Universities (both IT Universities and Business Schools) dedicated their time and resources in three different countries with vested research interest in business process management, strategy modelling, economics, business modelling, value management, performance management, service aspects, information and technology modelling. They brought together a rich blend of both academic and industry experience to contribute to a maturing field in Business and IT. The research and development team was lead by Mark von Rosing (Copenhagen Business School and IT University, Denmark), Siavash Moshiri (Sheffield Business School, United Kingdom) and Karin Gräslund (Wiesbaden Business School, Germany).

The maturity model development had the following focus:
*Practical as well as academic research.
*Best practice from different Industry leaders - to be a foundation of best practice standardization.
*Competency development maturity models where a company can focus not only on capabilities but on competencies (capabilities and resources).
*Integration of different maturity model.
*Cross-disciplinary integration of Enterprise Modelling concepts e.g. business model, all value aspects, services, process, information, applications, data, platforms, infrastructure, cloud as well as for transformation and innovation modelling.
*Modelling from As-Is and To-Be development and the identification of Core Competitive and Core Differentiated areas as well as value areas/drivers.
*Effective use of its maturities as they are rated with their Revenue and Cost: High, Medium or Low. To ensure the cost to achieve a higher maturity level would not exceed the possible gain. This may effectively “blind” an organization to the most effective use of its capabilities and resources.

During 2010, more people from the industry joined, among these were development members who work for SAP, IBM, Danish Defense, Government of Canada, Artos Origin, and The Open Group (who develops TOGAF) gave input, feedback and QA to build the cross integrated maturity models, some of these with more business focus while others with more application or technology focus.

The LEADing Practice Maturity Reference Content consist today of the following:

#[[#|Business Model Maturity]]
#[[#|Process Maturity]]
#[[#|Value Maturity]]
#[[#|Service Maturity]]
#[[#|Cloud Maturity]]
#[[#|Information Maturity]]
#[[#|Application Maturity]]
#[[#|Data Maturity]]
#[[#|Platform Maturity]]
#[[#|Infrastructure Maturity]]

[[File:POSTER-LEAD-Maturity-Reference-Method.png|frame|center|900px|link=http://{{SERVERNAME}}/images/c/cd/POSTER-LEAD-Maturity-Reference-Method.png|LEADing Practice Maturity Reference Content poster]]

[[Category: Maturity Assessment]]

LEAD Reference Content:Requirement Modelling Reference Content

2019-01-14T13:20:42Z

Admin: Created page with "{{DISPLAYTITLE: Requirement Modelling Reference Content}} = Requirement Modelling Reference Content = The LEADing Practice Requirement Reference Content provides requirement o..."

{{DISPLAYTITLE: Requirement Modelling Reference Content}}
= Requirement Modelling Reference Content =
The LEADing Practice Requirement Reference Content provides requirement ontology with its requirement description, specific requirement semantic relations and correlations. It is based on a collection of best and leading practice around how to work with requirements within enterprise modelling, enterprise engineering and enterprise architecture disciplines.

The Requirement Reference Content is therefore and essential part for any practitioner working with and around requirement aspects. It provides a structural way of thinking, working, modelling, implementation and governance around requirement definitions, and how requirements are applied within business functions, services, processes as well as applications.

The Requirement Reference Content also provides an overview of the key requirement aspects of the organisation and how they relate to the various business aspects, e.g. organizational construct, competencies, roles, resources, objects, rules, compliance, channel, media as well as reporting. The Requirement Reference Content therefore provides a way of analysing, appraising, approximating, assessing and capturing requirement related objects to enable innovation and transformation.

'''Documentat''': [[Media:LEADing Practice Requirement Modelling REFERENCE CONTENT-LEAD-ES20012BC.pdf|Download the Requirement Modelling Reference Content document]]

[[Category: Requirement Management]]

LEAD Reference Content:Strategy Management Reference Content

2019-01-14T13:19:27Z

Admin: Created page with "{{DISPLAYTITLE:Strategy Management Reference Content}} = Strategy Management Reference Content = Our Strategy Development & Execution patterns has been packaged into a repeata..."

{{DISPLAYTITLE:Strategy Management Reference Content}}
= Strategy Management Reference Content =
Our Strategy Development & Execution patterns has been packaged into a repeatable concept, and are supported by leading practices, industry practices and best practices reference content. Each standard is a unique set of documented patterns with descriptions, how to guide, decision points, modelling concepts and artefacts that are required to achieve the desired result. Like a recipe, where you can follow a sequence of simple steps to achieve the wished result.
*Disruptive Forces & Trends which influence strategy
*Strategy Development & Execution Capabilities
*Measures/KPIs relevant to strategy
*The use of Strategy techniques
*Strategy & Integrated Planning Model
*Strategy and the relationship to Revenue Model
*The relationship between Strategy and Value Model
*Strategy and the important of rethinking the Service Model
*Strategy and Performance Model
*Strategy relevant to the Cost Model
*How to redirect the Business Model with ones strategy
*Gain insight into an integrated Strategy Framework
*Have a complete set of Strategy Artefacts

'''Documentation''': [[Media:LEADing Practice Strategy Management REFERENCE CONTENT-LEAD-ES20012BC.pdf|Download the Strategy Management Reference Content document]]

[[Category: Strategy]]

LEAD Reference Content:Performance Modelling Reference Content

2019-01-14T13:16:33Z

Admin: Created page with "{{DISPLAYTITLE: Performance Modelling Reference Content}} = Performance Modelling Reference Content = The LEADing Practice Performance Reference Content provides performance o..."

{{DISPLAYTITLE: Performance Modelling Reference Content}}
= Performance Modelling Reference Content =
The LEADing Practice Performance Reference Content provides performance ontology with its performance description, specific performance semantic relations and correlations. It is based on a collection of best and leading practice around how to work with performance within enterprise modelling, enterprise engineering and enterprise architecture disciplines.

The Performance Reference Content is therefore and essential part for any practitioner working with and around performance aspects. It provides a structural way of thinking, working, modelling, implementation and governance around performance definitions, and how performance is applied within forces & drivers, processes, services and reporting The Performance Reference Content also provides an overview of the key performance aspects of the organisation and how they relate to the various business aspects e.g. owner, requirement, organizational construct, competencies, services and process.

The Performance Reference Content provides a way of analysing, appraising, approximating, assessing and capturing performance related objects to enable innovation and transformation.

'''Documentation''': [[Media:LEADing Practice Performance Modelling REFERENCE CONTENT-LEAD-ES20012BC.pdf|Download the Performance Modelling Reference Content document]]

[[Category: Performance Management]]

LEAD Reference Content:Owner Modelling Reference Content

2019-01-14T13:14:58Z

Admin:

{{DISPLAYTITLE: Owner Modelling Reference Content}}
= Owner Modelling Reference Content =
The LEADing Practice Owner Reference Content provides owner ontology with its owner description, specific owner semantic relations and correlations. It is based on a collection of best and leading practice around how to work with owners within enterprise management, enterprise management, enterprise modelling, enterprise engineering, enterprise architecture as well as in the various IT disciplines as well as in the various IT disciplines.

The Owner Reference Content is therefore an essential part for any practitioner working with and around owner aspects. It provides a structural way of thinking, working, modelling, implementation and governance around owner definitions and how owners are applied within business functions, process, services as well as applications.

The Owner Reference Content also provides an overview of the key owner aspects of the organisation and how they relate to the various business aspects e.g. goals (e.g. business, application, technology), organizational construct, business area, business group, business functions the services they provide process as well as associated cost.

'''Documentation''': [[Media:LEADing Practice Owner Modelling REFERENCE CONTENT-LEAD-ES20012BC.pdf|Download the Owner Modelling Reference Content document]]

[[Category: Owner Modelling]]

LEAD Reference Content:Owner Modelling Reference Content

2019-01-14T13:14:41Z

Admin: Created page with "{{DISPLAYTITLE: Owner Modelling Reference Content}} = Owner Modelling Reference Content = The LEADing Practice Owner Reference Content provides owner ontology with its owner d..."

{{DISPLAYTITLE: Owner Modelling Reference Content}}
= Owner Modelling Reference Content =
The LEADing Practice Owner Reference Content provides owner ontology with its owner description, specific owner semantic relations and correlations. It is based on a collection of best and leading practice around how to work with owners within enterprise management, enterprise management, enterprise modelling, enterprise engineering, enterprise architecture as well as in the various IT disciplines as well as in the various IT disciplines.

The Owner Reference Content is therefore an essential part for any practitioner working with and around owner aspects. It provides a structural way of thinking, working, modelling, implementation and governance around owner definitions and how owners are applied within business functions, process, services as well as applications.

The Owner Reference Content also provides an overview of the key owner aspects of the organisation and how they relate to the various business aspects e.g. goals (e.g. business, application, technology), organizational construct, business area, business group, business functions the services they provide process as well as associated cost.

'''Documentat''': [[Media:LEADing Practice Owner Modelling REFERENCE CONTENT-LEAD-ES20012BC.pdf|Download the Owner Modelling Reference Content document]]

[[Category: Owner Modelling]]

LEAD Reference Content:LEAD Enterprise Architecture Reference Content

2019-01-14T13:12:52Z

Admin:

{{DISPLAYTITLE:LEAD Enterprise Architecture Reference Content}}
= LEAD Enterprise Architecture Reference Content =
This document provides a summary of the LEAD Enterprise Architecture Body of Knowledge, setting out the concepts, terms, and descriptions as well as a description of our structured way of thinking, working, modelling, implementation, and governance.

The key feature of this document is that it captures the LEAD Enterprise Architecture ontology for each of the layers, showing the objects of each layer.

Through the specification of each LEADing Practice Objects, the Glossary captures the meaning, or way to think about the objects.

[[Category: Enterprise Architecture]]

LEAD Reference Content:LEAD Enterprise Architecture Reference Content

2019-01-14T13:12:31Z

Admin: Created page with "{{DISPLAYTITLE:LEAD Enterprise Architecture Reference Content}} = LEAD Enterprise Architecture Reference Content = This document provides a summary of the LEAD Enterprise Arch..."

LEAD Reference Content:Measurement & Reporting Modelling Reference Content

2019-01-14T13:09:56Z

Admin: Created page with "{{DISPLAYTITLE: Measurement & Reporting Modelling Reference Content}} = Measurement & Reporting Modelling Reference Content = The LEADing Practice Measurement & Reporting Refe..."

{{DISPLAYTITLE: Measurement & Reporting Modelling Reference Content}}
= Measurement & Reporting Modelling Reference Content =
The LEADing Practice Measurement & Reporting Reference Content provides measurement & reporting (hereafter: M&R) ontology with its specific M&R descriptions, semantic relations and correlations. It is based on a collection of best and leading practice around how to work with measurements/reporting within enterprise modelling, enterprise engineering and enterprise architecture disciplines.

The Measurement & Reporting Modelling Reference Content is therefore and essential part for any practitioner working with and around M&R aspects. It provides a structural way of thinking, working, modelling, implementation and governance around M&R definitions, and how M&R is applied within business functions, services, processes as well as applications.

The Measurement & Reporting Modelling Reference Content also provides an overview of the key M&R aspects of the organisation and how they relate to the various business aspects, e.g. owners, competencies, processes, services, as well as requirements. The M&R Reference Content therefore provides a way of analyzing, appraising, approximating, assessing, and capturing M&R related objects to enable innovation and transformation.

'''Documentat''': [[Media:LEADing Practice Measurement & Reporting Modelling REFERENCE CONTENT-LEAD-ES20012BC.pdf|Download the Measurement & Reporting Modelling Reference Content document]]

[[Category: Measurements (KPIs)]]
[[Category: Reporting]]

LEAD Reference Content:Operating Modelling Reference Content

2019-01-14T13:06:42Z

Admin: Created page with "{{DISPLAYTITLE: Operating Modelling Reference Content}} = Operating Modelling Reference Content = The LEADing Practice Operating Modelling Reference Content provides operating..."

{{DISPLAYTITLE: Operating Modelling Reference Content}}
= Operating Modelling Reference Content =
The LEADing Practice Operating Modelling Reference Content provides operating ontology with its specific operating descriptions, semantic relations and correlations. It is based on a collection of best and leading practice around how to work with operating around enterprise modelling, enterprise engineering and enterprise architecture disciplines.

The Operating Modelling Reference Content is therefore and essential part for any practitioner working with and around operating aspects. It provides a structural way of thinking, working, modelling, implementation and governance around operating definitions and how operating is applied within business functions, roles, competencies, process and cost.

The Operating Modelling Reference Content also provides an overview of the key operating aspects of the organisation and how they relate to the various business aspects e.g. goal, requirement, owner, service, rules and compliance. The Operating Reference Content therefore provides a way of analysing, appraising, approximating, assessing and capturing operating related objects to enable innovation and transformation.

'''Documentat''': [[Media:LEADing Practice Operating Modelling REFERENCE CONTENT-LEAD-ES20012BC.pdf|Download the Operating Modelling Reference Content document]]

[[Category: Operating Model]]

Category:Forces & Drivers

2019-01-14T13:03:42Z

Admin: Created page with "{{PAGESINCATEGORY: Forces & Drivers}}"

LEAD Reference Content:Forces & Drivers Reference Content

2019-01-14T13:01:56Z

Admin:

{{DISPLAYTITLE:Drivers & Forces (external/internal) Modelling Reference Content}}
= Forces & Drivers Reference Content =
'''Description:''' The Drivers & Forces Reference Content is a part of the Enterprise Modelling Standards and has the purpose of capturing the internal and external forces as well as drivers. The Drivers & Forces Reference Content has either an external or internal driver and/or force and is often referred to as a condition that influences (forces) or motivates (drives) the organization to define its direction (e.g. strategy, objectives and goals).

'''Artefact:''' The Drivers & Forces Reference Content has 3 types of artefacts, in terms of both maps, matrices and models that capture the above mentioned meta objects, which are instrumental and an essential part of the enterprise modelling, engineering and architecture. Each of these are based on a specific view, with particular stakeholder concern to enable value identification, creation, and realization in achieving the linked Value, Performance, Cost or Revenue Driver identified. Fully integrated and standardized application modelling and architecture artefacts enables the subject matter expert/practitioner to work and model with the Drivers & Forces meta objects throughout all the architectural layers (business, application and technology) and this is one of the strengths of the Enterprise Modelling Standards. Not only are the Drivers & Forces objects governed by its connection modelling rules, but how and where the artefacts interlink and share common objects is defined and standardized.

The Drivers & Forces artefacts are either maps, matrices or models. The maps are often in the form of a list and is a representation of the decomposed Drivers & Forces object:
*Identify and sort the forces (internal or external).
*Identify and catalog the drivers (internal or external).

The Drivers & Forces matrices are the continuity of and interconnection between a map (a representation of decomposed objects) and a model (a representation of interconnected and related objects) and is used to:
*Select and catalog the external drivers that have an impact and/or influence upon the business.
*Prioritize (based on level of impact, severity and/or urgency) the forces (internal or external) that might affect the business.

Internal and external Drivers & Forces can among others be categorized into:
*Value Drivers
*Performance Drivers
*Cost Drivers
*Revenue Driver

The Drivers & Forces maps, matrices and models are therefore used in the decomposition and composition work within and throughout the layers. The artefacts shows which objects are within each artefact, thereby specifying if it is a map, matrix or model. It furthermore shows where the object of one artefact can be reused in another artefact.

'''Usage:''' Once the external or internal Drivers & Forces have been specified, they are then linked and connected to the other objects. This association enables them to tie to the areas where the Drivers & Forces (external or internal) have a connection and/or influence. A list of meta objects the Drivers & Forces (external or internal) relate to are:
*Vision & Mission
*Strategy (Strategic Business Objective)
*Goal (e.g. business, application, etc.)
*Objective (Critical Success Factor, Plan, Forecast, Budget)
*Value Driver
*Performance Driver
*Business Area
*Business Group
*Competency Type (Diff, Comp, Non-Core)
*Business Owner
*Service Area
*Service Group
*Business Service
*Service Owner
*Process Area (categorization)
*Process Group (categorization)
*Business Process
*Process Owner
*Application/System Owner
*Data Owner
*Infrastructure Owner

'''Roles involved with the Drivers & Forces artefacts and meta objects:'''
<br/>
{|class="wikitable" style="width:100%;border:0px;" |
|style="background-color:#1497d5;color:#ffffff;width: 33%;text-align:left;border:0px;" |
'''ENTERPRISE MODELLERS'''
|style="background-color:#1497d5;color:#ffffff;width: 33%;text-align:left;border:0px;" |
'''ENTERPRISE ENGINEERS'''
|style="background-color:#1497d5;color:#ffffff;width: 33%;text-align:left;border:0px;" |
'''ENTERPRISE ARCHITECTS'''
|-
|style="background-color:rgb(235, 236, 236);border:0px;" |
Business Analyst
|style="background-color:rgb(235, 236, 236);border:0px;" |
Value Engineer
|style="background-color:rgb(235, 236, 236);border:0px;" |
Business Architect
|-
|style="background-color:rgb(235, 236, 236);border:0px;" |
Value eXpert
|style="background-color:rgb(235, 236, 236);border:0px;" |
Change Engineer
|style="background-color:rgb(235, 236, 236);border:0px;" |
Enterprise Architect
|-
|style="background-color:rgb(235, 236, 236);border:0px;" |
Transformation eXpert
|style="background-color:rgb(235, 236, 236);border:0px;" |
 
|style="background-color:rgb(235, 236, 236);border:0px;" |
Value Architect
|}
<br/>
'''Stakeholders involved with the Drivers & Forces artefacts and meta objects:'''
*Top Management: CEO/President (External & Internal Drivers)
*High Management: CxO(*)/Vice President/Senior Executive (External & Internal Drivers)
*High/Middle Management: Director/Senior Manager (Internal Drivers)
*Middle Management: Manager/Senior (Team) Leader (Internal Drivers)
*Lower Management: Team/Group Leaders (Internal Drivers)
*Operations: User (Internal Drivers)

(*): Chief Executive Officer, Chief Channel Officer, Chief Financial Officer, Chief Information Officer, Chief Risk & Security Officer, Chief HR Office, Chief Marketing & Sales Officer, Chief R&D Officer, Chief Procurement Officer, Chief Strategy Officer, Chief Buss. Dev. Officer, Chief Technology Officer, Chief Environment & Health Officer.

[[Category: Forces & Drivers]]

LEAD Reference Content:Forces & Drivers Reference Content

2019-01-14T13:01:34Z

Admin: Created page with "{{DISPLAYTITLE:Drivers & Forces (external/internal) Modelling Reference Content}} '''Description:''' The Drivers & Forces Reference Content is a part of the Enterprise Modell..."

{{DISPLAYTITLE:Drivers & Forces (external/internal) Modelling Reference Content}}

'''Description:''' The Drivers & Forces Reference Content is a part of the Enterprise Modelling Standards and has the purpose of capturing the internal and external forces as well as drivers. The Drivers & Forces Reference Content has either an external or internal driver and/or force and is often referred to as a condition that influences (forces) or motivates (drives) the organization to define its direction (e.g. strategy, objectives and goals).

'''Artefact:''' The Drivers & Forces Reference Content has 3 types of artefacts, in terms of both maps, matrices and models that capture the above mentioned meta objects, which are instrumental and an essential part of the enterprise modelling, engineering and architecture. Each of these are based on a specific view, with particular stakeholder concern to enable value identification, creation, and realization in achieving the linked Value, Performance, Cost or Revenue Driver identified. Fully integrated and standardized application modelling and architecture artefacts enables the subject matter expert/practitioner to work and model with the Drivers & Forces meta objects throughout all the architectural layers (business, application and technology) and this is one of the strengths of the Enterprise Modelling Standards. Not only are the Drivers & Forces objects governed by its connection modelling rules, but how and where the artefacts interlink and share common objects is defined and standardized.

The Drivers & Forces artefacts are either maps, matrices or models. The maps are often in the form of a list and is a representation of the decomposed Drivers & Forces object:
*Identify and sort the forces (internal or external).
*Identify and catalog the drivers (internal or external).

The Drivers & Forces matrices are the continuity of and interconnection between a map (a representation of decomposed objects) and a model (a representation of interconnected and related objects) and is used to:
*Select and catalog the external drivers that have an impact and/or influence upon the business.
*Prioritize (based on level of impact, severity and/or urgency) the forces (internal or external) that might affect the business.

Internal and external Drivers & Forces can among others be categorized into:
*Value Drivers
*Performance Drivers
*Cost Drivers
*Revenue Driver

The Drivers & Forces maps, matrices and models are therefore used in the decomposition and composition work within and throughout the layers. The artefacts shows which objects are within each artefact, thereby specifying if it is a map, matrix or model. It furthermore shows where the object of one artefact can be reused in another artefact.

'''Usage:''' Once the external or internal Drivers & Forces have been specified, they are then linked and connected to the other objects. This association enables them to tie to the areas where the Drivers & Forces (external or internal) have a connection and/or influence. A list of meta objects the Drivers & Forces (external or internal) relate to are:
*Vision & Mission
*Strategy (Strategic Business Objective)
*Goal (e.g. business, application, etc.)
*Objective (Critical Success Factor, Plan, Forecast, Budget)
*Value Driver
*Performance Driver
*Business Area
*Business Group
*Competency Type (Diff, Comp, Non-Core)
*Business Owner
*Service Area
*Service Group
*Business Service
*Service Owner
*Process Area (categorization)
*Process Group (categorization)
*Business Process
*Process Owner
*Application/System Owner
*Data Owner
*Infrastructure Owner

'''Roles involved with the Drivers & Forces artefacts and meta objects:'''
<br/>
{|class="wikitable" style="width:100%;border:0px;" |
|style="background-color:#1497d5;color:#ffffff;width: 33%;text-align:left;border:0px;" |
'''ENTERPRISE MODELLERS'''
|style="background-color:#1497d5;color:#ffffff;width: 33%;text-align:left;border:0px;" |
'''ENTERPRISE ENGINEERS'''
|style="background-color:#1497d5;color:#ffffff;width: 33%;text-align:left;border:0px;" |
'''ENTERPRISE ARCHITECTS'''
|-
|style="background-color:rgb(235, 236, 236);border:0px;" |
Business Analyst
|style="background-color:rgb(235, 236, 236);border:0px;" |
Value Engineer
|style="background-color:rgb(235, 236, 236);border:0px;" |
Business Architect
|-
|style="background-color:rgb(235, 236, 236);border:0px;" |
Value eXpert
|style="background-color:rgb(235, 236, 236);border:0px;" |
Change Engineer
|style="background-color:rgb(235, 236, 236);border:0px;" |
Enterprise Architect
|-
|style="background-color:rgb(235, 236, 236);border:0px;" |
Transformation eXpert
|style="background-color:rgb(235, 236, 236);border:0px;" |
 
|style="background-color:rgb(235, 236, 236);border:0px;" |
Value Architect
|}
<br/>
'''Stakeholders involved with the Drivers & Forces artefacts and meta objects:'''
*Top Management: CEO/President (External & Internal Drivers)
*High Management: CxO(*)/Vice President/Senior Executive (External & Internal Drivers)
*High/Middle Management: Director/Senior Manager (Internal Drivers)
*Middle Management: Manager/Senior (Team) Leader (Internal Drivers)
*Lower Management: Team/Group Leaders (Internal Drivers)
*Operations: User (Internal Drivers)

(*): Chief Executive Officer, Chief Channel Officer, Chief Financial Officer, Chief Information Officer, Chief Risk & Security Officer, Chief HR Office, Chief Marketing & Sales Officer, Chief R&D Officer, Chief Procurement Officer, Chief Strategy Officer, Chief Buss. Dev. Officer, Chief Technology Officer, Chief Environment & Health Officer.

[[Category: Forces & Drivers]]

LEAD Reference Content:Value Model Reference Content

2019-01-14T12:53:47Z

Admin:

{{DISPLAYTITLE:Value Model Reference Content}}
= Value Model Reference Content =
The LEADing Practice Value Model Reference Content is the result of research, industry expert and academic consensus and agreement.

The Value Way of Modelling is the means by which various practitioners working with value aspects follow in order to define the modelling principles to make an objective assessment of the possible. It provides a uniform and formal description of the models where the value objects and artefacts within one or more different types of models can be portrayed. The value models are a representation that graphically represent and shows the value relationship and the interconnection of specific composed objects and complies with a specific set of rules for what the graphical components mean, and how they are connected to the rest of the business. The key ideal of a value model is that it is a representation, an illustration, of a composition of information intended to represent an aspect of an enterprise (e.g. business, information and/or technology), using a specific set of rules, which express a logic or grammar.

Each practitioner working with value aspects has to be able to translate the “Way of Working” into a “Way of Modelling”, which for the most part include the following:
*<b>Expressiveness:</b> the degree to which a given modelling technique is able to denote the models of any number and kinds of layered domains (business, application and technology).
*<b>Arbitrariness:</b> the degree of freedom one has when decomposing and composing different models on the same domain.
*<b>Suitability:</b> the degree to which a given modelling technique is specifically tailored for a specific kind of wanted output/result.
*<b>Comprehensibility:</b> the ease of how the way of working and way of modelling techniques are understood by participants.
*<b>Coherence:</b> the degree to which the individual sub-models of a way of modelling constitute a whole.
*<b>Completeness:</b> the degree to which all-necessary concepts of the application domains are represented in the way of modelling.
*<b>Efficiency:</b> the degree to which the modelling steps (e.g. LEADing Practice steps) uses resources such as time and people.
*<b>Effectiveness:</b> the degree to which the modelling principles achieve its goals.
*<b>Audit:</b> the degree to which the end results of the models achieve its goals.

Based on already acquired information from the value maps and/or a value matrices, a value model is usually crafted to enable complex information to be used in different disciplines and within this to be communicated more easily to stakeholders, management and leadership. The fully integrated and standardized value artefacts enables the practitioner to work and model with the value objects throughout all the aspects of the enterprise (business, application and technology).

Not only are the objects governed by its semantic relations and connection, also the specified value modelling rules and tasks, which ensure how and where the value artefacts interlink and share common value objects is defined and standardized.

Below are some examples of the Value Model Reference Content:
{|class="wikitable" style="width:100%;border:0px;" |
|class="thead" style="background-color:rgb(195, 217, 255);width: 60%;text-align:left;" |
'''Standard/Artefact'''
|style="background-color:rgb(195, 217, 255);width: 25%;text-align:left;" |'''Reference Content'''
|style="background-color:rgb(195, 217, 255);width: 15%;text-align:left;" |'''ID #'''
|-
|[[Media:Value-Model-Reference-Content-The-Value-Planning-Creation-Realization-Cycle.pdf|The Value Planning & Creation & Realization Cycle]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|-
|[[Media:Value-Model-Reference-Content-Value-Driver-Generic-Value-Driver-Tree.pdf|Example of a Generic Value Driver Tree]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|-
|[[Media:Value-Model-Reference-Content-Value-Driver-Tree-for-a-Petroleum-Marketing-Company.pdf|Example Value Driver Tree for a Petroleum Marketing Company]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|-
|[[Media:Value-Model-Reference-Content-Value-Driver-Tree-for-a-Public-Agency.pdf|Example Value Driver Tree for a Public Agency]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|-
|[[Media:Value-Model-Reference-Content-Value-Lifecycle-Phases-Steps-SAP.pdf|Value Lifecycle Phases & Steps (SAP)]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|-
|[[Media:Value-Model-Reference-Content-Value-driven-Process-Modelling.pdf|Value-driven Process Modelling]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|-
|[[Media:Value-Model-Reference-Content-12-Characteristics-of-Effective-Performance-Drivers.pdf|12 Characteristics of Effective Performance Drivers]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|-
|[[Media:LEAD-Value-Reference-Framework-Enterprise-Value-Tree.pdf|Value Reference Content Poster]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|}

[[Category: Value Management]]

LEAD Reference Content:Value Model Reference Content

2019-01-14T12:53:16Z

Admin: Created page with "{{DISPLAYTITLE:Value Model Reference Content (ID# LEAD-ES20007BCPG)}} = Value Model Reference Content = The LEADing Practice Value Model Reference Content is the result of res..."

{{DISPLAYTITLE:Value Model Reference Content (ID# LEAD-ES20007BCPG)}}
= Value Model Reference Content =
The LEADing Practice Value Model Reference Content is the result of research, industry expert and academic consensus and agreement.

The Value Way of Modelling is the means by which various practitioners working with value aspects follow in order to define the modelling principles to make an objective assessment of the possible. It provides a uniform and formal description of the models where the value objects and artefacts within one or more different types of models can be portrayed. The value models are a representation that graphically represent and shows the value relationship and the interconnection of specific composed objects and complies with a specific set of rules for what the graphical components mean, and how they are connected to the rest of the business. The key ideal of a value model is that it is a representation, an illustration, of a composition of information intended to represent an aspect of an enterprise (e.g. business, information and/or technology), using a specific set of rules, which express a logic or grammar.

Each practitioner working with value aspects has to be able to translate the “Way of Working” into a “Way of Modelling”, which for the most part include the following:
*<b>Expressiveness:</b> the degree to which a given modelling technique is able to denote the models of any number and kinds of layered domains (business, application and technology).
*<b>Arbitrariness:</b> the degree of freedom one has when decomposing and composing different models on the same domain.
*<b>Suitability:</b> the degree to which a given modelling technique is specifically tailored for a specific kind of wanted output/result.
*<b>Comprehensibility:</b> the ease of how the way of working and way of modelling techniques are understood by participants.
*<b>Coherence:</b> the degree to which the individual sub-models of a way of modelling constitute a whole.
*<b>Completeness:</b> the degree to which all-necessary concepts of the application domains are represented in the way of modelling.
*<b>Efficiency:</b> the degree to which the modelling steps (e.g. LEADing Practice steps) uses resources such as time and people.
*<b>Effectiveness:</b> the degree to which the modelling principles achieve its goals.
*<b>Audit:</b> the degree to which the end results of the models achieve its goals.

Based on already acquired information from the value maps and/or a value matrices, a value model is usually crafted to enable complex information to be used in different disciplines and within this to be communicated more easily to stakeholders, management and leadership. The fully integrated and standardized value artefacts enables the practitioner to work and model with the value objects throughout all the aspects of the enterprise (business, application and technology).

Not only are the objects governed by its semantic relations and connection, also the specified value modelling rules and tasks, which ensure how and where the value artefacts interlink and share common value objects is defined and standardized.

Below are some examples of the Value Model Reference Content:
{|class="wikitable" style="width:100%;border:0px;" |
|class="thead" style="background-color:rgb(195, 217, 255);width: 60%;text-align:left;" |
'''Standard/Artefact'''
|style="background-color:rgb(195, 217, 255);width: 25%;text-align:left;" |'''Reference Content'''
|style="background-color:rgb(195, 217, 255);width: 15%;text-align:left;" |'''ID #'''
|-
|[[Media:Value-Model-Reference-Content-The-Value-Planning-Creation-Realization-Cycle.pdf|The Value Planning & Creation & Realization Cycle]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|-
|[[Media:Value-Model-Reference-Content-Value-Driver-Generic-Value-Driver-Tree.pdf|Example of a Generic Value Driver Tree]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|-
|[[Media:Value-Model-Reference-Content-Value-Driver-Tree-for-a-Petroleum-Marketing-Company.pdf|Example Value Driver Tree for a Petroleum Marketing Company]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|-
|[[Media:Value-Model-Reference-Content-Value-Driver-Tree-for-a-Public-Agency.pdf|Example Value Driver Tree for a Public Agency]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|-
|[[Media:Value-Model-Reference-Content-Value-Lifecycle-Phases-Steps-SAP.pdf|Value Lifecycle Phases & Steps (SAP)]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|-
|[[Media:Value-Model-Reference-Content-Value-driven-Process-Modelling.pdf|Value-driven Process Modelling]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|-
|[[Media:Value-Model-Reference-Content-12-Characteristics-of-Effective-Performance-Drivers.pdf|12 Characteristics of Effective Performance Drivers]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|-
|[[Media:LEAD-Value-Reference-Framework-Enterprise-Value-Tree.pdf|Value Reference Content Poster]]
|Value Model Reference Content
|LEAD-ES20007BCPG
|}

[[Category: Value Management]]

LEAD Reference Content:Call Center Management Reference Content

2019-01-14T12:31:15Z

Admin: Created page with "{{DISPLAYTITLE:Call Center Management Reference Content}} = Call Center Management Reference Content = The LEADing Practice Call Center Reference Content has the purpose to id..."

{{DISPLAYTITLE:Call Center Management Reference Content}}
= Call Center Management Reference Content =
The LEADing Practice Call Center Reference Content has the purpose to identify, develop and tailor call center specific standards and artefacts that are applied in specific and ongoing projects. Some of the standards and artefacts of the reference content are:
*Call Center Competency Map
*Call Center Business Model
*Call Center Service Matrix
*The Top Strategic Business Objectives of a Call Center (SBOs)
*Call Center Strategy Map and Model
*The Critical Success Factors of a Call Center (CSFs)
*Call Center Value Drivers
*The Key Performance Indicators of a Call Center (KPIs)
*Call Center Performance Drivers
*Call Center Process Map
*Example of Call Center Process Model in BPM Notations
*Integrated model of Call Center SBOs, CSFs, KPIs and processes
*Call Center Maturity Model
*Call Center Architecture
*Call Center Architectural Layers
*Call Center Business Architecture
*Call Center Application Architecture
*Call Center Service Architecture flow
*Call Center Technology Architecture

[[Category: Customer Centricity]]