Why getting started was slow
Cloud Pak for AIOps leaned heavily on on-premises installs. The root causes we started from:
- {{ c.n }}{{ c.b }} {{ c.t }}
Why BYOC, and why on MCSP
Customers wanted a managed service without their data leaving their own cloud. The Multi-cloud SaaS Platform (MCSP) already had the shape for that: one part IBM runs, one part the customer owns.
CONTROL PLANE · IBM RUNS IT
Service orchestration, platform updates, lifecycle operations and overall service health. One consistent management layer.
DATA PLANE · THE CUSTOMER OWNS IT
Runs inside the customer's own AWS account and connects securely to IBM's control plane, so the data stays in their environment.
THE TAKEAWAY
MCSP provides the shared platform and architecture. InnerSource lets product teams like AIOps reuse and extend it, instead of building their own.
Benchmark, assess, align, recommend
- {{ ph.n }}{{ ph.t }}
- {{ it }}
From marketplace to a running instance
The research ended with the BYOC journey laid out end to end, so design could start from the real technical flow. Three stops:
STOP {{ cur.n }} OF 3
{{ cur.t }}
{{ cur.d }}
I handed over the prep
- ✓Root causes, benchmarks and the existing AIOps experience reviewed.
- ✓End-to-end technical flow mapped with architects and engineers.
- ✓Recommendations for a guided setup handed to the design phase.
- –Design and build: picked up by the team after the research. Not my work, so not shown here.
Curious about the research?
happy to talk it through on a call
aayush.kriti3@gmail.com