Library synchronization between definitions and instances

TECHNICAL FIELD

The subject specification relates generally to industrial controller libraries and in particular to propagation of a modified definition instance.

BACKGROUND

Industrial control environments can typically involve complex mechanical, electronic, electromechanical, and/or robotic machinery that perform various automated mechanical and/or electrical functions. Such machinery can include industrial motors, pumps, conveyors, escalators, drills, refrigeration systems, and so on, that can provide a particular physical output. Typically, an industrial environment utilizes one or more control devices to determine when to activate or deactivate such machinery, as well as an appropriate level of activation, for instance (e.g., an amount of current to supply a variable input motor). Additionally, the control devices are associated with logical program code that can determine an appropriate time, degree, manner, etc., to operate such machinery based on various determinable circumstances (e.g., output of another device, reading of an optical sensor, electronic measurement such as current level in a device, movement or number of rotations of a device, and so on).

Different controls can be used to provide protective features in an industrial environment. If a user attempts to make a change upon the industrial environment, then various checks can take place to discover if a user is authorized to make the change, such as requesting the user to enter a username and password. In addition, the user can be provided various tools that can assist in making changes to the industrial environment, including providing a template to be used to make different modifications.

SUMMARY

The following discloses a simplified summary of the specification in order to provide a basic understanding of some aspects of the specification. This summary is not an extensive overview of the specification. It is intended to neither identify key or critical elements of the specification nor delineate the scope of the specification. Its sole purpose is to disclose some concepts of the specification in a simplified form as a prelude to the more detailed description that is disclosed later.

In a conventional industrial control system, multiple units such as controllers, servers, and the like have access to definitions that relate to copies of local program code provided by a library. Various instances of the definition (e.g., instances of items characterized by definitions in a library) can be retained locally for faster operations, protection, isolation, and the like. When a change in a definition is made, related instances can automatically be modified to represent the new definition. However, problems can arise from automatic and absolute synchronization between definitions and instances. For example, changing a definition while an application is running can cause undesirable errors and ultimately cause an application to fail.

The disclosed innovation regulates synchronization between instances and definitions when a definition changes. A change can take place upon a definition (e.g., local definition, global and/or general definition, etc.) and a determination can be made when and/or if the change should be populated upon a related instance. The determination can be based upon artificial intelligence techniques, user preference, a defined rule set, user instruction, or a combination thereof.

The following description and the annexed drawings set forth certain illustrative aspects of the specification. These aspects are indicative, however, of but a few of the various ways in which the principles of the specification can be employed. Other advantages and novel features of the specification will become apparent from the following detailed description of the specification when considered in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

<figref idrefs="DRAWINGS">FIG. 1</figref> illustrates a representative library and multiple project configuration in accordance with an aspect of the subject specification.

<figref idrefs="DRAWINGS">FIG. 2</figref> illustrates a representative library and project configuration where a library definition is propagated upon a project in accordance with an aspect of the subject specification.

<figref idrefs="DRAWINGS">FIG. 3</figref> illustrates a representative library and project configuration where a local definition is propagated upon a project in accordance with an aspect of the subject specification.

<figref idrefs="DRAWINGS">FIG. 4</figref> illustrates a representative library and project configuration with multiple definitions in accordance with an aspect of the subject specification.

<figref idrefs="DRAWINGS">FIG. 5</figref> illustrates a representative industrial control configuration in accordance with an aspect of the subject specification.

<figref idrefs="DRAWINGS">FIG. 6</figref> illustrates a representative industrial control configuration in accordance with an aspect of the subject specification.

<figref idrefs="DRAWINGS">FIG. 7</figref> illustrates a representative system that can implement upon a library with a detailed identification component in accordance with an aspect of the subject specification.

<figref idrefs="DRAWINGS">FIG. 8</figref> illustrates a representative system that can implement upon a library with a detailed resolution component in accordance with an aspect of the subject specification.

<figref idrefs="DRAWINGS">FIG. 9</figref> illustrates a representative system for updating information in regard to an industrial control configuration in accordance with an aspect of the subject specification.

<figref idrefs="DRAWINGS">FIG. 10</figref> illustrates a representative methodology for changing instances based upon definition in accordance with an aspect of the subject specification.

<figref idrefs="DRAWINGS">FIG. 11</figref> illustrates a representative methodology for changing updates in waiting in accordance with an aspect of the subject specification.

<figref idrefs="DRAWINGS">FIG. 12</figref> illustrates an example of a schematic block diagram of a computing environment in accordance with an aspect subject specification.

