Confirm the production point, sensor signal, connectivity and installation needs before shipping.
02
Connect and configure
Use your phone to configure the device’s Wi-Fi connection. Set up the line, product rates, units and production schedule in skyTON.
03
Validate and learn
Compare counts and stops with your line records. Review the largest recorded losses and agree your first improvement.
Check before shipping
Will it work with your line?
The current monitoring device supports configurable PNP/NPN sensor connections. A short compatibility check helps establish the right setup for your production point.
Self-installation includes configuration; your sensor connection may still need wiring or technical assistance. We’ll confirm the installation requirements for your line.
Production point What you want to count or measure, and the unit of output.
Sensor signal Sensor model, PNP/NPN type and electrical specifications.
Connectivity Wi-Fi coverage and any site network restrictions.
Installation Available power, mounting location and who can make the sensor connection.
Production context Typical rates, shifts and planned production schedule.
Product walkthrough · Real skyTON screens
Three measures. A more useful production picture.
Explore availability, performance and quality, then see the actual downtime and quality reports below. The screenshots use demonstration data; select a screen to enlarge it.
A
Availability
How much of scheduled production time did the line run? Stops inside the production schedule count as lost time. Planned maintenance should be reflected by changing that schedule.
P
Performance
How does measured output compare with the configured production rate during running time? Review product rates and units so the comparison means something for your line.
Q
Quality
How much output was good production? Record scrap against the production batch and review its contribution to quality for the selected reporting period.
Downtime & production visibility
Move from a low number to a useful question.
Review running and stopped time, classify downtime reasons and examine recurring events. Filter reports by line and period to focus the discussion on the work that matters.
Downtime duration, event counts and reason breakdowns
Stop classification and splitting for more accurate context
CSV exports for further review
Actual downtime report · Demonstration data
Actual quality report · Demonstration data
Batches, shifts & reporting
Keep the context behind the result.
Production batches retain their play, pause and stop history. Batch scrap is allocated across overlapping production run time when a report covers only part of the batch; it is an allocation, rather than an exact timestamp for each rejected unit.
Use production schedules, shift definitions and selected date ranges to review a line or reporting period. OEE trends and executive reports support regular production reviews.
Missing telemetry is flagged in reports. An incomplete measurement window should prompt a data check before a performance conclusion.
Make the information useful
From the shift review to the next action.
↗Bring the team into the conversation.
Operators add context to stops. Supervisors review the shift. Production and improvement teams agree which recurring loss to investigate next.
Take the findings into a skyTON Lean problem record and follow the countermeasure through your review routine. This handover is currently manual.
Start with the visibility you need, then decide where to expand.
Plan the scope. Review the costs.
Tell us about your first production point. We’ll confirm compatibility, subscription pricing, device arrangements and delivery costs with you before you begin.
Keep the tools that already work for your team. Start by making production counts and stop times easier to review.
We already use Excel. Why add skyTON?
Keep Excel for analysis. With a compatible sensor setup, skyTON records production counts and stop times to reduce manual collection. Export report data as CSV when you want to work with it in a spreadsheet. Your team still adds context, such as downtime reasons and batch scrap.
Do we need to replace our existing systems?
Start with standalone production monitoring. A connection to your ERP or other systems is not required to explore the OEE workflow. Any requested integration needs its own scope and validation; it is not included as a standard promise.
We do not have time for another implementation.
Start with one production point and guided self-service configuration. Set up the device connection using your phone, then validate the line’s counts and stops before expanding. Sensor wiring and site requirements are checked first; there is no fixed installation-time promise.
Will it work with our line?
Share the production point, sensor model and signal specifications, Wi-Fi availability and installation needs. The current device supports configurable PNP/NPN inputs. We’ll review compatibility before shipping; the setup depends on your line.
