Currently the specification implies that the manage subsystem parameters service is used to be able to provide a list of encyclopaedic data alongside other subsystem parameters. It might be a nice separation of concerns if the encyclopaedic data service provided a dedicated means for subsystems to advertise data sets that they are prepared to import and export

It would be desirable for the services to support data export as well such that any encyclopaedic data that had been tailored by a user could then be exported for use on other systems or to be archived for later reloading after events such as a system reinstallation.

Some encyclopaedic data sets can be quite large and therefore giving a subsystem the ability to report progress updates to the CMS such that a user can be kept informed could be beneficial

In the DDS PSM IDL the end_sensor_track_type has a key on subsystem_id. As each message is related to a particular track id then it should also be keyed on the_sensor_track_id such that subsequent instances relating to other tracks do not overwrite the current instance before it is able to be read by subscribers.