Operational dashboard live

• Design layout and structure tailored to the agreed operational workflow.
• Build defined visualisations and aggregations using Kibana Lens or custom ES|QL queries.
• Configure operational filters, search controls and time-window defaults.
• Establish space-level permissions and access settings where included in the variant.
• Execute query responsiveness and rendering performance tests under typical usage.
• Conduct a structured review session with operational stakeholders and complete handover.

• Designate an operational owner and target users to specify requirements.
• Define required measures, key performance indicators and target aggregations.
• Confirm that underlying index data exists, is current and is trusted for operational use.
• Provide required administrative or space permissions in Kibana.
• Participate in review walkthroughs and provide formal acceptance sign-off.

Required data must already be present and trusted in Elastic; measures, audience and acceptance owner must be agreed before activation. Simple requires standard measures and access. Standard allows moderate query or calculation complexity. Advanced requires Delivery approval for role-aware access, advanced calculations or material performance considerations.

• Onboarding new telemetry sources or creating new index pipelines.
• Data cleansing, schema remediation or fixing missing upstream fields.
• Open-ended analytics exploration or business intelligence reporting programmes.
• Building multiple independent dashboards in a single request.
• Broad UX design programmes or continuous dashboard iteration post-handover.
• Business-process redesign or organizational change management.

• 1. Confirm operational purpose: Validate target audience, required measures, data sources and acceptance criteria.
• 2. Design: Wireframe visual hierarchy, filter arrangements and drill-down paths.
• 3. Build: Construct visualisations, configure queries and assemble the dashboard container.
• 4. Test scenarios and access: Validate data accuracy, query execution latencies and role permissions.
• 5. User review: Walk through typical triage workflows with operational owners.
• 6. Complete: Export saved object manifests, document exceptions and close handover.

The dashboard is live, agreed scenarios and access checks pass and the operational owner accepts it. Evidence delivered at sign-off includes:

• Exported Kibana dashboard JSON and saved object inventory.
• Verification screenshots demonstrating live operational views.
• Query latency and performance validation records.
• Documented exceptions (if any) and formal operational-owner acceptance.

This deliverable is available only to customers with Elastic Specialist Advisory. Once the service advisor and, where required, Delivery have qualified the Service Request, the applicable credits are allocated from the customer's available credit pool. Delivery credits represent the defined result, not consulting hours.

If discovery reveals that necessary underlying telemetry is missing, data quality is inadequate or requirements expand into multiple dashboards, Observata pauses the affected work. The Service Advisor and Delivery then requalify the request to another option, another deliverable or a larger governed engagement before additional scope is performed or additional credits are consumed.

• 1. Define the operational visibility gap with your advisor during your regular working session.
• 2. Your Service Advisor verifies that underlying telemetry is ready and qualifies the variant.
• 3. The Service Request is activated, locking the visual scope and credit value upfront.
• 4. Delivery builds the dashboard, conducts a user walkthrough and hands over the verified asset.

• Service family: HYPR Serve
• Outcome ID: EO-ODBL
• Specification Version: 1.3
• Effective Date: 23 September 2026

Governing scope: Observata legal centre