Deep Research — Belrise Industries / Badve Engineering (Pantnagar)

1. Company overview & snapshot

Belrise Industries Limited, formerly Badve Engineering Limited, is a large Indian automotive-components manufacturer focused on safety-critical systems and metal-intensive products. Pantnagar matters because Belrise publicly lists two manufacturing facilities in Uttarakhand, corresponding to the legacy Badve Unit IX and Unit XII footprints surfaced in the outreach kit. Investor presentations position the company as a scaled, multi-plant Tier 1 supplier with deep capabilities in press operations, sheet-metal fabrication, coating and painting, welding, and system assembly.

For Stamped, the Pantnagar setup is attractive because it is not a single clean process. It is a mixed-load, mixed-utility environment, likely combining stamping, robotic welding, paint-shop infrastructure, compressors, air handling, ETP/STP support, and general assembly. Those are precisely the conditions where maximum-demand spikes and utility-side losses become expensive but hard to attribute cleanly.

Recent public signals in the last 12 months:

• Belrise went public in 2025 and has continued updating investors on growth and manufacturing footprint, which suggests tighter scrutiny on margin and plant performance.
• FY25 and Q1 FY26 investor materials continue to highlight Pantnagar among the company’s manufacturing locations.
• Public materials also note renewable-power sourcing from a 1.6 MW solar arrangement delivering roughly 200,000 kWh per month during FY24, plus wastewater-management programs across facilities.

1.1 Legal identity & corporate structure

Belrise Industries Limited is the current corporate name for the former Badve Engineering business. The DRHP records incorporation as Badve Engineering Private Limited in 1996, later changes to Badve Engineering Limited and then Belrise Industries Limited in 2022. Use “Belrise (formerly Badve)” once, then follow the contact’s preferred name; local plant relationships may still use Badve.

The two verified Pantnagar locations are Facility I, Plot 15, Sector 10, IIE-SIDCUL, Pantnagar, Rudrapur 263153, and Facility II, Plot 52, Sector 11, Tata Vendor Park, IIE-SIDCUL, Pantnagar, Rudrapur 263153. They are separate manufacturing sites, not automatically a single energy boundary. Confirm legal billing entity, UPCL service accounts, contract demand and local decision ownership before proposing a combined case.

1.2 What they make & where money comes from

Annual-report material identifies Pantnagar I with brake-lever/gear-change-lever, frame, painted and coated parts, and Pantnagar II with sheet-metal and body-in-white parts. The process implication is a mixed discrete-manufacturing environment: presses and forming, welding, coating/painting, assembly and utility systems. The commercial pressure is Tier-1 delivery, quality and cost—not a generic sustainability target.

1.3 Plants, addresses & footprint

The recommended first-pilot site is the facility with the clearest local sponsor and independently readable bill/meter boundary. Avoid a two-plant “energy program” before showing one useful result. Common compressed air, ETP, paint-shop utilities or shared maintenance can later make a cross-site comparison attractive, but only after the physical and billing boundaries are mapped.

1.4 Leadership & CRM map

The kit’s Sunil Lohani contact is a technical route, while Vikas Singh is a paint-shop utilities validator. Those people can explain actual load behavior, but a plant head or operations sponsor must own any schedule test and the finance/bill owner must validate the result. The listed emails are inferred and must be confirmed; no direct email should be described as verified.

1.5 Recent news (24 months) & timing for Stamped

Belrise’s 2025 listing and public reporting create a margin-accountability context. FY25 materials also describe IoT-enabled monitoring and centralized monitoring for critical coating processes. That is a reason to be precise: Stamped should not sell another monitoring layer. It should offer an action-to-UPCL-bill verification loop where data is already available.

2. Energy profile

• DISCOM: Inferred as UPCL for Pantnagar, Uttarakhand. Verify whether Unit IX and Unit XII have separate service accounts or demand sharing.
• Estimated electricity band: Likely ₹35L-₹60L/month across the Pantnagar operations combined. This range is inferred from Band A screening and the utility-heavy process mix.
• Process-energy character: High electrical intensity from stamping support equipment, robotic welding, motors, pumps, compressed air, paint-shop chillers and blowers, plus wastewater and utility systems.
• Thermal profile: Paint-shop or coating operations often create ancillary thermal loads and utility complexity even when the main energy narrative is electrical.
• Sustainability / EnCon signals: Public disclosures mention VFDs, efficient motors, LED lighting, and alternative-energy use including solar and wind. This implies Belrise has already captured some obvious housekeeping wins.
• Likely pain points: demand spikes from overlapping welding and paint-shop startup, compressed-air leakage, ventilation/HVAC drift, and hidden utility baseload spread across two nearby plants.

