|
|
One BIG and hopefully low hanging option we could add here is Data Flags like in InfoAsset Manager. If different users log into the platform we could easily track who changes what assets, objects, or fields. Could also add custom flags for where data came from (GIS, CCTV, etc.) Starting with these base tools, we could then add inference tools, ML/AI driven inferences, etc. in later versions. But all of it becomes much more useful with Data Flags. For whatever reason, few competitors seem to have this and users find them really useful.
Use Cases:
You have multiple users/organizations that are adding to a city's Info360 project. Everyone needs to track who's making edits where, and that the consultants/sub consultants are adding information as promised
You have multiple data sources coming together in the cloud on a regular basis. But then you realize the diameter values don't look quite right. You need to trace where those bad values came from
You have a database where 90% of the diameter values are present, but 10% are missing. You want to infer the 10% based on proximity and connection to adjacent pipes. By adding an inference flag, you can later tell the difference between 'real' diameter data and inferred data
Another one....down the road we might have WO's which are automatically generated from alerts. You'd want some kind of data flags to differentiate those from WO's which have been manually created. ML/AI creates a whole other story as well
Agree we could leverage our platform asset registry as a selling point - but two key requests:
We need to help solve differences between the asset network copy and the model. Wherever they're not 1:1, provide an easily relationship to share data both ways. The key is that we assemble one central point of truth, and it can run model simulations and offer asset insights all at once. No cumbersome data transfers.
Allow API access so that other software can use our data. Otherwise we'll never be the central point of truth.