@c5 Having worked at DXC, I’d like to see a lot less marketing language around OASIS and a lot more technical detail about what it actually does.
From an infrastructure operations standpoint, nothing has changed about the fundamentals. A server, switch, firewall, storage array, backup platform, hypervisor, or endpoint does not magically become visible because an AI platform is sitting above it.
Something still has to collect the data and something still has to execute the action.
That means agents, APIs, SNMP, collectors, telemetry, monitoring platforms, backup software, network-management tools, ServiceNow, Dynatrace, and the rest of the operational stack are still doing the heavy lifting.
OASIS appears to be an AI/AIOps orchestration layer sitting on top of those systems. It can correlate events, identify patterns, recommend remediation, and potentially trigger automation — but it still depends on the underlying tools to tell it what is happening and to actually make something happen.
So when I read statements suggesting OASIS is transforming how infrastructure is “managed,” my first question is: What exactly is OASIS doing that the existing tools are not?
Show us the architecture.
Show us how a failed backup is detected and restarted.
Show us how a network fault is identified and remediated.
Show us how it interacts with Windows, Linux, VMware, storage, firewalls, routers, switches, and backup platforms.
And most importantly, show us where OASIS stops and the traditional infrastructure-management tools begin.
That would tell infrastructure people far more than another AI marketing statement.