02
For operators
One simple station for the machines they run.
Assign only the relevant machines to each shared tablet. Operators see state and output, record activity, and raise an Andon without navigating the whole plant.
Open full screen ↗
JuzeTry it on your floorYour machines are already telling you what is happening
Stop finding outtoo late.
One live screen shows what is running, what stopped, for how long, and why—across old manual machines and live PLCs. See the problem. Act sooner. Keep the history.
Install onceOpen on any plant-network deviceNo public PLC exposure
Attention nowPress 101 stopped
Material jam · 08:14 elapsed
Your plant, right now16 machines visible 11 running · 3 need attention
This is what “live” looks like
One glance. The whole floor.
Start with the big question—what needs attention right now—then move straight into the machine, run, reason, and person behind it.
01
For supervisors and plant leaders
See 16 machines at once. Rotate through the rest.
Running, stopped, idle, and attention states stay visible beside output, yield, and active Andons. Choose how many machine cards each wallboard shows, then rotate pages automatically for larger plants.
- Up to 24 machines on each page
- Automatic rotation every 5 to 120 seconds
- Fullscreen light or dark wallboard
16 shown here24 max per page5–120s rotation
Open full screen ↗Open full screen ↗03
For reviews, meetings, and deeper analysis
Filter once. Export the right report for the room.
Run one filtered report, then download every row as CSV or a polished PDF for Production, Quality, or Maintenance. The date range, machine selection, and calculations stay consistent with the live screen.
CSVRaw dataEvery row for Excel, audit, or BI
PDFProductionOutput, availability, parts, and losses
PDFQualityYield, scrap, and quality-classified stops
PDFMaintenanceDowntime, recurring losses, and repair events
Open full screen ↗What leaves Juze
A clean report people can actually use.
Choose all machines or one machine, set the reporting period, and export the same production picture as a meeting-ready PDF. Open either sample to see the actual document layout.
Plant-wide or single-machine scopeSelected date range carried into the reportRuntime, downtime, output, quality, and lossesDemonstration data only
Open full screen ↗04
For the person solving the problem
Move from plant signal to machine context.
See the current part, elapsed state time, today’s timeline, production result, and manual actions together. No separate spreadsheet is needed to explain what happened.
Built for the floor
A tablet at the cell. A phone in your hand.
Juze runs in a normal browser on the plant network, so operators do not need a full computer beside every machine. Give each shared device a station link that opens only its assigned machines.
No app-store installationAssigned-machine station linksSame users, events, and history
What just stopped?
See it the moment the state changes—not after the next radio call or walkaround.
Are we on target?
Give the whole shift one live answer for output, yield, downtime, and active Andons.
Why did we lose it?
Keep the stop reason, operator action, run, and machine timeline together.
What about old equipment?
Put it on the same board today with operator entry, then automate when it makes sense.
Without a live plant viewWalk. Ask. Call. Guess.
→With JuzeSee. Act. Explain. Improve.
Silence is expensive
When a machine stops, the right people should know now.
Every unnoticed minute starts before someone walks past, checks a whiteboard, or makes a radio call. Juze turns scattered machine and operator information into one shared live picture—without replacing equipment that still works.
Without Juze
The shift is always asking.
- Which machine is down?
- How long has it been stopped?
- What part was running?
- Why did yesterday miss target?
With Juze
The answer is already visible.
- Live state and elapsed time
- Output, scrap, yield, and target
- Operator and stop-reason history
- Reports for the shift or date range
Example on the floorOne stop. One shared timeline.
9 minPress 101 stops
The wallboard changes immediately and the active stop appears.
The right people see it
The operator records the reason while the supervisor sees the same event.
Production resumes
Juze keeps the eight-minute loss, the user, and the reason in machine history.
From stopped to solved
The right department gets the call.The plant keeps the answer.
When an operator selects a routed stop reason, Juze creates a department request automatically. Maintenance, Tool & Die, Quality, Material, or Production can assign one or more named responders, bring in another department, share updates, and close each team's work with a record of what was actually done.
Operator
Requests the right help
Select the stop reason once. Routing happens automatically.
Department
Sees and hears the alert
The request appears for the assigned response team.
Responders
Assign and update the work
Everyone can see which people and departments are involved.
Plant history
Keeps the resolution
The repair, timing, notes, and people stay with the event.
1New
2Being handled
0Overdue
7Resolved today
Tool & DiePress 101
Die alignment requested
Latest work note
Inspected guide pins. Adjusting the left-side alignment block.
Request sent 08:42 2 responders assigned 08:43 Work in progress 08:47 Resolution log
!
New department requestTool & Die: Press 101
OpenA real Juze work record
See every team and responder working the same stop.
This active Maintenance request shows two named responders and a linked Quality request for the same stop. Each department keeps its own status, notes, and resolution while the plant retains one connected event history.
Multiple named respondersParallel department requestsRequired work-performed log
Open full screen ↗The request reaches the people who can act without another radio chain.
Operators and leaders see whether the call is new, claimed, or in progress.
Notes keep the next shift informed when work spans people or departments.
Completed work becomes searchable history instead of disappearing after restart.
Start with the plant you have
Old machines, new PLCs, and everything between.
Juze does not require a perfect automation project before it becomes useful. Give each machine the capture method that makes sense today and keep one consistent operating picture.
Manual operator entry
Make older equipment visible now.
Operators record runs, stops, parts, counts, scrap, and stop reasons from a tablet or machine-side computer.
- No PLC work required
- Logged-in user retained on events
- Same wallboard and reports
Live controller capture
Automate only what each machine provides.
Select a connector per machine, test the connection, and map only the useful signals. Juze monitors values and does not write commands to the controller.
- Every mapping signal is optional
- Mixed PLC brands in one plant
- Central Kepware or direct connection
Runtime-only equipment
Track assets that do not make a counted part.
Warmers, utilities, ovens, and support equipment can start without a recipe while Juze still records running and stopped time.
- No part selection required
- Running and stopped duration
- Visible beside production machines
Guided, read-only connectivity
Connect the PLC. Map what matters. Leave control alone.
Each machine can use its own driver and its own optional tags. A central Kepware server can also feed many machines while their mappings remain clean and separate.
Kepware OPC UAGeneric OPC UAMitsubishi MC / SLMPSiemens S7.NetAllen-Bradley / Rockwell
Designed for monitoringJuze reads production signals; it does not control the machine.
Open full screen ↗No slide deck. Your real floor.
Give Juze 60 days with your machines.
Install it on one Windows computer, add a useful group of machines, and let your real production team decide. The question is simple: did people see problems sooner and understand the shift better?
1 Install on the plant network2 Add machines, users, and parts3 Open it from laptops and tablets
60
days to evaluate with real plant data
On-premise. No public PLC access. No forced cloud dependency.
Built with Lithuanian roots.
A practical product for plants that want answers, not another complicated system. Questions and demos are welcome in English or Lithuanian.