Mfg/Model-Level Maintenance Defaults

Overview

Tag-based maintenance rules allow you to apply manufacturer and model-specific maintenance intervals across your entire fleet automatically. This powerful approach ensures every asset receives appropriate maintenance based on OEM recommendations, and new assets are automatically included when added to your fleet.

Understanding Tag-Based Scoping

How Tags Enable Manufacturer/Model Defaults

ARMOR's tagging system allows you to categorize assets by characteristics like manufacturer, model, type, and usage. When you scope a maintenance rule to specific tags, the rule automatically applies to all assets matching those tags—now and in the future.

Benefits of Manufacturer/Model-Level Defaults

• Scalability: Set it once, applies to hundreds of assets
• Automatic inclusion: New assets automatically get appropriate maintenance
• OEM compliance: Follow manufacturer recommendations precisely
• Simplified management: One rule per model, not per asset
• Easy updates: Change threshold once, affects all matching assets

Setting Up Manufacturer/Model Defaults

Prerequisites

1. Consistent tagging: All assets must have manufacturer and model tags
2. Standardized naming: Use consistent tag values ("Kaivac" not "kaivac" or "Kaivac Corp")
3. OEM recommendations: Know manufacturer's recommended maintenance intervals

Step-by-Step Configuration

Step 1: Research OEM Recommendations

Before creating rules, collect manufacturer specifications:

• Consult equipment manual or service guide
• Contact manufacturer technical support if needed
• Document: maintenance type, interval (hours/miles), and calendar backup (max days)

Step 2: Verify Tag Structure

Ensure assets are tagged correctly:

1. Navigate to Assets → filter by manufacturer
2. Verify all assets have consistent manufacturer and model tags
3. Correct any inconsistencies (e.g., "Kaivac" vs "kaivac")
4. Ensure tags are in appropriate categories (not custom fields)

Step 3: Create Maintenance Rule

1. Navigate to Administration → Maintenance Management
2. Click "Create New Maintenance Rule"
3. Fill in basic information:
   • Name: Kaivac 17CC Oil Change
   • Data Name: Oil Change
   • Data Field: runtime
   • Threshold: 250
   • Unit: hours
   • Max Days: 365
4. Configure scope with tags:
   • Click "Add Tag Filter"
   • Category: Manufacturer, Value: Kaivac
   • Click "Add Tag Filter" again
   • Category: Model, Value: 17CC
5. Set initialization mode (typically "current" for existing assets)
6. Save rule

Step 4: Verify Rule Application

1. Rule detail page shows "Assets in Scope" count
2. Verify count matches expected number of assets
3. Click into one asset detail page
4. Verify maintenance rule appears in Maintenance section

Common Configuration Patterns

Pattern 1: Single Model Rule

Pattern 2: Multiple Models, Same Interval

Pattern 3: Manufacturer-Wide Default

Pattern 4: Equipment Category

Managing Multiple Models

Strategy: One Rule Per Model (Recommended)

Approach: Create separate rule for each manufacturer/model combination

Advantages:

• Precise control over each model's intervals
• Easy to adjust one model without affecting others
• Clear audit trail of which rule applies to which assets

Example:

Strategy: Grouped Rules for Similar Models

Approach: Use OR logic to group models with identical intervals

Advantages:

• Fewer rules to manage
• Good for manufacturers with many similar models

Caution:

• If one model needs interval change, must split into separate rule
• Less granular reporting

Automatic Inclusion of New Assets

How It Works

When you add a new asset to ARMOR with matching tags, maintenance rules are automatically applied:

1. New asset created with tags: Manufacturer = "Kaivac", Model = "17CC"
2. ARMOR evaluates all maintenance rules
3. Finds rule scoped to Kaivac 17CC
4. Automatically assigns rule to new asset
5. Maintenance tracking begins immediately

Initialization for New Assets

New assets added after rule creation inherit the rule but need initial counter value:

• If init mode was "zero": New asset starts at 0 hours
• If init mode was "current": New asset starts at current runtime value

Best Practice: For new assets, use "current" initialization or manually adjust counter to reflect when maintenance was last performed (before asset entered ARMOR).

Handling Exceptions

When One Asset Needs Different Interval

Scenario: Most Kaivac 17CC scrubbers follow 250-hour interval, but one operates in extremely dusty environment and needs 200-hour interval.

Solution: Asset-Specific Override

1. Keep manufacturer/model default rule (applies to 99% of fleet)
2. Create second rule scoped to specific asset with 200-hour threshold
3. Asset receives both rules
4. More restrictive rule (200 hours) controls alert timing

See: Custom Overrides at Site/Asset Level for detailed instructions

When Entire Site Needs Different Interval

Scenario: All equipment at one site operates in harsh environment needing more frequent maintenance.

Solution: Site-Level Rule

1. Create site-specific rule with reduced threshold
2. Scope to both site AND manufacturer/model tags
3. Assets at that site follow more frequent schedule
4. Assets elsewhere follow standard schedule

Maintenance Rule Library

Building a Comprehensive Set

For each manufacturer/model in your fleet, create rules for:

Maintenance Type	Typical Interval	Data Field
Oil Change	200-300 hours or annually	runtime
Filter Replacement	100-150 hours or semi-annually	runtime
Tire Rotation (vehicles)	5000-7500 miles or annually	distance
Annual Inspection	Yearly only	None (time-based)
Battery Maintenance	50 hours or monthly	runtime

Naming Convention

Use consistent naming for easy management:

Best Practices

• Start with major manufacturers: Create rules for most common equipment first
• Use consistent tagging: Standardize manufacturer/model tag values across fleet
• Document OEM sources: Keep notes on where intervals came from
• Review annually: Check if manufacturer recommendations have changed
• Test before fleet-wide: Create rule, verify it applies correctly to a few test assets
• Use "current" initialization: For existing assets, prevents flood of immediate alerts
• Leverage OR logic: Group similar models to reduce rule count
• Plan for exceptions: Use asset-specific overrides sparingly and document why

Troubleshooting

Rule Not Applying to Expected Assets

Problem: Created rule with manufacturer/model tags, but assets aren't getting the rule

Solutions:

• Check tag spelling - must match exactly (case-sensitive)
• Verify assets actually have those tags assigned
• Check if assets have conflicting site or asset-specific rules
• Ensure tag is in correct category (Manufacturer vs Custom Field)

Too Many Assets in Scope

Problem: Rule applies to more assets than expected

Solutions:

• Add more specific tag filters (e.g., add model filter to manufacturer-only rule)
• Check for assets incorrectly tagged
• Use AND logic between filters to narrow scope

New Assets Not Getting Maintenance Rules

Problem: Added new asset but maintenance isn't tracking

Solutions:

• Verify new asset has correct manufacturer and model tags
• Check that tags match existing rules exactly
• Wait a few minutes and refresh - rule assignment may be delayed
• Manually check asset detail page Maintenance section

What's Next?

• Custom Overrides at Site/Asset Level - Handle exceptions to manufacturer defaults
• Creating a Maintenance Plan - Step-by-step rule creation guide
• Understanding Maintenance Rules - Deep dive into rule structure and logic

Getting Help

For assistance configuring manufacturer/model-level maintenance defaults, contact the ARMOR Support Team with your equipment list and OEM recommendations.