Skip to main content.

The Enterprise Map Priciples

The one page principle

The Enterprise map offers an tangible enterprise map to keep every one on the same page. A major challenge in Enterprise Architecture is the ambiguity of what is the Enterprise. The envision of Enterprise is different in every one's mind and they all on different page. Most of EA efforts are developed by people on different page without a visible Enterprise. As a result, it is difficult for EA to provide value. Enterprise map is the effort to visualize the tangible image of Enterprise for every one to be on the same page. The visible and tangible Enterprise Map is developed via collaborative effort where every one find their role in the Enterprise Map. It is not only an visible Enterprise map but also a tool to facilitate enterprise collaboration. Here are the links to my presentation.


1.0 INTRODUCTION

The Enterprise Topology is a complicate jigsaw puzzle without the picture on the cover and without the pieces in the box. It is an effort to see the unseen by rendering the picture-in-mind to an explicit picture.

1.1 A puzzle without the pieces

Unlike to a jigsaw puzzle which comes with all the pieces in the box, the Enterprise knowledge reside deeply in each individual. Some knowledge can be describe by words, some knowledge can only be describe by picture and some knowledge are subconscious. Knowledge transfer from each individual to Enterprise Topology is the initial challenge.

1.2 A puzzle without a picture on the cover

Enterprise is logical and invisible, each individual only touch one part of the enterprise. The only way to see the big picture is put the pieces together via reconciliation instead of insist on their righteousness.

3.0 LEVERAGE ON THE SENSATION OF JIGSAW PUZZLE

The Enterprise Topology approach leverage on the intriguing sensation of jigsaw puzzle. Anne D. Williams in her article on the Jigsaw puzzle – A brief history says :

Puzzles for adults emerged around 1900, and by 1908 a full-blown craze was in progress in the United States. Contemporary writers depicted the inexorable progression of the puzzle addict: from the skeptic who first ridiculed puzzles as silly and childish, to the perplexed puzzler who ignored meals while chanting "just one more piece;" to the bleary-eyed victor who finally put in the last piece in the wee hours of the morning.
Working on Enterprise Topology to render the logical and invisible enterprise big picture have the similar sensation to know what you do not know about the enterprise. The desire to find more information about the enterprise and the joy to know what you do not know and the add on value to share with the others has become very rewording for the architects. The difference is a jigsaw puzzle is only a game but the Enterprise topology is the fundamental of Enterprise Architecture.
All the jigsaw puzzle technique also applies. Most of technique in jigsaw puzzle follows the same pattern, people have created many different technique to solve jigsaw puzzle by organizing the pieces and using try and true method to put the big picture together. The puzzle of Enterprise Topology is solved in the same way by organize the enterprise information and put the pieces together with and try and true approach.



Building a jigsaw puzzle is a wonderful way to help your mind focus on a structured method of using problem solving skills. Enterprise Architecture can leverage on this method to establish the Enterprise Topology. It is a skill to be able to focus on a particular task and organize themselves so that completion of the whole is accomplished methodically and with greater ease. It allows one to develop structure and discipline in problem solving techniques. After all life itself is just a big puzzle

For a complicate jigsaw puzzle without the pieces, the first thing is to discover the pieces. In an enterprise, institutional knowledge embedded in the mind of different individual. Before composing the Enterprise Topology, the first thing is to discover the institutional knowledge from each individual. The Enterprise Topology approach learn from the story of stone soup to retrieve embedded institutional knowledge from different individual.


Solving the puzzle after a good night sleep.

During the night, the brain have the opportunity to organize and connect the piecies from what is learned in the day time to see the big picture




^ TOP

Posted on 06:06:13 by LEA - No comments

Enterprise Map approach

The Enterprise Map Framework

The Enterprise Map Framework lay out overall activitis to compose the Enterprise map. The vertical side list the Enterprise Map layers whcih does not only include the business architecture but also shows how business take advantage of automation systems.

