A repairable part does not settle the return to service
The appeal of a replaceable corner was real. So were the thirteen returns outside its process and the five eligible cases that remained held after the work.
A replaceable corner looks like a straightforward improvement to a rental case. Local damage need not mean discarding a much larger assembly, and a familiar component can make the service proposition easier to explain. I supported that development direction. What I wanted to resist was the quick movement from a repairable part to an assumption that any returned case with similar visible damage should be put through the same process. The complete product has a condition of its own. A convenient component cannot answer every question about that condition.
Design the decision around the component
Our 2023 review examined thirty-six selected returned cases. Qualified assessment found twenty-three eligible for the defined corner-repair process and thirteen outside its scope. The numbers were not a universal estimate of repairability across the rental population. They described a selected group and a particular supported process. Their value was in making the first decision visible. Before asking how quickly the workshop could replace a part, we needed to know whether that work was an appropriate route for the case in front of it.
The rental manager wanted the programme to restore stock before a busy touring period. That was a real operating need. A held case occupies space without serving the next customer, and a shortage can have consequences across several planned hires. I did not want engineering to treat speed as an unworthy concern. But a release count cannot be improved legitimately by changing the meaning of eligibility. The programme had to distinguish the commercial pressure to recover stock from the professional decision about which products the selected repair process could support.
Meera argued for eligibility and release as separate stages. I backed₹17 lakh for jigs and₹9 lakh for the associated training. Those resources were part of making the design usable in a responsible process. They were not a public repair recipe or proof of competence for every possible task. Qualified owners retained the criteria, work and final acceptance. The CTO's role was to fund and connect that system of responsibility, so that a clever assembly did not arrive in the workshop without the means to decide when and how it should be used.
Keep eligibility separate from completion
Eighteen of the twenty-three eligible cases completed the required release checks. Five remained held for further review. The thirteen outside the process kept their own status. I wanted all three groups in the account because they answered different questions. Eighteen releases demonstrated a useful result under the defined arrangement. Five held cases showed that initial eligibility was not the same as final completion. Thirteen ineligible returns showed that the process did not cover the whole examined set. None of those distinctions became less relevant because the team had invested effort in the new design.
There is a temptation to report the largest positive number available. We could have emphasised twenty-three repairable cases, leaving a reader to assume they had all returned to use. We could have reported eighteen completions without explaining the original thirty-six returns. Both accounts would have been incomplete in a way that mattered to the rental decision. The business needed to know what stock was actually available and what work or alternative disposition remained. A technically accurate isolated number can still encourage an operationally inaccurate conclusion when its surrounding states are omitted.
This is why repair architecture includes more than the removable part. It should make inspection practical, identify the supported use of tools and give the receiving team a way to hold uncertainty without improvising an approval. Documentation and access to appropriate expertise matter alongside the geometry. The design can help those responsibilities work together, but it cannot replace them. A component that is physically interchangeable may still be inappropriate in a particular condition or configuration. I do not equate ease of assembly with authority to return the complete product to service.
The economics also deserve a full account. Jigs, training, inspection, held stock and the treatment of ineligible returns all affect whether a repair option is useful. It would be misleading to compare only the price of a small replacement part with that of a complete case. The alternative may still be attractive, but the enterprise should understand what resources make it work. In our programme, the immediate stock benefit was narrower than the early presentation implied. I accepted that narrower result because it provided a basis for a repeatable process rather than a one-off count achieved by ignoring unresolved conditions.
Make repair access a considered relationship
A later discussion about repair drawings raised a related but different issue. Partners wanted material that would help them support cases closer to touring customers. Some requests could be supported under defined conditions, while others involved product implications or permissions requiring another decision. Sharing a file would not make every recipient qualified for every repair. Keeping every file internal would not automatically make the service better, either. We needed an explicit relationship between the technical material, the permitted work and the owners of acceptance and contractual responsibility.
I supported a reviewed release of nineteen requests from a set of thirty-two, with thirteen withheld. That programme cost₹38 lakh and carried commercial consequences that needed their own assessment. It was not an instruction to publish all designs or a general licensing model for other companies. The connection with the corner programme was the insistence on a defined scope. Access, eligibility, completed work and release are different decisions. A responsible system should help the people involved understand which one they have actually received, especially when the service is distributed across organisations.
For directors, the oversight question is whether repairability appears as a complete business capability or only as a product claim. What resources support the work? Who decides which returned products are eligible? How is a held condition reported? What does the customer understand about the service, and how does partner access change the company's responsibilities and income? A board need not approve an individual repair to examine those questions. It can require management to explain whether the investment and service model include the less visible work that makes the physical design useful.
I would now define the release evidence while the replaceable assembly is still being designed. The workshop and rental team should help identify what they must be able to inspect, record and explain before the product reaches a busy service period. That can reveal an awkward design choice early, when changing it is easier. The ambition is not to make every return recoverable. It is to build a repair proposition whose limits are understandable and whose accepted results can be used with confidence by the next responsible person. The part is one element of that proposition, not its entire proof.