232 Systems is committed to be responsive to any programming issues our clients might have. Our programmers all have laptops and cell phones 24/7 so they can respond to e-mail and voice mail communications instantly when emergencies arise. During normal office hours, if our client’s location is in different time zones, we will make every attempt to schedule around the client’s needs. Remote System Access Option A: 232 Systems preferred access for remote troubleshooting is via VPN to client’s firewall. We will also need to have a client’s technician onsite to relay what effects we are having on the system. This is the most robust and allows us the greatest latitude in finding solutions. Option B: 232 Systems second preferred remote access for troubleshooting is to connect to the client’s Crestron processor through the firewall to 4174-4175 ports. In addition, we request the client’s technician be onsite to relay what effects we are having on the system. This is a less robust method as a result of not being able to see the entire LAN. Remote System Access Case Studies Case Study #1: (VPN) Our programmer needed to troubleshoot a classroom problem at Harley Davidson Company. Using remote VPN access, he was able to update a Nexia program, touch panels, and monitor the operation of two projectors via Option A. Case Study # 2: (Firewall to 4174-4175 ports) Our programmer, located in Milwaukee, WI, was able to troubleshoot and solve a problem at a residence in Palm Springs, CA. He reconfigured a Lutron Lighting system and changed door bell triggers using Option B access. Note: in this case, without any additional onsite support.