Enterprise Architecture A State Government Perspective

1
Enterprise ArchitectureA State Government
Perspective

• SEARCH Conference
• Enterprise Architecture
• March 13, 2006
• Washington D.C.

Presented by Eric Sweden
2
About NASCIO

• NASCIO represents state chief information
  officers and information resource executives from
  the fifty states, six territories, and D.C.
• NASCIO's mission is to foster government
  excellence through quality business practices,
  information management, and technology policy.

3
Key Partnerships and Collaboration

• National Governors Association (NGA)
• National Conference of State Legislatures (NCSL)
• Council of State Governments (CSG)
• National Association of State Procurement
  Officers (NASPO)
• National Association of State Auditors,
  Controllers and Treasurers (NASACT)
• National Association of State Telecommunications
  Directors (NASTD)
• National Association of State Budget Officers
  (NASBO)

• American Council for Technology (ACT)
• Global Justice Information Sharing Initiative
• SEARCH
• National Electronic Commerce Coordinating Council
  (NECCC)
• eHealth Initiative
• NRC Computer Science and Telecommunications Board
  
• Information Technology Association of America
  (ITAA)
• International Association of Privacy
  Professionals (IAPP)
• Metropolitan Information Exchange (MIX)

4
NASCIO Committees 2006
Enterprise Infrastructure and Services
Information Security and Privacy
Enterprise Architecture
Health Information Technology
Project Management Forum
5
Holistic Enterprise Architecture
Enterprise Architecture is amanagement
engineering disciplinethat presents a holistic,
comprehensive view of the enterpriseincluding
strategic planning, organization, relationships,
business process, information, and operations.
The organization must be viewed as a fluid
changing over time as necessary based onthe
environment and managements response to that
environment.
6
The Rationale for EA

• Strategic intent supports guiding principles,
  objectives and strategies ability to frame and
  apply
• Discipline for understanding the wants and needs
  of constituents
• A blueprint for the desired future
• Making order out of chaos rules
• Transform current state into future state
• Traceability

7
Why Enterprise Architecture?

• Reconcile vertical and horizontal views of the
  enterprise
• Guide and Coordinate technology investments
  enterprise view
• Improve access and sharing of information
• Make better decisions reduce / manage
  complexity and diversity
• Support need for integration enterprise-wide
  processes with consistency
• Lead Government Transformation

8
Enterprise Architecture Value Chain
9
Strategic Planning Relationships
Strategic Planning -what trends -what
impact -what is our response
Influences
Influences
Business Factors
Legislative Factors
Technology Planning
Infrastructure Planning
Enabled through
Capability Management
Business Process Planning
Capital Planning
Capabilities delivered through
Business Services
Collaborative Information Exchange
Portfolio Management -management
initiatives -projects -programs
10
Holistic Enterprise Architecture
Should include all lines of business
Public Health
Environmental
Human Services
Transportation
Education
Public Safety
Traditional boundaries are becoming fuzzy
11
Inter - Enterprise Architecture

• managing inter-enterprise operability

Federal
State
County
12
EA key to managing interoperability
Enterprise Architecture
Toxicology
Investigation
Epidemiology
Justice
Intelligence
Defense
13
EA key to managing global interoperability
Global Policy
Enterprise Architecture
Anti-Terrorism
Communication
Transportation
Economic Alliances
Law
Defense
Justice
Intelligence
Social / Economic Policy
Public Health Policy
14
National EA Assessment Processconducted in 2005

• Developed clear objectives for assessment
• Designed a simple survey instrument
• Ensured diversity in
• geography
• population
• economics
• Compiled the results of the survey
• Assessed the results and developed
• observations
• Developed calls to action

15
How far have we come?
2005
1999

• Five states had an EA program

• 95 of respondents have embraced enterprise
  architecture
• 71 of respondents believe its necessary to have
  dedicated EA staff
• 92 of respondents - necessary to have a defined
  process for EA

