How can we create IT projects across organizational groups that present a cohesive "One Stanford" view to our clients? What are the challenges and opportunities?
Biggest Challenge per Matt: Business models. It's hard to do business across organizations and the financial administration requirements make it almost prohibitive.
Can we find a way to create a pool of money/resources at a higher level to streamline this process?
Solicited feedback on adoption, features, improvements, etc for MDM:
- Difficulty even knowing who has mobile devices. Users are able to register via SNSR and we cannot determine who is affiliated with different departments. Can we have at least department identifiers in the future? This would also allow groups to go back to those who were not registered through SNSR, as well.
- Recommend installing iStanford by default. (A future function will be an application delivery mechanism that will allow for this.)
Administrative Systems (http://as.stanford.edu ) manages Authority Manager, PeopleSoft, ReportMart 1 and 3, StanfordWho, etc etc etc (many systems). Their systems support close to 5000 users.
Stanford Modern theme available for download. Also available for Drupal and Wordpress sites installed via the Collaboration Tools Installer, and Drupal sites on sites.stanford.edu
Latest releases are mobile-aware (stacking).
Stanford Basic available on sites.stanford.edu
3 new themes: Wilbur, Jordan, Branner. There will be a base theme (Drupal), of which these three will be child themes.
Would be useful to have a list of features that are themed with these styles (e.g., tabbed interfaces, search boxes, menu items). Code snippets as an extension of a style guide.
Looking for a communication platform to share what software needs are on campus as a tool to draw upon to build new software applications.
Suggestion: ConnectSU was developed for this kind of thing.
See website notes from Scotty Logan from ITS Open house Apr 2011
ConnectSU
www.slideshare.net/scottylogan/connectsu
Suggestions:
- test a prototype communication tool with both a control group of administrators and
NOTE: Please checkout the University Virtualization Users group mailing list: virtualization-users@mailman.stanford.edu
- What is available for the University now (from ITS)?
IT Services provides a central virtualization solution that currently is bundled with systems administration. The SLA for a VM would currently include systems administration.
http://itservices.stanford.edu/strategy/platforms/server-virtualization
User fillable - secure web forms with a complex process. Residential Assistant hiring process is the first one in the works.
Resjobs - pick students to work in the dorms. Resjobs is a type of workflow, so why not use the same workflow product. But sometimes, if the product is too complicated, it makes sense to split the products back into simple and complex products (so, that's still an option).
Fellowship Matching or Residential Matching is another one of the functions they are looking for.
Functionality Highlights
Roles and Permissions
Notes
Advantages to users:
- accessibility to users
- ability to tap a wide variety of resources
- time to completion is faster when you're using remote control
- instant help
Advantages for IT providers:
- platform to collaborate with other IT professionals
- ability to multitask (read email, etc.)
- integration with remote control technologies
- ability to service multiple customers
- logging of conversation
Disadvantages:
- Too easy for users to contact IT
- Complexity / cost to implement
Requirements / Concerns:
Copyright Stanford University. Stanford, California 94305.
