Skip to main content
Profile header background
Robert B. - Information Technology - profile avatar
Profile header overlay
Available

Robert B.-Information Technology

Leinfelden-Echterdingen, Germany

Check rate

Summary

Software architect, TYPO3 specialist and technical project lead with over two decades of experience. Focus: complex B2B web portals, system integration and maintainable CMS solutions – from requirements analysis and architecture to production-ready code. I work where standard solutions fall short: understanding business processes, designing clean interfaces and reliably operating long-lasting applications.

Skills

  • Cms/Frameworks: Typo3 (Extbase, Fluid, Typoscript, Tca, Backend Modules, Scheduler, Sitepackages), Typo3 Cms 13.4, Neos/Flow, Symfony Components
  • Languages: Php 8.X/8.2, Typescript, C#/.Net 8
  • Architecture: Modular Typo3 Extensions, Domain Models, Repositories, Services, Controllers, Middleware, Dependency Injection Via Services.Yaml
  • Integration: Rest Apis And Rest-Based Http Endpoints, Xml/Xslt, Csv, Sftp With Phpseclib, Oauth/Saml, Jwt-/Oauth-Based Authentication Logic, Symfony Messenger And Doctrine Transport, Erp/Dms/Sap/Manufacturing Integration, Idempotent Uploads, Retry/Logging
  • Commerce And Processes: Aimeos (B2b), Shopping Cart, Checkout, Draft Orders, Catalog And Material Logic
  • Frontend: Vite/Vite 7, Typescript, Alpine.Js, Bootstrap/Bootstrap 5, Scss; Accessible (Wcag/Bitv); Typo3 Assetcollector
  • Windows Client: .Net 8, C#, System.Commandline, System.Text.Json, Xdocument/Linq-To-Xml, Httpclient, Wix Toolset, Msi Installer, Windows Registry
  • Data/Operations: Mysql/Mariadb, Doctrine, Typo3 Tca, Linux/Hetzner, Deployer, Ci/Cd, Phpunit, Phpstan, Traceable Logging, Maintenance, Retry And Cleanup Processes
  • Roles: Architecture · Technical Project Leadership · Implementation

Languages

German
Native

Certifications & licenses

AR/VR/MR/XR: Technologies, Applications & Issues

University of Michigan

Education

Aug 1994 - Sep 1997

Adolf LAZI Academy

Dipl. AV Mediendesigner · Media · Esslingen, Germany

Sep 1989 - Sep 1992

Max-Eyth Technical High School Kirchheim unter Teck

Technology · Kirchheim unter Teck, Germany

Statistics

Experience

Total positions 3
Experience in Manufacturing 21.5 y
Avg length 17 y 5 m
Longest experience 21 y 5 m

Expertise

Recent roles Digital fault reporting portal, custom ticketing system, Project Manager, Software Architect and Developer, Digital CAD ordering and integration portal
Main industries Manufacturing, Healthcare, Government and Administration
Main business areas Information Technology, Product Development, Project Management

Qualifications

Highest degree Bachelor
Certifications earned 1

Profile

Member since
Need a freelancer? Find your match in seconds.
Try FRATCH GPT
Jan 2016 - Present

Digital fault reporting portal, custom ticketing system

Municipal client

Position summary
Digital fault reporting portal, custom ticketing system at Municipal client
Industries
Government and Administration
Utilities
Business areas
Information Technology
Product Development

Digital fault reporting portal, custom ticketing system

Project type: Web development / custom development / operational application software

Technology: Neos CMS, Flow Framework, MySQL, Dexie.js, PhpSpreadsheet

Status: Delivered

Background:

Faults in the client’s day-to-day operations and facilities had previously been reported by phone, on paper or by email and coordinated manually. There was no structured follow-up, clear assignment of responsibilities or complete documentation. A particularly critical issue was that field staff on site had no direct access to a central system – fault reports were created in isolation and information was lost.

Market research also showed that common helpdesk or ticketing systems did not adequately cover the specific requirements of municipal wastewater management – decentralized facilities, on-call duty coordination and integration with existing communication channels. Custom development was the only sensible solution.

Solution:

The client received a custom web-based fault reporting portal, developed from the ground up for the company’s exact operational processes. The system combines structured ticket creation, traceable status tracking, mobile field reporting and automated notifications in a single, low-maintenance platform.