16
Direction for the states
Graphic source OMB
17
National Census of StatesEnterprise Architecture
Do you have an enterprise architecture program?
18
What does your EA program include?
73.7 Technical Architecture 52.6 Security
Architecture 18.4 Business Architecture 36.8
Data Architecture 18.4 Process
Architecture 55.3 Architecture Program
Management 44.7 Enterprise Architecture
Consulting 15.8 Enterprise Performance
Management 57.9 Project Management
19
Functional Roles
26.3 Business Architect 34.2 Data
Architect 23.7 Process Architect 52.6 Technical
Architect 26.3 Application Architect 36.8
Network Architect 39.5 Security Architect 42.1
Architecture Program Manager 36.8 Enterprise
Architecture Consultant 10.5 Enterprise
Performance Manager 52.6 Chief Enterprise
Architect 36.8 Chief Security Officer 15.8
Training Manager 13.2 Change Manager 13.2
Other, (please list)
20
Do you have performance metrics?
Yes 23.7
No 34.2
Plan to 42.1
21
EA and the States

• Discipline adoption and recognition of value is
  clearly growing
• Primarily a CIO responsibility
• Chief IT Architects 36
• Still need to engage business side sell
• Road to maturity is slow and

• bumpy

22
EA Assessment Observations

• Strong adoption of the enterprise architecture
  discipline across the states
• Emphasis on technology architecture prevails
• Some states broadening into specialized areas of
  EA
• business architecture
• performance management
• process architecture
• change management

23
More Observations

• CIO role in EA If you dont, who will?
• Need to promote the value of the specialized
  areas
• NASCIO products have been well received where
  there is awareness
• Need to build broader exposure through marketing
  and awareness
• NASCIO should continue to maintain the viability
  of its EA program

24
Direction for the states

• Pennsylvania Bureau of Enterprise Architecture
• Missouri Enterprise Architecture Program
  Influence
• Connecticut Enterprise Architecture
  Facilitation
• North Carolina Central Enterprise Architecture
• Illinois Enterprise Architecture Framework
  
• Methodology
• Indiana Mapped to Business Reference Model
• Kansas Integration of EA, PMO, Strategic
  Planning,
• Legislative Process

25
NASCIO Publications
26
Holistic Enterprise Architecture
Tool-Kit Content
Governance
Business
Information Systems
Technical
Solution
27
Templates
28
Strategic IT Targets

• Enterprise security solutions web filtering,
  virus, spam, spyware
• Infrastructure and services consolidation
• Wireless interoperability
• Configuration Management
• Portal integration - content management approach
• Connectivity broadband initiatives

29
Emphasis on Business Disciplines

• More emphasis on state mission and IT strategic
  alignment
• Project and portfolio management PM framework,
  methodology, education, training, tools and
  oversight
• Enterprise architecture
• Business case and risk assessment
• Procurement reform - leverage buying power

30
State CIO Challenges

• Champion of Change/Transformation
• Security Imperative culture process
• Selling Enterprise Architecture
• Identifying innovative funding
• Coordination and collaboration through the layers
  of government information sharing
• Focus on outcomes vs. outputs

31
On the Horizon

• Government Transformation
• IT as a strategic resource in state homeland
  security efforts
• Health IT and health information exchange
  health networks and e-medical records
• Privacy implications of emerging technologies -
  RFID
• Managing geospatial assets
• Electronic records management preserving born
  digital
• Dealing with e-waste

32
Direction for the states
Governance Defining and Managing Services
Business Process Improvement
Government Transformation Value
Added Citizen Services
Integration with project / program mgmt
and procurement
33
Enabling State Architects
Knowledge Areas

• Funding and Budgeting Process
• Legislative Processes
• Governance Processes
• Program and Project Planning Best Practices
• Procurement Processes
• Enterprise Architecture Disciplines and Domains
• Communication and Marketing Approaches
• Facilitation Approaches

34
For More Information

• Visit NASCIO _at_ http//www.nascio.org/
• Eric Sweden
• NASCIO
• 201 East Main Street, Suite 1405
• Lexington, KY 40507
• 859-514-9189
• esweden_at_AMRms.com
• Thank You