5 Frequently asked questions about Capture

What is Capture? How does it work? Why Capture?

Questions that usually come up quickly during a first conversation, but in this blog we reply to some other frequently asked questions.

1. Is Capture safe? How is Capture secured?

We start with a question that many people worry about. Security! The answer to the question of whether Capture is secure is yes. As a developer of Capture it is of course easy to take in this statement, which is why we have brought in an external partner to confirm this by means of an external audit.

How is Capture secured is a question that we answer on the basis of our security whitepaper. You can download it at the link below

Security Certificate Audit

2. Where does Capture store the data?

The choice is yours! A major asset of the Capture framework is flexibility and the ability to store your data locally, in the Capture cloud, hybrid or even on your own servers or cloud.

You can fully configure your data strategy. Decide for yourself where, when, for how long, how much and which data you want to keep.

3. Can I connect Capture to my own data platform?

Do you already have your own data framework or do you want to link with a MES or ERP package? Capture uses REST API to connect with external packages such as Azure, AWS, Power BI, … and many others.

Capture is an open framework and can connect to any external platform that has implemented the capture data format via endpoints. Does this sound complex? Our team of engineers have extensive knowledge to set up these connections to measure

4. Is it possible to give access to customers or colleagues?

There are no limits in the number of users. Based on our user management it is possible to manage this in an easy and safe way. The right data at the right time for the right person at no extra cost. It is also possible to create teams to trigger reports or alarms to a group of users.

5. How can I analyze the data?

Capture offers different ways to dig deeper into the data:

  • Trigger based logging save data only when a certain state is reached.
    • Detail triggers can be described when a condition of a value is exceeded, for example a temperature
    • Status triggers are rather related to a status that is reached, for example an error status
  • Calculations
    On the basis of queries you can create calculations on different variables such as A+B=C and these can be used in visualization, alarming and reporting.
    In this way you can take the first steps towards predictive maintenance, anomaly detection or OEE analyses.
  • External data analysis
    It is also perfectly possible to use the API to download data, transform it and finally send it back to Capture.
    It is perfectly possible to import data in Python, C#, C++ and others or create custom scripts to process the data.


6. Bonus question: Can we also add custom features?

Yes, customization is part of our DNA and we believe that a "one-fits-all solution" doesn't exist. We like to listen to the challenges of our customers and build tailor-made total solutions.




Our competences

  • Data collection and analysis
  • Edge & Cloud
  • Security


Security Whitepaper