EA IN TWO POSTERS
Light EA render the overwhelming Enterprise Architecture in two poster for total participation, the poster serve as the tip of EA iceberg to open the door to the profound enterprise architecture world. EA come with the notion of profound and intimidating in complicate computer models and volumes of heavy documents. It can be as simple as two poster for all level of stakeholders. To satisfy the above principles, LEA have developed the Enterprise Map to visualize the enterprise and see the whole in an intuitive poster approach. 20% effort to deliver 80% EA value
A tangible Enterprise Architecture
The purpose of Enterprise Map is for every one to see the enterprise architecture 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.
Compiled from popular EA diagrams Instead of reinventing wheel, Enterprise map leverage on popular architecture graphic. EA community have adapted popular diagram such as the concept of operation , value chain , business capability map , information landscape , and node connectivity diagram location map , organization chart  separately as the graphic presentation embedded in heavy volumes of architecture documents.
Enable every one to see the enterprise big picture
Enterprise map enable every to see the whole and visualize the enterprise via value chain, organization chart, location map, business capability map, and information land scape and external connectivity diagram as shown in the following framework. The EA community have make effort to visualize the enterprise separately from the aspect concept of operation, value chain, activity modeling, business process modeling, organization chart, location map, business capability map, information land scape and connectivity diagram. By doing so, the audience only visualize a part of the enterprise without see the whole. In the pass, EA relies on activity modeling and business process modeling to visualize the enterprise. It ends on creating expensive wall paper.
One page concept
Enterprise map enables the reader to comprehend the conopt, value chain, business capabilities, organization, location on one page . On the enterprise map, all these graphic are developed interrelated rather than separately. Value Chain is constructed based on mission statement; Business capability elaborate the value chain; Information landscape is derived from the business capabilities; Organization Chart is designed to support the business capability; Business locations are selected based on business capability. The whole is much greater than the sum of it parts.
The whole is much greater than the sum of its parts. Individually, each diagram is only a graphic in a document. However, putting this diagrams together on page from the aspect why, what, how, who, where and when have constitute a powerful enterprise to visualize the Enterprise Architecture. The whole is much greater than the sum of its parts.
Enterprise map was initiated in 1999 to mitigate the risk Year 2000. The enterprise map have serve well to see the whole. It is essential knows what do they have to protect from the risk of year 2000 yet most of organization only knows the parts without a artifact to see the whole. The first version of Enterprise Map is the visualization of enterprise for every one to comprehend the enterprise from the aspect of Why? What, How, Who, Where, When. It does not only describe the enterprise business but also shows how business take advantage of technology evolution via the EA layers of Application, Data and technology. This version of Enterprise Map relies on activity modeling and can be very overwhelming as shown in the following figure.
SEE THE WHOLE TO CONSTITUTE ENTERPRISE ARCHITECTURE
EA can be as simple as two posters.
Most of Enterprise Architecture approach talk and think about the whole without visualize the whole.
Describe the enterprise business
Enterprise map describe the enterprise not only from business capability but also from the aspect of stake holders, business value, business concept of operation, organization, location and business context of connectivity and interoperability. It describe the enterprise coherently by identifying the business stakeholders, establish the value chain, understand the concept of operation and model the business capability accordingly. On the foundation of business capability map, It enable the business to take advantage to automation and identify the enterprise information resources. The simple concept of operation and value also serve as a guide for readers to understand the complicate business capability map.
Business Capability instead of business processes
Enterprise map adapt business capability map to describe what is the enterprise. Business capability describe what enterprise do and business process describe how. Although EA , which have evolved from application development, has been very business process centric before. In application development paradigm, business processes drive automation development. The EA community have learned that business processes are the process solution to support business capability, it is not part of the business definition. Business processes subject to reengineering and localization. Business process must be reengineered to take advantage of technology evolution and it also subject to localization due culture difference. Business capability map clearly define the capabilities of an organization. On the other hand, business processes modeling can be overwhelming and lead to paralysis of analysis"
The Enterprise Topology method is established based on the discussion in last chapter on the Enterprise Topology principles which consider Enterprise Topology as a complicate puzzle without the picture on the cover and without the pieces in the box. It is a challenge to render the Enterprise big picture which is a picture in mind of many different people. It is a task of how to read the picture in mind. The Enterprise topology method leverage on popular and meaningful folk story of the stone soup and the blind man and the elephant to establish the approach in rendering the large, logical and invisible enterprise big picture. For the Enterprise big picture, every one only have partial image in mind, the challenge is how to read the partial image in different individual’s mind and render the true enterprise big picture explicitly for every one to comprehend.
<b>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. </b>
It does not serve well by sending out many survey form and conduct site visit, there is a goog chance of gathering bias information or talking to the wrong one. Usually, people who knows are too busy to talk. To prepare the logical and invisible Enterprise map, the Enterprise Architect must prepare their homework to kown the preliminary enterprise information.
1.0 Why Enterprise architecture map?
EA map was initially developed to support the Enterprise Architecture practice. It is a business centric discipline on how business take advantage of technology evolution, rather than a technology centric approach to design enterprise scalable solution. For example: Application Architecture in EA means how business leverage on automation solution rather than how to develop an enterprise scalable application. In analogy of automobile industry, it is a matter of now business take advantage of different type of automobiles rather than how to make the cars. In EA, it is essential to know the enterprise in order to take advantage of technology evolution from enterprise wide consideration. However, the architecture oriented EA community have focused on the word of “Architecture” and have overlook the key word of “Enterprise”.
Although, EA map is developed to support Enterprise Architecture, it is also found useful for all enterprise wide initiatives such as Enterprise Strategic planning, performance measurement , security management, risk management and capital investment.
<b>Enterprise map enable enterprise strategic planning, business architecture, alignment architecture, agility architecture and management architecture as shown in </b>
<%image(20090426-cea value.JPG|451|336|cea value)%>
The value of EA map can be best describe in article of Enterprise Map by Burton, Herbert O, Pennotti, Michael C
<a href=”http://findarticles.com/p/articles/mi_qa5394/is_200309/ai_n21337778/”><b>Enterprise map: A system for implementing strategy and achieving operational excellence in Engineering Management Journal , Sep 2003 </b></a>. They suggest that:
“This article describes how senior leaders can use the tools and techniques of systems analysis to develop a top-level process architecture that identifies the key processes of a business and specifies the critical interconnections and interrelationships between them. We call this top-level architecture an enterprise map and we believe it represents an important addition to a senior management toolkit, complementing other popular, performance-enhancing tools like process maps (Eckes, 2001) and the balanced scorecard (Kaplan and Norton, 1992).”
The difference between Enterprise Map and the Enterprise Architecture map is that EA map is not a business process centric, it map the enterprise from the aspect of the enterprise value (Why), Enterprise function (What), Business process (how), Organization (Who), Location (Where) and demand (When). In addition, the EA map also identify the Enterprise automation environment. Business process alone do not fully define the enterprise. Here are the reasons why EA map:
- EA map define a tangible Enterprise.
- Overcome the reputation of “stealth EA”.
- EA map to render the true big picture.
- EA map as the instrument to preserve institutional knowledge
- EA map is the tool to enable creative architecture design with visual reference.
The following paragraphs further elaborate each justification.
1.1 EA map to define a visible and tangible Enterprise.
EA map define a visible and tangible Enterprise map for stakeholder to comprehend. On the EA map, every one can find their places. A frequent asked question in Enterprise Architecture is “what is the Enterprise?”. Unfortunately the EA practice do not have any thing to show what is their Enterprise either. Many EA experts try to answer this question by saying Enterprise means everything; or cite the dictionary by saying enterprise is a business or company . The truth is that they are not very sure “what is Enterprise” either because EA community have put more attention on “Architecture” and overlooked on the need to have a tangible Enterprise.
A major part of architecture practice is missing in the EA practice which may be the essential reason for EA to be “Stealth” and lack of practicality. The EA community have forgeten about the architects most important partners, the Engineering surveyors. City planners, Architects and Civil Engineers are trained not only on architecture but also in geographical survey and they know that geographic map is the foundation. Enterprise Architecture, as a architecture discipline, does not have any exception either.
The first thing of Enterprise Architecture is to define a visible and tangible Enterprise topology rather jump into architecture design. It is futile to design a building without topographic map, it is also futile to EA without the Enterprise Map. The EA community, trained in architecture, have not yet realize that Enterprise architecture must define a comprehensive Enterprise Map to constitute a practical EA. They have forgotten to look EA from the analogy of engineering surveyors. Even the very popular EA approach such as The Open Group Architecture Framework (TOGAF) is very architecture oriented. They have forgotten about that architects relies on engineer surveyors work.
Many EA approaches have using the City Planning Metaphor. For example: In TOGAF 9, Wolfgang Keller said :
”An Enterprise Architect as the CIO’s city planner has to deal with almost any group of stakeholders in a company, be it senior management, be it groups of stakeholders in a company, be it public agencies the likes of a SEC (Security Exchange Commission) or agencies that deal with data protection, and last but not least those groups who want a new application. As these tasks have some similarities to city planning , the profession of Enterprise Architecture has sometimes to adopted that term for their occupation. “
It is a great description and along metaphor, we should not forget about that architects need surveyors. We all know that City planners, building architects, civil engineers relies on geographic map and topology. It is not too late for the EA community to realized that have missed a fundamental part of Enterprise Architecture which is the Enterprise Topology. “Enterprise” is the key to distinguish EA from system architecture. A system architecture is design to address a specific set of requirements which is much in a vertical solution. On the other hand, EA is architecture with enterprise wide consideration which is much in cross cutting and horizontal aspect. EA without a defined, visible, tangible Enterprise topology will not be very practical and meaningful and may subject the same fate as many other business improvement effort.
1.2 EA Map to overcome the reputation of “Stealth EA”
Enterprise Architecture is known to have the reputation of “Stealth EA” because not many people can see it. EA map render the Enterprise Topology which make Enterprise visible. In the real world, many times when the supportive senior managers make the effort to advocate EA, what they have found is some Power Point presentation, volumes of documents and complicate repository and reports. They are frustrated and have second thoughts about EA until they come to the exhibition of EA maps. The human considerate EA map have served as the portal to lead the senior managers into the world of EA. It has become their showcase of EA to the business community.
“Stealth EA” does not serve well to earn buy-in from stakeholders neither for the EA professionals. Buy-in from stakeholder is the major challenge of EA, however, it is understandable that stakeholders do not buy-in on something they can not see. The doubt of EA increases without a tangible Enterprise. For the EA professional, “Stealth EA” failed to present the EA professional’s hard work and justify the significant investment of EA.
1.2.1 Mapping instead of writing about Enterprise
A picture is worth a thousand words is a popular saying to present information in picture rather than writing. It refers to the idea that complex stories can be described with just a single still image, or that an image may be more influential than a substantial amount of text. It also aptly characterizes the goals of visualization where large amounts of data must be absorbed quickly
In traditional city planning and architecture practice, the architects have figure out long time ago that they need to communicate with stakeholders with architecture drawings instead of writing in large volume of documents. It will be very difficult to comprehend home’s architecture design if the architects deliver the architecture design by writing large volume of large documents.
However, EA community have not quite embrace the ideal of “A picture is worth “ a thousand words. EA products are frequently delivered in large volume of documents which is only good as shelfware for display purpose. EA has become a technical writing effort rather than and architecture practice. EA professional are “Profound”, on one hand they think in many dimensions to be profound, yet they convey their work in the very basic form by writing about the Enterprise and the Architecture. The two sides do not match.
As an improvement to the EA shelfware, many organizations have made significant investment on complicate EA repository which do not help much on the challenge of “Stealth EA”, It bury the EA artifact inside the repository which requires significant training to navigate. EA repository is frequently acquired on the justification to support senior manager on impact analysis and decision. In the history, leaders always look for decision support capability making ranging from Oracle reading to fortune telling and the complicate EA repository. Unfortunately, the fortune tellers are the one to get executed when they makes wrong prediction. The impact analysis and decision support capability is only as good as accuracy of EA model from the true big picture. Hopefully, EA professional do not follow the same fate as the others.
1.2.2 Resolve “Stealth EA” via understanding human biological and psychological limitation
to communicate with human and overcome the challenge of “Stealth EA”, it is important to understand human capability in comprehending information.
In A Strategy to Avoid Information Overload by Richards, C.E. (1987). Roles: Central Issues in Anthropology, 7(1), 9-12, indicate that
<a href=”http://library.humboldt.edu/~ccm/fingertips/overload_bib.html”>The information overload bibliography from Humboldt state university library </a>
“The research makes it clear that (a) the human brain is limited in its ability to process data, (b) the limitation is not susceptible to training, and (c) it is approximately the same for all humans.
EA in large volume Architecture drawing Communication to people subject to the nature human limitation in comprehending information. It is very different to device and device communication where the communication technology evolved rapidly. In the design of EA communication to stakeholders, It is important to understand human limitation in comprehending overwhelming information. “
The Magical number of seven by Miller, G.A. (1956). The magical number seven, plus or minus two: some limits on our capacity for processing information. Psychological Review, 63, 81-97. (Full text of this article at The Magical Number Seven.)
“Human beings have severe limitations on the amount of information they are able to receive, process, and remember. Their “span of immediate memory” or “channel capacity” is limited to approximately 7–plus or minus two– items. Through recoding items so that information to be remembered is placed in larger “chunks,” it is possible to expand this channel capacity somewhat.”
EA Map render the enterprise from the six aspect of why, what, how, who, where, when An Enterprise is not only large but also complicate, ideally an enterprise should be presented and described in many dimensions which become large volume of documentation. However, with the consideration of human factor, EA map render to Enterprise only based on the aspect of why, what, how, who, where and when.
1.2.3 EA map leverage on the wisdom Architecture Drawing
The traditional architecture drawing may appears to be too low-tech for the profound EA professionals. It has been used for thousand years to communicate architecture artifact with human consideration. Although, technologies have evolved rapidly in this century, human kind have not biologically evolved much in the past thousand years. People still can not comprehend thing which is too large , too small and thing that is logical. The architecture/engineering drawings are developed to accommondate human capability to comprehend architecture information
The one page concept Architecture drawing use large drawing size such as the ARCH size D (36” X 24”) to contain significant and meaningful information in one place via graphic presentation. By putting significant information in one place in a meaningful presentation can result the effect of the sum is much grater than the parts. Pieces of information many not says a lot, but putting it together, the one page drawing says more than volumes of documentation. The standard architecture drawing page is established based on human factor. It is large enough to contain signification information but not too large for human comprehension. The sum is much greater than parts. Enterprise Map is an effort to collect the enterprise parts and orderly arrange the parts to see the big picture of the enterprise. In the logical and invisible enterprise every one only touch parts of the Enterprise and the parts of institutional knowledge only reside deeply inside each one mind. The Enterprise Map method is designed to collect the Enterprise parts and put it together in an orderly arrangement. By putting together the big picture, one can truly realize the expression of “The sum is much greater than the parts”.
The architecture drawing set The one page concept is to render the different parts in one place to render the big picture. It does not limit the architecture to further elaborate each part of the enterprise. Traditional architects delivers architecture drawing set rather than one big picture. EA map also deliver in EA map drawing sets to elaborate the high level enterprise big picture. The key is to see the enterprise big picture first and elaborate the detail accordingly.
1.3 EA map to see the true Enterprise Big picture
EA map is the effort to render the true Enterprise big picture with collaboration and reconciliation from stakeholders. “not seeing the forest for the trees” The expression of which means something like “he’s seeing the details but not the overall picture” or, “he has all the facts but can’t put them together so they mean something”.
“Knowing in part may make a fine tale, but wisdom comes from seeing the whole” is the conclusion from the book of seven blind mice by Ed Young says that The book is a retelling of an old tale by ED Young, It is about seven mice go to the pond to find out what an elephant looks like, and each come back with a different answer. Although it is a children’s book , the conclusion means probably more for parents then children.
See the big picture enable critical thinking which consists of mental processes of discernment, analysis and evaluation. It includes possible processes of reflecting upon a tangible or intangible item in order to form a solid judgment that reconciles scientific evidence with common sense. In contemporary usage “critical” has a certain negative connotation that does not apply in the present case. Though the term “analytical thinking” may seem to convey the idea more accurately, critical thinking clearly involves synthesis, evaluation, and reconstruction of thinking, in addition to analysis.
The challenge is “what is the true Enterprise big picture?”. For the EA community, it is preaching to the choir saying “to see the Enterprise big picture”. The real problem is “What is the true Enterprise big picture?”. Enterprise is large, logical and invisible, no one can really comprehend the Enterprise big picture by themselves. The scope of Enterprise is very uncertain in the EA practice, every one see the enterprise differently based on the part they have touched and also insist their righteousness. EA does not evolve as expected due to the iffy enterprise definitionIt is difficult to constitute an enterprise architecture without know what is the Enterprise. After more than ten years, the EA practice has not evolved as expected. EA will not be practical without the capability to see the a true Enterprise big picture.
To see the logical and invisible Enterprise, the blind man to see the big elephant. The story is about six blind man want to know what is a big elephant. It is not unusual that people only believe what they have seen or touched. So each person comes with different perception of the elephant from the part they touched. The story taught us to see an invisible big picture via collaboration and reconciliation. Where People collaboratively put all the parts on the table and reconcile to put the part together and become meaningful. In a true enterprise big picture, every one can find their place and the parties they interact with.
EA map to render the true enterprise big picture learn from the story of blind man and elephant to see the enterprise big picture by lay out all the parts on the EA map drawing and orderly arrange the parts to be meaningful via reconciliation. EA map offer an visual reference to actually put down the picture that very one have in mind. notice there is big gap between the picture in mind and the picture on the drawing. In the practice to put down the picture in mind on a piece of paper, Put the picture in mind down on a piece of paper is the way for many people to clear up their mind. The picture in mind would not become clear until you are able to put it down on a piece of paper.
The gap between picture in mind and picture in drawing Reconciliation in words frequently subject to miss interpretation. Render the picture in mind on the paper enable visual communication between different perceptions of and achieve the reconciliation with clear understanding. Without the picture, communication in word subject to individual interpretation.
1.4 EA map is the instrument to compose the big picture
EA map is not only a big picture but also an instrument to compose the big picture.
Unlike geographic survey which physical, it can be measured with survey instruments or taking picture from air, Enterprise is large and logical, no one can directly see the entire Enterprise big picture. EA professional need an instrument to render the Enterprise big picture.
Documenting “As-is” is not a no-brainer effort. EA professional have put all their effort on “Architecture” and consider documenting ‘As-is “ is a no-brainer effort with the assumption that it is existing therefore it do not require effort to comprehend. some EA professionals thought. The problem is that there are many thing out there but not visible to human due to biological limitation. It is human limitation that they are unable to see things when it is too large or too small. Trying to document the logical and invisible enterprise asking around with data call, survey form and conduct site interview do not serve well either.
Comprehend the as-is big picture requires special instrument Geographical survey has been a major effort in human history to know the surface of Earth. From the Wikipedia, Surveying or land surveying is the technique and science of accurately determining the terrestrial or three-dimensional space position of points and the distances and angles between them. Surveying has been an essential element in the development of the human environment since the beginning of recorded history (ca. 5000 years ago) and it is a requirement in the planning and execution of nearly every form of construction. Its most familiar modern uses are in the fields of transport, building and construction, communications, mapping, and the definition of legal boundaries for land ownership. In the same token, EA community must also recognize that EA also establish an approach to comprehend the Enterprise big picture rather than just talking about architecture. Unlike the physical topographic map, the surveyors can use many different instruments to locate, level, connect and measure the points. The Enterprise topology is logical and invisible.
The initial EA map is the instrument to compose the Enterprise big picture. Unlike the physical topographic map, the surveyors can use many different instruments to locate, level, connect and measure the points. Most of institutional knowledge embedded in each individual. the challenge is how to induce the embedded institutional knowledge and put the part together to become meaningful. EA community need to establish a different instrument to see the Enterprise. The EA map adopt the approach from the old story of Stone Soup which is about how two hungry solders get food from villagers by raising their curiosity with pot of water and some stone. They know very well that they will not get much by asking food directly from the villagers. Current EA approach gather the enterprise knowledge in a direct approach by send out data call, survey form and conduct site interview.
The initial EA map started as a simple framework without significant content for the purpose to raise the stakeholders curiosity in the same way the solders have done to set up a pot of water and make the soup with some stones. The problem is that people with knowledge are too busy to talk and people who have the time to talk may not have the knowledge. Most of people are not good to describe what they do directly. Asking a person to tell you what they do, frequently get the answer of “Nothing”.
In the Stone Soup story, the solders understand human psychology, to get hidden food, the first thing is to raise the villagers curiosity by set up a pot of water and staring the fire. The second thing is leverage on the human nature of showing off they know better. Looking at the solders make soup with stone, the villagers feels that they know better in making soup.
Enterprise Architects must understand the human psychology too. The initial EA map with limited Enterprise knowledge or wrong information prompt the viewers to show off that they know better and begin to teach you what is right on the drawing by dumping their institutional knowledge. This approach work even better when multiple people dumping information on the EA map. The EA map become the instrument to provide visual reconciliation and gradually turn out the true big picture of the Enterprise. By working together, the Enterprise Architects have also address the challenge of buy-in from stakeholders.
EA professionals must do their homework to know the enterprise. The caveats is that the architects must do their homework to establish some credibility on the initial EA map to raise the stakeholders curiosity rather than turn off their interest. Although it is important to know the enterprise by asking the stakeholders, There is really nothing new under the sun. Enterprise Architects establish the initial EA map by reading existing documents and use patterns from the similar line of business.
<b>EA professional must be trained to map the Enterprise </b> Traditional Architecture and Engineers are all trained in engineering drawing and geographical survey. So does the EA professional must also be trained in mapping the Enterprise. As a matter of fact, the capability to map the enterprise and render the Enterprise big picture is unique discipline which distinguish EA professional from the other architects. EA professional are not Mr. know all, they are trained to see the big picture of the Enterprise and architect with enterprise consideration.
1.5 EA map is the tool to support creative architecture with visual reference
EA map enable visual architecture effort on the drawing board as the building architecture do. Visualization is a critical factor in architecture effort. The problem of EA is too much talking, too much thinking but lack of the capability to put it on an architecture drawing to pin down the architecture concept and communicate with stakeholders. It is not unusual for an architects to have all kind ideal and concept but unable to put down the ideals on a piece of paper and orderly arrange the parts.
<b>Supporting Creative Architecture Design with Visual Reference</b> <a href=”http://code.arc.cmu.edu/dmgftp/publications/pdfs/hi95-mdg.pdf”><i>Drawing Analogis -Supporting Creative Architectural Design with visual reference</i></a> by Grossm M and E. DO in 3rd International Conference on Computational Model of Creative Design suggest to develop tools to support creative design in architecture.EA map is consider as the tool to support creative design in Enterprise Architecture. The article suggest that
By ‘creative design’ we simply mean design in which neither the solution nor an algorithm to achieve the solution are immediately obvious, in which the designer must determine an initial set of concepts as a basis for design development. Among accounts of human creativity (e.g. Boden (1990), Koestler (1964)) several processes are frequently described: 1) combining ideas from different domains; 2) the use of visual imagination, metaphor, and analogy, and 3) expanding and varying the search space of alternatives.
<b>EA map enable Combining ideas from different sources</b> An often mentioned source of creativity is the combination of ideas, or as Koestler termed it, “bisociation” (Koestler 1964). Creative ideas are derived by combining borrowed ideas from other domains with the problem at hand. For example, Koestler describes Gutenberg’s invention of the printing press as combining the idea of seals used to press letters into wax with a wine press to print many letters simultaneously onto paper. Accounts of creative architectural design are replete with borrowing and adapting forms from other buildings as well as from natural and human artifacts.
<b>EA map enable creative architecture design Visual metaphor and analogy</b> EA map enable the Enterprise Architect in process reengineering, design sharing and consolidation via identify stove pipe and redundant systems, opportunity to take advantage of technology evolution, obsolete solution,
In many accounts of creative acts visual metaphor or analogy—‘seeing as’ — plays a key role, for example Kekulé’s seeing benzene’s carbon ring structure as a snake biting its tail, or Faraday’s seeing the universe as patterned by “lines of force,” which led to the electric motor (Koestler 1964).
The value of Enterprise Map:
. See the true whole . To visualize the logical and invisible enterprise. . Tangible Enterprise Architecture. . Facilitate collaborative culture. . Describe as is. . The skeleton of enterprise knowledge management. . Plan for the future.
http://www.liteea.com/nucleus3.24/nucleus/images/button-link.gif “Enterprise Architecture” is more than “Architecture”, the difference is “Enterprise” and it supposed to be the main subject of EA. However, EA community tend to jump into their confortable area of “Architecture” and overlook the main subject of “Enterprise”.
The definition of “Enterprise” remains fuzzy and ambiguous. Although there are many effort to define the enterprise with decriptive approach. The problem is that you can not architect what you can not see in the same token that you can not manage what you can see.
Enterprise map is effort to visualize the Enterprise. It is fundamental to Enterprise Architecture practice similar to geographical survey to Architects and Engineering. As the fundation of EA, the Enterprise map:
1. See the unseen enterprise. 2. See the true enterprise big picture. 3. Bring Enterprise Architects on the same page. 4. Faciliate Enterprise collaboration. 5. Plan to preseving Institutional knowledge. 6. Portal to institutional knowledge. 7. Conduct Enterprise master plan over Enterprise Map.
1. To See the unseen
Enterprise topology to see the unseen. It render the logical enterprise definition into visible and tangible presentation.
2. To see the true big picture
Enterprise topology to see the true enterprise big picture via collaboration and reconciliation.
3. Define the enterprise and bring every one to the same page.
4. Facilitate collaboration
Enterprise topology facilitate and articulate participation, collaboration and reconciliation.
5. Enterprise map as the plan and the portal to Enterprise Knowledge managment
6. Enterprise map to support enterprise master planning
The following paragraphes further ellaborate why Enterprise Map
THE COHERENCE BETWEEN VALUE CHAIN, BUSINESS CAPABILITIES, ORGANIZATION, LOCATION AND WORK LOAD