Understanding Key Definitions (KDs)

Why is a concept like Key Definition needed?

Every time you run an analysis in Petavue, the system generates a plan. A plan contains the execution steps: which tables and columns are selected, filters applied, and how each metric is calculated.

Without Key Definitions, the same metric could be defined differently each time you run an analysis. You might not notice the change, but the results would be inconsistent and trust in the output would suffer.

This is why Key Definitions (KDs) are essential.

What are Key Definitions (KDs)?

A Key Definition (KD) is a standardized metric or business term that ensures consistency across all analyses.

• Once a KD is defined, Petavue always applies the same formula when that metric is used.

  
  

• KDs can be scoped to an individual, a team, or the entire organization.

  
  

• Petavue provides a Metric Library of common KDs that can be configured on your data for specific use cases. This library is only a starting point, you can also create new KDs tailored to your own business needs beyond what’s included.

  
  

Types of KDs

Petavue supports two types of KDs:

1. Formula KDs → A metric or calculation defined with a formula.

   • Example: Pipeline Velocity is defined as (Total Pipeline Value / Average Sales Cycle Days).

     
     

     Term KDs → A business term defined by preferences or filters rather than a formula.

   • Example: Sales Touches could always be defined as only “call, email, or meeting” activities, excluding other task types.

     
     

When should I create a KD?

• When you have a metric or term that you want calculated the same way every time, across different analyses.

  
  
• When you need consistency across teams, so everyone is speaking the same language when they say “churn,” “pipeline velocity,” or “sales touches.”

How to Create a KD in Petavue

Follow this flow to create a KD from the Petavue UI:

1. Run an analysis

   • Example: “Show me the health and status of pipeline for deals created in the last 2 years, including pipeline velocity.”

     
     

   • A plan is generated. In step 3 of the plan below, you can see the formula for pipeline velocity.

     
     

2. Review the plan

   • Suppose the plan calculates Pipeline Velocity, if you want to use a different definition, modify the plan accordingly and execute the analysis.

     
     

     Create the KD

   • After execution, simply tell Petavue: “Remember Pipeline Velocity as a KD.”

     
     
   • Petavue will then open the KD creation flow, showing you the proposed name, description, formula, and the relevant tables/columns.

• Review the details and, if everything looks correct, approve the creation. The KD will then be saved and available for future analyses.

4. Use the KD in future analyses

   • Next time you ask a question involving Pipeline Velocity, Petavue automatically uses the KD logic.

     
     

   • The plan will reference the KD, ensuring consistency across runs.

     
     

     Find your KD

   • Go to Data Catalog → Definitions to view the KD you just created.

Editing or Deleting a KD

• Currently, you cannot edit the formula of an existing KD. Formula editing will be available in a future release.

  
  
• You can:
  • Edit the name and description.

  • Delete or disable a KD.

    
    
• If the formula itself needs to change, disable the existing KD and create a new one with the updated logic.