Text in snackbars can bolded or underlined text for emphasis
Login
Start a Conversation

User Guide

A step-by-step guide to getting started with Chassi’s application

Version V2 © Chassi, Inc. 2025

Overview

Chassi is a cloud-based analytics and intelligence platform designed to provide visibility into operational performance across key business workflows. It enables users to explore, analyze, and act on real-time data related to cycle times, milestones, and other critical metrics. By combining data from multiple sources into a single, unified interface, Chassi helps organizations identify inefficiencies, uncover opportunities, and drive data-driven decisions.

Whether you’re tracking performance across customers, orders, or financial indicators, Chassi provides powerful tools to surface insights and monitor trends, all without the need for a complex technical setup.

Purpose

This user guide is intended to help you navigate and use the Chassi platform effectively based on your role. It covers:

  • How to log in and get started
  • An overview of key modules and navigation
  • Step-by-step instructions for using core features
  • Role-based access to specific tools and analytics
  • Troubleshooting tips and best practices

Key Terminology

Whether you are a Chassi Admin, Tenant Admin, or standard user, this guide provides the foundational knowledge you need to get the most value out of the platform.

Term
Definition
Tenant

A top-level environment in Chassi that can include multiple clients. Used to separate business entities.

Client

An individual environment within a tenant, representing a specific customer or business unit with its own data and configurations.

Chassi Rewind

A data ingestion process that pulls system events starting from the most recent and continues backward until it reaches the rewind date.

Rewind Date

The cutoff date for data ingestion. Events older than this date are excluded.

Event

A recorded action that reflects a change within the system. This includes activities like updating a field and renaming a form. Events help track user activity and show how data or documents change over time.

Record

A data object that represents a specific business entity, such as a Purchase Order, Customer, or Invoice. Each record contains related data fields.

Milestone

A predefined event or step tracked in the data (e.g., “Invoice Sent”, “Payment Received”).

Event Stream

A second-by-second account of a system’s user activity, capturing a chronological log of events such as updates, interactions, and changes.

Process

Defined business workflows (e.g., Purchase Orders, Invoices) that a Chassi admin selects to track in order to import relevant data and begin analysis.

Pathway

A visual representation of a process flow tracked in Chassi.

Getting Started

Browser: Latest versions of Chrome, Firefox, or Edge

How to Access the Application

  1. Visit: https://app.chassi.com 
  2. No installation required, as Chassi is a web-based application
  3. Bookmark the login page for quick access

Installation Options:

You can choose the installation method that best suits your team’s preferences and security protocols:

Option 1: Chassi Bundle Install
  • Grant us admin access to your systems of record
  • We handle installation independently
  • Requires only a 15-minute follow-up call with your team
Option 2: Chairside Install
  • A 30-minute meeting where we walk through the installation with your team
  • No admin access is required

How to Log In / Sign Up

  1. Navigate to the login page. 
  2. If you already have an account, enter your email and password to log in.
  3. For new users: You must be invited by an Administrator to create an account. 
    1. Once invited, you’ll receive an email with a sign-up link
    2. Click the link, set your password, and complete your profile to access the platform.

Account Roles & Permissions Overview

  • Chassi Administrator Role: Has full access to manage all tenants and clients across the Chassi platform. 
  • Tenant Administrator Role: Has access to manage users and clients within their tenant. 
  • Viewer Role: Has access to view and interact with the client data within Chassi.

Troubleshooting and Support:

For any support needs, navigate to Chassi’s Help & Support Page.

https://chassi.com/support/

Core Features

1. At A Glance

Purpose (What is it?)

The At a Glance module allows you to combine multiple similar pathways into a simplified, high-level view of a process. This helps you quickly identify potential bottlenecks, spot delays, and assess overall performance without reviewing each individual pathway in detail.

Overview (Why use it?)

