Admin at 09:56, 14 January 2019

2019-01-14T09:56:31Z

Admin: Created page with "Category:Enterprise Architecture Standards {{DISPLAYTITLE:Process Architecture Reference Content}} In the context of LEADing Practice, a process is a set of activities an..."

2019-01-14T09:55:55Z

Created page with "Category:Enterprise Architecture Standards {{DISPLAYTITLE:Process Architecture Reference Content}} In the context of LEADing Practice, a process is a set of activities an..."

New page

[[Category:Enterprise Architecture Standards]]
{{DISPLAYTITLE:Process Architecture Reference Content}}

In the context of LEADing Practice, a process is a set of activities and transactions that an organization conducts in order to achieve its objectives. It can be simple (i.e. order fulfilment) or complex (i.e. new product development), short-running (i.e. employee on-boarding) or long-running (i.e. regulatory compliance), function-specific (i.e. proposal management) or industry-specific (i.e. energy procurement). It can exist within a single department (i.e. billing), run throughout the entire enterprise (i.e. strategic sourcing), or extend across the whole value chain (i.e. supply chain management).

<blockquote>
''You can download the [[Media:LEADing-Practice-Process-Reference-Content-Process-Classification.pdf|Process Classification here]].''
</blockquote>

A process represents flow of control between or within functions and/or services (depends on the granularity of definition). Processes represent a sequence of activities that together achieve a specified outcome, can be decomposed into sub-processes, and can show operation of a function or service (at next level of detail). Processes may also be used to link or compose organizations, functions, services, and processes. Specific Business Process's are defined by steps that perform an input into a single enriched output. At its most generic, any set of activities performed by a business that is initiated by an event, transforms information, materials or business commitments, and produces an output.

In the context of LEADing Practice Modelling principles, an activity typically refers to having a connection to any work that is being performed in a process. We define activity as the smallest decomposed sub-process (a part of) that a given business process team decides to illustrate the activity on their process diagrams. In the composition view, we could reverse that and say that a process is made up of one or more activities. Activities can consist of a single action, like approving a purchase request or placing a cap on a bottle passing on a production line. Other activities involve multiple tasks, actions and/or steps, like filling out a form or assembling a chair. There is no consistency about how the various methodologies use terms like task and step, but increasingly, the term activity is reserved for the smallest unit of analysis.

A given activity could be performed by one or more employees, by a software system, or a combination thereof. It is the lowest granularity for specification of a business process which reflects the single actions an actor performs to fulfill a specific Process Step (i.e. creating, updating, reading, or deleting a valid instance of a data field).

This can be modelled in 2 different ways:
#In the 5 level structure of process levels, the activity is the 5<sup>th</sup> level (after process steps which is the 4<sup>th</sup> level).
#In the BPMN view, there are 2 types of activities: Tasks and Sub-processes.

Other modelling references to activities could also be:
#Work activities: work performed to convert inputs into outputs. This is measurable.
#Activity-based Costing (ABC): Aggregations of actions performed in an organization which are useful for ABC computations.
#Value-driven Costing (VDC): The collection of the performance and value providing actions in an organization and the cost they have.
#Project Management: the activity is the smallest unit of work having four characteristics:
##definite duration;
##logic relationships with other activities in the project;
##resource consumption; and
##an associated cost. Often used as an alternative term for task.

'''Process (P) Artefacts'''

The Process Reference Content has 3 types of artefacts in terms of both process maps, matrices and models that capture the meta objects which are instrumental, and an essential part of the enterprise modelling, enterprise engineering and enterprise architecture.

Fully integrated and standardized process modelling and architecture artefacts enables the subject matter experts/practitioners to work and model with the process meta objects throughout all the architectural layers (business, application and technology). This is also one of the greatest strengths of the LEADing Practice Enterprise Standards. Not only are the process objects governed by its connection modelling rules, but how and where the artefacts interlink and share common objects is defined and standardized.

'''The Process (P) Map Artefact'''

