On Fri, 2007-03-09 at 14:01 +0100, [EMAIL PROTECTED] wrote: > Hi, > > Selon "Sullivan, John" <[EMAIL PROTECTED]>: > > > Bon jour. Pardonnez-moi que j'ecris anglais. Il et tres mellieux > > que ma Francais :( > > No problem. We could read english sometimes ;) > > (...) > > Our expertise is in telecommunications expense management for large > > (Fortune 1000) enterprises. We are a consulting and services firm > > and not a software development company. We commissioned a small > > development project to build a web based TEM application to handle > > our smaller clients. > > Sorry, i'm a little silly, could you explain what you mean by TEM > application ? > > (...) > > Would GLPI be interested in developing this project with us as part > > of GLPI? We would contribute the existing code base, our expertise as > > end users, our testing facilities, our client base as potential users > > and a small development budget. We do not have any developer > > resources to contribute. GLPI would take responsibility for > > maintaining the code and integrating it into GLPI. > > It's difficult to give you an answer now. It depends on the > fonctionnality of this application, the difficulty of integration, the > look and feel of the existing code etc... > > GLPI take already 300% of our human resources, it would be difficult to > take the responsibility to maintain and intégrating another module in > GLPI. But why not... > > Please give us (moyo or me) more information and we try to give you an > answer. > > Best regards, > > -- > Jean-Mathieu Doléans > www.glpi-project.org <snip> Thank you, Jean-Mathieu. TEM stands for Telecom Expense Management and is closely aligned with managing assets. For example, we would need to track circuits, contracts, carriers, contacts and phones -- most of which GLPI already does. Tracking the bills and call detail records are the parts we need to add.
For example, we need to associate billing information with a circuit along with any asset and contract information. This is an enormous amount of information as anyone who has had to wade through the mountains of monthly telecom bills of a large company would know. The billing then needs to be reconciled against contract to make sure the telco is not over or under billing. It is amazing how frequently telcos overbill by small amounts per unit that add up to very big amounts! An asset of type PBX would need to associate call detail records with it and correlate them to the billing for related contracts to produce a reconciliation report -- again very similar to the kind of value GLPI already provides to the CFO and accounting staff. I can quite understand the time demands of an open source project. I have the same difficulties with the ISCS project. We do have a small budget available if that would help someone spend additional time on integrating TEM into GLPI. We just don't have any developers :( What do you see as the next steps? Should we send you the code and a sample database? I look forward to hearing from you - John -- John A. Sullivan III Chief Technology Officer Atlas Group +1 207-985-7880 [EMAIL PROTECTED] _______________________________________________ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev
