Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
Required the functions/features to be able to append prefix to the name of the ingested data instead of only the prefix for externalId.
We had 50 or more machines with the same OPCUA data structure, if we ingest the data into Cognite, the timeseries name will be the same though we can append prefix to the externalId. It will be great that the OPCUA extractor able to append the prefix to the name as well so it is easier to identify the data or events.
Gathering Interest
OPCUA | Customize timeseries and event name
Hi, and apologies for the late response!
A historian would resolve the underlying problem because it displays the data as a hierarchy, correct?
What if you model the incoming source data using a similar hierarchy, rather than ask the extractor to modify/change what (to it) becomes source data (which for some of our other customers would be a different problem/issue)?
Of course a historian will resolve this but the design of Cognite allows pushing data directly from the source (e.g. PLC).
It is not easy to ask machine supplier to model differently as the structure are the same for all machines produces.
Assume we have 10 similar machines with the same OPCUA configuration, all the names will be the same when push to Cognite.
E.g. Every machine will push Counter and Message from RecjectPlaceX folder to Cognite.
Each machine had its own machine name.
When push as timeseries to Cognite, there will be multiple “Counter” and “Message” in the timeseries
Though the externalId will have the full path hierarchy “Prefix”.CounterInterval.RejecPlaceX.Counter”.
It will be great that we could have the timeseries name to be “Prefix”.Counter or “Prefix”.Message.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.