How Many Time Device Event Mappings and Web Clock Button Definitions to Create

Use these questions to help you decide how many time device event mappings or web clock button definitions you need to create.

Question	Examples and Comments
What events do you record with your time collection devices or web clock, for example shift start, break, meal, and shift end?	To ensure accurate time event validation and processing, there can't be any ambiguity about the time events that each device provides. They must clearly and consistently map to an In, Out, In and Out, or Out and In application event. For example: You identify when employees start their work using the Start Shift time device event, which maps to the In application event. You identify when employees take a break using either of these methods. Map one time device event, Break, to the Out and In application event. Or, map two time device events, Shift End and Break In, to the Out and In application events, respectively.
What are the time attributes and attribute values that correspond to the time device or web clock events?	For example, the Start Shift, Break, and Meal time device events all map to the Payroll Time Type time attribute. But, the events each have different attribute values. Shift Start: Regular Break: Paid Break Meal: Unpaid Meal Using discrete time attributes enables you to report in greater detail, but might require more event mappings and mapping sets or web clock buttons. For example, since you pay breaks and shifts at the same rate, you could use the same Payroll Time Type attribute value for both. Since you don't pay for meals, you could decide not to associate any time attribute. Time device rules could still validate the event but time calculation rules would ignore it.

Question

Examples and Comments

What events do you record with your time collection devices or web clock, for example shift start, break, meal, and shift end?

To ensure accurate time event validation and processing, there can't be any ambiguity about the time events that each device provides. They must clearly and consistently map to an In, Out, In and Out, or Out and In application event. For example:

You identify when employees start their work using the Start Shift time device event, which maps to the In application event.
You identify when employees take a break using either of these methods. Map one time device event, Break, to the Out and In application event. Or, map two time device events, Shift End and Break In, to the Out and In application events, respectively.

What are the time attributes and attribute values that correspond to the time device or web clock events?

For example, the Start Shift, Break, and Meal time device events all map to the Payroll Time Type time attribute. But, the events each have different attribute values.

Shift Start: Regular
Break: Paid Break
Meal: Unpaid Meal

Using discrete time attributes enables you to report in greater detail, but might require more event mappings and mapping sets or web clock buttons. For example, since you pay breaks and shifts at the same rate, you could use the same Payroll Time Type attribute value for both. Since you don't pay for meals, you could decide not to associate any time attribute. Time device rules could still validate the event but time calculation rules would ignore it.