1. Company overview & snapshot

India Glycols Limited is a listed specialty chemicals, spirits, biofuels and industrial products manufacturer with Kashipur as its flagship integrated complex. Public company material describes Kashipur as a roughly 300-acre state-of-the-art manufacturing site spanning fermentation, distillation, biofuels, ethylene oxide, glycols, solvents, specialty chemicals, industrial gases and bottling, so this is not a single-process plant but a utility-heavy campus with multiple energy centers and competing load priorities.

Within the last 12 months, the company completed meaningful capacity additions at Kashipur: grain-based distillery capacity increased to 500 KLPD, bio-fuel ethanol capacity increased to 590 KLPD, and value-added chemical capacity was further expanded. Management commentary indicates the major capex cycle is now largely complete and the near-term focus shifts from expansion to cash flow, ramp-up and operational efficiency. That matters for Stamped because a site just coming off capex is more likely to care about proving bill-visible savings on existing assets than buying more hardware.

Ownership and governance quality are strong enough to support structured pilots: the company is listed, publishes BRSR disclosures, and runs an integrated management system. Plant leadership is not fully public, but the outreach kit identifies utilities and operations stakeholders at the Kashipur site, which fits the need for a plant-first, technically credible entry.

1.1 Legal identity & corporate structure

India Glycols Limited should be treated as listed Indian manufacturer; the Kashipur complex is the operating unit to qualify rather than treating group reporting as plant-level evidence. The immediate sales record must distinguish the corporate parent, the manufacturing legal entity, the physical site and the electricity-account holder. That distinction is commercially important: a group annual report can establish scale, but it does not prove a particular feeder, sanctioned demand, or a plant manager’s authority to approve a 90-day pilot. Obtain the latest invoice header, GST/legal name, authorised signatory and procurement path in the first discovery conversation.

1.2 What they make & where money comes from

The public product picture is bio-ethanol, distillery products, glycols, solvents, specialty chemicals, industrial gases and bottling products. This creates an energy hypothesis rather than a claim of exact process configuration. Production mix, utilization, campaign length and product-quality requirements determine whether energy is driven by a continuous base load, campaign peaks, or support utilities. Ask which product family, line and customer commitments dominate the site this quarter; that answer makes the initial Stamped scope specific and prevents generic efficiency messaging.

1.3 Plants, addresses & footprint

The pilot location is Kashipur integrated complex, Uttarakhand. Treat the address and plant boundary in the outreach kit as a working record and confirm it with reception, a current invoice or the plant team. Pantnagar, Rudrapur and Kashipur accounts can have separate industrial-estate, corporate and GST addresses. A successful pilot needs the exact HT account(s), feeder map and whether shared utilities sit inside or outside the initial scope.

1.4 Leadership & CRM map

Current useful contacts are P. K. Tripathi (electrical/power/utilities in the kit), plant leadership and operations leadership; confirm current titles before contact. The desired buying group is a plant/P&L sponsor, electrical or utilities technical owner, production representative, finance/bill reviewer and any IT/OT approver. Start with the technical contact only to identify the bill owner and operational constraint; do not assume that a LinkedIn title proves signing authority. Record each contact’s current role, site presence, preferred route and whether they can share two anonymised bills.

1.5 Recent news (24 months) & timing for Stamped

FY25 disclosures and management commentary describe grain-distillery and ethanol capacity additions at Kashipur and a shift from capex completion to ramp-up and cash generation. The timing implication is practical: after a change in capacity, product mix or utility policy, historical baselines can be misleading. Stamped should propose an observation-and-prescription window with production context, not promise a percentage saving from prior-year intensity alone. No verified 24-month news item should be invented where disclosure is thin.

1.1 Legal identity & corporate structure

India Glycols Limited should be treated as listed Indian manufacturer; the Kashipur complex is the operating unit to qualify rather than treating group reporting as plant-level evidence. The immediate sales record must distinguish the corporate parent, the manufacturing legal entity, the physical site and the electricity-account holder. That distinction is commercially important: a group annual report can establish scale, but it does not prove a particular feeder, sanctioned demand, or a plant manager’s authority to approve a 90-day pilot. Obtain the latest invoice header, GST/legal name, authorised signatory and procurement path in the first discovery conversation.

1.2 What they make & where money comes from

The public product picture is bio-ethanol, distillery products, glycols, solvents, specialty chemicals, industrial gases and bottling products. This creates an energy hypothesis rather than a claim of exact process configuration. Production mix, utilization, campaign length and product-quality requirements determine whether energy is driven by a continuous base load, campaign peaks, or support utilities. Ask which product family, line and customer commitments dominate the site this quarter; that answer makes the initial Stamped scope specific and prevents generic efficiency messaging.

