|
() |
|
| 04.PR003 Completing FPAL Performance Review |
1.6 Log FPAL meeting date
Complete FPAL meeting date field in feedback tab of the selected opportunity in ERP |
|
| |
2.3 Describe the work undertaken
Complete the Product/Service section of the form with a description of the work undertaken |
|
| |
4.1 Discuss and compile informaiton on the job in preparation for the meeting
Prepare the necessary information for the meeting. This should include as a minimum:
1. A copy of the PDP - remember this is a confidential Metron document and should not necessarily be shared with the client.
2. A list of those involved with the project
3. A list of any specific issues caused by the client or Metron during the works (discuss with Ops Co or Manager)
4. A review of commercial success of project - was it on budget.
5. Was project delivered on time?
6. A list of any feedback or anecdotal evidence on success or otherwise of delivery.7. Any VOR's. |
|
| |
5.1 Review supplier performance
Review and agree all supplier performance elements with the client.
This should ideally be done at a face-to-face meeting. However, the client may choose to do via skype/phone or complete offline and send Metron the completed forms. Complete prepared paper form or directly online as agreed with client.
Only assess areas for which you are able to comment/make a judgement. Contact others if you need further information. |
|
| |
6.1 Review the buyer performance
Review and agree all buyer performance elements with the client.
This can be confidential to Metron, however, only with MD & KAM approval should buyer feedback be submitted without discussion with the client. |
|
| |
7.3 Submit forms to FPAL
|
|
| 04.PR008 Invoicing and Closing Out |
1.1 Check and update systems
- Check all project documentation is complete, as per the PDP
- Check Share to ensure all issued documents have been uploaded to the project site
- Check document register to ensure there are no documents left in draft for the project
- Check any mobilisations in ERP to ensure dates are correct - check against offshore timesheets if unsure
- Check all tasks are completed in the project and move the project to closed. Any remaining tasks must be completed before the project can be close out.
- If equipment was sent offshore, ensure all mobilisation records have been uploaded to the system, the asset register is up to date and all equipment has been returned.
- If any deliveries were made for the project, ensure all delivery notes and photos have been uploaded to the system |
|
| |
1.3 Project team feedback
Record any formal or informal feedback from the project team. Log a summary as a note against the opportunity. If there are any key points for concern, discuss with the Operations manager. |
|
| 04.PR009 Feedback from Client |
1.1 Identify method of feedback
I/P from
04.PR005 Qualification
04.PR006 Bid Preparation
04.PR007 Awaiting Award
04.PR008 Invoicing and Closing Out
Identify how feedback should be obtained from client. FPAL shall be the preferred method.If completing FPAL review, go to Completing FPAL Performance Review Process Feedback can be sought by a number of means. FPAL performance reviews are the preferred method.Clients do not need to be Achilles FPAL registered to perform an FPAL perforamance feedback reviewFeedback requests to clients of any kind should always be discussed prior to issue of any forms/paperwork
If feedback is provided by clients without request and they do not wish to use FPAL, the process should be followed as if the client had been requested for feedback. |
|
| |
3.1 Prepare feedback request
Prepare a list of the questions for the client and determine a scoring mechanism if appropriate.
Use the FPAL Report 1 and Report 3 to provide an indication of typical questions |
|
| |
3.2 Agree questions and any scoring with the client
|
|
| |
4.1 Undertake review and scoring with client
|
|
| 05.PR004 Preparation of an Acceptance Test Procedure |
1.2 Literature Search
Locate all sources of relevant information to be used when researching the functional requirements of the equipment. This should include (where available) product manuals, drawings and schematics. If insufficient information is available, the project technical lead should be consulted before proceeding. |
|
| |
1.4 Obtain Functional Requirements Specification Approval
Obtain approval of the draft Functional Requirements Specification. This should be in accordance with the document control standard, from the appropriate approver as identified in the Functional Requirements Specification template and/or project plan. |
|
| |
1.6 Obtain Acceptance Test Procedure Approval
Obtain approval of the draft Acceptance Test Procedure This should be in accordance with the document control standard from the appropriate approver as identified in the Acceptance Test Procedure template and/or project plan. |
|
| 05.PR028 Personnel mobilisation |
1.2 Identify named person to complete trip and allocate
Use the LMS competency filter to ensure a suitable named person is selected. Dependent on scope, multiple named persons may be required - this will be identified as part of the core delivery process.
|
|
| 05.PR031 Formal contract review process |
1.1 Formal contract review is due
I/P from 05.PR001 Project Delivery
Project team, Operations Manager, Technical Lead and Account Manager notified that a formal contract review is due, as per pre-defined timescales in the project quality plan, project delivery plan and project programme. |
|
| |
1.2 Project team to write agenda and circulate
Project team to set date, time and format of meeting (e.g. review contract quality plan, review performance, etc.) and distribute agenda.
Agenda to include:
-Quick summary of what the project is (5 mins)
-Review of current status
-Review of previous performance (i.e over a defined time period - e.g. 1 year or 6 months, etc)
-Good points
-Bad points
-AOB
-Actions - any actions from the meeting are to be entered into ERP before the meeting ends |
|
| |
1.3 Tasks to be assigned
Project team to define tasks and assign accordingly for any preparation work involved. |
|
| 56.PR008 CNR Routine Delivery Process |
1.3 Prepare Work Pack
Prepare work pack document using the approved client template |
|