Samuel Pendreigh

SARC 362 Protocol Report Project 1 Samuel Pendreigh- Table of Contents 1. Scope of Report................................................................................................................................................... 1 2 Project Information .................................................................................................................................................. 1 2.1 General ............................................................................................................................................................. 1 Key Contacts ........................................................................................................................................................... 1 2.2 Project Schedule................................................................................................................................................ 2 3 Group Protocol ........................................................................................................................................................ 2 3.1.1 Digital Environment ........................................................................................................................................ 2 3.1.2 Information Exchange..................................................................................................................................... 2 3.1.3 Project Goals .................................................................................................................................................. 2 3.1.4 Quality Control ............................................................................................................................................... 3 3.2 Meetings ............................................................................................................................................................... 3 3.3 Job Sheets ............................................................................................................................................................. 3 3.5 Conduct Contract .................................................................................................................................................. 4 3.9 Roles and Responsibilities ..................................................................................................................................... 4 4 Protocol Success Analysis .................................................................................................................................... 4 References .................................................................................................................................................................. 4 Appendices ................................................................................................................................................................. 5 1. Scope of Report The following documents the methodology adopted to enable group work. It states the way in which the group will work from a digital standpoint as well as assess the success of the techniques implemented. 2 Project Information 2.1 General Project Name: Project 1.1 Residential Client Project Owner: ETCS Project Address: 124 – 128 Rangithi Crescent, Takapuwahia, Porirua, 5022 Brief Project Description: 2 Storey Residential Build with Garage Contract Type: Design & Cost Contract Start Date: March 2017 Key Contacts Role Client Discipline N/A Contact Name Tobey Course Co-Ordinator N/A Fabricio Chicca Project Manager BBSc Samuel Pendreigh Architect 1 ARCH J’Adoube Elkington Architect 2 ARCH Griffin Tozer Contact Details----Facebook.com-Facebook.com- Architect 3 ARCH Rory Wilson-Cartwright Landscape Architect LND Sam Findlater Facebook.com-Facebook.com-Facebook.com 2.2 Project Schedule Project Phase Precedent Study Design Final Design Costing Modelling/Technical Details Content Refinements Content Deliver Estimated Start Date 13/03/2017 20/03/2017 27/03/2017 03/04/2017 10/04/2017 17/04/2017 24/04/2017 Estimated Completion Date 20/03/2017 27/03/2017 03/04/2017 10/04/2017 17/04/2017 24/04/2017 30/04/2017 3 Group Protocol 3.1.1 Digital Environment The group will operate collaboratively and save all work on a shared folder located in T-Drive – Folder name: SARC 362 GROUP 30 INFO. Members must relinquish work on REVIT files after every sessions of work. If more than one member is working on the REVIT project file at any given time then relinquishing must occur every 20minutes. Group design work and final work will occur on; (1) (2) (3) (4) Revit AutoCad 3Ds Max Excel Individuals are encouraged to use other programs to assist in this process as long as the final outcome is completed in the 3 listed programs. All files created which are uploaded to T-Drive will be saved as a shared file so appropriate editing and access can occur by all members. 3.1.2 Information Exchange Identifies the Software and File Format which the group will use during certain aspects of the project. BIM Use Schedule Specification Responsible Parties ARCH 1 – 3 LND ARCH 1 -3 LND Rendering ARCH 1 - 3 3Ds MAX Revit - .3ds .rvt Cost Estimation ARCH 1 – 3 LND PM Excel 2013 .xlsm Design Software Version File Format Revit 2017 .rvt Revit 2017 .rvt 3.1.3 Project Goals Expected outcomes from individuals for the project in relation to the digital environment. Priority Goal Description BIM Uses High Optimized Design which takes into consideration Clients stated requirements and is under clients budget High Medium Technical Drawings which inform Client Group Members Expertise are taken into account and optimized Design Reviews and Cost Estimation through Specification Design Review and Authoring Phase Planning and Skill Utilization 3.1.4 Quality Control Quality control will occur weekly as part of Thursdays scheduled meeting. All content from the weeks work will be present. Critical checks & discussions will be led by the Project Manager and ARCH 3 as stated by the Roles and Responsibilities Sheet on the quality of work (See Heading 3.5). Checks will consist of; Visual Revit Check: See that no unintended components have been included. Job Sheet Check: See that all delegated jobs have been completed by members in the Job Sheet Register. If required, changes and work improvements will be requested and made and then shown on Mondays scheduled meeting. 3.2 Meetings Meeting Type Facilitator Required Attendees ARCH 1 – 3 LND PM Required Technology Revit Frequency Location Time Weekly VS3.23 Mondays 12.40pm PM ARCH 3 ARCH 1 – 3 LND PM Revit Weekly VS2.36.A Thursdays 4.30pm PM ARCH 3 ARCH 1 – 3 LND PM Client One-off VS2.04 10/03/-pm 1)Week work PM Schedule/Protocol 2)Weekend Work Review 1)Progress Review 2)Weekend Work Goals 3)Quality Control Client Meeting Meetings as stated above will occur twice a week at the proposed fixed agenda times Members will bring content to the meeting which they wish to discuss on correlation to current work and future work defined by the Gantt chart. No time limit will be placed on meetings however all content to be covered should be completed by a maximum of 1.5hrs of meeting starting. All members will attend meetings unless prior notice is given, if a member cannot make a meeting the discussed topic will be communicated to them by the Project Manager. All meetings will also be register and uploaded to T-Drive>SARC 362 GROUP 30 INFO>Timetables and Management>Meeting Register so that meeting topics can be revised. Meetings are registered by the Project Manager and uploaded to T-Drive within 1 day of minutes being recorded. 3.3 Job Sheets Job sheets will be located in T-Drive>SARC 362 GROUP 30 INFO>Timetables and Management>JOB SHEETS and will be filled out by individuals responsible for that task as defined on the sheets to keep an updated register of the work needing to be completed. Job sheets will be edited and discussed on Thursday’s meetings to provide and establish challenge yet attainable goals for each member to push the quality of their work (See Appendices – Figure 1) 3.5 Conduct Contract A contract will be produced and signed by all members so that the listed requirements are clear and agreeable upon by all members to create a sense of responsibility for the digital and non-digital group work. This will be located in TDrive>SARC 362 GROUP 30 INFO>Timetables and Management>Contract (See Appendices – Figure 2) 3.9 Roles and Responsibilities A Roles and Responsibilities sheet will also be produced with similar intentions of the contract. This will specifically state your role and expected responsibility for certain tasks and parts of the project. This too will be located in TDrive>SARC 362 GROUP 30 INFO>Timetables and Management>Roles and Responsibilities of Individuals2. If there is any concern or uncertainty of the task required by your role then seek the communication channel for a resolution (includes grey areas – however there shouldn’t be any) (See Appendices – Figure 3). All Roles and Responsibilities defined by the sheet are to be complete in correspondence with the Gantt Chart. 4 Protocol Success Analysis The protocol provided did not work as efficiently as hoped. The addition of job sheets half way though the project did help members keep up with work however not by a large amount as hand-in dates still had to be adjusted to meet work flow. Where this could be improved for the next project could be ensuring no boundaries to work are created by clearly issuing the critical paths required for a week’s work (Baiden). Relinquishing the model provided problems until members became used to the process. Communication is essential and was at an appropriate level throughout the project with all members correctly following the “information exchange matrix” with the respective programs. Problems and queries within the group forums were clearly, effectively and freely communicated during meetings. Team dynamics were acceptable due to their being an atmosphere of a non-blame culture in the group which boosted people’s confidence to question certain methods and critically engage. This assisted with improving “quality control” as people remained professional when critical analysis took place and were not offended when disagreements happened as there was a group realization that it was for the benefit of the group. Meetings however could be improved as a total number of 6 meetings where missed by 3 individuals which meant that only 66.7% of the meetings had full attendance, ideally this should be at 95-100% so that all members are on the same page. This is as by doing so it will reduce the number of situations where work progress becomes temporarily halted as there was at times significant delays in conveying the information discussed at meetings such as drawing requirements for the week. Members, although they did not always keep up with work goals at times, knew what was required and did not lack motivational presence, which along with the team dynamics, which resulted in no conflicts arising. One of the most essential tools which appeared to work the best was the “Contract of Conduct” and “Roles and Responsibilities” sheet. Reasons for its success are closely attributed to the fact that all members had an influencing and collective factor on what should and should not be included/made their role. This created mutually beneficial outcomes through a highlighting one attainable goal which was defined in the contract scope (Baiden). References  Baiden, Bernard. Price, Andrew. The effect of integration on project delivery team effectiveness. ScienceDirect. ELSEVIER < https://blackboard.vuw.ac.nz/bbcswebdav/pid--dt-content-rid-_1/courses/201701.SARC-/The%20effect%20of%20integration%20on%20project%20deliver y%20team%20effectiveness.pdf >  Baiden, Bernard. Price, Andrew. The extent of team integration within construction projects. ScienceDirect. ELSEVIER < https://blackboard.vuw.ac.nz/bbcswebdav/pid--dt-content-rid-_1/courses/201701.SARC-/The%20extent%20of%20team%20integration%20within%20cons truction%20projects.pdf >  Project Management Methodologies, Project Management, Projecmanager.com, 17/04/2017 < https://www.projectmanager.com/project-management > Appendices Figure 1: Job Sheet Template Figure 2: Conduct Code Contract Figure 3: Roles and Responsibilities