|
|
|
|
|
|
|
FIG.4
The program breakdown: Program requirements are passed down and any
variances to program achievement are brought to the level where they can
be resolved and no further. |
|
|
|
|
|
|
|
|
for his deliverable, he has the authority to change the technical compliance and timescales as long as it does not affect the next level up program (see Fig. 4). Should the TGM be unable to resolve the issue, then the TGM brings the variance to the Chief Engineer who would try to resolve it through a reoptimization of his program phase. Again, should this not be possible he will bring it to the Project Manager who will attempt to resolve it within the terms and conditions of the contract. In this way, problems are only brought to the level at which they can be resolved rather than raising all problems directly to upper management who would spend all their time firefighting. |
|
|
|
|
|
|
|
|
If the problem could be resolved through release of contingency, then, the coordinator/manager at any level has the option to raise a business case to facilitate release of contingency (held by the Project Manager). This business case must indicate that a release of contingency is the most cost- |
|
|
|
|
|
