1 / 31

SNIA Roadmap Project

SNIA Roadmap Project. Wayne Rickard Chair, SNIA Technical Council & Roadmap Task Force October 27, 2004. Agenda. What is a Roadmap? The SNIA Roadmap: Goals & Objectives Schedule & Timeline Roadmap Workshops Business Driver Themes Tech Drivers Synthesis Presenting the Data

cate
Download Presentation

SNIA Roadmap Project

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. SNIA Roadmap Project Wayne Rickard Chair, SNIA Technical Council & Roadmap Task Force October 27, 2004

  2. Agenda • What is a Roadmap? • The SNIA Roadmap: Goals & Objectives • Schedule & Timeline • Roadmap Workshops • Business Driver Themes • Tech Drivers • Synthesis • Presenting the Data • Roadmap Trial Use Document • Next Steps – how you can help

  3. Roadmap Definition #1 “A 'roadmap' is an extended look at the future of a chosen field of inquiry composed from the collective knowledge and imagination of the brightest drivers of change in that field.” Bob Galvin

  4. Roadmap Definition #2 “….a science and technology roadmap provides a consensus view or vision of the future S&T landscape available to decision makers. The roadmapping process provides a way to identify, evaluate, and select strategic alternatives that can be used to achieve a desired science and technology objective.” Bob Schaller

  5. Trends drivers, key issues and uncertainties Evolution of required and desirable functional performance of storage systems of the future Required and desired technological response, including research requirements Policy, infrastructure, partnerships, inward investment, etc. Roadmap Planning What are we attempting to produce? Layers connect: Time (know-when) ‘purpose’ (know-why) ‘delivery’ (know-what) ‘resources’ (know-how) time Business / Market / Drivers / Objectives Products / Services / Capabilities / Systems / Opportunities / Risks Technology / Competencies Skills / partnerships / resources, etc.

  6. Objectives Architecture Validation (future) Development Revision (future) Analysis Roadmap Planning

  7. The SNIA Roadmap Goals and Objectives

  8. Workshop - Objectives Prioritization

  9. Roadmap Goals • Establish a Vision for the Storage industry • A focus for integrated strategic planning • Instill confidence in SNIA as preeminent industry group • Identify and guide opportunities for shared development • Clarify barriers and coordinate response within the community • Can be applied in a wide range of business contexts • Improved communication across the industry (vertical & horizontal)

  10. SNIA Roadmap Core Team • The core team consists of the following individuals: • Wayne Rickard, Seagate Technology • Mike Provance, Strateva • Ed Coyle, Purdue • Robert Peglar, XIOtech Corporation • Mark Bradley, Computer Associates • Michael Peterson, Peterson Associates • Mark Carlson, Sun Microsystems • Giora Tarnopolsky, Tarnotek/INSIC • David Dale, Network Appliance • Dave Thiel, Hewlett-Packard • Arnold Jones, Storage Networking Industry Ass. • Larry Krantz, EMC • Vincent Franceschini, Hitachi Data Systems • Rob Davis, qLogic • Ron Durbin – UCSD • Tony DiCenzo – SNIA Board

  11. Information Storage Industry Consortium Collaborators

  12. SNIA Roadmap – Progress to Date

  13. SNIA Roadmap – Delivery Schedule

  14. Business Drivers Business Drivers with Technical & Industry Relevance

  15. Example of Demand-Side Architecture

  16. Application Objectives & Business Process Categories Objectives (e.g. “Data Security Objectives”) align with business needs and are placed in time. • An objective represent maturity points where the transition from “development” to “adoption” occurs. • An objective is a measurable industry milestone, such as a first demonstration. • More practically, an objective indicates mature products and solutions are available in the market. • Objectives link directly to the technical elements they are dependent on. In other words, any technical milestone or innovation that is a dependency for achievement of this objective is shown. Need Alignment: Business Driver Objective <Tech Dependency 1> <Tech Dependency 2> <Tech Dependency 3>

  17. Explored 8 Business Drivers Themes • Competitiveness & opportunity • Business & IT agility • Instantaneous, online business • Globalization of supply chain • Regulatory compliance and risk management • Data security • Mobile convergence • Digital Society

  18. Business Driver Needs Progression Across all verticals, what environmental or market trends may be leveraged for competitive advantage through appropriate application of storage technology? In other words, when does adoption of appropriate storage technology become a differentiator in delivered value? During Introduction, both technical and business risk higher. During Adoption, firms enjoy measurable benefit from their investments During Maturity, benefits are widely available and most firms have adopted, diluting unique value contribution

  19. Sample Theme: “Data Security” Storage has matured in an environment where security has been a secondary concern. Now, new models for deploying storage expose systems to threats and attacks that put data at risk. Our industry must agree on requirements for storage network security, then create architectures, interfaces, and practices which make optimal use of existing security technologies in a storage network. Where nothing exists that meets the requirements for use in a storage network, we must create, or stimulate creation of, new information security technologies. Storage and Storage Networking security will be important for installations from the departmental level to the multi-enterprise. The security of the stored information in heterogeneous environments must also be addressed, as well as any security issues inherent in underlying transports or technologies. the cost and performance tradeoffs of deploying storage security must be weighed against the business risk of unprotected data. Finally, the industry must address best practices and preferred methods in anticipation of government-dictated security policies.

  20. Sample Theme: “Digital Society” The concept of the digital society has been growing over the last few years. With the advent of robust high speed communications, inexpensive storage, and inexpensive compute servers, applications for personal information processing and storage have begun to appear in the marketplace. The concept of the digital society promises to be one of the areas of explosive growth in coming years. Access to personal information, documents, medical history, as well as digital content has the potential to become the fastest growing market segments for pervasive information storage, application processing requirements, high speed and wireless communications. These market drivers will also drive requirements in access security, data assurance (DR, archival, and longevity). New applications and information devices will be introduced into the home as well as convergence of personal information devices such as CellPhones, PDA’s, cameras…

  21. Tech Drivers Technology Research and Development Trends in Storage

  22. Review – are all listed Business Drivers, requirements, and technical elements clearly defined? Assign Relevance 5 = critical technology dependency – can’t satisfy requirement without it 4 = very important technology dependency – inhibits mass adoption without it 3 = important technology dependency – enhances competitiveness 2 = minor technology impact – trivial impact, substitutes available 1 = no impact – unrelated technology 0 = use only if you don’t understand the technology or the requirement Share with other Subject Matter Experts Tech Element Relevancy Matrix

  23. Synthesis & Presentation Organizing and Presenting the Roadmap Data

  24. High Level Roadmap Strawman Contents: • Executive summary • Introduction, purpose, overview • Conceptual themes: demand, change, innovation • Business themes: single-page one theme perspectives, based on business drivers • Tech Drivers: The Tech roadmaps, with a hierarchy of basic research and tech elements • Trends: the data we believe and what we think it tells us. • Verticals: The skew and relative priorities of the various business drivers across several vertical segments. A vertical-specific refinement on the timing expressed in the theme section. • Basic Research: guidance, if SNIA, organizational leads & milestones, resource identification (i.e. TWGs) • Summary

  25. Identify SNIA alliances & liaisons Add data from additional customers/verticals to current data set Roadmap will align with high-level SNIA goals Workshop - Initial Influence Layers

  26. Ex: SNIA Data Security Needs Near-term (0-7) Mid-Term (7-15) Long-Term (15+) 2004 “Good Enough” Pervasive Need Transition: What drives this new need? What are the consequences of not transitioning? Metadata Security

  27. Sample Report Visualization A page from the Roadmap Document Theme described Critical Timeline Progression of NeedsBusiness Requirements Supportive Research Key technical deliverables Technology maturity index?Risk?Expected Payoff?

  28. Decision Support Tools

  29. Concept Development Proof of Principle Proof of Performance Pilot Scale Experience Example INEEL Component Roadmap – Hydrogen Generator Development

  30. 2004 December January February March April Complete Data SNIA Member Review Synthesis Spring SNW Add Vertical Perspectives Additional Tech Drivers Workshops Draft Trial Use Roadmap Core Team Review SNIA Review Draft Release Final

More Related