Deep Research ? Forace Polymers Private Limited (Haridwar)

This dossier separates public facts from operating hypotheses. [~] means an estimate, [dir] means a directory-derived item, and [!] means a point that must be verified with the plant. No invoice, personal email, or legal outcome is inferred here. The practical purpose is to make the first conversation specific while retaining a hard stop if the bill, decision authority, or data boundary does not qualify.

1. Company overview & snapshot

1.1 Legal identity & corporate structure

Forace Polymers Private Limited is a Haridwar-based private manufacturer founded in 1980. Public company material identifies a specialised resin/foundry-consumables business; incorporation capital and charges need an MCA check before contracting.

For CRM purposes, record the contracting legal entity shown on the electricity bill before any commercial document is issued. Parent-level reporting, a group website, or a brand name may not be the entity that carries the Pantnagar/Kashipur/Kotputli connection. This distinction matters because a plant-level pilot needs an accountable bill owner, a data approver, and a signatory; it should not begin as an open-ended corporate transformation discussion.

1.2 What they make & where money comes from

Forace makes phenolic and furan resins, refractory coatings, releases, core glues, foundry consumables and resin-coated sand. Public brochure capacity is 60,000 MT binders, 30,000 MT coatings and 36,000 MT resin-coated sand per year.

The product mix informs the energy conversation but does not prove a utility configuration. It indicates where production timing and common services may create controllable cost: large heat-up events, hygienic utilities, forming lines, material movement, packaging, or environmental conditioning. Stamped should treat all exact equipment counts, cycle times, output volumes and energy intensity as discovery questions, not pitch claims.

1.3 Plants, addresses & footprint

Core manufacturing is at 10th KM Stone, Haridwar?Delhi Road, Bahadrabad, Haridwar 249402. Company material also describes units for coatings/consumables and resin-coated sand. Confirm unit/feeder boundaries.

The recommended pilot boundary is the site named in the outreach kit. A pilot is stronger when it starts behind one bill or an identifiable common-utility feeder, rather than attempting to aggregate several plants, warehouses, offices or captive-generation settlements. Confirm whether separate feeders, leased buildings, or group entities change the comparison basis.

1.4 Leadership & CRM map

The paired kit names Vikas Garg as MD routing hypothesis, with Sonia Garg, Dipak Kumar Ghosh and Jashveer Singh as possible validators. Confirm each role and authority directly.

The first meeting should include a plant P&L owner and the electrical/utility owner. Production is essential when a recommendation changes timing; finance or procurement becomes relevant only after the team agrees on a defined, read-only 90-day experiment. The champion shown in the paired outreach kit is a routing hypothesis based on public profiles, not a claim of authority or current employment.

1.5 Recent news (24 months) & timing for Stamped

Company materials emphasise DCS, SAP HANA and WMS. A reported August 2024 fire is a safety and continuity context, not an outreach hook. Public event activity indicates continued market presence.

Timing should be driven by operating reality. Expansion, commissioning, new leadership, renewable-energy investment, TPM recognition, restructuring or safety recovery can all create a useful opening, but none is a reason to promise savings before reviewing the bill and production calendar. The best near-term question is: what did the last two bills contain that the operating team cannot presently explain or assign?

2. Energy profile

DISCOM / supply (name early): UPCL. Confirm the exact connection holder, HT/EHT tariff, contracted demand, meter boundary, open-access or captive settlement and DG role from a recent bill.

2.1 Bill band, tariff & demand

Screening bill band: INR ₹30 lakh/month or more [~] is the qualification threshold; the account-specific estimate below remains unverified until a recent bill is reviewed. Thermal resin operations make ₹35L–₹80L/month [~] on UPCL plausible, but this is not a disclosed invoice. Validate bills, contract demand and DG impact.

The INR (?) bill band is deliberately expressed as a range rather than an invoice claim. The qualification gate is a current monthly electricity bill of at least ?30 lakh [~], not a company-wide revenue figure. Request two recent bills plus four preceding months, sanctioned/contract demand, maximum demand, power factor, tariff schedule and known production disruptions. That permits a fair baseline and avoids attributing a tariff revision, billing correction, outage or volume shift to the pilot.

2.2 Generation, fuel & renewables

