GoodData AnalyticsUse cases

Typical situations solved with GoodData: which data goes in, what the product does, and what you get.

Plant-to-boardroom KPIs

OEE, downtime and scrap are calculated differently by production, maintenance and finance.

Data in
MES and historian data (in the warehouse)
What it does
Metrics are defined once in the semantic layer; plant dashboards and the executive summary use the same definition.
Outcome
The meeting discusses what to do, not which number is right.

Multi-site comparison

Several plants make the same product, but each one’s report is built separately.

Data in
Per-plant data
What it does
A shared model in the parent workspace and one child workspace per plant, scoped with a workspace data filter.
Outcome
Adding a plant is as simple as adding a child workspace.

Analytics embedded in your product

An equipment maker wants to show customers machine performance inside its own portal.

Data in
Machine data (in the cloud)
What it does
Charts are embedded in the portal with the React SDK, and the workspace hierarchy separates each customer.
Outcome
Customers see their own data without leaving the application.

Asking questions in plain language

Shift supervisors want to ask “which line stopped most yesterday?” instead of hunting through dashboards.

Data in
Governed metrics and the data model
What it does
The assistant does not guess at tables; it uses the defined metrics and model, and the sources behind an answer are traceable.
Outcome
Answers with consistent numbers, without navigating dashboards.

Let’s take the first step with GoodData together

Tell us where you are and what you want to achieve, and we will outline the right scope and pilot plan. Our team replies within 24 hours.