SE Stamped Energy Outreach Hub
Also like this

Peer iitr tier-1 refining accounts with a similar energy profile — reference on calls.

IITR Tier-1 Refining
Bharat Petroleum Corporation Limited 6/10
IITR Tier-1 Refining
IITR Tier-1 RefiningCaptive powerISO 50001Steam / thermal
Hindustan Petroleum Corporation Limited 4/10
IITR Tier-1 Refining
IITR Tier-1 RefiningCaptive powerISO 50001Steam / thermal
Dalmia Cement 6/10
IITR Tier-1 Cement
Captive powerISO 50001Steam / thermal
Tata Chemicals Limited 6/10
IITR Tier-1 Chemicals
Captive powerISO 50001Steam / thermal
Deep research dossier
Full dossier Call prep

Indian Oil Corporation Limited

PSU-safe account, refinery, post-expansion utility, leadership, procurement, environmental and pilot intelligence for IndianOil Panipat.

5/10 ICP fit
UHBVN DISCOM
ISO 50001 ✓ Energy mgmt
IITR Tier-1 Refining IOCL / BPCL / HPCL
₹
Bill band

₹30 lakh/month** economic floor on total utility energy, but that does not mean the DISCOM invoice is the appropriate verification boundary

→
Entry angle

**a post-P-25 Panipat utility action ledger that isolates one cross-unit steam/power or rotating-equipment exception, assigns it across operations/utilities/maintenance, and proves the normalised ₹ result from approved offline data—without touching DCS or APC.**

!
Top flag

Confirm bill band on first call

Primary champion Mukesh Mohan Executive Director, Refineries Division (Health, Safety & Environment)
Email LinkedIn Outreach scripts →

1. Company overview & snapshot

Indian Oil Corporation Limited (IndianOil/IOCL) is India’s flagship state-owned downstream energy company and a Maharatna central public sector enterprise under the Ministry of Petroleum and Natural Gas. It operates across refining, petrochemicals, pipelines, fuel marketing, gas, alternative energy and R&D. FY25 standalone revenue from operations was approximately ₹8,45,513 crore, and its refineries processed 71.56 MMT at 102% capacity utilisation. Panipat Refinery & Petrochemical Complex (PRPC) is IndianOil’s largest integrated refinery-petrochemical location and is undergoing expansion from 15 to 25 MMTPA.

The account has exceptional technical opportunity but poor startup sales fit. Panipat is in North India, has huge continuous utility loads and is at a baseline-changing commissioning moment. Against that, IndianOil has deep internal process/energy capability, mature APC/DCS systems, critical-infrastructure cybersecurity, public procurement and environmental scrutiny. Stamped should treat this as a strategic lighthouse experiment. The first goal is not a sale; it is a warm IIT Roorkee-enabled introduction to the refinery technical-services/power-and-utilities owner and a decision on whether one offline, read-only use case can be evaluated lawfully and safely.

1.1 Legal identity & corporate structure

Indian Oil Corporation Limited is a Government of India company, CIN L23201MH1959GOI011388, listed on the NSE and BSE, with registered office at G-9, Ali Yavar Jung Marg, Bandra (East), Mumbai 400051. Panipat Refinery & Petrochemical Complex is an operating unit of IOCL at Baholi, Panipat, Haryana 132140. The site includes refining and petrochemical assets and may use multiple project, cost-centre, utility and environmental-account boundaries. A pilot must be contracted with the correct IOCL unit and comply with its delegation of powers, vendor registration and tender rules.

Public materials report 11 IndianOil refineries and 80.75 MMTPA group refining capacity in FY25-era disclosures. Group and standalone figures cannot be assigned to Panipat. The P-25 expansion is a major IOCL project, and the complex has refinery, naphtha-cracker/petrochemical and project organisations. Discovery must identify whether the proposed dataset and savings ledger sit with Panipat Refinery, Petrochemicals, Power & Utilities, Technical Services, Finance or a project/core group. It must also determine whether procurement permits a small proof-of-concept, innovation sandbox, limited tender or only a formal competitive process.

1.2 What they make & where money comes from

Panipat processes crude into transportation fuels and other petroleum products and operates an integrated petrochemical complex. Public sources identify its status as a major refinery and naphtha-cracker/petrochemical location; the exact current unit train, run plan and product slate should be taken from IOCL-approved material rather than reconstructed from third-party descriptions. Refinery margin depends on crude mix, product yields, throughput, energy/fuel loss, hydrogen, utilities, turnaround, catalyst and market cracks. Energy performance must be normalised for complexity and feed/product mix.

