← Back to Selected Work

Enterprise SystemDelivered2007-2013

Maintenance Management ConsultantImplementation Lead

CMMS Implementations

Led end-to-end CMMS implementations across roughly ten manufacturing and petrochemical sites, translating maintenance requirements into asset structures and workflows, converting legacy text and spreadsheet records through SQL-based migration tooling, and supporting implementation through user training and site collaboration.

  • CMMS
  • SQL
  • Industrial Maintenance
  • Industrial ERP
  • Data migration
  • Asset hierarchy
  • Preventive maintenance
  • Predictive maintenance
  • Work management
  • Systems implementation
  • Information systems
≈10 sites
CMMS implementations
From requirements to training
Delivery scope
SQL script generator
Data migration tooling

From fragmented records to operational maintenance systems

Across these engagements, maintenance information and work processes were often held in text files, spreadsheets, and locally developed records. Implementing a computerized maintenance management system required more than importing that data: equipment structures, maintenance practices, responsibilities, and work processes had to be translated into a coherent operational model.

My role

I was responsible for the implementation path from requirements gathering through data conversion, system configuration, rollout, and user training. I worked with engineers from multiple disciplines at industrial sites to understand their equipment, maintenance practices, and existing workflows.

I translated those requirements into asset hierarchies, preventive and predictive maintenance structures, work-order processes, and KPI and reporting structures. This work required connecting the database model and system configuration to how maintenance was actually planned and performed.

Data migration and implementation tooling

A substantial part of each implementation involved converting legacy maintenance and equipment data from text files and Excel spreadsheets into structured databases. I wrote SQL scripts for these conversions and developed a utility that generated further conversion scripts, allowing parts of the site-specific migration logic to be produced programmatically.

The resulting systems combined converted maintenance records with configured asset structures and work-management processes. I also prepared and delivered training to support adoption by the people who would operate and maintain the systems.

Delivery evidence and limitations

Approximately ten CMMS implementations were delivered across manufacturing and petrochemical environments. The present evidence is the completed implementation work—including requirements, migration, configuration, and training—rather than a later commercial software product.

No verified post-implementation measures of downtime, maintenance cost, data quality, or user adoption are currently available. This entry therefore does not claim quantified operational improvement.

Foundation for later research

Working directly with industrial equipment, maintenance teams, and site-specific processes gave me a practical understanding of CMMS and industrial ERP implementation, asset and work hierarchies, preventive maintenance, predictive maintenance, and condition-based maintenance.

Many of the questions I later investigated through my master’s and doctoral research were motivated by this implementation experience. The delivered systems and the publications represent different aspects of the same trajectory: one concerns implementing maintenance systems in practice; the other concerns investigating the underlying methods and technical questions.

Related work

Discuss an Industry or Research Problem

I collaborate with asset-intensive organizations, research teams, and technical founders on problems involving maintenance, fleets, reliability, asset lifecycle, operational modeling, and system architecture.

If your organization has data, analytical models, or technical capability but still lacks a usable decision system, I would be interested in understanding the problem. Schedule a 20-minute introductory conversation to discuss the problem, its current constraints, and whether there is a useful basis for collaboration.

Schedule a 20-Minute Conversation