Ticket lifecycle and audit trail:

Every fault report follows a clearly defined lifecycle:

  • New
  • In progress
  • Under observation
  • Completed
  • Rejected

Every status change is logged immutably: who changed what, when – and why. The StateChange model ensures that the complete processing history can be traced at any time. In addition, staff can comment directly on tickets, ask questions and post status updates – keeping everyone on the same page without email chains.

Roles and permissions:

The portal has three user roles with fine-grained access rights:

  • Admin – full system access, user management, department configuration
  • Manager – processing and management of all reports within their area of responsibility
  • Employee – creating and viewing their own and assigned reports

Department assignments automatically determine which tickets a user sees and which notifications are triggered.

Mobile tablet support with offline synchronization:

Employees report faults directly on site – at a manhole, in a machine room or outdoors. A dedicated tablet mode was developed for this purpose:

  • Tablets are registered once and activated using a token-based process
  • When there is no network connection, the system stores reports locally in the browser (IndexedDB via Dexie.js)
  • As soon as a network connection is available, all reports created offline are synchronized automatically – no data loss and no manual reconciliation
  • Photos can be uploaded directly from the tablet camera and linked to the ticket

This mechanism solves a key practical problem at wastewater treatment plants: reporting under difficult conditions, far from the office Wi-Fi.

Department-based notification system:

Each fault report is assigned to one or more of the twelve specialist departments.

As soon as a report is created, edited or moved to a new status, the responsible department contacts automatically receive an email. Notification settings can be configured individually for each user – no noise and no missed reports.

On-call duty management:

The portal integrates on-call duty management directly into the fault reporting process. On-call groups (RB1, RB2, RB3) are stored and managed in the system. Incoming faults can be assigned directly to the staff on duty – the on-call schedule and ticketing system are no longer separate worlds.

Cost tracking and Excel reporting:

Cost center codes and expenses can be recorded for each fault report – useful for internal cost allocation and budget control. The system allows all reports and cost data to be exported as an Excel file for monthly reports, analysis and transfer to other systems.

Technical implementation:

The portal was delivered as a custom solution based on Neos CMS / Flow Framework (PHP) – an enterprise framework with a clear MVC architecture, Doctrine ORM database abstraction and integrated access control. The MySQL database documents the continuous development of the data model since the project began in 2016 through more than 20 migration versions.

Dexie.js (an IndexedDB wrapper) provides offline functionality, using proven browser technology for robust client-side data persistence. The sync mechanism is implemented through a dedicated API endpoint and was carefully designed to be idempotent and conflict-free.

The core data model includes 13 entities (Report, Department, Location, Tablet, Cost, Image, Ondutygroup, Post, StateChange, among others), 11 controllers and over 25 configured API routes – complexity that a standard product could not provide without significant customization.

Benefits for the client:

  • Fault reporting: phone, paper, email → structured web portal, including offline use
  • Traceability: none → complete audit trail of all status changes
  • Responsibilities: verbal and unclear → department assignment and role-based permissions
  • Notifications: manual → automatic, configurable by department
  • Field reporting: not possible → tablet app with offline sync and photo uploads
  • On-call duty: managed separately → integrated into the fault reporting portal
  • Reporting: compiled manually → Excel export at the click of a button
  • Document history: none → complete, with timestamp and user

Result:

The company now has an operationally proven, fully custom ticketing system that accurately reflects the real processes of municipal wastewater management. Twelve specialist departments, three user roles, mobile field staff with offline capability, automated notifications and complete logging form a coherent system – with no breaks between media and no isolated solutions.

The decision to build a custom solution has paid off: a standard product would not have achieved this level of operational integration without significant customization – and would have become more expensive and less flexible in the long run.

Oct 2006 - Present

Project Manager, Software Architect and Developer

Internationally operating corporation and plant manufacturer

Position summary
Project Manager, Software Architect and Developer at Internationally operating corporation and plant manufacturer
Industries
Manufacturing
Business areas
Information Technology
Product Development
Project Management

Document management – international and company-wide distribution of product documentation

