[Anthill-pro] How do manage shared Life-Cycle Models and competing status/environment configurations?

[Brian_Kelly at timeinc.com]

The majority of our projects are Java Web Apps that are deployed in the
same manner - using the Tomcat Manager. In order to reduce the amount of
duplication of maintenance in our AHP instance I created shared jobs and
workflows for building and deploy WARs.
 
In order for different projects to make use of the shared jobs and
workflows they need to be set up with the same Life-Cycle Model. This
means they also share the same status.
 
This starts to cause a problem when I need to introduce a Status for an
Environment that is specific to a set of projects but doesn't apply to
the other groups of projects using the same Life Cycle Model.
 
I'm currently experiencing this where a project needs to test their
builds out on a new non-live Production environment. Currently the Life
Cycle Model has the statuses "dev", "qa", "uat" and "prod". In order to
differentiate it self from the current live Production I'd need to
create a status called "prod-new" or something along those lines. This
new status would then show up for other projects that don't make use of
this environment. Do this for a few projects and the number of statuses
starts to get confusing.
 
How do others deal with this? I'd really like to avoid making separate
Life Cycle Models for each project which would result in lots of
duplicate jobs and workflows.
 
-brian