1. Partner licence renewal/New Partner
1.1. Inform patner of approach Dev/UAT/POC licences will be issued instead
1.1.1. Administration for VBP
1.1.1.1. Use VBP Licence Support Slots.
1.1.1.2. Pre Q2 2019 release
1.1.1.2.1. Default partner support Licence with 100,000 records , 2 users, 3 months
1.1.2. Administration of existing legacy systems
1.1.2.1. Check with BD - Volume and users allowed
1.1.2.1.1. Default partner support Licence with 100,000 records , 2 users, 3 Months
1.1.2.1.2. BD may request different config
1.1.3. Demo system needed
1.1.3.1. Progresses to UAT Issue short term one month max Third Party UAT licence But can be extended by BD
1.1.3.1.1. AWS demo systems available no partner licence issued
1.1.3.1.2. Progresses to Live Issue production Third Party licence Usual process.
2. POC/Client Demo
2.1. Timescale, Bundle and Volume agreed by BD. 1 month guideline
2.2. Must have "Named Client" and stays with licence ID.
2.3. Issue a new short term POC/Demo test licence
2.3.1. If access granted for clients POC EULA signed by client
2.3.2. VBP or Legacy Bureau third party only
2.3.2.1. Partner to configure available user functionality from those available in bundle choice
2.3.3. Goldvision Updated
2.3.3.1. BD - Record in GV against opportunity
2.3.3.2. Admin - Add to GV as POC licence zero value
2.3.4. Bing Keys May need to be charged to partner?
3. Partner dev new client system
3.1. Existing Legacy Bureau
3.1.1. Use bureau licence for development
3.1.1.1. Must have "Named Client" and stays with licence Recorded in GV against opportunity
3.2. VBP
3.2.1. Must have "Named Client" and stays with licence ID. Recorded in GV against opportunity
3.2.1.1. Issue new Dev Test Licence with Licence ID
3.2.1.1.1. Short term 1 month dev licence But can be extended by BD