At corporate level, petroleum products dominate revenue, with petrochemicals, gas and other businesses contributing additional turnover. Panipat’s expansion and petrochemical integration aim to add higher-value output. A Stamped engagement cannot use total site energy or bill decline as proof. It must define a unit or utility boundary and adjust for throughput, crude slate, severity, ambient conditions, product specifications, commissioning state and planned shutdowns. Financial verification may use internal utility transfer prices and fuel-equivalent cost rather than a simple external electricity invoice.

1.3 Plants, addresses & footprint

IOCL operates a national refinery network including Panipat, Mathura, Gujarat, Barauni, Paradip and other refineries, with Chennai Petroleum in the group network. Panipat is the preferred campaign site because it is in Haryana, proximate to Stamped’s North India focus, has a verified current refinery head and is in active expansion. Official environmental-compliance filings give the address as Panipat Refinery & Petrochemical Complex, Panipat, Haryana 132140, with phone 0180-2524001 / 0180-2579833 and HSE inbox prpc-hse@indianoil.in.

The P-25 project expands crude capacity from 15 to 25 MMTPA with petrochemical integration; IOCL’s FY2025-26 Q4 presentation reported 92.8% physical progress as of 31 March 2026. PRPC’s 28th Refinery Day in July 2026 featured M. L. Dahriya emphasising safe, on-schedule commissioning. Any pilot must avoid commissioning-critical units unless management explicitly selects a stable boundary. A utilities subsystem serving both old and new trains may be more valuable but harder to normalise.

1.4 Leadership & CRM map

M. L. Dahriya is verified by IndianOil’s senior-executives page and July 2026 coverage as Executive Director & Refinery Head, Panipat. He is the site sponsor and authority path, but no exact public personal LinkedIn or direct email was found. Mukesh Mohan is the recommended first contact: Executive Director, Refineries Division (Health, Safety & Environment), former Paradip Refinery Head and IIT Roorkee Chemical Engineering MEng (1993). His LinkedIn is https://in.linkedin.com/in/mukesh-mohan-488a4112. He can judge refinery credibility, safety framing and the right introduction.

