0% found this document useful (1 vote)
146 views25 pages

Matrix AEBAS Client Work Flow

Try again later.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (1 vote)
146 views25 pages

Matrix AEBAS Client Work Flow

Try again later.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 25

Matrix_VEGA

Matrix_VEGA Device can work in two modes


with AEBAS server
• Registration Mode
• Attendance Marking Mode
Device Idle Screen (When Device is not Registered)

17:09 AEBAS Server


connectivity status

Register Client Menu

Finger Sensor:
Initially – Inactive

Card Reader:
Always - active
On click of Register Client

17:09
Register Client

Server Location

Select Server Location

Activation Code
On click of Select Server Location field

17:09
Select Server Location

Maharashtra

Gujarat

Touch to select a server Telangana

Karnataka
Rajasthan
Karnataka
On click of Activation Code Textbox

17:09
Register Client
Activation Code

123I

1 2 3
4 5 6
7 8 9
0
On click of Continue icon

17:09
Register Client

Server Location

Gujarat

Activation Code

123456

Once server location and


code is entered, button will
get enabled and user can
click to continue
On click of Continue icon – while device is waiting for API response from
AEBAS server

17:09
Register Client

Server Location

Gujarat

Activation Code

123456
Processing…
On click of OK (if Activation Code is not matched or minimum length
criteria has not been satisfied)

17:09
Register Client

Server Location

Gujarat

Activation Code

12345 I
Invalid Activation Code!
On click of OK (Device is not getting response from AEBAS server before
Time-Out duration)

17:09
Register Client

Server Location

Gujarat

Activation Code

123456
Time-Out!
On getting Success response from Server Location API

17:09
Search Entry Point
Laboratory_3rd Floor

EC Department_Ground

Room No. 153 (Library)

R&D_3rd Floor

Room No. 113 (General)

Head Office_1st Floor


Selected Entry Point is shown. User should click continue

17:09
Register Client

Entry Point

EC Department_Ground
Next step is to show Biometric Credential

17:09

Place Your Finger...

Finger Sensor will be


active to take nodal
officer finger input
When Finger has been scanned by sensor

17:09

Remove Your Finger...


When Finger input doesn’t get match with nodal officer UID

17:09

Client Registration Failed!

Biometric Mismatch!
When Finger has been matched with nodal officer UID

17:09

Client Registration
Successful!
Device Idle Screen (When Device has been Registered Successfully)

17:09 Connectivity with AEBAS


Server

Attendance ID Menu

Finger Sensor:
Initially – Inactive
It will be active only when
Aadhar ID is entered/ card
shown on device

Card Reader:
Always - active
On click of Attendance ID

17:09

Enter Attendance ID

088999

1 2 3
4 5 6
7 8 9
0
On click of OK – without entering minimum digits of User Aadhaar ID

17:09

Enter Attendance ID

088 I
Minimum XX digits required

1 2 3
4 5 6
7 8 9
0
On click of OK (if last Aadhaar ID is entered or Card shown [in which
Aadhaar ID is written])

17:09

Place Your Finger...

Finger Sensor: It
becomes Active
When finger has been scanned

17:09

Remove Your Finger...


Opening punch of user

17:09

Attendance Type: Opening

ID: XXXXXXXXXXXX

Opening Time : HH:MM:SS


Closing Time : HH:MM:SS

Response Time: 1.23 sec


Closing punch of user

17:09
Attendance Type: Closing

ID: XXXXXXXXXXXX

Opening Time : HH:MM:SS


Closing Time : HH:MM:SS

Response Time: 1.23 sec


When Aadhaar ID is correct but finger input doesn’t match

17:09

Attendance Type: N/A

Error ID: 9906


Reason: Biometric Mismatch

Response Time: 1.23 sec


When Aadhaar ID is invalid

17:09

Attendance Type: N/A

Error ID: 9902


Reason: User Not Registered

Response Time: 1.23 sec


If device does not get response from AEBAS server before Time-Out
occurs

17:09

Time-Out!

You might also like