Regarding symmetrical or asymmetrical
I feel this information is non-proprietary so I will share where this all started with specifics.
Below is what was suggested initially by the team. You will see immediately that without a cross reference its difficult to know the purpose of the license bundle other than judging by the length of the name
One of the groupings has since been removed in the premium range but I forget which. (there are 5 total levels below, now only 4)
I've done my best to organise the appearance here to show where redundancy can be removed
My suggestion was to eliminate redundancy and simplify to the 3 categories
- Set type (2 types)
- Product Code (2 types)
- Features (4 types)
Entry UCC 3
Standard bundle
Premium bundle
Voicemail
vm to Email
cell Twinning
Next gen sip softphone
Pc softphone,
Micollab client
1 (MiNet phone)
2 (Generic SIP device)
[pre]
Bundle Name Product Code Features
EUSM1 VFB_Standard UCC3 license, MiNet phone, MiCollab Client
EUSM2 VFB_Standard UCC3 license, Generic SIP device, MiCollab Client
EUSVEM1 VFB_Standard UCC3 license, MiNet phone, VM, Vm to email, MiCollab Client
EUSVEM2 VFB_Standard UCC3 license, Generic SIP device, VM, Vm to email, MiCollab Client
EUPVETM1 VFB_Premium UCC3 license. MiNet Phone, EHDU, VM, Vm to Email, MiCollab Client
EUPVETM2 VFB_Premium UCC3 license. Generic SIP Device, EHDU, VM, Vm to Email, MiCollab Client
EUPVETNM1 VFB_Premium UCC3 license. MiNet Phone, EHDU, VM, Vm to Email, Next Gen Softphone, MiCollab Client
EUPVETNM2 VFB_Premium UCC3 license. Generic SIP Device, EHDU, VM, Vm to Email, Next Gen Softphone, MiCollab Client
EUPVETNPM1 VFB_Premium UCC3 license, MiNet Phone, EHDU, VM, VM to Email, Next Gen SIP softphone and PC softphone, MiCollab Client
EUPVETNPM2 VFB_Premium UCC3 license, Genric SIP Device, EHDU, VM, VM to Email, Next Gen SIP softphone and PC softphone, MiCollab Client
[/pre]
**********************************************
What's most important is that you realise ... There is no spoon.