K. K. Jain, former Barauni Refinery Head and former ED, Centre for High Technology, is a secondary IITR technical connector (https://in.linkedin.com/in/k-k-jain-60101014), not a current budget owner. The working pilot cell should include Dahriya as sponsor, Panipat technical-services/energy or power-and-utilities head, process/unit representative, instrumentation/OT cybersecurity, finance/costing, procurement and HSE. Use the verified PRPC HSE inbox only for routing. No personal email should be guessed from IndianOil’s inconsistent public email formats.

1.5 Recent news (24 months) & timing for Stamped

P-25 is the dominant timing event. IOCL stated that expansion to 25 MMTPA and petrochemical integration was on track for phased commissioning; progress exceeded 90% by the end of FY2025-26. The company is also developing green-hydrogen capacity at Panipat and associated petrochemical projects. Expansion changes steam, fuel, power, hydrogen, cooling-water and electrical interactions. Designed efficiency will not automatically equal stable operating efficiency during ramp-up, making post-commissioning normalisation valuable—but only after the selected units reach comparable operation.

FY25 directors’ reporting cited refinery MBN 68.9, Energy Intensity Index 96.4, fuel and loss 8.8%, 98.1% operational availability and strong capacity utilisation. These are mature operational metrics, not a gap in measurement. The wedge is closure of a cross-utility exception that traditional unit dashboards or monthly energy reviews do not assign and verify. July 2026 leadership coverage also reinforces safety and schedule as immediate priorities. Outreach must lead with safe, offline feasibility and accept that Stamped may be too early until commissioning stabilises.

2. Energy profile

DISCOM / supply (name early): Uttar Haryana Bijli Vitran Nigam (UHBVN) is the location-based distribution assumption for Panipat; verify the actual EHT/grid, captive generation and open-access arrangements. Do not substitute DHBVN merely because a parser recognises it; Panipat is in northern Haryana.

2.1 Bill band, tariff & demand

No Panipat refinery electricity bill, contract demand, voltage, tariff, captive generation cost or monthly grid-import spend was found in reviewed public sources. A refinery of this scale clearly exceeds the Stamped ₹30 lakh/month economic floor on total utility energy, but that does not mean the DISCOM invoice is the appropriate verification boundary. Refineries commonly generate steam and power internally, consume process fuel and use complex transfer pricing. Any monthly ₹ crore estimate without primary data would be speculative and is intentionally omitted.

Request an approved cost abstraction rather than raw sensitive commercial data if necessary: grid import/export and demand; internal generation; steam by pressure level; fuel-gas/LNG/fuel-oil equivalent; major utility electricity; throughput and unit states; and finance-approved marginal costs. Examine demand or standby charges, source switching, PF/reactive treatment and outages only if material. Cost proof must separate energy from feedstock and avoid exposing commercially sensitive refinery margin data beyond the agreed team.

2.2 Generation, fuel & renewables

Panipat’s power and steam system is expected to combine process fuel, boilers, cogeneration/turbines, grid support and backup generation, but exact capacities and current configuration were not verified from the reviewed sources. The P-25 expansion and petrochemical integration will change utility balances. IOCL has also announced a 10 KTA green-hydrogen project at Panipat; hydrogen production increases electrical demand and creates new interactions with renewable/source scheduling. Project state and meter availability must be confirmed.

The right analysis is marginal, not average: which unit sets the next tonne of steam or MW, what constraints govern turbine extraction/condensing, and when grid import is economically or operationally necessary. Stamped must not dispatch safety-critical utilities or advise fuel changes. It can identify recurring, approved operational states where utility imbalance, excess pressure let-down, simultaneous equipment starts or avoidable standby load creates a cost exception, then route it to the refinery’s authorised owner.

2.3 EnMS, PAT, ISO, BRSR

Indian refineries are PAT designated consumers and routinely benchmark energy through MBN/EII and Centre for High Technology or Solomon-style methodologies. IOCL’s FY25 report gives company-refinery energy metrics, demonstrating established conservation governance. The reviewed sources do not establish a current Panipat-specific ISO 50001 certificate, so verify its scope and validity. IOCL’s public reporting and PSU governance imply formal environmental, safety and efficiency systems.

Ask how Panipat decomposes corporate EII into unit and utility actions, how P-25 baseline changes are managed, and whether recommendations are tied to work orders and finance-accepted realised savings. Existing APC/RTO, process optimisation and monthly performance reviews may already cover much of Stamped’s proposition. The opportunity is a lightweight cross-system action ledger only if energy, maintenance and operations evidence remain fragmented. PAT, CCTS and carbon reporting can support prioritisation but should not be used as the initial sales hook.

2.4 Likely ₹ leak categories (hypothesis)

Post-expansion hypotheses include steam-header imbalance across old/new units; turbine and boiler loading that raises marginal fuel or grid import; pump/compressor trains operating away from an efficient configuration; utilities left in standby through commissioning holds; cooling-water and air systems not scaled to active load; simultaneous large motor starts producing electrical peaks; hydrogen/compression interactions; and heat-integration degradation visible through exchanger/furnace indicators. These are test questions, not claims about Panipat performance.

At a sophisticated refinery, action friction may be more material than detection: an APC, historian or energy review flags a deviation, but responsibility spans operations, utilities, maintenance and project teams, and realised cost is not reconciled after closure. Stamped should focus there. Exclude safety trips, mandatory redundancy, environmental systems, minimum-flow constraints, rotating-equipment reliability limits and any operator-critical action from automated recommendations.

3. Operations, equipment & digital stack

3.1 Process flow & critical loads

A refinery-level map includes crude receipt and storage → atmospheric/vacuum distillation → conversion and treating units → hydrogen/sulphur systems → product blending and storage, plus petrochemical conversion. Utilities include fuel gas, steam, power, water treatment, cooling water, compressed/instrument air, flare, nitrogen, effluent treatment and tank-farm systems. Panipat’s exact unit configuration and P-25 integration should be obtained from approved IOCL diagrams.

Critical electrical loads include large pumps, compressors, air blowers, cooling-water pumps and petrochemical machinery. Thermal demand includes furnaces, boilers and steam users; energy recovery occurs through heat-exchanger networks and turbines. The pilot should select a non-safety-critical utility interaction rather than a core process control loop. A useful map connects unit state, throughput, major equipment lineup, utility header conditions and cost. No Stamped output may suggest changing interlocks, alarm limits, trip logic or operator setpoints without IOCL engineering approval.

3.2 Shifts, seasonality, production pattern

Refineries operate continuously with planned turnarounds, unit slowdowns, crude/product slate changes and unplanned trips. Seasonal fuel demand and ambient temperature affect run plans and cooling. P-25 commissioning creates additional states: pre-commissioning utility service, circulation, start-up, stabilisation, performance test and integrated operation. Comparing these states without classification would produce false savings.

Use event-state normalisation at unit and utility level. Inputs may include hourly throughput, selected unit load, ambient temperature, equipment lineup and approved product/crude categories. The first 90 days should target repeated events rather than total-site energy reduction. If no stable comparator occurs, the result is a validated data model and no savings claim. Maintenance and turnaround windows may be ideal for integration but poor for financial baseline comparison.

3.3 Automation, metering, SCADA/EMS/DCS

A refinery of Panipat’s scale will have extensive DCS, historians, APC and energy/accounting systems, but no vendor should be named without site evidence. Cybersecurity is a primary gate because refineries are critical infrastructure. Stamped should propose no live inbound path initially. Begin with a data dictionary and anonymised/offline exports from an IOCL-controlled environment. If policy allows, analysis can run in a segregated environment with role-based access and retention limits.

Required minimum data is one utility/cost meter boundary, selected operating-state tags, event/maintenance log and approved cost factors. Path A direct read-only integration should be deferred until IOCL approves architecture. Path B offline files can test analytical value. Results should return as human-reviewed recommendations, not control commands. Log every transformation, recommendation, owner decision and verification rule for auditability.

3.4 Capex / tech projects affecting energy

P-25, petrochemical integration, associated rubber/petrochemical projects and green hydrogen are major baseline changes. IOCL’s FY2025-26 material reported the ₹38,231 crore P-25 project at 92.8% progress by March 2026. The new assets may include high-efficiency design, advanced controls and performance guarantees. Stamped cannot claim benefits during OEM performance testing and must avoid conflicting with EPC or licensor warranties.

Create a commissioning register: mechanical completion, first feed, stable operation, guarantee test, debottleneck and maintenance dates by selected boundary. If a project team already tracks every deviation, Stamped’s role may be unnecessary. A valid post-capex pilot starts after the owner accepts a stable baseline and focuses on operating coordination across project and existing utility systems. Green-hydrogen integration may be future scope only after meter, renewable and operating constraints are clear.

4. Stamped Energy fit analysis

4.1 ICP scorecard

  • North India manufacturing: Strong pass—Panipat, Haryana.
  • Electricity cost ≥ ₹30 lakh/month: Economic scale passes; exact grid bill and controllable boundary unverified.
  • Process intensity: Exceptional pass.
  • Revenue ₹300–5,000 crore: Severe fail; IOCL is vastly larger.
  • Plant-level decision speed: Fail/unknown due PSU tender, delegation and cyber requirements.
  • Data maturity: Very high, which helps analysis but raises incumbent/duplication risk.
  • PSU gate: Fails standard ICP unless a mandated pilot/innovation route exists.
  • Strategic reference value: Extremely high if a lawful, bounded proof is possible.

4.2 Fit score rationale

The 5/10 score is an honest account score, not a judgement on the contacts. Panipat offers the right geography, scale, process complexity, current expansion trigger and an excellent warm IITR technical route through Mukesh Mohan. M. L. Dahriya is a verified site sponsor. However, IOCL is explicitly outside the normal startup ICP: a Maharatna PSU with mature optimisation, public procurement, critical OT and high reputational risk. Sales cycle and integration cost may exceed the value of a first proof.

Advance only through a warm introduction and a no-obligation feasibility screen. A pass requires a named site owner, approved offline data, a procurement path proportionate to 90 days and an event class not already closed by existing systems. Otherwise retain IOCL as a network/learning account, not pipeline.

4.3 Wedge (parser-critical)

The strongest wedge is: a post-P-25 Panipat utility action ledger that isolates one cross-unit steam/power or rotating-equipment exception, assigns it across operations/utilities/maintenance, and proves the normalised ₹ result from approved offline data—without touching DCS or APC.

The IITR route should be explicit but not overplayed: ask Mukesh Mohan whether the use case is technically meaningful and who under M. L. Dahriya owns it. The message is “one residual coordination problem after world-class controls,” not “we will optimise your refinery.”

4.4 Objections & competitors

Likely objections: internal energy teams already benchmark EII/MBN; APC/RTO and historian analytics exist; data cannot leave the refinery; public procurement cannot sole-source; commissioning has higher priorities; startup has no refinery references; and invoice verification does not fit captive utilities. These are valid. Stamped’s response is an offline, human-reviewed, one-boundary feasibility proof using finance-approved utility costs and explicit kill criteria.

Competitors/alternatives are IOCL’s own technical services and R&D, Centre for High Technology benchmarking, process licensors, APC/RTO vendors, DCS/historian analytics, EPC/OEM performance programs, energy consultants and enterprise platforms. Do not position against them. Stamped is useful only as an action-workflow and cost-verification overlay across their outputs.

4.5 Pilot design

Phase 0 (no plant data): two-hour workshop to select one event class, define security/procurement route and decide go/no-go. Phase 1 (weeks 1–3): IOCL-controlled offline dataset, tag dictionary, operating states, marginal utility costs and baseline. Phase 2 (weeks 4–9): identify repeated exceptions, route human-reviewed action cards, record owner/constraint/execution. Phase 3 (weeks 10–12): compare like-for-like states and finance/technical acceptance.

Success is one defensible action with no safety/control impact, repeatable evidence and accepted ₹ cost movement. Kill if cyber policy blocks analysis, procurement has no proportionate route, no stable state exists, no unresolved event remains, data is export-controlled beyond scope, or attribution requires sensitive margin data. Any expansion needs a fresh security and procurement decision.

5. Before you reach out

5.1 Discovery checklist

  • Confirm Mukesh Mohan and M. L. Dahriya titles on current IOCL sources before contact.
  • Ask Mukesh for a warm introduction; do not cold-email a guessed Dahriya address.
  • Confirm which P-25 units are commissioned, stabilised or still under performance guarantee.
  • Identify the power-and-utilities/technical-services owner and their current top exception.
  • Confirm legal/procurement route: innovation trial, tender, GeM, empanelment or no route.
  • Confirm OT/security rule for external analysis and whether anonymised offline export is permitted.
  • Define the utility cost boundary; do not assume a DISCOM invoice represents site energy.
  • Verify grid licensee/account, contract demand, captive generation, steam and internal transfer prices.
  • Ask how EII/MBN deviations become work orders and how realised ₹ is accepted today.
  • Choose one non-safety-critical, repeated event with enough stable comparator data.
  • Exclude commissioning tests, trips, turnarounds and mandatory redundancy from savings claims.
  • Identify finance, HSE, procurement and cybersecurity reviewers before requesting files.

5.2 Do not lead with

  • Do not lead with a 15–20% savings claim, generic AI, dashboard or “optimise the refinery.”
  • Do not lead with enterprise rollout, direct DCS integration or automated control.
  • Do not claim a Panipat monthly bill or captive configuration.
  • Do not imply IIT Roorkee affiliation bypasses PSU procurement.
  • Do not use environmental controversy as a sales lever.
  • Avoid lead language that treats commissioning losses as operator failure.

5.3 Opening hooks (email / call / WhatsApp)

Email to Mukesh: “We are not proposing another APC, DCS or enterprise energy platform. We want your view on whether one post-P-25 utility interaction can be analysed from approved offline data, assigned to an owner and verified in the refinery’s own marginal-cost ledger.”

Call: “If Panipat already closes every cross-utility exception, we stop. If one falls between operations, utilities and maintenance, we test only that.” LinkedIn is the preferred first channel. The verified HSE inbox is a routing fallback, not a personal-contact substitute.

6. Risks, flags & sources

6.1 Integrity / controversy / regulatory (search explicitly)

6.2 Data quality flags

  • No exact public LinkedIn or direct email was found for M. L. Dahriya.
  • The PRPC HSE inbox is verified but is not Mukesh Mohan’s or Dahriya’s personal address.
  • Grid supplier, captive/steam configuration, tariff, bill and cost boundary remain unverified.
  • P-25 progress and commissioning dates can change quickly; recheck immediately before outreach.
  • Company-level MBN/EII and throughput are not Panipat-specific results.
  • No named DCS/APC vendor or Panipat ISO 50001 certificate was asserted.
  • Refinery process and leak hypotheses are generic due-diligence questions, not findings.

6.3 Sources consulted