AH
Hi,
I have a process to publish a resource schedule by a field manager on a weekly basis. Each week the manager looks at the amount of work they expect to have and the resources they have available, the amount of stock the operatives have to hand and produce a schedule of work for the operatives in that area.
In some cases an operative can get in contact with their field manager and explain that due to shifting circumstances they are not able to take on the same amount of work going forward. The field manager will take this information and use it in their publish a resource schedule process.
So there is an optional activity of the operative informing the field manager of their availability at the start of the process, otherwise the process doesn't change. How should this be modelled? Should there be 2 start points, how to indicate that one of them is optional?
Additional, if the information about changed availability comes before the schedule has been published then the process has to be undertaken again, otherwise an incorrect schedule would be published.
Kind regards,
I would designate each of the initial input submittals as events (normal and optional) and place them at the beginning of the process with an xor or and operand, depending on how the events come in. If the optional path arrives further down in the scheduling process, you can introduce the optional event at any point in the process with an xor then check for an "alternative" document or input within the model and loop back if that would be called for.