No confirmed site solar or captive asset was found. Thermal sources, steam/TFH, DG and cooling configuration must be verified.

Generation changes the analysis; it does not remove it. Solar can lower energy charges while leaving maximum demand, poorly timed flexible loads, export/import settlement, demand ratchets, PF and common-utility baseload unresolved. Boilers, thermic systems, DGs or other fuel assets should be brought into the operating map only where the plant confirms them. Stamped does not sell generation hardware or claim to optimise a process control loop.

2.3 EnMS, PAT, ISO, BRSR

Public ISO 9001 and automation claims exist; no ISO 50001 disclosure was located.

Where an EMS, SCADA, ISO programme, BRSR reporting or kaizen system exists, it is a source of context and a potential integration boundary—not evidence that the account has no remaining operating opportunity. Stamped’s test is narrower: can existing data produce an assigned next action, a ₹ hypothesis and an observable movement on the invoice? Public disclosures are mostly group-level unless explicitly labelled as site-specific.

2.4 Likely ? leak categories (hypothesis)

Resin heat-up/hold, reactor and common-utility MD overlap, pumps/motors, air, ventilation, off-shift loads, PF and DG-grid transition are hypotheses.

These are ranked hypotheses, not findings. Start with load sequencing and production constraints, then examine heater or furnace hold where relevant, idle utilities, compressed air/HVAC, PF drift and tariff windows. A recommendation should be rejected if it reduces output, compromises quality, creates a safety risk, or simply shifts cost outside the measured boundary.

3. Operations, equipment & digital stack

3.1 Process flow & critical loads

Resin formulation/cooking, transfer, coatings, sand processing, packing and common utilities create both batch and continuous elements.

Map the process to the electricity boundary in the first workshop: production steps, shared utilities, major motors/heaters, batch or line transition points, and planned downtime. The useful question is not ?what is the biggest machine?? but ?which controllable event changes MD or kWh without changing throughput?? That keeps the work operational rather than an unsupported engineering audit.

3.2 Shifts, seasonality, production pattern

Public material describes round-the-clock operations. Verify campaigns, grade changeovers and planned stops.

Ask for the last six months? production calendar, product-family changes, maintenance shutdowns, holiday operation, weather-sensitive loads, and abnormal dispatches. A production-normalised comparison protects both parties: lower consumption is not a saving if it came from less production. A stable 90-day window with named shift and utilities owners is more valuable than a broader but noisy data extract.

3.3 Automation, metering, SCADA/EMS/DCS

Forace publicly states DCS-controlled manufacturing with SAP HANA and WMS; ABB/Yokogawa DCS experience appears in a public employee profile. Data topology remains unverified.

Use a two-path entry. Path A: feeder, interval-meter, SCADA or DCS exports already exist; link them to bills and the production calendar. Path B: the team starts with bills, demand/PF history and a manually maintained operating calendar while assessing data availability. Both paths are read-only. No PLC write, setpoint change, network penetration or replacement of the plant?s controls is part of the offer.

3.4 Capex / tech projects affecting energy

Any recovery/expansion or safety changes require a new baseline.

New capacity, VFDs, solar, compressor upgrades or automation can change the baseline and make historic targets misleading. Treat them as segmentation events. The pilot should compare like-for-like shifts and product mix, record commissioning dates, and state which changes are outside the Stamped attribution window. This is especially important when teams have active capex programmes and want an audit-ready explanation of residual cost.

4. Stamped Energy fit analysis

4.1 ICP scorecard

Score: 8/10. Geography and industrial operations are positive signals. Bill size, connection topology, current production continuity, local approval rights and usable data remain [!] until confirmed. The account passes only when the plant can give a stable bill boundary, an operating owner and enough continuity to test one action fairly.

4.2 Fit score rationale

The score rewards process relevance and the chance that existing measurements can support a read-only deployment. It is reduced for undisclosed invoices, uncertain shared utilities and any governance friction. A high score is not a savings promise. It is a prioritisation view: the account merits a focused qualification call before deeper technical work.

4.3 Wedge (parser-critical)

The strongest wedge is: existing DCS and meter data can expose resin heat-up and common-utility overlap, reduce unnecessary hold energy, and turn safe scheduling changes into named ₹ actions verified on the UPCL bill.

