| 05.PR033 Project Close Out Process |
1.1 Check project documentation
Check all project documentation is complete and stored in the correct folder + approvals are recorded in Teams & saved correctly.
This includes:
Technical documentation
Planning documentation
Timesheets (in Operations drive for offshore trips)
Daily reports (for offshore trips)
Risk assessments etc
|
|
| |
1.2 Check project deliveries
If any deliveries were made for the project:
Ensure all delivery notes are signed & dated, have been uploaded to teams and are named + saved correctly in relevant sub folders
Ensure all photos have been uploaded to Teams and are named + saved correltyin relevant sub-folders
Ensure that any late deliveries are logged on ERP |
|
| |
1.3 Check project equipment
If equipment was hired out for the project:
Ensure all mobilisation records have been uploaded to the system
Ensure the asset register is up to date and that equipment has been checked for damage and/or missing items
Ensure all equipment hire has been invoiced correctly (check against delivery notes(s) out and delivery note(s) in) |
|
| |
1.4 Check document register
Check the document register to ensure:
There are no documents left in draft for the project
Documents are of the correct revision |
|
| |
1.5 Check project tasks
Teamwork is to be checked to ensure:
All tasks are marked as complete in Teamwork (no incomplete tasks)
Any remaining tasks must be completed before the project can be closed out (excluding the "close out" tasks) |
|
| |
1.6 Check invoices
Chesk that all the relevant boxes have been ticked in ERP to say the invoices have been completed |
|
| |
1.7 Close out in ERP
To 'Close Out' within ERP, click in the tab 'Close Out'. This closes the project out in ERP. |
|
| |
1.8 Record any lessons learnt and remove from whiteboard
Check with the prject team lead whether there were any lessons learnt (negative or positive) during the project.
In the whiteboard for that project:
Record any lessons learnt on the separate whiteboard "Lessons Learnt" tab as an improvement.
Inform QHSE department that a new lessons learnt has been added
QHSE to discuss and move lesson to relavant system (NCR/Strobe/Incident report etc)
Once moved the "Lessons Learnt" tab is to be updated to reflect how the issue is to be addressed. |
|
| |
1.9 Check client feedback
Check with projec team lead whether:
Any client feeedback has beeen recieved (Negative or Positive)
Enter into ERP system and inform QHSE Department |
|
| |
1.10 Check for marketing opportunity
Check with the project team lead and marketing whether the project could be a potential marketing opportunity taking the following points into consideration.
Challenging issue
Out of the ordinary
Made a significant difference to the client
Sloved an immediate issue for the client
Repesented a money/time saving issue for the client - Interesting problem to solve
Demonstrates Metron's expertise
Environmentally responsible |
|
| |
1.11 Review potential follow on work
Review all aspects of the job and highlight any potential follow on work that has been identified. This could be from:
Direct requests for assistance
Conversations with asset staff
Identifcation of ongoing issues
Current frustrations the asset is experiencing |
|
| |
1.12 Backup chat in Teams
Backup channel in Teams (using the Teams admin app)
To do this, firstly make sure all information (files) about the project is on the respective Teams channel |
|
| |
1.13 Upload Operations files to Teams
Upload (by dragging) the project files from the 'OPERATIONS' drive into the Team's file section on the project's channel |
|
| |
1.14 Delete Teams Channel
Only then should the Teams channel be deleted.
All files will now be accessible on SharePoint. |
|
| |
1.15 Close out and archive in Teamwork
Check off all close out tasks in Teamwork
Check off "Archive Teamwork Task" in Teamwork |
|