Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

Introduction

Employee Information System (EIS) basically contains the employee and the related master data. In BPA application, employees of the system play a major role. This document will touch upon the major features of the EIS system, which BPA application, directly and indirectly, is integrated with. Along with the employee, there are other key masters involved in the module like Designation and Position.

Prerequisites 

EIS system will depend on the Infrastructure components of the ERP. For the smooth running of this application infrastructure module, commonly known as EGI has to be up and running.

Functionality

Designation

A state or city will have a set of designations defined for themselves. This can be added or updated using the Designation module. Normally designations are defined at a state-level, however, the system provides the flexibility to have new ones for a specific city.

Position

In each of the departments for each designation, there will be a predefined number of posts. These posts are to be defined in the position master. If any of these posts are vacant the same can be attached to an employee, else it will be termed as a vacant post.

Employee Information

An employee can be created in the application using the Create Employee feature in the system. All basic information along with his/her work assignment details and jurisdiction details can be captured here. When an employee is created, the system internally creates a user. UserId will be provided in the employee screen or it can be preconfigured same like how the password is preconfigured. Any employee created will by default have the role "Employee" and using the userId, this employee can log into the system.

Jurisdiction

Generally, an employee will be responsible for working for a particular location, say a Ward or a Zone. In such case, the jurisdiction will be set to those list of Ward(s) and Zone(s). In cases where one employee's work jurisdiction is for the entire city, then mapping needs to be done at the city level.

Assignment

An employee in the system will be allocated to work for a particular department/designation for a defined period of time. This information is captured in the assignment section. One employee can have one primary assignment and one or more temporary assignment(s) at any point in time.


ParameterDescription
DepartmentDepartment master is part of the Administration module. Select any department in which the employee working 
DesignationSelect the designation with which the employee is working
is PrimaryThis flag true will indicate that this assignment is the primary one (one for which the payroll processing is done). False will indicate they are temporary or secondary assignments.
PositionSelect the position master associated with the employee. This will be listed based on the department and designation selected.
Valid fromFrom the date from which this assignment is applicable
Valid toThe date till which this assignment is applicable.

Configurations and Setup

If a designation master data needs to be set up at the state-level add the insert script for this into the database/main folder, whereas if a department master needs to be added for one specific city and not required in any other cities of the state, add the data into the city-specific folder, say database/<cityname>.

Jurisdiction for an employee is defined based on the "Administration" hierarchy (refer boundary set up).

Support Information

Administration

References and Notes


  • No labels