Document Search: Basic, Standard, and Advanced

Overview

A fixed-price, time-boxed implementation engagement to deploy a foundational Elastic document search solution on one (1) net-new Elastic Cloud Hosted (ECH) or Serverless cluster. This engagement is limited to one (1) net-new cluster only and does not cover existing (brownfield) deployments. Any additional clusters, deployments, environments, or expanded scope are expressly out of scope unless otherwise agreed in a mutually executed Order Form (change order).

Scope

• Conduct a technical discovery session to understand business search requirements and environment, and finalize one (1) in-scope dataset.
• Define up to five (5) sample queries for initial search experience validation.
• Develop and implement a foundational search deployment strategy using best practices, including data model design and ingestion for the one (1) in-scope dataset.
• Discuss, demonstrate, and implement one (1) basic example query and/or queries — showing how to use Kibana to inspect data and execute queries that retrieve relevant documents — optimized to work with the data model.
• Discuss, demonstrate, and implement basic RBAC, providing guidance and configuration for up to two (2) roles to ensure secure access to search data.
• Conduct a knowledge transfer session, 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 datasets beyond the one (1) dataset defined in Scope
• Sample or example queries beyond the five (5) defined in Scope
• Advanced search techniques not included in the Basic tier (e.g., partial text matching, fuzzy matching, autocomplete/typeahead, synonym incorporation, semantic search (ELSER and/or vector), filtering and faceting, spell checking)
• RBAC configuration beyond the two (2) roles defined in Scope, including document-level or other complex access controls
• Query latency evaluation or optimization
• Evaluation, configuration, or integration of additional clusters, deployments, or environments
• Evaluation or migration of existing (brownfield) Elastic deployments; this engagement covers net-new implementations only
• Project management beyond internal Elastic delivery coordination
• Ongoing support, operational ownership, or post-engagement remediation assistance unless separately purchased

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 ECH/Serverless cluster is accessible, operational, and ready for configuration at the start of the engagement
• Customer objectives, priorities, and the search use case are defined and agreed before kickoff
• The engagement covers a net-new (greenfield) implementation only; migration or evaluation of an existing deployment is out of scope
• The engagement is limited to one (1) in-scope dataset, up to five (5) sample queries, and basic RBAC for up to two (2) roles
• The engagement is limited to the configuration of one (1) cluster only
• 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 review of data sources for one (1) dataset
• Data model design and ingestion for the one (1) dataset
• One (1) basic example query and/or queries, optimized to work with the data model
• Basic RBAC guidance and configuration for up to two (2) roles
• One (1) final report
• Engagement documentation
• One (1) knowledge transfer session

Completion

The engagement will be considered to have reached Completion upon delivery of the search use case and source data analysis, the data model design and ingestion, the example query/queries, the basic RBAC configuration, the final report, and Elastic's delivery or making available of the knowledge transfer session. 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 net-new Elastic document search solution, including search use case analysis, data modeling and ingestion, basic example query implementation, basic RBAC configuration, and a final report, within the defined fixed-price scope. 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.

Overview

A fixed-price, time-boxed implementation engagement to deploy a foundational Elastic document search solution on one (1) net-new Elastic Cloud Hosted (ECH) or Serverless cluster. This engagement is limited to one (1) net-new cluster only and does not cover existing (brownfield) deployments. Any additional clusters, deployments, environments, or expanded scope are expressly out of scope unless otherwise agreed in a mutually executed Order Form (change order).

Scope

• Conduct a technical discovery session to capture detailed search requirements and environment specifics, and finalize one (1) in-scope dataset.
• Define up to five (5) sample queries for advanced search experience validation.
• Develop and implement a robust search deployment strategy, including data model design and ingestion for the one (1) in-scope dataset and advanced search features.
• Discuss, demonstrate, and implement advanced example query and/or queries optimized to work with the data model, covering additional search techniques such as partial text matching, fuzzy matching, autocomplete/typeahead, synonym incorporation, semantic search (ELSER and/or vector), filtering and faceting, and spell checking.
• Discuss, demonstrate, and implement advanced RBAC, providing guidance and configuration for several users, including complex document-level access controls.
• Evaluate and optimize query latency to ensure high-performance search experiences.
• 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 datasets beyond the one (1) dataset defined in Scope
• Sample or example queries beyond the five (5) defined in Scope, or search techniques beyond those defined in Scope
• RBAC configuration beyond the users and document-level access controls defined in Scope
• Evaluation, configuration, or integration of additional clusters, deployments, or environments
• Evaluation or migration of existing (brownfield) Elastic deployments; this engagement covers net-new implementations only
• Project management beyond internal Elastic delivery coordination
• Ongoing support, operational ownership, or post-engagement remediation assistance unless separately purchased

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 ECH/Serverless cluster is accessible, operational, and ready for configuration at the start of the engagement
• Customer objectives, priorities, and the search use case are defined and agreed before kickoff
• The engagement covers a net-new (greenfield) implementation only; migration or evaluation of an existing deployment is out of scope
• The engagement is limited to one (1) in-scope dataset, up to five (5) sample queries, and advanced RBAC for the users and document-level controls defined in Scope
• The engagement is limited to the configuration of one (1) cluster only
• 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 review of data sources for one (1) dataset
• Data model design and ingestion for the one (1) dataset
• Advanced example query and/or queries, optimized to work with the data model
• Advanced RBAC guidance and configuration, including document-level access controls
• 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 search use case and source data analysis, the data model design and ingestion, the advanced example query/queries, the advanced RBAC configuration, 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 net-new Elastic document search solution, including search use case analysis, data modeling and ingestion, advanced example query implementation, advanced RBAC configuration, and a final report, within the defined fixed-price scope. 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.

