This is not gonna help you w/ teamwork, but just to share my view:

I have a two person office as well, and I did TRY to work with teamwork to no avail. It just didn't make sense for me. Too many restrictions on who can do what and not, too much setup work involved for a small firm.

When I had it going briefly, it was a full sign in w/ full authority on one person - except maybe one drawing (one layer for all the notes for example in reflected ceiling plan) or one layout signed out to the other person.

After a while though, the sign-in out of whatever layer that other person needed to use with the confusion of multiplying plc files everywhere (not to mention the times when I had to make a new fill pattern or a composite or a linetype or even a layer! - everybody has to sign off, and team leader sign in with exclusive access to make any attribute) kind of became more of a hassle than dividing work project by project. I do project A in the morning while you do project B, then we switch, etc...

When there is only one project to work on with a urgent deadline, I just make a 'temporary' copy file for the other person to work on, and later imported the work into the master pln file manually. Also, another option is for that person to work on a separate file, and I bring it into the master file by hotlinking the other's mod file.

Anyway, if you are very disciplined, have a lot of passion for AC, and have TIME to play around, then I think you can eventually learn to do it without professional help. For me, for a two person office, the time invested to set up plus the efforts required to maintain that systematic organization with ever varying types and scales of projects (I think this is the key), does not seem more effective than the old fashioned / manual method I have resorted to.... for now.

Don Lee,

I'll throw my 2 cents into the ring. I've worked with teamwork on and off for about 2 years now, on projects with up to 5 or 6 people and more recently on projects with 2 people. I know I'm not using all the capabilities of teamwork, but I think my system works well for 2 people in the residential firm I work at. I doubt this would work as well for larger groups.

1) team members sit next to each other (or very close by) to facilitate communication and every morning discuss what the tasks are for the day. Knowing what everyone is going to do really makes things so much easier.
2) Have two layer combinations for sign-in and splitting up work.
I call mine --interiors-- and --exteriors-- so they appear at the top of the list. And yeah, they basically split the layers between interiors and exteriors (with interiors also having electrical layers and exteriors having all the structural layers plus whatever else can be cleanly divided into one or the other).
3) If the work can't be cut by layers for the day, we'll slice the building either by stories or in half with a marquee.
4) Then have at it.

If you need to make changes to things not in your space, write them down to change later, or go over and change them on the other machine. It's faster to stop the other person for 3 minutes than to sign in and out, etc. I find that someone can invariably get the model with exclusive access either at the end of the day or at the beginning (or at lunch if there's a crunch). This all goes back to the better you can plan out the work in realistically doable chunks the easier teamwork will become. If teamwork becomes first come, first serve, what are you working on these days? then you'll be in a world of hurt.

Oh, one last thing. Anyone can sign in as the team leader, but if one of the people is in charge of the overall file (not necessarily the person in charge of the project), that'll help keep things clean, organized, and humming along. Hope that helps.

If anyone has strong disagreements or recommendations with this process let me know, because I'm always interested in doing things more efficiently. And I am/will be teaching this process to the other 16 ArchiCAD users at my firm so I'd rather not have to reteach too much!!!

plan plan plan work work work

Sounds very realistic to me. The Teamwork specific layer combinations are a big help IME.

Cheers,
Link.

I originally used teamwork without layer combinations for sign-in and it was a hassle every day fighting over layers, yelling at people (or wanting to yell at people) for not paying attention and taking too many layers or the wrong layers or layers they didn't need...

The five, ten, fifteen minutes it takes to set up the combos at the beginning of the project are completely worth it (and then once they're in the template file... priceless). And on a larger team I would imagine the benefits increase.