Start Here

Catalyst Data: Getting Started

Start using Catalyst Data with a controlled example.

ProductCatalyst DataVerified version1.11.0ComponentComparison Studio, Connectors, Datasets, Embeds, Entities, Evidence Ledger, Export Studio, Indicators, Institutional Access, Instruments, Observations, Persistent Workspaces, Public API, Quality Rules, Questions, Refresh Operations, Review and Revision, Saved Queries, Sources, Units and MethodsUpdatedJuly 17, 2026Reading time18 minutes
← Back to product guides

Catalyst Data · Getting Started

Governed entities, indicators, sources, evidence, questions, instruments, datasets, observations, quality, review, query, export, API, access, connectors, and refresh.

Audience: product users, administrators, reviewers, and integrators.

Last verified version: 1.11.0

Reading time: 18–30 minutes

Status: Published support documentation.

Purpose

This guide provides a safe first run of Catalyst Data. It explains the product role, the main feature surface, the synthetic demonstration dataset, how to recognize a valid result, and when human or expert review is required.

Capability overview

  • Entities
  • Indicators
  • Sources
  • Evidence Ledger
  • Questions
  • Instruments
  • Datasets
  • Observations
  • Units and Methods
  • Quality Rules
  • Review and Revision
  • Persistent Workspaces
  • Saved Queries
  • Comparison Studio
  • Export Studio
  • Public API
  • Embeds
  • Institutional Access
  • Connectors
  • Refresh Operations

Prerequisites

  • A modern supported browser or runtime
  • The current installed product and service version
  • A new demonstration workspace
  • No confidential, personal, credential, or production information
  • A named reviewer for consequential output

Sample data

This article uses a fictional Resilient Community Retrofit Program. The files contain one demonstration row for every documented feature, so each capability can be tested without private or production data.

Download CSV feature examples · Download JSON workspace example

Preview

# Feature Sample action Expected result Classification
1 Entities create the Community Center entity a stable entity ID synthetic-demo
2 Indicators define monthly electricity use with unit, method, and direction a reusable indicator definition synthetic-demo
3 Sources register utility data with publisher, URL, license, retrieval, and citation a provenance source record synthetic-demo
4 Evidence Ledger attach a bill and meter export to observations an evidence chain synthetic-demo
5 Questions state whether use fell after weather normalization a bounded analytical question synthetic-demo

The downloadable files include all 20 feature rows.

Procedure

  1. Open the product from its canonical Sustainable Catalyst page or administrative route.
  2. Confirm the product and backend version before creating data.
  3. Create a synthetic workspace named CATALYST-DATA-RETROFIT-001.
  4. Download the CSV and JSON examples supplied below.
  5. Use the feature matrix to complete the first six feature checkpoints.
  6. Save, close, and reopen the workspace to verify persistence.
  7. Inspect warnings, sources, units, permissions, and lifecycle state.
  8. Export or hand off only after completing the verification checklist.

1. Entities

Action: create the Community Center entity.

Expected result: a stable entity ID.

2. Indicators

Action: define monthly electricity use with unit, method, and direction.

Expected result: a reusable indicator definition.

3. Sources

Action: register utility data with publisher, URL, license, retrieval, and citation.

Expected result: a provenance source record.

4. Evidence Ledger

Action: attach a bill and meter export to observations.

Expected result: an evidence chain.

5. Questions

Action: state whether use fell after weather normalization.

Expected result: a bounded analytical question.

6. Instruments

Action: define a meter-reading or import instrument.

Expected result: a versioned collection instrument.

Expected output

  • a stable entity ID
  • a reusable indicator definition
  • a provenance source record
  • an evidence chain
  • a bounded analytical question
  • a versioned collection instrument
  • A saved record that reopens without data loss
  • An export or handoff that identifies product, version, artifact, source, and review state

Verification

  • Every sample value remains attached to its identifier and classification.
  • Warnings remain visible and are not silently treated as approval.
  • The saved workspace reopens in a clean session.
  • The product and version shown in output match the installed release.
  • Another reviewer can understand how the output was produced.

Responsible use

Governed data is not automatically true or fit for every purpose; preserve source rights, privacy, definitions, uncertainty, and review.

Scroll to Top