Integrate force/location into configuration #23
Description
Right now the force and location data is passed via Rates.Configuration.ProductionOptions. For many (all?) types of applications it is necessary to keep them next to the configuration itself. Might be worth integrating into the configuration instead.
I have some reservation about this as this data is defined redundantly in a meta configuration. Data-wise it would be possible to have meta children with different force/location, but that doesn't really make any sense.