Commonwealth of Pennsylvania Enterprise Architecture

1
Commonwealth of PennsylvaniaEnterprise
Architecture

• Standards Committee Orientation
• June 11, 2004

2
Agenda

• Welcome / Introductions
• EA Mission
• Organization
• Governance Model
• Roles
• Domains and Disciplines
• EA Standards Committee and Domain Team Activities

3
Objectives

• Provide Enterprise Architecture Standards
  Committee (EASC) with an overview of the EA
  Governance model and new processes being
  developed
• Familiarize EASC members with their role

4
What is Enterprise Architecture?

• A clearly defined relationship depicting how the
  business architecture (business processes) and
  the system architecture (supporting IT structure)
  interrelate and change as new events occur.
• An overall plan for designing, implementing and
  maintaining the infrastructure to support the
  Enterprise business functions and underlying
  networks and systems.
• It is actionable and builds a roadmap to get
  there . . . a plan of record.

5
Enterprise Architecture

• Benefits
• Optimize resources technology, people and
  processes
• Increase business interoperability between
  Municipal, County, State and Federal Partners
• Improve business agility to support dynamic
  change
• Drives re-usability of architecture models and
  best practices
• Streamline informed decision making
• Standardize IT for cost effective delivery of
  government services
• Eliminate duplication and redundancy and reduce
  Cost of Ownership
• Improve delivery of training and business services

6
Mission Statement
To serve the Commonwealth of Pennsylvania and
its citizens by providing enterprise-wide
technology policy, standards, architecture,
information, and solutions to enhance system
interoperability, security and cost
effectiveness.
Enterprise Architecture is a guiding principle
for the Office of Information Technologys new
organization. The Bureau is responsible for
overseeing development of IT technical standards
and monitoring compliance across Commonwealth
Agencies.
7
Guiding Principles

• Champion the vision of standards of excellence in
  IT Governance
• Address the challenge to create more efficiencies
  with less cost
• Partner in the development of business and
  technology standards, policies and solutions for
  Commonwealth Enterprise resources
• Governance through prioritized investment
• Leverage existing IT resources and knowledge
• Ensure business requirements drive technology
  solutions

8
Organization
9
OA/OIT Organization
PA IT Governance Board

Mr. Art Stephens, Deputy Secretary Governors
Office of Administration
CIO
Office for Information Technology (OIT)
SERVICES SOLUTIONS
ENTERPRISE
ENTERPRISE PROJECTS
PLANNING ADMINISTRATION
INFRASTRUCTURE OPERATIONS
GEOSPATIAL TECHNOLOGIES
ARCHITECTURE
JNET Radio Enterprise Project Multi-Agency
Teams CRM Distance Learning Homeland
Security Fingerprinting/ Biometrics Grants
Mgmnt Project/Portf. Mgmt Continuity of
Government
Enterprise GIS Data standards Interoperability
Data sharing w/State, Federal Local
Govts.
Technical Standards Compliance Chief Security
Officer Network Security Mgmt Enterprise
Product Licenses EA Policy Planning
Strategic Planning OIT Budget, Procurement,
Contracts HR IT Enterprise Recruiting IT
Enterprise Training IT Enterprise Grant
Writing ITQ Program ITB Issuance Administrative
Support
Enterprise Server Farm (ESF) Exchange email
DPH Contract Service Level Mgmt LAN
Mgmt Printing Alt. Site Mgmt Desktop
Technology Network
Enterprise Application Maintenance Agency
Account Reps. Enterprise DB Dev.
Services Portal OA Application Support Knowledge
Management
10
Enterprise Architecture Organization

11
Enterprise Architecture Framework

• The Commonwealths Enterprise Architecture (EA)
  is based on NASCIOs Enterprise Architecture
  Framework
• NASCIO National Association of State Chief
  Information Officers
• NASCIO provides a toolkit that is template driven
  and adaptable to meet the needs of state and
  local governments
• Enables information sharing across traditional
  barriers
• Enhances the ability to deliver effective and
  timely services
• Supports agencies in their efforts to improve
  government functions and services

