Add Activity For Missed Case Deadline

Overview

The Add Activity For Missed Case Deadline enrichment automatically inserts a new activity into cases where a deadline has been missed. This powerful conformance monitoring tool compares a deadline date attribute against an execution activity timestamp to detect deadline violations. When the execution activity occurs after the deadline (or when no execution activity exists and current date exceeds the deadline), the enrichment creates a new event marking the deadline miss.

This enrichment is essential for deadline monitoring and SLA compliance analysis, enabling you to track deadline violations as distinct process events that can be analyzed, filtered, and reported like any other activity in your process.

Note: This enrichment is available only to administrators due to its ability to modify the event log by inserting new events.

Common Uses

  • Track missed payment deadlines in accounts payable processes
  • Monitor SLA violations in service management workflows
  • Identify overdue deliveries in supply chain processes
  • Detect missed approval deadlines in procurement
  • Flag expired contract renewals or compliance deadlines
  • Mark overdue maintenance activities in asset management
  • Monitor missed response deadlines in customer service processes

Settings

Deadline Attribute: Select the case attribute containing the deadline date. This should be a date or datetime column representing when an activity should have been completed by. Common examples include "Due Date", "SLA Deadline", "Expected Completion Date", or "Payment Due Date".

Execution Activity Name: Specify the activity that represents deadline fulfillment. This is the activity that should occur before the deadline to avoid a violation. For example, "Pay Invoice" for payment deadlines, "Complete Delivery" for shipping deadlines, or "Approve Request" for approval deadlines.

First or Last: Choose whether to use the first or last occurrence of the execution activity when cases have multiple executions:

  • First: Use the earliest occurrence of the execution activity
  • Last: Use the most recent occurrence of the execution activity (default)

New Activity: Define the activity to insert when a deadline is missed. Configure the activity name (e.g., "Deadline Missed", "SLA Violation", "Payment Overdue") and optionally set the expected order position for process map display.

Use Current Date: When enabled, cases without an execution activity are evaluated against the current system date. If the current date exceeds the deadline, a missed deadline event is created. This is useful for monitoring ongoing cases that haven't yet completed but have already missed their deadlines.

Example

Accounts Payable Deadline Monitoring

Scenario: You want to track invoices that were paid after their due date, creating a visible event for late payments.

Settings:

  • Deadline Attribute: "Due Date"
  • Execution Activity Name: "Pay Invoice"
  • First or Last: Last
  • New Activity: "Due Date Missed"
  • Use Current Date: Yes

Before: | Case ID | Activity | Timestamp | Due Date | |---------|----------|-----------|----------| | INV-001 | Receive Invoice | 2024-01-10 | 2024-01-25 | | INV-001 | Approve Invoice | 2024-01-15 | 2024-01-25 | | INV-001 | Pay Invoice | 2024-01-30 | 2024-01-25 |

After: | Case ID | Activity | Timestamp | Due Date | |---------|----------|-----------|----------| | INV-001 | Receive Invoice | 2024-01-10 | 2024-01-25 | | INV-001 | Approve Invoice | 2024-01-15 | 2024-01-25 | | INV-001 | Due Date Missed | 2024-01-25 | 2024-01-25 | | INV-001 | Pay Invoice | 2024-01-30 | 2024-01-25 |

Insights: The new "Due Date Missed" activity is inserted at the deadline date (January 25), making it visible in process maps and allowing you to filter for late payments, calculate late payment rates, and analyze patterns in deadline violations.

SLA Compliance Monitoring

Scenario: A service desk needs to track tickets that exceeded their resolution SLA.

Settings:

  • Deadline Attribute: "SLA Resolution Deadline"
  • Execution Activity Name: "Resolve Ticket"
  • First or Last: First
  • New Activity: "SLA Breached"
  • Use Current Date: Yes

Output: Tickets resolved after their SLA deadline will have an "SLA Breached" event inserted at the deadline timestamp. Open tickets that have passed their deadline will also receive this event based on the current date comparison.

Insights: This enables real-time SLA compliance dashboards showing breached tickets, helps identify patterns in SLA violations by category or team, and provides data for root cause analysis of deadline misses.

Delivery Deadline Tracking

Scenario: A logistics company wants to mark orders with late deliveries.

Settings:

  • Deadline Attribute: "Promised Delivery Date"
  • Execution Activity Name: "Complete Delivery"
  • First or Last: Last
  • New Activity: "Delivery Late"
  • Use Current Date: No

Output: Orders delivered after the promised date will have a "Delivery Late" event created at the promised delivery date timestamp. Cases still in transit are not evaluated (Use Current Date is disabled).

How It Works

  1. Deadline Evaluation: For each case, the enrichment retrieves the deadline date from the specified attribute
  2. Execution Check: Looks for the first or last occurrence of the execution activity in the case
  3. Comparison Logic:
    • If execution activity exists: Compare its timestamp to the deadline
    • If no execution activity and Use Current Date enabled: Compare current date to deadline
  4. Violation Detection: If execution date > deadline date, a deadline miss is identified
  5. Event Insertion: A new event is created with the specified activity name, timestamped at the deadline date
  6. Log Update: The event log is regenerated with the new events included

Output

The enrichment modifies the event log by inserting new events:

  • New Activity: Events with the specified activity name are added to cases with deadline violations
  • Timestamp: The new events are timestamped at the deadline date (from the deadline attribute)
  • Expected Order: If configured, the activity appears in the correct sequence position in process maps
  • Case Association: New events are properly linked to their parent case

The inserted events can then be used for:

  • Filtering cases with deadline violations
  • Calculating deadline miss rates and patterns
  • Visualizing violations in process maps
  • Creating conformance metrics and dashboards
  • Triggering alerts for SLA breaches

See Also

This documentation is part of the mindzie Studio process mining platform.