The work moved from application fields to enterprise decisions

Mandate

Preserve identity, measurement, event and state meaning across the service's information systems

Outcomes

• Removed an unsupported shortage calculation before billing
• Separated device observations from wash-cycle history
• Reconstructed time-context links and narrowed the reservable-stock view

Decisions in context

I became CIO in February 2021 as the service's information responsibilities expanded across six regional plants. Veqnari now has 680 employees and 48 hospital customers, with ₹112 crore revenue and ₹9.4 crore operating profit for FY ending March 2026. I lead 26 IT colleagues through four heads, reporting to Nandita, with ₹7.6 crore annual operating expense and a separate ₹1.8 crore approved capital allocation. My work connects system records with the physical service while David and other qualified owners retain process decisions. The cases include unlike weight comparisons, repeated tag reads, time-context links and stock states. I want technology completion to identify exactly which information problem has been corrected and which judgement remains elsewhere. I hold no statutory seat, and my employee-trust interest remains relevant to any proposed outside contribution.

Reason for the move

Current technology leadership role; no statutory directorship

Mandate

Coordinate a growing systems estate while preserving the business meaning of its source records

Outcomes

• Expanded technology leadership beyond a small systems team
• Stopped a 2019 migration before production cutover after identifier collisions
• Rebuilt the mapping and changed the review of identity transformations

Decisions in context

The April 2013 appointment brought responsibility for fourteen IT colleagues through two heads and ₹3.2 crore annual expense, reporting to the CEO. Veqnari employed 420 people and recorded ₹64 crore revenue for FY 2014. As the system estate grew, standardisation became an attractive way to simplify interfaces. In 2019 I approved numeric treatment of text identifiers that removed meaningful leading zeros. A rehearsal collapsed 1,240 identifiers into 1,192 unique keys, affecting forty-eight pairs. We stopped before production cutover, retained the original identity form and spent ₹36 lakh on rework over six additional weeks. The source owners had shown that my design assumption was wrong. I learned to examine the distinction a transformation must preserve before describing a nonconforming source value as data that the business should clean.

Reason for the move

Appointed CIO in February 2021

Mandate

Connect collection, processing and return records without confusing their different measures

Outcomes

• Moved from software support into a physical healthcare-service supply chain
• Learned the different meanings of article counts, weights and observed movements
• Established working boundaries with operating and process-assurance colleagues

Decisions in context

I joined in June 2005, leaving the software cooperative without a retained ownership interest. Veqnari had 120 employees and ₹18 crore revenue for FY 2006. I led six IT colleagues with ₹54 lakh annual expense, reporting to the COO. The service introduced a physical sequence behind each record: collection, processing, movement and return. A count and a weight could both be accurate while answering different questions, and an observed movement did not settle the condition of the article. I worked with operations to understand those distinctions before changing the system account. I also learned that a complete IT record did not replace qualified process assurance or the hospital's responsibilities. The role gave me a service context for technical choices that had previously appeared primarily as application or support issues.

Reason for the move

Promoted to head of IT in April 2013

Mandate

Resolve application problems by reconstructing the user's operating context

Outcomes

• Took responsibility for a support team and function expense
• Learned how local conventions survived inside apparently standard fields
• Developed habits for distinguishing implementation defects from misunderstood requirements

Decisions in context

In April 1997 I became support manager, leading ten colleagues through two leads with ₹2.1 crore annual function expense under the operations director. Ravqoli employed 61 people and recorded ₹9.4 crore revenue for FY 1998. Supporting applications after installation required us to understand what users had done before the reported fault appeared. A field could carry a local convention that the original technical description had not explained. I learned to ask why a value looked unusual before deciding it should be removed or normalised. The work also required managing colleagues and explaining a resolution that clients could use, rather than merely closing a technical ticket. That experience prepared me to move into an enterprise where I would live with the continuing operating consequence of the systems we supported.

Reason for the move

Moved to an in-house systems role in June 2005

Mandate

Translate service-business requirements into usable application records

Outcomes

• Applied computing study to practical software development
• Learned to ask how users distinguished objects and events
• Built the technical foundation for later support and enterprise leadership

Decisions in context

I began in July 1990, one month after completing my computing degree. Ravqoli employed 24 people and recorded ₹1.1 crore revenue for FY ending March 1991. I worked in a five-person development group under the development manager, with no supervisory duties or expenditure authority. The early work made me interested in the difference between a form that could store a value and an application that understood what a user meant by it. I learned through requirements discussions, implementation and correction, rather than through responsibility for enterprise policy. A number on a screen could be a quantity, a label or part of a convention, and the distinction affected the software we built. Those practical questions became more important as I later managed support and took responsibility for information systems inside a physical service business.

Reason for the move

Promoted to support manager in April 1997