AI Integrations
EA GraphLink’s GraphQL API connects your Sparx EA repository directly to Power BI. Your architecture data flows from the repository through EA GraphLink into Power BI datasets, which feed live dashboards. When you update application records, technology components, or architecture decisions in EA, those changes appear in Power BI automatically: no exports, no batch jobs, no manual refresh cycles.
The Power BI Connector add-in abstracts the GraphQL complexity. Your Power BI analysts work with familiar Power BI data models and visual design tools. Behind the scenes, the connector translates GraphQL queries into Power BI datasets. The result: live architecture dashboards that stakeholders trust because they’re current, authoritative, and integrated into the BI platform they already use for financial, operational, and HR data.
This is not a one-time data export. It’s not periodic reporting. It’s a continuous data flow that keeps architecture information synchronized with reality.
The shift from reactive reporting to proactive insight.
Your current state: Stakeholders ask for architecture information. Architects spend 2-8 hours compiling exports, creating PowerPoint visualizations, sending PDFs via email. By the time the report lands, some facts have changed. Next week, a different stakeholder asks a variant of the same question. The cycle repeats.
Your future state: Architecture dashboards live in Power BI alongside financial dashboards, operational KPIs, and HR metrics. Stakeholders pull the information they need on their own timeline. When data changes, dashboards update automatically. Architects spend those 2-8 hours developing deeper insight instead of formatting reports. Architecture information becomes self-service rather than request-driven.
The enabling mechanism is continuous synchronization. Your repository is the source of truth. Power BI is the reporting surface. EA GraphLink is the bridge that keeps them synchronized.
You get portfolio visibility without asking architects to interrupt their work. Application lifecycle status, technology investment by portfolio category, compliance coverage, technical debt trends: all live in the same BI environment where financial and operational data live. One source of truth. One governance layer. One platform.
Reporting overhead drops. Dashboards replace monthly or quarterly PowerPoint cycles. Your team stops producing status reports and starts producing strategic insight. The dashboard tells you what’s happening. Your architects analyze why it matters and what to do about it.
Architecture is no longer hidden in a specialized tool. When you need to understand the architecture impact of a decision, the dashboard is in Power BI: the same platform you use for other business intelligence. No new logins. No specialized tools. Architecture data integrated into the business intelligence you already consume.
Application Portfolio Management Dashboard
Status view: which applications are in production, which are sunset candidates, which are under development. Layer in business criticality, customer-facing status, and technical health scoring. Color-code by lifecycle phase. Show investment by category. Executive viewers can see the whole portfolio. Filter down to business-unit-specific views. Drill from portfolio status into individual application detail.
Technology Obsolescence Alerts
Which applications and components are running on technologies approaching end-of-support? Surface this in a dashboard timeline: 30-day, 60-day, 90-day, 180-day risk windows. Link application obsolescence to business criticality: a critical business application on end-of-life technology is a different risk profile than a non-critical one. This dashboard surfaces risk you might otherwise miss in architectural reviews.
Architecture Investment Reporting
Show how your architecture budget is allocated across portfolio categories, technology domains, or business capabilities. Link spending to architecture principles and strategy. Show how architecture investment aligns with business priorities. This is the evidence that architecture is a business function, not just a technical cost center.
Compliance Coverage Visualization
Which architecture principles have coverage across your portfolio? Where are the gaps? Map compliance by business capability, by application, or by technology domain. Show progress over time as you close compliance gaps. For regulatory or risk-sensitive domains (finance, healthcare, government), this dashboard becomes a governance artifact that tracks standards adherence.
Architecture KPIs in Executive Reporting
Blend architecture metrics into executive reporting. Maturity trend, technical debt trajectory, decision velocity, architecture review turnaround time. Track how these metrics move in response to practice improvements. Position architecture as a measurable function contributing to business outcomes.
| Role | Primary Benefit | Secondary Benefit |
|---|---|---|
| IT Executive | Portfolio visibility without special requests | Evidence of architecture’s business contribution |
| Architecture Manager | Reporting hours freed for strategy work | Automated tracking of practice metrics |
| CFO/Finance Leadership | Architecture investment visible in BI platform | Alignment of architecture spend to portfolio strategy |
| Risk/Compliance Officer | Live compliance coverage dashboard | Automated standards tracking |
| Application Owner | Self-service view of their application’s architecture context | No waiting for architect responses to basic questions |
| Portfolio Manager | Real-time application lifecycle and investment visibility | Data to support portfolio decisions |
| Business Stakeholder | Architecture information in familiar BI tool | No specialized training required |
Architecture information should live where decisions happen.
Most organizations have invested heavily in Power BI. It’s the enterprise BI platform. Finance dashboards live there. Operational metrics live there. HR analytics live there. Your executive team opens Power BI every week. Architecture is often missing from that ecosystem: it’s either a specialized report or locked in a tool the business doesn’t use.
This integration makes architecture a first-class citizen in your enterprise business intelligence. Stakeholders don’t have to ask architects for information. They don’t have to learn a new tool. They access architecture data in the platform they already trust for business intelligence.
Continuous synchronization reduces reporting overhead.
The manual reporting cycle: compile data, create visualizations, distribute, answer follow-up questions, repeat next month: consumes architect time that’s better spent on architecture. Live dashboards eliminate the cycle. Update the data in EA. Power BI reflects the change automatically. Stakeholders see current information. Architects are freed to focus on analysis.
Live data is more trustworthy.
Periodic reports go stale. They’re accurate at the moment of publication and increasingly inaccurate as time passes. Live dashboards reflect reality. When a stakeholder makes a decision based on a Power BI dashboard, they’re confident they’re working with current facts. Architects can build analysis on data they know is synchronized with the source of truth.
Power BI as a platform becomes more strategic.
BI investments pay off when the platform covers the full business picture. Adding architecture data closes a gap in many organizations’ BI strategy. It shows that architecture is data-driven and measurable. It positions architecture alongside finance, operations, and HR as a core business function that deserves visibility.
This is not justified if you don’t have Power BI.
If your organization hasn’t invested in Power BI or uses a different primary BI platform (Tableau for Salesforce-centric organizations, for example), this integration path doesn’t apply. Evaluate Tableau integration if Salesforce is your primary platform. If you use neither, consider whether a BI investment makes sense in your context.
Power BI Creator/Pro licenses have cost implications.
The dashboard consumers might only need Power BI licenses at a user level sufficient to view published reports. But the people who build and maintain the architecture dashboards need Power BI Creator or Pro licenses. In organizations with many Power BI builders, licensing cost adds up. This is not a blocker: it’s a cost to factor into ROI calculations. Many organizations find the investment justified by reporting hours saved.
Dashboard quality depends on repository quality.
Garbage in, garbage out. If your repository data is incomplete, inconsistent, or out of sync with reality, your Power BI dashboards will amplify that problem. Before deploying Power BI integration, assess whether your repository is authoritative enough to trust at scale. This is what Discover does: it evaluates your MDG Technology and repository governance to determine readiness. Don’t skip that assessment.
You need a governance discipline for ongoing success.
Live dashboards create ongoing accountability for data quality. As business stakeholders start using the dashboards, they’ll ask questions. Some questions reveal inaccuracies in the data. Your team needs a process for addressing those gaps. This isn’t a technical problem: it’s a practice discipline. Establish the governance upfront.
EA GraphLink with GraphQL interface enabled. This is the integration bridge. Your EA GraphLink instance must expose the GraphQL API. This is part of standard EA GraphLink deployment: your Sparx Systems account manager confirms it’s active.
Power BI license (Pro or Premium). You need sufficient Power BI licensing to support dashboard creation, publication, and consumption. Determine how many dashboard creators you need and what consumption model makes sense for your organization. This is a licensing conversation with your Power BI account team, not with Sparx Services, but it’s a prerequisite.
Power BI Connector add-in installed and configured. The connector translates GraphQL to Power BI datasets. Installation is straightforward: it’s a Power BI custom connector. Configuration requires specifying your EA GraphLink endpoint and authentication credentials. Your Sparx Services team handles this as part of Connect.
MDG Technology assessed for BI readiness. Your MDG Technology defines how repository data maps to the GraphQL schema. If your MDG has gaps or inconsistencies, they’ll surface in Power BI visualizations. Before dashboard development begins, we assess MDG quality against BI requirements. If gaps exist, we address them first. This is part of the Discover phase or early in Connect.
Data governance established for dashboards. Decide who can create dashboards. Who can publish to which workspaces. How dashboard changes are reviewed. Who owns dashboard maintenance. These are organizational questions, not technical ones, but they matter for sustainable integration.
Start with reporting hours.
Count the hours your team spends on architecture reporting each month. Include all manual reporting activities: data compilation, visualization creation, distribution, follow-ups, and ad-hoc requests answered via email.
Estimate reporting elimination.
Live dashboards eliminate approximately 70-85% of routine reporting overhead. Some manual work remains (dashboard maintenance, addressing questions dashboards don’t answer, creating new specialized views), but the bulk of the repetitive work goes away.
Calculate annual savings.
Formula:
(Reporting hours per month × elimination rate × hourly rate) +
(Executive time freed by reducing briefing prep) = annual savings
Example:
30 hours/month × 75% elimination × $150/hour = $40,500 annually
Plus: 4 hours/month executive briefing prep × 75% × $400/hour = $14,400 annually
Total: $54,900 annual savings
Add to this the value of faster decision-making (architecture data available when needed rather than via request-response cycles). For organizations where architecture information informs significant capital allocation decisions, faster access to current data can materially improve decision quality.
Factor in costs.
Power BI licensing (Creator/Pro seats for dashboard builders and consumers). EA GraphLink licensing (if not already in place). The Connect engagement cost itself. Calculate net ROI: total benefits minus total costs.
For most organizations, the payback period is 12-18 months. Thereafter, it’s pure savings.
Tableau (Salesforce Ecosystem)
If Tableau is your primary BI platform and Salesforce is your dominant enterprise system, Tableau integration is the natural path. The technical architecture is identical to Power BI (same GraphQL interface, same EA GraphLink foundation). The dashboards and use cases are the same. The difference is platform: Tableau instead of Power BI. Evaluate this if Salesforce/Tableau is genuinely your BI standard.
Prolaborate (Browser-Based EA Reporting)
Prolaborate is Sparx Systems’ browser-based reporting tool. It offers dashboards, reporting, and portfolio views without leaving the Sparx ecosystem. Pros: lower licensing cost, no external BI platform dependency. Cons: less integration depth, weaker executive BI ecosystem alignment, smaller visualization library. Prolaborate is a good option if you want self-service reporting without enterprise BI investment. It’s not a competitor to Power BI: it’s a different category.
Manual Power BI Reports from Exported EA Data
You can export data from EA and build Power BI reports on that data. Pros: no EA GraphLink dependency, simple to start. Cons: not live, periodic exports create sync lag, manual refresh cycles reintroduce reporting overhead. This is a viable interim solution while you’re assessing readiness for live integration, but it doesn’t deliver the core benefit of continuous synchronization.
Direct Power BI Connection to EA Repository Database
Technically possible but not recommended. Power BI can connect directly to your repository database (SQL Server, MySQL, PostgreSQL). Pros: avoids EA GraphLink licensing. Cons: bypasses the MDG Technology transformation layer, exposing raw database schema to BI tools. This creates data quality risk and brittle connections that break when repository schema changes. The MDG transformation layer exists to prevent this. Use EA GraphLink.
Q: How often does Power BI data update?
A: Refresh frequency is configurable. Most organizations refresh every 4-24 hours. Real-time updates (minute-level or second-level) are possible but typically unnecessary for architecture dashboards: the decision cycle for most architecture questions is measured in days or weeks, not minutes. Discuss refresh frequency as part of Connect planning.
Q: Can we build custom dashboards beyond the standard templates?
A: Absolutely. The Power BI Connector add-in exposes your architecture data as a Power BI dataset. Your Power BI developers can build any dashboard they want using standard Power BI design tools. We provide reference templates and best practices. Your team extends from there.
Q: What if our Power BI workspace structure is complex?
A: We accommodate complex workspace governance. Datasets can be published to specific workspaces. Different stakeholder groups can build dashboards in their own workspaces. Permissions, certification, and approval workflows all apply. This is standard Power BI governance: EA GraphLink integration doesn’t change it.
Q: How do we handle sensitive architecture information in dashboards?
A: Row-level security (RLS) in Power BI filters dashboard data based on viewer identity. For example, a business unit head sees only architecture data relevant to their business unit. A portfolio manager sees the full portfolio. This requires coordination between your Power BI team and your EA governance: they define which data is sensitive and how to filter it. Not a blocker, but a governance decision.
Q: What happens if we make changes to our MDG Technology after Power BI dashboards are live?
A: MDG changes affect the GraphQL schema that Power BI consumes. Minor changes (new fields, new metadata) can often be accommodated without reworking dashboards. Major structural changes may require dashboard modifications. This is why MDG governance is important. Establish a change control process before you deploy dashboards.
Q: Can Power BI dashboards access data from systems beyond EA?
A: Yes. Power BI can combine data from multiple sources: Power BI can blend your EA data with financial systems, HR systems, or other operational data. This unlocks cross-domain analytics: “How does our technology debt correlate with our IT cost overruns?” These analyzes require careful data governance, but the capability is there.
Q: How do we ensure dashboard users understand the data?
A: Document the definitions. What does “technical health score” mean? How is application lifecycle status determined? Include tooltips and glossaries in the Power BI environment. Consider training for heavy dashboard users. Most organizations find that once dashboards are available, usage ramps quickly: training is less about teaching Power BI and more about teaching architecture context.
Q: Is EA GraphLink required, or can we integrate directly from EA?
A: EA GraphLink is required. It’s the licensed integration layer that exposes your repository to external systems. Without it, you’re back to manual exports or direct database connections (neither of which is supported). EA GraphLink licensing is part of the Connect engagement cost.
Power BI integration transforms how your organization consumes architecture information. From request-response cycles to self-service dashboards. From static reports to live views of your portfolio.
The journey starts with assessing your readiness: repository quality, MDG strength, Power BI licensing. If you haven’t completed a Discover assessment, that’s the first step.
If you’ve already assessed your foundation and you’re ready to deploy integration:
[Start Your Connect Engagement]
Or, if you have questions about how Power BI integration fits your specific architecture practice:
[Let’s Talk About Your BI Strategy]
Talk to a Sparx Services architect about where your organization is on the journey and what the next stage looks like.