The entire TCMS system is divided into 8 sub-systems u2013 power supply, doors, drive break & control, HVAC, Passenger Information & Entertainment system, traction control, automatic train protection and visualization & diagnostics.
The software team needs to work on the requirements interfacing with the actual design teams so that the software is fit for purpose from a system design perspective. This interface is one of the main challenges.
Once we have developed the software and we test it by taking it back and validating on a train zero and field testing it out to prove that what we wrote is actually what it performs. The interface challenges happen in translating the system requirements into software requirements.
We operate across the V-lifecycle. We offer a comprehensive verification & validation service for all the 8 modules of TCMS. We also do the V-lifecycle for the non-critical systems. For critical components we support OEMs as per their needs.
We have recently upgraded a single traction train to double traction. Our two differentiators are Train zero and lab-setup.
We have our own TCMS lab at Hyderabad in India and we build the complete racks which are being used for the software development or testing activities. Development engineering and testing team use the lab by accessing it remotely. We procure all the equipment, assemble it and then we qualify that lab which is acceptable in the engineering environment to claim that this software is developed and tested correctly with the right process and then finally it goes into the train. It is called a qualified lab as we follow certain procedures based on the rail industry standards and we qualify the lab and perform all these engineering activities.
Train zero facilities are available at customer locations. Since our engineering solutions or product offerings are also a part of the V-Model process, it also has to go to train zero testing where the product will be tested, verified and claimed that yes the software is now really working fine in the real integrated environment which is equivalent to real train. In that also our product is being verified & validated and if there are any issues complained about we solve them based on our capability or agreement with the customer.
When we operate across the entire V lifecycle for non-critical systems and especially on the testing and validation for critical systems we not only do the software testing but we have dedicated lab setups where we actually test it out on the racks on a virtual train so that our chances of getting accepted on a real train testing become high. So the cost benefit that the customer gets is of a first time right TCMS product with minimal bug fixes needed at a later stage. We have a continuous integration u2013 continuous development along with a virtual testing environment which is also a differentiator.
TCMS uses EN 50128 and EN 50657 certification as expected by the customer. TS250 is a customer centric certification. Also, the majority of TCMS employees are mandatorily certified in ISTQB certification.