You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Reviewing a Service for Consideration

When do we add a new service into the NET+ Cloud Services Portfolio?

  1. Is there an unmet need in the market today for a specific technology?
  2. Is there a challenge with an existing supplier (contract terms, business model, relationship) where there research and education community can work together?

Key Characteristics and Requirements for a NET+ Service:

  • Scale at least nationally
  • Meet unique R&E needs today and into the future
  • Delivered over global R&E networks
  • Adopt R&E federated identity standards
  • Commit to community Accessibility, Privacy, Security and other Compliance needs
  • Commit to sales practices and a business model that aligns with community expectations
  • Support a common, community contracting terms and conditions (negotiate once, use many times)

Candidate Services

Requirements of Service Providers

  • Service Provider Sponsor: Executive sponsor within sales and within product at the service provider 
  • Identified Sponsor: CIO or other senior executive from a member institution
  • Membership in Internet2 and InCommon Federation
  • Adoption of InCommon -Shibboleth/SAML2.0 and Connection of services to the R&E Network
  • Completion of the Higher Education Cloud Vendor Assessment Tool (HECVAT)
  • Commitment to:
    • A formal Service Evaluation with 5-7 member institutions
    • Enterprise wide offerings and best pricing at community scale
    • Establishing a service advisory board for each service offering
    • Community business terms (Internet2 NET+ Business and Customer agreements)
    • Support the community’s security, privacy, compliance and accessibility obligations
  • Willingness to work with the Internet2 community to customize services to meet the unique needs of education and research
  • No labels