12
Business Planning Business, Strategic and
Budgetary Planning Communities of Practice
Agencies
Business Architecture
? Business Process Identification and Mapping ?
Business Intelligence ? Communities of Practice
? Policy Review and Creation? Project
Management Methodologies ? Performance
Measurement
OIT Agencies
Information Architecture
Enterprise Architecture Framework
? Business Intelligence ? Knowledge Management
and Transfer? Workflow and Document Management
? Classifying data, meta-data, ISAC ?
Enterprise Reporting ? Asset Management
Enterprise Architecture Framework
Agency Profile Database and IT Portfolios
Application Architecture
? Code Registry Re-use Component Driven ?
Application Integration ? Project Development
Frameworks and Best Practices ? IT Principles
and Tech Trends ? Training Standardization ?
Modeling and Simulation
OIT Agencies
Infrastructure Architecture
? Network Communications ? Client/Server Web
Technologies? Computing and Storage Standards ?
Services Support
13
Business / Technology Domains
EA Advisory Board
EA Standards Committee
IT Standards Technology Solutions Best Practices
14
(No Transcript)
15
Role Mapping
16
Translate strategic elements into both procedural
tactical elements to accomplish the business
goals and objectives of the Commonwealth

• Enterprise Architecture Advisory Board
• Leadership
• Technology Goals and Objectives
• Strategic Initiatives and Partnerships

• Enterprise Architecture Standards Comm.
• Technology Standards
• Policies and Procedures
• Adaptive Enterprise Architecture Planning

• Enterprise Architecture Domain Teams
• Technology and Business Alignment
• Standards and Technology Research and
  Recommendations
• Industry Best Practices

17
Enterprise Architecture Framework
Enterprise Architecture Framework This provides
the structure and procedures necessary to allow
the Domain Teams to function in isolation while
addressing business requirements.

• There are 9 IT Domains that include
• Platform - Network
• Applications - Integration
• Access - Information
• Security - Privacy
• Systems Management
• They are further categorized into technical
  functional areas described as IT Disciplines.

18
Domains and Disciplines

• Domains Logical groupings of disciplines that
  form the main building blocks within the
  architectural framework.
• Disciplines The logical functional subsets of a
  Domain. Disciplines allow further breakdown of
  the Domain into manageable pieces (for example,
  within the Systems Management Domain you may have
  Asset Management, Change Management, Problem
  Management, etc.).
• Technology Areas are those technical topics that
  support the functional areas within the
  Discipline (for example, the technology area
  within the Database Management Discipline might
  be Relational Database, Desktop Database, etc.).
  Each technology area will have associated
  products, protocols or configurations.

19
Domains and Disciplines

• Product Components within a technology area
  include protocols, products (families) and
  configurations. Examples of Product Components
  identified within the technology area of
  Relational Database include Oracle, SQL Server
  and DB2, etc.
• Compliance Components Identify guidelines,
  standards and legislative mandates associated
  with a Discipline, Technology Areas and/or
  Product Component, as appropriate.

20
Enterprise Architecture Process Overview

• The EASC will develop the project charter for all
  projects assigned to domain teams or technical
  work groups that will identify
• Business objectives and business drivers
• Guiding principles
• Existing ITBs that may be impacted or new ITBs
  that are needed
• Specific outcomes / deliverables
• Success criteria
• Timeline for completion

21
Enterprise Architecture Process Overview

• The Domain Team or technical work group will
• Gather enterprise and agency requirements for
  analysis
• Solicit executive feedback where exceptions or
  gaps exist
• Determine if existing solutions can be leveraged
• Review best practice and industry analysis
  reports
• Engage business partners to obtain additional
  information where appropriate
• Develop technology solutions and/or options that
  include
• Cost/benefit analysis
• Total Cost of Ownership
• ROI Analysis
• Develop content for the ITB and submit to the
  EASC for review and feedback
• Develop best practice policies and procedures
  that support ITBs

22
EASC Participant Profiles

