Logodoc

Metrics

Quantifying Operational Performance from Protocol Insights.

What are Metrics?

If Protocols are the "sensors" in your Blueprint, then Metrics are the instruments that quantify and interpret the signals those sensors detect. They translate the raw scores generated by Protocols (from real-time interactions in Stream or retrospective analysis in Replay) into meaningful measurements aligned with strategic operational objectives (e.g., OKRIs - Organization Key Results Indicators).

Metrics form the crucial link between low-level operational observations and high-level performance understanding. They are the direct inputs used to calculate the overall Operational Excellence Index (OEI), providing a quantifiable view of how well the organization is performing against its defined standards.

Metrics are a shared concept used by both Stream and Replay, though the timing and source of their input data differ.

Key Attributes & Configuration

Each Metric is defined by several key attributes that determine how it functions:

Data Source (Protocols)

A Metric must be associated with one or more specific Protocols. These Protocols provide the necessary input scores or signals required for the Metric's calculation. Both required and optional Protocol sources can be defined.

Calculation Logic

Defines *how* the Metric's value is derived from its input Protocol scores. This includes:

  • Format: Type of value (Percentage, Ratio, Score, Binary, Index, Number, Trend).
  • Calculation Method: How individual data points are calculated (e.g., average, weightedAverage, sum).
  • Aggregation Type: How multiple data points are combined over time or context (e.g., average, sum).

Gold Standard (GS)

The benchmark or target value representing ideal performance for this Metric. Performance is measured relative to this standard when calculating OEI contribution.

Target Influence

Determines how the Metric impacts the overall OEI score:

  • Weight: Importance relative to other Metrics.
  • Directionality: Is higher better, lower better, or should it maintain a value?
  • Thresholds: Tolerance levels (warning, critical) for deviations from the Gold Standard.

Creation & Activation

Metrics are typically defined via the EVA Control Center (for Stream) or potentially within Replay's Blueprint editor. The process involves specifying the attributes mentioned above and, crucially, linking the Metric to its required source Protocols.

Placeholder graphic representing the concept of Operational State

Protocol Association & Validation

Before a Metric can be calculated, the system needs to ensure its required source Protocols are available and correctly configured within the relevant Blueprint. Blankstate uses a validation mechanism (conceptually represented by the `getProtoStatus` API flow for Stream) to check if existing Protocols meet the Metric's needs, require updates, or if new Protocols must be created.

[Conceptual: Flow diagram showing Metric definition Validation Check (getProtoStatus) → Status Report (Available/Update/Create Protocols)]

Activation

A Metric only becomes Active and contributes to calculations (like OEI) once all its required source Protocols are properly associated, configured, and themselves active within the Blueprint being used (either the active one in Stream or the selected one in Replay).

Calculation Context: Stream vs. Replay

While the definition and core calculation logic of a Metric remain consistent, the context and timing differ between Blankstate products:

  • Stream:Calculations occur based on aggregated, near real-time data from Phantom signals. Values can be calculated locally in Phantom for immediate feedback (like OES previews) and centrally for historical tracking, reporting, and aggregated OEI calculation in the EVA Control Center. Data is typically stored as time-series points.
  • Replay:Calculations happen retrospectively within the Replay application after the Protocol scoring (Feature Extraction) is complete for an analysis session. Metric values represent the performance measured within the specific set of analyzed documents, based on the selected Blueprint. These values contribute to the OEI reported for that particular analysis.

No headings found.