2.1 Bill band, tariff & demand

DISCOM / supply (name early): UPCL is the working utility hypothesis for both Pantnagar sites. The ₹35L–₹60L/month [~] combined estimate is not publicly disclosed and may be wrong if bills are separate or the process mix differs. Obtain two invoices per facility. Review sanctioned demand, recorded MD, demand charges, PF line, TOD treatment and production days before calculating any opportunity.

The testable issue is not simply “high energy.” Welding starts, paint-shop support, blowers, chillers, hot-water generation, compressors and ETP operation may overlap in a way that inflates demand or leaves persistent baseload. Volume, coating workload, ambient conditions and tariff changes must be separated from controllable operating behavior.

2.2 Generation, fuel & renewables

Belrise has publicly referenced renewable-power sourcing at group level. It is not evidence of a Pantnagar-specific supply arrangement. Confirm rooftop solar, open access, DG use, coating/paint thermal fuel, and whether utility systems are electrically or thermally driven. Solar does not solve a demand problem if loads still overlap.

2.3 EnMS, PAT, ISO, BRSR

Public disclosures indicate efficiency initiatives such as VFDs, motors and lighting, but do not establish a Pantnagar ISO 50001 certification or plant-level EnMS scope for this dossier. Ask what the team already monitors, who gets a weekly exception, and whether an exception becomes a named action. Stamped should complement—not challenge—existing TPM, maintenance or corporate monitoring.

2.4 Likely ₹ leak categories (hypothesis)

Prioritize start sequencing across welding and coating utilities; off-shift compressor/blower/chiller load; air-pressure drift; ETP baseload; and PF behavior. None is a confirmed defect. The responsible engineering owner must approve each intervention, especially where paint quality, ventilation or safety is involved.

3. Operations, equipment & digital stack

Belrise’s public process stack is highly relevant:

• press operations
• sheet-metal fabrication
• robotic welding
• coating and painting
• system assembly

That combination usually creates one of the hardest plant energy problems to manage well: many subsystems, each individually understandable, but collectively messy at the bill level. Robotic welding can create spiky load signatures. Paint shops and their support utilities often carry large hidden baseloads. Utility assets such as chillers, pumps, blowers, ETPs, and air compressors are typically treated as overhead until the bill becomes painful.

The likely operating rhythm is multi-shift and customer-schedule-driven, with strict Tier 1 delivery discipline. In these plants, the energy opportunity often sits less in one catastrophic inefficiency and more in poor startup coordination, low-visibility utility losses, and weak assignment of ownership for baseload reduction.

Digital-stack inference: Belrise almost certainly has mature controls on core manufacturing assets and some level of SCADA or utility visibility, especially in welding and paint operations. But two conditions may still hold:

1. data is fragmented between production and utilities;
2. no one sees a clean, next-bill answer to which line or utility combination inflated MD this month.

That makes the site a strong fit for a read-only prescriptive layer rather than another retrospective audit.

3.1–3.4 Detailed operating diligence

Treat the plant as a set of interacting load zones: presses/forming; welding; coating/painting; assembly; and common utilities. The main energy question is which zones share a meter and which are individually visible. A paint process may include AHUs, blowers, pumps, chillers, ovens or hot-water equipment; do not assert a particular configuration until local validation.

Shift patterns, OEM schedules, model mix and maintenance windows are not public. Build a production-normalized baseline. A lower bill caused by fewer painted parts, a weekend shutdown or weather should not become a claimed saving. Public monitoring references support a read-only integration hypothesis but do not verify SCADA vendor, historian access or meter granularity. Support a Path A export from existing systems and a Path B bill-plus-interval-data pilot, with no PLC writes.

New capacity, post-IPO systems integration and efficiency projects may affect the baseline. Ask what has changed in the last six months before comparing periods.

