Layout View¶
Introduction¶
Layout View is a customizable dashboard view type. It lets you assemble your own set of KPI, chart, gauge, status, and table cards, choose exactly what each one shows, and arrange them freely on a grid — without needing any technical setup. It's the view type to use when the built-in pages don't show data in quite the layout you want.
Key Features¶
- Add Component: Build a dashboard card by card — a KPI (a single headline number), a Chart (a full graph over time), a Gauge, a Status Tile (a machine, line, or parameter's current state), a Status Timeline (how a state changed over time), or a Table (a ranked list)
- Multiple data sources: Pull cards from Batch Tracking (production batches, lines, process metrics), EMS (energy consumption, demand, active power, power factor, cost), a single Parameter (a live or historical reading from any machine), a Machine (status or performance metrics), a Line (run status, output, rejection, downtime), a Manufacturing Logbook KPI, Parameter Health (a monitored parameter's current status, health history, or compliance), or Batch × Line Metrics (a wide table comparing many metrics across batches)
- Drag and resize: Freely rearrange and resize cards on the grid to build the layout you want
- Edit anytime: Change a card's title, data source, or display style without recreating it
- Optional targets: Set a reference value on a card (for example, a demand limit) — values on the wrong side of it are flagged
- Click-through: Some cards support clicking a value or chart point to jump to the underlying batch, line, incomer, or section
Getting Started¶
- Create a new view and choose Layout View as the view type (requires engineer access).
- Click Add Component (the + button).
- Choose a Module — the part of the platform this card pulls data from (Batch Tracking, EMS, Parameter, Machine, Line, Manufacturing Logbook KPI, Parameter Health, or Batch × Line Metrics).
- Fill in the data source fields — these change depending on the module you picked (see below).
- Where it applies, choose how readings combine (Aggregation), what each point on the chart represents (Group by), and how much history to include (Time range). Some modules — or specific metrics within them, like a live status — skip some or all of these, and the form only shows what's relevant.
- Choose the Type of card (KPI, Chart, Gauge, Status Tile, Status Timeline, or Table). Which types are available depends on the module, and for some modules, the metric you picked — Enture pre-selects a sensible one for you.
- For charts, pick a chart style (line, bar, or area).
- Optionally set a Target — a reference value shown on the card.
- Click Add component. Drag the card to reposition it, or drag its corner to resize it.
To edit or remove a card later, use the menu on the card itself.
Data sources¶
Batch Tracking¶
Tracks a metric from a production process — pick the Process, the specific Metric, and optionally narrow it to one Line. Time ranges can be a number of recent batches (e.g. last 30 batches) or a calendar period.
EMS¶
Tracks an energy metric from the EMS application:
| Metric | What it shows |
|---|---|
| Energy Consumption | Energy used (kWh), summed over the period |
| Demand (Peak/Max) | Peak demand (kW or kVA, depending on your organisation's demand unit) |
| Active Power | Active power draw (kW) |
| Power Factor | Power factor (a ratio, not summable — see note below) |
| Cost | Energy cost for the period, in your organisation's currency |
For each metric, choose a Scope:
- Organisation-wide — every configured incomer
- Incomer Type — all incomers of one source (EB, DG, Solar, or Wind)
- Specific Incomer — a single meter
- Section — a utilization section (Energy Consumption only — the other metrics aren't tracked per section)
Why some options are missing
Demand, Active Power, and Power Factor are instantaneous readings, not totals — adding them up over a period doesn't produce a meaningful number, so Sum isn't offered as an aggregation for these metrics. Energy Consumption and Cost are totals, so summing them is exactly what you'd want, and remains available.
Adding an EMS dashboard to the EMS app
Once you've built a dashboard with EMS cards, you can attach it to the EMS application itself so it appears as a tab under EMS → Views. See EMS Configuration → Views Setup.
Parameter¶
Tracks a single reading from any machine — pick the Workspace, then the Machine, then the specific Parameter.
Choose a Data mode:
- Live — the card always shows the parameter's current value, updating in real time.
- Historical — the card shows a value or trend built from past readings over the Time range you choose.
For Historical cards, choose a Data source:
| Data source | What it shows |
|---|---|
| Timeseries | The raw readings themselves, plotted or aggregated over the time range. |
| Daily aggregate | Pre-calculated daily totals — pick which value to show (e.g. Usage, Average, Minimum, Maximum, Start Value, End Value, and others). |
| Shift-wise aggregate | Totals calculated per production Shift — pick the shift, then which value to show (Usage, Minimum, Maximum, Start Value, or End Value). |
When to use Daily or Shift-wise instead of Timeseries
Daily and Shift-wise aggregates are pre-calculated once per day or per shift, so they're a faster, steadier way to show totals like daily energy usage or a shift's output than plotting every raw reading. Use Timeseries when you want to see the actual reading-by-reading trend instead.
Machine¶
Tracks a machine's live status or one of its performance metrics. Pick a Metric:
| Metric | Shown as | What it shows |
|---|---|---|
| Current Status (live) | Status Tile | The machine's live status, updating in real time |
| Status Timeline | Status Timeline | How its status changed over the time range |
| Uptime % | KPI, Chart, or Table | Share of time spent running |
| Total Downtime | KPI, Chart, or Table | Downtime, in hours, over the period |
| Energy Consumed | KPI, Chart, or Table | Energy used, in kWh, over the period |
| Running Hours | KPI, Chart, or Table | Hours spent running over the period |
Then choose a Scope:
- Single machine — the card covers exactly one machine. Required for Current Status and Status Timeline — a status tile or timeline can only ever describe one machine at a time.
- Workspace (all machines) — every machine in a workspace, as a rollup (one point per machine on a chart or table). Available for the four performance metrics only.
- Process (all machines) — the same rollup, scoped to a process instead of a workspace.
Status metrics have no time range
Current Status is always live and Status Timeline always covers the window you choose — neither uses Aggregation or Group by, since there's nothing to combine.
Line¶
Tracks a production line's status or run performance. Pick the Metric, then the Process, then the Line itself.
| Metric | Shown as | What it shows |
|---|---|---|
| Current Status | Status Tile | Whether the line currently has a run in progress — checked once when the dashboard loads, not continuously live |
| Run / Downtime Timeline | Status Timeline | Runs and downtime over the time range |
| Run Output | KPI, Chart, or Table | Units produced |
| Rejection % | KPI, Chart, or Table | Rejected units as a share of total output |
| Run Duration | KPI, Chart, or Table | Average length of a run |
| Downtime | KPI, Chart, or Table | Downtime, in hours |
Comparing every line of a process at once
Run Output, Rejection %, and Downtime can be shown as a Chart or Table for All lines of the process side by side (one point per line), instead of picking a single line — useful for spotting which line is under-performing. Run Duration and the two status-based metrics always describe one specific line.
Manufacturing Logbook KPI¶
Tracks one or more KPIs defined on a manufacturing logbook. Pick the Logbook, then the Table the KPIs were defined on (this narrows which KPIs are available), then the KPI(s) themselves.
Some KPIs are defined with a grouping — for example, one figure per product on the same logbook table. Two toggles control how that grouping shows up on the card, and they behave differently depending on whether you're building a Chart or a Table:
Chart:
- Normally trends a single KPI, with its groups combined into one line.
- Show one line per group — splits that single KPI into one line per group instead of combining them.
- Date-wise — compares up to 3 KPIs instead of one, each as its own combined line. Turns off "Show one line per group" — the two can't be used together.
Table:
- Normally shows one row per group, with each KPI you picked as a column.
- Date-wise — flips this around: one row per date instead, for a single KPI, with one column per group.
The KPI list depends on the table
A KPI is defined against one specific table on the logbook, so changing the Table clears your KPI selection — pick the table before the KPI(s).
Parameter Health¶
Tracks a monitored parameter's health, not its raw reading — how it's graded against the range or value rules you've configured for it. See Parameter Health for what that means.
Choose a Metric:
| Metric | Shown as | What it shows |
|---|---|---|
| Current status | Status Tile | The parameter's current state — Healthy, Unhealthy, Critical, Offline, or Unknown |
| Health timeline | Status Timeline | How its state changed over the time range |
| Time in range | KPI | Compliance percentage over the time range |
| Excursions | KPI | Count of deviations opened in the time range |
| Time not reporting | KPI | How much of the time range its edge device was unreachable |
| Parameters needing attention | Table | The worst-off monitored parameters across the whole organisation, worst first — no parameter to pick, this one is fleet-wide |
Every metric except Parameters needing attention needs a specific Parameter — only parameters that already have health configured appear in the list.
Only shows parameters with health already set up
A parameter has to be monitored before it can appear on a dashboard card. See Setting up Parameter Health to configure one.
Batch × Line Metrics¶
Builds a wide comparison table with one row per batch and a column for each metric you choose, so you can review a whole run of batches side by side instead of opening each one's journey separately.
This module always produces a Table — KPI, Chart, and Gauge aren't offered, because a row made up of many unrelated metrics has no single headline number or trend to plot.
Every table begins with two columns, Batch ID and Start, followed by your chosen metrics arranged into groups under a spanning heading. The Group by process switch decides what those groups are:
| Group by process | Column groups are… | Metrics are chosen… | Best for |
|---|---|---|---|
| Off (default) | One per Line you pick | Per line | Following a batch through the sequential stages of a flow — the lines you pick can belong to different processes (e.g. Milling → Brewing → Distillation) |
| On | One per Process you pick | Once per process | A process with many interchangeable lines (e.g. ten fermenters) — every line of that process counts automatically, so you don't pick them one by one |
With the switch on, each process group also gains a Line column naming whichever line that particular batch actually ran.
Choosing what appears:
- Use the Lines (or Processes) selector to choose which ones become column groups — Select all and Clear all are there for long lists.
- Each one you select gets its own card below, with a metric selector listing the metrics available for that process. Pick as many as you want per group.
- Use the up/down arrows on each card to reorder them — this is also the order the groups appear in the table.
Empty cells are expected
A batch is listed if it touched any of your selected lines or processes. Cells belonging to a line or process that batch never visited are simply left blank — that's normal for a multi-stage flow where not every batch goes everywhere, not missing data.
When one batch ran more than one line of the same process
With Group by process on, a batch normally runs just one line of a process, and that line's own values are shown. In the less common case where a batch ran several lines of the same process, the Line column names all of them and each metric's value is combined across them — using the combination rule (average, sum, minimum, maximum, or last) already configured for that metric on its process template, so the result matches how that metric is summarised everywhere else.
Why there's no 'last 30 batches' option here
Time ranges for this module are calendar periods only (last 7 days through year-to-date). A batch campaign usually spans several days and more than one line, so a batch count would be ambiguous across the multiple lines or processes a single card can cover.
Like other table cards, click a column heading to sort by it, and use Prev/Next at the foot of the card when there are more batches than fit on one page. Clicking any row opens that batch.