1.3 Plants, addresses & footprint

The pilot location is Kashipur integrated complex, Uttarakhand. Treat the address and plant boundary in the outreach kit as a working record and confirm it with reception, a current invoice or the plant team. Pantnagar, Rudrapur and Kashipur accounts can have separate industrial-estate, corporate and GST addresses. A successful pilot needs the exact HT account(s), feeder map and whether shared utilities sit inside or outside the initial scope.

1.4 Leadership & CRM map

Current useful contacts are P. K. Tripathi (electrical/power/utilities in the kit), plant leadership and operations leadership; confirm current titles before contact. The desired buying group is a plant/P&L sponsor, electrical or utilities technical owner, production representative, finance/bill reviewer and any IT/OT approver. Start with the technical contact only to identify the bill owner and operational constraint; do not assume that a LinkedIn title proves signing authority. Record each contact’s current role, site presence, preferred route and whether they can share two anonymised bills.

1.5 Recent news (24 months) & timing for Stamped

FY25 disclosures and management commentary describe grain-distillery and ethanol capacity additions at Kashipur and a shift from capex completion to ramp-up and cash generation. The timing implication is practical: after a change in capacity, product mix or utility policy, historical baselines can be misleading. Stamped should propose an observation-and-prescription window with production context, not promise a percentage saving from prior-year intensity alone. No verified 24-month news item should be invented where disclosure is thin.

2. Energy profile

2.1 Bill band, tariff & demand

DISCOM / supply (name early): UPCL is the working distribution-company assumption for this Uttarakhand industrial location; verify account name, tariff category, sanctioned/contract demand, connection voltage, meter boundary and open-access/captive arrangements. Working bill band: ₹20–₹35 Cr/month [~] at the integrated complex; standalone FY25 power-and-fuel expense is cited in the kit at ₹361.88 Cr, but that line is not a monthly electricity bill. This is a research estimate, not an invoice-derived fact. Request two recent UPCL HT invoices and 15-minute demand data (if available) before sizing value. Inspect demand charges, ToD slots, PF incentive/penalty, reactive-energy treatment, billing-demand ratchet and any multiple-feeder aggregation.

2.2 Generation, fuel & renewables

Do not assume grid-only supply. Ask whether DG, captive power, steam turbines, boilers/thermic-fluid systems, rooftop solar, open access or a PPA changes the marginal-cost calculation. A renewable claim reduces neither MD charges nor the need to sequence flexible loads. Map which loads can move into lower-cost ToD or solar windows and which are constrained by recipe, quality, safety or dispatch commitments. Fuel and thermal systems should be measured separately from electrical-bill savings so the pilot does not double-count an outcome.

2.3 EnMS, PAT, ISO, BRSR

Public management-system evidence should be used as a signal of data maturity, not as proof that every prescription is already covered. Confirm whether the site has ISO 50001, ISO 14001, PAT/CCTS obligations, BRSR reporting, SEC targets, an energy manager and monthly energy reviews. Where an EMS/DCS/SCADA exists, Stamped’s entry is read-only and additive: use existing tags and bills to turn observed deviations into named tasks with ₹ estimates and invoice reconciliation. Where only meter exports exist, begin with a lighter feeder-and-bill path.

2.4 Likely ₹ leak categories (hypothesis)

Likely operating loads are distillation, fermentation, boilers, turbines, evaporation, compressors, cooling towers, pumping and chemical-process auxiliaries. The first hypotheses are: (1) maximum-demand spikes created by coincident starts; (2) furnace/heater/thermal hold or preheat that continues through breaks and changeovers; (3) idle compressors, pumps and auxiliaries; (4) compressed-air pressure drift and off-shift HVAC/chiller operation; (5) PF drift; and (6) flexible-load scheduling outside favourable ToD/solar windows. Each is a hypothesis to test against meter traces, production events and UPCL invoice lines—not an allegation of poor operation.

3. Operations, equipment & digital stack

3.1 Process flow & critical loads

Build a one-page process map in discovery: raw-material receipt → preparation/formulation or reaction → heating/cooling or processing → transfer → filling/finishing → QA → dispatch. Mark batch starts, heat-up/hold, CIP/changeover, packing starts, utility headers and large motors. The key question is not simply “what consumes kWh?” but “which controllable operating event produces cost at the demand, tariff, PF or baseline level?” Capture production constraints before recommending sequencing.

3.2 Shifts, seasonality, production pattern

