iDT Unashamedly Revolutionary Software

iBIOS re-defines Hospitality Systems with 'iDT'.

When we came to design the interface for the iBIOS System, we took a radically different approach. We made iBIOS a 'Desktop' style environment. The Desktop paradigm allows information to 'pop up' when needed, and either fade into the background, or just 'go away' when it isn't, so we could fit a load more stuff in there. It also breaks down a large piece of software into lots of much smaller pieces that are only loaded when needed, which greatly reduces overall start up times.

One of the most exciting aspects of this system however, is the ability to provide an 'App Store' type environment. It allows businesses to pick and choose the functionality they need, and if that functionality doesn't exist, it can be written and dropped in without impacting the rest of the system, or the experience of other users.

We also took this concept a step further, and introduced 'extensions'. Extensions are not separate 'apps', rather they are small pieces of code that can modify the functionality of an existing app.

A short, 2 minute tour of iDT, the iBIOS Desktop

iDT is a web app, it runs in a browser, but by fully utilising the recent advances in web technologies we have made sure that it runs just as fast as a native application. iDT caches (or 'stores') regularly used data on the machine running it, meaning that it doesn't need to go out onto the internet to retrieve that data. This not only makes it faster, but it also means that it is capable of operating without an internet connection.

Security of the Internet...

Although iDT is a web app, we've gone the extra mile to ensure its safety. iBIOS knows where your property is, we need to know so that we can send guests there! iDT uses geolocation services to ensure that people trying to access your system are at least in the same area. We monitor the IP Address of all logins, so that we can flag spurious activity from unknown locations, we save no identifiable data client side, so no usernames or passwords are held on the local machines, and we one-way encrypt (MD5) sensitive data on the client before sending over the net.