AI Control Tower integration with Enterprise Architecture
Summarize
Summary of AI Control Tower integration with Enterprise Architecture
The AI Control Tower integration with Enterprise Architecture enables ServiceNow customers to view and manage AI systems linked to business applications directly within the Enterprise Architecture Workspace. This integration provides unified AI governance by connecting AI oversight with the broader technology portfolio, enriching AI governance decisions with business context, and giving enterprise architects portfolio-wide visibility of AI adoption and governance status.
Show less
By associating AI systems with business applications, organizations gain a complete picture of AI-related risks, conformance, and operational dependencies, which traditional Enterprise Architecture alone cannot provide. This integration supports governance activities throughout the AI lifecycle—from onboarding through deployment—while grounding decisions in the business impact of AI systems.
Key Features
- Unified AI governance: Connect AI systems to business applications for integrated oversight and informed governance decisions.
- Business context for AI: AI stewards can view which applications depend on AI systems, their owners, and business criticality, improving risk classification and accountability.
- Portfolio-wide AI visibility: Enterprise architects can see AI adoption, governance states, and pending approvals across their application portfolio without switching workspaces.
- AI systems tab on business application records: Displays managed and unmanaged AI systems, their lifecycle phases, states, risk classifications, and governance status.
- Bidirectional associations: AI systems and business applications are linked and visible in both AI Control Tower and Enterprise Architecture Workspace, ensuring consistent, up-to-date information for both enterprise architects and AI stewards.
- Association methods: AI systems can be linked to business applications either through the service portal's “Request an AI Use Case” form (recommended) or manually by users with the APM User role.
Value for ServiceNow Customers
Enterprise Architects
- Gain clear visibility of which business applications use AI and their governance status directly within the Enterprise Architecture Workspace.
- Assess AI-related risks as part of application portfolio management, including identifying AI systems pending approval or under review.
- Make informed decisions during application rationalization or retirement by understanding AI system dependencies.
AI Stewards and AI Asset Owners
- Access business context for AI systems under governance, including application dependencies and ownership, leading to better risk assessments and accountability.
- Reduce the risk of approving AI systems without full understanding of their business impact.
- Support audit readiness with a clear evidence trail of AI systems supporting active and in-scope business applications.
Practical Considerations
- Only active business applications are available for AI system association; retired or end-of-life applications are excluded automatically.
- Removing an AI system association from a business application does not delete the AI system record; governance continues independently.
- Viewing AI system associations requires the APM User role or higher; adding or removing associations requires AI Steward or AI Asset Owner roles.
- The “Business Application” field on the AI use case request form requires Enterprise Architecture Workspace version 9.0.1 (Zurich) or 8.0.3 (Australia) or later.
View and manage the AI systems associated with a business application from the Enterprise Architecture Workspace to understand AI risk and governance status as part of your broader application portfolio.
Key benefits of AI Control Tower integration with Enterprise Architecture
- Unified AI governance: Connect AI oversight to your technology portfolio as an integrated capability. AI governance decisions can be made with full awareness of the business applications they affect.
- Business context for AI: AI governance without business context is incomplete. AI stewards can see the applications, owners, and business impact tied to every AI system they govern — enabling better-informed decisions on approval, risk classification, and accountability.
- Portfolio-wide AI visibility: Enterprise architects get AI adoption and governance status surfaced directly in their existing workflows — no context switching required. An enterprise architect responsible for hundreds of business applications can see exactly which ones are using AI, and whether that AI has been approved.
Why AI systems are connected with business applications
Enterprise Architecture manages business applications by tracking their costs, business value, functional fitness, and risk. AI systems embedded in or supporting those applications introduce a new category of risk — one that requires dedicated governance beyond what traditional Enterprise Architecture covers. Without visibility into which AI systems are associated with each business application, an enterprise architect cannot form a complete picture of that application's risk profile, conformance, or operational dependencies.
At the same time, AI Control Tower governs AI systems through their full lifecycle — from onboarding and risk assessment through build, test, and deployment. However, AI governance is most effective when AI systems are understood in their business context: which applications depend on them, which business processes they support, and what the organizational impact would be if they were changed or decommissioned. That context lives in the Enterprise Architecture Workspace.
The integration between the Enterprise Architecture and AI Control Tower addresses both gaps. Enterprise architects can assess AI risk at the application level. AI stewards can ground governance decisions in business impact. Together, they give your organization a unified view of AI activity that spans both the application portfolio and the AI asset inventory.
- Track total cost of ownership: Track AI systems related budgets at a business application level
- Track ownership and accountability: Track AI system ownership through the business application it serves
- Track AI system impact: Track the business impact the AI system is creating by connecting the AI system's technical outputs to the business functions it supports
Value by persona
| Persona | Before integration | After integration |
|---|---|---|
| Enterprise architect | I manage 500 business applications but have no idea which ones are using AI or whether that AI is approved. | I can see AI adoption across my application landscape and understand governance status from my existing workspace. |
| AI steward | I govern AI systems but don't understand their business context—who owns the applications using them, how critical they are. | I see exactly which business applications depend on each AI system and who's accountable. |
Value for enterprise architects
The AI systems tab on a business application record lets enterprise architects answer questions that were previously difficult to address from Enterprise Architecture alone:
- Which AI systems are running inside or alongside this business application?
- Are any of those AI systems still not reviewed and pending AI Steward approval?
- What is the governance and lifecycle status of each AI system this application depends on?
- If this application is being rationalized or retired, which AI systems will be affected?
- What is the AI adoption picture across my entire application portfolio, and where are the governance gaps?
Because the AI systems tab surfaces data directly from AI Control Tower, enterprise architects don't have to switch workspaces or contact the AI governance team to get these answers. The AI system's lifecycle phase, state, lifecycle status, and risk classification are all visible from the business application record.
Value for AI stewards and AI asset owners
AI Control Tower tracks AI systems through four lifecycle stages: onboard, assess, build and test, and deploy. At each stage, governance decisions — such as risk classification, conformance review, and approval — benefit from knowing the business context of the AI system being evaluated.
Without this integration, an AI steward reviewing a submitted AI system sees only its technical attributes. They have no visibility into which business applications depend on the system, who owns those applications, or how critical those applications are to the organization.
By associating AI systems with business applications, AI Stewards and AI Asset Owners gain visibility into the business scope of each AI system before they begin governance activities. This reduces the risk of approving or escalating an AI system without understanding which business processes and applications it affects.
The business application associations on an AI system record also support audit readiness. During an AI risk assessment or conformance review, being able to show which business applications an AI system supports — and that those applications are active, non-retired, and within scope — is a key part of the evidence trail.
Managed and unmanaged AI systems
AI systems in the AI systems tab appear under one of two sections:
- Managed
- AI systems that an AI Steward has reviewed or is under review. Managed systems are actively governed and tracked through their lifecycle in AI Control Tower.
- Unmanaged
-
AI systems created in AI Control Tower that have not yet been submitted for AI Steward review and have not entered the governance lifecycle.
Both sections are visible on the business application record so that enterprise architects can see not only the AI systems that have cleared governance review, but also those still awaiting it. An application with several unmanaged AI systems warrants closer attention during portfolio assessments and rationalization exercises.
The tab displays the following information for each AI system:
| Column | Description |
|---|---|
| Display name | The name of the AI system. |
| Provider | The organization or vendor that provides the AI system. |
| Vendor | The technology vendor associated with the AI system. |
| Managed by | The role responsible for managing the AI system, such as AI Asset Owner. |
| Lifecycle phase | The current phase in the AI system lifecycle: New, Assess, Build and test, or Deploy. |
| State | The current state of the AI system record, such as Development. |
| Lifecycle status | The review or approval status, such as AI steward review. |
| Risk classification | The risk level assigned to the AI system during governance review. |
How associations are created
An AI system is associated with a business application in one of two ways:
- A user submits the Request an AI Use Case catalog item in the service portal and selects one or more business applications in the Business Applications field. This is the
recommended intake path because it creates the AI system record in AI Control Tower and establishes the business application association in a single step. Note:The Business Application field is only displayed on the service catalog page for the AI system use case if the Enterprise Architecture Workspace version meets the minimum requirement. The field requires Enterprise Architecture Workspace version 9.0.1 or later for Zurich, or version 8.0.3 or later for Australia. If your instance does not meet the minimum version, the Business application field will not appear on the form.
For information on how to create an AI use case, see Request an AI use case.
For information on the Request an AI use case form fields, see Request an AI use case form.
- A user with the APM user (sn_apm.apm_user) role manually adds an AI system from the AI systems tab on a business application record in the Enterprise Architecture Workspace. This is useful for associating AI systems that were not submitted through the service portal intake form. For information, see Add an existing AI system to a business application.
Only active business applications are available for association. Business applications with a status of Retired or a lifecycle stage of End of Life are excluded automatically, so the associations on an AI system record reflect only applications that are currently in scope for portfolio management.
Removing an AI system association from a business application record does not delete the AI system record from AI Control Tower. The AI system continues through its governance lifecycle independently of its application associations.
Viewing associated business application in AI Control Tower
The association between AI systems and business applications is bidirectional. To view linked business applications in AI Control Tower, navigate to . This view is read-only in AI Control Tower; to add or remove associations, use the tab on the business application record in the Enterprise Architecture Workspace.
For enterprise architects who work primarily in the Enterprise Architecture Workspace and AI stewards who work primarily in AI Control Tower, this bidirectionality means each team sees the same associations from their own workspace without requiring the other team
to maintain a separate record.
Required roles
To view the AI systems tab on a business application record, you must have the APM User role (sn_apm.apm_user) or higher. Users with the AI Steward (sn_aig.ai_steward) or AI Asset Owner (sn_aig.ai_asset_owner) role can add or remove AI system associations.