Free Enterprise Architecture Views

Download free, ready-to-use Enterprise Architecture views for Essential. These views are built using Essential View Builder and cover application architecture, business architecture, technology architecture, strategy, roadmapping and portfolio management.

Connected Architecture, Better Decisions

Essential’s Enterprise Architecture views turn architecture data into visual information that supports specific decisions. Rather than maintaining disconnected diagrams, Essential views are generated from a shared semantic model, allowing information about capabilities, processes, applications, technologies, organisations, suppliers and strategic change to be viewed from different perspectives.

All of these views work in both the free, Open Source version and the commercial versions of our EA tool

Supplier Sovereignty Dashboard

Supplier Sovereignty

Shows the supplier, application, technology, process, ownership and regulatory relationships that determine where services operate and where sovereignty exposure may exist.

This view connects supplier ownership and legal domicile with application deployments, technology nodes, performing processes, data objects and regulations.

What questions does this answer?

Operational footprint
Which suppliers, applications, technology products and processes are present in each country or site?
Ownership and control
Who operates a supplier, who is its ultimate parent, and which child organisations contribute to the impact?
Data sovereignty
Where is application data stored, where is it used, and which processes create that usage footprint?
Regulatory scope
Which applications handle Data Objects explicitly in scope of a Regulation?
Data quality
Which relationships and locations are recorded, and where are the gaps?

How to install

CloudOS
Download the supplier-sovereignty-view and extract it into your Essential viewer’s user folder.

supplier-sovereignty-view

Apply the DUP included in the package to create the report. The report will then appear in the Enterprise section of the View Library.

What architecture information is used?

The view uses live information captured in the Essential repository. Results are derived from relationships and values in the repository rather than a manually maintained supplier or personal-data list.
Dashboard result Required relationship or value
Supplier location and ultimate parent Supplier-to-actor ownership, the
is_member_of_actor
hierarchy, and Legal Entity domicile through
legal_entity_domiciled_in_geos
. The hierarchy is followed for up to five steps.
Fallback supplier location If Legal Entity domicile is not recorded, Group Actor sites are used and the result is flagged for confirmation.
Application deployment geography Application deployment → Technology Instance → Technology Node → Site → geographic location → Geographic Region.
Technology product geography Associated application deployments → Technology Instance → Technology Node → Site → location → region.
Process geography Application-to-process mapping plus the process performing site → site geographic location → Geographic Region.
Regulated data Regulation →
REGULATED_COMPONENT_RELATION
→ Data Object, then Data Objects mapped to applications and processes through the supported data routes.
Contract and control position Supplier/operator and parent relationships, relevant contracts, and contract coverage or lifecycle values.

Legal domicile and ultimate parent

A product may be mapped to a Group Actor or a Legal Entity. The view follows the ownership/member hierarchy to identify the ultimate parent. If the mapped actor is a Legal Entity, its legal domicile is preferred over the site → location → region route.
Group Actor or Legal Entity → is_member_of_actor → parent actor (up to 5 steps)
If no Legal Entity domicile exists, the Group Actor’s sites are used as a fallback. This is shown as a recorded site-based location, with a confirmation warning where the legal domicile remains unconfirmed.

Application, technology and process locations

Application locations are derived from deployment paths to technology nodes and sites. Technology product locations are inferred from their associated application deployments. Processes are located where they are performed.
Application → Application Deployment → Technology Instance → Technology Node → Site → Geographic Region
Application → Physical Process → performing site → Geographic Region
Multiple sites are grouped rather than repeated. Select a multiple-sites or multiple-processes indicator to open the complete list, sorted by country and site.

Regulation and exposure

Exposure is not based on a hard-coded list of personal-data names. A regulation must be linked to a Data Object through the repository relationship below.
Regulation → regulation_applies_to → REGULATED_COMPONENT_RELATION → regulated_component_to_element → Data Object
The in-scope Data Objects are then traced to applications and processes using the supported application-to-Data Object routes and process Information View routes, before deployment geography, process geography and ultimate-parent control are applied.

What each page shows

🗺 Map View
Country and site footprint for ultimate parents, processes, applications and technology. Select a country or site dot to see the records at that location.
📋 Supplier Registry
Supplier base location, application and technology counts, deployment countries, operator and ultimate-parent chain. “Multiple processes” and “Multiple sites” open detail panels.
⊞ Sovereignty Matrix
Supplier-by-country presence, including ultimate-parent, application, technology and process impacts. Select a cell to inspect its data and child-supplier impacts.
↔ Data Flows
Data categories, storage locations, process “Used from” locations, supplier control and contract position. Select a Used from location to see the processes causing it.
⚖ Exposure
Applications meeting the confirmed exposure criteria, with assessment, storage, usage, findings and explicit regulation badges.
⌘ Sovereignty Table
Relationship table for a selected application, technology product or process, showing the repository paths behind the result.
◇ Data Insight
Data Model and Data Gaps. The model shows required classes and relationship paths; gaps show recorded and missing coverage.

