Auto Clock In/Clock Out

Since Non-WMS and Ad hoc activities are captured through clocking, WFM ensures that the users are clocked into facility and activity in the right sequence. However, if users start their day with WMS mobile transactions, it’s possible that a user may forget to clock into facility before starting the activity. Although this would not impact warehouse operations, it would result in incorrect productivity calculations for the user.

The auto clock feature in WFM can be used to automatically clock users into a facility enabling users to focus on performing WMS activities rather than following SOPs for clocking appropriately. The clocking is automatically done by WFM behind the scenes without any manual intervention.

Auto clock feature can be enabled by setting the facility parameter AUTO_CICO to “Yes”. When this parameter is enabled, WFM automatically clocks the user into a facility when the user logs into mobile options.

Note that even if the facility parameter is enabled, it is only applicable to users with group permission Track Record/Require CICO Validations. Auto clock in/clock out will not be performed for users that do not have this permission. Also, unlike other permissions, this permission is not enabled for ADMINISTRATOR ROLE by default.

Auto Facility Clock In

When a user logs into mobile, depending on the current state of the user, WFM performs next steps as described in the table below:

Auto Facility Clock In

Current User Status WFM Response
User is already clocked into the current facility No further action is taken by WFM.
User is clocked into a different facility WFM clocks the user out of the other facility before clocking into the current facility. Note that, auto clock feature needs to be enabled in the other facility for WFM to perform auto clock out from the other facility.
User is found to be inactive.
A user is considered inactive in the following scenarios:
  • If the last clock record of the user is more than 1440 mins (24 hours) ago.

OR

  • If there are no clock records or no WMS activity for the user for last X number of minutes. The value X can be configured in the facility parameter CICO_INACTIVITY_TOLERANCE_MINS which can be set between 120 minutes to 1440 mins.

Facility Parameter: CICO_INACTIVITY_TOLERANCE_MINS

  • If the facility parameter is not configured, a default value of 240 minutes will be used.
  • If the facility parameter configured is less than 120 mins, 120 minutes will be used.
If the facility parameter configured is greater than 1440 mins, 1440 minutes will be used.
User is clocked into the current facility.

However, before clocking the user into the facility, WFM checks if the user has any open clock records. If yes, WFM systematically clocks the user out of all such entities in the right sequence. For example, if the user was clocked into a break before becoming inactive, WFM will clock the user out of break and the facility before clocking user into current facility.

As of Release 26B, a 24-hour restriction has been introduced between facility clock in and clock out. Depending on the user's last facility clock-in, facility clock-out timestamp for the user will be determined as follows depending on whichever event is latest:
  • End timestamp of the last WMS Activity that is within 24 hours from user's facility clock in time.
  • Clock out time of the last closed Non-WMS, Ad hoc or break that is within 24 hours from user's facility clock in time.
  • Clock out time of the last open Non-WMS, Ad hoc or break that is within 24 hours from user's facility clock in time.

Open break or activity records will be closed with the same timestamp as the clock in timestamp of such records.

Any other user activity that is outside the 24-hour window will remain orphaned without any clock records and need to be manually addressed by supervisors.
Note: Auto Clock out from facility is not triggered based on any other action such as mobile log out, UI logout, mobile idle time or UI idle time. It is ONLY triggered when user logs into mobile and is found to have been inactive.

User Inactive Scenarios

Scenario 1: Clock Record entry greater than 24 hours; No activity in between

  • Login to mobile: Nov 3, 7:00 am
  • Auto FAC-CI: Nov 3, 7:00 am
  • Login to mobile: Nov 4, 7:05 am
  • Since Clock Record has exceeded 24 hours, facility parameter CICO_INACTIVTY_TOLERANCE_MINS is ignored.
  • Auto FAC-CO: Nov 3, 7:00 am; Auto FAC-CI Nov 4, 7:05 am.

Scenario 2: Clock Record entry greater than 24 hours; Activity in between

  • Login to mobile: Nov 3, 7:00 am
  • Auto FAC-CI: Nov 3, 7:00 am
  • End_ts of WMS Activity: Nov 4, 6:00 am
  • Login to mobile: Nov 4, 7:05 am
  • Since Clock Record has exceeded 24 hours, facility parameter CICO_INACTIVTY_TOLERANCE_MINS is ignored.
  • Auto FAC-CO: Nov 4, 6:00 am; FAC-CI Nov 4, 7:05 am

Scenario 3: Clock Record entry less than 24 hours; CICO_INACTIVTY_TOLERANCE_MINS = 120 mins

  • Login to mobile: Nov 3, 7:00 am
  • Auto FAC-CI: Nov 3, 7:00 am
  • End_ts of WMS Activity: Nov 3, 9:30 am
  • Login to mobile: Nov 3, 10:00 am
  • Since 10:00 am - 9:30 am < CICO_INACTIVTY_TOLERANCE_MINS, no clock records are written
  • Login to mobile: Nov 3, 1:00 pm
  • Since 1:00 pm - 9:30 am > CICO_INACTIVTY_TOLERANCE_MINS, user is clocked out of facility and clocked into facility.
  • Auto FAC-CO: Nov 3, 9:30 am; Auto FAC-CI Nov 3, 1:00 pm.
Note: As of Release 26B auto clock into work area has been removed, since it’s no longer required for employees to clock into Work Area.