<figref idrefs="DRAWINGS">FIG. 13</figref> illustrates an example of a block diagram of a computer operable to execute the disclosed architecture.

DETAILED DESCRIPTION

The claimed subject matter is now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the claimed subject matter. It can be evident, however, that the claimed subject matter can be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing the claimed subject matter.

As used in this application, the terms “component,” “module,” “system,” “interface,” or the like are generally intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a controller and the controller can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers.

As used herein, the terms to “infer” or “inference” refer generally to the process of reasoning about or deducing states of the system, environment, and/or user from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states, for example. The inference can be probabilistic—that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources.

Furthermore, the claimed subject matter can be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips . . . ), optical disks (e.g., compact disk (CD), digital versatile disk (DVD) . . . ), smart cards, and flash memory devices (e.g., card, stick, key drive . . . ). Additionally it should be appreciated that a carrier wave can be employed to carry computer-readable electronic data such as those used in transmitting and receiving electronic mail or in accessing a network such as the Internet or a local area network (LAN). Of course, those skilled in the art will recognize many modifications can be made to this configuration without departing from the scope or spirit of the claimed subject matter.

Moreover, the word “exemplary” is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the word exemplary is intended to disclose concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. It is to be appreciated that determinations or inferences referenced throughout the subject specification can be practiced through use of artificial intelligence techniques.

Now referring to <figref idrefs="DRAWINGS">FIG. 1</figref>, an example industrial control system <b>100</b> is disclosed that includes a library <b>102</b> and three projects <b>104</b>, <b>106</b>, and <b>108</b> (designated Project A, Project B, and Project C respectively). The library <b>102</b> can include a definition X that can be used by various entities that are part of the industrial control system <b>100</b> such as the projects <b>104</b>, <b>106</b>, and <b>108</b>. For example, the definition X can propagate upon each of the projects once and thus creating XA, XB, and XC, which are instances of the definition X. Propagation can occur from a request generated by a project <b>104</b>, <b>106</b>, or <b>108</b> as well as an instruction from the library <b>102</b> or an auxiliary entity. The definition X can be considered a general definition, which can be a definition that multiple entities use. This can differ from a local definition which can be a definition used only upon one entity and commonly is based upon a general definition of another entity.

A change can take place upon the definition X, such as a user modifying a meaning of a term. An identification component <b>110</b> can recognize the change, commonly though passive observation, receiving an explicit notice that the change occurs, and the like. In conventional operation, the change does not propagate automatically and is performed manually, which can cause undesireable errors and become relatively time consuming for a user. A user can be running an important application on Project A while the change in the instance can be relatively minor—making the change on the instance can disrupt the application and cause the application to restart. Therefore, a user can desire for the propagation to take place after the application runs. A resolution component <b>112</b> can determine a manner in which the change should be implemented. For example, the resolution component <b>112</b> can notify the user of the proposed propagation and the user can specify a time the propagation should occur (e.g., a set time, after the application runs, not to propagate, etc.)

Now referring to <figref idrefs="DRAWINGS">FIG. 2</figref>, an example industrial control system <b>200</b> is disclosed. Project A <b>104</b> can have multiple instances XAn (e.g., n can be an integer 1, 2, 3, or 4) based upon definition X retained upon library <b>102</b>. As a change takes place upon the definition, related instances can be modified to reflect the change. An identification component <b>110</b> can recognize a change in definition X and the resolution component <b>112</b> can determine a manner in which to propagate the change. In an illustrative example, the resolution component <b>112</b> can collect metadata related to operation of the system <b>100</b> and based upon a rule set, a determination can be made when propagation of each instance should take place. <figref idrefs="DRAWINGS">FIG. 2</figref> can be considered a logical perspective of an industrial control system, such that the specific instances do not need to exist physically separate from one another. One type of instance can be a disconnected instance—instance of a component that is intentionally disconnected from the library <b>102</b> once instantiated. Thus, changes to the library <b>102</b> are not propagated to a disconnected instance, thereby protecting custom modifications to such disconnected instance. There can be a method for searching for and reconnecting such disconnected instances so they can be reset to a latest library definition. This searching and reconnecting can be initiated from, the library, the disconnected instance, a terminal, etc.