For an international elevator manufacturer, I developed a secure, multilingual document portal and operated and enhanced it over several years. The portal provides sales materials, product descriptions, operating, maintenance and installation manuals, planning drawings, safety data sheets, certificates, standards and CAD data centrally to internal employees, group companies and partners. The solution combines category-based navigation, faceted full-text search across PDF content, role-based access control and single sign-on via Microsoft Entra ID. It also includes a subscription-based notification system for document changes (Content Alert) and automated processes for editorial work, user management and data export.

I had overall responsibility as project manager, software architect and developer. I gathered and structured the business requirements, designed the data model and target architecture, and implemented both in custom TYPO3 extensions. I was responsible for operating and developing the platform through several major TYPO3 versions, a transition to centralized identity management and a corporate rebrand.

Objective

The project aimed to bring scattered and sometimes manually distributed product documentation together in one central, searchable and access-protected platform.

Documents had to be available in up to six languages (English, German, French, Spanish, Russian and Portuguese) and quickly findable by document type, component and elevator system. Users needed to be actively notified about changes to relevant documents. At the same time, automation was intended to keep the editorial workload as low as possible. Access rights had to reflect the organizational structure and be managed centrally through the corporation’s identity management system.

My responsibilities

  • Project management from requirements gathering, planning, implementation and rollout through long-term operations and further development, in coordination with product management, sales and corporate IT
  • Architecture of a system comprising custom TYPO3 extensions with clearly separated responsibilities for document logic, search, user management and Sitepackage
  • Design of the data model with three hierarchical category trees (document type, component, elevator system), language-specific files for each document, change history and access rights at document and category level
  • Initial data migration using an Excel import with multilingual titles, file assignments by language, category mapping, database backup and import report
  • Integration and enhancement of faceted search with custom indexers for PDF full text, language-specific indexers and filtering of results by permissions
  • Development of the Content Alert system with subscription management, automatic change detection and scheduled multilingual email delivery
  • Authentication: initially registration with a domain whitelist, approval workflow and password expiry; later migration to SAML-based single sign-on via Microsoft Entra ID with automatic group mapping; additionally, outbound token-based single sign-on to a subsidiary’s extranet
  • Automated and privacy-compliant processes for the user account lifecycle
  • Technical modernization across several major TYPO3 versions up to TYPO3 11.5 LTS and PHP 8, including migration to PSR-14 events, Dependency Injection and current Core APIs
  • Implementation of the rebrand following the corporation’s name change
  • Development of a comprehensive multilingual data export to migrate content to a successor platform

Technology stack

  • Backend: PHP 8, TYPO3 CMS 11.5 LTS, Extbase, Fluid, Flux, VHS, TYPO3 Scheduler, Symfony Console Commands
  • Architecture: custom TYPO3 extensions, Domain Models, Repositories, Services, PSR-14 Event Listeners, PSR-15 Middlewares, DataHandler Hooks, custom FormEngine elements, Upgrade Wizards, Dependency Injection via Services.yaml
  • Search: ke_search with custom indexers (PDF full text via pdftotext, a custom indexer for documents in less common languages), custom facets and filters, and enrichment of search results
  • Authentication and identity: SAML 2.0 (md_saml, onelogin/php-saml) with Microsoft Entra ID, mapping group claims to frontend user groups, retaining deeplinks via RelayState
  • Registration: femanager with custom server- and client-side validators, Captcha and password expiry
  • Partner integration: token-based single sign-on via HTTPS/JSON
  • File management: TYPO3 File Abstraction Layer with custom file storage, language-specific file metadata and protected downloads
  • Data and persistence: TYPO3 TCA, extension of sys_category, custom tables for documents, document files, changes, subscriptions, imports and logs
  • Import and export: XLSX processing with box/spout, JSON export, ZIP packaging of large file collections
  • Frontend: Bootstrap, SCSS (compiled server-side), jQuery, tree and date pickers with gijgo, AJAX notifications, responsive gallery and list views
  • Other components: human-readable URLs and short links by language, cookie consent, News module, Fluid-based HTML and text emails

Functional scope

The portal is organized into Products, Components, Systems and Documentation. Documentation is further divided into Sales, Technology, Installation, Standards and Certificates. Each page is linked to categories and automatically displays the relevant documents. Lists can be filtered by document type, component and system, displayed as a gallery or list, and browsed with a variable page size. Selected settings are retained for the session. Each document has a detail page with all available language versions and a change history. Downloads are protected and only provided after successful checks of login status and group membership.

