Enterprise Architecture Planning (EAP)

  Enterprise Architecture Planning (EAP)

  Office of Information Technology and System Strategy

Discussion

• 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 organization’s 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

  CG MEMBER CG ORGANIZATION COAST GUARD ASSET MARITIME ACCIDENT REGULATION AUXILIARIST NAVIGABLE WATERS ATON COASTAL INTRUSION LAW MARINER GOVERNMENT FACILITIES COMMERCIAL VESSEL RESPONSE ACTIVITIES STANDARDS RECREATIONAL BOATERS AIR RECREATIONAL BOAT ATON DISCREPENCY DIRECTIVE CONTRACTORS BRIDGES PORT FACILITY PREVENTION ACTIVITIES PLAN GOVERNMENT CONTACTS REGULATED MANUFACTURERS

  ICEBERG DEFENSE OPERATIONS MISSION REGULATED MANUFACTURERS HAZARDOUS MATERIAL ACQUISITION LEGAL REQUIREMENT CASUALTY CUSTOMER ASSET SUPPORT OPERATIONS

  INTERNATIONAL AGREEMENT BUDGET BUDGET BUILD POLITICS RADIO FREQUENCY SPECTRUM CASE SUPPORT ASSETS TRAINING/EDUCATION PROGRAMS CASE META DATA FUNDS

  Source: U.S. Coast Guard Information Architecture Architecture Layers

PERSONNEL WLB PLATFORMS WPB

  T1 Lines OSC HQ FINCEN WMEC MLCP

INFRASTRUCTURE

  AR&SC

  ISC

  ISC Ports

  ISC PPC ELC TISCOM

  ISC Boston NOLA Honolulu

  D17

  ISC

  ISC St Louis ISC Cleve. CAA MLCA Mia.

Some EAP Components

• A standard methodology
• A standard set of templates
• A repository
• A configuration management process
• Easy access
• Ability to export

Zachman’s Framework for Information Systems Architecture

Data Function Network People Time Motivation List of Locations List of Things List of Processes the List of Organizations List of Events List of Business Important to Business Important to Business Business Performs Important to Business Significant to Business Goals/Strategies

  Planner’s View Entity=Class of Function=Class of

  Time=Major Business End/Means=Major Node=Major Business Business Thing Business Process Agent=Major Org Unit Event Business Goal/CSF Location e.g., Function Flow e.g., Business Plan e.g., Entity e.g., Logistics Network e.g., Organization e.g., Master Schedule Diagram Relationship

  Chart Diagram Owner’s

  Node=Business End=Business Location

View

   Objectives Ent=Business Entity Link=Business Agent=Org Unit Time= Business Event Function=Business Means=Business Rel=Business Rule Linkage Work=Work Product Cycle=Business Cycle Process

  Strategy e.g., Data Model e.g., Human Interface e.g., Data Flow Diagram e.g., Distributed e.g., Processing e.g., Knowledge Architecture System Architecture Structure Architecture _{Analyst Engineer Secretary}

  Designer’s View Entity=Data Entity Funct=Appl Function Node=Info Sys Funct Time=System Event End=Criterion Relationship= Data

  Agent=Role Arg=User Views Link=Line Char Cycle=Processing Cycle Means=Option Relationship Work=Deliverable e.g., Human/ e.g., Data Design e.g., Structure Chart e.g., System e.g., Control Structure Technology Interface e.g., Knowledge Architecture _{Analyst Engineer Secretary Design}

  Builder’s Entity=Segment/Row Funct=Computer Funct Node=Hardware/

  View End=Condition Relationship=Pointer/ Arg=Screen/Device System Software Time=Execute Agent=User Means=Action Key Formats Link=Line Specification Cycle=Component Cycle Work=Job e.g., Timing Definition e.g., Data Definition e.g., Program e.g., Network e.g., Security e.g., Knowledge Description Architecture Architecture Definition

  Subcontractor’s Time=Interrupt Ent=Fields Funct=Language Stmts Node=Addresses Agent=Identity End=Subcondition

  View Cycle=Machine Cycle Rel=Addresses Arg=Control Blocks Link=Protocols Work=Transaction Means=Step

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

