Please report any problems to the Shared Tools Team at st-help@doit.wisc.edu    Broken Links? Missing Macros? WIKI Retiring Plugins
Child pages
  • IT Assets Meeting 2018-06-07
Skip to end of metadata
Go to start of metadata

Thu, Jun 07, 2018, 12:30-1:30, Rm 2281 CS

This meeting was rescheduled to accommodate schedule conflicts.

Wiki page: https://wiki.doit.wisc.edu/confluence/display/POLICY/IT+Assets  
Box folder: https://uwmadison.box.com/v/Policy-IT-Assets  

_x_ Michael Block, _x_ Gary De Clute, _x_ J.J. Du Chateau, _x_ Lea Ericson, _x_ Rafi Lazimy, __ Kristen Mcroberts, _x_ Colleen Reilly, _x_ Bruce Riley, __ Tyler Schultz

Agenda

  1. Agenda Review / Previous Minutes

    Action
    • OK

  2. Review list of compliance areas
    Handout: List of compliance areas
      
    Action:
    • We discussed the list is considerable detail. Suggested one major change:
      • Split Cybersecurity and Privacy into three separate entries: Cybersecurity, Privacy, and Data Management.
      • Gary will modify the document accordingly, and will also add what unit or group, and what person ot title we might consult with regarding the language under each entry.
    • Conclusion we reach regarding how to use the list:
      • The main entries (at the top) are the items that we ask people to certify that they are compliant with
      • The other entries are things they should also be compliant with, if applicable, but we will not ask them to certify any of those.
    • Gary wll put the modified document on the private subfolder of the team's Box folder.
         
  3. Discuss implications to the team's organization and work. Considerations might include:
    1. Timeline: Can this be done this Summer, or is this a longer process that will extend into the Fall.
    2. Membership: Do we have the right mix of people? If not, what expertise do we need?
    3. Sponsorship: Is the PAT and PAT EC adequate sponsorship for an initiative of this scope and impact? If not, who should sponsor it?
        
    Action
    • Timeline: This initiative will need to continue into the Fall.
      • Gary will send an email give team members the opportunity to withdraw or suggest a replacement, because this exceeds the time committement that people agreed to when the team formed.
    • Membership:
      • See Timeline and Sponsorship.
    • Sponsorship:
      • PAT and PAT EC are not the right sponsors for the expanded effort envisioned by the team.
      • This will become a CIO office initiative. The team will need a charter. Rafi will follow up on that.
      • The PAT and PAT EC will continue to be involved regarding which IT policies are relevant to the acquiring IT assets.
          
  4. Outside work between now and next meeting.

    Action:
    • Gary wll put the modified document on the private subfolder of the team's Box folder.
    • The team can comment upon and edit this document.
    • J.J. Has some notes he will send to Gary
    • We decided to cancel the 6/20 meeting
    • The team plans to meet again on 7/11 (which is the last currently scheduled meeting)
    • We will scheduled more meetings as we learn more about future plans for the team.
         
  5. For next meeting on Jul 11.
    • Review draft charter
    • Continue discussing the list.

  6. Follow up
    • On June 15, we'll report progress to the PAT Exec Comm.
      • Rafi and Gary will both be there, and can make the report.
    • Further action TBD.

Ground Rules

  1. Everyone must be treated respectfully, whether present or not.
  2. Everyone present who wants to speak on a topic must have a chance to speak.
  3. Attend more often than not, and review materials when you can't attend.
  4. Don't be shy, or worry about perception of an idea - we need open borders for these discussions.
  5. Let's park side issues or extensive detail for future work by this team, or others.

Work Plan

  • Initiate Subcommittee. DONE.
  • April 3, Get organized. Have a common goal, and a process to get there. DONE.
  • April 18, Brainstorm DONE.
  • May 7, Create preliminary definition with information from brainstorm

    Deliver preliminary recommendations to PAT EC by May 11. (PAT EC meeting is May 18.)
     
  • May 23, Refine, as necessary. Result: Possibly changing the team's approach to the problem.
  • June 7, Consider if the new approach is way the team wants to proceed.
       
    Report the team's recommended approach to the PAT EC by Jun 13. (PAT EC meeting is June 15.)
        
  • Additional follow up TBD.

Future Meetings

Team Members

MemberUnitMemberUnitMemberUnit
Michael BlockL&SGary De CluteIT PolicyJ.J. Du ChateauDoIT Architecture
Lea EricksonAccounting ServicesRafi LazimyITC (faculty)Kristen McrobertsStudent Financial Services
Colleen RiellyDoIT PurchasingBruce RileyPuchasing ServicesTyler SchultzSMPH

Attachments

File Created Comment

Acquisition-Decision-Tree-2018-06-01.docx

Jun 01, 2018 16:17  

  • No labels