A wholly owned subsidiary of Zoho Corporation Kurichi, Tamil Nadu contact@aardhraa.com

EMH Crane Components

Five departments, one on-premise application

Five departments running on separate tools and spreadsheets, with the data in each invisible to the others. Now one on-premise Creator application covering customer to part to project to support, hosted on their own infrastructure.

Use cases  ·  manufacturing

What changed

  • Five modules — CRM, projects, part creation, support desk and visitor management — on one platform
  • Hosted on premise, so the data never leaves their own infrastructure
  • Approvals, notifications and dashboards built in rather than chased by email

Author

Anantha Padmanabhan Anantha PadmanabhanProject Manager
Zoho Creator
SOURCE SYSTEMS BUILT AND RUN BY US WHERE IT GOES Customers SALES TEAM 1 enquiries and orders Visitors RECEPTION 2 arrival and purpose Departments INTERNAL FORMS 3 part and project records ZOHO PLATFORM Zoho Creator (on premise) 4 Customer management Project execution Part creation Support desk Visitor management Managers REPORTS 5 dashboards and approvals Departments ALERTS 6 notifications on their own records Used by: Sales, Engineering, Production, Support, Reception
Customers, site visitors and internal teams feed a single on-premise Zoho Creator application holding five modules — customer management, projects, part creation, support desk and visitor management — with approvals, dashboards and notifications across them.

Where they started

A crane components manufacturer with five distinct operational areas — customer management, project execution, part creation, support and visitor management — each handled in its own way. Work that crossed departments crossed a gap: a part created for a project was not visible from the customer record, and a support call did not know what had been built.

What we built

A single business management application in Zoho Creator, deployed on premise rather than in the cloud, covering all five modules. Each has its own forms, reports, workflows, approvals and dashboards, and the business logic that connects them was written into the application rather than left to people to remember.

On premise was a requirement rather than a preference, so the deployment runs on their own servers and the data stays on their infrastructure. The application has been maintained since, not handed over and abandoned.

All work