DHANASHREE ENGINEERING
DHANASHREE ENGINEERING
DHANASHREE ENGINEERING
How DHANASHREE ENGINEERING reduced firefighting using a single system of record

How DHANASHREE ENGINEERING reduced firefighting using a single system of record

How DHANASHREE ENGINEERING reduced firefighting using a single system of record

Turning daily follow-ups into a repeatable workflow across departments.

8→3 days

Improvement in order-to-dispatch lead time for engineering work

8→3 days

Improvement in order-to-dispatch lead time for engineering work

24%

Reduction in excess inventory across store and production

24%

Reduction in excess inventory across store and production

9%

Reduction in scrap/rework with fewer last-minute follow-ups

9%

Reduction in scrap/rework with fewer last-minute follow-ups

Hero Background

About DHANASHREE ENGINEERING

About DHANASHREE ENGINEERING

DHANASHREE ENGINEERING is a small engineering manufacturing unit based in Pune. Their day-to-day work involves coordinating orders, material availability, production execution and dispatch commitments. Earlier, updates were shared through a mix of Excel sheets, calls and WhatsApp, which made it hard to keep everyone aligned. By moving to a centralised workflow, the team standardised handovers, reduced rework in reporting, and improved execution predictability.

Workspace Icon

Engineering

Industry

Workspace Icon

Engineering

Industry

Workspace Icon

Small

Company Size

Workspace Icon

Small

Company Size

Workspace Icon

Pune, India

Location

Workspace Icon

Pune, India

Location

Workspace Icon

Multi-stage production planning + WIP control

Use Cases

Workspace Icon

Multi-stage production planning + WIP control

Use Cases

Challenges

WIP at job worker was invisible, so internal planning was always a guess.

Customer statements took hours to reconcile due to scattered notes and missing debit/credit references.

Shortage was detected only when the supervisor walked the floor, not when planning was done.

Implementation: Centralised workflow with clear owners

Implementation: Centralised workflow with clear owners

Implementation: Centralised workflow with clear owners

Earlier, job-work material movement was tracked in registers and return status was unclear. This broke down on returns; shortages and rate differences led to repeated reconciliations. We implemented a centralised workflow where each order, material requirement and update had a clear owner and timestamp. Material sent out and received back was logged against job-work orders, making shortages visible immediately. Over time, the team built confidence because the numbers matched what they saw on the floor. The practical outcome was that teams stopped re-entering the same data and acted on exceptions early.

Earlier, job-work material movement was tracked in registers and return status was unclear. This broke down on returns; shortages and rate differences led to repeated reconciliations. We implemented a centralised workflow where each order, material requirement and update had a clear owner and timestamp. Material sent out and received back was logged against job-work orders, making shortages visible immediately. Over time, the team built confidence because the numbers matched what they saw on the floor. The practical outcome was that teams stopped re-entering the same data and acted on exceptions early.

Before: Too many moving parts, no single view

Before: Too many moving parts, no single view

Before: Too many moving parts, no single view

Earlier, collections follow-ups were scattered and disputes reopened older invoices. This broke down on part-payments; the receivable view changed daily and escalations increased. We implemented structured stage-wise tracking and checklists so work moved forward only when prerequisites were met. Collections follow-ups moved to a single list with dispute tagging so teams stopped chasing the wrong invoices. The practical outcome was fewer escalations, faster decisions, and dates that changed less often.

Earlier, collections follow-ups were scattered and disputes reopened older invoices. This broke down on part-payments; the receivable view changed daily and escalations increased. We implemented structured stage-wise tracking and checklists so work moved forward only when prerequisites were met. Collections follow-ups moved to a single list with dispute tagging so teams stopped chasing the wrong invoices. The practical outcome was fewer escalations, faster decisions, and dates that changed less often.

Controlling rework through traceability and holds

Controlling rework through traceability and holds

Controlling rework through traceability and holds

Earlier, store stock, WIP and finished goods were tracked in separate sheets and message threads. This broke down whenever priorities changed—material looked available, but the line stalled due to bin-level shortages. We implemented a centralised workflow where each order, material requirement and update had a clear owner and timestamp. Supervisors started reviewing shortages at shift start and raised purchase/transfer requests before the line was blocked. It also made owner reviews easier because key exceptions were visible without chasing the team. The practical outcome was that teams stopped re-entering the same data and acted on exceptions early.

Earlier, store stock, WIP and finished goods were tracked in separate sheets and message threads. This broke down whenever priorities changed—material looked available, but the line stalled due to bin-level shortages. We implemented a centralised workflow where each order, material requirement and update had a clear owner and timestamp. Supervisors started reviewing shortages at shift start and raised purchase/transfer requests before the line was blocked. It also made owner reviews easier because key exceptions were visible without chasing the team. The practical outcome was that teams stopped re-entering the same data and acted on exceptions early.

More like this

Numakers Asia LLP

Numakers Asia LLP, a small packaging manufacturer in Surat, faced significant operational challenges, including miscommunication on vendor commitments and a lack of synchronization between dispatch processes. To address these issues, they implemented a centralized workflow that streamlined coordination across departments. This transformation led to improved execution predictability and reduced reliance on individual team members for updates. Discover how this approach not only stabilized their planning but also enhanced their overall operational efficiency.

Read More

Hira packaging solutions

Hira Packaging Solutions implemented a centralized workflow to tackle significant operational challenges, such as unclear work-in-progress quantities and disjointed communication across departments. This approach transformed their order-to-dispatch processes, leading to improved execution predictability and streamlined reporting. The team transitioned from reliance on scattered tools and outdated methods to a cohesive system, enhancing accountability and reducing the frequency of escalations. Discover how these strategic changes reshaped their daily operations and outcomes.

Read More

Omkar Industries

In a bid to enhance operational efficiency, Omkar Industries adopted a centralized workflow solution to tackle persistent coordination challenges. The company faced issues with inconsistent inventory tracking, conflicting reports from different systems, and difficulty in managing vendor follow-ups. By streamlining these processes, they aimed for smoother inter-departmental handovers and improved execution predictability, setting the stage for a more cohesive work environment.

Read More

Hero Background
Become the
AI-Run Factory

Born in India. Building for the world.

Built by IIT & IIM founders

Hero Background
Become the
AI-Run Factory

Born in India. Building for the world.

Built by IIT & IIM founders

Hero Background
Become the
AI-Run Factory

Born in India. Building for the world.

Built by IIT & IIM founders