- About Us
Beginning with version 11, the TEAMS software suite introduced Unicode fonts support. This allows users to add content in any language supported by their currently installed Unicode fonts. Once a model has been exported to a TEAMS-RDS server, translators may add several end-user translations of the model’s diagnosis content via a web interface.
In order to view Unicode characters in other languages, a Unicode font supporting the required ranges must be installed on the computer. These fonts are used to display character data in the reports generated by the TEAMS software suite. One such popular font is the MS Arial Unicode font; it supports a wide range of Unicode characters. By default, it is installed as part of the Microsoft Office setup. It may also be bought separately from Microsoft; a quick web search will provide the necessary link.
Conventional methods of measuring the duration of an outage start the clock when the problem is first reported to the vendor or Call Center. The clock stops when the technician logs that the problem is resolved. In reality, however, the outage really starts the moment the system has an interrupt or stops working. With “Enhanced Service Coverage View”, the TEAMS system can detect problems at or even before the moment of outage, so that corrective actions can occur almost immediately. On the back end of the timeline, TEAMS can also run system verification tests to ensure the instrument is 100% fixed before it is returned to service. Click here to see an illustration of the difference between Conventional and Enhanced Service Coverage.
All require some form of history or prior service knowledge. Many of these other approaches rely on difficult-to-obtain problem history to run their computations and analysis. If this information is unavailable (as is the case with new products), the quality of their diagnostics is significantly diminished. Furthermore, the performance of some of these approaches degrades as system complexity increases. Updates to the instrument or system under test can be disruptive to these other solutions. Some systems have problems correctly analyzing the multi-fault conditions that may occur in the real world. TEAMS can also be used to develop your service strategy before the product is ready for First Revenue Ship.
Knowledge Management Systems are very good at searching and finding data formed around a very sophisticated process based on understanding the user request. The strategy employed by TEAMS, however, is very different. QSI believes that knowledge should be presented to the Service Agent, including what they need, when they need it, and where they need it and, most importantly, how they need it. The Service Agent should never have to ask for knowledge or information. Additionally TEAMS actually generates knowledge; today’s KMS systems do not create knowledge, they only find and parse it to best meet the Service Agent’s request.
Root Cause Analysis is a problem solving strategy that attempts to identify the fundamental or root cause of a problem. This is in contrast to other strategies that look to eliminate a problem’s symptoms, not its true cause. The latter is like resetting the check engine light in your car, sooner or later the problem reappears and another service call is required. TEAMS strength is that it defines the steps and assets needed to find and resolve the route cause.
Several components of the TEAMS system are designed to run in standalone mode without any network connection. TEAMS-RT is an embedded reasoner that can run directly on the instruments on-board computer. Running on a laptop or mobile device, both the TEAMATE and PackNGo applications are designed to run completely in standalone mode. All the required troubleshooting information is downloaded to these devices prior to dispatch.
This is a proactive strategy that empowers service agents to identify problems up front, at the lowest cost level. Once understood, support personnel can then dispatch an asset or an on-service agent with the correct skills, material, knowledge, and tools to resolve the issue. This approach reduces truck rolls, unresolved issues, and return customer site visits and helps to dramatically reduce the cost of materials.