The following Enterprise Maps framework describe the approach.

null




1. Enterprise Map Approach




LEA has developed the Enterprise Map approach to provide insight to holistic business architecture via collaboration and reconciliation. The jigsaw puzzle-like ideas in the Enterprise Map approach enable enterprise-wide participation. The Enterprise Map was developed by the author and has been used innumerous EA projects since 2003, effectively opening the door of EA to the business community.

Figure 9. Enterprise Map

The Enterprise map, an interactive graphical business architecture approach, is inspired by the folk story of Stone Soup [11]:
• the architect’s presents his/her perception of the enterprise to raise stakeholder curiosity;
• collaboration occurs, and contributions from the stakeholders are incorporated into the enterprise map;
• The architect reconciles the enterprise map, enabling stakeholders to see the true holistic business architecture;
• and stakeholders take ownership of the enterprise map, resulting in total participation and buy-in.




EA map templates


1. Mapping the business environment

In addition to the Enterprise itself, it is also important to show how the Enterprise interact with external organization. EA map reserve the bottom part to lay out the supporting organizations.

Enterprsie map


2. Mapping the Automation Environment

alignment mapping

3. Mapping interoperability


4. A iterative approach

^ TOP

Posted on 06:12:42 by LEA - No comments

Enterprise Map training

With a defined and repeatable approach, the EA professional can get training on Enterprise Map.


Enterprise Map semina

School traing

Enterprise Map as the EA 101 class.

Enterprise Map Interest Group





The purpose is to establish a repeatable Enterprise Topology methodology as the fundamental practice of EA

Enterprise topology is a fundamental element of Enterprise Architecture similar to geographical survey in traditional architecture and engineering. The capability to see the true Enterprise big picture is a unique EA discipline. Hopefully, the EA professionals will recognize the Enterprise Topology as the fundamental of EA discipline and become the bread and butter in EA practice.


Enterprise map is the methodological approach to see the true Enterprise big picture.

Enterprise topology is a methodological approach to see the true enterprise big picture. The only way to see the true enterprise big picture is through collaboration and reconciliation with total participation. The story of the blind men and elephant which point out the human nature of believing the part they have touched as the whole and suggest to see the true big picture with collaboration and reconciliation is a good lesson to learn.


Enterprise Topology approach pave the way for architecture buy-in

The Enterprise Maps approach does not only render the true enterprise big picture but also resolve the challenge of buy-in from the stakeholders which has been the biggest hurdle of EA practice. The collaboration and reconciliation approach establish partnership and pay the way for architecture buy-in. Enterprise topology take the stakeholder buy-in into account at the onset of EA effort rather wait to the end.

^ TOP

Posted on 10:29:02 by LEA - No comments

The Enterprise Map Framework

1. Establish a repeatable Enterprise Map approach

EA community must establish a repeatable method to stake out Enterprise maps. Composing EA map to see the true big picture is a unique discipline for Enterprise Architects. The EA professional must be able to put down the big picture in every one's mind on a large page of drwing to make it meaningful for every one. To become a disciplint, it is paramount to establish a repeatable approach for EA map to become a architecture practice rather than artistic work.


The Enterprise Map Framework

The Enterprise Map Framework lay out overall activitis to compose the Enterprise map. The vertical side list the Enterprise Map layers whcih does not only include the business architecture but also shows how business take advantage of automation systems.

The following Enterprise Maps framework describe the approach.

null

It describe that enterprise maps is composed in five stages:

.Archaology
.Straw man
.Colaboration
.reconcileation
. buy-in

Enterprise Maps is composed in the following layers.

. Enterprise overview which include concept of operation, value chain, organization chart and geographical map.
. Enterprise floor plan
. Business activity
. Business Application
. Enterprise Context

The following paragraphes elaborate the stages of enterprise maps and the Enterprise maps layers.

