Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Enterprise Data Maps

577 views

Published on

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

Enterprise Data Maps

  1. 1. Three Year IT Management and Budget Plan Enterprise Data Maps 07.21.2006
  2. 2. Agenda <ul><li>Clarify 3 Year Plan Instructions </li></ul><ul><li>Enterprise Data Maps Discussion </li></ul><ul><li>Open Discussion </li></ul>
  3. 3. Clarify 3 Year Plan Instructions
  4. 4. 3 Year Plan Clarification <ul><li>Technology Assets -> Database </li></ul><ul><ul><li>Production databases only </li></ul></ul><ul><ul><li>Mainframe and server based databases </li></ul></ul><ul><ul><li>Databases that are integrated into third party software probably should not be counted </li></ul></ul><ul><ul><li>Non-relational databases really do not have “tables” but use that area to list the number of non-relational databases that exist </li></ul></ul>
  5. 5. 3 Year Plan Clarification <ul><li>Business Contingency Planning / IT Disaster Recovery </li></ul><ul><ul><li>Hot button issue for ITAB and Executive CITO </li></ul></ul><ul><ul><li>The split was made to see the level of disaster planning that is occurring </li></ul></ul><ul><ul><li>These two plans can exist in one document </li></ul></ul><ul><ul><li>Simple “Yes” or “No” question, but feel free to add any additional information that helps to crystallize your agency’s disaster planning </li></ul></ul>
  6. 6. Any Other Questions?
  7. 7. Enterprise Data Maps
  8. 8. Overview <ul><li>Part of the Enterprise Architecture models added to the Three Year Plan last year </li></ul><ul><li>Still and optional section in this year’s Three Year Plan </li></ul><ul><li>There is no timeline for this to be included, but would be a good idea to start looking at it sooner rather than later </li></ul>
  9. 9. What is an Enterprise Data Map? <ul><li>Graphical, condensed, high level representation of your agencies data </li></ul><ul><li>This could be shown in a number of ways </li></ul><ul><ul><li>Conceptual Data Model </li></ul></ul><ul><ul><ul><li>Non-technical, as seen by a business person </li></ul></ul></ul><ul><ul><li>Logical Data Model </li></ul></ul><ul><ul><ul><li>How business data objects would be implemented in an Information system, how the database designer would see it </li></ul></ul></ul><ul><ul><li>Physical Data Model </li></ul></ul><ul><ul><ul><li>How the logical data would be organized, how the database developer would see it </li></ul></ul></ul>
  10. 10. What are we asking for? <ul><li>Somewhere between the conceptual and logical model </li></ul><ul><ul><li>We want conceptual information organized logically. </li></ul></ul><ul><ul><li>Want a list of subject areas, i.e. Customer, Product, Employee. </li></ul></ul><ul><ul><li>The logical part is that we would like to see some of the high level groupings, interactions, and relationships. </li></ul></ul>
  11. 11. Why an Enterprise Data Map? <ul><li>A model that will allow the state to understand the data that exists </li></ul><ul><li>A model that will help develop common data standards </li></ul><ul><li>A model that will help data interoperability </li></ul><ul><li>A model that will allow for a discussion on data to take place </li></ul>
  12. 12. Why? (continued) <ul><li>High Level understanding of what data you are collecting as an agency </li></ul><ul><li>Find redundant and inefficient data exchanges </li></ul><ul><li>Find possible collaboration points or additional data exchanges </li></ul>
  13. 13. Background: Federal Data Reference Model <ul><li>The FEA Data Reference Model (DRM) is intended to promote the common identification, use, and appropriate sharing of data/information across the federal government through its standardization of data in the following three areas: </li></ul><ul><ul><li>Data Context – A standard approach to representing taxonomies that an agency uses to categorize its data. Such categorization enables the business context of data to be well understood. </li></ul></ul><ul><ul><li>Data Sharing – A standard approach to describing the characteristics and requirements of interagency data exchanges, including data sources. Defines a standard message structure known as an Information Exchange Package. </li></ul></ul><ul><ul><li>Data Description – A standard approach to describing an agency’s structured, semistructured, and unstructured data. Structured data includes individual entities (such as those defined within a data architecture), their attributes, and the relationships between them. Unstructured data includes multimedia files, and documents created using earlier versions of applications such as Microsoft Word. Semi-structured data includes Web pages and e-mails. </li></ul></ul>
  14. 14. Our Approach vs. Federal Approach <ul><li>We are not mandating anything. </li></ul><ul><li>Our approach is to give you complete flexibility in context, sharing, and description </li></ul><ul><li>In time we may look at standardization (and it will probably not be mandatory), but that is years down the road </li></ul><ul><ul><li>Unless there are some interested parties and then we will be happy to start helping you develop strategies for this </li></ul></ul>
  15. 15. Example #1 – Too much information
  16. 17. Example #2 – Correct Level of Information
  17. 19. How to complete an Enterprise Data Map? <ul><li>I am not a DBA / Application developer by trade, so my knowledge on this is limited </li></ul><ul><li>But remember we are looking for high level information </li></ul><ul><ul><li>Customer Information rather than First Name, Last Name, Address, Billing information, ect </li></ul></ul><ul><ul><li>Critical information </li></ul></ul><ul><ul><li>Column level data </li></ul></ul>
  18. 20. How? (continued) <ul><li>I would start by trying to compile all your agencies data by system </li></ul><ul><ul><li>Could also look at stand alone databases </li></ul></ul><ul><li>Then with that data look for any natural groupings that exist for naming consistency </li></ul><ul><li>Aggregating this master set of information will be critical to get this effort in the proper scope </li></ul><ul><li>Then begin to find any linkages between the different data sets </li></ul><ul><li>Finally plot all those pieces </li></ul>
  19. 21. Issues <ul><li>This is a large undertaking </li></ul><ul><ul><li>We know this. We think it is an important undertaking for Kansas. That is why we are talking about it now and not making it required. </li></ul></ul><ul><li>Trying to drill down to deeply in your data. </li></ul><ul><ul><li>Having too much information will be a detriment to fitting this on a single page </li></ul></ul><ul><ul><li>Remember KDOT took 50+ databases, 4000+ tables, and 100000+ rows and fit the summary on a page. </li></ul></ul>
  20. 22. Level of Detail <ul><li>Provide what ever level of detail you can realistically complete in the given time. </li></ul><ul><li>We would rather see a partial data map than no data map </li></ul><ul><ul><li>Submit it to us as a “draft” and we will not publish it </li></ul></ul>
  21. 23. Final Reminder <ul><li>Three year plans are due September 1 st . </li></ul>
  22. 24. Questions?
  23. 25. Open Discussion
  24. 26. Contact Information <ul><li>Bill Roth, CITA, 785-296-2108 </li></ul><ul><ul><li>[email_address] </li></ul></ul><ul><li>Bryan Dreiling, 785-296-2809 </li></ul><ul><ul><li>[email_address] </li></ul></ul><ul><li>http://da.ks.gov/kito/ITMBP-07.htm </li></ul>

×