I get NOC'd down... ...but I get up again T owards excellent NOC - - PowerPoint PPT Presentation

i get noc d down
SMART_READER_LITE
LIVE PREVIEW

I get NOC'd down... ...but I get up again T owards excellent NOC - - PowerPoint PPT Presentation

I get NOC'd down... ...but I get up again T owards excellent NOC customer service even when things go wrong Gareth Eason (HEAnet) TF-NOC Meeting, Barcelona, 2 nd Sep 2010 Who am I? Gareth Eason Network Operations Manager, HEAnet


slide-1
SLIDE 1

...but I get up again T

  • wards excellent NOC customer service

even when things go wrong

Gareth Eason (HEAnet)

TF-NOC Meeting, Barcelona, 2nd Sep 2010

“I get NOC'd down...”

slide-2
SLIDE 2

Who am I?

  • Gareth Eason

­ Network Operations Manager, HEAnet

John Boland (CEO) Gareth Eason

(Network Operations Manager)

Brian Nisbet

(NOC Manager)

NOC (Virtual T eam) NetOps team

slide-3
SLIDE 3

Remember Copenhagen?

This is only presentation #1 (of at least 2) ... because this one has no answers,

  • nly questions...
slide-4
SLIDE 4

Barcelona

This is presentation #2 (of at least 2) ... where we realise there are no answers but there are some good ideas ...

slide-5
SLIDE 5

Overview

I want to change:

  • 1. how you think about your NOC
  • 2. how your NOC thinks about its customers
slide-6
SLIDE 6

Overview

  • TF­NOC Work item
  • Planning for failure
  • When a supplier's service fails
  • When a client's service fails
  • Lessons learned
slide-7
SLIDE 7

Overview

  • TF­NOC Work item
  • Planning for failure
  • When a supplier's service fails
  • When a client's service fails
  • Lessons learned
slide-8
SLIDE 8

TF-NOC: Work Items

  • NOC Users
  • Who are they?
  • Agreements
  • What agreements should exist?
  • What should they contain?
  • User Relations
  • How do they relate to a NOC?
  • Escalation & Priority
  • When? How? How do we ensure resolution?
slide-9
SLIDE 9

Overview

  • TF­NOC Work item
  • Planning for failure
  • When a supplier's service fails
  • When a client's service fails
  • Lessons learned
slide-10
SLIDE 10

“Expect success, but plan for failure” -- Unknown

slide-11
SLIDE 11

Who you gonna call?

  • NOC only gets called when a failure occurs.
  • Be proactive – avoid failures!

­ Resilient solutions ­ Monitoring and alerting ­ Alerting relevant to client

  • Consider alerting direct to the client

­ The NOC calls the client on detecting a problem ­ Web portal displaying monitoring for client

slide-12
SLIDE 12

Who you gonna call?

  • Make sure NOC is available

­ Designated call handler ­ Designated escalation paths ­ Consider a recorded message saying there is a problem

  • Make sure problem is resolved

­ Designated call handler ­ Designated problem handler

  • Make sure customer stays informed!
slide-13
SLIDE 13

Overview

  • TF­NOC Work item
  • Planning for failure
  • When a supplier's service fails
  • When a client's service fails
  • Lessons learned
slide-14
SLIDE 14

Failure of a supplier

  • Measure

­ how do we define (there is) a problem?

  • Inform

­ Make sure the supplier knows ­ Make sure the rest of your organisation knows

  • Plan to resolve

­ Agree what you want (from supplier)

  • Agree timeline and metrics

­ Agree how you will both know it's resolved

slide-15
SLIDE 15

Crisis Meeting

  • Second last resort
  • Collect data and metrics before the meeting
  • Invite account manager
  • Invite account manager's manager
  • Avoid covering old ground
  • Avoid assigning blame
  • ...
slide-16
SLIDE 16

Crisis Meeting

  • 1. Agree there is a problem
  • 2. Agree the scope of the problem
  • 3. Agree a resolution to the problem
  • Might be a resolution
  • Might be periodic updates if long­running problem
  • Define what you want to see from supplier
  • 4. Agree how you'll know the problem is resolved
  • 5. Agree the next meeting date
slide-17
SLIDE 17

Next steps

  • Supplier failure:

­ Escalate further (if useful) ­ Contractual penalties ­ Use alternate suppliers, if any

  • Last resort: Material breach of contract

­ Material breach of contract / cessation of contract ­ ...might mean procurement again. ­ Dependant on legal jurisdiction

slide-18
SLIDE 18

Overview

  • TF­NOC Work item
  • Planning for failure
  • When a supplier's service fails
  • When a client's service fails
  • Lessons learned
slide-19
SLIDE 19

Client Problem

  • 1. Understand their problem
  • 2. Triage
  • 3. Define action plan (with client)
  • 4. Implement Plan
  • 5. Report on success (or otherwise) of plan
  • 6. GOTO step 1.
slide-20
SLIDE 20

Understand their problem

  • Often biggest hurdle
  • Understand direct and indirect implications

­ Loss of revenue? ­ Loss of face? ­ Media? Press? Publicity?

  • Knowing your client well will help

­ You do have regular meetings with your clients, right?

  • Find out what the client is actually trying to do!
slide-21
SLIDE 21

Triage

  • Can we solve the whole problem?
  • Busy website

­ Are some parts of it busy? Can we isolate them? ­ Can we replicate the service

  • Loss of connectivity

­ Are there vital services for which a few 3G modems will do?

  • Figure out what the customer actually needs
slide-22
SLIDE 22

Action plan

  • 3 hour (emergency)
  • 24 hour
  • 3­day
  • 7­day
  • 1 month
  • 3 month
  • Long term (1 year, etc.)

Emergency Reactive Proactive Strategic

slide-23
SLIDE 23

Implement Plan

  • Put everything in place.
  • Monitor towards success criteria
slide-24
SLIDE 24

Report

  • Discuss measurements with client
  • Did things work as expected?
  • Were the success criteria met?
  • Were they the right success criteria?
  • Go back to step 1 : Understand their problem
slide-25
SLIDE 25

Business As Usual

  • Agree (with customer) criteria for returning to

Business As Usual

  • Learn from failure

­ Make the business as usual for NOC better business!

slide-26
SLIDE 26

Overview

  • TF­NOC Work item
  • Planning for failure
  • When a supplier's service fails
  • When a client's service fails
  • Lessons learned
slide-27
SLIDE 27

Understanding

  • Understand the problem

­ Educate suppliers about your pain points ­ Educate supplier on implications of problems (e.g. Delivering a router late means a client cannot register students at a new campus.) ­ Learn from customers – what are their pain points?

slide-28
SLIDE 28

Communication is key

  • Deal with the 'Mars' and 'Venus' compexes

­ Allow NOC to listen to problems – some customers just want to let you know. (Recorded message!) ­ Enable NOC to triage, work around and fix

  • Make sure communication doesn't slow down

fault resolution

­ Designated person on point for comms. ­ Designated person on point for escalations.

slide-29
SLIDE 29

Work around problems

  • Don't be afraid to work around problems

­ Root cause repair might not be quick enough ­ Understand the customer's view of the problem – maybe something less than a complete fix is good enough.

  • Agree and stick to action plans

­ Agree plan with customers ­ Ensure your NOC knows the plan. ­ Ensure your boss knows the plan!

slide-30
SLIDE 30

Don't fear change!

If the action plan is not working... ... CHANGE IT!

slide-31
SLIDE 31

Do one thing today to change how one customer thinks about your NOC in a positive way.