- Resource Planning begins with Commitment Maps. The Commitment Maps are the router of the system.
- Several Commitment Maps come from different DUs. Planning’s role is to synthesize these commitment maps (centrally). This gets translated into a calendar and requirements across CUs.
This means what functions deliver to, is not based on what functions can do, but working backwards from what planning is giving them.
- The moment the board approves at P0, it is an E&P level commitment that has to be met. When the commitment goes to the resource teams – if the requirement is 100 and they have 80 people, then they have to look for alternate ways of working to meet the commitment.
- The ‘What’ (commitments) is not in the control of the functions, but the ‘How’ is in their control – i.e. the resource group has the power to arrange for alternate resources.
- The other area where the resource group can add value is – out of the total requirement, they can identify how much is repeatable and how much is unique. This is the case for standardization across project(s).
Example: they have taken a call that they will have the same ASU (Air Separation) across various locations. If it takes 100 man days the first time, it should not take even 10 man days the next time.
This is the thinking Design & Engineering can bring to the table. So, in product, the question is being asked is, “Is it being done for the first time, OR is it a repeat item OR are we looking for improvement?” The choice of resources will be based on that. The value comes from there.