Discovery
Device Data Quality
Measure the completeness of device records and identify gaps that need to be filled before migration planning can proceed.
Overview
Device Data Quality scores every device in your CMDB against mandatory and suggested fields, assigning each a score from 0–100% and a quality tier. Unlike Application Data Quality (admin only), this dashboard is accessible to all authorised users — enabling the whole project team to monitor and act on device record completeness.
When to Use
- Immediately after importing devices via VMware RVTools, Nutanix, or CSV to assess completeness
- Before assigning devices to move groups — incomplete records lead to inaccurate capacity planning
- During weekly project health checks to track data quality improvement
- When a device fails a migration — incomplete records are a common root cause
Dashboard Sections
| Section | What it shows |
|---|---|
| KPI Cards | Total devices, overall quality score (0–100%), devices with all mandatory fields complete, devices missing critical data. |
| Quality Distribution Chart | Devices grouped into Excellent (≥90%), Good (70–89%), Fair (50–69%), Poor (<50%) tiers. |
| Field Completion Rates | Bar chart showing % completion rate per field. Mandatory fields shown in dark, suggested in light. |
| Device Quality Details Table | Per-device: Name, Quality Score, Quality Tier, Missing Mandatory Fields, Missing Suggested Fields, Environment, Power State. |
How to Use
1
Navigate to Discovery → Data Quality & Discovery → Device Data Quality.
2
Review the overall quality score KPI. Aim for above 80% before starting move group assignment.
3
Check the Field Completion Rates chart — find which mandatory fields have the lowest fill rates. Common gaps: Owner, Environment, Business Unit, CI Type.
4
Sort the Device Quality Details table by Quality Score ascending. Export or note the Poor-tier devices and update their records in Discovery → CMDB → Devices.
Key Fields
| Field | Description |
|---|---|
| Quality Score | 0–100% completeness score across mandatory and suggested fields. |
| Quality Tier | Excellent / Good / Fair / Poor based on score thresholds. |
| Missing Mandatory Fields | Count of required fields that are blank — must be completed before planning. |
| Missing Suggested Fields | Count of recommended fields that are blank. |
| Environment | Production, Development, Test, UAT, etc. |
| Power State | On / Off — powered-off devices in Poor tier may be decommissioned candidates. |
Quality Tiers
| Tier | Score | Recommended Action |
|---|---|---|
| Excellent | ≥ 90% | Ready for migration planning. No action needed. |
| Good | 70–89% | Minor gaps. Can be included in planning; complete suggested fields when possible. |
| Fair | 50–69% | Complete mandatory fields before assigning to a move group. |
| Poor | < 50% | Do not include in migration planning until record is improved. |
Tips & Common Mistakes
Bulk-update device fields directly in the CMDB Devices DataTable using inline edit — far faster than opening each record individually.
Powered-off devices in Poor quality tier are prime decommission candidates. Flag them in the RAID Log rather than spending time completing their records.
Mandatory field requirements are configured per project in Settings → CMDB Field Management. Ensure these are set up before using this dashboard as a quality benchmark.