Epiphany's data model and functional architecture
Platform: All | 2 Comments 10.08.2009 Sephane
Hi, I am looking for technical infos about Epiphany, particularly about the CRM processes Ep’s datamodel and about the CRM processes covered (particularly in SFA). I am in the telco industry and we are considering getting Comverse One, which CRM module is a verticalized white labelled version of Ep. Yet there are strong functional gaps so I’d like to see what Ep can offer besides to cover the gaps. Would anybody have a document about Ep’s functional architecture? Many thanks. Stephane
Hi there Stephane,
As Jason Balliet pointed out, there really aren’t too many resources that can definitively specify or point out the product components as it relates to the key process and problems it solves, moreover they are feature/function lists. As you might expect, at first glance, Epiphany, like all major CRMs have about the same feature/function list, so discerning between them probably requires further discussion with those that have implemented it and those that have used it.
In your case, depending on what your needs are – i.e. prepaid and/or post-paid, billing front-end or call center infrastructure or retail POS locations etc, probably shapes the questions to further delve into it’s suitability.
If these are the sorts of specifics you’re looking for, I’d be happy to field a call to help you in your discovery. I was the architect for a Telco that implemented Comverse Kenan FX Billing with Epiphany as the front-end to support 4 call-centers (each with 250+ agents) along with 110 retail locations and distributed enterprise sales teams. We integrated telephony switching products for call handling, routing and distribution etc. along with Redoing the whole order management piece to better suit to Kenan’s data model and ordering processes.
Let me know if you want to know more about our experience or if you have specific questions about your future needs etc.
jason@visualcube.com









Stephane,
This is a fairly broad topic and one of the reasons for this site was built is that documentation was not always as comprehensive as we would like. We (VisualCube) have been implementing this product for 6 years and I was once an employee of E.piphany when the product was developed. We have implemented a number of large projects over the years and we recently finished a large Telco in Asia last year, so we may be able to help. If there is something specific you need, please update a comment with a bit more specifics of the gaps you want to fill or we would be happy to engage your organization (if you would like) to give you the specifics of what EP can do for you.
Direct Email addresses : jb@visualcube.com and jason@visualcube.com
Let us know if we can help