I would really need more context to be able to answer this question, however some things that we look from the operational side of things are the following:
The AIXM tool we use to store the aeronautical features needs to be easy to use, that is a pre-requisite. It should as much as possible have a human-machine interface (HMI) that hides the more complex parts of AIXM that we shouldn't be dealing with but still exposes those parts we need
It needs to have a way to apply business rules, checks, validation and let's use see quickly where any input mistakes or rules have been broken. There is nothing worst than spending months of effort getting data inside without validations to just realize the whole AIXM database is just plain bad. Garbage In = Garbage Out
Should have a way to allow to add features without direct impact on other features until you are certain to make the changes permanent, so a way of working on a "branch" that is not still in the "main" area is key to be able to isolate the working data from the operational one. In many places they call this containers, work packages, etc
Backups, Backups, Backups! Any tool we use needs to have this essential feature and depending on how much information and how often we update it the backup may need to happen in closer intervals or not
System login of errors, updates, etc. In essence we need logs for traceability and to ensure that all the processes have been done including access control to just the right people with the right credentials.
Modern interoperability possibilities, either through AIXM exports or other means like the use of APIs. Development in 2021 and from quite a while relies on the use of API to access some information about the database without knowing the inner structure of it. In this way we can hook one system to another and they can interact. AIXM is more of a transport layer or payload but it is not very efficient (probably) to make systems ingest data this way. I am not programmer so I may be saying something totally dumb but this from a GIS perspective of getting a query to get all of the airports in my area of interest (AOI) would be interesting without needing to read and parse GML. Let's say each use case has their own methods and procedures.
I am a GIS person and I do love visualizations! So for me being able to see the information from the DB in both tabular and geographic ways is definitely a plus. Our brains are not wired to understand the bits and pieces of individual tables, rows, attributes and entities. We need structure and familiar ways to put everything together.
Provides adequate training, there are many powerful packages in the software world that can do a lot of things but their documentation and the possibility to get training makes them only useable by their developers and core power users. Same thing happens with AIXM databases in the aeronautical information management (AIM) world. If a system doesn't provide good training that includes knowledge transfer or know-how then it will be difficult for the average AIM staff to be able to use it. Knowledge is power. On many occasions the issue is you need not only the technical background but operational background in order to really understand the bottlenecks.
I would really need more context to be able to answer this question, however some things that we look from the operational side of things are the following:
The AIXM tool we use to store the aeronautical features needs to be easy to use, that is a pre-requisite. It should as much as possible have a human-machine interface (HMI) that hides the more complex parts of AIXM that we shouldn't be dealing with but still exposes those parts we need
It needs to have a way to apply business rules, checks, validation and let's use see quickly where any input mistakes or rules have been broken. There is nothing worst than spending months of effort getting data inside without validations to just realize the whole AIXM database is just plain bad. Garbage In = Garbage Out
Should have a way to allow to add features without direct impact on other features until you are certain to make the changes permanent, so a way of working on a "branch" that is not still in the "main" area is key to be able to isolate the working data from the operational one. In many places they call this containers, work packages, etc
Backups, Backups, Backups! Any tool we use needs to have this essential feature and depending on how much information and how often we update it the backup may need to happen in closer intervals or not
System login of errors, updates, etc. In essence we need logs for traceability and to ensure that all the processes have been done including access control to just the right people with the right credentials.
Modern interoperability possibilities, either through AIXM exports or other means like the use of APIs. Development in 2021 and from quite a while relies on the use of API to access some information about the database without knowing the inner structure of it. In this way we can hook one system to another and they can interact. AIXM is more of a transport layer or payload but it is not very efficient (probably) to make systems ingest data this way. I am not programmer so I may be saying something totally dumb but this from a GIS perspective of getting a query to get all of the airports in my area of interest (AOI) would be interesting without needing to read and parse GML. Let's say each use case has their own methods and procedures.
I am a GIS person and I do love visualizations! So for me being able to see the information from the DB in both tabular and geographic ways is definitely a plus. Our brains are not wired to understand the bits and pieces of individual tables, rows, attributes and entities. We need structure and familiar ways to put everything together.
Provides adequate training, there are many powerful packages in the software world that can do a lot of things but their documentation and the possibility to get training makes them only useable by their developers and core power users. Same thing happens with AIXM databases in the aeronautical information management (AIM) world. If a system doesn't provide good training that includes knowledge transfer or know-how then it will be difficult for the average AIM staff to be able to use it. Knowledge is power. On many occasions the issue is you need not only the technical background but operational background in order to really understand the bottlenecks.