Enterprise Architecture Information Policy CouncilPresentation Transcript
Enterprise Architecture Information Policy Council Apr 19, 2001
Why Enterprise Architecture?
Electronic government is fundamentally changing the way citizens interact with the government, both as consumers of government services and stakeholders in the affairs of state
The primary design goal for information systems must be to enable rapid change in business processes and the applications and technical infrastructure that enable them.
Provide better interoperability of agency systems
Deploy advanced electronic government services
Enterprise Technical Architecture
A logically consistent set of principles, standards, and models that:
Are derived from business requirements
Guide the engineering of an organization’s information systems and technical infrastructure across various domains
Components of Technical Architecture
Conceptual Architecture - the top-level set of principles and standards that guide the domain architectures
Domain Architectures - Logical groupings of related technologies
e.g. application, network, data, middleware, groupware, security, accessibility
Business Drivers I
Appropriate government information and services will be accessible regardless of location, time, method of access and group (e.g. language, culture, age and ability)
Access to information and services will be authenticated to the degree required by specific information and services. Information will be protected to the level required both internally and externally.
Provide coherent and navigable access across multiple points of interaction for government information and services (I.e., “no wrong door”) spanning departments and other levels of government.
Business Drivers II
Government information and services will quickly respond to the client’s changing expectations
Government will reduce the total cost of ownership of IT investments though the elimination of duplicate infrastructures, support services, and leveraging economies of scale.
The government will increase attractiveness for business investment to build stronger local economies.
Start with existing Architecture Advisory Group and Architecture Working Group
Use shortcut process to display tangible progress
Use an existing template to develop a draft with small team from the Working Group
Get go-ahead from Advisory Group
Develop the conceptual and domain architectures with parallel teams.
Cover Design ENTERPRISE ARCHITECTURE FOR DUMMIES CIO EDITION A Reference for The Rest of Us! 21 Hundred Sold
Operational focus of agency IT efforts
Impact on smaller agencies
Existing efforts, e.g.:
Common security infrastructure (PKI)
Northstar portal upgrades
Electronic Government Services collaborative
Recordkeeping Metadata study
Adoption and Implementation
Willingness of agencies to adhere to the architecture in future development:
Compelling perceived advantage
Substantial natural consequence
Drafting Committee - mid March
Working Group approval - Mid April
Advisory Group approval - late May
Domain architecture definitions - June-September
Architectural Reference, version 1 - October
Finis Per altro informazione [email_address] 651-297-5568
Attributes of State Government
Lack of longevity and continuity in leadership
Lack of incentives to search for intra-agency or inter-agency savings
Historical lack of central leadership in statewide IT efforts
Perceived lack of understanding and support in the legislature for adequate resources
Concern about the ability to share data in an environment of much tighter privacy restrictions
Technical Architecture Process K e y E n t e r p r i s e D r i v e r s W h a t , W h o , W h e n , W h e r e C o m m o n R e q u i r e m e n t s V i s i o n D o m a i n A r c h i t e c t u r e W h a t , n o t H o w S e t o f P r i n c i p l e s E n v i r o n m e n t a l T r e n d s E n t e r p r i s e B u s i n e s s S t r a t e g i e s B u s i n e s s I n f o r m a t i o n R e q u i r e m e n t s R e q u i r e m e n t s f o r T e c h n i c a l A r c h i t e c t u r e C o n c e p t u a l A r c h i t e c t u r e C o n c e p t u a l A r c h i t e c t u r e A s - I s A s s e s s o f B e s t P r a c t i c e s I d e n t i f y D o m a i n s D o m a i n P r i n c i p l e s I d e n t i f y T e c h n o l o g i e s A s - I s A s s e s s m e n t T e c h n o l o g i e s I d e n t i f y S t d s , P r o d u c t s & C o n f i g s Best Practices
Enterprise Architecture Process
Silo Processes & Applications
Applications optimized at program/department level
Theme: Empower the program director
IT optimized around each program area
What does it all mean?
All of the books in the world contain no more information than is broadcast as video in a single large American city in a single year. Not all bits have equal value. — Carl Sagan
absolute power is sorta neat, though. — Anonymous
Data can be assembled into information .
Information is the currency of democracy. — Thomas Jefferson
Information can be used to create knowledge.
For knowledge, too, is itself power. — Francis Bacon There is no knowledge that is not power. — Ralph Waldo Emerson
All power to the people. — Eldridge Cleaver
Digital economy with the Internet
Cost curves - technology down, talent up
Demand for rapid new and innovative services and access to them