FireSkan.

One product. Fifteen client deployments.

FireSkan is a web and mobile system for companies that work with fire-protection systems. It supports operational tracking, barcode scanning and reporting across web, Android and iOS applications.

A commercial partner distributes the product to companies in the sector. Each client has its own deployment and configuration, accessed through a client-specific subdomain. My work spans product decisions, implementation, client deployments and ongoing production ownership.

The brief was to rebuild and improve it.

The starting point was an earlier system with inefficient processes. The request was broad: reconstruct the product and make it work better. That meant understanding the operation before deciding how to implement it.

I analyzed processes, identified friction and redesigned flows. The work was as much about deciding what a user needed to do next as it was about building the interface and business logic behind it.

My responsibility crossed the whole system.

I analyze operational processes, redesign flows and carry those decisions into the web and mobile applications and production environments.

• Analyze operational processes and simplify user flows.
• Build interfaces, business logic, REST APIs and mobile functionality.
• Configure each client’s deployment and visual identity.
• Deploy applications and manage infrastructure configuration.
• Diagnose incidents and provide ongoing production support.

Simpler flows, configurable deployments.

I redesigned operational flows to remove unnecessary steps from the previous system. The aim was to make the existing work easier to complete, rather than reproduce the same friction in a new interface.

The product also needs to serve several companies through a distribution partner. Client-specific configuration covers identity, icons, colors and design tokens. This allows the same product to be delivered with the configuration and presentation each implementation needs.

My work includes both sides of that arrangement: building the product and configuring it for the companies using it.

Web, mobile and the production environment.

The application stack uses GeneXus 18 and WorkWithPlus, with MySQL and REST APIs. The product includes web, Android and iOS applications. Production infrastructure involves .NET / IIS, Windows Server and Plesk.

Each client has its own implementation and configuration, with subdomains used to reach those environments. The diagram below describes the system’s scope; it does not imply a shared database or a particular tenant-isolation model.

The work continues after deployment.

I handle application deployments, client configuration and production troubleshooting. That includes working with IIS, Windows Server, Plesk, DNS and firewall configuration when diagnosing environment or availability problems.

I also developed scripts to monitor services and domains. These checks help detect failures and make ongoing support part of the engineering work, rather than an afterthought.

A running system, with ongoing responsibility.

FireSkan has 15 active client deployments. The product runs across web and mobile, with simpler operational flows than the previous system and continued deployment, configuration and support work.

This project brings together the parts of engineering I want to keep doing: understanding a process, changing how the software supports it, and staying responsible for what happens in production.