====== Operational Resource ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]

===== Discussion =====

An Operational Resource is a [[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resource]] used to perform or support an operational activity.

An Operational Resource can include:

  * A person
  * An [[dido:99_annexes:annex-b-terms-and-definitions:o:organization|Organization]]
  * A [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]
  * A [[dido:99_annexes:annex-b-terms-and-definitions:n:node_set|Node Set]]
  * A service
  * A software component
  * A physical machine
  * A virtual machine
  * A container
  * A network
  * A storage facility
  * A database
  * An [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_facility|Execution Facility]]
  * A [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Target]]
  * A test instrument
  * A communication facility
  * An external system
  * Another resource required to conduct or support operations

An Operational Resource can identify:

  * Its identity
  * Its name
  * Its description
  * Its type
  * Its [[dido:99_annexes:annex-b-terms-and-definitions:v:version|Version]]
  * Its owner
  * Its operator
  * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:r:role|Roles]]
  * Its provided capabilities
  * Its required capabilities
  * Its interfaces
  * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:e:endpoint|Endpoints]]
  * Its dependencies
  * Its configuration
  * Its availability
  * Its capacity
  * Its operational status
  * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_policy|Governance Policies]]
  * Its [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * Its [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

A [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] can contain, identify, allocate, configure, or provide access to Operational Resources required for [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]].

===== Definition =====

//[[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resource]] used to perform or support an operational activity//

===== Source =====

Adapted from:

  * [[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resource]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
  * DIDO Reference Architecture
  * DIDO Reference Implementation Conceptual Model
  * DIDO-TE draft Requirements Register

===== Note =====

Every Operational Resource is a Resource. A Resource is not necessarily an Operational Resource.

A Resource becomes an Operational Resource when an operational activity uses or depends on it.

An Operational Resource differs from a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]:

  * An Operational Resource performs or supports an operational activity
  * A Test Environment identifies the conditions, configurations, dependencies, and Operational Resources required to conduct testing

An Operational Resource differs from a [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Target]]:

  * An Operational Resource performs or supports an operational activity
  * A Deployment Target provides a destination for installing, configuring, or activating a deployable artifact

The same resource can satisfy both definitions.

An Operational Resource differs from an [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_facility|Execution Facility]]:

  * An Operational Resource performs or supports an operational activity
  * An Execution Facility interprets or performs [[dido:99_annexes:annex-b-terms-and-definitions:e:executable_instruction|Executable Instructions]]

Every Execution Facility used operationally is an Operational Resource. An Operational Resource is not necessarily an Execution Facility.

An Operational Resource can be:

  * Dedicated or shared
  * Permanent or temporary
  * Local or remote
  * Physical or virtual
  * Human-operated or automated
  * Internal or external to the system

===== Example =====

A DIDO-TE [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] uses the following Operational Resources:

  * Three Nodes forming a Node Set
  * A container runtime
  * A test automation service
  * A database
  * A communication network
  * An Artifact Repository
  * A monitoring service
  * A User acting in the Test Operator Role

Each Operational Resource supports the applicable Test Execution and appears in the resulting [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Run]] record.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>