Showing posts with label Catalogues. Show all posts
Showing posts with label Catalogues. Show all posts

October 6, 2007

Enterprise Architecture: Catalogues, Portfolios, and Inventories

There are three levels of architecture in the organization: enterprise, segment, and solutions. This is explained in a prior post.

Each level of the architecture identifies and categorizes business and technical information. However, the information captured in the three architecture levels (enterprise, segment, and solutions) differs as to their level of detail.

Here’s how this works:

  • CataloguesEnterprise architecture maintains catalogues of strategic-level enterprise assets. For example, EA provides catalogues of enterprise business functions and activities, enterprise systems, and enterprise hardware and software products and standards.
  • Portfolios—Segment architecture maintains portfolios of items scoped to the individual lines of business (LOB), at a medium level of detail, with impact focused on business outcomes. For example, a portfolio of systems or databases relevant to the functioning of a specific LOB such as for Finance, HR, and so on.
  • Inventories—Solutions architecture maintains inventories of configuration items for the enterprise. The configuration items are at the maximum level of detail for maintaining control of changes. This is used, for example, for software configuration management and for engineering support of IT infrastructure.

All three types of information products types—Catalogues, Portfolios, and Inventories—contain similar types of information pertinent to the organization; however, each product functions at a different level in the architecture—enterprise, segment, and solutions. Each of the information product types should be traceable and align to the next, so that inventories roll up into portfolios, and portfolios roll up in total to the enterprise asset catalogues. In this way, the architecture framework is consistent throughout the organization, items are traceable at all levels—from the solutions developers up to the strategic-level EA—and items can be viewed at the appropriate level of detail depending on whether the viewer is a senior leader, an executive decision-maker in the LOB, or a solution provider (“fixer-doer”).

Some organizations have chosen for simplicity’s sake to call all three of these product types “inventories.” That is acceptable, with the understanding that these “inventories” are providing different levels of detail corresponding to the different levels of architecture.


August 28, 2007

Data Architecture Done Right

Data architecture done right provides for the discovery and exchange of data assets between producers and consumers of data.

Data discovery is enabled by data that is understandable, trusted, and visible.

Data exchange is facilitated by data that is accessible and interoperable.

Together, data discovery and exchange are the necessary ingredients for information sharing.

Why is it so hard?

Primarily it’s a coordination issue. We need to coordinate not only internally in our own organization (often already large and complex), but also externally, between organizations — horizontally and vertically. It’s quite a challenge to get everyone describing data (metadata) and cataloging data in the same way. Each of us, each office, each division, and so forth has its own standards and way of communicating. What is the saying, “you say poTAYtos, and I say poTAHtos”.

Can we ever get everyone talking the same language? And even if we could, do we really want to limit the diversity and creativity by which we express ourselves? One way to state a social security number is helpful for interoperability, but is there really only one "right" way to say it? How do we create data interoperability without creating only one right way and many wrong ways to express ourselves?

Perhaps, the future will bring artificial intelligence closer to being able to interpret many different ways of communicating and making them interoperable. Sort of like the universal translator on Star Trek.