Assessment and Health attributes for the Integrations Inventory - Integrations Inventory and Attributes

Assessment and Health attributes for the Integrations Inventory

(Chapter 15 of Integrations Inventory and Attributes)

Executive Summary: Chapter Overview

IF4IT

The Bottom Line

Assessment and Health attributes evaluate the operational condition of each Integration by capturing dependency impact, error rate, and mean time between failures. These attributes convert runtime behavior into portfolio intelligence for incident prevention, reliability investment, and integration health management.

Core Concepts

Concept	Definition & Strategic Role
Dependency Impact	Dependency Impact translates integration failure into business terms, identifying what processes, reports, capabilities, or operations break when the flow fails.
Operational Health	Error Rate and Mean Time Between Failures provide objective reliability signals when monitoring and observability data are available.

Quick Q&A

Question: Why is Dependency Impact important for integration governance?

Answer: Technical failure metrics are not enough. Dependency Impact explains the business consequence of an integration failure, which helps teams triage incidents, prioritize remediation, and justify reliability investment.

Assessment and Health attributes capture the evaluated operational health of each Integration — its failure impact, error characteristics, and stability over time.

Attribute Name	Maturity	Description and Notes
Dependency Impact	Walk	Description — A description of what breaks, degrades, or is blocked if this integration fails — which downstream processes, reports, capabilities, or business operations are affected. Benefit(s) — Translates integration failure into business impact language. Essential for incident response triage, change risk assessment, and investment justification for integration reliability improvements. Source — Manual. Examples — Daily claims payment processing halted; Customer portal unable to display account balances; Regulatory report generation blocked; Warehouse operations delayed
Error Rate	Run	Description — The observed percentage of executions that result in an error or partial failure over the most recent measurement period. Benefit(s) — Surfaces integrations with chronic quality problems before they cause business-visible failures. A rising error rate is a leading indicator of integration health degradation. Source — Calculated. Notes — Requires active monitoring infrastructure and integration platform observability tooling. Calculated from integration platform logs or APM monitoring tools.
Mean Time Between Failures	Run	Description — The average time between integration failures — a key indicator of integration stability over time. Benefit(s) — Enables objective comparison of integration reliability across the portfolio. Integrations with declining MTBF require proactive investment before they become incident drivers. Source — Calculated. Notes — Requires historical monitoring data. Calculated from integration platform incident logs.

Attribute Name

Maturity

Description and Notes

Dependency Impact

Walk

Description — A description of what breaks, degrades, or is blocked if this integration fails — which downstream processes, reports, capabilities, or business operations are affected.

Benefit(s) — Translates integration failure into business impact language. Essential for incident response triage, change risk assessment, and investment justification for integration reliability improvements.

Source — Manual.

Examples — Daily claims payment processing halted; Customer portal unable to display account balances; Regulatory report generation blocked; Warehouse operations delayed

Error Rate

Run

Description — The observed percentage of executions that result in an error or partial failure over the most recent measurement period.

Benefit(s) — Surfaces integrations with chronic quality problems before they cause business-visible failures. A rising error rate is a leading indicator of integration health degradation.

Source — Calculated.

Notes — Requires active monitoring infrastructure and integration platform observability tooling. Calculated from integration platform logs or APM monitoring tools.

Mean Time Between Failures

Run

Description — The average time between integration failures — a key indicator of integration stability over time.

Benefit(s) — Enables objective comparison of integration reliability across the portfolio. Integrations with declining MTBF require proactive investment before they become incident drivers.

Source — Calculated.

Notes — Requires historical monitoring data. Calculated from integration platform incident logs.

How to cite this page

When referencing this page in academic work, internal standards, or external publications, include the page title, IF4IT as author and publisher (The International Foundation for Information Technology (IF4IT), LLC), the URL, and your access date.

Example (informal web citation):

The International Foundation for Information Technology (IF4IT), LLC. Assessment and Health attributes for the Integrations Inventory | Integrations Inventory and Attributes. https://if4it.org/best-practices/integrations-inventory-and-attributes/assessment-and-health-attributes-for-the-integrations-inventory/ (accessed 2026-09-08).

See About Us for content governance and site-wide citation guidance.

Legal Disclaimers