The manageXSystem.sh and startXSystem.sh scripts are cumbersome to maintain and inflexible...copies have to be made for each configuration of BRs, EVBs and Aggregators. Also, experiment will want to have configuration management and revision control (i.e. a configuration database), and we need some method of translating database-stored variables to configuration files that the existing ARTDAQ Run Control infrastructure can use.
Included in the configuration management requirement is some form of configuration editor, which can load and save named configurations independent of running the ARTDAQ system that the configurations describe. The editor (and configuration files) should be extensible so that individual experiments can "plug in" configuration variables for their particular use-case.