How a Bank Built an Automated Operations Platform and CMDB Middle‑Platform

1. Bank Transformation

Ping An Bank’s rapid internet‑driven transformation forced a massive increase in servers, services, and concurrent requests, exposing the limits of its legacy, monolithic architecture and prompting the need for a more adaptable, tool‑driven operations platform.

2. Identify Problems

Low automation coverage : automation was fragmented, leaving many steps manual and increasing risk as scale grew.

Opaque configuration data : reliance on disparate Excel sheets caused duplication, omission, and lack of a closed‑loop view.

Insufficient standardization : inconsistent processes across the workflow chain prevented reliable automation.

Complex change‑control monitoring : regulatory reporting requirements made change management cumbersome.

Limited tool capability : reliance on third‑party products hindered rapid iteration and integration.

3. Recommendations

To address these gaps the team built a comprehensive CMDB that serves as the foundation for AIOps and DevOps. By aggregating data from network, application, container, virtual machine, and storage domains into a unified model, the CMDB provides accurate, real‑time relationships, enabling data‑closure, cross‑domain subscription, and automated validation.

Data is ingested via a message bus, cleaned, and stored in MongoDB for persistence, while Elasticsearch (referred to as “GraphSQL”) indexes flattened records for sub‑second retrieval across tens of thousands of assets.

The platform also introduces a subscription‑driven event model: when a domain publishes a change (e.g., a new database instance), interested services receive the update automatically, ensuring consistent state without manual coordination.

4. Capabilities Required for an Operations Middle‑Platform

Key capabilities include:

Task orchestration with reusable scripts and templated workflows.

Gray‑scale execution to safely roll out commands across large fleets.

High‑risk detection for disaster‑avoidance scenarios.

Relationship identification via the CMDB to map assets to applications and services.

Compliance handling through integrated ITSM and regulatory reporting.

These functions are exposed through a unified portal that allows one‑click execution of complex change‑sets, migration, failover, and scaling operations.

5. Summary

Building a middle‑platform around a robust CMDB enables closed‑loop data, automated workflows, and scalable operations in a heavily regulated banking environment, turning a traditionally rigid infrastructure into a flexible, observable, and compliant system.