A major platform vendor just built its enterprise AI story around an uncomfortable admission: most organizations are running more AI in production than they can name, and that gap has turned from a hygiene issue into a budget and audit exposure.
At Knowledge 2026, ServiceNow expanded its AI Control Tower from a governance layer into what it now calls an enterprise AI command center, operating across five dimensions — discover, observe, govern, secure, and measure. Discovery is the revealing one. Thirty new connectors reach across AWS, Google Cloud, and Azure, plus SAP, Oracle, and Workday, to find AI assets wherever they run rather than only inside ServiceNow, and the model pulls non-human identities and connected devices in alongside them. New dashboards track model spend and return. ServiceNow says it monitors more than 1,600 AI assets across its own estate — a useful tell about how fast this sprawls even inside a company that builds the tooling. The governance frameworks ship aligned to NIST and the EU AI Act.
Two Pressures, One Prerequisite
Two pressures are landing on the CIO's desk at the same time. AI spend is scaling faster than anyone budgeted, and the accountability bar is rising — the EU AI Act as binding law, frameworks like NIST's AI RMF as the emerging standard of care — toward a defensible account of which models are running, on what data, making which decisions. Both pressures share one prerequisite: an accurate, current inventory of AI assets across the estate. Most organizations don't have one, because the AI never came through a single door. It arrived as a SaaS feature here, a hyperscaler service there, a team's retrieval pilot somewhere else.
The Integration Problem Beneath the Dashboard
That makes the inventory an integration problem as much as a governance one — and the integration problem has a floor most command-center narratives skip past. A connector can register that a model exists. It takes a different layer to say what data that model was trained and grounded on, where that data came from, and whether the lineage still holds a week later. ServiceNow's fabric maps and reaches the assets; the governed data foundation underneath — the kind Cloudera anchors — is what keeps the answer true as pipelines change. The dashboard is the visible part. The data layer beneath it is what decides whether the dashboard is telling the truth.
That is the part worth internalizing: the seam between systems is where control quietly breaks, and no dashboard resolves a picture the underlying data can't hold. The organizations that can produce a live, sourced inventory — not a static register, but one that reconciles itself as the estate moves — will walk into their next audit describing a system they actually control. Standing that up now, while it's an architecture decision, costs less than reconstructing it later on an examiner's timeline.