Use of Non-UW-Madison Applications and Services
Was: Third Party Applications, then Cloud Computing (Cloud)
Current guidelines are at http://www.cio.wisc.edu/policies and include:
- Guidelines for Use of Non-UW-Madison Applications and Service for Instruction
- Guidelines for Use of Non-UW-Madison Applications and Service for Research
The Use of Non-UW-Madison Applications and Services (TPA) initiative, (variously named "Use of Third-party Apps" and "Use of Cloud Computing",) addresses intellectual property, privacy and security issues that arise when university units use tools offered by web service providers (such as Google Apps.)
The Personally Owned Devices policy stakeholder team is currently addressing issues related to non-UW-Madison applications and services. (Even though the technologies are very different, the underlying privacy and security issues are similar.)
To comment on draft documents or any other aspect of IT policy, please add your comments at the bottom of the page in question. Comments are welcome on any document at any time. Formal review is a publicized period of time where comments are proactively invited.
Current Process Step
Vetting of draft gudelines. OK?
|Currently at IT policy process step 4. Drafting. |
Documents are drafted in consultation with the sponsors, stakeholders, and the community.
|10/04/12||Merged history of Guidelines for Use of non-UW-Madison Applications and Services into nUWGuidance. For history see: nUWGuidance#nUWGuidance-History.|
POD Meeting 2010-09-30. Hideko Mills visits POD team to discuss Mobile Devices Initiative and relationship with Personally Owned Devices initiative. Mobile Apps Initiative is about device type independent of ownership. Personally Owned Devices is about the ownership independent of the device type. Much overlap, however, since many personally owned devices are mobile, and that is likely to increase. Same underlying privacy and security issues.
First draft of CommonServices document (list of UW and non-UW apps and services.)
POD Meeting 2010-04-29. Among other things of more substance but less amusement, the "POD" and "Personally Owned Devices" names have "stuck" in our local nomenclature. Changing the name is more trouble than it is worth. Keep same name but note the expanded scope as needed. (So it goes when working on the leading edge of terminology.)
Campus reaches an agreement on Google Apps, and begins managing the wisc.edu domain.
Policy Planning Team (PPT) suggests that the Personally Owned Devices (POD) team can address issues of immediate concern during FY 2010/2011 regarding Use of Non-UW-Madison Applications and Services. This is because the primary recommendation of the POD team is equally applicable to personally owned devices and non-UW-Madison appliations and services. (Note: it becomes increasingly clear that the POD initiative needs a new name to more accurately describe the expanded scope.)
Continued behind-the-scenes activity negotiating contracts for non-UW-Madison applications and services.
It is noted that we should (eventually) have Guidelines for Use of Non-UW-Madison Applications and Services for Administration. These would not differ substantially from the previous guidelines, but would reorganize the material to highlight the administration-specific issues.
POD Meeting 2009-11-20. POD Team immediately realizes that the same privacy and security principles apply to non-UW-Madison applications and services. Thereafter, much activity of the team is applicable to both.
Behing-the-scenes activity researching the issues and negotiating contracts for non-UW-Madison applications and services.
Requested input from TP-Prime list on draft Guidelines for Use of Non-UW-Madison Applications and Services. This name replaces "third party apps" and "cloud computing".