Architecture and delivery for a smart-city platform

What the work covered

• Platform delivery and release coordination

  Release planning, staging validation, technical briefings and integration coordination between the provider teams.

  Delivery

• System architecture and data-hub planning

  Current and target system diagrams, alternative data-flow views and a draft sensor process.

  Architecture

• IoT platform evaluation

  A comparison of cloud-IoT products, asking whether existing software could avoid custom development.

  Advisory

• Tenant onboarding and sensor taxonomy

  Location types, device references and import structures for municipal tenants.

  Data mapping

• Provider integration and migration

  Diagnosis of duplicate and stale devices, identifier handling and tenant migration preparation.

  Integration

• Smart parking

  Occupancy and counting logic, including packet ordering and ambiguous direction data.

  Hands-on

• Traffic data

  A Node-RED flow that downloads and parses FTP files, with InfluxDB queries for aggregation.

  Implementation

• Swimming-pool occupancy

  Visitor-count API integration and the logic behind capacity displays and a traffic-light indicator.

  Integration

• Demand-based irrigation

  Briefing, dashboard controls including emergency stop, sensor and control-group mapping, and end-to-end test coordination.

  Pilot

• Street-lighting control

  Requirements, downlink-command lists and coordination across LoRaWAN, provider systems and dashboard actions.

  Specification

• Plant health and tree sensors

  Tree-trunk and soil-moisture data integration, with diagnosis of missing or incorrect data.

  Monitoring

• Waste fill levels

  Sensor comparison, device mapping, distance-to-percentage logic and dashboard thresholds.

  Configuration

• Public displays and info portals

  Multi-tenant portals, display configuration and speed-measurement displays.

  Operations

• Mobile app sensor mapping

  CMS transition input, plus sensor-ID and widget-reference changes for the mobile app.

  Code contribution

• Environmental widgets

  Weather-sensor and API references for environmental widget delivery.

  Integration

• Ferry-position signs

  A concept translating ferry ramp and relay states into location information for public signs.

  Concept

• Energy controlling and digital twin

  Feasibility of energy monitoring and a digital twin using shared sensor data.

  Feasibility

• API monitoring

  API-monitoring setup and troubleshooting across sensor platforms.

  Operations

• Programme closure

  Advice on provider shutdown and sensor-data export options.

  Lifecycle