Technology Roadmapping Lesson 3
Leadership in Science & Technology Management Mission Vision Strategy Goals/ Implementation Strategy Roadmap Creation Portfolios Portfolio Roadmap Creation Project Prioritization and Selection Project Roadmap Creation Planning For Technology Transition Project Proposals Project Execution Technology Transition 2
Lesson 3 Learning Objectives Define and explain the purposes of technology roadmapping Learn the types and steps of technology roadmapping Analyze the best practices of technology roadmapping Illustrate the benefits of roadmapping to researchers and customers Discuss key DoD initiative: Reliance 21 and Communities of Interest (COI s) 3
Roadmap Origins While organizations have been planning for technology development for many years the widespread use of structured processes began in the 1970s Motorola has been recognized as the first major corporation to use roadmaps to support improved alignment between technology and product development 4
Technology Roadmap Benefits Identifies technologies that are critical for future customer & product needs Assists leadership in deciding needed technologies, funding levels (prioritization and urgency) Allows leadership to better position their development activities with limited resources Used by industry to remain competitive and responsive Used by Department of Defense to plan activities for technology insertion into programs 5
EXERCISE Build Roadmap Strategic Diagram Each Team start with a box in the middle of your whiteboard (easel). In the center of the box - teams define what is a technology roadmap Roadmap Definition 6
Roadmap Definitions Flexible technology plan widely used to support strategic and long range planning Technology planning process that helps identify, select and develop technology alternatives to satisfy a set of product needs A document which outlines the plan to reach short term and long term goals through the use of technology solutions A compilation of documents providing a complete description of the product line of a division or operating group So a technology roadmap can take many forms and be used for many purposes 7
EXERCISE Roadmap Strategic Diagram Build Motivators (Why?) On top - teams identify Roadmapping motivators Roadmap Definition 8
Linking Strategy with Roadmapping Capability Information Portfolio Gap Analysis Technology Options Evaluated Roadmap Creation Defined Targets Project Proposals Technology Assessment Identification of Technology Available/Feasible/Possible Adapted from: Technology roadmapping A planning framework for evolution and revolution Robert Phaal, Clare J.P. Farrukh, David R. Probert, 26 May 2003 9
EXERCISE Roadmap Strategic Diagram Build Motivators (Why?) On the bottom - teams identify Roadmapping Factors and constraints Roadmap Definition Factors/ Constraints 10
Inputs for Roadmapping Directive DoD Strategic Technology Plan Service Strategic Technology Plan Lab Strategic Technology Plan Derived Validated warfighter capability gaps (requirements) Threat assessments (may not be reflected in capability gaps) Commanders inputs (CoCOMs, DoD, etc.) Warfighter demand Economics Desire for innovation Prioritizing resources External Technologies Drivers for Roadmapping Ability to communicate Internal Increasing complexity Changing environment Skill available and skills required S&T researcher initiatives Is this comprehensive? Can you influence these? How? 11
Technical Specialist Input Leadership Input Leadership & Specialist Input Integrated into a common Roadmap Framework Roadmapping Captures Both Strategic and Tactical Aspects Portfolio Gap 1 Portfolio Gap 2 Portfolio Gap Roadmap P1 P2 P3 P4 P5 Product Roadmap T1 T2 T3 Technology Roadmap AR1 AR2 AR3 Applied Research Programs BR1 BR2 BR3 BR4 BR5 Basic Research Programs Adapted from: Petrick, Irene J. (PENNSTATE case study,) Developing and Implementing Roadmaps A Reference Guide Time 12
EXERCISE Roadmap Strategic Diagram Build teams identify Roadmapping Inputs and Outputs Motivators (Why?) Inputs Roadmap Definition Outputs Factors/ Constraints 13
Roadmapping Process There have been many Roadmapping processes proposed a simple google search will show many available tools They all tend to include the following basic steps Planning - What is the purpose and scope Development The technical requirements The resources available Schedule constraints Alternatives Proposed roadmap Implementation and follow up The following slides provide more detail on one of the many process models 14
Roadmapping Process Steps Planning Process results in a first-cut roadmap together with identification of key knowledge gaps, and implementation factors Continuously update Implementation Adapted from: Technology roadmapping A planning framework for evolution and revolution Robert Phaal, Clare J.P. Farrukh, David R. Probert, 26 May 2003 15
Roadmap Planning Define inputs, outputs, units of analysis Select from inputs technologies to roadmap Identify participants and senior leaders Identify existing acquisition programs/ customers Identify new programs of record required to field technologies WHY ARE WE DOING THIS? 16
Define Roadmap Scope Asses technology performance expectations Identify, group and prioritize internal/external drivers Define Technology Gaps (TG) Identify known risks Conduct SWOT analysis Consider strategic context WHAT IS THE SCOPE? e.g. DOD WIDE OR ONE TECHNOLOGY DOMAIN IN A LAB 17
Define Technology Strategy Identify and assess the impact of technology on internal/external drivers Develop approaches to address TGs Assess resources: money, people, time Document technology strategy Technology Gaps (TG) 18
Identify Technology Solutions Select and assess the impact of technology on gaps Prioritize/rank product features and technology solutions Define if redundancy is needed to reduce risks 19
Generate Roadmap Develop time line Generate roadmap Support with Technology Transition/Transfer Agreements Define exit criteria 20
Roadmap Levels Narrow Technology Participation Technology Thrust Area Lab/R&D Center Service Broad DoD Communities of Interest What level are you working at? 21
Types The previous slide shows that roadmaps can be used at different levels of an organization Roadmaps can have different purposes such as: Strategic planning Product planning Program planning Process planning They can also have different formats: Multiple or single layers Tables Bars Graphs Flow charts Text Some examples follow 22
Examples of Technology Roadmap Planning Formats Tables Global Horizons Final Report, 2013 Flow Charts ONR, GAO Brief, 2014 Bars Space Situational Awareness, AFRL 2014 23
Air Force Space Technology Roadmap Source: Global Horizons 2013 24
ONR FY16 Technology Insertion Programs (TIPS) Selection Process Roadmap Source: ONR brief to GAO- June 5, 2014 25
Space Situational Awareness Capability Development Roadmap 26
NASA Technology Roadmaps One example of very thorough technology roadmaps is with NASA Its latest version can be seen at https://www.nasa.gov/offices/oct/h ome/roadmaps/index.html It shows roadmaps in 14 technology areas each of which is very detailed and goes out to 2035 The launch propulsion systems roadmap, for example, is a 103 page document and is found in your references 27
Naval Aviation Enterprise Roadmap Process Phase I: Identify Needs and Set Objectives Science and Technology Objectives (STOs) identify gaps and thrust areas at a high level 10 capability gaps such as surface warfare, force protection, information dominance Supported by 33 S&T objectives such as SUW maritime surveillance FP platform survivability ID communication and networks 28
Naval Aviation Enterprise Roadmap Process -2 Phase II Identify Investments and Opportunities Identify current investments Leverage and collaborate where possible All S&T investments housed in a database that tracks them to gaps, STOs, core capabilities, mission areas, portfolios, and transition targets The investment strategy is reflected in roadmaps that match short and long term goals with specific technology solutions Each STO has a roadmap Roadmaps provide the strategy to mature and transition technologies 29
Naval Aviation Enterprise Roadmap Process - 3 Roadmaps and associated back-up books provide: Mission scenario Measures of effectiveness and performance Where S&T funds are being invested Time phased technology development path for gap closure Relationship of each project to the associated gap Example for Wide Area Search and Detection STO Three MOEs Cumulative probability to detect Probability of correct classification Initial area of uncertainty Ten technology areas address this STO: e.g.: Passive acoustics Active acoustics Data fusion 30
Naval Aviation Enterprise Roadmap Process - 4 Phase 3 Evaluation and Assessment Indicates how current investment is going and where additional investment may be warranted Quantifies benefit to warfighter through operational analysis Phase 4 Modify and Update If goal met, declare success If not, what more needs to be done Develop new investment ideas and update/modify strategy Repeat process 31
Research Planning to Support Roadmapping Research program planning works inside your walls: Plan/manage your resources (people, equipment, budget, etc.) Technology roadmaps connect your work to other programs, for example Acquiring nascent technologies from industry or academia Collaborating with related projects in other services or other agencies Transitioning to new weapon systems of upgrades of fielded systems Technology roadmaps connect your work to broad technology advances in your discipline, for example impact of: Integrated circuit technology on your embedded controllers Autonomous control technology on your vehicles New materials on your sensors 32
Suggested Best Practices for Roadmapping Integrated with technology development and selection Integrated with stage-gate and other execution processes Incorporate awareness or (better) collaboration with other technology development organizations Clear distinction between a presentation of the lay of the land (passive observation) versus a plan for changing the landscape (active intervention) Roadmapping can be used for either Reviewed and supported by high-level leadership Articulates a collaboration strategy with all stakeholders Linked to portfolio analysis and risk analysis Focus on outcomes how will it be implemented? What are the challenges that you have seen? 33
RELIANCE 21 AND COMMUNITIES OF INTEREST 34
Reliance 21 Management Structure Reliance 21 (http://www.acq.osd.mil/chieftechnologist/reliance21.html) is the overarching framework of the DoD s S&T joint planning and coordination process DBRAG: Defense Basic Research Advisory Group LQEP: Laboratory Quality Enhancement Panel 35
Communities of Interest (CoI) 16 cross-cutting, S&T areas staffed with senior leaders and subject matter experts from the Services and Defense Agencies Mission focus Capabilities enabled by advanced technologies and systems Counter-IED Counter-WMD Biomedical (ASBREM) Systems/ Capability focus Multiple technologies are integrated into complex systems to achieve mission impact Command, Control, Comms, Computers, and Intelligence (C4I) Autonomy Air Platforms Human Systems Ground & Sea Platforms Cyber Sensors Electronic Warfare Space Weapons Technologies Technology focus Technology goals with multiple applications Advanced Electronics Energy & Power Technology Materials & Manufacturing Processes Alumni CoIs Engineered Resilient Systems (http://www.acq.osd.mil/chieftechnologist/cois.html) 3
Reliance 21 Operating Principles 37
38
What do COIs Achieve? Deliver strategic plans and roadmaps with a 10 year horizon that capture technical goals and mission impact Identify common S&T needs and show Where they are being addressed Where there are gaps or future opportunities Plans are used to guide long-term budget decisions and to influence near-term program priorities in each of the Services Work closely with program executives and warfighters throughout the Department Are also expected to coordinate international S&T engagement for their technical area Are considered mission-critical to the effective conduct of the Department's S&T program 39
Roadmapping Exercise 1. In this exercise, you will help Joshua, in the case study, plan technology development in the context of completed, ongoing, and planned technology projects in other agencies 2. Joshua has the option of a. developing technology in his own branch b. depending on another lab or agency to develop the technology c. collaborating with the other agency and modifying their plans 3. There are several technology gaps, and closing them is far to expensive for Joshua s lab going solo, so creativity will be required 4. A great deal of technology development has already been done on scramjet propulsion for hypersonic vehicles. 5. The result of this effort should be (1) a technology roadmap (with supporting Roadmap Strategic Diagram) and (2) a plan for next steps 40
Lesson 3 Summary Technology roadmapping is the process as well as the end product Links Strategy to project proposals Has 4 steps from planning to implementation Planning Implementation Internals and external inputs have to be considered when developing technology roadmaps There are multiple standard types of technology roadmaps based on their planning purpose 41