iv. CMS management functions
1. The NMS shall support a hierarchical configuration state change approach i.e. planned, installed and in-use.
2. Each stage should be security / user controlled to disseminate responsibility between organisational departments.
3. All configurations must be linked to templates to ensure standardisation across creations.
4. Mass configurations must be possible via pop-up wizard functions and mass configuration tools.
5. The NMS shall always be master in regards to network configurations implemented on the network. NMS to element synchronisation must be possible.
6. All configurations in the network must have a rollback function to ensure as-was state is possible.
7. The NMS shall provide network auto discovery and graphical display of the network layout.
8. The system shall provide Nodal Element inventory collecting the information automatically from the managed Nodal Elements (modules, boards, ports, firmware and software version, etc.).
9. The NMS shall support remote software upload/download to Nodal Elements.
10. The NMS shall support remote configuration upload/download to Nodal Elements.
11. The NMS shall support execution of command files to the Nodal Elements. It shall support importing commands from external scripts.
12. The NMS shall provide tools for automatic Network Element massive provisioning and data filling.
13. The NMS shall support automatic network data backup on a pre-set basis (daily, hourly, weekly, etc.). It shall be possible to initiate a backup, total or partial of the Network Element data and transfer the data to a back-up media connected to the NMS. The NMS shall provide functions to initiate a complete system backup.