Infrastructure Management

Set and enforce the standards

Managing the technology portfolio means applying standards to restrict proliferation of technologies while being flexible enough to support new ones as needed. Achieving this requires transparency across the technology portfolio, and the ability to answer questions such as: 'What technologies do I have and which applications depend on them?'.

planningIT answers these questions quickly and helps synchronize changes through comprehensive lifecycle management, as well as providing the structure to engage other stakeholders in managing the infrastructure effectively.

Explore more:

 
 
|1533|| /media/12264/infrastructure_management1.jpg |1533|1572| /media/12272/infrastructure_management2.jpg

Overview Architecture Diagram

The architecture diagram in the PlanningIT application provides a landscape overview of a selected business area (here Customer Relationship Management). The diagram is created from real underlying data. Filters at the top enable users to look at the current landscape, the past landscape and the future landscape. Colors indicate critical information and the health of each application can be included in the diagram. Information Flows between the applications are also depicted!

|1533|1574| /media/12280/infrastructure_management3.jpg

Application Platform View

The platform view shows the different components that are required to run the applications. Components can be defined in a component catalog and can be grouped into so-called tiers and layers. The view above shows which components are deployed on the different platform tiers and layers. It also shows which components are absolutely mandatory vs. optional. The view above also compares the current technology to defined standards and highlights non-compliance!

|1533|1575| /media/12288/infrastructure_management4.jpg

Platform Component Life Cycles

Applications are based on a technology platform which is leveraging components that have a life cycle. It is important to understand what the life cycles of the underlying components are so that upgrade and release planning can be done ahead of time and surprises with “not longer supported technologies” can be avoided. The example above shows the application owner that MS Windows 2003 Server is only supported until the end of 2010!

|1533|1576| 4