It will touch every single individual.
CMS includes integrated software applications that manage
data and communications for human resources, finance and student
systems. So faculty or staff members who look up student data,
anyone involved in hiring or maintaining attendance records
– be it student, staff or faculty members; anyone buying
supplies or performing accounting duties for departments –
all will be using CMS.
Every campus operates differently, but we all have common
functions that we perform. It is these common functions that
CMS will affect, and everyone on campus either performs tasks
involved in these functions or is affected by them.
We began the process with human
resources first and hope to “go live” in November
2005. We kick off the process of implementing the finance
section in November and expect to have it in wide-spread use
by July 2006. The last segment, student systems, will begin
in September 2005, with completion sometime in July 2008.
We established a campus steering
committee that will meet regularly to discuss issues, review
progress, provide resources and make decisions. In May, members
of the human resources project team began visiting campuses
similar in size and makeup to Fullerton. One of our visits
was to Cal State Northridge, where we became familiar with
some of the planning and issues they faced prior to implementing
all three modules in October 2003. We also visited San Francisco
State and Cal State San Marcos.
We looked at the strengths and weaknesses of each campus’s
efforts and have come up with ways we hope will make the process
go smoothly on our campus. One very important component is
to keep the campus informed of what is being done and how
individuals can be involved.
||How can members of the campus be included?
For starters, they can attend one of the
information forums we’re hosting about the project,
and its status – and we want colleagues to ask questions.
We want everyone to feel comfortable, to understand how this
will be a part of their lives. And we want feedback. We don’t
want to go into this in a vacuum – because it will never
work if that happens.
The first is slated Sept. 30 with others to follow throughout
October. We plan to have such forums every semester until
the project is completed.
In addition, we have a Web
site dedicated to providing information and updates on
We’re also organizing selected user work teams to
review application design and the reengineering of our business
process, as well as to test the system, identify issues and
suggest solutions before we move to broader implementation.
People in this group will be committed to the project for
about four hours each week.
We’re asking each division to name one or two staff
members – not managers – to be our testers. These
people will be the ones we go to consistently throughout the
process for their feedback. When we
visited the other campuses, one of the points we heard from
users is that they wished they had been consulted or had been
involved earlier. That’s why we’re organizing
these teams now – at the front end. We want their feedback.
Users will impact the design of new and reengineered processes.
Definitely – and we are
already planning a support system, like the Help Desk, that
will assist individuals using CMS. We’re trying to build
an infrastructure that answers all the questions that come
up – not just during implementation, but also for the