Enterprise Map specifications and standards
1.0 Enterprise Map SPECIFICATION
To suggest the Enterprise Map approach, it is critical to establish an Enterprise map specification to define a repeatable Enterprise map approach. The Enterprise Map concept is not new, many people have used similar method to visualize enterprise. However, these experiences have not been preserved to become a repeatable method. This method is not teachable without a specification.
The Enterprise map specification is intended to establish a standard and repeatable way to visualize the invisible enterprise. After the many practical and successful EA map experiences. many people would like be able to develop their own. However, without a EA map specification, the EA map is more art work with creative expression rather than a repeatable engineering drawings. With many years experiences, the author has developed a draft EA map draft template and specification for the EA community to use.
1.1 EA map specification to establish a repeatable Enterprise Map approach
The EA map specification establish the common EA map standard and enable a repeatable and trainable EA map approach. After many years experiment in many enterprise, the author found this lay out very use full to render the enterprise from the aspect of mission, function, process, organization, location and demand. It is the signature of EA map. The name to Enterprise Architecture (EA) map is derived from its capability to map not only the enterprise business but also map the automation environment.
1.2 The One Page concept
From human factor consider, the best way to see the big picture is to see the whole on a one page rendition. Although the technology has evolved rapidly in the last 50 years, human beings have not evolved much in the last couple thousand years. To put every on one big picture still serve the best to communicate architecture ideal with human being. Big picture in mind is very different from big picture on a one page drawing. An architects may have all kind consideration and good idea, but the bottom line is to put down on a piece of paper so that every one can see.
1.3 Based on Line of Business
The Enterprise map is created based on line of business.
The enterprise map adopt the standard architecture drawing size. The Enterprise Map drawings are originally design . In 1946 the International Organization of Standards (ISO) was formed in the interest of worldwide communication. One of its committees, ISO TCIO was formed to define an accepted set of drawing standards. Today's modern engineering and design organizations have adopted, either in full or with minor changes, the standards set up by this committee, which was and is made up of selected personnel from industry, technical organizations, and education. [Engineers Edge]
2.0 Drawing size
Under the one page concept must consider the human factor, some architect have created a monster page to cover the wall. The Enterprise Map drawing adopt the traditional architecture drawing size which are proven sizes suitable for human comprehension.
The Wall paper size The original EA map adopt the Architecture D size ( 24” X 36”) drawing size which is reasonable large drawing to accommodate the human comprehensive big picture in a one page concept. It is also call the wall paper size drawing to post on the wall and getting feed back from the community.
The Desktop size The EA maps are frequently reduced to Architecture C size drawing (18” X 24” ) for the purpose of manipulation in a regular desktop. The reduce size drawing requires very sharp vision capability to read the small print.
2.0 Specification of Enterprise Map layout
EA map is composed on a architecture D (24" X 36") size drawing with a drawing frame, reading guide, legend, Application system index and title blocks. The following paragraph describe the EA map drawing components from the left of EA map reading guide, the EA map legend and notes and EA map title block.
This area describe the mission, the stakeholders.
2.3 Value Chain
Concept of operation are created in a free form to capture the enterprise operation in a nutshell. A example of CONOPS approach can be find in.
This area display the enterprise Organization chart.
2.5 The activity model area
The Enterprise Data centers
This area describe the enterprise data centers
3.0 The EA map reading guide
Although it is the goal for EA map to be intuitive for people without specific training. However, many people found EA map is difficult is hard to understand without a simple guidance due to the fact that the map try to describe from the aspect of what we do? How we do it, who is doing it and the location. The following guidance illustrate the area of interest to guide the reading on EA map.
3.1 Enterprise Map Notes and Legends
Drawings are comprised of symbols and lines that represent components or systems. Although a majority of the symbols and lines are self-explanatory or standard (as described in later modules), a few unique symbols and conventions must be explained for each drawing. The notes and legends section of a drawing lists and explains any special symbols and conventions used on the drawing, as illustrated below. Also listed in the notes section is any information the designer or draftsman felt was necessary to correctly use or understand the drawing. Because of the importance of understanding all of the symbols and conventions used on a drawing, the notes and legend section must be reviewed before reading a drawing. [Engineers Edge]
3.2 Enterprise Map Title blocks for control and certification
The title block of a drawing, usually located on the bottom or lower right hand corner, contains all the information necessary to identify the drawing and to verify its validity. A title block is divided into several areas. On of the areas normally found within the title block are the drawing title, the drawing number, and lists the location, the site, or the vendor. The drawing title and the drawing number are used for identification and filing purposes. Usually the number is unique to the drawing and is comprised of a code that contains information about the drawing such as the site, system, and type of drawing. The drawing number may also contain information such as the sheet number, if the drawing is part of a series, or it may contain the revision level. Drawings are usually filed by their drawing number because the drawing title may be common to several prints or series of prints.
Other areas of the title block normally contains the signatures and approval dates, which provide information as to when and by whom the component/system was designed and when and by whom the drawing was drafted and verified for final approval. This information can be invaluable in locating further data on the system/component design or operation. These names can also help in the resolution of a discrepancy between the drawing and another source of information.
Title block enable certification The EA community has not yet establish architecture certification practice for the Enterprise Architects to take responsibility of their work due the fact that it is a overwhelming liability to certify the content in a volume of documentation or the massive information in the repository.
EA map serve as the container to clearly define the EA artifact and enable EA certification. The EA map and title block allow the Enterprise Architect to certify the architecture design within this drawing as the traditional surveyors, architects and engineers do to certify map, architecture and engineering drawing.
3.3 The application system index
To help the user of EA map to further understand the acronym of Application and locate an application system on the map. The EA map provide the application system index area which spell the application system acronyms and list all the application system in alphabetical order. The application index area should be done last as the finish touch of this drawing.
Enterprise Context ^ TOP