Deep Research ? Otsuka Chemical (India) Private Limited (Kotputli)

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

Otsuka Chemical (India) Private Limited was incorporated in 2006 as an Otsuka group company to manufacture GCLE in India. It is a Rajasthan account, not a Kashipur account; confirm exact legal billing entity and approval path.

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

The Kotputli business produces GCLE, an intermediate used in cephalosporin antibiotics; public material also references bulk-drug expansion and rubber-additives scope. EC material records expansion proposals including reactors, centrifuges, dryers and distillation.

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

The factory is at RIICO Industrial Area, Village Keshwana Rajpoot, Tehsil Kotputli, Rajasthan. Confirm the precise feeder, connection and relationship to the Jaisalmer solar facility.

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 Pratul Gupta as operations/projects champion hypothesis and Bangaji Mahendra as site leader. MNC procurement, OT security and legal review are likely stakeholders.

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

Public site says the DCS plant has operated since May 2008. Otsuka public material reports Jaisalmer solar planned at 15 million kWh annually; expansion history is an opportunity to revisit baseline.

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): JVVNL. 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. ?45L??100L/month [~] is plausible for a DCS-controlled fine-chemical site but no public invoice is available. Historic EC material refers to a 5,000 KVA JVVNL connection for expansion planning; do not treat this as current demand.

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

Public material confirms Jaisalmer mega solar; settlement, banking, open access and direct JVVNL linkage require confirmation.

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

Otsuka states commitment to energy conservation, environment and water. No plant-specific 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)

Batch timing, distillation/drying utility peaks, post-expansion demand, solar-grid settlement, PF and tariff windows 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

Likely activities include reaction, separation, centrifugation, drying/distillation and utilities; exact production recipe is not needed for qualification.

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

Campaign manufacturing and expansion commissioning may create variable loads; get campaign calendar and solar availability.

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

Company describes fully automatic DCS control. No public EMS/analytics detail is sufficient to assume integration method.

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

Solar and historic expansion change comparison periods; segregate them.

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: post-expansion batch and utility timing can be reconciled with contract demand and solar/grid settlement, producing named ₹ actions and next-invoice verification on JVVNL without changing the DCS.

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 JVVNL invoice.

4.4 Objections & competitors

Solar, DCS and group energy programmes are complements. The likely concern is cybersecurity and MNC vendor review; lead with minimum read-only data and a scoped site pilot.

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

Start on one process/common-utility feeder with six JVVNL bills, campaign calendar, demand/PF and solar-settlement context. Success is production-normalised bill movement with no control writes.

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 direct JVVNL/open-access connection and bill holder.
• Ask whether solar settlement, MD, PF or batch utility peaks is the priority.
• Confirm local data/approval owner.
• Confirm the legal entity and site shown on the recent electricity bill.
• Confirm whether the service is direct JVVNL 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 call the site Uttarakhand or UPCL.
• Do not say solar failed or claim exact capacity/current load.
• 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)

?The DCS and solar have done capital work; we test the remaining scheduling and settlement decisions against the actual JVVNL invoice.?

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)

Searches of Otsuka Chemical India/Kotputli with pollution, notice, lawsuit and controversy found no reliable account-specific controversy outcome. Historic environmental-clearance documents describe proposed expansion controls and are not evidence of a violation.

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

• Current capacity, 5,000 KVA status, bill and solar settlement are unverified.
• Leadership-profile expansion data needs company confirmation.
• 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://otsukaindia.com/facilities/
• https://otsukaindia.com/green-energy/
• https://environmentclearance.nic.in/viewminutes.aspx?code=IND2&date1=02%2F16%2F2015
• https://rajasthan.industry-focus.net/2019/01/09/otsuka-chemicals-to-expand-its-bulk-drug-unit-in-keshwana-rajpoot/
• Template and messaging reference: marketing/content-strategy/positioning/cold-call-capability-points.md.
• Paired outreach kit: outreach/2026-07-best-prospects-band-a/14-otsuka-chemical.md.