Diversity - Complexity
IT is diverse in nature and complex
by the way it is implemented. One
needs only to think about the
complexity if a new accounting
system is to be implemented, but for
whatever reason one branch needs to
stay on the old legacy system. The
speedy lifecycle and the shortened
support for application of older
Versioning leads to a situation
where easily the overview is lost.
Nevertheless also IT needs to be
planned in a logical and justifiable
manner.
To be able to get a grip on the
situation IT landscapes or IT
Architectural plans are used to
represent the situation on hand.
Once established it becomes swiftly
the common communications platform
everybody is referring to when
addressing changes to the existing
Systems.
It can often be observed that
companies deny the need for such
representation, but once established
the usual response is that one could
not imagine how one could have lived
without it.
Content
An IT Landscape contains usually the following
components
- Process inventory
- Project inventory / Process
portfolio
- Application Inventory
- Application interface
collection
- Infrastructure inventory
- Server inventory
- Asset inventory
- Contract inventory
- License inventory
- Location inventory
With the application of different
"View" and respective charting
techniques, it is possible to
represent the IT landscape in its
entirety and also viewable according
to different purposes and
dependencies.
This enables a hands on modelling
and scenario development which is
especially important during the
Strategy development process.
|
Uses
Besides the use of the IT
Landscape for developing different
"to-be" scenarios during the
Strategy development is proved
invaluable for determining
dependencies when making changes to
the system/systems.
Another scenario in which an IT
landscape is of highest importance
is during Carve-out, Merger and
Acquisition activities.
Generally it can be said that the
IT Architecture / Landscape has even
in small companies already high
degree of details and often also a
considerable degree of complexity.
In order to keep on top of it,
without having to rely on wizards
who might or might not have all the
details in his/her head, it is
essential to represent IT-components
in one way or another
Conclusion
The investment in a documented IT Landscape pays itself
back in very short time in form of pinpoint clear
decision which cost less in implementations and cost
least in maintenance given the situation in a particular
company.
Also here there are 2 phases for a company which decides
to go for it:
1) The Establishment of documents / charts and forms to
represent the given Landscape best
2) The repetitive up-keeping of the established
Landscape
When implementing an IT landscape it is highly advisable
to have an external support available who can coach you
during this process.
|