Your service, as a product your customers log into.
The Customer Service Portal gives your customers a branded view of their own machines: uptime, SLA progress, planned maintenance and alarm status. You stop sending service by email and start delivering it as a product, on the connectivity and data foundation you already run.
Same foundation as Fleet Performance · secured per customer with row-level security · delivered in your brand and domain.
See it in action.
A white-label Customer Service Portal, running on sample data. The same layout runs on your customer's machines, in your brand.
This is one example view, on synthetic data. On the same governed foundation we shape it to your machines, your KPIs and your brand, so a different layout is a configuration, not a rebuild.
You're looking at one view of it.
Everything here runs on the same governed data foundation. Build the views you need now, and the ones you need later, on top of it.
Fleet Performance
OEE, alarms and uptime for your team
Customer Service Portal
White-label, for your customers
Service Intelligence
Wear parts, stock & reorder
Your own view
Shaped to your KPIs, no rebuild
Built once, shaped to you. Because every view runs on one governed foundation, a different view, or a new one next year, is a configuration, not a rebuild.
Your service, as a product your customers log into.
At a glance: what's inside the Customer Service Portal, in your brand, and what it does for your service business.
Your customer's site at a glance
Site uptime, active alerts, open service items, next maintenance and SLA status, in one header that updates through the shift.
Service request status
Every open request on their machines, with status from open to resolved, mirrored read-only from your ticket system. New requests open a form or link straight into your system.
Early warnings before a line stops
Trend signals like vacuum drift, motor-current rise and cycle-time creep, each with an estimated time-to-threshold.
Planned maintenance & wear parts
Upcoming service on run-hours and calendar, plus wear-part life per machine, so a visit is scheduled before a part reaches end of life.
SLA performance, automatically reported
Uptime against the guarantee, incidents and response times, delivered as an automatic monthly report your customer can open any time.
Documents & spare parts
Manuals, certificates and the automatic SLA reports ready to download, plus the parts that fit their machines. Ordering deep-links into your own shop, so you keep stock, pricing and fulfilment.
How the Customer Service Portal works.
The same reusable foundation as Fleet Performance, with a customer-facing layer on top: each customer sees only their own machines, in your brand.
One foundation, three views. Fleet Performance for your team, the Customer Service Portal for your customers, Service Intelligence on top, no rebuild.
The people behind the portal.
StriData was built by industrial data practitioners who got tired of two things: dashboards no one acts on, and machine data that stays stuck in the gateway. We work where operational reality meets business outcomes, one foot in IT and one on the floor.
We build the foundation and the analytics on top of what you already run. We are honest about scope: we deliver the data and the portal, and we link out to your shop and ticket system rather than rebuild them.
“A service portal only works if it shows the customer something true. That starts with the data, not the design.”
Questions machine builders ask us.
What if this view isn't exactly what we need?
That's the point. What you see is one example. Because it runs on a governed data foundation, a different view is a configuration, not a rebuild: we reshape the screens, KPIs and layout to your machines and your customers without touching the plumbing underneath. The modules show what's possible; your version is shaped in the Quick Scan.
Is it really our brand, or does it say StriData?
Your brand. The portal runs under your name, your colours and your own domain, with your contract and SLA terms. StriData is the data engine underneath, shown only as a small "powered by" line if you want it there at all.
How do you stop one customer seeing another's data?
Row-level security on a per-customer basis. Every customer login is mapped to its own machines and contract, and the filtering runs in the data model, not the front end. We treat tenant isolation as a hard release gate, tested with separate accounts before go-live.
Can customers create tickets or order parts in it?
In the first version, yes, but lightly. Tickets and parts run through deep links into your existing ticket system and webshop, or a small embedded Power App where you have none. We do not rebuild your webshop or own your stock and invoicing. A fuller interactive layer is a later step, only if a paying customer needs it.
Do we need a separate platform, or does it run on Power BI?
It runs on the same Power BI and Azure foundation as Fleet Performance, embedded in your brand. That keeps the first version fast to deliver and cheap to maintain, with deep links and an optional Power App tile for the few interactive parts.
What does the customer actually see on day one?
Site uptime, active alerts with status, planned maintenance and wear-part life, and an automatic monthly SLA report, in your brand. The richer service and parts features layer on from there.