This guide explains how to identify, analyze, and understand missing values in your sensor data.
Missing values analysis helps you:
- Identify sensors with incomplete data
- Quantify missing data percentages
- Find missing data patterns over time
- Understand data completeness
- Make informed decisions about data quality
Missing values occur when:
- Sensor readings are not recorded at expected timestamps
- Data collection was interrupted
- Sensors malfunctioned temporarily
- Data transmission failed
- Data Quality Assessment: Understand data completeness
- Sensor Health: Identify malfunctioning sensors
- Analysis Reliability: Know which sensors have sufficient data
- Maintenance Planning: Identify sensors needing attention
- Open the application at http://localhost:5173
- Click Missing Values in the sidebar or home page
- Select a machine group from the dropdown
- Choose a machine group from the Select Machine Group dropdown
- The system loads available sensors automatically
- Use the sensor selector to choose specific sensors
- Leave empty to analyze all sensors
- Selected sensors appear in the analysis
Tip: Start with all sensors for overview, then focus on specific sensors if needed.
- Click Analyze Missing Values button
- Wait for analysis to complete
- Results appear in multiple sections
General Information:
- Date Range: Start and end dates of data
- Total Data Points: Expected number of readings
- Total Missing Values: Count of missing readings
- Missing Percentage: Overall completeness percentage
- Number of Sensors: Sensors analyzed
Interpretation:
- < 5% missing: Excellent data completeness
- 5-10% missing: Good, minor gaps
- 10-20% missing: Moderate, some concerns
- > 20% missing: Poor, significant data gaps
Per-Sensor Statistics:
- Sensor Name: Sensor identifier
- Data Points: Expected readings
- Actual Readings: Recorded readings
- Missing Readings: Count of missing values
- Missing Percentage: Sensor-specific completeness
Visualization:
- Bar chart showing missing percentage per sensor
- Sorted by missing percentage (highest first)
- Color-coded for quick identification
Use Cases:
- Identify sensors with most missing data
- Compare completeness across sensors
- Prioritize sensors for investigation
Interval Information:
- Start Time: When missing period began
- End Time: When missing period ended
- Duration: Length of missing period (hours/days)
- Sensor: Which sensor had the gap
Longest Intervals:
- Shows sensors with longest continuous missing periods
- Helps identify major data collection issues
- Useful for understanding system downtime
Interpretation:
- Short intervals (< 1 hour): Minor gaps, likely normal
- Medium intervals (1-24 hours): Moderate issues
- Long intervals (> 24 hours): Major problems, investigate
Time Series Visualization:
- Chart showing missing values across time
- Identifies patterns in missing data
- Shows when data collection issues occurred
Patterns to Look For:
- Random gaps: Normal sensor behavior
- Periodic gaps: Scheduled maintenance or system issues
- Continuous gaps: Sensor malfunction or system downtime
- Increasing gaps: Degrading sensor or system
- Low missing percentage (< 5% overall)
- Even distribution across sensors
- Short, infrequent gaps
- No systematic patterns
- High missing percentage (> 20% overall)
- Concentrated in specific sensors
- Long continuous gaps
- Systematic patterns (same time daily, etc.)
High Missing Percentage:
- Investigate sensor hardware
- Check data collection system
- Review transmission logs
- Consider sensor replacement
Long Missing Intervals:
- Identify root cause (maintenance, failure, etc.)
- Document system downtime
- Plan preventive measures
- Consider backup sensors
Systematic Patterns:
- Review maintenance schedules
- Check system configuration
- Investigate environmental factors
- Adjust data collection settings
- Regular Analysis: Check missing values periodically
- Set Thresholds: Define acceptable missing percentages
- Document Issues: Record reasons for missing data
- Monitor Trends: Track missing values over time
- Take Action: Address sensors with high missing rates
- Understand Expected Frequency: Know how often readings should occur
- Check Data Range: Ensure sufficient data for analysis
- Review Sensor Status: Know which sensors are active
- Focus on High Missing Rates: Prioritize sensors with most issues
- Check Time Patterns: Look for systematic gaps
- Compare Sensors: Identify outliers
- Document Findings: Record missing value statistics
- Investigate Causes: Determine why data is missing
- Plan Improvements: Address identified issues
- Re-analyze: Check improvements after fixes
Observation: Single sensor has 30% missing values Action:
- Check sensor hardware
- Review sensor-specific logs
- Consider sensor replacement
Observation: All sensors show gaps at same timestamps Action:
- Check data collection system
- Review system maintenance logs
- Investigate network issues
Observation: Missing values occur at same time daily Action:
- Check scheduled maintenance
- Review system configuration
- Investigate environmental factors
Export Options:
- Screenshot: Capture analysis results
- Data Export: Export statistics as CSV (if available)
- Report: Document findings for stakeholders
Problem: Analysis shows 0% missing Possible Causes:
- Data is truly complete (good!)
- Analysis method doesn't detect gaps
- Data preprocessing filled gaps
- Check raw data for verification
Problem: Analysis is slow Solutions:
- Select fewer sensors
- Use date range filters
- Check data volume
- Verify backend performance
Problem: Results don't match expectations Solutions:
- Verify data source
- Check date range
- Review sensor selection
- Compare with raw data
After analyzing missing values:
- Check Invalid Values: See Invalid Values Guide
- Assess Overall Quality: Use Data Quality Guide
- Visualize Data: Go to Data Visualization Guide
- Chat with Agent: Ask DQA Agent about missing values
- Data Quality Guide - Comprehensive quality assessment
- Invalid Values Guide - Invalid readings analysis
- Data Loading Guide - Load and view data
For technical details, see the Backend API Documentation.