START Vision

Owned by Former user (Deleted)
Last updated: Feb 04, 2013 by AnonymousVersion comment
2 min read

START Vision Mtg - 1/10/13

  • "My Tech" area on ITS website - Bob and Wendy will shop to business managers.
  • Request / Order shopping cart to be on each Service page.
  • "My Preferences" section should include notification and delegates.

IAM-START Mtg - 1/29/13

  • 40% of billing is in Pinnacle
  • Long-term idea --> IAM (storage of access) access info to be displayed on ITS website via XML feed
  • Portal page on ITS website =  "My Access" or similar name
  • Risk: Current IAM projects to create new provisioning system, can we match schedules so that the new START functions will connect to new provisioning system instead of building with old provisioning system. June/July timeframe for bridges to new IAM.
  • NetID Pin set --> InfoSec should review the workflow (Matt Pretka was working on documenting the current process, now works in InfoSec
  • 1st target for IAM projects is to create an enterprise directory to replace current people lists

Notes from Josh

Current State

 
NetAdmin is the system of record for inbound requests for client accounts. Requests are logged in this system and the existence of an active net id for the individual verified. Via NetAadmin requests for Exchange E-Mail, Pantheon e-Mail, Tivoli Backup, PIN, Billing for Email and Tivoli are logged.
 
NetAdmin Issues

  • Limited integrated reporting
  • Multiple possible forms to request access
  • Request queues are managed per request format
  • Link to provisioning is manual
  • Multiple paths to provisioning the services supported by this tool
  • Not all provision-able services are handled by this tool

Future State

Enterprise Directory Service

  • Attribute and event driven directories used to support policy based decisions
  • Centralized management of Identity attribute data

Provisioning Engine

  • Monitored Events trigger automated provisioning
  • Website / SNow front ends self-service provisioning (service catalog based)
  • Role Based
  • Automate where possible
  • Approval-based Self-service
  • Log request in queue for manual execution where automation not yet available
  • Single/ same process and “forms” for new and change requests
  • Establish SLA

Expose Web Services

  • Directory and Provisioning available to current state and future state
  • Allows new technology and process to phase in and support decommission of legacy IAM in a decoupled manner