TR-069: MAKE VS. BUY

At first glance, developing a TR-069 product seems easy.

Not so fast!

Developing a TR-069 product that is interoperable with others in the market is a difficult and time-consuming task. The TR-069 suite of protocols is loosely documented and interoperability remains a significant challenge. TR-104 and TR-111 are an even greater challenge because of the layered data structure and external systems involved.

Furthermore, keeping up with the changes in the TR-069 protocol set is required to ensure future compatibility; do you want to dedicate an engineering team to this?

Telcos often develop their own ACS. Even if the ACS is not fully TR-069 compliant, the telco doesn't care: the TR-069 client must support their ACS. Dimark has already done this work and won these deals.

The last thing you want is lose a deal because the TR-069 implementation has a bug and fails in trials, doesn't function with the Telco's ACS, or lacks the required functionality.

Internal development efforts are too expensive from the perspective of ROI, time to market and lost sales.

Dimark has been doing nothing but TR-069 for almost four years, and the reason we are so successful is because our software works in deployment, we support all elements of TR-069, and we keep current with the changes in the specifications.