The message should be concrete and bill-first. Stamped does not position itself as another dashboard, maintenance AMC, solar EPC or annual audit. It takes the information already available, identifies a controllable operating choice, assigns a ₹ value and owner, and checks whether MD, energy and PF move on the next UPCL invoice.

4.4 Objections & competitors

?Our DCS already controls the plant? is expected. Agree: DCS controls process; the proposed layer links operating timing to bill outcomes. Safety and EHS approval come before any schedule suggestion.

The respectful response is to agree that the existing system may be strong. A DCS, EMS, TPM team, solar asset, ISO programme or electrical team is not the problem. The question is whether it produces a weekly, owned prescription queue and invoice-level verification. Never disparage the incumbent or imply that a plant has poor controls from public information alone.

4.5 Pilot design

Pilot one resin or utility boundary with six UPCL bills, DCS trends and batch calendar. Track MD, kWh/batch, PF and safety constraints; exclude post-incident recovery changes.

The commercial design should include kill criteria: bill below the qualification threshold; inactive or materially volatile production; no named site owner; no usable billing or demand data; safety/quality constraints that block every candidate action; or a boundary dominated by an external tariff/billing event. Stopping cleanly is preferable to manufacturing a result.

5. Before you reach out

5.1 Discovery checklist

• Confirm operating unit, UPCL connection and ? bill band.
• Ask whether heat-up, hold, demand peaks or utilities concern management.
• Confirm DCS/export and EHS review route.
• Confirm the legal entity and site shown on the recent electricity bill.
• Confirm whether the service is direct UPCL supply, a shared connection, or has open-access/captive settlement.
• Ask for the electrical lead and production owner who can act on a scheduling or idle-load recommendation.
• Establish six months of bills and the production denominator before discussing any percentage saving.
• Ask which event?MD, idle utilities, PF, tariff timing, thermal hold, air/HVAC or a new line?currently creates the most unexplained cost.

5.2 Do not lead with

• Do not lead with dashboards, AI buzzwords, or ESG-first pitch.
• Do not lead with the 2024 fire.
• Do not assert a particular thermal-fluid, steam or reactor configuration.
• Do not quote an exact saving, bill amount, equipment count or invoice outcome that has not been supplied by the plant.
• Do not treat a public contact pattern as a verified personal email address.

5.3 Opening hooks (email / call / WhatsApp)

?You already have DCS and SAP; we focus on the operating overlap that reaches the UPCL invoice?sequencing and hold discipline, not replacing controls.?

A concise first call should ask permission, state one matching operating problem, clarify the read-only boundary, and ask to verify the bill band. Use only two or three capability points: intelligent load sequencing; furnace/heater hold discipline if applicable; idle-load control; compressed-air/HVAC discipline; PF; tariff-aware dispatch; assigned ? fixes; and invoice verification. Listing all capabilities at once sounds like a generic audit.

Operating interpretation for the first workshop. Begin with a one-line bill bridge: energy charge, demand charge, PF adjustment, taxes/levies and any open-access adjustment. Then compare the few days around the highest MD interval with the shift handover, batch/start schedule and utility state. This prevents an attractive but false correlation. For every candidate action, define the owner, safe operating constraint, expected mechanism, expected ? range [~], start date, reversal condition and evidence required on the bill. The team should retain the right to decline any action that conflicts with quality, EHS, customer service or maintenance.

Measurement discipline. Use the plant?s own invoice as the commercial truth, while retaining the interval trends needed to explain it. Reconcile changes against production, operating hours, weather where HVAC is material, captive or solar availability, tariff changes and shutdowns. Avoid claiming that a reduction in kWh automatically equals a reduction in total bill. A bill can rise because of demand, PF, charges or a changed settlement even when one load improved. Equally, an invoice reduction can be unrelated to a prescribed action. This is why a narrow boundary and pre-agreed comparison method are stronger than broad ?AI savings? language.

Security and implementation boundary. The requested access is read-only and minimum necessary: bills, meter/SCADA/DCS exports where permitted, and production calendar context. The plant retains control of credentials and operational decisions. No setpoints are written, no production recipe is changed, and no claim is made that a recommendation supersedes EHS, quality or OEM guidance. If cybersecurity or validation review is required, scope a time-boxed data review rather than promising instant integration.