Operational

View

  

Identifes Warfghter

al od Relationships and Information Needs

• N

  Pro ts

  Info on ter en ces Req rm

  In ati m sin d re rm uire ui atio g a an fo me g eq n E

  In nd L

  R nts sin of xch ge es eve

  Bas ls ns an

  Sup oc ang s, io ve e ls o

  New ic T ch Pr f tie por iat

  Le C

  Ex vi ech tab oc ss cti apa d nolo ility ts , A s A an bili gy en an es m es d ties m od ste lin ire

  N ed Sy qu to Ne

  Re Specifc Capabilities

Technical

  Identifed to Satisfy

Systems

  Information-Exchange

View

  Levels and Other

View

  Operational Requirements Relates Capabilities and Characteristics

Prescribes Standards and

  Technical Criteria Governing to Operational Requirements

Conventions

  Interoperable Implementation/ Procurement of the Selected System Capabilities

  

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. •

  Information Systems Technical Architecture COMDTINST 5230.45A

  Information Technology Life Cycle and

  Information Resource

  Management (cancelled)

  COMDTINST 5230.41

  Standard Terminal Application Software DeploymentCOMDTINST 5234.3

  Standard Terminal Application Software

  DeploymentCOMDTINST 5234.3

  Information Technology Life Cycle and Configuration Management Policy

  COMDTINST 9999.99

  Configuration Management Policy

  Information Resource Management (cancelled)

  COMDTINST 9999.99

  IT Life Cycle and CM Policy Consolidation

  IT Systems Development Plan (DRAFT)

  COMDTINST 9999.99

  IT Systems Development

  Plan (DRAFT)

  COMDTINST 9999.99

  Other Policy TBD

  COMDTINST 5230.41

  5231.2

  Information Systems Technical Architecture

  Standard Workstation III Configuration Management

  COMDTINST 5230.45A

  USCG Common Operation Environment

  (USCG COE) COMDTINST 5230.59A

  USCG Common

  Operation Environment (USCG COE)

  COMDTINST 5230.59A

  Standard Workstation III Configuration Management Policy COMDTINST

  5200.16

  Policy COMDTINST

  (AIS) COMDTINST

  5200.16

  USCG C4ISR Baseline Architecture COMDTINST

  3090.6

  USCG C4ISR Baseline Architecture

  COMDTINST 3090.6

  Planning Approval for Automated Information Systems (AIS)

  COMDTINST 5231.2

  Planning Approval for Automated Information Systems

  Other Policy TBD

Benefits

  Facilitates information services that provide: flexibility, interoperability, reliability, survivability, affordability, sustainability, portability, reusability, Adaptability, Compatibility

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 business • 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 customer’s needs • Reduced data-entry costs • Head-count is reduced • Increased productivity of personnel permits increased level of business • and containment of costs Improved skills raise enthusiasm and loyalty • • Efficient systems maintenance means improved service.

• 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 measures End user has direct access to shared data • New systems are developed faster and at less cost due to common data, • common code, and a shortened requirements phase Easier to evaluate and select vendor SW packages • Effective use of repository and CASE products •

  Source: Enterprise Architecture Planning Steven Spewak

  "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 that’s your assessment… You can’t complain that the systems aren’t “aligned” with the enterprise,or are inflexible, or cost too much, or that vital information is not available, or that the data you get isn’t any good, or too late, or you can’t change anything, or that I/S is slow and unresponsive… and, I am here to tell you Outsourcing isn’t going to fix the problem. Packages (in themselves) won’t fix the problem. Decentralization won’t fix the problem. And, the Internet isn’t 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 Zachman reflections on EA Planning 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)

  DISCUSSION