Phoenix was an internal web portal I conceived, developed, deployed and maintained for the Atlantic NOC team while supporting Vodafone UK network operations.
The portal brought fragmented radio-access-network information into one operational workspace. Engineers could search sites and cells, inspect multi-vendor data, open a geographic view, run consistency checks, review command logs and access operational reporting without moving between separate data sources.
The preserved source dates from 2013–2018. This repository is a sanitised portfolio archive of that work, not a production-ready application.
- Site and cell search across 2G, 3G and 4G data.
- Huawei, Nokia/NSN, Ericsson and Alcatel-Lucent network domains.
- Geographic site views and vendor-aware map markers.
- External-neighbour checks between radio technologies.
- Network data-quality checks, including duplicate and identifier validation.
- Huawei command-log search for operational investigation.
- Repeat-offender views for recurring network alarms.
- Parameterised access to ZenPM performance reporting.
- Role-based menus, user administration and access control.
- A dispatch dashboard for maintaining the active dispatcher list and reviewing incidents, tasks, priorities and daily distribution totals.
I owned the application from idea to operation: requirements, data model, backend and frontend development, data import processes, deployment, documentation, user support and iterative improvements based on the team's daily work.
Incident Assignment Orchestrator (GIL) was a later, separate project that automated ticket assignment in Remedy and exposed its history through Grafana. No direct Phoenix–GIL production integration is claimed.
- PHP and MySQL
- JavaScript and jQuery
- Bootstrap
- Leaflet and OpenStreetMap
- Highcharts
- Python and shell scripts for selected imports
- IMAP-driven file ingestion
- PHPExcel and PHPMailer
legacy-source/— curated application and import code.docs/architecture.md— functional architecture and data flow.docs/sanitisation.md— what was deliberately excluded or replaced.docs/technical-review.md— an honest assessment of the legacy design and how I would rebuild it today.tools/verify-public-copy.ps1— repeatable privacy and repository-content checks.
The source is retained to demonstrate the scope of the system and the problems it solved. It depends on retired infrastructure and legacy libraries, and it intentionally excludes operational data and several third-party bundles. It is therefore not expected to run as a standalone application.
The code should not be used as a security or architecture reference for a new system. See the technical review for the modernisation path.
This is a public portfolio archive, not an open-source release. No licence is granted for reuse, modification or redistribution of the application source. Product and company names are used only to describe the historical operating context; no endorsement or current affiliation is implied.