NORDUnet Network Inventory

1

See components and their relation to other components for trouble shooting purposes when there is an alarm or trigger.

2

User needs to be able to update the system when a change occur to get the system to reflect reality.

3

See all components and their relation to other components if there is an alarm to help ticket creation. Also to help finding an already made ticket or to determine not to make a ticket.

4

Resources can be put in service or out of service to make the NOC aware what is in use.

5

The NOC should be able to find out how a customer is affected by a problem to be able to know what to write in a ticket.

6

Find information concerning a site to help a technician get to the site and to find the way inside the site.

7

See free resources in equipments, cables and connections when planning to install new services.

8

Reserve resources in equipments, cables and connections after deciding how a new service should be implemented.

9

The system should support multi-endpoint connections to be able to document Ethernet services or similar.

10

Reserve IDs for cables to be able to print a batch of labels and later label the physical cable.

11

The user should be able to bulk import structured information to make it faster to input information into the system.

12

Be able to see who made changes to the components in the system so you know which user to ask about the change if you have any questions.

13

The user should be able to define new components without involving the developers when new equipment are bought or new connections provided.

14

The NI-system should be able to compare equipment information in its database with the live equipment to verify its consistency.

15

A user should be able to comment on components to pass along temporary information to colleagues.

16

User should be able to search for components based on several criteria to get statistical information.

17

The user should be able to store a search so that complex searches do not have to be rewritten.

18

The system should support read-only and read-write users to keep integrity of the data.

19

The user should be able to add user created features in the form of plugins so the user can extend the system to suit the users needs without involving the developers.