Customer management and billing system

Objective: To design and implement a LAMP system to manage and bill customers and groups of customers for an existing telecom system. There are no other systems that need to be touched other than MySQL databases, so there is no telecom programming required. Background: Currently we operate a telecom system based on asterisk and MySQL. The operations takes all information from the database(operating database) and writes Call Detail Records(CDRs) and balance updates when each call ends. We need a system that will operate on a separate MySQL database to manage all of the customer information, such as names, addresses, billing information, Groups (or Agents) and balance data. The system also needs to be able to invoice customers and make the invoices available online when the customer or agent logs in to the system. The administrators should also be able to print invoices if we have to mail them out. The system should pull CDR data from the operating database to create the invoices, while marking the files as billed so as not to duplicate billing later. When payments or credits are made in the new system, there should be a balance update pushed to the operating database. ## Deliverables If required, I can move to a dedicated server if the shared environment does not work for some reason. Requirements: 1.? ? ? ? ? ? All operating data will reside on the Operational Database and all no Operational Data will be on the new platform so as not to have duplicate information. 2.? ? ? ? ? ? Very modular permissions structure is required through groups and directly on each user. We want to be able to show certain fields to some users and not to others. Some users will have access to modify information and others will not. A detailed list of items to be controlled will be generated when the project gets started. 3.? ? ? ? ? ? A credit card charging system needs to be integrated(information will be provided to connect to our bank system. Wachovia). Also Paypal payments will need to be integrated. 4.? ? ? ? ? ? A backup system will be needed to produce DB backups on a regular basis. 5.? ? ? ? ? ? The chosen partner will need to be available to work with us on an ongoing basis as this project will need to be modified a bit until we get the best setup for us. We will also want someone that can add features as we need them later. 6.? ? ? ? ? ? All code will be provided to us for modification later if the partner is not available. Comments: The biggest issue in this project will be to define all of the items that need to be done. It will be a fluid project even though it is a smaller one. I believe that this can be completed in less than 3 weeks by skilled programmers that are available to discuss changes with us as the project progresses. I will provide access to existing databases and all information to be tracked in the new one.