AF Users often create new attributes updated by analyses, but fail to give the attribute an output PI tag. As a result, caching performance drops and analysis engine startup time increases. As an checkbox option, AF Admins should be able to enforce that attributes updated by an analysis must be connected to an existing tag or the user will not be able to check in the change. If the tag exists and the change checked in, but the tag is accidentally deleted at a later time, then the analysis will be automatically disabled and an error logged as not to impact performance.