I wanted to start a thread where we talk about how we organize and distribute designs in WorksManager/TCC. With the workflow being almost totally through Worksmanager now, I'm more interested in that.
What i'm talking about exactly is how do you guys organize what gets put on designs, how you break them up to send out to the data collectors, handle the conflicts that arise afterwards. I feel like I am constantly resolving conflicts due to having objects in several different designs.
How I do it:
We break our designs into several different designs for each surface/utility scope, so we end up having a pond design, a parking design, a full site surface design, a landscape design, a pads design, a full site design, a water util design, storm design, sewer water design, channel design, roadway design, etc. If a project has many pieces to it, this can get pretty crazy. We started doing this to keep designs from getting too big when loaded into the data collector and keeping from too many objects being on one design.
This causes a lot of the same objects to be a part of several different designs so even if I make a small change to a curb I have to republish every single design because of it. Also, objects tend to get taken off the design all the time from editing linestrings, so I have to go back into each design and make sure all objects are still selected.
I've thought about including a site map to remedy this, but then our surveyors get frustrated from having to back out and load into several different designs because the site map is only for reference.
I'm always open to different ways of going about things and am wondering if any of you have better ways of organizing your information.
------------------------------
john chronister
------------------------------