Case study 04 of 05 · FMCG (food and personal care, multi-plant Group)

Group BRSR scramble eliminated. Live ESG metrics across 5 plants.

Multi-plant FMCG Group, Pune base · Pune-Chakan-Aurangabad (Group HQ) + 4 other plants

A 5-plant FMCG Group headquartered in Pune (3 food plants, 2 personal care plants, across Pune, Aurangabad and Bengaluru) used to run 5 separate vendor stacks per plant. 25+ vendor relationships. Quarterly Group consolidation in Excel. Post-Zentry Enterprise, the Group runs one platform. Each plant chose its deployment tier. The Group CFO, CIO and EHS Head see one live dashboard.

GROUP CONSOLE5 plants · live
FMCG Group · operations
PUNE FOODOn-Prem · live1,840
AURANGABADHybrid Edge · live1,280
MUMBAI FOODCloud · live1,180
PUNE PCHybrid Edge · live1,040
BENGALURU PCCloud · live1,060
GROUP P&LProject marginLive
BRSRESG live100%
Enterprise · 5 plants · 1 console · 1 audit posture
EXPORT GROUP BRSR
Anonymised composite · representative
SectorFMCG (food + personal care)
ClusterPune-Chakan-Aurangabad (HQ) + Bengaluru
Plant footprint5 plants, 6,400 workers Group-wide
BundleZentry Enterprise (Sitewide+ at each plant + central Group console)
Deployment tiersMixed: 2 Cloud, 2 Hybrid Edge, 1 On-Premise
Hardware retainedExisting ESSL biometric across plants
Audit pressureFSSAI Schedule 4 + Labour Officer CLRA + SEBI BRSR (listed parent)
Go-live9 months for full 5-plant rollout
The challenge

What the plant was facing.

The Group operated five plants, each with its own visitor system, biometric, vehicle register, paper induction and Excel-based contractor muster. Five separate stacks per plant meant 25+ vendor relationships, 25+ AMC contracts, 25+ escalation paths. Quarterly Group consolidation of project P&L, BRSR-relevant operational metrics and audit posture was a six-week Excel scramble per quarter.

The parent company is listed and the SEBI BRSR framework demands ESG-relevant operational data Group-wide, refreshed annually. The Group CFO could not produce consolidated project margin across plants without a manual quarterly reconciliation. The Group EHS Head could not see the audit posture across plants without flying to each plant. The Group CIO inherited five vendor stacks per plant with no consolidation path.

The solution

How Zentry was deployed.

Zentry Enterprise: Sitewide+ deployed at each of the 5 plants, with a central Group console aggregating across them. Each plant chose its deployment tier. The Mumbai food plant and the Bengaluru personal care plant chose Cloud for the fast deployment. The Aurangabad food plant and the Pune personal care plant chose Hybrid Edge for plant-resident data with remote support. The Pune food plant (defence-canteen supplier) chose On-Premise for the customer-specific data residency clause.

Evidence chain produced

What Zentry Enterprise produced for the Group:

Per-plant Sitewide+ at each of 5 plants

Full 6-module deployment, plant-local execution, gate-anchored event stream.

Central Group console (Cloud)

Federates across 5 plants. CFO sees Group project P&L live. CIO sees one platform posture. EHS Head sees per-plant compliance score live.

Cross-plant policy management

Contractor agency master list, induction modules, DPDPA consent template, BRSR metric definitions, audit retention windows. Pushed from Group, inherited by each plant.

FSSAI Schedule 4 across food plants

Visitor and contractor hygiene induction trail. Per-plant FSSAI inspector evidence pack.

SEBI BRSR live dashboard

ESG-relevant operational metrics (training hours, contractor hours, accident records) live across plants for the parent's BRSR filing.

Group renewal

1 Enterprise contract replaces 25+ per-plant AMC contracts.

Before and after

The metrics that moved.

