Enterprise Systems Committee
Minutes of February 15, 1999 and Februrary 22, 1999
Present: Bob Sneed, Dennis Graham, Don Graham, Debbie McElroberts, Ed Masterson,
John Miller, George Johnson, George Wellman (on 2/15), Mike Biechler, Jeff Wright,
Bob Hannigan (on 2/22), Arno Rethans, Bev Taylor, Dan Crozier (on 2/15), Fred Ryan
(Chair)
Agenda:
1.
2.
3.
4.
5.
ClickNet (remote desktop diagnostic tools)
Year 2000 Issues
Oracle License & Costs
"Readiness" Plans
CMS/PeopleSoft Updates (Warehousing, CSU Priorities)
1. ClickNet (remote desktop diagnostic tools)
The ClickNet software will be used for analyzing desktop computers for year 2000
compliance. All desktops need to be examined very soon, so that departments can take
action to either fix or purchase new desktop computers as appropriate before January
2000. We are attempting to take into consideration confidentiality and privacy concerns.
It was recommended and agreed that Communications Services will discuss the process
in advance with offices having special confidentiality requirements such as Counseling,
Personnel, Student Records, Health Center. Y2K is the immediate issue, but ClickNet is a
step toward managing desktops as a University resource and thus more efficiently for
cost savings and better reliability. (LATER NOTE: For several technical reasons, most of
the work with ClickNet will not be done remotely, but done with technical staff working
on site in campus offices).
2. Year 2000 Issues




a Butte County Y2K Advisory Group has been set up including the County, City,
the University and other public agencies to try to work cooperatively on the issue.
the question of our January intersession was raised. It starts on January 3rd
immediately after the start of the year, and a small number of universities have
delayed or even cancelled their January classes. This item which would have
significant academic implications is brought up just for awareness, and we'll
return to this question at our next meeting.
we will need to assign certain staff to work the night of Dec.31st (a Friday) and
January 1st (a Saturday), and Mike B. was asked if we have any contractual or
legal issues here. Mike indicated that if advanced notice was given, we should be
able to work this out in a mutually satisfactory way with the affected staff.
the Y2K Committee will be asking everyone in the University to have all
equipment possible turned off over that weekend.
3. Oracle License & Costs
There has been a change in the Oracle licensing arrangement for the CSU, and Chico has
to decide if it will join the Systemwide contract. Chico and several other campuses have
not been part of the Systemwide license, but the contract situation may make it necessary
to re-evaluate our position, before the 2/28 deadline. This license fee covers essentially
unlimited database development, including Web development for Chico faculty, staff,
students, & prospective students, but does not cover further web development which
would require additional funds from the campuses in the future. The approximately
$299k license cost for Chico is payable by August 1, 1999. The reasons in favor of doing
this are:




costs more NOT to do it now
$115,000 cost avoidance on one-time license fees plus save approximately 50%
on annual support fees through February 2002
we have to do this at some point anyway for CMS (but delaying negates the cost
savings)
data warehouse functionality may be compromised if we don't proceed
After considerable discussion, the ESC recommended (5-2 in favor, 1 abstention) that we
proceed. (LATER NOTE: apparently all campuses with the possible exception of one
have also joined)
4. "Readiness" Plans
Our HR Readiness Group has been working and will be coming forward with information
within the next month or two outlining our readiness status and providing additional data
and background for our decision on what HR "Wave" we should be aiming toward.
5. CMS/PeopleSoft Updates (Warehousing, CSU Priorities)



discussions about a CSU collaborative warehousing project are continuing. The
thrust here is that even if CMS moves ahead smoothly, we will still have our
legacy systems for a number of years yet, and moreover, even when Peoplesoft is
implemented, there will be a need for warehousing. Eleven campuses plus the
Chancellor's Office have expressed interest in this development. Although the
plans are still tenuous, if this project does materialize, it's possible that within the
next 6 months it could be in operation.
there is considerable discussion Systemwide about the CSU technology
development path and so many irons in the fire at once. A major issue is the
scarcity of both technical staff and dollars to do both the network build-out
project and CMS.
some of the extensive real work of analysis and definition of next steps has begun
by the HR 1st Wave campuses, with a target date of December 1999 for a 1st
wave HR product. Minutes of meetings and a record of status of the various CMS
groups and committees is on the CMS web page. (LATER NOTE: Fred has a
number of documents outlining the process and the decisions made so far, which
will be shared with the ESC).
~ As before, in order to keep meetings to a minimum, the nest ESC meeting will be "on
call" and members are asked to keep free the Monday 11am time slot.