Foundational Modules
The Screen Configurator holds every operator screen on your floor. Build one in the editor, preview it as the terminal shows it, then publish. No development ticket.
Screen list
Every screen built for the site sits in one list. Open one to edit it, preview it, or assign it to an asset or a line. Start a new screen from the same list.
Editor
Place the blocks the job needs and set the order. The layout saves as configuration, not code, so nothing waits on a development ticket. Update it the same day the job on the floor changes.
Preview
Preview shows the screen exactly as it will run on the terminal. Open it from the list or the editor, adjust a block, and check again before you publish.
Assignments
The assignment stays with the screen instead of in someone’s head. One screen can serve several assets doing the same job, and you can change the assignment without touching the layout.
Runtime
A published screen opens by its own short name and fills the display. The runtime holds one screen at a time, so the operator sees the job in front of them and nothing else.
Block library
A screen controls what is shown and where it sits, nothing more. What a person is allowed to do lives in Security, and the forms that capture data are built in Form Builder.
No. A screen is configuration, laid out in the editor and published from there.
You assign it to an asset or a line. Published, it opens by its own short name.
Yes. Preview runs the screen as configured, and you go back to the editor to adjust.
No. The Screen Configurator decides what a screen shows. Security decides what a person may do.
30 minutes on the job and what the Screen Configurator would lay out for it.
We use cookies to understand how the site is used and to connect form submissions to earlier visits. No analytics or marketing cookies are set until you choose. Privacy Policy