DOORS Next process/project template inheritance

In a nut-shell DOORS Next currently has the following 3 limitations:

1) The Process Template inheritance for DOORS Next doesn't work. The way we work with RTC is that we have a ‘Master' project area and all other project areas inherit their settings from that. Essentially we want the same for DOORS Next. This allows us to centrally define and control the Process Template that all other Project Areas will use. This makes rolling out changes to Process Templates easier as we just need to make the changes in one area, and all other Project Areas automatically pick it up.
2) DOORS Next currently has a separate Process and Project Templates. However they are very tightly coupled, e.g., in the Process Template we define the Workflow that our artefacts will be using and in the Process Template you define those artefacts and specify that they are using a particular Workflow. However when you setup a new project area and pull in both the Process and Project template, this coupling is lost so each time we need to go in and reset all the connections (which takes a while). This means that for each Component we setup, we have to redefine the connections between the Project Template it is using and the workflows, and then go into the Process Template in the particular project area and reset the Permissions for each artefact in that component. This can take hours per component!
3) The DOORS Next Project Template cannot be inherited, currently you have to import the Project Template into each component you create. Ideally we should be able to specify a DOORS Next Component to inherit it's Project Template from another Component. This would allow us to have a ‘Master' Component and thus manage changes to the template in a single area. Currently if we need to make changes to a Project Template, we then need to flow those changes out to every Component individually, by hand. Given that with a full-scale deployment for the business will result in us having thousands, if not 10s of thousands of components, it makes the scalability and long-term support of DOORS Next incredibly large, so much so that we cannot allow wide-scale usage of the tool within MBDA.