Also like this

Peer sidcul plants in Pantnagar — useful for social proof on calls.

SIDCUL
Deep research dossier

Pricol Ltd

Stamped-relevant intel for pre-outreach due diligence on Pricol's Pantnagar plants.

8/10 ICP fit
UPCL DISCOM
Check EnMS Energy mgmt
Pantnagar Plant
SIDCUL Rudrapur belt
Bill band

₹251 crore

Entry angle

**use Factory VI/VII’s existing digital data to assign a demand or shared-utility action, then verify the effect on the next UPCL bill.** The message is: "You already monitor operations; we help convert that into specific electricity-cost actions verified on the next UPCL bill." FY25 reporting adds a useful…

!
Top flag

Public sources confirm Pantnagar plant locations and broad product families, but exact energy-intensive equipment at each of Plant VI and VII is not fully disclosed.

Primary champion Sanjay Kr Saini Head of Maintenance

1. Company overview & snapshot

Pricol is a listed automotive technology and precision-engineering company with a broad manufacturing footprint across India and overseas. Pantnagar is part of that network through Plant VI and Plant VII in SIDCUL Rudrapur/Pantnagar, and public directory and company material tie these plants to instrumentation, pumps, sensors and related automotive components.

What makes Pricol particularly relevant is not just size but its current operating philosophy. Recent public material shows a company actively pushing digital manufacturing, predictive maintenance, real-time monitoring and eventually prescriptive analytics via an AI center of excellence. At the same time, Pricol’s reporting emphasizes sustainability goals including zero-waste ambition and a target of moving to 100% renewable energy across facilities by 2026.

For Stamped, that combination matters. Pricol is likely more digitally mature than the average auto-component prospect, which means the pitch cannot be “we bring visibility.” It has to be “we tie your existing data and your electricity bill together into specific, assigned actions that a plant team can verify in 90 days.”

Pricol Limited is a listed Indian public company (NSE: PRICOLLTD; BSE: 534708) headquartered in Coimbatore. Its Pantnagar footprint is part of a multi-plant group, so a local operational sponsor can validate the problem but information security, procurement and commercial approval may involve corporate functions. This is a different buying motion from an owner-led SIDCUL plant: early outreach should seek permission for a tightly bounded plant proof, not approval for a group digital-transformation programme.

FY26 results reported by the company through major business publications give the account additional commercial context: consolidated total income was nearly ₹4,000 crore and full-year PAT was about ₹251 crore. These are group results; they do not disclose Pantnagar economics or the local electricity bill. They do, however, make a short-cycle plant-P&L case more credible than a pitch based only on general sustainability positioning.

1.2 What they make & where money comes from

Public information associates the Pantnagar factories with instrumentation, oil pumps, fuel-level sensors, gear-metering screws and related vehicle-component production. Across the group, Pricol serves driver-information and connected-vehicle systems, actuation/control and fluid-management products, and precision products. Exact revenue by Plant VI, Plant VII, product family, customer programme, or OEM is not publicly established in the reviewed sources. Treat all plant-specific process descriptions as discovery questions rather than assumptions.

The group’s FY27 capital plan reportedly ranges from ₹680 crore to ₹700 crore across automotive controls, fluid management, polymers, driver information and connected-vehicle solutions. Management has cited capacity constraints in plastics and a pipeline of new business. This creates an operating context where uptime, repeatable quality and utility cost all matter, but it does not establish that Pantnagar receives any particular line or capital allocation.

1.3 Plants, addresses & footprint

The working target is the two Pantnagar/Rudrapur sites commonly described as Factory/Plant VI at Plot 11 and Factory/Plant VII at Plot 45, Sector 10/11 references within IIE Pantnagar. Public sources are inconsistent about the sector and plot wording, while the FY25 report identifies Plot 45, Sector 11, Integrated Industrial Estate, Pantnagar, Rudrapur 263153. Keep the two plants separate in CRM until the legal consumer name and connection boundary are confirmed. The official contact route published in the lead report is +91 5944 250317 / 250318 and connect@pricol.com; neither proves the identity of a specific utilities owner.

1.4 Leadership & CRM map

