Product Version History
| Version | Purpose | Date | Owner |
|---|---|---|---|
| V01 | Initial release | 1/30/2026 | Joe Morton |
Purpose of this Feature
Adaptive Thresholds allow Action Manager alerts to use dynamic threshold values instead of static, manually-set numbers. The threshold is defined as a formula that gets evaluated for each entity when the alert is checked.
Problems it solves:
- Different products, lines, or machines may have different performance targets
- Maintaining separate alert profiles for each variation is time-consuming and error-prone
- Static thresholds don't account for context-specific goals
Who benefits:
- Operations teams who need alerts that adapt to different products or equipment
- Quality managers with varying yield targets across products
- Anyone managing alerts across entities with different performance standards
Key Functionalities and Workflows
Capabilities:
- Set thresholds dynamically using formulas that reference properties from the Factory Map or Product Map
- Formula is evaluated for each entity during alert checks
- Supports variables for site, area, line, machine, and step (including substep attributes)
Supported Modules:
- Quality - FPY (First Pass Yield)
- Quality - SPY (Second Pass Yield)
- Downtime Duration (React)
Threshold Types:
- Manual: Static value that applies uniformly
- Formula: Dynamic value calculated based on entity properties
Step-by-Step Usage Instructions
Configure an Adaptive Threshold
- Navigate to Action Manager → Trigger Management
- Select a module that supports adaptive thresholds (Quality - FPY, Quality - SPY, or Downtime Duration)
- Create a new profile or edit an existing one
- In the Configuration section, find Threshold Type
- Select Formula from the dropdown
- Enter your formula in the Threshold Formula field
- Hover over the info icon for guidance on supported variables
- Click Save
Example Formulas
-
machine.properties.target_fpy— Use a target FPY stored on the machine -
step.attributes.quality_threshold— Use a threshold defined on the product step -
coalesce(step.attributes.target, machine.properties.default_target, 0.95)— Use step target if available, fall back to machine default, then 0.95
Configuration or Setup Requirements
Prerequisites:
- Properties or attributes must be defined in the Factory Map (for site, area, line, machine) or Product Map (for step, substep) before they can be referenced in formulas
- User must have permission to create and edit Action Manager profiles
Formula Output Requirements:
- Quality - FPY / SPY: Formula result must be between 0 and 1 (representing a percentage)
- Downtime Duration: Formula result must be in seconds
Supported Variables:
-
site— {slug, properties} -
area— {slug, properties} -
line— {slug, properties} -
machine— {slug, properties} -
step— {attributes, substep: {attributes}}
Expected Outputs or Reports
When an adaptive threshold is configured:
- The alert evaluates the formula for each entity in scope
- Different entities can trigger (or not trigger) based on their specific calculated threshold
- Alert behavior otherwise remains the same (routing, playbooks, etc.)
Appendices
Technical Documentation
For detailed formula syntax, supported functions, and advanced usage, refer to the public technical documentation:
Action Manager Adaptive Threshold Documentation
FAQ
Q: Where do I set the properties that formulas reference? A: Properties are set in the Factory Map (for site, area, line, machine) or Product Map (for step and substep attributes).
Q: Can I use adaptive thresholds with other Action Manager modules? A: Currently, only Quality - FPY, Quality - SPY, and Downtime Duration (React) support adaptive thresholds.
Q: What happens if a property referenced in my formula doesn't exist? A: The formula will fail to evaluate. Use the coalesce() function to provide fallback values.
Comments
0 comments
Please sign in to leave a comment.