Baladiya Automation & Risk Guard

[DELIVERABLES]
PLATFORM
[IMPACT]
Reliability
[ROLE]
Automation Engineer
[SERVICES]
SCRAPING • OTP • Handling
[THE STORY]

Thousands of excavation requests arrive daily, and approving the wrong one can cut provider’s fiber and trigger major outages. I built an end-to-end automation that logs into the government Baladiya portal, pulls new requests, checks each request’s lat/long against our topology within a safety radius, then auto-accepts, rejects, or raises a joint-visit case.

Result: faster approvals, fewer outages, and reduced operational workload and joint visits.

[SOLUTION]

An automated approval system that evaluates government excavation requests against telecom topology to prevent cable damage, streamline responses, and coordinate joint site visits when uncertainty exists.

GITHUB
[ARCHITECTURE]
Python
Selenium
Rest Apis
Nextjs
Telegram Bot
Gis
[DEVELOPMENT SPECIFICATIONS]
AUTHENTICATION
2 Factor Authentication
DATABASE
PostgreSQL
GIS
Here Tech
AUTOMATION
Selenium
[USER FLOW]
USER FLOW

New request received → Bot logs into Baladiya portal (OTP) → Fetch requests → Geo-compare (lat/long + radius) against topology DB → Decision: Accept / Reject / Joint Visit → Portal action submitted + audit logged → Technician notified for joint visit (if needed)

[DETAILS]
  • Automated retrieval of excavation requests from a non-API government portal (Selenium)
  • OTP-enabled login workflow using Telegram bot relay + mobile forwarding script
  • Geo-radius matching (lat/long) against internal topology/asset database
  • Auto-decision engine: Accept / Reject / Joint Visit based on proximity confidence
  • Joint-visit case creation with technician details (time/day/location/contact)
  • Next.js dashboard for tracking, audit logs, and manual override when required