Please enable Irrigation Manager to Import Project > Type workflow, rather than vice versa. It doesn't make any sense to start from the Type window if we're not sure what a Project has in it. If an employee is directed to import the Irrigation equipment from a specific project, why are they expected to go through all the blank equipment Types in importing equipment from one Project to another? It would make much more sense to select the Project, and then import from the EXISTING equipment Type list, not run into a bunch of dead ends and error messages selecting equipment Types that aren't on a project.
We work with municipalities throughout California and need to roll over irrigation equipment from one project to the next. Are we to maintain Templates in parallel with Projects through the design phase under a given client??
The tool would require fewer clicks to simply import Equipment from a recent project, and have that drill down to specific Irrigation Equipment Types that actually exist. If we start a second project from a Client, why do we have to go through trial and error for Irrigation equipment from a specific project? Are we expected to maintain a project throughout the course of Design phase in parallel with Templates? Seems like duplicating the workload.
Thank you,
Daniel
We work with municipalities throughout California and need to roll over irrigation equipment from one project to the next. Are we to maintain Templates in parallel with Projects through the design phase under a given client??
The tool would require fewer clicks to simply import Equipment from a recent project, and have that drill down to specific Irrigation Equipment Types that actually exist. If we start a second project from a Client, why do we have to go through trial and error for Irrigation equipment from a specific project? Are we expected to maintain a project throughout the course of Design phase in parallel with Templates? Seems like duplicating the workload.
Thank you,
Daniel