Fixed Price Deliverable

Ecommerce Accelerator

Standard

Overview

A fixed-price, time-boxed implementation engagement to deploy and operationalize Elastic's PRISM (Policy, Rules, & Intent Synthesis Middleware) framework for intelligent, natural-language product search, on one (1) Elastic Cloud Hosted (ECH)/Serverless or self-managed (ECE/ECK) cluster of up to ten (10) nodes for self-managed deployments. This engagement supports either a net-new PRISM implementation or the modernization of an existing search experience, and is scoped to one (1) primary product catalog. This engagement is limited to one (1) cluster and one (1) primary catalog only. Any additional clusters, catalogs, deployments, environments, or expanded scope are expressly out of scope unless otherwise agreed in a mutually executed Order Form (change order). PRISM is a services accelerator, not a supported Elastic product, and is customer-operated following delivery.

Scope

  • Conduct discovery to understand the customer's business search use case, intent, and desired versus undesired search outcomes.
  • Review the source-of-truth dataset for one (1) primary catalog, including current data format and search-relevant fields.
  • Review the target cluster's topology, node settings, non-production/pre-production environment access, and backup and recovery planning, using available diagnostic tooling; report risks and recommendations (advisory only — no hands-on remediation).
  • Review the existing data model (if applicable) and/or design a new data model aligned to the search use case.
  • Review and design analyzers and query understanding configuration, and provide education on the PRISM rule-lookup (percolator-based) mechanism.
  • Review and provide guidance on the ingest and transformation workflow for one (1) data source; this is a review/guidance service — Elastic does not build or operate the ingest pipeline.
  • Enable the PRISM rule framework and author up to forty (40) seed merchandising rules.
  • Design rule governance and precedence guidance covering how multiple rules interact and take precedence.
  • Extend PRISM rule capabilities for up to two (2) to three (3) additional constrained rule patterns within the single primary catalog, as needed.
  • Curate a golden query set of ten (10) to twenty (20) queries with expected outcomes and a pass/fail rubric, and build a minimal test harness exercising PRISM query construction against the set.
  • Conduct an integration workshop and provide advisory support for integrating PRISM into the customer's application query flow; this is advisory/pairing only — no hands-on coding in the customer's application, and no API gateway or authentication work; the customer's team implements.
  • Implement indexing strategy (e.g., blue-green indices) and review indexing efficiency.
  • Demonstrate how to evaluate and debug queries, and review search queries and client-developed application code for improvement opportunities.
  • Discuss and provide guidance on basic RBAC structure for up to two (2) roles; this is guidance only — Elastic does not configure RBAC on the customer's behalf.
  • Conduct training sessions demonstrating how PRISM works to business and technical stakeholders, conduct a knowledge transfer workshop, provide documentation and a final report, and transfer engagement assets to the customer.

Out of scope

This engagement does not include:

  • Evaluation, configuration, or ingestion of catalogs or data sources beyond the one (1) primary catalog and one (1) data source defined in Scope
  • Hands-on build, operation, or ongoing management of data ingestion pipelines; ingest work is advisory/review only
  • Authoring of merchandising rules beyond the forty (40) seed rules and the up to two (2) to three (3) additional rule pattern extensions defined in Scope
  • Multi-catalog or cross-category rule logic
  • Golden queries or acceptance test cases beyond the ten (10) to twenty (20) queries defined in Scope
  • Hands-on remediation of cluster configuration, backup/recovery, or infrastructure issues identified during the environment review; this is an advisory review only
  • Hands-on coding in the customer's application, API gateway configuration, or authentication work; this is advisory/pairing only, and the customer's team implements
  • RBAC configuration on the customer's behalf; RBAC work is guidance and examples only, and the customer implements
  • Query latency evaluation or optimization
  • Reference search UI or admin UI development, demonstration, or customization
  • Ongoing support, operation, or maintenance of the PRISM configuration after Completion; PRISM is a services accelerator, not a supported Elastic product, and is customer-operated
  • Evaluation, configuration, or integration of additional clusters, deployments, or environments
  • Deployments or cluster sizing exceeding ten (10) nodes (self-managed)
  • Project management beyond internal Elastic delivery coordination

