Re: ISP billing - data collection, correlation, and billing

[Jose Gerardo Perales Soto <gerardo.perales () axtel com mx>]

Hi, we use the same approach as you. When provisioning services they’re identified by a label in the interface 
description so data is collected and delivered to our billing systems.

Gerardo

El 14/07/17 13:43, "NANOG en nombre de Sean Pedersen" <nanog-bounces () nanog org en nombre de spedersen.lists () gmail 
com> escribió:

    I went back a few years in the archives and found a few odd references, but
    not much discussion. I'm curious what some other approaches are to
    usage-based billing, both the practice of generating/correlating data and
    the billing itself.



    We bill based on use/95th percentile and our system is rudimentary on its
    best day. We use SNMP and interface descriptions to generate data and
    correlate it with customers. This works for the most part, but leaves a lot
    to be desired.



    Ours is one method, and I've seen others who use NetFlow data in a similar
    fashion, with the assumption that the NetFlow data is correlated either via
    IP address or source interface.



    Most of the systems I've seen are full-fledged CRM, billing, and OSS, which
    is a little overkill for us at the moment. I think we would have issues
    trying to integrate such a multi-headed beast into our organization at this
    time.



    What methods do you use to collect and correlate data?

    What systems, if any, do you use?



    I'm a little in the dark as the billing/OSS side of things is outside of my
    normal scope and would appreciate any recommendations.



    Thanks!




________________________________

NOTA: La información de este correo es de propiedad exclusiva y confidencial. Este mensaje es sólo para el destinatario 
señalado, si usted no lo es, destrúyalo de inmediato. Ninguna información aquí contenida debe ser entendida como dada o 
avalada por AXTEL, S.A.B. de C.V, sus subsidiarias o sus empleados, salvo cuando ello expresamente se indique. Es 
responsabilidad de quien recibe este correo de asegurarse que esté libre de virus, por lo tanto ni AXTEL, S.A.B. de 
C.V, sus subsidiarias ni sus empleados aceptan responsabilidad alguna.
NOTE: The information in this email is proprietary and confidential. This message is for the designated recipient only, 
if you are not the intended recipient, you should destroy it immediately. Any information in this message shall not be 
understood as given or endorsed by AXTEL, S.A.B. de C.V, its subsidiaries or their employees, unless expressly so 
stated. It is the responsibility of the recipient to ensure that this email is virus free, therefore neither AXTEL, 
S.A.B. de C.V, its subsidiaries nor their employees accept any responsibility.