Skip to main content
Planview Customer Success Center


A capability represents a business operation or function that delivers a product or service to an entity or external consumer.

You can use capabilities to manage and measure the value obtained by consumers against the investment in the resources that were used to deliver the capability.

You can use the capability domains, types, and hierarchy to model the distinct component types and layers that exist in different frameworks, for example, "Business Function" from TOGAF.

About using capability domains

You can use capability domains to create separate models. For example, you can import a standards-based model into one domain, and then develop a more customized version of the model in another domain. You can then map either or both models to consumers and delivery resources.

You can also use capability domains to model concepts from different models, such as an IT-oriented model underlying various business models.

You can create relationships between nodes in different capability domains. Enterprises often have at least two major capability domains: one for internal capabilities and the other for external capabilities. You can create relationships between the internal corporate functions that directly or indirectly support the external business capabilities that are customer-oriented.

Related connections

Connections that play a role in the implementation or delivery of a capability.

On a connection, a source system or company connects to a target system or company to obtain a good or service. The target system or company exposes an interface that implements some aspect of one or more capabilities. Therefore to some extent, a connection can represent an interface (for example, a web service) on a system.


Field name



Name of the entity record. Names should be descriptive and intuitive.


Description of the entity.

Reference ID

The identifier, typically from an external system for integration, import/export, or reference purposes.

Enterprise Approved

State of the entity with respect to the enterprise approval process.

Lifecycle State

The state of the entity with respect to enterprise management and planning.

Capability Domain

The business model, service model, or other domain model to which the capability belongs.

Capability Type

Indicates both the kind of capability and the hierarchical level of the capability.

Content Status

State of the entity record. Content status is used to control contributions throughout the lifecycle of an entity. The statuses are as follows, in order:

  • Identified – entity record has been added, perhaps with very minimal information.
  • Planned – entity record has been prioritized for inventory, with a completion date.
  • In Process – entity record is being inventoried, with a completion date.
  • Completed – inventory is complete, but is yet to be reviewed.
  • Approved – inventory has been reviewed and verified.

Lifecycle Roadmap

Chart that displays the lifecycle states for the entity graphically in a time frame according to their date ranges (if set).


URLs to online resources that provide additional information about the entity.


A custom flag that you can add to entity records to group them into a collection or report.