Now referring to <figref idrefs="DRAWINGS">FIG. 3</figref>, an example system <b>300</b> is disclosed where there are both a general definition X and a local definition XA. The definition X can propagate as an instance XA upon Project A <b>104</b>; however, other instances can become dependent off the instance XA shown as instances XAn. Therefore, XA can operate as an instance of definition X and as well as be a local definition for instances XAn. An identification component <b>110</b> can recognize a suggested change in the definition X and a resolution component <b>112</b> can determine a manner in which the change should take place. The change can be a modification to the definition X, a propagation of the change upon the local definition XA, and/or propagation of the change upon at least one of the instances XAn—however, it is possible that propagation not be allowed.

While disclosed as residing upon the library <b>102</b>, it is to be appreciated that the identification component <b>110</b> and/or resolution component <b>112</b> can reside upon other entities. For example, the identification component <b>110</b> can reside upon the library <b>102</b> while the resolution component <b>112</b> resides upon Project A <b>104</b>. Additionally, these components as well as other components disclosed in the subject specification can reside upon a pluggable device that can be operatively coupled to the system <b>300</b>.

Now referring to <figref idrefs="DRAWINGS">FIG. 4</figref>, an example system <b>400</b> is disclosed for propagating a change upon a portion of instances. A library <b>102</b> can include a definition X that can be used as a basis for a local definition XA upon project A <b>104</b>. However, the definition X can be requested to change to X*. An identification component <b>110</b> appreciates the suggested change and a resolution component <b>112</b> can determine whether a change should be implemented.

Project A <b>104</b> can receive a notice that there is a change to the definition X to X* (e.g., there are multiple revisions of one definition) and therefore instances of X should be changed to represent X*. Project A <b>104</b> can retain two versions of the definition X-XA and XA* where XA discloses X and XA* discloses X* A determination can be made by the resolution component <b>112</b> on what instances of XA should be immediately changed to XA* and which instances should wait. The determination for these instances can be based upon artificial intelligence techniques, user preference (e.g., a profile created for a user through artificial intelligence inferences), a defined rule set, user instruction, other techniques, or a combination thereof. For example, a user can instruct that XA<b>3</b> and XA<b>4</b> be immediately updated while XA<b>1</b> and XA<b>2</b> be updated in about one hour. Therefore, XA<b>1</b> and XA<b>2</b> retain the value of XA while XA<b>3</b> and XA<b>4</b> retain the value of XA*.

Now referring to <figref idrefs="DRAWINGS">FIG. 5</figref>, an example system <b>500</b> is disclosed representing a complex industrial control system. Library A and previous versions of the library can be provided through an OEM (original equipment manufacturer). Library A as well as previous versions can be used for product support. At one time, the OEM can sell a first product with Library B to a customer, where Library B is a previous version of Library A that includes definitions X<b>1</b> and Y<b>1</b>. At a later time, the updated library can be provided to the customer represented as Library C that includes definitions X<b>2</b> and Y<b>2</b>, updates of definitions X<b>1</b> and Y<b>1</b> respectively. Various security measures can be instituted, such as password protecting portions of entities, including definitions. If a vendor accesses the system <b>500</b>, the security measures can protect sensitive information.

The customer can assign various definitions and instances to plants (e.g., Plant A, Plant B, and/or Plant C) that can be located at different physical locations. The plants can include individual projects (e.g., Project A, Project B, and/or Project C reside upon Plant B) where the individual projects can be reliant upon different network entities (e.g., Controller A, Controller B, and Server, which are used by Project C). Each plant, project, entity, and the like can have various instances and/or local definitions (e.g., an instance from a general definition upon which other instances on a common entity are reliant) based upon internal logic. For example, each plant, project, and entity (can be referred to as articles) can have an individual identification component <b>110</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> and/or resolution component <b>112</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>. Updates of definitions can be communicated to each article and an article can use the resolution component <b>112</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> and/or the identification component <b>112</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> to recognize the change and to determine how and/or if the change should be implemented upon an instance. Thus, different articles of one industrial control system can have different definition versions.

It is possible that determining a manner in which a change to a definition should be implemented can include determining the change should not take place. For example, Plant A and Plant B can manufacture different elements of a product. Definitions in plant B can include data relevant for operation of Plant A but unnecessary in plant B. It can be a waste of resources for Plant B to continuously update the definitions to reflect changes since the definitions are not used by Plant B, so a determination can be made never to implement the update.

