Skip to content
MCIT Talk to us

Examples Pastéis de Belém

Pastry and confectionery

PdB People: a portal built for people, on top of ELO.

For around 226 Pastéis de Belém staff, a web portal that replaces ELO's interface on the people side, while keeping all of ELO's logic and processing and the facial recognition time clocks.

Pastéis de Belém

ELO carries on doing what it does well. People now have autonomy.

~226staff in ELO
2faces: staff portal and management console
8 + 9modules, in the portal and the console
4write areas in ELO, validated and signed
0copies of personnel data
1single source: ELO, as always

01The client

Antiga Confeitaria de Belém, the home of Pastéis de Belém, manages around 226 staff in ELO, the system that holds personnel data, clock-ins, absences and holidays, and that feeds the payroll information into Primavera.

02The problem

ELO did its job well, but its native portal did not serve people. It was a technical interface, designed for the back office, that gave staff no autonomy at all.

  • Everything went through HR, on paper or by email: holidays, absence justifications, missed clock-ins, payslips.
  • Personal data fell out of date, because updating it meant work for everyone.
  • Rotas lived in Excel or on paper, and there was no internal communication channel.
  • HR was overloaded with requests that staff could have handled themselves.

The path of a holiday request

Before
  1. Staff member
  2. Paper or email
  3. HR
  4. Entry in ELO
Everything went through HR
Now
  1. Staff member
  2. PdB People
  3. Approval in the console
  4. ELO
Request, approval and entry, with no paper

What the client asked for was clear: simple access for staff, on their phone or PC; less pressure on HR, with requests and approvals automated; an internal communication channel; and ELO and Primavera remaining the single source.

03What stayed as it was

Replacing ELO was never on the table. The decision was to keep all of ELO's logic and processing, as well as the facial recognition time clock hardware, and to build a layer on top designed around people.

  • The facial recognition time clocks still record clock-ins in ELO, just as before.
  • The logic and processing remain in ELO, unchanged.
  • Payroll follows the same route as ever: ELO's own export to Primavera.
  • There is no copy of personnel data and no synchronisation: the portal reads directly from ELO.
Stayed as it was reads and writesexportsclock-insapp data Staff memberphone or PC HR and managersmanagement console PdB Peopleweb portal ELOsingle source Primaverapayroll Time clocks facial recognition Supporting databasetickets, rotas, requests

The application's own data, such as tickets, rotas and requests, lives in a separate supporting database, so that nothing is mixed with ELO.

04The solution

PdB People is a web portal that replaces ELO's interface on the people side. It has two faces, each with its own modules, and is in production on the company's own infrastructure.

Staff portal

Sign-in with the NIF, on phone or PC. Personal data, clock-ins and corrections, absence justifications, holiday planner, my rotas, overtime, documents, tickets and announcements.

Management console

For HR, managers and the board. People management, approvals, absence planner, rota planner with a touchscreen viewer, staff documents, tickets, announcements with read rates and performance appraisal.

Connection to ELO

Live reading and four validated write areas: personal data, clock-ins, absence justifications and holidays. Each write is made just as ELO would make it and is signed with the author «PdB-People».

Security was built in from the start: sign-in with the NIF, mandatory password change, lockout after failed attempts, a log of sign-ins, access by module and a separate administration area.

05What changed

The everyday problems, one by one, and what happens now with PdB People:

  • Missed clock-ins Correction request in the portal, approved in the console and written to ELO.
  • Absence justifications on paper Justification submitted in the portal, approved and recorded in ELO.
  • Holiday requests by email Holiday planner in the portal, with approval and entry in ELO.
  • Payslips requested from HR Documents available in the portal, without asking anyone.
  • Out-of-date personal data Staff update their own data and, once validated, it is stored in ELO.
  • No internal communication channel Announcements with read rates, and tickets for everything else.
  • Rotas in Excel or on paper Rota planner in the console, my rotas in the portal and a touchscreen for viewing.
  • HR overloaded Requests and approvals automated, in one place.
  • Scattered performance appraisal Performance appraisal in the console, in a single process.

Less pressure on HR, more autonomy for staff, audited processes, ELO preserved as the single source and an internal communication channel that did not exist before.

The next step: sick leave through the same mechanism as holidays, and more automation in rotas.

ELO remains the source. PdB People is the way to reach it.
The facial recognition time clocks stayed exactly where they were.
Every write to ELO is signed: «PdB-People».
Client
Pastéis de Belém
Sector
Pastry and confectionery
Technologies
  • ELO
  • Primavera

Inside

PdB People, screen by screen.

The main features of the staff portal and the management console, as they run in production.

Staff portal

The home screen: everything a staff member needs, on a single screen.
The home screen: everything a staff member needs, on a single screen.
The day's clock-ins, read from ELO, with the hours recorded and the balance.
The day's clock-ins, read from ELO, with the hours recorded and the balance.
The days with missing clock-ins, ready to be corrected.
The days with missing clock-ins, ready to be corrected.
The team's holiday map, with upcoming absences.
The team's holiday map, with upcoming absences.

Management console

The console: people, absences, rotas, approvals, documents and appraisal.
The console: people, absences, rotas, approvals, documents and appraisal.
People management, with each staff member's section and account status.
People management, with each staff member's section and account status.
Clock-in corrections awaiting a decision, before they go to ELO.
Clock-in corrections awaiting a decision, before they go to ELO.
The absence map for the whole company, with holidays and absences.
The absence map for the whole company, with holidays and absences.
Performance appraisal: who appraises whom, and each appraiser's progress.
Performance appraisal: who appraises whom, and each appraiser's progress.

Screenshots of the production system. Names and identification numbers have been replaced with fictitious data.

Does your system do the job well, but your people cannot use it?

We build the missing layer, designed around the people who use it, without replacing the system that already works or duplicating the data.

Talk to us All examples