TECHNOLOGY

The only platform that combines search, RFP Creation, Contract Management, and Data Intelligence in the same product.

Vindow is able to compare hotels at a granular level based on the knowledge created by its algorithms. That knowledge is also used to make recommendations tailored to the user’s behavior.

Vindow Bid Intelligence algorithm provides real time feedback, allowing our clients to make more educated decisions with full transparency.

 

 

The only platform that combines search, RFP creation and data intelligence in the same product.

Vindow is able to compare hotels at an incredibly granular level based on the knowledge created by its algorithms.  That knowledge is also used to make recommendations tailored to the user’s behavior.  Vindow’s knowledge is like having a travel procurement agent that is constantly learning about your business and the market to make your travel procurement experience more intelligent and less painful.

   The Volume of Data: Access to data from millions of client’s reviews.

   Unique Data Intelligence: Vindow uses AI techniques such as sentiment analysis, topic extraction, and natural language processing.

   Vindow Parameter Scoring: We have created a unique industry score by processing and categorizing millions of reviews. Vindow uses 10 categories to rank hotels in which we have applied industry preferences allowing users to review hotels based on relevant feedback.

   Hotel Similarities: Using the individual scores as a baseline, Vindow is able to detect similarities between hotels which are many times missed by humans, improving the hotel selection process.

   Pricing Forecast: Predicting market performance with high levels of accuracy.

   Market Knowledge is Power: Better negotiations come from understanding hospitality industry drivers.

   The Volume of Data: Access to data from millions of guest reviews.

   Unique Data Intelligence: Vindow uses AI techniques such as sentiment analysis, topic extraction, and natural language processing.

   Vindow Parameter Scoring: We have created a unique industry score by processing and categorizing millions of reviews. Vindow uses 10 categories to rank hotels in which we have applied industry preferences allowing users to review hotels based on relevant reviews.

   Hotel Similarities: Using the individual scores as a baseline, Vindow is able to detect similarities between hotels which are many times missed by humans, improving the hotel selection process.

   Pricing Forecast: Predicting market performance with high levels of accuracy.

   Market Knowledge is Power: Better negotiations come from understanding hospitality industry drivers.

Vindow Innovation

Our statistical indicator uniquely rates a property based on multiple data sets.

The scoring methodology combines the existing ratings across dozens of travel websites worldwide with sophisticated deep learning algorithms that extract intelligence from hotel reviews at a very granular level. In that sense, the score expands the static rating model in travel websites with the intelligence expressed in hotel reviews.

Vindow Innovation

Our statistical indicator uniquely rates a property based on multiple data sets.

 

The scoring methodology combines the existing ratings across dozens of travel websites worldwide with sophisticated deep learning algorithms that extract intelligence from hotel reviews at a very granular level. In that sense, the score expands the static rating model in travel websites with the intelligence expressed in hotel reviews.

Vindow Technology FAQ

Below, we answer frequently asked questions about Vindow and our Technologies

Hosting/Infrastructure
Is the solution multi-tenant?

Yes

 

Does the vendor host the solution or utilize a third-party for hosting (IaaS/PaaS/hosting provider)?

Using AWS as IaaS

What compliance certifications does the platform/solution hold? (HIPPA, PCI, COBIT, Safe Harbor, SP800-53).

We are pursuing a COBIT certification.

What data center certifications does the hosting provider hold? (SOC-1, SOC-2, SOC-3, SAS70/SSAE-16, ISO27001).

We use AWS as a data hosting provider and they hold all center certifications.

Please describe the technology infrastructure that hosts your solution. If you have supporting diagrams which help describe your hosting infrastructure, please provide them.

Our solution is hosted in AWS. The front end is a React SPA served from a CDN.

Service layer is a collection of REST APIs built in Node.js, hosted as docker containers behind a load balancer that manage the amount of instances as needed.

The data layer is composed of different NoSQL DBs (DynamoDb and MongoDB). Every db has a Redis Cache to support them.

Machine Learning models are built in Python using TensorFlow, Keras and scikit learn and they a run in a cluster as docker containers.

 

Does the platform/solution provide hosting/infrastructure status reports (availability, performance degradation, etc.)?

Yes

Does the platform/solution utilize geographically dispersed data centers to serve customers? If so, how many are there and where are they located?

