One Connected View

An enterprise architecture repository becomes more useful when it connects not only applications, capabilities, technology, and strategy, but also the processes that show how work actually happens. GlobeArc brings Enterprise Architecture and Business Process Management into one configurable repository, connecting strategy, processes, capabilities, applications, technology, data, people, and organizational context through the same underlying information.

The same records can be reused across BPMN process models, capability maps, value streams, application landscapes, reports, queries, heat maps, and planning views. Instead of creating another copy whenever information appears somewhere new, GlobeArc keeps architecture and process information connected, giving teams one consistent foundation for understanding dependencies, planning change, and seeing how the enterprise operates.

Objects represent the things an organization needs to understand. These can include applications, capabilities, processes, value stream stages, stakeholders, organizational units, initiatives, and other business or technology elements.

Associations describe how objects relate to one another. An application can support a capability, an organizational unit can perform a capability, or an initiative can realize a capability. These explicit connections allow teams to trace dependencies across different architecture domains instead of relying on names, spreadsheets, or manually maintained cross-references.

Enterprise decisions rarely stay inside one architecture domain. Retiring an application can affect a process, a capability can depend on several applications, a value stream can cross organizational boundaries, and a strategic initiative can require changes across both business and technology.

GlobeArc brings these domains together through shared records and explicit relationships. Teams can follow those connections to understand how strategy, processes, applications, capabilities, information, stakeholders, and organizational structures influence one another, without rebuilding the context for each new question.

Enterprise architecture isn't identical everywhere, and it doesn't remain static over time. GlobeArc uses State, Location, and Org Unit as structural planning contexts, allowing teams to understand architecture information in the context where it applies.

State can represent Current, Interim, and Target architecture. Location and Org Unit can represent geographic and organizational differences, including hierarchical rollups and explicit exceptions. Teams can therefore examine the same connected architecture from different planning perspectives without creating a separate repository for each variation.

Compare Current, Interim, and Target States

GlobeArc can compare states to identify differences between the architecture that exists today and the architecture an organization intends to create. Comparisons can show structural differences as well as directional property changes, helping teams see what has been added, removed, or changed.

This makes Current and Target states part of the underlying architecture context rather than disconnected diagrams that need to be reconciled manually.

GlobeArc supports native BPMN process modeling using repository-connected enterprise information. Process lanes can resolve to stakeholders, organizational units, and locations, while activities can link to other repository objects. The model can also derive relevant associations from those connections, making a process part of the broader architecture rather than an isolated diagram.

Business capability maps provide a structured view of what the organization needs to be able to do. Because capabilities share the same repository with applications, organizational units, information concepts, value streams, and other objects, teams can explore what supports a capability and where dependencies exist.

Value streams help teams understand how value moves through the organization. GlobeArc connects value stream stages to the same capabilities, stakeholders, and other enterprise information used elsewhere in the platform, helping business architecture remain connected across different views.

BPMN process models in GlobeArc can be simulated, not just drawn. Process simulation uses the information already connected to the model, including the stakeholders who perform the work and their headcount and weekly availability. Trace mode lets teams follow work step by step to see where it slows down or waits.

The Process Analysis view compares Current and Target variants of a process side by side on cost, duration, waiting time, and team capacity, so teams can see the expected effect of a change before committing to it. Because the process connects to the same applications, organizational units, and stakeholders used across the repository, the results stay tied to the wider enterprise rather than sitting in a separate simulation tool.

GlobeArc provides search and query capabilities for moving through connected architecture information without manually navigating a large repository. Global Search helps locate records quickly, while "Related objects" and "Also exists" in reveal additional context around an object and where it appears.

For more structured questions, saved queries use a validated query structure rather than raw SQL. Teams can preserve useful queries and return to them as repository information changes, making the answer repeatable rather than dependent on another one-off data exercise.

A connected enterprise architecture repository is only useful once it contains enough trustworthy information to support the questions an organization needs to answer. GlobeArc uses its metamodel to generate Excel import templates, helping teams bring existing objects and property values into the platform without manually recreating every record. Existing Visio process diagrams can also be imported and converted into BPMN process models in the repository.

Organizations can start with the information they already maintain and build greater depth over time. The GlobeArc team works with each customer during onboarding to plan how existing data, including the relationships between objects, is brought into the repository.

The point of a connected repository isn’t to put more information in one place. It’s to make the relationships between that information usable. It's to make the relationships between that information usable. With a shared foundation, teams can:

When processes, capabilities, applications, value streams, organizational structures, strategy, and other enterprise objects share the same underlying repository, teams can investigate questions across domains without first reconciling several versions of the organization. GlobeArc turns those connections into models, comparisons, analytics, queries, and reports, giving architecture and process teams a common foundation for understanding the organization as it is today and planning what it needs to become.