ERES Facility Portal.
Operations portal running daily at ERESfacility — 39 DB tables, 45 permissions, PWA for field technicians. Live since 2025.
Roles
UI/UX Design Full-Stack Development Database Architecture DevOps & Deployment API DesignProblem
ERESfacility had outgrown shared spreadsheets. Operations teams were tracking service schedules, contracts, and client reporting across a handful of uncontrolled Google Sheets. Duplicates appeared weekly. Month-end client reporting ate a day of manual consolidation. The owner, Dr. Ján Pavlis, wanted a single operational portal — but refused to hand it to an agency that would disappear after launch.
ERES manages refrigeration and cooling equipment across multiple client locations. They needed a centralized system to track equipment, manage maintenance schedules, handle compliance documentation, and coordinate field technicians — replacing a patchwork of spreadsheets and paper forms.
Approach
One discovery call, three sharp questions, one architecture proposal. Laravel 11 + Filament 3 admin + Postgres — boring, mature, hireable stack. The Filament admin meant Dr. Pavlis could customise forms and views himself after launch without waiting on a developer. Real-world data migrated in the first week so every subsequent feature was built against real records, not synthetic fixtures.
The multi-tenant architecture ensures each client's data is isolated while giving ERES administrators a unified view across all accounts.
What's in it
- Multi-tenant architecture — data isolation per client, unified ERES admin view.
- 39 database tables across 10 core modules — equipment, contracts, schedules, tasks, documents, users, audit, billing, reporting, and compliance.
- 45 role-based permissions — granular access control with full audit trail.
- Equipment lifecycle tracking — every cooling/refrigeration asset tracked from install through service to decommission.
- Maintenance scheduling and compliance — recurring service patterns, conflict detection, automatic technician assignment.
- PWA for field technicians — offline-capable, GPS-tagged photo evidence, timestamp verification.
- Document generation and management — contracts, service reports, invoices, with version history and e-signature workflow.
Inside the portal
The dashboard after sign-in. Active contracts with a trend line, expiry warnings, and the weekly maintenance calendar. One screen tells the admin what must not slip this week.
The contracts register. Customer / supplier / active / expiring tabs, per-row status and priority badges, responsible person, term (1- to 5-year), validity and value. This is the module that replaced the main spreadsheet.
Performance records — the heart of monthly reporting. Every record carries plan vs. actual in both hours and euros, a type (delivered services, maintenance, audit), an out-of-scope flag and an approval state. What used to be a day of manual consolidation is a filter plus an export here.
Documents tied to contracts — delivery notes, invoices, inspection reports, photo documentation, scanned contracts. Categories, reporting month, confidential / signed flags. Compliance paperwork stopped living in e-mail attachments.
The multi-tenant organisations register — customers, suppliers, auditors. Each organisation has its own users, contracts and isolated data; Excel/CSV export straight from the table.
Users with per-organisation roles — administrator, customer, supplier, auditor. Under the roles sit 45 granular permissions on Spatie Permission; invite-based onboarding with e-mail verification.
The report generator — type, period, optional organisation, generate. The monthly client report that used to eat a full day is a four-field form.
Tech stack
- Backend: Laravel 11, PHP 8.3
- Admin UI: Filament 3 (TALL stack), Livewire, Alpine.js
- Database: PostgreSQL with complex relations
- Auth: Spatie Permission with 45 permissions
- Storage: Document storage with image processing
- Deploy: Production server, PWA-enabled
- Caching: Redis
Outcome
Three months from kickoff to production. Running daily since 2023. Live since 2025, daily usage. Month-end reporting dropped from a full day to ~30 minutes. Two internal staff trained to administer the portal without me.
| Metric | Outcome |
|---|---|
| Admin time reduction | 70% |
| DB tables | 39 — most complex in portfolio at the time |
| Production status | Active, daily usage since 2025 |
| Staff trained | 2 internal admins independent of me |
The portal is also the reference I point other ops-software prospects at when they ask "could you build something like this for us?" — yes, and here's who runs it daily.
Our experience at ERESfacility, and mine personally as managing director, with Norbert has been entirely positive. Highly professional approach, responsible and accommodating when meeting agreed deadlines. The price for his work was very acceptable for our company. Our ERESfacility portal gives our clients a perfect 24/7 overview of the outsourced facility-management services we provide. It positions us in an entirely different place relative to the competition. Having seen similar portals, I can say ours is unique. I warmly recommend the programming services provided by Norbert Kovalčín.
Dr. Ján PavlisManaging Director · ERESfacility s.r.o.Pick
a week.
I'll have it live
the one after.
No slot fits? Send a brief →