Prophecy Enterprise Express Statement of Work

‍‍This Statement of Work (this “SOW”) is entered into and governed by the license agreement executed by Customer and Prophecy.

1. PROJECT OVERVIEW

The purpose of this Prophecy Enterprise Express SOW is to provide services designed to assist Customer in deploying the applicable Prophecy software module, based on best practice, reference architecture and selected use case(s). Customer must be committed to deploying the use case during an agreed upon timeframe. The standard milestones and timeline for the entire SOW is set forth below. Each project begins with an initiation phase that will produce the High Level Design Document (HLDD) and validate the contents with the Customer.

2. MILESTONE & TIMELINE

Milestone Name	Estimated Timeline	Definitions of Activities and Scope
Initial Introduction & Readiness	Week 0 1 – 2 Weeks*	Initial call Use Case Selection Customer Readiness Checklist Review Next Steps
Project Start
Project Initiation	Week 1	Project Kickoff Review of SOW (1 hr) Readiness Review Next Steps
Discovery & Design	Week 2	Discovery & Design Session (4 hours) High Level Design Document (HLDD)
Prophecy Platform Foundations	Week 3	Platform connectivity established Source, destination, and notification integrations complete
Implementation	Week 4–7	Implementation of the selected use case(s) per the HLDD
Project Closeout	Week 8	As built demo As built updates to the HLDD Project acceptance Adoption planning (CSM)

‍* Time elapsed to Project Start will be determined by Customer timeframe to accomplish remaining “readiness” activities

3. SCOPE OF WORK

Initial Introduction & Readiness

The initial call is an opportunity for the Customer to meet the CSM that will be working with them throughout their journey and review the project prerequisite. Introduction & Readiness activities may include:

Initial call (1 hour)
- Participants:
  - Customer Project Team
  - Prophecy Account Executive
  - Prophecy Customer Success Manager (CSM)
- Agenda
  - Welcome
  - Use Case Selection (details in section 4 below)
  - Customer Readiness Checklist Review
  - Recommended Education
  - Next Steps

Project Initiation

Once the Customer has confirmed with the CSM they are ready for the Services project to begin, a formal kickoff call will be scheduled where the CSM and Data Solutions Architect (DSA) will walk them through the onboarding process. Project Initiation activities may include:

Project Kickoff Call (1 hour)
- Participants:
  - Customer Project Team
  - Customer Champion/Executive Buyer
  - Prophecy Account Executive
  - Prophecy CSM
  - Prophecy DSA
- Agenda
  - Review of SOW
  - Review of Platform Configuration Readiness Worksheet
  - Readiness Review
  - Next Steps

Discovery & Design

The design phase is the opportunity for the DSA and Customer to align on the technical details and desired business outcomes of the implementation. Discovery and Design activities may include:

Discovery Call (2 hours*)
- Participants:
  - Customer Project Team
  - Customer Subject Matter Experts
  - Prophecy CSM
  - Prophecy DSA
- Agenda
  - Review of SOW
  - Readiness Review
  - Next Steps

*In the event the DSA does not have sufficient details from the Discovery call to move forward with creating the HLDD, they will request an additional session.

High Level Design Document

Approximately, three (3) business days following the final discovery session the DSA will provide the Customer a HLDD design document for their review. HLDD contents may include but are not not limited to:

Groups/Teams
Integrations, Sources, Destinations, Other Sources (SMTP Server, Microsoft SharePoint, etc)
Use Case Objectives (definition of done)

Prophecy Platform Foundations

Prophecy Platform Foundations is designed to ensure connectivity and functionality are established and the groundwork laid for the remaining implementation. This will be done through a series of remote working sessions and asynchronous work where the DSA guides the customer through the required configurations. Prophecy Platform Foundations outcomes may include:

Baseline connectivity established (PrivateLink or IP whitelisting between Prophecy and Databricks environment)
GIT and IDP configuration and connection to Prophecy
Source, destination, and notification Integrations complete

