NISUS ENERGY PRIVATE LIMITED
NISUS ENERGY PRIVATE LIMITED
NISUS ENERGY PRIVATE LIMITED
NISUS ENERGY PRIVATE LIMITED tightened shop-floor control with a centralised workflow

NISUS ENERGY PRIVATE LIMITED tightened shop-floor control with a centralised workflow

NISUS ENERGY PRIVATE LIMITED tightened shop-floor control with a centralised workflow

Standardising approvals and handovers so teams work off the same numbers.

58%

Reduction in daily coordination time for auto ancillary work

58%

Reduction in daily coordination time for auto ancillary work

22%

Reduction in excess inventory across store and production

22%

Reduction in excess inventory across store and production

7→2 days

Improvement in order-to-dispatch lead time with fewer last-minute follow-ups

7→2 days

Improvement in order-to-dispatch lead time with fewer last-minute follow-ups

Hero Background

Inside NISUS ENERGY PRIVATE LIMITED

Inside NISUS ENERGY PRIVATE LIMITED

NISUS ENERGY PRIVATE LIMITED is a medium auto ancillary manufacturing unit based in Ahmedabad. 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

Auto Ancillary

Industry

Workspace Icon

Auto Ancillary

Industry

Workspace Icon

Medium

Company Size

Workspace Icon

Medium

Company Size

Workspace Icon

Ahmedabad, India

Location

Workspace Icon

Ahmedabad, India

Location

Workspace Icon

Batch-wise traceability for parts and rejections

Use Cases

Workspace Icon

Batch-wise traceability for parts and rejections

Use Cases

Challenges

Rejections were logged on paper; rework cost showed up only after dispatch was missed.

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

No simple view of vendor-wise delays, so the same issues repeated every month.

Reducing month-end surprises with traceable transactions

Reducing month-end surprises with traceable transactions

Reducing month-end surprises with traceable transactions

Earlier, QC holds and rework notes were kept on paper and were not visible to planning. This broke down during rejections; without traceability, isolating root cause took days and blocked dispatch. We implemented a centralised workflow where each order, material requirement and update had a clear owner and timestamp. QC marked holds against lots, and planners saw only cleared stock as available for production. It also made owner reviews easier because key exceptions were visible without chasing the team. The practical outcome was fewer escalations, faster decisions, and dates that changed less often.

Earlier, QC holds and rework notes were kept on paper and were not visible to planning. This broke down during rejections; without traceability, isolating root cause took days and blocked dispatch. We implemented a centralised workflow where each order, material requirement and update had a clear owner and timestamp. QC marked holds against lots, and planners saw only cleared stock as available for production. It also made owner reviews easier because key exceptions were visible without chasing the team. The practical outcome was fewer escalations, faster decisions, and dates that changed less often.

After: Predictable execution, fewer escalations

After: Predictable execution, fewer escalations

After: Predictable execution, fewer escalations

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. 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. 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, vendor follow-ups were call-driven and depended on whoever remembered to push. This broke down during peak load—approvals got delayed and committed dates slipped without a simple exception view. We implemented a centralised workflow where each order, material requirement and update had a clear owner and timestamp. The purchase team used one follow-up queue, logged committed dates, and escalated exceptions early. The practical outcome was fewer escalations, faster decisions, and dates that changed less often.

Earlier, vendor follow-ups were call-driven and depended on whoever remembered to push. This broke down during peak load—approvals got delayed and committed dates slipped without a simple exception view. We implemented a centralised workflow where each order, material requirement and update had a clear owner and timestamp. The purchase team used one follow-up queue, logged committed dates, and escalated exceptions early. The practical outcome was fewer escalations, faster decisions, and dates that changed less often.

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