Kodelinesoftware engineering
Renewable Energy

Built an Azure-hosted offline PWA for solar installation teams with weekly appointment planning, task-specific workflows, automatic synchronization, and backend PDF protocol storage.

References
Technical scope

Progressive Web App for field service, solar installation and scheduling

User login, role- and team-based access, AC/DC teams, appointments, offline photos, offline notes, auto-sync, sync indicators, and signed acceptance protocol PDFs.

Before

Appointments, tasks, photos, notes, and acceptance protocols were difficult to coordinate with unstable field connectivity and the existing SQL database.

After

An Angular/.NET PWA connects user login, roles, teams, offline entries, auto-sync, sync indicators, and signed acceptance protocols with the extended SQL database.

System context

Production platform, not a reporting demo.

The system helps solar installation teams coordinate field work across AC teams, DC teams, and task-specific teams. It combines weekly appointment planning, Aufgaben workflows, file and note handling, offline field capture, automatic synchronization, and signed Abnahmeprotokoll PDFs stored in the backend.

System screens

Screenshots in project context

Selected views appear where they provide concrete proof of architecture, workflow, or reporting behavior.

Engineering challenge

Field work had to become mobile without replacing the existing database.

The project was not a greenfield database replacement. The PWA had to connect to an existing SQL database that is also used by an offline Windows program, while still giving field teams modern appointment, task, file, note, and protocol workflows.

  • Multiple installation teams with AC, DC, and task-specific responsibility
  • Username/password access with role-based and team-based visibility
  • Weekly appointment planning with full-day, half-day, and quarter-day slots
  • Offline capture of photos, notes, and field data
  • Automatic synchronization and clear UI states for pending data
  • Signed acceptance protocol workflow with backend PDF storage
Architecture

.NET API and Angular offline PWA on top of an existing SQL system.

The .NET API protects the shared SQL database from direct frontend access and exposes controlled operations for teams, appointments, Aufgaben, files, notes, protocol data, and PDFs. The Angular PWA gives office and field users a responsive operational layer that works even when connectivity is unstable.

  • Read/write integration with existing appointment and task data
  • Role-based and team-based API access rules
  • Offline synchronization endpoint support for field changes
  • Backend persistence for photos, notes, and protocol PDFs
  • Azure-hosted deployment connected to the existing operational database
Offline workflow

Sync-aware UI for field work with unstable connectivity.

Field teams can capture photos, notes, and other appointment or task data without a stable connection. When connectivity returns, pending offline changes synchronize automatically and the UI makes unsynced state visible.

  • Offline photo capture
  • Offline note and field-data entry
  • Automatic synchronization after reconnect
  • Visible pending-sync indicators
  • Compatibility with the wider database synchronization model
Field workflows

Teams, appointments and signed protocols in one offline PWA

The platform connects solar field teams, appointment planning, task workflows, offline capture, synchronization and acceptance protocol PDFs.

Teams and Aufgaben

The platform supports AC teams, DC teams, and teams assigned to specific Aufgaben. Different task types expose different actions instead of forcing every workflow into the same generic form.

  • IBN Aufgabe: done state, notes, files, planned date, and done date
  • Anlage anmelden: notes and files
  • Team-specific task assignment
  • Role- and team-based visibility for operational areas

Weekly Appointments

The Termine area gives teams a weekly view of planned installation appointments with visual day placement and slot sizes.

  • Full-day, half-day, and quarter-day appointment slots
  • Team assignment in appointment context
  • Appointment notes and file attachments
  • Planning view for office coordination and field execution

Acceptance Protocols

Teams can complete an Abnahmeprotokoll for appointments, capture installer and client signatures, and store the signed protocol as a backend PDF.

  • Protocol completion in the field
  • Installer and client signatures
  • PDF storage in the backend
  • Protocol data connected to appointment, notes, and files
Engineering

Technical contribution

  • .NET API integration with an existing SQL database
  • Offline-capable Angular Progressive Web App for solar field operations
  • Username/password authentication for web app users
  • Role-based and team-based access model
  • Offline capture for photos, notes, and field data
  • Automatic sync after reconnect and sync-aware UI states
  • Azure-hosted application deployment
  • Task workflows for IBN Aufgabe and Anlage anmelden
  • Weekly Termine view with full-day, half-day, and quarter-day appointment slots
  • Abnahmeprotokoll workflow with installer and client signatures
  • Backend storage of signed protocol PDFs
  • SQL extensions required for web app access and offline PWA synchronization
Impact:

Business impact

The PWA gives solar installation operations a central web-based layer for teams, appointments, Aufgaben, files, notes, offline field data, and signed protocols without replacing the existing offline Windows system.

  • Clearer weekly appointment planning
  • Role- and team-based visibility for office and field staff
  • Offline field work for photos, notes, and entered data
  • Automatic synchronization when connectivity returns
  • Task-specific workflows instead of generic forms
  • Signed acceptance protocols stored as backend PDFs
  • Azure-hosted operational layer connected to an existing SQL database
Screenshot gallery

Additional system views

The gallery collects additional anonymized screenshots without hiding the technical case study inside a slider.