I get asked this question a lot too. Sometimes it comes down to understanding what lifecycle event they are trying to capture with the Status field so you can tell them what Status to use.
I relate every Status value to a lifecycle event that happens to a CI/Asset. Generally speaking, once they see that in conjunction with utilizing Status Reason codes, it resolves the need for adding Status values. Some industries (like the government sectors) use different words to describe the Status at a particular junction, so that can be a challenge and then sometimes people don't understand that the Status belongs to the Lifecycle of the thing - they might think it's the status of support or the status of the master part, etc. IMO, most of the time this question is just an education gap between process and the tool. Janie On Wed, Jan 21, 2015 at 12:15 PM, Ray Gellenbeck < ray.gellenb...@redmangollc.com> wrote: > Thanks to both of you and I agree 100% Rick. The client has been strongly > warned against this but I wanted to have my Plan B ready in case they > ignore counsel. We'll see what they decide. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
