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 Management2017.11

Develop > Processes and Best Practices Guide > Configuration Management Workflows > Configuration Identification (process ST 3.2)

Configuration Identification (process ST 3.2)

In the Configuration Identification process, the Configuration Administrator selects Configuration Items (CIs), records their identifying characteristics, and assigns unique identifiers to the selected items. This process helps to ensure efficient data storage and retrieval.

Configuration Identification process is enables you to do the following:

Identify and register CIs
Assign unique labels
Record relationship information

Configuration Identification is responsible for collecting information about CIs and their relationships, and for loading this information into Configuration Management. Configuration Identification is also responsible for labeling the CIs, which enables the corresponding configuration records to be found.

Details for this process can be seen in the following figure and table.

The Configuration Identification workflow is illustrated in the following figure:

Configuration Identification process
Process ID	Procedure or Decision	Description	Role
ST 3.2.1	Validate task for CI creation	The Configuration Administrator reviews the task to verify that all required information to create a new configuration item is complete and correct. Configuration describes a group of CIs that work together to deliver an IT Service, or a recognizable part of an IT Service. The term configuration can also refer to the parameter settings for one or more CIs.	Configuration Administrator
ST 3.2.2	Information correct and complete?	If the information is correct and complete, continue with ST 3.2.3. If not, go to ST 3.2.15 (reject task).	Configuration Administrator
ST 3.2.3	Determine CI type(s) of configuration	Determine the CI type(s) needed to register the CIs. A CI type is used as a template to document the CI, including, attributes and required fields.	Configuration Administrator
ST 3.2.4	Appropriate CI type(s) exist?	A CI can only be registered if the CI type is known and a Configuration Management policy is available for these types. Existing types must match the attributes that need to be managed and allow designation of a person who is responsible for maintaining the CI. CIs of a registered type can be used as templates for new CIs. If there are existing CI types, continue with ST 3.2.5. If not, go to ST 3.2.11.	Configuration Administrator
ST 3.2.5	Existing reference data?	Verify that the reference data (the product definition from the manufacturer or supplier) for the configuration exist. If there is no reference data, go to ST 3.2.6. If yes, continue with ST 3.2.7.	Configuration Administrator
ST 3.2.6	Create new reference data	Create a reference data.	Configuration Administrator
ST 3.2.7	Create new CI	Create the CIs part of the configuration. One or more CIs can be created. Select the CI type (template). Select the model.	Configuration Administrator
ST 3.2.8	Populate configuration details	Enter the required CI attributes, according to the Configuration Management policies. Capture relationships and dependencies between the CIs. Depending upon the CI type and business rules, examples of details include: Serial number location (for example, on stock) Purchase order number Receipt date warranty conditions and warranty end date CI specific attributes	Configuration Administrator
ST 3.2.9	Register ownership and support groups	All CIs must be assigned to an owner (that is, a reference to an organizational entity such as a cost center) and an administrator (the group responsible for managing the CI during its life cycle). Activities include: Assign owner Assign Configuration Administrator (group) Assign support group for incident assignment (for example, if needed for automated assignment in case of events detected on the device)	Configuration Administrator
ST 3.2.10	Relate to contract?	Determine related contracts for the components, such as: Maintenance or support contracts Financial contracts (for example, lease or rental) License contract or service contracts (for example, SLA, UC, and OLA) If no contracts are relevant for this Configuration, go to ST 3.2.12. If yes, continue with ST 3.2.11 to link the items to the contract.	Configuration Administrator
ST 3.2.11	Match and relate to contract(s)	Link the CIs to one or more contracts. Capture the inclusion date of the CI to the contract. If needed, inform the Contract Manager of the new items attached to the contract.	Configuration Administrator
ST 3.2.12	Labeling of CI required?	Determine whether CIs need to be labeled according to the Configuration Management policies. If not, go to ST 3.2.14. If yes, continue with ST 3.2.13.	Configuration Administrator
ST 3.2.13	Create and attach label	Create and print a label. Physically attach the label to the CI.	Configuration Administrator
ST 3.2.14	Close Configuration Management task	After completion, the task can be closed. Update closure code.	Configuration Administrator
ST 3.2.15	Reject task	If the task cannot be completed, reject the task. Update the task with reasons and details of any issues found.	Configuration Administrator
ST 3.2.16	Assess reason for rejection	The Change Coordinator assesses the reason for the rejection.	Change Coordinator
ST 3.2.17	Gather and document required details	The Change Coordinator documents the details related to the rejected task.	Change Coordinator

Send Help Center feedback