On this basis, instead of the previous analysis, now the PM is responsible for the
data analysis in order to get a time-now picture of the situation. Therefore, since he
knows the project targets, he is the one who can activate warnings, if any, and pro-
pose and implement corrective solutions to possible malfunctioning over the course
of the project itself, by always posing to himself three fundamental questions:
where are we, where should we be, where are we going?
Then it will be possible to obtain an S curve of the project as shown in Fig. 12.1.
This graph represents the progress according to the JET of the Actual Monthly
Plan (AMP), Cumulative Plan on an expected basis (CPE), Monthly Plan (MP),
Cumulative Plan (CP), Monthly achieved (MA) and Cumulative achieved (CA).
On the basis of the information, Actual is updated on the MP and the CP.
If we want to go into detail, then we shall refer to the MPL and the data con-
tained in it and already represented in the initial planning picture, which shows in
its graphic representation of the job progress all the typical elements of a time bar
chart. It is therefore possible to check connections, define the critical path, and
modify, if necessary, flows and time schedules.
This is a tool that is always available for use also vis-à-vis the final customer, so
as to be able, if necessary, to show data to the customer in a professional way.
What must never be neglected, since it is essential for the success of the first part
of the project, is the link between the MPL and the job site activities related to the
erection of the equipment and systems, and to their startup.
Therefore, variations must be weighed up not only with regard to the workload,
or in production or financial terms, etc., but also by analysing their consequences
and impact on the future job site activities. It will be also necessary to check the
possibility to modify the operating sequences and the various activities in time
without missing the objective or failing to achieve the contractual target.
As regards project monitoring and internal reporting, Table 12.1 later gives an
idea of how to tackle the problem of company reporting with the consequent creation
of standardised models that can be filtrated at various levels.
Table 12.1 Project report requirement
Stakeholders What they care What they need
Top management and
executives
Company development,
profitability, reputation
Project status report, issues
Director Project performance Project status, cash flow, earned
value, issues
Executive Project Manager Time, cost, quality, cash
flow
Task status, cost, problems, issues
Project Manager (support
staff)
Time, cost, quality, cash
flow
Task level details, overall project
status
Team members from various
departments
Schedule, workload Overall project status and depart-
ment details
Client Schedule, quality Project status, schedule, quality,
selected details
Suppliers Exchange of information,
schedule
Delivery target dates, technical
details
Information Management Database update Dedicated information on project
12.2 Project Monitoring 185