User Tools

Site Tools


modeling_of_activities_and_processes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
modeling_of_activities_and_processes [2018/11/01 13:47]
andries [2. Specification of how objects are involved in occurrences]
modeling_of_activities_and_processes [2018/11/02 21:31] (current)
andries [Occurrences, activities, processes and events]
Line 1: Line 1:
-====== ​Occurrences, activities, processes and events ======+====== ​Modeling of occurrences, activities, processes and events ======
 An occurrence is in its widest sense anything that happens. This includes human activities, but also physical and (bio)chemical processes, control processes, events and physical phenomena. Processes includes both discrete processes and continuous processes. A discrete process consists of a sequence of discrete process steps or actions. Examples of discrete processes are business processes in which various persons provide a contribution in the process, mechanical production processes in the mechanical industry and batch processes in the chemical industry. A continuous process is a process that is an operation on a continuous stream of raw material to produce one or more continuous streams of product materials. Examples of continuous processes are the flowing of water in a river, the operation of an electric power generation plant and the various refinery processes. An occurrence in fact always happens over time, but in some cases, such as events, the duration can be neglected. All these kinds of occurrences can be modeled in Gellish in a similar way. An occurrence is in its widest sense anything that happens. This includes human activities, but also physical and (bio)chemical processes, control processes, events and physical phenomena. Processes includes both discrete processes and continuous processes. A discrete process consists of a sequence of discrete process steps or actions. Examples of discrete processes are business processes in which various persons provide a contribution in the process, mechanical production processes in the mechanical industry and batch processes in the chemical industry. A continuous process is a process that is an operation on a continuous stream of raw material to produce one or more continuous streams of product materials. Examples of continuous processes are the flowing of water in a river, the operation of an electric power generation plant and the various refinery processes. An occurrence in fact always happens over time, but in some cases, such as events, the duration can be neglected. All these kinds of occurrences can be modeled in Gellish in a similar way.
  
Line 31: Line 31:
 | 1 | P-101 | 101 | 194201 | pumping | 2 | S-1|  | 1 | P-101 | 101 | 194201 | pumping | 2 | S-1| 
  
-The UID of the idea (in the example idea 101) is the identifier of the occurrence. In this example the individual occurrence is not given a name. However, as a guideline it is recommended that software generates a name that is the concatenation of the name of the kind of relation, the word '​of'​ and the name of the individual subject. In the example the name of the process would be ‘pumping of S-1’.+The UID of the idea (in the example idea 101) is the identifier of the occurrence. In this example the individual occurrence is not given a name. However, as a guideline it is recommended that software generates a name that is the concatenation of the name of the kind of relation, the string ​' of ' and the name of the individual subject. In the example the name of the process would be ‘pumping of S-1’.
  
 ====== 3. Definition of kinds of occurrences,​ activities, processes and events ====== ====== 3. Definition of kinds of occurrences,​ activities, processes and events ======
  
-Occurrences that do not exist yet in the Gellish ​English ​dictionary can be added in a similar way as defining physical ​objectsby ​obeying the [wiki:"​Proper definition of a concept"​ rules for proper definitions] ​in Gellish English. A kind of occurrence shall be defined as a subtype of an existing kind of occurrence and facts that are by definition ​true shall be added to complete the definition. \\ +Occurrences that do not exist yet in the Gellish dictionary can be added in a similar way as defining physical ​objects by obeying the [wiki:"​Proper definition of a concept"​ rules for proper definitions]. A kind of occurrence shall be defined as a subtype of an existing kind of occurrence and given a textual description,​ whereas ​facts that are by definition ​the case shall be added to complete the definition. \\ 
-In general, generic kinds of activities and processes are independent of the subject of the occurrence, and independent of the performer or the enabler. For example, the activity '​design'​ or '​operate'​ does not include an indication of what is designed or operated. However, more specialised ​‘qualified’ activities often do include the subject of the activity or process. For example, "​design a pump" or "​operate a facility"​. In such a case the definition of such a kind of occurrence should include and explicit relation that states that it has by definition as subject a particular kind of thing. For example: \\ +Note that there is a distinction between generic kinds of occurrences and kinds of occurrences that have by definition an intrinsic performer or enabler. ​In general, generic kinds of activities and processes are independent of the subject of the occurrence, and independent of the performer or the enabler. For example, the activity '​design'​ or '​operate'​ does not include an indication of what is designed or operated. However, more specialized ​‘qualified’ activities often do include the subject of the activity or process. For example, "​design a pump" or "​operate a facility"​. In such a case the definition of such a kind of occurrence should include and explicit relation that states that it has by definition as subject a particular kind of thing. For example ​the concept '​design a pump' is defined as follows: \\ 
-^Name of left hand object^Name of relation ​type^Name of right hand object^ +^Name of left hand object^Name ​of kind of relation^Name of right hand object^Partial definition
-| design a pump | is a qualification ​of | design| +| design a pump | is a qualitative subtype ​of | design|where the subject is a pump.
-| design a pump | has by definition as subject a | pump|+| design a pump | has by definition as subject a | pump|
  