Any work outside the scope above requires a mutually executed Order Form (change order) and may result in additional fees, revised assumptions, and schedule changes.

Engagement timeline

  • Scheduled to commence approximately 6–8 weeks after purchase, subject to resource availability and Customer readiness
  • Delivered by an Elastic Consultant or a certified partner resource under Elastic oversight
  • Unless otherwise agreed in writing, the services will be delivered remotely
  • Delivery is expected to occur over contiguous business days or contiguous calendar weeks, as scheduled by Elastic
  • If delivery is delayed, interrupted, or rescheduled due to Customer availability, access issues, environment readiness, or other Customer dependencies, Elastic may reassign resources, adjust the schedule, or require an Order Form (change order)
  • Time scheduled for the engagement that cannot be used due to Customer delay, unavailability, failure to meet dependencies, or inability to provide required access will count against the total consulting days

Fixed-price conditions and assumptions

The fixed price is based on the following assumptions and conditions:

  • Customer provides all required access, credentials, documentation, and relevant architectural information before the kickoff call
  • Customer designates a single point of contact and ensures appropriate technical stakeholders are available and responsive throughout the engagement
  • The target cluster is accessible, operational, and ready for configuration at the start of the engagement
  • Customer provides access to real source data or realistic sample data for the one (1) primary catalog and one (1) data source in scope
  • Customer objectives, desired versus undesired search outcomes, and merchandising priorities are defined and agreed before kickoff
  • The engagement is limited to one (1) primary catalog, one (1) data source, up to forty (40) seed merchandising rules, and a golden query set of ten (10) to twenty (20) queries
  • The engagement is limited to the configuration of one (1) cluster only, up to ten (10) nodes for self-managed deployments
  • No material changes to scope, target environment, architecture, or objectives are introduced after kickoff
  • Elastic's configuration and recommendations depend on the completeness, accuracy, and timeliness of the information and data provided by Customer or made available from the target environment during the engagement

If any of the above assumptions are not met, Elastic may adjust the schedule, limit the services performed to fit the fixed-price scope, or require an Order Form (change order).

Deliverables

  • Search use case and intent discovery summary
  • Source data and dataset review for one (1) catalog and one (1) data source
  • Cluster and environment health review findings and recommendations
  • Data model review and/or new data model design
  • Analyzer and query understanding design
  • PRISM rule framework enablement
  • Forty (40) seed merchandising rules
  • Rule governance and precedence guidance
  • Golden query set (10–20 queries) with a minimal test harness
  • Basic RBAC guidance for up to two (2) roles
  • One (1) final report
  • Engagement documentation
  • One (1) knowledge transfer workshop

Completion

The engagement will be considered to have reached Completion upon delivery of the cluster and environment health review findings, the data model review and/or design, the analyzer and query understanding design, the PRISM rule framework enablement and seed merchandising rules, the golden query set and test harness, the RBAC guidance, the final report, and Elastic's delivery or making available of the knowledge transfer workshop. The engagement may also be deemed to have reached Completion if Customer delays, is unavailable, fails to meet required dependencies, or is otherwise unable to participate after Elastic has made commercially reasonable efforts to schedule and deliver the services within the agreed scope. Completion is not conditioned on Customer's participation in, use of, or response to any deliverable or session.

General terms

Capitalized terms used but not defined in this package description have the meanings given to them in the Order Form, the applicable Service Description, or the Elastic Services Agreement.

No formal Customer signoff and no milestone or deliverable acceptance process applies to this fixed-price Services Package. Each Service is deemed accepted upon Completion.

"Completion" means, with respect to a Service, the point at which Elastic has performed the activities within the scope of this Services Package, including (where applicable) delivery of any written report, materials, or knowledge transfer session described in this package's scope, or the expiry of the time-boxed engagement period for this package, whichever occurs first. Completion does not require Customer signoff or acceptance of any deliverable.

Customer is solely responsible for the backup, maintenance, and security of its environment, systems, and data. Elastic is not responsible for any configuration changes, data loss, downtime, or other impact to Customer's environment arising from or in connection with the Service.

