Do you want to introduce a new device type quickly?

Do you experience an issue in changing small parameters and commands towards devices as part of your provisioning and activation scenarios?

Do you want to replace costly Element Management Systems (EMS) that is hard to maintain and does give the correct transparency in fulfillment processes?

Values & Benefits

  • Replacing Element Management Systems give lowered CapEx cost and lowered OpEx costs

  • Pre-integrated with Provisioning, Inventory and Monitoring capabilities for lowered costs of integration

  • High level of configurability enables you to make changes continuously gives lowered OpEx costs


The Resource Controller is a capability that enables Netadmin to communicate directly with network elements. It encapsulates small scripts that is executed as atomic transactions, called drivers, towards the network elements. It is possible to use the drivers in provisioning flows, as troubleshooting tools, as collection scripts for monitoring and for performing reoccuring operations towards network elements.

With Resource Controller it is possible to reduce the amount of Element Management Systems and any integrations towards such systems. It is also a comprehensive tool for adding support in your fulfillment processes for new network elements that is introduced. It is also a way of fetching network information and present that within Netadmin Nine.


The Resource Controller connects to your devices and executes commands that otherwise is configured manually by engineers or by other types of systems. It has got the following key functionalities:

  • Communicates via CLI, SNMP, TL1, XML, HTTP and more protocols
  • It is possible as a user of Netadmin to write your own drivers towards network elements
  • Used in provisioning flows, monitoring and troubleshooting
  • Drivers are versioned and it is possible to rollback to older versions
  • A specific driver can have multiple implementations depending on network element vendor, model and firmware
  • Each driver has a definition with the required parameters that the driver needs in order to execute
  • Each execution is logged as a transaction
  • Drivers are programmatically written in a script language
  • The output can be formatted using XSLT

Since drivers are using a common scripting language it is possible to programmatically write conditions based on the communication with the network element. Typical drivers for a fixed broadband network would be VLAN related operations like adding, removing, or adding VLANs or enabling/disabling ports. Other typical drivers could be to add service profiles to ports or fetching signal values.

To summarize the capability of Resource Controller it is a highly configurable module for making it easier to create support for different network elements and incorporate that support into your fulfillment and assurance business processes.