Meeting - 2010-05-05 - Agenda and Notes

Owned by David Walker (Unlicensed)
Last updated: Aug 03, 2010Version comment
3 min read

Meeting - 2010-05-05 - Agenda and Notes

 AGENDA

From: David Walker <DHWalker@ucdavis.edu>
To: Kirk Alexander <kdalex@ucdavis.edu>, Thomas Amsler <tpamsler@ucdavis.edu>, Curtis Bray <clbray@ucdavis.edu>, Christopher Clements <clements@ucdavis.edu>, Brian Donnelly <bdonnelly@ucdavis.edu>, Linda Durst <ljdurst@ucdavis.edu>, Rodger Hess <rwhess@ucdavis.edu>, Deborah Lauriano <dalauriano@ucdavis.edu>, Robert Ono <raono@ucdavis.edu>, Jatinder Singh <jatsingh@ucdavis.edu>, Joshua Van Horn <jvanhorn@ucdavis.edu>
Cc: David H Walker <dhwalker@ucdavis.edu>, IETLC <iet-leadership@ucdavis.edu>
Subject: IET's new architecture / implementation coordination group
Date: Tue, 27 Apr 2010 16:45:04 -0700

Everyone,

As I believe you all are aware, the IETLC has decided to create a work group of IET's technology leaders to coordinate implementation strategies within a common architecture.  Your directors have designated you to represent their areas of IET, but we will be taking an IET-wide perspective on issues, educated by knowledge of your specific areas.

I am getting a wiki space an mail list set up for us.  In the mean time, I've posted a DRAFT description of the group at Home .  I'll move it to the new wiki space once it's set up.

I'll also ask to have one of the administrative assistants schedule our first meeting.  Here's a proposed agenda for that meeting:

  • Review the draft group description at Home  . We have been asked to finalize these document within our first couple of meetings for review and (hopefully) acceptance by the IETLC.
  • Discuss a work plan for the rest of 2010.  Is the initial activity the right one?  Should we start with something else?
  • Decide on a name for our group.  (You'll notice that I've called it different things in different places.)

Thanks to all of you for participating in this group; I'm looking forward to our first meeting.  If you have any questions before then, please give me a call or send mail.

David Walker
Campus IT Architect
Information and Educational Technology, Office of the Vice Provost
University of California, Davis
One Shields Avenue
Davis, CA 95616
(530) 752-9390
DHWalker@ucdavis.edu

MEETING NOTES


Attendees:  Kirk, Thomas, Curtis, Chris, Brian, Linda, Rodger, Deborah, Babette, Jatinder, Joshua and David


Comments from review of group description draft on the home page:

  • Confirmed existing bulleted list of points, focus of group is future direction, interoperability, implementation strategies rather than the specific of an implementation
  • Want to be a sounding board for options - bring ideas at the early, rough stages rather than waiting for a polished 200-45 like report
  • The initial focus of the group should be within IET.  Question of whether to bring in other IT organizations is outstanding however some project, like ID Management already are collaborative efforts.  Will address whether to bring in the Health System's and/or ARM's IT with its responsibility for core systems in the future.
  • Identified areas/actions that would be out-of-scope for this group:
    a) not replacing operational groups responsible for day-to-day issues or changes
    b) not replacing existing work groups (i.e. establishing software standards, researching tools, reporting), rather act in oversight capacity
    c) not replacing the need for regular collaboration meetings (i.e. the DC/NOC/Middleware)

Next steps:

  • Need to Inventory the IET projects/systems
    a) need to identify the existing/future dependencies
    b) check into the status of the Service Catalog project - can we use what has been developed rather than maintaining one ourselves
    c) Project Portfolio - need to also include projects that are in progress or coming
    d) are there projects that we are specifically not working on?
  • Need to identify what we want on the work plan:
    a) building up our own Service Catalog if existing system is unavailable
    b) when the campus/we discuss the Central Data Warehouse what do we mean, what exists and understand what is being done and why
    c) central "ticketing" system - promoting/identifying common tools in response to how our initial goals apply to applying the goals from our home page
    d) how do we structure upgrades, system changes.  Rather than identifying the specifics on an upgrade, work on the structure
    e) can we establish a systems-wide schedule, a common calendar (may want to overlay with critical business dates such as beginning/ending of terms, applicant process, year end)
    f) roadmap

Admin Notes :

  • No suggested group name changes
  • Membership was agreeable to meeting at the different offices: CR, DC, Chiles Rd where/when space is available
  • Next meeting should happen shortly (2-3 weeks) to capitalize on the momentum, fall back to monthly after established
  • Babette proposed reviewing the membership roster once our action steps have been identified to make sure we have the appropriate membership
    a) membership was identified by the directors so additional members should be approved by them
    b) ad-hoc attendees can be added to specific meetings as topics require
  • Wiki pages will be open, may develop high-level summary pages for management and more private "in progress" working pages for committee in the future