Modular system including management and deployment of software updates and revisions

1. A system for managing deployment and update of services within an enterprise, the system comprising:

a distributed network of servers, wherein each server has an assigned lifecycle level;

a computing platform including network memory and a processor in communication with the memory; and

an operating system-agnostic, modular-based, service delivery application stored in the network memory, executable by the processor and including a plurality of modules, each module configured to deliver a service to the enterprise, wherein the modules include:

a provisioning module configured to provide management over deployment of the services delivered by the modules and version updates to the services delivered by the modules, including:

determine and automatically implement an optimal schedule for service deployment and service version updates based at least on (i) three or more predetermined lifecycle levels, each predetermined lifecycle level being assigned to one of at least three or more networked devices in the enterprise executing the service delivery application, and (ii) segments within the enterprise, wherein each of the three or more predetermined lifecycle levels is selected from the group consisting of (1) development, (2) System Integration Testing (SIT), (3) User Acceptance Testing (UAT), (4) pre-production and (5) production, and wherein each of the at least three or more networked devices has a different one of the three or more predetermined lifecycle levels;

deny execution of non-permitted service versions by requiring networked devices in the enterprise that execute the service delivery application to verify a version being launched prior to executing the version; and

schedule deactivation of a declining service version and alert service delivery application users of the scheduled deactivation of the declining service version and a need to download an emerging version.

2. The system of claim 1 , wherein the provisioning module is further configured to determine and automatically implement the optimal schedule for service deployment and service version updates, wherein the optimal schedule comprises staging service deployment and service version updates over a predetermined period of time based at least upon the predetermined lifecycle levels assigned to the networked devices.

3. The system of claim 1 , wherein the provisioning module is further configured to automatically implement service version rollbacks.

4. The system of claim 3 , wherein the provisioning module is further configured to determine and automatically implement an optimal schedule for the service version rollbacks based on the predetermined lifecycle levels assigned to networked devices in the enterprise that execute the service delivery application.

5. The system of claim 1 , wherein the provisioning module is further configured to provide management over deployment of the services delivered by the modules and version updates to the services delivered by the modules, including implement side-loading of version updates to allow a user to simultaneously execute a current version while the version update is occurring.

6. An apparatus for managing deployment and update of services within an enterprise, the apparatus comprising:

a computing platform having a memory and at least one processor in communication with the memory; and

an operating system-agnostic, modular-based, service delivery application stored in the memory, executable by the processor and including:

a plurality of modules, each module configured to deliver a service to the enterprise, wherein the modules include,

a provisioning module configured to provide management over deployment of the services delivered by the modules and version updates to the services delivered by the modules, including:

determine and automatically implement an optimal schedule for service deployment and service version updates based at least on (i) three or more predetermined lifecycle levels, each predetermined lifecycle level being assigned to one of at least three or more networked devices in the enterprise executing the service delivery application, and (ii) segments within the enterprise, wherein each of the three or more predetermined lifecycle levels is selected from the group consisting of (1) development, (2) System Integration Testing (SIT), (3) User Acceptance Testing (UAT), (4) pre-production and (5) production, and wherein each of the at least three or more networked devices has a different one of the three or more predetermined lifecycle levels;

deny execution of non-permitted service versions by requiring networked devices in the enterprise that execute the service delivery application to verify a version being launched prior to executing the version; and

schedule deactivation of a declining service version and alert service delivery application users of the scheduled deactivation of the declining service version and a need to download an emerging version.

7. The system of claim 6 , wherein the provisioning module is further configured to determine and automatically implement the optimal schedule for service deployment and service version updates, wherein the optimal schedule comprises staging service deployment and service version updates over a predetermined period of time based at least upon the predetermined lifecycle levels assigned to the networked devices.

8. The apparatus of claim 3 , wherein the provisioning module is further configured to determine and automatically implement an optimal schedule for the service version rollbacks based on the predetermined lifecycle levels assigned to networked devices in the enterprise that execute the service delivery application.

9. The apparatus of claim 1 , wherein the provisioning module is further configured to provide management over deployment of the services delivered by the modules and version updates to the services delivered by the modules, including implement side-loading of version updates to allow a user to simultaneously execute a current version while the version update is occurring.