4. Stamped Energy fit analysis

4.1 ICP scorecard

Two Pantnagar manufacturing sites, mixed utility loads and post-IPO margin pressure fit the ICP. Confirm whether either service account clears ₹30 lakh/month UPCL and whether Units IX/XII are separately governed.

4.2 Fit score rationale

7/10: strong mixed-load opportunity, offset by billing-boundary uncertainty and more formal post-IPO vendor process.

4.3 Wedge (parser-critical)

The strongest wedge is: sequence welding/paint-shop demand, reduce persistent chiller/blower/compressed-air baseload and create assigned ₹ actions that are verified on each relevant UPCL bill.

4.4 Objections & competitors

Efficiency projects, legacy monitoring and OEM cost-down work are complementary. Stamped does not touch robotics/PLCs or replace the EMS; it creates an operating prescription and bill-verification loop.

4.5 Pilot design

Pilot one unit first, with feeder data for welding, paint-shop utilities and common air/ETP; baseline six bills and production schedule; expand only after a clear production-normalised MD or baseload result.

Fit score view: Solid Band A fit with good upside if both Pantnagar units are inside the same energy conversation. Post-IPO operating discipline may make quantified savings more attractive than before.

Why Stamped can land here:

• welding plus paint-shop utilities are classic MD and SEC-drift territory
• two-plant complexity makes attribution harder for internal teams
• read-only deployment reduces resistance in a safety- and quality-sensitive auto environment
• bill verification is stronger than a consultant recommendation deck because it closes the loop financially

Best entry angle: Lead with utility coordination and demand charges, not generic automation.

1. What is driving demand spikes across the Pantnagar plants?
2. Which utility systems are persistently off baseline?
3. Which operational changes can be tested within one bill cycle and verified?

Stamped proof points likely to resonate

• no hardware retrofit
• no control writes into robotics or paint systems
• actionable instructions for maintenance and utility owners
• next-bill validation for finance and plant leadership

Competitive / alternative frame

• existing utility logs
• maintenance team’s own observations
• OEM-driven cost-down programs
• legacy EMS or panel-level monitoring without prescriptive closure

4.1–4.5 Decision case and pilot

The ICP passes on process complexity and location; it is conditional on actual UPCL bills clearing the addressable band, accessible data and a plant sponsor. Retain 7/10: welding/coating and two-site complexity are promising, but they also increase procurement and baseline risk.

The strongest wedge is: use existing Pantnagar meter or monitoring data to identify one welding/paint-shop/common-utility overlap or persistent baseload, assign a safe ₹-valued action to its owner, and verify the outcome on the relevant UPCL bill.

Do not compete with robotics, paint controls, VFDs, solar, TPM or the existing monitoring stack. Stamped is read-only, does not write to controls, and does not promise that a dashboard solves execution. A pilot should begin at one plant: validate billing, meter hierarchy, line schedule and safety constraints in weeks 1–2; establish a normalized baseline in weeks 3–4; log weekly owner-approved actions in weeks 5–10; reconcile to the invoice in weeks 11–12. Kill the pilot if the plant cannot isolate a stable boundary, provide bill context or appoint an action owner.

5. Before you reach out

• Verify whether Unit IX and Unit XII should be treated as one pilot opportunity or two separate plant cases.
• Ask specifically about paint-shop utilities, because that is where hidden baseload often lives.
• Confirm whether welding, compressors, chillers, blowers, and ETP are individually metered.
• Use Belrise’s public renewable-power and efficiency efforts as evidence that the company cares, then pivot to the missing question: “What still cannot be tied to the monthly bill fast enough?”
• Do not start with ESG language; margin, throughput support, and plant controllables are more credible.
• Likely landmine: post-IPO procurement and vendor onboarding may be more formal. Keep the first step as a tightly scoped 90-day plant pilot.
• Another landmine: contacting only a maintenance lead can trap the conversation at technical level. Make sure plant or cluster economics are still in frame.
• Be careful with naming: public materials now use Belrise while some local relationships may still say Badve. Use both once, then follow the contact’s preferred name.

5.1 Discovery checklist

