Missing Goal Data

Overview

Your goal is configured and active, but when you check asset performance, the data field shows "No Data", "0", or "—". This prevents goals from evaluating properly and may cause false positives or missed alerts. This guide explains why data might be missing and how to resolve it.

Understanding "Missing Data" vs. "Zero Values"

It's important to distinguish between different scenarios:

Display	Meaning	Impact on Goal
— or "No Data"	Field not available for this asset type	Asset skipped, goal not evaluated
0	Asset reports zero value (legitimate or error)	Goal evaluates: 0 compared to threshold
null or blank	Telemetry missing/delayed	Asset skipped or treated as 0 (behavior varies)

Common Causes and Solutions

1. Data Field Not Supported by Asset Type

How to diagnose:

1. Navigate to asset detail page
2. Check if the data field appears at all
3. Look for telemetry configuration - does device support this sensor?

Example scenario:

Solutions:

• Option 1: Change goal to monitor a different field that all assets support (e.g., runtime instead of distance)
• Option 2: Adjust goal scope to exclude assets that don't support this field
• Option 3: Create separate goals for different asset categories

Asset type field availability reference:

Asset Type	Typical Fields Available	Fields NOT Available
Mobile equipment	runtime, distance, location, speed	Production metrics
Stationary equipment	runtime, production, power metrics	distance, location, speed
Electric assets	batteryLevel, chargeTime, voltages	fuelLevel, engineHours
Non-telemetry assets	Manual data only	All telemetry fields

2. Telemetry Device Offline or Not Transmitting

How to diagnose:

1. Open asset detail page
2. Check "Last Telemetry Update" timestamp
3. If >24 hours old: device offline
4. If timestamp recent but values stuck: data collection issue

Quick check table:

Last Update Age	Status	Next Step
<5 minutes	✅ Healthy	Data should be current
5-60 minutes	⚠️ Delayed	Check cellular signal
1-24 hours	❌ Stale	Check device power, reboot if needed
>24 hours	❌ Offline	Investigate hardware/installation issue

Solutions:

1. Power: Verify device has stable power connection; check fuses/wiring
2. Cellular signal: Ensure antenna is properly installed and equipment is in coverage area
3. Device reboot: Power cycle the telemetry device (turn off equipment, wait 30 seconds, turn back on)
4. Firmware update: Check if device needs firmware update (contact Support)
5. Subscription status: Verify data plan is active (check billing status)

See Telemetry Not Feeding Goals for comprehensive connectivity troubleshooting.

3. Data Transmission Delays

How it affects goals:

• Daily goals: If data arrives after 2 AM check, asset appears to have 0 activity for that day
• Weekly/monthly goals: Less impactful if data arrives before period ends

Solutions:

• Improve signal: Relocate antenna or upgrade to external antenna
• Adjust goal timing: For daily goals in poor signal areas, consider switching to weekly checks
• Accept delays: Data will backfill; just acknowledge alerts may be delayed

4. CAN Bus Integration Issues

How to diagnose:

1. Check if location and lastUpdate are current (device is online)
2. Check if runtime, distance, speed fields are all 0 or missing
3. If GPS works but engine data doesn't: CAN bus issue

Solutions:

• Verify CAN harness is properly connected to OBD port or J1939 connector
• Check installation guide for equipment model - some require specific adapters
• Confirm equipment ECU is compatible (older models may not support CAN)
• Contact ARMOR Support for CAN configuration validation

5. Wrong Time Period Selected

Field naming conventions:

• runTimeToday - Only today's data (resets at midnight)
• runTimeWeek - Current week's data (resets weekly)
• runTimeTotal - Lifetime accumulation (never resets)

Example confusion:

Solution: Always verify you're viewing the same time period and data field that the goal monitors.

6. Data Field Mapping Errors

How to diagnose:

1. Compare 3-5 assets that should be identical
2. If some show data and others don't, it's a configuration issue (not a device connectivity issue)
3. Check telemetry device model - older devices may support fewer fields

Solutions:

• Update asset configurations to use consistent telemetry mappings
• Upgrade older telemetry devices to current hardware
• Create separate goals for assets with different capabilities
• Contact Support to review asset telemetry configuration

7. Manual Data Entry Assets

Impact on goals:

• Goals requiring real-time telemetry will not work for manual assets
• Asset will be skipped during goal checks
• Manual data (if entered) may appear in reports but not feed into goal evaluation

Solutions:

• Exclude from scope: Adjust goal to exclude manual assets (use tag-based scoping)
• Install telemetry: Equip asset with telemetry device if monitoring is needed
• Create manual process: Use reporting instead of automated goals

8. Newly Onboarded Assets

Typical timeline:

Solution: Wait 24-48 hours after asset onboarding before expecting complete data. Goals will start working once data is available.

Diagnosing Multiple Assets with Missing Data

If many assets show missing data:

Scenario 1: All Assets in a Site

• Likely cause: Site-wide connectivity issue (tower outage, network problem)
• Solution: Contact ARMOR Support to check regional network status

Scenario 2: All Assets of Same Type

• Likely cause: Data field not supported by this asset category
• Solution: Change goal to monitor a different field, or scope to exclude this asset type

Scenario 3: All Assets Using Specific Goal Template

• Likely cause: Template configured with incompatible field
• Solution: Edit goal template or create custom goal with correct field

Scenario 4: Random Assets Across Fleet

• Likely cause: Individual device issues (power, installation, subscription)
• Solution: Investigate each asset individually; likely hardware maintenance needed

Preventive Best Practices

• Test goals on pilot assets - Verify data availability before rolling out fleet-wide
• Create telemetry health goals - Monitor "Last Update" to detect offline devices before they affect other goals
• Document asset capabilities - Tag assets by telemetry device model and supported fields
• Regular audits - Monthly check: which assets haven't reported data in >7 days?
• Onboarding checklist - Verify telemetry for 48 hours before adding asset to goal scopes

Quick Reference: Data Availability Checklist

Use this when troubleshooting missing data:

Check	How to Verify	If Issue Found
Device online?	Check "Last Telemetry Update" <5 minutes	Power cycle device, check cellular signal
Field supported?	Field appears on asset detail page	Change goal field or exclude asset
CAN working?	Engine data present (not just GPS)	Check CAN harness connection
Correct time period?	Field matches goal (Today/Week/Total)	View correct time-scoped field
Data fresh enough?	Timestamp within expected check window	Improve signal or adjust goal timing

When to Contact Support

Contact ARMOR Support if:

• Device is online (recent Last Update) but specific fields show no data
• Multiple assets of same type have inconsistent data availability
• Data disappeared suddenly (was working, now broken)
• CAN bus appears connected but no engine data

Information to provide:

• Asset name/ID and telemetry device serial number
• Specific data field(s) missing
• Screenshot showing "Last Telemetry Update" and missing fields
• Asset type and telemetry device model
• When data was last visible (if known)

Related Topics

• Goals Not Triggering Alerts - Full goal troubleshooting guide
• Telemetry Not Feeding Goals - Device connectivity issues
• How to Improve Goal Accuracy With Telemetry - Data quality optimization

Getting Help

If data issues persist after following this guide, contact the ARMOR Support Team with asset details and screenshots showing missing data.