Many asset models provide defect checks, also referred to as DOC4000 checks. As updated information is collected and processed, DOC4000 uses these defect checks to identify inconsistencies in the collected information. These inconsistencies can indicate a potential configuration issue. You can then assign a defect to someone to investigate and resolve the issue.
For example, you may be cleaning up CL programs that are no longer needed. However, you may miss a tag that references a removed CL program. DOC4000 can identify this reference for you. DOC4000 can also detect data collection that provides incomplete or inconsistent data.
An asset model can identify a set of defects, such as disabled programs or disabled I/O ports. The Implementation Guide for each asset model provides details about that asset model, including the defect checks it provides. For more information about an asset model, see the Implementation Guide for that asset model.