Step 1: Reset the Sensor
Remove the battery from the sensor. Wait ten seconds and then replace the battery back into the sensor. Make sure that the flat side of the battery is touching the coil within the sensor. Wait two minutes and then check freshloc.net to see if the sensor is online and reporting current data. If the sensor is not reporting current data, go to step two.
Step 2: Swap the Battery
If you have a spare new battery, replace the battery within the sensor with the new battery. If you do not have a spare new battery, take a battery from a nearby “working” sensor and use that battery to replace the battery within the “non-working” sensor. Move the “non-working” sensor to a spot within ten feet of a “working” reader. Wait two minutes to see if the sensor has now come online and is reporting current data. If the sensor comes back online, and you had to use a battery from a “working” sensor to test it with. Place the working battery back into the original “working” sensor that it came from and then, Contact FreshLoc Sales at 972-759-0111 ext. 2 to order additional spare batteries. If the sensor is still not reporting current data, move on to step three.
Step 3: Contact Support
Contact FreshLoc Support at 972-759-0111 ext. 4. Let support know that the above troubleshooting steps have been completed and that the sensor is still not working. Support will verify that all readers are online and any other troubleshooting steps that may need to be taken. Once all steps have been exhausted, if the sensor is still under warranty, an RMA will be created by the support technician for the return of the merchandise, and a like sensor with a 90 day warranty will be sent to the client.
What protocols are used?
UDP, TCP/IP and standard encapsulations. Depending on configuration, external addresses might be: http://www.freshloc.net/
How much bandwidth is required per client?
A very nominal amount, even in the busiest of systems. The average maximum is 10bps for each sensor. At 1000 sensors max is 10Kbits/sec, typical using our default compression is 1K bits/sec.
Does this product have wireless capability? If so, is it compliant with Cisco WPA, TKIP and LEAP security?
The following is supported by the WIFI version:
- WEP (Wired Equivalent Privacy) -64/128-bit encryption (RC4)
- 128-bit TKIP/CCMP encryption
- 802.1x EAP authentication
- LEAP (WEP only), PEAP, TTLS, TLS
- GTC, MD5, OTP, PAP, CHAP, MSCHAP, MSCHAPv2, TTLS-MSCHAPv2
Enterprise and Pre-Shared Key (PSK) mode?
Can this product be accessed through a modem?
No, there is no analog phone line support
Are any modem lines required?
Is a VPN connection required?
A VPN is not required. The application is browser based. If there are any optional onsite applications FreshLoc prefers a secure access for critical support issues.
Are you capable of supporting a site to site VPN connection (IP tunnel using the ISAKMP / IPSEC protocol suites)?
Yes, currently. The customer needs to furnish tunneling information.
Describe FreshLoc’s Servers
- We are a 24/7 NOC with distributed sites coming on line.
- Servers are secured by a Cisco Firewall and all ports are completely blocked.
- Servers update security patches automatically, with operator supervision daily.
- Extensive custom software suite and web pages operates on the latest or next to most current Windows Server Operating Systems, Microsoft Internet Information Systems and Microsoft SQL platforms.
- All software is designed or tested on Explorer 6, 7 and 8.
- All other non-Explorer browsers provide substantial functionality but are not technically supported.
- All servers are contained in temperature and humidity secured controller racks.
- Servers and raid array have dual supplies.
- Processors are multi-core and/or multiprocessor Dell and or IBM.
- Customer data is maintained online in RAID arrays.
- Loss of up to two drives neither compromise data nor its immediate availability.
- The software suite consists of watchdogs and dashboards which monitor all processes within the NOC(s).
- Backups are made 6 times per day with Symantec Veritas software.
- Memory capacity exceeds 12 Terabyte (12,000,000,000,000 bytes).
- Diskless disk drives are hot swappable with automatic failover to spares.
- VPN tunnels are Cisco based hardware VPNs.
Is there a requirement to run FreshLoc software on the client’s server?
FreshLoc is a Software as a Service (cloud) concept. Our Receivers transfer all data via an authorized port through the client’s firewall to the Internet and the FreshLoc data center. There is only one option that requires software to run on the client’s server. If the client wants to deliver pop-up messages directly to a workstation on the their network, a pop-up distribution application must reside on the server and be connected by VPN to FreshLoc’s server.
If so, what type of Connection do you need (e.g. modem, ISDN, VPN, etc.)?
Are there any specific file types or directories that must be excluded from antivirus scanning to make the application functional or perform optimally?
Are there any known compatibility issues with any backup software (Arcserver, Veritas, Commvault, etc)?
The newest version of Veritas is competent and proven
Are there any special routines involved in the backup of the application or database?
ISSS (Information Systems Security Standards)
What are the minimum workstation requirements?
Explorer 6.0 or better for browser applications. If you want to receive popups on workstations a local application needs to be installed.
Are there special printer/printing requirements?
Reports use color legends so printing in color is more informative
What Client side OS is required?
What Client side software will be needed (assume the workstation has nothing on it)?
Can Mesa provide electronic installation instructions?
There is a user’s guide on the website
What are the licensing requirements for each client (include any MS licenses needed)?
Is there a drive mapping(s) required?
Can the workstation use a DNS or UNC name to reference the server or devices?
Can client stations use DHCP to include any data collection devices?
Are any special procedures required to transfer your application from an existing system to a new system (in a technology refresh situation)?
What is Mesa's expectation for local support from the client site?
Ease of access when we are supporting you or one of your internal customers
Does Mesa Labs provide IS staff training?
Onsite or webinar-based training is available
Does Mesa Labs provide system manager training?
Onsite or webinar-based administrator training is recommended
Does Mesa Labs provide end-user training?
Onsite or Webinar based training is available
Are electronic manuals provided?
Yes, in Adobe PDF Format.
What is the database back end?
If there is a database backend, what version is required? What service packs are acceptable or required?
What type of database license is recommended (i.e.: MS-SQL Enterprise, per processor)?
What is the backup recommendation for the database?
Will database support be expected of the IT department once the application is in place? Or, will there be shared support between the vendor and the database team? Or, will support be handled strictly by the vendor?
Will this application interface with any other hospital systems (e.g. Sunquest, Peoplesoft, etc.)? If so what type of interface do you use?
At present, we do not believe our application interfaces with hospital systems
What protocol is used for interface(s)?
Mostly HTML to the user’s browser
Will this application interface with a Central Data Repository? Clinical? Financial?
No financial and no patient data. The application is strictly measurement information of machinery.
Is there patient billing, charging, registration, or scheduling involved?
Does this application comply with TJC, State Board, TDH, and other regulatory requirements?
We are committed to compliance with these disparate groups
Can updates be pushed down from the server to each workstation?
N/A, we are browser-based
Does the system support an authentication method other than passwords? If so, what method(s)?
Does the system support a hierarchy of access levels? If so, are these defined by the system or can they be modified to support our hospital’s needs?
Yes, from read only to complete dominion over the administration data
What are the minimum and maximum password lengths permitted?
8 and 14
Can users re-use the same password?
Can users be limited to accessing only their data?
Does the application maintain an audit trail of when and by whom passwords were created/changed?
Does (or can) the application maintain an audit trail of user activity?
Does (or can) the application force a user to change his/her password during the first on-line session?
Not at present
Does the application allow the user to change his/her own password?
Yes, if allowed by the Client Administrator
Are stored passwords encrypted?
Are stored passwords only accessible from the password system?
Does or can the system log users out for inactivity?
No. The browser refreshes its page by the FreshLoc html/java code every 10 minutes. Often times users will leave their browser open to the real time report they are currently watching or interested in.
Can the application authenticate through an LDAP server?
Does the system provide limits on the number of invalid access attempts allowed? If so, is the user locked out of the system indefinitely or for a specified timeframe?
Not at present
Why am I getting a "No Sensor Contact" alert for my CheckPoint sensor?
If you are getting the “No Sensor Contact” alarm for your CheckPoint G4 Sensor, there are a few simple steps you may take to troubleshoot and resolve the issue. The video below will help guide you through these steps to get your sensor back in proper working order.
Mesa Labs recommends the following 12 Keys to Successfully Implementing a CM System to guide you through this process:
- Assemble a Dedicated Project Management Team
- Compile a Complete Equipment List by Department
- Understand the Unique Needs of Each Key Stakeholder
- Secure Commitment from Each Department Director
- Floor Plans
- Select the Right Continuous Monitoring Vendor
- Post-Installation Transition Period
- On-Going System Support and Help Desk
- Annual Probe Calibrations and System Maintenance
- Regular Alarm Checks and Preventative Maintenance
- Disaster and Emergency Recovery Plan
- Maintain On-Site Spare and Emergency Parts