This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
modeling_of_activities_and_processes [2018/11/01 14:09] andries [3. Definition of kinds of occurrences, activities, processes and events] |
modeling_of_activities_and_processes [2018/11/01 14:27] andries [4. Specification of activity sequences] |
||
---|---|---|---|
Line 50: | Line 50: | ||
====== 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 a 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 a 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]] |