When to Involve KAGES
Use KAGES when the owner needs an independent view of a development plan, engineering decision, contractor performance or project risk. We connect the technical evidence to the decision the owner needs to make.
What KAGES Provides
- Technical consulting and Owner’s Engineer guidance for government energy departments, including oil-and-gas engineering advice and technical support during IOC contract negotiations.
- Owner’s representation and independent cold-eyes reviews.
- Review of IOC and Tier-1 EPC execution, engineering evidence and contractor interfaces.
- Cost-recovery, contract-value and compliance auditing within the appointment.
- Risk identification, mitigation, accountability and follow-up.
- Technical expert-witness support for an agreed dispute or investigation.
- Review against applicable national, contractual and technical requirements, including API, ISO and ASME where relevant.
Representing the owner’s interests
Our review focuses on whether the proposed work is fit for purpose and represents value for the owner. We examine assumptions, interfaces and the evidence behind contractor submissions, then communicate findings and priorities clearly.
Contractor and technical assurance
We bring relevant engineering, quality, construction and commissioning expertise to the review. The assignment identifies the applicable contractual and technical standards, the evidence to be examined and how issues will be escalated.
Technical Advice and Contract Decisions
Independent engineering review supports government, NOC and owner decisions about contractor submissions and IOC contract negotiations. Technical expert-witness support is scoped to engineering evidence and the agreed appointment; legal representation remains with the authorised legal advisers.
A practical approach to project risk
A useful risk register connects a risk with its consequences, controls, responsible people and follow-up actions. The example below shows how those decisions can be recorded and reviewed through the project lifecycle.
Selected entries from the supplied source workbook; original row identifiers distinguish repeated record numbers. The complete example retains all 155 entries and 44 fields.
Source row 6: 4. Organizational
- Risk Description: Causes & Event or Circumstance
- General to other Projects: SharePoint Project Files hard to follow and disjointed. Can lead to files being double handled or misplaced or not tracked, need DCC assistance rather than retrieving on own. (Not user friendly)
- Consequences / Impact
- All documents for Project require easy logical tracking and current difficult to track and hard to ensure are fully correct and completed. Wrong information be stored and latest edition not known, correspondance not correct, quality checks unknown
- Probability Score (score 1-5)
- 5
- Impact Score (score 1-5)
- 4
- Risk Rating (Before mitigation)
- 20
- Probability (after mitigation)
- 1
- Severity (after mitigation)
- 1
- Risk Rating (After mitigation)
- 1
- Risk Owner (Action By)
- Client Project Management
- Risk Response Plan Outline
- Understanding all the Phases & Stage Gates and organising files into the correct area will vastly increase the efficiency of the project and bring understanding of current status within a Project.
- Risk Actions Description
- PMO and Document Control to organise files in unison and ensure Traceability and easy to Track.
- Action Status Open/Closed
- Open
Source row 7: 2. Economical
- Risk Description: Causes & Event or Circumstance
- General to other Projects: Need to ensure Document Control has the correct training and qualifications to hold such a critical position.
- Consequences / Impact
- It has been witnessed consistantly that the person incharge of Document Control does not have sufficient training which severly impacts the Project performance. Regular problems include, latest up-dated system drawing not issued, duplicate areas of information storage, personnel files used for information, lack of organising transmittals and daily correspondance, not making files easily tracable.
- Probability Score (score 1-5)
- 5
- Impact Score (score 1-5)
- 3
- Risk Rating (Before mitigation)
- 15
- Probability (after mitigation)
- 1
- Severity (after mitigation)
- 1
- Risk Rating (After mitigation)
- 1
- Risk Owner (Action By)
- Client Project Management
- Risk Response Plan Outline
- Retrain current Document Control or Hire a Better Qualified Document Control
- Risk Actions Description
- Massive Impact on normal work activities and time taken away from doing the job when searching for information which should be readily available
- Action Status Open/Closed
- Open
Source row 8: 4. Organizational
- Risk Description: Causes & Event or Circumstance
- General to other Projects: PM not picking own Project Management Team at the start of a Project
- Consequences / Impact
- A Project Manager should choose their own team based on the abilities each member brings to the team. Using none approved / personally vetted personnel runs a high risk of Project failure
- Probability Score (score 1-5)
- 4
- Impact Score (score 1-5)
- 4
- Risk Rating (Before mitigation)
- 16
- Probability (after mitigation)
- 1
- Severity (after mitigation)
- 1
- Risk Rating (After mitigation)
- 1
- Risk Owner (Action By)
- Client Project Management
- Risk Response Plan Outline
- Vet all new people prior to starting on the project.
- Risk Actions Description
- Do not accept personnel from outside or other projects without correctly vetting them
- Action Status Open/Closed
- Open
Relevant Experience
Relevant Expertise
Deliverables and Useful Information
- A prioritised findings and recommendations record.
- A risk and action view with responsibilities and follow-up points.
- Decision support on the agreed engineering, contractor or contract-value question.
Information to Prepare
- Project objectives and the decision required.
- Relevant engineering, commercial and contractor records.
- Existing risk registers, audit findings and delivery reports.
Presentations and Examples
Project Risk Register: Example
A populated example of risk assessment, responses, responsibility and follow-up.
Project Risk Register: Example
Read-only example · 311 PDF pages · 674 KB
KAGES Capability Statement
Read the written company statement or view the companion presentation for an overview you can share within your organisation.
KAGES Capability Statement
Document · 2 PDF pages · 319 KB
Company capabilities and selected experience across the KAGES team.
KAGES Capability Presentation
Presentation · 9 slides · 254 KB
An introduction to KAGES services and the team’s professional experience.
