Tasks Waiting for Input — Problem Description
- An entity shall be shall require X hours to process, but X time cannot be completed in one step.
- The elapsed time to complete X, shall be Y.
- The number of times a resource will needed to complete X, shall be Z.
- The number of Entities that shall be allowed to be in this cycle shall be C.
- The resource used to work on the entity shall be R.
- Allow distributions to be used for the definition of X, Y and Z.
- Divide the elapsed time by the number of touches for an approximation of the time between touches.
- Divide the processing time by the number of touches for an approximation of the “time per touch”
- Design this section of model so that it can be duplicated by a simple copy and paste.
- Make all entries changeable through scenario parameters. Make the scenario parameters increment for each new instance of the model segment.
Implementing the “Tasks Waiting for Input” Feature
The following are steps you need to take in order to use the new feature in a process simulation.
- Update all model objects. If you haven’t done this for a while, this could take a few minutes. There have been more than 180 new features added so be patient. To update model objects select the Model Objects/Check for Updates menu item.
- Select the model object by using the Model Objects/Insert menu item.
- Select the MISC category.
- Select Long Process Time – Short Resource Usage and select the insert button.
- Click on the screen where you would like to place the upper left corner of the model object.
- Route into and out of the model object.
- Change the default values for the scenario parameters.
You will only need to connect to this activity and from this activity to the remainder of the model.
The Action Logic
The powerful yet simple language in ProcessModel allows complex logic to be defined as part of the model building process. Because this is predefined, the user will not need to write the logic for this complex interaction.
Simple logic defines a complex interaction of tasks waiting for input.
Each time this segment of the model is used in the same model the corresponding scenario parameters are added. You can simply go to the scenarios parameters dialog and enter the default values that define:
- Expected elapsed time (can be a distribution).
- Work content (can be a distribution).
- Number of times the resource will be used to complete work on this entity (can be a distribution).
- The capacity of the activity (how many of these entities will be allowed in process at the same time).
- The name of the resource that you would like to have work at this activity.
Parameters of tasks waiting for input are easily entered in one place using the scenarios parameter dialog.
The tasks waiting for input feature helps to accurately show the delay caused by incomplete information and helps to understand the resource usage over time to complete a delayed entity.
I hope this helps all of you that are looking for ways to code this scenario for business process improvement. If you need help with other scenarios, leave me a comment and I will try my best to reply to them. Best of luck implementing Tasks Waiting for Input in your next process simulation.