Reviewed the documentation Initial set up document was discussed and reviewed - downloaded the initial clock software from the Release Wiki.

IP Address was discussed for the time clock as well as the host. The Clock Address already has a default address you cannot change the initial default address of the clock. If you do the clock will not link correctly. If you want to change to a static address after you configure the clock and have made sure it works correctly, this can be done using the clock web software. App Server IP address is needed for the HOST. Download the TFTP software to be able to move the conf and jar files to the clock

Updated the configuration files and the URL setup as two different files: • Two files will be created the AppReguar.conf and the AppBiometric.conf file. The differences between these files is the Biometric file has STORE_BIO set to True where the Regular File has it set to False. • A device Name and welcome message were defined these could be changed later. • ALLOW_KEYING was set to False • USE_BADGE was set to True (which requires the setup of ITCC with Clock Cards) • MIN_BADGE_LEN was set to 5 • MAX_BADGE_LEN was set to 5 • ENTER_JOB was set to False • The HOST URL was set up as follows: • All other configuration in the file remained as defaulted

In this training only clocking was to be done. We did not have to set up IMCS for Time Batch Codes, or IDWR for TM-Shift Calendar or IDWR for Time Rule of Default Time. If punching is going to connect to payroll all these will need to be set up in order to process the punches that have been created into Time Sheets.

Set up configuration will be as follows for the clocks: • Connect the clock to the network and record the IP address (this will be the DHCP address) • Using TFTP you must load in this order o Load the AppRegular.conf or AppBiometric.conf (as the Local File) o The host is the DHCP address of the clock you are configuring o The remote file will always be app.conf o After the "Put" then Load the App.jar and do a "Put" • In the Web Software add new static address information • Move the clock to the new location

If there are too many employees to manually load into ITCC then you can use IDIF and create a file to load the clock cards. In IDIF you will need to create two separate Interface Codes in order to load to ITCC. You will load the header in and after that has loaded using LMTD you can then load the details. • File to load header is ITCC_HEADER_LOAD TCC.CLOCK_CARD_CODE (Load from file) TCC.STANDING (Constant Value of A) TCC.DEN_ID (Constant Value of the ID for the Entity being used) • File to load details is ITCC_DETAIL_LOAD TCCD.TCC_ID.CLOCK_CARD_CODE (load from file) TCCD.EEM_ID.EID_ID.PERSON_CODE (load from file) TCCD.CLOCK_CARD_STATUS (Constant value of 01) TCCD.CARD_TYPE (Constant value of 02 or 01 or 03) TCCD.EFFECTIVE (Constant value of 01-Jan-2013 or whatever start date you want to use for clocking) TCCD.TCC_ID.DEN_ID (Same value as loaded in the header record file)

Set up the ITCD record for the clock devices. This will be set up right now as the name of the device with the location. The description will further define the location.

A report was created to report the punches to the timekeepers for each payroll period. • In DISCOVERER created KH_Clocking Report Report contains date, time, day of week, person code, name, department, authorization area, clock name and location of the clock Sorted by Department then Person Code then Date with a Page Item of Authorization Area Parameters are Start Date, End Date and Person Code, Person Code is not a required field When run by the time keeper only the authorization area they are allowed to see will be reported.