Once metrics are defined the values associated with them can be captured.  Figure Me.21 – Metric shows the MetricMeasure entity and its directly related entities.<br/>The MetricMeasure might be collected for 0..1 RootEntity because some entities may be explicitly related to a MetricMeasure, such as those entities currently in the Performance, including Service and Resource, and SLA entities, including ProductOffering and ServiceSpecification. These explicit associations represent a more detailed association than the more general association to RootEntity.<br/>This diagram uses RootEntity as an abstract concept showing how any entity can be associated to MetricMeasure.<br/>Since RootEntity is also a real class in the SID model and is the base class of several ABEs (Resource, ResourceSpec, Service, ServiceSpec and Policy) this diagram also includes examples on how to model Metrics that measure entities which are not subclasses of RootEntity in the SID model. <br/>For example, suppose there is a need to collect a metric for the Service instance of RootEntityType. The first step is to select one of the MetricDefinition(s) for it, then the MetricDefMeasure to use, then the MetricDefinitionDeterminationMethod. <br/>The MetricMeasure is associated to the method and to RootEntity (not RootEntityType) that represents for example the instance of Service for which the MetricMeasure is being collected. <br/>There are indirect associations (i.e. derived) from the MetricMeasure to the MetricDefMeasure via the association to MetricDefinitionDeterminationMethod and from MetricMeasure to MetricDefinition via its association to MetricDefMeasure.<br/>