Overview

A fixed-price, time-boxed implementation engagement to deploy a foundational Elastic document search solution on one (1) net-new, self-managed Elastic deployment (including ECE/ECK). This engagement is limited to one (1) net-new cluster of up to ten (10) nodes and does not cover existing (brownfield) deployments. Any additional clusters, deployments, environments, or clusters exceeding ten (10) nodes are expressly out of scope unless otherwise agreed in a mutually executed Order Form (change order).

Scope

• Conduct an in-depth technical discovery to assess customer environment, infrastructure, and search objectives, and finalize one (1) in-scope dataset.
• Define up to five (5) sample queries for comprehensive search validation.
• Develop and implement a comprehensive search deployment strategy, including data model design and ingestion for the one (1) in-scope dataset, advanced search features, and infrastructure provisioning.
• Discuss, demonstrate, and implement advanced example query and/or queries optimized to work with the data model, covering additional search techniques such as partial text matching, fuzzy matching, autocomplete/typeahead, synonym incorporation, semantic search (ELSER and/or vector), filtering and faceting, and spell checking.
• Discuss, demonstrate, and implement advanced RBAC, providing guidance and configuration for several users, including complex document-level access controls.
• Evaluate and optimize query latency for peak search performance.
• Provision and validate infrastructure to support the self-managed deployment (up to 10 nodes).
• Conduct a thorough knowledge transfer session, hand over 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 datasets beyond the one (1) dataset defined in Scope
• Sample or example queries beyond the five (5) defined in Scope, or search techniques beyond those defined in Scope
• RBAC configuration beyond the users and document-level access controls defined in Scope
• Evaluation, configuration, or integration of additional self-managed deployments, clusters, or environments
• Evaluation or migration of existing (brownfield) Elastic deployments; this engagement covers net-new implementations only
• Deployments or cluster sizing exceeding ten (10) nodes
• Underlying infrastructure procurement, capacity planning beyond the provisioned environment, or ongoing infrastructure management
• Project management beyond internal Elastic delivery coordination
• Ongoing support, operational ownership, or post-engagement remediation assistance unless separately purchased

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 infrastructure is provisioned, accessible, operational, and ready for configuration at the start of the engagement
• Customer objectives, priorities, and the search use case are defined and agreed before kickoff
• The engagement covers a net-new (greenfield) implementation only; migration or evaluation of an existing deployment is out of scope
• The engagement is limited to one (1) in-scope dataset, up to five (5) sample queries, and advanced RBAC for the users and document-level controls defined in Scope
• The engagement is limited to the configuration of one (1) self-managed deployment (including ECE/ECK) of up to ten (10) nodes only
• 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 review of data sources for one (1) dataset
• Data model design and ingestion for the one (1) dataset
• Advanced example query and/or queries, optimized to work with the data model
• Advanced RBAC guidance and configuration, including document-level access controls
• Infrastructure provisioning and validation for the self-managed deployment (up to 10 nodes)
• One (1) final report
• Engagement documentation
• One (1) knowledge transfer session

Completion

The engagement will be considered to have reached Completion upon delivery of the search use case and source data analysis, the data model design and ingestion, the advanced example query/queries, the advanced RBAC configuration, the provisioned and validated infrastructure, the final report, and Elastic's delivery or making available of the knowledge transfer session. 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 net-new, self-managed Elastic document search solution, including search use case analysis, data modeling and ingestion, advanced example query implementation, advanced RBAC configuration, infrastructure provisioning, and a final report, within the defined fixed-price scope. 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.