• EASC Team Participants
• Support the gathering, review and analysis of
  Commonwealth business requirements and make
  recommendations on technology solutions based on
  research and analysis performed by the Domain
  Teams
• Identify business drivers or environment trends
  that require changes to the IT strategic plan
• Support efforts to model the enterprise in its
  current (as is) state and participate in efforts
  to analyze and bridge gaps in order to move to
  the to be state
• Provide input into the development of and updates
  to the EA standards and policies (with an
  emphasis on enterprise compliance)
• Provide support for the development of business,
  information, applications and infrastructure
  architectures within the EA
• Key Skills
• Leadership
• Enterprise view
• Collaborative
• Objective

23
EA Domain Participant Profiles

• Domain Team Participants
• Provide subject matter expertise to one or more
  of the EA Domains
• Gather, analyze and finalize Commonwealth
  business requirements
• Provide recommendations on the development of
  IT standards and policies
• Develop solutions and submit for review to the
  EA Standards Committee
• Focus on enterprise technology issues, not just
  a single agency perspective
• Understand that business requirements drive all
  technology decisions
• Develop solutions that
• Fulfill business requirements
• Leverage existing technology
• Adhere to all standards and policy
• Key Skills
• Technology expertise in a domain area(s)
• Enterprise view
• Collaborative
• Objective

24

• The following slides will provide a brief
  description of the disciplines within the 9
  domains that will be part of the Enterprise
  Architecture and includes examples of typical
  projects within each domain.
• These domains are
• Access
• Information
• Application
• Integration
• Network
• Platform
• Systems Management
• Privacy
• Security

Enterprise Architecture Domains and Disciplines
25
Enterprise Architecture Domains and Disciplines

• Access Domain
• Access - electronic delivery of information and
  services. Includes internet, intranet,and
  extranet access.
• Branding - defines the "look and feel" for
  government websites.
• Accessibility - applies to tool sets used to
  facilitate the accessing of informationand
  services by disabled citizens.
• Examples Policies governing internet access to
  applications standards for deploying technology
  for use by disabled citizens or employees Anti
  Spam, etc.
• Information Domain
• Data Management - data definition, design,
  management and administration of data.
• Knowledge Management - systematic process of
  finding, selecting, organizing anddistilling
  information. (Examples Document Management Data
  Warehousing Data-marts Metadata , etc.).
• GT / GIS - defines the standards and technologies
  for implementation of Geographic Information
  Systems.
• Data Storage - acquisition and deployment of data
  storage media.
• Examples Database standards Business
  Intelligence GIS Mapping Image Repositories

26
Enterprise Architecture Domains and Disciplines

• Application Domain
• Application Development Management - technologies
  that define how applications are designed,
  documented, and maintained technologies that
  optimize the use/reuse of application components
  strategies for the retention/phase out of legacy
  applications.
• Electronic Collaboration tools that facilitate
  the interaction of the workforce andpromote
  group productivity. These include e-mail,
  directory services and otherperson-to-person or
  group collaboration tools.
• Examples Active Directory Upgrade (2003),
  MVSJVM Extraction, DSF Assessment Project,
  selection of new application development tools.
• Integration Domain
• Functional Integration - responsible for the
  conceptual and logical models, whichshow how
  each of the functional areas, various application
  systems, andbusiness information requirements
  tie together.
• Middleware - the components that create an
  integration environment betweenthe user
  workstations and legacy and server environments
  provides interfacesbetween applications and
  network communications mechanisms.
• Examples Standards for middleware or broker
  software, SURE/JNET/CLEAN integration.

27
Enterprise Architecture Domains and Disciplines

• Network Domain
• Physical Network - includes network
  infrastructure for the computing environment.
  Consists of infrastructure elements, physical
  components and protocols. It does not include
  user workstations, server platforms or their
  operating systems.
• Network Management management of the
  communications infrastructure for the
  organizations distributed computing environment.
  It defines the structure, topologies,
  bandwidth management, carrier services and
  protocols, includes consideration for public
  access from private and kiosk workstations,
  wireless devices and PCs.
• Examples Telecommunications RFP, Operation
  Secure Enterprise (OSE).
