From a completed service task to a continuing company promise

Mandate

Make the operating system and investment evidence support the customer commitment

Outcomes

• Required usable-duration evidence for thermal storage
• Differentiated supported continuity scopes from unresolved dependencies
• Kept capital approval distinct from completed professional acceptance

Decisions in context

I became CEO and an executive director in April 2020. Seven functional heads report to me, including operations head Sameer Vezqrani, within a company of 312 employees. The separately chaired board approves the operating and capital programmes and challenges my recommendations. Qualified technical, safety, financial and legal owners retain their responsibilities. The storage investment required a larger and later project than the original outline because the usable duration had to match the intended service. The continuity review then required different commercial accounts for arrangements whose supporting dependencies were at different stages. My role was to make those conditions part of the company commitment, not leave them as specialist qualifications outside the headline. I hold a 0.3 percent beneficial interest through the employee vehicle and one current executive seat; both must be considered before any additional outside appointment.

Reason for the move

Current role; considering thermal-services leadership and one assessed additional non-executive contribution

Concurrent appointment

CEO and executive director of the same company since April 2020; one statutory appointment

Mandate

Bring component performance into a complete plant and service account

Outcomes

• Withdrew a chiller-only saving claim I had supported
• Reopened the wider rollout recommendation
• Funded examination of auxiliary electricity and comparison conditions

Decisions in context

My remit grew to five operating heads and 240 employees within a ₹126 crore annual envelope. Major capital remained subject to board approval, and professional engineering and safety owners controlled their disciplines. In 2017 I supported a rollout using lower chiller electricity as the central result. The auxiliary account reversed the apparent whole-plant saving. I withdrew the recommendation and funded the wider review rather than protect the component headline. Comparable cooling quantities did not remove the need to examine weather and operating conditions, so I also avoided treating the revised total as proof of a single cause. The lesson prepared me for company leadership by changing the boundary of the question. The operating account had to match the service and investment being promised, even if a narrower number was easier to celebrate.

Reason for the move

Appointed CEO and executive director with company-wide accountability

Concurrent appointment

No statutory seat during the COO appointment

Mandate

Connect site performance with the defined delivery boundary and customer obligations

Outcomes

• Brought auxiliary systems into the plant account
• Clarified the measured service boundary
• Preserved technical and safety decision ownership

Decisions in context

I joined the plant owner with responsibility for fifty-eight employees and an ₹18 crore annual operating envelope. Engineering, electrical and safety decisions remained with qualified owners, while I was accountable for the management account and coordination of the site. The work showed why equipment performance and service delivery are related but different questions. Cooling had to be measured at an agreed boundary, supporting systems consumed resources and customer-side conditions could affect the wider experience. I learned to ask which obligations the company had actually accepted and whether the operating evidence described them. The move from service management to plant ownership also changed the time horizon. A repair could end a visit, but the plant’s commitment continued. That experience later informed my insistence that storage duration and continuity dependencies appear alongside equipment specifications in investment papers.

Reason for the move

Promoted to multi-plant operating leadership

Mandate

Coordinate the service account without treating every connected system as ours to change

Outcomes

• Combined field observations across equipment boundaries
• Distinguished repair completion from wider system performance
• Escalated work requiring customer or professional approval

Decisions in context

Twenty-one colleagues worked within ₹3.2 crore annual delivery expense. The customer retained its capital decisions and operating responsibilities, and our qualified technical staff controlled their authorised work. I coordinated service visits and the account of what they established. A complaint described as a chiller problem could involve a pump, a control arrangement or a condition on the customer’s side of the installation. The useful response required those observations to be brought together without assuming that the service team could alter every connected system. I learned to distinguish completion of our task from proof of the whole installation’s performance. Moving to a plant owner offered the chance to manage that continuing system account directly. It also required a broader understanding of commercial obligations and the resources needed after the service visit was over.

Reason for the move

Joined a cooling-asset owner to lead continuing plant operations

Mandate

Record the conditions and limits of a completed equipment-service task

Outcomes

• Supported authorised equipment service under supervision
• Recorded observations for professional review
• Kept customer operation distinct from our service task

Decisions in context

I entered a seven-person service group after completing mechanical-engineering studies in May 1990. I worked under qualified supervision and could not independently authorise electrical interventions or a customer’s operating decisions. The early work taught me to record what had been inspected or restored and the conditions under which it was observed. A successful visit did not establish performance under every future load or resolve every dependency in the installation. That distinction was easy to understand at the worksite but easier to lose when later management reports compressed several systems into one result. My 2017 component-saving error showed that senior responsibility did not make the early lesson automatic. I return to it when examining an investment promise: what exactly has the evidence established, which conditions still matter and who is authorised to decide the next step?

Reason for the move

Promoted to service management