From Enterprise Design with EDGY
(Created page with "=<span style="color: #1b56e2;">Process</span>= '''A set of related activities our enterprise carries out.''' Description Processes focus the design attention on a flow of activities needed for product creation (either directly or indirectly). They consist of a set of activities that are performed in coordination in an organisational or technical environment. A process is composed of activities connected by flow relationships. A process can be strictly structured (the s...")
 
No edit summary
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=<span style="color: #1b56e2;">Process</span>=
<small>[[Enterprise Elements]] | [[Facet and Intersection Elements]] | {{element|Ar Icon-Architecture|Architecture}}</small>


'''A set of related activities our enterprise carries out.'''
={{element|Ar Element-Process|Process}}=


Description
<span class="Ar Def">A set of related activities our enterprise carries out.</span>
Processes focus the design attention on a flow of activities needed for
product creation (either directly or indirectly). They consist of a set of
activities that are performed in coordination in an organisational or
technical environment. A process is composed of activities connected
by flow relationships. A process can be strictly structured (the sequence/
flows stay more or less the same in every process instance) or less
structured (activities may be omitted, the sequence/flows can vary).
If designed well, they lead to enterprises that operate efficiently
and effectively.


A process transforms a set of inputs into a set of products or
==Description==
intermediary outputs. In a Business Process Management practice, each
Processes are the [[flows]] of [[activities]] needed for [[product]] creation (either directly or indirectly). They transform a set of inputs into a set of products or intermediary [[outputs]] and consist of a set of activities that are performed in coordination in an organisational or technical environment. A process is composed of activities connected by flow relationships. It can be strictly structured (the sequence/flows stay more or less the same in every process instance) or less structured (activities may be omitted, the sequence/flows can vary). Processes can run across several [[organisation|organisational units]] or can be performed within one organisational unit only.
process shall have a Process Owner that has the overall responsibility for
 
the end-to-end management of one or more processes.
Well-designed processes lead to [[enterprises]] that operate efficiently and effectively across all required organisational units.
 
==Process Map==
 
[[File:EDGY-Process-Map_Process-Model_Process-Chart.png|EDGY Process Map / Process Model / Process Chart]]
 
Depicting [[tree]] and [[flow]] relationships. Also known as Process Model or Process Chart.


==Examples==
==Examples==
Line 27: Line 24:
==Use==
==Use==
*Engineer operations for efficiency.
*Engineer operations for efficiency.
*Design the interplay between organisational units.
*Design the interplay between [[organisation|organisational units]].
*Design flows of data or physical structures.
*Design flows of [[data]] or physical [[objects]].
*Establish a continuous improvement of processes.
*Establish a continuous improvement of processes.
*Define end-to-end process ownership.
==Base element==
*{{element|Ar Element-Process|process}} is an {{element|Element-Activity|activity}}


==Related==
==Related==
*[[product]] is created by [[process]]
*{{element|Pr Element-Product|product}} is created by {{element|Ar Element-Process|process}}
*[[organisation]] performs [[process]]
*{{element|Or Element-Organisation|organisation}} performs {{element|Ar Element-Process|process}}
*[[process]] realises [[capability]]
*{{element|Ar Element-Process|process}} realises {{element|Ar Element-Capability|capability}}
*[[process]] requires [[asset]]
*{{element|Ar Element-Process|process}} requires {{element|Ar Element-Asset|asset}}
 
==Suggested labels==
*internal, shared ([[tagging|tag]])
*structured, non-structured ([[tagging|tag]])
*manual, automated, hybrid ([[tagging|tag]])
*automation degree ([[metric]])
*cost ([[metric]])


==Variants==
{{#seo:
*Automated process
|keywords=Process Management,Process,BPM,Business Process,Business Process Management,Process Model,Process Chart
*Manual process
|description=In EDGY, a process is a set of related activities our enterprise carries out. EDGY is Intersection Group's Open Source tool for collaborative Enterprise Design.
*Structured process
|image=EDGY-Process-Map_Process-Model_Process-Chart.png
*Non-structured process
|image_alt=EDGY Process Map
}}

Latest revision as of 18:38, 8 June 2023

Enterprise Elements | Facet and Intersection Elements | Architecture

Process

A set of related activities our enterprise carries out.

Description

Processes are the flows of activities needed for product creation (either directly or indirectly). They transform a set of inputs into a set of products or intermediary outputs and consist of a set of activities that are performed in coordination in an organisational or technical environment. A process is composed of activities connected by flow relationships. It can be strictly structured (the sequence/flows stay more or less the same in every process instance) or less structured (activities may be omitted, the sequence/flows can vary). Processes can run across several organisational units or can be performed within one organisational unit only.

Well-designed processes lead to enterprises that operate efficiently and effectively across all required organisational units.

Process Map

EDGY Process Map / Process Model / Process Chart

Depicting tree and flow relationships. Also known as Process Model or Process Chart.

Examples

  • A car company has largely automated their production process.
  • An insurance provider treats incoming claims in a structured fashion.
  • A government lab engages citizens to contribute to public innovation as a non structured process.
  • A software company uses agile methods to manage their development process.

Use

  • Engineer operations for efficiency.
  • Design the interplay between organisational units.
  • Design flows of data or physical objects.
  • Establish a continuous improvement of processes.
  • Define end-to-end process ownership.

Base element

Related

Suggested labels

  • internal, shared (tag)
  • structured, non-structured (tag)
  • manual, automated, hybrid (tag)
  • automation degree (metric)
  • cost (metric)