Tempurity™ System Requirements

The Tempurity™ System uses multiple software and hardware components that can be distributed throughout your network. You require at least one computer acting as Tempurity Server and one computer acting as a Tempurity Monitor in order for the system to operate.  In many cases the Server and Monitor software are installed such that they run on the same machine, so a minimum of one computer is needed to run Tempurity. See a general description of the system's architecture for an overview.  One way to view the architecture is that each Tempurity Server is like a web page and each Tempurity Monitor is like a browser. The Tempurity Server computer is where the data is stored, Tempurity Monitors are connected permanently, 24 hours a day, to the Tempurity Server to which they are connected and data is streamed constantly between a Tempurity Server and a Tempurity Monitor. You can have many Tempurity Monitors as you wish connected simultaneously to a single Tempurity Server. You can have as many Tempurity Servers as you wish as well and they can operate redundantly. The Tempurity Monitor is the "read" part of the Tempurity System and is the main user interface. Tempurity Monitors are not capable of any data write functions. 

-The Tempurity Monitor component of the software runs on Windows10, Windows 8, Windows 7, Windows XP, operating systems. There are some slight differences in how the Monitor works under different operating systems. You can run the Tempurity Monitor from any Windows computer operating system, including Windows 8 tablets.

-Access to TCP/IP wired or wireless network connections are required by Tempurity Servers, clients, and Networked Robotics' proprietary NTMS network hardware.

-The system is subject to network security. Firewalls, router configurations, security software, and spam filtering software can affect the operation of the system.

-Tempurity Servers and Monitors require at least 1024 x 768 graphic resolution.

-An e-mail account is required on a mail server which will be used as the "from" address from which alarm notifications can be sent.

-Internal alarm notification e-mail from Tempurity Servers to internal corporate Exchange servers is sent unauthenticated. You can use other types of internal and external e-mail servers such as those used by Gmail which is sent authenticated and can be encrypted. Gmail has some restrictions on use of accounts for this purpose. You must use the lesssecureapps flag in Gmail for use with Tempurity even though mail sends are encrypted.

-Computers that are used as Tempurity Servers and Monitors should have a BIOS option that allows the computer to restart after a power interruption such "AC Power Loss Restart" or "Restore on AC Power Loss". Most desktop and server computers have such an option. 

-TCP port 80 and port 3010 need to be open on all Tempurity Servers in order to provide access to remote Tempurity Monitor clients. Tempurity Server computers must not be running web hosting software.

-Tempurity Server computers must be capable of sending mail over port 25 to a mail server.

-The system requires that at least one computer be running 24 hours a day. Uninterruptible Power Supplies are recommended for key computers, mail servers, and network components. The system requires periodic review to ensure that components are operating properly.

-The implementation of redundant Tempurity Servers and Monitors are recommended in critical applications. The Tempurity System can be run as redundantly as you wish and there is no additional cost to establish redundant monitoring processes.

-Voice alarm notifications (usually to land lines) require a fixed single external IP address. The "voice" type of alarm notification can not be used if your IT infrastructure uses NAT firewalls with a large block of rotating external IP addresses. 

-UDP broadcasts should not be blocked on subnets that contain Networked Robotics hardware.

-Networked Robotics recommends the use of VLANs when a large number of devices are monitored from different buildings or sites however the use of VLANs is not required.