Enterprise Architecture - PowerPoint PPT Presentation

Loading...

PPT – Enterprise Architecture PowerPoint presentation | free to view - id: 20641-Y2MyN



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

Enterprise Architecture

Description:

Enterprise Architecture. Information Policy Council ... Enterprise Technical Architecture ... Enterprise Architecture Process. Silo Processes & Applications ... – PowerPoint PPT presentation

Number of Views:103
Avg rating:3.0/5.0
Slides: 17
Provided by: dennis89
Category:

less

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

Title: Enterprise Architecture


1
(No Transcript)
2
Enterprise Architecture
  • Information Policy Council
  • Apr 19, 2001

3
Why Enterprise Architecture?
  • Electronic government is fundamentally changing
    the way citizens interact with the government,
    both as consumers of government services and
    stakeholders in the affairs of state

4
Design Goals
  • Facilitate change
  • The primary design goal for information systems
    must be to enable rapid change in business
    processes and the applications and technical
    infrastructure that enable them.
  • Provide better interoperability of agency systems
  • Deploy advanced electronic government services

5
Enterprise Technical Architecture
  • A logically consistent set of principles,
    standards, and models that
  • Are derived from business requirements
  • Guide the engineering of an organizations
    information systems and technical infrastructure
    across various domains

6
Components of Technical Architecture
  • Conceptual Architecture - the top-level set of
    principles and standards that guide the domain
    architectures
  • Domain Architectures - Logical groupings of
    related technologies
  • e.g. application, network, data, middleware,
    groupware, security, accessibility

7
Business Drivers I
  • Appropriate government information and services
    will be accessible regardless of location, time,
    method of access and group (e.g. language,
    culture, age and ability)
  • Access to information and services will be
    authenticated to the degree required by specific
    information and services. Information will be
    protected to the level required both internally
    and externally.
  • Provide coherent and navigable access across
    multiple points of interaction for government
    information and services (I.e., no wrong door)
    spanning departments and other levels of
    government.

8
Business Drivers II
  • Government information and services will quickly
    respond to the clients changing expectations
  • Government will reduce the total cost of
    ownership of IT investments though the
    elimination of duplicate infrastructures, support
    services, and leveraging economies of scale.
  • The government will increase attractiveness for
    business investment to build stronger local
    economies.

9
Minnesota Version
  • Start with existing Architecture Advisory Group
    and Architecture Working Group
  • Use shortcut process to display tangible progress
  • Use an existing template to develop a draft with
    small team from the Working Group
  • Get go-ahead from Advisory Group
  • Develop the conceptual and domain architectures
    with parallel teams.

10
Document Structure
11
Domain Structure
  • Purpose
  • Scope
  • Principles
  • Best Practices
  • Implementation Guidelines
  • Standards

12
Cover Design
13
Other Considerations
  • Operational focus of agency IT efforts
  • Impact on smaller agencies
  • Existing efforts, e.g.
  • Common security infrastructure (PKI)
  • Northstar portal upgrades
  • Electronic Government Services collaborative
  • Recordkeeping Metadata study

14
Adoption and Implementation
  • Willingness of agencies to adhere to the
    architecture in future development
  • Compelling perceived advantage
  • Substantial natural consequence
  • OT leadership
  • IPC sponsorship

15
Schedule
  • Drafting Committee - mid March
  • Working Group approval - Mid April
  • Advisory Group approval - late May
  • Domain architecture definitions - June-September
  • Architectural Reference, version 1 - October

16
Finis
  • Per altro informazione
  • Dennis.Fazio_at_State.MN.US
  • 651-297-5568

17
Attributes of State Government
  • Lack of longevity and continuity in leadership
  • Lack of incentives to search for intra-agency or
    inter-agency savings
  • Historical lack of central leadership in
    statewide IT efforts
  • Perceived lack of understanding and support in
    the legislature for adequate resources
  • Concern about the ability to share data in an
    environment of much tighter privacy restrictions

18
Technical Architecture Process
19
Enterprise Architecture Process
20
Silo Processes Applications
  • Applications optimized at program/department
    level
  • Theme Empower the program director
  • IT optimized around each program area

21
What does it all mean?
  • Data can be assembled into information.
  • Information is the currency of democracy. Thomas
    Jefferson
  • Information can be used to create knowledge.
  • For knowledge, too, is itself power. Francis
    BaconThere is no knowledge that is not power.
    Ralph Waldo Emerson
  • All power to the people. Eldridge Cleaver
  • Power corrupts

absolute power is sorta neat, though.
Anonymous
  • All of the books in the world contain no more
    information than is broadcast as video in a
    single large American city in a single year. Not
    all bits have equal value. Carl Sagan

22
Trends
  • Ubiquitous bandwidth
  • Intelligent devices
  • Information dependency
  • Digital economy with the Internet
  • Cost curves - technology down, talent up
  • Demand for rapid new and innovative services and
    access to them

23
Ad Hoc Integration
24
Question of the day
  • Is the entire State government an Enterprise?

25
Enterprise Architecture Process
About PowerShow.com