RFC Form Notes by Sandra Stevenson-Revill

RFC form should populate a calendar directly to avoid people requiring to manually update the maintenance calendar.

s_revill1 — 2015-04-22 22:10:05 UTC

automatically block out key University days when changes are not possible in a calendar

s_revill1 — 2015-04-22 22:10:37 UTC

Field to link to services affected - via service catalogue

s_revill1 — 2015-04-22 22:13:06 UTC

RFC form could do with ‘management description’ and ‘technical description’ boxes

s_revill1 — 2015-04-22 22:14:18 UTC

rfc form suitability

s_dashfield — 2015-04-27 11:46:58 UTC

is the "rfc form" appropriate for ALL chnages or are other change control processes permissable?

intergration with statuspage.io

2015-04-27 11:48:57 UTC

standard change register doesn't show all of the standard approved changes

2015-04-27 12:12:38 UTC

Should there be a different process to then submit subsequent standard rfc work

2015-04-27 12:13:46 UTC

RFC submitters should be more informed about when they can schedule in work. e.g. selection of a time and date which blocks out times for other pre-approved work

2015-04-27 12:15:38 UTC

Category of change - infrastructure/Application

2015-04-27 12:22:11 UTC

Its not have customers been communicated with, It's which customers have been involved in the planning

2015-04-27 12:31:06 UTC

mark change as completed

2015-04-27 12:39:57 UTC

No risk doesn't exist

2015-04-27 12:42:47 UTC

calendar view of upcoming changes

2015-04-27 12:54:57 UTC

Risk assessment matrix to decipher severity of change/risk

2015-04-27 13:05:22 UTC

Written in English

2015-04-27 13:06:38 UTC

Business/service knowledge vs technical detail

2015-04-27 13:07:59 UTC

By default there should be a description of high-level understanding of the change from a business/service point of view. Also there should be a separate box for technical detail to understand potential impact on other systems for example. CAB is a mix of mgmt & technical which is a good balance - both sets of information needed

2015-04-27 13:15:43 UTC

Capture dependencies of making the change

2015-04-27 13:16:51 UTC

Other team resources required? Need to capture who else will be needed to complete the change

ensure that all info recorded on ref form is available when the form is printed

j_eaglesfield1 — 2015-04-27 13:22:05 UTC

Can

2015-04-27 13:35:12 UTC

Can the approved and completed RFC

2015-04-27 13:35:16 UTC

Can the approved and completed RFC

2015-04-27 13:35:22 UTC

Can the approved and completed RFC filter data down to the service catalogue

2015-04-27 13:35:25 UTC

For example, an {New event} entry is created in the Service Catalogue for that service once a successful change has occurred - keeps an accessible history for the service

Can the approved and completed RFC filter data down to the service catalogue

2015-04-27 13:35:27 UTC

Can the approved and completed RFC filter data

2015-04-27 13:35:48 UTC

Can we have the ability to save an RFC form before submission

2015-04-28 10:40:44 UTC

This would give each team the ability to review the RFCs as a group before they are properly submitted