ArchiGraph platform

What do you like best?

Our company is creating the city's infractructure models to help the local authorities and resources suppliers to optimize infractructure investments. This kind of modeling requires a complex representation of the infrastructure itself, of city's structure key elements, population distribution, as well as a number of their economic parameters. The ontologies are quite useful for the arbitrary real-world entities modeling which cannot be handled by the specialized modeling packages.

The key problem of using ontologies is that there is not much of the IT professionals ready to work with them. So we needed an ontology management tool which can be used by an average analyst or programmer after a short training. It is particularly important to be able to store ontology-structured data in the relational databases and access them through an API much simpler and faster than SPARQL. ArchiGraph is a promising solution of that kind, and we are on the way of adopting it in our processes.

What do you dislike?

The editor's UI could be more friendly in some aspects - for example in the workspace layout configuration, the entity editing form layout etc. The data filtering function doesn't allow creating complex filters, although the API allows it. It would be useful to provide an API allowing to transfer data from the platform to the BI tools, such as OData.

Recommendations to others considering the product:

If you need data modeling tool you have to test ArchiGraph

What problems are you solving with the product? What benefits have you realized?

Data modeling as basis for digital twin