Page 2 of 2
Rev11, 2014-10-13
How can this change be reversed? If the change
cannot be reversed, provide a reason for a lack of
reversibility.
How will you know if the change is successfully
implemented?
At what point will a go/no-go decision be made to revert this
change?
How much time will verification take for this change? How
much time will it take to revert the change (if necessary)?
# of Business Processes Affected
# of IT workgroups/teams involved (including
vendors or contractors)
Serves 1 dept.,
optional to others
Serves multiple
organizations
11+, up to 10% of
campus users
More than 10% of
campus users
Number of External Users (Outward facing
applications and services)
11+, up to 10% of
campus users
More than 10% of
campus users
24 hrs/day, 7 days
per week
24 hrs/day, 7 days per
week, 4 hr. response
Experience Level of Technical Staff
Implementing Change
In-house expertise;
already in
widespread use
Familiar; already
in limited use
New to campus;
requires significant
changes
New to campus;
requires new business
process altogether
Low impact on
department, medium
impact on workgroup
Low impact on multiple
depts., medium impact on
department, high impact
on workgroup
Low impact on CSUCI or
beyond, medium impact on
multiple departments, high
impact on a department
Medium/High impact on
CSUCI or beyond, high
impact on multiple
depts.
Required for Project Risk Level
Risk Levels 4+ above; Or RFC with high security
implications
Risk Levels 4+ above; Or any pre-approved change
request
ROUTING:
Email T&C Administrator for approval.
Email Change Control Coordinator to schedule change, post to change calendar and notify CCB.
If change impacts Level 1 or Level 2 data, send copy to ISO.
Send copy to User Services Manager for campus global.
Email office coordinator to post service alerts to myCI.