Develop Processes for Administering and Managing NetTerrain to Multiple Editors

We want to extend the editing ability of NetTerrain to multiple teams (Infrastructure for example) to allow them to manage their own design area, but we need a way of managing how changes are made and controlled. Other areas that need to be defined are:

• What training will be given to new users, how, and by whom?
• Do we need to implement or is there the ability to restrict editing rights on certain pages to minimise mistakes?
• What do we do if someone makes a mistake and we have to roll back to the previous day's backup? How can we minimise this risk?
• How can we create a basline and identify the changes?
• How will changes be managed, reviewed, and agreed?
• Will NetTerrain be the single source of truth and negate the need for updating the reference design documents?
• What improvements can be made that will allow us to get the most out of NetTerrain?
• How can we identify the different array releases, including how we identify temporary equipment during each stage?
• What are the costs for increasing the number of editor licenses?
• Who will manage the overall process and oversee the changes?