Recent FY26 coverage says Vikram Mohan succeeded Vanitha Mohan as Chairman and Managing Director. That leadership transition is relevant for corporate context but is not a reason to start at CMD level. The useful buying committee is a validated Pantnagar plant head, maintenance/electrical or utilities owner, production representative, local finance/controller representative, and—only when needed—corporate IT/security or sustainability. Sanjay Kr Saini, Mahendra Singh Adhikari and Neeraj Kumar are publicly surfaced technical leads to verify, not confirmed authority or current employment status.

1.5 Recent news (24 months) & timing for Stamped

FY26 results reported in May 2026 show revenue growth and materially higher profit, alongside management’s warning that geopolitical developments, currency volatility, commodity prices and freight could pressure margins. This strengthens a margin-defence conversation, but only if it remains operational and fact-based: bill mechanics and avoidable utility load, not a claim that the local plant is underperforming.

The subsequent reported ₹680–₹700 crore FY27 capex cycle is a second timing cue. Management said it intends to expand capacity and execute new business wins as its prior cycle has ended and utilisation is high. For Stamped, the appropriate relevance is that added machinery and changing schedules can make historical energy baselines stale. A pre- or post-capex plant diagnostic can document which cost movements are explained by production growth and which remain controllable; it should never be positioned as an alternative to the capex programme.

Coverage also describes a potential demerger of the driver-information and connected-vehicle-systems business into Pricol Autotech. This is a corporate portfolio matter, not a Pantnagar operating fact. Its practical CRM consequence is simply to verify legal entity, signer and data-access ownership before moving beyond a local pilot.

2. Energy profile

DISCOM / supply (name early): UPCL. Pantnagar/Rudrapur is in Uttarakhand. Exact sanctioned demand and utility configuration for Plants VI and VII are not public, but the two-factory setup, coupled with die-casting, assembly, testing and utility support, should put the account in or above the ICP range. A sensible working estimate is roughly ₹30 lakh to ₹60 lakh per month [~] across the two co-located plants, pending confirmation of metering boundaries.

Pricol’s public sustainability posture is advanced. The company has stated a goal of 100% renewable energy by 2026, and public reporting plus media coverage indicate high renewable-energy penetration and serious work on emissions reduction. That makes energy a board-visible topic. However, it also means Stamped must stay away from sounding like another broad digital-transformation or ESG tool.

Likely plant-level pain points are more specific: overlapping startups between Plant VI and VII, utility base-load inefficiency, compressed-air and HVAC drift, test-bench and assembly-line variability, and difficulty translating shop-floor events into bill-causality that local teams can act on.

The crucial qualification is the billing boundary. The two facilities might have independent UPCL connections, separate contract-demand records, or a shared incomer with internal submetering; those conditions produce different savings logic. A combined bill estimate must therefore never be quoted as a local fact. Ask for two recent invoices per legal consumer, the tariff schedule, sanctioned demand, billing demand, PF/reactive adjustment and 15-minute kW/kWh before deciding whether a demand, ToD, base-load or per-unit-energy problem is even present.

3. Operations, equipment & digital stack

Pantnagar appears to manufacture a mix of dashboard instruments, oil pumps, fuel-level sensors, gear metering screws and other vehicle components. Broader Pricol manufacturing capability includes pressure die casting, plastic injection molding, PCB assembly, robotic lines and in-house machine-building capability. Not all of that should be assumed to be concentrated at Pantnagar, but it does indicate a company comfortable with automation-rich production.

Digital maturity is the strongest public signal in this prospect. Recent press coverage describes real-time monitoring, historical-data exploitation, predictive maintenance, early-warning systems, IoT-based shop-floor digitization and movement toward prescriptive intelligence. That means existing data plumbing probably already exists, at least at a respectable level.

This is precisely why the Stamped wedge should be narrowed to plant economics. Pricol likely already tracks uptime and reliability better than many peers; the unresolved gap may be cost attribution across shared utilities and across the two Pantnagar factories. A read-only bill-verification layer can sit beside their current stack without trying to replace it.

3.1 Process flow & critical loads

The site walk must establish which operations actually run at each plant. Candidate load families include compressor systems, HVAC, lighting, material handling, test areas, machine tools, moulding or die-casting auxiliaries, and assembly cells; none should be asserted as a Pantnagar load without confirmation. For each confirmed load family, capture its feeder identity, production dependency, shift pattern, safe operating range, and whether an action can be reversed without affecting an OEM-approved quality process.