Operating interpretation for the first workshop. Begin with a one-line bill bridge: energy charge, demand charge, PF adjustment, taxes/levies and any open-access adjustment. Then compare the few days around the highest MD interval with the shift handover, batch/start schedule and utility state. This prevents an attractive but false correlation. For every candidate action, define the owner, safe operating constraint, expected mechanism, expected ? range [~], start date, reversal condition and evidence required on the bill. The team should retain the right to decline any action that conflicts with quality, EHS, customer service or maintenance.

Measurement discipline. Use the plant?s own invoice as the commercial truth, while retaining the interval trends needed to explain it. Reconcile changes against production, operating hours, weather where HVAC is material, captive or solar availability, tariff changes and shutdowns. Avoid claiming that a reduction in kWh automatically equals a reduction in total bill. A bill can rise because of demand, PF, charges or a changed settlement even when one load improved. Equally, an invoice reduction can be unrelated to a prescribed action. This is why a narrow boundary and pre-agreed comparison method are stronger than broad ?AI savings? language.

Security and implementation boundary. The requested access is read-only and minimum necessary: bills, meter/SCADA/DCS exports where permitted, and production calendar context. The plant retains control of credentials and operational decisions. No setpoints are written, no production recipe is changed, and no claim is made that a recommendation supersedes EHS, quality or OEM guidance. If cybersecurity or validation review is required, scope a time-boxed data review rather than promising instant integration.

Decision protocol for this account. In the first two weeks, the plant team should agree the production-normalisation rule and identify the one operational change it is actually willing to trial. A useful prescription is deliberately small: stagger one eligible start, set back a non-critical utility during a known idle window, correct an observed PF operating drift, or move a flexible task into a permitted tariff/solar window. Record the baseline, owner, operating constraint and stop condition before action. In weeks three through eight, compare interval behaviour with production and confirm that neither a shutdown nor an external supply/tariff event explains the result. In the final period, reconcile the invoice lines and decide whether to scale, refine, or stop. This creates a credible evidence trail even when the first hypothesis is disproved.

Commercial guardrails. The first discussion should not request confidential recipes, customer data or control access. Bills, demand/PF history, aggregated meter trends and a simple calendar are normally enough to qualify the problem. If a data-sharing or cybersecurity review is required, it should be a documented prerequisite with clear scope. The promise is not a percentage; it is disciplined identification, accountable action and bill verification. This protects the plant from unsupported savings claims and gives the sponsor a clean basis for continuing only if the measured boundary supports it.

6. Risks, flags, controversies & sources

6.1 Integrity / controversy / regulatory (search explicitly)

A major August 2024 fire was reported at Forace Specialty Chemical in Haridwar. Reports said workers were evacuated and the cause was to be investigated; no reliable final cause or liability finding was found. No reliable company-specific PCB/court outcome was located in the search reviewed.

This section records search evidence, not allegations. Search terms used included the company and site name with pollution notice, PCB, NGT, lawsuit, court, labour, tax raid, fraud, fire, accident, CIRP and controversy. Absence of a result is not proof of absence; it means no reliable, account-specific outcome was located in the sources reviewed. Do not repeat unverified claims to a prospect.

6.2 Data quality flags

• Capacity is brochure-based and may not equal current utilisation.
• Bill, utility configuration and exact site entity are unverified.
• No exact monthly invoice, sanctioned demand or tariff category should be represented as verified unless the plant shares it.
• Group disclosures should not be silently applied to the nominated site.
• Directory contacts and public profile titles need confirmation before outreach.

6.3 Sources consulted

• https://foracespeciality.com/
• https://foracespeciality.com/company-profile-forace/
• https://foracespeciality.com/wp-content/uploads/2019/08/Latest-Brochure.pdf
• https://www.devdiscourse.com/article/headlines/3043665-massive-blaze-engulfs-haridwar-chemical-factory-prompt-fire-response-saves-lives
• Template and messaging reference: marketing/content-strategy/positioning/cold-call-capability-points.md.
• Paired outreach kit: outreach/2026-07-best-prospects-band-a/13-forace-polymers.md.