Get the answers you need

Frequently asked questions

Here is a summary of the most common questions we get when speaking with prospects and partners.

Technical (8)

The SOFTBOT Platform can be cloud-hosted by SVT or in a customer provided environment.

No. The platform is designed to reduce the demand typically placed on teams. Once deployed, system monitoring typically takes less than 4 hours per week.

SVT requires a Postgres database for the platform but can support the utilization of other databases depending on the customer needs.

If you choose to deploy on the SVT cloud, a broadband internet connectivity to your facility is required. If the deployment is on-prem, SVT can provide exact specs based on your solution, but a modern processor with at least 16gig of RAM is a minimum requirement.

SVT, a partner, or customer can make some modifications to their SOFTBOT configurations.

SVT has a partner network for coverage in EMEA, APAC and LATAM.

No, SVT standardizes data and communications so that OEMs do not have to change their API. This is important to ensure every technology can remain on standard. Why? Because every time you customize, you go off standard, which means its more costly to deploy, maintain or adapt to your changing business requirements.

We are frequently asked about latency. To provide an accurate response, please provide answers to the following questions:

  • What real-work operations require a performance SLA on messaging?
  • What are your messaging volumes?
  • What connection technologies are you using? (REST, TCP/IP, flat file, etc)

With these answers, we can provide guidance on expected latency. We have tested our platform with various technologies and protocols, and we have found that in most cases, the latency we introduce is negligible or within acceptable limits for the operations. For example, we can handle TCP/IP messages in milliseconds, REST calls in seconds, and flat files in minutes.

General (8)

SVT helps accelerate innovation by decoupling automation deployments with upgrade paths. This enables customers to benefit from automation without waiting while also providing a seamless path to upgrade with the business is ready (no rework needed).

The SOFTBOT Platform:

  • provides multi-point integrations
  • connect multiple WMS
  • doesn’t not require the OEM to change their API
  • standardizes data from all connected technologies
  • provides out-of-the-box active monitoring and alerting

Customers often do not have the skillset or context to build solutions in house. Plus, it takes teams months and months to build, taking resources away from other critical priorities of the business.

Customers pay annually to reduce risk of system downtime across disparate technologies and for the ability to easily change or scale their automation deployments with minimal disruption or rework.

OEM’s are great at deploying their own tech, yet unlikely to be experts at integrating other technologies from other providers. It’s a great option if you have 1 site and just use that one OEM. If you have multiple technologies and/or multiple sites, this option is limiting. Plus, it’s unlikely to provide out-of-the-box visibility into the system health of all your automation technologies.