Packaging fleet data, finally turning into service revenue.
For OEMs building flow-wrappers, case packers, palletisers, VFFS / HFFS and end-of-line equipment. We turn your installed base into a structured service business, a customer portal your FMCG customers actually log into, and aftermarket forecasting that stops being gut-feel.
See sealing-jaw drift and vacuum-cup wear days before the line stops, and send the right engineer with the right part the first time.
Uptime guarantees and SLA reporting your FMCG customers pay for, tiered into a subscription instead of free firefighting.
Your customers log into your portal, under your name, for live OEE, open alarms and service ETA. Not a spreadsheet you mail once a quarter.
How we work in your packaging fleet.
Four steps from your installed base to a service business that scales. You decide which steps we do, and which stay with your team.
Connect your fleet and your service desk
We integrate with your IXON, Secomea or Beijer CloudVPN deployment without touching router or device-template configuration. Plus your service ticketing tool (ServiceNow, Salesforce, in-house), so reason codes flow into the workflow you already have.
Build the data layer around recipe and site
Medallion architecture on Azure with recipe, customer site and machine archetype as first-class dimensions. Bronze, Silver, Gold. Hosted in our tenant or yours, depending on your customers' data-residency requirements.
Stand up the customer-facing portal
Power BI Embedded under your brand, your domain, your SSO. Multi-tenant by design: customer A sees A, customer B sees B, you see all sites consolidated. Service ETA, alarms, historic uptime, recipe-level performance, in your portal.
Turn historic service tickets into reason codes
We mine your historic tickets for recurring patterns: sealing-jaw drift, vacuum-cup wear, dose drift, heater fatigue. The Activate layer proposes the matching reason code and dispatch action. Your engineer validates before anyone drives anywhere.
Full technical breakdown of every building block on what we build →
Three modules. One foundation.
The same three modules we build across machine-builder fleets, on one Medallion architecture. Each can start independently and expand over time. The framing and defaults here are tuned for packaging.
A white-label portal your FMCG customers log into to see line performance, open alarms, service ETAs and historic uptime. Embedded under your brand, your domain, your authentication. Customers see your portal, not StriData.
Discover Customer Service Portal →Sealing temperature drift, jaw wear, film tension anomalies, glue head pressure dips. The patterns that predict the next service ticket. Reason codes derived from your historic data, validated by your service engineer before action.
Discover Service Intelligence →Comparable OEE, changeover and downtime across flow-wrappers, case packers, palletisers and end-of-line equipment in one fleet view. Benchmark customer sites anonymously to feed your own engineering and product roadmap.
Discover Fleet Performance →
The data was always there. Making it usable was the hard part.
We built StriData to fix exactly that for packaging OEMs: a reusable data foundation for service revenue, customer uptime and aftermarket insight, on top of your existing connectivity stack. Your team stays in control.
Published case: TMI.
A packaging machine builder we partnered with through IXON. Published, named, and quotable. The strongest proof we have in this sector.
Company snapshot
- Sector
- Packaging machine builder (OEM)
- Lines built
- Bagging, palletising and stretch-wrapping
- Industries served
- Food, agro-feed, construction & mining, chemicals & petrochemicals, recycling
- Reach
- 1,500+ machines deployed across 40 countries
- How we connected
- IXON Technology Alliance Partner channel
What we built together
TMI's customers were asking for machine performance data and a single source of truth combining IXON machine data with their own ERP and CRM. We built a no-code Power BI connector that turned IXON data into a customer-facing analytics layer, embedded inside TMI's own service portfolio.
Request your packaging Quick Scan.
A focused look at your fleet and service data. In about two weeks you get a concrete plan, no obligation, no platform commitment.
- What's worth measuring across your line types
- A data-foundation outline, hosted in your tenant or ours
- The first portal or module that pays off fastest
Questions packaging OEMs ask us.
We already have IXON (or Secomea, or CloudVPN) deployed across our fleet. Do you replace it?
No. We integrate. Routers and device templates stay with your existing connectivity partner. We add the data foundation, reporting and Activate layer on top. We are an IXON Partner and work alongside Secomea and Beijer CloudVPN deployments routinely. We don't touch router or device template configuration; that stays where it belongs.
Can the customer portal be embedded under our white-label, our domain, our authentication?
Yes. We build the portal on Power BI Embedded under your domain, with your branding and your single sign-on. Your customers see your portal, not StriData. Multi-tenant by design: customer A sees only customer A's data, you see all sites consolidated.
Do you replace our service ticketing system?
No. We integrate with what you have, whether that's ServiceNow, Salesforce Service Cloud, an in-house system, or a combination. Reason codes and proposed actions flow into your existing ticket tool. Your service engineers keep working where they already work today.
We have a recipe library with 200+ variants. How does that work?
We treat recipe as a dimension in the data model. Changeover times, OEE, alarms and material consumption are sliceable per recipe per customer site. Your engineering team owns the recipe definitions; we hook into them. Adding recipes later doesn't require platform changes.
Our customers are split across multiple countries with different data residency rules. Can the platform handle that?
Yes. The Medallion foundation runs on Azure and can be deployed per region where required. Hosted in a StriData tenant for speed of operation, or in your own tenant or per-customer tenant if data residency demands it. We discuss the trade-off in the Quick Scan.