Implementation

During Implementation the DSA works collaboratively with the customer through a series of remote working sessions and asynchronous work to implement the selected use case and achieve the outcomes as defined in the HLDD.

Project Closeout

As the use case is completed and reviewed with the Customer team, the CSM will work with the Customer to help them define and document the next steps on the adoption journey. The CSM will also ensure the Customer has access to product documentation, support, and key Prophecy resources to assist them moving forward. Project Closeout activities may include:

As built demo
As built updates to the HLDD
Project acceptance
Adoption planning (CSM)

4. USE CASE SELECTION

USE CASE SELECTION

Services for one (1) use case are included with the purchase of Prophecy Express. Customer may select one (1) use case from the options below.

USE CASE OPTIONS
NEW PIPELINE
Develop one (1) new data analysis pipeline, using AI, automation, and observability, on Prophecy Enterprise Express. The pipeline developed may leverage Prophecy AI Agents to assist with pipeline logic creation and data curation. The pipeline will be deployed with Prophecy Automate, scheduled to run on the Prophecy platform, and code managed through a supported GIT provider. The process to promote the pipeline between environments will be documented and shared with the Customer.
Activities	Provide guidance on networking configuration for either PrivateLink or IP whitelisting connectivity between required integrations with Prophecy Enterprise Express Configure integration between Databricks and Prophecy Enterprise Express Configure integration between GIT and Prophecy Enterprise Express Configure integration between up to a total of five (5) sources, destinations, or external sources (e.g., SMTP Server, Microsoft SharePoint, etc.). Configure connectivity between Prophecy Enterprise Express and Customer LLM endpoint. Guide customer through using Prophecy Enterprise Express agents to build new data analysis pipeline logic Guide customer through using Prophecy Enterprise Express agents for data exploration Guide customer through testing and triaging data analysis pipeline execution and testing Guide customer through committing data analysis pipeline code to GIT provider Guide customer through using Prophecy Automate for scheduling data analysis pipeline execution Guide customer through using Prophecy Observability to monitor data analysis pipeline execution and errors Document process for promoting data analysis pipeline between environments
Outcomes	Successful new data analysis pipeline capable of running on a schedule in one (1) customer environment Pipeline code capable of being managed through normal software development lifecycle
Out of Scope	Any integrations / sources / targets or Gems not supported out-of-the-box (“OOTB”) Configuration of VPC connectivity Configuration of any customized IDP (support for Okta is standard) Creation of Spark pipelines

PIPELINE MODERNIZATION
Modernize and migrate one (1) Alteryx workflow, using AI, automation, and observability, on Prophecy Enterprise Express. The resulting pipeline will be modernized leveraging Prophecy AI Agents to assist with pipeline logic translation. The pipeline will be deployed with Prophecy observability, scheduled to run on the Prophecy platform, and pipeline code managed through a supported GIT provider. The process to promote the pipeline between environments will be documented and shared with the Customer.
Activities	Provide guidance on networking configuration for either PrivateLink or IP whitelisting connectivity between required integrations with Prophecy Enterprise Express Configure integration between Databricks and Prophecy Enterprise Express Configure integration between GIT and Prophecy Enterprise Express Configure integration between up to a total of five (5) sources, destinations, or external sources (e.g., SMTP Server, Microsoft SharePoint, etc.). Configure connectivity between Prophecy Enterprise Express and Customer LLM endpoint. Analyze up to one hundred (100) Alteryx workflows and provide report on Prophecy coverage report. In collaboration with Customer, Prophecy to select one (1) suitable Alteryx workflow to modernize on the Prophecy platform. Translate the selected Alteryx workflow into a Prophecy native data analysis pipeline Guide Customer through using Prophecy Enterprise Express agents for resolving conflicts and missing logic in the translated pipeline Guide Customer through testing and triaging data analysis pipeline execution and testing pipeline output Guide Customer through committing data analysis pipeline code to GIT provider Guide Customer through using Prophecy Automate for scheduling data analysis pipeline execution Guide Customer through using Prophecy Observability to monitor data analysis pipeline execution and errors Document process for promoting data analysis pipeline between environments
Outcomes	Successful modernized data analysis pipeline capable of running on a schedule in one (1) customer environment Pipeline code capable of being managed through normal software development lifecycle
Out of Scope	Any integrations / sources / targets or Gems not supported OOTB Configuration of VPC connectivity Configuration of any customized IDP (support for Okta is standard) Creation of Spark pipelines Custom development or modifications to the Prophecy Enterprise Express platform core code or functionality. Creation, delivery or support of custom-built modules or extensions for any solutions Any workflows beyond one (1) Alteryx workflow