The At a Glance module provides a summarized snapshot of multiple pathways by flattening them into a single, unified view. When you select at least two milestones and redefine the population by applying filters, Chassi generates an aggregated visualization that displays key metrics such as total pathways, total orders, median cycle time, and average rework. These metrics help surface performance trends and timing insights across processes, enabling you to quickly understand overall workflow behavior and identify areas that may need attention.

Common examples of processes tracked with At a Glance include:

  • Lead to Cash
  • Opportunity to Cash
  • Order to Cash
Who Can Access AAGs
  • Tenant Admins 
  • Chassi Admins
  • Viewers
How to Use It
  1. Navigate to the At a Glance module on the Dashboard page.
  2. Click + Create Your First Process Measurement. 
  3. Fill in the required information:
    • Title (e.g., Lead to Cash)
    • + Milestones: Select at least two (up to eleven) milestones relevant to the workflow you want to analyze (e.g., Opportunity Created, Sales Order Created, Invoice Created).

      Important:

      • The order of milestones matters. It must reflect a sequence that actually exists in the data.
      • Exactly two milestones must be selected to proceed. If more than two are pre-filled, delete the extras so only two remain.
  1. Click Next to define the population criteria (optional):
    • Pathway Criteria Filters:
      • Includes: Pathways that include the listed milestones.
      • Excludes: Pathways that exclude the listed milestones.
      • Employees: Pathways that involve at least one of the listed employees.
      • Customers: Pathways that involve at least one of the listed customers.
      • Subsidiary: Filter pathways by business unit or segment.
      • Time Frame: Pathways completed within the specified date range.
  2. Define the Time Frame: 
    • Select a customized date range or choose from the available drop-down options to specify the period for your analysis.
    • Beginning: The process measurement will start from the first milestone you selected.
    • Ending: The process measurement will end at the last milestone you selected.
  3. Review the Population Metrics summary based on your filters.
  4. Click Save to generate the flattened snapshot of matching pathways.
Understanding the Metrics
  • Pathways: Number of distinct workflows matching the selected criteria.
  • Orders: Volume of orders within the selected population.
  • Med Cycle Time:  Median time taken between the first and last milestone; useful for identifying typical process duration.
  • Avg Rework: Average number of times steps were repeated or modified; indicates potential inefficiencies.
  • Segmentation Calculation: A visual pathway shows the median cycle time between two selected milestones. Clicking on this pathway expands a detailed view displaying both the median and average cycle times for that segment, allowing deeper analysis of timing and performance between milestones.

2. Cycle Time Analysis (CTAs) 

Purpose

The purpose of a CTA is to measure and analyze the time spent between two specific milestones, helping you identify delays, monitor performance trends, and uncover opportunities for process improvements within targeted segments of your workflow.

Overview

Cycle Time Analysis (CTA) enables you to view the average time it takes for processes to progress between two defined milestones (“From” and “To”) within a selected time frame. By creating a CTA, you gain a focused view of process durations between these key steps.

Common examples of CTAs
  • Invoice Created to Paid
  • Bill Created to Paid
  • Opportunity Created To Won
Who Can Access CTAs 
  • Tenant Admins 
  • Chassi Admins
  • Viewers 
How to Use It
  1. Navigate to the Cycle Time Analysis module on the Dashboard page.
  2. Click + Cycle Time Analysis to create a new CTA.
  3. Fill in the required information:
    1. Title: Give your CTA a descriptive name (e.g., Invoice Created to Paid).
    2. Select From Milestone: Choose the starting milestone.
    3. Select To Milestone: Choose the ending milestone.
    4. (Optional) Set Pathway Criteria by expanding the filters:
      1. Includes: Pathways that include the listed milestone. 
      2. Excludes: Pathways that exclude the listed milestones.
      3. Employees: Pathways involving one or more specified employees.
      4. Customers: Pathways involving one or more specified customers.
      5. Subsidiary: Filter pathways by business unit or segment.
      6. Time Frame: Pathways completed within the specified date range.
    5. Define the Time Frame: 
      1. Select a customized date range or choose from the available drop-down options to specify the period for your analysis.
      2. Beginning: The CTA date range starts at the ‘From’ milestone you selected.
      3. Ending: The CTA date range starts at the ‘To’ milestone you selected.
    6. Review the Population Metrics summary based on your filters.
    7. Goal: Define a timeframe to achieve each cycle time target.. 
    8. Set an Exception: Specify a cycle time threshold to flag records for the exception report. 
  4. Click Save to add your Cycle Time Analysis.