This engagement delivers a configured PRISM (Policy, Rules, & Intent Synthesis Middleware) implementation, including data modeling, rule authoring, and a golden query test harness, within the defined fixed-price scope. Certain deliverables — including data ingestion, RBAC, and application integration — are advisory and demonstration-based; Elastic provides guidance and examples, and Customer's team is responsible for implementation. PRISM is a services accelerator, not a supported Elastic product; following Completion, PRISM is customer-operated, and Elastic is not responsible for its ongoing support, maintenance, or operation unless separately purchased. Elastic does not guarantee any specific performance, cost, operational, or business outcome beyond the deliverables defined above. Customer remains solely responsible for ongoing operations, configuration changes made outside the engagement scope, and all post-engagement activities related to its environment.

References in this package to validation, testing, acceptance tests or acceptance test harnesses, golden queries, launch readiness, or go-live describe activities performed, demonstrated, or delivered by Elastic and do not create any Customer acceptance, signoff, testing, or payment condition. Completion occurs as defined in this package regardless of any such activity, and no portion of the fees is withheld or deferred pending any test result, validation, or go-live event.

Advanced

Overview

A fixed-price, time-boxed implementation engagement to deploy and operationalize Elastic's PRISM (Policy, Rules, & Intent Synthesis Middleware) framework for intelligent, natural-language product search, on one (1) Elastic Cloud Hosted (ECH)/Serverless or self-managed (ECE/ECK) cluster of up to ten (10) nodes for self-managed deployments. This engagement supports either a net-new PRISM implementation or the replacement of an existing (legacy) search experience, for customers whose environment or catalog structure is more complex. The customer's environment may include multiple catalogs or complex configurations; however, this engagement's PRISM rule authoring and configuration is scoped to one (1) primary product catalog and its associated rule set — cross-catalog or cross-category rule logic requires a mutually executed Order Form (change order) regardless of environment complexity. This engagement is limited to one (1) cluster only. Any additional clusters, deployments, environments, or expanded scope are expressly out of scope unless otherwise agreed in a mutually executed Order Form (change order). PRISM is a services accelerator, not a supported Elastic product, and is customer-operated following delivery.

Scope

  • Conduct deep discovery to understand the customer's business search use case, intent, and desired versus undesired search outcomes, for environments with complex catalog structures or configurations.
  • Review the source-of-truth dataset for one (1) primary catalog, including current data format and search-relevant fields.
  • Review the target cluster's topology, node settings, non-production/pre-production environment access, and backup and recovery planning, using available diagnostic tooling; report risks and recommendations (advisory only — no hands-on remediation).
  • Review the existing data model (if applicable) and/or design a new or refactored data model aligned to the search use case.
  • Review and design advanced analyzers, relevance, and query understanding configuration, and provide education on the PRISM rule-lookup (percolator-based) mechanism.
  • Review and provide guidance on the ingest and transformation workflow for up to three (3) data sources, including orchestration guidance and validation/testing; this is a review/guidance service — Elastic does not build or operate the ingest pipeline.
  • Enable the PRISM rule framework and author up to one hundred (100) seed merchandising rules.
  • Design rule governance and precedence guidance covering how multiple rules interact and take precedence.
  • Extend PRISM rule capabilities for up to two (2) to three (3) additional constrained rule patterns within the single primary catalog, as needed; multi-catalog or cross-category rule logic requires a mutually executed Order Form (change order).
  • Curate a golden query set of twenty (20) to forty (40) queries with expected outcomes and a pass/fail rubric, and build a minimal test harness exercising PRISM query construction against the set.
  • Conduct an integration workshop and provide high-touch advisory pairing support for integrating PRISM into the customer's application query flow; this is advisory/pairing only — no hands-on coding in the customer's application, and no API gateway or authentication work; the customer's team implements.
  • Implement indexing strategy (e.g. blue-green indices) and review indexing efficiency.
  • Demonstrate how to evaluate and debug queries, review search queries and client-developed application code for improvement opportunities, and implement improvements to reduce query latency.
  • Discuss and provide guidance on advanced RBAC structure for several users, including examples of complex document-level RBAC; this is guidance only — Elastic does not configure RBAC on the customer's behalf.
  • Provide advice and guidance on incorporating metrics into search results, and demonstrate how to benchmark and profile queries.
  • Conduct a security review and provide remediation guidance, including minor, non-invasive fixes; broader remediation requires a mutually executed Order Form (change order).
  • Provide launch readiness advisory and a go-live checklist; the customer owns the production runbook.
  • Demonstrate how to set up monitoring, alerting, and dashboards.
  • Complete a non-production rehearsal of reindexing (if needed), and provide cutover planning advisory and go-live documentation; the customer owns the production runbook and approvals.
  • Conduct training sessions demonstrating how PRISM works to business and technical stakeholders, conduct a knowledge transfer workshop, provide documentation and a final report, and transfer engagement assets to the customer.

