Editing & Updating Existing Goals

Overview

Once you've created a goal, you can modify it at any time. ARMOR's goal editing system allows you to adjust thresholds, change scope, update schedules, and refine alert messages without creating new goals from scratch.

This guide covers everything you need to know about editing existing goals safely and effectively.

Required Role: Account Admin or Super Admin (goals you created or have permission to manage)

Quick Access to Edit a Goal

Method 1: From Goal Management Page

1. Navigate to Administration → Goal Management
2. Find the goal in the list
3. Click the three-dot menu (⋮) on the right side
4. Select "Edit"

Method 2: From Goal Details View

1. Click on the goal name in Goal Management
2. The goal details panel opens on the right
3. Click the "Edit" button at the top of the panel

Method 3: From Alert Notifications

1. Click on a goal-triggered alert in the Alerts page
2. View the alert details
3. Click "View Goal"
4. Click "Edit" in the goal details

What You Can Edit

Field	What It Affects	Impact
Goal Name	Display name in UI and notifications	Cosmetic - no operational change
Description	Internal notes and documentation	Cosmetic - no operational change
Data Field	Which telemetry metric is monitored	⚠️ Major - changes what is tracked
Constraint Type	At Least (>=) or At Most (<=)	⚠️ Major - reverses alert logic
Target Value	Threshold for alerts	? Moderate - adjusts sensitivity
Frequency	When checks occur (daily/weekly/monthly)	? Moderate - changes alert timing
Scope	Which assets are monitored	? Moderate - expands or reduces coverage
Alert Messages	Notification text content	Cosmetic - clearer communication
Notification Recipients	Who receives alerts	? Moderate - changes notification distribution
Active Status	Whether goal checks run	⚠️ Major - stops or starts monitoring

Step-by-Step: Editing a Goal

1. Open the Goal Editor

Access the goal using any of the methods above. The goal editor form appears with current values pre-filled.

2. Make Your Changes

Adjusting Target Values

Example scenario: You set a daily runtime goal of 6 hours, but your team consistently hits 8 hours. Alerts are too frequent.

Solution:

1. Locate the "Target Value" field
2. Change from 6 to 8
3. Click "Save Goal"

Effect: Alerts will only trigger if assets fall below 8 hours instead of 6.

Changing Scope

Example scenario: Your goal applies to all assets, but some are backup units that shouldn't be monitored.

Solution:

1. Locate the "Scope" section
2. Change from "All Assets" to "Specific Assets"
3. Deselect the backup units
4. Click "Save Goal"

Effect: Goal only checks selected assets, ignoring backups.

Updating Frequency

Example scenario: Your weekly goal checks Monday-Friday, but you need weekend monitoring.

Solution:

1. Locate the "Frequency" section
2. Change from "Weekly" with Mon-Fri selected
3. Add Saturday and Sunday to the weekDays list
4. Click "Save Goal"

Effect: Goal now checks all 7 days for weekly totals.

Refining Alert Messages

Example scenario: Your default message "Daily runtime goal not met" isn't specific enough for operators.

Solution:

1. Locate the "Alert Message (Set)" field
2. Change to: "Equipment runtime below 8 hours - contact site supervisor"
3. Update "Alert Message (Clear)" to: "Equipment runtime back to normal levels"
4. Click "Save Goal"

Effect: Operators receive clearer, actionable instructions.

3. Review Your Changes

Before clicking Save, review the summary at the top of the form:

• ✅ Goal name is descriptive
• ✅ Data field matches what you want to track
• ✅ Constraint type is correct (At Least vs. At Most)
• ✅ Target value is realistic
• ✅ Scope includes the right assets
• ✅ Frequency matches your operational schedule

4. Save and Verify

1. Click "Save Goal"
2. Return to Goal Management page
3. Confirm your changes appear in the goal list
4. Check the "Last Modified" timestamp

When Changes Take Effect

Type of Change	When It Takes Effect
Target value adjustment	Next scheduled check (overnight for daily, end of period for weekly/monthly)
Scope change (add/remove assets)	Next scheduled check
Frequency change	Immediately (new schedule starts)
Alert message updates	Next alert triggered by goal
Active/Inactive toggle	Immediately (stops or resumes checks)

Common Editing Scenarios

Scenario 1: Too Many False Alerts

Problem: Goal triggers daily but assets are performing fine.

Diagnosis: Threshold is too strict for your operation.

Solution:

• Edit the goal
• Increase target value for "At Least" goals
• Decrease target value for "At Most" goals
• Save and monitor for 3-5 days

Scenario 2: Not Enough Alerts

Problem: Goal rarely triggers, but you know assets are underperforming.

Diagnosis: Threshold is too lenient.

Solution:

• Edit the goal
• Decrease target value for "At Least" goals
• Increase target value for "At Most" goals
• Save and monitor for 3-5 days

Scenario 3: Wrong Assets Monitored

Problem: Goal applies to equipment that shouldn't be tracked.

Diagnosis: Scope is too broad or includes wrong assets.

Solution:

• Edit the goal
• Change from "All Assets" to "Specific Assets" or "Tag-Based"
• Select only the relevant assets or tags
• Save

Scenario 4: Seasonal Adjustment

Problem: Goal thresholds that work in summer don't work in winter (or vice versa).

Diagnosis: Operational patterns change seasonally.

Solution:

• Edit the goal at the start of each season
• Adjust target values to match expected seasonal performance
• Document the seasonal values in the goal description
• Set a reminder to change back

Scenario 5: Expanding from Pilot to Fleet-Wide

Problem: Goal was tested on 5 assets, now you want to apply it to the entire fleet.

Diagnosis: Pilot phase complete, ready to scale.

Solution:

• Edit the goal
• Change scope from "Specific Assets" to "All Assets" or broader selection
• Verify target values still make sense for wider group
• Save and monitor closely for first week

Best Practices for Editing Goals

• Edit incrementally - Change one thing at a time so you can measure the impact
• Document major changes - Update the goal description to note threshold adjustments and why
• Test after editing - Wait 3-5 days to see how the changes affect alerts
• Don't over-edit - Frequent changes make it hard to establish baselines
• Communicate with your team - Let operators know when goal thresholds change
• Review quarterly - Schedule regular goal reviews to ensure thresholds remain relevant

What You Cannot Edit

The following require creating a new goal:

• Account assignment (Super Admins only) - Cannot move a goal from one account to another
• Goal history - Past alerts and check results cannot be modified
• Goal ID - System-generated unique identifier is permanent

Troubleshooting Edit Issues

Changes Not Saving

Possible causes:

• Missing required fields (name, data field, target value)
• Invalid target value (negative number, non-numeric input)
• Insufficient permissions (trying to edit another admin's goal)

Solution: Check for error messages at the top of the form. Ensure all required fields are filled. Verify you have edit permissions for this goal.

Goal Still Using Old Values

Possible causes:

• Changes saved but next check hasn't occurred yet
• Cached data in browser

Solution: Wait for the next scheduled check time. Refresh the page. Check the "Last Modified" timestamp to confirm save was successful.

Related Topics

• How to Create a Custom Goal - Building goals from scratch
• Goal Statuses Explained - Active, Completed, Archived states
• Goal Alerts & Notifications - How notifications work

Getting Help

If you need assistance editing a goal or troubleshooting changes, contact the ARMOR Support Team.