Reference · for Operators, Engineers
Apps
Fill in the forms your roles may use, such as downtime reasons, quality checks and shift handovers, for a device, with drafts saved as you type.
Apps lists the forms you can fill in: downtime reasons, quality checks, shift handovers and any form an engineer publishes for your roles. A record you submit is kept with the device it is about, who filled it in and when. It is in Monitor > Apps; forms are designed in Organize > Forms.
Who sees which form
A form names the roles that may fill it in, see its records and approve them. You see a form when one of your roles is named, and your role also needs the matching capability:
| You want to | Your role needs |
|---|---|
| Fill in and submit a form | Fill in forms, and to be named among the form's roles that fill it in |
| Approve or reject records | Approve forms, and to be named among the form's approvers |
| Add the sample forms | Publish forms |
A form filled in for a device follows your site: you only see the devices your roles may see. See Users and roles for the built-in roles.
Fill in a form
- Open Monitor > Apps and select a form.
- When the form is about a device, choose the device. The address bar now names the form and the device, so a bookmark or a link opens the same form for the same machine, for example on a tablet next to it.
- Fill in the fields. Fields marked with * are required. Some fields appear or become required from your answers: in Shift handover, Why the scrap appears when the scrap count is above zero.
- Select Submit. Fields that need attention say why next to the field (for example At most 500 pcs., or the designer's own message), and the record is not sent until they are fixed.
Your draft is saved a moment after each change. When you open the same form for the same device again, the draft comes back. Each person has one open draft per form and device.
A form that needs approval shows It now waits for approval after you submit it.
Sample forms
When a sample form is missing, a user who may publish forms sees Add sample forms. It adds and publishes the missing ones, which name the built-in roles:
| Form | What it records |
|---|---|
| Downtime reason | Why a machine stopped, chosen from the reason tree; when, for how long, and whether it runs again. A stop over 30 minutes needs a note; the duration is worked out when the machine runs again |
| Quality check | A first-piece or in-process checklist with a pass or fail result; an engineer approves it |
| Shift handover | Output, scrap and its reason, safety, and open issues for the next shift |
| Work order | Starting or finishing a work order on a machine: the order number (scanned), good and scrap, and the yield worked out from them; a yield under 90 % needs a note |
| Maintenance request | What is wrong with a machine, how urgent, with photos; a stopped machine makes it urgent. Maintenance (an engineer) accepts or turns it down |
| Component tour | Every component a form can use, to start your own forms from |
| Machine panel | An operator screen: speed, count and trend of a machine, its target speed within limits, a shift note |
Roles a hub does not have are left out of a sample's lists. The Downtime reasons choice list that the Downtime reason form uses is added with it when the hub does not have it yet.
What a form can hold
- Text, numbers, dates and times. Numbers have large − and + buttons, the unit and the allowed range.
- Choices. A few options show as cards you tap; many options open a searchable list. Several answers show as chips.
- Choices with levels. A reason such as Unplanned › Breakdown › Electrical is chosen one level at a time with large buttons; the way back is shown above them and a long list can be searched. Change opens the list again where the choice was. See Choice lists.
- Checklists. Each line is answered OK or Not OK; a failed line can ask for a note.
- Photos, files and a signature. On a tablet, adding a photo opens the camera. A signature is drawn on the screen.
- Live machine values. Values of the device the form is opened for update while the form is open, with their quality and when they last changed.
- Writing to the machine. A setpoint stays within the limits the form sets, and a write button asks to confirm before it writes. The machine's answer is shown next to it.
My records and approvals
The tabs above the forms show records instead of forms:
- My records lists every record you filled in, drafts included, newest first.
- To approve lists the submitted records that wait for your decision, oldest first. The tab is there when you approve at least one form, and its badge counts what waits.
Select a record to open it beside the list.
- Where the record stands, the device it is about, who filled it in and when.
- Approve, or Reject with a reason. The person who filled it in reads the reason on the record.
- The answers, drawn as the form people fill in, with photos, files and the signature from the record.
- PDF downloads the record for printing, with its photos and signature.
A draft has Continue filling in, which opens it in the form for the same device. The record's history at the bottom shows when it was started, submitted, decided and exported, and by whom.
Signing a record
A form that asks for an electronic signature opens a signing window when you select Submit, and an approver's Approve or Reject does the same when the form signs decisions.
- Who signs: the signed-in person. Sign with your own account only.
- What the signature means, as the form states it.
- Your Proxus password, typed again for this signature (your signature PIN when you sign in with Windows; the first time, you set it here).
- Sign and send checks the password and sends the record with the signature. A wrong password asks again and counts as a failed sign-in.
The record shows its signatures under Electronic signatures (who, when, what it meant, how they signed) and in its PDF; a signature that no longer matches the record is marked in red.
Analysis
The Analysis tab sums up a form's records: how many there are, or how much of a number answer, by each answer of a choice, by device, by person, by state, or by day, week or month.
- Measure: Records, or the Sum, Average, Lowest or Highest of a number field (Field). Group by lists the form's choices, yes/no answers and short answers, then Device, Person, Status, Day, Week and Month. A form opens with its own summary, set in the designer; Form's default goes back to it.
- Period (the last 7, 30 or 90 days or a year, today included), which Records (every sent record, approved only, waiting for approval or rejected only) and, for a form filled in for a device, one Device.
- The figures: how many records, the measure over all of them, and the largest group with its share of the total.
- Create dashboard opens the summary as a dashboard (see below).
Below them, the groups come largest first with their cumulative share: a Pareto that shows the few reasons behind most of the downtime. Beyond 12 groups the smallest are shown together as Other; grouped by time, the days, weeks or months come in order. The same measure follows over time, and a table lists every group with its value, records, share and cumulative share.
- The tab sums up the records your lists show you: everyone's when you may see all records of the form or approve them, otherwise only your own (the tab says so). Your site scope applies, and drafts are never counted.
- A summary reads at most the newest 100,000 records of the period and says when there were more.
- Create dashboard, for roles that design dashboards, opens the summary in Reporting > Dashboards with a date filter, the measure over time and a table; change it in the dashboard designer like any dashboard. The dashboard does not copy the records: everyone who opens it sees only the records of the form they may see.
- The AI Assistant answers questions such as "which downtime reasons cost the most last week on Press 4" with the same summary, and MCP clients use it as
form_summary.
Operator screens
A form designed as a screen shows its items as tiles, like an operator panel: live values, counters, trends and setpoints side by side, with the fields of the record among them. It works as any form: values a person writes to the machine stay within the setpoint's limits (a value outside them is refused before it reaches the machine), and Submit stores the record. On a phone the tiles stand one under the other, row by row.
- A live value tile.
- The setpoint: the target speed within 0 to 3000 rpm, written after a confirmation.
- A write button that fills its tile.
Kiosk mode
A tablet next to a machine can show one form all day, without menus: the kiosk.
- Open the form on the Apps page for the machine and select Kiosk link in the form's header. The link is copied; where the browser does not allow copying, it is shown to copy by hand.
- Open the link on the tablet. It has the form of
https://<hub>/forms/kiosk/<form key>/<device number>; without the device number, the kiosk asks for the device.
- The device the kiosk is for. A kiosk opened with a device number stays on that device.
- The clock. The screen does not go to sleep while the kiosk is open, where the tablet's browser allows it.
- Leave kiosk asks to confirm, then returns to the Apps page. Full screen next to it hides the browser's bars.
- Controls are large enough for gloves. After Submit, the next empty record starts by itself after a few seconds.
When the connection to the hub drops, an orange strip says so above the form: changes made then are not saved. When the hub answers again, the page reloads by itself, with the form, the device and the saved draft.
Setting up a tablet
- Sign in once on the tablet with a user whose role may fill in the form, for example a shared Operator account for the line. The kiosk stays signed in like any browser tab.
- Lock the tablet to the browser: Chrome's kiosk mode (
--kioskwith the kiosk link) on a PC or Chromebook, Screen pinning or a managed kiosk on Android, Guided Access on an iPad. - Turn off sleep and battery saving for Wi-Fi in the tablet's own settings, and keep a way for an administrator to leave the kiosk.
Offline app
Where the network is patchy (a yard, a warehouse, a line far from the access point), people fill in their forms in the offline app instead. It runs in the browser without the hub and sends the records when the hub can be reached again. Open it with Offline app in the Apps page's header or at https://<hub>/forms/app/, and add it to the tablet's or phone's home screen (Install or Add to Home Screen in the browser) to open it like an app.
- Open the app once while the hub can be reached and you are signed in. It takes along the published forms you may fill in, the choice lists they use and the devices you see, and keeps them on the device.
- From then on, open it with or without a connection. Forms, rules, formulas and checks work as on the Apps page; drafts are kept on the device.
- Submit keeps the record on the device and says so. The app sends waiting records, in the order they were sent, as soon as the hub answers, when it opens and every half minute while it is open.
- Whether the hub can be reached: Online, Offline (no network) or Hub unreachable (a network without the hub).
- What waits: records to send or to correct, or when the app last synced. Select it to sync now.
- A record waiting for the hub. It keeps the time it was sent on the device; the record's history on the hub notes that it came from the offline app.
- A record the hub refused (the values no longer pass the form's checks, the form was changed or archived, access was taken away) shows the reason. Correct opens it on the form, with the fields to fix marked, to send it again.
What the offline app does not do:
- Machines are neither read nor written: live values show a dash and write buttons are off.
- Forms filled in for a place in the Unified Namespace need the hub.
- Approving, exporting and other people's records stay on the Apps page.
- Records wait on the device until the person who filled them in signs in again on the hub. When the hub session has ended, the app says so; sign in from the link it shows. Sent records are kept on the device for a week.
- Whoever uses the device can see its waiting records: give each person their own device account, or send records and delete the device's data before handing a device over (see This device).
A form that asks for a signature on sending waits on the device as Waiting for signature: select Sign and send when the hub can be reached, and type your password or PIN. Signatures are never checked or kept without the hub.
This device
Select the tablet button in the app's bar to see what the app keeps on this device and to delete it.
- New records until: how long the forms may be filled in without the hub. The hub sets it with
OfflineMaxDaysunder[Forms]in the configuration file: 7 days by default,0for no limit. Past that date the app says so and its forms cannot be opened, drafts included, until it reaches the hub and takes the forms again; records already filled in are still sent. Connecting lifts it at once. - Storage: whether the browser keeps the app's data when the device runs short of space. The app asks for this the first time it takes the forms. Browsers usually grant it to an app installed on the home screen; when they do not, the app shows a note on its start page.
- Delete this device's data removes the forms, lists, devices, records and files the app keeps in this browser, for everyone who used it here. It asks once more and says how many records the hub does not have yet; those are lost.
- Confirm. If someone is still signed in on the hub, the app takes their forms again right away: sign out of the hub first to leave the device empty.
Access and security
- There is no separate sign-in. The app uses the hub's own session: people sign in on the hub's sign-in page, so its password rules, session length and switched-off users apply. Without a session the hub gives the app nothing.
- Anyone can load the app's files, as anyone can load the sign-in page; they hold no data.
- The app takes along only the forms the person may submit (the form's access list and Submit forms) and the devices their roles and site scope let them see.
- Every record is checked again by the hub when it arrives, with the person's access at that moment: a record of a form they may no longer fill in, or for a device outside their site scope, is refused.
- Without a connection the hub cannot check the session. The forms already on the device can still be filled in; the check happens when the records are sent.
- What the app keeps on the device (forms, device names, drafts, waiting records with their photos and signatures) is protected by the device's own sign-in and the browser profile, not encrypted by Proxus. Signing out of the hub does not remove it: use Delete this device's data.
- The forms on a device stop being usable after the number of days the hub allows, so a device left without a connection does not go on with forms, lists and access that may have changed since.
Setting up a device
- Use HTTPS. Browsers run an app without a connection only on a secure address. Open the hub as
https://<hub>/forms/app/, and make the tablet trust the hub's certificate: install the Proxus Platform CA (or your company CA that issued the hub's certificate) on the tablet. Over plainhttp://the app opens while the hub can be reached, but not without it. - Install the app on the home screen (Install or Add to Home Screen). On an iPad this also keeps its data; Safari clears the data of sites that are not installed and not used for a while.
- Open the app once a day while the hub can be reached, so it has the latest forms and sends what waits.
Limits in this version
- A rejected record is not edited again: fill in a new record.
Was this page helpful?
Evaluating Proxus? See it on your own machines in a 30-minute technical session.