Time Patterns

# Time Pattern TP10: Periodicity

Especially in the medical domain there are frequently recurring tasks to be executed according to a periodical specification (e.g., a treatment plan). Thereby, periodical implies some regularity, but does not necessarily mean equally distanced.

Time Pattern TP10: Periodicity
Also known as
Recurrence, Appointment Series
Problem
A particular set of activities shall be performed periodically (i.e., according to a particular periodicity rule). Thereby, periodically implies some regularity, but does not necessarily mean equally distanced.
Design Choices
 C A schedule can be applied to different process granularities b Activity set M The Number of cycles is a determined by a fixed / dynamic number of iterations, b depends on end date, c depends on exit condition
Solution

A variant of an Ad-hoc Sub-Process may be used in combination with an associated periodicity rule.

Periodicity rules can be realized by combining patterns TP1-6, TP8 and TP9 which are applied when scheduling the activities of the respective Ad-hoc Sub-Process.
Context
The context requirements of the participating time patterns need to be fulfilled.
Examples
• Starting with next Monday group meetings will take place every two weeks at 11:30 am (Design Choices C[a] M[c]).
• Each day at 7 am the responsible assistant physician of the Gynecological Clinic is informing the assistant medical director about the patients (Design Choices C[a] M[c]).
• Course ``Business Processes and Workflows'' takes place every Monday from 8:00 am to 11:00 am starting on Oct 6th and ending on Jan 26th. On Dec 8th, 22nd, 29th and on Jan 5th no lectures will take place (Design Choices C[a] M[b]).
• An information letter is sent by the leasing company to each customer within the first two weeks of each year (Design Choice C[a] M[c]).
Related Patterns

# Product Evaluation

We differentiate between supported, partially supported, not supported, and not specified.
If an evaluation object provides support for the particular pattern the supported design choices are listed. If the pattern is only partially supported (e.g., by a work-around) this is indicated by the additional label "*" and if support is not specified this is indicated by the label "?". Missing support is labeled with "-".

 Product/Language Version Score Motivation Microsoft Outlook 2010 — not supported Sunbird 1.0 — not supported Google Calendar 12.2011 — not supported Microsoft Project 2010 — not supported BPMN 2.0 — not supported IBM Websphere Integration Developer 6.1 — not supported WebSphere Lombardi Edition 7.1 — not supported AristaFlow 1.0.1 — not supported Intalio 6.0.3 — not supported TIBCO Business Studio 3.4.2 — not supported Bettini et al. — loops are explicitly excluded from considerations Combi et al. M[a,b,c] Periodic Constraint on loop Activity; no really complex periodicities Eder et al. — loops are explicitly excluded from considerations Marjanovic et al. — loops are explicitly excluded Zhuge et al. — not discussed