Mapping the Enterprise
Nov 01, 2014
The first thing for EA professional to do is to map the Enterprise for every one to comprehend a tangible enterprise. This presentation shares Enterprise Map experience which has been useful for both business and technical community. In the speaker’s experience, the Enterprise Map is the few EA artifact that has retained its value long after delivery. While other EA artifacts end up as shelf-ware (and hence long forgotten in the EA repository), sets of Enterprise Maps make it much easier to explain EA concepts (at least in comparison to the Zachman framework).
Not only does the Enterprise Map help to unravel the “big picture” of the enterprise, but it also facilitates enterprise collaboration. Gaining a true understanding of the enterprise is a collaborate process; this process is well-illustrated in the story of the blind man and the elephant. Thus, the formulation of the Enterprise Map also serves to create a culture of collaboration throughout the enterprise.
One can draw parallels between the Enterprise Map (and its function as the “ground work” of EA) and an engineering survey. The Enterprise Map is not just a glorified diagram output from a complicated EA system; rather, it is built piece-by-piece from the hard work and total participation of various stakeholders. In fact, the Enterprise Map does not require a complicated EA system – it can be prepared with basic tools and manual processes (e.g., Microsoft Visio / SmartDraw).
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Presentation goal Explain why the enterprise map is a
fundamental tool for EA professionals. Describe the enterprise map and its real-world
applications. Step by Step approach preparing the Enterprise
Map based on the Enterprise Map framework. The phase of Archeology, Draft, Collaboration,
Consensus, Sharing and Maintenance. The column of Value chain, Information, Business
Capabilities, Organization, Location and Workload. Using Enterprise Map to identify the enterprise
application systems
Background
The Enterprise Map approach was created in 1998 by John Wu and has been used to support different US government agencies and private industries.
Initially it was created in a free style and very difficult to repeat and train the other Enterprise Architects.
This version develop a repeatable and trainable Enterprise Map approach by defining :
The Enterprise Map approach framework . The Enterprise Map specification template.
2014 Revision
This is an update version of Enterprise Map approach.
In this version Enterprise map demonstrate the whole is much
greater the part of concept of operation, value chain, organization map, location map and business capability map and information landscape.
Provide more detail. Focus on business capability map and moved away
from the business process.
The use of Enterprise Map An Enterprise Map is similar to a
geographical map: it maps enterprise locations, business functions, processes and application systems. Helps new staff see the “big picture” of
the enterprise. Serves as an information repository. Helps to organize enterprise knowledge. Allows practitioners to drill-down into
specific areas of enterprise knowledge.
A holistic approach An Enterprise Map is prepared in a holistic
approach by: Use Zachman framework as a thinking
tool. See the whole Use the principle of the whole is greater
than the sum of its parts. Coherence between all its parts. Facilitate collaboration Prepare enterprise map for large and
small organization in base on macro and microcosm concept.
The tools are not complicate
The Enterprise Map only requires basic drawing tools to start with.
It is not necessary to make significant investment on EA tools to initiate EA efforts!
Drawing software (Visio)
A large plotter A simple repository
such as MS Sharepoint for example.
But, the effort is not trivial
The effort to prepare the enterprise Map is not trivial by putting all the charts on large paper.
The criteria is to see the true enterprise big picture and every one can find their place on the map.
Each map can take several month off and on to be useful.
It is a continuous effort.
Enterprise map is analogy to a
puzzle without a picture on the box.
The EA map easel enable architects to work on several map in the same time and enable subconscious to work by looking at it every day.
Subconscious brain works on problems while we are not actually aware of it
Here is an example of home made EA map easel.
Multiple EA maps working rack
The Enterprise Map set
Prepare Enterprise map not only for the entire enterprise but also for the sub organization which function as a whole.
Based on the macro and micro concept, enterprise map is prepare for large and small organization.
It start with the over all Enterprise maps and subject to break down for more detail.
As shown on the next picture.
Enterprise Map and EA repository
Enterprise Map also shared in EA repository as part of institutional knowledge.
It serve as the guide to organize institutional knowledge. The following example use Enterprise Map link to Sharepoint
repository.
User can drill down from the Enterprise map on the left to the Sharepoint repository on the right.
The Enterprise Map Specification
Location Map
Value Chain OrganizationChart
Business Capability Map
Connectivity InformationLandscape Work Load
Title Block & legend
Customer
Title BlockLegend
The specification enable a repeatable method for purpose of training .
D size drawing (36” X 24”) to post on the wall.
Reduce to C size drawing set for desktop use.
Example
This is good example to demonstrate the whole is much greater
than the sum of its parts. Each diagram by itself, is only a diagram in some document
without significant value. Align these diagrams on one big picture, one can see the
coherent alignment of customer need, business capabilities, value chain, concept of operation, organization chart and location as a whole.
The whole is indeed greater than the sum of its parts
Whole is larger than the sum of its parts
Enterprise Map illustrate the coherence customer’s need, value
chain, business capabilities, organization chart, location, information and workload.
Business capability satisfy to customer’s need. Business capabilities align to value chain. Organization in coherence to business capabilities. Information landscape derived from business capabilities. Workload based on business capability. Location in coherence to business workload. Automation align to business capabilities.
Enable the coherence between the parts
Title Block
The title block (T/B, TB) is an area of the drawing that conveys header-type information about the drawing, such as:
Drawing title (hence the name "title block") Drawing number Name of the design activity (corporation, government agency, etc.) Address of the design activity (such as city, state/province, country)
Legend
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,
Customers The Maslow’s Hierarchy of
Customer Service from the book “Peak: How Great Companies Get Their Mojo From Maslow,” by Chip Conley.
Level 1: Companies can meet expectations with current customer service mode
Level 2: To fulfill desires, companies have to figure out exactly what those desires are.
Level 3: To meet unrecognized needs you have to learn more about the customer and develop a certain intuition about what would make them happy.
Enterprise Map Framework Enterprise Map framework
based on ZF as a thinking tool. The map is created is created
holistically from the aspect of Value Chain (Why), Information (What), Business Capabilities (How), organization (Who), Location (Where) and Workload (When)
It is prepared in the phases of Archeology, Draft, Collaboration, Consensus, Sharing, and Maintain.
Archeology (Row 1) Most of organization have
already make significant investment in documenting there environment and systems, however, it is burried in
Strategic plan. System documentations Powerpoint presentations.
Instead of reinvent the wheel, Enterprise Architect acting as archeologist to dig into existing documents.
Draft (Row 2)
Enterprise Architect must do their homework to raise every one’s curiosity and enable then to contribute their knowledge.
Enterprise Architect take a first cut to visualize the enterprise.
It is a big puzzle without a picture for guidance.
Apply Jigsaw puzzle technique. Hang the draft on the wall,
information comes in piece and find a right place to put the puzzle together
Things you know; Things you know that you don’t know; Things you don’t know that you don’t know.
Enterprise map take a stone soup approach to enable collaboration by total participation.
Conduct review meeting. Conducting review meeting is important to complete the enterprise map.
Post on the public area for review and input because people are too busy or too shy to speak up in the meeting. they prefer to comment on the wall.
Collaboration (Row 3)
Consensus (Row 4)
The Enterprise Map is a total participation work and it subject to consensus.
Each person only touch parts of the enterprise and like to consider the parts they have touched is the whole.
Frequently there are different view of the same subject, and people intend to insist on their righteousness.
The story of blind man and the elephant tell us the only way to see the true enterprise picture is via the consensus process.
Building consensus through meeting and discussion to find the common ground.
Sharing (Row 5) Enterprise maps should become a popular display
in an organization. In office and meeting room and public area to
become a common knowledge of an organization. Deliver the Enterprise Map both in electronic form
and by hard copy: Use PDF for electronic delivery. Hard copy is useful but difficult to deliver.
Enterprise Map in EA repository. Print the hard copy on
Desktop version: (24” X 18”) Wallpaper version: (36” x 24”)
Maintenance (Row 6) EA to set aside budget for Enterprise map budget.
Enterprise Map is a continuous effort rather than a
one time job. It subject to update annually to reflect change. The maintenance update :
Business capability Organization chart. Location map, The enterprise application and information land scape.
It is still a collaborative effort.
Value Chain (Why) (Column 1) EA use value chain to
describe the operation of an organization.
The concept comes from business management and was first described and popularized by Michael Porter
"The idea of the value chain is based on the process view of organizations, the idea of seeing a manufacturing (or service) organisation as a system.
Information Landscape (What) (Column 2)
Information landscape identify enterprise information resources.
Enterprise map can associate the Application and information landscape.
Information landscape on the Enterprise Map enable a person to walk through all the information resources even after many years.
Business capabilities (How) (Column 3)
EA plans for the enterprise SOA and cloud computing environment.
Distinguish cross-cutting architecture from top-down architecture.
IT capabilities map created by Jeff Scott.
The capability map can be link to the detail capability information in the repository.
Organization Chart (Who) (Column 4)
An organizational chart (often called organization chart, org chart, organigram(me), or organogram(me)) is a diagram that shows the structure of an organization and the relationships and relative ranks of its parts and positions/jobs
An organization chart on Enterprise map allow a visual alignment between business capability and enterprise organization.
Location (Where) (Column 5) A location map, used in EA
to show the location of the enterprise.
Location map within EA map allow the reader to align business location with business capabilities and workload.
An Enterprise location map alone on the wall can effectively remind the audience that they part of the whole and learn from each other.
It should not be overlooked as a clerical work.
Business Work Load (When) (Column 6)
Customer demand generate enterprise workload. Workload is essential in engineering calculation but it is often overlooked in
application design. There different workload at different business capability at different time of the year. There are different workload at different location at different time of a year as show
shown in Annual workload by Business Locations.
Annual Workload by capabilities
Annual Workload by locations
Connectivity diagram
Enterprise map include the connectivity diagram.
Adapting the OV-2 operational node connectivity diagram from DODAF and MODAF.
Internal node to node. Internal system to
system. External Node to Node. External system to
system.
NODESCOMMUNICATIONS
NETWORKTO OTHER
COMMUNICATIONSSYSTEM
1
COMMUNICATIONSSYSTEM
2
SYSTEM2
NODE A
PROCESSING
SYSTEM1
PROCESSING
CO
MM
UN
ICA
TIO
NS
N
ET
WO
RK
FR
OM
OT
HE
R
NO
DE
S
Interface
CS1/PS2
Interfac
e PS1/PS2
Interface PS2/CS2
SYSTEM 1
Component 1FROM OTHERSYSTEM
Component 2
Component 4 Component 3
Component 5
TOOTHER
SYSTEM
Internodal PerspectiveSystem-to-System
Intranodal Perspective Intrasystem Perspective
Internodal PerspectiveNode Edge-to-Node Edge
NODE A NODE B
NODE C
SYSTEM2
SYSTEM1
EXTERNALCONNECTION
SYSTEM1
COMMS Interface
COMM
S Inter
face
COMMS InterfaceOne-way SATCOM
Interface
SYSTEM2
SYSTEM3
SYSTEM1
SYSTEM4
NODE ANODE B
NODE C
SYSTEM2
SYSTEM1
EXTERNALCONNECTION
SYSTEM1
COMMS Interface
COMM
S Inter
face
COMMS InterfaceOne-way SATCOM Interface
SYSTEM2
SYSTEM3
SYSTEM1
SYSTEM4
Application landscape on Enterprise Map
Application landscape on the enterprise map render the Application with the context of business capability.
With the Application landscape on the enterprise map, any person can walk through all the application systems without remembering it even after many years.
The purpose
Discover and identify the application systems in the enterprise.
The source of Enterprise Application System catalog. Identify duplicate systems. Enable every one to know all the application systems for
the purpose of sharing and reuse. A easy way to master the enterprise application systems
without remember the systems. One can tell a story of the enterprise application systems
base on the enterprise map in a short time or many years after.
Enterprise map to discover the Applications
Use enterprise map to discover automations system and brief description in the organization.
Enterprise does not really know how many systems they have.
There are systems they know, There are systems they know that they don’t know, There are systems that they don’t that they don’t know.
Site interview or survey request does not find out all the systems.
Enterprise map use “Stone Soup” strategy to discover all the systems.
Enterprise Map as the pot to bring up curiosity and contribute their embedded institutional knowledge.
Business take advantage of automation
CAD
Computer aid system
Risk
Risk Management system
Budget system SAP Human
Resources
Asset Management
Customer Relation System
ServiceManagement Service Management
system
MonitoringSystem
Cyber security System
CRM
GovernanceVendorManagement
Project
CM
Configuration Manage system
Procure
Procurement system
Project Management System,
Perform
Performance Measurement System
EA Repository
EA Repository
Assign technologies
Enterprise Map use color bobbles to represent technology pattern.
CAD
Computer aid system
Risk
Risk Management system
Budget system SAP Human
Resources
Asset Management
Customer Relation System
ServiceManagement Service Management
system
MonitoringSystem
Cyber security System
CRM
GovernanceVendorManagement
Project
CM
Configuration Manage system
Procure
Procurement system
Project Management System,
Cyber security System
EA Repository
Perform
Performance Measurement System
Identify the technologies in color code
Mainframe
ASP
Mainframe
Master plan on Enterprise Map
Enterprise Map does not only describe the existing environment, It can also used to plan for the future.
Use Enterprise map as the based to plan for future as the master plan.
Business reengineering. Business reorganization. Organization consolidation. Location consolidation. Information consolidation. Automation consolidation. Further discussion in the presentation of Master Plan
Conclusion
Enterprise map is the tip of iceberg of EA in leading to massive institutional knowledge under the iceberg.
It is not only a pretty picture. Enterprise Map is a collaborative work, Enterprise Architects
serve as the “Glue” not the “Glue” . Enterprise map should be a public knowledge in an
organization. It continue to provide value to enable sharing and reuse in
the organization. It help people to the “context of discovery” but does not to
the “context of justification”.
Related Documents
![Mapping the Business Model Canvas to ArchiMate · paper is defining a mapping between Osterwalder’s Business Model Ontology (BMO) [1] and The Open Group’s enterprise architecture](https://static.cupdf.com/doc/110x72/5d1cf8d788c993d2288d0786/mapping-the-business-model-canvas-to-archimate-paper-is-defining-a-mapping-between.jpg)