• Platform Domain
• Platform - decision-making criteria for the
  acquisition and deployment of computing and
  data storage hardware. Components of the
  Platform discipline range from enterprise-
• class servers to workstations and handheld
  computing devices.
• Configuration Management - criteria for the
  set-up and provisioning of computing and data
  storage hardware specifications and its operating
  software and systems.
• Provides for the inclusion of industry standard
  operating systems and utility systems running
  on the platforms.
• Example Application hosting policy.

28
Enterprise Architecture Domains and Disciplines

• Systems Management Domain
• Asset Management - systems required for the
  tracking and reporting of assets owned, service
  level agreements (SLAs), capacity management,
  cost management and personnel skills inventory.
• Change Management - version control of all IT
  assets.
• Console/Event Management - monitoring and
  controlling components of all collective
  hardware and software within the data center.
• Help Desk / Problem Management - monitoring and
  controlling problem reporting and resolution.
• Business Continuity - disaster recovery and
  restoring the enterprise to full functionality.
• Examples Alternate Site Design and Planning.

29
Enterprise Architecture Domains and Disciplines

• Privacy Domain
• Profiling - tools used for creating, maintaining,
  and utilization of profiles for the various
  stakeholders of the organizations services.
• Personalization - tools used for creating,
  maintaining and implementing personalization of
  services and information.
• Privacy - addresses the privacy concerns of
  citizens and agencies, addresses all state and
  federal laws related to privacy issues.
• Examples Compliance to HIPAA, CHRII, IRS
  regulations.
• Security Domain
• Enterprise Security provides for audits and
  business process reviews for monitoring and
  ensuring the security across the organizations
  enterprise. Includes securing the physical
  assets from theft and vandalism.
• Network Security - monitoring and ensuring
  security across the organizations network.
• Host Security - monitoring and ensuring security
  across the organizations platform
  infrastructure.
• Examples Operation Secure Enterprise, Identity
  Management/PKI, Enterprise Security Assessment.

30
EASC and Domain Team Activities
31
(No Transcript)
32
(No Transcript)
33
Getting Started

• Setting Enterprise Standards - To be completed
  over the next 12 months
• We need to assess the current state of technology
  within the Commonwealth and understand what
  technology initiatives the Agencies have planned
• Based on this assessment
• Evaluate the impact on Commonwealth standards
• Identify technologies that should be phased out
• Identify technologies that are emerging

34
Getting Started

• Over the next month, Agencies will be asked to
  complete a Technology Profile
• EA will compile the current as is for the
  Enterprise
• Working together we will
• Evaluate the as is
• Begin to create the to be Enterprise
• Develop a plan based on the gap analysis

35
Templates / Examples- Technology Profile
Example- Technology Classifications
36
Technology Classifications

• Sunset Components that are in use, but do not
  conform to the stated architecture direction, if
  the date of discontinuance has been identified.
  The date of discontinuance indicates the date
  that the Component will no longer be acceptable
  for use within the architecture.
• End of Life - Components are in use, but do not
  conform to the stated architecture direction.
  However, these have no date of discontinuance
  identified. Components should not be used to
  develop new applications. Extensive
  modifications to these systems require review to
  determine if they can/should be redeployed using
  newer technology.
• Current This classification is given to those
  components that meet the requirements of the
  architecture. These recommended Components should
  be used in deployment of technology solutions.
• Emerging This classification is given to
  components that have the potential to become
  current. While identified as Emerging these
  Components should be used only in pilot or test
  environments, under very controlled regulations.

37
Developing Recommendations

• Project Documentation
• Business Case
• Project Charter
• Defines the scope of the initiative and the
  opportunity
• Defines business drivers
• Business requirements
• Defines functional requirements
• Proposed Solutions
• A synopsis of options considered and
  recommendations
• EA Web Site
• http//www.oit.state.pa.us/eashare/site/default.as
  p?eashareNav

38
Templates / Examples- Project Charter Template
/ Example
39
Priorities by Domain Team
40
Priorities by Domain Team
41
Confidentiality Statements