QTMS Process Data
QTMS Process Data
This function will process the data polled from the hardware clocks or from door access systems.
PROCESS DATA will populate Time-In, Time-Out, and breaks into employee TIME ENTRY.
You may then modify employee daily attendance from TIME ENTRY module.
IMPORTANT
* Remember to check process log file generated by PROCESS DATA.
The log file will normally list possible employee swiping errors such as swiping outside designated shift zones,
forgotten swipes, or other possible errors within system settings.
* The date to start processing can be any date but you must always remember to process until the day before the
current date
* See CLOCK SETTINGS topic on IN-CLOCK list, OUT-CLOCK list and EXCLUDE-CLOCK list.
You may use IN-CLOCK and OUT-CLOCK list to determine employee swipe IN or OUT status.
EXCLUDE-CLOCK list will ignore swipe records collected from these clocks.
* Blank card number and card number = FFFFFF are automatically ignored
Query
Click on [ Query ] button to filter by employee, cost center, department, or section.
Option Button
View TMS.TXT option will view polled data inside TMS.TXT file..
View TRANSACTION.DB option will view processed swipe data.
View Process Log option will view processed remarks generated by PROCESS DATA module.
Process Date
Process Date From … To: Select the date to process. It will then determine the time in / time out, overtime,
lateness and etc. The data will then be represented in Time Entry.
(1a) ST8000 Door Access (DBF): Select directory where data files are stored
// ST8000 has 2 card number fields ie. 'CardNo' and 'BadgeNo'. Default uses 'CardNO'.
// Older ST8000 Door Access software version does not have field "BadgeNo"...
// To override, insert below line into <Data\Database>\TMSSetup.INI file:
// UseBadgeNo=1
//------------------------------------------------------------------------------
// Filename format: TRyymmdd.DBF
// Database Format: DBF (dBase)
// Fields:
// - DATE (string yyyy/mm/dd)
// - TIME(string hh:nn:ss)
// - TRANS_DESC
// - BUSNO, UNITNO, READERNO
// - CARDNO
// - BADGENO
// Note:
// - Only TRANS_DESC = 'Valid Card Access (IN)' and 'Valid Card Access (OUT)' records are included.
// Other records are ignored.
// - 'Valid Card Access (IN)' will be assigned with CLOCK SETTINGS ==> Time In character
// - 'Valid Card Access (OUT)' will be assigned with CLOCK SETTINGS ==> Time Out character
// - Clock ID = BUSNO + UNITNO + READERNO
(1b) ST8000 Server (Text File): Select directory where data files are stored
(2) SYNEL Clock Data (Text File): Select directory where data files are stored.
(3a) Time Portal (DBF): Select directory where data files are stored.
(3b) Time Portal / xPortal (MDB): Select directory where data files are stored.
** Requires Full read & write access to data folder where MDB files are stored.
(3c) MicroEngine Door Access (DBF): Select directory where data files are stored.
(3d) MicroEngine (XLS): Select directory where data files are stored.
Reminder: To use swipe IN & OUT detection, please assign CLOCK SETTINGS ==> Time IN & Out
characters
(3e) MicroEngine (TXT): Select directory where data files are stored.
(3f) MicroEngine (CSV): Select directory where data files are stored.
(8a) Castle Clock (Text File): Select directory where data files are stored
(8b) Castle Clock [B] (Text File): Select directory where data files are stored
(10d) FALCO (TXT): Select directory where data files are stored
(11a) ADC Door Access (DBF): Select directory where data files are stored
(12a) IES BAR-CODE (Text File): Select directory where data files are stored
(12b) IES MAG-8 (Text File): Select directory where data files are stored
(13a) Xenix (Text File): Select directory where data files are stored
(15a) CIS Clock (Text File): Select directory where data files are stored
(15b) CIS Clock (Text File): Select directory where data files are stored
(17b) ELID Access (Paradox): Select directory where data files are stored
(17c) ELID DAT (Text File): Select directory where data files are stored
(17d) ELID DAT Ver 2 (Text File): Select directory where data files are stored
(18a) EntryPass (DBF): Select directory where data files are stored
(18b) EntryPass PlatForm1 (Text File): Select directory where data files are stored
(19) PerfectEntry (DBF): Select directory where data files are stored
// Filename Format: ZTyyyymmdd.DBF
// Database Format: DBF (dBase)
// Fields:
// - TDATE (String yyyy/mm/dd)
// - TTIME (String hh:nn:ss)
// - USERID (String(6))
(21b) TIMELINE 100 (Text File): Select directory where data files are stored
(21c) FINGERTEC TCMSv2 (Text File): Select directory where data files are stored
(22a) ALC GLOBAL (Text File): Select directory where data files are stored
(22b) ALC (CSV Format): Select directory where data files are stored
// Example :-
// 015304112112070842
// 015303632112070843
// 019049272112070845
Example:
30062008,2359,ABC123456,0,1
30/06/2008,23:59,ABC123456
30/06/2008,2359,ABC123456
Example:
ABC123456,30062008,2359,0,1
ABC123456,30/06/2008,23:59
(27) RCG (Text File): Select directory where data files are stored
// Filename Format: yyyymmdd.DAT
// Database Format: CSV (space delimeted)
// Fields: CCCCCCCCCCXXXXXMMDDHHNNSS
// Where : XX=Ignore, CC=Card, MM=Month, DD=Day, HHNNSS=Hour/Min/Sec
(28) RCG [B] (Text File): Select directory where data files are stored
Please use ELSYS system to retrive employee Card Number and Badge Number.
Then, enter any (or both) numbers into QUICK TMS ==>Employee Master ==> Card Number
// CHECKINOUT Fields:
// - UserID (Employee Number) ==> Will refer to Table USERINFO for "CardNo" or "BadgeNumber"
// - CheckTime (DateTime)
// - SensorID (Clock ID)
// USERINFO Fields:
// - UserID (Employee Number)
// - BatchNumber (Card Number #1) ~ optional field
// - CardNo (Card Number #2) ~ optional field
// CHECKINOUT Fields:
// - BadgeNumber (Card Number)
// - CheckTime (DateTime)
// - SensorID (Clock ID)
(31) SIS Point Of Sale : Select directory where data files (*.xls) are stored
(32) JDI: Select directory where data files (*.dbf) are stored
(36) Giga TMS Promag: Select directory where data files (*.txt) are stored
(40) KIME (*.XLS) : Select directory where data files (*.xls) are stored
(41) CHALLENGER (*.XLS) : Select directory where data files (*.xls) are stored
(42) PALM-ATN (*.ATN) : Select directory where data files (*.atn) are stored
(44) HANVON (*.XLSX) : Select directory where data files (*.xlsx) are stored
(46) PACOM (*.XLS) : Select directory where data files (*.xls) are stored
(47) SMART POINT-OF-SALE (*.XLSX) : Select directory where data files (*.xlsx) are stored
(49) ONGUARD (*.XLS) : Select directory where data files (*.xls) are stored
(52) CHIYU (*.XLS) : Select directory where data files (*.xls) are stored
(53) AXEONTEC (*.CSV) : Select directory where data files (*.csv) are stored
(54) ACESYS (*.CSV) : Select directory where data files (*.csv) are stored
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TECHNICAL TIPS - PROCESS DATA
What are the common PROCESS DATA problems when detecting swipes ?
- Employee forgotten to swipe-IN or swipe-OUT
- Swipe-IN or swipe-OUT outside designated zones in Shift settings
During PROCESS DATA, I get a warning "Error Time-OUT" and "Cannot Find Shift Number"
Goto TIME ENTRY and check the entire swipe records for the month for wrongly time detection. Time detection
errors are common for 24 hours rotating shifts when employees swipe wrongly.
During PROCESS DATA, when no time-out swipe is detected, will the swipe-in be saved ?
NO. Instead, only a warning "Cannot find Time-OUT" will be prompted