1 / 38

Best Practices for Enterprise Data Management

July 12, 2011. Best Practices for Enterprise Data Management. Greg Pleiss Don Hong. Topics. Procurement Approaches Necessary Features and COTS Architecture Deployment Considerations Summary Questions. Procurement Approaches. Enterprise System Procurement Approaches.

khoi
Download Presentation

Best Practices for Enterprise Data Management

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. July 12, 2011 Best Practices for Enterprise Data Management Greg Pleiss Don Hong

  2. Topics • Procurement Approaches • Necessary Features and COTS Architecture • Deployment Considerations • Summary • Questions

  3. Procurement Approaches

  4. Enterprise System Procurement Approaches A spectrum of system implementation patterns Custom System Built entirely with custom code Component System Uses stand alone COTS components with significant development COTS System Configured with minimal development

  5. Comparing Approaches COTS System follows standard system development lifecycles, but activities are different than traditional developmental systems

  6. What is the COTS Approach? “Going with the grain” Maximizes investment in commercial off the shelf software in a GIS system Meets business goals by leveraging COTS • Configures and extends COTS • Avoids developing software Provides immediate capability… continually improving via COTS release cycles Engages users early and often to iteratively improve system

  7. A Different Way of Thinking • Challenges common procurement models • Requirements focused on business goals vice detailed feature functions • Select COTS that best meets business goals and implement “with the grain” for best results • Schedule linked to COTS release cycles • Asks users to consider new business processes • New workflows based on COTS strengths (usually better) • People resist change • Organizations resist change • Avoid temptation to overly customize • Best intentions of many people often push systems towards customization

  8. ArcGIS System Concept The backbone of a COTS based, enterprise data management system… Cloud Services ArcGIS Using & ManagingMap & GeographicInformation Web Browser Enterprise Services • Mapping • Analysis • Collaboration • Editing • Compilation Rich Client Local Mobile …with flexibility to support wide range of user roles Desktop

  9. Enterprise GIS System Pattern @ ArcGIS 10 Power to configure how content is produced, shared, and used Services (Maps, Analysis) Map & Data Products Authoritative Content Producers Field Edits & Partner Input Basemaps (ArcGIS Online) • Configurable & shared • workflows • production tools • business rules

  10. Necessary features and COTS architecture

  11. Enterprise Data Management Key features Production Management Content Dissemination Geodata Management and Maintenance Web Services Web Services Production Geodatabase Publication Geodatabase

  12. Production Management Configuring COTS to support work tasking, reporting, and management • Provide transparency • Task and manage production • Provide status and reporting • Utilize role-based functionality • Targeted user experience • Keep it simple • Extend the reach of GIS workflows • Simple, web-based access • Enable non-GIS users

  13. Production Management Providing transparency and extending the reach of GIS workflows Web Applications Managers & Executives ArcGIS Server Web APIs Flex API Silverlight API JavaScript API ArcGIS Server Workflow Manager ArcGIS Server Reporting Services Tasking Services Management Services Execution Services Basemaps Operational Layers Production

  14. Geodatabase Design Best Practices Delivering high performance, application-ready geodata • Emphasize end-user capabilities • Define detailed information products • Build to deliver, avoid the “what ifs” • Embrace federated compilation and maintenance • Be realistic, prioritize compilation capabilities • Leverage data content provided by the enterprise • Integrate content at the service level, not RDBMS • Design for COTS usability • Leverage geodatabase concepts (FCs, subtypes, etc) • Balance tradeoffs for maintenance and dissemination

  15. Enterprise Geodata Management Providing options for distributing geodata management activities Production Geodatabase Publication Geodatabase Geodatabase Versions • Direct editing • Basis for replication Connected Replicas • Workgroups • Two-way exchange One-Way Replica Disconnected Replicas • Ideal for outsourcing work • XML-based transfer • Two-way exchange • Read-Write Access • Tuned for Editing • Authoritative Content • Read-Only Access • Tuned for Services • Approved Content Check Out Replicas • File-based GDB • Inhouse or Outsourced • One-time exchange

  16. Data Maintenance Configuring COTS to support workflow-driven, rule-based production • Model new and existing processes • Integrate GIS and non-GIS • Standardize and streamline • Continually evolve workflows • Configure a common rule-base • Feature templates • Map templates • Quality Control rules

  17. Data Maintenance Providing standardized workflows and rules-based data maintenance GIS Professionals Field Users Non-GIS Users ArcGIS Workflow Manager Application Integration Workflows Task Assistant Manager ArcGIS Web APIs ArcGIS Mobile Tasking Services Management Services Execution Services Windows iOS Java Script Flex Android Silver light ESRI Production Mapping ArcGIS Server Workflow Manager Mapping Services QA\QC Rules Feature Templates Metadata Rules Map Templates Production ArcGIS Server ArcGIS Desktop

  18. Content Dissemination Using COTS to support a variety of end-users and applications • Deliver diverse information products • Visualization • Analysis • Geodata • Enable search & discovery • Standards-based (i.e. OGC) • ArcGIS Online ‘tags’ • Support internal and external users • Web services (connected) • Traditional media (disconnected)

  19. Content Dissemination Providing well-defined information products to the enterprise and beyond Connected Disconnected Many Applications Many Users ArcGIS Server Web APIs Flex API Silverlight API JavaScript API ArcGIS Server & GeoPortal Extension Search & Discovery OGC Services Geoprocessing Services Map Services Geodata Services Distributed Publication Node Publication

  20. A Complete System for Enterprise GIS Managing, maintaining, and delivering geodata to the enterprise Content Dissemination (Connected/Disconnected) Production Management Tasking Many Users Management Web Apps Visualize Execution Non-GIS Users Reporting Analyze Geodata Management and Maintenance Access Data Generate Products Multiple Options GISUsers Search & Discover Many Apps Field Users

  21. Deployment Considerations

  22. COTS Impacts to System Development Process Traditional Approach REQ Test Implement Planning Design DEV Users Exercise System COTS Approach Test Implement Planning REQ Design DEV Accelerated Delivery Configuration Users Exercise System Demos for Users

  23. Planning Identify clear project goals • Focus on business objectives and goals • What are you trying to accomplish? • Improving productivity • Increasing revenue • Reducing cost • Supporting regulatory requirements • All system requirements and technical decisions should consider business goals Remember you are trying to solve a business problem not engineer a new software module

  24. Planning Prepare for change • Plan project using multiple phases/iterations • Plan for heavy user interaction and validation of capabilities • Allows for integrating new COTS releases • Provides an opportunity for intermittent training Phases or iterations should focus on completing a use case or scenario

  25. COTS Based Phased Planning Phase 1: Out of Box Phase 2: Refine • Implement base COTS release • Data Model – first release • Workflows - initial configuration • Usage Patterns – Identify • User Roles – Define • Architecture - establish initial infrastructure Phase 3: Finalize • Implement incremental COTS Release • Data Model – modify based on input • Workflows – elaborate and create new • Usage Patterns - refine • Architecture - Integrate with other systems • Implement Final COTS Deployment Release • Data Model - finalize • Workflows - finalize workflows • Architecture – plan for system implementation • Training – develop plan Continuous Learning & Improvement

  26. Requirements Do not start with a blank slate – understand & leverage existing COTS functionality • Focus on the “what” NOT the “how” • Embrace the change – do not modify COTS technology to support an inefficient process • Keep it simple COTS Demos Users COTS Traditional

  27. Design Orchestration of COTS functionality • Short focused interactive design sessions • Heavy use of prototyping and lab environment • End users along with COTS experts • Defining user roles • Defining workflows • Identifying efficiencies • Understanding end user access • Consider future COTS releases Design should emphasize delivering immediate capabilities

  28. COTS Design/Configuration Process

  29. Develop Configuration of workflows and business rules • Based on user input and feedback • Targeted to configuration not customization • 90% configuration 10% (or less) development Workflows Data Model Roles & Usage COTS Products Configuration Team Users

  30. Test Functionality proven via use case validation • Frequent user validation • Multiple user groups to verify usage patterns • Prioritize user feedback – leverage phases • Use validation as training opportunity Use/Exercises Training Feedback Refine Configuration Team Users Real time feedback to Configuration Team

  31. Implementation Consider COTS release schedule in implementation plan • Understand you are changing process not just technology • Leverage COTS training • Data flow patterns • IT Specifications • Security considerations • Administration • Who? What? Skills? • Don’t forget about the data!

  32. COTS Based Phased Implementation Pilot Deployment Phase 2 Deployment Phase 1

  33. Summary

  34. Benefits of a COTS Approach • Minimized cost to implement • Shorter schedule – immediate exercising by users • Reduced risk (technology proven by user-base) • Lowered maintenance costs • Evolves with future COTS functionality • Wider range of qualified people to use and maintain system

  35. Summary • COTS configuration is a more efficient way to approach system development • The COTS Approach redefines system development process, with focus on mission instead of building software • ArcGIS 10 provides a platform for configuration and rapid development – making the COTS Approach viable for many systems

  36. Thank you! More Info: • COTS Approach ArcNews article • http://www.esri.com/news/arcnews/winter1011articles/the-cots-approach.html • COTS Approach white paper • http://www.esri.com/library/whitepapers/pdfs/cots-based-approach-enterprise.pdf Contact us: • Greg Pleiss, gpleiss@esri.com • Don Hong, xhong@esri.com • Please fill out the online evaluation • http://www.esri.com/sessionevals

  37. Questions?

More Related