Platform-Based Enterprise Technology Service Portfolio Management

2. The computing platform of claim 1, wherein the client device is associated with the first application and separate from the second application.

3. The computing platform of claim 1, wherein the first application is configured to implement a plurality of enterprise service configurations of the first enterprise service.

4. The computing platform of claim 1, wherein the first application is configured to monitor the one or more events associated with the second application based on a list of dependencies maintained by a third application hosted by the computing platform, wherein the list of dependencies comprises one or more relationships between the first enterprise service and the second enterprise service.

5. The computing platform of claim 1, wherein the first application is configured to monitor a performance of the first enterprise service, wherein, in response to determining that the event negatively affects the performance of the first enterprise service, the computing platform is configured to communicate the information related to the event to the client device.

6. The computing platform of claim 1, wherein the first application is associated with a first user of the computing platform and the second application is associated with a second user of the computing platform.

7. The computing platform of claim 1, wherein the computing platform comprises a cloud computing platform.

8. The computing platform of claim 3, wherein the first application is configured to generate a performance score for each of the plurality of enterprise service configurations of the first enterprise service based at least in part on the information related to the event.

9. The computing platform of claim 4, wherein the one or more relationships comprise a shared hardware relationship.

11. The method of claim 10, wherein the first portfolio of one or more enterprise services is associated with a first entity and separate from a second entity, and wherein the second portfolio of one or more enterprise services is associated with the second entity and separate from the first entity.

12. The method of claim 10, wherein the first application is configured to monitor the events associated with the second application based on a list of dependencies maintained by a configuration management database (CMDB) hosted by the computing platform, wherein the list of dependencies comprises one or more relationships between the enterprise service of the first portfolio of one or more enterprise services and a second enterprise service of the second portfolio of one or more enterprise services.

13. The method of claim 10, wherein the first application comprises a plurality of enterprise service configurations for each enterprise service of the first portfolio of one or more enterprise services, wherein the first application is configured to monitor a configuration performance of each enterprise service configuration of the plurality of enterprise service configurations.

14. The method of claim 11, comprising, in response to the first application determining that a second event of the events associated with the second application impacts the performance of the enterprise service, causing the client device to display, via the graphical user interface, second information related to the second event, wherein the client device is associated with the first entity.

15. The method of claim 14, comprising, in response to the first application determining that a third event of the events associated with the second application does not impact the performance of the enterprise service, continuing to monitor the events associated with the second application without causing the client device to display, via the graphical user interface, third information related to the third event.

16. The method of claim 12, wherein the one or more relationships comprise a software dependency.

18. The non-transitory, computer-readable memory of claim 17, wherein the first application is configured to generate a performance score for the enterprise service based at least in part on the information related to the event.

19. The non-transitory, computer-readable memory of claim 18, wherein the first application is configured to generate a portfolio performance score for the first portfolio of one or more enterprise services based at least in part on the performance score of the enterprise service and at least one additional performance score corresponding to at least one additional enterprise service of the first portfolio of one or more enterprise services.

20. The non-transitory, computer-readable memory of claim 17, wherein the event comprises a hardware outage caused, at least in part, by the second application.