This section covers the conclusions from the two implementations that have so far been made using the Managed Resource Interface.

The MRI encourages incremental development of systems. It is a natural interface that allows the subsystem to be broken down into subtasks that can be developed and tested independently before being integrated. It also allows subsystems to be added at a later stage of the development phase, allowing engineers to concentrate on core functionality above details such as graphical tools or standardized protocols. MRI also allows subsystems to be interchanged or rewritten with little effect on the overall software. Reusability is also an important element which we has been aided and made possible. All of these arguments follow the philosophy that has to be adopted when working with Erlang, and attempts to enforce it where it is not obvious.

The MRI was first used in the rewrite of the ANX. After the rewrite, it allowed a small group of software engineers to quickly and efficiently implement an HTTP based management system. The Local Craft Terminal, a tool used by operators out on the field, was implemented with no impact on the existing CP software. In addition, this team was able to test their code by reusing the stubs the engineers working on the SNMP rewrite implemented. The original aim of the MRI was thus achieved.

The AxM3 project, on the other hand, was started from scratch with the MRI in its original design. The MRI had successfully been used as an interface in the prototype, giving simple tools controlling the system a protocol that was first used locally on the same node and across a network through the use of RPC:s.

The AxM3 project reused the ANx MRI Information model for all equipment and alarm handling, providing the first defacto Information model. This allowed for large parts of SNMP specific code and Managed Resource tools from the ANX to be reused, including parts of the MRI stubs.

The project, in turn, resulted in several generic subsystems in the NE interfacing the MRI. These subsystems, including equipment and alarm handling, can in turn be used in any telecom software platform. This base, along with all the experience which has been collected in this area so far, will now allow for the implementation of the perfect system. A system where standardized management protocols can be placed alongside each other with out affecting the architecture of the logical parts of the software architecture, providing the flexibility required to quickly adapt to changing market requirements or information models.