chip7238

Maybe I am missing something obvious here...

How is the best way to upgrade a current client's system in D-Tools without "losing" the data from the system that is in place (I say "losing" because the data is not lost, only it is not present in the current project).

For example, a client with a fairly involved system that is fully documented in D-tools would like to upgrade a few items and add some additional systems in the near future. How can I update the documentation on his current system without confusing what is new and what is already in place? Obviously, I need to keep the wiring labels and component IDs in place from the previous installation.

Ideas? What is everyone else doing with this issue? I tried to search, but couldn't find what I was looking for...

Thanks in advance!
Chip

AaronB

Well this is something that may be good to figure out. I have been deleting the items, but wish i could see the previous drawings now.. Only thing i can think of at the moment would be to copy the drawing then rename and go from there, i havent used the Rev. feature yet though maybe that would help?

Travis R

The way I do it is:

Create a new project.
New visio drawing.
Dtools>insert system (select the original job that you did for the client)


Now, your original drawings, parts, and IDs are there. Go to your project data matrix and change everything to owner furnished and clean out any misc. cost and labor (get you project cost to $0.

Now you are ready to add your new or upgrade parts, labor and misc. cost.

Additionaly, to help the techs. I change the color of all new parts to green so they can easily identify to new parts/changes.

AaronB

great idea

chip7238

This is a great idea Travis. I like to have a new project number assigned to new jobs, and your technique would allow for that as well. I did not realize that the import project retained the component ID... I would be interested to see if anyone does things differently than this.

Travis, you say create a new Visio drawing - do you have to create a blank drawing in the new project for the old drawing to be inserted from the previous project? Sorry for the ignorance here - I haven't really used the Visio capabilities yet (or the insert system for that matter). I suppose that after a number of different types of projects are in the system, it is far quicker to insert a system and simply change a few things around to fit the new project.

On a side note to Aaron - I use the revision capabilities for changes to the project. I will add/delete items and packages in a project until I get all the details I need, then I submit to the client. If additional changes are necessary after any submittal to another party, I ALWAYS create a new revision to retain a copy of work done previously - what if the client says "This one is good, but I think I DO want to go with your initial proposal..."? Simply promote that revision to be the current and go from there. I sometimes have 6-8 revisions on a project (some small changes, others large).

Note that revisions are not really intended to be used for additions or changes that are part of a new job. The revision is the driver for the change orders associated with one project. It would be a mistake to use revs any other way.

Travis R

Originally Posted by chip7238

Travis, you say create a new Visio drawing - do you have to create a blank drawing in the new project for the old drawing to be inserted from the previous project? Sorry for the ignorance here - I haven't really used the Visio capabilities yet (or the insert system for that matter). I suppose that after a number of different types of projects are in the system, it is far quicker to insert a system and simply change a few things around to fit the new project.

What works for me anyway is, create the new project and then create a new visio drawing from your companie's template. Then delete all pages (except the background, because you can't delete everything). Now insert the system that you want to upgrade.

Now there may be a different way to insert drawings and keep all of the info, but I haven't found it.

I actually use this method a lot. Our sales often times quote a job that is similar to a previous one. So maybe I just need to add a camera here and a change the displays from monitors to projectors, but everything else is the same. I just wipe out the data matrix and insert a known good and similar system, make the changes and review it with the project manager and sales. This saves me hours of design and keeps my AMX programming similar as well. It also helps the techs by keeping things similar.

AaronB

Thanks for the reply Chip.