Logodoc

The Blueprint

Defining and applying your organization's framework for Operational Excellence.

What is a Blueprint?

A Blueprint is the cornerstone of measuring and guiding operational excellence within the Blankstate ecosystem. It represents your organization's unique, defined framework – essentially, the standard against which operational activities and outcomes are assessed.

Functionally, a Blueprint is a curated collection of specific Protocols (what to sense or look for) and associated Metrics (how to measure and quantify performance). It acts as the lens through which both real-time actions (Stream) and historical data (Replay) are viewed and evaluated.

Placeholder graphic representing the concept of Operational State

How Blueprints are Used

Application in Stream

The currently active Blueprint directly configures the Phantom browser extension for all users. It dictates which Protocols Phantom uses to monitor interactions in real-time, enabling features like:

  • Peacekeeper: Governance based on 'Policy' Protocols.
  • North Star: Guidance based on 'CT'/'GP' Protocols.
  • OEI Calculation: Feeding scores into Metrics defined in the Blueprint.
  • Catalyst: Identifying success patterns based on Protocol/Metric impact.

Purpose and Goals

Blueprints serve several critical functions in achieving operational excellence:

  • Observe Current State: Provide the framework to understand "where we are now," whether through Stream's real-time data aggregation or Replay's historical analysis.
  • Define Target State: Act as the foundation for defining "where we want to be." While the target state might involve specific Metric goals, the Blueprint defines *what* is being measured.
  • Evaluate Performance: Offer the standard for assessing effectiveness, identifying gaps, and recognizing successes against the organization's defined operational goals.
  • Ensure Consistency: Promote a shared understanding and consistent application of operational standards across the organization.

Technical Implementation (Conceptual)

Behind the scenes, a Blueprint is essentially a data structure stored centrally within the Blankstate platform. It links an Organization ID to a specific collection of Protocol IDs and Metric IDs, along with important metadata.

  • Central Storage: Blueprints are defined and stored centrally, accessible via API.
  • Key Components: Primarily composed of references to specific Protocols and Metrics.
  • Metadata: Includes name, description, version, status (e.g., active, draft), creation date, etc.
  • Configuration Source: Acts as the configuration source for:
    • EVA Control Center reporting and analysis settings.
    • Replay's analysis engine parameters.
    • Phantom extension's active monitoring rules.

Learn more about the Mind Architects.

No headings found.