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. […]

Read More…

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 […]

Read More…

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 […]

Read More…

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. […]

Read More…

What’s PAYG Support ?

If you do not have a RAPID Service Level Agreement with us, but have an issue with your RAPID Software, technical support is available on a single incident basis. We help you to troubleshoot a specific problem, error message or functionality that isn’t working as expected. […]

Read More…