How enterprise architecture fits into AI adoption

Start with the enterprise systems landscape

An AI initiative rarely sits apart from existing business processes. Map the systems and workflows involved before deciding where AI belongs. Finance, supply chain and manufacturing provide a useful example: each spans connected processes, and a change in one part of the landscape can affect work elsewhere. Rohan Hall’s enterprise systems background includes global implementations across these areas, including a PeopleSoft ERP implementation at Corning spanning the United States, Europe and Asia.

Connect adoption to the operating model

Architecture decisions are not only about where a capability runs. Consider who will use it, how work will change and what education is needed to support that change. This is the difference between fitting AI into an existing workflow and treating it as a separate experiment. Hall’s enterprise AI and transformation work encompasses operating models, education and workflow transformation as part of moving toward durable capability.

Build trust into the architecture

As an AI initiative moves toward broader use, make evidence, transparency, governance, assurance and standards part of the adoption discussion. Enterprise architects can use these considerations to examine how a proposed capability will be understood and overseen, rather than leaving trust questions until after deployment.

Plan for knowledge to spread

A capability is harder to sustain if understanding stays with a small group. Include learning and knowledge transfer in the architecture plan. Hall has taught PeopleSoft courses and train-the-trainer programs for implementation partners and enterprise customers, and helped develop curriculum for manufacturing and related enterprise systems. His knowledge-activation work focuses on turning expertise into scalable learning and organizational capability.

Frequently asked questions

Where should an enterprise architect begin with an AI initiative?

Begin with the business process: identify the workflow, the systems it depends on and the people whose work may change. Then examine the operating model, education and governance needed if the initiative expands beyond experimentation.

Why does ERP experience matter to this discussion?

ERP work brings finance, supply chain, manufacturing, integration and business processes into the same architecture conversation. That experience can help frame AI adoption within a connected enterprise landscape rather than as an isolated tool.

What perspective does Rohan Hall bring beyond systems implementation?

He has researched emerging-technology trends and their impact on financial services and the enterprise, alongside his work in enterprise architecture, education and transformation.