ERP System

Identifies structural gaps and proactively proposes a modern, maintainable revamp.

Agent: IT-Partners Limited Client: IT-Partners Limited

The company’s custom ERP, built in the 2000s for Internet Explorer, remains a core asset but suffers from age‑related issues. I was initially assigned to maintain it by fixing immediate bugs and addressing colleague reported problems. As I dug in, the system captured my interest; I reverse engineered key components to understand the business logic and underlying mechanisms, uncovered structural gaps, and proactively proposed a modern, maintainable revamp to align the platform with current standards and long term needs.

TL;DR (STAR)

Situation

Legacy ERP on an outdated LAMP ES5 stack with no documentation, messy DB, and clunky UI hurt performance, traceability, and UX.

Task

Reverse‑engineer the system, fix the database and UI, and propose a modernised, maintainable revamp.

Action

Database

• Mapped structures/semantics across hundreds of tables; removed deprecated/duplicate tables.

• Restored integrity by adding missing keys and referential constraints; standardised data types and defaults.

• Migrated to a faster storage engine and updated character encoding.

• Produced ER diagrams for clear documentation and traceability.

User Interface

• Analysed PHP code paths and transaction logic.

• Redesigned UI for modern look, cross‑browser support, and better UX.

• Upgraded search with advanced filters; enabled spreadsheet exports for sales.

• Reinstated validation/verification on forms; improved transactions, sessions, and permissions.

• Implemented SSO with LDAP.

Result

• Fully reverse‑engineered the ERP, surfaced business logic, and delivered a revamped system.

• Significant gains in performance, usability, and data traceability.

• Proposal and outcomes impressed GM/MD; system now aligns with operational needs and strengthens critical workflows.

What was wrong with the ERP?

The legacy ERP ran on an outdated LAMP ES5 stack with no documentation, a messy database, and a clunky UI. These issues degraded performance, hindered traceability, and hurt the overall user experience, making maintenance slow and scaling risky.

How did I stabilize and revamp the ERP?

As a System Engineer, I reverse‑engineered the platform to uncover its business logic and underlying mechanisms. I stabilized the product by fixing database issues and UI defects to resolve legacy bugs and immediate pain points. I then proposed a modernized, maintainable revamp that aligns with current standards and sets the foundation for long‑term scalability and ease of support.

Database

• Mapped structures/semantics across hundreds of tables; removed deprecated/duplicate tables.

• Restored integrity by adding missing keys and referential constraints; standardised data types and defaults.

• Migrated to a faster storage engine and updated character encoding.

• Produced ER diagrams for clear documentation and traceability.

User Interface

• Analysed PHP code paths and transaction logic.

• Redesigned UI for modern look, cross‑browser support, and better UX.

• Upgraded search with advanced filters; enabled spreadsheet exports for sales.

• Reinstated validation/verification on forms; improved transactions, sessions, and permissions.

• Implemented SSO with LDAP.

What impact did the overhaul deliver?

I fully reverse‑engineered the legacy ERP, surfaced the hidden business logic, and delivered a revamped system tailored to real operational needs. The result was a substantial improvement in performance, usability, and data traceability, restoring confidence in day‑to‑day workflows.

The proposal and outcomes impressed the GM/MD, and the upgraded platform now aligns with core processes while strengthening critical workflows across the business.