Contracting for non-UW-Madison Applications and Services (Cloud Contracting)
Contracting for Non-UW-Madison Applications and Services (Cloud Contracting) seeks to adapt or define processes to identify, select, negotiate, communicate and review contracts for non-UW-Madison applications and services (a.k.a. cloud computing.)
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.
Need to evaluate how this fits in with the IT Strategic Plan, Administrative Excellence and Internet II Net+. Continue monitoring projects that are modeling a deliberate process for pre-purchasing discussion. For example: the "Email, Calendar and Chat" project (ECC) is following a process that could serve as a prototype for pre-purchasing engagement with stakeholders.
Created initiative pages on wiki.
Previous POD Activity:
POD/Cloud Meeting . Review results of discussion at the Aug IT Policy Forum, Discuss membership of implementation teams. This is the last planned meeting of the current POD/Cloud team. Implementation teams will be organized.
IT Policy Forum . Includes POD/Cloud implementation discussion groups.
POD/Cloud Meeting Special meeting to prepare for IT policy forum discussion.
POD/Cloud Meeting . Reviewed draft of revised POD recommendations. Created a list of possible implementation teams.
POD/Cloud Meeting . Reviewed draft executive summary of revised POD recommendations.
POD Meeting . Discussed revision of POD recommendations.
POD Meeting . Discussed electonic records and mobile apps.
Meeting with APR Tools leadership . Discussed mobile and personally owned devices and apps.
Follow up meeting with Mobile Apps subcommittee.
POD Meeting. Meeting with CIO.
Meeting the Mobile Apps subcommittee.
POD Meeting. Planned next steps. (Lots of possible contacts with other teams and initiatives.
POD Meeting. 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. Discussed possible event to be held in November.
Meeting with OCIS to discuss the initiative and current recommendations. Identified that access to POD's is necessary in order to investigate possible security incidents.
POD Meeting with CIO . Discuss recommendations. Next steps.
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.)
POD Meeting. Preparation for meeting with the CIO and preparation for the forum.
Deadline for changes by team. Final version to be submitted to the CIO on April 9.
POD Meeting. Final review of recommendations.
Team deadline for edits to be included in "final draft".
POD Meeting. Review recommendations. Next steps.
POD Meeting. Review recommendations.
Original version of POD Recommendations.
Updated POD Charter.and
Invited additional members of PPT to participate. (One more volunteered.)
Invited additional members of UW-MIST to particate in the Policy Stakeholders Team. (Two more volunteered.)
Invited several people to participate in a meeting to discuss scope.
Decided that a pre-charter meeting to discuss scope was needed.
Scheduled Initiation of POD in September. Need to form a .
PPT Meeting. The policy statement might be included in IRM. Next steps: Wait until it becomes more apparent whether or not IRM will include a POD policy statement. Procedures, guidelines or standards could be developed independently.
Included this initiative in the list of possible new initiatives. This policy was proposed after the the IT Policy Plan was developed and approved. (The plan anticipates that other possible initiatives might be identified during the fiscal year.)