COREY Kurt A <br /> From: COREY Kurt A <br /> Sent: Thursday, April 11, 2002 4:16 PM <br /> To: COREY Kurt A <br /> Subject: FW: Eugene/EWER coordniation meeting <br /> -----Original Message----- <br /> From: KOBLE Becky A <br /> Sent: Wednesday, April 10, 2002 4:49 PM <br /> To: DAVIS Lori M; SCHOENING Mark A; MCVEY Fred <br /> Cc: COREY Kurt A <br /> Subject: RE: Eugene/EWEB coordniation meeting <br /> Hi, guys! I wanted to touch base on some internal coordination issues related to our various levels of interaction with <br /> EWEB. As a framework for Mark, those levels are: <br /> • PW Coordination group -This is the group you all are referring to below, which meets directly with EWEB staff and <br /> works on in-the-trenches (so to speak!) issues, mostly related to capital projects and related coordination concerns; <br /> this group is coordinated and staffed by Public Works folks, although other departments are encouraged to attend, <br /> based on the agenda items proposed for a particular meeting. <br /> • EWER Advisory Group (EAG) -This is the internal interdepartmental group made up of one or more reps from each <br /> department which meets a couple of times a year to update Jim on significant issues, concerns and points of <br /> cooperation with EWEB, particularly issues with interdepartmental implications; this group is coordinated and staffed <br /> by Central Services folks (which, in recent years, has been me). <br /> • EWEB/City Staff Communications -This group (made up of Jim Carlson, Marty Douglass, Deb Brewer and either <br /> Mary Walston or myself) pre-processes issues which have "bubbled up" from either the EAG or the PW Coordination <br /> meetings and which are significant enough to be taken to a higher level of joint discussion. Sometimes these form <br /> the agenda for either Joint Exec or Joint Elected Officials meetings; sometime they result in direction to staff to solve <br /> a problem. <br /> • Joint Execs Meeting -These meetings between Randy Berggren and Jim Carlson take place about twice a year, <br /> depending on the number and urgency of the issues, which were probably pushed up to this level from some of the <br /> other meetings, above. <br /> • Annual EWEB Board/Council Work Sessions -These meetings are staffed by Central Services (last one was Feb. <br /> 25, 2002) and would address only-very high-level policy issues of concern to both organizations. <br /> <br /> Also, and I think you're aware of this, Jim Carlson (in his assistance city manager capacity) is our executive liaison to <br /> EWEB, so we want to keep him looped in on all major issues, regardless of the department that generates the issue. <br /> Last week Jim asked me to pull together the EAG (internal interdepartmental group) for an update of issues, so I'd begun <br /> looking at calendars and updating our latest issues list in preparation for doing that. That group's members overlaps the <br /> PW coordination group to some degree-but not exactly. For example, in the EAG, we have telecom, our gov'tl affairs <br /> manager (Mary Walston) and a whole lot fewer PW folks! So, I'm wondering if we can talk about how we coordinate the <br /> request for updates of issues, set the agenda for the PW coordination discussion, etc. without having City people feel like <br /> <br /> they are getting hit from two different sides with requests for issues. <br /> When I think back as to how Les and I used to do this, I recall that we generally tried to have the internal group meet first, <br /> then bundled some specific PW issues from that list and took it to the PW coordination meeting with EWEB staff. That <br /> way Jim knows what the discussion issues will be, even if he can't attend (which he already told me he probably won't go <br /> <br /> to your meeting). I hate to have you all delay your meeting until after the internal staff meeting, but I'd be interested in <br /> your ideas as to how we address the issue of avoiding duplication of work for city staff and achieving some coordination <br /> of effort here. Thanks for giving this some consideration, and I'd welcome your suggestions. <br /> Becky Koble <br /> <br /> x5036 <br /> 1 <br /> <br />