Now referring to <figref idrefs="DRAWINGS">FIG. 6</figref>, an example system <b>600</b> is disclosed for synchronizing at least one definition and at least one instance across an industrial control configuration. Specifically, the system <b>600</b> can represent matching named elements disclosed in the system <b>500</b> of <figref idrefs="DRAWINGS">FIG. 5</figref>. Library A can initially include a definition X<b>1</b> that is populated upon Plant C, Project B (e.g., a project of Plant C), and Controller A (e.g., a controller used in operation of Project B). However, the definition X<b>1</b> can be subjected to a modification such that X<b>2</b> becomes a new value. A request to populate the new definition X<b>2</b> can be transferred to Plant C.

Plant C can evaluate the request through use of an identification component <b>110</b> and a resolution component <b>112</b>. The identification component <b>110</b> can recognize that the definition is to be changed from X<b>1</b> to X<b>2</b>. The resolution component <b>112</b> can determine a manner for implementing the change from X<b>1</b> to X<b>2</b>. According to one embodiment, the change is for local definitions and/or instances in Plant C. However, other configurations can be practiced, such as the identification component <b>110</b> and/or resolution component <b>112</b> operating for dependent units such as Project B and/or Controller A.

It is to be appreciated that propagation can take place from dependant units. For example, a user can make a request to change Definition X<b>1</b> to Definition X<b>2</b> at Controller A. The identification component <b>110</b> and resolution component <b>112</b> can be used to determine not only how instances and local definitions of the controller should change, but also how instances and/or definitions upon other units should change, including those that are ‘up-stream’ of Controller A, such as Project B, Plant C, or Library A.

Now referring to <figref idrefs="DRAWINGS">FIG. 7</figref>, an example system <b>700</b> for determining a manner in which a change upon a definition should be propagated and/or synchronized through an at least one unit of industrial control system with an example detailed identification component <b>110</b>. An identification component <b>110</b> can recognizes a change upon a definition. To facilitate operation, the identification component <b>110</b> can use a communication component <b>702</b> that can engage with other devices to transfer information, such as to send a request for metadata to determine how a change should be synchronized, receiving metadata from an auxiliary source, etc. Operation can take place wirelessly, in a hard-wired manner, employment of security technology (e.g., encryption), etc. Additionally, metadata transfer can be active (e.g., query/response) or passive (e.g., monitoring of public communication signals). Moreover, the communication component <b>702</b> can use various protective features, such as performing a virus scan on collected metadata and blocking metadata that is positive for a virus.

Oftentimes a user can make a request for a definition to change or to provide guidance on a manner in which to synchronize definitions with instances. An interaction component <b>704</b> can collect a user response to the change in the definition, the user response is employed to regulate the determination. Multiple criteria can be taken into account when determining a manner to perform the change including user instruction balanced against another standard such as against a rule set.

It is possible that request to change a definition can derive from an unauthorized source. For example, a station employee can request to change a definition that is intended to have change limited to a process management employee. Therefore, the authentication component <b>706</b> can determine if a request to change a definition and/or propagate the change upon other instances and/or definitions should be implemented, derives from an allowable entity, and the like.

Different pieces of information, such as collected metadata, component operating instructions (e.g., communication component <b>702</b>), source location, components themselves, etc. can be held on storage <b>708</b>. Storage <b>708</b> can arrange in a number of different configurations, including as random access memory, battery-backed memory, hard disk, magnetic tape, etc. Various features can be implemented upon storage <b>708</b>, such as compression and automatic back up (e.g., use of a Redundant Array of Independent Drives configuration). In addition, storage <b>708</b> can operate as memory that can be operatively coupled to a processor (not shown). The system <b>700</b> can include a resolution component <b>112</b> that can determine a manner in which the change should be implemented.

Now referring to <figref idrefs="DRAWINGS">FIG. 8</figref>, an example system <b>800</b> for determining a manner in which a change upon a definition should be propagated and/or synchronized through an at least one unit of industrial control system with an example detailed identification component <b>110</b>. An identification component <b>110</b> can recognize a change upon a definition (e.g., a proposed change, an implemented change, etc.). With the identified change, a resolution component that determines a manner in which the change should be implemented, such as updating a definition when the change is to modify a definition value or to synchronize a definition with at least one instance when the change is to propagate a definition change. According to one embodiment, the identification component <b>110</b> can create a library (e.g., library <b>102</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>) for an existing code block).