Understanding the Metrics
  • Median: The median time it takes to complete the selected CTA milestone across all applicable records.
  • Average: The average time taken to complete the selected CTA milestone.
  • Goal:  Set the desired time frame to complete the selected CTA milestones. This represents the target duration you aim to achieve.
    • It serves as a benchmark for success and helps track progress toward efficiency improvements.
  • Exceptions: Define a cycle time threshold that, when exceeded, flags the CTA in the exception report.
    • This helps you quickly identify outliers and areas that may need further investigation or corrective action.
  • CTA Time Frame: The date range applied specifically to evaluate the selected CTA milestone(s).
  • CTA Count: The number of records where the selected CTA milestone occurred and was measured.
Drilling Down Into Metrics

All metrics for the CTA, including Median, Average, Goal, Exceptions and CTA Time Frame support drill-down functionality. When you click on any metric, you’ll access a detailed view that provides deeper insights into the data for the associated CTA. 

  1. Cycle Times Distribution
     Explore how cycle times vary within the selected CTA using:
    1. A Scatter Plot to visualize individual cycle times and spot trends or outliers.
    2. A Histogram to understand the distribution and frequency of cycle times.
    3. A Detailed Table listing all individual cycle times for full transparency: 
      1. Order Number
      2. Customer Name
      3. Order Created Date
      4. A Timestamp (From Milestone)
      5. B Timestamp (To Milestone)
      6. Cycle Time: Duration from Milestone A to B
  2. Exceptions
     View any exceptions that were defined and triggered by the user for this CTA. This helps identify where the process deviated from expected norms.
  3. Root Cause Analysis (BETA)
     Get early-stage insights into potential root causes behind delays or exceptions.
    Note: This feature is currently in BETA and subject to ongoing updates.

3. Pathways

Purpose

Pathways help you uncover how work truly moves through your system. You can measure variations, spot inefficiencies, and identify bottlenecks. With flexible filtering, you can narrow in on specific customers, subsidiaries, or processes to analyze what matters most.

Overview

The Pathways module provides a visual representation of how your processes actually unfold, not just how they were designed. It maps real workflows by tracing each milestone and variation across records, giving you an objective, end-to-end view of process behavior.

Key Benefits
  1. Visualize actual workflow behavior across records
  2. Identify deviations and variations across similar processes
  3. Pinpoint inefficiencies, delays, or unnecessary steps
  4. Quickly filter by milestones, employee, customer, and more
Who Can Access Pathways
  1. Tenant Admins 
  2. Chassi Admins
  3. Viewers 
How to Use It
  1. Navigate to the Pathways tab from the sidebar menu. You’ll land on the Pathways page, where the pathways are displayed from most to least orders. 
  2. Click Filter Pathways to expand the Pathway Criteria panel and view all available filters.
  3. Use the available filters to refine your results. You can filter pathways by:
    • Includes Milestone: only show pathways that contain specific milestones.
    • Excludes Milestone: removes pathways that contain certain milestones.
    • Employee: focus on records associated with a specific user.
    • Pathway ID: display pathways corresponding to a specific identifier, showing the exact sequence of milestones within that pathway
    • Customer: limit results to a specific customer account.
    • Subsidiary: view pathways tied to a specific business unit or entity.
    • Date Range: filter by a defined time frame.
  4. Click Update to save filters and render results.
Understanding the Metrics

