There are several two ways to start the user interfaces/terminals.
Production Control > Periodic > Manufacturing Execution > Job registration start the terminal in the default configuration sat in the terminal form. If it is the first time started it will be prompted for a configuration.
Home > Common > Time and attendance > Clock in/out (Punch clock). This launches the terminal in the clock in/out only mode sat in the terminal configuration.
Or atleast they should… There are some bugs you should be aware of.
The first is that there is a caching issue when starting the client. This results in the client authenticating as the AOS server the first time the job registration form is opened. There is a fix for this (KB 2970350).
Another thing is that the clock in/out menu item does not work properly wither. Might be some coding that’s missing. I have not gone through the work of figuring this one out.
Once started the terminal shows the authentication screen.
User logs on with worker ID or Badge ID and password (if active).
System finds the active profile (profile calendar (User > Group > All), Profile relation for the Profile group and finaly the default profile for the user). If the clock in time is after the clock in time for the profile (if there is any), the user is presented with the absence form to explain why they have been absent.
If all is okay the user is presented with the default interface for the terminal configuration or the configuration sat for the worker on the worker employment settings.
There are several areas the user can look for jobs to work on. These are toggled to with menu buttons.
* Selected jobs
This is used for bundeling work and checking the jobs that are selected. If a barcode is scanned and the user is in bundle mode this screen is shown.
* My jobs
If the resource is connected to an employee that is logged on the user can be presented with work only for that user.
All production orders. Can be limited to only show for a production area, resource group or a single resource.
All project and project activities that are active
* Indirect activities
Shows all the indirect activities that the user can clock time on.
After a job is selected the user clicks start to make the job or jobs active.
Instead of navigating around the user can use the JobID and feed it in to the barcode area either woth a keyboard or preferably by barcode if this is activated on the terminal setup.
If the user is not in bundle mode and active on a manufacturing job the user will be prompted with the feedback dialogue (Either grid or wizard type). The user can also do feedback directly by clicking feedback in the menu.
There are three status updates to be given for the jobs on feedback.
* None – User continues to work on the item. Not optional if not bundeling.
* Stopped – The user stops working on the job, but the job is still available later.
* Finished – Job is marked as closed and not available for further work.
If he user presses finish by mistake the Supervisor can override. There is also the option for quantity validation before closing.
The user can also make changes to picking lists at this point if needed.
After feedback is given the form is closed by clicking close.
The terminal returns to the authentication screen.