add itil section

Author: fredericcarre

config/en/mkdocs.yml

@@ -6,6 +6,7 @@ repo_url: https://xcomponent.github.io/appcontrol-documentation/
 
 nav:
     - Introduction: index.md
+    - AppControl and ITIL: itil.md
     - Getting Started:
           - Introduction to AppControl SaaS: gettingStarted
           - Demo setup with no connection to local infrastructure: gettingStarted/#try-demo

docs/en/index.md

@@ -29,6 +29,11 @@ While many traditional monitoring solutions focus primarily on servers, networks
 -   **Ease of Deployment**: Simple installation with quick configuration and minimal effort.
 -   **Scalable**: Adapts to the needs of your business as it grows.
 
+## AppControl and ITIL: Bridging the Gap Between Teams
+
+In modern IT organizations, incident and problem management require seamless collaboration across Operations, Development, Support, and Business teams. AppControl enhances ITIL practices by automatically linking incidents to affected application components, reducing diagnostic time, and improving cross-team communication.
+Unlike traditional monitoring tools, AppControl provides a unified view of applications to accelerate incident resolution and foster continuous improvement, making it a key complement to ITSM solutions.
+
 ## Why Choose AppControl?
 
 AppControl is specifically designed for businesses that:

docs/en/itil.md

@@ -0,0 +1,77 @@
+# 📌 AppControl and ITIL: A Cross-Team Tool for Incident Management and Continuous Improvement
+
+## 🎯 **The Gap in Traditional ITIL Approaches**
+
+In a standard ITIL approach, ITSM tools (ServiceNow, Jira Service Management, BMC Helix...) are primarily **focused on ticket management**. They structure incident, problem, and change tracking but have several limitations:
+
+-   **Fragmented teams**: Operations, Development, Support, and Business often work in silos using different tools.
+-   **Lack of application visibility**: Incidents are often reported without a clear link to the affected components.
+-   **Reactive rather than proactive management**: Incident analysis relies on often incomplete or manual data.
+
+These limitations lead to wasted time, diagnostic errors, and inefficiencies in incident and problem management.
+
+---
+
+## 🚀 **AppControl: A Cross-Team Solution for ITIL**
+
+AppControl acts as the **missing link** between ITSM and application management. Its added value is based on **four key pillars**:
+
+### 1️⃣ **Automatically Linking Incidents to IT Components**
+
+✅ Each incident is **directly associated** with the impacted application components (services, databases, APIs, VMs...).
+✅ Reduced diagnostic time and better understanding of dependencies.
+
+### 2️⃣ **Facilitating Cross-Team Collaboration**
+
+✅ A **shared view** of applications between operations, development, support, and business teams.
+✅ Eliminates silos: every team can see the impact of incidents on critical components.
+
+### 3️⃣ **Accelerating Resolution and Continuous Improvement**
+
+✅ **Automation** of information gathering and diagnostics.
+✅ Incident history tracking and **root cause identification** to reduce recurring problems.
+
+### 4️⃣ **An Ideal ITSM Complement (Evolved CMDB)**
+
+✅ AppControl enhances ITIL management by providing a **dynamic SI mapping**.
+✅ A direct link between **incidents, problems, and technical components**, facilitating post-mortem analysis and continuous improvement.
+
+---
+
+## 🔥 **Why Choose AppControl in an ITIL Approach?**
+
+| ITIL Criteria                               | Without AppControl                                | With AppControl                                        |
+| ------------------------------------------- | ------------------------------------------------- | ------------------------------------------------------ |
+| 🔍 **Application Visibility**               | Incidents often disconnected from real components | Incidents **directly linked to IT components**         |
+| 🏗️ **Cross-Team Collaboration**             | Silos between Ops, Dev, Support, and Business     | A **unified and shared** incident view                 |
+| ⏳ **MTTR (Mean Time to Repair) Reduction** | Manual and slow analysis                          | Rapid diagnosis via **dynamic mapping**                |
+| 🔄 **Continuous Improvement**               | Difficult to identify root causes                 | Incident pattern analysis and **proactive prevention** |
+
+---
+
+## 💡 **Use Case: Incident Management with AppControl**
+
+🔴 **Without AppControl:**
+
+1. An incident is detected on a critical application.
+2. The support team opens an ITSM ticket.
+3. Manual research is conducted to identify affected components.
+4. Difficulty in determining the cause and impact.
+5. Long resolution time and risk of recurrence.
+
+🟢 **With AppControl:**
+
+1. AppControl **detects the incident** and immediately identifies the **impacted components**.
+2. Teams receive an **enriched notification** with key information.
+3. Resolution is **accelerated** thanks to mapping and associated logs.
+4. A post-mortem analysis helps prevent similar incidents.
+
+---
+
+## 🎯 **AppControl: Modernizing ITIL with an Agile Approach**
+
+AppControl does not replace ITSM tools but **complements them intelligently**, facilitating **cross-team information sharing** and optimizing **incident and problem resolution**.
+
+✅ **Unified application and infrastructure visibility**.
+✅ **Enhanced cross-team collaboration**.
+✅ **Continuous improvement and recurrence reduction**.

mkdocs_push.yml

@@ -7,6 +7,7 @@ repo_name: 'GitHub Project'
 
 nav:
     - Introduction: index.md
+    - AppControl and ITIL: itil.md
     - Getting Started:
           - Introduction to AppControl SaaS: gettingStarted.md
           - Demo setup with no connection to local infrastructure: gettingStarted/#try-demo