@prefix s: . @prefix d: . d:AD d:has-category "Databases"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "AD". d:ADFS d:has-category "Authentication"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "ADFS". d:AWS d:has-category "IaaS / Container orchestration"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "AWS". d:Accelerometers d:has-category "Sensors & measurements"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Accelerometers". d:Android d:has-category "Mobile"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Android". d:Angular d:has-category "Web frameworks"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Angular". d:has-category "Scheduler"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Apache Airflow". d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Apache Jena Fuseki". d:description "Dockerized Apache Jena Fuseki distribution with built-in GeoSPARQL support, Lucene indexing, Apache SIS EPSG tooling, and production-oriented defaults for serving spatial RDF data."; d:during-job ; d:external-link ; d:has-category "Semantic"; d:has-linked-projects , ; d:has-tagged-roles , d:Developer; d:has-tagged-techniques , d:Docker, d:GeoSPARQL, d:GitHub; d:is-featured "No"; d:public true; d:type d:Project; s:name "Apache Jena Fuseki GeoSPARQL". d:has-category "Data analytics"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "Apache Spark". d:has-category "Webservers"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Apache http server". d:Arduino d:has-category "Micro computer"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Arduino". d:description "A backend processing system to identify railway assets on pictures taken by camera's on measurement trains. The results help in creating inventories and manual digital inspection. The goal is to also categorize assets according to their state (health/worn..)"; d:during-job ; d:has-category "Image processing"; d:has-linked-projects ; d:has-tagged-roles , ; d:has-tagged-techniques , d:Dbeaver, , d:Postgresql, d:Railway, d:S3; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Asset recognition on images from measurement train". d:Asset360 d:description "A data platform combining all asset data, setting the golden record and creating the foundation for a data centric landscape."; d:during-job ; d:has-category "Data platform"; d:has-linked-projects , ; d:has-tagged-roles , ; d:has-tagged-techniques , , , , d:Dbeaver, d:Postgresql, d:Python, d:Railway; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Asset360". d:has-category "GIS & topology"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "AutoCAD suite". d:description "A backend system to automate data transfers from several databases. Using several techniques such as delta transfer or ID based copying."; d:during-job , , ; d:has-category "Data processing"; d:has-tagged-roles , , , d:Developer; d:has-tagged-techniques , d:Dbeaver, d:Git, , d:Kerberos, d:Loki, d:MSSQL, d:Openshift, d:Oracle, d:Postgresql, d:Quartz, , d:SAS, d:Serilog; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Automated data pipelines". d:Azure d:has-category "IaaS / Container orchestration"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Azure". d:BaneNor d:external-link ; d:type d:Company; s:name "BaneNor". d:Binary d:has-category "Data models"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "Binary". d:audience-size 10; d:during-job ; d:external-link ; d:format "Online webinar"; d:is-featured "Yes"; d:public true; d:type d:Talk; d:year 2026; s:name "Building a Railway Knowledge Graph with SPARQL Anything". d:has-category "Data & IT role"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Role; s:name "Business analyst". d:description "Track layout is one of those fundamental asset data sources on which most other railway assets depend. Having a healthy data delivery of this information is therefor required. This project implemented changes in the business process to accommodate this data delivery."; d:during-job ; d:has-category "Business process"; d:has-linked-projects d:Asset360; d:has-tagged-roles , ; d:has-tagged-techniques , d:LandXML, d:Railway; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Business process for track tracé data delivery". d:has-category "Programming languages"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "C#". d:has-category "Programming languages"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "C++". d:CEB-BEC d:external-link ; d:type d:Company; s:name "CEB-BEC". d:CSV d:has-category "File format"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "CSV". d:Caddy d:has-category "Webservers"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Caddy". d:Camera d:has-category "Sensors & measurements"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Camera". d:description "We installed over 16 camera's on a measurement train to inspect the overhead contact line system from multiple perspectives. The camera's are triggered based on distance travelled. The images are timestamped and the server time is synced with a Stratum 1 local NTP server. In post processing, the location of the images is calculated. The images are used for digital inspection of the system, both manual (using a webapp) and automatically (using AI)."; d:during-job ; d:has-category "Measurement system"; d:has-linked-projects , , , , ; d:has-tagged-roles , d:Technician; d:has-tagged-techniques d:Camera, d:Laser, d:NTP, d:Railway, d:S3, d:SSH; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Camera inspection system for OCL". d:Certifer d:external-link ; d:type d:Company; s:name "Certifer". d:description "A full stack application to manage change context inside the topology management system."; d:during-job ; d:has-category "Webapp"; d:has-linked-projects d:Asset360, , , ; d:has-tagged-roles , ; d:has-tagged-techniques , d:Git, , , d:Python, d:RDF, d:Railway, d:SHACL, d:SPARQL, d:VueJs; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Change context management application". d:ClickOnce d:has-category "DevOps"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "ClickOnce". d:Cloudflare d:has-category "Networking"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Cloudflare". d:CogniZone d:external-link ; d:type d:Company; s:name "CogniZone". d:has-category "Leading roles"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Role; s:name "Company representative". d:description "A hardware system using camera's and lasers mounted on a pantograph to measure the thickness of a wire. The results are very important to optimize maintenance and renewal and avoid catenary incidents."; d:during-job ; d:has-category "Measurement system"; d:has-linked-projects , , ; d:has-tagged-roles , , d:Developer, ; d:has-tagged-techniques d:Camera, d:Laser, , d:Railway; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Contact wire thickness measurement system". d:description "A solar/battery powered hardware system mounted in the catenary, measuring the vertical movement of the contact wire at the passage of a train. Everything was designed, assembled, programmed, ... by myself."; d:during-job ; d:has-category "Measurement system"; d:has-linked-projects ; d:has-tagged-roles , d:Developer; d:has-tagged-techniques d:Arduino, , d:GSM, d:Git, , ; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Contact wire uplift measurement system". d:description "A strategic model to estimate and compare costs for decision-making and enterprise reporting."; d:during-job ; d:has-category "Strategy"; d:has-linked-projects , ; d:has-tagged-roles , ; d:has-tagged-techniques d:Excel, d:PowerBI; d:is-featured "No"; d:public true; d:type d:Project; s:name "Cost model". d:DSMR d:has-category "Sensors & measurements"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "DSMR". d:has-category "Data & IT role"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Role; s:name "Data analyst". d:has-category "Data & IT role"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Role; s:name "Data architect". d:description "An enterprise like a railway infrastructure manager, typically has a very siloed data/IT landscape. In order to make certain use cases possible, data has to be integrated between silo's. That's not always possible using existing systems and a spaghetti mess begins. And long term approach to data integration is defining a data centric strategy, meaning to create a data layer based on a single enterprise data model. This project set up several key requirements to becoming data centric. Reporting was done on director and enterprise level."; d:during-job ; d:external-link ; d:has-category "Strategy"; d:has-linked-projects d:Asset360, , ; d:has-tagged-roles , , , d:Teacher, d:Teamlead; d:has-tagged-techniques , d:Railway; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Data centric strategy". d:has-category "Data strategy"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Data centricity". d:description "Linear assets and linear events typically have a start and an end position using a linear referencing system (kilometerpole position). For BI and operational systems, it is easier if these linear things are denormalised. A innovative model and process was thought out to calculate smallest linear segments with a unique set of properties (over 100 properties were thus defined)."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects , ; d:has-tagged-roles , , d:Developer; d:has-tagged-techniques , d:Dbeaver, d:Postgresql, d:Qlikview, d:Topology; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Data cube: linear phenomena's". d:has-category "Business"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Data governance". d:description "Setting up an enterprise data helpdesk that gives advices and solves data bugs."; d:during-job ; d:has-category "Strategy"; d:has-linked-projects ; d:has-tagged-roles ; d:has-tagged-techniques d:Docker, d:Git, , d:Jira, , d:Openshift; d:is-featured "No"; d:public true; d:type d:Project; s:name "Data helpdesk". d:description "Older tamping machines use a relative system for track tamping. That means that the position of the track is corrected based on it's current position, contrary to a absolute system were the design position is respected. In order to make evaluate the effectiveness of tamping and ensure the end quality, the measurements that are done on the machine are forwarded and combined with design parameters and other measurements. For this, a state of the art GNSS system was installed, the measurement computers were connected to an Azure server over SSH and data transfer is automated."; d:during-job ; d:has-category "Measurement system"; d:has-linked-projects ; d:has-tagged-roles d:Developer, , d:Technician; d:has-tagged-techniques d:Azure, d:GNSS, , d:SSH; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Data integration of old track tamper machines". d:description "The data about operational length of tracks and platforms was a manually controlled inventory. This was laborious and not of high quality. This project had as goal to automatically calculate the operational length based on track topology, signal and platform locations. Integrating all the data into a common topology was the challenge."; d:during-job ; d:has-category "Data processing"; d:has-tagged-roles , , d:Developer, ; d:has-tagged-techniques d:Dbeaver, d:Plpgsql, d:PostGIS, d:Postgresql, d:PowerBI, d:Topology; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Data integration: operational platform & track length". d:audience-size ">30"; d:during-job ; d:external-link ; d:format "Conference"; d:is-featured "Yes"; d:public true; d:type d:Talk; d:year 2023; s:name "Data mineurs, 7th". d:description "Automatically sync measurement results from a measurement vehicle to the data center."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects , ; d:has-tagged-roles d:Developer; d:has-tagged-techniques d:VBA; d:is-featured "No"; d:public true; d:type d:Project; s:name "Data sync tool measurement vehicle". d:description "A database is mostly managed in several environments and changes are pushed to production after a lengthy review process. For some database applications, this is a costly overhead that is preferably avoided. Development happens directly on the production system (no worries, this has been going well for over 10 years now). And one of the reasons this goes well is because we have a system that daily captures the DDL changes of the database and stores them in a git repository. Reverting to a previous state become a matter of using git."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects , ; d:has-tagged-roles , ; d:has-tagged-techniques , d:Dbeaver, d:Git, d:Postgresql, d:Quartz, d:Serilog; d:is-featured "No"; d:public true; d:type d:Project; s:name "Database versioning system based on git". d:Datalog d:has-category "Semantic technologies"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "Datalog". d:Dbeaver d:has-category "Databases"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "Dbeaver". d:Debian d:has-category "Operating systems"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Debian". d:has-category "Leading roles"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Role; s:name "Department representative". d:description "The design office still employed a manual process for signature and process reporting of new designs. During covid, manual had to become digital. A sharepoint process was set up with email notification for signature management."; d:during-job ; d:has-category "Business process"; d:has-linked-projects ; d:has-tagged-roles , , d:Developer, ; d:has-tagged-techniques d:Sharepoint; d:is-featured "No"; d:type d:Project; s:name "Design process workflow". d:description "Schematic designs are used in railway for the track, signaling and catenary system. They schematically show how everything is connected. But it's not easy to find the changes between design revisions, for example when a signal is added or removed. To aid, we developed a machine vision based tool that finds the differences between two pdf revisions."; d:during-job ; d:has-category "Image processing"; d:has-linked-projects ; d:has-tagged-roles , , , d:Developer, ; d:has-tagged-techniques d:ADFS, , , d:Dbeaver, d:Devcontainers, d:Git, , d:Jira, , d:OpenCV, d:Openshift, d:Postgresql, d:Python, d:Quartz, d:S3, d:Serilog; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Design revision comparison". d:has-category "Data & IT role"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Role; s:name "DevOps engineer". d:Devcontainers d:has-category "DevOps"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Devcontainers". d:Developer d:has-category "Data & IT role"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Role; s:name "Developer". d:description "The project has as goal to build a knowledge graph of the railway infrastructure of Norway and generate railML v3.3 files for use cases such as RunTime Calculation (RTCI) and Runtime Simulation (RSIM)"; d:during-job ; d:has-category "Semantic"; d:has-linked-projects d:Asset360, , ; d:has-tagged-roles , , , d:Developer, d:Ontologist, ; d:has-tagged-techniques , d:Azure, , d:ESRI, d:GIS, d:GeoPackage, d:GeoSPARQL, , d:Grafana, d:Kubernetes, d:Kustomize, d:OAuth, d:OpenTNF, , d:Prometheus, d:Python, d:QGIS, d:RDF, d:RTM, d:RailML, d:SHACL, d:SKOS, , d:SSH, d:Topology; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Digital Infrastructure Model Norway". d:Django d:has-category "Web frameworks"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Django". d:Docker d:has-category "DevOps"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "Docker". d:EIM d:external-link ; d:type d:Company; s:name "EIM". d:ENERGIR d:type d:Company; s:name "ENERGIR". d:ERA d:external-link ; d:type d:Company; s:name "ERA". d:description "A proof of concept to show how RDF data together with an ontology can be used together with a LLM such as ChatGPT. The project result is a public web application where the user can ask questions in natural language and get a data result as output."; d:during-job ; d:external-link ; d:has-category "Semantic"; d:has-linked-projects ; d:has-tagged-roles , d:Developer, d:Ontologist; d:has-tagged-techniques d:Azure, d:Docker, , d:Git, , , d:OWL, d:Python, d:RDF, d:Streamlit; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "ERA RINF Chatbot". d:audience-size ">100"; d:during-job ; d:external-link ; d:format "Conference"; d:is-featured "Yes"; d:public true; d:type d:Talk; d:year 2024; s:name "ERA Rail Data Forum 2024". d:has-category "Data models"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "ERA ontology". d:ESP32 d:has-category "Micro computer"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "ESP32". d:ESRI d:has-category "GIS & topology"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "ESRI". d:EULynx d:has-category "Data models"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "EULynx". d:Elia d:external-link ; d:type d:Company; s:name "Elia". d:description "Energy settlement (responsible for a large part of the operational turnover of the company) is still done mainly using Excel. Several interfaces to existing JSON API services were added to the Excel file to add a higher level of automation to the system."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects ; d:has-tagged-roles , , d:Developer; d:has-tagged-techniques d:Excel, , ; d:is-featured "No"; d:public true; d:type d:Project; s:name "Energy settlement data lookup". d:has-category "Engineering"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Role; s:name "Engineer overhead contact line". d:description "In order to improve data deficiencies, the enterprise decided to review the current governance model and implement a new one. A high level strategic project started and data governance was discussed on multiple dimensions (structure, roles, governing bodies, policies, vision, ...). The project result has impact on the enterprise structure."; d:during-job ; d:has-category "Strategy"; d:has-linked-projects ; d:has-tagged-roles , , d:Teamlead; d:has-tagged-techniques , , ; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Enterprise data governance model". d:description "A very important element in an enterprise to avoid siloed data, is to have an enterprise data model by which the data (and applications..) are modelled. This ensures data interoperability from the start of the application. When dealing with legacy systems, starting an enterprise data model is not that easy. The goal of this project is setting up a team of experts that know the domain and are able to model the enterprise. In order to make the model as extensible as possible, semantic technologies were chosen. The model is published in different forms, among which is a Widoco internet site."; d:during-job ; d:has-category "Semantic"; d:has-linked-projects , ; d:has-tagged-roles , d:Developer, d:Ontologist, , d:Teacher, d:Teamlead; d:has-tagged-techniques , d:Gist, d:Git, , d:OWL, d:Protege, d:QUDT, d:RSM, d:RTM, d:RailML, d:SHACL, , d:SKOS, d:Widoco; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Enterprise data model". d:Excalidraw d:has-category "Other"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Excalidraw". d:Excel d:has-category "Data analytics"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "Excel". d:Facilitator d:has-category "Leading roles"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Role; s:name "Facilitator". d:Fastlane d:has-category "DevOps"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "Fastlane". d:Firewall d:has-category "Networking"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Firewall". d:has-category "Networking"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Forward proxy". d:audience-size 100; d:during-job ; d:external-link ; d:format "Conference"; d:is-featured "Yes"; d:public true; d:type d:Talk; d:year 2025; s:name "Fosdem 2025". d:GIS d:has-category "GIS & topology"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "GIS". d:GNSS d:has-category "Sensors & measurements"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "GNSS". d:description "In order to reduce the number of \"signals passed at danger\", a project was launched to track in real time the location of safety equipment. A custom GPS tracker was designed and interfaced with the internal network over LTE."; d:during-job ; d:has-category "Measurement system"; d:has-linked-projects ; d:has-tagged-roles , d:Developer, ; d:has-tagged-techniques d:Binary, , d:Firewall, d:GNSS, d:Git, , , d:Traccar; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "GPS trackers for mobile safety equipment". d:GPSD d:has-category "Sensors & measurements"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "GPSD". d:GSM d:has-category "Communication"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "GSM". d:GeoPackage d:has-category "Data models"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "GeoPackage". d:GeoSPARQL d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "GeoSPARQL". d:Gist d:has-category "Data models"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Gist". d:Git d:has-category "DevOps"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Git". d:GitHub d:has-category "DevOps"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "GitHub". d:has-category "DevOps"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Github actions". d:has-category "DevOps"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "Gitlab CI CD". d:Grafana d:has-category "Data analytics"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Grafana". d:GraphDB d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "GraphDB". d:HDF5 d:has-category "Data models"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "HDF5". d:has-category "DevOps"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "Helm charts". d:description "Very advanced home automation. The basic logic level is run by a Wago PLC that is interfaced with Openhab for higher level logic and user interfacing. A lot of sensors are custom made (PIR motion sensors, reed sensors, water level sensor, current sensing, ...) and interfaced using ESP32 boards like NodeMCU. Several software programs are custom built to make custom interfaces with existing product interfaces (like pushing telnet data to mqtt)"; d:has-category "Data platform"; d:has-tagged-roles , , , d:Developer, , , d:Technician; d:has-tagged-techniques d:Arduino, , d:Caddy, d:Cloudflare, d:DSMR, d:Dbeaver, d:Django, d:ESP32, d:Firewall, d:Git, , d:Grafana, d:Logseq, d:Loki, d:MQTT, d:NFC, d:NodeMCU, d:OpenHAB, d:PLC, d:Postgresql, d:Prometheus, d:Python, , , d:SSH, d:Telnet, d:VPN; d:is-featured "No"; d:public true; d:type d:Project; s:name "Home automation system". d:has-category "Message queue"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "IBM MQ". d:audience-size 100; d:during-job ; d:external-link "[ICT-for-RAILWAYS | Workshop | 8 th Edition Madrid – Spain 2-3 October 2025](https://www.ict-for-railways.eu/)"; d:format "Conference"; d:is-featured "Yes"; d:public true; d:type d:Talk; d:year 2025; s:name "ICT for railways". d:IIS d:has-category "Webservers"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "IIS". d:IMU d:has-category "Sensors & measurements"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "IMU". d:has-category "AI/MV"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Image recognition AI". d:has-category "Data & IT role"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Role; s:name "Independent expert". d:Infrabel d:external-link ; d:type d:Company; s:name "Infrabel". d:description "The Infrabel opendataplatform is a classic platform that allows a download of the datasets in different formats such as csv, excel, json. It is also possible to export the dataset in the RDF serialization, turtle. However, this resulted in a very generic use of a nameless ontology. Datasets were not linked. This project added a YARRRML configuration to the platform to make use of existing ontologies in describing the data in the dataset."; d:during-job ; d:has-category "Semantic"; d:has-linked-projects , ; d:has-tagged-roles d:Developer, d:Ontologist, ; d:has-tagged-techniques , d:GeoSPARQL, d:Ontop, d:Opendata, d:Opendatasoft, d:QUDT, d:RDF, , d:RMLMapper, ; d:is-featured "No"; d:public true; d:type d:Project; s:name "Infrabel opendata to RDF". d:description "The legacy system to manage the electrified auxiliary tracks was not data centric. The goal of the project was to combine the available data such as the track topology and the sectioning of the OCL to create the inventory, resulting in a dramatically reduced workload."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects ; d:has-tagged-roles , d:Developer, ; d:has-tagged-techniques d:Dbeaver, d:Plpgsql, d:PostGIS, d:Postgresql, d:QGIS, d:Qlikview, d:Topology; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Inventory: OCL auxiliary tracks". d:audience-size ">100"; d:during-job ; d:external-link ; d:format "Conference"; d:is-featured "Yes"; d:public true; d:type d:Talk; d:year 2021; s:name "Iot & Big Data for Rail 2021". d:JSON d:has-category "File format"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "JSON". d:has-category "API"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "JSON API". d:Java d:has-category "Programming languages"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Java". d:Javascript d:has-category "Programming languages"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Javascript". d:Jira d:has-category "Data platform"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Jira". d:at-company d:Infrabel; d:description "Participating in (student) engagement events."; d:ended-on "2017-09"; d:has-duration "8 years"; d:has-linked-roles ; d:started-on "2009-11"; d:type d:Job; s:name "Job: Ambassador". d:at-company d:CEB-BEC; d:description "Chairing the national sessions and representing Belgium for the TC9 committee."; d:ended-on "2017-10"; d:has-duration "5 years"; d:has-linked-roles , ; d:started-on "2013-01"; d:type d:Job; s:name "Job: Chairman committee 9". d:at-company d:Infrabel; d:description "Taking pro-active measures to improve operational railway safety."; d:ended-on "2010-03"; d:has-duration "0,5 years"; d:has-linked-roles ; d:started-on "2009-09"; d:type d:Job; s:name "Job: Coordinator operational safety". d:at-company d:EIM; d:description "Representing the interests of the EIM members at ERA working groups during discussions on the evolution of the TSI ENE."; d:ended-on "2017-09"; d:has-duration "5 years"; d:has-linked-roles , ; d:started-on "2013-01"; d:type d:Job; s:name "Job: EIM speaker for energy subsystem". d:at-company d:ERA; d:description "Selected independent expert for ERA Telematics (CEI 2025 22), contributing rail data interoperability and infrastructure modelling expertise."; d:has-duration "tbd"; d:has-linked-roles , , ; d:started-on "2026-01"; d:type d:Job; s:name "Job: ERA independent expert Safety & Telematics". d:at-company d:ENERGIR; d:description "creation of official building energy certificates"; d:ended-on "2011-02"; d:has-duration "1 years"; d:has-linked-roles ; d:started-on "2010-01"; d:type d:Job; s:name "Job: Entrepreneur, head of my own company". d:at-company d:KULeuven; d:description "Teaching fencing classes at different levels (novice up to international fencers) for the university team. Coaching the team to the university championships (and organizing the championships from time to time)."; d:ended-on "2010-03"; d:has-duration "0,5 years"; d:has-linked-roles d:Teacher; d:started-on "2009-09"; d:type d:Job; s:name "Job: Fencing instructor". d:at-company d:Matdata; d:description "data consulting services for railway companies"; d:has-clients d:BaneNor, d:Certifer, d:CogniZone, d:ERA, d:Transurb; d:has-duration "tbd"; d:has-linked-roles , , , , d:Developer, d:Ontologist, ; d:started-on "2025-02"; d:type d:Job; s:name "Job: Independent railway data freelancer". d:at-company d:Elia; d:description "Internship to perform an analysis on voltage dips"; d:ended-on "2008-09"; d:has-duration "0,2 years"; d:started-on "2008-07"; d:type d:Job; s:name "Job: Internship statistical analysis of voltage dips". d:at-company d:Infrabel; d:description "Responsible for organizing project management for strategic development and rollout projects at Infrabel Asset Management."; d:ended-on "2020-01"; d:has-duration "2 years"; d:has-linked-roles ; d:started-on "2017-09"; d:type d:Job; s:name "Job: Project lead SMILE". d:at-company d:Infrabel; d:description "Leading the digitalisation efforts in the domain of linear assets at Infrabel."; d:ended-on "2022-04"; d:has-duration "2 years"; d:has-linked-roles ; d:started-on "2020-01"; d:type d:Job; s:name "Job: Project lead digitalisation linear assets". d:at-company d:Infrabel; d:description "Setting out the data strategy for the Infrabel Operations department (~8000 people)"; d:ended-on "2025-02"; d:has-duration "~3-years"; d:has-linked-roles d:Teamlead; d:started-on "2022-04"; d:type d:Job; s:name "Job: Teamlead data centricity". d:at-company d:Infrabel; d:description "Mainly involved in the digitalisation efforts for work management and linear measurements."; d:ended-on "2017-09"; d:has-duration "2 years"; d:has-linked-roles ; d:started-on "2010-03"; d:type d:Job; s:name "Job: engineer overhead contact lines". d:KULeuven d:external-link ; d:type d:Company; s:name "KULeuven". d:Kerberos d:has-category "Authentication"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Kerberos". d:Kubernetes d:has-category "IaaS / Container orchestration"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Kubernetes". d:Kustomize d:has-category "DevOps"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Kustomize". d:has-category "AI/MV"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "LLM & ChatGPT". d:LRS d:has-category "Data models"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "LRS". d:LandXML d:has-category "Data models"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "LandXML". d:Laser d:has-category "Sensors & measurements"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "Laser". d:has-category "Sensors & measurements"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "Laser triangulation". d:audience-size ">1000"; d:during-job ; d:external-link ; d:format "Online webinar"; d:is-featured "Yes"; d:public true; d:type d:Talk; d:year 2023; s:name "Law as a Code". d:Leaflet d:has-category "Web frameworks"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Leaflet". d:Lidar d:has-category "Sensors & measurements"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Lidar". d:description "A lidar-based detection workflow to identify vegetation overgrowth along railway infrastructure."; d:during-job ; d:has-category "Lidar processing"; d:has-linked-projects ; d:has-tagged-roles , ; d:has-tagged-techniques , d:Lidar; d:is-featured "No"; d:public true; d:type d:Project; s:name "Lidar vegetation detection". d:description "Lightning strikes on railway infrastructure can cause serious damage and is not always detected. There exist commercially available measurement systems that interface their data of the lightning strike location and strength. We interfaced with these datasources and mapped the location (with some business rules) on the rail network. An email system was put in place to notify the installation responsible person. A GIS webapp and dashboard were also developed."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects ; d:has-tagged-roles , d:Developer, ; d:has-tagged-techniques d:Angular, , d:Dbeaver, d:Docker, d:Git, , d:Kerberos, d:Leaflet, d:MSSQL, d:Nginx, d:Openshift, d:PostGIS, d:Postgresql, d:QGIS, d:Qlikview; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Lightning detection alerting system". d:description "Linear measurements used to be distribute on paper or sometimes pdf. Obviously, this does not allow for normal data analysis, let alone be a driver for predictive maintenance. For this project, a data platform was set up with an automatic data transfer from measurement system to storage, automatic loading of the measurement onto the data platform and alert creation according to business rules. Furthermore an analysis desktop tool was developed that allows to visualise the measurement on an interactive chart. Other features were also developed, such as an image viewer, lidar viewer, trend analysis, inventory viewer and management, event viewer, GIS viewer, GPS tracking, export, ..."; d:during-job ; d:has-category "Desktop app"; d:has-linked-projects , , , , , , d:RCM-DX, ; d:has-tagged-roles , , , , d:Developer, ; d:has-tagged-techniques , d:Camera, d:ClickOnce, d:Dbeaver, d:GPSD, d:Git, , d:Leaflet, d:Lidar, d:PostGIS, d:Postgresql, d:Qlikview, d:Scichart, d:Serilog, d:Topology, d:WMS; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Linear measurement data viewer". d:audience-size 16; d:during-job ; d:external-link ; d:format "Workshop"; d:is-featured "Yes"; d:public true; d:type d:Talk; d:year 2026; s:name "Linked Data - A Hands-on Introduction". d:description "Location measurement of a measurement train is very important. The usability of the other measurement systems depend on the ability to locate the measurement. Before this project, each measurement system had it's own GNSS antenna, odometer sensor and so on. And not to mention its own quality of the location. The inhouse project developed a measurement system that is independent of any other and is optimised for railway vehicles."; d:during-job ; d:has-category "Measurement system"; d:has-linked-projects , , , , , ; d:has-tagged-roles , , d:Developer, , d:Technician; d:has-tagged-techniques d:GNSS, d:GPSD, d:Git, d:Grafana, d:IMU, d:Odometry, d:Prometheus, d:Python, , d:SSH; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Location measurement system for measurement train". d:description "Train vehicle locations arrives as GNSS positions. Depending on the quality of the hardware, a reliable and accurate position is not always guaranteed. The post processing system will handle a location collection from a train path and use all available information sources, such as signaling train detection information, in order to improve the quality of the location. This is very important for other infrastructure measurements."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects , , , d:Openrail; d:has-tagged-roles , , d:Developer, ; d:has-tagged-techniques , d:Dbeaver, d:GNSS, d:Git, , d:IMU, d:Odometry, d:Openshift, d:PgRouting, d:PostGIS, d:Postgresql, d:QGIS, d:Quartz, d:RTM, d:S3, d:Serilog, d:Topology; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Location post processing system for railway vehicles". d:Logseq d:has-category "Other"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Logseq". d:description "A tool to export a Logseq-authored markdown graph to RDF for downstream validation and publishing."; d:during-job ; d:has-category "DevOps"; d:has-linked-projects ; d:has-tagged-roles d:Developer; d:has-tagged-techniques d:Docker, d:Git, ; d:is-featured "No"; d:public true; d:type d:Project; s:name "Logseq RDF export". d:Loki d:has-category "Monitoring system"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Loki". d:MQTT d:has-category "Message queue"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "MQTT". d:has-category "Databases"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "MS Access". d:has-category "API"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "MS Graph". d:has-category "Business"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "MS Project". d:MSSQL d:has-category "Databases"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "MSSQL". d:MapInfo d:has-category "GIS & topology"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "MapInfo". d:description "The EU requests publishing data based on the RINF data model. Our train statistics data model is not using the RINF model as a basis. A translation system was set up to convert from one model into the other allowing to comply with EU requirements."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects ; d:has-tagged-roles , , d:Developer; d:has-tagged-techniques d:Dbeaver, , d:Excel, d:Git, d:PgRouting, d:Plpgsql, d:Postgresql, d:QGIS, d:RTM, d:SPARQL; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Mapping train statistic on RINF data model". d:Matdata d:external-link ; d:type d:Company; s:name "Matdata". d:Maven d:has-category "DevOps"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Maven". d:description "Several measurement trains are equipped with camera's that capture the railway infrastructure from different angles. These images are timestamped, but not necessary positioned. The goal of this project is to create an automatic image processing service that positions the image, based on its timestamp, the position of the camera in the vehicle and the position of the vehicle."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects , , ; d:has-tagged-roles , , d:Developer, ; d:has-tagged-techniques , d:GNSS, d:Git, , d:Openshift, d:Quartz, d:S3, d:Serilog; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Measurement train image post processing". d:description "This was the first mobile application of the enterprise. It's a GIS application, working very similar to a Map application. The user can interact with the map, search for assets, get directions, report incidents, ... Very important features of the app were the ability to visualise defect axle counters. This mostly happened during works and with the mobile app, the work teams have the ability to repair the issue before the track enters back into service (which would cause a significant amount of delays). Also requesting the technical designs or the traffic management system viewer based on your location is possible."; d:during-job ; d:external-link "https://apps.apple.com/be/app/amdm/id1553037373, https://play.google.com/store/apps/details?id=be.infrabel.amdm&hl=en, https://amdm-web.infrabel.be/"; d:has-category "Mobile app"; d:has-linked-projects ; d:has-tagged-roles , , d:Developer, , d:Teamlead; d:has-tagged-techniques d:Android, d:Azure, , d:Fastlane, d:GNSS, d:Git, , , d:SSH, d:VueJs, d:iOS; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Mobile app for geolocated technical assistance". d:description "A mobile app for catenary technicians for documentation lookup that is accessible offline and synced when online. The app uses Git to accomplish the syncing."; d:during-job ; d:external-link "https://apps.apple.com/be/app/infradoc/id1592342814, https://play.google.com/store/apps/details?id=be.infrabel.infradoc"; d:has-category "Mobile app"; d:has-linked-projects , ; d:has-tagged-roles , , ; d:has-tagged-techniques d:Android, , d:Fastlane, d:Git, d:iOS; d:id "67326741-8497-49a1-9305-ee8bc1ae0408"; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Mobile app: synced documentation". d:description "A mobile app for time registration using NFC badges."; d:during-job ; d:has-category "Mobile app"; d:has-linked-projects ; d:has-tagged-roles , d:Developer; d:has-tagged-techniques d:NFC; d:is-featured "No"; d:public true; d:type d:Project; s:name "Mobile time registration system with NFC badges". d:description "The enterprise is divided into about 15 workcenters. Each workcenter is assigned a certain resource amount, expressed in full time equivalents and number of worktrains. Each workcenter has also a certain amount of workload, expressed in number of assets and their maintenance charge. The project had as goal to create an objective and as realistic as possible model to calculate the absolute resource need for each workcenter. Simulations should also be possible: what if workcenters would merge, what if maintenance load increased, what if new assets were assigned, ..."; d:during-job ; d:has-category "Strategy"; d:has-linked-projects , ; d:has-tagged-roles , , , d:Developer, ; d:has-tagged-techniques d:Dbeaver, d:Excel, d:Oracle, d:Postgresql, d:SQL, d:VBA; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Model for FTE calculation of OCL technicians". d:MySQL d:has-category "Databases"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "MySQL". d:NFC d:has-category "Communication"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "NFC". d:NTP d:has-category "Sensors & measurements"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "NTP". d:has-category "Leading roles"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Role; s:name "National representative". d:NeTEx d:has-category "Data models"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "NeTEx". d:Nextcloud d:has-category "Other"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Nextcloud". d:Nginx d:has-category "Webservers"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Nginx". d:NodeMCU d:has-category "Micro computer"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "NodeMCU". d:OAuth d:has-category "Authentication"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "OAuth". d:description "Pendules are the vertical droppers that suspend the contact wire to the carrier wire of the overhead contact line system. The application calculates the required dropper length, based on span width, system height and lots of other system and engineering project parameters. Initially the scope was to convert a legacy VB application with a very bad architecture into a modern C# .NET application with a good architecture. The logic needed to be separated from the visualisation so that the logic could also be implemented into other business applications. After the initial scope was completed, the business rules were revised and are still being revised as business learn more about the system."; d:during-job ; d:has-category "Desktop app"; d:has-linked-projects ; d:has-tagged-roles , ; d:has-tagged-techniques , d:ClickOnce, d:Dbeaver, d:Git, , d:Postgresql, d:Railway, d:Scichart; d:is-featured "No"; d:public true; d:type d:Project; s:name "OCL dropper calculator". d:description "The pantograph is that part of the traction vehicle in a train that conducts electrical current to the engine (or battery). It has a certain dimension and as it is on top of the vehicle, is heavily influenced by the sway vibrations of the vehicle and external influences such as wind. In order to design the overhead structures, it is important to keep everything out of the path of the pantograph. The possible positions of the pantograph are called the \"free space\". This projects goal was to revise the design principles used in the enterprise and participate in the revision of the principles on a European level."; d:during-job ; d:has-category "Engineering"; d:has-linked-projects ; d:has-tagged-roles , , ; d:has-tagged-techniques d:Excel, d:Railway, d:VBA; d:is-featured "No"; d:public true; d:type d:Project; s:name "OCL freespace design principles". d:description "The goal of the project was to define a balanced set of work related KPI's to evaluate workcenters. The balance was in predictive KPI's and historical KPI's. The report was also augmented with indicators that could explain a less favorable KPI (for example, the experience of the workforce or the availability of resources). The reporting was automated and centrally available."; d:during-job ; d:has-category "Business process"; d:has-linked-projects , ; d:has-tagged-roles , d:Developer; d:has-tagged-techniques d:Dbeaver, d:Oracle, d:Postgresql, d:Qlikview, d:SQL; d:is-featured "No"; d:public true; d:type d:Project; s:name "OCL maintenance KPI's". d:description "A frontend GIS (graphical) management application running in QGIS to build and update the sectioning database of the overhead contact line. The base layer is the track topology on which a layer of sectioning elements and cables are attached. A backend program creates a sectioning topology from these singular and linear elements that is linked to the track topology. The resulting data-centric inventory is then used for calculating the electrified length of the network, for safety sheets or even for validating request for putting out of service."; d:during-job ; d:has-category "Data management app"; d:has-linked-projects , ; d:has-tagged-roles , , d:Developer; d:has-tagged-techniques , d:Dbeaver, d:Git, d:PgRouting, d:Plpgsql, d:PostGIS, d:Postgresql, d:QGIS, d:Quartz, d:RTM, d:Railway, d:Topology; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "OCL sectioning topology management application". d:description "A project to define and refine design principles that ensure the stability of overhead contact line infrastructure."; d:during-job ; d:has-category "Engineering"; d:has-linked-projects ; d:has-tagged-roles ; d:has-tagged-techniques d:Excel, d:Railway, d:VBA; d:is-featured "No"; d:public true; d:type d:Project; s:name "OCL stability design principles". d:ODK d:has-category "Other"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "ODK". d:OWL d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "OWL". d:Odometry d:has-category "Sensors & measurements"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Odometry". d:Ontologist d:has-category "Data & IT role"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Role; s:name "Ontologist". d:Ontop d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Ontop". d:OpenCV d:has-category "AI/MV"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "OpenCV". d:OpenHAB d:has-category "Other"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "OpenHAB". d:OpenID d:has-category "Authentication"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "OpenID". d:audience-size 100; d:during-job ; d:external-link ; d:format "Conference"; d:is-featured "Yes"; d:public true; d:type d:Talk; d:year 2025; s:name "OpenRail Day 2025 - TP-Lib". d:OpenTNF d:has-category "Data models"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "OpenTNF". d:Opendata d:has-category "Data strategy"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Opendata". d:Opendatasoft d:has-category "Data platform"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "Opendatasoft". d:Openrail d:description "The Openrail foundation is an opensource initiative started by OBB, DB, SNCF and UIC. As I am a big supporter of opensource, European initiatives, I managed to convince my company to join the Openrail foundation. I took upon myself a role in the technical committee to represent my company and opensource one of our projects."; d:during-job ; d:external-link ; d:has-category "Strategy"; d:has-linked-projects , d:RCM-DX; d:has-tagged-roles , , ; d:has-tagged-techniques , d:Railway; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Openrail". d:Openshift d:has-category "IaaS / Container orchestration"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "Openshift". d:Oracle d:has-category "Databases"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Oracle". d:has-category "Frontend"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "Oracle Forms". d:description "A planning tool to consolidate out-of-service requests into a coordinated operational plan."; d:during-job ; d:has-category "Planningtool"; d:has-linked-projects , ; d:has-tagged-roles , ; d:has-tagged-techniques d:Azure, , ; d:is-featured "No"; d:public true; d:type d:Project; s:name "Out of service planning consolidation system". d:description "A digital workflow for requesting planned out-of-tension interventions on overhead contact line infrastructure."; d:during-job ; d:has-category "Business process"; d:has-linked-projects ; d:has-tagged-roles , , ; d:has-tagged-techniques , , ; d:is-featured "No"; d:public true; d:type d:Project; s:name "Out of tension digital request system". d:has-category "Sensors & measurements"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "PCB design". d:PHP d:has-category "Programming languages"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "PHP". d:PLC d:has-category "Micro computer"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "PLC". d:PMO d:has-category "Business"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "PMO". d:description "A measurement systems deployed on about 15 commercial vehicles. The purpose is to detect shocks happening due to pantograph/catenary interaction. The measurement system consists of accelerometers on the pantograph head on high voltage and a low voltage system inside the train. Both communicate wirelessly. Every shock is transmitted and analysed by a server side centrally and self developed system. The biggest innovation is the method used for grouping the alerts. The location associated with the shock depends on the placement of the GNSS antenna compared to the pantograph head and on the orientation of the vehicle. Several other business rules are important as well to make this, relatively big data system, business usable. But at the end of project, it became fully integrated with the work management system and workorders were automatically created when possible."; d:during-job ; d:has-category "Measurement system"; d:has-linked-projects , , ; d:has-tagged-roles , , , d:Developer, , d:Technician; d:has-tagged-techniques d:Accelerometers, , d:Firewall, d:GIS, d:GNSS, d:Git, , d:Loki, d:Openshift, d:Plpgsql, d:PostGIS, d:PowerBI, d:QGIS, d:Qlikview, d:Quartz, d:RTM, d:Railway, d:SSH, d:Serilog, d:Topology; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Pantograph shock detection system". d:PgAdmin d:has-category "Databases"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "PgAdmin". d:PgRouting d:has-category "GIS & topology"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "PgRouting". d:Plpgsql d:has-category "Programming languages"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Plpgsql". d:description "The legacy measurement system was file based and project specific. We went to a database based system with a QGIS management layer. A data quality improvement campaign was launched to improve the inventory based on measurement registrations of overhead structure. Pole naming was improved based on camera systems and AI detections."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects , , ; d:has-tagged-roles , d:Developer, , d:Teamlead; d:has-tagged-techniques d:Dbeaver, d:GIS, d:LRS, d:PostGIS, d:Postgresql, d:QGIS, d:Railway, d:WMS; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Pole inventory management system". d:description "A data-processing workflow to generate polygons for EBP posts using QGIS and Voronoi-based geometry operations."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects ; d:has-tagged-roles , d:Developer; d:has-tagged-techniques d:QGIS; d:is-featured "No"; d:public true; d:type d:Project; s:name "Polygon generation for EBP posts". d:description "A measurement train contains many measurement systems that collect a lot of data. In order to reduce the amount of bytes, the data is mostly written into binary files having a specific binary structure. The goal of this project is to automatically read the binary files and write the data into a usable system such as a database."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects , , , d:RCM-DX; d:has-tagged-roles , , , d:Developer, ; d:has-tagged-techniques d:Binary, , d:ClickOnce, d:Git, , d:Postgresql; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Post processing of binary linear measurement file". d:PostGIS d:has-category "GIS & topology"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "PostGIS". d:description "The goal of the project was a set of database functions to allow conversion between geographic coordinates, schematic coordinates, intrinsic coordinates and linear referencing (LRS) coordinates. Not only for points but also for linear segments and area's."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects , ; d:has-tagged-roles , , d:Developer, ; d:has-tagged-techniques d:GIS, d:Git, d:LRS, d:PgRouting, d:Plpgsql, d:PostGIS, d:Postgresql, d:RTM, d:Railway, d:Topology; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "PostGIS: GIS to LRS calculation library". d:description "Several tools developed by my team that help in managing a Postgres database."; d:during-job ; d:has-category "Database"; d:has-linked-projects ; d:has-tagged-roles , , d:Developer; d:has-tagged-techniques ; d:is-featured "No"; d:public true; d:type d:Project; s:name "Postgres management tools". d:Postgresql d:has-category "Databases"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "Postgresql". d:has-category "Data analytics"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Power Query". d:PowerBI d:has-category "Data analytics"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "PowerBI". d:has-category "Data & IT role"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Role; s:name "Product owner". d:description "Ensuring the proper usage of resources. Building the right things. Having a complete and clear roadmap."; d:during-job ; d:has-category "Strategy"; d:has-linked-projects , ; d:has-tagged-roles , , , d:Teamlead; d:has-tagged-techniques d:ESRI, d:Jira, d:Oracle, d:PostGIS, , d:QGIS, d:RTM; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Product owner: enterprise GIS tooling". d:description "The track microtopology topology is a very important data aspect for a railway infrastructure manager. It's without a doubt, THE data foundation. The process needs to run smoothly, errors need to be corrected ASAP and clients need to be heard."; d:during-job ; d:has-category "Business process"; d:has-linked-projects , , , ; d:has-tagged-roles , , , d:Teamlead; d:has-tagged-techniques , , d:GIS, d:Jira, d:LandXML, d:Oracle, d:RTM, d:Railway, d:Topology; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Product owner: railway micro-topology management platform". d:description "A work management systems allows the planning of workorders and is necessary to lower the administrative burden on technicians. The system has a time table (dates as columns and people as rows) for availability planning, an inventory with maintenance requirements, an incident reporting environment and a workorder system to link everything together. The system requires many types of reporting and interfacing with other systems."; d:during-job ; d:has-category "Strategy"; d:has-linked-projects , ; d:has-tagged-roles , , , ; d:has-tagged-techniques d:Git, d:Java, d:Oracle, , , d:Qlikview, , , ; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Product owner: work management system OCL". d:has-category "Leading roles"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Role; s:name "Project lead". d:has-category "Business"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Project management". d:Prometheus d:has-category "Monitoring system"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Prometheus". d:Protege d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Protege". d:Python d:has-category "Programming languages"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Python". d:QGIS d:has-category "GIS & topology"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "QGIS". d:QUDT d:has-category "Data models"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "QUDT". d:Qlikview d:has-category "Data analytics"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "Qlikview". d:description "The Flemish household electricity cost is settled based on energy consumption as well as maximum power use. The maximum power is a yearly value based on the average monthly values. The average monthly value is the maximum 15min average power consumption. Yes.. better read that twice. In order to avoid overcharging, the home automation system interfaces with the DSMR reader to calculate this 15min value and regulate power consumption where possible."; d:has-category "Data processing"; d:has-linked-projects ; d:has-tagged-roles d:Developer; d:has-tagged-techniques d:DSMR, d:Dbeaver, d:Docker, d:Git, d:MQTT, d:OpenHAB, d:Postgresql, d:Python; d:is-featured "No"; d:public true; d:type d:Project; s:name "Quartely peak power". d:Quartz d:has-category "Scheduler"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "Quartz". d:RCM-DX d:description "Measurement systems on the market for railway mostly use a proprietary data exchange format. This creates a digitalisation barrier. RCM-DX aims to standardise the data exchange format of linear measurements. This is an opensource project."; d:during-job ; d:external-link ; d:has-category "Strategy"; d:has-linked-projects , d:Openrail, ; d:has-tagged-roles , d:Teamlead; d:has-tagged-techniques d:Binary, d:HDF5, ; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "RCM-DX". d:has-category "Data models"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "RCM-DX format". d:RDF d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "RDF". d:RINF d:has-category "Data models"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "RINF". d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "RML & YARRRML". d:RMLMapper d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "RMLMapper". d:RSM d:has-category "Data models"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "RSM". d:RTM d:has-category "Data models"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "RTM". d:audience-size ">50"; d:during-job ; d:external-link ; d:format "Conference"; d:is-featured "Yes"; d:public true; d:type d:Talk; d:year 2019; s:name "RailLive 2019". d:RailML d:has-category "Data models"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "RailML". d:description "The workgroup aims to create an ontology for the railML data exchange format."; d:during-job , ; d:external-link "[Ontology - railML.org (EN)](https://www.railml.org/en/ontology.html)"; d:has-category "Semantic"; d:has-linked-projects , ; d:has-tagged-roles d:Ontologist; d:has-tagged-techniques d:Git, d:Nextcloud, d:OWL, d:Protege, d:RDF, d:RTM, d:RailML, d:Railway, d:SHACL, d:SPARQL, d:Widoco; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "RailML ontology workgroup". d:Railway d:has-category "Business"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Railway". d:audience-size "2x40"; d:during-job ; d:external-link ; d:format "Conference"; d:is-featured "Yes"; d:public true; d:type d:Talk; d:year 2025; s:name "Railway data modelling". d:has-category "Other"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Railway telematics". d:has-category "Micro computer"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Raspberry Pi". d:Raspbian d:has-category "Operating systems"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Raspbian". d:React d:has-category "Web frontend"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "React". d:has-category "Networking"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Reverse proxy". d:Rust d:has-category "Programming languages"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Rust". d:S3 d:has-category "Data storage"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "S3". d:has-category "ERP"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "SAP CATS". d:has-category "ERP"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "SAP CO". d:has-category "Data platform"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "SAP HANA BIQ". d:has-category "ERP"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "SAP MM". d:has-category "ERP"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "SAP PM". d:has-category "ERP"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "SAP PS". d:has-category "ERP"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "SAP SCM". d:SAS d:has-category "Data analytics"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "SAS". d:SHACL d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "SHACL". d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "SHACL Play". d:SIRI d:has-category "Data models"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "SIRI". d:SKOS d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "SKOS". d:SOLID d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "SOLID". d:SPARQL d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "SPARQL". d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "SPARQL Anything". d:SPARQL-Anything d:description "SPARQL Anything is a system for querying diverse data formats (CSV, JSON, XML, HTML, etc.) using SPARQL. I've contributed multiple enhancements including a modernized Yasgui interface, internal caching system, XML attribute handling fixes, CI/CD automation, and automatic documentation snippet generation."; d:during-job ; d:external-link ; d:has-category "Semantic"; d:has-linked-projects ; d:has-tagged-roles , d:Developer; d:has-tagged-techniques d:CSV, d:Docker, d:Git, , d:JSON, d:Java, d:Maven, d:RDF, d:SPARQL, d:XML; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "SPARQL-Anything". d:has-category "Leading roles"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Role; s:name "SPOC data for department of 9000 employees". d:SQL d:has-category "Programming languages"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "SQL". d:SQLite d:has-category "Databases"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "SQLite". d:SSH d:has-category "Networking"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "SSH". d:Scichart d:external-link ; d:has-category "Frontend"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Scichart". d:has-category "Leading roles"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Role; s:name "Sector representative". d:has-category "Data & IT role"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Role; s:name "Security Champion". d:Serilog d:has-category "C# library"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "Serilog". d:description "At the time of the start of the project, project management was not done very professionally at the enterprise for development projects. Granted, that is a very difficult type of project to manage due to its complexity. The goal of setting up the PMO office was to give a central support and a way to connect people with similar issues. Management also wanted reporting, so that was also set up using the PMO system."; d:during-job ; d:has-category "Business process"; d:has-linked-projects ; d:has-tagged-roles , ; d:has-tagged-techniques , , , ; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Setup PMO office". d:Sharepoint d:has-category "Data platform"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "Sharepoint". d:description "A data management application in QGIS to manage the geographic location of shelters (containing signaling or power equipment). Several different sources of data are available for the user to manage the relevant data, including GPS coordinates of inspections of the shelters and satelite images."; d:during-job ; d:has-category "Data management app"; d:has-linked-projects ; d:has-tagged-roles , , d:Developer; d:has-tagged-techniques d:Dbeaver, d:Git, d:ODK, d:Plpgsql, d:PostGIS, d:Postgresql, d:PowerBI, d:QGIS, d:Topology, d:WMS; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Shelter GIS position management system". d:description "Having a track micro topology is a solid foundation for railway infrastructure data. But for some applications, reworking that topology into a signaling topology simplifies the usage. The goal of this project was to do this rework and publish the resulting topology."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects , ; d:has-tagged-roles , , d:Developer, ; d:has-tagged-techniques d:Git, d:PgRouting, d:PostGIS, d:QGIS, d:RTM, d:Railway, d:Topology; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Signaling topology calculation program". d:description "Small Docker-ready proxy to work around CORS restrictions when consuming APIs and SPARQL endpoints from browser-based tools, with built-in preflight handling and optional token-based protection."; d:during-job ; d:external-link ; d:has-category "DevOps"; d:has-linked-projects ; d:has-tagged-roles d:Developer; d:has-tagged-techniques d:Docker, , d:GitHub, d:Javascript; d:is-featured "No"; d:public true; d:type d:Project; s:name "Simple CORS proxy". d:Slidev d:has-category "Web frontend"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Slidev". d:description "A periodic relevant reporting on the status of strategic projects was requested by the upper management. A special focus was put on change and issue reporting. Projects were categorized into two types: development and roll-out programs. A prioritisation model was also developed to objectively score projects for attention and resource reasons."; d:during-job ; d:has-category "Business process"; d:has-linked-projects ; d:has-tagged-roles , , d:Developer, ; d:has-tagged-techniques d:Dbeaver, , d:PMO, d:Postgresql, , d:Qlikview, d:Sharepoint; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Strategic project reporting". d:description "A server that synchronizes it's time from GNSS measurements and allows for other local systems to synchronize their time over NTP (over a network connection)."; d:during-job ; d:has-category "Sensors & measurements"; d:has-linked-projects , ; d:has-tagged-roles d:Developer, , d:Technician; d:has-tagged-techniques d:GNSS, d:NTP, ; d:is-featured "No"; d:type d:Project; s:name "Stratum 1 NTP server". d:Streamlit d:has-category "Frontend"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "Streamlit". d:TP-Lib d:description "Building an open source train positioning library for railway GNSS post-processing, map matching, and path review, created for Infrabel and intended to be contributed to the OpenRailAssociation."; d:during-job ; d:external-link ; d:has-category "Data processing"; d:has-linked-projects , d:Openrail; d:has-tagged-roles , d:Developer; d:has-tagged-techniques d:Docker, d:GNSS, d:GitHub, , d:Leaflet, d:Python, d:Railway, d:Rust; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "TP-Lib". d:TSI d:has-category "Other"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "TSI". d:audience-size 30; d:during-job ; d:external-link ; d:format "Classroom"; d:is-featured "Yes"; d:public true; d:type d:Talk; d:year 2025; s:name "TSI telematics course". d:Teacher d:has-category "Leading roles"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Role; s:name "Teacher". d:Teamlead d:has-category "Leading roles"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Role; s:name "Teamlead". d:Technician d:has-category "Engineering"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Role; s:name "Technician". d:description "Giving a full day course on railway telematics to the ministry of transport of the Belgian government."; d:during-job ; d:has-category "Course"; d:has-linked-projects ; d:has-tagged-roles d:Teacher; d:has-tagged-techniques d:NeTEx, , d:SIRI, d:TSI, d:Transmodel; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Telematics course". d:description "Creating a telematics ontology based on XSD schemes for TAF and TAP TSI."; d:during-job ; d:has-category "Semantic"; d:has-linked-projects d:XSD2RDF; d:has-tagged-roles , , d:Developer, d:Ontologist; d:has-tagged-techniques d:NeTEx, d:OWL, d:Python, d:RDF, , , d:SHACL, d:SIRI, d:SKOS, , d:TSI, d:Transmodel, d:XSD, d:XSLT; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Telematics ontology". d:Telnet d:has-category "Networking"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Telnet". d:description "A project to prepare thematic GIS layers for reporting and analysis."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects , ; d:has-tagged-roles , , d:Developer; d:has-tagged-techniques ; d:is-featured "No"; d:public true; d:type d:Project; s:name "Thematic layers for GIS reporting". d:description "A Logseq-authored expertise graph that is exported to RDF, validated with SHACL, and published as a website, RDF dataset, and CV."; d:during-job ; d:external-link ; d:has-category "Webapp"; d:has-linked-projects ; d:has-tagged-roles , d:Developer, d:Ontologist; d:has-tagged-techniques d:Datalog, d:Docker, d:Git, , d:Logseq, d:RDF, ; d:is-featured "No"; d:type d:Project; s:name "This expertise graph & website". d:description "The goal of the project was to ensure that micro topology data was available at the time of creation, many years before the topology change would get into service. For this a new business process needs to be put in place with enhanced tooling. The result would be an increased data centric foundation. The design process for new equipment is not well connected with the micro topology since the AS IS topology is insufficient for them. Publishing the TO BE micro topology data would allow them to position the new assets already on the correct topologic location. That will give a snowball effect of data centric benefits."; d:during-job ; d:has-category "Business process"; d:has-linked-projects d:Asset360, , , ; d:has-tagged-roles , , ; d:has-tagged-techniques , , d:Git, d:Jira, d:RTM, d:Topology; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Topologie to be". d:Topology d:has-category "Data models"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "Topology". d:Traccar d:has-category "GIS & topology"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Traccar". d:description "A desktop application that interfaces with the traffic management system to show the location of trains on a screen. The user can then select an area for which he wants to be warned if a train enters this place. The system will scan the image and when pixels change, alert the user."; d:during-job ; d:has-category "Desktop app"; d:has-linked-projects ; d:has-tagged-roles , , ; d:has-tagged-techniques , d:ClickOnce, d:Git, , d:OpenCV, d:Railway, d:Serilog; d:is-featured "No"; d:public true; d:type d:Project; s:name "Train alert system". d:Trainannouncer d:description "A backend system using the train detection system to announce the train number to measurement systems. The train detection data arrives on a message queue, this queue is continuously read and processed for relevant messages. When train enters or exists a zone with a measurement system, the announcer will send this data to the measurement system. The measurement system uses this information for immediate action (pulling the train aside) or predictive actions (worn carbon of the pantograph)."; d:during-job ; d:has-category "Data processing"; d:has-linked-projects "PantoCAM, Numberfinder"; d:has-tagged-roles , , d:Developer; d:has-tagged-techniques , d:Dbeaver, d:Git, , , d:Openshift, d:Postgresql, d:PowerBI, d:Quartz, d:SSH, d:Serilog; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Trainannouncer". d:Transmodel d:has-category "Data models"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "Transmodel". d:Transurb d:external-link ; d:type d:Company; s:name "Transurb". d:description "Lightweight linked-data dereferencer that turns resource URIs into interactive HTML views backed by SPARQL DESCRIBE queries, while also supporting content negotiation for RDF serializations."; d:during-job ; d:external-link ; d:has-category "Semantic"; d:has-linked-projects , ; d:has-tagged-roles d:Developer; d:has-tagged-techniques d:Docker, d:GitHub, d:Javascript, d:Leaflet, d:Nginx, d:RDF, d:SPARQL; d:is-featured "No"; d:public true; d:type d:Project; s:name "URI Dereferencer". d:Ubuntu d:has-category "Operating systems"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Ubuntu". d:VBA d:has-category "Programming languages"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "VBA". d:VPN d:has-category "Networking"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "VPN". d:Virtuoso d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "Virtuoso". d:VueJs d:has-category "Web frameworks"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Competent"; d:type d:Technique; s:name "VueJs". d:WMS d:has-category "GIS & topology"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "WMS". d:has-category "Other"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "Web development". d:description "The goal of the project is to create a webapp that allows users to perform a digital inspection of the railway infrastructure. The app is GIS based, it shows the railway network and works very similar to Google streetview. The user clicks a location and can look around. Features are available to annotate the location. AI detections and Lidar interaction is also possible."; d:during-job ; d:has-category "Webapp"; d:has-linked-projects , , , , , ; d:has-tagged-roles , , ; d:has-tagged-techniques d:Angular, , d:Dbeaver, d:GIS, d:Git, , , d:Lidar, d:Loki, d:Nginx, d:Plpgsql, d:PostGIS, d:Postgresql, d:Railway, , d:SQL, d:Serilog, d:WMS; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Webapp for digital inspection". d:description "SAP is not a very user friendly system. The available tools to perform planning of workorders are insufficient for railway purposes. Thus a new web application was designed and interfaced with SAP backend. This project is part of a \"planningtools\" program to improve the business process and optimise the use of resources."; d:during-job ; d:has-category "Planningtool"; d:has-linked-projects ; d:has-tagged-roles , ; d:has-tagged-techniques d:Azure, , d:Logseq, ; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Webapp on SAP PM for workorder and ressource planning". d:description "The goal was to replace an old fashioned system with technical limitations (certainly concerning interfacing and access) with a modern web application. The application consists of an API that returns \"dangerous places\" and other sectioning information of the overhead contact line. The web application allows to easily query the API and print a pdf."; d:during-job ; d:has-category "Webapp"; d:has-linked-projects ; d:has-tagged-roles , , , d:Developer; d:has-tagged-techniques d:Angular, , d:Git, , d:Openshift, ; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Webapp: OCL safety sheets". d:description "Sometimes, multiple railway vehicles are discovered with damages on the same location, for example 30cm out of center of the pantograph. This is a clear sign of an infrastructure issue. In order to narrow down the location of the infrastructure problem, the train paths are visualised on a map that is common to all the vehicle. The challenging part of this project is to find a sufficiently detailed trainpath and a relation between the vehicle and the trains in which it served."; d:during-job ; d:has-category "Webapp"; d:has-linked-projects , , ; d:has-tagged-roles , , , ; d:has-tagged-techniques d:Angular, , d:Docker, d:Git, , , d:Nginx, d:Openshift, d:PgRouting, d:Topology, d:WMS; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Webapp: common path of several railway vehicles". d:description "A (work)traindriver that comes out of a track out of service, needs to configure his vehicle to the correct TPS system (TBL1+ or ETCS L1 LS, L1 FS, L2). This webapp allows the driver to correct locate himself on the track topology, using either a signal or his GPS position and give a driving direction. The app will then calculate the TPS level. The challenge of this project was to inventorise the TPS systems on the topology and create a routing algorithm using business logic to find \"the next signal\" on the trainpath, returning multiple if applicable. The TPS inventory is also used as an opendata dataset."; d:during-job ; d:external-link ; d:has-category "Webapp"; d:has-linked-projects , ; d:has-tagged-roles , , , ; d:has-tagged-techniques d:ADFS, d:Angular, , d:Docker, d:Firewall, d:GNSS, d:Git, , , d:Openshift, d:PgRouting, d:PostGIS, d:QGIS, ; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Webapp: train protection system". d:Widoco d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "Widoco". d:Windows d:has-category "Operating systems"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "Windows". d:audience-size 40; d:during-job ; d:external-link ; d:format "Workshop"; d:is-featured "Yes"; d:public true; d:type d:Talk; d:year 2026; s:name "Workshop RINF data provisioning". d:XML d:has-category "File format"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "XML". d:XSD d:has-category "Data models"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Expert"; d:type d:Technique; s:name "XSD". d:XSD2RDF d:description "Creation of an opensource python library that transforms an XSD into OWL, SHACL and SKOS."; d:during-job ; d:has-category "Semantic"; d:has-linked-projects ; d:has-tagged-roles , , d:Developer; d:has-tagged-techniques d:OWL, d:Python, d:RDF, , d:SHACL, d:SKOS, , d:XSD, d:XSLT; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "XSD2RDF". d:XSLT d:has-category "Data models"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "XSLT". d:description "Yet Another SPARQL GUI"; d:during-job ; d:external-link ; d:has-category "WebApp"; d:has-linked-projects , ; d:has-tagged-roles d:Developer; d:has-tagged-techniques d:Git, , d:Javascript, d:RDF, ; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "Yasgui - SPARQL GUI". d:description "Yasgui plugin that adds a result tab to see the query results on a map"; d:during-job ; d:has-category "WebApp"; d:has-linked-projects , ; d:has-tagged-roles d:Developer; d:has-tagged-techniques d:GIS, d:Git, , d:Javascript, d:Leaflet, d:WMS, ; d:is-featured "No"; d:public true; d:type d:Project; s:name "Yasgui Geo Plugin". d:description "A plugin for Yasgui to explore a query result with a graph vizualisation"; d:during-job ; d:has-category "WebApp"; d:has-linked-projects , ; d:has-tagged-roles d:Developer; d:has-tagged-techniques d:Git, , d:Javascript, d:RDF, ; d:is-featured "No"; d:public true; d:type d:Project; s:name "Yasgui Graph Plugin". d:iOS d:has-category "Mobile"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "iOS". d:macOS d:has-category "Operating systems"; d:is-featured "No"; d:public true; d:self-estimated-proficiency "Advanced beginner"; d:type d:Technique; s:name "macOS". d:audience-size ">100"; d:during-job ; d:external-link ; d:format "Conference"; d:is-featured "Yes"; d:public true; d:type d:Talk; d:year 2023; s:name "railML 44th conference". d:description "Built a reusable pipeline to convert railML 3.2 infrastructure data into ERA ontology (RINF-compatible RDF), including enrichment and SHACL validation."; d:during-job ; d:external-link ; d:has-category "Data processing"; d:has-linked-projects ; d:has-tagged-roles , d:Developer, ; d:has-tagged-techniques , d:Docker, , d:GIS, d:Python, d:RDF, d:RINF, d:RailML, d:SHACL, d:SPARQL, , d:rdflib; d:is-featured "Yes"; d:public true; d:type d:Project; s:name "railML to ERA". d:rdf-compare d:description "Open source CLI and browser viewer to compute semantic diffs between RDF files, preserving named graphs, supporting blank-node-aware comparison, and producing machine-readable RDF diff output."; d:during-job ; d:external-link ; d:has-category "Semantic"; d:has-linked-projects ; d:has-tagged-roles d:Developer; d:has-tagged-techniques d:Docker, d:GitHub, , d:Leaflet, d:RDF, d:Rust; d:is-featured "No"; d:public true; d:type d:Project; s:name "rdf-compare". d:rdflib d:has-category "Semantic technologies"; d:is-featured "Yes"; d:public true; d:self-estimated-proficiency "Proficient"; d:type d:Technique; s:name "rdflib". d:rdfsplitter d:description "Open source command line utility to split large RDF files into smaller chunks, making heavy datasets easier to validate, diff, transport, and load into downstream pipelines."; d:during-job ; d:external-link ; d:has-category "Semantic"; d:has-linked-projects ; d:has-tagged-roles d:Developer; d:has-tagged-techniques d:Docker, d:GitHub, , d:RDF, d:Rust; d:is-featured "No"; d:public true; d:type d:Project; s:name "rdfsplitter".