Question 1

Can trex Cloud monitor my machines?

Accepted Answer

Yes. trex Cloud can monitor your machines in real time by collecting operational data from PLCs, sensors, and industrial systems and securely transferring it to the cloud for dashboards, reports, and analytics.
Live monitoring typically includes

Machine status (Running / Stopped / Idle / Alarm)
Production counts (actual vs target)
Cycle time & performance trends
Alarms and stop reasons
KPIs such as OEE, downtime, performance loss

Outcome

Faster response to issues
Better coordination acros

Question 2

What information do you need from us?

Accepted Answer

To connect your machines quickly and reliably, we typically need the following information:
Machine & connectivity details

Machine / PLC brand and model
Supported protocol (OPC UA/DA, Modbus TCP, Siemens S7, MQTT, Serial/RS-232, etc.)
IP address and port (if applicable)
Network access type (LAN / VLAN / VPN)

Data scope

Tag / signal list (what to read/write)
Required KPIs (OEE, downtime reasons, cycle time, energy, alarms, etc.)
Expected sampling rate (e.g., 1s, 5s, event-based)

Access &a

Question 3

What hardware is required?

Accepted Answer

In most cases, no additional hardware is required if your machines already support standard industrial connectivity (e.g., OPC UA, Modbus TCP, Siemens S7).
Depending on your setup, you may need

An industrial PC / Edge gateway on-site
trex Cloud Edge Device (optional) for local collection and forwarding
An OPC Server (e.g., Kepware) for OPC DA environments
Network requirements (switch port, firewall rules, VPN)

We always recommend the lightest setup that meets reliability and security needs.

Question 4

How do machines connect to trex Cloud?

Accepted Answer

Machines connect to trex Cloud through a secure data collection layer:

Data is collected locally from PLCs, sensors, OPC servers, or gateways
Data is normalized and buffered to prevent loss during short interruptions
Data is securely transmitted to trex Cloud (encrypted communication)
Dashboards and analytics provide real-time visibility and reporting

This architecture ensures high reliability without disrupting production networks.

Question 5

How long does setup take?

Accepted Answer

Setup time depends on machine count, protocol availability, and tag complexity. Typical timelines are:

Single machine: 1–2 hours
Small line (5–10 machines): ~1–2 days
Full factory rollout: 2–3+ weeks

Main factors affecting timeline

IT approvals (VPN/firewall)
Tag list readiness and validation
Access to PLC programs/documentation

We usually recommend starting with a pilot and scaling step-by-step.

Question 6

Do you provide onboarding?

Accepted Answer

Yes. We provide onboarding to ensure your team can start using trex Cloud effectively from day one.
Onboarding typically includes

System setup guidance (sites, lines, machines)
KPI definitions (OEE, downtime, cycle time, energy, etc.)
Dashboard configuration and best practices
User roles and access setup
Go-live checklist and validation

Our goal is a smooth rollout with fast adoption across teams.

Question 7

Can we brand trex Cloud?

Accepted Answer

Yes. trex Cloud supports branding options depending on your subscription and deployment model.
Branding options may include

Company logo and visual identity elements
Custom colors (where applicable)
Custom domain (optional / enterprise)
Customer-specific dashboards and naming conventions

If you have a corporate brand guideline, we can align the UI accordingly.

Question 8

Do you support remote assistance?

Accepted Answer

Yes. We provide remote assistance for troubleshooting, configuration, and operational support.
Remote support can cover

Connectivity checks and diagnostics
Tag mapping and data validation
Dashboard and KPI tuning
Performance and reliability troubleshooting

Remote assistance reduces downtime and accelerates issue resolution.

Question 9

Is training included?

Accepted Answer

Training can be included as part of your onboarding or support package.
Training is typically delivered for

Operators (daily usage, stop reasons, basic dashboards)
Supervisors (shift monitoring, performance tracking)
Managers (KPIs, trends, decision dashboards)
Maintenance & quality teams (alarms, root cause workflows)

We can tailor training sessions based on your roles and use cases.

Question 10

Can we scale across sites?

Accepted Answer

Yes. trex Cloud is designed to scale from a single line to multiple factories and regions.
Scaling features

Multi-site structure (site / plant / line / machine)
Standardized KPI definitions across locations
Central dashboards for cross-site comparisons
Role-based access and governance

This enables consistent visibility and performance management across your organization.

Question 11

How is pricing determined?

Accepted Answer

Pricing is determined based on your scope and usage needs.
Typical pricing factors

Number of machines / lines / sites
Required modules (OEE, downtime, energy, analytics, etc.)
Data volume and collection frequency
Integrations and customization needs
Support level (standard vs advantage)

We can provide a clear proposal after a short discovery call.

Question 12

Is there a pilot option?

Accepted Answer

Yes. A pilot option is available to validate connectivity and business value before scaling.
Pilot typically includes

Limited number of machines (e.g., 1–5)
Core KPIs (status, downtime, OEE basics)
Initial dashboards and validation
Short implementation timeline

After the pilot, scaling to more machines is straightforward.

Question 13

Are integrations included?

Accepted Answer

Integrations depend on your package and the target systems.
Common integrations

PLCs and industrial protocols (OPC UA/DA, Modbus TCP, S7, MQTT)
ERP/MES data exchange (optional)
APIs for customer-specific data flows

We confirm integration scope and effort during the proposal phase.

Question 14

Is support included?

Accepted Answer

Yes. Support is included, with different service levels available.
Support may include

Monitoring and incident response
Remote troubleshooting
Configuration updates and tuning
Knowledge base and documentation

Enterprise options can include extended SLA and dedicated support channels.

Question 15

Can we customize features?

Accepted Answer

Yes. Feature customization is possible depending on requirements and roadmap alignment.
Customization options

Customer-specific dashboards and KPIs
Additional data points and calculations
Workflow and alerting logic
Integration connectors

We evaluate customization requests to ensure maintainability and scalability.

Frequently asked
questions

Implementation

Services

Pricing

Frequently asked questions

Implementation

Services

Pricing

Frequently asked
questions