Ideas

Proposed ideas for DC Wishlist:

Every DC does their own thing (portals, process etc.)
Impossible to automate
Tedious and labour intensive (manual auditing, checking of spreadsheets vs our data...)
Gaps in the process
- Not notified when a new crossconnect has been installed (Customer doesn't always tell us either)
- Allows customers to order the wrong thing (wrong port, wrong connector type...)
- If "A" end does not cancel the crossconnect, hard for us to know about/get DC to cancel it
Error-prone
"I hate it"

Can we develop a common API (similar to the IX-F API, or build on existing e.g. IX-API

Common method to access and understand your processes (and know when it changes!)
- "When I go to site, I can't get in because you changed the access procedure"
  - I didn't know that.
  - Procedure change was badly communicated:
    - You said: "Sign up to our shiny new portal! Yay!".... (whatever.)
    - You really meant: "You MUST sign up otherwise you won't be able to get in!"
Notifications of maintenance, outages etc.
- But only relevant ones!
- I don't care about routine maintenance (cleaning the floor, changing the lights in another room, toilets...)
- I DO care about work affecting our racks/outages (power, fibre, infrastructure etc.)
  - E.g. Power outage: Update affected customers quickly
Notifications from data centers are all horrible, messy, hard to read formats!
- Put the important detail at the top!
- A lot of "waffle" about escalation process, procedures, logos, pretty but useless html...
- The important detail buried at the end, tiny font.
- Comes from a ticket system I can't reply to
- Too many, and poorly targeted:
  - Sending automated invoices for "£0.00."
  - Don't send technical notices to our finance dept etc.
  - Sending everyone everything...

...