3.2 Shifts, seasonality & production pattern

Auto-component demand can vary with OEM schedules, model launches, dispatch cycles and shutdown days. This makes a simple month-on-month bill comparison weak evidence. The baseline should annotate shift calendar, planned maintenance, product/part mix, output, rework or test activity, ambient conditions affecting HVAC, and any DG run hours. If a high-demand event coincides with a planned line recovery after a shutdown, the right result may be “necessary event,” not a saving recommendation.

3.3 Automation, metering, SCADA/EMS/DCS

No named Pantnagar meter vendor, historian, EMS or SCADA system was independently verified. The public digital narrative is evidence of company capability, not a data-access guarantee. Path A uses approved, read-only extracts from existing meters, historian or SCADA plus production context. Path B starts with main-meter interval data, bills and shift records when feeder access needs central approval. Neither path needs PLC writes, machine-control changes, new hardware or a claim that Stamped will replace Pricol’s existing systems.

3.4 Capex / tech projects affecting energy

The FY27 capex cycle and new business pipeline may alter equipment mix, utilisation and daily loading. Freeze a documented baseline before a major line change where possible, then re-baseline after commissioning rather than attributing all movement to an operational action. This is a useful differentiator for a finance stakeholder: a bill-verified result must isolate volume, product mix, renewable settlement and tariff effects from the proposed utility action.

4. Stamped Energy fit analysis

Pricol is a good Band A fit, but the route in is more nuanced than with privately held foundry-style shops. The strongest wedge is: use Factory VI/VII’s existing digital data to assign a demand or shared-utility action, then verify the effect on the next UPCL bill. The message is: “You already monitor operations; we help convert that into specific electricity-cost actions verified on the next UPCL bill.” FY25 reporting adds a useful credibility signal: Pricol reports 72% renewable energy consumption and targets 100% renewable energy by 2026; this is group-level evidence, not a Pantnagar allocation.

Stamped proof points that should land are read-only integration, no PLC writes, no new hardware, and a tight 90-day program with kill criteria. The twin-factory story is also useful because co-located plants often create exactly the kind of MD overlap and utility-sharing inefficiency that a site team can feel but not fully isolate.

Main alternatives are Pricol’s own digital and maintenance organization, incumbent EMS/IoT vendors and internal continuous-improvement projects. Stamped only wins if it remains tightly scoped to rupee-value capture rather than trying to compete with Pricol’s broader digital roadmap.

The fit score remains 8/10 conditional on bill and access confirmation. Geography, manufacturing scale, a two-plant complexity hypothesis and reported digital maturity are positives. The hard Band A gate remains unverified because there is no public monthly bill. Reduce the score if the plants are below the ₹30 lakh/month [~] threshold, lack interval data, have no plant sponsor able to action findings, or are already operating a mature bill-to-action workflow that leaves no identifiable gap.

The proposed 90-day scope is one legal billing account and one load family. Baseline four to eight weeks against production, shift, weather-sensitive HVAC use, renewable settlement, PF and recorded MD. At day 45, either execute a reversible, production-safe action with an agreed owner or stop. Success is one bill-reconciled result with normalisation notes; failure is valid if data quality, controllability or the account boundary makes the causal claim unsupported. Only after that evidence exists should Pricol consider comparison across Plants VI/VII or another group facility.

5. Before you reach out

  • Confirm whether Plants VI and VII are billed separately or through one UPCL boundary; this changes the pilot design.
  • Ask what the plant team already sees daily versus what only appears at month-end on the bill.
  • Use their digital maturity as a compliment, then pivot: “Where does today’s stack still fail to assign rupee ownership for bill movements?”
  • Avoid leading with AI. They already have a digital narrative and may resist another broad platform story.
  • Confirm the exact product/process mix at Pantnagar today; public sources mix companywide capabilities with plant-level products.
  • Position the offer as an operational spend project owned by maintenance/utilities or plant leadership, not as an enterprise IT initiative.
  • Probe for demand-charge overlap between Factory VI and VII, especially around shifts, startup windows and shared utilities.
  • If they ask about differentiation from current analytics, anchor on next-bill verification and assignment of actions via existing workflows.
  • Confirm whether the local account name is Pricol Limited or another group entity before requesting bills or connectivity.
  • Ask whether any FY27 capex or new-programme commissioning will change the baseline during a potential 90-day window.
  • Ask finance which bill movement creates the most internal attention: maximum demand, energy charge, PF, ToD, fixed charge or renewable-settlement variance.
  • Do not promise that co-location means a shared incomer, shared utilities or a demand-overlap problem; verify all three.

