The next data acquisition mechanism supported by RevTwo is via a cloud data source. Cloud data access can be optionally performed for each issue submitted to RevTwo. Each product type has its own cloud data collection mechanism and is invoked regardless of the presence of an existing data set. In fact, the cloud data acquisition has the ability to modify the data set submitted with the issue before AI evaluation. Each issue that utilizes cloud data acquisition, goes into a pending state until the cloud data request is satisfied.
The RevTwo cloud data access mechanism is not limited to a single data source.
The most common cloud data acquisition mechanism utilized by RevTwo is an existing IoT platform. RevTwo will request the desired information from that system and wait until it is returned. Utilizing an IoT cloud is the preferred mechanism when the RevTwo is invoked from a location that does not have direct access to product data, such as a contact center.
Supported IoT clouds include but are not limited to Microsoft IoT Hub, AWS IoT, and PTC ThingWorx.
Other Enterprise Data Sources
In addition to IoT clouds, RevTwo can access data from cloud-based systems of record. The only requirement for RevTwo is that the desired platform has RESTful web-services. Examples of cloud systems include CRM or ERP systems such as Salesforce or SAP.
Private Customer Data Sources
The final data acquisition mechanism supported by RevTwo is typically used in plant maintenance scenarios or when a cloud system is operated in an on-premise configuration. With this mechanism, RevTwo utilizes a data queue to acquire data securely from a company’s IT environment.
The RevTwo data queue accepts requests from RevTwo and puts them on the queue for the appropriate data provider. Within the company’s IT environment, a RevTwo agent monitors its queue for data requests. When a data request is seen, the RevTwo agent will perform a data acquisition script to access the desired data from the local enterprise system. Once the data is acquired it is placed on the queue satisfying the request. Upon receipt by the cloud queue, it is returned to RevTwo for processing.
This mechanism maintains the integrity of the customer’s firewall and can even be operated within their IT environment.