Our Framework
/ Infra / – from Latin meaning below or under
/ tech / – from late 19th century meaning technology and applied sciences
Users across enterprise and government have forgotten just how much lies below the technology they depend on every day.
Like the foundations of a building, you may not see them, but if they are not designed, built and installed correctly, disaster will happen, it is only a matter of time.
We divide Infratech into three broad categories of technology:
#1 Physical
The hardware and equipment that delivers modern IT.
#1 Infrastructure
cabling/racks/cooling/power/span>#2 Networks
LAN/WLAN/MAN/WAN/span>#3 Compute
Cloud/DC/Edge/End-user#4 Storage
Tape/Disc/NAS/SAN#5 Security
Access Control, Firewalls, IDS/IPS#2 Logical
The configurations and software that enables modern IT.
#1 Networks
SDN/SD-WAN/NFV#2 Compute
Virtualisation/Container/Serverless/SaaS#3 Storage
Block/Object/Distributed#4 Security
SASE/CASB/IdAM#5 Automation
DevOps/RPA/Infrastructure-as-code#3 Operational
The processes and automations that make modern IT work.
#1 Service / Network Operations Center
RMM/Break-fix/Moves-Adds-Changes-Deletions#2 Security Operations Centre
SIEM/SOC/EDR/SOAR#3 Backup, archival & disaster recovery
BC/DR runbooks/High-Availability DesignInfratech 5 Cubed
5cubed changes the way infrastructure eXperience is viewed by providers, customers and architects.
Every lens is different but the outcomes remain constant when the approach is used.
Technologies
grouped by operational application
Artefacts
documentation delivering consistency
States
prioritising business outcomes
Our cubes each have only five sides, because one is always firmly grounded on physical reality.
Despite what you have heard about the “cloud” and “virtual reality” – somewhere there is a real physical technology making is possible.
The three cubes that make up our 5 Cubed are:
5Cubed in action follows a set pattern of activity… in effect our “5 Steps” to project delivery;
This sequence of activity is essential to ensure business value.
Most IT projects fall down not because of technical reasons, but because organisations failed to clearly define the who-what-why-where and when drivers, instead skipped directly to how and brought some shiny tech.