There are two scenarios in which TEAMS-RDS may send a Pack-N-Go job to remote technician.  The first is the ability for any “Remote Technician” user to take their current session off-line.  The second scenario involves a “Call Center Agent” user passing on the session to a Remote Technician in the field.  The PackNGo job is configured with the necessary resources and diagnostic test information required to complete the job in the field.  The  PackNGo job may be sent by selecting “PackNGo” from the Options menu during a troubleshooting session.

Pre-requisites

• The user must choose at lease one symptom to troubleshoot.
• The intended recipient needs to have the “Remote Technician” role assigned.
• The Pack-N-Go license must be installed on the TEAMS-RDS server.

Before starting your TEAMS-RT client application, the model must be mapped to a system instance in TEAMS-RDS.  Follow the steps below to setup the instance in TEAMS-RDS:

1. Export the model from TEAMS-Designer to TEAMS-RDS.
2. Log in using a “Supervisor” user.  Go to Create/Delete Systems from the Tasks menu.
3. Enter a name and revision for the TEAMS-RDS system.  Choose the TEAMS-Designer model and revision exported in step one.
4. Click on Create to finish.

Now we must create an instance of the system.

1. Select Assign Systems from the Tasks menu.
2. Select the system just created and click on Enter.
3. Select a serial number for the new system and click on Save to finish.

During the initial connection to TEAMS-RT, edit the application “message utils” structure to include the serial number for the new system instance.  Now the TEAMS-RT server is able to connect your session with a system instance in the TEAMS-RDS server.  To view the current system’s health status:

1. Log in using a user with the “Manager” role.
2. Select System Health Status from the Tasks menu.
3. Finally click on the system’s serial number to view its health status.

The TEAMS-RDS TEAMS-RT Software Development Kit (SDK) allows users to build applications that can connect to the TEAMS-RT server component running as part of a TEAMS-RDS server.  As long as the client application has access to the TEAMS-RDS server, it may reside on a system any where in the world.  By connecting to the TEAMS-RT server and sending it data in real-time, users may monitor the system in real-time by connecting to TEAMS-RDS server.  The TEAMS-RDS server will provide the status of the system and lists good/suspected/bad components of the system.

The error code “40” indicates the TEAMS-RDS server is not reachable.  You can try to ping the server or open a browser connection to the TEAMS-RDS server web page.  You may also ensure that the Tomcat and TEAMS-RT services are running on the TEAMS-RDS server.  On Linux servers, also check that the TEAMS-RDS broker is running as well.

TEAMS PackNGo is available for download at the Apple App Store  and Google Play Store.

TEAMS PackNGo is supported on Apple’s iOS (version 5 and above) and Google’s Android (version 2.3.3 and above) platform.

The user will require access to a TEAMS-RDS server.  Without a TEAMS-RDS server, TEAMATE will not be able to download any model to troubleshoot.  The following table lists the minimum system requirements for TEAMATE.

* Required if log files are sent via e-mail.

The FMECA (Failure-mode, effects and criticality analysis) add-on includes the following additional features over the standard edition of TEAMS-Designer.

Before a user can start troubleshooting systems, they need to configure TEAMATE’s repository locations.  TEAMATE needs to know two locations, the location of the TEAMATE model files and the location to place the session logs.   By default, TEAMS-RDS will store and receive TEAMATE files via HTTP(s).  Follow the steps below to configure TEAMATE to connect to a TEAMS-RDS repository via HTTP(s):

1. Launch TEAMATE.
2. Select “Synchronization” from the Tasks menu.
3. Under “Model Consolidation” select “http(s)” for the repository type and enter the repository location for the model files.  In a default server configuration, the model location is “http://<server_address>/RDS/synchronization/models“.
4. Under “Log Synchronization” select “http(s)” for the repository type and enter the repository location for the log files.  By default, the log repository is located at “http://<server_address>/RDS/synchronization/logs“.
5. Click on “Update” to test the configuration settings.  Upon success, a message will be displayed above the configuration settings.  If an error occurs, please consult your TEAMS-RDS administrator for further information.  The repository locations may have been changed from their default locations.

Once the repositories are configured, we can start downloading the TEAMATE model files from the TEAMS-RDS server.  Select “Consolidate Models“, a list of all the TEAMATE models available to you are displayed.  Check all of the models you wish to download and click on “Update“.  Once you have downloaded the models you may begin troubleshooting by selecting “Troubleshoot System” from the Tasks menu.

TEAMS-Designer

TEAMS-Designer does not require any firewall ports to be opened.

TEAMS-RDS Server

When TEAMS-RDS runs for the first time under a Windows enviroment, the user may be warned by the firewall software that the installed components are trying to access the computer’s internal loopback interface.

The following table lists the default ports used by TEAMS-RDS services on a Windows operating system.

In a Linux environment, the following default ports are utilized by the default TEAMS-RDS installation:

TEAMATE

The following ports require access to the internal loopback interface.