Each pathway includes a set of key performance metrics to help you evaluate performance and identify trends. 

  • Pathways: Total number of unique pathways returned based on the applied filters.
  • Orders: Total number of orders that follow each pathway.
  • Median Cycle Time: The middle value of the cycle time for orders within the pathway, giving a sense of typical duration.
  • Average Cycle Time: The mean cycle time for all orders in the pathway.
  • Average Reworks (Field):  The average number of times a field was reworked across all orders in the pathway.

4. Process Tracker

Purpose

The purpose of the Process Tracker is to allow users to identify and configure which business processes are relevant for analysis. It ensures that only meaningful data is tracked and visualized, helping users focus on workflows that matter and reduce noise from irrelevant or incomplete data.

Overview

The Process Tracker provides users with the insight to manage the business processes they want to analyze. By selecting specific processes to track, users can view record relationships, import data for analysis, and manage which records are included in the workflow. This module serves as the entry point for process mapping and operational insights.

Who Can Access the Process Tracker
  • Tenant Admins 
  • Chassi Admins
  • Viewers (View-only)
How to Use It
  1. To Add a New Process
    1. From the sidebar menu, click on the Tenant name to expand the submenu, then select Processes to open the Process Tracker.
    2. Click Add Process – the Process Root modal will appear, showing the top 5 process records and a full list of detected records from the dataset. 
    3. Select one record  (i.e. Invoice, Sales Order) and click Track. 

When configuring a process, you can adjust the following filters to refine how your process is structured and visualized:

  1. Process Root: The main anchor of the process flow. For example, selecting “Invoice” makes it the starting point of your process map.
    1. Generations: Defines how many levels deep the process should display from the root. A value of “5” means it will include up to 5 downstream steps or entities.
    2. Minimum Instances: Set the minimum number of occurrences a process record must have occurred in the results. (Example: Setting this to 5 shows only records that happen 5 or more times to the linked relationship.)
    3. Show Ancestors (Off/On): When turned on, this shows entities that occur before the root in the process. When off, only what happens after the root is displayed.
    4. Show Entities (Off/On): Enables the display of additional related records or entities linked to the process. Turning this off limits the view to essential relationships.
    5. Show Custom (Off/On): When enabled, includes custom-defined data relationships in the process view. Useful for highlighting organization-specific logic.
    6. Allow Multiple Parents (Off/On): Allows a single entity to be linked to more than one parent. When off, each entity is restricted to a single parent in the process flow.
  2. After selecting your filter options, click the Update button to refresh the Process Tracker and apply your filter selections.
  3. Now, select the record relationships you want to track and view in the application.
    1. Purple indicates the record is selected.
    2. Grey indicates the record is unselected.
  4. After making your selections, click Track in the bottom-right corner of the tracker panel to apply your changes.
    A confirmation modal will appear, click Track again to confirm and proceed.
Proceed Processing Events:

To update record relationships after setting up your process:

  1. Click the Process Events button.
  2. From the dropdown, select Update Pathways to proceed and refresh the related record connections. 
Understanding the Metrics
  • Process: Displays the root name of the process. 
  • Records Tracked: Shows the number of unique records being tracked for this process.
  • Total Record Instances: Indicates the combined total number of record occurrences. 

5. Import Milestones

Purpose

The purpose of this feature is to simplify the process of adding critical milestones by offering curated suggestions based on tracked records. This helps analysts quickly identify and import important events needed for accurate and comprehensive process analysis without manual searching or guesswork.

Overview

The Import Milestones from Catalog feature allows users to browse and select from a list of suggested milestones associated with tracked records. It provides key details like milestone name, record type, event type, and frequency of occurrence to help users efficiently import relevant milestones for analysis.

Who Can Access the Import Milestones Blade
  • Tenant Admins 
  • Chassi Admins
  • Viewers (View-only)
How to Use It

