Practical Guidance

Overview

• Start with dependencies before fixing a downstream symptom. A display error may be caused by an AF Attribute, which may be caused by a missing PI Point.
• Use AF Templates to find repeated modeling or template-driven problems.
• Use Change History when a previously healthy object suddenly becomes unhealthy.
• Use Show missing only when you are investigating deleted, moved, excluded, or unavailable objects.
• Use suppression sparingly. Suppression is a documented exception, not a repair.
• Rerun a scoped scan after a targeted fix. Use Full Inventory when the fix crosses PI Points, AF, and PI Vision.