2. ENTERPRISE MAP LAYERS

The following paragraphes describe the Enterprise Map layers which include the business architecture layers and illustrate how business taking advantages of technology evolution.

2.1 Enterprise maps overview

Enterprise maps describe the enterprise from the aspect of mission, function, processes, organization, location and demand as shown in the following business architecture model.

2.2 Enterprise floor plan

The enterprise maps describe the enterprise automation environment to show the application systems used in business processes, the data associate to the applications and the technology used by the application systems as shown in the following EA model.

2.3 Enterprise Functions

2.4 Enterprise proces


The Alignment Architecture

The alignment architecture is the effort to align solution to business need. The summary from Enterprise Architecture Alignment Heuristics by Pedro Sousa in Microsoft Architect Journal says:


2.6 Enterprise context


The next thing people want to know is “How you do it?”. EA map identify the work flow between each room and the high level business process in each room. In addition to business function and process, people become curious on the automation system in the enterprise. It is similar to the furniture in the house. EA map use the bubble icon to represent application systems used in the business process along with associate database. EA map present technology with technology patterns in different color as specified in the legend.

3. THE STAGES TO FACILIATE COLLABORATION

Enterprise maps is a complicate puzzle without the picture on the cover and the pieces in the box. It is not possible to compose the Enterprise Maps without collaboration and reconciliation to transfor institutional knowledge and see the trure Enterprise big picture. It takes four phases to compose the Enterprise maps with total participation, collaboration and reconciliation.

3.1 Archaeology

Apply Archeology skill to dig out existing documents can save significant redundant effort. Existing architecture documents are the low hanging fruit to pick. During the practice of software engineering in the past two decades, organization have written tons of architecture documents. But it is also true that all these documents have disappeared as the time have past. However, very likely it is buried somewhere in the organization and it take archeology skill to rediscover the treasure of existing documents.

3.2 Straw man

The ideal is to intrigue their curiosity first by preparing the draft EA map. The Enterprise Architect most do their home work to prepare the draft EA map to show demonstrate their sincerity in knowing the Enterprise. Do not worry about making mistake in the draft. It is a human psychology that people start to dump out their hidden knowledge when people think they know better than you do.

3.3 The Collaboration

The collaboration phase collecting institutional knowledge from each individual. Institutional knowledge is not explicit, most of enterprise knowledge reside deeply in each individual and the knowledge varnished with their departure, the challenge is how to retrieve the hidden knowledge for every one to share;

3.3.1 Print the draft copy prepared for collaboration.

Despite the technology evolution, the human specie has not evolved much in the last couple thousand years, the hard copy still the best for human interaction to compose the big picture, induce the hidden institutional knowledge and enable reconciliation over the true enterprise maps. As much as we want to get rid of paper in the information age, the Enterprise Maps approach has found that hard copy still serve as the practical instrument to compose the Enterprise maps because human is still human.

3.3.2 Business liaisons to communicate with business community

3.3.3 The collaboration meeting

3.3.4 Posting for public review

Post the drawing in traffic area and request to mark up on the drawing.

3.4 THE RECONCILIATION STAGE

3.5 Establish partnership and ownership

With the total participation approach, the stakeholder take the ownership to present the Enterprise Maps to their colleges.


^ TOP

Posted on 04:32:01 by LEA - No comments

What is Enterprise Map?

Enterprise Map Training


A identity and low hanging fruit of EA

Enterprise Map is a graphical EA approach to enable the Enterprise on architecture drawing similar to the traditional architects. The result is a tangible Enterprise Architecture which is intuitive for every one to comprehend. Enterprise map is the light Enterprise Architecture approach compare to the heavy duty effort of complicate enterprise modeling and analysis. Enterprise map is the tip of the Enterprise Architecture iceberg which provide an tangible EA and lead industry to the massive enterprise knowledge. The Enterprise map does not only establish the identify of EA but also a low hanging fruit of Enterprise Architecture.


