Microsoft Technology Licensing, LLC

Nigel Graham Cain

Andrea Westerinen

Giedrius Zizys

Thomas Keane

Bahadir Baris Onalan

Marisol Ontaneda

Thomas N Martino

Ashvinkumar J Sanghvi

Anders Bertil Vinberg

Vij Rajarajan

Adam Herscher

Ashvin Sanghvi

Kenneth Van Hyning

Dileep R Kumar

Anthony Baron

R Syam Kumar

Pritam K Sharma

Andrew Timothy Hopper

Andy Hopper

Dileep R P Kumar

Andrea Rose Westerinen

A change management system may use a phased status indicator that may illustrate several phases of a change request and a current status for each phase of a change management lifecycle. Additionally, a group of change requests may be displayed in a linked manner showing various relationships between change requests. The status indicator and linked display may be used together or separately to illustrate the status of various change requests and within interactive displays of change request data.

Visualizers for change management system

Defining target data types within an instance of a target data type definition for inclusion in a reference data type definition to declare expected entity relationships in a model. The model corresponds to, for example, software, a business process, or an organizational structure. The target data type defines one or more elements with target data. The target data describes entities that are expected to be related to the reference entity according to a predefined entity relationship. The existing reference data type definition is used to declare the expected entity relationships. In an embodiment, the defined target data type includes a tag in an eXtensible Markup Language (XML) document.

Describing expected entity relationships in a model

A change management system for managing configurable devices such as computer systems uses a set of rules for validating change requests, linking change requests, and determining inconsistencies within various configuration states. Analysis and validation may happen at the time the change request is created with respect to the current environment, as well as analysis and validation with respect to other pending requests and proposals, and historical actual states. The maintenance of accurate and consistent state and change information may enable various automated tools to analyze and manipulate change requests, including analysis of future desired states, historical actual states, pending change requests, and current state. The change request may be processed through an approval cycle all the while being incorporated into a scheduling system that may be used to detect inconsistent, illogical or harmful configurations in potential future configurations.

Configuration change management tool

A configuration management database for storing configuration information about an IT system. The configuration management database may have representations of configuration items that correspond to configuration items in the IT system, indicia of relations between the configuration items, and attributes of the configuration items. The configuration management database may also have configuration state information of the configuration items, where the configuration state information has information indicating whether a configuration item, relation, or attribute is in a state of pending approval or in a state of planned deployment. The configuration management database may also have temporal information indicating a temporal state of a configuration item, relation, or attribute.

Configuration management database state model

A computer-readable storage medium having a data structure for representing a plurality of objects. The data structure includes a first data field storing data associated with a taxonomy type. The data structure also includes a second data field storing data associated with a reference to a model instance of an object classified by the taxonomy type. The model instance identifies an entity represented by the classified object. A third data field stores a first data set having data stored in the second data field. The first data set identifies a set of one or more objects related to the classified object positioned higher in a hierarchical structure than the classified object. A fourth data field stores a second data set having data stored in the second data field. The second data set identifies a set of one or more objects related to the classified object positioned lower than classified object.

Taxonomy object modeling

Growing community of inventors

Redmond, WA, United States of America

Nigel Graham Cain