How to use the view

  1. Use the global search to filter suppliers, applications, technology products, processes and locations.
  2. Use
    All Countries
    to restrict results to one country, and
    All suppliers
    to focus on one supplier and its network.
  3. On the map, select a country or site dot. Selecting a site keeps the current zoom and opens site details.
  4. Use the clickable counts and indicators in the registry to open applications, technology, sites or processes.
  5. In the matrix, select a cell to inspect applications, technology, processes, mapped sites and impacts inherited from child suppliers.
  6. Use Data Insight → Data Model to understand required paths and Data Insight → Data Gaps to see missing links.
Not recorded
means the required repository value or relationship is absent from the data available to the view. It does not prove that the value does not exist in the organisation.

Technology Radar

Shows you your technology disposition by Technology Capability
Technology Radar

This view uses disposition on technology product roles, e.g. Tomcat as a Web Server. to show the disposition and impacts on applications and processes

Each product is shown as a circle in the flat radar view. When 3D mode is enabled, the circles become towers. The tower height and circle size represent the selected usage measure

What questions does this answer?

Which products support each technology capability
Where each product sits in its disposition lifecycle
Whe relative amount of usage associated with each product
Which applications use a selected product, and
Which business processes are supported by those applications
Data Required relationship or value
Technology capabilities Capabilities linked to technology components
Technology components realisation_of_technology_capability points to one or more capabilities
Technology products Products linked to technology product roles
Technology product roles role_for_technology_provider points to a product; implementing_technology_component points to a component
Dispositions Product roles link through tl_disposition_lifecycle_status
Disposition order Each disposition should have a usable sequence/order value
Lifecycle colours An Element_Style points to each disposition and supplies element_style_colour
Supplier and vendor lifecycle Products link through supplier_technology_product and vendor_product_lifecycle_status

Note this requires the technology disposition slot on the Technology Product Roles so you will need to have applied the 6.21 meta model release for that.

Application usage

To show application usage and application names, the model needs this dependency path:

Technology product role → Technology provider usage → Technology build architecture → Technology product build → Application deployment → Application provider or composite application provider

In Cloud/Docker, this is straightforward to set up using the Technology dependency editor tab on the application editor.

The application instances must have a populated name slot. The radar uses application identifiers for counting, then resolves the visible names through the dependency traversal API.

Business process usage

To show the processes supported by applications, each application must be mapped to its physical processes. The dependency traversal follows:

Application or application provider role → Physical process → Business process

In Cloud/Docker, use the Business Capability to Application drag-and-drop editor to create these relationships if they do not already exist.

Business process names come from Business_Process.name. Processes with a criticality ending in High or Critical are marked as Critical in the process drawer.

How to install

CloudOSExtract the file below into the user folder. Apply the DUP in the to create the report. The view will appear in the Technology section of the View Library.
technology_radar

How to use the view

1. Select capabilities

Use the capability chips in the Segments bar to see the capabilities currently selected. Select Add capability to open the capability selector.

  • Select a capability to add it to the radar.
  • Use the × on a chip to remove it.
  • Only capabilities with linked technology products appear.

2. Read the radar

  • Concentric rings represent disposition lifecycle stages.
  • The legend maps each ring to its lifecycle colour.
  • Product circles use the matching disposition colour.
  • Larger circles indicate more of the selected usage measure.
  • In 3D mode, the same measure controls tower height.

Products are laid out by capability, disposition, and product name to reduce visual overlap.

3. Change the sizing measure

Use Size by to choose how product circles and towers are scaled:

  • Applications — size by application usage.
  • Business capabilities — size by business capability usage.
  • Equal — give each product an equal baseline size.

Size changes animate smoothly.

4. Focus on one capability

Each capability label has a circular control at its outer edge:

⌕ Focus capability
↑ Restore radar

Selecting the magnifying-glass control focuses the radar on that capability. A radar sweep then reveals the products and names as it passes over them. Select the upward-arrow control to restore the previous capability selection.

5. Use 3D mode

Select 3D to animate the radar into a tilted view. Product circles rise into towers, with taller towers representing greater usage.

Product and capability names remain readable and flat while disposition labels follow the tilted radar. Select Flat to animate back.

6. Inspect a product

Click a product circle or tower to open its technology product panel. The panel shows product context, lifecycle information, usage totals, and related data links.

Application and business-capability usage values are interactive. Deployments are not shown in this view.

7. View applications and processes

  1. Click the application usage value in the product panel.
  2. An Applications drawer opens with resolved application names in alphabetical order.
  3. The Processes drawer opens alongside it with the processes supported by those applications.
  4. Critical processes are highlighted with a Critical label.
  5. Click an application name to filter the process drawer to processes supported by that application.
  6. Close either drawer using its × control.

While names are being resolved, the Applications drawer shows pulsing loading placeholders instead of raw identifiers.