Determine if the site is continuous, campaign-based, multi-shift or heavily seasonal. Record scheduled breaks, weekly shutdowns, maintenance windows, SKU/changeover frequency and dispatch-driven overtime. A valid bill comparison must normalise for production volume, weather-sensitive HVAC, production mix and commissioning/ramp-up. If throughput is unstable, set success metrics around avoidable peaks, idle hours and verified invoice components rather than gross kWh alone.

3.3 Automation, metering, SCADA/EMS/DCS

No named plant-specific SCADA/EMS vendor is assumed unless independently sourced. Start with a data-access inventory: main-meter interval data; feeder/sub-meter exports; DCS/PLC historian tags; boiler/TFH logs; compressor/chiller status; production schedule; and two to six UPCL bills. Path A is a read-only connection/export from existing systems. Path B is structured CSV or meter export plus a production-event log. Both paths must exclude PLC writes, recipe changes and unapproved remote control.

3.4 Capex / tech projects affecting energy

Ask about new lines, automation, solar, utility upgrades, VFDs, compressor replacement, boiler work and product launches in the last 24 months. These can create a false “before” baseline and may have warranties or safety constraints. Stamped should position post-capex work as operational verification: ensure the asset is scheduled and used to achieve the expected bill result, rather than claiming credit for capex it did not cause.

4. Stamped Energy fit analysis

4.1 ICP scorecard

Geography passes: Uttarakhand gives a UPCL industrial context and practical proximity. Vertical/process fit is likely positive, subject to confirmation of production intensity. Bill qualification remains estimated until a current invoice proves ≥ ₹30 lakh/month. Data maturity is unknown-to-medium/high depending on the site; decision speed depends on local authority and corporate governance. The account passes to a 20-minute discovery call, not automatically to a full integration.

4.2 Fit score rationale

The kit’s fit score is an outreach prioritisation score, not a financial guarantee. Score strength comes from plausible process loads, potential HT bill exposure and a plant-operational entry. Score deductions come from disclosure gaps, bill uncertainty, entity ambiguity or MNC procurement. The initial call must explicitly qualify bill band, site authority, accessible data and one measurable problem before committing engineering effort.

4.3 Wedge (parser-critical)

The strongest wedge is: cross-utility dispatch after expansion: stagger high-electrical-load starts, relate steam/turbine conditions to grid draw, and assign each avoidable UPCL MD or PF cost to an owner. The message is “what should change tomorrow, who owns it, what ₹ line should move, and how will the UPCL invoice verify it?” This avoids positioning Stamped as a maintenance AMC, new dashboard, solar EPC or replacement EMS.

4.4 Objections & competitors

Likely alternatives are internal electrical/continuous-improvement teams, existing EMS/SCADA analytics, an ISO/energy consultant, an equipment OEM, and “we already have solar.” Response: Stamped does not replace controls or sell capex; it prioritises operational prescriptions, attaches an owner and reconciles results to the bill. For a sophisticated site, offer a small read-only proof with explicit security/data boundaries. For a private site, lead with a concrete invoice problem rather than AI, ESG or digital-transformation language.

4.5 Pilot design

Start with one meter boundary or one controllable utility/process cluster for 90 days. Weeks 1–2: validate UPCL bills, meter coverage, production context and baseline. Weeks 3–8: issue weekly ranked prescription cards covering MD sequencing, idle loads, thermal hold, air/HVAC, PF or tariff dispatch. Weeks 9–12: compare normalised bill components and production-adjusted indicators. Success: at least one action has an owner, measurable execution evidence and a defensible ₹/invoice movement. Kill criteria: bill below threshold, no data access, no plant owner, unstable operation without usable normalisation, or no controllable lever.

5. Before you reach out

5.1 Discovery checklist

• Confirm the exact legal entity, site address, UPCL account name, tariff and whether this is an HT/EHT bill.
• Verify monthly bill band in ₹ lakh/₹ Cr, sanctioned demand, billing demand and PF line.
• Identify the highest-load process, utility owner, shift pattern and current production constraint.
• Ask for the most recent MD event: when, what started, what it cost and who acted.
• Ask whether heaters/thermal systems, compressors, chillers, AHUs or pumps remain live during breaks/changeovers.
• Confirm existing EMS/SCADA/historian and what can be exported read-only.
• Confirm solar/captive/open-access context before discussing tariff-smart dispatch.
• Identify whether a site sponsor can approve a bounded 90-day proof and who must clear IT/OT.
• Request two UPCL invoices, interval demand/energy data and a production/event calendar.
• Define a success measure tied to bill lines and production normalisation, not a generic dashboard KPI.

