Case study 04 · Public Sector / Digital Services · 2017 – 2024
Municipal Services Portal & Violation Commission
Delivered a citizen-facing municipal services portal and Building Violation Commission software, covering online payments, request workflows, property maps, financial calculations, reporting and digital signatures.
- Domain
- Municipal / public sector
- Role
- Team lead (delivery of both products)
- Type
- Product delivery on a platform
- Stack
- .NET · SQL Server · WebGIS
From my work before founding ArtaPattern. Client names and confidential details are left out, and diagrams are conceptual.
Public services on a shared platform
Two products on the same municipal automation platform: a services portal where requests, payments and property information come together, and Building Violation Commission software that carries a case from registration through calculation to a digitally signed decision.
Engineering context
These are two products on the same platform as the Enterprise Platform Modernization case study: that case covers migrating five related subsystems to .NET 7; this one covers delivering new, citizen-facing products on the platform. They depended on the same workflows, spatial data, reporting and signature infrastructure as the rest of the platform, so changes had to fit the platform rather than work around it.
Problem & constraints
- Payments and financial calculations had to be correct and traceable.
- Decisions needed digital signatures before they took effect.
- Every request and case had to be tied to a property and its spatial data.
- Both products had to integrate with the existing platform subsystems and reporting.
Compose from platform capabilities
Requests and commission cases were modeled as workflows on the shared platform. Property maps came from the platform's WebGIS layer, calculations and reporting ran against the same SQL Server data, and decisions were closed with digital signatures, so each case kept one consistent record from submission to signed outcome.
Key engineering decisions
Use the platform's workflows instead of new ones
Requests and violation cases followed the same workflow model as the rest of the platform, so staff and support worked with one consistent process.
Anchor every case to a property
Linking requests and cases to property maps kept spatial data, calculations and decisions aligned.
Close decisions with digital signatures
Signed decisions gave each case a clear, verifiable end state.
Implementation & delivery
- 01
Requirements
With municipal stakeholders.
- 02
Workflows
Requests and case flow.
- 03
Payments
Online payments and calculations.
- 04
Close
Signatures and reporting.