As the application transitions to SaaS, TempTracking™ will transition to Location IQ® Temp and AssetTracking® will transition to Location IQ® Asset. Until then you will still see TempTracking™ and AssetTracking® referenced in the documentation.
Introduction
The TeleTracking® Real-Time Locating System solution is a web-based product that connects RTLS (Real-Time Locating System) data sources to create a system that:
Monitors the location and movement patterns of assets, patients, and staff.
Tracks asset status and attributes.
Tracks work orders associated with assets.
Tracks ownership of and responsibility for assets.
Uses alerts, alarms, and notifications to support security for assets.
Aligns the movement and use of assets with business objectives.
Monitors the temperature of refrigerated substances.
The following are the minimum recommended system requirements for the
TeleTracking® Real-Time Locating System solution.
Third Party Hardware Requirements
System Performance
System performance will vary based on data volume, network, and server capacity.
Server Hardware Requirements
The following server hardware is required to deploy the TeleTracking® Real-Time Locating System:
Hardware Server:
A dedicated server for RTLS system software. Refer to Hardware Server Requirements.
Application Server:
A dedicated application server running the solution software is required.
Database Server:
A dedicated Microsoft® SQL Database Server or an existing client’s Enterprise Database Server environment can be used for the solution. Refer to Application Server Requirements.
Network Requirements
General Network Requirements
Transport Layer Security (TLS) v1.2:
Must be enabled for v2018.2.1.1 or later. TLS v1.2 has been tested on SQL Server 2016 (as of v2018.2.1.1).
Simple Mail Transfer Protocol (SMTP):
Used for sending email notifications (ports 25 and 587).
Ports: All ports are configurable and can be changed as needed.
Network Topology:
Ethernet 100/1000 Mbps - PoE (Power over Ethernet) IEEE 802.3af-2003.
Network Infrastructure:
Sufficient PoE ports available for like number of collectors.
PoE - IEEE 802.3af-2003 on same subnet or routed subnets. PoE switches or a PoE injector can be used (if AC power adapter is not used).
IP Addresses:
Fixed IP addresses available for like number of RTLS Network Connected Device = 1 fixed IP address.
Cabling:
CAT 5 or later TIA/EIA-568-B.
Ports:
TCP Ports: 8794 and 8181.
UDP Port: 7171.
HTTP access to web server: 80.
Internal Mongrel services: 4001 to 4004.
Note: These ports can change based on the RTLS vendor chosen.
Managing Ports
General Port Openings
The following ports openings are applicable to most CMS implementations. The TeleTracking project team will indicate if any of these routes can be omitted:
Name | Port | Source | Destination | Direction |
User Access | TCP 80, | Workstations | CMS Application Server | Outbound |
Mobile User Access | TCP 443 | Mobile Devices | CMS Gateway Server | Outbound |
XT Reporting Service Communication | TCP 8523 | SQL Server | CMS Application Server | Outbound |
SQL Communication | TCP 1433 | CMS Application Server, CMS Gateway Server | SQL Server | Bidirectional |
Interface Ports | TCP 225XX1* | Interface System or Integration Engine | CMS Application Server | Inbound or Outbound Depending on Port |
Mobile Notification Relay | TCP 443 | CMS Application Server, CMS Gateway Server | CMS Gateway Server | Outbound |
Mobile Notification Relay | TCP 5671 | CMS Gateway Server | 20.36.244.76 (TeleTracking Cloud Services) | Outbound |
Real-Time Transport Protocol (VoIP/SIP) | TCP or UDP 5060 | PBX | CMS Application Server | Bidirectional |
Real-Time Transport Protocol (VoIP/SIP) | TCP or UDP 49151-49501** | PBX | CMS Application Server | Bidirectional |
NotificationSenderService | TCP 10060 | CMS Application Server, CMS Web Server |
| Bidirectional |
*Interface ports will be customized per client. Ports will need to be opened in the direction that corresponds to the interface direction. Your TeleTracking project team can provide a specific port listing upon request.
**The ports listed here will be defined by the client telecom team, based on configuration of the SIP connection. The number of ports that need to be opened will reflect the maximum concurrent call volume.
Optional Port Openings
The following ports are required to be open systems for specific interfaces and are not applicable to all clients. The TeleTracking project team will advise if any of the following ports may need to be opened:
Name | Port | Source | Destination | Direction |
SMTP Notifications | TCP 25 | CMS Application Server | SMTP Relay / Mail Server (Client Provided) | Outbound |
SNPP Notifications | TCP 444 | CMS Application Server | Paging Vendor (Client Provided) | Outbound |
RTLS Host Port | 6016 | TeleTracking RTLS Application Server | CMS Application Server | Bidirectional |
Staff Integration Utilities Service Host Port | 13373 | Staffing System | CMS Application Server | Outbound |
Rauland Service Host Port | 13374 | Rauland | CMS Application Server | Outbound |
External Integration Service Host Port | 13375 | External System | CMS Application Server | Outbound |
Census Based Scheduling | 13376 | External CBS System | CMS Application Server | Bidirectional |
Mobile Heartbeat | 8443 | 20.36.244.76 (TeleTracking Cloud Services) | Mobile Heartbeat Endpoint (MH Cure Server) | Bidirectional |
Required Open Ports
The following ports are required to be open on the Application Server:
Name | Port |
Default port, needed for integration with CMS | 6016 |
Default port, needed for CWS integration | 7002 |
Needed for RTLS Engine API connection | 5016 |
Used by AssetTracking UI | 81 |
Used by TempTracking UI | 82 |
Default UDP port used by TempTracking | 7167 |
Default UDP port used by AssetTracking | 7171 |
Default port, used for RTLS Engine “CacheViewerEndpoint” | 5019 |
Default port, used for RTLS Engine “RtlsMapManagerEndpoint" | 7200 |
Default port, used for RTLS Engine “RtlsEngineHttpRequestHandlerEndpoint” | 7300 |
Default port, used for Centrak Integration | 8025-8034* |
Default port, used for Impinj xSpan Integration | 5084 |
Default port, used for Kontakt.io Integration | 443 |
Default port, used for BBraun and ICU Medical Integration | 5025* |
Default port used for Impinj Integration | 1883* |
Default port used for Midmark Integration | 3000 |
Default port used for Sonitor Integration | 8088* |
Default port used for Stanley Integration | 87 and 8081* |
Default SMTP server connection port used by the integration service (all vendors) to send error status email notifications | 587 |
*These are the default ports, but they can be changed.
Hardware Server Requirements
This server cannot be used for any other TeleTracking Technologies applications.
Contact your RTLS vendor for system and hardware specifications. Your TeleTracking representative can help you find the latest version of the documentation for your specific RTLS vendor.
Application Server Requirements
Type | Value |
Dedicated Servers Required | 1 |
CPU | 4 CPU Cores minimum (automatic discharge or low volume RTLS activity only) 8 CPU Cores or more required for high volume sites (multiple buildings in campuses) |
RAM | 8 GB minimum (automatic discharge or low volume RTLS activity only) 16 GB required for high volume sites (multiple buildings in campuses) |
Disk Architecture | RAID 5 15K SAS SCSI Drive |
Free Internal Disk Space | 80 GB for the application partition and a separate 40 GB operating system partition |
Network Interface | 1-Gigabit Ethernet |
Backup Device/Method | Customer provided. Backup must have open file capability. File locking must be disabled. |
Application is CPU Intensive | Yes |
TLS Supported | TLS/SSL encryption is mandatory for the AssetTracking® application if it integrates with the Capacity Management Suite® solution version 2022.03 or later. TeleTracking recommends following industry best practices for security. Clients must supply a valid TLS 1.2 certificate. Trusted self-signed or third-party provided (Verisign) certificates are valid. Test certificates are not considered valid. Use the FQDN and IP address in the alias of the TLS Certificate. TeleTracking representative to make this change for you. |
Paging File Size | Use recommended Microsoft® Windows setting. |
Web Server and Third Party Software Components | The following are required and installed by the TeleTracking installation program:
|
Third-Party Software |
|
Virtualized Servers | The server can be a virtualized server as long as the virtual machine meets all requirements that are specified in this document for each server and for resources dedicated to the virtual machine TeleTracking will not set up and support this environment for our clients. Support for this environment is the responsibility to our client’s server administrator or equivalent role. Performance can vary greatly based on hardware, configuration, and utilization. All systems should conform to Microsoft’s Best Practices. VM environments may increase RAM and CPU requirements. Please consult TeleTracking support for more information. |
Virus Scan | Anti-virus software exclusion lists must include the directories and sub-directories where TeleTracking software is installed. Include a wildcard when listing the directories and sub-directories. |
FIPS Security Setting | Disable the FIPS Security Setting on the Application server to allow email and notifications to process correctly. |
Workstation Requirements
See - Technical Information Reference - Info - Capacity Management Suite® | Workstation Requirements
Remote Access
RTLS Hardware Vendors
Contact your RTLS vendor for system and hardware specifications. Your TeleTracking representative can help you find the latest version of the documentation for your specific RTLS vendor.
Third Party Hardware
Clients who have the AssetTracking® application can use badges from CenTrak®, Sonitor®, Stanley® Healthcare, Impinj™, Midmark™ (formerly Versus Technologies), and ICU Medical. The AssetTracking® application supports the use of badges from one or more of those vendors, but only in certain configurations. Badges from different vendors cannot be attached to the same type of entity, but they can be used for different entities. For example, the AssetTracking® application does not support using both CenTrak® and Sonitor® badges as patient badges, but it can support using CenTrak® badges for patients, Sonitor® badges for assets, and Stanley® Healthcare badges for staff, or any other combination of vendor and entity.
Although the AssetTracking® application supports multiple different hardware vendors, the hardware vendors do not all support every feature of the AssetTracking® application. Below is a table that describes which features of the AssetTracking® application are supported by which badge vendors.
Note: In the table below ~ = Not Supported
Supported Feature | CENTRAK® | SONITOR® | STANLEY® HEALTH-CARE | IMPINJ™ | MIDMARK™ | B. BRAUN | ICU MEDICAL |
Asset Locating | Yes | Yes | Yes | ~ | Yes | ~ | ~ |
Staff Locating | Yes | Yes | Yes | ~ | Yes | ~ | ~ |
Patient Locating | Yes | Yes | Yes | Yes | Yes | ~ | ~ |
Patient Auto Discharge (Detach and Discharge) | Yes | Yes | Yes | Yes | Yes | ~ | ~ |
Hand Hygiene | Yes | ~ | ~ | ~ | ~ | ~ | ~ |
Display Badge Battery Info in Application | Yes | Yes | Yes | ~ | Yes | ~ | ~ |
Staff Assistance Alarm | Yes | Yes | Yes | ~ | Yes | ~ | ~ |
Patient Isolation Alarm | Yes | Yes | Yes | Yes | Yes | ~ | ~ |
Patient Walkout Alarm | Yes | Yes | Yes | Yes | Yes | ~ | ~ |
Asset Button Press | Yes | Yes | Yes | ~ | Yes | ~ | ~ |
Missing Badge | Yes | Yes | Yes | ~ | ~ | ~ | ~ |
Asset Status Change | ~ | ~ | ~ | ~ | ~ | Yes | Yes |
Asset Location Changes Status | Yes | Yes | Yes | ~ | Yes | ~ | ~ |
Inventory Par Level Rule for Assets | Yes | Yes | Yes | ~ | Yes | ~ | ~ |
Patient/Staff/Asset Interactions | Yes | Yes | Yes | ~ | Yes | ~ | ~ |
Health Monitoring | Yes | ~ | Yes | ~ | Yes | Yes | Yes |
Temperature Tracking | Yes | ~ | ~ | ~ | ~ | ~ | ~ |
Asset Tamper Events | Yes | ~ | Yes | ~ | ~ | ~ | ~ |
Disable Patient Walkout | Yes | Yes | Yes | ~ | Yes | ~ | ~ |