Ratings can take the form '+' which indicates that a particular tool or language provides direct support for the pattern involved, '+/-' which indicates that some limitations exists regaring direct support, and '-' which indicates that no direct support is provided. If support is not specified this is indicated by the label '0'.

Pattern	Design Choice				Score	Comment
	System-specific Design Choices			A[b,c], B[a*,b*]	+/-	partially supported
	A	Parameters of a pattern may be set at	a	At build-time	-	not applicable
			b	At instantiation time	+	When a "process is created" all the activities are added as tasks or appointments that is the instantiation time
			c	At run-time	+	Parameters of tasks and appointments can be modified at any time
	B	Time parameters can be specified in different time granularities	a	Basic	+/-	Cycles support Day, Week, Month and Year. Hour and Minute are only supported for Durations
			b	System-defined	+/-	Working Days (needs clarification, granularity vs. Reoccurrence pattern)
			c	User-defined	-	not supported
TP1	Time Lags between two Activities			—	-	No constraints on time lags between activities supported
	D	There are three kinds of restrictions	a	Minimum value	-
			b	Maximum value	-
			c	Time interval	-
	E	Time lags can be realized based on four different time relations	a	Start-Start	-
			b	Start-End	-
			c	End-Start	-
			d	End-End	-
TP2	Durations			C[a], D[b]	+/-	partially supported for single activities
	C	Patterns can be applied to different process elements	a	Single activity	+	appointments always have a duration
			b	Activity set	-	not supported
			c	Process model	-	concept does not exist
			d	Set of process instances	-	concept does not exist
	D	There are three kinds of restrictions	a	Minimum value	-	not supported
			b	Maximum value	+	supported by assigning an end-date to an appointment
			c	Time interval	-	not supported
TP3	Time Lags between Arbitrary Events			—	-	No events supported
	D	There are three kinds of restrictions	a	Minimum value	-
			b	Maximum value	-
			c	Time interval	-
TP4	Fixed Date Elements			C[a], F[a,b,d]	+/-	partially supported for activities
	C	Patterns can be applied to different process elements	a	Single activity	+	supported as tasks or appointments
			c	Process model	-	concept does not exist
	F	Patterns can restrict three dates of a process artifact	a	Earliest start date	+	start date for tasks and appointments
			b	Latest start date	+	reminder for tasks and for appointments
			c	Earliest completion date	-	not supported
			d	Latest completion date	+	due date for tasks, end date for appointments
TP5	Schedule Restricted Element			—	-	No constraints on activity dates supported
	C	Patterns can be applied to different process elements	a	Single activity	-
			c	Process model	-
	F	Patterns can restrict three dates of a process artifact	a	Earliest start date	-
			b	Latest start date	-
			c	Earliest completion date	-
			d	Latest completion date	-
TP6	Time Based Restrictions			—	-	No relations between activites supported, no constraints on activity dates supported
	G	Time Based Restrictions can be applied to different types of process artifacts	a	activities within same process instance	-
			b	activities within different process instances	-
			c	Instances of a process or group of processes	-
	H	There are two kinds of restrictions	a	Minimum number of executions	-
			b	Maximum number of executions	-
	I	There are two types of restrictions which can be expressed by Time Based Restrictions	a	Number of concurrent executions	-
			b	Number of executions per time period	-
TP7	Validity Period			—	-	No constraints on activity dates supported
	C	Patterns can be applied to different process elements	a	Single activity	-
			c	Process model	-
	F	Patterns can restrict three dates of a process artifact	a	Earliest start date	-
			b	Latest start date	-
			c	Earliest completion date	-
			d	Latest completion date	-
TP8	Time Dependent Variability			—	-	There is no control-flow
	J	There are different time aspects which may be considered by an instance of this pattern	a	Execution time of an activity / process instance	-
			b	Time lags between activities / events	-
TP9	Cyclic Elements			D[a], E[a, c], K[a], L[a]	+/-	partially supported
	D	There are three kinds of restrictions	a	Minimum value	+	as all dates are considered as earliest start there are only minimum values supported
			b	Maximum value	-	not supported
			c	Time interval	-	not supported
	E	Time Lags can be realized based on four different time relations	a	Start-Start	+	create new task every n days (weeks, etc.)
			b	Start-End	-	not supported
			c	End-Start	+	create new task n days (weeks, etc.) after last tasks has finished
			d	End-End	-	not supported
	K	Cyclic Elements may restrict the time lag between	a	two directly succeeding iterations	+	supported
			b	two subsequent activity instances belonging to arbitrary iterations	-	not supported
	L	Time Lag between cycles	a	is fixed	+	supported
			b	may vary	-	not supported (no evaluation of any "formula" possible)
TP10	Periodicity			—	-	not supported
	M	The Number of cycles is	a	fixed / dynamic number of iterations	-	not supported
			b	depends on time lag and end date	-	not supported
			c	depends on exit condition	-	not supported