You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For every target activity in the transitions with WT due to batching, we need to identify what batch processing strategy is applied in that activity. More specifically, we need to identify:
activities in which batch processing is applied (i.e., target activities);
frequency of batch processing (i.e., percent of cases for which batching is applied from the total number of cases processed in the activity);
The requirements for the UI for this component will be specified in a separate ticket.
FYI
Here, we also need to know which resources apply batch processing and how much WT due to batching each of them induces in each transition. This is already available in Kronos.
The text was updated successfully, but these errors were encountered:
@PowerMaxZ
For every target activity in the transitions with WT due to batching, we need to identify what batch processing strategy is applied in that activity. More specifically, we need to identify:
There is no need to develop the code for this functionality from scratch as it is already developed by David (see https://github.com/AutomatedProcessImprovement/batch-processing-discovery). Here, we need to re-use it.
The requirements for the UI for this component will be specified in a separate ticket.
FYI
Here, we also need to know which resources apply batch processing and how much WT due to batching each of them induces in each transition. This is already available in Kronos.
The text was updated successfully, but these errors were encountered: