It Infrastructure Management An Introduction
It Infrastructure Management An Introduction
What is IT infrastructure and how do you manage it? Gartner defines IT infrastructure this way:
IT infrastructure is the system of hardware, software, facilities, and service components that support the
delivery of business systems and IT-enabled processes.
Let’s tackle the broad topic of what IT infrastructure is, what it includes, and who manages it. Then,
stick around for the end. We’ll play a game that puts your IT infrastructure knowledge to the test!
(If you’re looking for how-to’s and tips, see IT Infrastructure Planning: How To Get Started.)
IT infrastructure is a road
The Gartner definition is good for dealing with IT people. However, when discussing IT infrastructure
with organizational management, HR, or the C-suite, I generally use this road metaphor:
IT infrastructure is the digital road your information travels on.
Like building a physical road, infrastructure professionals plan, build, maintain, fix, and secure their
own digital road, over which all organizational data travels. They do not load and unload the
informational vehicles riding that road; they create the pathway the vehicles run on, maintain the
road, and regulate access and behavior on their infrastructure road.
All of which ensures the requested information gets to its intended user or app—be it terminal
screens, in-house applications, web sites, mobile apps, time punches, spreadsheets, documents,
reports, emails, or anything else.
Like local authorities, IT infrastructure managers manage their own individual piece of the road and
its access to the internet. Non-IT people may be fuzzy about hardware and IT-enabled processes,
but they know exactly what a road is. That is why the road metaphor works.
But note. There are a lot of grey areas. Especially when considering other IT infrastructure-adjacent
professions such as Data Center Manager, Network Manager, DevOps, database administrator,
Application Support, Service Desk management, etc. Many of these jobs handle functions that are
considered infrastructure and cover different sub-functions of the infrastructure.
But the heart and reason for infrastructure management are the areas covered above.
The technicians must understand how to deploy and set up infrastructure components.
The project manager needs to understand and direct infrastructure changes.
The higher-level staff must understand the architecture, budgeting, specifications, and
strategic purpose of each infrastructure function.
Cabling
Firewalls
HVAC systems and fire suppression systems
Intermediate Distribution Frames (IDFs)
Modems
Patch panels
Physical security for on-premises, off-premises, and cloud data centers (keyed locks,
electronic locks, mantraps)
Power systems (UPS and generators)
Routers
Server racks and server hardware
Special purpose servers for load balancing, security, Internet gateways, email filtering, etc.
Storage devices
Switches
Telecommunications equipment
Wall jacks
Wireless access points
Hardware skills also include managing any cloud infrastructure services your organization may use,
where services have migrated to the cloud. Technical skills for dealing with infrastructure hardware
include:
Installation
Repair
Hardware upgrades
Operating system installs and updates
Configurations
Going back to my analogy that your IT infrastructure is a road, the hardware infrastructure are the
building blocks and components needed to build an infrastructure road.
The hardware infrastructure is physically connected through cabling or wireless access points.
Patch panels, switches, routers, firewalls, and appliances are cabled and configured for access.
IP addresses, subnets, and gateways are created to segment your network, along with the
TCP/IP services (such as DHCP and DNS) that allow traffic to move inside and outside each
network segment.
The network infrastructure is also connected to the internet and your Wide Area Network
(WAN) through security servers\devices such as firewalls, edge servers, and
telecommunication lines.
In the road analogy, the network infrastructure is the connected and configured set of physical
devices that convey traffic along the infrastructure road.
These skills are applied for on-premises environments and in any Software as a Service (SaaS),
Infrastructure as a Service (IaaS), or Platform as a Service (PaaS) environments you may be using in
the cloud.
Business apps are usually custom written or modified. (That’s in spite of vendors saying you will be
able to run their apps in their delivered, vanilla configuration.) Infrastructure apps are generally
purchased third-party applications that are configured by infrastructure staff.
Here are some examples of what I would consider infrastructure software versus business
application software:
Additional resources
For more on this topic, explore these resources: