The primary contributions of each member was delegated based on their previous experience and skills. Otherwise, throughout the project there was a strong team spirit and support was frequently granted to any member rushed for time or overwhelmed with extra-curricular pressures. Deadlines were allocated on a weekly basis for target deliverables and outcomes. Weekly meetings were organised with the project supervisor, following which subsequent targets were set. This acted as the primary driver for work to be achieved throughout the project. 

 

The team communicated via two mediums: a Whatsapp group-chat and online zoom meetings. The Whatsapp group-chat allowed brief ideas and queries to be communicated quickly. The zoom meetings were held approximately three days a week and acted as progress updates where each member was given the chance to openly discuss ongoing work. All resources such as PyLESA input sheets, relevant literature and presentations were shared via a Googledrive. This allowed all members to easily access and modify ongoing work simultaneously.  

 

Focus was given to areas of work in a methodological manner. Initially, the team was split into two. Those with prior Python experience aimed to gain an understanding of PyLESA and explore its potential for the project. The others accumulated available literature and industry knowledge for applicability to the West Whins case study. This foundation led to a collaboration of knowledge throughout the project, forming ideas such as the proposed smart control. This communication formed the backbone of our project and actively encouraged creative ideas. 

 

Overall, the team’s approach to communication, organisation and methodology proved successful. By strategically forming a wealth of knowledge and communicating creative ideas in an effective manner, the key deliverables of this project and believed to be a  valuable contribution to this area of industry.