25
Enterprise Architecture The Arkansas Approach

Enterprise Architecture

  • Upload
    harlan

  • View
    72

  • Download
    3

Embed Size (px)

DESCRIPTION

Enterprise Architecture. The Arkansas Approach. Key Areas. What is enterprise architecture? Why is it important? How you can participate Current status Case studies Next steps. What is EA?. - PowerPoint PPT Presentation

Citation preview

Page 1: Enterprise Architecture

Enterprise ArchitectureThe Arkansas Approach

Page 2: Enterprise Architecture

2

Key Areas

• What is enterprise architecture?• Why is it important?• How you can participate• Current status• Case studies• Next steps

Page 3: Enterprise Architecture

What is EA?

Enterprise architecture is the process of translating business vision and strategy into effective enterprise change by creating, communicating and improving the key requirements, principles and models that describe the enterprise's future state and enable its evolution. The scope of the enterprise architecture includes the people, processes, information and technology of the enterprise, and their relationships to one another and to the external environment.

Page 4: Enterprise Architecture

What is EA?

Enterprise Business Architecture• What processes are state-wide process and

which are agency or entity specific?• What/how are business processes defined?• How should processes in different

organizations be interfaced to be most efficient?

Page 5: Enterprise Architecture

What is EA?

Enterprise Information Architecture• What data (in what applications) should be

managed at the enterprise level as an enterprise asset?

• Who owns the data? (business owner, IT steward, system of record, system of reference)

• How do I manage information (decision support) and operational (transactional) data?

Page 6: Enterprise Architecture

What is EA?

Enterprise Technology Architecture• How do I provide reliable, high-performance, cost-effective

connectivity between sites and to the community?• How do I transform transactional data into useful

information that people can access securely and effectively?• What client and server platforms should I invest in , and how

do I manage them cost-effectively?• How do I deploy technology in a way that manages risk:

protecting data, defending and controlling my assets?

Page 7: Enterprise Architecture

What is EA?

Enterprise Solution Architecture• How do I implement critical solutions for the

State to get a more agile environment infrastructure?

• Where do systems begin and end? How do I distribute functionality and interfaces logically and sensibly?

Page 8: Enterprise Architecture

What is EA?

Page 9: Enterprise Architecture

What is EA?

Page 10: Enterprise Architecture

10

Why is EA important?

• One of the main issues is that common problems are addressed differently

• If there is ever a need to plan for more than one project or application at a time, or is there a project that will involve more than one business unit? If so, enterprise architecture is beneficial

Page 11: Enterprise Architecture

11

Why is EA important?

• Ensuring the linkage of IT to state business strategy• Improving interoperability and integration of systems• Increasing agility to meet changing requirements• Improving security • Reducing risk• Improve quality• Identifying innovation opportunities

Page 12: Enterprise Architecture

12

Current Status

• Project charter has been created that outlines• Scope of the project• Deliverables• Risks• Training• Communications plan

Page 13: Enterprise Architecture

13

Current Status• The Team:

• Administrative Office of the Courts • Arkansas Crime Information Center• Arkansas Science Technology Authority• Arkansas State Library• Dept. of Health• Dept. of Finance and Administration• Dept. of Human Services• Dept. of Labor • Economic Development• Highway and Transportation

Page 14: Enterprise Architecture

14

Current Status

• What’s been created?– Identified and documented:• Goals• Trends (environmental and technology)• Strategies• Requirements

– State of Arkansas Strategic Plan for Information Technology

– www.dis.arkansas.gov

Page 15: Enterprise Architecture

DRAFT 15

Technology Trends

Page 16: Enterprise Architecture

16

Current Status

• What’s been created?Current state• Hardware• Software• Major applications• Projects• IT Support costs

Page 17: Enterprise Architecture

17

Hardware Software Labor Training Services Other -

200,000,000

400,000,000

600,000,000

800,000,000

$37243119.6 M $26725106.6 M

$65644224.1 M

$2513479.3 M

$729218993.9 M

$49541895.9 M$28305905.8 M $25789020.0 M

$71291186.2 M

$1125599.0 M

$744513098.1 M

$51810569.9 M

FY12 FY13

Page 18: Enterprise Architecture

18

Current Status

Working Groups & Domain Teams• Security• Network• SharePoint• Adobe

Page 19: Enterprise Architecture

19

SUCCESSFUL EXAMPLE OF ENTERPRISE ARCHITECTURE

Problem: The IT planning process identified 10 different vendors providing anti-virus software in the state environment and over 60 different versions.

Page 20: Enterprise Architecture

20

ANTI-VIRUS AND ENDPOINT PROTECTION STATE CONTRACT

Solution: Create a security working group tasked with identifying requirements for anti-virus and endpoint protection tools and provide the information to DFA-Office of State Procurement who put out the requirements for bid.

Page 21: Enterprise Architecture

21

ANTI-VIRUS AND ENDPOINT PROTECTION STATE CONTRACT

Results• Three vendors provided qualifying bids with average

savings of 40% below what was paid last year• Annual savings realized is approximately $117,000 • Additional benefits• Easier to manage• Enterprise more protected• Contract is available to K12, counties and cities

Page 22: Enterprise Architecture

22

Page 23: Enterprise Architecture

ENCRYPTION STATE CONTRACT

Results• Three vendors provided qualifying bids with average

savings of 20% below what was paid last year• Annual savings realized is approximately $22,000 • Additional benefits• Solutions are vetted by group of SMEs• Enterprise more protected• Contract is available to K12, counties and cities

23

Page 24: Enterprise Architecture

24

Page 25: Enterprise Architecture

25

Next Steps

• Complete EA principles• Begin documenting future state architecture• Create gap analysis or road map• Identify specific areas of need that need to be architected• Create a team of subject matter experts and develop

solutions• Review documentation on at least an annual basis and

revise as necessary• Define and implement governance