Access the Milestones Panel

  1. From the sidebar menu, click on the Tenant name to expand the submenu, then select Milestones to open the Manage Milestones blade.
  2. Click Import from Catalog.
  3. Select the suggested milestones related to your tracked records and click Import Selected.
  1. A confirmation modal will appear: “Are you sure you want to upload (X) milestones?”, click Import to proceed.
  2. The selected milestones will appear as “Staged for Processing.”
  3. Process Milestones: To begin processing events and import the selected milestones:
    1. Click the Process Events button.
    2. From the dropdown, select Update Pathways.

This will begin processing all relevant events and include the selected milestones in the pathway analysis.

Manually Add a Milestone (if needed)
  1. Click “Create New Milestone.”
  2. Fill out the required fields:
    1. Name
    2. Record Type
    3. Milestone Timestamp (choose Timestamp of Field Change or New Value of Field)
    4. Date Format
    5. Expression
    6. Priority
    7. Finalize and Apply Milestones
       Once all desired milestones have been imported or created, click “Process Events”, then “Update Pathways” to apply the changes.
Understanding the Metrics
  • Milestone: Name of the event being tracked (i.e. Sales Order Created, Invoice Paid in Full)
  • Type: The record type the milestone is based on (i.e. Sales Order, [SF] Account Created)
  • Expression: Logic used to detect the milestone, often based on field changes. 
  • Record Count: Number of unique records where the milestone occurred. 
  • Occurrences: Total times the milestone event happened. 
  • Errors: Number of errors detected during milestone processing. 
  • Status: Indicates if the milestone has been successfully processed (i.e. Live) 
  • Updated Date: Last time the milestone definition was updated. 
  • Updated By: User who last modified the milestone. 
  • Visibility: Shows whether the milestone is visible throughout the application (i.e. Visible or Hidden)

6. Console

Purpose

The purpose of the Console is to streamline client management by giving administrators a single, easy-to-use platform to manage workflows, sensors, and expedite system changes, using one interface. 

Overview

The Console is a centralized interface that allows administrators to manage all client-specific settings in one place. It provides tools to initiate new data configurations, such as adding tracked records and relationships, and sends these configurations to the installed bundle (e.g., NetSuite). Users can also run and monitor scripts in real time, and access execution logs and scheduled script statuses.

Who Can Access It
  • Tenant Admins 
  • Chassi Admins
How to Use It
  1. From the sidebar menu, click on the Tenant name to expand the submenu, then select Console to open the Console blade.
  2. Click the Update Configuration button to open the configuration modal. Here you will enter key information needed to connect your application to the NetSuite sensors, including:
    • Rewind Date: The date from which sensors begin tracking historical events.
    • Authentication & Keys: Tokens and keys required for authorization.
  1. The Send button includes important actions accessible via a dropdown menu:
    • Process Changes: Starts processing recent updates to workflows or sensors.
    • Get Config: Retrieves the current system configuration.
    • Analyze Model: Runs an analysis of the data model to find issues or areas for optimization.
  1. Queue Status Graph: Shows backlog or processing issues within event queues.
    • X-axis: Displays event queues:
      • Dead-Letter Queue: Contains events that failed processing and need manual attention.
      • NetSuite Change Log: Tracks changes made in NetSuite requiring processing.
      • AWS Queue: Manages events routed through AWS services.
      • Unprocessed Database Events: Events recorded but not yet processed.
    • Y-axis: Number of events in each queue.
  2. Events Processed Graph: Monitors daily event throughput to track system performance over time.
    • X-axis: Date when events were processed.
    • Y-axis: Number of events processed per day.
  3. Script Chains Table:  Provides visibility into ongoing and completed processes.
    • Lists Active Script Chains (currently running workflows)
    • Completed Script Chains (workflows that have finished).

7. Data Sandbox

Purpose

The Data Sandbox simplifies the export of multi-record data by eliminating the need for manual joins in external tools like Excel. Users can create focused, exportable datasets across interconnected records to support deeper analysis and reporting needs.

