Technical Architecture Components

In general, infrastructure or data center cost is around 35-40% of an over all IT cost. Due to the high cost absorption in that area, it is prudent for any senior executive in the IT organization to have a better handle on the infrastructure cost.  The industry lacks uniformity in the cost management of IT as a whole and it applies to infrastructure/data center cost. The various cost management structure are available to manage the over all IT cost and it depends on the size and type of an organization. However, the general principle remain the same.

IT infrastructure cost  looked closely for IT cost optimization by every chief information officers. It is essential, particularly during this economical climate, to look the infrastructure cost distribution and study the alternative approaches for cost and competitive advantage. Chief Enterprise architects are directed by CIO and other senior executives to develop an IT infrastructure cost optimization program. To accomplish it, the enterprise architect must understand the high level information of  various components of  infrastructure and develop a technical architectural strategy.  Technical architectural strategy defines the future state and provides a foundation, the blueprint, for the infrastructure/data centre cost optimization program.

For any future state analysis and definition, the current state is studied and understood before a road map is developed to reach the future state.  1. To study the current state, itemize the various components of technical architecture and the service rendered in each components.

Components of technical/infrastructure architecture

  • Hardware
    • Servers
      • Distributed
        • WinTel
          • Linux
          • Windows
        • RISC
          • HP-UX
          • AIX
          • SGI
          • SUN Solaris
      • Mainframe
        • MVS
        • AS/400
    • Disk arrays
      • SAN storage
      • NAS storage
      • Backup
    • Network
      • Logical
        • Extranet
        • Internet
        • Intranet
      • Physical
        • Network Appliances (SSL accelerators, Net Cache devices, XML appliance)
        • Network devices (Routers, Switches, VPN devices, Hubs, Firewall, Wireless,Intrusion prevention)
        • Telephony devices (Dialer, ACDs, IVRs, PBX)
      • External Connectivity
        • SFTP drop box
        • VPN Tunnel
        • T1 line
        • ANX
        • OC3/5 internet connectivity
        • Frames/MPLS
    • Desktop
      • PC
      • Laptop
      • Mobile devices (iPhone, BlackBerry, Smart Phones, pagers)
  • Software
    • System Software
      • Server operating systems
      • Network operating system
      • Storage operating system
      • Desktop operating system
      • Compilers, Interpreters
      • File system management (VSAM, GFS )
      • Name resolution system (DNS)
      • Email servicing system (SMTP)
    • Web infrastructure
      • Application Server
      • Web Server
      • Portal Server
    • Data Administration
      • Database server – OnLine Transaction Processing (OLTP)
      • Data ware house
      • Reporting
      • Business Intelligence
    • Office management
      • Microsoft Office/OpenOffice
      • Email client
      • Browser
      • Remote login
      • Security – Virus prevention
    • Service Layer
      • Business process server
      • Message broker
      • Connector – database drivers, bridges,
    • Monitoring and control management
      • Service monitoring
      • Device monitoring
      • Compliance management
        • Data Loss prevention
        • Login monitoring
    • Collaboration Management server
    • Document management server
    • Storage Management Server
    • Emergency Management Service
      • Disaster Recovery Management
      • Business continuity Management
    • Enterprise Resource Planning (it will expand based on the core business)
      • Financials
        • Accounting
        • Management Accounting
          • Cash flow management
          • Fund flow management
      • HR
      • Procurement
  • Data center Services
    • Power grid architecture
    • Power Distribution Units (PDUs)
    • Backup power –
      • Automatic generators
        • Cooling and backup cooling for generators
        • Fuel capacity and distribution management
    • Cooling and heating
      • Backup cooling and heating
    • Wiring management
    • Rack management
    • Physical security
  • Security Service
    • Directory Services
    • Identity Management Services
      • User provisioning
      • Authentication
      • Authorization
      • User management
      • User de-provisioning
    • Network Security
    • Intrusion prevention
    • Firewall protection
    • Layered protection
      • Zoning – web zone, app zone, database zone, messaging zone, Demilitarized zone, file exchange zone

The service offering in each area depends on an enterprise.  Some enterprise has internal teams to provide all these services  and some has outsourced all of them. Mostly, enterprises adopt a hybrid approach with both external service provider and internal teams.  2. Define the future state in terms of strategic objectives like IT simplification, cost optimization, adaptability, agility for new market segment and etc.  3. For each component of the infrastructure, perform a SWOT, cost and new solution analysis and define the road map.

3 thoughts on “Technical Architecture Components

  1. Pingback: Technical Architecture Component – Service Delivery Model « Enterprise Architecture, IT Strategy & Others

  2. My question is here what kind of sills an EA should posess.List is Humangous and EA should have the broad level of knowledge to understand such kind of domains.Untill and unless he doesnt have the skills how can he optimise.he should be aware of each and every viable options in each service area for doing cost optimisation.So it cant be alone a EA taks.Ideally all the above service levels come under Infrastructure Architect.So do we need to have a Infra Architect ta take care of cost optimisation & if that is so what shall be the role of EA? Will he be a mere spectator to convey those inputs to CIO ?I am bit confused on the overlap of single domain architect with EA ?Kindly clarify

Leave a comment