Skip to content
Enterprise Internal2026

Agentic AIOps Blueprint

Intelligent ITSM & Infrastructure Mapper

Emerging Technologies Engineer Enterprise IT Operations & ITSM

A multi-agent system that reads live infrastructure and auto-generates compliant ITSM design and operational documents.

An infrastructure-mapping platform whose agents read Infrastructure-as-Code and Kubernetes configs, trace CI/CD and data flows, and emit compliant SOPs, Low-Level Designs and Microsoft Word deliverables for ITSM.

System Architecture

mapIaC / K8sConfigsCI/CD PipelinesData flowsTopology IngestParserAgentic MapperLangGraphInfra → LLDDesign docsSOP / SOW GenRunbooksCompliance FmtMS WordITSMApprovals
IaC and CI/CD signals feed an agentic mapper that synthesises LLDs, SOPs and compliant Word docs, driving down ITSM rejections.

Live Demo

booting live pipeline…

The Problem

Bridging MLOps environments to enterprise ITSM compliance was manual and error-prone: runbooks took days to write and approvals were frequently rejected for inaccurate topology.

What I Engineered

  • Spearheaded an infrastructure-mapping platform whose coordinated agents bridge MLOps environments and enterprise ITSM compliance.
  • Built an engine that reads Infrastructure-as-Code, including Kubernetes pod configs, to auto-generate operational SOPs and SOWs.
  • Developed Infrastructure-to-LLD mapping that traces CI/CD pipelines and distributed data flows into Low-Level Design docs.
  • Automated generation of compliant Microsoft Word deliverables, eliminating manual formatting overhead for ITOps.

Impact & Scale

  • Accelerated deployment-to-production timelines by 35%
  • Cut runbook creation from days to under 10 minutes per deployment
  • Reduced ITSM approval rejection rates by over 90% via accurate topology mapping
  • Eliminated 100% of manual compliance-formatting overhead
Deploy time−35%
RunbookDays → <10 min
Rejections−90%

Engineering Decisions

  1. 01

    Derived design from live IaC and Kubernetes state, not the CMDB.

    ITSM approvals were being rejected for inaccurate topology. Reading the actual Infrastructure-as-Code and pod configs, the real source of truth, removed the drift that documentation-based mapping always accumulates.

  2. 02

    Extracted topology with deterministic parsers before the agent reasons over it.

    Structure is parsed by code and handed to the LLM as verified facts, so the agent reasons over real infrastructure instead of inventing components. Non-determinism is confined to synthesis, never to what exists.

  3. 03

    Emitted native, compliant Word / SOP artifacts in the exact format ITSM already requires.

    Compliance reviewers live in fixed Word templates. Generating those deliverables directly eliminated manual reformatting entirely, a larger operational win than asking an org to adopt a new tool.

Stack

Multi-Agent SystemsLangGraphAzure OpenAIKubernetesInfrastructure-as-CodeCI/CDPythonITSM

Source is HPE-internal and cannot be published — architecture and trade-offs walked through on request.

Open to AI Software Development & Platform Engineering roles

Need someone who ships systems like this into production?