Wish - Improved ECO routing

[sathersc23]

Since we can't customize ECO routing (no the approval lists are NOT sufficient, they are just barely passable), it would be nice if we could get a route to reject back to work from review.

A lot of times we find minor updates during the review process, things that are "acceptable" to the engineering checker, but not acceptable down-stream.

Right now we have to reject the ECO, reopen the ECO, and re-submit to work. This takes 2 people (the rejecter and ECO admin) and 3 operations. We find it either gets delayed because the ECO admin has to get involved, who is usually busy doing his own work, or because the folder gets physically handed off without all the corrosponding electronic steps to get from a->b.

Please please please please please consider updating the ECO routing to make it as flexible and powerful (or more) as you have with the file/folder/project lifecycles. Being able to setup custom (dept.) routing and group level (instead of user) signoffs would get you 95% of the way to having a fantastic ECO system that we could build into a fully electronic 140001 capable tool.

Thanks, 

[mollons]

Have you considered turning on the check state for ECOs?

You can do this int eh global settings.

This adds a check state between WIP and Review, and the Check state has a transition back to WIP.

[sathersc23]

Scott,

We currently impliment the check state and use this for our engineering check. However, I would be lying if I said passing this meant the ECO was 100% ready for release. A lot of time down stream as the ECO routs for approval with each dept. signing off on it, we find issues with the ECO in some way shape or form and end up rejecting it back so we can complete the rework.

Please let us know if we somehow mis-understand the intended workflow of the check state. We're always on the look out for process improvement.

Regards,