I joined Siemens on 01Jun2005 and by beginning of Jul05, was assigned to complete the project for SmartPay integration with eServ IN apart from handling the other Telco Clients supported from Kolkata. At that point of time, the product should have been supplied and implemented. However, I found that there was no clarity of scope and no work had begun. Reliance could not really get at us as eServ delivery was also delayed. So, we clarified the scope and documented it and committed to supply the project by Dec05.
The SmartPay was a Pre-Paid Solution (which had all components including a CRM, Inventory Management, Integration with ERP, etc.) which was for CDR based Rating. We had to remove the charging part as this function would be done by the eServ IN while the remaining functions remained in SmartPay. At the outset, the job looked simple. However, that was not the case as SmartPay was a reasonably large software and could serve a Tier II Telco very efficiently. Also, SmartPay was largely written in Visual BASIC & ASP & some portions in C/C++ & some part in Java and almost nobody in the team knew much about the part of the existing code in ASP (and this was the largest chunk). As it was very difficult to alter this code, after 2 weeks of effort I decided to write the software afresh using ASP.Net keeping the C/C++ & Java components which were mainly for handling the SMSC and IVRS and some more interfaces. This was a huge risk and my boss did not approve of the same as he was not sure of a new software and he trusted SmartPay. However, in spite of not being in agreement, he did not stop me. I found that I had very competent people to alter the C/C++ & Java portions and I found Indranil, who had joined a month earlier than me, to complete the eServ IN interface with SmartPay (the ticket handling part. Later, Indranil was known as Ticket Babu in Reliance). To build the ASP.Net portion, I got support from Somenath and 2 new college recruits in the team (who joined a month later than me).
Somenath had joined Siemens a few days earlier to me. He was extremely energetic and very enthusiastic. This made up for some of his lack of skills. As all the developers were new, I took the load for developing the bulk of the software. This was tough as I had to manage the customers during the day time besides internal departments like marketing and quality assurance and others. So, I used to sit to write my part of the code in the evening from around 5PM and carry on till 12 midnight or later. Somenath used to always keep me company, no matter how late it got.
We completed the software by Dec05 and decided to call it INIS for IN Integrated SmartPay. Then, my boss told me that we should leverage the SmartPay brand name and thus stick to the same. We started the deployment knowing very well that there were a number of flaws. However, my conscience was clear that I knew where the problems were and we would fix all of that in the due course of time. Till we were able to fix the problems, we would give unconditional support in running the software. This was to advantage of Reliance as well as they could launch new services and products. As was expected, once the software went live, problems started to surface and Reliance spared no opportunity in abusing us. However, they also did not throw us out. Sandip was our primary front end for the support and I positioned Somenath to be the primary help for Sandip. This was because Somenath knew how to handle the Front-end systems newly written in ASP.Net and also because he had an enormous amount of energy and commitment. He would rush to Reliance at any hour of the day or night when there was any issue. Also, he carried a Reliance phone, with which he would routinely check the system (whether he was brushing his teeth in the morning or during any other time of the day).
Now, when a problem surfaced, which was almost every day, I would meet the team and we would work out solution strategy and get to work on the same. We supplied routine updates as all testing was done in our labs as Reliance did not have a test bed. Now, Somenath would be part of our discussions and heard all that we discussed. As he would spend so many hours in Reliance Office, Reliance Managers got in talks with him to know what was fixed and when it would be deployed, etc. In his innocence and in his enthusiasm, Somenath would blurt out all the truth about what we would have discussed in the office including how much was a patch work and how much was a long-term solution. The Reliance Managers found this very interesting and started to get back to me with even greater vengeance. This was becoming a real challenge to manage. There were severe escalation and it was getting more and more difficult to manage our Management, especially the Marketing & Sales unit (Reliance was the largest account for Siemens Telecom Division in India).
So, I struck a strategy. I created assignments at the Reliance site and assigned them to Somenath so that he would be there for most part of the day. In that time, I would convene the rest of the team and work out solution strategies which we would develop. Somenath would come back to our office after all Reliance staff had left their office in the evening. By this time, most of our team members would have also left the office. So, there would be Somenath and I in the office. I used to seat Somenath in my workstation and tell him half-truths about what we would have developed to solve the immediate issues. And as per my calculations, next day Somenath would go and blurt out that much in Reliance. Within a week or two, I found the aggressiveness of Reliance Managers reducing and this was most comfortable for me as now we had more time to work out proper solutions.
Till Mar06, we kept vigil of the system for 24 hours a day with us taking turns to spend the nights in Reliance. Around end of Mar06, the system was sort of stable and we were more in the office working on future releases. Reliance always called our system “Kachra System” (Junk System). However, they never threw it away and the system took them from handling 3 million subscribers to 12 million subscribers. From Apr06 till Dec09, there was not a single escalation to even my boss from Reliance. This apart, we got orders for many change requests between 2006 to 2009 and they continued to be the biggest source of earning for us. When ultimately, Reliance Telecom merged with Reliance Communications and all systems & people were moved to Mumbai and our system was scrapped, we were definitely sad. However, we also had the satisfaction that what we had developed had served its purpose and definitely it had earned many times more than what it cost.