6. Risks, flags & sources

Data quality flags:

  • Public sources confirm Pantnagar plant locations and broad product families, but exact energy-intensive equipment at each of Plant VI and VII is not fully disclosed.
  • Renewable-energy and AI/digital statements are often company-level rather than Pantnagar-specific.
  • The exact current address mapping between Plant VI, Plant VII, plot numbers and sector references varies slightly across public sources.

Sources consulted:

Pricol Limited is a listed Indian automotive-technology company (NSE: PRICOLLTD; BSE: 534708). Its FY25 annual report describes a network of 14 India manufacturing plants plus an Indonesian plant and international offices. The two Pantnagar references in the public record need care: Plant VI is associated with Plot 11, while the FY25 report identifies Plot 45, Sector 11, Integrated Industrial Estate, Pantnagar, Rudrapur 263153. Treat the sector/plot mapping as a contact-verification task rather than a reason to merge two electricity accounts in the model.

The company’s public financial and sustainability reporting supports a professionally managed, multi-site account, not a local owner-led sale. That normally means plant engineering can identify the operating case but corporate functions may determine security, procurement and commercial terms. The right goal for first contact is therefore a bounded site proof with a named Pantnagar sponsor, not an enterprise-wide “digital transformation” proposal.

6.2 Energy, renewable and bill mechanics

DISCOM / supply: UPCL. The Pantnagar location is in Uttarakhand; verify the legal consumer name, HT category, account count, contract demand, tariff and whether Plants VI and VII share utilities. The ₹30 lakh–₹60 lakh/month [~] band is an account-level hypothesis based on a two-plant automotive footprint. It is not a disclosed bill and must be verified from two invoices before using Band A economics.

FY25 material says Pricol consumed 72% renewable energy and is targeting 100% renewable energy across facilities by 2026; the company sustainability page separately describes rooftop solar and green-energy purchase agreements. These are group claims. They do not show the Pantnagar renewable share, roof capacity, wheeling arrangement, or whether imported electricity and demand charges sit on the same bill. Renewable procurement does not remove the operating problem: it makes it more important to separate production demand, grid draw, solar timing and avoidable maximum-demand events.

Discovery should request six months of UPCL bills, 15-minute import/demand data, PF and ToD components, solar/open-access settlement where applicable, Plant VI/VII production calendar, and shared-utility operating states. Start with questions that can falsify the opportunity: Are the plants separately billed? Which shifts cause recorded MD? Does the plant already have a per-part energy baseline? Can an electrical owner distinguish compressor, HVAC, test, die-cast and assembly load at feeder level? No savings number should be promised until those answers exist.

6.3 Operations and data-access design

Public sources mix Pantnagar-specific facts with Pricol’s broader capability set. It is safe to say the Pantnagar footprint is part of a company making instruments, pumps and sensor products; it is not safe to assert that every group process—such as PCB assembly, injection moulding or pressure die casting—is in either specific Pantnagar plant. Use a site walk-through to identify the actual critical-load map: incomer, compressor house, HVAC, process/test areas, material handling and production cells.

Pricol’s public digital-manufacturing discussion implies a mature environment: real-time monitoring, historical data use, predictive maintenance and IoT initiatives. That creates two parallel requirements. First, Stamped must integrate read-only with existing meter/SCADA/historian paths where approved, and never position itself as a replacement. Second, the local team must identify the gap that their existing stack does not solve: conversion of a production/utility pattern into a named, rupee-valued action with invoice reconciliation.

Path A is appropriate if time-series feeder, production and bill data can be read without a long central IT project. Path B is a limited diagnostic if access is delayed: main-meter interval data, two bills and production-shift records can identify demand, PF and ToD questions; no machine-level claim should be made until submeter or historian data is available. In either case, no PLC or control-system writes are required.

