SEE IT IN ACTION
The Challenge
CMDB export. APM spreadsheet. Visio diagrams. PowerPoint capability model. Two portfolios, different vocabularies, no common language. The mapping exercise starts from a blank spreadsheet and two architects who will spend the next three weeks building it row by row.
Every status report depends on it. Every executive decision is made against it. By the time it reaches the steering committee, it reflects the work of the architects who had time to contribute to it, not the full picture of what each organization owns. When the executive asks about something not yet covered, the answer is a follow-up email.
Both organizations use the word "Application" but mean slightly different things by it. One uses "BusinessOwner." The other uses "ProductManager." The normalization decisions that make the comparison possible are never written down as a formal deliverable. They are informal consensus, carried by the architects who attended the meeting where the consensus happened.
When you use AI Augmented Architecture for M&A Integration
Claude ingests the source files from both organizations into Sparx EA packages. CMDB exports, APM spreadsheets, and existing architecture documentation become queryable packages with source metadata preserved. The acquired company's portfolio is a model that can be compared structurally, not a file to be reviewed row by row.
Claude proposes the vocabulary mappings and normalization rules based on the data you have. The architect adjudicates each decision. The metamodel is written, versioned, and persisted in the repository. It becomes the shared working standard for the full integration program: a written, adjudicated document that survives the integration window.
The comparison runs from the normalized view. Each candidate equivalent arrives with the signals that produced it: capability classification, owner domain, downstream dependencies. The rationale shows where the match holds and where it is ambiguous. The architect adjudicates with context in front of them, not with a row in a spreadsheet.
Accepted equivalents, gap list (acquired elements with no current company equivalent), functional overlaps, rationalization candidates. The integration management office receives an adjudicated view with an auditable trail, not a spreadsheet with a confidence-level column. The rationalization decisions belong to the executive committee. AI Power Tools for EA produces the evidence base those decisions are made against.
Decisions are persisted as connectors with adjudication dates. compare_baseline shows the full change set. When the integration management office asks how a decision was reached, the answer is in the repository.
AI POWER TOOLS FOR ENTERPRISE ARCHITECT
86 tools. Full read/write access to your Sparx EA model. Seven-day free trial. No credit card required to start.
HOW TO GET STARTED
Understand your starting point
Get AI Power Tools for EA running
Build the habit across your team
FREQUENTLY ASKED QUESTIONS
No. Claude ingests whatever format they have. CMDB exports, APM spreadsheets, Org Charts, XMI exports from any EA tool, and structured architecture documentation are all viable starting points. The acquired company does not need to change anything about their systems or tools.
CMDB exports in CSV or Excel format, APM portfolio spreadsheets, XMI exports from any EA tool, structured architecture documentation including Visio files where the data is sufficiently structured, and PowerPoint capability models where the taxonomy is explicit. If the data is structured, AI Power Tools for EA can ingest it.
It is the shared vocabulary both datasets are normalized to before the comparison runs. Without a common metamodel, comparison is name-matching. With one, the comparison is structural: it runs against common field definitions, common taxonomy levels, and common ownership patterns. The metamodel is also a deliverable for the integration program: a written, adjudicated standard for what each term means. It survives the integration window.
No. The retain, retire, and consolidate decisions belong to the executive committee and integration leadership. The role of AI Power Tools for EA is to produce the comparison view and the evidence base so those decisions are made on a solid foundation. Every decision the tool surfaces carries the rationale. Every decision the architect makes is recorded in the model. The human team owns the outcomes.
The data is processed locally within your Sparx EA environment. AI Power Tools for EA connects Claude to the Enterprise Architect software running on your computer via EA's automation interface. The source files are read by Claude in the context of your local session. No content is transmitted to an external service. Nothing is retained between sessions. The data stays inside your environment throughout the capture, metamodel, normalization, comparison, and findings steps.
A discovery call takes thirty minutes and tells both of us whether this is the right fit for your acquisition, your source data, and the window you are working in.
Schedule a Discovery Call