An artificial intelligence component <b>802</b> can be used to determine the manner in which the change should occur and can be configurable through rules definitions. The artificial intelligence component <b>802</b> can employ one of numerous methodologies for learning from data and then drawing inferences and/or making determinations related to dynamically storing information across multiple storage units (e.g., Hidden Markov Models (HMMs) and related prototypical dependency models, more general probabilistic graphical models, such as Bayesian networks, e.g., created by structure search using a Bayesian model score or approximation, linear classifiers, such as support vector machines (SVMs), non-linear classifiers, such as methods referred to as “neural network” methodologies, fuzzy logic methodologies, and other approaches that perform data fusion, etc.) in accordance with implementing various automated aspects described herein. In addition, the artificial intelligence component <b>802</b> can also include methods for capture of logical relationships such as theorem provers or more heuristic rule-based expert systems and use an expert system that remembers what is learned and is used to make decisions on learned knowledge. The artificial intelligence component <b>802</b> can be represented as an externally pluggable component, in some cases designed by a disparate (third) party.

An implementation component <b>804</b> can implement the change in accordance with the determination. According to one embodiment, the manner in which the change should be implemented is if implementation should occur about immediately or after experiencing a delay (e.g., an estimated delay, instructed by a user, and the like). The delay can be time-based, state-based (e.g., wait until the production line is idled for maintenance), event-based (e.g., wait until the current production run is finished), user command based (e.g., all changes wait until user approves), delay ends based on at least one artificial intelligence rule, etc. Once implementation occurs, a verification check can be performed by the implementation component <b>804</b> to determine if implementation is successful. If implementation is determined not to be successful, then the implementation component <b>804</b> can re-attempt to implement, determine why there was not success, attempt to repair an identified problem, create a diagnostic report concerning a problem, and the like.

The resolution component <b>112</b> can operate in multiple aspects—a manner can be determined for changing a definition, for changing a local instance, chancing a remote instance, and the like. The resolution component <b>112</b> can use a propagation component <b>804</b> that concludes an approach in which the change should be synchronized about at least one instance reliant upon the definition. The conclusion can be made based upon artificial intelligence techniques, user preference, a defined rule set, user instruction, or a combination thereof, as well as through other standards. According to one embodiment, the definition is a general definition (applicable to more than one entity) that resides in a library (e.g., library <b>102</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>). Thus, at least one instance subject to synchronization can reside in the library and/or a unit reliant upon the library. The definition can also be a local definition that resides in a unit reliant upon a library.

An adjustment component <b>808</b> can modify how the determination is made based upon at least one observation or instruction. For example, the adjustment component <b>808</b> can observe if errors occur when a rule set is relied upon for making a determination on a manner for implementation. If there is an error, then the adjustment component <b>808</b> can change at least a portion of the rule set in order to prevent other errors during other synchronizations. In addition, a user, an entity, and the like can make an explicit instruction to change the rule set, such as a user requesting the rule set be re-ordered and the adjustment component <b>808</b> can evaluate the request and implement the request if appropriate.

Now referring to <figref idrefs="DRAWINGS">FIG. 9</figref>, an example system <b>900</b> is disclosed for synchronizing a change upon a definition to various instances (e.g., local definitions that also function as instances of a general definition, pure instance—instance that do not have dependant instances, etc.) of an industrial control system. An identification component <b>110</b> can recognize a change upon a definition. The identification component <b>110</b> can operate as means for identifying a change upon a definition (e.g., implemented change, proposed change, and the like).

A distinguish component <b>902</b> can be used to identify at least one local instance (e.g., instance that is part of a common module of at least one definition) and/or at least one remote instance (e.g., instance that is not part of a common module of at least one definition) of the changed definition. Various manners can be used to identify instances. For example, each time an instance is created and/or deleted, a log can be modified to indicate information concerning the instance. Additionally, metadata can be logged that relates to an instance, such as a current version, a party that instructs a change, time of previous changes, and the like. Additionally, the distinguish component <b>902</b> can perform a search upon an industrial control system to determine instances of a definition. The distinguish component <b>902</b> can operate as means for distinguishing at least one local instance of the definition or at least one remote instance of the definition.

With identified instances, a resolution component <b>112</b> can determine a manner in which to modify the instances in accordance with a change upon the definition. The resolution component can use a local resolution component <b>904</b> that functions upon local instances and a remote resolution component <b>906</b> that functions upon remote instances.

The local resolution component <b>904</b> can implement as means for determining if at least one local instance of the definition should be automatically propagated with the change if at least one local instance is recognized. The remote resolution component <b>906</b> can function as means for determining if at least one remote instance of the definition should be automatically propagated with the change if at least one remote instance is recognized. Additionally, means for determining if at least one local instance of the definition should be automatically propagated with the change if at least one local instance is recognized can use artificial intelligence techniques, user preference, a defined rule set, user instruction, or a combination thereof in making at least one determination. Additionally, means for determining if at least one remote instance of the definition should be automatically propagated with the change if at least one remote instance is recognized can use artificial intelligence techniques, user preference, a defined rule set, user instruction, or a combination thereof in making at least one determination.