6.4 Pilot, objections and CRM sequencing

The pilot should select one plant and one measurable load family—not both sites and every utility. A defensible first hypothesis is start-up overlap or shared-utility baseload between Plants VI/VII. Baseline four to eight weeks against product mix, output, shift, weather-sensitive HVAC use, RE settlement, PF and recorded MD. The success test is one implemented action whose mechanism and next-bill reconciliation are agreed in advance; the kill test is unavailable data, no controllable variance, or an unresolved billing boundary.

Likely objections are predictable. “We already have digital systems” is answered by “we do not replace them; we assign the next bill-linked action.” “We already have renewable power” is answered by “solar changes supply, but does not automatically eliminate demand or idle-load leakage.” “Corporate must approve” is answered by proposing an architecture-light, read-only plant diagnostic that produces a decision memo rather than a group rollout commitment.

Primary CRM target remains an authenticated Pantnagar maintenance/utilities or plant lead; Sanjay Saini and Mahendra Singh Adhikari are leads to verify, not confirmed decision authority. The plant head sponsors operating trials. Finance validates bill outcomes. Sustainability can use the M&V output only after a P&L outcome is established. Never use inferred personal email addresses as verified contact data.

6.5 Integrity / controversy / regulatory

Targeted review of the FY25 annual-report material, official sustainability pages, BSE filings and current public web results did not surface a verified Pantnagar-specific pollution order, material litigation outcome, fraud allegation or regulatory controversy to state in outreach. Public reports do identify corporate-level execution risks: FY26 management commentary cited geopolitical tension, currency volatility, commodity prices and freight costs, while the company is entering a new capex cycle. These are business-context risks, not allegations of misconduct and not evidence of a local plant issue. This is not a claim of full compliance. Search terms included “Pricol Pantnagar pollution”, “notice”, “NGT”, “penalty”, “lawsuit”, “fraud”, “controversy”, “capex”, and “demerger”. Before sending any executive outreach, check the latest stock-exchange disclosures and confirm that a named individual still holds the role shown.

6.6 Additional sources consulted

6.7 Measurement plan and account-specific questions

Before a commercial proposal, establish the billing boundary in writing. If Plant VI and Plant VII have separate UPCL service connections, calculate baseline and savings per account; do not aggregate them merely because they are co-located. If they share an incomer but have separate production areas, map the shared compressor, HVAC, lighting, water, test and material-handling feeds before assigning a cost to a line. Request interval kW/kWh, PF, maximum demand, tariff schedule, sanctioned demand, billing demand, reactive-energy adjustment, diesel-generator run hours, RE schedule and production/shift data. The objective is to explain bill movement rather than to infer it from a dashboard.

Useful discovery questions are:

  • Which single bill component—MD, energy, PF, ToD, or fixed charge—has generated the most internal discussion in the last three invoices?
  • Are start-up windows formally sequenced across Plants VI and VII, or left to department routines?
  • What load remains during meal breaks, weekly shutdowns, changeovers and low-volume shifts?
  • Which assets are feeder-metered, and which are only visible within an EMS/BMS or machine PLC?
  • Has the renewable transition altered the way the plant decides when flexible work should run?
  • Who can approve an operational trial, and who will sign the bill-reconciliation method?

For a first prescription, prefer an action that is reversible, production-safe and independently measurable: a staggered non-critical start, documented compressor-pressure reset during a stable shift, correction of an off-shift utility schedule, or a PF-drift investigation before capacitor capex. Exclude any action that changes validated product parameters, safety interlocks, customer quality requirements or PLC logic. A result should be reported as measured change with normalisation notes, not as “AI savings.”

The account has a credible land-and-expand path only after local proof. A successful Pantnagar diagnostic could be compared with a second plant using the same bill methodology, but Pricol’s different product families, locations and renewable arrangements mean a cross-plant benchmark needs like-for-like operating context. The commercial handoff should therefore be a one-page operating result: original hypothesis, data quality, prescribed action, execution owner, measured impact, counterfactual caveats and next decision. This format gives plant engineering, finance and corporate sustainability a common record without turning the pilot into a reporting project.