E7A / 04.08
Back to archive

08 / Record

2024

AIS “SPO Infrastructure Base”

Practice

Frontend / internal systems / geodata / prototyping

A parallel internal system for facilities and infrastructure staff: tracking vocational education organizations, buildings, object condition, repairs and related data. The project did not continue into full-scale production, but became a practical testbed for maps, spatial data and frontend architecture patterns.

Scope of work

  1. 01

    Registries of educational organizations, industries, specialties and buildings

  2. 02

    Search and filtering by industry, specialty, organization and individual building

  3. 03

    Building workspace covering condition, repair information, relations, projects and photos

  4. 04

    Address, geographic data and map-oriented workflows

  5. 05

    Role-based access and permissions for different user groups

  6. 06

    WebSocket integration with HTTP API fallback on timeout or unavailable connection

  7. 07

    Parallel refinement of architecture and UI patterns later reused in larger systems

  8. 08

    Development stopped before the product reached full industrial maturity

Technology chronology

Vue application

Vue 3.4.35 / Vite 5.3.5 / TypeScript 5.5.4

A standalone Vue application using Vuetify 3.6.13 and Pinia 2.2.0. Its stack ran in parallel with the mature EPK frontend and served to refine shared frontend approaches.

Geodata / Mapbox

Mapbox GL 3.5.2

A meaningful early hands-on experience with maps and spatial data: buildings, addresses, geographic context and experiments with cartographic representation.

Realtime transport

WebSocket → HTTP fallback

The client transport supported request/response over WebSocket, reconnect behavior and automatic fallback to the HTTP API on timeout.

Project status

Internal prototype / paused

The system remained an unfinished internal direction. Its main value was practical experience and validation of architecture, mapping, permissions and realtime integration patterns.

Versions and dates reflect states confirmed by archives, Git history or releases and do not imply that every component was used in every deployment.

Contact
Copied