Sometimes you want to scan more than just the employee and project when tracking time for employee jobs.
Sure, the timesheet displays job time for each employee. That's your primary purpose for tracking time. You do it for the timesheet data. But you might also want to track time for which machine you're using. Or which building you're in. Or which tool is being used on the assembly line.
User-defined barcode sequence
Watch this video for a quick overview of how to collect user-defined scans required for your specific purposes.
Once those requirements are scanned, the timer will start. You'll still collect all the same timer information, but you'll also get more details you can report on.
Time and materials are a great thing to track with a barcode scanner. Standard Time® does that; that is the basics that you see in some of the other videos. This video is a little more advanced. We're going to get into tracking other kinds of information above and beyond the basics.
If you haven't seen those other videos go check those out.
Think about the things that you might want to track in your manufacturing, assembly process that are above and beyond the very basics. Things like maybe a building, assembly line, product line, machines and other details of your product that we've never even thought of. That you want to set up and be prompted for when you're scanning to start the timer. You will have to scan those required items before the timer will even start. That's take a look and see how that's done.
Over in Standard Time we'll press the F4 key to open the barcode window. In the lower right corner you see a button only administrators can see, required scans. And that is how you set up the requirements for gathering additional information.
You can see that I've got three of these, these are all fictional, building, machine and material. So presumably out on the shop floor, manufacturing you have employees that are collecting this information. They would first click the building they're working in, the machine that they are operating on and the material they are using. A fictional scenario here.
Each one of these has fields that we're want to take a look at. First of all there is the name and the prompt. That's the information that the end user actually sees that tells them what to scan. Then you've got the scan order which order you want to see these pop up on the end user screen. Then you have conditions that govern whether it actually pops up.
You could assign these to users; some users you want to collect the information and other people you don't have to, they are working in different divisions or areas. Same thing with project, category and task. You may want to collect certain information just for one project or for a certain kind of work or a certain task that you're working on. Simply put those in and this will pop up only during those scenarios.
The last field is the time log field in which the actual scanned data is going to go into. If you look at these three you'll see that this time log field is different for each of these. You can set up custom fields in the time logs or just use these text fields to put the information in.
Again when the end user actually scans the value they scan goes into that field in the time log. You can see I have three of these set up; you should be sensitive to the fact that the end user is going to have to scan a lot of stuff. They probably already going to have to scan their user name, a project, a task. So they may be up to three scans already before they even reach yours. Limit this to two-four would be a good thing. You collect whatever information you need to collect. This is just an idea of how they might look.
So let's go ahead and click OK and then start scanning to see what the end user would experience. They're going to start by scanning their name first; they'll probably then scan a project and then a task.
So the timer would ordinarily start here but we've got some requirements in this case we're going to scan the building. You see the name on the prompt. Let's put some information in, now we're up to the machine, again another scan and then the material. We've completed the requirements and so you see a new time log in the background. And you see that the timer has started. Two indicators that the timer is running.
Let's go ahead and click close; click on this time log and you can see in these text fields, that we talked about earlier, where the actual scans occur.
Now that you've collected this information you can run reports on this. You can get graphs, find out how much time you've spent on each of the different things that you're collecting. In this case how much time was spent in each building, how much time on each machine, how much time on each kind of material.
You do have the ability to also scan what we call expense templates for supplies, materials in a manufacturing process. But in this case I just put it in here as a fictional example. You can get all the reports you need off of this information plus the actual work, the project, the category, the task, lots of information here. That you can run reports on to get the metrics you need.
Again, press F4, barcode window pops up then press the required scans button. Then here you can set up whatever requirements you have to collect the information you need.