Your browser doesn't support the features required by impress.js, so you are presented with a simplified version of this presentation.

For the best experience please use the latest Chrome, Safari or Firefox browser.

Decentralized HRM in Public Service
 -
 The CNR Approach
{Marco.Andreini, Cristian.Lucchesi, Alessandro.Martelli,
 Maurizio.Martinelli,Dario.Tagliaferri}@iit.cnr.it
Who are we?
How many people are we?
  • CNR employs more than 8000 people grouped by title and category
  • It's made up of the headquarters in Rome and 108 research institute
How are we structured?
  • Each institute has a partial authonomy in the personnel management
    of its staff and equipment.
  • It prompts the need to flexibly manage the data
    (concerning staff attendance, reason of absences etc...)
  • CNR is the largest Italian research body
  • It spreads across Italy
Introduction
In line with other Public Administrations, CNR adopts an ERP
(Enterprise Resource Planning) to:
  • meet the needs of system integration
  • increasing demand for real-time information
  • integration of information systems (local and central in this case)

We present a federated and distributed architecture:
  •  the head office provides common services
  • the institutes use them to supplement their local information systems

In these slides we describe the functioning of one of these components:
the attendance detection system called
ePAS (electronic Personnel Attendance System)
General architecture
Is based on two types of software systems:

  • CNR centralized systems containing the common denominator of all 
    the necessary informations for each employee
    (name, number, contract data, qualification etc...)
  • Local systems locally integrate all data that are specifically of interest
    to the local office (stampings, location in institute, absences, etc....)
The purpose of this distributed architecture is: 

  • standardize the information and workflows necessary to the central
    office for its administrative tasks
  • to ensure a high degree of flexibility for the institutes
Why CNR needs ePAS?
  • CNR has a lot of different institutes and each one has a different need in
    personnel data processing.

  • Every institute need to count presences and absences of their employees 
    and each employee's category (researchers, technicians...)
    needs a different processing.

  • Also managing paper data could be hard for a great number of people.


  • We provide a free solution in order to help institutes budget
ePAS helps managing all this processes and data
in homogenous and organized way
The model
  1.     Every institute has a different deploy of ePAS and detect its own daily stampings.
  2.     All personnel information are saved on local databases.
  3.     Every month administrative staff can link ePAS to Cnr central repository to send
    employees informations
How is it done? - ePAS architecture
Administrator:
  • insert/update/delete people
  • insert stampings/absences
  • manage competences
  • check if person is at work or not
  • control meal ticket situation
  • manage vacations situation
  • send attendance certificates
Simple user:
  • check daily stampings
  • verify yearly absences
  • verify monthly absences
  • check vacations recap
  • insert training hours
  • manage password
The usage of roles
How to detect stampings?
via RESTful
via web
{
 "tipoMatricolaFirma": ["matricolaCNR",   
 "idTabellaINT", "matricolaBadge"], "anno": 2014, 
  "giorno": 15, "lettore": "08", "minuti": 12, 
  causale": "", "matricolaFirma": "XXXX", 
  "operazione": "00", "mese": 9, "ora": 12 
}


Other detection systems based on Iris or Biometric
recognition could be integrated developing a
specific ePAS REST client
Sending attendance certificates
The headquarters provides the "Certificates" portal for the submission of
information regarding the attendance of employees, in particular:

  • justified absences of each employee
  • competences
  • the number of monthly meal vouchers
  • the number of training hours
  • staff overtime, work shifts, staff availability
every month ePAS sends this information
to the Certificates portal
This information is used to provide essential data to the CNR payroll
management system
How to interact with ePAS??
Via RESTful!!!
How is it implemented?
ePAS is totally based on open source software.

It will be released as OS within the CNR:
  • to ensure a reduction of costs
  • in order to receive improvements or new features


ePAS diffusion
Currently it has been deployed in 5 institutes
Conclusions
Nowadays the organizational structure of several public organizations:
  • tends to be more complex (fragmented departments)
  • affect the ability to identify appropriate process owners
The solution proposed falicitate the integration of information systems that are
different but closely connected.

Each office/institute is owner of the process and info associated with its own
personnel.

ePAS interacts with central site in a homogenous and organised way by means of the
common REST software and services.

This distributed approach could be taken in consideration by each organization
with multiple location and many decentralized departments.
Future works...
Workflow paperless system
Man -hours in the accountancy of projects
(particularly those of the EU)
ePAS doesn't want to become a cumbersome application, but rather to integrate
with other applications using the API REST...
Thank you for your attention!
Any questions?

Use a spacebar or arrow keys to navigate