Standard Change Suggestions

[rmcb]

This organization is just discovering the advantages of having standard changes.  Could anyone provide some examples of the standard changes they've set up at their site?

[Dr Atul - LNG]

Hi @rmcb 

Standard changes are pre-approved and low-risk changes benefits

- Can be deployed at any time

- No approval required.

- A standard process

- Only raised via dedicated and approved templates

- No Risk assessment

What we used at our client side

- For Weekly Server Reboot

- For monthly patch installations

- For Service Account Creation and here are few OOTB

• Building power shutdowns
• Bulk data load for a specific application
• New instance of a database
• New application hosting environment of a standard configuration
• Application monthly/quarterly releases
• Restoring of an environment or database for developers
• Firewall changes 

[rmcb]

I'm so glad you replied.  That was helpful, indeed.  Also, it brings up the subject of server reboots.  I was wondering if a reboot really qualifies as a "change" since there's not a change in the component itself, once it has rebooted.  It seems like it would be more of a task, but I don't know how that would be recorded and mapped to a CI in ITSM.  Maybe there's a maintenance component of SNOW that we don't have.

[Dr Atul - LNG]

Hi @rmcb 

Yes and No both, reboot is standard change if you are doing in a regular basis. Sometimes clients don't want reboot as standard change , so it depend if by previous changes you prove that reboot can be done without issue and convert this to standard change. and its not SNOW, its SN or ServiceNow.

[Uncle Rob]

There's a whole bunch of them already articulated OOB is there not?
Maybe that's just my PDI with demo data