A named user is any person or device authorized to access any TEAMS software component. The following are some examples:
- If there are 4 people capturing system knowledge using TEAMS-Designer, each of them count as a named user.
- If there are 4 experts helping with testing and validation of the guided troubleshooting solution by logging into TEAMS-RDS and testing out the solution, each of them will count as a named user.
- If there are 100 service agents (including TAC agents, FSE, CSE, TSE, their managers) who log into TEAMS-RDS, TEAMATE or receive TEAMS-PackNGo job, each one of them will be counted as a named user.
- If your remote devices are configured to upload data periodically to TEAMS-RDS server for real-time monitoring and automatic diagnosis, each such system also counts as a named user.
- If your system has embedded diagnosis powered by a TEAMS-RT reasoner, each such system counts as a named-user.
However, each person is counted only once. For example, a service agent may use only TEAMATE in the field, or TEAMS-RDS in the TAC and TEAMATE in the field, but he or she still counts as one named user.
Customers may revise the actual number of named users on a quarterly basis based on good-faith estimates of the total number of users and devices authorized to access the TEAMS software. Customer will report to QSI the number of authorized users on a quarterly basis. If the number of users exceed the number of licenses purchased, the customer will be billed for extra licenses on a quarterly basis. In case the number of users is less than the number of licenses purchased (but greater than 100), a credit will be carried forward and applied to the next renewal.