How to Create a Custom Goal

Overview

Creating a custom goal in ARMOR allows you to monitor any telemetry metric collected by your assets. Whether you're using a pre-built template or building a goal from scratch, this guide walks you through every step of the goal creation process.

Time to Complete: 5-10 minutes

Required Role: Account Admin or Super Admin

Before You Start

Make sure you have:

• Account Admin or Super Admin access
• A clear understanding of what metric you want to monitor
• Knowledge of which assets/sites this goal should apply to
• A target threshold value for your goal

Step-by-Step: Creating a Goal

Step 1: Navigate to Goal Management

1. Log into the ARMOR web portal
2. Click Administration in the main navigation menu
3. Select Goal Management from the administration options
4. Click the "+ Create New Goal" button in the top right

Step 2: Choose Template or Custom

You'll see the template selection screen with two options:

Option A: Use a Template

• Browse available templates by category (Runtime, Distance, Efficiency, etc.)
• Click on a template to see its pre-configured settings
• Click "Use This Template" to start with those settings
• Skip to Step 3 to customize the template

Option B: Create Custom Goal

• Click "Create Custom Goal" at the bottom of the template screen
• Start with a blank goal form
• Continue to Step 3 to configure all settings manually

Step 3: Configure Basic Information

Goal Name

Enter a descriptive name for your goal. This is what you and your team will see in the Goal Management list and in alerts.

Examples:

• "Daily Runtime - Main Warehouse Forklifts"
• "Weekly Distance Target - Delivery Fleet"
• "Excessive Idle Time - All Assets"

Goal Key (Auto-Generated)

The system automatically generates a unique key based on your goal name. This key is used internally by ARMOR and doesn't need to be edited.

Select Account

• Super Admins: Choose which account this goal applies to from the dropdown
• Account Admins: Your account is automatically selected

Step 4: Define What to Monitor

Data Field

Select the telemetry field you want to monitor from the dropdown. Common options include:

• runTimeToday - Daily runtime hours
• distanceToday - Daily distance traveled
• chargeTimeToday - Daily charging duration
• idleTimeToday - Daily idle time
• batteryLevel - Current battery charge percentage
• Custom fields - Any telemetry field your assets report

Sub-Field (Optional)

For complex data structures, you may need to specify a sub-field. This is typically only needed for advanced custom telemetry fields. Leave blank for standard metrics.

Step 5: Set the Target Threshold

Constraint Type

Choose how the goal should evaluate the data:

• At Least (>=) - Alert when value is below the target
  • Use for: Minimum performance targets, utilization standards
  • Example: "Runtime should be at least 6 hours"
• At Most (<=) - Alert when value exceeds the target
  • Use for: Maximum limits, waste reduction, safety caps
  • Example: "Idle time should be at most 2 hours"

Target Value

Enter the threshold number. The unit (hours, miles, %, etc.) depends on the data field you selected.

Examples:

• Runtime goal: 6 (hours)
• Distance goal: 50 (miles)
• Battery goal: 20 (percent)
• Temperature goal: 80 (degrees F)

Unit Selection

For some fields, you can choose the unit:

• Time fields: Hours or Minutes
• Distance fields: Miles or Kilometers
• Temperature fields: Fahrenheit or Celsius

The system automatically converts your input to the stored format.

Step 6: Configure Schedule

Frequency

Choose how often ARMOR should check this goal:

• Daily - Checked once per day (early morning)
  • Best for: Day-to-day performance monitoring
  • Resets: Each day at midnight
• Weekly - Checked on specific days of the week
  • Best for: Work week performance, 5-day operations
  • Requires: Selecting which days to check
• Monthly - Checked at month end
  • Best for: Long-term trends, strategic planning
  • Resets: First day of each month

Week Days (For Weekly Goals Only)

If you selected "Weekly" frequency, click the days of the week when this goal should be checked. For example, select Monday through Friday for a 5-day work week.

Step 7: Define Scope (Who Does This Apply To?)

Choose which assets this goal should monitor:

Scope Options

All Assets in Account

• Applies to every asset in the account
• Use when: You have fleet-wide standards

Specific Sites

• Select one or more sites from the dropdown
• Goal applies to all assets at those sites
• Use when: Different locations have different standards

Specific Assets

• Search for and select individual assets
• Goal applies only to those exact assets
• Use when: Monitoring specific equipment or test groups

Tag-Based Filtering

• Apply goal to assets matching specific tags
• Use when: You've tagged equipment by type, department, or purpose
• Example: All assets tagged "forklift" or "warehouse-a"

Step 8: Configure Advanced Options

Only If Field Exists

Check this box if you want the goal to only apply to assets that actually report this data field. This prevents false alerts for assets that don't have the capability to track this metric.

Example: If monitoring "batteryLevel" but some assets don't have batteries, enable this to skip those assets.

Step 9: Customize Alert Messages

Set Message (When Goal is Triggered)

This message appears in the alert when the threshold is crossed. Be clear and actionable.

Examples:

• "Daily runtime goal not met - asset underutilized"
• "Excessive idle time detected - please investigate"
• "Battery level critically low"
• "Charging time exceeds recommended duration"

Clear Message (When Goal Returns to Normal)

This message appears when the asset returns to acceptable levels.

Examples:

• "Daily runtime goal achieved"
• "Idle time back to normal levels"
• "Battery charged to acceptable level"
• "Charging complete within target time"

Step 10: Set Goal Status

Active/Inactive Toggle

• Active: Goal is monitored and will generate alerts
• Inactive: Goal is saved but not actively checking (useful for seasonal goals or testing)

Step 11: Review and Save

1. Review all settings in the form
2. Verify the scope is correct
3. Double-check your threshold value and constraint type
4. Click "Save Goal" at the bottom of the form

Your goal is now active! ARMOR will begin monitoring based on the schedule you configured.

Example: Creating a Daily Runtime Goal

After Creating a Goal

What Happens Next?

1. Goal appears in Goal Management list - You can view, edit, or delete it anytime
2. ARMOR begins monitoring - Based on the frequency you set (daily, weekly, monthly)
3. Alerts are generated - When thresholds are crossed, alerts appear in the Alerts page
4. Status visible on assets - Goal progress shows on individual asset detail pages

Testing Your Goal

After creating a goal:

1. Wait for the next check cycle (may be up to 24 hours for daily goals)
2. Check the Alerts page for goal-related notifications
3. Verify alerts are triggering as expected
4. Adjust threshold values if needed

Common Mistakes to Avoid

Best Practices

• Use descriptive names - Include the metric and scope in the goal name
• Start narrow, expand later - Test on a few assets before going fleet-wide
• Review actual data first - Check historical telemetry to set realistic thresholds
• Write clear messages - Alert text should explain the issue and suggest action
• Document your goals - Keep notes on why each goal exists and what threshold values mean
• Review regularly - Revisit goals quarterly to ensure they're still relevant

Next Steps

• Using Goal Templates - Leverage pre-built configurations
• Editing & Updating Existing Goals - How to modify goals after creation
• Goal Alerts & Notifications - Understanding the alert system
• Recommended Goals for Fleet Customers - Industry best practices

Getting Help

If you need assistance creating goals or have questions about configuration options, contact the ARMOR Support Team.