Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Service Manager9.52

Develop > Processes and Best Practices Guide > Change Management Workflows > Change Proposal (process ST 2.0)

Change Proposal (process ST 2.0)

Change proposals are submitted to change management before chartering new or changed services in order to ensure that potential conflicts for resources or other issues are identified. Authorization of the change proposal does not authorize implementation of the change but simply allows the service to be chartered so that service design activities can commence.

A change proposal is used to communicate a high-level description of a change. This change proposal is normally created by the service portfolio management process and is passed to change management for authorization. In some organizations, change proposals may be created by a programme management office or by individual projects.

The following figure depicts the Change Proposal workflow in Process Designer.

For details of the Change Proposal process, see the following figure and table.

Change Proposal (process ST 2.0)
Process ID	Procedure or Decision	Description	Role
ST 2.0.1	Register Change proposal	The change requester logs a change proposal with a high-level description of the proposed change.	Change Requester
ST 2.0.2	Records Change proposal details	The change owner records details of the change proposal. The change proposal should include the following items: A high-level description of the new, changed or retired service, including business outcomes to be supported, and utility and warranty to be provided A full business case including risks, issues and alternatives, as well as budget and financial expectations An outline schedule for design and implementation of the change	Change Requester
ST 2.0.3	Assess and evaluate proposed Change	The change owner assesses and evaluates the change proposal, including risks, issues and alternatives, as well as budget and financial expectations.	Change Owner
ST 2.0.4	Abandon?	The change owner decides whether to abandon the proposal or not.	Change Owner
ST 2.0.5	Authorize Change proposal	CAB reviews the change proposal and the current change schedule, identifies any potential conflicts or issues and responds to the change proposal by either authorizing it or documenting the issues that need to be resolved.	CAB
ST 2.0.6	Initiate a change or project	After the new or changed service is chartered, RFCs will be used in the normal way to request authorization for specific changes. These RFCs will be associated with the change proposal so that change management has a view of the overall strategic intent and can prioritize and review these RFCs appropriately.	Change Manager

Send Help Center feedback