Out of scope

This engagement does not include:

  • Evaluation, configuration, or ingestion of catalogs or data sources beyond the one (1) primary catalog and up to three (3) data sources defined in Scope
  • Hands-on build, operation, or ongoing management of data ingestion pipelines; ingest work is advisory/review only
  • Authoring of merchandising rules beyond the one hundred (100) seed rules and the up to two (2) to three (3) additional rule pattern extensions defined in Scope
  • Multi-catalog or cross-category rule logic
  • Golden queries or acceptance test cases beyond the twenty (20) to forty (40) queries defined in Scope
  • Hands-on remediation of cluster configuration, backup/recovery, or infrastructure issues identified during the environment review; this is an advisory review only
  • Hands-on coding in the customer's application, API gateway configuration, or authentication work; this is advisory/pairing only, and the customer's team implements
  • RBAC configuration on the customer's behalf; RBAC work is guidance and examples only, and the customer implements
  • Production monitoring, alerting, or dashboard configuration; monitoring work is demonstration only
  • Production runbook ownership, cutover execution, or go-live approvals; these remain with the Customer
  • Security remediation beyond minor, non-invasive fixes; broader remediation requires separate scoping under a mutually executed Order Form (change order)
  • Reference search UI or admin UI development, demonstration, or customization
  • Ongoing support, operation, or maintenance of the PRISM configuration after Completion; PRISM is a services accelerator, not a supported Elastic product, and is customer-operated
  • Evaluation, configuration, or integration of additional clusters, deployments, or environments
  • Deployments or cluster sizing exceeding ten (10) nodes (self-managed)
  • Project management beyond internal Elastic delivery coordination

Any work outside the scope above requires a mutually executed Order Form (change order) and may result in additional fees, revised assumptions, and schedule changes.

Engagement timeline

  • Scheduled to commence approximately 6–8 weeks after purchase, subject to resource availability and Customer readiness
  • Delivered by an Elastic Consultant or a certified partner resource under Elastic oversight
  • Unless otherwise agreed in writing, the services will be delivered remotely
  • Delivery is expected to occur over contiguous business days or contiguous calendar weeks, as scheduled by Elastic
  • If delivery is delayed, interrupted, or rescheduled due to Customer availability, access issues, environment readiness, or other Customer dependencies, Elastic may reassign resources, adjust the schedule, or require an Order Form (change order)
  • Time scheduled for the engagement that cannot be used due to Customer delay, unavailability, failure to meet dependencies, or inability to provide required access will count against the total consulting days

Fixed-price conditions and assumptions

The fixed price is based on the following assumptions and conditions:

  • Customer provides all required access, credentials, documentation, and relevant architectural information before the kickoff call
  • Customer designates a single point of contact and ensures appropriate technical stakeholders are available and responsive throughout the engagement
  • The target cluster is accessible, operational, and ready for configuration at the start of the engagement
  • Customer provides access to real source data or realistic sample data for the one (1) primary catalog and up to three (3) data sources in scope
  • Customer objectives, desired versus undesired search outcomes, and merchandising priorities are defined and agreed before kickoff
  • The engagement is limited to one (1) primary catalog, up to three (3) data sources, up to one hundred (100) seed merchandising rules, and a golden query set of twenty (20) to forty (40) queries
  • The engagement is limited to the configuration of one (1) cluster only, up to ten (10) nodes for self-managed deployments
  • No material changes to scope, target environment, architecture, or objectives are introduced after kickoff
  • Elastic's configuration and recommendations depend on the completeness, accuracy, and timeliness of the information and data provided by Customer or made available from the target environment during the engagement

