1 / 25

FEA DRM- What are some Strategic Alternatives- Suggestions

This agenda discusses strategic alternatives and suggestions for data and information management in the Federal Enterprise Architecture Data Reference Model (FEA-DRM). It covers topics such as barriers and inhibitors, assessing organizational needs, data management scorecards, templates for data modeling, industry alternatives, technology landscape, and deliverables. The proposed IAC role involves providing an EA perspective, working with SIGs, and linking to emerging technologies and research.

jsiler
Download Presentation

FEA DRM- What are some Strategic Alternatives- Suggestions

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. FEA DRM- What are some Strategic Alternatives- Suggestions State of FEA DRM & actions and IAC Role Sept 21, 2005

  2. Agenda • Strategic Data and Information Planning for “Mere Mortals” • Are there some simple steps? What are the barriers and inhibitors? • Assessing where the organization is and where they have to go? • Data Management and Interoperability Scorecard • Simple Templates and Spreadsheets for Level 1 to 2 • Registries and Repositories and Data Training etc- Shared but level 3- XML Schemas and universal core • Level 4 and 5: Model Management, Semantics • Purpose-Driven EA Data Modeling and Enterprise Data management • Department- Operating Unit and Lines of Business Models • Some alternatives being used in Industry • Technology and Standards Landscape • Simple Templates and Data Containers and Subject Area Data Collections • What would the deliverables be? • What is the process to get to the deliverables? Involvement • Next Steps

  3. Proposed IAC Role • Provide EA perspective and work with other SIG’s such as • Create IAC team: Integrators, Experts, Vendors- bring in University Thought Leaders also. Put out a call and conduct workshops. Review 1.5 version with small group and expand as desired • Link to emerging technologies, research and standards- extensions to SQL, XQBE, MOF, ISO…….data services • Ed Robertson and Cathy Wyss- Indiana Univ, Ed Sibley- GMU, Richard Wang- MIT • Mix of Vendors and Integrators and links to Universities……Mike Stonebraker- Streambase, etc….. • Thought leadership- provide some ideas for consideration: Business- Driven Data and Information Management and Convergence of Standard based on goals and outcomes • Security and Privacy Profile – need for standard labeling and Security and Privacy Data and Information Service Recommendations • Create basic material that can used in “open-source” type fashion- may need to go through extensive OMB review cycle or could be used “experimentally” through CAF and Industry group outreach • Review what has been prepared- make suggestions • Support and Outreach campaign- Create Starter kits for the level of the implementation, encourage contractors to do DRM implementation, .

  4. Business Community: • Goals-Outcome Trees • Priorities • Budgets • Business Models Data Base Community Library Community Standards Convergence Programming & Package Systems Community XML/ Web Community Business Data Registry- Repository Reuse & Shared Query Points & Converged Models

  5. Range of Data and Information Needs • Where are you today? Sophisticated Data and Information Leader Data Newbie What are the evolutionary steps? Level 4/5 … Level 1

  6. Categorizing the State of Data and Information Architecture and Different Service and Solution Needs • Different Needs and Interests • Different Levels of readiness • Different Urgencies • But all will have to play and move forward • What can a Step by Step Action Plan be! Data & Information Leaders Close Followers Masses: Limited Data and Information Architecture Perspective

  7. Who is within each Category? • DHS, DOD, Intelligence, Justice all have • Urgent Needs • Other communities like Science • Statistics, etc have formed on own • Many are waiting • This too shall pass us by! Data & Information Leaders Close Followers Masses: Limited Data and Information Architecture Perspective • Many are watching and waiting • FAA, Education, etc

  8. Who they are Leaders: DHS, Justice, Intelligence (Folks with strong business case- management gets it!) Close Followers: Pick organizations that want to get moving ( Management almost gets it but needs an early success) Masses (management doesn’t get it and focus education) What they Need! Focus! Information Sharing and Exchange: Create Channels and Data Services Transportation and Critical Infrastructure Security: Fit with need of COOP Architecture Get leaders to work with each of the 3-6 Close Follower projects Provide general training and toolkits and provide readiness tools and support in the business case analysis Identify Two or Three at each Category to work with: Focus

  9. Road Map for EA Evolution: Data and Information

  10. Measures for • Consistency • Completeness • Message of Information Sharing and Exchanges- is there are trickle or stream… • Core Data Type Alignment • Coherency • Different Types of Data and Information Usages may have different measures • “Make Success Measurable”- Steve Batista

  11. Issues- Concerns • Thinking through the approach of how agencies construct their taxonomic • layer of the DRM, there was quite a bit of discussion around the E-gov • act : • section 207D- and their recommendations- • The library community supports a ISO Interoperable search standard- • SEE the GILS may get the boot- • Looks like we are moving away from open standards for search- hence that • will impact , perhaps, how agencies model their taxonomy.

  12. Data Sharing Inefficiencies These Problems… Result in… • Lack of a common way to describe or define data • Common reference – dictionary • Unifying mappings of inconsistent information from disparate systems • Lack of metadata for finding relevant information • Lack of context for information • Incorrect or missing classifications • Lack of central place for obtaining metadata descriptions • Registry • Duplication of data rather than sharing/reuse of data • Stove-piped data boundaries

  13. Convergence of Models around Business Drivers and Priorities Standard Convergence: Business Drivers and Priorities Business Process Modeling Data Services Business- Data Exchange Agreements Data & Information Modeling Query & Data Sharing Maps Information Product Mapping

  14. Context Service Context Security Context Subject Context Subject Area Security Class Service Class Subject Class Input/Output Association Association Association Who When What Why Where Sharing Information Exchange Information Access Exchange Class Unique Identifiers Exchange Payload Query Class Association Association Description Data Element Description Resource Description Structured Data Class Semi-Structured Resource Class Data Property Unstructured Association Association Revised DRM Structure Source: Designing the FEA DRM for Information Sharing, October 9, 2004, Michael C. Daconta, Metadata Program Manager, US Department of Homeland Security.

  15. Context Service Context Security Context Subject Context Subject Area Security Class Service Class Subject Class Input/Output Association Association Association Who When What Why Where Sharing Information Exchange Information Access Exchange Class Unique Identifiers Exchange Payload Query Class Association Association Description Data Element Description Resource Description Structured Data Class Semi-Structured Resource Class Data Property Unstructured Association Association Data Modeling Structure & Services • Business Context • Data Services • Basic • Advanced • Semantic • Dynamic Business • Discovery • Data Interoperability • Services: • Basic • Advanced • Semantic Integration • Dynamic Event • Streaming and Filtering • Data and Information • Content Services • Basic • Advanced • Semantic Consistency • Validation Service • Dynamic Change Triggers • and Events Services Source: Designing the FEA DRM for Information Sharing, October 9, 2004, Michael C. Daconta, Metadata Program Manager, US Department of Homeland Security.

  16. Technology, Standards and Gaps in “next Practices” Process- Aware Information Systems- BPEL, WFMS, etc Big Gap and “next Practices” and Templates missing! Standard Convergence: Business Drivers and Priorities Data Services with WSDL, Semantics, Metadata Repositories Business Process Modeling Many Varieties of approaches by different communities! Data Services Business- Data Exchange Agreements Data & Information Modeling Query & Data Sharing Maps Information Product Mapping Research- Univ of Washington, Indiana, Stanford, IBM, Microsoft, startups Information and Data Quality: Information Product Maps MIT- TDQM- Wang, et. Al.

  17. What are issues? • Data and information modeling and management naturally falls into Storming • Business Goals and Outcomes and recognizing that get something practical with phased approach- maturity by taking incremental steps • Enterprise Architecture and Business Driven perspective needed within the DRM effort- introduced these thoughts • Are there simple approaches? Business-Data Agreement in a template format- add other templates • Create Templates for Starterkits. • Bring in the Researchers and innovators • Can they incrementally grow to more advanced options? • Can this fit with Lines of Business: • Federal Health Architecture • Financial • Etc. • What is going on in DOD and other places in the government? • Can we help get something released?

  18. Relating Business Line Needs to Key-Essential Generic Data Objects and Services • Each business area has a few key “large common data objects” that can be delivered with Service Models • Business Level Generic Objects: • FHA has Electronic Health Record • Air Traffic Management- Generic Flight Record • Each line of Business area…HR, FM • Business Innovations Introduce new concepts and new information and data types • Goals and Outcomes searching and alignment workshops and Collaboration Zone • Shared “Archetypes” and patterns

  19. Starter Kit from Level 1 to 2: Simple Steps • Powerpoint and Visio • Data and Information Templates • Simple Meta Data Spreadsheet • Give some time for learning and getting more data and information architects and Enterprise Architecture on the same page • Taking part of the DRM at Time • Preparing for Enterprise Data Management for Level 3 and Beyond

  20. Context Service Context Security Context Subject Context Subject Area Security Class Service Class Subject Class Input/Output Association Association Association Who When What Why Where Sharing Information Exchange Information Access Exchange Class Unique Identifiers Exchange Payload Query Class Association Association Description Data Element Description Resource Description Structured Data Class Semi-Structured Resource Class Data Property Unstructured Association Association Data Modeling Structure & Services Phased Approach • Business Context • Data Services • Basic • Advanced • Semantic • Dynamic Business • Discovery • Data Interoperability • Services: • Basic • Advanced • Semantic Integration • Dynamic Event • Streaming and Filtering • Data and Information • Content Services • Basic • Advanced • Semantic Consistency • Validation Service • Dynamic Change Triggers • and Events Services Source: Designing the FEA DRM for Information Sharing, October 9, 2004, Michael C. Daconta, Metadata Program Manager, US Department of Homeland Security.

  21. Series of Services: From Simple to aggregated Results: Designed for Change Must be policy Based and also address Privacy Context Service Context Security Context Subject Context Subject Area Security Class Service Class Subject Class Input/Output Association Association Association Who When What Why Where Sharing Information Exchange Information Access Exchange Class Unique Identifiers Exchange Payload Query Class Association Association Description Data Element Description Resource Description Structured Data Class Semi-Structured Resource Class Data Property Unstructured Association Association Must Connect to Business Architecture Data Modeling Structure & Services • Business Context • Data Services • Basic • Advanced • Semantic • Dynamic Business • Discovery Data Connected to Business Innovations Dynamics, Materialized View from Data Marts, and Virtualized must be supported…standards, transformation Must Connect Business Level Agreements: learn from ebXML Data Marts & Web Data Mgmt?? • Data Interoperability • Services: • Basic • Advanced • Semantic Integration • Dynamic Event • Streaming and Filtering Designed for Change and Change Notification • Data and Information • Content Services • Basic • Advanced • Semantic Consistency • Validation Service • Dynamic Change Triggers • and Events Services Strong Semantics and Content Management Elements Record management and Archives?? Source: Designing the FEA DRM for Information Sharing, October 9, 2004, Michael C. Daconta, Metadata Program Manager, US Department of Homeland Security.

  22. Information Quality Mandates Technology “Roadmap” “Asset” Assessments Enterprise Data Management Process E-gov 2002 & Directives FEAPMO DRM Concepts Business Drivers- Simple Templates EDM Step 3 and 4 “Blueprint”

  23. Data Management with Meta Data Benefits

  24. Public Health Immunization Justice Warrant Environment Wildlife Geo-spatial Recreation Camping … Data Mapping Examples – Another View Business Contexts IEP’s Data Elements Vaccination Data Object Vaccination Delivery Name Arrival Date Dose Strength Side Effect Data Properties/ Representation Contains Defines Grant Application Carrier Name Age Gender Camping Permit Request Facility Budget Submission Name Type Address

  25. What are some early successes? • Ideas….have to be moved into successes • Select Targets at each of the levels 1-2-newbies, 3- close followers, 4-5- define some advanced cross-government projects • Continue leveraging the WIKI and Workshops but add industry and going back through contracts • Create a Industry-Government Network and broad recognition and training program • Work with Universities both on Research and integrating into Programs: GMU, GWU, Univ of Maryland, VT, UMBC, and many national progams- MIT, Cal,etc

More Related