Skip to main content

Frameworks & Resources: SPEAR

SPEAR (Semantically Powered Enterprise Architecture Repository) is a vendor-agnostic knowledge graph of common capabilities, processes, roles, applications and information objects.

L
Written by Leart Kollqaku

Why Use SPEAR in Ardoq?

Many of an organization's core building blocks are not unique. Processes, roles and systems are increasingly standardized, and there is little value in modeling from scratch what has already been mapped out.

Importing SPEAR gives you a ready-made, connected starting point: which processes realize which capabilities, which roles perform them, which applications support them, and what information they use. Because SPEAR's relationships are explicit, they come with the import. You can trace a capability to the processes that realize it, the roles that perform those processes and the applications that serve them, and replace SPEAR's generic examples with your own applications and data as you model.


How Ardoq Adopts SPEAR

SPEAR is implemented as five workspaces, one per kind of building block, so you can connect them to the rest of your architecture models. Each workspace groups its content by industry sector.

Workspace

Component Types

Description

SPEAR - Capabilities

SPEAR Capability, SPEAR Sector

What the organization is able to do, in a hierarchy from broad to specific.

SPEAR - Processes

SPEAR Process, SPEAR Sector

The activities that realize capabilities, in a hierarchy, with the triggers between them.

SPEAR - Roles

SPEAR Role, SPEAR Sector

Roles in a reporting hierarchy, with their seniority level.

SPEAR - Applications

SPEAR Application, SPEAR Sector

Generic application types that serve processes and access information.

SPEAR - Information Objects

SPEAR Information Object, SPEAR Information Attribute, SPEAR Sector

Business information concepts such as Employee or Invoice, each with its attributes.

The SPEAR Sector component type is a category in every workspace. It groups that sector's components together, and it is not itself a capability, process, role, application or information object, so it does not affect your counts.

Every component also has an Industry Sector field, along with its SPEAR ID, SPEAR URL, status and revision details, so you can filter or report by sector.

Full size preview

Industry Sectors

SPEAR contains an Enterprise Core, which applies to every organization, plus ten industry sectors.

  • Enterprise Core

  • Agriculture

  • Education

  • Financial Services

  • Insurance

  • Logistics & Supply Chain

  • Manufacturing

  • Public Administration

  • Retail & Wholesale Trade

  • Telecommunications

  • Water Services

Sector content connects across sectors where SPEAR defines it. For example, a retail role can own an Enterprise Core capability, so Enterprise Core is a useful base for any sector.


Importing SPEAR into Ardoq

Access SPEAR through Ardoq's Frameworks & Resources Importer. The import creates five workspaces with about 5,000 components, including more than 3,000 information attributes, and all sectors are included. For step-by-step instructions, see How to use the Frameworks & Resources Importer.

Source and License

SPEAR is published by CYGNUS DATA AS. For the original model and full documentation, go to the source:

  • SPEAR home page: an overview of SPEAR.

  • Open SPEAR wiki: explore the SPEAR model and its relationships. Each component in Ardoq has a SPEAR URL field that links to its page in the wiki.

  • SPEAR license: license terms and tiers.

Did this answer your question?