Most systems are interfaced to the hotel's property management system. This is generally by serial, but now systems are IP based. The newer card encoders are also IP based. The workstations that are running the encoders and the key database should be dedicated workstations, but these are usually networked for support and management. Some vendors are better than others, the ones that don't let use join these to our domain cause the most issues because we loose the ability have have these centrally managed.
Their statistics suck, even if their principles are sound.
Let us look at the last few years worth of rankings 2002 17th 2003 31st 2004 22nd 2005 44th 2006 53rd 2007 48th 2008 36th 2009 20th 2010 20th 2011-12 47th 2013 32nd 2014 46th
Seems like a yo-yo, maybe this index is more about creating headlines than true measure. Please do reference the On The Media story linked above.
I am just today working to install OCS Inventory on my network (3 servers, 50 clients). So far the setup of the server has been smooth. I'm now starting to get the clients installed.
My existing lock system only encodes the check-in date, the check out date, the number of keys (1 of 2, 2 of 2) and a sequence number.
On the date of check out the key will stop working at 3:00 PM. If you check out early, your key will continue to work until 3:00 PM on your check out date. But if I check someone else into the room and create them a new key, when they open the door, they will advance the sequence register on the door lock and all prior keys will stop working.
My system has the ability to but the guests name on the card but in order to do this the card must be made directly by the key system. This only happens when I make master keys for employees. Guest keys are processed through an interface between my Front Office system and the key system. As a result no name is transmitted and when I read the key it will list the guest name as Guest.
Slashdot Mirror
Most systems are interfaced to the hotel's property management system. This is generally by serial, but now systems are IP based. The newer card encoders are also IP based. The workstations that are running the encoders and the key database should be dedicated workstations, but these are usually networked for support and management. Some vendors are better than others, the ones that don't let use join these to our domain cause the most issues because we loose the ability have have these centrally managed.
Think for yourself, but have a look here.
Their statistics suck, even if their principles are sound.
Let us look at the last few years worth of rankings
2002 17th
2003 31st
2004 22nd
2005 44th
2006 53rd
2007 48th
2008 36th
2009 20th
2010 20th
2011-12 47th
2013 32nd
2014 46th
Seems like a yo-yo, maybe this index is more about creating headlines than true measure. Please do reference the On The Media story linked above.
I am just today working to install OCS Inventory on my network (3 servers, 50 clients). So far the setup of the server has been smooth. I'm now starting to get the clients installed.
My existing lock system only encodes the check-in date, the check out date, the number of keys (1 of 2, 2 of 2) and a sequence number.
On the date of check out the key will stop working at 3:00 PM. If you check out early, your key will continue to work until 3:00 PM on your check out date. But if I check someone else into the room and create them a new key, when they open the door, they will advance the sequence register on the door lock and all prior keys will stop working.
My system has the ability to but the guests name on the card but in order to do this the card must be made directly by the key system. This only happens when I make master keys for employees. Guest keys are processed through an interface between my Front Office system and the key system. As a result no name is transmitted and when I read the key it will list the guest name as Guest.