Universiti Kuala Lumpur

Malaysian Institute of Aviation Technology

(UniKL MIAT)
ABB 30304 PROJECT MANAGEMENT

PROJECT CHARTER

TITLE: AVIATION SMART LEARNING EXPERIENCE WITH VR

GROUP 6

PROGRAMME: BACHELOR OF AIRCRAFT ENGINEERING TECHNOLOGY (HONS)

IN AVIONICS
PREPARED BY:
1) RABIATU ADAWIYAH BINTI MUSTAFFA 53213220104
2) RAGUNAN A/L P SANDRAN 53213121028
3) SHIHAB ABDELAZIZ MOHAMED ELHASSAN 53213220121
4) SIRIGUDI LIKITH SAGAR 53213220110
5) NUR SYAHIRAH BINTI KAMALRUL ARIFFIN 53213221049

PREPARED FOR: MR. MOHAMMAD FAKHRULNIZAM BIN MOHAMMAD

SUBMISSION DATE: 29 SEPTEMBER 2022

1.0 RISK MANAGEMENT PLAN

Risk management is an essential part of any project management which

allows the management team to identify potential risk that they can face along
the completion of the project.

The risk management also will lead to strategies that can be undertaken to
mitigate the risk while carrying our activities regarding the project.

The risk management document must be updated every fortnightly and every
time a significant event occurred from the day-to-day operation of the project .

1.1Embedding the risk management plan

The risk that have been identified are those that can prevent the project from
meeting the objective stated in project charter. Due to this, it is important to
refer and review the risk management plans against the organisation’s vision
and mission.

These documents will be reviewed by the Project Manager fortnightly to

update any contingencies that the team might face.

1.2 Audience

Group Reason
Directors Governance responsibility
Staff Operational responsibility
Quality Regulatory body
Assurance
Finance and Funding body
Accounting
2.0 Organisational Context

It is not possible to avoid risk entirely. To attempt to do so would mean

that the organisation would effectively be unable to function. It would also not
be able to take advantage of opportunities as they arise. Taking this into
consideration, the primary responsibility is to develop a conducive learning
process in UniKL MIAT to produce quality and efficient aircraft maintenance
engineer.

Therefore, the number of risk that must be taken into account will be
numerous to counter and mitigate those risk in the most proper manner. The
risk management plan will ensure a smooth flow of any unwanted
occurrences that might arise from any corner while working towards the
completion of the project .

3.0 Risk Strategy

To ensure that risks are identified in a consistent manner across the

project management team, a "Risk Assessment Model" will be applied. This
will enable us to rank the risks in priority order and those risks considered
essential to track will be recorded on the "Summary of Risks".

Mitigation strategies will be developed, recorded, and monitored every

2 weeks by the project manager. If new major risks are identified these shall
be recorded. The "Summary of Risks" will be reported to the higher
management on the monthly basis.

At appropriate times during the project, it may be appropriate to re-assess the

risks by applying the "Risk Assessment Model".
4.0 RISK ASSESSMENT DIAGRAM –
SMART LEARNING EXPERIENCE WITH VR
5.0 LIST OF RISK IDENTIFIED (RISK BREAKDOWN STRUCTURE)

RBS LEVEL 0 RBS LEVEL 1 RBS LEVEL 2 RISK CODE

Project Risk  Unplanned man  P05/01
power down
 Delay in
Obtaining  P05/02
Copyright and
Patent
Functional Risk  Inability to use  F05/03
due to dizziness
and nausea
 Reduced  F05/04
awareness on
surrounding
(possibility of
hitting or falling
SOURCES OF down)
PROJECT RISK
Resource Risk  Personal or  R05/05
Organizational
Data Leak
 Delay to develop  R05/06
the custom VR
Device
Organizational Risk  ROI could not be  O05/07
met at the
planned time
 Change of  O05/08
Management
Team
Technical Risk  System Collapses  T05/09
or hang during
operation
 Lack of internet  T05/10
