Developing a Results Driven Enterprise Architecture_September ...
-
date post
21-Oct-2014 -
Category
Business
-
view
391 -
download
1
description
Transcript of Developing a Results Driven Enterprise Architecture_September ...
Mark GriffithState of North Carolina - Senior Enterprise Architect
Thursday, September 11, 2003, 1:15 PM - 2:30 PM
· STRATEGY and PLANNING · QUALITY ASSURANCE
ENTERPRISE ARCHITECTURETECHNOLOGY ASSISTANCE
Developing a Results-Driven Enterprise Architecture
September 11, 2003 © Copyright State of North Carolina 2003 2
Agenda
• Overview of North Carolina IT Governance
• IT Project Review Process
• Life Cycle of IT Investments
• Overview of the NC Enterprise Architecture
• Enterprise Architecture Review Findings
• Overview of the Resulting Changes to the EA
September 11, 2003 © Copyright State of North Carolina 2003 3
Governor’sOffice
Governmental Lines of Business(Also Known as State Agencies)
State CTOHead of ETS
COO CFO CSOCRM & Public
Relations
State Chief Information Officer
StatewideIT
Procurement
Statewide IT LeadershipCentral
IT Agency
NC IT Governance
September 11, 2003 © Copyright State of North Carolina 2003 4
Enterprise Technology Strategies Office
• Review agency IT projects and recommendapproval to governing bodies.
• Provide leadership, guidance, and mentoringto agencies on approaches to IT, IT procurement,and IT project management.
• Independent Verification & Validation on keyprojects, services, and systems.
• Provide enterprise IT planning and strategies forthe State CIO and governing bodies.
NC IT Governance
September 11, 2003 © State of North Carolina 2003 5
NC IT Governance
Governor
State Chief Information
Officer
Information Resource
ManagementCommissionOther
IT Boardsand
Commissions
NorthCarolinaGeneral
Assembly
Appoint Appoint
Representation Support
Advice
Appoint
September 11, 2003 © Copyright State of North Carolina 2003 6
Project Closeout
Project Review & Closeout
Project Review Process
Monthly Project Status Reporting and
Independent QA Reviews
IRMC Project
Certification
Project Concept Definition
Project Implementation
AgencyStrategic Plan
Business Case
Statewide and agency technical architectures -security & application
architectures
September 11, 2003 © Copyright State of North Carolina 2003 7
Life Cycle of IT Investments
Phase 1Phase 1 – Planning, – Planning, Budgeting and Funding Budgeting and Funding (State Expansion (State Expansion Budget Process) Budget Process)
Phase 3Phase 3 - Operation, - Operation, Maintenance and Maintenance and
RetirementRetirement
Phase 2Phase 2 - Project Certification - Project Certification and Implementationand Implementation
o Potential Investments Approved by Agency
o Potential Investments Certified by State CIO and Reviewed by IRMC
o Potential Investments Included in Governor’s Budget
o Projects Funded by General Assembly
o Candidate IT Investments for Agency Review
o Operational Assets Under Budget Review for Cost-Effectiveness
o Completed Projects Creating Operational Assets
o Projects Being Implementedo Certified Projects
NCNCEnterpriseEnterprise
ArchitectureArchitecture
September 11, 2003 © Copyright State of North Carolina 2003 8
North Carolina Enterprise Architecture
• It is an Enterprise-Wide Technical Architecture; we call it a Statewide Technical Architecture.
• It is NOT currently an Enterprise Business or Information Architecture.
• It is NOT a product list.
• We have a mature architecture. We began using the STA as a framework for projects in 1997.
• We recently completed a self-directed review.
IT In North Carolina
September 11, 2003 © Copyright State of North Carolina 2003 9
EA Review Findings
We Found That:
• Agencies often had difficulty interpreting the principles, practices, and standards.
• There was resistance, on the part of some agencies, to following the STA.
• The technical architecture was not very usable.
• The technical architecture was not current.
• Change happened very slowly.
• The architecture team was too small.
September 11, 2003 © Copyright State of North Carolina 2003 10
EA Review Findings
We Found That:
• The technical architecture was too narrowly focused.
• There were inconsistencies in the architecture.
• We did not have a way of measuring whether having an Enterprise Architecture was having thedesired effect.
• The supporting products and processes were oftenpoorly defined.
September 11, 2003 © Copyright State of North Carolina 2003 11
Presentations
Glossary Workgroups&
Committees
WhitePapers
PurchasingContracts
ImplementationGuidelines
Policies &Legislation
Principles,Practices, Standards
Architecture Products
Informational items that comprise the enterprise technical architecture.
September 11, 2003 © Copyright State of North Carolina 2003 12
NCEnterprise
Architecture
Maturity ReviewEvergreen
Strategy
Trai
ning
Pla
n
ContentDevelopment
Gov
erna
nce
Architecture Processes
Processes are the methods used to maintain the Architecture.
September 11, 2003 © Copyright State of North Carolina 2003 13
Contact Information
Mark GriffithSenior Enterprise [email protected]
State of North CarolinaEnterprise Technology Strategies OfficePO Box 17209Raleigh, North Carolina 27619-7209
North Carolina Enterprise Architecture Websitehttp://www.ncsta.gov