- 6 minutes to read

Ownership Clarity at 3 AM

Know who owns every integration the moment it fails. Nodinite Custom Metadata puts the owner, emergency contact, and SLA in your alerts, so your on-call engineer calls the right person first.

  • ✅ 2 minutes to engagement instead of 45 minutes hunting
  • ✅ The first call reaches the right person
  • ✅ SLAs preserved, and in the illustrative example below, about $4,700 saved per critical incident

The Problem: 45 Minutes Lost Hunting for an Owner

It's 3 AM. An integration is down and production is burning. Your on-call engineer stares at the logs:

"Order-to-Cash integration down"

Now what?

  • Search SharePoint for documentation (if you remember the URL)
  • Find relevant documents (if they exist and are current)
  • Identify the owner from the last modification date
  • Call that person (if they still work here)
  • They're not answering → call their manager
  • The manager doesn't know → escalate to the architect
  • 45 minutes wasted → SLA blown → CEO angry

The Solution: Owner and Contact in the Alert

Alert Enrichment turns alerts into the first step of your incident response, with instant owner identification.

Alert Email with Custom Metadata 

SUBJECT: [GOLD SLA - CRITICAL] Finance Integration Failed: Order-to-Cash

Integration: Order-to-Cash
Owner: Henrik (henrik@company.com)
Owner Mobile: +1-555-0123
Emergency Contact: Michael (michael@company.com, +1-555-0199)
Department: Finance
SLA Level: Gold (4-hour response required)
Business Impact: Month-end invoice processing blocked
Escalation: If no response from Owner in 15 minutes, contact Emergency Contact

On-Call Engineer Actions

  1. Receive the alert: full context, owner, contact, SLA
  2. Call Henrik immediately: +1-555-0123
  3. Henrik answers (he expects critical calls at 3 AM for a Gold SLA)
  4. 2 minutes to engagement
  5. SLA preserved

Illustrative Impact

The figures below are a worked example for this scenario, not measured customer results. Replace the assumptions with your own numbers to estimate the effect in your organization.

Assumptions

  • 45 minutes to reach the right person without ownership metadata, and 2 minutes with it (the two timelines on this page)
  • An incident cost of $110 per minute while the owner is being found, covering on-call time and business impact such as blocked month-end invoicing; use your own cost of downtime here
  • 50 critical incidents a year

Worked Example

Metric Without Custom Metadata With Custom Metadata Difference
Time to engagement 45 minutes 2 minutes 43 minutes per incident
Cost of finding the owner, per incident 45 × $110 = $4,950 2 × $110 = $220 $4,730 per incident
Cost of finding the owner, per year 50 × $4,950 = $247,500 50 × $220 = $11,000 $236,500 per year
First call Often a stale contact from an old document The verified Owner from the alert First call reaches the right person
SLA At risk while the owner is being found Escalation starts within minutes Contractual SLAs protected

The formula is: minutes saved per incident × cost per minute × critical incidents per year, here 43 × $110 × 50 = $236,500.

Note

The cost per minute is an assumption for illustration. The real figure depends on the integration, the business process it supports, and your on-call model.

How It Works

1. Define Metadata at Creation

When you create an Integration, Service, or Endpoint, Mandatory Fields require:

  • Owner: Responsible person (with email + phone)
  • Emergency Contact: Backup escalation point
  • Department: Business owner (for context)
  • SLA Level: Gold/Silver/Bronze (determines alert priority)

Governance starts on day 1: no integration goes live without clear ownership.

2. Alert Enrichment

The Alarm Plugins receive the Custom Metadata of the entities behind the failing Resource:

Integration fails → Alarm Plugin receives the alert data with Custom Metadata → Alert shows Owner/Emergency Contact/SLA

The HTTP Webhook payload carries the values, and the email stylesheet decides which fields the email shows. Set up the stylesheet once; after that, every alert uses the current values from the Repository.

3. SLA and Department as Context

The alert shows the SLA Level and Department next to the owner:

Integration: Employee-Onboarding
Owner: Sarah (HR IT)
Department: Human Resources
SLA Level: Silver

The responder sees at a glance how urgent the failure is and which business area it affects. Who receives the alert is set by the Alarm Plugins on the Monitor View, not by these values; if your ticketing or chat tool should route on Department or SLA Level, let the webhook consumer do that.

Implementation Scenario: Finance Order-to-Cash

Integration Order-to-Cash is in the Finance domain and on the critical path.

Metadata Defined

  • Owner: Henrik (Finance IT Lead)
  • Emergency Contact: Michael (VP Finance IT)
  • Department: Finance
  • SLA: Gold (4-hour target)
  • Business Process: Month-End Invoice Processing
  • Compliance: GDPR, PCI DSS

The Incident with Metadata (3:15 AM Tuesday)

  1. Integration connection pooling exhausted
  2. Alert triggered: the alarm stylesheet shows the ownership metadata
  3. Henrik receives the alert on his phone with full context
  4. The on-call engineer calls Henrik, who answers (3:15 AM, Gold SLA, he expects it)
  5. Henrik diagnoses a connection leak in Service X
  6. He restarts the connection pool: 03:27 AM
  7. Integration recovers: 12-minute outage
  8. SLA preserved (4-hour target)
  9. Finance month-end processing continues

The Same Incident Without Metadata

  1. 03:15 AM incident starts
  2. On-call engineer: generic alert "Order-to-Cash down"
  3. 03:20: Searches SharePoint for owner
  4. 03:28: Finds developer list (likely stale)
  5. 03:30: Calls first developer (wrong number, phone disconnected)
  6. 03:35: Calls second developer (not on-call, never returned call)
  7. 03:50: Escalates to manager (asleep)
  8. 04:15: Finally reaches Henrik
  9. 04:27: Incident resolved (1+ hour outage)
  10. SLA breached (4-hour target blown by delay)
  11. CEO called, Finance team angry, on-call engineer blamed

The difference: metadata gives a 12-minute outage with the SLA preserved; no metadata gives a 1+ hour outage and an SLA breach.

Reusable Metadata Fields

Define common ownership fields once and reuse them everywhere, as Select fields (see Rich Data Types).

Owners

  • Henrik (Finance IT Lead)
  • Sarah (HR IT Lead)
  • Michael (Operations)
  • Ahmed (Integration Architect)

Emergency Contacts

  • Michael (VP Finance IT)
  • Sarah (VP HR Operations)
  • Ahmed (Chief Architect)

SLA Levels

  • Gold (4-hour response, 99.9% uptime target)
  • Silver (8-hour response, 99% uptime target)
  • Bronze (24-hour response, 98% uptime target)

Values Applied to Each Entity

  • Integration "Order-to-Cash": Owner=Henrik, Emergency=Michael, SLA=Gold
  • Integration "Employee-Onboarding": Owner=Sarah, Emergency=Michael, SLA=Silver
  • Integration "Budget-Reporting": Owner=Ahmed, Emergency=Michael, SLA=Bronze
  • Service "SAP-Connector": Owner=Henrik, Emergency=Ahmed, SLA=Gold
  • Service "Database-Sync": Owner=Sarah, Emergency=Michael, SLA=Silver

The result is a consistent ownership model across 100+ integrations. Each entity keeps its own values, so update the owner on the entity once, and every page, filter, and alert that shows that entity uses the new value.

How This Scenario Uses Nodinite Features

  1. Alert Enrichment – Owner, Emergency Contact, and SLA in email and webhook alerts
  2. Mandatory Fields – No integration without an owner
  3. Rich Data Types – Select fields for owners, contacts, and SLA levels

Next Steps