-Similar considerations apply for specific ​activities that include a specific subject. For example, the specific ​activity called '​design P-101" is by definition a design of a thing called P-101. This is specified as follows: \\ +Similar considerations apply for individual ​activities that include a specific ​individual object as its subject. For example, the activity called '​design ​of P-101" is by definition a design of a thing called P-101. This is specified as follows: \\ 
-^Name of left hand object^Name of relation ​type^Name of right hand object^ +^Name of left hand object^Name ​of kind of relation^Name of right hand object^ 
-| design of P-101 | is classified as a | design of a pump +| design of P-101 | is classified as a | design of a pump| 
-| design of P-101 | has as subject | P-101+| design of P-101 | has as subject | P-101
 + 
 +Note that the kind of relation 'has by definition as subject a' classifies a relation between two kinds, whereas the kind of relation 'has as subject'​ classifies a relation between two individual things.
  
 ====== 4. Specification of activity sequences ====== ====== 4. Specification of activity sequences ======
  
-Often it is required to specify in which sequence activities or chains of shall be or are performed. This may result in activity networks. For example, ​in activity scheduling ​for testing, commissioning and start up of facilities ​or to describe ​a maintenance procedure. ​This can be done for sequences of kinds of activities, but also for sequences individual activities, or for procuderes ​in which typical activity sequence is describedthat ​shall be repeated every time that the procedure is followed. \\ +Often it is required to specify in which sequence activities or chains of activities ​shall be or are performed. This may result in activity networks. For example, ​a sequence of activities that specifies a schedule ​for testing, commissioning and start up of a facility ​or the activity sequence that describes ​a maintenance procedure. ​Sequences ​can be specified ​for kinds of activities, but also sequences ​of individual activities, or in procedures ​in which typical ​(individual) ​activity sequence is described that shall be repeated every time that the procedure is followed. \\ 
-For example, ​the following ​activity sequence ​may describe ​steps that shall be taken during a planned maintenance shut-down (also called a turnaround) of facility:+For example, ​a generic ​activity sequence ​that describes ​steps that shall be taken during a planned maintenance shut-down (also called a turnaround) of facility ​may specify a sequence of kinds of activities. For example as follows:
  
-^Name of left hand object^Name of relation ​type^Name of right hand object^+^Name of left hand object^Name ​of kind of relation^Name of right hand object^
 | purge a vessel | shall occurs after a | drain a vessel| | purge a vessel | shall occurs after a | drain a vessel|
 | inspect a vessel | shall occurs after a | purge a vessel| | inspect a vessel | shall occurs after a | purge a vessel|
  
-Whereas ​a sequence of individual activities is expressed as follows:+Typical activities are activities about individual things. Usually they are modeled as individual activities. When used in procedure, the represent imaginary activities, whereas the real activities repeatedly use the procedure as a template. A sequence of typical ​individual activities ​uses other kinds of relations than above. Such a detailed procedure ​is expressed as follows:
  
-^Name of left hand object^Name of relation ​type^Name of right hand object^+^Name of left hand object^Name ​of kind of relation^Name of right hand object^
 | assemble system A | occurs after | clean system A| | assemble system A | occurs after | clean system A|
 | test system A | occurs after | assemble system A | | test system A | occurs after | assemble system A |
 +
 +Further details, for example about specifying partly overlapping activities, are given in the book '​Semantic Information Modeling Methodology'​.
  
 **//​Continue with//** [[:Document Management]] **//​Continue with//** [[:Document Management]]
modeling_of_activities_and_processes.1541076426.txt.gz · Last modified: 2018/11/01 13:47 by andries