With faceted full-text search, users can also find documents based on their content. Indexing extracts text from PDF files and stores categories and access rights for each language. As a result, users only see documents they are authorized to access in the search results. Results also show the document type and available language versions.

The favorites feature (“My ELI”) lets users collect frequently needed documents in a personal area. Favorites can be added and removed via AJAX without reloading the page.

With Content Alert, users subscribe to changes based on search terms, categories and document languages. They choose the notification language and format (HTML or text). A notification is triggered when the editorial team changes a document’s title or categories or replaces a file. Notifications can be disabled for individual documents when changes are minor corrections. A scheduled process identifies relevant changes for each subscription and sends bundled emails in the selected language. A dedicated test mode with specified recipients is available for testing before going live.

Editorial work has been largely automated. When a file is uploaded to the document store, the system automatically creates the associated record. When a file is replaced, the linked documents receive a new change date, triggering Content Alert. When a document is saved, parent categories are added automatically, and human-readable URLs and short links are generated for each language. These links are displayed directly in the backend form for the editorial team.

To access an external standards database, authorized users receive their user group’s credentials by email after agreeing to the terms of use, along with instructions. Every request is logged.

User management is now handled through single sign-on. When users log in via SAML, the portal automatically creates or updates their accounts and assigns them to the appropriate permission groups based on their identity management groups. Accounts that have been disabled and unchanged for one year are automatically marked for deletion. The affected accounts are documented in an Excel report. After two years, they are permanently removed. Outbound single sign-on lets authorized users access a subsidiary’s extranet directly without logging in again.

To migrate the content to a successor platform, I developed a comprehensive export. It outputs all documents, language versions, categories and metadata as JSON and Excel files, including deeplinks and a flat import format for the target system. Physical files are organized by document and split into ZIP packages of limited size.

Architecture and implementation

The solution consists of a domain-specific extension for document logic and a separate Sitepackage for templates, assets, middleware and identity integration. This separation keeps business logic independent from presentation. It proved especially useful during the rebrand: the look and feel could be changed without touching the document logic.

Editorial automation is event-driven. DataHandler Hooks respond when documents are saved, while PSR-14 Event Listeners respond to file operations in the File Abstraction Layer. Category inheritance, change detection, file record maintenance and URL generation all run in the background, without requiring extra steps from the editorial team.

Search builds on ke_search extension points. Custom indexers and filters extend standard search with PDF full text, the category taxonomy and access rights, without changing the search system itself. This keeps the search updateable.

Login and access protection are implemented as a chain of PSR-15 Middlewares. They require users to log in to access protected areas, redirect users after SAML login to the originally requested document via RelayState, and identify accounts without group assignments. Mapping Entra ID groups to portal groups is configurable, allowing changes to the organizational structure to be applied without code changes.

Recurring tasks such as sending Content Alerts and cleaning up user accounts run as Symfony Console Commands and are controlled through TYPO3 Scheduler. They can also be run manually or via Cron and produce traceable logs.

I modernized the system step by step across several major TYPO3 versions, without data loss. I replaced outdated mechanisms such as Signal/Slot, old Extbase CommandControllers and Hooks with PSR-14 events, Dependency Injection, Symfony Commands and the current Pagination API. Upgrade Wizards handle the necessary data updates, such as adding missing URL segments.

Contribution to service quality

The portal brings all product documentation together in one place. Sales, engineering, installation teams and partners all access the same current version instead of working with locally stored or emailed copies. This reduces the risk of using outdated documents.

The combination of category navigation, filters and full-text search significantly speeds up document searches. Being able to find documents by their content is especially useful for large technical documents.

Content Alert keeps users up to date. Anyone responsible for a system or component automatically receives notifications in their own language about changes, without having to check the portal regularly.

Single sign-on through the corporation’s identity management system makes access much easier. Users do not need a separate password, and new employees automatically receive the right permissions through their group membership. Manual approvals and password resets are no longer needed for administrators.

