System, method, and computer program for generating a visibility model for a project

1. A computer program product embodied on a non-transitory computer readable medium, comprising:

computer code for identifying, by a visibility model generation hardware system, a plurality of disparate systems associated with a project, the visibility model generation hardware system being separate from the plurality of disparate systems and the project being a network rollout plan for a communication service provider (CSP) and the plurality of disparate systems contributing to execution of the project;

computer code for receiving, by the visibility model generation hardware system, information associated with the project from the plurality of systems during execution of the plan, the information corresponding to a status of discrete activities associated with the project;

computer code for organizing, by the visibility model generation hardware system, the received information corresponding to the discrete activities according to stages of the project;

computer code for generating, by the visibility model generation hardware system, a visibility model associated with the project utilizing the organized discrete activities, the visibility model presenting a graphical representation of a plan associated with the project and the plan having:

parent plan nodes each representing a different one of the stages of the project,

the discrete activities indicated in the parent plan nodes based on the organization of the discrete activities according to the stages of the project, and

an indication of the status of each of the discrete activities, wherein the status of each of the discrete activities is selected from the group consisting of: not yet started, started, and completed, and wherein the status of each of the discrete activities further includes an indication of a number of times that the discrete activity has been re-executed;

computer code for making the visibility model accessible, through one or more web services, to client devices for viewing by users;

acting, by a service level management module associated with the visibility model generation hardware system, on the start and completion statuses of each of the discrete activities to monitor an actual duration against an expected duration, wherein the service level management module is configured with escalation thresholds which when triggered are placed back into the visibility model to be used by the client devices, and wherein the service level management module resets the monitoring so that the escalation thresholds can be independently triggered for each re-execution;

computer code for receiving, by the visibility model generation hardware system, first updated information associated with the project from a first one of the plurality of disparate systems, the first updated information being an update to the status of at least one of the discrete activities;

computer code for receiving, by the visibility model generation hardware system, second updated information associated with the project from a second one of the plurality of disparate systems, the second updated information being one or more new activities included in a sub-stage of one of the stages of the project;

computer code for updating, by the visibility model generation hardware system, the visibility model associated with the project utilizing the first updated information and the second updated information by:

updating the indication of the status of the at least one of the discrete activities included in the visibility model based on the first updated information, and

adding the sub-stage of the one of the stages of the project including the one or more new activities as a sub-plan to one of the parent plan nodes representing the one of the stages of the project; and

computer code for making the updated visibility model accessible, through the one or more web services, to the client devices for viewing by the users.

2. The computer program product of claim 1 , wherein the computer program product is operable such that the visibility model is capable of modeling arbitrary dependencies.

3. The computer program product of claim 1 , wherein the computer program product is operable such that the visibility model is searchable.

4. The computer program product of claim 3 , wherein the computer program product is operable such that the visibility model includes a presentable timeline of key points associated with the project.

5. A method, comprising:

identifying, by a visibility model generation hardware system, a plurality of disparate systems associated with a project, the visibility model generation hardware system being separate from the plurality of disparate systems and the project being a network rollout plan for a communication service provider (CSP) and the plurality of disparate systems contributing to execution of the project;

receiving, by the visibility model generation hardware system, information associated with the project from the plurality of systems during execution of the plan, the information corresponding to a status of discrete activities associated with the project;

organizing, by the visibility model generation hardware system, the received information corresponding to the discrete activities according to stages of the project;

generating, by the visibility model generation hardware system, a visibility model associated with the project utilizing the organized discrete activities, the visibility model presenting a graphical representation of a plan associated with the project and the plan having:

parent plan nodes each representing a different one of the stages of the project,

the discrete activities indicated in the parent plan nodes based on the organization of the discrete activities according to the stages of the project, and

an indication of the status of each of the discrete activities, wherein the status of each of the discrete activities is selected from the group consisting of: not yet started, started, and completed, and wherein the status of each of the discrete activities further includes an indication of a number of times that the discrete activity has been re-executed;

making the visibility model accessible, through one or more web services, to client devices for viewing by users;

acting, by a service level management module associated with the visibility model generation hardware system, on the start and completion statuses of each of the discrete activities to monitor an actual duration against an expected duration, wherein the service level management module is configured with escalation thresholds which when triggered are placed back into the visibility model to be used by the client devices, and wherein the service level management module resets the monitoring so that the escalation thresholds can be independently triggered for each re-execution:

receiving, by the visibility model generation hardware system, first updated information associated with the project from a first one of the plurality of disparate systems, the first updated information being an update to the status of at least one of the discrete activities;

receiving, by the visibility model generation hardware system, second updated information associated with the project from a second one of the plurality of disparate systems, the second updated information being one or more new activities included in a sub-stage of one of the stages of the project;

updating, by the visibility model generation hardware system, the visibility model associated with the project utilizing the first updated information and the second updated information by:

updating the indication of the status of the at least one of the discrete activities included in the visibility model based on the first updated information, and

adding the sub-stage of the one of the stages of the project including the one or more new activities as a sub-plan to one of the parent plan nodes representing the one of the stages of the project; and

making the updated visibility model accessible, through the one or more web services, to the client devices for viewing by the users.

6. A system comprising:

a memory system of a visibility model generation hardware system; and

one or more processing cores of the visibility model generation hardware system that are coupled to the memory system and that are each configured to:

identify a plurality of disparate systems associated with a project, the visibility model generation hardware system being separate from the plurality of disparate systems and the project being a network rollout plan for a communication service provider (CSP) and the plurality of disparate systems contributing to execution of the project;

receive information associated with the project from the plurality of systems during execution of the plan, the information corresponding to a status of discrete activities associated with the project;

organize the received information corresponding to the discrete activities according to stages of the project;

generate a visibility model associated with the project utilizing the organized discrete activities, the visibility model presenting a graphical representation of a plan associated with the project and the plan having:

parent plan nodes each representing a different one of the stages of the project,

the discrete activities indicated in the parent plan nodes based on the organization of the discrete activities according to the stages of the project, and

an indication of the status of each of the discrete activities, wherein the status of each of the discrete activities is selected from the group consisting of: not yet started, started, and completed, and wherein the status of each of the discrete activities further includes an indication of a number of times that the discrete activity has been re-executed;

make the visibility model accessible, through one or more web services, to client devices for viewing by users;

act on the start and completion statuses of each of the discrete activities to monitor an actual duration against an expected duration, wherein escalation thresholds, when triggered, are placed back into the visibility model to be used by the client devices, and wherein the monitoring is reset so that the escalation thresholds can be independently triggered for each re-execution;

receive first updated information associated with the project from a first one of the plurality of disparate systems, the first updated information being an update to the status of at least one of the discrete activities;

receive second updated information associated with the project from a second one of the plurality of disparate systems, the second updated information being one or more new activities included in a sub-stage of one of the stages of the project;

update the visibility model associated with the project utilizing the first updated information and the second updated information by:

updating the indication of the status of the at least one of the discrete activities included in the visibility model based on the first updated information, and

adding the sub-stage of the one of the stages of the project including the one or more new activities as a sub-plan to one of the parent plan nodes representing the one of the stages of the project; and

make the updated visibility model accessible, through the one or more web services, to the client devices for viewing by the users.