Enterprise Standards:Blueprinting Reference Content - Revision history

Admin at 23:13, 28 October 2015

2015-10-28T23:13:11Z

Admin at 11:04, 3 September 2015

2015-09-03T11:04:52Z

Admin at 10:47, 3 September 2015

2015-09-03T10:47:45Z

Admin at 10:44, 3 September 2015

2015-09-03T10:44:37Z

87.121.100.91: Created page with "Category:Enterprise Information & Technology Standards"

2015-07-13T09:11:42Z

Created page with "Category:Enterprise Information & Technology Standards"

New page

[[Category:Enterprise Information & Technology Standards]]

@@ Line 35: / Line 35: @@
 The LEAD Way of Implementing is not only about combining Enterprise Modelling and Enterprise Architecture principles; it is the approach the LEAD eXpert or architect follows in order apply the way of working and modelling into the physical and thereby the execution and concrete relevant aspects.
-The LEAD Way of Implementing provides a uniform and formal implementation description of the specific LEAD meta objects and artifacts by using decomposition and composition modelling techniques within the different layers (e.g. business, application and technology).
+The LEAD Way of Implementing provides a uniform and formal implementation description of the specific LEAD meta objects and artefacts by using decomposition and composition modelling techniques within the different layers (e.g. business, application and technology).
 Most implementations fall short of transforming the business and creating real value due to the fact that they automate the existing way of working. Thereby actually reinforcing a siloed and ineffective way of automation. Hence, the implementation approach is not only about identifying and minimizing duplication of business functions, roles in terms of employees, process’s, services and many other cost cutting potential. It is in addition about the possibility to totally rethink the business workflow, the service flow, the process flow as well as the measurement and reporting flow. It can fundamentally rethink and transform the organization.
 The LEADing Practice Way of Implementing has been developed as a fully integrated part of any of the frameworks and methods and details a series of steps to be taken in order to produce a wanted and pre-determined result in the areas of the decomposition and composition of the business, application and technology relevant objects. The implementation approach is designed so that you can do a full project implementation e.g. ERP, cloud, service renewal, while applying full integrated enterprise architecture principles as well.

@@ Line 4: / Line 4: @@
 Aligning Business and IT is a challenge, mainly because they have a different scope in terms that they work with something different.
 *'''The scope of business:''' Business strategies and goals define the reason and purpose of the business area and competencies (resource and capabilities). Business competencies deliver the business functions and task to execute the defined goals and objectives. When business competencies deliver these business services, they have activities (business process). Rules are set in place to govern the business function and the services delivered.
 *'''The scope of IT:''' IT is all about systems. Applications can automate one or more processes (business process) which interact with the business objects, information object and data object. An Application is decomposed in one or more application component(s) and functions. An application function defines (a part of) an application service flow (which support the business service flow). Application users, have roles that use the application functionality that call upon information objects. Applications are deployed on platforms that reside within an infrastructure.
 This is not only about identifying and minimizing duplication of; business functions, roles in terms of employees, process's, services and many other cost cutting potential. It is much more about the possibility to totally rethink the business workflow, the service flow, the process flow as well as the measurement and reporting flow. It can fundamentally rethink and transform the organization.
 The LEADing Practice Blueprinting Reference Content structures the practitioner’s way of modelling in the specific areas with a supporting scope, concept, roadmap and conceptual model. The Blueprinting Reference Content is designed so that you can do a full enterprise architecture blueprint with the approach, but you can, however, also do a full ERP blueprint with it as well.
 One can combine it with for example the LEADing Practice Service Reference Content and the LEADing Practice Business Innovation & Transformation Enablement (BITE) Reference Content for enabling business innovation and transformation and do a full ERP blueprinting, design and implementation while at the same time doing a full service renewal and business transformation within the project.
 The LEADing Practice Blueprinting Reference Content is in that perspective a really unique help with critical enterprise modelling aspects:
 *Blueprint the As-Is situation and design the needed To-Be.
 *Identify cost cutting potential in terms of duplication of business functions, services, processes, channels, etc.
