AdvancedEC is a project-based network engineering practice. Campus wireless and wired design, NAC rollouts, platform migrations, and the server and cloud infrastructure underneath — Aruba and Cisco, hands on the equipment, with documentation your team keeps when the engagement ends.
Specific, scoped projects — the ones with a maintenance window, a rollback plan, and consequences if they go sideways. Not a support contract, and not a body in a seat.
Wired and wireless design for new buildings, refreshes, and expansions — addressing, segmentation, and naming conventions written down so the tenth site matches the first.
Aruba to Cisco, Cisco to Aruba, or a generational refresh in place. Planned cutovers with a tested fallback, staged by site rather than attempted in one night.
ClearPass and ISE from policy model through enforcement. The phase most rollouts stall on is going from monitor mode to enforcement without locking out the building — that phase is the work.
What is actually deployed versus what the documentation claims, where the two drifted, and what it will cost to close the gap. Delivered as a written report you keep either way.
VMware and Hyper-V estates, Windows Server and Active Directory, DNS and DHCP — designed and consolidated alongside the network rather than as someone else's separate project.
Configuration generation, source-of-truth reconciliation, and reporting built against your systems — so the repetitive part of the last project doesn't have to be repeated by hand on the next one.
Two network stacks carried end to end, and the server, virtualization, and cloud infrastructure underneath them. Not certification-deep — deployment-deep. The distinction matters when the window is four hours and the fallback has to actually work.
The complete stack, from access layer to policy enforcement.
The parallel stack, for organizations standardized on Cisco.
Infrastructure — designed, built, operated
| Domain | Platforms |
|---|---|
| Wireless | Aruba Central & Instant, Cisco Catalyst wireless, Ubiquiti UniFi |
| Wired & switching | Aruba AOS-CX, Cisco Catalyst / IOS-XE, Ubiquiti |
| Network access control | Aruba ClearPass, Cisco ISE |
| IPAM, DNS & DHCP | BlueCat, Infoblox, Windows DNS / DHCP |
| Virtualization | VMware vSphere / ESXi, Microsoft Hyper-V |
| Server infrastructure | Windows Server, Active Directory, file & print services |
| Cloud & identity | Microsoft 365, Entra ID, Exchange Online |
Integrated in automation work
| Domain | Platform |
|---|---|
| OT & device visibility | Claroty |
| Certificate lifecycle | AppViewX |
| ITSM & CMDB | ServiceNow |
| Monitoring | SolarWinds |
| Endpoint management | Workspace ONE |
| Power & environmental | EcoStruxure |
| Physical security | Avigilon |
| Enterprise print | LRS |
Client names, locations, and identifying details are withheld under confidentiality. The projects below are described by their shape rather than their logos.
Designed and built an internal platform that generates switch and access-point configuration from documented standards, then reconciles it against the systems that are supposed to agree — IPAM, NAC, monitoring, and the CMDB. Replaced a build process that ran on spreadsheets and institutional memory.
Reworked that platform so it is not welded to one organization's vendor choices. Each capability — network management, access control, IPAM — sits behind a driver interface, so a site on one vendor stack runs the same product as a site on another, with the inapplicable pieces switched off rather than half-built.
Built the tooling to migrate between IPAM platforms without trusting either one blindly — reconciling fixed leases against reservations by IP address, enriching each record with its device profile, and producing the exception list of what genuinely had to be resolved by hand.
Packaged the platform to install into an environment with no outbound connectivity at all — delivered by copied bundle rather than by URL, with signed updates, automatic snapshots, and rollback. No agent phoning home and no standing inbound access into the protected network.
Three stages, whether the engagement ends in a design document or a completed cutover.
What is actually deployed, what the standards say, and where the two have drifted apart. You get written findings — ranked, costed, and yours regardless of whether the project continues.
Design and implementation against a fixed scope. Migration path, rollback, and maintenance windows agreed before anything is touched — not improvised at 2 a.m.
Documentation, diagrams, and any automation built along the way, transferred to your team. The measure of success is that you don't need to call me about it again.
A migration you would rather not run alone, a NAC rollout that stalled in monitor mode, or a network nobody has documented in six years. First conversation costs nothing.