Skip to content
Discuss a project

Software · 04 · Data, monitoring & dashboards

See what needs attention, and why.

We turn operational signals into clear views, useful alerts and decisions, without burying the people who use them in raw data.

Discuss your requirements View related projects
Operational dashboard for a pump stationA monitoring screen for Pump station 2. A data-quality bar shows the last sample time, the sample rate and the share of good-quality data. On the left, six assets are sorted by severity, with transfer pump P-101 in warning. The main chart shows P-101 discharge pressure over seven days with a warning limit at 4.5 bar and a high alarm at 5.0 bar; after a filter change on 12 October the pressure rises steadily and crosses the warning limit. Below are a small layout of the station, from tank and strainer to two pumps, a pressure transmitter and an outlet valve, and a list of recent events.Pump station 2SITE NORTH · OPERATIONS24 h7 d30 dLAST SAMPLESAMPLE RATEDATA QUALITY09:42:10 · 2 s ago1 s raw · 1 min avg99.6 % goodASSETS · 6sorted by severityP-101Transfer pump4.6 barWarningF-201Suction strainerΔP 0.4 barWatchC-301Air compressor7.1 barRunningLT-501Storage tank71 %NormalFV-401Outlet valve62 % openNormalP-102Transfer pump—StandbyTHIS SHIFTOpen alerts1Open work orders2Next reportFri 08:00P-101 · Discharge pressurePT-101 · bar · 1-min average · last 7 days4.6barAbove warning since 14 Oct3.04.04.55.0HIGH ALARM 5.0WARNING 4.5Filter change · WO-118Pressure rose after filter change+0.6 bar since 12 Oct, still climbing9 Oct10 Oct11 Oct12 Oct13 Oct14 Oct15 OctLAYOUT · PUMP STATION 2PT101LT-501F-201P-101P-102FV-401OUTTap an asset to open its trendEVENTS · P-101, F-20114 OCT 21:1012 OCT 10:0511 OCT 16:40PT-101 above 4.5 bar (warning)F-201 element changed · WO-118P-102 set to standbyAcknowledgeOpen WO-118 → P-101 discharge pressure over seven days, rising above the 4.5 bar warning limit after a filter changeP-101 · Discharge pressurePT-101 · bar · last 7 days4.6HIGH 5.0WARN 4.5Filter changeRose after the change+0.6 bar since 12 Oct9 Oct12 Oct15 Oct

Last sample 09:42:10 · 1 s rate · 99.6 % good

Illustrative dashboard · all values, tags and events are examples

From sensor to screen

What happens to one reading before it reaches the chart.

  1. 01 · TagPT-101 · 4–20 mANamed, scaled to 0–10 bar and given a unit once.
  2. 02 · Sample1 s · time · qualityRaw values kept with their health flag.
  3. 03 · Aggregate1 min · min / avg / maxStored for trends and reports.
  4. 04 · Alert> 4.5 bar for 2 minSent to a named role with a next step.

Questions a good dashboard answers

We design screens around the questions people ask.

Before choosing charts, we write down what each user needs to decide. If a panel does not help answer one of these questions, it does not go on the screen.

  1. Q 01

    Which equipment needs attention right now?

    On screen

    Assets sorted by severity, not by tag number, with the reason shown next to each state.

  2. Q 02

    Is this reading normal for this asset?

    On screen

    Trends drawn against the asset’s own limits and recent history, so a number has context.

  3. Q 03

    What changed before the alarm?

    On screen

    Maintenance, setpoint changes and operator actions on the same timeline as the data.

  4. Q 04

    Can I trust the number on the screen?

    On screen

    Last sample time, sample rate and data-quality flags kept visible, so stale data is obvious.

  5. Q 05

    Who needs to know, and what should they do?

    On screen

    Alerts routed to a role with a suggested next step, and reports that replace manual spreadsheets.

Typical deliverables

What a project can include.

The exact package is agreed from your context, risk, timeline and responsibilities. Each part ends with something you can review.

DeliverableWhat it coversYou receive
01Data-source and event mappingWhere each signal and record comes from, its units, sample rate, owner and the events that matter to operations.
  • Tag and source register
  • Event and alarm list
02Operational dashboardsScreens for each role, from overview to single asset, designed around the decisions those people make.
  • Screen designs per role
  • Working dashboards
03Equipment and process monitoringCollection, storage and trending of equipment and process data, with data-quality checks built in.
  • Data pipeline and storage
  • Retention and quality rules
04Reporting and alert workflowsScheduled reports and alert rules with delays, escalation and a clear owner for each alert.
  • Report templates
  • Alert rules and routing table

A good fit for

Where a monitoring project helps most.

  • Operations lacking a shared view of performance
  • Connected equipment producing useful signals
  • Teams replacing manual reporting

What helps us start

Bring what you have. Gaps are normal.

  • A list of equipment or an asset register, even a spreadsheet
  • Where the data lives today: PLCs, meters, databases or files
  • Who will use the screens and what they decide
  • Existing alarm limits or reports you want to replace

Start a conversation

Talk through your data, monitoring & dashboards requirements.

Tell us which signals you have and which decisions they should support. We will come back with what we would map, store and show first.

Discuss your requirements

Inquiries are routed to the relevant practice lead.