Ideation
Identification
Conceptual Design
Front End Design and Tendering
Detail Design
Construction
Commissioning and Handover
Project
Close out
Idea ready for enrichment
Main purpose: ensure a robust resource allocation in the ideation process.
Steps to pass Gate 1:
Develop idea pitch (typically a slide set) including
• Technical description
• First cost estimation
• Idea for a business model
• Strategic fit for Uniper
If a project is inherited from another business unit or part of a customer request, this decision might not be required.
Steps to pass Gate 1:
Develop idea pitch (typically a slide set) including
• Technical description
• First cost estimation
• Idea for a business model
• Strategic fit for Uniper
If a project is inherited from another business unit or part of a customer request, this decision might not be required.
Develop for SD
Additional resources are mobilized for the next project sub phase: Identification. A small project organization develops the project idea further with the aim to pass the SD decision.
Pre-SD quality check
Ideally two months ahead of an SD decision a review workshop takes place. Aim of the workshop:
- Review of the project documents to date (SD papers, and assumptions)
- Development of a project roadmap to FD submission.
SD / Approval of engineering budget
Gate 4 serves
- to confirm the project strategic fit and outline the business case for Uniper,
- to receive development funding, and
- to ensure alignment on commitments and expectations set through the project development phase.
Concept Freeze
- Review of the results of the conceptual design phase in preparation of the front end design & tendering phase start.
- The reconciliation of ORS/customer requirements and conceptual design results is documented in the "Book of Assumptions" under the heading "Requirements vs Solutions".
- The result of the concept review is a design freeze of the “conceptual design” phase.
Start Tendering
To start tendering, basic engineering documents need to be reviewed. Typical documents for revision are:
- procurement strategies
- delivery and service specifications incl. the contract conditions
- associated QA/QC and HSE documents and specific site conditions
- Basic Engineering Report (incl. E&A reports with design bases), and
- site and installation plans
Pre-FD quality check
Purpose of this WS:
- prepare FD decision
- handover of the project from developing unit to execution unit
- definition of the handover documentation between these two units
A successfully completed project review is required for the handover of the project to the execution unit. As part of this project review, the future signatories of the FD application shall be involved, and at a minimum, the developing and executing Uniper entity. At this point in time the execution phase setup (governance/organisation etc.) is aligned between the involved parties.
Typical subject of this review are business case, permitting plan, cost calculation and schedule, risk assessment, (register and Monte Carlo simulations), project organization for execution, and technical results of the engineering.
Purpose of this WS:
Typical subject of this review are business case, permitting plan, cost calculation and schedule, risk assessment, (register and Monte Carlo simulations), project organization for execution, and technical results of the engineering.
Purpose of this WS:
FD (Financial Decision)
FD is to confirm the full business case and make the final investment decision. Hence, one of the most important gates within the process.
Ready for construction
A review workshop is used to prepare for site activities at the end of the Detail Design phase. Typical bases are e.g., construction execution plans, site setup concept, site regulations, site organization, assembly concept, workshop plans, workshop acceptances, QA plans, QA specifications. The outcome will be documented accordingly.
Ready for commissioning
A review workshop is used to prepare for the commissioning/start-up activities at the end of the construction phase.
Typical bases are e.g.
Typical bases are e.g.
- commissioning plan
- commissioning instructions
- safety instructions
- QA plans
- inspection records of manufacturing and erection QA
- amendment protocols
- manufacturer's documents
The outcome will be documented accordingly.
Ready for handover
Gate 11 serves as preparation for the operation phase. The reviewed document should include
- the handover documentation incl. operation manual,
- commissioning experience/knowledge
- training documents and training plan
- LOP list
- AERO risks, etc.
In case documents are missing or not complete, this will be transparently documented.
A specific risk assessment of the potential impact on future operation must be carried out and recorded in the risk management process. The completed and signed checklist is part of the documentation for the handover process to the future operator.
A specific risk assessment of the potential impact on future operation must be carried out and recorded in the risk management process. The completed and signed checklist is part of the documentation for the handover process to the future operator.
Project close out
Gate 12 is the final review of the overall project to evaluate the project outcome, the overall performance, as well as identification of improvement potentials for the execution of future projects based on the PMEF.
Typical review basis is the complete project documentation with a strong focus on the development of costs, time schedule and quality issues in the course of the projects all lessons learnt compiled.
The outcome of this workshop will be documented accordingly.
Typical review basis is the complete project documentation with a strong focus on the development of costs, time schedule and quality issues in the course of the projects all lessons learnt compiled.
The outcome of this workshop will be documented accordingly.
G1
G2
G3
G4
SD
G5
G6
G7
G8
FD
G9
G10
G11
G12