Yes, we have global replication for our static content via Cloudfront, and we have multiple instances of our APIs in different Availability Zones in the US.

Environments and SDLC
Does your solution have multiple environments to accommodate production and pre-production, so functional development and integration testing by IHG can be performed without affecting production? Are these environments community based or do you have multiple environments available for each of your customers?
We can provide community pre-production environments based on a request.
Please detail the process you use to develop and launch enhancements within your solution. How do you control and release different versions of code across customer instances or environments?
We use an Agile development process with two week long sprints. We release into our QA environment and have our analysts test each story and perform regression testing within the system. Once we are assured the functionality works as designed we release into our production environment.

Every release has it’s own branch in the source control system.

How often do you release patches or upgrades for your solution? How do you accomplish these releases while minimizing risk and downtime for your customers?
We have releases every two weeks (see above for further description). In addition, we can release hot fixes for urgent issues within 24 hours on an as needed basis.
Does the platform/solution provide change/upgrade/outage notifications to users?
We keep our customers notified via email of any upcoming maintenance windows with at least 24 hours’ notice.
How do you notify your customer base of new releases for your product? Is there a set schedule for releases and if so, how far in advance are they publicized?
Currently, we notify users via email of new features released. As mentioned before we have releases every two weeks. In the future we will be adding a section in the tool where users can find newly releases features and updates.
Does your solution offer the ability to refresh data within non-production environments on an ad-hoc request basis or is there a set schedule for refreshing data in non-production environments?
Yes, we can refresh data on a per request basis on non-production environments.
Data Management
Does your solution encrypt data at rest (RSA, DES, AES, Blowfish, Bitlocker, etc.)? If so, please provide details.
Yes, we use encryption at rest for DynamoDB, MongoDB, S3 and ElasticSearch. All of them using AES-256 keys.
Does your solution encrypt data in transit? If so, please provide details.
Yes, during communication between our internal services and with the customer, using the latest HTTPS standards.
Does the platform/solution have built-in data loss prevention capabilities?
Yes, we have automated backups for all our data services.
If a data loss occurs, clarify the impact to IHG - how it is disclosed, etc.?
If data loss occurs, Vindow will provide a forensic analysis of the root causes. We will update the data loss policies accordingly.
Does the platform/solution provide disaster recovery services?
Yes
Is disaster recovery data encrypted? Does it also exist in an unencrypted format anywhere?
Yes, the backup data is encrypted and it’s not available unencrypted anywhere.
How often will backups occur? What type of backup is performed?
Vindow does incremental backups every one hour.
Does the backup exist in a separate location from the primary data center where the solution is hosted?
Yes
Does the platform/solution allow classification of stored data into different security types? (Public, Confidential, Restricted, Proprietary)
Yes
Does the platform/solution have capabilities to treat each data classification differently in terms of encryption, access control, etc.?
Yes
Does the platform/solution allow tenant-managed encryption keys?
Encryption keys are managed by Vindow.
Does the platform/solution segregate data by tenant? How is data segmented?
Every piece of transactional data in the database is associated to a specific account and only accessible by users within that account.
Who has the ability to decrypt customer data? For example, vendor personnel?
Only the chief architect can decrypt customer data.
Does the platform/solution allow the customer to download a full copy of the customer's data if the customer stops using the solution? If so, how does the download occur?
Yes, on a per-request basis, we can provide an output file with the full set of data associated to your account id.
Does the platform/solution erase all customer data if the customer stops using the solution? How does the data deletion occur? How long will the data remain on the platform/solution before it is removed?
Yes, we can remove all customer associated data on a per-request basis.
Please describe your approach to storing and accessing historical and production data for transactions and reporting purposes.
Historical data is archived in their own tables. Transactional and historical data are always available and can be accessed any time. In case that both sources are required to fulfill a report, a fan out query is executed to be consolidated after execution.
User Security & Access Management
Which authentication and SSO mechanisms are supported by the platform/application? (SAML, OAuth, OpenID, AD/LDAP)
Currently, Vindow supports user login via username and password. We will be supporting OAuth and OpenID SSO in future releases.
Who has the ability to control access to the solution? For example, can the vendor add a super user account?
Yes, the vendor can use an Admin to control access to the solution.
Does the platform/solution provide admin audit and access logging?
Yes
Does the platform/solution provide standard user audit and access logging?
Yes, we can export this on per-request basis.
Does the platform/solution support 2-factor authentication?
We’ll be including 2FA in next releases.
Does the platform/solution support strong password enforcement?
Yes
Does the platform/solution support IP Filtering?
Yes
Integrations with IHG Systems of Record
IHG anticipates utilizing data which may be sourced from cloud systems (such as Salesforce and Workday). What capabilities does your solution provide to integrate with cloud systems?
We would need additional information to understand what data will be integrated from cloud systems. A custom integration can be developed as needed.
IHG anticipates utilizing an API Gateway for all integrations between internal IHG systems and external systems. What capabilities doe your solution provide to integrate with API Gateways (such as Apigee)?
All of our application services are exposed as REST APIs that can be integrated in any API gateway.
User Interface
Can the solution be “white-labeled” to IHG?
Yes
Can the UI accommodate different experiences per role or per other user attributes (geography, property, user type, etc.)?
Yes
Can the UI be personalized by individual users?
Yes
Does the solution support multiple languages?
Yes
Are session timeouts enforced by the application? If so, what are the timeout values? Describe the user experience when a timeout occurs.
Yes, we have a 1 hour timeout after user stops using the application. User will be redirected to login screen when this happens.
Performance
Has your product been subjected to both load and performance testing? If "Yes", please share the test results with us regarding user volume, product complexity, and transaction volume.
Yes
Can you provide performance statistics regarding page load times for your product during periods of low user volume vs. high user volume. Please provide these statistics across the various global regions?
Yes
Can you provide performance statistics regarding page load times for your product for simple, complex, and highly complex transactions?
Yes
Define the length of time you consider to be a “time-out” for your solution broken down by individual transaction, user workflow, and reports. Describe the related user impacts for each (for example, must a user re-enter previously input data fields?)
The standard time-out for single transactions is 90 seconds, reports generation up to 180 seconds. When the timeout occurs a notification, message is provided to the user without losing any of the inputted data. If in the retry attempt the transaction flows, no data is required to be reentered).
Based upon the volume of information defined for number of hotels, room attributes, hotel amenities, and conditions of sale, does your solution have the ability to process data loads fast enough to accommodate the desired frequency of scheduled loads (e.g. hotel data updated every 2 hours)?
Yes
Are you able to provide documented records of product performance statistics in operating environments and service call volume by global region (e.g. information related to issue, system, release, or service management procedures and reports)?
Yes
Support, Escalation, and SLAs
What types of support services do you provide to your customer base? What are the various pricing and availability/response models offered?
Download Document Here
Can you provide a description of your escalation process for Level 1, Level 2, and Level 3 production issues within your solution? What are your service level agreements regarding response to and follow-up on the resolution of Level 1, Level 2, and Level 3 production issues?
Download Document Here
Please include your target Service Levels (SLAs) related to your solution. Explain what SLAs you can commit to, how you measure SLA performance, and how you remedy missed SLAs. What penalties are incurred as a result of missed SLAs?
Download Document Here
Please indicate additional key performance indicators that you typically use to assess business/relationship performance for your customers.
Download Document Here
How is your SLA performance presented to your customers?
Business Reviews and Customer Success Reports on a monthly and quarterly basis.
Relationship Management
Describe the relationship management touch points and frequency you provide to maintain communication with customers. How often do customer account reviews occur?
Company will provide account management support available during normal business hours (9AM – 5PM EDT) to provide assistance regarding administration or operation of the platform provided by Company.

Account reviews occur quarterly.

How do you handle customer requested configurations and customizations to your solution? Please describe the process through request, response, prioritization, and implementation.
We offer an intake form dedicated specifically to request custom features, all feature requests are timestamped.

Client will need to categorize each feature request by their end goal, keeping in mind the company’s goals, both short and long-term.

Steps to handle new feature requests
1.- Analyze
2.- Gather requirements
3.- Prototype the feature
4.- Size task effort
5.- Budget the task
6.- Approval
7.- Bulid and test
8.- Release to production
9.- Gather feedback

Releases are made every 2 weeks

We provide market insight including hotel rate trends, ADR and occupancy forecasting, city news and events, economic drivers and hotel reviews, all in one source.