Methods and systems for performing change management at login

1. A method for change management, comprising:

constructing, by a change management processor, an administratively prescribed target data store as a function of received administrative input;

storing, by the change management processor, the administratively prescribed target data store in a target data database;

receiving, by the change management processor, login information for a user from an input system, the login information having a username identifier, service provider identifier, and current use time-stamp;

querying, by the change management processor, a historical data store having stored therein, a user status that associates the username identifier and the service provider identifier with a previously used feature, feature-state and a previous use time-stamp;

querying, by the change management processor, the administratively prescribed target data store using the service provider identifier, to obtain a target feature and target feature-state, a mismatch message, a predefined time threshold, and a match message;

determining, by the change management processor, whether there is a mismatch, defined as an occurrence of the previously used feature and feature-state not matching the target feature and target feature-state;

displaying the mismatch message when there is a mismatch; and

displaying the match message when the current use-timestamp does not exceed the predefined time threshold and there is not a mismatch.

2. The method of claim 1 , further comprising:

determining, by the change management processor, when the mismatch represents that the user is attempting to use an outdated version of the target feature; and

displaying an updated version available message responsive thereto.

3. The method of claim 2 , further comprising:

upon displaying the updated version available message,

determining that the user previously used the target feature with the target feature-state but reverted to using the target feature with the previously used feature-state; and

displaying a user prompt asking why the user reverted to the previously used feature-state.

4. The method of claim 1 , further comprising:

determining, by the change management processor, when a new feature is available; and

displaying a new feature available message responsive thereto.

5. The method of claim 1 , further comprising:

determining, by the change management processor, when the mismatch represents that the username identifier has lost authorization to use any of: the service provider identifier, the previously used feature, or the target feature; and

displaying a failed authorization message responsive thereto.

6. The method of claim 1 , wherein:

the service provider identifier is one of a plurality of service provider identifiers;

the username identifier is one of a plurality of username identifiers;

each username identifier has an association with at least one service provider identifier of the plurality of service provider identifiers; and

the historical data store further has stored therein, for each association of each username identifier of the plurality of username identifiers, a respective user status that associates the username identifier and the service provider identifier of the plurality of service provider identifiers, the user status further associating with the service provider identifier, a respective previously used feature, feature-state, and use-timestamp.

7. The method of claim 6 , wherein:

each service provider identifier of the plurality of service provider identifiers has at least one target feature and each target feature of the at least one target features has a respective target feature-state; and

the target data store further has stored therein, for each of the at least one target feature of each service provider identifier of the plurality of service provider identifiers: a target feature-state, a mismatch message, a predefined time threshold, and a match message.

8. A non-transitory computer-readable medium having stored thereon instructions that, when executed by one or more processors, are configurable to cause the one or more processors to:

construct an administratively prescribed target data store as a function of received administrative input;

store the administratively prescribed target data store in a target data database;

receive login information for a user from an input system, the login information having a username identifier, service provider identifier, and current use time-stamp;

query a historical data store having stored therein, a user status that associates the username identifier and the service provider identifier with a previously used feature, feature-state and a previous use time-stamp;

query the administratively prescribed target data store using at least the service provider identifier to obtain a target feature and target feature-state, a mismatch message, a predefined time threshold, and a match message;

determine whether there is a mismatch between the previously used feature and feature-state and the target feature and target feature-state;

display the mismatch message when there is a mismatch; and

display the match message when the current use-timestamp does not exceed the predefined time threshold and there is not a mismatch.

9. The non-transitory computer-readable medium of claim 8 , wherein the instructions are further configurable to cause the one or more processors to:

determine when the mismatch represents that the user is attempting to use an outdated version of the target feature; and

display an updated version available message responsive thereto.

10. The non-transitory computer-readable medium of claim 9 , wherein the instructions are further configurable to cause the one or more processors to:

upon displaying the updated version available message,

determine that the user previously used the target feature with the target feature-state but reverted to using the target feature with the previously used feature-state; and

display a user prompt asking why the user reverted to the previously used feature-state.

11. The non-transitory computer-readable medium of claim 8 , wherein the instructions are further configurable to cause the one or more processors to:

determine when a new feature is available; and

display a new feature available message responsive thereto.

12. The non-transitory computer-readable medium of claim 8 , wherein the instructions are further configurable to cause the one or more processors to:

determine when the mismatch represents that the username identifier has lost authorization to use any of: the service provider identifier, the previously used feature, or the target feature; and

display a failed authorization message responsive thereto.

13. The non-transitory computer-readable medium of claim 8 , wherein:

the service provider identifier is one of a plurality of service provider identifiers;

the username identifier is one of a plurality of username identifiers;

each username identifier has an association with at least one service provider identifier of the plurality of service provider identifiers; and

the historical data store further has stored therein, for each association of each username identifier of the plurality of username identifiers, a respective user status that associates the username identifier and the service provider identifier of the plurality of service provider identifiers, the user status further associating with the service provider identifier, a respective previously used feature, feature-state, and use-timestamp.

14. The non-transitory computer-readable medium of claim 8 , wherein:

each service provider identifier of the plurality of service provider identifiers has at least one target feature and each target feature of the at least one target features has a respective target feature-state; and

the target data store further has stored therein, for each of the at least one target feature of each service provider identifier of the plurality of service provider identifiers: a target feature-state, a mismatch message, a predefined time threshold, and a match message.

15. A change management system, comprising:

a historical data store having stored therein, a user status that associates a username identifier and a service provider identifier with a previously used feature, feature-state and a previous use time-stamp; and

a change management processor programmed to:

construct an administratively prescribed target data store as a function of received administrative input, the administrative input specifying, for the service provider identifier: a target feature and target feature-state, a mismatch message, a predefined time threshold, and a match message;

receive login information for a user, the login information having the username identifier, the service provider identifier, and a current use time-stamp;

query the historical data store with the username identifier and service provider identifier to obtain the previously used feature, feature-state and the previous use time-stamp;

query the administratively prescribed target data store to obtain, for the service provider identifier to obtain the target feature and target feature-state, the mismatch message, the predefined time threshold, and the match message;

determine whether there is a mismatch between the previously used feature and feature-state and the target feature and target feature-state;

display the mismatch message when there is a mismatch; and

display the match message when the current use-timestamp does not exceed the predefined time threshold and there is not a mismatch.

16. The system of claim 15 , wherein the change management processor is further configured to:

determine when the mismatch represents that the user is attempting to use an outdated version of the target feature; and

display an updated version available message responsive thereto.

17. The system of claim 16 , wherein the change management processor is further configured to:

upon displaying the updated version available message,

determine that the user previously used the target feature with the target feature-state but reverted to using the target feature with the previously used feature-state; and

display a user prompt asking why the user reverted to the previously used feature-state.

18. The system of claim 17 , wherein the change management processor is further configured to:

determine when a new feature is available; and

display a new feature available message responsive thereto.

19. The system of claim 18 , wherein the change management processor is further configured to:

determine when the mismatch represents that the username identifier has lost authorization to use any of: the service provider identifier, the previously used feature, or the target feature; and

display a failed authorization message responsive thereto.

20. The system of claim 19 , wherein the service provider identifier is one of a plurality of service provider identifiers;

the username identifier is one of a plurality of username identifiers;

each username identifier has an association with at least one service provider identifier of the plurality of service provider identifiers; and

the historical data store further has stored therein, for each association of each username identifier of the plurality of username identifiers, a respective user status that associates the username identifier and the service provider identifier of the plurality of service provider identifiers, the user status further associating with the service provider identifier, a respective previously used feature, feature-state, and use-timestamp.