---
sourceDocument: Brazil Enterprise Architecture
sourceDocumentLink: https://www.servicenow.com/docs/r/application-portfolio-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Enterprise Architecture

ft:clusterId :

    - appportman

bundleId :

    - appportman

workflow :

    - Technology


---

# AI Control Tower integration with Enterprise Architecture

# AI Control Tower integration with Enterprise Architecture {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 9 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of AI Control Tower integration with Enterprise Architecture

The integration of AI Control Tower with the Enterprise Architecture Workspace enables ServiceNow customers to view and manage AI systems linked to business applications within their enterprise portfolio.
This integration provides a unified approach to AI governance by connecting AI oversight directly to the business applications they support, enhancing risk assessment and governance decisions with full business context.
Show full answer Show less  
This connection helps enterprise architects understand AI adoption and governance status across their application landscape without switching contexts, while AI stewards gain insight into the business impact, ownership, and criticality of the AI systems they govern.

## Key Features

* **Unified AI Governance:** Integrates AI governance into the broader technology portfolio, enabling governance decisions informed by the business applications affected.
* **Business Context for AI:** AI stewards can see which applications depend on each AI system, their owners, and business impact to make better-informed approval and risk classification decisions.
* **Portfolio-wide AI Visibility:** Enterprise architects can identify AI usage and governance status across hundreds of applications within their existing workflows.
* **AI System Lifecycle Tracking:** AI Control Tower manages AI systems through onboarding, risk assessment, build, test, and deployment stages, with lifecycle and risk details visible in Enterprise Architecture.
* **Bidirectional Associations:** AI systems and business applications are linked bidirectionally, allowing viewing and management of associations from both the Enterprise Architecture Workspace and AI Control Tower.
* **Domain Separation Support:** Business applications and AI associations respect domain hierarchies, providing appropriate visibility based on domain context.
* **Multiple Ways to Associate AI Systems:** Users can create AI system records and associate them with business applications via a service portal intake form or manually from the Enterprise Architecture Workspace.
* **Managed vs Unmanaged AI Systems:** The AI systems tab differentiates between AI systems under governance review and those not yet submitted, helping identify governance gaps.

## Key Outcomes for ServiceNow Customers

* **Enterprise Architects:** Gain clear visibility into which business applications use AI, the governance and lifecycle status of those AI systems, and can easily identify governance gaps or risks during portfolio rationalization and management.
* **AI Stewards and Asset Owners:** Obtain critical business context when assessing AI systems, reducing risks in approval by understanding application dependencies, ownership, and business impact. This also supports audit readiness by evidencing application relevance during AI risk and conformance reviews.
* **Improved Risk Management:** Enables more accurate AI risk classification at the application level by connecting AI systems to business processes and organizational impact.
* **Enhanced Collaboration:** Supports collaboration between enterprise architects and AI stewards by providing a shared, synchronized view of AI assets and their business application relationships.

## Practical Usage Notes

