IIMS – Implemented Scope & Planned Roadmap Overview

Information Infrastructure Management System (IIMS)

Purpose

This document provides a concise executive and technical overview of:

What IIMS Implemented delivers today
What is intentionally planned for Planned and future evolution

It serves as:

A scope reference for engineering teams
A roadmap and planning guide for management
A positioning document for stakeholders and architects

This document complements the detailed architecture and workflow documents and acts as the single “what is done vs what is planned” reference.

1. Implemented Strategic Positioning

1.1 What Implemented Is

Implemented establishes IIMS as a unified operational coordination and visibility platform.

The primary goals of Implemented are:

Unify inventory, monitoring, incidents, maintenance, and tickets into one model
Provide a single operational UI for NOC and operations teams
Eliminate fragmented visibility across monitoring and ticketing systems
Build a strong provider‑independent foundation for future automation

Implemented focuses on:

Stability
Correctness
Provider abstraction
Manual and operator‑driven workflows

Implemented intentionally avoids heavy automation and intelligence in order to:

Reduce risk
Validate the domain model
Establish trust with operators

1.2 What Implemented Is Not

Implemented is not yet an autonomous or self‑healing operations platform.

In Implemented:

Correlation is rule‑light and mostly operator‑driven
Topology is used for visualization, not automatic impact propagation
Root cause analysis is manual
SLA enforcement and escalation are limited
Routing and failover are policy‑driven, not adaptive

These advanced capabilities are intentionally deferred to Planned.

2. Implemented Delivered Capabilities (Current Scope)

2.1 Unified Infrastructure Model

Implemented delivers a complete infrastructure foundation:

Hierarchical Site model (regions, data centers, zones)
Asset inventory with types, tags, enable/disable, provisioning state
Geo‑location with inheritance (asset inherits site location)
Roll‑up alert and severity summaries by site

This provides a consistent structural model for all operational workflows.

2.2 Monitoring Integration (Zabbix)

Implemented delivers stable monitoring integration:

Monitoring Targets abstraction
Zabbix adapter implementation
Asset provisioning and template binding
Alert ingestion and normalization
Interface discovery and telemetry queries

Routing features:

Site‑aware target resolution
Collector routing using constraints (site, tags, asset type, capacity)
Deterministic and policy‑driven routing

2.3 Alert Management

Implemented delivers:

Alert ingestion and normalization
Alert history and alert cache
Acknowledgement and close actions
Maintenance‑aware suppression

Limitations (by design):

Correlation is rule‑light
No automatic incident creation engine

2.4 Incident Management

Implemented delivers a stable human workflow model:

Manual and rule‑light incident creation
Incident lifecycle:
New
Investigating / Open
Resolved
Closed
Alert ↔ Incident linking
Activity timeline for all incident actions

Limitations:

Ownership and assignment are basic
No SLA timers or escalation policies

2.5 Ticketing Integration (Zammad)

Implemented delivers:

Ticket creation from incidents
Ticket reference storage in incidents
Limited periodic status synchronization

Safety controls:

Ticket creation blocked during maintenance

Limitations:

No real‑time bi‑directional synchronization
Single ticket per incident (practical limit)

2.6 Maintenance and Operational Control

Implemented delivers first‑class maintenance handling:

Maintenance windows by site, asset, tags, or scope
Alert suppression during maintenance
Incident and ticket creation blocked during maintenance
Full audit trail of maintenance actions

This provides reliable noise suppression and operational safety.

2.7 Topology and Geo Visualization

Implemented delivers:

Topology Links with LineString geometry
Manual status binding and policy‑based link status
GeoMap with clusters, assets, and links
Bounding‑box queries and cached map summaries

Behavior:

Visualization and situational awareness
Manual impact assessment by operators

Limitations:

No automatic impact propagation
No blast‑radius or root cause engine

2.8 Caching, Dashboards, and Performance

Implemented delivers:

Alert cache and map cache
Summary counters for dashboards
Fast read‑only UI backed by cached views
Background refresh workers

This enables scalable UI performance without overloading providers.

3. Planned Strategic Vision

Planned builds on the Implemented foundation and transforms IIMS from a coordination platform into an intelligent operations automation and decision system.

The strategic goals of Planned are:

Reduce manual operator work
Automatically correlate signals into problems
Infer root causes and blast radius
Enforce SLAs and escalation policies
Provide real‑time, proactive operations intelligence

4. Planned Roadmap by Capability Area

4.1 Automation & Correlation

Planned Planned capabilities:

Automatic alert correlation rules
Automatic incident creation and merging
Deduplication and noise scoring
Time‑based and topology‑based correlation

Business value:

Faster incident detection
Reduced alert noise
Lower operator workload

4.2 Topology Impact & Root Cause Analysis

Planned Planned capabilities:

Automatic dependency traversal
Blast‑radius computation
Root cause candidate identification
Service‑level impact modeling

Business value:

Faster troubleshooting
Clear understanding of business impact
Reduced mean‑time‑to‑repair (MTTR)

4.3 SLA, Escalation, and Ownership

Planned Planned capabilities:

Incident ownership and assignment model
SLA timers and breach detection
Escalation policies and on‑call routing
Priority‑driven workflows

Business value:

Enforced operational discipline
Predictable response times
Management‑level reporting and accountability

4.4 Multi‑Provider & Intelligent Routing

Planned Planned capabilities:

Active multi‑provider monitoring (Zabbix + Prometheus)
Provider health scoring
Automatic target and collector failover
Capacity‑aware and latency‑aware routing

Business value:

Higher availability
Easier platform migration
Reduced vendor lock‑in risk

4.5 Ticketing & Workflow Automation

Planned Planned capabilities:

Real‑time bi‑directional ticket synchronization
Multi‑ticket per incident
Automatic ticket state → incident state mapping
Workflow templates and playbooks

Business value:

Reduced manual ticket handling
Better alignment between NOC and ITSM
Faster resolution workflows

4.6 Real‑Time Dashboards & Collaboration

Planned Planned capabilities:

Streaming dashboards and push updates (WebSockets)
Live topology and map updates
Collaborative incident workspaces
Post‑mortem and reporting tools

Business value:

Real‑time situational awareness
Improved collaboration during major incidents
Strong operational reporting and analytics

5. Architectural Continuity

A key design goal of IIMS is that Planned builds directly on Implemented without breaking existing workflows.

Implemented already provides:

Provider‑agnostic adapters
Routing abstraction (targets + collectors)
Domain‑driven core model
Cached read models
Policy engines for links and routing

These foundations allow Planned automation to be added incrementally:

Without changing the UI contract
Without rewriting domain models
Without disrupting operations

6. Summary

Implemented establishes IIMS as a unified operational coordination platform with:

Strong inventory and topology foundation
Stable Zabbix and Zammad integrations
Reliable alert suppression and incident handling
Fast, cached dashboards and geo visualization

Planned evolves IIMS into an intelligent operations automation platform by adding:

Automated correlation and RCA
Topology‑driven impact analysis
SLA enforcement and escalation
Multi‑provider resilience
Real‑time collaboration and analytics

Together, these phases position IIMS as a long‑term strategic operations platform capable of growing from unified visibility into advanced autonomous operations.