The Enterprise map visualize the

. Business layer
. The application layer
. The data layer
. The technology layer.

Enterprise map the As-is environment and the target environment.

Enterprise map method does not only used to map the As-is environment but also the target enterprise environment. Initially, it is used to plan the target IT environment, in a advance EA approach it is is also used to transform the entire business.


What is an Enterprise Map?

Enterprise Map renders the holistic Enterprise business and automation environment for every one to comprehend. To know an Enterprise people like to know :

What you do?
Who are you?
What you do?
How you do it?
Where are you located?
What is your organization look like?
The organizations around you?
Your automation environment?

The Enterprise Map takes all the frequent ask question about the enterprise into account and orderly arrange them in an one page approach as shown in the following figure which also serve a the reading guide for an Enterprise Map.





Enterprise Map provide the enterprise business overview with location, organization, concept of operation and value chain to introduce the Enterprise at a holistic and high level overview; To address the question of what you do, the Enterprise Map lay out their business function similar to a floor plan, it is not just a function list. The business floor is the framework of what they do.

The next thing people want to know is “How you do it?”. EA map identify the work flow between each room and the high level business process in each room. In addition to business function and process, people become curious on the automation system in the enterprise. It is similar to the furniture in the house. EA map use the bubble icon to represent application systems used in the business process along with associate database. EA map present technology with technology patterns in different color as specified in the legend.

In addition to the Enterprise itself, it is also important to show how the Enterprise interact with external organization. EA map reserve the bottom part to lay out the supporting organizations.

Enterprise Map is not process centric

Enterprise Architecture is not business process centric as the Enterprise Map approach by Burton, Herbert O, Pennotti, Michael C.. Business process modeling and optimization has been the major concern in the information age of automation. However, it takes more attributes than business process to define an Enterprise. The popular Zachman framework describe the Enterprise from the aspect of What? How? Who? When? Where? and Why?

Give a second thought, business processes realy do not define Enterprise, they are the process solution to support enterprise business goal rather then the definition of an Enterprise. We all know that business process must be reengineered to take advantage of technology evolution.

Enterprise Map become sensitive information

The Enterprise should secure their Enterprise Map, although the Enterprise Map can be created from many pieces of non-sensitive information, but "The sum is much greater tha parts", by putting together the non-sensitive information in the proper order, it will become sensitive information to the enterprise.

WHAT IS NOT Enterprise Map?

Enterprise Map is not a business process or activity model Enterprise Map is not a conventional business processes or activity model in the traditional EA. The application development trained IT professional have been business process centric and more likely to confuse EA topology with business processes or activity model. The EA topology describe the enterprise mission and definition rather than business process model.

Enterprise Map is not the enterprise inventory EA map is very different from inventory the exiting environment. EA map is a mapping effort to orderly arrange all the parts and map the overall relation to render the enterprise big picture. The wikipedia describe that the word inventory was first recorded in 1601. The French term inventaire, or "detailed list of goods," dates back to 1415. Inventory management is primarily about specifying the size and placement of stocked goods. Inventory management is required at different locations within a facility or within multiple locations of a supply network to protect the regular and planned course of production against the random disturbance of running out of materials or goods.

Enterprise Map is not art work EA Map is not only a pretty picture or a piece of arts as many people suggested. The EA community must establish a repeatable Enterprise Map approach which will become a major discipline of Enterprise Architects in the say way as the discipline of Engineering survey. EA is an emerging discipline, the capability to develop enterprise map distinguish Enterprise Architects from other discipline.

The Enterprise Map Framework

The Enterprise Map Framework lay out overall activitis to compose the Enterprise map. The vertical side list the Enterprise Map layers whcih does not only include the business architecture but also shows how business take advantage of automation systems.

The following Enterprise Maps framework describe the approach.

null
^ TOP

Posted on 18:27:54 by LEA - 19 comments