The framework is divided into System Development on the left and Process map on the right. The process spans the pre-design, schematic design, detail design, and construction phases. Project Initiation receives input from H E stakeholders comprising Governance, H E B P s, and Faculties. It proceeds through Identify need for a new project, Master plan or strategic plan, and End-user Identification. End-user groups comprise academics, students, researchers, and professional staff. The process then moves to Acquire User Requirements and Consolidating End-user Requirements, marked two, producing a User Brief. Design Elements, D E, include spatial configuration, aesthetics, inclusivity and accessibility, sustainable design, connection with nature, privacy, lighting, I A Q, thermal, ergonomics, operational services, L T R enablers, and safety and compliance. These feed the User Requirements Acquisition Module, marked one, where user needs are acquired based on D E. The User Brief leads to a Co-created Project Brief containing an H E project brief and returned project brief. H E project teams comprise designers, F M s, and faculty, while external architects also contribute. The schematic design phase begins with Schematic Design Development. The schematic design proceeds to Pre-Occupancy Design Evaluation, Pro D E, which also receives input from the Design Evaluation Module, marked three, and end-user groups. End-user feedback reaches a decision point, marked four, asking whether the sketch design satisfies D E criteria. A No path returns end-user recommendations for improvements to Schematic Design Development. A Yes path produces a finalised schematic design and proceeds to Detail Design Development. The detail design returns to Pre-Occupancy Design Evaluation for further end-user feedback. A second decision point, marked four, asks whether the detail design satisfies D F criteria. A No path returns end-user recommendations for improvements to Detail Design Development. A Yes path leads to Finalised design for construction.End-user engagement process map
Source: Authors’ own work
Sharing content requires targeting cookies to be enabled. Please update your cookie preferences to use this feature.