The Process (P) Map provides an overview of the key processes of the organization and their main aspects. The following aspects are described per process:
*'''What''' (in terms of context specification): Process Area.
*'''What''' (in terms of context specification): Process Groups.
*'''What''' (in terms of context specification): Business Process.
*'''What''' (in terms of context specification): Process Steps.
*'''What''' (in terms of context specification): Process Activities.
*'''Who/whose''' (in terms of who is concerned with and/or responsible for the delivery of the results): Stakeholder Involved.
*'''Who/whom''' (in terms of who is ultimately accountable for): Process Owner.
*'''Who/whose''' (in terms of who is concerned with and/or responsible for the delivery of the results): Managers Involved.
*'''Who/whose''' (in terms of who is concerned with and/or responsible for the delivery of the results): Roles/Resources Involved.

[[File:LEAD-Frameworks-Table-Process-Map-01.png|frame|center|900px|link=http://{{SERVERNAME}}/images/0/0f/LEAD-Frameworks-Table-Process-Map.pdf|Process Architecture Reference Content - Process Map]]

'''The Process (P) Matrix Artefact'''

The Proces (P) Matrix provides an overview of the key processes of the organization and their main relationships with other objects:
*'''Whither''' (in terms of options and/or alternatives): Events, Gateways and Measures (manual/automated).
*'''Where''' (in terms of location specification): Strategic, tactical or operational.
*'''How''' (in terms of how-to-do-it specification): management, main or supporting.
*'''Why''' (in terms of reason and/or motivation): rules and compliance aspects.
*'''Whither''' (in terms of goal specification): goals, plans, requirements, etc.
*'''Why''' (in terms of reason and/or motivation): performance/value expectations.

[[File:LEAD-Frameworks-Table-Process-Matrix-01.png|frame|center|900px|link=http://{{SERVERNAME}}/images/e/e2/LEAD-Frameworks-Table-Process-Matrix.pdf|Process Architecture Reference Content - Process Matrix]]

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

A Process (P) Model can illustrate a plethora of different steps and activites depending on the context in which it is designed for and used within. The attached example of a Process (P) Model is based on BPMN 2.0, yet also showing the design and modelling opportunities for processes using the LEADing Practice X-BPMN (eXtended Business Process Modelling Notations) modelling principles:

[[File:LEAD-Cross-Enterprise-Standards-Process-Reference-Content-Business-Process-Diagram-WITH-LEGEND-01.png|frame|center|900px|link=http://{{SERVERNAME}}/images/8/86/LEAD-Cross-Enterprise-Standards-Process-Reference-Content-Business-Process-Diagram-WITH-LEGEND.pdf|Process Architecture Reference Content - Business Process Model]]

'''Using the Process (P) Artefacts'''

Once the key processes of the organization have been specified, they are then linked to, associated with and conntected to the other objects. This association enables the expert/practitioner to tie them to the areas where the key processes have a connection and/or influence. A list of meta objects the key processes relate to are:
*Goal (e.g. business, application, technology) (S)
*Objective (Critical Success Factor, Plan, Forecast, Budget) (S)
*Performance Indicator (+Tier: Strategic, Tactical or Operational) (S)
*Value Expectation (S)
*Performance Expectation (S)
*Resource/Actor (S)
*Business Roles (S)
*Business Owner (S)
*Business Rules (S)
*Business Compliance (S)
*Service Tier (Strategic/Tactical/Operational) (S)
*Service Roles (S)
*Service Rules (S)
*Process Area (categorization) (P)
*Process Group (categorization) (P)
*Business Process (P)
*Process Step (P)
*Process Activity (P)
*Events (P)
*Gateways (P)
*Object (Business, Information & Data) (P)
*Process Type (main/mgmt./support) (P)
*Process Flow (incl. Input/output) (P)
*Process Roles (P)
*Process Rules (P)
*Process Measurement (PPI) (P)
*Process Owner (P)
*Service Measurements (Level Agreements) (S)
*Application/System Owner (S)
*Application Rules (S)
*Application Compliance (S)
*Data Rules (S)
*Data Compliance (incl. Security) (S)

'''Roles involved with the Process (P) Artefacts and meta objects:'''

{|class="wikitable" style="border: none;width:100%;border:0px; color:white;"
|class="thead" style="border: none;background-color:#1497d5;width: 30%;text-align:left;" |
'''ENTERPRISE MODELLERS'''
|class="thead" style="border: none;background-color:#1497d5;width: 30%;text-align:left;color:white;" |
'''ENTERPRISE ENGINEERS'''
|class="thead" style="border: none;background-color:#1497d5;width: 30%;text-align:left;color:white;" |
'''ENTERPRISE ARCHITECTS'''
|-
|style="border: none;background-color:#ebecec;color:black;" |
Business Analyst (P)
|style="border: none;background-color:#ebecec;color:black;" |
Value Engineer (S)
|style="border: none;background-color:#ebecec;color:black;" |
Business Architect (P)
|-
|style="border: none;background-color:#ebecec;color:black;" |
Process eXpert (P)
|style="border: none;background-color:#ebecec;color:black;" |
Technology Engineer (S)
|style="border: none;background-color:#ebecec;color:black;" |
Solution Architect (S)
|-
|style="border: none;background-color:#ebecec;color:black;" |
Value eXpert (P)
|style="border: none;background-color:#ebecec;color:black;" |
Process Engineer (P)
|style="border: none;background-color:#ebecec;color:black;" |
Value Architect (P)
|-
|style="border: none;background-color:#ebecec;color:black;" |
Information eXpert (S)
|style="border: none;background-color:#ebecec;color:black;" |
Test Engineer (S)
|style="border: none;background-color:#ebecec;color:black;" |
Data Architect (S)
|-
|style="border: none;background-color:#ebecec;color:black;" |
Service eXpert (S)
|style="border: none;background-color:#ebecec;color:black;" |
Quality Engineer (S)
|style="border: none;background-color:#ebecec;color:black;" |
Service Architect (S)
|-
|style="border: none;background-color:#ebecec;color:black;" |
Transformation eXpert (S)
|style="border: none;background-color:#ebecec;color:black;" |
Change Engineer (S)
|style="border: none;background-color:#ebecec;color:black;" |
Technology Architect (S)
|-
|style="border: none;background-color:#ebecec;color:black;" |
|style="border: none;background-color:#ebecec;color:black;" |
Software Engineer (S)
|style="border: none;background-color:#ebecec;color:black;" |
Process Architect (P)
|-
|style="border: none;background-color:#ebecec;color:black;" |
|style="border: none;background-color:#ebecec;color:black;" |
|style="border: none;background-color:#ebecec;color:black;" |
Enterprise Architect (S)
|-
|style="border: none;background-color:#ebecec;color:black;" |
|style="border: none;background-color:#ebecec;color:black;" |
|style="border: none;background-color:#ebecec;color:black;" |
Information Architect (S)
|-
|}

(P) = Primary object/role
(S) = Secondary object/role

'''Stakeholders involved with the Process (P) Artefacts and meta objects:'''

*Top Management: CEO/President
*High Management: Chief x (*) Officer/Vice President/Senior Executive/Director/Senior Manager
*Middle Management: Manager/Senior (Team) Leader
*Lower Management: Team/Group Leader
*Operational: User (Senior, Medior, Junior)

(*): 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.

'''The Process Architecture Reference Content Poster'''

The Process Architecture Reference Content poster gathers all significant process-related objects and principles into a single, easy-to-use source of reference that covers nearly all areas, but is primarily focused on process modelling, process engineering and process architecture.

[[File:POSTER-LEAD-Process-Reference-Framework.png|frame|center|900px|link=http://{{SERVERNAME}}/images/d/d4/POSTER-LEAD-Process-Reference-Framework.pdf|LEADing Practice Cross-Enterprise Standard - Process Reference Content]]

[[Category: Process Management and Process Optimization]]

@@ Line 1: / Line 1: @@
 {{DISPLAYTITLE:Process Architecture Reference Content}}
+= Process Architecture Reference Content =
 In the context of LEADing Practice, a process is a set of activities and transactions that an organization conducts in order to achieve its objectives. It can be simple (i.e. order fulfilment) or complex (i.e. new product development), short-running (i.e. employee on-boarding) or long-running (i.e. regulatory compliance), function-specific (i.e. proposal management) or industry-specific (i.e. energy procurement). It can exist within a single department (i.e. billing), run throughout the entire enterprise (i.e. strategic sourcing), or extend across the whole value chain (i.e. supply chain management).

LEAD Reference Content:Process Architecture Reference Content - Revision history

Admin at 09:56, 14 January 2019

Admin: Created page with "Category:Enterprise Architecture Standards {{DISPLAYTITLE:Process Architecture Reference Content}} In the context of LEADing Practice, a process is a set of activities an..."