How-to... Info
The info section may contain valuable additional information about TaskPack. If there is a misunderstanding in execution, we can almost certainly find a quick solution here. But due to the volume of the Info section, it can become burdensome for both the Doer and the Process Manager. That is why we should use it selectively, only to the extent that it is really necessary because not all of this information is suitable or necessary to follow every TaskPack.
Trigger
The start of TaskPack execution is usually the very end of the previous TaskPack.
But if this is not the case, then we can specify what or who initiates the start of TaskPack execution. For example: before, after, during something; every 1st of the month, at the end of the year; when the temperature drops below 40°F; when the Process Manager says so, at 10 o'clock, etc.
Estimated duration
We can empirically determine how long the execution of a particular TaskPack takes. This information is valuable to the Process Manager for planning daily activities in the tool: Operators > Arena.
We need to determine how much time in minutes and hours can be spent on TaskPack execution.
If the nature of the TaskPack is such that the duration of the execution varies a lot from case to case, then we should not try to set a time limit for the execution.
Collect : Deliver
It is very useful to know in advance how the connected TaskPacks will handover results to each other. How does TaskPack receive previous results as its input? How TaskPack delivers its result to the next TaskPack. Are the results received and delivered one by one or do they wait for a certain amount to accumulate and then collect or deliver them as a group?
This information can be crucial for the speed of the process. We can present them abbreviated with these combinations:
1:1
A 1:1 exchange occurs when a Doer collects results from previous TaskPacks one by one, executes the necessary tasks from his/her TaskPack, and delivers their results individually, one by one, to the next Doer.
1 : accumulation
When a Doer collects the results from previous TaskPacks one by one, executes the necessary tasks from his/her TaskPack, and accumulates his/her results in one place (such as on a pallet, in a box, or in a file) before delivering them in bulk, it is referred to as an accumulation exchange or a "1:accumulation" exchange.
accumulation : 1
In the reverse case, when a Doer takes accumulated results (such as a palette of something), performs the necessary tasks on them from their TaskPack, and delivers them successively one by one, it is referred to as an "accumulation:1" exchange.
accumulation : accumulation
In the last variant, Doer takes the accumulated results (eg a pallet of something) and then performs the necessary tasks from his TaskPack on them and accumulates his results in one place (eg boxes of something) before delivering them in bulk. That would be "accumulation: accumulation".
Collect : Deliver description
Collection and delivery do not always have to be simplified as in the above combinations. In this case, it is useful to describe the handover in more detail.
Required resources, conditions, etc.
Here we need to specify the necessary special conditions and resources for the execution of the TaskPack. Common resources that are shared between multiple TaskPacks and multiple Doers are especially emphasized.
Variations
In variations, we describe rarer variants, i.e. different situations in which Doer can find himself when executing the same TaskPack. If there are minor variations of the TaskPack for which it is not worth writing a separate TaskPack, such a variation is described here.