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), a Table (a ranked list), or an EMS Heatmap (energy use by hour or by day)
- 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 | Scopes offered |
|---|---|---|
| Energy consumption | Energy used (kWh), summed over the period | All four |
| Demand (peak / max) | Peak demand (kW or kVA, depending on your organisation's demand unit) | Organisation-wide, incomer type, specific incomer |
| Active power | Active power draw (kW) | Organisation-wide, incomer type, specific incomer |
| Power factor | Power factor (a ratio, not summable — see note below) | Organisation-wide, incomer type, specific incomer |
| Cost | Energy cost for the period, in your organisation's currency | Organisation-wide, incomer type, specific incomer |
| MD utilization % | Peak demand as a % of the sanctioned MD (KPI cards only) | Incomer type, specific incomer |
| MD headroom | Sanctioned MD minus peak demand (KPI cards only) | Incomer type, specific incomer |
| Peak active load (coincident) | The highest total active power (kW) of all incomers of one source at the same hour | Incomer type |
| Load factor | Average demand ÷ peak 15-minute demand, in % — see below | Incomer type, specific incomer |
For each metric, choose a Scope:
- Organisation-wide — every configured incomer
- Incomer type (EB / DG / Solar / Wind) — all incomers of one source
- Specific incomer — a single meter
- Section — a utilization section (Energy consumption only — the other metrics aren't tracked per section)
The Scope list only offers the scopes that make sense for the chosen metric.
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. Demand, MD utilization %, MD headroom and Peak active load are judged on the peak alone, so they offer Max only. Peak active load reads hourly data, so its time range is limited to 90 days, This month, Last month or Month before last.
Load factor cards¶
- What it is: average demand ÷ peak demand over 15-minute intervals, with all incomers in scope added together interval by interval — the same figure as the Load Factor card on the EMS Summary and the Load Factor Trend in Load & Demand.
- KPI cards show the load factor of the whole time range. This is not the average of the daily values; it is usually lower, because the range's peak is the highest of all its days. The trend underneath shows one value per day, week or month.
- Aggregation is fixed to Average, as the figure is always worked out from the readings themselves.
- Time range is limited to 90 days, This month, Last month or Month before last, as the metric reads 15-minute data.
- Scope is an incomer type or a specific incomer. There is no organisation-wide option: EB, DG and Solar in one ratio would not mean anything.
- Target: a target you set on the card is used. Without one, the card shows the Target Load Factor from EMS Settings.
Comparing with an earlier period¶
EMS cards have two extra time ranges: Last month and Month before last (whole calendar months). Three KPI cards side by side — This month, Last month, Month before last — give the Current / previous month / two months ago view.
An EMS KPI card can also show the same figure for an earlier period. Set Compare with:
| Compare with | The earlier period is |
|---|---|
| Previous period | The same length just before. Last 7 days is set against the 7 days before them. This month is set against the same days of last month (on the 12th, the 1st–12th of last month), so it shows whether this month is running ahead or behind. Last month is set against the month before it. Year to date is set against the same dates last year. |
| Same period last year | The same dates one year earlier. A whole month is set against the whole same month last year. |
The card then shows the earlier figure under the value, with the change next to it:
- The change is in %. For metrics that are already a percentage (Load factor, MD utilization %), it is in points instead (40 % → 44 % is shown as 4 pts, not 10 %).
- The arrow only says whether the figure went up or down. It isn't green or red, because higher isn't always better (more consumption, but a better power factor).
- The earlier figure is worked out with the same rules as the card itself — the same scope, aggregation and fallbacks.
- No data for the earlier period — the change isn't shown (for example, meters that were installed recently).
- Hover over the line to see the exact dates of the earlier period.
- Not available for the Projected cost card, which already compares itself with last month's actual cost, or for charts and tables.
Several series in one chart¶
On an over-time chart, the Series field draws one line or bar per item on the same card, instead of a single line:
| Series | Each line or bar is | Covers | Metrics |
|---|---|---|---|
| One per incomer type | one source — EB, DG, Solar, Wind | Organisation-wide | All chart metrics |
| One per incomer | one meter | Organisation-wide, or one incomer type | All except Peak active load |
| One per section | one utilization section | Organisation-wide | Energy consumption |
- Each series is worked out exactly as a card for that one item would be. For example, Load factor, one per incomer type shows each source's own coincident load factor, and Peak active load, one per incomer type shows each source's own peak hour. This is how to compare sources on one card, since those two metrics have no organisation-wide figure of their own.
- Cost across the organisation counts the paid sources (EB and DG) only, as the single-line cost card does.
- Stack the series (Energy consumption and Cost only) puts the bars or areas on top of each other, so each column's top is the total, like the consumption chart on the EMS Summary. It needs Bar or Area; the other metrics can't be stacked because peaks and ratios don't add up.
- Many items: up to 8 series are drawn. For Energy consumption and Cost, the 7 largest are kept and the rest are added together as Other. For the other metrics, a card with more than 8 items shows a message asking for a narrower scope — for example one incomer type instead of the whole organisation.
- Different units: if the series don't share a unit (for example Demand where one source has no demand meter and falls back to kW), the card leaves the axis without a unit and says so under the chart.
- Colours: one per incomer type uses each source's own colour, as on the EMS pages (EB blue, DG red, Solar amber, Wind green). Incomers and sections get colours that are none of the source colours, so a second EB meter isn't mistaken for Solar. Other is always grey.
- Click a name in the legend to hide or show that series. Points on a chart with several series don't open a page when clicked.
EMS tables¶
A Table card lists several metrics side by side, one row per item — for example every incomer with its consumption, cost, peak demand, power factor and load factor for the month.
- Choose Table as the card type.
- Rows — what each row is: One row per incomer type, One row per incomer or One row per section.
- Scope — which rows the table covers. One row per incomer can cover the whole organisation or the incomers of one incomer type; the other two always cover the whole organisation. A table of incomers across the organisation also shows each incomer's type.
- Columns — add up to 6 metrics, each with its own aggregation, and use the arrows to put them in order. A column only offers the metrics its rows can have: section rows have Energy consumption only, and incomer rows don't offer Peak active load.
- Group by and Time range apply to every column. Group by matters for an Average, Minimum or Maximum column: Energy consumption, Average grouped by day is the average daily consumption.
What the cells show:
- Each cell is the same figure a KPI card for that row and metric would show, with the same rules — a load factor column is each row's whole-period load factor, Demand is the peak, Cost uses your tariff.
- A load factor or Peak active load column limits the time range to 90 days, This month, Last month or Month before last, as on their own cards.
- An empty cell (—) means there's no data for that row. For example, a solar incomer has no cost, and MD utilization needs a sanctioned MD in EMS Settings.
- Different units: if one row's figure is in another unit (Demand falling back to kW for a source with no demand meter), that column shows the unit in each cell instead of in the heading.
- A note under the table names the rows whose figures came from a fallback or couldn't be worked out.
- Click a heading to sort, and click a row to open that incomer, incomer type or section on the EMS pages.
- A table has no target. Large tables are limited to 120 figures (rows × columns); a bigger one asks you to narrow the scope or drop a column.
EMS heatmaps¶
A Heatmap card shows energy consumption as a grid of shaded cells — the darker the cell, the more energy was used — like the heatmap on the EMS Summary.
- Choose Heatmap as the card type. The metric is always Energy consumption.
- Layout:
- Time of day — one row per hour, one column per day. Shows the daily load pattern: when the plant starts up, lunch breaks, night load. The time range can be up to a month: Last 7 days, Last 30 days, This month, Last month or Month before last.
- Calendar — one cell per day, a weekday per row and a week per column. Shows weekly patterns and holidays over a longer period, up to a year.
- Scope — the whole organisation, one incomer type, one incomer, or one section. A section counts each of its machines by its share, as on the Sections page.
What the card shows:
- Hover over a cell to see its date (and hour) and the energy used; the scale under the grid runs from the smallest to the largest cell.
- A card for one incomer type or one incomer is shaded in that source's colour (EB blue, DG red, Solar amber, Wind green); the others use your accent colour.
- On an incomer type card, click a cell to open its 15-minute breakdown — the same breakdown as on the EMS Summary heatmap. Cards for other scopes don't open one.
- Hours are your organisation's local time.
- A heatmap has no aggregation, grouping or target. If the card is smaller than the grid, it scrolls — resize the card to see it all.
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.