|
pgribben
|
 |
« Reply #2 on: April 05, 2011, 01:29:24 pm » |
|
In My world, and example is probably the best.
I have a project, which is to replace a pump. I want to be able to track all the costs of the project, but I have multiple complex tasks in differing locations.
I create a Parent with the Project Description-Replace Pump
I create 3 child work orders, one for the Engineering, one for the Mechanical path, one for the electrical path
in those children, I define the tasks-
In the Engineering Package, it would be submit documents for review (potentially service requests for vendor assistance)
If I want to work in parallel, civil, mechanical, electrical, I can create tasks and track them
In the Mechanical Package, I have materials, Items, and tasks for tagout, prefabrication, installation, post installation testing
In the Electrical Package, I have materials, items, and tasks for pulling wire, tagout, live/dead checks, post installation testing.
I would not inherit status on the child work orders, I could then track the status of all 3 paths, and have a representation of costs.
The parent child heiarchy just gives a bit more flexibility in how you track and start/stop work. There can be pitfalls, if you are doing corrective type, how do you say when the decifiency is resolved? Is it at the parent level or at the particular child that resolves the deficiency.
Hope that helps a little bit.
|