5. ENVIRONMENT REQUIREMENTS

Networking: PrivateLink or IP Whiteslisting
- Connectivity from Prophecy Enterprise Express platform to Databricks REST API endpoints
- Connectivity between Prophecy Enterprise Express platform and Customer GIT provider
- Connectivity between Prophecy Enterprise Express platform and use case required external data sources (e.g., Oracle, SharePoint, etc)
Customer LLM endpoint if not using Prophecy OpenAI endpoint
Customer GIT provider in OOTB supported list of GIT providers and is configured per documented configuration methods (see doc link)
Identity Management
- Not customized IDP passthrough (.e.g., standard OKTA)
- If not using Prophecy username / password authentication, Customer IDP must pass same email address as is used with Databricks OAUTH
Customer outcome leverages OOTB supported source and destination Gems (see doc link)‍

6. Customer Responsibilities

Prophecy’s ability to deliver the Services is dependent upon Customer’s cooperation, as well as the accuracy and completeness of any information and data Customer provides. Customer’s responsibilities are detailed below:

Customer will complete their required prerequisites set forth in the Customer Readiness Checklist
Customer will provide all requested contact information for the Customer’s key business leaders and stakeholders required for Prophecy to provide the Services
Customer will coordinate communications with, and provide contacts for, all third parties necessary for the completion of the use case(s)
Customer will provide appropriate technical resources to work collaboratively with Prophecy.
Customer will deliver timely responses to requests for information, technical questions and requested decisions pertaining to the project and the SOW.
Customer will manage and supervise Customer’s contractors and service providers as necessary to support the Services
Customer will assign a designated project lead from Customer’s staff who, on its behalf, will grant all approvals, provide information, make decisions, attend meetings, and otherwise be available to assist Prophecy in facilitating the delivery of the Services
Customer will provide timely access to systems, information, and personnel necessary for Prophecy to perform the services.
If the SOW includes Advisory Services, those services are at the direction and prioritization of the Customer.

7. Prophecy Responsibilities

Prophecy is responsible for providing the Services.
All Services will be provided remotely unless mutually agreed to.
The Services will be delivered as a single, continuous project. If Customer requires additional scope, the parties must execute a separate agreement.
Prophecy standard maintenance and support services are provided in accordance with Prophecy’ maintenance and support policy, and such services are not part of the SOW.
The Services provided under the SOW are specific to the Prophecy Enterprise Express licensed by Customer only, and do not include any consultation, guidance, or support for any other software, products, solutions or materials.‍

8. DELIVERABLES

Ownership. As between Customer and Prophecy, Prophecy retains all right, title and interest in the Services provided and any results of thereof including the deliverables specified in the SOW (collectively, “Deliverables”). Subject to Customer’s payment in full of all fees due under the SOW, Prophecy grants Customer a limited, non-exclusive, non-transferable and non-sublicensable right and license to use the Deliverables during the applicable Subscription Term in connection with Customer’s use of the applicable ModuleProducts in accordance with the Agreement. For the avoidance of doubt, Deliverables do not include any Customer Confidential Information, and any Customer Confidential Information contained in the Deliverables shall remain the sole and exclusive property of Customer.

‍