1 / 25

Enterprise Architecture

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

harlan
Download Presentation

Enterprise Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enterprise Architecture The Arkansas Approach

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

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

  4. 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?

  5. 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?

  6. 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?

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

  8. What is EA?

  9. What is EA?

  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

  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

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

  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

  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

  15. Technology Trends DRAFT

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

  17. Current Status Working Groups & Domain Teams • Security • Network • SharePoint • Adobe

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

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

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

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

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

More Related