Learn to manage BIM workflows and create professional Archicad templates with the BIM Manager Program.

Modeling
About Archicad's design tools, element connections, modeling concepts, etc.

Do you use TeamWork?

Anonymous
Not applicable
I'm curious to know how many of us use TeamWork and in what manner.

This would be an interesting piece of trivia and it might also be helpful to the GS development team. Let us know if you do or don't and why.

Thanks,
18 REPLIES 18
__archiben
Booster
Erika wrote:
What I am trying to ask is when have you found working on a solo project that will never be shared with others the occasion to switch to teamwork?
for a solo practitioner:
automatic backing up of the last <n> number of changes . . .

~/archiben
b e n f r o s t
b f [a t ] p l a n b a r c h i t e c t u r e [d o t] n z
archicad | sketchup! | coffeecup
Anonymous
Not applicable
We use Teamwork, largely in a single user environment (me). I have found it useful for the reasons of better backups but also strangely enough I enjoy the way drafts can work in Teamwork.

The interface no longer bothers me as I have gotten used to it, but I do not look forward to explaining it to the next person. Every once and a while one of the partners will log on and do some visualization or layout drafting so it nice to have the collaborative capability there when needed.

So even though we have barely scratched he surface of Teamwork's functionality, I find for a little hassle logging on in the morning the benefits are worth it in the long run even on "small" projects.
Anonymous
Not applicable
Oh yeah, I forgot. Teamwork is also cool for alternates when working solo. You can save multiple drafts of the same sign-in and later send the changes for the approved version. Of course you can also have different people working on each of the PLC. It's a bit strange having several people working on versions of the same draft (kind of teamwork inside out) but very effective.

It's especially cool with live linked views in a single layout book. Just "Read all from..." each PLC and plot/print the alternates in quick succession.
Anonymous
Not applicable
Bummer....221 view of this thread, but only 21 votes?! Come on now...cast your vote.


Anonymous
Not applicable
We used to use Teamwork on every job which involved more than one person. however, as much as I love the idea of the system, and as much as i would not want to go back to separate files, I find the lack of development in this area quite frustrating.

1) The need for exclusive access to change certain things needs to be eliminated. With people working on multiple drafts, people working at home, people on various scedules, etc... it's just too hard to get it!
2) Workspaces need to be "Saved" somehow. Quickviews, layer combinations, etc all come to the aid of workers managing all their layers and working environments during the drawing process, but there is nothing to make it manageable during sign-in. Inevitabely, people take more than they need to avoid having to do it again later, and they trip up the next person who needs the layers.
3) Typically, fixing annotations and typing schedules are tasks given to junior members of a team because they are straightforward tasks. In Teamwork... not so. If we want to generate the door schedule from the virtual building, we need to have that person edit the doors themsleves with the info, which means they need to have the walls, and they need to understand the calculate menu, and they need to understand how to export the info and format it, etc. VERY complicated for what should be a simple task. And worse, because they need the walls, no one else can get any plan work done. This is a ridiculous limitations. Similarly, if any notes are done through labels, the person needs the label layer and the layer of the original items (?!!!) once again making it impossible for someone else to carry on with related work)
4) Team leader is a necessary function, but it should be hot-swappable (i.e. I should be able to request "team leader" status from the current team leader and immediately get it if they say okay)
5) Graphisoft should be shot for the horror that was teamwork and quickviews. We will be paying for that debacle for years to come. It is criminal to have publisher, the only worthwhile upgrade in AC 7, be based on quickviews, when quickviews are computer specific. A single user would never notice this, but when several computers are working toghether, and changes to quickvies and publisher do not transfer from one computer to the next, mistakes are made. We have lost lots of time and money, and made many mistakes, because of a confused publisher updating our plotmaker documents improperly. Luckily, in AC 8 the system seems fixed, but I sure hope they never pull anything like that again.

I could go on... and I have (on the wishlists, and in discussions with the developpers), but it had been a while since I had vented on the subject.

just wanted Graphisoft to know that AC 7 was responsible for our firm going to Autocad. I tried to save it but failed.
Erika Epstein
Booster
"Miguel Ladouceur" wrote:
We used to use Teamwork on every job which involved more than one pers
1) The need for exclusive access to change certain things needs to be eliminated. With people working on multiple drafts, people working at home, people on various scedules, etc... it's just too hard to get it!

Excellent point




To me, as I read the rest of Miguel's comments it brings up another area for discussion. The division of labor needs to be re-thought and restructured working in ArchiCAD. The way to work effectively in archicad is different from how one worked by hand or with other programs. These days many of the "junior tasks" that you describe I see as being done by all team members within a well thought -out template reflecting office standards. This frees up all of us to spend our time on design, learning, gossip rags etc.

An analogy is once we dictated or wrote in long hand our letters and then the proverbial secratary typed them. They took care of formatting, gramar, spelling, looking up the address etc. We now type our own correspondence.
Erika
Architect, Consultant
MacBook Pro Retina, 15-inch Yosemite 2.8 GHz Intel Core i7 16 GB 1600 MHz DDR3
Mac OSX 10.11.1
AC5-18
Onuma System

"Implementing Successful Building Information Modeling"
Anonymous
Not applicable
Erika wrote:
We now type our own correspondence.
<<<Begin completely irrelevant reply:

Yeah, and have you noticed how our spelling and grammar has gone down the toilet?

I'm not perfect by any means, but you should see some of the correspondence we get from clients and contractors! It is really sad. We have a 3 ring binder that contains all such correspondence called the "MGA English Language Usage Guide". It's pretty funny but it helps remind us about such errors so we don't make as many ourselves.

On a related not check out www.engrish.com for further inspiration.

<<<End completely irrelevant reply:


Otherwise I agree with what you're saying Erika. In fact most "junior" people are the ones who do the "Team Leader" stuff most of the time anyway, not the actual Team Leader.
Erika Epstein
Booster
so grammar has 2 'm's ?
Erika
Architect, Consultant
MacBook Pro Retina, 15-inch Yosemite 2.8 GHz Intel Core i7 16 GB 1600 MHz DDR3
Mac OSX 10.11.1
AC5-18
Onuma System

"Implementing Successful Building Information Modeling"
Anonymous
Not applicable
Erika wrote:
so grammar has 2 'm's ?
Good catch! I mad esure Iran spelledcheck befor I submitted that lasts one. 😉