Professional Documents
Culture Documents
Risk Report BI-10-01382
Risk Report BI-10-01382
Risk Report BI-10-01382
Summary
The Risk Heat Map is shown opposite that shows the current number
of risks at each level of significance.
The current risk level is low as there are two critical and one
significant risk.
There are 2 critical and 1 significant risks.
There are 4 important risks.
The project cost impact is very low and almost negligible
The project schedule impact is 4.75%.
Three opportunities are identified to improve the project
schedule.
Referring to the trend chart opposite, the future risk situation is expected to remain low:
Commentary
- LSTK is currently executing package #1; hence, PMT has historical information reflecting
performance and efficiency.
- The majority of risks fall into the categories off project delivery and technology and engineering.
These should be actively managed as a group for maximum impact on the project.
Project delivery: risks# 5622, 5623, 5624 and 5625.
Technology and engineering: Risks# 5618, 5620, and 5621.
- The Detail Design phase is under tough schedule and most risk actions are classified urgency
level.
- SAPMT and LSTK should closely improve project communication and reporting.
Recommendations
- Project communication plan to be developed to improve project coordination.
- 10% construction PRM workshop is important to review this workshop actions effectiveness.
- The project is urged to use issue log.
Management Activities
- The project assigned a temporary Risk manager ANWAR SYED while a full time risk manager
is recommended.
- In the next risk workshop, the risk should be identified on the activities level rather than
deliverables.
BI-10-01382-0001
EXPAND DHAHRAN RESIDENTIAL COMMUNITY
UTILITIES INFRASTRUCTURES AND NETWORKS
PACKAGE - 2
Risk Management Status Report
Notes on interpreting the report at the end of Project Proposal and in later Detail design and construction stages
of the project.
The following information will aid in the interpretation of this report:
Number of critical risks. A low project risk is where the number of critical/significant risks is below four. High
project risk is where the number of critical/significant risks is eight or more.
Cumulative Schedule risk. This is calculated by adding the individual schedule risks end-to-end. In a real
project much of the schedule risk appears in parallel, so this value is a qualitative indicator only. The
cumulative schedule risk is considered low if it is below 16% of the project schedule and high if it is 23% or
more.
Cost risk. This is the accumulated cost risk for the project. Cost risk is considered low if it is below 4% and high
if it is above 6% or more of project value.
Threat Factor. This is a qualitative assessment of the level of risk in the project. It is the average Risk severity
for the top twenty threats. A value below 16 is considered low risk and a value of 24 or more is considered
high risk. The maximum value of 100 occurs when all risks have a very high impact on the project and a very
high probability of occurring.
Red Flags. A Red Flag is a risk outside the scope of management of the project and for which no effective
response plans have been identified.
Orange Flags. Orange Flags are risks within the scope of management of the project but where insufficient
risk response plans have been identified for the management of the risk.
Overall risk rating. This is a calculation based on the above four risk indicators.
Expected. The expected risk position is the risk position that should result if all risk response plans are
adopted and they are effective, based on the current expectations of the project. Many risk response plans
take time to become effective so the expected risk situation may not reached within the next reporting
period.
BI-10-01382-0001
EXPAND DHAHRAN RESIDENTIAL COMMUNITY
UTILITIES INFRASTRUCTURES AND NETWORKS
PACKAGE - 2
Risk Management Status Report
(The table below is a risk register summary. It shows essential information at a glance and without too much detail. These
ticks are used to indicate that the risk is being successfully managed. Crosses can be used to indicate poor or ineffective
management. Poor management can arise from the risk increasing, or that the risk response actions did not have the desired
effect by the end of the ‘Phase Managed’.
Target resolution indicates that the risk is expected to be managed and by when. This allows the manager to understand that
the risk is not going to go away today. ‘Residual’ is used to highlight those risks that are not controllable or are outside the
scope of management of the project.)
5618 Delay of the 90% DD package submittal ANWAR SYED Critical Significant
5620 Change orders and changes to the design ANWAR SYED Low Low
5621 Quality of the detail design is effected ANWAR SYED Important Low
5623 late in delivering the Manpower on time ANWAR SYED Significant NIL
5624 Subcontractors are not available when needed ANWAR SYED Important Important
Alerts
Risk response plans within the scope of management of the project, but not expected to have a
significant effect on the risks they are trying to manage.
Risks are not within the projects management scope of action.
Click the following link to download the risk register: (Click Here for project risk register)
SYED JAFAR
5623 1.Place the P.O. for GIS material.
BASHA
5625 Use ARAMCO approved manpower supply vendors for full SYED JAFAR
time QA manager BASHA
BI-10-01382-0001
EXPAND DHAHRAN RESIDENTIAL COMMUNITY
UTILITIES INFRASTRUCTURES AND NETWORKS
PACKAGE - 2
Risk Management Status Report
5620 Comments from HAZOP is not yet closed ANWAR SYED After
SYED JAFAR
5626 Expedite closing the comments SLFE
BASHA
5627 AYC, SAPMT are reviewing the quality along with design
ALAA ALI
process
5628 Exploratory excavation road network only for the Detail SYED JAFAR
Design phase BASHA
5623 Resources are not yet assigned to the project ANWAR SYED After
SYED JAFAR
5629 Assigning upto supervisor level and reflect to the histogram
BASHA
SYED JAFAR
5628 Management responding to the residents complaints After
BASHA
SYED JAFAR
5629 Opportunity: Project Partial IFC After
BASHA
Breaking the IFC submittal in different packages to accelerate the construction start date. High Opp.
Response Plan ID - Owner Before
Exploit SYED JAFAR BASHA
Action ID - 5637 Owner Date NIL
SYED JAFAR
5637 Issue system by system IFC
BASHA
BI-10-01382-0001
EXPAND DHAHRAN RESIDENTIAL COMMUNITY
UTILITIES INFRASTRUCTURES AND NETWORKS
PACKAGE - 2
Risk Management Status Report
SYED JAFAR
5630 Project Management practices After
BASHA
Construction equipment manager to improve the activities quality and optimization Moderate Opp.
SYED JAFAR
5639 Plan for work session between SLFE and AYC with vendors
BASHA