22
Customer Information Systems Albert Hankel, Wladimir Mufty 07 February 2013 Experience gained with SugarCRM & headlines new SURFnet CRM

Customer Information Systems

  • Upload
    forest

  • View
    24

  • Download
    0

Embed Size (px)

DESCRIPTION

Customer Information Systems. Experience gained with SugarCRM & headlines new SURFnet CRM . Albert Hankel , Wladimir Mufty 07 February 2013. Agenda 09:00 – 09:30 (CET). Customer Information Systems. Part 1: Current situation @SURFnet Part 2: Future situation @SURFnet - PowerPoint PPT Presentation

Citation preview

Page 1: Customer Information Systems

Customer Information Systems

Albert Hankel, Wladimir Mufty07 February 2013

Experience gained with SugarCRM & headlines new SURFnet CRM

Page 2: Customer Information Systems

Customer Information Systems

Agenda 09:00 – 09:30 (CET)

• Part 1: Current situation @SURFnet

• Part 2: Future situation @SURFnet

• Part 3: Discussion & Questions

Page 3: Customer Information Systems

Customer Information Systems

SugarCRM – Customer Information

• Contacts: Research & Education, vendors, partners, NREN’s

• 1000+ contacts and 3500+ contact persons.

• Basic setup and basic datamodel

• Front end + back end

• SOAP support

Page 4: Customer Information Systems

Customer Information Systems

SugarCRM – Datamodel

Connected Institutions Contacts SURFnet

Page 5: Customer Information Systems

Customer Information Systems

SugarCRM – User experiences

• Web based

• Complete content

• 1-many relations

• Main source system

• No batch export

• Customizing consequences

• No auto-complete or live search

Page 6: Customer Information Systems

Customer Information Systems

IDD – Institution Services Database

Page 7: Customer Information Systems

Customer Information Systems

SURFdashboard – Customer interface

url

Page 8: Customer Information Systems

Heading towards a new CRM

Page 9: Customer Information Systems

Customer Information Systems

Our current CRM

Page 10: Customer Information Systems

Customer Information Systems

Reasons for change

• Tangled entirety of systems- Hard to change anything without causing problems elsewhere- Diffuse responsibility of individual systems

(Law of the handicap of a head start)

• Our digital archive is getting outdated

• Towards more self-service: SURFdashboard SURFcockpit

Page 11: Customer Information Systems

Customer Information Systems

Goals

• Integrated support for customer relationship management

• Increase efficiency

• Flexibility in flow of digital documents

• Transparancy in system responsibility and minimized in-house maintainance

• Ready for future changes en developments

Page 12: Customer Information Systems

Customer Information Systems

Describing current situation

Toegewezencontact...

3.1 Informeren klant

Informerenklant

Klantgeïnforme...

Archiverengegevens

Telefoontje

E-mail

Brief

Page 13: Customer Information Systems

Customer Information Systems

Describing current situation

Toegewezencontact...

3.1 Informeren klant

Informerenklant

Klantgeïnforme...

Archiverengegevens

Telefoontje

E-mail

Brief

Toegewezencontact...

3.1 Informeren klant

Informerenklant

Klantgeïnforme...

Archiverengegevens

Telefoontje

E-mail

Brief

IST SOLL

Needs & Wishes

Page 14: Customer Information Systems

Customer Information Systems

Where do we want to be a year from now?

Phase 1 Analysis

Phase 2 Oriëntation

Phase 3 Realisation

Fase

Page 15: Customer Information Systems

Dreaming of perfect customer relationship

Page 16: Customer Information Systems

Customer Information Systems

Optimal self-service

Page 17: Customer Information Systems

Customer Information Systems

Complete and correct information

Page 18: Customer Information Systems

Customer Information Systems

Realtime synchonization of systems

Page 19: Customer Information Systems

Customer Information Systems

Tailored and pro-active communication (e.g. marketing)

Page 20: Customer Information Systems

Customer Information Systems

Behaving system users

Page 21: Customer Information Systems

Discussing the way forward(for us and perhaps for collaboration between NRENs)

Page 22: Customer Information Systems

Questions we could/should ask ourselves

- Is there any difference between NRENs in the way they manage their customer relationships?

- What are our implicit assumptions about the way things work?

- Who is the ‘Customer’ in CRM?

- What are the CRM boundaries?

- Are NRENs that special that off-the-shelf solutions don’t work for us?

- One big system vs (a modular set-up of) different systems?