Stage 2: Setup for implementation to the team
4.5 Stage 2: Setup for implementation to the team
By having the system to be up and running, it is now the time to implement the system to team members. The first step in this stage is to apply the configuration step in Stage 1 to the project team. The illustration of the flow diagram of this stage had been highlighted as it has been shown in Figure 4.45.
Stage 1: Setup for initial test on functionality
Step 1: Setting up the equipment Step 2: Setting up user’s account
User 1 (sender)
Step 3: Setting up shared calendar
User 2 (receiver)
User 1 (sender)
Pop-up Step 4: Setting up notification system SMS
SMS Step 5: Gathered a system feedback (next chapter)
Stage 2: Setup for implementation to the team
Step 1: Apply the concept in Stage 1 (Step 1 to 4) to the project team Step 2: Gathered a system feedback (next chapter)
Figure 4.45: Setup for implementation to the team
The configuration were then been applied to the system which been used by the officer in the project team. The organization chart for PWD’s Pulau Pinang hierarchy is given as in Figure 4.46. The unit involved in the implementation had been highlighted as it has been shown in Figure 4.47.
Director
Head of Assistant Head of Assistant Director (Building)
Director (Project)
Assistant Director
Assistant Director (Building)
Mu
(Project)
Assistant Engineer Assistant Engineer (Building)
(Project)
Technician (Building) Technician (Project)
Figure 4.46: Typical organization chart in the department
Director
Head of Assistant
Head of Assistant
Director (Building)
Director (Project)
Assistant Director
Mu
Assistant Director
(Building)
(Project)
Assistant Engineer
Assistant Engineer
(Building)
(Project)
Technician (Building)
Technician (Project)
Figure 4.47: Detail organization chart based on the equipment used
In the system setup, the ‘Assistant Director (Project)’ had been set as it was User 1 and the other team members as User 2. By having this configuration, there will
be a two-way communication from the User 1 to the User 2 and vice-versa. The illustration of this way of communication is given as in Figure 4.48. This way, any changes to the ‘Assistant Director (Project)’ event will be sent to the other team members. Also, any event changes from the ‘Head of Director (Project)’, ‘Assistant Engineer (Project)’ and ‘Technician (Project)’ will automatically sent to the ‘Assistant Director (Project)’. The illustration of this process is given as in Figure 4.48.
User 2 to User 1 User 1 to User 2
Head of Assistant
User 2
Director (Project)
Assistant Director
User 1
Mu (Project)
Assistant Engineer
Technician (Project)
Figure 4.48: Implementation involves only the person inside the dotted line
To have the above functionality, there is a need to set a configuration as in Figure 4.49. At the ‘Calendar Settings’ interface, it had been set five types of calendar
within the team which refer to general calendar ‘JKR Penang’, project ‘Al- Manshoor’, project ‘Kolej Jururawat’, project ‘UiTM Bertam’ and ‘Personal’. The
details of the project had been described in the early chapter.
The share options of each of the calendar type can be either similar or totally different configuration. In this implementation, the configurations are similar to the entire calendar. For example, the officers which shared the ‘JKR Penang’ calendar are listed in the ‘Share with specific people’ as it had been given in the Figure 4.50.
Figure 4.49: Team calendar settings
Figure 4.50: Team share calendar options
At the notification options, the officer had been set to receives the SMS each before 10 minutes of the event and immediately after the changes made to the event. The configuration interface is given as in Figure 4.51.
Figure 4.51: Team share notifications options