• No results found

System requirements

In document data) on the construction site. (pagina 81-86)

5. Development of a New Quality Assurance Process and System

5.2. System requirements

Quality Assurance system requirements can be divided into two categories, namely functionalities and experiences. Functionalities refer to possibilities/facilities in the system, and experiences refer to how the system is experienced by the user.

5.2.1. Required System Functionalities

Based on the results from the interviews which are shown in Appendix VIII the functionalities are presented in Table 5 below. In this table, the functionalities are listed indicating whether the functionality is already included in the current system or the new QA system. These new QA system functionalities are based on the results from Chapter 4.

Table 5 – New QA system functionalities

Besides these new QA system functionalities based on the interviews, there are also new QA system functionalities based on the type of activity. These activities are given in the process models in Chapter 5.1. This includes the new QA system functionalities and experiences. These are the following: Inspection list (1); Task follow-up in case of deviation (2); Registering an error during work (3); Registering a completed building component (4); and Business office (5);

In Chapter 5.1, the new QA process models are given. The new QA system functionalities are included in these process models. To give a clear picture of how these functionalities are arranged in the processes, a list is given below. The new QA system functionalities for the new QA system listed in Table 5 are listed below in the five different processes during the execution phase.

New QA System Functionalities Current

System

Desired System Linking photos and comments to location on construction drawing (1) Sent captured photos and comments to relevant person within the system (2)

Share insight in the system to persons (3)

Use of a tablet on the construction site (4)

Link photos and comments to walls, ceiling and other BIM objects (5) Categorize photos and comments to the relevant subcontractor (6) Authorise the functionalities that people are allowed to use (7) Use tablet for inspection list out of the construction office (8)

Clear overview in the system of the made checks (13)

Function to walk digitally through the construction (14)

Structure with a timeline with a clear view of what, whom, and when must do (17) Flow-chart for notifying or giving insight after checking or uploading photo's (18)

3D model implementation (19)

Augmented Reality function for visual inspection (20)

Page 81 of 282 1. Inspection List

i. The use of a tablet on the construction site (4)

ii. Use of tablet/mobile for the inspection lists outside the construction site (8) iii. Categorising photos and comments to the relevant subcontractor (6)

iv. Clear overview in the system of the inspections carried out (13) v. Notifying the progress of the inspection (18)

vi. Task follow-up in case of deviation

vii. Structure with a timetable with a clear overview of what, who, and when to do something (17)

2. Visual Control

i. Digitally walk through the buildings (14) ii. Visualisation of the building project in 3D (19)

iii. Augmented Reality function for visual inspection (20) iv. Notification of the progress of the inspection (18)

v. Task follow-up in the event of deviation

vi. Structure with a timetable with a clear overview of what, who, and when to do something (17)

3. Fault during construction

i. Registering an error during work

ii. Sending captured photos and comments to the relevant person in the system (2)

iii. Categorise photos and comments to relevant subcontractor (6)

iv. Linking photos and comments to walls, ceiling and other BIM objects (5) v. Notification of the progress of the inspection (18)

vi. Task follow-up in case of deviation

4. Recording a major completed building component i. Registering a completed building component

ii. Linking photos and comments to the location on the construction drawing(5) iii. Structure with a timetable with a clear overview of what, who and when to

do is missed in the new process (17) 5. Business Office

i. Sharing understanding of the new system with individuals (3) ii. Authorise functionalities per user (7)

iii. Notify progress of inspection (18)

Page 82 of 282 5.2.2. Required user Experience

Based on the interviews, the following user experiences on the new QA process shown in Table 6 were mentioned. These new QA User experiences on the QA process are based on the results from Chapter 4.

Table 6 - New QA User experiences on Qa process (Interviews)

Based on the literature study, the following new QA user experiences on the new QA process shown in Table 7 were mentioned.

Table 7 - New QA user experience on QA process (Literature)

In Chapter 5.1, the new QA process models are given. The new QA user experiences are included in these process models. To give a clear picture of how these experiences are arranged in the processes, a list is given below. The new QA user experiences for the new QA process listed in Tables 6 and 7 are listed below in the five different processes during the execution phase.

1. Inspection List

i. Quality assurance by means of the inspection lists ii. User-friendliness of the system (15)

iii. Communication with task scheduling

iv. Detection of errors that normally go unnoticed (L1) v. Saves time needed for inspection (L2)

New QA User Experience on QA process (Interviews) Current System

Desired System Feedback the results from quality assurance for future projects (9) Clear who is responsible when a client sends a picture or comment (10) Clear overview for client when subcontractor solves problem (11)

Intensive quality assurance during execution phase (12)

High user-friendliness with simplified steps (15)

Ready-made package for the executor on the tablet (16)

Augmented Reality function for instruction (21)

Give a quality value to subcontractors (22)

New QA User Experience on QA process (Literature) Current System

Desired System

Discovery of errors that normally go unnoticed (L1)

Saves time needed for visual inspection (L2)

Clear overview of the project's progress (L3)

Clear representation of the construction project (L4)

Monitoring of activities and tasks at the construction site (L5)

Detection of deviations on the building site (L6)

Providing instructions for the execution (L7)

Effective communication between management and subcontractor (L8)

Page 83 of 282 vi. Clear overview of project progress (L3)

vii. Ready-made package for the contractor on the tablet (16) viii. Quality assurance during implementation phase (12)

ix. Demonstrating the quality delivered x. Content of inspection lists

xi. User-friendliness with simplified steps (15) 2. Visual Control

i. Performing a visual check

ii. Using AR for communication and task monitoring (L8) iii. Detection of errors that would normally go unnoticed (L1) iv. Saves time needed for visual control (L2)

v. Clear overview of project progress (L3)

vi. User-friendly system with simplified steps (15)

vii. Ready-made package for the executor on the tablet (16) viii. Quality assurance during implementation phase (12)

ix. The AR functionality has added value

x. Clear representation of the construction project with AR (L4)

xi. Monitoring of activities and tasks on the construction site with AR (L5) xii. Detection of deviations on the building site with AR (L6)

xiii. Giving instructions for execution with AR. (L7) 3. Fault during construction

i. User-friendly system with simplified steps (15)

ii. Ready-made package for the performer on the tablet (16) iii. Quality assurance during implementation phase (12)

iv. Clear responsibility in case of fault notification by client (10) 4. Recording a major completed building component

i. User-friendly system with simplified steps (15)

ii. Ready-made package for the performer on the tablet (16) iii. Quality assurance during implementation phase (12) 5. Business Office

i. Clear responsibility in case of fault notification by client (10) ii. Overview for principal when subcontractor solves problem (11) iii. Feedback of quality assurance results for future projects (9) iv. Give quality rating to work of subcontractors (22)

5.3. Sub-conclusions

The new proposed QA protocol has been developed in this chapter and is in accordance with all proposed functionalities and experiences of Chapter 4. The new WKB Act has also been taken into account. In Appendix X, the process model of the developed QA protocol is attached.

Page 84 of 282

Page 85 of 282

In document data) on the construction site. (pagina 81-86)