Factor 1

Without a complete and enforced Enterprise Architecture, organizations run the risk of implementing strategies, which are outdated, managing processes which are redundant and buying and building systems that are duplicative and  incompatible. Unnecessarily, they add extra costs to integration, maintenance  & running the enterprise and its systems.

Factor 2

Very often you create a composite model, i.e. compound (multi-variable model) and store it.  It’s like creating X-ray of human body parts and storing it for solving a problem in the future without realizing that each body part is evolving daily. Unfortunately, current focus is to create a set of pre-defined “x-rays”. The reality is that we need the capability to get “x-ray” in real time as and when needed. The focus should be to define & create the enterprise “structure” so that snapshot or enterprise x-ray can be created on the fly and quickly (in minutes).

Factor 3

In the absence of ontology, several Enterprise Architecture projects end up producing just pictures (irrelevant composite models) and go onto the shelves never to be used. The sad story is that people are not even aware about it.

Factor 4

The bigger challenge is that all the EA frameworks (except Zachman Framework) focus on creating composite models (multi variables) and call them as “architecture” models. It’s like referring a “compound” as an “element” in the periodic table.

Zachman Framework is “enterprise ontology” and not just taxonomy (Top 21  Zachman Framework Myths – Busted). The framework is ontology, i.e. complete set of things that makes the enterprise, similar to “Periodic Table.” All the compounds (chemical) which exist on planet Earth can be formulated by mixing the primitive elements (of periodic table). Similarly, all the enterprise composites are possible by combining the primitive cells in Zachman Framework.

You will agree that every human being is different, yet they follow a common body structure. Similarly, every enterprise is different, but they follow a common structure, i.e. Zachman framework. Unfortunately, Human body is so complex that medical people still don’t have a good ontology.

Of course, there is no end to the prevailing confusions and myths in the industry about Enterprise Architecture. Best part is everyone is trying to outsmart the John Zachman …without realizing that he has spent nearly 40 years x 365 days, evolving the discipline of Enterprise Architecture.

Prevailing confusions and myths in the industry about Enterprise Architecture

BTW, you will definitely like the new post by John A Zachman on “Unfounded Reasons People Tell Me Why They Can’t Do Enterprise Architecture“.

The fact is that ALL Enterprise Architecture “Frameworks” in the industry is methodologies or derivatives from the Zachman Framework. They help in creating the “composite models” (implementation models)  and not “primitive models” (architecture models are single variable models). You may like to read my earlier blog post on “Deconstruct Business Process Model using Zachman Framework Principles – 5 part videos“.

Is there a way to validate the above?

Yes, it’s simple. Create a set of primitive models for each cell of “Executive Perspective” and “Business Management Perspective, i.e. Row 1 and Row2 in the framework. Once you have them, now you can create composite strategy models for any strategy frameworks such as Balance Score Card or Business Motivation Model or Mckinsey 7 S model, etc.

Some more cells and you are ready to create composite models for TOGAF or FEAF or DoDAF, etc.  Of course; reverse is not true. That means if you have primitive models (enterprise wide), you can create composite models to suit any frameworks, whether they are related to strategy, business process, systems, technology, etc. But, if you have only the composite model, it’s very difficult to get the primitives right.

I am planning for a post on “How to create different strategy models using Zachman framework primitive models,” hope to get that by middle of June. Hopefully, it will answer some more questions for you .

In the meanwhile, just the take the poll :Have you witnessed Enterprise Architecture projects that just produced pictures and went on shelves never to be used?

Next time when you  hear someone calling ”implementation models” (composite models – multi variable models) as the “architecture models”, don’t forget to remind them . Only those models which are single variable models are entitled to be called as “architecture model”. Let’s show some mercy , please.

Related articles

• Deconstruct Business Process Model using Zachman Framework Principles – 5 part videos (blogs.icmgworld.com)

Some questions related to – what’s the difference between primitive and composite?  Why do you need primitive models ? how these concepts are helpful in the context of business process modeling?  How to use the primitive to create the target business process diagram?    What are the limitations of the approach which doesn’t consider the concepts of primitive models ?

Too many questions, and best thing I could do is to show you the samples and in the process answer some of the questions. Have tried to explained the concept of primitives and composites in the context of business process models. Hope you will like it.

1. Problem definition – how to deconstruct & map the business process diagram in to Zachman framework

2. Primitive models – how to create single variable models in the context of business process

3. Composite model – how to create composite business process models from primitive models?

4. Samples  – samples of composite business process models. Five composite business process models.

5. Target process models – creating target process with multiple variables.

Real improvement, real benefits

Related articles

• John Zachman quotes on inherent complexity in running and managing enterprises (blogs.icmgworld.com)
• Top 21 Zachman Framework Myths – Busted (blogs.icmgworld.com)
• Zachman Framework graphics v3.0 – what’s NEW? (blogs.icmgworld.com)
• John Zachman will certify only 50 professionals in next 6 months world over, are you the chosen one? (blogs.icmgworld.com)

You will agree that the most complex object of the information age is “Enterprise.” The inherent complexity is nothing less than what you will find inside a human body (anatomy). Human beings existed much before the arrival of medical science. Medical science brought common understanding about the anatomy, various systems such as Muscular, Nervous, and Reproductive, etc. This resulted in discovery of the fact that every human being is different, yet they follow a common structure. Guess what, resulting tools, techniques, equipment, etc. brought predictability in the process of creation of life, evolution and life cycle management. Of course, in extreme cases, diagnosis is possible without any luck with the treatment, sad but true.

