Impact thresholds define the baseline severity classification for engineering change orders and PLM staging journals. When no specific impact rule matches a change, the agent evaluates these thresholds against the aggregate metrics of the affected transactions to decide whether the change is CRITICAL, HIGH, MEDIUM, or LOW. Configure thresholds so that raw impact counts gain business context and every user receives a consistent severity assessment.
Prerequisites
You have access to the Engineering change management module in D365 F&SCM.
You are assigned the System administrator or ECM manager role.
The ECM+ Impact Agent is configured and operational.
Steps
Go to Engineering change management > Setup > Impact analysis > Impact thresholds. The Impact thresholds page opens with four severity sections: CRITICAL, HIGH, MEDIUM, and LOW.
(Optional) To define thresholds that apply to an individual user rather than the organization-wide defaults, select the Business Impact User Setup link at the top of the page and configure the per-user values there. Skip this step if you only need the shared, organization-wide thresholds.
In the severity section that you want to configure, select New on the section toolbar to add a threshold condition.
In the new row, complete the following columns:
Type – Select the metric to evaluate, such as Sales order count, Purchase order count, Production order count, Total order value, Customer count, Days to nearest delivery, On-hand inventory value, or Supplier count.
Operator – Select the comparison operator: Greater than (>), Less than (<), Greater than or equal to (>=), Less than or equal to (<=), or Equal to (=).
Value – Enter the numeric threshold value for the condition.
To add more conditions to the same severity level, select New again and repeat the previous step.
Repeat steps 3 through 5 for each severity section that you want to configure.
To remove a condition, select the row and then select Delete on the section toolbar. To find a condition, select Search on the section toolbar.
Select Save.
Results
The agent uses the saved thresholds as the baseline severity classification.
When you ask the agent about impact analysis and no rule matches, the agent evaluates the thresholds against the aggregate metrics and cites the threshold that the change exceeded to explain the severity.
The following example shows how you might configure the sections:
Severity | Type | Operator | Value |
|---|---|---|---|
CRITICAL | Total order value ($) | > | 1,000,000 |
CRITICAL | Sales order count | > | 50 |
CRITICAL | Days to nearest delivery | < | 3 |
HIGH | Total order value ($) | > | 100,000 |
HIGH | Sales order count | > | 25 |
HIGH | Days to nearest delivery | < | 7 |
MEDIUM | Total order value ($) | > | 10,000 |
MEDIUM | Sales order count | > | 10 |
MEDIUM | Days to nearest delivery | < | 14 |
LOW | Total order value ($) | <= | 10,000 |
LOW | Sales order count | <= | 10 |
LOW | Days to nearest delivery | >= | 14 |
Note
When several metrics meet different severity levels, the agent assigns the highest matching level. The precedence is CRITICAL > HIGH > MEDIUM > LOW.
If you configure both thresholds and impact rules, the rules take precedence and the thresholds serve as the fallback. If you configure no thresholds, the agent returns impact counts without a severity classification.