Logodoc

Production

Deploying your Operational Excellence framework for live use and analysis.

Taking Your Blueprint Live

Moving a validated Blueprint into "Production" means activating it for use by end-users within the Blankstate ecosystem. This process differs slightly depending on whether the Blueprint is intended for real-time monitoring via Stream or retrospective analysis via Replay.

Before going to production, ensure your Blueprint and its constituent Protocols and Metrics have undergone thorough Evaluation to guarantee accuracy and alignment with your operational goals.

Production in Stream (Real-time)

In Stream mode, a Blueprint is activated organization-wide (or for specific teams/Spaces in future versions) to enable real-time monitoring and guidance.

  • Activation via EVA Control Center: Administrators activate a specific, validated Blueprint version for Stream use through the EVA Control Center. Only one Blueprint can be active for Stream at a time per scope (organization/team).
  • Instant Application: Once activated, the Blueprint definition (including its Protocols and Metrics) is securely distributed from the central Blueprint Store to each user's Phantom browser extension and the backend IBF services. This happens near-instantly upon activation or user connection/update.
  • Real-time Analysis: With the Blueprint active, Phantom's local IBF begins analyzing user interactions (Metamarkers) in real-time against the defined Protocols. Scores are generated locally.
  • Continuous Metric Calculation: Protocol scores from all relevant user interactions are processed by the IBF Metric Impact Engine (MIE) in the backend to continuously update the values of the active Metrics defined in the Blueprint.
  • Live OEI and Guidance: The real-time Metric values feed the continuous calculation of the Operational Excellence Index (OEI), visible in the EVA Control Center. The active Blueprint also governs real-time guidance (North Star) and governance (Peacekeeper) actions within Phantom based on Protocol scores and Metric thresholds.

Consumption and Pricing Implications

Using Blueprints in production, particularly in Replay, has implications for your consumption and pricing under your Blankstate agreement.

  • Stream: Consumption in Stream is typically related to active users utilizing the Phantom extension and the volume of interactions processed by the backend IBF services based on the active Blueprint. The complexity of the active Blueprint (number and complexity of Protocols) can influence processing load but is generally factored into user-based or interaction-volume-based pricing models.
  • Replay: Consumption in Replay is directly tied to the volume of documents or data processed using a selected Blueprint. When you ingest documents and run an analysis, Blankstate's systems perform the necessary processing (IBF analysis against Protocols, Metric calculation, etc.).

    • Pricing for Replay is typically based on the time spent analyzing, reflecting the computational resources used to apply the Blueprint's analytical framework to your historical content. Using proper files and initiating analysis directly correlates to this consumption.

  • Blueprint Complexity: While the primary Replay consumption driver is data volume, the complexity of the *selected* Blueprint (number of Protocols, complexity of IBF definitions within Protocols) can indirectly influence the processing cost per data unit. More complex Blueprints require more intensive analysis.
  • Monitoring Consumption: Details regarding your specific consumption metrics and pricing model are available through your Blankstate account management interface or by contacting your account representative. Refer to the Pricing page for general information.

No headings found.