From completed studies to continuing evidence stewardship

Mandate

Keep maintenance analytics connected to prediction timing, component identity and the limits of observation

Outcomes

• Withdrew a prediction claim contaminated by later repair records
• Retained unfinished histories in a reliability review
• Rebuilt supported attribution for 227 component changes
• Kept rare-event alert evaluation separate from operating release

Decisions in context

The CDO role began in January 2022 and made me accountable for the evidence behind the company's analytical propositions. Forty-seven colleagues now work through four heads within ₹9.3 crore FY2026–27 expense, alongside a separately approved ₹3.1 crore programme. Qenvathi's 420 employees and ₹184 crore FY26 revenue describe the whole service business. Imran holds enterprise decisions, and Ritu leads engineering; safety and field-service authority do not transfer to my office when a model is proposed. My first-year error was endorsing a prediction score before examining when its inputs existed. Later work retained unfinished observation, corrected component histories and made an alert queue's burden visible. These cases have made me more demanding about the connection between a result and its intended use. I am considering how that discipline might contribute to a board without turning oversight into another operational analytics function. No statutory directorship accompanies this executive appointment.

Reason for the move

Current appointment; exploring a first outside board contribution

Mandate

Connect component histories and analytical studies to the questions posed by service managers

Outcomes

• Expanded stewardship from individual records to analytical propositions
• Brought field explanations into the interpretation of component histories
• Distinguished internal investigation results from broader commercial claims

Decisions in context

The asset-analytics directorship was a functional title, not a place on the company's statutory board. I led twenty-eight colleagues through three heads within ₹4.8 crore annual expense. The business employed 268 people and recorded ₹102 crore revenue for FY ending March 2017. My remit grew from the maintenance record itself to the studies and proposed services built from it. I had to explain why an account useful for investigating an equipment question might still be insufficient for a wider promise about performance. Field colleagues remained essential because they knew what a late closure, a changed serial number or a discontinued service relationship actually meant. I learned to bring that context into the analytical design before a polished result reached commercial discussion. The later CDO appointment widened the responsibility again, requiring me to challenge the enterprise interpretation of our evidence as carefully as the preparation of the underlying records.

Reason for the move

Appointed CDO in January 2022

Mandate

Make field records interpretable across component changes and service periods

Outcomes

• Connected analytical preparation with the people creating service records
• Kept equipment identity questions visible during data review
• Learned how observation ends when service relationships change

Decisions in context

I joined Qenvathi in September 2011 because I wanted to follow a maintenance record beyond a commissioned study. The company had 148 employees and ₹46 crore revenue for FY ending March 2012. Twelve colleagues worked through two leads within ₹1.6 crore annual expense. Our task was to preserve the meaning of field evidence as it moved into planning and analysis. I spent time with service colleagues who could explain why a component identifier changed or why a record stopped arriving. Those explanations were not merely administrative detail. They could change which physical history an analyst believed was being observed. I also learned the limits of my own function: a data correction could improve attribution without determining whether equipment was fit to operate. Moving into asset analytics later gave me responsibility for the interpretations built on these records, while keeping that distinction between evidence preparation and engineering judgement.

Reason for the move

Promoted to director of asset analytics

Mandate

Explain what observed histories could support before a study result became a planning assumption

Outcomes

• Managed studies with explicit event and observation definitions
• Explained limits of comparisons built from unequal follow-up
• Connected analytical findings to the client's actual planning question

Decisions in context

Promotion in June 2005 brought responsibility for nine colleagues through two leads and ₹68 lakh annual expense. Pazqemi had 143 employees and ₹28 crore revenue for FY ending March 2006. Clients often needed one assumption for a practical planning decision, while the available histories described different durations and different reasons for ending. My responsibility was to help the team explain that gap without treating uncertainty as an excuse to be unhelpful. We needed to show what was observed, which conclusion remained unsupported and what further evidence could change the answer. Managing other analysts also taught me to make those expectations explicit before a study began. I became interested in improving the records at their source rather than only qualifying them at delivery. Joining Qenvathi offered that continuing responsibility, with field colleagues available to explain the physical events behind an analytical row.

Reason for the move

Moved inside a service company to improve evidence throughout its lifecycle

Mandate

Prepare histories with their observation periods and defined events intact

Outcomes

• Learned to distinguish an observation cutoff from a failure time
• Recorded the assumptions behind early reliability studies
• Built analytical practice under supervisory review

Decisions in context

I completed mathematics at Dorzevi Mathematics College in June 1999 and began work at Pazqemi the following month. The firm employed sixty-two people and reported ₹10.6 crore revenue for FY ending March 2000. I contributed within a six-person study group under a senior analyst, without staff or spending authority. The early lesson was that a time value needed a history around it. A unit could have failed, remained in service at the cutoff or disappeared from our observation for another reason. Those states could not be made interchangeable simply because a calculation expected a number. Supervisors reviewed the method and interpretation before anything reached a client. I learned to ask what the record actually established and to distinguish a useful analytical assumption from an observed fact. The later management role added responsibility for helping colleagues apply that discipline consistently and explain it in terms a planning team could use.

Reason for the move

Promoted to reliability study manager