Now referring to <figref idrefs="DRAWINGS">FIG. 10</figref>, an example methodology <b>1000</b> is disclosed for facilitating a change upon an instance or definition in an industrial control configuration. A requested alteration for a definition or an instance can be obtained through action <b>1002</b>. The suggestion can be analyzed at event <b>1004</b>. Metadata related to the suggested alteration can also be collected as a result of the analysis, such as a name of an entity that makes a request. The suggestion can be to modify a definition as well as to synchronize an instance with a changed definition.

A check <b>1006</b> can occur to determine if a user response to a suggested change can be gathered. Commonly, the user response is taken into account when determining when and/or how a change should be propagated. If the user response is available, then a user can be solicited and the user can provide a proposal on how the change should be implemented at event <b>1008</b>. For example, a user can propose that the change be implemented when a set of diagnostic tests are completed.

With or without a user proposal, a manner in which change should be implemented can be determined through act <b>1010</b>. Act <b>1010</b> can function as determining a manner in which a suggested alteration to a definition should be implemented. The specific manner chosen, a slight variation based upon changing characteristics, and the like can be implemented through action <b>1012</b>. Action <b>1012</b> can operate as implementing the alteration in accordance with the determination.

The definition can be a general definition retained in a library, a local definition that resides in a unit reliant in a library, as well as other configurations. Artificial intelligence techniques as well as a rule set can be used to determine how implementation should occur (e.g., synchronization). However, the outcome could not be desirable, such as synchronization takes too long. Therefore, a result of the implementation can be analyzed for determination if modification of how a determination is made on the manner is appropriate at action <b>1014</b>. A check <b>1016</b> can determine if a change is appropriate—if a change is not appropriate, then the methodology <b>1000</b> can return to action <b>1002</b> to collect another suggested alteration. However, if a change should occur, then a proper modification can be identified and the determination can be changed in accordance with the identified modification at event <b>1018</b>.

Now referring to <figref idrefs="DRAWINGS">FIG. 11</figref>, an example methodology <b>1100</b> is disclosed for updating a modification to a definition or an instance that is in waiting. A suggestion to modify a definition or an instance can be obtained through action <b>1102</b>. The suggestion can arise for a user as well as from an automatically operating unit. A manner in which to implement the suggestion can be determined at act <b>1104</b>. Thus act <b>1104</b> can function as determining a manner in which a suggested alteration to a definition should be implemented.

A check can be performed at event <b>1106</b> if there are multiple alterations in waiting. For example, a first update can be transferred and an instruction can be made that synchronization should wait one hour. However, a second update can be suggested about a half hour later, thus there are two waiting updates. Event <b>1106</b> can operate as checking if there is a stale alteration in waiting. At block <b>1108</b> the second update can related the first update in order to conserve configuration resources. Block <b>1108</b> can operate as replacing a stale alteration with the suggested alteration. The alteration can be implemented through action <b>1110</b> in accordance with the determination at act <b>1104</b>, thus this can utilize the second update.

It is possible for multiple updates to be in waiting for a particular instance. Additionally, logic can be used to determine an appropriate synchronization when conflicting updates arise. For example, simultaneous updates can originate from different sources—artificial intelligence techniques can be used to determine which update should be synchronized in the system.

For purposes of simplicity of explanation, methodologies that can be implemented in accordance with the disclosed subject matter were shown and described as a series of blocks. However, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks can occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks can be required to implement the methodologies described hereinafter. Additionally, it should be further appreciated that the methodologies disclosed throughout this specification are capable of being stored on an article of manufacture to facilitate transporting and transferring such methodologies to computers. The term article of manufacture, as used, is intended to encompass a computer program accessible from any computer-readable device, carrier, or media.

In order to provide a context for the various aspects of the disclosed subject matter, <figref idrefs="DRAWINGS">FIGS. 12 and 13</figref> as well as the following discussion are intended to provide a brief, general description of a suitable environment in which the various aspects of the disclosed subject matter can be implemented. While the subject matter has been described above in the general context of computer-executable instructions of a program that runs on one or more computers, those skilled in the art will recognize that the subject matter described herein also can be implemented in combination with other program modules. Generally, program modules include routines, programs, components, data structures, etc. that perform particular tasks and/or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the inventive methods can be practiced with other computer system configurations, including single-processor, multiprocessor or multi-core processor computer systems, mini-computing devices, mainframe computers, as well as personal computers, hand-held computing devices (e.g., personal digital assistant (PDA), phone, watch . . . ), microprocessor-based or programmable consumer or industrial electronics, and the like. The illustrated aspects can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. However, some, if not all aspects of the claimed subject matter can be practiced on stand-alone computers. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