It’s nearly 40 years back when John Zachman’ started on his endeavor to find the common structure behind every “Enterprise.” With his success, came the much-needed insight in to the enterprise anatomy and the evolving discipline is called “Enterprise Architecture.” This has resulted in discovery of the fact that every enterprise (in whatever industry) is different, yet they follow a common structure, i.e. Zachman Framework.

This discovery is similar to the discovery of “Periodic Table” by Mendeleev, who found that every “compound” on earth (any beyond) follow a common structure i.e. consisting of elements. This knowledge resulted in formalizing and evolution of discipline, i.e. Chemical Science. The Mendeleev’s Periodic Table brought much-needed predictability in analysis, creation and life cycle management of “compounds.” Our ability to create an object which could withstand a temperature of 14,000 degree Celsius is a good example of what can be accomplished.

“Enterprises” have existed much before the discovery of the framework. Zachman Framework of Enterprise Architecture, is brining much-needed predictability in the creation, evolution and life cycle management of the “Enterprise.” That’s reason why Zachman Framework is also known as “Periodic Table for the Enterprise.”

Very often enterprise disorders are caused due to modernization initiatives,  shrinking margins, operational overheads, misplaced assets, IT mismanagement, business process duplication & redundancy, friction among stakeholders, efforts in isolation, growth  deceleration, sloppy decision-making etc.

 Here, is the list of 9 common enterprise dis-orders:

		Enterprise Disorder	Diagnosis & Treatment	Impact
		If you are embarking on a modernization initiative?	Understand the actions & activities minus buzzwords	Increase Revenue
		Shrinking margins and slow growth, operational overheads?	Use the Zachman Framework for diagnosis & corrections. Get the enterprise back on track.	Increase Revenue
		Untangle the mystery of enterprise assets (People, Business Processes, IT, Technology, Network etc. & readiness	Learn how to create traceability, relationship matrix, impact analysis before expanding into new markets	Increase Revenue
		Success is about decisions – right ones.	Decisions driven by insights (enterprise x-ray).  Effectively translate strategies to execution	Increase Revenue
		Optimize your internal or outsourced IT investment & assets	Minimize the application, technology overlaps, redundancy and isolate the ones which are obsolete	Cost Savings
		Isolate process duplications & remove redundancy	Optimize the business processes in terms of timeliness, cost and resources available	Cost Savings
		How to minimize the friction  among the stakeholders	Understand the role distribution, work assignments and measurement to effectively minimize  friction	Cost Savings
		Learn why efforts in isolation will result in entropy	Several way to minimize the entropy	Cost Savings
		Minimize operational overheads	Understand the source and nature of leakage and overheads. Plug it quickly and effectively. Every dollar counts.	Cost Savings

 You can acquire the skills and experience to address the issues as described above. The “Zachman Certified – Enterprise Architect” program is aimed at professionals like you who are currently involved in projects/programs of high visibility & complexity. If you are involved in a project which has enterprise-wide significance and wherein stakes are high, don’t miss this.

Workshop schedule

This is a very exclusive certification program. If you want to understand the “Complexity & Contradiction” in Enterprise and struggling to manage non-adaptive enterprise and dysfunctional systems, you don’t want to miss this. Not to mention, you’d be embarking on a journey to be one of the leading enterprise architecture practitioners in the world.

Related articles

• Top 21 Zachman Framework Myths – Busted (blogs.icmgworld.com)
• John Zachman will certify only 50 professionals in next 6 months world over, are you the chosen one? (blogs.icmgworld.com)
• Zachman Framework graphics v3.0 – what’s NEW? (blogs.icmgworld.com)
• John Zachman quotes on inherent complexity in running and managing enterprises (blogs.icmgworld.com)

The CFOs and board are looking at the economics of enterprise architecture as a blueprint to business transformation. It has been established beyond doubt that successful organizations have achieved significant performance achievements based on architecture driven initiative resulting in reduction in  IT cost, business process improvement, new service offerings, cost efficiency, readiness for changes, etc.

It’s nearly 40 years back when John Zachman’ started on his endeavor to find the common structure behind every “Enterprise.” With his success, came the much-needed insight into the enterprise anatomy and the evolving discipline is called “Enterprise Architecture.” This has resulted in discovery of the fact that every enterprise (in whatever industry) is different, yet they follow a common structure, i.e. Zachman Framework.

Announcing one of the most productive, four-day certification workshop by two brightest brains on “Enterprise Architecture.” Of course, one is living legend and the inventor of the “Enterprise Architecture” himself – John Zachman and other is Sunil Dutt Jha – an accomplished practitioner and CEO of iCMG who will help you to unravel the science behind the “enterprise.”

This 4-day workshop covers the latest version of the Zachman Framework v3.0. It’s the most EA-inclusive representation of the Zachman Framework over the last 40 years. This program will prepare the participants for “Zachman Certified- Enterprise Architect (both Level 1 & Level 2) examination, which is taken separately at a later date.

Our experts will discuss about the diagnostic techniques that can help narrow the causes of the problem or complication and ensure that the diagnosis is accurate. These techniques include visual modeling, creating composites, simulations, traceability, relationship matrix, gap analysis, impact analysis, etc. These visualization tools let you “see” inside your enterprise (or department or system) to get a “picture” of strategy, business processes, data assets, technology stacks, network channels, distribution logistics, events, stakeholders, workflow, rules, etc. This is a way you can determine if there are any abnormalities. Furthermore, minimize the friction between the IT folks and business leaders and grease the joint efforts.

There are only 50 certifications available in next 6 months (until August 2012) unlike other certifications, which are in hundreds every month. So, hurry and enroll quickly in the city and country near you. This is a very exclusive certification program. If you want to understand the “Complexity & Contradiction” in Enterprise and struggling to manage non-adaptive enterprise and dysfunctional systems, you don’t want to miss this.

Who should attend?

1. If you are involved in a project which has enterprise-wide significance and wherein stakes are high, don’t miss this.

2. If you are CIO or Chief Architect or Enterprise Architect and don’t want your sponsors & enterprise to fail, enroll yourself.

3. If you are warming up for a career as a Chief Architect, CIO or Enterprise Architect, etc. this certification program will equip you with necessary skill & techniques to manage non-adaptive enterprise and dysfunctional systems.

How to justify the investment

1. This program is aimed at professionals who are currently involved in projects/programs of high visibility & complexity.
2. It’s advisable to use the project budget to fund this training and certification and let the “training budget” available for others. 
3. This program will empower you with unparalleled insights and of course double your chances to know the pitfalls, risks and issues twice as early.
4. In fact, we have found that decision which would take months of efforts are now arrived in minutes.
5. Of course, timely decision can put your business way ahead of your competitor.
6. Furthermore, a risk avoided could result in saving of millions and minimizes the hurt burns.

Look out for the next blog post on “Nine reasons why Zachman certification is a smart investment”.

Workshop schedule

 This certification program can teach you architecture skills that will surprise you and your friends. Better, you will have fun and have valuable practical TOOLS inside your “brain.” Yes, even you can learn to do seemingly complex architecture blueprint in your “brain.” Not to mention, you’d be embarking on a journey to be one of the leading enterprise architecture practitioners in the world.

Related articles

• John Zachman quotes on inherent complexity in running and managing enterprises (blogs.icmgworld.com)
• Top 21 Zachman Framework Myths – Busted (blogs.icmgworld.com)
• Zachman Framework graphics v3.0 – what’s NEW? (blogs.icmgworld.com)

On behalf of iCMG management and the jury, I am happy to invite nominations for the world’s most coveted Enterprise & IT Architecture Awards. This year is the third year in a row. In the last two years, the experience and excitements of the participants and winners (

 Why Architecture Excellence Awards?

 About Jury

I look forward to hearing from you.
Cheers

Related articles

• iCMG Award 24 Winners for Global Excellence in Enterprise & IT Architecture (prweb.com)
• Missed it Last Year? Nominate for the Architecture Awards 2012 (blogs.icmgworld.com)

Last year, we had a discussion in iCMG LinkedIn group (over 20,000 members) which ignited the passion and invited over 1000 comments. The title of the thread was “What’s killing the Enterprise Architecture? – quote extracted from one of John Zachman’s article.” As the time has gone by, the number of people who misrepresent and misinterpret the Zachman framework has gone up significantly. The problem is that the framework is easily available for download and it has English labels which are legible.

You will agree that downloading recipe from a cookery portal doesn’t make one a master chef.

As the time has gone by, number of misrepresentations has only gone up – thanks to the growing interest in the discipline of “Enterprise Architecture.”

Some of the common myths about the framework are: Is the framework for Enterprise or IT or both; colors are random; there is no Integration across columns; transformation vs. decomposition; number of rows can change, columns are arbitrary, perspectives are random; no rules to separate primitive vs. composites; architecture constructs vs. manufacturing constructs; methodology vs. ontology; taxonomy vs. ontology; checklist vs. periodic table; row 1 & row 2 vs. row 6; etc.

	Myths	Facts
1.	Column 1 is labelled “Data,” which classify Zachman Framework™ as a Framework for Information Systems.	Not correct. It’s not the framework for Information Systems. In fact, in 2004, the term “data” was removed from the framework. Please note that in 2011 version of the framework graphics – The enterprise name for “What” is “Inventory Sets”.
2.	“Data” is the most important aspect of the enterprise as it’s in the first column. “Motivation” is “least” important as it’s in column six	Not correct. Order of columns has nothing do to with their relative importance in the context of “Enterprise”. The order of column just reflect the order in which 6 communication interrogative i.e. what, how, where, who, when, why are being used. “What or earlier data” column being the first column is just reflecting the order in which people (around the world) have been using these 6 interrogative.
3.	The Framework, and Enterprise Architecture for that matter, are an IT issue	No.The reality is that the Zachman Framework is Ontology for Enterprise Architecture. Unfortunately, most people who come from IT today are thinking of building and running systems and not about engineering and manufacturing enterprises.
4.	People’s misperception that working your way down the columns is merely an increase in level of detail.	The movement down each column has nothing to do with level of detail; it has to do with transformation
5.	Each cell containing composite constructs.	Oops! Wrong again. Each cell consists of primitive constructs, not composites.
6.	The Framework is just a matrix	The brilliance of this Framework is in the concepts of Integration (across the Rows) and Transformations (down the Columns). Often, constructs within the “Enterprises” are in “composites” form created by integrating the elements across the cells.This helps in effective diagnosis, better predictability and enhanced traceability for change and complexity management. Once you will use it, you will understand what I am talking about.
7.	The Framework is a checklist.	It’s similar to saying “Periodic Table” is a checklist. You can use the framework as a checklist, but it’s oversimplifying the fact. We know that one can use the periodic table for creating complex compounds with predictive characteristics or behaviour. Similarly, one should use the framework for creating complex enterprise constructs (composites) to meet some defined need.
8.	There is NO indication that INTEGRATION exists between the Columns.	Blame the previously available framework graphics. In fact, the new framework graphics very clearly represents the “Integration lines” linking elements between the columns. This clearly establishes that integration exists between the Columns as well. Architects can use the primitive cells of the Framework (Periodic Table) to build the composite implementations (Chemical Engineering) to produce predictable, repeatable results (a science).  The integrations and transformations are like “mortar between the bricks” (the bonds between the chemical elements).
9.	Framework is  enterprise taxonomy	It’s understatement. Framework is “enterprise ontology” and not just taxonomy i.e. complete set of things that makes the enterprise similar to “Periodic Table.” All the compounds (chemical) which exist on planet earth can be formulated by mixing the primitive elements (of periodic table). Similarly, all the enterprise composites are possible by combining the primitive cells in Zachman framework. Every human being is different, yet they follow a common body structure. Similarly, every enterprise is different but they follow a common structure i.e. Zachman framework. Unfortunately, Human body is so complex that medical people still doesn’t have a good ontology.
10.	The Zachman Framework in competition with other  Enterprise Frameworks	There are many “Frameworks” in EA and there is significant confusion about what the word “Framework” actually means. The fact is that ALL Enterprise Architecture “Frameworks” in the industry is a methodology or derivative of the Zachman Framework. The Zachman Framework for Enterprise Architecture is “Enterprise Ontology”.
11.	Most people who misrepresent Zachman Framework as a “waterfall,” think that each Row represents another level of detail, i.e. the highest level of detail at the top of The Framework (Row 1) and the most excruciating level of detail at the bottom of The Framework (Row 5)	Grossly misunderstood. This is not the case at all. The models of each Row TRANSFORM- they do not get more detailed. Level of detail is represented in the height of each cell, i.e. a high level of detail at the top of each cell and an excruciating level of detail at the bottom of each cell
12.	The Framework’s fundamental concept is decomposition, down each column	The Framework’s fundamental concept is “transformation”, not “decomposition”, in the reification process down each column. An idea (or Scope-Row 1) has to go through 6 well-known phases in order to reach reality (Operations-Row 6) such that the reality retains an alignment with the initial idea as it was conceived and designed.
13.	Column 3 (Network Nodes- 2004 Version).Enterprise Architects often thought of this as point-to-point nodes and were not building their models correctly.	The fact is that the fundamental concept of Column 3 deals with distribution of resources as opposed to node addresses on a network.
14.	The six rows are arbitrary i.e. John has just picked up 6 different perspective (in six rows) and there are more perspective which can be added – that is, more rows can be created.	No it’s not arbitrary. John uses the 2000 year old concept of reification i.e. how to transform an abstract idea to reality.Reification consist of 6 phases of transformation i.e.- Identification (mapped to Row 1)- Definition (mapped to Row 2)- Representation (mapped to Row 3)- Specification (mapped to Row 4)- Configuration (mapped to Row 5) and - Instantiation (mapped to Row 6)The models in each row get transformed to the next Row below, and the Row 6 wraps up the 6th phase of reification
15.	“Who”: Column 4 – Organization Groups.  As soon as the Enterprise Architects saw this label, they incorrectly assumed it as: Organization Chart?	This is not so. This Column is all about “responsibility”. In Zachman Framework v3.0 (2011), meta-model has been changed to form the title “Responsibility Assignments” for Column 4.
16.	Zachman Framework is a “methodology”	The Zachman Framework™ is the “Enterprise Ontology” and not “methodology”. It’s a classification theory about the scientific nature of any Enterprise and the kinds of “Things” (entities) that have an existence in that Enterprise. Therefore, The Zachman Framework for Enterprise Architecture is the ENTERPRISE ONTOLOGY. The way the “Periodic Table” is ontology for “Chemistry”; the “Zachman” framework is the ontology for “Enterprise”. Once you know the “Enterprise Ontology”, you can create /use a methodology of your choice. Using a methodology without ontology is a “trial and error” practise.
17.	Creating the “composite model” is creating the “architecture”	No, “composites” are manufacturing constructs. Primitives (single variable models) are Architecture constructs. Unfortunately, people are building composite models by hard-binding multiple concepts together in their “model” and calling it “Architecture”.
18.	Six columns in Zachman Framework are arbitrary, I can add few more columns on need basis	Wrong, the columns are not arbitrary. The 6 columns represent the universally accepted 6 communications interrogative i.e. what, how, where, who, when and why.
19.	The colours are just a decorative piece; I can use any colour. I don’t see any logic or significance.	The colours of the models in each Row are significant.  Here, John used the colour models as a teaching tool to re-enforce the idea that each Row is different and is the result of a transformation, NOT a decomposition of detail. John used spectrum colours: Red, Orange, Yellow, Green, Blue and Orange. Why he didn’t round out the spectrum with Purple in Row 6.? The reason is that, “Row 6 is Orange to match Row 2; because whatever the Owners have in mind (Row 2 – Business Concepts – Orange) should be what is actually instantiated in the Enterprise (Row 6 – THE ENTERPRISE – Orange).”
20.	Enterprise Architecture is only Row1 & Row 2.	Enterprise Architecture is comprised of Rows 1-5. The instantiated Enterprise is represented in Row 6
21.	Zachman Framework is complex.	Ignorance. The framework is not complex, but the enterprise IS. The Periodic Table has to be complete in order to allow the chemists to be able to analyse, and create compounds with accuracy and repeated predictability. Similarly, Enterprise framework has to be complete to ensure that enterprise architects are able to analyse, and create enterprise constructs quickly and in a repeatable fashion to achieve the results. The problem lies in basic understanding and application of the framework. A chemist never creates “infinite” number of compounds just because it’s theoretically possible using the Periodic Table. They create the compound based on the need. Similarly, doctor never creates 1000 x-rays or scans of all parts of the body of a patient and stores it in the repository. On the similar lines, the idea is not to create infinite number of composites based out of the Zachman framework, rather create those which are needed to address some problem of the Enterprise.

Of course, 5 myths that one can find around the corner:

1. Enterprise Architecture is only row1 & row 2
2. Zachman Framework is a “methodology”
3. TheFramework’s fundamental concept of decomposition, down each column. Each Row represents another level of detail
4. There is NO indication that INTEGRATION exists between the Columns.
5. Each cell containing composite constructs.

What’s your experience? Share your favorite myth about Zachman Framework. Feel free to share if you have come across any other misperceptions? Would be happy to hear from you.

Note:For the insight on the evolution of framework since 1984, please visit article by John P Zachman

Related articles

• Zachman Framework graphics v3.0 – what’s NEW? (blogs.icmgworld.com)
• John Zachman quotes on inherent complexity in running and managing enterprises (blogs.icmgworld.com)

There are several noteworthy changes in the new version which raises the understanding level and discards some of the existing myths and misconceptions. Moreover, this time the framework is aimed at the enterprise community in general and hopefully clears the cloud over the prevailing confusion about Enterprise Architecture vs. Enterprise IT Architecture.

While there are visible changes, it’s important to note that both “theory” and the “logic” of the framework remains unchanged. It continues to be a two-dimensional classification system – a “schema” consisting of communication interrogative (What, How, Where, Who, When and Why) and reification transformations (Identification, Definition, Representation, Specification, Configuration, Instantiation).

Here, is a list of 16 key visible changes in Zachman Framework graphics v3.0 compared to v2.0 (2004).

16 changes in Zachman Framework 3.0

#	Key changes	Description
	New graphic is subtitled, as “The Enterprise Ontology.”	Framework is ontology or the complete set of all the “elements” that exist in the Enterprise. It describes nothing about how Enterprise Architecture is done, it only defines the “science of what Enterprise Architecture is”… or the ontology.
2.	Horizontal integration lines ( across the cells)	Most obvious change is the addition of the “Integration lines” linking elements between the columns. This clearly establishes that integration exists between the Columns.This is also a serious problem, because many Enterprise Architects are building composite models and hard-binding multiple concepts together in their Architecture, rather than separating independent variables and then integrating the variables across each Row as and when needed.
3.	Vertical Integration Lines (Crooked transformation symbol), across the cells.	The vertical integration lines convey the idea of transformation when moving from the top to the bottom of each column. Now, it is clearer that the models of each row transform - they do not get more detailed.Please note that level of detail is represented in the height of each cell, i.e.: a high level of detail at the top each cell and an excruciating level of detail at the bottom of each cell. I will detail this idea in another blog post, hopefully by next month.
4.	Reification process down each column	The models in each cell are re-designed and transformed to the next Row below, and a complete Row 6 wraps up the 6th phase of reification. The six phases of reification are -Identification-Row 1, -Definition-Row 2, -Representation- Row 3,-Specification-Row 4,-Configuration-Row 5 and - Instantiation-Row 6),
5.	Audience perspective (label)	Audience perspectives have been labelled to attract the attention of General Management. The labels are: -Executive Perspective, -Business Management Perspective, -Architect Perspective, -Engineer Perspective, -Technician Perspective, -Enterprise Perspective
6.	Model Names (label)	The six models names (labels include) -Scope Contexts, -Business Concepts, -System Logic-Technology Physics, -Tool Components, -Operation Instances
7.	Classification Names ( label)	The 6 communication interrogative remains the same (What, How, Where, Who, When and Why)
8.	Enterprise Names (label)	The 6 communication interrogative  in enterprise context include-Inventory sets (Classification name is “What”)- Process Flows (Classification name is “How”)-Distribution Networks (Classification name is “Where”)-Responsibility Assignments ((Classification name is “Who”)-Timing Cycles ((Classification name is “When”)-Motivation Intentions  (Classification name is “Why”)
9.	Process Transformations (2004 version) changed to Process Flows	Based on the inputs from the business process experts, Column 2 name was changed from “Process Transformations” to “Process Flows”
10.	Network Nodes (2004 version) changed to Distribution Networks	The fundamental concept of this Column deals with distribution of resources as opposed to node addresses on a network.Column 3 was grossly misunderstood because of this terminology “Network Nodes”.Enterprise Architects often thought of this as point-to-point nodes and were not building their models correctly.
11.	Organization Groups  (2004 version) changed to Responsibility Assignments	The 2004 version confused quite a number of people with its title“Organization Groups”.As soon as Enterprise Architects saw this label, they incorrectly assumed: Organizational Chart – It is not so. This Column is all about responsibility; John aptly changed the meta-model to form the title “Responsibility Assignments” for Column 4.Some people often complained that the Framework doesn’t include ‘Customers’.  With this new title, it encompasses all the stakeholders of the business.
12.	Timing Periods ( 2004 version) changed to Timing Cycles	Column 5 changed from “Timing Periods” (2004 version), to “Timing Cycles”. This is better understood by the enterprise community.
13.	Audience perspective	Audience perspective moved to the LHS, earlier in RHS. Also, the labels are more meaningful
14.	Model names	Model names are moved to RHS; also the labels have been changed.
15.	Composite Integration	Earlier, people had this misconception that There is no integration exists between the Columns. Also, the concept of “primitives” and “composites” are not clearly understood.The fact is that the models of the Enterprise integrate horizontally.  Addition of the “Integration lines” linking cells across the rows brings the much-needed clarity on “primitive” and “composites”.  As you are aware “primitives” are single variable element within a cell. These single variable element within cell integrated with another single variable element of another cell resulting in a “composite”.It’s important to have independent variables and then integrating the variables across each Row to create composites. This ignorance has serious ramification, as several Enterprise Architects are building composite models and hard binding multiple concepts together in their Architecture making it brittle.
16.	Alignment Transformation	It’s important to note that the models of the Enterprise transform vertically. Each Row is different and is the result of a transformation, not a decomposition of detail.Most people who mis-represent The Zachman Framework as a “waterfall,” think that each Row represents another level of detail, i.e.: the highest level of detail at the top of The Framework (Row 1) and the most excruciating level of detail at the bottom of The Framework (Row 5). This is not the case at all. The models of each Row “ transform”  they do not get more detailed. In the reification process (down each column), an idea (or Scope-Row 1) has to go through 6 well-known phases in order to reach reality (Operations-Row 6). This is important to guarantee that the “reality” retains an alignment with the initial idea as it was conceived and designed.

 BTW, hope you are aware that “Enterprise Architecture” is comprised of Rows 1-5.  The instantiated Enterprise is represented in Row 6. 

My top 5 favorites are:

1. Focus on science of “Enterprise” i.e. “The Enterprise Ontology.”
2. Horizontal integration lines ( across the cells) which clearly establishes that integration exists between the Columns
3. The vertical integration lines which convey the idea of transformation ( phases of reification) when moving from the top to the bottom of each column
4. The new labels are meaningful and aimed at enterprise community in general
5. The framework cells are represented in white background so that we could easily comprehend the horizontal integration and vertical transformation among the cells

What’s your favorite?

 A passing note, every human being are different, yet follow a common structure (anatomy). Similarly, every enterprise are different, yet follow a common structure i.e. Zachman Enterprise Architecture. Like it or dislike it – but you can’t ignore it.

 Note: For the insight on the evolution of framework since 1984, please visit article by John P Zachman

Related articles

• John Zachman quotes on inherent complexity in running and managing enterprises (blogs.icmgworld.com)

It’s already 12 days since the New Year began. The need for managing change and demand for quick response to the ongoing challenges are mounting pressure on time and resource utilization. Though some of the disciplines like “management” (invented by Peter Drucker nearly 70 years back) and “enterprise architecture” (invented by John Zachman nearly 34 years) are handy, people around us make it difficult sometime .

 Time is one of the commodities which seem to be in the short supply. Unfortunately, I have not been regular with blogs in the last three months. Even though every week there are 2 to 3 very exciting ideas and problems that we get to work on, and every time I feel like sharing that with you, unfortunately lack of time and travel has prevented it. 

 It is exciting to know the way enterprise architecture has got prominence in the boardroom discussions. But, what is not exciting is the quality of the work being done. But, isn’t it very natural as both the people and the body of knowledge are evolving day by day.

 Last year, I had chance to spend good time with legendary John Zachman. We got to discuss several issues related to how the industry is preparing in response to the dynamics of economic uncertainty, created by ongoing changes. Those of you who have had the chance to interact with John Zachman will agree that every minute spent with him is enriching, inspiring. To start the New Year, I thought it is a good idea to put together some of the comments and the quotes by John Zachman.

JohnZachman

 The comments are from John and reflect his insight into Enterprise. There are 10 such quotes.  These quotes are related to issues like enterprise objective, status of “strategy” within the enterprises, the need for traceability across the enterprise structural elements, how does IT (Information Technology) people perceive enterprise objective, how does a CEO of an enterprise perceives IT, need for simulation to understand impact analysis, idea vs. instantiation, changing external environments, complexity management, what makes the enterprise dysfunctional, need for architecture and of course the idea of lean enterprise.

 Hope you will find these quotes very handy and will act as smart answers for some of the very difficult questions that your peers pop at you.

 Quotes by John Zachman :

1	Objective	Most people who come from IT today are thinking of building and running systems and not about engineering and manufacturing enterprises. My argument here is that the end objective is to engineer and manufacture the enterprise, not simply to build and run systems
2		Here’s what your typical CEO says to their IT team, “I have spent a lot of money in IT but I don’t think what you guys are doing with that money is in line with the plans I have for the enterprise.” When your CEO thinks this way, something is seriously wrong.
3		Architecture enables you to accommodate complexity and change.  If you don’t have Enterprise Architecture, your enterprise is not going to be viable in an increasingly complex and changing external environment!!
4		No one would knock down walls in a building indiscriminately without understanding the building architecture.  You could make apparently small changes and the whole building potentially could collapse.  Similarly, you could make apparently small changes to an enterprise and if you didn’t understand the Enterprise Architecture, the apparently small changes could potentially render the whole enterprise dysfunctional.”
5		We can simulate performances of airplanes in 3D, why can’t we do it with enterprises?  This is where we should be heading – a stage where we can actually simulate how certain changes or decisions will affect the enterprise.
6		The problem is that the enterprise strategy is not clearly manifested … there is an inordinate focus on optimizing current performance at the expense of investing in the future.
7		Zachman Framework! Yes, it is a schematic representation of the various components in an enterprise and their relation with each other. These include inventory, network, process transformation, business concepts, etc. The framework also tells you how a change in any one component or artifact will affect other artifacts related to it.
8		The process of converting an idea into reality needs to go through a set of transformations – you must name it, define it, create the semantic constructs of the concepts, then you have to represent it; because you are dealing with engineering designs; specify it, based on the implementation technology, then you configure the tooling and then you instantiate the idea. That is, you need to go through this process IF you care that the instantiation bears any resemblance to the idea that you had in the first place.
9		Few enterprises today have descriptive representations that depict how the enterprise works. Therefore, change can only be accommodated by trial and error. As complexity and the rate of change increase, risk of trial and error increases. Architecture provides the structure to predict the impact of change, reduce the risk and maintain enterprise viability in a changing environment
10		Enterprise Architecture is useful in those areas which minimize general operating costs, change enterprise with minimum time disrupt to cost, and are able to dynamically adapt to demands placed on an enterprise by the external environment. Make it lean, mean and change it with minimal cost

How to use these quotes:

 This time I have chosen quotes of John which reflect on the inherent complexity in running and managing enterprises as well those which represents the Information Technology dilemma. You can go further and use these quotes to create “to do list”. Here, is summary table for easy reference.

Roles	Quotes	Remarks
If you are sponsor of architecture initiatives	#3,#4,#5	Prioritize your key driver for architecture initiatives
If you are a practicing architect	#7,#8	Understand what it takes to transform “idea” to “reality”
If just you want to enhance your  understanding	#9	What is Architecture?
CEOs, Business Heads of various industries	#6,#10	Why Enterprise Architecture?
IT folks	#1,#2	Hope we could change this perception in near future

 Please go ahead and download these quotes and use them as a reference. Also, you may like to include them in your presentation and education programs within your organization. These quotes are available for download in PPT, PDF and video. There is also a flip book created for these quotes. Of course, there is a mobile version as well, just in case you would like to browse with your smart phones. I hope you will like these quotes and enjoy sharing with friends and peers.

Wishing you a very happy and fun-filled 2012.

Winners 2011

The “Business Categories” consist of excellence in five key areas such as Business Process Management, Customer Oriented Business Models, Growing business in new territory or new service offering, Business Intelligence and Analytics, and Startups.

1. Business Categories

2. Enterprise (Business & IT) Categories

The “Enterprise (Business & IT) category” consist of excellence in 6 areas such as Transformation and Planning, IT Landscape Rationalization, Architecture Governance, Best Green Architecture, Acquisition and Mergers and Enterprise Architecture.

 3. Technical Categories

The “Technical Categories” consist of excellence in five key areas such as Future IT (Web 2.0, Cloud and other
emerging technologies), SOA Vision for Enterprise Services, IS Security Architecture, IT Service Management and Open Source Technologies.

4. John Zachman Award for Enterprise Architecture

The iCMG Architecture World 2011 John A. Zachman Enterprise Architecture award is bestowed upon Amar Kumar Pandey in acknowledgement and appreciation of his innovative employment of Enterprise Architecture concepts in Criminal Investigation:

Winner of the Zachman Award 2011 - Mr. Amar Kumar Pandey

• discerning and extracting elementary components (Primitives) of criminal events,
• creating and employing feasible scenarios (Composites) for analysis, evaluation and action,
• facilitating effective administration, management and deployment of Law Enforcement resources,

leading to efficient and successful identification of perpetrators and mitigating life-endangering threats to society.

5. iCMG Hall of Fame 2011

Winner of iCMG Hall of Fame for 2011 is Mr. Steve Towers, CEO of BP Group. A seasoned practitioner with over 30 years of hands-on experience, Steve is one of industry’s noted experts in Advanced BPM and Performance transformation. He heads the Research & Professional Services network within the BP Group.  Steve is a well-known,  coach, mentor and inspirational leader including author of 5 books.

Heartfelt, thanks to all the winners for contributing to the betterment of the world through their work.

Related articles

• 12 finalists striving in 5 Business categories for Excellence Awards (blogs.icmgworld.com)
• Here, are the finalists for the iCMG Architecture Excellence in Enterprise (Business and IT) categories (blogs.icmgworld.com)
• iCMG Architecture Awards – 2nd round of evaluation is going to be difficult for jury (blogs.icmgworld.com)
• What are the different award categories, nomination in multiple categories allowed? (sunilduttjha.wordpress.com)
• Key observations while going through the nominations for the iCMG Architecture Awards (sunilduttjha.wordpress.com)
• Oh My God! Enterprise Architecture is like thunder rolling down the mountain! (blogs.icmgworld.com)

• An Hon. Deputy Chief Minister & a Finance Minister who has become synonym with achieving results which other feel impossible and unthinkable
• Inventor of Enterprise Architecture, interestingly 70% of respondents of a recent poll by Gartner concurred that EA is critical
• Guru who coined the term “ BPM”, Business Process Management
• Director – IT of one of the major Telecom operator in India whose parent organization is a giant in Russia
• An IPS and IG Police who twice won “President’s Medal” for bravery and who served as IGP for Internal Security, Karnataka last year
• Chief Architect of a Oilfield services company and
• A practising architect, entrepreneur, aerospace engineer and CEO of one of the largest Architecture Services company (did I say, it’s “meeee”

First, in my list is the valedictory presentation by Mr. Sushil Kumar Modi, Hon. Dy Chief Minister of Bihar  on “Re-architecting the enterprise – Bihar Under Transformation . Ask this science graduate about the art of making a good budget that safeguards the interest of all stakeholders and pat comes the reply: You require a little bit of common sense and a lot of sincerity.

The most under-governed and underdeveloped state of the country (India), for the first time after Independence, is working out new development architecture. There are growth strategies, new ownership models, emphasis on industrialization, and adoption of new technologies in healthcare, agriculture and most importantly the participation of the millions of stakeholders in this re-architecting initiative.

You will agree that the grammar of governance is changing in Bihar. Let’s ask him, how did he calculate the ROI?

Introducing the living legend – John Zachman, the inventor of “Enterprise Architecture” discipline. The emerging discipline, which is revolutionizing the way we think “enterprise”. And as he quips “up until now, Enterprises have simply happened… somehow”. It would take another hundred years to have ENTERPRISES which are well architect.

Guess! what you would have asked if you would have met Sir Isaac Newton? Can you tell us what the application of your formula? There are good chances that he won’t have dreamt about application of his formulas, what was coming such as aircraft, satellites, mobile phones, etc.in 1600 century?

The key to complexity and change is ARCHITECTURE. And you won’t be surprised as you start your architecture journey why does “ Zachman Framework™” is the basis for Architecture. Also, if you know Zachman Framework, it’s easy for you to understand other 34 frameworks. Of course, reverse is not true.  

In fact, nearly 70% of respondents in a recent Gartner poll said that their primary focus for Enterprise Architecture during 2011 and 2012 will be on aligning with business, delivering business value or transforming the business. So, come meet this living legend whose honest work and a great vision is taking world by storm.

Be on time on 27^th morning for the inaugural keynote by John Zachman. BTW, don’t be surprised if you see an old fashioned OHP (Overhead Projector) in the conference hall.
Third in my list is Steve Towers who is the founder of the Business Process Group (www.bpgroup.org) a global business club (originally formed 1992) exchanging ideas and best practice in Business Performance Management, Transformation and Process Improvement.

Drawing on 2010-11 BP Group & iCMG industry surveys, Steve will  share with you the key global EA & BPM trends and industry evolutions from the last 12 months and the year ahead.

1. Key evolutions in the BPM EA corporate agenda: What are the market trends for programme development?
2. Emerging Next Practice, Techniques, Tips and Methodologies
3. How has the industry moved on: Onsite polling around your top investment and development areas for the next twelve months
4. Making a new resolution: Looking forward to the ‘must dos’ for the next 12 months
5. Outside-In: The Secret of the 21^st centuries leading companies – who are they and what are they doing?

Manoj Shrivastava who is Director – IT in MTS Telecom in India will discuss about what it takes to be “Innovative”? Most of the time, he has observed the confusion amongst managers and executives in the corporate world when differentiating invention and innovation. This key note address will first try to highlight the differences between the two terms and then move on the different types of innovations. Manoj will cover the ingredients which make an innovation succeed, and the organization culture required to build a successful innovation factory.

The second part of the talk will address on how the innovation principles can be applied by IT and Enterprise Architects to make innovation a way of life when making architecture decisions. Towards the end of the presentation, the speaker will try to cover the benefits the business can gain from IT architects who are innovators. This is the fourth keynote in my list.

The fifth keyote presentation is by Mr. Amar Kumar Pandey, IPS, IG Police who will share a case study about utilization of EA principles in Police Management.  In this presentation, he will discuss how a complex case was resolved by utilizing multiple views of Karnataka police service in southern range including the various policing processes, organizational structure, functional processes and information requirements as well the underlying technology infrastructure.

As the strategy takes an information led approach (instead of gut feeling) for realization of its goals, there is need to define the conceptual model for describing the organization’s operation. Defining an accurate and consistent representation for each of the above views is critical for solving the case in a short time frame (one week?).

As he says, “For me, Enterprise Architecture provides a formal structure and process by which the vision is conceived, planned, executed and monitored”.  While using the EA principles, how did he use his time tested practices such as short implementation cycles, high-bandwidth communication and continuous dialogues  between the various stakeholders and aggressive testing approaches were key in delivering the result on time.

The sixth keynote is by Jim Heaton  who is Vice President, Infrastructure & Operations Services as well as Chief Architect of IT, CITO/Baker Hughes. He will discuss about how to fast track creating an Enterprise Architecture Group. One of the key element in such effort is to Drive immediate BUSINESS value. Some of the challenges related to seed a team, mentoring, how to create rapid value, how to create pull (not push) demand, generate external recognition .

Let me also briefly describe my keynote presentation “How do you transform a Business Strategy to an IT implementation artifact?”. In a simpler way, if an organization wants to grow its revenue by say 10%, what’s impact on business service, underlying processes, roles and responsibilities, distribution across the departments, systems and applications, software components, IT infrastructure etc.

This question sounds simple but has a very complex underlying mappings, connections and transformations need with thousands of break points. The magnitude of problem could be understood by the fact that companies around the world are failing to align their business goals and IT investments. Efforts to align once in a year, is meeting with failure. Imagine if this alignment has to happen every 30 days?.

In order to realize the existing gap and the transformation efforts, we need to understand the various stakeholders, types of models, categories, connections and dependencies among these models which form the basis of any enterprise definition. In the beginning, one might feel the absence of relationship between a business objective and an IT implementation artifact. However, as we traverse the journey of transformation from strategy to business, business to systems, systems to technology, technology to implementation, etc., it brings out a very clear and obvious dependency across them.

Hope these 7 keynotes provide insight to the world of “doers” who are getting the work done, need not be very aligned to a specific school of thought or idea. But, what is common is the “experience” on the ground that they acquire and their inclination to make it a way of living and not something that they do just from 9 to 6.
As the dates for the summit is nearing, it also brings some changes in the agenda. Anyways, we are gearing with our best and I look forward to see you and meet you in person on 27July.

Related articles

• Nine CIOs and only one question – does IT Architecture matter? – join the panel discussion on 27th July. (blogs.icmgworld.com)
• Enterprise & IT Architecture World summit ,27- 28 July, in Bangalore – a city which is a first choice for many businesses (blogs.icmgworld.com)
• Dr. Sushil Modi, Dy CM of Bihar Live during iCMG Architecture World Summit to discuss Bihar Under Transformation (blogs.icmgworld.com)
• Oh My God! Enterprise Architecture is like thunder rolling down the mountain! (blogs.icmgworld.com)
• iCMG Enterprise & IT Architecture Excellence Award 2011 competition! (sunilduttjha.wordpress.com)