Cloud demo for clarity. Physical trial for proof.
In manufacturing, these two motions should never be confused. A demo proves that the system is understandable. A trial proves that it improves your operation.
The Difference
Two entry points. Two different jobs to be done.
The strongest industrial software vendors tend to use both. The mistake is treating a cloud walkthrough as if it were plant-level proof, or treating a pilot as if it were only a product tour.
Cloud-based functional evaluation
The cloud demo is designed to help stakeholders understand the product: operator workflows, dashboards, alerts, escalation paths, reporting, and how the modules fit together.
Cloud-based access with a ready-to-use environment
Preloaded production, downtime, and quality scenarios
Operator, supervisor, and management views in one walkthrough
No on-site installation, no hardware, and no machine wiring
Fast validation of workflows, roles, dashboards, and reports
Best for alignment across operations, IT, quality, and leadership
On-site validation with physical modules
The trial is a physical deployment motion: basic IIoT, selected modules, and real production data from your plant. It is the stage where assumptions are replaced with measured losses and verified opportunities.
Physical installation of modules and the basic IIoT layer
Connection to selected real machines, stations, or one pilot line
Operator screens, status capture, downtime input, and quality events
Measured baseline for OEE, stops, defects, and response time
Real plant data instead of simulated or sample data
Best for proving operational value and defining scale-up priorities
Side-by-Side
What changes between the two motions
The simplest way to explain the offer is to show exactly what the customer gets and what kind of evidence each step creates.
| Topic | Demo | Trial |
|---|---|---|
| Purpose | Validate workflows, usability, dashboards, roles, and reporting logic. | Validate operational impact with real devices, operators, and production data. |
| Environment | Cloud environment with sample or simulated data. | On-site installation with physical modules and basic IIoT connectivity. |
| Speed to start | Fastest entry point. | Requires planning, install window, and pilot scope definition. |
| Best for | Stakeholder alignment and fast product understanding. | Business-case validation, baseline creation, and scale-up decisions. |
| Evidence level | Functional proof. | Operational proof. |
| Typical output | Clear view of what the system does and which roles benefit from it. | Measured losses, first improvements, and a rollout recommendation based on plant data. |
Competitive Verification
How this maps to common market approaches
Validated against publicly visible motions used across industrial cloud platforms, IIoT trials, and machine monitoring pilot programs.
Simulated cloud environments
Common in Industrial AI and IIoT platforms. Great for showing features fast, but they do not prove what happens on your own assets and shifts.
IRIS uses the cloud demo for product understanding, not as a substitute for operational proof.
Self-install SaaS trials
Popular in machine monitoring vendors. Fast to start, but often optimized for a narrow slice such as machine data or OEE visibility.
IRIS positions the trial around a broader execution loop: operator actions, quality capture, downtime reasons, and live production context.
Consulting-heavy pilots
Useful for complex plants, but can feel slow, expensive, and hard to compare with a simple software demo motion.
IRIS splits the journey clearly: demo for clarity, trial for proof, scale for rollout. This makes evaluation easier for both business and technical stakeholders.
Decision Guide
When to use which path
The right entry point depends on what your team needs to validate first.
Choose demo if you need fast understanding
Use the cloud demo when the team needs to see the product logic, user flows, and reporting structure before any technical work starts.
Choose trial if you need proof from your own line
Use the on-site trial when internal approval depends on real machine data, real operators, and a measured operational baseline.
Use both if you want the strongest path to rollout
The cleanest journey is often demo first for alignment, then trial for validation, then scale based on measured bottlenecks and quick wins.
Start in the cloud. Prove it on the floor. Scale with confidence.
That sequence is easier to understand internally, easier to defend commercially, and stronger against market alternatives that only offer one half of the evaluation journey.
Competitive framing informed by public materials from industrial cloud, IIoT trial, and machine monitoring vendors that separate simulated access from operational validation in different ways.