signal (Low Wifi
Strength)
6.0 ANALYSATION OF RISK

6.1 Risk Code

Each risk has been a dedicated code for easier referencing for future
updates and possible occurrences. It is also helps in categorizing the
risk into better formatting.

Eg: T05/09 in which ‘T’ stands for Technical Risk, ‘05’ stands for risk
chapter and ‘09’ stands for n’th number of risk.

6.2 Risk Likelihood

The risk likelihood will be classified from Level 1 to Level 5 to set the
range of the risk. Level 1 will be the lowest probability and level 5 will
be the highest probability.

6.3 Risk Consequences

The risk consequences are the impact or damage that can happen
towards the project if the risk were to happen. The risk will also be set
from Risk Level 1 to Level 5 ranging from lowest risk to highest risk
respectively.

6.4 Control Adequacy

The control adequacy is to inform whether the risk is under control or
need a prompt action if the risk is beyond control. The control
adequacy will be categorized into three groups; SAT – Satisfactory,
MON- Monitoring Needed, ACT- if immediate action needed. These
group will be separated into score classes as below:

Below 15 = SAT

15 -19 = MON

20 – 25 = ACT
7.0 RISK MANAGEMENT REGISTER (METHOD 1)

RISK THE RISK AND HOW IT CAN Risk Risk Risk Control Responsibility
CODE OCCUR likeli- conce- score Adequacy
hood quences
Project Risk
P05/01 Unplanned Man-Power Down – 4 3 12 SAT -Project
due to diseases or accidents Manager
P05/02 Delay in obtaining Copyright 3 5 15 MON -CAE
and Patent – Involving different
countries and organization -Project
which will delay the process Manager

Functional Risk
F05/03 Students Inability to Use due to 5 4 20 ACT -QA director
Dizziness and Nausea

F05/04 Reduced Awareness on 2 4 8 SAT -QA director

Surrounding – Possibility of
hitting or falling down
Resource Risk
R05/05 Personal or Organizational 3 5 15 MON -Project
Data Leak Manager

R05/06 Delay to develop custom VR 3 4 12 SAT -CAE

device – since it is not readily
available in the market, it must -Project
be designed uniquely Manager
Organizational Risk
O05/07 ROI could not be met at the 5 3 15 MON -Finance and
planned time – since it is for Accounting
educational purpose, the
revenue will be a second factor
O05/08 Change of Higher Management 2 5 10 SAT -Dean
or Sponsor
Technical Risk
T05/09 System Collapses or Hang 3 5 15 MON -Project
during operation Manager

