Full-stack technology modernization at a regional HVAC business

This was not a software rollout. It was a modernization of the company's entire technology stack, executed as one program by a single-operator IT department. Every layer moved: the servers, the network, identity, email and productivity, the line-of-business service platform, and the tooling technicians carried into the field. Replacing the legacy service-management system was one workstream inside it, and it could not have happened without the others.

The starting point

The business ran on a stack that had accumulated rather than been designed. The service side lived on a Unix-based HVAC service-management system running on SCO OpenServer. There was no domain and no central identity: machines were managed individually. Email and file storage were similarly ad hoc. In the field, technicians wrote work orders on paper and phoned the office whenever a customer's card needed to be charged.

No factory training had been provided on any of it. I picked up SCO OpenServer administration, operation of the legacy service platform, user provisioning, backups, terminal session setup, printing, and break/fix support on the job from vendor documentation and Unix man pages, and kept the legacy environment running reliably while building the case and the plan to move off it.

Workstream: server and network infrastructure

Stood up a modern server foundation to host what came next: Windows Server on Hyper-V with SQL Server, replacing the single-box Unix environment that everything had depended on. This established the platform that Active Directory, file services, and the new service-management application all landed on, and removed a single point of failure whose operational knowledge lived in one person's head.

Workstream: Active Directory from scratch

Designed and deployed Active Directory where none existed: redundant domain controllers, DNS and DHCP, group policy, and a move from per-machine local accounts to centrally managed domain identity. This was the prerequisite for everything else. Without central identity there was no way to provision users consistently, apply a security baseline, or connect the environment to cloud services.

Workstream: Office 365 migration

Migrated the company to Office 365, with Exchange Online replacing the previous mail arrangement: tenant and domain setup, mailbox migration, mail-flow cutover, client and mobile reconfiguration, and licensing. This moved email off locally maintained infrastructure and onto a platform with real availability, and gave the business a cloud identity and collaboration foundation it built on for years afterward.

Workstream: network refresh

Refreshed the network underneath all of it: switching and routing, wireless coverage across office and shop space, segmentation, and connectivity between sites. The legacy environment had been built around terminals on a flat network; the new stack assumed reliable wireless, cloud-bound traffic, and mobile devices moving through the building, and the network had to be rebuilt to match.

Workstream: service-management platform replacement

The legacy platform covered a genuinely wide footprint: service, service agreements, customer and site records, dispatch scheduling, equipment, job cost, GL, AP, AR, payroll, inventory across warehouse, truck, site and serialized stock, fleet maintenance, marketing and leads, point of sale, plus an office system with its own email and built-in fax. Replacing it meant replacing all of that at once.

I evaluated the HVAC service-management options available at the time and selected the best fit. Notable in the selection: the chosen platform came from the same vendor as the legacy one, which meant the vendor could perform the data conversion themselves rather than the business having to extract and rekey the legacy Unix datastores. Customers, sites, equipment with warranty and PM history, service agreements, dispatch, AR/AP, and job-cost history were all converted by the vendor.

My role on this workstream covered vendor selection, project management on the company side, cutover coordination timed around the seasonal dispatch load, validation of the converted data, training for dispatchers, technicians, office staff and management, decommission of the SCO OpenServer environment after cutover, and ongoing administration afterward: FoxPro DBF backup and recovery, schema updates with each release, and user provisioning.

Workstream: iPads, MDM, and the field workflow

The workstream that changed the business most visibly. Before it, technicians wrote paper work orders, phoned the office to charge a customer's card, returned at the end of each week with a stack of completed paperwork, and office staff re-keyed every one of them into the system.

After it, technicians carried iPads: device selection and provisioning, mobile device management for enrollment, app deployment, configuration and remote wipe, cellular connectivity, in-field card processing, and real-time work-order capture straight into the service platform. Dispatchers gained a live view of field work, and the weekly paper-to-database re-entry cycle was eliminated entirely.

Why it had to be one program

Each workstream unblocked the next. iPads in the field are only useful if the service platform can capture work orders in real time. A modern service platform needs a server foundation and a network that can carry it. Central identity has to exist before users can be provisioned consistently across on-premises and cloud services. Sequencing them as one program, rather than as separate projects competing for budget and attention, is what made the field transformation reachable at all.

What this accomplished

• Replaced an end-of-life Unix stack, and the undocumented self-taught operational knowledge holding it together, with vendor-supported, standard platforms.
• Gave the business central identity and cloud email for the first time, the foundation every later IT initiative was built on.
• Eliminated paper work orders and the weekly office-return-to-re-key cycle; dispatchers gained a live view of field work.
• Brought customer card payments into the field, removing the call-the-office-to-charge interruption and shortening the path from completed work to invoice.
• Standardized operational data and reporting across the service business.
• Delivered as a single-operator IT department, with no platform team, no consultants running the program, and no interruption to a seasonal service operation.