• Confirm Facility I versus Facility II, current product routes and direct UPCL service accounts.
• Replace ₹35L–₹60L/month [~] with invoices; inspect MD, PF and TOD.
• Map welding, paint utilities, compressors, blowers, chillers, ETP and any shared infrastructure.
• Ask what monitoring exists and what actions it currently produces.
• Capture output, shifts, paint workload and shutdowns for normalization.
• Identify a plant sponsor, maintenance/utility executor, safety/quality approver and bill-data owner.
• Confirm data-security/no-write requirements.

5.2 Do not lead with

• Do not lead with ESG, generic AI, dashboard replacement or post-IPO assumptions.
• Do not describe group solar/efficiency claims as Pantnagar facts.
• Do not promise savings before bills, meter boundaries and production context exist.
• Do not propose changes to paint, ventilation, welding or robot controls without engineering approval.

5.3 Opening hooks (email / call / WhatsApp)

“Welding and paint-shop utilities can be individually well managed yet still overlap into a costly UPCL demand or baseload pattern. We sit read-only on existing data, give the responsible owner one ₹-valued action, and verify it on the next bill.”

6. Risks, flags & sources

6.1 Integrity / controversy / regulatory (search explicitly)

Searches for Badve Pantnagar pollution, Belrise Pantnagar notice, Badve lawsuit, Belrise controversy and Belrise regulatory action found no verified unit-specific enforcement outcome. CPCB reporting on the Pantnagar common effluent-treatment plant concerns the estate operator/infrastructure and must not be attributed to Belrise without evidence. This is not a compliance clearance.

6.2 Data quality flags

Data quality flags

• Public sources confirm Pantnagar plant presence but not plant-specific electricity bills.
• The ₹35L-₹60L/month estimate is inferred from process mix and Band A screening.
• Public sustainability actions are company-wide and not uniquely tied to the Pantnagar units.
• Exact process split between Unit IX and Unit XII should be validated in the first call.
• The kit’s direct emails are inferred and must be confirmed.

Interpretation guardrails. The public record is strong enough to establish the two-facility footprint and broad component/process families, but not strong enough to reconstruct a Pantnagar energy balance. In particular, it does not show whether each facility has one HT connection, whether common utilities are shared, which coating technology is active, or the relationship between production volumes and monthly demand. A demand spike during a coating run can be operationally necessary; it becomes an opportunity only when the plant can safely move, stagger, reduce or avoid it.

The correct first deliverable is therefore a fact map, not a saving forecast. It should show the bill account, main meter, downstream feeder visibility, process owner, utility owner, normal production period, weather-sensitive equipment and the change-control route for each proposed action. This prevents three common errors: attributing a tariff rise to efficiency, claiming a low-output month as a saving, and asking a maintenance engineer to make a scheduling decision owned by production.

There is also a naming and procurement risk. “Badve” may remain familiar locally while legal, finance and public documents use Belrise. Use the exact legal entity printed on the invoice and purchase route, record the operating name preferred by the contact, and keep both facility references explicit. Do not assume a successful proof at one unit automatically creates access at the other; demonstrate the first result, then use the documented meter/process boundary to propose expansion.

For the first stakeholder meeting, ask to see a single representative UPCL bill, a simple shift/production calendar and a utility layout rather than requesting broad plant data. This creates a low-friction way to establish whether the hypothesis is real. It also identifies the individuals who can approve a safe operating test. If paint quality, ventilation or welding throughput cannot be protected, the candidate action is not suitable for a pilot.

Use a written baseline protocol: representative days, production measure, excluded shutdowns, invoice fields, approved action, owner and review date. It protects the maintenance team from unsupported attribution and gives leadership a clean decision record. This is especially valuable where two sites, mixed utilities and legacy naming otherwise obscure accountability.

6.3 Sources consulted

Sources consulted

• https://belriseindustries.com/infrastructure/uttarakhand
• https://belriseindustries.com/assets/site/docs/Belrise_Investor_Presentation_Q4FY25_16.06.25_FINAL.pdf
• https://belriseindustries.com/assets/site/docs/Final_Belrise_Investor_Presentation_Q1FY26_12.08.25.pdf
• https://belriseindustries.com/assets/site/docs/BELRISE_Intimation%20of%20Investor%20Presentation_11.11.2025.pdf
• https://www.arihantcapital.com/company-information/directors-report/38976