Referring now to <figref idrefs="DRAWINGS">FIG. 12</figref>, there is illustrated a schematic block diagram of a computing environment <b>1200</b> in accordance with the subject specification. The system <b>1200</b> includes one or more client(s) <b>1202</b>. The client(s) <b>1202</b> can be hardware and/or software (e.g., threads, processes, computing devices). The client(s) <b>1202</b> can house cookie(s) and/or associated contextual information by employing the specification, for example.

The system <b>1200</b> also includes one or more server(s) <b>1204</b>. The server(s) <b>1204</b> can also be hardware and/or software (e.g., threads, processes, computing devices). The servers <b>1204</b> can house threads to perform transformations by employing the specification, for example. One possible communication between a client <b>1202</b> and a server <b>1204</b> can be in the form of a data packet adapted to be transmitted between two or more computer processes. The data packet can include a cookie and/or associated contextual information, for example. The system <b>1200</b> includes a communication framework <b>1206</b> (e.g., a global communication network such as the Internet) that can be employed to facilitate communications between the client(s) <b>1202</b> and the server(s) <b>1204</b>.

Communications can be facilitated via a wired (including optical fiber) and/or wireless technology. The client(s) <b>1202</b> are operatively connected to one or more client data store(s) <b>1208</b> that can be employed to store information local to the client(s) <b>1202</b> (e.g., associated contextual information). Similarly, the server(s) <b>1204</b> are operatively connected to one or more server data store(s) <b>1210</b> that can be employed to store information local to the servers <b>1204</b>.

Referring now to <figref idrefs="DRAWINGS">FIG. 13</figref>, there is illustrated a block diagram of a computer operable to execute the disclosed architecture. In order to provide additional context for various aspects of the subject specification, <figref idrefs="DRAWINGS">FIG. 13</figref> and the following discussion are intended to provide a brief, general description of a suitable computing environment <b>1300</b> in which the various aspects of the specification can be implemented. While the specification has been described above in the general context of computer-executable instructions that can run on one or more computers, those skilled in the art will recognize that the specification also can be implemented in combination with other program modules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the inventive methods can be practiced with other computer system configurations, including single-processor or multiprocessor computer systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.

The illustrated aspects of the specification can also be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

A computer typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by the computer and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable media can comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer.

Communication media typically embody computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer-readable media.

With reference again to <figref idrefs="DRAWINGS">FIG. 13</figref>, the example environment <b>1300</b> for implementing various aspects of the specification includes a computer <b>1302</b>, the computer <b>1302</b> including a processing unit <b>1304</b>, a system memory <b>1306</b> and a system bus <b>1308</b>. The system bus <b>1308</b> couples system components including, but not limited to, the system memory <b>1306</b> to the processing unit <b>1304</b>. The processing unit <b>1304</b> can be any of various commercially available processors or proprietary specific configured processors. Dual microprocessors and other multi-processor architectures can also be employed as the processing unit <b>1304</b>.

The system bus <b>1308</b> can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory <b>1306</b> includes read-only memory (ROM) <b>1310</b> and random access memory (RAM) <b>1312</b>. A basic input/output system (BIOS) is stored in a non-volatile memory <b>1310</b> such as ROM, EPROM, EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer <b>1302</b>, such as during start-up. The RAM <b>1312</b> can also include a high-speed RAM such as static RAM for caching data.

The computer <b>1302</b> further includes an internal hard disk drive (HDD) <b>1314</b> (e.g., EIDE, SATA, SCSI, RAID), which internal hard disk drive <b>1314</b> can also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD) <b>1316</b>, (e.g., to read from or write to a removable diskette <b>1318</b>) and an optical disk drive <b>1320</b>, (e.g., reading a CD-ROM disk <b>1322</b> or, to read from or write to other high capacity optical media such as the DVD). The hard disk drive <b>1314</b> can also be solid state. The hard disk drive <b>1314</b>, magnetic disk drive <b>1316</b> and optical disk drive <b>1320</b> can be connected to the system bus <b>1308</b> by a hard disk drive interface <b>1324</b>, a magnetic disk drive interface <b>1326</b> and an optical drive interface <b>1328</b>, respectively. The interface <b>1324</b> for external drive implementations includes at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies. Other external drive connection technologies are within contemplation of the subject specification.