T05/10 Lack of Internet Signal (Low 5 5 25 ACT -Project

Wifi Strength Manager
 8.0 RISK MATRIX KEY (METHOD 2)

5 O05/07 F05/03
Very Much
Likely

L 4 P05/01
i More
k Likely
e
l
3 R05/06 P05/02
i
Likely R05/05
h
T05/09
o
o 2 F05/04 O05/08
d Least
Likely

1
Unlikely

1 2 3 4 5
Insignificant Minor Moderate Major Catastrophic

Risk Consequences
9.0 RISK EVALUATION
Upon analysing the risk into scores and matrix form, it is be much convenient to
prioritize the risks from most catastrophic to the least significant risk. This will helpful
for the team to find out ways to prevent the risk from arising at any point of the
project. Even if they arises, there will be ways to strategize those risk in the most
efficient manner.

9.1 PRIORITY RISK TABLE

Risk RISK Risk description
Priority CODE

1 T05/10 Lack of Internet Signal (Low Wifi Strength

2 F05/03 Students Inability to Use due to Dizziness and Nausea

3 P05/02 Delay in obtaining Copyright and Patent – Involving

different countries and organization which will delay the
process

4 R05/05 Personal or Organizational Data Leak

5 O05/07 ROI could not be met at the planned time – since it is

for educational purpose, the revenue will be a second
factor

6 T05/09 System Collapses or Hang during operation

7 P05/01 Unplanned Man-Power Down – due to diseases or

accidents

8 R05/06 Delay to develop custom VR device – since it is not

readily available in the market, it must be designed
uniquely

9 O05/08 Change of Higher Management or Sponsor

10 F05/04 Reduced Awareness on Surrounding – Possibility of

hitting or falling down
 10.0 TREAT THE RISK

Upon prioritizing the risk, there are decision to be made to prevent the risk from
arising, or in the case of unavoidable circumstances, what are the countermeasures
to be taken by the team will be listed in the table below for each risk.

Risk Code: T05/09

Risk identified and likely impact :
System Collapses or Hang during operation

Summary of recommended response

When we have specific software systems (in our case, VR), there are many reasons for this, but the
most common ones are due to overuse, which happens when we use them for extended periods of
time and results in system failure in the hardware department. Technical failures always cause a lot of
loss and stress in an organisation.
Action plan
Regular maintenance checks with check sheets.

Resource requirement
A skilled Man power of 3-5 persons required.

Responsibility
Project Manager

Timing
3 to 5 hours

Reporting and monitoring required

Yes
Risk Code: T05/10
Risk identified and likely impact
Lack of Internet Signal (Low Wifi Strength)

Summary of recommended response

Poor WIFI or poor internet connection can lead to technical glitch which disrupts students during their
course learning. Sometimes it may delay the plan of action of the students and lecturers due to lack of
internet or low WIFI strength

Action plan
A Wi-Fi analysis programme is the best approach to determine your router's optimum network
settings if your Wi-Fi is terrible. Consider looking into your Wi-Fi issues if you still have unstable
internet after changing the channel on your router. Installing modern router or Installing WIFI extender
or Installing long range router; can also prevent disruption in low signal strength.

Resource requirement
Man power of 2 persons required from IT department

Responsibility
Project Manager

Timing
2-3 hours

Reporting and monitoring required

Yes
Risk Code: O05/07
Risk identified and likely impact
ROI could not be met at the planned time (Moderate)

Summary of recommended response

Installing such applications in the university’s system can be quite costly. However, in this case, this is
not the major issue. The question of the hour is whether the university will be able to get its ROI i.e.,
return on investment. As this project is meant for academic utilizations, the ROI will be in terms of the
educational standards like enhanced understanding and higher grades among students.

Action plan
Before implementing the project entirely, there are some small-scale schemes that can be carried out
to check the students’ acceptance towards the concept of virtual learning and to familiarize them with
this idea. This can be achieved by installing a variety of ready simulation software programs for the
aircraft interior on the university’s computers in any of the computer labs. Later on, we will be able to
determine the students’ level of comprehension through tests and questionnaires.

Resource requirement
- Financial Advisor
- Technical Analyst
- 1 person from the Academic Services Section (AcSS)

Responsibility
Financial Advisor

Timing
1-2 months

Reporting and monitoring required

Yes
Risk Code: O05/08
Risk identified and likely impact
Change of Higher Management or Sponsor (Catastrophic)

Summary of recommended response

Each person has his/her own point of view, regarding the VR, some may be in favour of it and some
may not. This means that a newly appointed employee(s) in the higher management or a new
sponsor may not be supporting it.

Action plan
On condition that the higher management changes, for instance, the Dean or Deputy Dean of
Academics, the previous or current personnel in charge (Dean or Deputy Dean) will have to notify the
newly appointed person in charge about the project and that it is for academic purposes. However, if
the sponsor changes, our team will provide the new sponsor with our project charter document. In
addition to that, a report of the results and changes in the students’ grades and the university’s
learning system along with numerous student and lecturer feedbacks regarding the smart learning
system will be provided to them. This will demonstrate how much the students and the university staff
as well, benefited from this system. This will all be done through UniKL MIAT’s Dean.

Resource requirement
- Project Manager
- Financial Advisor
- Technical Analyst
- Chief Technician
- QA Director
- 1 person from the Academic Services Section (AcSS)
Responsibility
Dean

Timing
2-3 weeks

Reporting and monitoring required

Yes