Data Centre map

Shows you the sites of your servers and the applications and technologies mapped to those

Data Centre View Data Centre Map
This view connects physical locations with the infrastructure, applications, integrations and business processes they support.

What questions does this answer?

Applications and APIs
Which applications and APIs are hosted at each data centre?
Infrastructure
Which technology nodes support those applications?
Integrations
Which applications communicate with each other, and where are they hosted?
Business impact
Which sites host critical business processes?

What architecture information is used?

The view uses information captured in the Essential repository. Most of the required data can be maintained through the Cloud Application Editor and Technology Node Editor.
For site locations, use AI or another geocoding service to populate the latitude and longitude values for each site.

Business processes are identified through the relationship:

Business Process → Physical Process → Application
Critical business processes are highlighted when the repository identifies them as critical, high, mission-critical or business-critical.

Sites and map positions

Each Site is located through the following relationship:

Site → site_geographic_location → GeoLocation → gl_geocode → GeoCode

The map reads the location from:

  • geocode_latitude
  • geocode_longitude

If coordinates are missing, the site cannot be positioned reliably on the map.

Technology node counts

Technology nodes are linked to sites through:

Technology Node → technology_deployment_located_at → Site

The technology node count controls:

  • The tower height in 3D mode
  • The site summary metrics
  • The Technology Nodes tab
  • The Count selector

Application counts

Applications are identified through their deployment chain:

Site → Technology Node → Application Software Instance → Application Deployment → Application Provider
The view lists the distinct applications and APIs deployed on technology nodes at each site. The application count represents applications supported at the site through recorded deployments. It is not a count of every application in the repository.

Integration flows

Cloud
Integration relationships can be captured through the deployment tab in the Application Editor, using drag and drop or the Launchpad Plus integrations sheet.
OS
The Launchpad Plus integrations sheet can be used to speed up integration capture.

Integration data is based on:

:APU-TO-APU-STATIC-RELATION

Each integration relation contains:

  • A :FROM endpoint
  • A :TO endpoint
  • A relation name
  • A Static_Application_Provider_Usage record at each endpoint
The endpoint usage records are resolved to the actual application or API through:
Static Application Provider Usage → static_usage_of_app_provider → Application or API
Where applicable, the view resolves the parent application so that users see a meaningful application or API name rather than an internal repository identifier.

Integration flows are shown only when:

  1. Integration flows are enabled.
  2. A site has been selected.
  3. The source or target application is hosted at that site.
  4. The other endpoint can be mapped to a known site.
The lines therefore show application and API relationships involving the selected site, rather than every integration in the repository.

How to install

Cloud

Extract the files below and upload its contents to the viewer’s user folder (select the zip file in the extracted file and upload that). Apply the DUP to create the report. The view will appear in the Technology section of the View Library.
data_centre_cloud_files

OS

Extract the file below into the relevant viewer folders. Apply the DUP to create the report. The view will appear in the Technology section of the View Library.
data_centre_map_os

How to use the view

  1. Ensure that sites have valid latitude and longitude values.
  2. Open the Data Centre Map from the Technology section.
  3. Select a site on the map.
  4. Use the tabs to inspect technology nodes, applications and business processes.
  5. Click an application or API to view its integrations and hosting sites.
  6. Enable Integration Flows to display animated relationships involving the selected site.
  7. Select a class and instance where available to open the related network diagram.
  8. Use View Layers to switch to the column-based view.
  9. Hover over paths to inspect them, or click a path to keep it highlighted.

Node Tubemap

Allows you to select an instance in Essential and see its core connections, from Business Capability down to Servers (Technology Nodes). Allows you to see key connections and dependencies in the enterprise architecture

Node Dependency

This view traces relationships from business capabilities through processes, applications, technology and sites.

What questions does this answer?

Business capabilities
Which applications support a business capability?
Technology impact
What happens if this server goes down, and which business processes are impacted?
Application support
Which business processes does this application support?
Site activity
Which processes are performed at this site?

What architecture information is used?

The view uses information captured in the Essential repository and navigates through the following relationship chain:

Business Capability → Business Process → Physical Process
→ Application Service → Application
→ Deployments → Technology → Sites
The Application Service relationship is optional. Where it has not been captured, the view follows the available relationships directly to the application.

How to install

CloudOS
Download the Node Tube Map package and extract it into your Essential viewer’s user folder.
node_tubemap file
Apply the DUP included in the package to create the report. The report will then appear in the Support section of the View Library.

How to use the view

  1. Select a class.
  2. Select an instance.
  3. Review the resulting network diagram.
  4. Use View Layers to switch to the column-based view.
  5. Hover over paths to inspect relationships.
  6. Click a path to keep it highlighted.

Please note: These views are provided ‘as is’ and may subsequently be incorporated into a production release of Essential. Where this happens, the production version may differ in appearance, functionality or implementation from the version provided here.

Contact Us