Wikihub has been upgraded. Please send an email to confluence-support@lists.berkeley.edu if you experience any issues.
Skip to end of metadata
Go to start of metadata

Agenda

Goals

  1. Identify initial service types to model
  2. Propose a data model for a commodity service – required and optional fields
  3. Identify risks associated with community sourced model of these data elements
  4. Identify data sources that will migrate data

Service Types

  • Professional
  • Commodity
  • Web-based Services for Developers

Feedback

Additional potential types to research and assess

  • Applications
  • Software available to download as opposed to procure
  • Common good

Example - Virtual Private Servers Mock Up

  • VPS service was mocked up, see here
  • This mock up consolidate a majority of the information from two data sources: the IST web site and the knowledge base FAQs related to this service.
  • The sponsor has communicated his intent on streamlining the IST web presence and migrating much of the service information that exists at ist.berkeley.edu over to the TSR.

Identify data elements for an IST commodity service

The following data elements were identified as being possible subheading candidates for a TSR contribution of a commodity service.

Definitional Data Elements

  • Product Name
  • Home Page
  • Short Description – 1 sentence
  • Long Description – paragraph
  • Tags
  • Intent
  • Audience
  • Version
  • Restrictions
  • Client OS's supported
  • Provider
  • Pricing, link or listed
  • Service Window
  • Lifecycle
  • License, if applicable
  • Contact Info
  • Service Catalog link
  • SLA
  • Departmental Use
    • We use this product
    • We don't use this product
  • News
    • iNews
    • Other Posts

Exercise and Feedback

The group was divided and asked to identify which of these data elements should be required of IST Commodity Service. It is assumed that a non-IST technology will be allowed to be contributed with minimal data; e.g. name, description and homepage. This exercise was intended to define the data model for IST services that will be migrated to the TSR.

While completing this exercise, it was noted that where these data elements help describe an individual service, they do not incorporate certain information that help customers decide among similar service options, such as Database Services pages entitled: Selecting your database platform.

Proposed Required Data Elements for IST Commodity Services

  • Product name
  • Provider name (i.e. IST)
  • Short description (one sentence)
  • Long description (either text or link)
  • Contact Information
    It was noted that there are multiple types of contact information and that we need to decide which kinds of contact information we will require displaying.
    • for questions about the service – should this be folded into FAQ?
    • for support
    • for procurement
  • Restrictions (alternate name: Limits)
  • Pricing (either text or link)
  • Audience
  • Tags
  • SLA (either text or link)
  • License
    • debated
    • most likely required when applicable

Proposed Optional Data Elements for IST Commodity Services

  • Home page
    From how this is being described, it assumes that this entry will become the home page.
  • Intent
    It was felt that with both a long description and an audience element, the intent should reveal itself.
  • Service Catalog link
  • Security restrictions, i.e. protected data
  • News
    • I-News
    • Other
  • Client OS's supported
  • Departmental use of a product
  • Accessibility
  • Campus contract exists

Risks associated with a fully community-sourced model around the proposed data elements


Note: I rephrased many of the concerns we documented as risks to help us better assess their impact and how to mitigate these.

Risk

Impact of risk

Mitigation Options

Service provider teams might get consistently pushed beyond capacity with an additional set of items/notifications to watch re: data changes on the TSR related to their services

1) Low morale
2) Negative customer interaction

 

IST Service provider teams might be pushed beyond capacity during migration of information from existing locations to the TSR for a period of time

 

 

A customer or service provider might not be able to find data while migrating information from existing locations to the TSR

 

 

A customer might get inaccurate data related to a services for a period of time b/c of inaccurate entry by a contributor

 

 

A service provider might lose control of their service data for a period of time b/c of a malicious contributor

 

 

A customer might get bad pricing information for a period of time b/c of inaccurate entry by a contributor

 

 

Service provider might not provide regular updates to their pages

 

 

The campus community may not adopt the TSR

 

1) Identify a functional and operational owner
2) Develop a communication and community organization plan