Provisioning: Complexities

• Most Services require service specific provisioning information

  • User: social security number, Locations, frequent flyer numbers, meal preferences
  • Application: Mailbox size

• But constrained by company specific info

  • Jamcracker has locations &#-109;Cuper&#-108;, &#-109;phx&#-108;

• Intersection and union of constraints won&#-110;t just be &#-109;discovered&#-108;

  • Humans must determine and program the semantics

• Also: how does customer enter provisioning data?

  • Either lazy or eager data entry
    • Bulkload, email, web pages.

• Jamcracker has a Master Provisioning Schema

• And ecosystem of provisioning web services

  • No duplicate data entry, automated provisioning, user id mgmt