Hierarchy

Hierarchy is an order which is used to progress a certain element through logical steps i.e. in a typical computer you have a file which is stored in a folder which is then stored on a drive.
This means you can find your information simply by following the hierarchy of: C:\simon\hierarchy.exe

Governments have a hierarchy from the prime minister downwards and probably the most common and well known hierarchy is in the military where a rank is assigned to each soldier and they must follow orders accordingly.

Hierarchy is also present in our collaborative group with myself being labelled the team leader. However, whilst this may be relevant to solving disputes amongst members, what I have learnt is that the real team leader is the person who continually ensures that the project is heading towards the desired outcome. In this regard, whilst I have done my best, our group tutor Matt has really been the group leader.

Hierarchy in relation to our building:

The building hierarchy consists of a square superstructure turned diagonally on a podium to orientate its forecourt symbolically towards parliament. The superstructure consists of vertical service cores carrying long span roof trusses in a crossover pattern which supports a glazed dome at the centre.
The glass dome provides light to the central open space while the enclosing walls are formed by long span beams with glazing in between attaching to the leg of the square cross. 3 of the enclosed 4 quarters of the cross are occupied by the circular court chambers while the remaining quarter forms the entrance.

The building structure reflects a social hierarchy in that the base contains the administrative offices and services while the upper levels accommodate barrister’s and judges chambers. It could also be claimed that the glass dome then extends the hierarchy to the heavens in a subtle reminder that there is only one other power higher than the courts. Very medieval in concept and reminiscent of the great cathedrals of Europe.

REFERENCES:
'Architecture for the new world. The work of Harry Seidler'
By Peter Blake
Horwitz Australia Ltd., Sydney
Wittenborn and Co.,New York
Karl Kraemer Verlag, Stuttgart

Intent

Intent to me means what I intend to achieve and how I intend to achieve it.
My intents for this collaboration project are:
* To learn how to work in a team environment to achieve an outcome.
* Improve my skills in new areas of computing (UT3, wikis etc)
* To improve my presentation skills.
* Finally to improve my skills in researching and presenting a building with no detailed and specific information.
* And of course to pass my subject.......

With all of the above combined I intent to be a more employable person with a wider range of skill sets and collaborative skills than other potential applicants.

ACHIEVING MY GOALS:

Working in a team environment
'Projects often require that people work together to accomplish a common goal; therefore, teamwork is an important factor in most organizations. Effective collaborative skills are necessary to work well in a team environment. Many businesses attempt to enhance their employees' collaborative efforts through workshops and cross-training to help people effectively work together and accomplish shared goals.' (1)

With the above quote in mind, this subject has become a 'workshop' and 'cross training' which will help us learn to work together to achieve our desired outcome. How I intent to improve and learn in this area is simply by participating with my team and completing my set tasks which will in turn teach me some of the pitfalls of collaborative work and also show my strengths and weaknesses in the area.

Improving my skills in computing
My intentions are to conquer new technologies such as UT3, wiki's and other collaborative tools, along with new software encounted in video editing and presentations.
I will achieve this by completing tutorials given to us along with my own research from several internet sites. With this as my base knowledge I will then start the tried and true method of trial and error within these programs!

My Presentation skills
Through the multiple presentations required I will learn as each one happens (and from observing others) the best way to keep my audience interested and awake.....
From our initial presentation I thought we did well in regards to keeping people entertained as there have been others which have been....well simply boring. I have learnt that to get your message across (no matter how good your subject knowledge is) you must keep people interested and doing so with light humour seems to be a good way to inform.

Research
Last semester I completed a subject which required the study of built buildings with heritage value, whilst in this subject we are required to research a building that was not built and as such requires guess work and comparisons of similar buildings for information. I will become skilled at this type of research through the development of our model.

This is my intent and how I plan to follow through with my intentions to get my result.

REFERENCES:
'teamwork' viewed 26th April 2008
http://en.wikipedia.org/wiki/Teamwork

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.

RECORDS

Keeping records is a crucial (although a little boring) element in collaborative work. It provides documented proof of what people are committed to, what people have said and is essential in resolving disputes when they arise….and when money is involved, disputes always happen!

A first hand real world example of keeping records (in the form of minutes in this case) for dispute resolution, was a council meeting for a medium density job I worked on a few years back, where council agreed to the colour schedule in a meeting (which ended up being built) but conflicted with a note on the drawings (a leftover that was not changed). When council insisted the roof be changed to match the drawing, a review of the minutes revealed they had actually agreed to the change and it was ruled the roof could stay as it was built.

In our collaborative work, documenting what has been agreed on is going to ensure we all pull our own weight and achieve the goals we have agreed on. The email below, which we all have, clearly shows us agreeing on the division of work amongst our team.

Architect Peter Aeberli says ‘what if the project is not running smoothly, or relationships break down and the architect, realising it has long since expended the contract fee and there is still work to do, makes a claim for additional fees, which the client rejects?’

‘This means the architect must provide evidence that the work for which it is claiming additional fees is extra to that for which the contract fee is payable. These records must be sufficient to refute any suggestion that the work
is not extra at all, but was part of the originally envisaged scope of work’

So well kept records are essential for maintaining a collaborative effort and are absolute in solving disputes where members of the project cannot agree on who is responsible for certain work.

References:

Good housekeeping Better records are the key to claims for additional fees

http://www.aeberli.co.uk/articles/PRACTICE.pdf - viewed on friday april 11 2008

Discipline

Discipline

The disciplines involved in our collaborative work to produce the proposed High court of Australia by Harry Seidler in its final form in UT3 are:

Exterior modeling

Interior modeling

Internal texture mapping

External texture mapping

Surrounding landscape mapping

Building/landscape research

Video presentation

Lighting

Animation

Image manipulation

Sound

We have each assigned ourselves to a particular disciplines from those required above and will progress our areas as they become available from our teammates prior works e.g. V has done a great external model which she can pass on to the external texture mapper and also to the surrounding landscape mapper which can all finally be added into our video presentations in a more complete form.

We will focus on our individual tasks but due to the team nature of the project pass on our effort s to teammates to help them further theres which will ultimately culminate in our final product.

The use of collaboration amongst our tasks allows us to focus our skills on one area we are good at (or push ourselves to learn new areas of development)whilst our teammates work on there specialized areas and join them together as we progress and exchange skills.

We chose our disciplines via our group emails (with surprising ease, I expected more clashing for certain tasks) with most choosing things they knew they could accomplish but some also choosing to tackle a new task they had not yet attempted which will allow a good mix of productive work in our comfort zones along with some challenging new skill sets which will require some more time and energy and brain storming amongst team members.

My personal disciplines I will tackle involve texture mapping of surrounding landscapes (something I have not done to much of with my works usually involving an interior focus), video presentation (a skill I have done on both an educational and hobby level) and Sound (I have done a little bit on my previous video presentation work).

And lastly there will be a bit UT3 editing for all of us (with some choosing to tackle it as a main focus) which is totally new to me and yet another program I will try to cram into my brain!