Departmental Report 12/2002

292 views

Published on

Published in: Business, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
292
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
8
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • The objective of this meeting is to introduce for discussion, the concept of Enterprise Architecture Planning. During our discussion, the following questions should be considered: What is EAP? What is it used for? Why should we do it?
  • When we say Enterprise Architecture Planning, the Architecture part is a comprehensive blueprint of an organization. The planning part is the definition, development and most importantly the implementation and configuration management of the architecture.
  • An Enterprise Architecture describes the information necessary to operate the business, the technology necessary to support the business operations and, the processes for implementing new technologies for evolving from the current to the target architecture in response to the changing needs of the business.
  • When we say Enterprise Architecture Planning, the Architecture part is a comprehensive blueprint of an organization. The planning part is the definition, development and most importantly the implementation and configuration management of the architecture.
  • When we say Enterprise Architecture Planning, the Architecture part is a comprehensive blueprint of an organization. The planning part is the definition, development and most importantly the implementation and configuration management of the architecture.
  • When we say Enterprise Architecture Planning, the Architecture part is a comprehensive blueprint of an organization. The planning part is the definition, development and most importantly the implementation and configuration management of the architecture.
  • To facilitate enterprise architecture development some logical practices must be employed: A common methodology or approach must be used to promote a repeatable process, reduce training costs, and shorten the life cycle of that process. A common set of templates must be employed to ensure the right information is collected in a common usable format. A centrallized repository must be implemented to make the information accessible. This should facilitate collection as well as use of the EA information. The Architecture configuration must be controlled to maintain its integrity. This requires the implementation of an EA configuration management process. All other processes which cause change to the architecture should feed this CM process. The EA must be easy to access anytime from anywhere. The information must be exportable to facilitate its use.
  • To facilitate enterprise architecture development some logical practices must be employed: A common methodology or approach must be used to promote a repeatable process, reduce training costs, and shorten the life cycle of that process. A common set of templates must be employed to ensure the right information is collected in a common usable format. A centrallized repository must be implemented to make the information accessible. This should facilitate collection as well as use of the EA information. The Architecture configuration must be controlled to maintain its integrity. This requires the implementation of an EA configuration management process. All other processes which cause change to the architecture should feed this CM process. The EA must be easy to access anytime from anywhere. The information must be exportable to facilitate its use.
  • To facilitate enterprise architecture development some logical practices must be employed: A common methodology or approach must be used to promote a repeatable process, reduce training costs, and shorten the life cycle of that process. A common set of templates must be employed to ensure the right information is collected in a common usable format. A centrallized repository must be implemented to make the information accessible. This should facilitate collection as well as use of the EA information. The Architecture configuration must be controlled to maintain its integrity. This requires the implementation of an EA configuration management process. All other processes which cause change to the architecture should feed this CM process. The EA must be easy to access anytime from anywhere. The information must be exportable to facilitate its use.
  • To facilitate enterprise architecture development some logical practices must be employed: A common methodology or approach must be used to promote a repeatable process, reduce training costs, and shorten the life cycle of that process. A common set of templates must be employed to ensure the right information is collected in a common usable format. A centrallized repository must be implemented to make the information accessible. This should facilitate collection as well as use of the EA information. The Architecture configuration must be controlled to maintain its integrity. This requires the implementation of an EA configuration management process. All other processes which cause change to the architecture should feed this CM process. The EA must be easy to access anytime from anywhere. The information must be exportable to facilitate its use.
  • All the work of collecting, maintaining, and employing the information pays off when this information is used for the activities, such as those listed, to make better informed business decisions. The architecture helps the organization better uderstand what is being managed
  • The objective of this meeting is to introduce for discussion, the concept of Enterprise Architecture Planning. During our discussion, the following questions should be considered: What is EAP? What is it used for? Why should we do it?
  • All the work of collecting, maintaining, and employing the information pays off when this information is used for the activities, such as those listed, to make better informed business decisions. The architecture helps the organization better uderstand what is being managed
  • One of the key means for ensuring interoperable and cost-effective systems is to establish comprehensive architectural guidance. The Framework provides the rules, guidance and product descriptions for developing and presenting architectural descriptions. This ensures a common denominator for understanding, comparing, and integrating architectures. Application of the framework will enable architectures to contribute more effectively to engineering interoperable and cost-effective systems. Architecture provide a mechanism for managing complexity.
  • An Enterprise Architecture describes the information necessary to operate the business, the technology necessary to support the business operations and, the processes for implementing new technologies for evolving from the current to the target architecture in response to the changing needs of the business.
  • The objective of this meeting is to introduce for discussion, the concept of Enterprise Architecture Planning. During our discussion, the following questions should be considered: What is EAP? What is it used for? Why should we do it?
  • An Enterprise Architecture describes the information necessary to operate the business, the technology necessary to support the business operations and, the processes for implementing new technologies for evolving from the current to the target architecture in response to the changing needs of the business.
  • An Enterprise Architecture describes the information necessary to operate the business, the technology necessary to support the business operations and, the processes for implementing new technologies for evolving from the current to the target architecture in response to the changing needs of the business.
  • An Enterprise Architecture describes the information necessary to operate the business, the technology necessary to support the business operations and, the processes for implementing new technologies for evolving from the current to the target architecture in response to the changing needs of the business.
  • The benefits of EAP provide a full menu of "ilities" as benefits.
  • All the work of collecting, maintaining, and employing the information pays off when this information is used for the activities, such as those listed, to make better informed business decisions. The architecture helps the organization better uderstand what is being managed
  • Steven Spewak further elaborates the benefits in his EAP publication entitled "Developing a blueprint for data, applications and technology."
  • The objective of this meeting is to introduce for discussion, the concept of Enterprise Architecture Planning. During our discussion, the following questions should be considered: What is EAP? What is it used for? Why should we do it?
  • Finally,this slide communicates Zachman's "pay now, or later" concern.
  • The benefits of EAP provide a full menu of "ilities" as benefits.
  • This matrix represents a set of Coast Guard enterprise entities likely to be found in our enterprise architecture. This table was a product of the Coast Guard Information Architecture planning process.
  • To maintain the integrity of the architecture, a structured, enforced configuration management process needs to be implemented. All changes to any component of the architecture must pass through this CM process to update the architecture.
  • Departmental Report 12/2002

    1. 1. Enterprise Architecture Planning (EAP) Administrative Computing Services 12/17/2002
    2. 2. Topics <ul><li>What is Enterprise Architecture Planning (EAP)? </li></ul><ul><li>What is an EA used for? </li></ul><ul><li>Why should we do it? </li></ul>
    3. 3. What is an Enterprise Architecture? A comprehensive blueprint of an organization by which we analyze and plan changes and make additions. The structure of (Enterprise) components and their relationships, as well as principles and guidelines governing their evolution over time. A common understanding, of the names and definitions of our organization’s entities. MOST IMPORTANTLY: THE MODELS ... We need to build a new application… What do we have already in place? Impact?
    4. 4. <ul><li>The EA is a strategic asset repository which defines the current and target architecture environments, including: </li></ul><ul><li>the business (processes) , </li></ul><ul><li>the information (data or entities) , </li></ul><ul><li>the technology , and </li></ul><ul><li>the transitional processes that keeps all aligned . </li></ul><ul><li>Emphasis on Logical, not Technological… </li></ul><ul><li>Technology will always change </li></ul><ul><li>Beware of Protocol Gas! </li></ul>What is an Enterprise Architecture? Source: Federal Conceptual Architecture model
    5. 5. Example: Technical Blueprint
    6. 6. Example: Organizational Data/Entities
    7. 7. Example: Organizational Data Attributes
    8. 8. EAP Consists of... <ul><li>A standard methodology </li></ul><ul><li>A standard framework </li></ul><ul><li>A standard set of templates </li></ul><ul><li>A repository </li></ul><ul><li>A change management process </li></ul>
    9. 9. Methodology adopted: “Guiding Principles” <ul><li>Conceptual Guiding Principles for all Architecture Domains </li></ul><ul><li>Specific Domain Architecture Guiding Principles </li></ul><ul><ul><ul><li>Commercial-Off-The-Shelf Solutions </li></ul></ul></ul><ul><ul><ul><li>Developed Applications </li></ul></ul></ul><ul><ul><ul><li>Middleware </li></ul></ul></ul><ul><ul><ul><li>Network </li></ul></ul></ul><ul><ul><ul><li>Platforms </li></ul></ul></ul><ul><ul><ul><li>Security </li></ul></ul></ul><ul><ul><ul><li>Databases </li></ul></ul></ul><ul><ul><ul><li>Operations Management </li></ul></ul></ul>
    10. 10. Adopted “Sliding Window” Technology Change Management Methodology <ul><li>Matrix for a 4-year, 16-quarter sliding window within which the various recommendations for the Specific Domain Architectures are documented. </li></ul><ul><li>Document which components should be researched, piloted, invested in, maintained but not upgraded, disinvested, obsoleted, and rejected . </li></ul><ul><li>Planning Architecture Governance and Change Management Procedures </li></ul>
    11. 11. Adopted Baseline Reference Technology <ul><li>J2EE </li></ul><ul><li>XML </li></ul><ul><li>LDAP Directory </li></ul><ul><li>Business Portal (uPortal) as application development and integration framework </li></ul>
    12. 12. Adopted Zachman’s Framework for Information Systems Architecture
    13. 13. Topics <ul><li>What is Enterprise Architecture Planning (EAP)? </li></ul><ul><li>What is an EA used for? </li></ul><ul><li>Why should we do it? </li></ul>
    14. 14. <ul><li>Investment decisions, vendor selection </li></ul><ul><li>Modeling </li></ul><ul><li>Analysis </li></ul><ul><li>Requirements definition </li></ul><ul><li>Planning </li></ul><ul><li>Describing, understanding, and communicating </li></ul>What is an EA used for?
    15. 15. What is an EA used for? <ul><li>Promote interoperable and cost-effective systems </li></ul><ul><li>Provide the rules, guidance and governance for buying or developing systems and managing change </li></ul><ul><li>Ensure a common denominator for understanding, describing, comparing, and integrating systems </li></ul><ul><li>Provide a mechanism for managing complexity . </li></ul>
    16. 16. Architecture Defines the Transitional Roadmap Source: Federal Conceptual Architecture model
    17. 17. Topics <ul><ul><li>What is Enterprise Architecture Planning (EAP)? </li></ul></ul><ul><ul><li>What is an EA used for? </li></ul></ul><ul><li>Why should we do it? </li></ul><ul><ul><ul><ul><li>Too much work! </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Too difficult! </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Too many deadlines! </li></ul></ul></ul></ul>
    18. 18. Non-optimum HRIS Situation DATA Applicant Tracking DATA Staffing Management (Job Description Builder, QuickRec, FastClass) Employee Evaluation DATA Training Mgmt. DATA Payroll DATA Budgeting DATA
    19. 19. Optimum Situation Staffing Management (Job Description Builder, QuickRec, FastClass) Employee Evaluation Training Mgmt . Payroll Applicant Tracking Budgeting DATA Integrated Systems and Data Competency Modeling
    20. 20. Non-optimum Payquest Billing Agency Info AdCom Payquest Billing Agency Info Gastroenterology Pediatrics Billing Agency Info
    21. 21. Optimum Payquest Situation Gastroenterology Training Mgmt . Pediatrics AdCom Payquest Any department Billing Agency Info in LDAP Directory Integrated Data and Access Control Eudora Any LDAP compliant software (DralaWorkflow, uPortal, Expresso) Competency Modeling
    22. 22. Present “Stovepipes” Source: Federal Conceptual Architecture model
    23. 23. Desired State Source: Federal Conceptual Architecture model
    24. 24. Target Source: Federal Conceptual Architecture model
    25. 25. How do we get to the Target? <ul><li>Understand our challenges, goals and “Guiding Principles”. </li></ul><ul><li>Apply and maintain “16-quarter Sliding Window” technology management Matrix for Domain Architectures (Security, COTS, etc). </li></ul><ul><li>Build in Reference Technology (J2EE, XML, LDAP, Portal) </li></ul><ul><li>Populate Zachman Framework Row 1 - the Planner’s perspective. </li></ul><ul><li>Work with our business units to populate Zachman Framework </li></ul><ul><ul><li>Row 2 - the “Stakeholder’s” perspective (business models). </li></ul></ul><ul><li>Understand where we take “shortcuts”, why, and for how long. </li></ul><ul><li>Plan, organize and commit. </li></ul><ul><li>Communicate. </li></ul>
    26. 26. <ul><li>Applications in different technologies </li></ul><ul><li>Redundant code, redundant data with multiple uses </li></ul><ul><li>Redundant security, user/group management </li></ul><ul><li>30 year old systems </li></ul><ul><li>Alignment with business needs not timely </li></ul><ul><li>Data quality issues </li></ul><ul><li>Costly integration </li></ul><ul><li>Customized development of application instead of assembly from “parts” </li></ul><ul><li>Funding (State Budgets depend on explicit EAP ) </li></ul><ul><li>Projects done without architecture planning cost significantly more in long term (John Zachman) </li></ul><ul><li>Without it, we can’t understand impact of change. </li></ul>Why? Too much work! Impossible!
    27. 27. Benefits to the Business of planned systems <ul><li>More responsive to customer’s needs </li></ul><ul><li>Reduced data-entry costs </li></ul><ul><li>Efficient systems maintenance means improved service. </li></ul><ul><li>Architectures eliminate complex costly interfaces between incongruent systems </li></ul><ul><li>Management decisions in all functional areas will be based on more accurate and timely data, leading to various improvements and cost-saving measures </li></ul><ul><li>New systems are developed faster and at less cost due to common data, common code, and a shortened requirements phase </li></ul><ul><li>Easier to evaluate and select vendor SW packages </li></ul><ul><li>Source: Enterprise Architecture Planning </li></ul><ul><li>Steven Spewak </li></ul>
    28. 28. Conclusion <ul><ul><li>What is Enterprise Architecture Planning? </li></ul></ul><ul><ul><li>What is an EA used for? </li></ul></ul><ul><ul><li>Why should we do it? </li></ul></ul><ul><ul><li>MOST IMPORTANTLY: THE MODELS </li></ul></ul><ul><ul><li>... We need to build a new application… </li></ul></ul><ul><ul><li>What do we have already in place? Impact? </li></ul></ul>
    29. 29. <ul><ul><ul><li>&quot;You may think this is too much work… </li></ul></ul></ul><ul><ul><ul><li>Or, it takes too long </li></ul></ul></ul><ul><ul><ul><li>And it costs too much </li></ul></ul></ul><ul><ul><ul><li>Or is too theoretical </li></ul></ul></ul><ul><ul><ul><li>Or too high risk </li></ul></ul></ul><ul><ul><ul><li>Or too whatever. </li></ul></ul></ul><ul><ul><ul><li>However, if that’s your assessment… </li></ul></ul></ul><ul><ul><ul><li>You can’t complain that </li></ul></ul></ul><ul><ul><ul><li>the systems aren’t “aligned” with the enterprise,or </li></ul></ul></ul><ul><ul><ul><li>are inflexible, </li></ul></ul></ul><ul><ul><ul><li>or cost too much, </li></ul></ul></ul><ul><ul><ul><li>or that vital information is not available, </li></ul></ul></ul><ul><ul><ul><li>or that the data you get isn’t any good, or too late, </li></ul></ul></ul><ul><ul><ul><li>or you can’t change anything, </li></ul></ul></ul><ul><ul><ul><li>or that I/S is slow and unresponsive… </li></ul></ul></ul><ul><ul><ul><li>and, I am here to tell you </li></ul></ul></ul><ul><ul><ul><li>Outsourcing isn’t going to fix the problem. </li></ul></ul></ul><ul><ul><ul><li>Packages (in themselves) won’t fix the problem. </li></ul></ul></ul><ul><ul><ul><li>Decentralization won’t fix the problem. </li></ul></ul></ul><ul><ul><ul><li>And, the Internet isn’t going to fix the problem. </li></ul></ul></ul><ul><ul><ul><li>No amount of money, Or </li></ul></ul></ul><ul><ul><ul><li>technology is going to fix the problem! </li></ul></ul></ul><ul><ul><ul><li>It is NOT a technical problem, </li></ul></ul></ul><ul><ul><ul><li>it is an ENTERPRISE problem. </li></ul></ul></ul><ul><ul><ul><li>Only ACTUAL WORK is going to fix the problem, and </li></ul></ul></ul><ul><ul><ul><li>“ Someday, you are going to wish you had all those models, </li></ul></ul></ul><ul><ul><ul><li>Enterprise wide, </li></ul></ul></ul><ul><ul><ul><li>horizontally and vertically integrated, </li></ul></ul></ul><ul><ul><ul><li>at excruciating level of detail.” </li></ul></ul></ul><ul><ul><ul><li>You might as well start working on them TODAY!!! </li></ul></ul></ul><ul><li>John Zachman </li></ul>Zachman reflections on EA Planning
    30. 30. Benefits Facilitates information services that provide: flexibility interoperability reliability survivability affordability sustainability portability reusability adaptability compatibility
    31. 31. Business Benefits of EAP <ul><li>Focus on strategic use of technology for managing data as an asset </li></ul><ul><li>Standard vocabulary facilitates communication and reduces inconsistency and data redundancy </li></ul><ul><li>Documentation increases understanding of the business </li></ul><ul><li>Models can be used to explain the business and assess the impact of business changes </li></ul><ul><li>Decision making policies can be reviewed </li></ul><ul><li>It allows for a comprehensive, objective and impartial approach </li></ul><ul><li>The long range systems plan compliments the business plan </li></ul><ul><li>It involves a feasible migration strategy with short term achievements </li></ul><ul><li>It is easier to assess the benefits and impact of new systems and software </li></ul><ul><li>It allows easier accommodation of dynamic business changes </li></ul><ul><li>Management participation provides a business prospective, credibility, confidence </li></ul><ul><li>Source: Enterprise Architecture Planning </li></ul><ul><li>Steven Spewak </li></ul>
    32. 32. Examples - Entities Source: U.S. Coast Guard Information Architecture A distinguishable - person - about which information is kept. place, thing, event, concept
    33. 33. Work involved... <ul><ul><li>Refine goals, objective, principles </li></ul></ul><ul><ul><li>Establish membership </li></ul></ul><ul><ul><li>Identify a methodology </li></ul></ul><ul><ul><li>Identify a framework </li></ul></ul><ul><ul><li>Identify resources </li></ul></ul><ul><ul><li>Define deliverables </li></ul></ul><ul><ul><li>Refine timeline </li></ul></ul>
    34. 34. Definitions - Miscellaneous Technical Reference Model - A common framework, probably conceptual, to define a common vocabulary so as to better develop and aquire some level of support. It would provide you with a representation of the domain showing commonality and integration and interoperability. Common Operating Environment - The set of capabilities that would allow you to address the suite of integration products that you need to ensure a cohesive framework of systems for development. Like the DII COE address architecture, standards, software reuse, shared data, interoperability, portability, configuration management and integration. Standards Roadmap - It would start with a common set of mandatory standards and guidelines. It would then be tailored to the development that was being implemented. So it would be the &quot;building codes&quot; that would be reviewed and selected to facilitate the development of the system or systems needed to be built. (A Technical Architecture View for a particular area (Defense Transportation System) starting from the DOD Joint Technical Architecture.) Dick Webb, ASD(C3I)

    ×