Overview

The Data Sandbox is a customizable export tool that allows users to build tailored datasets by selecting a root record, defining relationships, and choosing specific fields or milestones. It’s designed to give users greater flexibility in pulling multi-record data needed for reports.

Key Benefits
  • Export clean, structured data without external tools
  • Customize fields and milestones for root and related records
  • Build complex exports that reflect real-world relationships
  • Filter data before exporting to reduce post-processing work
Who Can Access the Data Sandbox
  • Tenant Admins 
  • Chassi Admins
  • Viewers
How to Use It
  1. On the Dashboard page, navigate to the Data Sandbox module.
  2. Click + Data Sandbox to create a new sandbox query.
  3. Click Select Root Entity and choose the record type you want as the root of the query (e.g., Sales Order) and click Select.
  1. Set the Minimum Instances value according to your criteria.
  2. Click on the selected record to choose the Milestones and any Fields you want to include in the export. 
  3. Configure the toggles (only applicable to Chassi Admins)
    • Save to Studio: When enabled, it saves the report to the Reporting Studio (accessible only by Chassi admins).
    • Scheduled: When enabled, schedules the query to update automatically on a daily basis.
       Typically, both toggles are set to Off unless you want to save the report or automate updates.
  4. Click “Export” and navigate to the Download Manager to access export.
Understanding the Metrics 
  • Root: The primary record type selected as the starting point for the query (e.g. Sales Order)
  • Joined Records: Lists the records connected to the root entity through defined relationships.  
  • Save to Studio: Indicates whether the query is saved to the reporting Studio (accessible only by Chassi Admins)
  • Export Status: Displays a status bar showing the progress of the export.

8. Work Analysis

Purpose

The purpose of Work Analysis is to help users identify areas within a workflow where manual intervention or rework frequently occurs. By quantifying field changes between specific milestones and tracking the users involved, users can uncover inefficiencies and target areas for automation or process improvement.

Overview

The Work Analysis module provides detailed visibility into field-level activity across tracked processes. By selecting specific record types and milestone ranges, users can analyze how often certain fields are changed, who is making the changes, and how frequently these edits occur across distinct records. This focused analysis helps surface patterns of manual work or rework that occur between defined process steps.

Who Can Access Work Analysis
  • Tenant Admins 
  • Chassi Admins
  • Viewers
How to Use It
  1. From the sidebar menu, select Work Analysis.
  2. Click + Create Your First Analysis.
  3. In the Type dropdown, select the record type you want to analyze (e.g., Sales Order, Invoice).
  4. Based on the selected type, the From and To milestone dropdowns will populate:
    • From: Select the starting milestone.
    • To: Select the ending milestone. 
      • These define the range of the workflow you want to analyze.
  5. Define the Time Frame: 
    • Select a customized date range or choose from the available drop-down options to specify the period for your analysis.
    • Beginning: The pathway date range begins using the ‘From’ milestone you selected.
    • Ending: The pathway 
  6. Includes: Pathways that include the listed milestones. 
  7. Excludes: Pathways that exclude the listed milestones.
  8. Created By: Records created by specific employees:
  9. Employees: Pathways involving one or more specified employees.
  10. Customers: Pathways involving one or more specified customers.
  11. Changes Filters:
    • Exclude changes with same old and new values
    • Exclude fields set on record creation
    • Reset Filters to clear all applied filters
Understanding the Metrics
  • Field Modifications: Total number of unique fields that were modified during the selected time frame (e.g., 44 fields).
  • Processed Timestamp: The date and time when the analysis was last processed (e.g., Processed 5/21/2025, 2:20:48 PM).
  • Records Modified: Number of records that had at least one field modification.
  • Modifications: Total number of individual field changes made across all records.
  • Average Modifications: The average number of modifications per modified record.

Contents

Assessments

Sectors

Resources

Company

Assessments
Who We Help
Platform
Partners
Start a Conversation