Knowledge

Thinking of knowledge in a collaborative effort makes the following come to mind:
1 - What knowledge of the project as a whole do we possess.
2 - What individual knowledge of specific instances of the project do we each possess.
3 - What knowledge needs to be learnt in order to complete the required tasks.
4 - And finally the knowledge of the actual building we have chosen to do.

The project as a whole, I believe we came into the project with a fair bit to be learnt. But it soon became clear what would be needed to achieve the end result (our building in UT3) , but not yet the specifics of how we would achieve it. We have broken it down to choosing a building, choosing how we would create the building and then finally how we would incorporate it all into the UT3 engine.

Our individual knowledge of certain aspects of this process were also discussed and became apparent early on (V for example has excellent knowledge of 3ds max whilst Marko has exceptional knowledge of Revit). None of us had knowledge of UT3 and is something we will all gain and learn from each other throughout our collaborative effort to produce the final product.

So what we need to all learn is obviously UT3 but also increase our knowledge of existing systems to aid in the development of our building with our team members. An important aspect of the pitfalls of teamwork is also valuable knowledge to acquire. Timelines to achieve goals are critical to ensuring we are all progressing at the necessary speed to meet our final deadline.

And lastly our knowledge of the High Court of Australia by Harry Seidler and how it fits together with the surrounding landscape will vastly improve in order to complete our final task. How the building is constructed and the different materials used will all be necessary to complete the model, and studying his existing buildings help us gain an insight into what he may have intended for parts of the building with which there is no certain information.