The drives and their associated computer-readable media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For the computer <b>1302</b>, the drives and media accommodate the storage of any data in a suitable digital format. Although the description of computer-readable media above refers to a HDD, a removable magnetic diskette, and a removable optical media such as a CD or DVD, it should be appreciated by those skilled in the art that other types of media which are readable by a computer, such as zip drives, magnetic cassettes, flash memory cards, cartridges, and the like, can also be used in the example operating environment, and further, that any such media can contain computer-executable instructions for performing the methods of the specification.

A number of program modules can be stored in the drives and RAM <b>1312</b>, including an operating system <b>1330</b>, one or more application programs <b>1332</b>, other program modules <b>1334</b> and program data <b>1336</b>. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM <b>1312</b>. It is appreciated that the specification can be implemented with various proprietary or commercially available operating systems or combinations of operating systems.

A user can enter commands and information into the computer <b>1302</b> through one or more wired/wireless input devices, e.g., a keyboard <b>1338</b> and a pointing device, such as a mouse <b>1340</b>. Other input devices (not shown) can include a microphone, an IR remote control, a joystick, a game pad, a stylus pen, touch screen, or the like. These and other input devices are often connected to the processing unit <b>1304</b> through an input device interface <b>1342</b> that is coupled to the system bus <b>1308</b>, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, etc.

A monitor <b>1344</b> or other type of display device is also connected to the system bus <b>1308</b> via an interface, such as a video adapter <b>1346</b>. In addition to the monitor <b>1344</b>, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.

The computer <b>1302</b> can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s) <b>1348</b>. The remote computer(s) <b>1348</b> can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all of the elements described relative to the computer <b>1302</b>, although, for purposes of brevity, only a memory/storage device <b>1350</b> is illustrated. The logical connections depicted include wired/wireless connectivity to a local area network (LAN) <b>1352</b> and/or larger networks, e.g., a wide area network (WAN) <b>1354</b>. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer <b>1302</b> is connected to the local network <b>1352</b> through a wired and/or wireless communication network interface or adapter <b>1356</b>. The adapter <b>1356</b> can facilitate wired or wireless communication to the LAN <b>1352</b>, which can also include a wireless access point disposed thereon for communicating with the wireless adapter <b>1356</b>.

When used in a WAN networking environment, the computer <b>1302</b> can include a modem <b>1358</b>, or is connected to a communications server on the WAN <b>1354</b>, or has other means for establishing communications over the WAN <b>1354</b>, such as by way of the Internet. The modem <b>1358</b>, which can be internal or external and a wired or wireless device, is connected to the system bus <b>1308</b> via the input device interface <b>1342</b>. In a networked environment, program modules depicted relative to the computer <b>1302</b>, or portions thereof, can be stored in the remote memory/storage device <b>1350</b>. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.

The computer <b>1302</b> is operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone. This includes at least Wi-Fi and Bluetooth™ wireless technologies. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from a couch at home, a bed in a hotel room, or a conference room at work, without wires. Wi-Fi is a wireless technology similar to that used in a cell phone that enables such devices, e.g., computers, to send and receive data indoors and out; anywhere within the range of a base station. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b, g, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wired networks (which use IEEE 802.3 or Ethernet). Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands, at an 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, as well as 802.1 in standard, for example, or with products that contain both bands (dual band), so the networks can provide real-world performance similar to the basic 10 BaseT wired Ethernet networks used in many offices. In addition, wireless networks can be configured as secured and unsecured, using various protocols, such as: Shared, Open, WEP, WPA, 802.1X, CCKM, etc. It is to be appreciated that other standards can be used and capabilities can be increased. For instance, protocol extending to 108 MBS, 200 MBS, etc.

The aforementioned systems have been described with respect to interaction among several components. It should be appreciated that such systems and components can include those components or sub-components specified therein, some of the specified components or sub-components, and/or additional components. Sub-components can also be implemented as components communicatively coupled to other components rather than included within parent components. Additionally, it should be noted that one or more components could be combined into a single component providing aggregate functionality. The components could also interact with one or more other components not specifically described herein but known by those of skill in the art.

What has been described above includes examples of the subject specification. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the subject specification, but one of ordinary skill in the art can recognize that many further combinations and permutations of the subject specification are possible. Accordingly, the subject specification is intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.