Automated editorial processes reduce the workload for specialist teams. Files are uploaded or replaced, and the system handles assignment, notifications and links. This keeps documentation up to date with little effort.

Automatic cleanup of inactive user accounts supports compliance with data protection requirements. Excel reports make each cleanup run traceable and audit-ready.

The structured export ensures that content built up over many years, including metadata, language versions and categories, can be fully migrated to successor systems.

Result

The result is a multilingual document platform that has been in productive use for many years. It provides technical product documentation reliably, securely and in an easy-to-find format, and has been continuously developed across several technology generations, a transition to centralized identity management and a corporate rebrand.

The project shows that I can turn business requirements into a robust data model and maintainable architecture, and operate and modernize them reliably over many years. Particularly relevant is the combination of project management, TYPO3 architecture and development, search integration, identity and SSO integration, editorial process automation, privacy-compliant user management and the ability to migrate established data sets cleanly to new systems.

Jun 2005 - Present
Remote

Digital CAD ordering and integration portal

Medical technology

Position summary
Digital CAD ordering and integration portal at Medical technology
Industries
Healthcare
Manufacturing
Business areas
Information Technology
Product Development
Project Management

A modern application was developed for a leading manufacturer of dental implants to digitize and automate CAD-based ordering processes. The solution combines a customer-facing order portal with an administrative backend, automated file uploads, catalog and material logic, an API for CAD system integrations, a Windows wrapper for exocad DentalCAD, and interfaces to ERP and manufacturing systems.

My role included overall responsibility as project manager, software architect and developer. I structured the business requirements, defined the target technical architecture, translated it into custom TYPO3 extensions, API components and a supplementary Windows client application, and developed key parts of the application myself.

Objective

The project aimed to turn a largely manual service process for dental CAD orders into a reliable, traceable and scalable digital platform.

The application helps customers and internal service teams enter, check and manage CAD orders with large design files, and automatically pass them on to downstream systems. Direct integration with exocad DentalCAD allows order data and STL files to be sent to the portal from the CAD workstation. This reduces handoffs between media, minimizes follow-up questions and shortens customer service processing times.

My responsibilities

  • Project management from requirements gathering and technical planning through implementation and coordination with business stakeholders
  • Architecture of a modular TYPO3 13 application with clearly separated domains for ordering, integration, catalog and Sitepackage
  • Development of the customer-facing ordering process, including shopping cart, checkout, file upload and order completion
  • Development of a backend module for processing, checking and tracking orders
  • Implementation of the integration layer for ERP and manufacturing processes, including CSV generation, SFTP transfer, logging and retry mechanisms
  • Architecture and development of an exocad integration through a Windows wrapper application, with XML parsing, local validation, OAuth-based device authentication and API upload of JSON order data and STL files
  • Design and implementation of asynchronous processes using TYPO3 Scheduler, Symfony Console Commands and message processing
  • Creation of a maintainable frontend asset pipeline with Vite, TypeScript, SCSS, Bootstrap and Alpine.js
  • Technical quality assurance through structured services, domain models, repositories, configuration, local validation logic, reproducible installer processes and unit tests for core integration logic

Technology stack

  • Backend: PHP 8.2, TYPO3 CMS 13.4, Extbase, Fluid, TYPO3 Backend Modules, TYPO3 Scheduler
  • Architecture: modular TYPO3 extensions, Domain Models, Repositories, Services, Controllers, Middleware, Dependency Injection via Services.yaml
  • Asynchronous processing: Symfony Messenger, Doctrine Transport, TYPO3 Console Commands, Scheduler-controlled worker processes
  • API and client integration: REST-based HTTP endpoints, OAuth-based device and token logic, multipart/form-data uploads, JSON payloads, STL file transfer, browser deep link to draft orders
  • Windows client: .NET 8, C#, System.CommandLine, System.Text.Json, XDocument/LINQ-to-XML, Microsoft.Extensions.Configuration, Microsoft.Extensions.Logging, HttpClient
  • Desktop deployment: WiX Toolset, MSI installer, exocad SendTo registration via Windows Registry, PATH integration, appsettings.json-based language and API configuration
  • Integration: CSV export, SFTP with phpseclib, JWT/OAuth-based authentication logic, ENV-based configuration for production credentials
  • Frontend: TypeScript, Vite 7, Alpine.js, Bootstrap 5, SCSS, manifest-based asset delivery via TYPO3 AssetCollector
  • Data and persistence: TYPO3 TCA, Extbase Repositories, custom tables for orders, line items, attachments, catalog data, shipping costs and integration logs
  • Quality and operations: PHPUnit, Console Commands for maintenance, retry and cleanup, traceable logging, configurable upload and processing limits, defined exit codes and error handling for the CAD client integration