5.2 Do not lead with

• Do not lead with dashboards, AI buzzwords, generic kWh claims or a promised percentage reduction.
• Do not lead with ESG, carbon or ISO reporting; lead with a controllable ₹ line on the UPCL bill.
• Do not imply control-system writes, replacement of the EMS, compressor maintenance or solar EPC.
• Do not state the estimated bill band as fact; ask to verify it.
• Do not attach unrelated regional NGT matters to this company.

5.3 Opening hooks (email / call / WhatsApp)

“Plants of this type often lose money in MD overlap, thermal holds, idle air/HVAC and PF drift. We sit read-only on your existing data, send a named operational fix with a ₹ estimate, and reconcile the result to the next UPCL invoice.” Then ask: “Which one hurts more today—MD at starts, utility hold through changeovers, or off-shift auxiliaries?” A valid next step is two bills plus the correct electrical POC, not a platform demo.

6. Risks, flags, controversies & sources

6.1 Integrity / controversy / regulatory (search explicitly)

• A historical NGT/CPCB/UKPCB compliance context is documented: India Glycols’ Kashipur chemical and distillery units were named in river-pollution monitoring/compliance material in 2020–22. This dossier does not infer a current violation or outcome; no specific 2024–25 company-targeted NGT action was located.
• Search scope included company/legal-name variants with “NGT”, “PCB”, “pollution notice”, “lawsuit”, “environmental compensation”, “labour dispute”, “tax raid” and 2024–2026 terms, plus Uttarakhand-specific results. Search-engine coverage is not a legal clearance.

6.2 Data quality flags

• The UPCL service, bill band, sanctioned demand, tariff and site-meter boundary are research hypotheses unless supported by an actual invoice.
• Leadership titles, email patterns and LinkedIn availability must be confirmed immediately before outreach.
• Process, shift and automation details contain informed inference where public site disclosures are thin.
• Separate plant-specific fact from group-level ESG, revenue, certification and capacity disclosures.

6.3 Sources consulted

• India Glycols FY25 annual/BRSR and Q4 FY25 call materials; India Glycols compliance page; MoEFCC environmental-clearance material; NGT/CPCB status material in Shailesh Singh matters; Screener/BSE filings.
• Existing outreach kit and campaign lead-report reference; ICP — Large North India Manufacturers; Stamped cold-call capability points.

6.4 Evidence discipline and next research actions

This dossier deliberately separates three evidence classes. Verified public facts are sourced corporate disclosures, public environmental-clearance filings, official certification material and named official releases. Directional operating hypotheses use the disclosed industry/process profile to identify what should be checked; they are not presented as a claim about a specific machine, event, bill or control failure. Commercial estimates—especially electricity spend, annualised opportunity and savings percentage—remain estimates until the site provides a current invoice and production context.

The practical research sequence after first contact is: first, verify entity and invoice ownership; second, collect two UPCL invoices and document tariff, demand and PF lines; third, identify the top three load events with the electrical/utility owner; fourth, map production constraints that cannot be moved; fifth, agree the smallest controllable boundary for a 90-day trial. This ordering protects credibility. It avoids proposing that a process, quality requirement or safety-critical utility should be altered merely because it appears energy intensive.

For any invoice-derived opportunity model, calculate demand, energy, reactive/PF and applicable tariff components separately. Normalise against operating hours, tonnes/batches or another valid production proxy; a lower bill is not proof of operational savings if production fell. Record baseline dates, holiday/shutdown days, exceptional maintenance, new-line commissioning, fuel or captive-generation changes and weather-sensitive HVAC conditions. Keep a decision ledger: recommendation, owner, due date, operational constraint, expected ₹ line, implementation evidence and observed invoice result. This is the difference between a one-off audit observation and a bill-verifiable operational system.

Security and governance should be addressed before data transfer. Confirm the permitted interface—historian export, meter CSV, secure file exchange or supervised read-only access—plus retention, access roles and plant-IT/OT approvals. No proposal should imply changing PLC logic, recipes, interlocks, setpoints or operator authority. If a corporate procurement route is unavoidable, preserve the plant-level hypothesis and evidence package so the request does not become a generic software evaluation.

Finally, treat adverse information proportionately. A negative search does not establish that no legal, environmental, labour or financial issue exists. Conversely, regional environmental litigation is not evidence against an unrelated site. When a named proceeding exists, cite its source, date, procedural status and exact entity; do not imply guilt, current non-compliance or business impact without reliable evidence. Re-check material sources and contact tenure immediately before a campaign is sent.