AI Integrations
If your organization runs Salesforce and uses Tableau as your enterprise BI platform, this is your architecture dashboard path.
EA GraphLink’s GraphQL API connects your Sparx EA repository directly to Tableau. The integration path is technically identical to Power BI: same GraphQL interface, same live-data synchronization, same architecture dashboard use cases. The difference is platform: Tableau instead of Power BI, aligned to the Salesforce ecosystem instead of the Microsoft ecosystem.
When you deploy this integration, Tableau becomes the platform where architecture dashboards live alongside operational, sales, and customer data. Stakeholders in your Salesforce-centric organization access architecture information in the BI platform they already use. No exports. No external tools. Live data from your Sparx EA repository feeding Tableau visualizations, updated automatically.
Architecture dashboards aligned to your Salesforce ecosystem.
Your current state: Architecture information lives in EA. Salesforce users live in Salesforce. Your BI users live in Tableau. These are separate worlds. Architecture stakeholders ask architects for information. Architecture is not integrated into the business intelligence ecosystem.
Your future state: Architecture dashboards live in Tableau alongside Salesforce reporting. Sales and customer data. Operational metrics. Portfolio status. Technical roadmaps. All visible in the same BI environment. Stakeholders don’t have to leave Tableau to understand architecture context. Architecture is part of the Salesforce-integrated business intelligence.
EA GraphLink exposes your repository via a GraphQL API. The Tableau connector translates this GraphQL interface into Tableau datasets. Your Tableau analysts and developers build dashboards using standard Tableau design tools on those datasets. The pipeline is simple: EA repository → EA GraphLink GraphQL → Tableau Connector → Tableau datasets → Tableau dashboards.
When repository data changes, Tableau datasets refresh automatically (configurable schedule, typically 4-24 hour cycles). Dashboards reflect current data without manual intervention.
This is the natural architecture dashboard path. Salesforce is the dominant platform. Tableau is the BI standard. EA integration into Tableau aligns with your technology strategy. You’re not introducing a new BI platform. You’re extending your existing BI investment to include architecture.
Portfolio visibility in the BI environment you already use. Application lifecycle, technology investment, compliance coverage: alongside operational and financial data. One governance layer. One platform. One source of truth.
Reporting overhead drops. Dashboards replace PowerPoint cycles. Your team stops producing status reports and starts producing strategic insight. Architecture becomes visible in the BI platform stakeholders trust.
Application Portfolio Management Dashboard
Status view of your application portfolio in Tableau: lifecycle phase, business criticality, technical health, investment category. Color-code by maturity. Show trends over time. Filter by business unit or technology domain. Link portfolio status to Salesforce data (revenue by application, customer impact by technology platform). This is the executive view of architecture in the ecosystem Salesforce users already understand.
Technology Obsolescence Timeline
Which applications run technologies approaching end-of-life? Surface this in Tableau as a timeline with risk windows. Layer in business criticality from EA, revenue impact from Salesforce. Executives can see which technical risks also represent business risks. Prioritize remediation by impact.
Compliance and Standards Dashboard
Architecture principles coverage across your portfolio. Which applications meet your standards? Where are the gaps? Link compliance to business capability and investment. For regulated Salesforce implementations, this dashboard tracks standards adherence in the same BI environment as compliance dashboards for Salesforce workflows.
Architecture Investment Reporting
Show how architecture budget is allocated across portfolio categories and technology domains. Link spending to architecture strategy. Blend with financial data from your ERP (Salesforce Finance Cloud or other financial systems). Show that architecture investment aligns with business priorities.
Business Capability to Application Mapping
Visualize how applications support business capabilities. Link application data from EA to capability definitions. Combine with Salesforce data about which capabilities drive revenue. Executives see how technology investment maps to business outcomes.
Technology Roadmap Visibility
Share architecture technology roadmaps in Tableau alongside Salesforce roadmaps. Show planned technology transitions, end-of-life timelines, modernization priorities. Make the roadmap visible and accessible without access to EA.
| Role | Primary Benefit | Secondary Benefit |
|---|---|---|
| IT Executive | Portfolio visibility in Tableau (familiar ecosystem) | Evidence of architecture alignment to business |
| Architecture Manager | Reporting hours freed for strategic work | Automated architecture dashboard maintenance |
| Sales Executive | Architecture context visible in BI platform | Understanding of technology risks by customer |
| Salesforce Admin | Architecture integrated into Salesforce BI ecosystem | One platform for all business intelligence |
| Portfolio Manager | Real-time portfolio visibility for decisions | Data-driven portfolio prioritization |
| Business Capability Owner | Application-to-capability mapping visible | Self-service architecture context |
| Compliance Officer | Standards coverage tracking in BI platform | Compliance visibility alongside audit data |
Salesforce ecosystem completeness.
If Salesforce is your dominant platform and Tableau is your BI standard, architecture data should be part of that ecosystem. Salesforce provides customer data, sales pipeline, opportunities. Tableau integrates with those sources. Architecture dashboards in Tableau complete the picture: they show how technology investment supports the business outcomes Salesforce tracks.
No new tools to introduce.
You already have Tableau. Your team already knows Tableau. Architects already understand Tableau design patterns from other dashboarding projects. EA integration is an extension of existing investment, not a new platform to adopt.
Architectural alignment to business platform.
Organizations that run Salesforce are often Salesforce-first companies. Everything important flows through Salesforce. BI centers on Tableau. Architecture dashboards belong in Tableau to signal that architecture is aligned with business priorities.
Live data reduces reporting cycle.
Instead of scheduled PowerPoint reports and email distribution, architecture data flows live through Tableau. Stakeholders pull the information they need. Architects spend time on analysis instead of formatting.
Tableau Creator/Explorer licensing flexibility.
Tableau has flexible licensing tiers. You can balance Creator licenses (for dashboard builders) with Viewer licenses (for consumers). Size your licensing to what you actually use rather than per-user models.
Only makes sense if Tableau is genuinely your BI standard.
If Power BI is your primary BI platform or you use multiple BI tools, Tableau integration may not be the right path. Evaluate Power BI if Microsoft is dominant. Choose the path aligned to your actual BI platform, not your secondary one.
Tableau Creator licensing required for dashboard development.
The people who build and maintain architecture dashboards need Tableau Creator or Explorer licenses, which cost more than Viewer licenses. Validate that you have budget for the Creator licenses you need. For small teams, licensing cost is minimal. For large teams, it’s a factor in ROI calculation.
Repository quality is prerequisite.
If your EA repository contains incomplete or outdated data, Tableau dashboards will expose that at scale. Before deploying Tableau integration, ensure your MDG Technology and repository governance are strong enough to sustain scrutiny. This is what Discover assesses.
Salesforce-specific use cases limited.
Unlike Power BI in Microsoft organizations (where everything flows through Azure/Microsoft cloud), Tableau’s Salesforce integration is primarily BI-layer. It doesn’t inherently connect to Salesforce data. You can build Tableau dashboards that blend EA data with Salesforce data, but this requires explicit data integration work. If your goal is to connect architecture directly to Salesforce operational systems, evaluate Agentforce for conversational integration instead.
EA GraphLink with GraphQL interface enabled. The GraphQL API is the integration bridge. Standard EA GraphLink deployment includes this. Your Sparx Systems account manager confirms it’s active.
Tableau license (Creator, Explorer, or Viewer).
Creator or Explorer licenses required for people building and maintaining dashboards. Viewer licenses for dashboard consumers. Determine your license mix based on your organization. This is a licensing conversation with your Tableau account team.
Tableau Connector for EA GraphLink. The connector translates GraphQL to Tableau datasets. Installation is straightforward: it’s a Tableau custom connector. Configuration requires specifying your EA GraphLink endpoint and authentication credentials. Your Sparx Services team handles configuration as part of Connect.
MDG Technology assessed for dashboard readiness. Your MDG Technology defines how EA data maps to the GraphQL schema. If your MDG has gaps or inconsistencies, they’ll surface in Tableau dashboards. Before dashboard development begins, we assess MDG quality against BI requirements. This is part of Discover or early in Connect.
Data governance framework for dashboards. Who creates dashboards? Who can publish to which Tableau projects? How are dashboard changes reviewed? These organizational governance questions must be answered before dashboards go live.
Start with your current BI investment in Tableau.
You already have Tableau. The incremental cost is primarily EA GraphLink licensing (if not already in place) and Tableau Creator licenses for dashboard developers. These are much lower incremental costs than deploying a new BI platform.
Estimate reporting hours eliminated.
Count current monthly reporting hours. Estimate what percentage live Tableau dashboards will eliminate (typically 70-85%). Calculate annual hours saved at architect or analyst rates.
Formula:
(Current reporting hours/month × elimination rate × hourly rate × 12 months) -
(Tableau Creator licenses for dashboard developers × annual cost) -
(EA GraphLink cost allocation) = net annual savings
Example:
30 hours/month × 75% × $150/hour × 12 months = $40,500 annual savings
Tableau Creator licenses (2 FTE) = $8,000/year
EA GraphLink (if new cost) = $0 (assuming already deployed)
Net annual savings: $32,500
Payback period: Typically 3-6 months if EA GraphLink already deployed, 9-12 months if EA GraphLink is incremental.
For organizations that already have EA GraphLink for Copilot or other integrations, Tableau integration adds value at minimal incremental cost (just Tableau Creator licenses and dashboard development effort).
Power BI (Microsoft Ecosystem)
If Microsoft is your dominant platform (not Salesforce), Power BI is the architecture dashboard path. Technically identical to Tableau (same GraphQL interface, same live-data model, same use cases). Different platform for different ecosystems. Choose based on your dominant platform.
Prolaborate (Sparx Browser-Based Reporting)
Prolaborate provides browser-based dashboards and portfolio views without external BI platform dependency. Pros: lower licensing cost, no Tableau dependency. Cons: less integration depth, weaker ecosystem alignment, smaller visualization library. Prolaborate is good for self-service reporting if you don’t want BI platform dependency.
Salesforce Agentforce (Conversational Integration)
For Salesforce-centric organizations seeking conversational AI access to architecture data, Agentforce uses the same EA GraphLink MCP interface as Copilot. It surfaces architecture answers inside Salesforce. Pros: native Salesforce integration, conversational interface. Cons: different use case (conversational vs. dashboard), separate licensing. Agentforce and Tableau serve different needs: consider both if you want both dashboards and conversational access.
Manual Tableau Reports from Exported EA Data
You can export data from EA and build Tableau reports on that data. Pros: no EA GraphLink dependency. Cons: not live, periodic exports create sync lag. This is viable as a short-term solution while assessing readiness for live integration.
Direct Tableau Connection to EA Repository Database
Technically possible but not recommended. Bypasses MDG Technology transformation, exposing raw database schema. Creates data quality risk and brittle connections. Use EA GraphLink.
Q: How often do Tableau dashboards refresh?
A: Refresh frequency is configurable. Most organizations use 4-24 hour cycles. Real-time updates (minute-level or second-level) are possible but typically unnecessary for architecture dashboards. Discuss refresh frequency as part of integration planning.
Q: Can we blend EA data with Salesforce data in Tableau?
A: Yes, if you have Tableau’s Salesforce connector and appropriate Salesforce data access. You can build Tableau dashboards that combine EA data (from GraphQL connector) with Salesforce data (from Salesforce connector). This requires Tableau development expertise and is useful for use cases like “revenue impact of technology changes.”
Q: What if we use multiple BI tools?
A: The EA GraphLink GraphQL interface is vendor-neutral. If you use both Tableau and Power BI, you can deploy both integrations from a single EA GraphLink instance. Different dashboards in different platforms for different audiences. This is a legitimate approach for organizations using multiple BI tools.
Q: How do we handle sensitive architecture information?
A: Tableau supports row-level security (RLS) using filters based on user identity. Sensitive data can be excluded from Tableau or restricted to specific user groups. Coordinate this with your data governance team.
Q: What happens if we make changes to our MDG Technology?
A: MDG changes affect the GraphQL schema. Minor changes (new fields) often accommodate without reworking dashboards. Major structural changes may require dashboard updates. Establish MDG change control before deploying dashboards at scale.
Q: Do we need Tableau Server or can we use Tableau Cloud?
A: Both work. Tableau Cloud (SaaS) is simpler operationally. Tableau Server (on-premises) gives you more control. Either can connect to EA GraphLink. Discuss which fits your infrastructure strategy.
Q: How many Tableau Creator licenses do we need?
A: Depends on how many people will build and maintain dashboards. Many organizations start with 2-4 Creator licenses. Larger organizations may need more. Start conservative and expand based on demand.
Q: Can Tableau access EA repository data for Salesforce use cases specifically?
A: Yes. You can build dashboards specific to Salesforce org health, Salesforce user adoption, Salesforce CRM data combined with architecture data. These are legitimate use cases for organizations where Salesforce is the primary business platform.
Q: Is EA GraphLink required, or can we integrate directly?
A: EA GraphLink is required. It’s the licensed integration layer that exposes repository data to external systems. Direct database connections are not supported and create data quality risk.
Tableau integration positions architecture dashboards in the Salesforce ecosystem. For organizations where Salesforce is dominant and Tableau is the BI standard, this is the natural dashboard path.
The journey starts with assessing your readiness: repository quality, MDG strength, licensing. If you haven’t completed a Discover assessment, that’s the first step.
If you’ve assessed your foundation and you’re ready to deploy Tableau integration:
[Start Your Connect Engagement]
Or, if you want to understand how Tableau dashboards fit alongside other integrations (Copilot, Fabric, Agentforce):
[Talk to Us About Your BI and AI Strategy]
Talk to a Sparx Services architect about where your organization is on the journey and what the next stage looks like.