Beruflich Dokumente
Kultur Dokumente
Enterprise Version
eFront
Enterprise Version
EPIGNOSIS LTD
44, Katehaki, Athens, Greece, 11525 &
Patras Science Park, Stadiou Str, Platani, Patras, Greece, 265 04
email: info@epignosis.com.gr, info@efront.gr
phone: (+30) 210 6756008, (+30) 210 6756112
Fax: (+30) 210 6756527
CONTENTS ............................................................................. 3
IMAGES LIST .......................................................................... 5
1. INTRODUCTION .................................................................. 7
2. CONCEPTS AND FEATURES ................................................... 7
2.1 USERS - EMPLOYEES ................................................................... 7
2.1.1 Roles ......................................................................................... 7
3.4 SKILLS................................................................................... 21
3.4.1 Skills review ............................................................................. 21
The core eFront platform supports three basic user roles: Administrator, Professor
and Student, with each role having a different interface. The organizational
component retains the same user categorization, but adds a second level of user
differentiation, namely the one regarding their role in the company hierarchy. In
this respect, users (or from this point on employees), are divided into three
categories: Administrators, Supervisors and Employees. The first role has actually
the same meaning as in the learning component of eFront: it gives access to
every operation and management of any other employee. The other two roles are
defined for each employee when jobs are assigned to each of them. A Supervisor
has administrator rights to any employee of the branch where he is assigned as a
supervisor, as well as to all of its sub-branches. Moreover, a large subset of the
Administrator HCD-related functionalities is also provided to a supervisor. On the
other hand, users that have the role of an Employee, have limited access, which
mainly relates to information flow and communication means from and to the
upper levels of the organization hierarchy.
• Every time an employee loses his or her supervisor role in a branch, then,
unless that employee is a supervisor at a higher level in the organization
hierarchy, all supervisor rights to the sub-branches, where that employee
does not have supervisor placements, are recalled.
An efficient HCD system needs to maintain many more information for each
employee than the name, surname and email data, maintained by the learning
component of eFront. These attributes are divided into temporal and non-
temporal data as shown in table 1.
Non-temporal Temporal
All users have access to their personal record and are allowed to edit some of
their data. This access is granted through the “Personal Data” link under the
“Tools” tab of the left side frame. More specifically, employees are allowed to edit
their records, but cannot change the following pieces of information:
• Job descriptions
• Wage
• National service
The notion behind this discrimination is rather obvious: each user of the system is
allowed to edit his personal records, but not any of those that affect his position
in the company or in the educational process.
2.4 SKILLS
The skills management is of critical importance to an HCD system. Knowing the
current skill-set of an employee, correlating skills to job descriptions, training
employees to acquire new skills and identifying the most suitable employee for
each job assignment according to his skills are some of the most useful features
offered by this module. Administrators and supervisors are thus able to evaluate
skill shortages in the current personnel of the company and try to plan training
programs to improve the level of their employees and consequently the total
quality of the organization.
When an employee has a skill then the latter is assigned to him or her together
with a specification that describes how the employee is related to skill. For
example an employee may be assigned the skill “Work experience” and use as
specification “2 years of work experience as desk salesman”.
2.5 EVALUATIONS
Another important feature of the eFront Enterprise™ is evaluation management
for the system’s employees. This enables administrators and supervisors to add
any kind of positive or negative comments for staff members,
the evaluations of other supervisors. This feature offers thus invaluable
information on the profile of each employee, facilitating the personnel
management from the Human Resources Manager of a company.
2.6 HISTORY
The system offers a history mechanism for all employees of the system. This
entails keeping a diary-like record for each employee, containing information like
date of hiring, job assignment or reassignment, acquisition of skills, lesson
subscription, wage change etc. The supervisors of each employee have
permission to review this record, get a fast preview of the employee’s history in
the company and reach decisions regarding future promotions, wage raises etc.
The file manager module bears several file system functionalities like creating
new subfolders, renaming files and copying or moving files to different folders.
Finally, folders and files can be zipped into compressed files for archiving. The
interface of the file manager for the contents of the publicly available folder is
shown in image 5:
• Professors can see and add both Educational and Organizational events.
The Educational events regard the lessons that they teach.
• Students can see both Educational and Organizational events, but can only
add Organizational events. The Educational events regard the lessons that
they attend.
Clicking on the calendar link, redirects the user to a page created only for
calendar management, as shown in image 7. On the upper right corner of the
page appears a drop down menu with two values: Educational and Organization
profile. Hovering the mouse over the calendar shows the events for each day that
correspond to the current view only.
Clicking on the “Add Event” link over the calendar on the left opens a popup,
which allows insertion of events. A drop down menu in this popup designates
whether the new event will refer to a specific lesson (Educational) or to the
Organization profile of the calendar. A user-friendly “Submit and add another”
button is provided to allow multiple consecutive calendar event insertions.
Obviously, these links point to the pages that correspond to the five of the seven
distinct functionalities of the eFront Enterprise™, as described in the previous
chapter. The evaluations and history functionalities are managed and previewed
respectively at the “Employees” page.
3.2 BRANCHES
3.2.1 Branch Review
The first page that is shown to the employee when he selects the “Branches” link
is a list of all registered branches. Each branch is listed together with its location,
the employees that work in it and its father branch as shown in image 10.
Clicking on the name of a branch, or the “Edit” icon underneath the “Operations”
column links to the “Branch editing” page (chapter 3.2.3). Otherwise, clicking on
the “Delete” icon under the “Operations” column, deletes the branch and all of its
sub-branches in the organization chart after a positive response to a relative
confirmation question.
The first task an administrator needs to perform regards the insertion to the
system of the branches that comprise the organization hierarchy. This is done by
clicking on the “New Branch” link on the top left corner of the –initially empty-
branches list. The form used to perform this operation, which is shown in image
11, allows the insertion of location information, contact data as well as positioning
in the company hierarchy, through definition of the father branch of the newly
inserted branch. Each branch has zero or one father-branches, an approach which
renders the organization chart as a tree with (potentially) multiple roots. Finally,
if the assignment of a father branch will create a circular chain in the hierarchy,
then it will be perceived as illegal by the system and disregarded.
Image 12 shows the branch-editing page. The initial page shows the registered
branch data, which can be changed and re-submitted, and below a list with all
employees currently assigned to the branch. The other three tabs on top of the
page perform the following tasks:
• Sub-branches: A form same as the “Branches List” page of Image 13, having
an “Insert Sub-branch” link on top of the list, which points to a form like the
one shown in Image 11. Upon submission of the new sub-branch the user will
automatically return to the branch-editing page.
• Job descriptions: A form that lists all job descriptions that have been defined
for the branch. If no job descriptions are defined, then no employees can be
assigned to a branch, since all assignments are done when an employee
acquires a job placement at a branch. A “New Job Description” link enables
administrators to directly add a job description to this branch and return after
its submission to the branch-editing page.
The organization chart is accessed through the link with the same name on the
administrator’s control panel. The chart (Image 16) shows all branches with their
All job descriptions are shown in the job description list, which is the first page
linked by the “Job descriptions” link on the control panel of the administrator.
Next to each job description appear the name of the branch to which this
placement belongs, the number of employees assigned this job, the vacancies for
this job description and the skills required by it. The number under the vacancies
column refers to the difference between the “Vacancies” number inserted into the
respective field on the job description insertion form (see chapter 3.3.2) and the
number under the “Currently employed” column. The last column provides links
to the two operations on an existing job description: editing and deletion. Editing
a job description is explained in chapter 3.3.3. On the other hand, deleting a job
description, removes the specified job from that branch, after a positive response
to a confirmation question. It is noted here, that the deletion of the job
description “Salesman” from a branch, does not affect other jobs described as
“Salesman” at different branches.
Job descriptions can be inserted either to a single branch all to all branches of the
organization. As mention in chapter 2, the same job description can be
differentiated for different branches, thus offering maximum customization per
branch needs. However, for efficiency and user-friendliness, the functionality of
adding the same job description to all branches is also provided, by selecting “All
branches” from the drop down menu next to the “Branch Name” field, as
demonstrated in image 17.
For example, in image 18 the “Vacancies” field for the “Manager” job description
at the “Head Department” branch equals to 1. However, 1 employee is already
assigned to that job description. Therefore, the number for the “Vacancies”
column regarding that job description equals to 1 minus 1, namely zero. The skills
required is the sum of all skills that are set as prerequisites for each job
placement, through the process described in chapter (3.3.3)
Editing the data of a job description entails changing any of the information
stored for that placement at the designated branch. It is worth mentioning, that if
the “All branches” choice is selected from the drop down menu next to the
“Branch Name” label, then the change will affect all job descriptions at all
The next tab in the job description-editing page is used to correlate job
descriptions to skills. This happens with a user-friendly method, which registers
this assignment or re-assignment with a simple click on the corresponding skill.
The same method, where a simple click on the checkbox immediately makes the
assignment without any submission button, is used in the third tab called
“Associated lessons”. This tab provides a list of all registered lessons to the
system. Next to the record of each lesson appear the category it belongs to, the
language used for it as well as the number of skills provided upon completion of
that lesson. This assignment of skills to lessons is explained in chapter 3.6. If no
skills are offered then a relevant message is shown for this lesson. The final
column contains a checkbox: upon checking it, the job description under editing is
correlated to that lesson. Un-checking a checked lesson dissolves that
relationship.
3.4 SKILLS
3.4.1 Skills review
Though branches and job descriptions suffice to provide the basic eFront
Enterprise™ functionalities, like job assignments and employee management,
skills have a very significant role as well. Management of skills is one of the most
important tasks a human resource manager needs to perform, and therefore it is
suggested that a basic set of skills is inserted into the system as a third step,
before the employees’ accounts are created. Skills can be very easily registered
to the system, since all that needs to be provided for each of them, is a general
description, like “Work Experience”, degrees like “Bachelor” or “MBA” or soft skills
like “Intelligence”, “Diligence” or “Communicative”. When an employee is actually
assigned a skill, then an appropriate text specification is also entered. For
example, the specification for an employee having “Work Experience” could be “2
years programmer, 3 years project manager”.
Skills can be edited either be clicking on their description link anywhere it can be
found in the eFront Enterprise™ environment or by clicking on the “Edit” icon
under the operation’s column on the skills’ list. The form that appears is shown in
image 24. Changing and submitting the value next to the “Skill Description” field
alters the name of the description, wherever it appears. Underneath the submit
button, exists a list of all employees currently possessing that skill together with
the specification given for each of them. Special attention needs to be given to
the “Operations” column on the right side of the table: the “Edit” and “Delete”
functionalities refer to this skill being assigned to the employee of each record.
This means that clicking on the edit icon will redirect the administrator to the
employee-editing page (chapter 3.5.3) and more specifically to the “Skills” tab.
The second tab of the skill-editing page is used to massively assign skills to
employees. Each time an employee is selected from the list by clicking on the
corresponding checkbox under the “Check” column, the specification field will
appear and the administrator may insert the relevant piece of information. If an
employee that already has the skill assigned is un-checked then this skill is
removed from his or her skill set, when the “Apply Changes” button is clicked.
Finally, the administrator may change the specification of an existing skill
assignment to an employee by changing the corresponding field. This process is
3.5 EMPLOYEES
3.5.1 Employees review
Having inserted branches, job descriptions and skills the administrator is now able
to insert employees into the system with all functionalities enabled. Otherwise, if
branches or job descriptions are not defined, then though employee accounts
may be created, no job positions can be assigned. On the other hand, if no skills
The main page of the employees’ management part of the eFront Enterprise™
is linked by the “Employees” link on the administrative control panel and shows a
list of all registered employee accounts. Every record of the table shows the login
name of the user in the eFront system, his or her actual name and surname, the
preferred language for the system and the number of job assignments in all
branches. Three more columns are provided for each record, which correspond to
four different functionalities: the first enables or disables an employee account in
the system. The second, under the column “Reports”, shows employee statistics,
while the other two refer to the “Edit” and “Delete” operations, presented in the
previous chapters as well. Editing an employee will be explained in chapter 3.5.3.
Deleting an employee, entails removing all employee data from the system: job
descriptions and skills assigned, evaluations and history, as well as any piece of
personal information on that employee account. Since this operation incurs such a
change to the system, a confirmation window is used to ensure the administrator
selection. As always, over the top left corner of the table, exists the “New
employee” link, which leads to the creation of a new employee account, as
explained in the following chapter.
Clicking on the “New employee” link leads to the employee insertion page, which
contains a form with extended info fields for each employee. Though the actual
number of information fields is about thirty, only five of them are required:
If branches have already been inserted into the system, before the employee’s
account creation, then the administrator is able to assign a job description right
away, during employee insertion to the system. This approach facilitates the
It must be underlined at this point that each employee is still assigned with a role
relevant to the learning part of eFront, namely “administrator”, “professor” or
“student”. As for the role regarding the organizational aspect of each employee, it
is determined according to the following three rules:
• If a user has a learning role of an “administrator” then this user also has
an administrative role in the HCD aspect of the system
Every time an employee’s login is encountered in the system it has the form of a
link. Clicking on it, redirects the administrator to the page of editing the
employee. The first tab of that page is the same with the one of image 27,
whereas each piece of information registered during employee creation appears
next to the corresponding fields. Any field value may change, thus leading to the
same alteration upon form submission. If branches are defined, then selecting a
branch and a job description make this assignment to the employee, when the
form is submitted. If the employee already had a job description then:
• changing the job description to an empty value removes the existing job
from the employee.
However, each employee may have more than one job description in more than
one branch. Therefore, the second tab of the editing page enables assignments of
more jobs to the employee, by one job at every submission. As shown in image
22, that tab contains a table with all job descriptions the employee currently has,
together with the role for that placement. Two operations are permitted here:
The third tab offers the employee to skills management feature. More specifically
all registered skills of the system are shown and next to each one that is
possessed by the employee, exists a specification and a selected checkbox. If the
specification changes, then the respective skill assignment to the employee
changes as well. If an unchecked record is checked, then this skill is assigned to
the employee, while if the opposite occurs then the skill is removed from the
The next tab in the employee-editing menu regards the evaluations and the
history of this employee. Both concepts have been thoroughly explained in
chapters 2.5 and 2.6 respectively and are shown in image 4. It is important to
remind that the history table is not editable in any way: no records can be
inserted or deleted. On the other hand, evaluations are manipulated in the same
way as any other entity. A list of all evaluations together with their subject and
author name is listed chronologically. On the rightmost column called
“Operations” exist the “Edit” and “Delete” icons, which provide the corresponding
functionalities. Administrators are allowed to view and change any evaluation, a
fact that is not true for supervisors, which can only modify their own evaluations,
as we will see in the next chapter. Moreover, over the top left side of the
evaluations’ table exists the “New evaluation” link, which redirects to a form for
adding the data for the new evaluation. This form, used by both “New evaluation”
and “Edit” links, is shown in image 30.
The fifth tab is the “File Record”, which provides the File Manager interface to the
administrator. The administrator can interact with every employee in four ways:
The next tab is the “Employee Form”, which shows a digest of the employee’s
record as explained in chapter 2.8. The following tab provides User Groups
management. A list with all user groups is shown and the administrator can
Users that belong to the same User Group can be automatically assigned with the
same skills, job descriptions or lessons.
The final two tabs of the employee-editing page regard the lessons and the
courses that the employee under review is attending or can select respectively.
Since the administrator defines lessons and course assignments, this is one of the
two places in the eFront Enterprise™, where this operation can be performed.
Both tabs are divided in lessons and courses and enable an administrator to
assign or remove a lesson or a course from an employee, by selecting or un-
selecting the correct checkbox. This interface is shown in the image below.
Under the Employees tab on the left hand sidebar frame, you can fine the “Search
for employee” link. This points to a page, which enables the administrator to find
all employees that fulfill several criteria. The administrator can select whether all
criteria or at least one must be fulfilled in order for the system to return an
employee record. This is done with a radio box, with two selections: “Satisfy all
criteria” and “Satisfy any criteria”. Underneath the radio box, exist three drop
down menus, which correspond to the criteria for branches, job descriptions and
skills. Every time a new value is set in any of these menus, the page reloads and
the employees fulfilling the determined criteria are presented as a list.
Furthermore, the page consists of a second tab, which has all fields that describe
an employee as shown in image 27. The administrator can fill in any of those
fields and submit the “Advanced criteria” form. From this point all subsequent
searches will take into account the values of the fields completed. It goes without
saying that, even when advanced search criteria are set, the “Satisfy all criteria”
and “Satisfy any criteria”, continue to apply.
3.6 LESSONS
Lesson and courses management is a core of the Standard eFront Edition.
Nevertheless, the correlation of lessons and skills that applies in the
organizational aspect of eFront leads into a relevant extension for the Enterprise
Edition. Therefore, a new tab is added in the lessons management page, pointed
to by the “Lessons” link under the “Lessons” tab on the left hand sidebar frame.
This tab, which is shown in image 34, allows administrators to associate lessons
and skills, together with skill specifications. This implies, that upon successful
completion of the lesson, all attending employees will acquire each skill selected
here together with its specification. If the employee already has one of the
associated skills, then the specification on his skill is extended with the one
provided for the skill acquired by the lesson. For example, if a user has the skill
“MS Office Knowledge” with specification “MS Word and Excel” and attends a
lesson “Databases” with skill specification for “MS Office Knowledge” “MS Access”,
then the final specification of this employee for the skill after the completion of
the “Databases” lesson will be “MS Word and Excel, MS Access”.
The difference between the administrator and supervisor types regards the fact
that supervisors are less involved with system operations. Therefore, they do not
have any access rights on lesson or skill management operations, as the
administrators do. Since the two types are very much alike, the following
presentation of the supervisor type will only mention the differences from the
operations mentioned in chapter 3 for administrators.
As will be clearer from the following presentation the basic logic behind every
supervisor management operation is that it is limited to the branches that he or
she supervises. The same thing applies for branches, job descriptions and
employees. It is worth mentioning here that the eFront Enterprise™ is designed
in such a way, so that it facilitates the correct usage of the functionalities from
supervisors, by limiting their choices of branches with the use of drop down
menus, with predetermined values.
4.2 BRANCHES
Supervisors are allowed to view all registered branches in the initial branches list
or the organization chart. However, they have permission to edit only the ones
they supervise. Moreover, another significant difference with administrator
branches’ management is that, though a supervisor can still add a branch into the
4.4 EMPLOYEES
Employee management varies somehow from the branches and job description
one. The first difference is that the initial list of employees does not contain all
employees and limits access to the ones supervised, but only shows the latter
group. This means that a supervisor will be oblivious of the existence of an
employee that works at a branch on a higher lever of the branches hierarchy, a
reasonable choice considering that there is no need for the supervisor to know
this piece of information. On the other hand, if an employee is not currently
assigned to any branch, then the supervisor is allowed to view the data and
designate job descriptions to that employee.
Another difference is that employees inserted or edited by the supervisor can only
be assigned a placement in one of the branches that supervisor supervises. It is
worth mentioning, that these assignments can also involve assignments of
employees to job descriptions as supervisors. In other words, supervisors have
the ability to “create” other supervisors. Nevertheless, these supervisors will have
at most the same access rights as the supervisors that created them.
Since supervisors are not allowed to add skills, the “New Skill” link is missing
from the employee editing at the employee-to-skills tab.
Another difference regards the evaluation tab of the same page. Though
administrators have access and management rights on every evaluation, this
feature does not apply for supervisors, which are allowed to edit or delete only
their own evaluations. However, they still have permission to view evaluations
regarding a specific employee from other administrators or supervisors, as long of
course as they supervise this employee.
5.2 EVALUATIONS
In other words a user of type “Employee” cannot edit any other employee-
records, branches, skills or job descriptions. There exists only one exception to
that rule: if an “Employee” has the educational role of a “Professor”, then that
user may add evaluations to the users that attend this employee’s lessons. This
functionality is offered at the “Certificates” option on the lesson management
control panel. This is the menu that appears once the professor clicks on the
name of a specific lesson he or she teaches. Clicking on the “Certificates” link
leads to the page of image 37. Under the rightmost column, called “Functions”,
exist three operations regarding certificates. The leftmost option provides the
functionality of adding a new evaluation to the employee of that record, through
the form of image 29.
• Only recipients defined in the field below: The message will be sent
only to the recipients whose logins are completed in the “Additional
Recipients” field on the lower part of the page (which uses an auto
complete service to facilitate this process).
• All active system employees: All system users who have their account
activated by an administrator or supervisor.
• Employees with skill: All employees that possess the selected skill,
indifferent of the specification describing this assignment, will receive that
message
• Employees involved with lesson: All employees that are involved with a
lesson, either as professors or students are going to receive the message.
• Specific type of employee: The message will be sent to all system users
belonging to the selected system type.
The lower part of the “New message” page is similar with the one of the Classic
Edition eFront. The additional recipients field is completed via auto complete, with
employee logins, separated with semicolon, or with ‘%’ to be sent to all
employees or ‘[*]’ to be sent to all students of the current user, if that user is of
a “Professor” type. Finally, the eFront Enterprise™ offers the option of sending
this message as an email as well, using the email addresses that have been
provided for the employees.
7. TECHNOLOGIES
eFront Enterprise™ is based on the following technologies:
3. Usage of web technologies and protocols: TCP/IP, HTTP, HTML, DHTML, PHP,
AJAX, SCORM, LDAP, UNICODE
6. Small web pages to lower bandwidth requirements and facilitate the efficient
eFront system usage even for dial-up connections
7. Data integrity and system security through access control mechanisms for the
Information System (usage of login/password for each employee)