Functional scope

The application provides a complete digital ordering process for CAD-related orders. Customers can enter orders, select materials and products, upload large CAD files and complete orders through a guided process.

A chunk-based upload with parallel transfer, retry mechanisms and server-side limit checks was implemented for large technical files. Files are stored in a structured way, linked to the order and prepared for further processing.

The internal backend module allows service teams to search, filter, check and track orders. It includes detail views, attachments, export status, CSV previews, download functions, the option to trigger exports again and technical configuration checks.

The integration layer generates separate export formats for ERP and manufacturing. Orders and attachments are transferred automatically to target systems via SFTP. Every step is logged, and failed exports can be retried in a controlled way.

A catalog module provides domain logic for products, materials, implant systems, manufacturers and price calculations. Import and mapping components for structured product and Exocad data were also prepared and/or implemented.

An ExocadWrapper was also developed as a Windows command-line application. It is called from exocad DentalCAD through the SendTo function with the current project path, identifies the relevant project files, parses constructionInfo and dentalProject data, maps STL files to teeth and construction types, and creates a standardized JSON order model for the portal.

Before transfer, the wrapper checks required data, FDI tooth notation, the plausibility of the practice assignment, the existence and readability of STL files, and technical edge cases such as missing or empty files. Errors are reported directly at the workstation before incomplete data is sent to the portal.

Authentication uses device-specific registration with a Client ID, Client Secret, device fingerprint, Refresh Token and Access Token. After a successful upload, the API creates a draft order, which is then automatically opened in the browser. Users can review, complete and submit the order in the portal without having to upload CAD files manually.

Architecture and implementation

The solution was divided into separate TYPO3 extensions. This keeps the ordering process, integration logic, catalog data and template/asset structure cleanly separated in both business and technical terms. This structure reduces dependencies, makes maintenance easier and allows future enhancements without major changes to existing processes.

The ordering process is service-oriented. Shopping cart, file storage, material assignment, shipping cost calculation, draft order processing, email notifications and order conversion are modeled as separate services.

A robust asynchronous approach was chosen for integrations. Order placement remains responsive for customers, while export and transfer processes run in the background. Retry, cleanup and consumer processes are controlled through TYPO3 Scheduler and Symfony Console Commands.

Frontend assets are built using Vite and delivered as versioned files with a manifest. This cleanly separates source code, build artifacts and TYPO3 delivery.

The exocad integration was deliberately implemented as a lightweight client with clearly divided responsibilities. The wrapper handles CAD-related extraction and technical pre-validation, while the portal is responsible for the business logic, material assignment, draft order creation and further process control. This keeps the server-side API independent of native exocad XML structures and allows it to be used with other CAD systems in the future.

The wrapper is service-oriented. XML Parser, OrderDataBuilder, Validator, API Client, CredentialManager, DeviceFingerprintService and BrowserLauncher are separate components. This structure makes testing and troubleshooting easier and supports future enhancements, such as new exocad file formats, additional validation rules or changes to API endpoints.

A WiX MSI installer was created for rollout. The installer deploys the application and its configuration, registers the SendTo integration in the Windows Registry, detects exocad installations and sets language options in the configuration file. This allows the integration to be installed and updated in a controlled way on customer workstations.

Contribution to service quality

The application significantly improves service quality by letting customers submit CAD orders in a structured and traceable way. Required information, attachments and order data are collected as part of the digital process, reducing follow-up questions and manual rework for the service team.

The portal’s chunk-based upload and direct STL upload from exocad make it more reliable to transfer large CAD files. Retry mechanisms, local pre-checks and server-side checks reduce failed uploads and improve the user experience with technically demanding files.

The backend module improves operational visibility. Service staff can view order data, attachments, export status and integration logs in one place. This makes it easier to check cases quickly, identify sources of errors and respond to customer questions with better information.

