Infrastructure Reference Model (IRM)
What is Infrastructure Reference Model (IRM)?
The Infrastructure Reference Mode (IRM) categorizes the network/cloud related standards and technologies to support and enable the delivery of voice, data, video, and mobile service components and capabilities.
The IRM implementation enables sharing and reuse of infrastructure to reduce costs, increase interoperability across the government and its partners, support efficient acquisition and deployment, and enable greater access to information across enterprises. In addition to providing a categorization schema for IT infrastructure assets, the IRM enables analysis of IT infrastructure assets at a Department or Agency level as well as at a Federal Government level. In the Federal context, the IRM is adopted and used to conduct Government-wide analysis of IT infrastructure assets and to identify consolidation initiatives. In the Department or Agency context, the IRM is used to drive good IT infrastructure asset management practices such as identifying end-of-life assets before they affect the mission of an organization and to identify opportunities for sharing and consolidating infrastructure.
The IRM taxonomy is intended to provide a categorization scheme for physical IT assets, the operating systems and firmware that run them, and the locations or facilities that host the physical IT assets. The IRM is divided into three levels as shown in the figure below. Level 1 of the hierarchy, called “Domain”, consists of three entities, Platform, Network and Facility, which are linked and related to each other to enable analysis of IT assets across the three dimensions. Level 2 of the hierarchy, called “Area”, consists of 13 total Areas (for example, “Hardware”) linked to the three Domains in Level 1. Level 3 of the hierarchy, called “Category”, consists of 90 total Categories (for example, “Personal Computer – Laptop”) linked to the 13 Areas in Level 2. The adaptive and loosely coupled approach of the IRM supports multiple levels of executive management, capital planning and architecture stakeholders and their analytical needs.
source: The EA Pad
Federal Enterprise Architecture Framework Version 2 OWH