when working in teamwork......

[Anonymous]

When working in Teamwork......should there be a .plc file for each user? or just one .plc file that could be accessed by anyone simultaneuosly?

Thanks!

[David Pacifico]

The .PLP file is the shared file that everyone signs into.
The .PLC file is the local draft file that is optional, but I would recommend, for each individual user. Each user working on a .PLC then needs to do a send and recieve to update the PLP.
Also consider signing in as a task, such as "Electical Guy" and "Wall Section Guy" instead of Joe or Jane. Then you can tell who ever to open the Electircal Guy .PLC and fix the electrical stuff.

[Anonymous]

David wrote:
The .PLP file is the shared file that everyone signs into.
The .PLC file is the local draft file that is optional, but I would recommend, for each individual user. Each user working on a .PLC then needs to do a send and recieve to update the PLP.
Also consider signing in as a task, such as "Electical Guy" and "Wall Section Guy" instead of Joe or Jane. Then you can tell who ever to open the Electircal Guy .PLC and fix the electrical stuff.

Interesting...so .PLC is an optional file when doing teamwork! Thanks David. I guess my next question for teamwork is...Should the views in plotmaker be directly imported from the .PLP file? And also....what becomes of the .PLN file from which the shared project was derived from?

[David Pacifico]

I guess my next question for teamwork is...Should the views in plotmaker be directly imported from the .PLP file?

Now this is more interesting. Yes they can be. I suspect most do it this way. But a more bullet proof way is to save the .PLP out to a .PLN and link to that to the Layout Book. This way if anything ever happens to the .PLP you have a something to fall back on. Someone can link up the Layout book independent of PLP. The downside is that it is a small extra step to overright this .PLN.

And also....what becomes of the .PLN file from which the shared project was derived from?

The beggining .PLN and for that matter the old .PLC's can be purged when you are done using them. Maybe a Project Trash folder if you want to keep everything.

[Anonymous]

We have for many years been

1. linking drawings directly to the PLP
2. Not using draft files (PLC)
3. deleting the PLN file immediately upon creation of the PLP

If you use PLC files you add extra steps to the workspace changing options. Users will need to open/save their PLC files. If the workspace needs to be changes they need to save their work in the PLC and then Send & Receive to the PLP, then change workspace. If you accidentally sign out of the PLP you must sign in again to the PLP, not the PLC. The PLC will not longer be able to S&R to the PLP when your sign-in ID changes. IMHO it is confusing for the user, error prone, and not very practical. Of course the PLC does have it's place and I think it is appropriate for remote users.

Linking drawings to the PLP has not caused any real usability problems. Saving it out to a PLN and linking to that is viable, but again its just adds extra steps to the workflow. If you're using PLCs, to then:
1. Save the PLC
2. S&R to the PLP (and get the other team members to do it also)
3. Sign into the PLP
4. Save the PLP to a PLN
5. Open the LBK
6. Update drawings (from the PLN)

I'm already tired, just thinking about it! 😉 David's method has many safeguards in place, but they're at the expense of time.

[TomWaltz]

For me, the PLC is a nice middle-ground for not doing a Send & Receive every 10 minutes but still being able to svae your work throughout the day. They are also useful if you want to go home at night and come in the next morning to the same workspace.

[Anonymous]

Eric wrote:
We have for many years been

Method 1:
1. linking drawings directly to the PLP
2. Not using draft files (PLC)
3. deleting the PLN file immediately upon creation of the PLP

Method 2:
1. Save the PLC
2. S&R to the PLP (and get the other team members to do it also)
3. Sign into the PLP
4. Save the PLP to a PLN
5. Open the LBK
6. Update drawings (from the PLN)

Method 1 seems great! no extra files floating around...straight to the point.

Method 2 seems great as well....yes...extra steps...but gives you "insurance".


I've been working towards method 1 but came across some library issues when I would start importing to plotmaker from the .PLP file. Some library parts weren't showing up. I double checked the view in the .PLP file and everything seemed to be great....but unfortunately, things weren't that great when I would import them to plotmaker. My guess...it has to do with library loading issues.

After playing around, and importing here and there...well...I ended up doing a method just like method 2. Saved the file as a .PLN and imported the views from there. Nothing was missing...so it worked out. I would like method 1 to work, maybe my libraries are mixed up or something. I might have to go back to the .PLN file and make sure things are loaded the right way ...and then share the project.

[TomWaltz]

Don't forget that in AC10, the whole "LBK" step goes away and it's all in one file. At that point, it would seem silly to have a separate PLP and PLN.

[Anonymous]

TomWaltz wrote:
Don't forget that in AC10, the whole "LBK" step goes away and it's all in one file. At that point, it would seem silly to have a separate PLP and PLN.

Good point

Another reason added to my list for wanting to switch to 10!

[Anonymous]

junior wrote:

TomWaltz wrote:
Don't forget that in AC10, the whole "LBK" step goes away and it's all in one file. At that point, it would seem silly to have a separate PLP and PLN.

Good point

Another reason added to my list for wanting to switch to 10!

There should be a few dozen by now