* Access to the AI systems tab on business applications requires the APM User role or higher.
* AI Stewards and AI Asset Owners have permissions to add or remove AI system associations.
* Only active business applications (not retired or at end of life) are available for AI system associations.
* Associations are maintained independently of AI system lifecycle status; removing an association does not delete the AI system.
* Upgrading Enterprise Architecture Workspace to version 10.1.3 or later and running the migration job is necessary for customers using earlier integration versions to align data models.  
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 {#eaw-aict__section_ify_sj3_y3c}

The integration between the AI Control Tower and business applications is built around four core themes:

* Unified AI governance: Connect AI oversight to your technology portfolio as an integrated capability. You can make AI governance decisions 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.
{#eaw-aict__ul_zs2_zj3_y3c}

## Why AI systems are connected with business applications {#eaw-aict__section_why_integration}

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 can't form a complete picture of that application's risk
profile. This includes conformance and 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.  
The connection between AI systems and business applications enables you to:

* 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
{#eaw-aict__ul_izp_rk3_y3c}

## Value by persona {#eaw-aict__section_lwz_ll3_y3c}

{#eaw-aict__table_ezm_nl3_y3c__entry__3}

| 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. |
[Table 1. Enterprise Architecture - AI Control Tower integration benefits for personas]

{#eaw-aict__table_ezm_nl3_y3c}

## Value for enterprise architects {#eaw-aict__section_ea_value}

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?

{#eaw-aict__ul_ea_value}

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 {#eaw-aict__section_aict_value}

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 a context of 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, you can show which business applications an AI system supports. Demonstrating that
those applications are active, non-retired, and within scope is a key part of the evidence trail.

## Managed and unmanaged AI systems {#eaw-aict__section_managed_unmanaged}

AI systems in the AI systems tab appear under one of two sections:

Managed
:   AI systems that an AI Steward has reviewed or that an AI Steward is reviewing. AI Control Tower actively governs and tracks managed systems through their lifecycle.

Unmanaged

:   AI systems created in AI Control Tower that users have not yet submitted for AI Steward review and have not entered the governance lifecycle.

Both sections are visible on the business application record. Enterprise architects can see the AI systems that have cleared governance review and 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:
{#eaw-aict__table_ai_systems_columns__entry__2}

| 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 that AI stewards assign to the AI system during governance review. |
[ ]

{#eaw-aict__table_ai_systems_columns}

## How associations are created {#eaw-aict__section_how_associations_created}

Enterprise Architecture supports domain separation at the data level. If your instance uses domain separation, such as a managed service provider hosting multiple client tenants, the available business
applications reflect the domain hierarchy. You can select business applications in the global domain and in the domain you're currently operating in. Viewing the association from a parent domain shows the AI systems and
business application associations created in that domain and in all of its child domains. A child domain's view shows only its own associations.  
An organization has a business application in the global domain and two business applications, one each in the Domain A and Domain B child domains. A user operating in Domain A can associate an AI
system with the global business application, the Domain A business application, or both. The user can't select the Domain B business application. A user at the parent domain can see the AI system associations created in both
Domain A and Domain B. These associations are rolled up together wherever they involve the shared global business application.
Users associate an AI system 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. Use this 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 for AICT plugin (`com.sn_ea_aict`) is installed. This plugin installs automatically when you install the AI Control Tower Core plugin at the required version. If your instance does not meet the minimum version, or if the Enterprise Architecture for AICT plugin is not installed, the Business application field does not appear on the form. For version requirements and what to expect if your Enterprise Architecture Workspace, AI Risk and Compliance, and AI Control Tower Core plugins are upgraded out of sync, see [Enterprise Architecture for AICT plugin installation and upgrade considerations](https://www.servicenow.com/docs/access?context=aict-ea-common-upgrade-considerations&version=brazil&pubname=brazil-intelligent-experiences&ft:locale=en-US).

  For information on how to create an AI use case, see [Request an AI use case](https://www.servicenow.com/docs/access?context=request-ai-system&version=brazil&pubname=brazil-governance-risk-compliance&ft:locale=en-US) or [Create AI system assets](https://www.servicenow.com/docs/access?context=create-ai-system-assets-newexperience&version=brazil&pubname=brazil-intelligent-experiences&ft:locale=en-US).

  For information on the Request an AI use case form fields, see [Request an AI use case form](https://www.servicenow.com/docs/access?context=request-ai-system-form&version=brazil&pubname=brazil-governance-risk-compliance&ft:locale=en-US).
* 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. Use this to associate AI systems that were not submitted through the service portal intake form. For information, see [Add an existing AI system to a business application](https://www.servicenow.com/docs/unyF52unQxm~DJLrUwsj~Q "Associate an existing AI Control Tower AI system with a business application from the Enterprise Architecture Workspace.").

{#eaw-aict__ul_assoc_methods}

Only active business applications are available for association. The system automatically excludes business applications with a status of Retired or a lifecycle stage of End of Life. 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.

If you activated the AI Control Tower and Enterprise Architecture Workspace integration on a Enterprise Architecture Workspace version earlier than 10.1.3, upgrade to version 10.1.3 or later. Then run the Migrate BA Product Model Map from EA Workspace job. This job migrates existing AI system-to-business application associations to the Enterprise Architecture for AICT plugin's data model. The job does not run automatically. For steps, see [Run the Migrate BA Product Model Map job](https://www.servicenow.com/docs/2_niIJA8dwCiWnyqZOP52Q "Run this job to migrate existing AI system-to-business application associations to the new Enterprise Architecture for AICT data model after activating the AI Control Tower and Enterprise Architecture integration.").

## Viewing associated business application in AI Control Tower {#eaw-aict__section_j4r_gp3_y3c}

The association between AI systems and business applications is bidirectional. To view linked business applications in AI Control Tower, navigate to WorkspacesAI Control TowerAI AssetsAI systemsSelect an AI systemDetailsBusiness applications. This view is read-only in AI Control Tower; to add or remove associations, use the Related assetsBusiness applicationsAI systems tab on the business application record in the Enterprise Architecture Workspace.

Enterprise architects work primarily in the Enterprise Architecture Workspace, while AI stewards work primarily in AI Control Tower. This bidirectionality means each team sees the same associations from their own workspace. Each team can view and work with
the associations without maintaining a separate record.

## Required roles {#eaw-aict__section_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.
**Related concepts**   

* [Exploring the AI Portfolio tab on the Enterprise Architecture Workspace dashboard](https://www.servicenow.com/docs/tySdpCK2Qao~4aiSTwVm2A "The AI Portfolio tab on the Enterprise Architecture Workspace dashboard provides visualization widgets that show how business applications and AI systems in your organization are associated.")  
**Related tasks**   

* [Remove an AI system from a business application](https://www.servicenow.com/docs/ysmK9FaaLLMk7PRedEzCNw "You can remove an AI system from a business application record in the Enterprise Architecture Workspace.")
* [View AI system details from a business application](https://www.servicenow.com/docs/HqipNjLuy32H85xweDiMnw "You can open an AI system record in the AI Control Tower Workspace directly from the AI Systems tab on a business application record in the Enterprise Architecture Workspace.")
* [Run the Migrate BA Product Model Map job](https://www.servicenow.com/docs/2_niIJA8dwCiWnyqZOP52Q "Run this job to migrate existing AI system-to-business application associations to the new Enterprise Architecture for AICT data model after activating the AI Control Tower and Enterprise Architecture integration.")  
**Related topics**   

* [AI Control Tower Home](https://www.servicenow.com/docs/access?context=ai-control-tower-home-page&version=brazil&pubname=brazil-intelligent-experiences&ft:locale=en-US)
* eaw-exploring-the-ai-portfolio.html
* [Enterprise Architecture for AICT plugin installation and upgrade considerations](https://www.servicenow.com/docs/access?context=aict-ea-common-upgrade-considerations&version=brazil&pubname=brazil-intelligent-experiences&ft:locale=en-US)
* [Associate a business application with an AI system](https://www.servicenow.com/docs/access?context=disc-asset-associate-business-application&version=brazil&pubname=brazil-intelligent-experiences&ft:locale=en-US)

*[\>]: and then


