Enterprise Architecture
DoDAF Framework and The CASE
Welcome
Prior module discussion: 15 minutes
Assessment on prior module: 20 minutes
New concept: Rest of the class
2015-1001 Fanshawe College Boulevard; P.O. Box 7005 London, Ontario N5Y 5R6 Phone: 519-452-4290 Fax: 519 659-9522 [Link]
RMN AIRPORT TODAY
Our hypothetical RMN Airport is
strategically located in (an
alternative) Southern California,
south and east of LAX, surrounded
by the hypothetical towns of
Tornton, Brownsville, and
Petersboro. The airport is near major
freeways, but there is undeveloped
land surrounding it, as shown in
Figure 3-1.
Figure 3-1 Location of the airport
Business Analysis Program
OPPORTUNITIES AND ASPIRATIONS
a conceptual image of the
airport, with the typical
components divided into
airside components and
landside components.
Figure 3-2 Conceptual image of RMN Airport
Business Analysis Program
CHALLENGES
The factors and
stakeholders
that RMN must
address if it is to
grow into the
role of a reliever
airport for LAX.
Figure 3-3 Airport enterprise, stakeholders, and concerns
Business Analysis Program
What are the key challenges of the airport
case?
• Dealing with areas of environmental impact, energy footprint,
neighborhood and local governments, federal regulators,
transportation security, etc.
• Remaining operational during large-scale construction of runways
and terminals (size of runaways to handle wide-body jets);
widening and lengthening of runway; restriction of runway because
of construction equipment – needs supervision and procedures for
safety; financial investment at risk if traffic growth doesn’t happen
• Changes must be closely coordinated during the transformation
period.
REGULATIONS
FAA Regulations
§ Runways
§ Airport equipment and instrumentation
§ Air traffic personnel
§ Airline staff and aircrew
Local Regulations
Other Federal and State Regulations
Business Analysis Program
Exercise (15-20 min)
• Review Airport case Groups and Stakeholders
• Explain some of the key 1. Government authorities (city,
state, federal) & Regulatory
challenges of RMN case bodies
2. Air carriers / Service
providers
3. Residential and commercial
neighbours
4. International (Border,
customs, immigration,
drugs)
STAKEHOLDERS
• TSA
• United States Immigration and Customs Enforcement (ICE)
• United States Customs and Border Protection (CBP)
• U.S. Department of Agriculture
• U.S. Drug Enforcement Agency (DEA)
• Contractors
• Unions
• Airlines
Business Analysis Program
Who are the stakeholders of the RMN
Airport and their roles for the airport?
Stakeholders and Roles
• TSA - Passenger and baggage screening, sky marshals
• US Immigration and Customs Enforcement (ICE) - Immigration
screening of incoming foreign nationals
• US Customs and Border Protection (CBP) - Customs processing
and border controls enforcement of incoming passengers from
foreign originating ports on first entry to the US at RMN Airport
• U.S. Department of Agriculture – Agriculture Public Health
Inspection Service (APHIS) Screening of baggage for dairy, plants,
and farm products
Stakeholders and Roles
• U.S. Drug Enforcement Agency (DEA) - Screening of
passengers and baggage for illegal drugs
• Contractors - Vendors providing landside (terminal)
passenger services
• Unions - Organized airport, contractor, and facility
workers
• Airlines - Checking in passengers and managing local
airline operations landside and airside through the airline
operations centers
MORE FUNCTIONS, FACILITIES, AND CAPABILITIES
a) Landside Functions and Facilities
b) Airside Functions and Facilities
c) Passenger Processing Capabilities
• (i) Passenger management; (ii) Passenger comfort; (iii)
Passenger convenience; (iv) Passenger safety
d) Cargo Processing Capabilities
§ (i) Cargo handling capabilities; (ii) Cargo tracking capabilities; (iii)
Cargo inspection capability; (iv) Cargo storage and cargo
management capabilities; (v) Hazardous material cargo (hazmat)
handling capabilities
e) Information Technology Capabilities
Business Analysis Program
LANDSIDE
FUNCTIONS
AND
FACILITIES
Figure 3-4 Airport terminal functions
Business Analysis Program
AIRSIDE
FUNCTIONS
AND
FACILITIES
Business Analysis Program Figure 3-5 Airside function summary
ADDITIONAL CONSIDERATIONS
• Larger Management Staff
• Continuous Interactions with Communities of
Interest
• Cultural Issues
Business Analysis Program
PLANS
Overview of the contents
of the Airport Master
Plan (AMP) and two
related plans: the Airport
Layout Plan and the
Integrated Project
Roadmap.
Business Analysis Program Figure 3-6 Overview of the Airport Master Plan
OBJECTIVES OF THE AMP
• Document the issues that the proposed development will address.
• Justify the proposed development through the technical, economic, and environmental investigation
of concepts and alternatives.
• Provide an effective graphical presentation of the development of the airport and anticipated land
uses in the vicinity of the airport.
• Establish a realistic schedule for the implementation of the development proposed in the plan,
particularly the short-term capital improvement program.
• Propose an achievable financial plan to support the implementation schedule.
• Provide sufficient project definition and detail for subsequent environmental evaluations that may be
required before the project is approved
• Present a plan that adequately addresses the issues and satisfies local, state, and federal
regulations.
• Document policies and future aeronautical demand to support municipal or local deliberations on
spending, debt, land use controls, and other policies necessary to preserve the integrity of the airport
and its surroundings.
• Set the stage and establish the framework for a continuing planning process. Such a process should
monitor key conditions and permit changes in plan recommendations as required.
Business Analysis Program
REQUIREMENT
RMN Airport management has prepared an AMP for the transformation of the airport but has focused on a 15-year view
for this version of the plan, versus the 20-year time frame suggested by the FAA. RMN management will update the AMP
every 5 years during the 15-year time frame of this plan.
From an enterprise architecture viewpoint, the AMP outline requires much of the same content as an enterprise
architecture:
• Defines the vision and incremental steps with explicit annual progress measures—a target architecture, phasing
architectures, and strategic viewpoint
• Describes the existing airport inventory—an as-is architecture
• Describes facility requirements, provides development alternatives, and describes the capital improvement program—
other parts to the to-be architectures
The AMP requires aviation activity forecast and demand/capacity analysis, which would be needed as input to to-be
architectures.
However, the AMP wants narrative descriptions, whereas an enterprise architecture provides specific views and
mathematical models, many of which are graphical in nature. The more detailed and structured views of the enterprise
architecture can be used to support the required analyses required by the AMP.
Elements of the AMP and its two associated plans will need approval by the commissioners, the city councils of the three
surrounding communities, and the FAA. Other approvals may be needed from the State of California Department of
Transportation, the Environment Protection Agency, or local environmental organizations.
Business Analysis Program
DoDAF Framework
2015-1001 Fanshawe College Boulevard; P.O. Box 7005 London, Ontario N5Y 5R6 Phone: 519-452-4290 Fax: 519 659-9522 [Link]
DODAF
• One of the oldest frameworks
• Its views are compatible with the TOGAF
• The primary purpose of defense architecture
framework is to provide a common format and
semantics for comparison, aggregation, and analysis
of multiple architectures.
Business Analysis Program
LEVELS OF ENTERPRISE
Support strategic decision-making for the enterprise
Manage capabilities or business services to
ensure coordination and interoperability of
related business processes, systems, and data
Manage business process and system
development and acquisition
Figure 4-1 Levels of enterprise architectures
Business Analysis Program
QUESTIONS OR ISSUES THAT AN ENTERPRISE
LEVEL ARCHITECTURE MIGHT ADDRESS
• How do the business functions or capabilities relate to the enterprise’s strategy
and goals?
• Are there dependencies among the capabilities or business functions?
• How will business function or capability performance be measured?
• When will the capabilities or business functions be implemented and what projects
will provide them?
• What organizations will use the capabilities or business functions?
• What organizations are in charge of which projects?
• What are the timelines for the projects and what are the dependencies among
them?
Examples: RMN Airport Enterprise Architecture, Defense enterprises undertaking
complex, large multiyear acquisition programs from aircrafts and ships to worldwide
software applications
Business Analysis Program
SEGMENT LEVEL ARCHITECTURE
• Each Segment Level architecture addresses a core mission area
of the enterprise, a subset of the Enterprise Level architecture
capabilities, or a common or shared service that supports core
mission areas.
• The common or shared services may be either business services,
such as human resources management or financial management,
or enterprise services (IT services, knowledge management or
communications).
• Examples: Joint Capability Areas, Passenger Management,
International Trade; IT, HR, Product Lines
Business Analysis Program
SOLUTION LEVEL ARCHITECTURE
Questions or issues that Solution Level architectures addresses:
• What are the key elements of the operational concept?
• How are the business/mission operations performed?
• Who performs the business/mission operations and what
resources are exchanged?
• What are the systems/services and what are their interfaces (both
internal and external)?
• How do the systems/services support operations?
• What are the technical standards for the systems/services?
Business Analysis Program
DODAF VIEWPOINTS
Figure 4-2 DoDAF viewpoints (graphic from the DoDAF)
Business Analysis Program
Exercise (15 min)
Breakout Groups and Viewpoints Questions
1. Capability • What is the focus of the
viewpoint?
2. Data and Information
• What is it providing and/or
3. Operational supporting?
4. Services • Who are the stakeholder
group(s) interested?
5. Systems
• How many views are there
associated with it?
All Viewpoint (2 Views)
• Provides an overview of the entire architecture.
• Its views provide both a living executive summary of the
architecture, including conclusions and
recommendations, and the detailed definitions for all
terms used in the architecture.
• This viewpoint is used by all architecture stakeholders.
Capability Viewpoint (7 views)
• Focuses on the strategic aspects of the enterprise,
such as the vision of the enterprise, its goals and
objectives, capabilities that are necessary to achieve
those goals and objectives
• Provides relationships among the capabilities, how the
delivery of these capabilities will change over time, and
organizations that will use these capabilities.
• Primary interest: Executive management.
Data and Information Viewpoint (3 views)
• Focuses on descriptions of the shared, structured
enterprise data.
• Views in this viewpoint provide representations of the
conceptual, logical, or physical models of this shared
data.
• May be of interest to any of business managers,
operational personnel, and IT personnel, depending on
the level of detail included.
Operational Viewpoint (9 views)
• Provides information on the operations of the enterprise, such as
the business or mission concept of operations, the business or
mission processes and who performs them, the information flows
between these performers and between the activities of the
processes, and the organizations involved.
• Provides information on the operational behaviors of the
enterprise: the operational elements that have interesting state
behavior, the key operational scenarios, and the business or
operational rules.
• Primary interest: Business manager and operational personnel.
Project Viewpoint (3 views)
• Describes the various development projects current or
planned for the enterprise.
• Views in this viewpoint identify what organizations
manage which projects, what the delivery timelines are
for sets of projects and what the dependencies among
the deliveries are, and which projects provide
components for which capability.
• Primary interest: Executives and business managers.
Services Viewpoint (13 views)
• Provides information on the business or IT services of
the enterprise.
• This information can include service functions, service
interfaces, and service level agreements (SLAs); how
the services are interconnected; what resources are
exchanged; and when services will be available.
• The behavioral aspects of the services can also be
described.
• Primary interest: Business managers (for business
services) and IT personnel (for IT services).
Systems Viewpoint (13 views)
• Provides information on the enterprise’s systems.
• Information includes what the systems are, how they
are interconnected, what resources flow between them,
when they become available, and what activities they
support.
• The behavioral aspects of the systems can also be
described.
• Primary interest: IT personnel.
Standards Viewpoint (2 views)
• Focuses on the technical standards and the systems or
services these standards should apply to.
• The technical standards are usually organized based
on a technical reference model (TRM).
• Standards may have dates associated with them: when
the standard must be met and when the standard will
no longer apply and what emerging standard will
replace it.
• Primary interest: IT personnel and to business
managers involved in acquisition.
DODAF VIEWPOINTS
Figure 4-2 DoDAF viewpoints (graphic from the DoDAF)
Business Analysis Program
DODAF VIEWPOINT RELATIONSHIPS
Figure 4-3 Relationships among the DoDAF viewpoints
Business Analysis Program
DODAF VIEWS
Table 4-1 DODAF Views Organized by Viewpoint
Continued…
Business Analysis Program
DODAF VIEWS
Table 4-1 DODAF Views Organized by Viewpoint
Continued…
Business Analysis Program
What are the different concepts that can
be related to a data model?
• High-level concepts and their relationships
• Logical data model - data requirements and business
process (activity) rules
• Physical data model - the physical implementation
format of the logical data model entities, e.g., message
formats, file structure, physical schema
DODAF VIEWS
Table 4-1 DODAF Views Organized by Viewpoint
Continued…
Business Analysis Program
DODAF VIEWS
Table 4-1 DODAF Views Organized by Viewpoint
Continued…
Business Analysis Program
DODAF VIEWS
Table 4-1 DODAF Views Organized by Viewpoint
Continued…
Business Analysis Program
DODAF VIEWS
Table 4-1 DODAF Views Organized by Viewpoint
Continued…
Business Analysis Program
DODAF VIEWS
Table 4-1 DODAF Views Organized by Viewpoint
Continued…
Business Analysis Program
DODAF VIEWS
Table 4-1 DODAF Views Organized by Viewpoint
Continued…
Business Analysis Program
DODAF VIEWS
Table 4-1 DODAF Views Organized by Viewpoint
Business Analysis Program
Question
• Explain DoDAF Views / Viewpoints
DELIVERABLES
Follow the dates in FOL for assignments, quizzes, and tests
Read materials in FOL, textbook, and your class notes
Be prepared for in class presentation and discussion
2015-1001 Fanshawe College Boulevard; P.O. Box 7005 London, Ontario N5Y 5R6 Phone: 519-452-4290 Fax: 519 659-9522 [Link]
