Enterprise Architecture Planning (EAP) - PowerPoint PPT Presentation

View by Category
About This Presentation

Enterprise Architecture Planning (EAP)


A comprehensive blueprint of an organization. The structure of (Enterprise) components and their ... A common understanding by all, of the names and ... – PowerPoint PPT presentation

Number of Views:746
Avg rating:3.0/5.0
Slides: 20
Provided by: BEy5


Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: Enterprise Architecture Planning (EAP)

Enterprise ArchitecturePlanning(EAP)
  • Office of Information Technology and System

  • What is Enterprise Architecture Planning (EAP)?
  • What is an EA used for?
  • Why should we do it?

What is an Enterprise Architecture?
A comprehensive blueprint of an
organization. The structure of (Enterprise)
components and their relationships, as well as
principles and guidelines governing their
evolution over time. A common understanding by
all, of the names and definitions of an
organizations entities.
What is an Enterprise Architecture?
  • The EA is a strategic asset repository which
    defines the current and target architecture
    environments, including
  • the business,
  • the information,
  • the technology, and
  • the transitional processes.

Source Federal Conceptual Architecture model
Examples - Entities
A distinguishable - person - about which
information is kept. place, thing,
event, concept
Source U.S. Coast Guard Information Architecture
Architecture Layers
Some EAP Components
  • A standard methodology
  • A standard set of templates
  • A repository
  • A configuration management process
  • Easy access
  • Ability to export

Zachmans Framework forInformation Systems
What is an EA used for?
  • Acquisition
  • Investment decisions
  • Modeling Simulation
  • Analysis
  • Requirements definition
  • Plan baseline
  • Describing and understanding baseline

DoD C4ISR Architecture Framework 2.0
DoD C4ISR Architecture Framework 2.0
What is an EA used for?
  • Promote interoperable and cost-effective systems
  • Provide the rules, guidance and product
    descriptions for developing and presenting
    architectural descriptions
  • Ensure a common denominator for understanding,
    comparing, and integrating architectures.
  • Enable architectures to contribute more
    effectively to engineering interoperable and
    cost-effective systems.
  • Provide a mechanism for managing complexity.

IT Life Cycle and CM Policy Consolidation
Information Systems Technical Architecture COMDTI
Planning Approval for Automated Information
Systems (AIS) COMDTINST5231.2
Standard Workstation III Configuration
Management Policy COMDTINST5200.16
Information Technology Life Cycle
and Configuration Management Policy COMDTINST
ITSystems DevelopmentPlan(DRAFT) COMDTINST9999
InformationResourceManagement(cancelled) COMDTI
USCGC4ISRBaseline Architecture COMDTINST3090.6
Standard TerminalApplication SoftwareDeploymentC
Other Policy TBD
Facilitates information services that
provide flexibility, interoperability, reliabili
ty, survivability, affordability, sustainability,
portability, reusability, Adaptability, Compatibi
Business Benefits of EAP
  • Focus on strategic use of technology for managing
    data as an asset
  • Standard vocabulary facilitates communication and
    reduces inconsistency and data redundancy
  • Documentation increases understanding of the
  • Models can be used to explain the business and
    assess the impact of business changes
  • Decision making policies can be reviewed
  • Integration of current systems with new systems
    is considered.
  • It allows for a comprehensive, objective and
    impartial approach
  • The long range systems plan compliments the
    business plan
  • A cost-effective long term solution considers
    rate of return
  • It involves a feasible migration strategy with
    short term achievements
  • it is easier to assess the benefits of impact of
    new systems and software
  • it allows easier accommodation of dynamic
    business changes such as mergers, acquisitions,
    new products, lines of business.etc.
  • Management participation provides a business
    prospective, credibility, confidence, and
    demystifies system development.
  • Source Enterprise Architecture Planning
  • Steven Spewak

Benefits to the Business of planned systems
  • More responsive to customers needs
  • Reduced data-entry costs
  • Head-count is reduced
  • Increased productivity of personnel permits
    increased level of business and containment of
  • Improved skills raise enthusiasm and loyalty
  • Efficient systems maintenance means improved
  • Architectures eliminate complex costly interfaces
    incongruent systems
  • Management decisions in all functional areas will
    be based on more accurate and timely data,
    leading to various improvements and cost-saving
  • End user has direct access to shared data
  • New systems are developed faster and at less cost
    due to common data, common code, anda shortened
    requirements phase
  • Easier to evaluate and select vendor SW packages
  • Effective use of repository and CASE products
  • Source Enterprise Architecture Planning
  • Steven Spewak

Zachman reflections on EA Planning
"You may think this is too much work Or, it
takes too long And it costs too much Or is too
theoretical Or too high risk Or too
whatever. However, if thats your assessment You
cant complain that the systems arent aligned
with the enterprise,or are inflexible, or cost
too much, or that vital information is not
available, or that the data you get isnt any
good, or too late, or you cant change anything,
or that I/S is slow and unresponsive and, I am
here to tell you Outsourcing isnt going to fix
the problem. Packages (in themselves) wont fix
the problem. Decentralization wont fix the
problem. And, the Internet isnt going to fix the
problem. No amount of money, Or technology is
going to fix the problem! It is NOT a technical
problem, it is an ENTERPRISE problem. Only
ACTUAL WORK is going to fix the problem,
and Someday, you are going to wish you had all
those models, Enterprise wide, horizontally and
vertically integrated, at excruciating level of
detail. You might as well start working on them
TODAY!!! John Zachman
Next Steps
  • CKO Charter an Enterprise Architecture
    Configuration Control Board (EACCB)
  • Identify goals, objective, principles
  • Establish membership
  • Identify a methodology
  • Identify a framework
  • Identify resources
  • Define deliverables
  • Establish a timeline
  • CKO Charter an Enterprise Data Dictionary
    Configuration Control Board (EDDCCB)

JCAPS Benefits
Primary - to facilitate change Structure is best
way to organize complicated information More
manageable Easier to understand Easier to detect
omissions and overlaps (can automate) With
structure, learning something about part,
equals learning something about whole. Easier to
update Promotes/Supports traceability Increases
the speed and credability of information
sharing Creates opportunity to work faster, more
reliably, more economically Enhances
decision-making Meta data is essential to meet
report requirements
Definition - Mission
A sequence of one or more tasks executed by an
(Actor) entity to achieve a specific objective or
related set of objectives.
Definition - Action
The alteration of an entity which produces a
change in state or condition
Definition - Task
The execution of one or more actions by an entity
Definition - Interaction
The interface which defines the flow of entities,
and/or actions between entities executing tasks
Definitions - Miscellaneous
Technical Reference Model - A common framework,
probably conceptual, to define a common
vocabulary so as to better develop and aquire
some level of support. It would provide you with
a representation of the domain showing commonality
and integration and interoperability. Common
Operating Environment - The set of capabilities
that would allow you to address the suite of
integration products that you need to ensure
a cohesive framework of systems for development.
Like the DII COE address architecture, standards,
software reuse, shared data, interoperability, por
tability, configuration management and
integration. Standards Roadmap - It would start
with a common set of mandatory standards and
guidelines. It would then be tailored to the
development that was being implemented. So it
would be the "building codes" that would
be reviewed and selected to facilitate the
development of the system or systems needed to be
built. (A Technical Architecture View for
a particular area (Defense Transportation System)
starting from the DOD Joint Technical
Architecture.) Dick Webb, ASD(C3I)
About PowerShow.com