Professional Documents
Culture Documents
28 Meeting reporting deadlines due to late submission of inputs. Reports are issued on time though but creates a lot of
tension which seems to be affecting health.
29 Time / effort taken in producing reports Periodic check whether these reports are really being
used.
30 Due to continuous prolonged working on the computer, stress
relief measures need to be undertaken
31 List of the engineering deliverables related to Precomm and
Comm is finalized very late (almost at the completion of fab).
This documents and estimates related to precomm and comm
does not get captured at this stage in the Lotus Notes. This
results in progress calculation outside the system and the
system will not have complete info.
32
There is no tool available with planning to ensure that the
manhours booking regarding engineering is going to right
CTR. This is req'd. to avoid bad productivity resulting because
of wrong booking (CO mhrs may wrongly booked to main job)
33 We have implemented ICAPS for reporting progress on
Precomm and Comm on Dolphin. Weighting at ITR level and
the list of ITRs does not get finalized resulting in conflict in
progress reporting and rejection of invoices from client or
reduction in progress.
34 There is a tradition of changing the project weighting by PMT
almost every month. The weighting structure and "work
statement" (one progress report which is back up for invoice)
must be finalized by PMT and client and should be given to
Planning. In Dolphin's case PMT is forcing Planning to come
up with the weightings and changes are made to the same as
per the wish and will of the client almost every month. This
results in progress distortion.
35 PMT sometimes tries to negotiate progress from us.
36 We are down loading Lotus notes database and have to do a
lot of work to find progress at the activity level. Level 4
progress program can be modified and used to measure
progress on engineering and uploading of progress to the
network can be automated. The same can be done for
procurement.
37 Progress reporting on the Subcon activities should be done by
the production group. At present we are taking progress from
Subcon's updated network.
38 Progress at subfunction is not made 100% even after
completion of activity to avoid time card rejection in future if
some work comes up. This makes the primavera network ugly
and the forecast also is affected.
39 The review of the schedules does not happen by project team
properly before it goes to client.
40 Because of the estimates not being accurate the forecast
generated comes out wrong.
41 Production's input related to factoring and breaking the
subfunctions into activities is little.
42 We don't have set structure and set reports to work on
commissioning and precommissioning. This results in client
coming up with different requirement at different times making
the job difficult.
43 The h/up estimate should also come the way it comes for
structure or piping. Normally it is done at the end of fab.
44 In case of big project like dolphin the network should be
divided in to two, as it becomes to big to manage especially
when all activities are going on simultaneously.
45 Time spending in reports affects actual planning job
46 Uneasiness in the dealings with Controls group This was started with unnecessary intervention from
controls group on issue of reports
47 Slow computer