Employee Data Template

From JUNO Wiki
Revision as of 07:10, 22 February 2020 by Lokesh (talk | contribs) (Created page with " Employee Details are required in the following format. Special care needs to be taken in choosing Employee Id and Email (which will be used for Logging in) {| class="wikit...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Employee Details are required in the following format.

Special care needs to be taken in choosing Employee Id and Email (which will be used for Logging in)

Employee Id Email First Name Middle Name Last Name Gender Contact No Designation Pay Band (VI PAY/VII PAY/Consolidated) Pay In Band G.P. A.G.P. Pay Band Effect Date (DD-MM-YYYY) Joining Date

(DD-MM-YYYY)

Condn For Approval (Regular/Permanent/ Adhoc/Contractual) W.E.F Date (DD-MM-YYYY) Category Name
EMP1151 [[1]] Shrinath Uppal Nagpure Male 7894561230 Assistant Professor 5200-20200 (VI Pay) 50000 0 6000 01/05/2010 25/10/1997 Regular 01/05/2010 Open
                                 

Employee Login Credentials Creation

Advisable to use Genuine email-ID for login credentials because

  • Email ID’s are globally unique
  • Easy to remember
  • System can communicate on that email ID with the student

Suggested to use email-ID which are person specific and not post specific like [[1]]   This is for the reason that against each email ID a persons records are stored. Like his service book records, leave records and all the workflows that he has used. Now if the person with login credentials based on [[2]] resigns and is replaced by another person, who is using the same login credentials, separate records cannot be maintained for two different users with same login credentials.

UNIQUE ID 

Unique ID for Student and Employee should be as per the ORGANIZATION POLICY.

For students it could be Admission Year+Inst+Course+Rollno/GRNO

For Employee a similar scheme could be adopted.

However special care should be taken that after the employee/student leaves the organization the same ID should not be relocated to anyone else.

For creation of Employee Login – Service Book entry is a must.

  • Salary and Leave are connected to Service Book of an Employee
  • Appraisal is also dependent on Service Book of an Employee
  • After the appraisal cycle the action cascades in the service book. It can be one of the following
    • Continuation of services with regular increment
    • Continuation of services with additional increments
    • Continuation of services without any increments
    • Dis-continuation of services.
    • Promotion
    • Demotion
  • Resignation of services is also reflected in the service book of the employee
  • In addition to Salary Calculation, calculation of LTA, Gratuity, PF and all Leave related encashment also depends on service book.
  • No Dues Calculation and relieving letter also dependent on Service Book