Data requirements for "What is our standards catalog?"

This business question helps to assess whether components are aligned with the standards catalog to support the company's IT capabilities.

MM_WhatIsOurStandardsCatalog

To have meaningful data for the business question What is our standards catalog?, you must capture the following information about the components and IT capabilities in your company.

Class	Attribute	Mandatory	Explanation
Component	Name	x	Necessary for the visualization.
	Version	x	Necessary for the visualization.
	Start Date		The start date is the date when the component is actively used.
	End Date		The end date is the date when the component is no longer actively used.
	Object State		Describes the operational status of the component and indicates whether it is actively used, planned to be used, or has been used in the past. Possible values are: Plan: The component is proposed to be used and still in the stages of planning and building. Active: The component is currently and used now. The active period begins with the component's start date and ends with the end date. Retired: The component is no longer used
	Strategic Component		Specifies whether the component is strategic.
	Support Model		The business support model for the component. Possible values are: In-House: Support is provided from within the enterprise. 3rd Party: Support is provided by an external vendor. Other: Support is managed through other channels. Unknown: Support model has not yet been assessed.
	Standardization	Required for business question	Specify whether the component is a standard component. This helps you to promote the use of standard components and reduce non-standard technologies. Possible values are: Not Classified: The component is not assigned to a standardization category. Free for User: The component may be used. Users do not need approval to use the component. Approval Required: The use of this component must be approved. Users should contact the authorized user or another person such as the IT Owner who has a role defined for the component to gain approval to use the component. authorized user An authorized user has primary responsibility to maintain the data for an object. Typically this is the user that has created the object. The authorized user as well as members of authorized user groups have write permissions to objects they are responsible for. role A role describes the functional relationship that a user or organization has for an object. Not Permitted: The component may not be used.
	IT Capability	x	A component is assigned to the IT capability it supports.
IT Capability	Level ID		The hierarchical number of the IT capability in the IT capability hierarchy. For example: 1, 1.1, 1.1.1, 1.2, 1.2.1, etc. Necessary for the visualization.
	Name	x	Necessary for the visualization.
	Parent IT Capability		The parent IT capability relationship is used to aggregate components assigned to a lower-level IT capability to the second-level IT capability in the IT capability hierarchy.

component

IT capability

authorized user

role