FAQs

1. How is the product deployed?

Deployment Model – RobilityAI®

2. How is the product licensed?

 All Robility components are licensed on an annual basis. Sutherland also offers automation development as a service, which incorporates Robility licenses as bundle.

3. How is the product supported?
Documentation and Resources: Robility offers extensive documentation, guides, and information regarding licensing of Robility products. These resources are available through the Robility Documentation Portal.

Technical Support: All active Robility Enterprise Licensed customers are provided with support to address queries relating to the product via email and call.

4. What is the RTO / RPO for the product?

Robility Manager Cloud’s Recovery Time Objective (RTO) and Recovery Point Objective (RPO) are not universally fixed values; they are tailored to meet the specific needs of each client. Robility team collaborates closely with clients to define RTO and RPO values that align with their business continuity requirements, ensuring minimal disruption and data loss in the event of a system failure.

For instance, in scenarios involving disaster recovery for Robility Manager, the deployment model can be configured to ensure both high availability and disaster recovery. In such configurations, both Manager nodes are active, and the load balancer directs traffic to them using a specific algorithm, such as Round Robin or one of its variants. This setup requires good network connectivity between the datacenters, which are located in different geographical areas.

It’s important to note that the specific RTO and RPO values will depend on the deployment model and the client’s specific requirements. Therefore, it’s recommended to consult with

Robility Product team to determine the appropriate RTO and RPO for your specific use case.

In general, Robility Manager Cloud managed by Sutherland is designed with robust disaster recovery capabilities to ensure business continuity. The platform offers a Recovery Time Objective (RTO) of 6 hours and a Recovery Point Objective (RPO) of 15 minutes. This means that in the event of a disruption, Robility aims to restore services within 6 hours, with a maximum data loss of 15 minutes.

5. How does the product meet GDPR compliance requirements?

Yes. Robility is committed to complying with General Data Protection Regulation (GDPR) and implementing the below measure to ensure adherence.
Privacy by Design: Robility incorporates privacy considerations into the development of all its components, ensuring data protection is a fundamental aspect of the design language.
Security Measures: Robility employs industry standard security practices, including encryption and access control, to protect personal data from unauthorized access.

6. Does the product store PII data?

Robility products do not store any PII by default.

PII collected during automation processes remains the property of Robility’s customers. Customers have full control over the data, including decisions on processing and purposes. Users can view and edit data collected and stored locally on their devices, ensuring transparency and control.

All data transmitted to Robility is encrypted both in transit and at rest. This encryption ensures that PII is protected from unauthorized access during transmission and storage.

7. Is it possible to configure data retention events and periods?

We currently do not have this option to configure data retention events and periods.

8. High-level technical diagrams