Slashdot Mirror


Ask Slashdot: Management Software For Small Independent ISP?

First time accepted submitter Vorknkx writes "I work in a small ISP. Most of our customers have cable modems but some of them are using Canopy or Ubiquity products. To manage all that, we're using a number of programs and solutions not necessarily made for such a task that are kept up to date simply using copy and paste. We have an Access database for all our internet customers, an Excel document for our wireless users, The Dude to monitor every user and a custom-made web application to monitor traffic. Needless to say, we're starting to hit the limit and juggling between all these programs is a complete pain. Is there some kind of all-in-one solution that would allow us to eliminate all the copy and paste while keeping the same functionality?"

81 of 141 comments (clear)

  1. have fun waiting by Anonymous Coward · · Score: 1

    Not really. To have true management you need SNMP. Ubiquiti doesn't have a full snmp MIB, which is a pain. Great products, poor management capability.

  2. LAMP by Anonymous Coward · · Score: 5, Informative

    Just build yourself a LAMP setup, with workers feeding a database, and web GUI to access/update.
    Sync data from other sources into that, to provide a single converged view of whatever item (customer, router, location, network link...whatever). (Don't forget copious use of memcache btw)

    Trust me....this works really well and scales to millions of customers :-)

    1. Re:LAMP by Morpf · · Score: 4, Informative

      Or go LAPP and use PostgreSQL instead of MySQL. ;)
      But either way: Try to automate all recurring tasks, try to make all information necessary for one job visible from one spot.

    2. Re:LAMP by nastyphil · · Score: 1

      Just build yourself a LAMP setup, with workers feeding a database, and web GUI to access/update. Sync data from other sources into that, to provide a single converged view of whatever item (customer, router, location, network link...whatever). (Don't forget copious use of memcache btw)

      Trust me....this works really well and scales to millions of customers :-)

      Yes, like an MS Access database.

      --
      Dialectician. Archology.
    3. Re:LAMP by cerberusss · · Score: 1

      That sounds really easy until you calculate the time that goes into this setup. Assuming you have about 30-40 screens, 3 to 4 days work on each, you're talking about a pretty big project.

      --
      8 of 13 people found this answer helpful. Did you?
    4. Re:LAMP by m1ndcrash · · Score: 1

      I'm in exactly the same boat as OP. We're using a DB with a web-GUI as described above. All software is made in da'house.

    5. Re:LAMP by wer32r · · Score: 1
    6. Re:LAMP by Morpf · · Score: 1

      Okay, then LAPC(GI)? or LAPT(omcat)? ;)

    7. Re:LAMP by olau · · Score: 1

      30-40 screens? 3-4 days? For run-of-the-mill web + db stuff? I think you need something more light-weight, like Django or Ruby on Rails.

  3. Scripting and macros by fustakrakich · · Score: 2

    Doesn't anybody do that anymore?

    --
    “He’s not deformed, he’s just drunk!”
    1. Re:Scripting and macros by fuzzyfuzzyfungus · · Score: 2

      Doesn't anybody do that anymore?

      Rancid is arguably the contemporary equivalent. At the user end, you get all the convenience of revision control and versioning for your configurations; but the actual 'make-it-so' layer that turns the configuration you define into a properly configured device is handled in the background by a scripted process that logs in, makes config changes, collects data, and so on.

      It is mostly aimed at fancier switches, rather than cheapie endpoint devices; but adding device support through modules is doable and might be worth a look in this case(especially if the SNMP-foo of some of the devices is very weak, as a poster above claimed).

    2. Re:Scripting and macros by AK+Marc · · Score: 1

      No. They are delicate, time consuming, and waste bandwidth.

  4. Not cheap... by aleph · · Score: 2

    But you could look and see if Jet is within your budget.

    http://www.obsidian.com.au/products/jet/jet-isp-telco

    At the very least a base install will give you some billing software and hooks for other automation. It wouldn't hurt to drop them a line, at any rate.

    disclaimer: I used to work for obsidian ~6 years ago. they're a small company, but full of bright people and they have a lot of experience in the area. if jet isn't for you i have no doubts they can at least give you some honest advice on what to look at instead that's within your budget, fits your needs.

    1. Re:Not cheap... by viperidaenz · · Score: 2, Funny

      What a coincidence. They are currently using Jet

  5. Access? by NetNinja · · Score: 1

    Why are you using access?

    I suggest you get either MySQL or MSSQL to manage your contacts before you find yourself wishing you had put all that data on a real database. Oh wait you are starting to see that already.

    Solarwinds?
    What are you copying and pasting? You must be looking for some sort of CRM.
    http://www.insidecrm.com/articles/crm-blog/the-top-10-opensource-crm-solutions-53507/

    You say you are wroking for this small ISP? That means they are also paying you small. If they haven't figured out how they are going to support a larger customer base then leave before the ship sinks. Don't stay loyal to stupid people. The promise of stocks went out during the dot bomb era.

    1. Re:Access? by FaxeTheCat · · Score: 2

      Why are you using access?

      I suggest you get either MySQL or MSSQL to manage your contacts before you find yourself wishing you had put all that data on a real database.

      The problem with your suggestion (and you are not alone in this discussion) is comparing Access, which does both application development as well as a database back end, to a pure database back end. With MySQL or MSSQL you woiuld need to add an application development platform as well.

      As they already use access, it is pretty simple to move the back end to MSSQL if they need more scalability. The front end (application) can stay in Access.

  6. Do any of the tools on the cable TV work with HSI by Joe_Dragon · · Score: 1

    Do any of the tools on the cable TV work with the HSI system?

  7. Solving the right problem by Anonymous Coward · · Score: 2, Insightful

    So, you have an access database to track your Internet customers, and an Excel sheet tracking wireless customers.

    Why? How did this come into being? Who thought two different solutions to essentially the same issue were a good idea? Or did no one notice? Why haven't you consolidated these (preferably in the database? Did no one know how to make that work?

    I'm not trying to cast aspersions on the technical chops of people I've never met. Maybe there are really good reasons you have the solution you have. Maybe it was really the result of a series of "right decision at the time." But as an outsider, it certainly doesn't sound that way.

    I'm sure there are some suggestions that could be made to integrate your existing tools better. I'm sure there are off the shelf tools that you could use.

    What I'm worried about, however, is that the big problem is that have a technical capability problem, and you're trying to solve it as a tool problem. If that's not accurate, great. But I've seen company after company try to solve a "we don't have the tech skills" problem by finding "the magic tool" that will compensate. And I've rarely seen it end well.

    I realize this isn't directly a response to your question. Just a suggestion before that, before you start tinkering with zoomier tools, you take a hard look at who's going to install, configure, maintain, and administer the tool, and make sure you're confident they're up to the task. If not, solve that issue first. Tools won't fix it.

  8. Powercode by Anonymous Coward · · Score: 1

    Check out www.Powercode.com which is a per user per month software platform that does it all. A good free alternative is www.freeside.biz which can do it all as well but will require more effort on your part and comes with no bells and whistles.

    Pete

  9. Stackexchange network by Anonymous Coward · · Score: 1

    Stackexchange network is leaking...

  10. Might I suggest... by Svartalf · · Score: 2
    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    1. Re:Might I suggest... by kwerle · · Score: 2

      I went to their site, and I'm still left wondering: what problem[s] are they trying to solve? Why would I install OpenNMS? What does it enable me to do [more easily]?

    2. Re:Might I suggest... by kwerle · · Score: 1

      And yet, I was 100% successful in selling you on everything I intended to.

  11. There are commercial apps for this by laffer1 · · Score: 3, Informative

    There are commercial apps for ISPs to manage customers. When I worked for a dial-up/isdn/t1 service provide about 12 years ago, we used Platypus.

    We used it both for customer service / billing and technical support. It had a windows client and a web client and used Microsoft SQL server on the backend.

    Even a help desk software package could help. The great thing about Platypus is that it could handle all the credit card and billing stuff too. You might also look at HEAT or Remedy for just keeping a customer database and doing tech support.

    1. Re:There are commercial apps for this by ruir · · Score: 2

      The problem is not the billing or ticketing, plenty of things for that. The problem is LINKING your customer database to monitoring and provisioning automagically.

  12. Two words: by pigiron · · Score: 1

    relational database

    1. Re:Two words: by pigiron · · Score: 2

      Nonsense. It doesn't even meet Ted Codd's original 12 rules. Postgres is the open source choice although I must admit MSSQL is really easy to set up and use (and this is is coming from an M$ hater.)

    2. Re:Two words: by viperidaenz · · Score: 1

      Which of the 13 rules does Access not meet?

  13. ISP management by ruir · · Score: 4, Informative

    I was in your position some years ago. I also know that our main operator wasted millions in Incognito software just to throw it away, and ended up paying millions to Microsoft. Obvious not the average "small ISP", but I hope you get across my point. Small/medium ISPs end up writing their own custom software, because there is not a specialized/vertical package that works as it should. I ended up doing that too, and connecting my software to a in-house developed ERP package. Check my profile in linked.in. Regards, http://pt.linkedin.com/pub/rui-ribeiro/16/ab8/434/

    1. Re:ISP management by ruir · · Score: 1

      PHP my well be good for some of the frontend, specially if you are a SMALL ISP. however it is no good for the hard work. And mind you, there may be frontend solutions to administer some of this services, however they themselves do not and cannot run in PHP (although I honestly believe it is a typo of yours). Regards

  14. Depends on the scale by papasui · · Score: 2

    Depends on how big you guys really are, you say small but to me a small isp is less than 50k subscribers. If you're much smaller than this then you have more options. Anyway there aren't a lot of good drop in solutions for monitoring thousands of devices unless you're planning on spending a ton of money. Easiest way to roll a cable modem monitoring system (Note: I have personal experience doing this for ~5 million subscribers) is to build a database (MySQL/etc) and then create a collection script in perl/php/other scripting language that collects your cable modem ip addresses directly from the CMTS. Your script will log directly into the cmts execute 'show cable modem' or appropriate command for the platform your using and you will log all this information into your database. Your second script will use SNMP to collect statistics from those logged cable modem ip addresses. Things you'll want to collect would be the transmit, receive, downstream snr, upstream snr, interface statistics, etc. Once you have this information then you can put together a webpage that will present the data with nice graphs that give you a good idea of what's going on. This same script can act as a monitoring system to collect modem state changes or you can use a trap system like Nagios to just catch the alarms the CMTS can be configured to kick out. Good luck!

    1. Re:Depends on the scale by papasui · · Score: 1

      Forgot to mention. the goal with the collection scripts is to tie them to a cron job that runs like every 5-30 mins. This makes it all automatic and and as you add new subscribers the script then auto updates your information for you.

    2. Re:Depends on the scale by ruir · · Score: 1

      I write what you are describing for two ISPs with roughly 10,000 customers in the past. Of course you want to have a log of your modem signals to ascertain customers problems, and then, maybe a page where you input the MAC or name of customer, and you have got the current SNR whatever signals. You also want to collect netflow stats if you are billing bandwidth over usage. I wrote everything in C in the past, and someone wrote the PHP interface. In the last gig, I also wrote the web interface, the PHP interface was slow and cumbersome.

  15. Kind of depends what you're doing by Ritchie70 · · Score: 1

    I am not in the ISP business, but since you didn't tell us what you're using Access or Excel for, it's darn hard to tell you how to replace them.

    I would think that you would need billing, help desk, and network management products.

    --
    The preferred solution is to not have a problem.
  16. Re:Call the big guys. by Sir_Sri · · Score: 1

    Edit: Specifically, NDS (before being bought by cisco) had bought a company that specializes in just this sort of thing.

  17. Experience writing this exact thing by tokencode · · Score: 1

    I wrote a customer billing, administrative, ticketing and sales system for a small ISP (that ended up growing into a larger hosting company). The system integrated with the email server, RADIUS server, vendor ticketing systems a web portal for clients, had it's own inventory tracking system, IP allocation tool and managed the sales process from lead to quote to billable account. It is definitely doable to write your own but keep in mind that this does require some commitment of resources to not only write the software but maintain it in the future. If you want an integrated system, writing your own is the way to go and developing those systems while you are smaller is much easier. In general commercial ISP management systems are either too expensive, too rigid, or too fragmented.

    1. Re:Experience writing this exact thing by ruir · · Score: 1

      I wrote it too in the past. Add me in my linked.in if you would like to have my contact. http://pt.linkedin.com/pub/rui-ribeiro/16/ab8/434/

  18. Ubersmith by Thalagyrt · · Score: 2

    Take a look at Ubersmith. It's designed for quite a few use cases and is pretty much a complete CRM for ISPs/Telcos/Colo facilities/etc with integration into just about everything.

    --
    Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo!
    1. Re:Ubersmith by bastion_xx · · Score: 1

      Agreed. The interface is sometimes confusing, but the ability to pull in customer details and tie it to custom services shows off it's flexibility.

      Internap's cloud platform, from the Voxel purchase, uses it for current and upcoming services.

  19. Re:mysql,nagios,php,rancid etc. by M0j0_j0j0 · · Score: 3, Insightful

    Small ISP, and you dont even imagine the number of small mid companies governed on an excel sheet with the balance on cell A11 with green or red.

  20. Typical. by westlake · · Score: 5, Insightful

    "I work in a small ISP."

    This sums up the problems with most "Ask Slashdot" stories.

    This "small" ISP could have 50 clients or 15,000.

    There is no way to know.

    Budgets? Staffing? Your guess is as good as mine.

    1. Re:Typical. by monstza · · Score: 2

      Well, he said they are growing. So, who knows where they will be in 2 - 5 years. I am sure they don't and none of us have a crystal ball.

      The question should be, whats their strategy? you know.. the usual... where do you want to be in 5 years? how will you want to get there? and whats the catch?

      So, if the answer came back... " We want to be the largest ISP in the country. We are sitting on a pile of cash and plan to out spend everyone else. The problem is are as stupid as the stuff pigs play in". Then something expensive and well supported is probably the way to go.

      I think you guys get the idea...

    2. Re:Typical. by Luckyo · · Score: 1

      In a fairly stable market like specialty retail? Sure.

      In a volatile market with constantly changing legislation and a chance that a major player who can undercut you on price at loss until you go out of business will enter your particular area? Not so much.

  21. Maybe ispconfig can fill the bill... by Anonymous Coward · · Score: 1

    ISP management??

    Maybe you should try ISPCONFIG. (www.ispconfig.com). It's free, but the authors offers commercial support.

  22. Indeed by Anonymous Coward · · Score: 3, Informative

    Google is running hundreds of millions of customers on a MySQL Sharded Cluster. That means a hash function maps each email address onto one of 100 physical database servers. That means easy scaling.

  23. Experience of a "small" ISP by Wookie_CD · · Score: 1

    I work at a small ISP. We're a decade past your point, but our wired-building model means we're still sitting on less than 5000 customers. We run Ispconfig and use the commercial support while upgrading, that hosting server paid for itself many times over and continues to be great value to us. For network monitoring we started with mrtg on a solaris box, manually configured *shudder*. Since moving to JFFNMS we've been very happy with the network-monitoring side of things. I think you'd do well to follow other suggestions here looking for a suitable billing-system solution. Try not to focus on getting all these things in one, just make a internal webpage with links to all the respective systems.

    1. Re:Experience of a "small" ISP by therealobsideus · · Score: 1

      This.you don't need a one solution to all your issues, find solutions that improve each area and create an easy way to access those systems / pull data and aggregate it for your use. I come from Comcast (definitely not small) and they use so many different systems for network monitoring. Allot the data is pulled into a custom built solution for the tech support (grand slam previously, now moving to Einstein), BMW remedy for ticketing (grand slam and Einstein feed into this), custom comtrac and csg for billing (depending on east/west coast), And we at ne&to developed scout / scout flux for end of line performance metrics and to detect signal impairments.

    2. Re:Experience of a "small" ISP by Wookie_CD · · Score: 1

      Yep.

      Our internal administrative links page has eight section divs in two columns holding 60 links to a diverse range of destinations such as telephony servers, KVM's, powerboards, dozens of custom-written internal tools, server admin, KB's etc.

      It has grown naturally as we add capabilities & systems over time.

      btw if the above comment seems useful please upvote. seems like a downvote got me stuck in bad karma land for years :/

  24. Inomial's Smile by Virtual_Raider · · Score: 1

    Look into Inomial's Smile ( http://www.inomial.com/ We use it and it's better than Platypus somebody mentioned; might suit you.

    --
    +Raider of the lost BBS
  25. The Dude by isorox · · Score: 1

    The Dude is a great product, with 2 major shortcomings
    1) Runs on windows
    2) Has a terrible name when it comes to talking to senior managers about design decisions

    Does anyone know a comparable product that runs on something a little more "servery" (i.e. linux)?

    1. Re:The Dude by viperidaenz · · Score: 1

      Try The Dude

    2. Re:The Dude by Hognoxious · · Score: 1

      Has a terrible name when it comes to talking to senior managers about design decisions

      pronounce it "dooDAY" and tell them it's French for pineapple.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    3. Re:The Dude by ruir · · Score: 1

      do it right, and use NAGIOS...It is a pain in the ass in the beggining, however if you have minimum scripting ability and SNMP knowledge , you can virtually monitor everything.

    4. Re:The Dude by isorox · · Score: 1

      do it right, and use NAGIOS...It is a pain in the ass in the beggining, however if you have minimum scripting ability and SNMP knowledge , you can virtually monitor everything.

      I do, I have about 10k services on about 900 hosts in 20 countries monitored

      Doesn't give me a real time network graph though. I have command line snmp scripts showing bits/second which I can run against key troublespots, but a real time map of inter-site connections and exit points is a useful tool, especially as I want to add another 100 sites strung together by VPNs and occasional leased lines in a mesh

    5. Re:The Dude by ruir · · Score: 1

      If you are using Cisco, try nedi. We also connect NAGIOS to cacti here, and use the comments of NAGIOS to place the URL of cacti.

  26. Several options ... by theSatinKnight · · Score: 2

    Honestly, if you are already performing all these tasks manually and have a "working system", you would likely be better off completing your build with scripting to finish automating all the processes and completing central data storage in a database package.

    1) Enlarge your Access system to encompass all functionality. I've written deeper managed systems in Access (and some are still in use, LOL) which is fully capable of handling all the necessary tasks with appropriate scripting. But when you get larger ... Access may slow you down.

    2) Graduate to MSSQL and scripted applications moving your data. There are many different ways to approach this, of course, as virtually every application builder, language and script type speaks SQL in some fashion. But the concept of centralized data storage with scripts reaching in to accomplish tasks and interfaces allowing you to manually modify the data is hardly new. The advantage of MSSQL of course is that many users can access the data instead of a single workstation. Even if you "share" the DB file in Access you don't have a true multi-user system until you can all access it at one time and make concurrent changes (a good trick in Access, but normal in MSSQL).

    3) Super-Graduate to MySQL and port the entire operation to a free licensing envinroment (otherwise the same description as MSSQL! LOL). In addition to the free licensing, the programmers available in the Linux world are fairly plentiful and do not (as a rule) expect to get $30k for each application. Just remember: Don't send money to a company you cannot sue until after you have your product. Especially to a location where $500 is two year's Salary and the programmer would do better economically to disappear with that money than actually build the application! I like "one piece at a time" small script building solutions. It builds a relationship between developer and client while providing useful results with smaller amounts. And keeps the developer busy with lots of little clients (so no single client can "shut down" the developer ...very important these days when clients go *poof* easily).

    All the above are assuming that scripted systems can modify what needs to be modified when conditions change. Also all assume you have knowledge of at least one language or scripting language to make these changes. Generally this sort of thing is handled one item at a time, starting with the most "work-hours-intense" piece (to recoup those man-hours as quickly as possible). This is something most IT shops do for clients on a daily basis: Automation. The fact that you ARE an IT shop does not make you immune from the need to have automation! LOL

  27. Re:Ideco by skaag · · Score: 1

    Like most software and cars (Lada) coming from Russia, it looks like it was made sometime in the early 90's...

    --

    All those moments will be lost in time, like tears in rain... time... to... die...

  28. Re:wtf? by Anonymous Coward · · Score: 1

    MS SQL Express 2008/2010/2012 are much much better than Access.

  29. Did nobody mention Freeside? by Shaman · · Score: 2

    It may be more than you want... but check out Freeside.

    --
    ...Steve
  30. SugarCRM or X2Engine by skaag · · Score: 1

    You could use any of those two CRM's, with SugarCRM being more mature than X2Engine, as well as having a pretty good development studio built into the CRM. This allows you to create custom modules, with custom fields & forms. That's what you might use to manage equipment inventories for example.

    You can also use hooks in the code, to call various API's to provision services. For example if a customer is assigned a new product, you can hook that event to make something happen in the real world.

    If you don't have anyone skilled enough to do this, you can hire a developer to implement that for you. The advantage with this approach is that for very little money you will get a custom tailored solution. It will be so cheap that even if you throw the system away after 2 years, it's still worth it.

    And as an aside, I can hook you up with such a team if you can't find one of your own :-)

    --

    All those moments will be lost in time, like tears in rain... time... to... die...

  31. FreeSide by quist · · Score: 1

    Before our small ISP smalled-out, we were converting to FreeSide, a FOSSy sol'n, from WinNT-based Platypus. Had all the goods for user self-provisioning (RADIUS and such), billing, reporting; Nice perly hooks for places you needed a more custom fit.

    Might be worth a look-see...

    1. Re:FreeSide by quist · · Score: 1

      Yeah, it was a struggle to deploy, tho' not much worse than compiling your own KDE 2.x->3.0 days. :o
      Good ole Ivan. Guess he hasn't changed much ;-)

  32. Why are they using MS Project? by dutchwhizzman · · Score: 1

    Why are they using MS Project in other projects then?

    Seriously, just because you can manage a "ten item list" in an Excel sheet doesn't make it a proper tool for running a CRM with at least hundreds of users in it. If you want to use the CRM to manage modems, or at least IP traffic, you'll be looking at something special already. Managing services like e-mail, home pages and whatever else you choose to provide is is another thing.

    I've spent ten in the last fifteen years or so working for ISPs and I haven't seen one that didn't have to do a lot of custom coding done on their CRM. The amount of money made or lost on a customer was usually related to the effectiveness of the CRM in automating tasks and the amount of money they wanted to spend on advertising. ISPs that had to spend time on manually administrating users due to lack of features or robustness of their CRM tended to bloat out of control regarding the number of people required to keep things going. Once you get above a certain number, the amount of middle management, HRM and whatnot to keep them functioning made it unprofitable for the ISPs to keep their operation running. The ones that focused on making their people work more effective lost the battle, the ones that off-shored their people are losing as we speak and the ones that focused on tech solutions are still in the black, despite their competition throwing lots of shareholder money at advertising and stealing their customer with unprofitable propositions.

    Focusing on fixing this properly with tools that require as little as possible hands on is the thing to do here. Integration that means that you don't have to rewrite twenty applications if you add or change one proposition is crucial if you want to keep costs down and efficiency up. that saves you more money than having to fix something in a dozen places in a dozen languages and having no way to do a proper dev/test/accept/production environment will make changing propositions a nightmare. This will make you slow and expensive in a very competitive market.

    If you do it right the first time, you get less complaining customers, which means less time and money spent on the phone helping them. It means you'll get a better reputation, which means you'll have to spend less on advertisement and can get away with asking a buck more per month than your competitor, with your customers stating they'll happily pay more because your service is so good.

    Even though he'll most likely be trampled by some big ISP coming to his town some time in the future, the guy has a good point asking around for decent solutions. It's either that or go bankrupt from your own incompetence. All I can say is focus on your data model and make it extendable. Make sure that whatever proposition you're offering can keep on going next to new ones. Make sure that you can change taxes and fees with a starting date stamp and an ending date stamp somewhere in your database, so you can re-run billing runs and all that. Lots of ISPs I've seen didn't have this sort of functionality built in and were forced to change contracts with users, making them lose some of them, or had to run multiple instances of their CRM software because they couldn't adapt their software to a new law or proposition. To my knowledge, there is no ready made solution for this sort of thing, so pick best of breed tools for your management and ticketing systems and make sure you can glue them into your CRM in such a way that you can exchange them or add more tools without having to rewrite your core billing system. Once you have to rewrite your billing system or have to do manual stuff to keep everything in sync, you'll be looking at infinite monkeys on infinite typewriter style scenarios and those are lethal for lean-and-mean style ISPs.

    --
    I was promised a flying car. Where is my flying car?
  33. Bespoke by biodata · · Score: 1

    My opinion is that your requirements are unique, and any software package in existence will only do 80% of what you need. You have two choices - put together a couple of these 80% packages with some scripting glue, or write something bespoke from the bottom up. I would favour the former probably, since then when your programmer leaves you will have a better chance to get someone else who can easily find out how the whole thing works.

    --
    Korma: Good
    1. Re:Bespoke by TheBracket · · Score: 1

      I recently helped a small wireless ISP get started, and one of the first things we did was put together a management application. It's grown to be moderately large, but a lot of the functionality required can be constructed from various free sources. My client is chugging away nicely with a Java-based (server-side) system, although it could have been written in any one of a large number of languages - Java was convenient for the available skill-set in the company [never overlook the value of using an environment with which the customer is already skilled!]. The Seam+Hibernate stack provides a very quick development path for most of the CRUD [Create/Read/Update/Delete] functionality that forms the backbone of any data-driven app - but it could just as easily be Access, or (insert favorite ORM here). We found a few commercial systems that could do all of this, but they typically cost more than putting this together ourselves - however, that's partly a function of who you have available.

      The key to getting the project off the ground, in use, and genuinely useful was to identify the various areas that are essential - and automate them as building blocks within a framework. You're already used to Access+Excel+manual legwork, so you don't need to start with an amazing UI (although it is a good idea to come up with one that doesn't make the eyes bleed) - identify areas to automate (starting with the biggest pain points) and gradually reduce the pain as you can afford to do so. Also, don't be afraid to use various Free/Open Source packages to help out with sections!

      The important chunks for my client (and probably for other ISPs) were:
      * Customer database. This acts as the core for a lot of the rest of the system; database (and UI) for customers, their addresses and billing information, account history, etc. Includes tables linking to inventory to indicate what devices they have activated and the details (including billing plan, etc.)
      * Inventory system. Lists CPEs, with status, location, ownership info and history. Linked back to the customer database, to make it easy to say "Johnny has this CPE, on that plan". This ended up growing lots of historical options for reporting, but those aren't really essential.
      * Activation. This was the biggie for us. When a customer (optionally a new customer) is "activated" with a CPE/plan/etc. (a wizard helps you pick), it adds the appropriate history items and invokes scripts that setup the account in RADIUS and LDAP servers. This is the obvious place to include every step you need - but you can start as simple as "email tells you what to do" while you automate the steps.
      * Deactivation. Suspending customers (typically for non-payment), handling CPE returns, etc. You can probably live without this immediately, but it is really nice to have.
      * Billing. The first few iterations made CSV files for Quickbooks - that should be fine to get started. The most recent handles credit card payments, etc.

      There's also a lot of management niceties, and these were integrated back into the main portal for convenience:
      * Cacti for graphing various bits of the network, notably throughput and latency across the network. Very useful for planning.
      * Nagios for monitoring the network and paging us when something isn't responding.

      As it grows, you'll doubtless end up with a bunch of esoteric scripts also. We even have one that periodically uses an SSH session to log into various access points and records who is online in each sector, what their signal strength is like, and any de-registration events that have occurred. That highlights the biggest pitfall: it is really easy to get excited and try to program in the kitchen sink. If you don't focus on small/modular at the core, you'll end up with a mess - fast. We try to keep the core small, and then have the core UI link into various other tools as we create them.

      --
      Lead developer, http://wisptools.net
    2. Re:Bespoke by TheBracket · · Score: 1

      I missed "trouble tickets" - we ended up going with RT from Best Practical and linking into it. No need to reinvent the wheel.

      --
      Lead developer, http://wisptools.net
  34. Re:A Company Called "Accenture" by FaxeTheCat · · Score: 1

    And this screams: "Citation needed".

  35. Stop by Hognoxious · · Score: 1

    We have an Access database

    Wait, I think I see your problem.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  36. Re:Ideco by Hognoxious · · Score: 1

    i think it can be ruled out.

    Good idea, I wouldn't touch it with a borrowed bargepole.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  37. open-source solutions based on snmp:info by funkboy · · Score: 1

    It's not terribly clear what exactly you're trying to accomplish, but have a good look at NetDisco (designed for college campuses, mostly for tracking MAC addresses & the devices that know about them) and NetDot (designed more generically for wide-area networks but not so much for tracking end stations). They're both excellent pieces of software that keep track of everything on your network for you in a clean multivendor way. I particularly like NetDot as it has the much-sought-after feature of a plugin framework that generates config files for the other tools you already use. Think of it as sort of a control panel/dashboard for your network management apps & you start to get the idea.

  38. been there, doen that, NO.. by bigwavedave33 · · Score: 1

    Without the time and resources to do it right the answer is simply no. You would have to write it on your own. I owned and operated a small ISP with dialup, DSL, and 4 different flavors of wireless. there exisits no central management tool. You're best bet is to find a decent customer front end product for billing, ticketing, etc probably a commericail product would be best. Then use open source products to monitor your network(s). Either way you will have to do some glueing together of things as state above using the APIs and scripting. It can be done, but by the time you plan, write, and implement, your production network will have changed and so will your requirements.

    1. Re:been there, doen that, NO.. by ruir · · Score: 1

      I second this comment. Been there, done that. Dont try to write it in one go, try to devise a module/plug-in architecture, and write small modules as you need them (customer automation one module/modem stats another/DHCP bookkeeping another one...you get the gist). Divide it in projects, and write your modules over time as work load permits. Or hire someone.

  39. RPM Provisioning Management by jpd720 · · Score: 1

    I own a small provisioning company called RPM Provisioning Management (www.rpmcable.com) and offer DOCSIS and Wireless provisioning and monitoring software. I operate several very large wireless grids using StarOS and Mikrotik equipment. I don't have much experience with Canopy, but do have a lot of experience with Ubiquiti. We should be able to come up with an acceptable solution for you. Take a look at our site and shoot me an e-mail if you'd like some more information. Thanks and good luck!

  40. Platypus Recommendation: Avoid at all cost by Anonymous Coward · · Score: 1

    From my POV, Platypus was a never ending nightmare of various implementation and migration problems, a horrifying fat client, and a basically worthless web app. Hopefully it's better now, since they're still in business, but it's not something I would recommend except for avoidance.

  41. Bilt by blueapples · · Score: 1

    I suggest looking into the Bilt application: http://buildadatabaseapp.com/ It's a fairly easy to extend system built for creating adhoc shared database applications without having to write any code. You could use a bit of custom PHP on top of it to integrate into whatever public forms or whatever you need to pull data from. All your operators and employees would only need to interact with the UI provided by Bilt.

    --
    www.blueapples.org
  42. Re:A Company Called "Accenture" by AK+Marc · · Score: 1

    Yeah, ours had the bottom line in N25, not A11.

    And I worked for more than one multi-million dollar company that used Quicken or Quickbooks, which isn't much better than a spreadsheet.

  43. ISP management software by tetherow · · Score: 1

    Products that come to mind: platypus visp.net azotel freeside powercode billmax

  44. Re:Do any of the tools on the cable TV work with H by papasui · · Score: 1

    Yes and no. Cable TV (excluding the communication back to the headend for VOD or SDV) is one way. This means the traffic flows to your home. HSI is two-way communications (your both recieving and sending). So tools that can look at the downstream certainly apply to Video & HSI however return is pretty much exclusive to the HSI side.

  45. Wispmon by cscrum · · Score: 1

    Take a look at Wispmon. It does Wireless Customer Qualification, CRM, Provisioning with any equipment, workorders, trouble tickets, billing (recurring and usage based), and has mobile apps that provide utilities to your field techs. It was designed by a couple of guys who ran a WISP for 8 years to solve just the problem you are having. www.wispmon.com

    1. Re:Wispmon by cscrum · · Score: 1

      Also does high level network monitoring notifying you of outages via email and text message.

  46. outsourcing? by ruir · · Score: 1

    are you thinking of outsourcing the job?