Ah, figured out how DCIM asset deployment should work, do you see the Information Architecture

I am having fun expressing some of my views of DCIM.  One area I don't think I've heard anyone discuss is the Information Architecture of their DCIM solution.

What is Information Architecture?

Information architecture is a specialized skill set that interprets information and expresses distinctions between signs and systems of signs. More concretely, it involves the categorization of information into a coherent structure, preferably one that the intended audience can understand quickly, if not inherently, and then easily retrieve the information for which they are searching[2][page needed]. The organization structure is usually hierarchical, but can have other structures, such as concentric or even chaotic[2][page needed]. Typically this is required in activities such as library systems, content management systems,web developmentuser interactionsdatabase development, computer programmingtechnical writingenterprise architecture, and critical system software design. Information architecture originates, to some degree, in the library sciences. Many schools with library and information science departments teach information architecture.[6]

In the context of information systems design, information architecture refers to the analysis and design of the data stored by information systems, concentrating on entities, their attributes, and their interrelationships. It refers to the modeling of data for an individual database and to the corporate data models that an enterprise uses to coordinate the definition of data in several (perhaps scores or hundreds) distinct databases. The "canonical data model" is applied to integration technologies as a definition for specific data passed between the systems of an enterprise. At a higher level of abstraction, it may also refer to the definition of data stores.

Why do you need an information architecture? For the same reason you need architects to design a building to make sure the end user purpose is met, but there is more to good architecture than does it work.  A good architecture has three qualities.

Three Principles of Good Architecture

The Roman architect Vitruvius in his treatise on architecture, De Architectura, asserted that there were three principles of good architecture:

  • Firmatis (Durability) - It should stand up robustly and remain in good condition.
  • Utilitas (Utility) - It should be useful and function well for the people using it.
  • Venustatis (Beauty) - It should delight people and raise their spirits.

Most would blow off the third principle.  How many users of DCIM delight in their time spent in the system and feel their spirits raised?  

If you don't think Beauty is important.  Than you don't get the way Apple products are designed.  Steve Jobs would be an example of a person who would believe in all three principles of good architecture.  How many executives buying DCIM want or believe in the three principles?  Not many.  On the other hand beauty is the experience people get from almost all luxury services - BMW, Porsche, etc.  So there is value in beauty.  

A great DCIM information architecture will be beautiful one of these days.