@@ Line 34: / Line 26: @@
 *Business dependencies and scenarios that connect the right dots together.
 *Capabilities needed to innovate, change, and efficiently operate against a set of financial indices.
 An example of an overview of LEADing Practice Blueprinting Reference Content is below (for detailed examples and how to apply it to Enterprise Architecture, ERP and/or Transformation, please [[contact_us|contact us]]):
 [[File:LEAD-Blueprinting-Decomposition-Composition-Approach-Layered-Architecture-Roadmap-01.png|frame|center|900px|link=http://{{SERVERNAME}}/images/a/a2/LEAD-Blueprinting-Approach.pdf|An example of a LEADing Practice Blueprinting Reference Content]]
 === Way of Implementing ===
 The LEAD Way of Implementing is not only about combining Enterprise Modelling and Enterprise Architecture principles; it is the approach the LEAD eXpert or architect follows in order apply the way of working and modelling into the physical and thereby the execution and concrete relevant aspects.
 The LEAD Way of Implementing provides a uniform and formal implementation description of the specific LEAD meta objects and artifacts by using decomposition and composition modelling techniques within the different layers (e.g. business, application and technology).
 Most implementations fall short of transforming the business and creating real value due to the fact that they automate the existing way of working. Thereby actually reinforcing a siloed and ineffective way of automation. Hence, the implementation approach is not only about identifying and minimizing duplication of business functions, roles in terms of employees, process’s, services and many other cost cutting potential. It is in addition about the possibility to totally rethink the business workflow, the service flow, the process flow as well as the measurement and reporting flow. It can fundamentally rethink and transform the organization.
 The LEADing Practice Way of Implementing has been developed as a fully integrated part of any of the frameworks and methods and details a series of steps to be taken in order to produce a wanted and pre-determined result in the areas of the decomposition and composition of the business, application and technology relevant objects. The implementation approach is designed so that you can do a full project implementation e.g. ERP, cloud, service renewal, while applying full integrated enterprise architecture principles as well.

← Older revision		Revision as of 10:47, 3 September 2015
Line 36:		Line 36:


−	An example of an overview of LEADing Practice Blueprinting Reference Content is below (for detailed examples and how to apply it to Enterprise Architecture, ERP and/or Transformation, please [[#\|contact us]]):	+	An example of an overview of LEADing Practice Blueprinting Reference Content is below (for detailed examples and how to apply it to Enterprise Architecture, ERP and/or Transformation, please [[contact_us\|contact us]]):

← Older revision		Revision as of 10:44, 3 September 2015
Line 1:		Line 1:
	[[Category:Enterprise Information & Technology Standards]]		[[Category:Enterprise Information & Technology Standards]]
		+	{{DISPLAYTITLE: Blueprinting Reference Content}}
		+
		+
		+	Aligning Business and IT is a challenge, mainly because they have a different scope in terms that they work with something different.
		+
		+
		+	*'''The scope of business:''' Business strategies and goals define the reason and purpose of the business area and competencies (resource and capabilities). Business competencies deliver the business functions and task to execute the defined goals and objectives. When business competencies deliver these business services, they have activities (business process). Rules are set in place to govern the business function and the services delivered.
		+
		+
		+	*'''The scope of IT:''' IT is all about systems. Applications can automate one or more processes (business process) which interact with the business objects, information object and data object. An Application is decomposed in one or more application component(s) and functions. An application function defines (a part of) an application service flow (which support the business service flow). Application users, have roles that use the application functionality that call upon information objects. Applications are deployed on platforms that reside within an infrastructure.
		+
		+
		+	This is not only about identifying and minimizing duplication of; business functions, roles in terms of employees, process's, services and many other cost cutting potential. It is much more about the possibility to totally rethink the business workflow, the service flow, the process flow as well as the measurement and reporting flow. It can fundamentally rethink and transform the organization.
		+
		+
		+	The LEADing Practice Blueprinting Reference Content structures the practitioner’s way of modelling in the specific areas with a supporting scope, concept, roadmap and conceptual model. The Blueprinting Reference Content is designed so that you can do a full enterprise architecture blueprint with the approach, but you can, however, also do a full ERP blueprint with it as well.
		+
		+
		+	One can combine it with for example the LEADing Practice Service Reference Content and the LEADing Practice Business Innovation & Transformation Enablement (BITE) Reference Content for enabling business innovation and transformation and do a full ERP blueprinting, design and implementation while at the same time doing a full service renewal and business transformation within the project.
		+
		+
		+	The LEADing Practice Blueprinting Reference Content is in that perspective a really unique help with critical enterprise modelling aspects:
		+
		+
		+	*Blueprint the As-Is situation and design the needed To-Be.
		+	*Identify cost cutting potential in terms of duplication of business functions, services, processes, channels, etc.
		+	*Accurately evaluating new thinking in terms of innovation potential.
		+	*Developing new ways to reach the strategic business objectives and critical success factors.
		+	*Provide a fully integrated enterprise modelling capability within the blueprint and build continuous improvement approaches.
		+	*Identify value, create it and help continuously realize it.
		+	*Fully integrated requirement management method.
		+	*Enabled and interlinked maturity assessments in order to benchmark ones situation and make the right decision.
		+	*Business dependencies and scenarios that connect the right dots together.
		+	*Capabilities needed to innovate, change, and efficiently operate against a set of financial indices.
		+
		+
		+	An example of an overview of LEADing Practice Blueprinting Reference Content is below (for detailed examples and how to apply it to Enterprise Architecture, ERP and/or Transformation, please [[#\|contact us]]):
		+
		+
		+	[[File:LEAD-Blueprinting-Decomposition-Composition-Approach-Layered-Architecture-Roadmap-01.png\|frame\|center\|900px\|link=http://{{SERVERNAME}}/images/a/a2/LEAD-Blueprinting-Approach.pdf\|An example of a LEADing Practice Blueprinting Reference Content]]
		+
		+
		+	=== Way of Implementing ===
		+
		+	The LEAD Way of Implementing is not only about combining Enterprise Modelling and Enterprise Architecture principles; it is the approach the LEAD eXpert or architect follows in order apply the way of working and modelling into the physical and thereby the execution and concrete relevant aspects.
		+
		+
		+	The LEAD Way of Implementing provides a uniform and formal implementation description of the specific LEAD meta objects and artifacts by using decomposition and composition modelling techniques within the different layers (e.g. business, application and technology).
		+
		+
		+	Most implementations fall short of transforming the business and creating real value due to the fact that they automate the existing way of working. Thereby actually reinforcing a siloed and ineffective way of automation. Hence, the implementation approach is not only about identifying and minimizing duplication of business functions, roles in terms of employees, process’s, services and many other cost cutting potential. It is in addition about the possibility to totally rethink the business workflow, the service flow, the process flow as well as the measurement and reporting flow. It can fundamentally rethink and transform the organization.
		+
		+
		+	The LEADing Practice Way of Implementing has been developed as a fully integrated part of any of the frameworks and methods and details a series of steps to be taken in order to produce a wanted and pre-determined result in the areas of the decomposition and composition of the business, application and technology relevant objects. The implementation approach is designed so that you can do a full project implementation e.g. ERP, cloud, service renewal, while applying full integrated enterprise architecture principles as well.