Pre-EnterprisePost-Enterprise
25+ vendor relationships Group-wide1 Enterprise contract
Quarterly Group consolidation in Excel (6 weeks per quarter)Live Group dashboard
Group CFO project P&L visibilityLive consolidated across 5 plants
Group EHS audit posture visibilityLive per-plant, per-statute scoreboard
Annual SEBI BRSR data collectionLive operational metrics, no scramble
Group CIO platform posture5 plants, 5 vendor stacks per plant → 1 platform
AMC spend Group-wideDown 47%
Audit prep time Group-wideDown 81%
The audit outcome

What happened at the next audit.

FSSAI inspections at the 3 food plants closed in under 60 minutes each, zero findings. The first SEBI BRSR filing cycle post-Enterprise was completed in 2 weeks (vs 6 weeks pre-Enterprise). The Group CFO now reports consolidated project margin to the Board live, no Excel reconciliation. The Group EHS Head reports per-plant compliance scores to the Board quarterly, no flying to plants.

"We were running 25+ vendor relationships across 5 plants. Every quarter, six weeks of Excel just to consolidate the Group story for the Board. Now the Board gets a live dashboard. The BRSR filing went from a six-week scramble to a two-week review. The CFO trusts the project margin number for the first time. That is the difference Enterprise made."
Group CIO and Group EHS Head, anonymised composite
All case studies
Similar plant. Similar audit pressure?

Request a reference call.

We can connect you with a Plant Head or EHS Head at a similar plant under NDA. Hear the story from the customer, not the salesperson.

Case study FAQ

Common questions on this deployment.

Can different plants in the Group really choose different deployment tiers?

Yes. The Enterprise model is built for mixed-tier Groups. In this case, 2 plants chose Cloud (fast deployment, no data residency constraint), 2 chose Hybrid Edge (data at the plant with remote support), and 1 chose On-Premise (defence-canteen customer's data residency clause). The Group console federates across all three tiers.

How does the Group console handle per-plant data residency?

The Group console aggregates metadata and audit-relevant signals from each plant. Sensitive operational data and PII stays on the plant's chosen tier. The Group console is always Cloud (India-resident, multi-AZ). Per-plant data residency is preserved by design.

Is this a real Group or a composite?

Composite story drawn from real Zentry Enterprise deployments at multi-plant FMCG Groups headquartered in Pune. Industry, geography and metrics are representative. Named references are available under NDA at the Group level.

How long did the full 5-plant rollout take?

9 months end-to-end. The first plant (Mumbai Cloud) was the reference deployment at 10 weeks. The 2 Hybrid Edge plants ran in parallel and went live at month 5. The On-Premise plant went live at month 7. The final personal care plant went live at month 9. The Group console was live from month 3, federating each plant as it onboarded.

How does the platform support FSSAI Schedule 4 at the food plants specifically?

Pass kiosk captures visitor hygiene induction at every food plant entry. Gate ties contractor entry to a current FSSAI hygiene induction certificate. Induct delivers the FSSAI-specific induction module. The FSSAI inspector evidence pack is a one-click export at each plant.

What is the TCO position at the Group level?

AMC spend dropped 47% Group-wide versus the per-plant sum-of-parts. The bigger benefit is operational: the Group CFO trusts consolidated project margin for the first time, the BRSR filing cycle compressed from 6 weeks to 2 weeks, the Group EHS Head no longer flies to plants for audit reviews.

Can the Group add a 6th plant later?

Yes. New plants federate into the existing Group console. Typical new-plant addition (Cloud tier) goes live in 6 to 8 weeks once the Group playbook is established. The Group contract scales by total plant count and worker footprint.

How does the platform handle the parent's SEBI BRSR filing?

BRSR-relevant operational metrics (training hours, contractor hours, accident records, energy proxies via meter integration) are tracked live per plant. The BRSR filing pack is a one-click export at the Group level. The compliance team reviews and submits within the SEBI window.

How it all connects

One event. Six audit narratives.

Every gate read, every kiosk submission, every certificate validation lands in a single tamper-evident, signed log. From that one event, six modules produce six distinct evidence trails, for six different audits, six different inspectors and six different heads inside the plant.