DOC 01 RFAS Unipessoal Lda · est. 2020 · rev 2026.07
Engineering consultancy with a digital arm: bespoke tools, automations and dashboards — no subscriptions, no unnecessary complexity.
Table 01 · General data
DOC 02 OTL Portugal
Seven years of Flemish practice in Object Type Library, being transposed methodologically to Portugal. I work at the Flemish road agency designing the model; RFAS is the vehicle to bring it here in time for the 2026–2030 window.
Each service is modular. Hire one, combine several, or start small and expand when it makes sense. Engineering consultancy is the core; everything else connects to it.
Surveys (damp, water infiltration, building pathologies), geotechnics, energy certification in Flanders (Belgium), information organisation and support for project decisions.
Sheet → S·02Proposal generation, email organisation, PDF exports, repetitive workflows — automated in small modules.
Sheet → S·03Reorganised Excel, simple web dashboards, control sheets. Indicators that answer the right questions.
Sheet → S·04Plugins for design software, internal web apps, mobile apps and calculation tools. Small things that save hours every day.
Sheet → S·05Lightweight institutional sites, no heavy CMS and no subscriptions. The client provides domain and hosting; RFAS does the rest.
Sheet → S·06Have a process, a technical problem or a tool in mind that doesn't exist yet? Describe it. If it makes sense and is useful, we build it.
Talk →Two short examples of the kind of problems RFAS usually solves — between engineering and code. The full set is in projects.
Automatic extraction of volumes per space and areas of the envelope elements from the SketchUp model, straight into the EPB energy-certification software of Flanders (Belgium).
CPT test interpretation: segments the profile into layers and proposes a classification for each layer with a confidence level, for review by the engineer. Currently tuned to the Belgian SB260 specification — easily adaptable to other reference standards.
Every project starts by looking at the actual problem — the files, the full workflow — to see whether the simple solution is enough. When it is, we stop there.
Analysis of the situation from concrete examples of the full workflow or problem — real files, sample cases, the end-to-end process.
A short document: scope, timeline, cost. No fine print. No mandatory subscriptions.
Intermediate iterations are delivered along the way. Adjust early, avoid rewriting at the end.
Files, code or tool + a short manual. The client becomes autonomous; support stays available.
Explain in two lines. The reply comes with a practical suggestion — even if it's to say it isn't worth doing.