If any of the above assumptions are not met, Elastic may adjust the schedule, limit the services performed to fit the fixed-price scope, or require an Order Form (change order).

Deliverables

  • Deep search use case and business discovery summary
  • Source data and dataset review for one (1) catalog
  • Cluster and environment health review findings and recommendations
  • Multi-source ingest guidance (up to 3 sources)
  • New or refactored data model design
  • Advanced analyzer and relevance design
  • PRISM rule framework enablement, including up to two (2) to three (3) additional rule pattern extensions
  • One hundred (100) seed merchandising rules
  • Advanced rule governance and precedence guidance
  • Golden query set (20–40 queries) with an extended test harness
  • Advanced RBAC guidance, including complex document-level access control examples
  • Query latency profiling and improvement
  • Security review findings and minor, non-invasive remediation guidance
  • Launch readiness advisory and go-live checklist
  • Monitoring, alerting, and dashboard setup guidance
  • Cutover and go-live advisory, including a non-production reindex rehearsal
  • One (1) final report
  • Engagement documentation
  • One (1) knowledge transfer workshop

Completion

The engagement will be considered to have reached Completion upon delivery of the cluster and environment health review findings, the data model design, the advanced analyzer and relevance design, the PRISM rule framework enablement and seed merchandising rules, the golden query set and extended test harness, the advanced RBAC guidance, the security review findings, the launch readiness and cutover advisory materials, the final report, and Elastic's delivery or making available of the knowledge transfer workshop. The engagement may also be deemed to have reached Completion if Customer delays, is unavailable, fails to meet required dependencies, or is otherwise unable to participate after Elastic has made commercially reasonable efforts to schedule and deliver the services within the agreed scope. Completion is not conditioned on Customer's participation in, use of, or response to any deliverable or session.

General terms

Capitalized terms used but not defined in this package description have the meanings given to them in the Order Form, the applicable Service Description, or the Elastic Services Agreement.

No formal Customer signoff and no milestone or deliverable acceptance process applies to this fixed-price Services Package. Each Service is deemed accepted upon Completion.

"Completion" means, with respect to a Service, the point at which Elastic has performed the activities within the scope of this Services Package, including (where applicable) delivery of any written report, materials, or knowledge transfer session described in this package's scope, or the expiry of the time-boxed engagement period for this package, whichever occurs first. Completion does not require Customer signoff or acceptance of any deliverable.

Customer is solely responsible for the backup, maintenance, and security of its environment, systems, and data. Elastic is not responsible for any configuration changes, data loss, downtime, or other impact to Customer's environment arising from or in connection with the Service.

This engagement delivers a configured PRISM (Policy, Rules, and Intent Synthesis Middleware) implementation, including data modeling, rule authoring, and a golden query test harness, within the defined fixed-price scope. Certain deliverables — including data ingestion, RBAC, application integration, security remediation, monitoring, and launch/cutover activities — are advisory and demonstration-based; Elastic provides guidance, examples, and (where noted) minor non-invasive assistance, and Customer's team is responsible for implementation, production runbook ownership, and go-live approvals. PRISM is a services accelerator, not a supported Elastic product; following Completion, PRISM is customer-operated, and Elastic is not responsible for its ongoing support, maintenance, or operation unless separately purchased. Elastic does not guarantee any specific performance, cost, operational, or business outcome beyond the deliverables defined above. Customer remains solely responsible for ongoing operations, configuration changes made outside the engagement scope, and all post-engagement activities related to its environment.

References in this package to validation, testing, acceptance tests or acceptance test harnesses, golden queries, launch readiness, or go-live describe activities performed, demonstrated, or delivered by Elastic and do not create any Customer acceptance, signoff, testing, or payment condition. Completion occurs as defined in this package regardless of any such activity, and no portion of the fees is withheld or deferred pending any test result, validation, or go-live event.