We will agree on the definition of the problem with you when you raise the support incident. The incident will be closed after our support engineer has delivered one or more suggested solutions to you which resolve the issue. If you are not happy with the resolution you can notify us. It is at Automsoft’s […]
Archives: FAQs
Am I guaranteed a solution ?
Although our support engineers will make best efforts to resolve your issue, we cannot guarantee to resolve all issues. If the support engineer is unable to deliver a solution, you’ll be notified and the case will be closed as unresolved. It is at Automsoft’s discretion whether to refund the PAYG Support Ticket fee. […]
Am I restricted to the tag name provided by an OPC server ?
No, RAPID must use the name from the OPC server to collect data from it, but also supports 2 additional naming fields for each tag. These are ‘Alias’ which is typically a shorter name for the data and ‘Description’ which is a longer name. For data sources where there is no specific item names, the […]
Does RAPID support Store and Forward data collection ?
If store and forward is required then a RAPID Data Agent can be installed local to the data source (OPC, MODBUS, MQTT etc) and this will collect data from the source independently of the state of the RAPID system or its network connection. During normal operation the Agent sends the data to RAPID over a […]
Does RAPID support Alarm & Condition data ?
Yes, RAPID supports insertion of both continuous and A&E data. There is a specific schema for A&E data that is based on the OPC specification and there are a number of agent plugins that support the collection of A&E data (OPC, SQL etc). This schema also supports vendor defined attributes. […]
Is there a limit to the number of events that can be inserted to each tag ?
Essentially no. Each tag can have up to 1000 events per second (more if multiple events share the same timestamp, where we create an internal array of the data). The only real limit will be imposed by the storage space available. […]
Does RAPID support data backfill ?
Yes, RAPID allows backfill of data into the database. By default any time range can be inserted, but there are settings to limit insertion of both past and future data. […]
Can I backup the database while in production ?
Yes, RAPID supports three mechanisms to backup the system, all work while in production. The first is a meta data backup, where the structure of the system can be backed up without the data. The second is a regular incremental backup that can either be invoked interactively or via a schedule. Finally there is ActiveBackup. […]
How many tags can be supported in a single RAPID Database ?
The structure of a RAPID Database consists of 1 to many nodes each containing 1 to many tags. In a normal system we would recommend that each node contains up to 100,000 tags and that there are up to 100 nodes. This means that each DB can have up to 10 million tags. If more […]
How does RAPID compress data ?
The underlying schema used to store the data has a patented mechanism to compress the timestamp while retaining its accuracy and the accuracy of the data value. If lossy compression is permitted then RAPID also suppports a number of data compression mechanisms at the cost of data accuracy. […]