Automated ERP and manufacturing exports reduce manual handoffs. Idempotent uploads, logging and retry mechanisms make processes more reliable and lower the risk of duplicate or lost transfers.

Central management of recurring tasks through TYPO3 Scheduler makes operations easier. Maintenance, retrying failed exports and cleaning up temporary upload data are standardized and traceable for administrators.

The exocad integration further improves service quality by allowing customers to prepare orders directly from the CAD system they already use. Order data, tooth information, material notes and STL files are automatically taken from the CAD project. This reduces manual data entry, cuts transfer errors and makes it much easier for dental practices and laboratories to start using the digital ordering process.

Device-specific authentication means credentials do not have to be entered again for every order. At the same time, devices can be managed and revoked, and support teams can work with defined error codes. This improves both security and support case handling.

Result

The result is a modular, maintainable and integration-ready platform that digitizes a business-critical service process and extends it with direct CAD client integration. The solution improves the customer experience, reduces the workload for internal service processes and provides a technical foundation for further automation around CAD orders, product data, exocad workflows and manufacturing integration.

The project demonstrates my ability to translate business requirements into a robust architecture and implement it as production-ready, maintainable code. Particularly relevant is the combination of project management, technical architecture, TYPO3 development, API design, .NET client development, installer and deployment planning, integration design and operational process improvement.

Industry experience

See where this freelancer has spent most of their professional time.

Experienced in Manufacturing, Healthcare, Government and Administration, and Utilities.

Manufacturing
Healthcare
Government and Administration
Utilities
Profile match chart

Business area experience

See which departments and functions this freelancer has contributed to most.

Experienced in Information Technology, Product Development, and Project Management.

Information Technology
Product Development
Project Management
Profile match chart
More actions

Frequently asked questions

Have questions? Find more information here.

Robert is based in Leinfelden-Echterdingen, Germany and can operate in on-site, hybrid, and remote work models.

Robert speaks the following languages: German (Native).

Robert has at least 21 years of experience. During this time, Robert has worked in at least 3 different roles and for 3 different companies. The average length of individual experience is 7 years and 2 months. Note that Robert may not have shared all experience and actually has more experience.

Based on recent experience, Robert would be well-suited for roles such as: Digital fault reporting portal, custom ticketing system, Project Manager, Software Architect and Developer, Digital CAD ordering and integration portal.

Robert's most recent position is Digital fault reporting portal, custom ticketing system at Municipal client.

In recent years, Robert has worked for Municipal client, Internationally operating corporation and plant manufacturer, and Medical technology.

Robert is most experienced in industries like Manufacturing, Healthcare, and Government and Administration. Robert also has some experience in Utilities.

Robert is most experienced in business areas like Information Technology, Product Development, and Project Management.

Robert has recently worked in industries like Manufacturing, Healthcare, and Government and Administration.

Robert has recently worked in business areas like Information Technology, Product Development, and Project Management.

Robert holds a Bachelor in Media from Adolf LAZI Academy.

Robert has 1 certificate: AR/VR/MR/XR: Technologies, Applications & Issues.

Robert is immediately available part-time for suitable projects.

Daily rate distribution

0% 25% 50% 75% 100%
22% of experts charge less than €640 per day.
11% of experts charge between €640 and €800 per day.
33% of experts charge between €800 and €960 per day.
11% of experts charge between €960 and €1120 per day.
22% of experts charge €1280 or more per day.
<€640 €640-​800 €800-​960 €960-​1120 €1280+

The rates shown represent the typical market range for freelancers in this position based on recent contracts on our platform.

Average rates for similar positions

Rates are based on recent contracts and do not include FRATCH margin.

1000
750
500
250
Rate comparison chart
Daily rate avg. 874 €

The average daily rate is the mean of all daily rates from recent contracts of comparable freelancers on our platform.

1000
750
500
250
Rate comparison chart
Median rate 800 €

The median daily rate is the middle value of all daily rates — half of comparable freelancers charge less, half charge more. Unlike the average, it is barely affected by outliers.

Calculated based on our freelancers’ daily rates as of 18 Nov 2026. Actual rates may vary depending on seniority level, experience, skill specialization, project complexity, and engagement length.