There are two approaches to developing systems that can communicate with each other. Either
you can use an interface designed specially to meet your needs or you can use some
standardised approach. Each has its advantages. Using standards (or open standards as they are
sometimes called) confers a range of benefits in developing systems, and it is worth stating them
briefly and then looking at the benefits of using a proprietary approach.
They key benefits are:
-
You are not tied into a single supplier as the system will work with anyone who is using the
same standard. Some standards that work like this are so obvious that they are almost
invisible. A good example is the electric socket. You can plug anything you want into a socket
without worrying as toasters do not use different plugs to say televisions. The only time that
this becomes visible is when you travel abroad and find a different standard in use, which can
be overcome using a travel adapter.
-
Migration is easier related to the last point, you will be able to change component of your
system more easily if they are using the same standard, and are unlikely to have to expend as
much effort compared to incorporating a new component within a proprietary environment.
-
Development costs are shared. Instead of having to fund the development costs for your
particular solution the costs are shared between everyone using the system.
-
Future proofing. Standards are developed to be as widely applicable as possible, and are
continually under review and revision to meet changing needs. This means that the standard is
likely to meet your needs and that many people have been thinking about it to solve the
problem. You are therefore likely to find it easier to change as your needs develop.
In short then, open standards give greater flexibility and reduced long term development and
support costs, and prevent you getting 'locked into' a single supplier.
The alternative approach is to use specially designed systems (often referred to as proprietary).
These can be more efficient as they is designed to do exactly what you want and it may as a result
also be easier to implement in the short term. The major disadvantages are:
-
Only a limited number of systems will be able to make use of it which may mean that you
either have a large implementation task when you buy additional parts of the MLE or that you
are unable to use a large proportion of the systems on the market.
-
All the adaptation and improvement has to be done for these systems, you are not able to take
advantage of developments that are being undertaken at a national or international level. The
advantage of standards is that any system that is using them will (in theory) work with any
other system that is using the same standards. Of course it is not that simple (see the limits
of standards below).
Where vendors are working towards the same standards then it should be much simpler to
implement the connectivity you need to make an MLE work. There is also the advantage that the
standards are continuously being reviewed and updated in the light of changing needs across the
community and that you are likely to find many of the things that you want to do are enabled as the
standards are updated.
