Hi Christhiam,

Indeed, TR-069 is a very relevant standard in the context of CPE data collection, i.e. a DataMiner EPM solution deployment.  DataMiner does not offer TR-069 out of the box though.  While the protocol engine would be perfectly capable of supporting this, reality is that this has never been required (so far).  The main reason so far is that TR-069 in many ecosystems that we came across was a (fairly expensive) option that had to be activated, and alternative (non-TR-069) APIs and methods were available to collect the required data from the CPEs (i.e. the flexibility of the DataMiner protocol engine was leveraged to avoid the TR-069 route).

But if TR-069 is effectively in place, and if it is the preferred option, then of course DataMiner would be able to support that (i.e. DataMiner comes with the guarantee that it can interface with any data source, irrespective of the protocol or type of interface that would be required for that purpose, including both standard and proprietary / vendor-specific solutions).  Now, I do believe that in that case the best option is to look at what kind of APIs are available on your ACS servers, because that is probably the most logical point to tap off the data, and get it flowing into your EPM platform (where it is probably then further combined and aggregated along with data coming from other sources).

Hope this answers the question.  Feel free to get in touch if you have more questions.  And thank you for using Dojo!