Methodological bases for the development of a roadmap. How to create the perfect product roadmap and what is needed for this? When to Apply the Model

Cherepanov M.A.

In a dynamic external environment, companies that are focused on the prospects for the development of their activities, it is necessary to introduce modern methods of organization management. These methods make it possible to most accurately represent, evaluate and predict the future development trend of the company, develop probable scenarios for the development of facilities, and their potential profitability, as well as make optimal management decisions in terms of resource costs and economic efficiency.

The domestic theory of management does not attach sufficient importance to many modern methods that could not only facilitate the management of modern organizations, but also create a detailed scenario plan for the development of any object.

One of the little-studied methods, which is a scenario for the development of a particular object, is " Road map". This method is based on the deductive decomposition of the process of achieving a goal into steps, this process is called "Road Mapping". In general, road mapping serves as the basis for information support of the management process, and in particular, this technique serves to develop the stages of development of an object and determine the time for making management decisions, as well as to rationalize the cause-and-effect relationships between various stages of the project.

The theme of road maps is reflected in the publication of K.L. Lidin "Varieties of building roadmaps", which describes the essence of the method of road mapping, and its application in real organizations. The work "Roadmaps of Russian business: Analytical report on the study" by the team of authors Manchulyantseva O.A. and others, is devoted to the practical use of road maps. This work is based on an original study, which includes a questionnaire survey, expert and in-depth personal interviews with executives and top managers of 50 largest Russian companies. The analysis of these works makes it possible to identify the reasons for the productivity of using this method, which separates road mapping as an effective method of project management. Based on the sources presented, it is possible to identify limitations and barriers to the application of the road mapping method, as well as predetermine methods for overcoming these negative circumstances.

The purpose of this article is to define the content of the road mapping method and its application for the development of the organization.

The author refers to the objectives of the study carried out a comparative analysis of road mapping and other tools for the development of the organization; explore the benefits and limitations of road mapping; consideration of the possibility of creating project portals based on the method of road mapping.

Currently, there are many tools that contribute to the development of the organization. Such tools are used to form guidelines and priorities for making managerial decisions. A comparative analysis of these tools is presented in Table 1.

Table 1 — Comparative analysis of management decision-making tools

All of the above methods, with their proper use, create an information base that facilitates managerial decision-making:

The application of the Delphi method results in several well-founded decisions based on a survey of a group of people.

SWOT analysis gives a structured description of the situation regarding which a decision needs to be made, the conclusions drawn on its basis are descriptive without recommendations and prioritization.

As a result, the brainstorming method presents a list of solutions to a specific problem expressed by experts, and then, from the total number of ideas expressed, the most successful ones that can be used in practice are selected.

The scenario method is a text that allows you to create a preliminary idea of ​​the system in terms of quantitative parameters and their relationships, however, the scenario, like any text, is subject to ambiguity in its interpretation, so it should be considered as the basis for further development of a model for solving the problem.

The goal tree method allows you to present a complete picture of the relationship of future events up to obtaining a list of specific tasks and obtaining information about their relative importance. The construction of a tree of goals and objectives ends at the level of determining the executors. In the process of building a tree of goals, algorithms for the joint work of experts are often used, but, nevertheless, the method is based not on group work as such, but on a special logic of reasoning.

Building a roadmap, as a result, gives a graphic plan-scenario for the dynamic development of the organization, taking into account alternative paths and the possible identification of areas of performance degradation (bottlenecks), as well as detailed description such important components of the organization as resources, technology, product, market, customer, strategic goal, and creates a well-coordinated system of communicative interaction between all organizational structures.

All the presented methods cannot fully represent the results that are achieved by creating a roadmap, but they can act as a basis for using the roadmapping method.

One of the main features of roadmaps is their appearance, namely, they look like a variant of the analysis based on the selection of possible solutions for individual parts of the main problem - the construction graphic network, consisting of "nodes" (stages of technology development, or points for making managerial decisions) and "links" (causal relationships between "nodes").

As a strategic project management method, road mapping has two main functions:

foresight and planning of the development of the situation, including technological, social, economic and political aspects (forecast of the future);

managing the development of the situation depending on the set strategic goals (designing the future).

Roadmaps imply long-term development of an object for up to 10 years, and reflect the resulting economic effects, determine the effectiveness of alternative options for using resources.

Based on the goals of road mapping, the following types of road maps are distinguished:

Corporate roadmaps;

Scientific roadmaps;

Technology roadmaps;

Product roadmaps.

Any type of roadmap represents the evolution of a product, technology, scientific component of a company, or a corporation as a whole, and creates a graphical representation of various options for the development of an object in time space. Different kinds roadmaps are interconnected and interdependent, which is associated with the need to simultaneously take into account product, technological, industry or corporate components.

Types of road maps are divided by relevance depending on specific goals and time periods. Relevance criteria are based on the versatility of roadmaps, the more components a roadmap includes, the more informative it is for an organization. The lack of strict regulation distinguishes the mapping process high level creativity, which makes it possible to make roadmaps a simple, visual and adaptive tool for making managerial decisions.

On the initial stage development of the organization, the creation of a corporate roadmap, which includes scientific, technological and product aspects, is of particular importance. The next most important is the scientific goal, which includes technological and product components. In the future, the organization no longer needs to develop global roadmaps, because at subsequent stages of development only concentrated methods of organizational management are needed, which are aimed at researching production technologies and products.

The optimal form of a roadmap is a schedule that provides answers to questions about what exactly, how, in what period of time and why will lead to the achievement of the strategic goals of the organization.

Table 2 - Advantages and limitations of using roadmaps

To overcome the limitations and barriers to the use of roadmaps in organizations, various authors propose the following activities:

Establishment of a strategic planning department.

Creation of organizational and regulatory support for road mapping within the organization

Training of employees of the strategic planning department in road mapping;

Creation of a strategic monitoring system.

The barriers to the implementation of road mapping include well-established planning methods in organizations, which is caused by conservatism and the lack of a generally accepted road mapping methodology.

Table 3 - Universal methodology for building roadmaps

Based on the developing external environment, the algorithm proposed by the methodology can be amended in the stages and activities that will most effectively build a roadmap in relation to a particular organization.

The essence of creating project portals is to organize an electronic space that allows you to track the progress of a specific project in real time, as well as to carry out electronic document management for the project. That is, the project portal is an effective system for storing and accessing internal corporate information necessary for project management and project communications by absolutely all project participants. The scheme of interaction between project participants through the project portal is shown in Figure 2.

Rice. 1. Scheme of interaction between project participants through the project portal

The project portal contains a list of ongoing programs, which consist of projects. Inside each project is a roadmap, which is divided into 3 scenarios: optimistic, optimal, and pessimistic. Each of the scenarios involves its own chain of project implementation.

Every project starts in the optimal implementation scenario because the project inputs are always known. Further, as the project progresses, scenarios may change as risk events occur and their results.

When planning a project implementation roadmap, all scenarios must be carefully planned, namely: what inputs are present in the project; what risk events may occur during the implementation of the project, and what are their consequences; what actions should be followed after the occurrence of a particular risk event; and what is the end result. As the actual implementation of the project, its scenario is marked in red. A graphical example of a project roadmap is shown in Figure 3.

Rice. 2. Project roadmap

The main elements of the roadmap are:

Beginning of the process;

risk event;

Action;

Process result.

In general, each element of the roadmap should contain source documents or other objective grounds on the basis of which a management decision is developed. In particular: the element "Beginning of the process" contains information about the available resources at the beginning of the project; "Risk event" contains information about the scenarios that must be applied when a risk occurs; "Action" contains technologies and methods; The Process Outcome element contains information about the end product of the project.

This system will allow centralizing the management decision-making system, get rid of the distortion of information, and form the document flow of projects. Also, on the basis of already implemented projects, you can create a typical roadmap, when implementing similar projects, this will greatly simplify the process of achieving strategic goals within the organization.

Today, in state bodies, project management methods are just beginning to be introduced. Road mapping based on a system of project portals must also be introduced into the system of interaction between government agencies. This innovation will facilitate the process of interaction in the implementation of identical projects, will reduce both labor costs and, accordingly, material costs. According to the author, the widespread introduction of project portals based on the road mapping method will create a database of projects in various fields of activity.

The project portal allows you to effectively solve organizational, communication and other tasks related to the administration of the organization's project activities, as well as increase the efficiency and timeliness of managerial decision-making. The project portal is an innovative method of interaction between the subjects of any activity, which increases the effectiveness of this interaction.

Summarizing all of the above, it is necessary to conclude that road mapping is an effective method used for organizational development, on the basis of which management decisions are developed and implemented. This method, at present, is not widely popular, as most management personnel try to use established management methods, and, due to their conservatism, do not consider road mapping as an effective management method.

Literature

Research methods [electronic resource]. URL: http://s21.ozersk.chel.fcior.edu.ru/nd/poisk/method_issled.htm (accessed 20.02.2014)

Khvoshchin A.A. Socio-economic forecasting. Tutorial. Tyumen: Tyumen State University Publishing House, 2007.

Road mapping technology [electronic resource]. URL: http://www.unido.org/fileadmin/import/16963_TechnologyRoadmapping.pdf (Accessed 02/23/2014)

Lidin K.L. Variety of building road maps. Irkutsk. 2006.

Dzhemala M. Corporate "road map" - An innovative method of knowledge management in corporations // Russian Journal of Management. 2008. Volume 6. No. 4. S. 149-168.

Manchulyantsev O.A., Pavlycheva E.Yu., Krauzova E.N., Tkacheva A.V. Roadmaps of Russian business: An analytical report on the study. Moscow: Open Innovation Inc. 2012. 64 p.

SWOT.-analysis [electronic resource]. URL: swot-analysis.ru (accessed 03.03.2014)

Brainstorming method [electronic resource]. URL: http://www.metodolog.ru/00072/00072.html (accessed 10.03.2014)

Peregudov F.I., Tarasenko F.P. Introduction to system analysis. Moscow: Higher school, 1989.

Goals of enterprise management [electronic resource]. URL: http://univerlib.ru/page/23-cely-v-upravlenii-3262.html (Accessed 03/10/2014)

Bibliography

research methods. URL: http://s21.ozersk.chel.fcior.edu.ru/nd/poisk/method_issled.htm (date of access 20.02.2014)

Hvoshchin A.A. Socio-economic forecasting. coursebook. Tyumen.: Tyumen State University Publishing House, 2007.

road mapping technology. URL: http://www.unido.org/fileadmin/import/16963_TechnologyRoadmapping.pdf (date of access 02/23/2014)

Lidin K.L. The variety of roadmaps design. Irkutsk. 2006.

Jemala M.Corporate « road map» — innovative method of knowledge management in corporations // Russian Management Journal. 2008 Vol. 6. No. 4. P. 149-168.

Manchulyantsev O.A., Pavlycheva E.Yu., Krauzova E.N., Tkacheva A.V. Road maps of Russian business: analytical report on research. Moscow: Open Innovation Inc. 2012. 64 p.

SWOT-analysis. URL: swot-analysis.ru (date of access 03.03.2014)

Roadmap as a tool for planning and monitoring the strategic development of the machine-building complex of the Samara region

Deev Alexander Anatolievich
Senior Lecturer

departments of state and

municipal government
Russian Economic University

named after G.V. Plekhanov
[email protected]

annotation

The development of sectoral roadmaps for the development of the machine-building complex suggests that the administration of the Samara region can provide the necessary conditions for the effective development of machine-building in the region, managing a wide range of resources and the development of economic structures to increase the investment attractiveness of machine-building enterprises of various clusters in the region.

Abstract

Working out of branch road maps of development of a machine-building complex assumes that the administration of the Samara region can provide the necessary conditions for effective development of mechanical engineering in area territory, operating wide scale of resources and development of economic ways to increase of investment appeal of the machine-building enterprises of various zones in area territory.

Keywords

Scenarios, roadmap, economic effect, clusters, scenario methodology, mechanical engineering, processes, modernization, program-targeted and project-oriented management.

keywords

Scenarios, road map, economic benefit, zones, scenario methodology, mechanical engineering, processes, modernisation, the programmno-target and design-focused management

A roadmap is a visual representation of a step-by-step scenario for the development of a certain object: a single product, a class of products, some technology, a group of related technologies, a business, a company that combines several business units, an entire industry, an industrial cluster, an industry, and even a plan to achieve political, social and other strategic goals.

Examples of various roadmaps to support management tasks are presented in Figure 1.1.

Figure 1.1.- Examples of "Roadmap"

The proposed examples of roadmaps can be used to address a wide range of managerial issues within the administration of the Samara region. In particular, they can be used to visually represent the results of planning and monitoring project-oriented activities.

The roadmap is recommended to be used to present and discuss the execution logic and the generalized schedule of the Portfolio/Project/Programme. At the same time, the roadmaps themselves make it possible to present a general picture of project activities, which can be used both in planning tasks and in monitoring and control tasks. This high-level overview presents milestones, milestones/results and the Projects/Programs themselves as a whole. Such schemes contain critical tasks and the logic of their implementation, and also represent the main results of the target activity.

Roadmap is:

The most important events on one page;

Simple, clear symbolism for major milestones, activities, and critical jobs;

Arrows showing the logic of work execution and presentation of results.

Roadmaps allow you to visually link the vision, strategy and development plan of the object, building in time the main steps of this process according to the principle "past - present - future". Roadmaps allow you to view not only likely scenarios, but also their potential profitability, as well as choose the best paths in terms of resource costs and economic efficiency. In the general case, roadmaps are aimed at informational support for the decision-making process for the development of the control object.

For roadmaps, it is possible to formulate invariant principles for the formation and implementation in practice:

1. All roadmaps include a plan-forecast for the development of an object for the long term - as a rule, it is about 10 years - broken down into smaller sub-periods (horizons), the duration of which depends on the specifics of the object - be it a consumer product characterized by a relatively short life cycle , or an entire technological field or industry that has been developing for decades under the influence of a wide variety of factors. At the same time, the planned or predicted state of the object has already been expertly set, the roadmap only clearly reflects the path to achieve it.

2. All roadmaps are quite an expensive management tool. Since the preparation and implementation of any long-term plan is always associated with risks of a very different nature, to create a roadmap, it is necessary to form an entire working group, which should include specialists of the most diverse profiles and the highest competence, and depending on the scale of the object, the number of specialists may vary significantly.

3. The process of forming a roadmap in itself is a kind of revision of the existing development potential of the object under study, the detection of bottlenecks, threats and opportunities for growth, needs for provision, etc.

4. The roadmap is an interactive tool that allows you to immediately make any changes and clarify the scenarios for the development of the object. At the same time, it is important that the roadmap becomes a necessary management tool used not only in planning tasks, but also in monitoring and decision support tasks. This will make the roadmap itself an effective and efficient toolkit for managing the implementation of the facility development strategy.

5. The degree of development of the roadmap for different horizons can be different, from detailed blocks and milestones for the near future, to the general setting of target results for the long term.

In Russia, road maps are not yet a generally applicable management tool. Therefore, as such, unified methodological approaches and algorithms for the formation of roadmaps have not yet been formed, the structure and form of this document are not rigidly specified, and the entire construction process is characterized by a high degree of creativity.

Taking into account the specifics of the object under consideration - the machine-building complex of the Samara region, it is inappropriate to consider individual structural-logical elements and subsystems separately. Therefore, the roadmap should also reflect a "comprehensive picture" that allows you to coordinate and interconnect the various components of the machine-building complex and its environment within the framework of purposeful development.

An example of a possible template for presenting a roadmap for the development of the machine-building complex of the Samara region is shown in Figure 1.2.

Figure 1.2. - An example of a possible template for presenting a roadmap for the development of the machine-building complex of the Samara region

As part of the presented template, the following structural and graphic elements were used:

Structural elements:

1. Target areas of strategic development - the main areas of activity with which the successful implementation of strategic transformations of the machine-building complex of the Samara region can be associated. These areas are:

1.1. Legislation - combines activities in the field of formation of favorable legislative conditions and provisions;

1.2.Taxation - combines activities in the field of tax regulation;

1.3. Related clusters - fixes milestones and key points that are necessary for the interconnection and coordination of ongoing measures for the development of the machine-building complex in conditions of close interaction with other socio-economic subsystems;

1.4. Market - fixes the conditions and conditions for the development of markets for the sale of engineering products, as well as, if necessary, other "related" sales markets;

1.5.Products - fixes the target dates for the creation of new products / services within the framework;

1.6.Technologies - fixes the composition and timing of the deployment of new technologies that are critical for the implementation of the strategy;

1.7.Research and Development - fixes the directions and tasks of applied research for the innovative development of the industry.

2. Time horizons of strategic planning are the key stages in the implementation of measures for the development of the machine-building complex of the Samara region. As such horizons, you can use:

2.1. Operational horizon (Horizon 1) - the interval for achieving "quick wins".

2.2.Our strategy (Horizon 2) is the interval for the formation of reserves and potentials to achieve long-term goals.

2.3. Perspective (Horizon 3) - an interval of strategic perspectives and ambitious goal formulations.

Graphic elements:

- a legislative act or other legal document;

– tax incentives or other preferences for taxes and fees;

– milestones or target controlled results;

– state of the markets;

– introduction/production of new products, product lines;

– deployment and implementation of technology;

– conducting research and development.

Also among the graphic elements are directional arrows denoting logical, technological and other relationships between the elements of the network diagram, which interconnects the various structural components of the roadmap. At the same time, the structural components of the roadmap themselves represent specific activities (usually programs and large projects), as well as key results for these programs / projects or checkpoints, allowing unambiguous evaluation of the strategy implementation progress.

The placement of one or another graphic element on a “track” indicates a semantic, technological or other classification assignment of the corresponding program/project or their results to a specific direction.

In cases where the proposed division into areas may be ambiguous due to the high complexity of programs and projects implemented as part of the implementation of the strategy, more simplified road maps may be formed that display only the composition, relationships and "temporal" parameters of the objects of the road map, or use other forms of semantic grouping of objects (for example, on a territorial basis, or on the basis of a responsible / supervising person), or other formats for displaying information on planning and monitoring the implementation of the adopted strategy.

Among the possible effects of the use of roadmaps, the following are usually noted:

With the help of roadmaps, it is possible to set more realistic goals and form the most effective ways their achievements.

Roadmaps are the link between strategy, market data, technology, society and other aspects of the facility environment.

The roadmap develops a kind of "guide" for managers, thus allowing you to identify intermediate results and adjust areas of activity. As a result, a “balance” is formed between short-term and long-term problems, strategic and operational tasks related to technology, resources, finance and other aspects of activity.

With the help of roadmaps, gaps (shortcomings) in the plans are detected, which allows them to be avoided, rather than to solve possible problems in the future.

Accounting for time and temporal relationships. Creating roadmaps helps leaders ensure that they have the resources, technology, and capabilities they need to execute strategy and plans at the right time.

The creation of road maps involves the exchange of information between representatives of the administration, business, society and other parties interested in the development of the facility. Using the roadmap, you can very easily explain in which direction it is planned to develop the object and in which it actually develops.

The formation of a roadmap requires the development and improvement of the management system, which should inevitably lead to an improvement in the general state of managerial decision-making processes.

To build a roadmap for the machine-building complex of the Samara region, it is first advisable to form a hierarchical structure that reflects the main directions and activities in the framework of the strategic development of the machine-building complex of the Samara region, indicating the target results, and then display the resulting tree on the "temporary" axis indicating the logical, technological and other links between planned activities and key results. A possible variant of such a structure is shown in Figure 1.3.:

Figure 1.3.- The structure of the decomposition of the main directions, activities, target results and milestones for the roadmap for the development of the machine-building complex of the Samara region

The presented scheme contains the main directions and blocks of work, indicating the key results. In the process of discussing and introducing the Roadmap technology into the management processes of the administration of the Samara Region, this structure can be supplemented, refined and adjusted accordingly. A variant of displaying the proposed activities and their result on the time axis is shown in the figure (see Figure 1.4.)

Proposals for the roadmap of the machine-building complex of the Samara region can become the basis for the introduction and development of effective and efficient methods of program-targeted and project-oriented management in the implementation of targeted changes in the national economic and socio-economic systems, subsystems and complexes on the territory of the Samara region.

Particular attention should be focused on the development of relevant principles and management systems in the Samara region, which should form a systemic basis for the implementation of program-targeted and project-oriented management.

The proposed decomposition structure of the main directions, activities, target results and control points for the roadmap for the development of the machine-building complex of the Samara region and the roadmap for the development of the machine-building complex of the Samara region itself are "open", i.e. allow for expansion and adjustment both “vertically” (adding new areas recognized as essential for the implementation of the strategy) and “horizontally” (decomposition of work and target results within the proposed areas and activities).

Picture 1.4.- Roadmap for the development of the machine-building complex of the Samara region

Bibliographic list

1. Kozlov A.S. Program and Project Portfolio Management: Processes and Tools. Monograph. - M .: CJSC "Project PRACTICE", 2010. - 350 p.
2. Kozlov A.S. Methodology for portfolio management of programs and projects. Monograph. - M .: CJSC "Project PRACTICE", 2009. - 194p.
3. All-Russian classifier of types of economic activity.
   OKVED. OK 029-2001 (NACE Rev. 1). OK 029-2007 (NACE Rev. 1.1).
4. Directory of enterprises and organizations of the machine-building complex of the Samara region / Ministry of industry, energy and technology of the Samara region. www .minprom. samara .en, accessed 11/10/2010. – 15 s.
5. Strategy for socio-economic development of the Samara region for the period up to 2020. Appendix to the Decree of the Government of the Samara Region of October 9, 2006 No. 129. - 329 p.
6. Forecast of socio-economic development of the Samara region for 2011 and the planning period of 2012 and 2013. Annex 2 to the Decree of the Government of the Samara Region dated October 21, 2010 No. 506
7. V. Artyakov. Speech with a budget message to the deputies of the Samara Provincial Duma. http://www.adm.samara.ru/news/important/11.11.2010/55218 accessed on 08.12.2010
8. State and business: institutional aspects - M.: IMEMO RAN, 2006
9. Savransky P.V. Public-private partnership in the implementation of promising areas of innovative development of the Russian economy. Dissertation for the degree of candidate of economic sciences.

Project roadmap

To achieve the result, each person plans his activity and draws it up using the plan. To implement any idea, a project is used that allows you to realize the author's intention. The project is carried out in stages, a roadmap is used for its successful implementation.

A roadmap is a step-by-step implementation of project implementation activities that allows you to predict the result of each stage and the project as a whole. The project roadmap specifies the exact start and end dates for each implementation activity in a specific order.

Algorithm for compiling and designing a project roadmap

In order to create a project roadmap, you need to:

1. Determine the scope of work and activities.

2. Determine the order in which each activity in the project will be performed.

3. Determine the start and end dates for each activity.

4. Determine the performers of each type of activity.

5. Indicate in the roadmap the sequence of each type of activity and the exact dates for the start and end of work.

For example: Roadmap for the Health Rainbow mini-project

* Responsible can be not only micro-collectives, but also a person

Sample:

1. Draw up a roadmap for the project "Nature is our home" using a well-known algorithm:

2. Determine the total number of days and months that will be needed to complete the project "Nature is our home"

Option to perform an informative task:

Project roadmap development - guidelines and examples of roadmap development. The degree of implementation of each project depends on the plan and control over its implementation. The roadmap format is the most acceptable way to implement any event. This tool is an algorithm with fixed stages of development of an object and a certain time for solving a particular problem within the framework of the project.

A roadmap is a time-based chart. A well-designed chart allows for a qualitative analysis of the relationship between the current state of affairs and emerging prospects.

Purpose and signs of the need to develop a roadmap

The goal in developing a roadmap is to present the development path of an object, taking into account possible options to achieve the desired result. A political situation, a technological process, interpersonal relations, etc. can be considered as an object.

A well-prepared roadmap should have one goal and several options to achieve it. In this case, priority is given to the scenario that looks more beneficial to achieve the final result. The principle “the end justifies the means” with this method of planning fades into the background, since other scenarios can only be applied in the event of force majeure.

Let us give examples of conditions when roadmap development is a legitimate need:

• There have been significant changes in the scope of the company.
• The company is losing market share due to the rapid growth of competition in the industry.
• The company has a vision of competitive development, but cannot competently draw up a strategic plan.

• objective of the project;
• a list of necessary measures with the definition of responsible persons;
• the main requirements for the work for which the managers are responsible;
• time intervals required for the implementation of a specific activity;
• checkpoints at each stage of the project with the provision of reports on the activities performed;
• possible options another way to implement the project.

Types of road maps

There are several types of roadmaps. All of them contain some common elements, but pursue different goals and objectives.

Roadmap in industry- aimed at developing strategies for enterprises, taking into account the demands set by the market.

Science and technology roadmap- allows you to determine the choice of a particular technology to optimize the production process.

Product roadmap allows you to find the best way to develop a product (service). Minimizes the risks arising from the implementation of this process. Enterprise business plan can be a special case of a roadmap of this kind.

Program roadmaps- are used, as a rule, by government agencies to develop strategies adapted to a rapidly changing political and economic situation.

The division of roadmaps into types is rather arbitrary, since the implementation of any major project affects many areas of human activity. The goal of optimizing the operation of each mapping object is to obtain the maximum economic effect using the least costly ways to achieve this result.

Development project roadmaps

The process of developing a roadmap (road mapping) is a complex and costly undertaking. To optimize the activities of any large facility, it is necessary to create a working group, which will include specialists from various industries, science, etc.

To create an effective development algorithm, a detailed study of the processes that have taken place at the facility so far is necessary. Roadmaps are a pretty handy strategy visualization tool.

NTI roadmaps must comply with the form of an action plan ("roadmap") of the National Technology Initiative, which is an annex to the Rules for the development and implementation of action plans ("roadmaps") of the National Technology Initiative (hereinafter referred to as the Rules), approved by a government decree Russian Federation dated April 18, 2016 No. 317, with the exception of the road maps specified in paragraph two of clause 2 of the Rules.

Roadmaps are created using the text editor Microsoft Word for Windows in Times New Roman font size No. 12 (for tabular materials), 13 or 14 with 1 line spacing.

Margin sizes in the text of the roadmap should be defined as follows: left margin - 30 mm, right margin - 15 mm, top margin - 20 mm, bottom margin - 20 mm (these parameters should be applied in both landscape and portrait page orientations).

Roadmap pages should be numbered. The page number is printed in the center of the top margin of the sheet in Arabic numerals without a heading and punctuation marks in a font of the same size as the text of the document. The page number is not printed on the first page of the document.

Title and heading formatting

The “Roadmap Name” prop must include the words “National Technology Initiative Action Plan (“Roadmap”) and a market designation printed with a lowercase letter in quotation marks, formed as a result of creating a compound abbreviated word by combining the original word denoting the field of activity on English language, and the transliterated component “no” (“Marinet”, “Healthnet”, “Foodnet”, etc.), for example:

The word "PLAN" is printed in one line in capital letters with a sparse character spacing of 2 pt. The words in the remaining lines of the props are printed in lowercase letters (with the exception of the words "National" and the market designation, printed in uppercase letters), centered relative to the longest line, which is limited to the right margin.

The props are printed with 1 line spacing in bold type, aligned to the center of the page without paragraph indentation.

The heading of a section (subsection) of the roadmap consists of a number and a thematic part that verbally defines the content of the corresponding structural unit of the text, and is given in accordance with the form of the plan.

A dot at the end of a heading placed on a separate line is not put. In the heading, consisting of two independent, syntactically unrelated sentences, a dot is placed between them, and at the end general rule dot goes down.

Sections (subsections) should have sequential numbers within the entire document, indicated by Roman numerals with a dot (subsections - by Arabic numerals with a dot), for example:

Headings of sections (subsections) are printed aligned to the center of the page without paragraph indentation at 1 line spacing, separated from the previous and subsequent requisites by 1.5 line spacing.

When preparing a roadmap for printing, it is not recommended to place headings and subheadings at the bottom of the page if it does not fit more than 2 lines of subsequent text.

The text of the roadmap may provide for structuring into paragraphs within sections.

In this case, the paragraphs are numbered with Arabic numerals with a period (if there is a number with a dot, the text starts with an uppercase letter). It is recommended to do through (single throughout the text) numbering of paragraphs within sections.

Indexing numbering (consists of the numbers of all sections, subsections, etc., to which a certain structural unit of the text is subject, for example: 2.11) is possible when naming subsections (no more than one additional level) and tables (multiple level numbering is possible), and also when making applications containing technical information.

Headings are not assigned to paragraphs in the text.

Text decoration

The text of the roadmap should be clear, concise, logical and provide an accurate and unambiguous perception of the information contained in it.

The paragraph indentation of the roadmap text lines (excluding tables, illustrations, etc.) is 12.5 mm from the left border of the text field.

Hanging lines are not allowed in the text of the document (a hanging line means the initial line of a paragraph that ends a page, or the end incomplete line of a paragraph that starts a page, which are unacceptable according to the general rules of document design).

Spacing between paragraphs in the text does not apply.

Font highlights in the text (bold, italic, underline, color, etc.) are used only when there is a special need to draw attention to the structural units of the text (sentences, phrases, words, abbreviations).

The text of the roadmap can be formatted as a connected text, a table, or a combination of these structures.

If a special system of abbreviations of concepts is introduced in the roadmap, the abbreviations are given in brackets after the first use of the expanded concept, for example:

If an expanded concept needs to be structured into several abbreviations, or the presentation of the text does not allow the introduction of abbreviations for each expanded concept, the abbreviations are given in brackets after the corresponding concept, for example:

With a significant number of concepts that require abbreviation, as well as the need to define the concepts and terms used in the roadmap, a List of terms and abbreviations is formed in the order of the Russian alphabet, which is placed in the annex to the roadmap.

Formatting footnotes and notes

After the footnote character, the footnote text begins with an uppercase letter. A dot is placed at the end of the footnote.

If necessary, notes may be provided in the text of the roadmap.

A note is drawn up by indicating the word "Note" and a sentence continuing after a colon or several paragraphs, numbered in Arabic numerals with dots (the text in such paragraphs is printed with a capital letter and ends with a dot).

For the design of the note, Times New Roman font is used, 1-2 points smaller than the point size of the main text of the roadmap.

Registration of numerical units

Monetary amounts in the roadmap are given in Russian rubles using the unit of measure "thousand" (thousand rubles). If necessary, the roadmap can use the designations of other national currencies of the world and the units of measurement "million" or "billion" (for example, when analyzing the world economy, etc.).

Numeric values ​​when listed (if there are fractional numbers) are separated by a semicolon (for example: "1.2; 5.1; 6.3").

Amounts in numerical form are given with a breakdown into groups denoting thousands, hundreds of thousands, millions, etc. (divided into groups of three digits from right to left (except for the fractional part), separated by spaces). The point between the digital groups of a multi-digit number is not put.

The fractional part is separated from the corresponding numeric group by a comma.

Registration of details and applications

The details of legislative and other regulatory legal acts are indicated in the text of the roadmap in the following order - the type of act, the date of its adoption (approval), the document number and the name of the act (document title), for example:

It is not allowed to use the sign "N" as part of the details of regulatory legal acts, documents of a legal nature, as well as in other cases where it is necessary to designate numbers. The sign "No" is used to designate numbers.

If there is an attachment to the roadmap, the text of the roadmap must include a link to such an attachment. The link to the application is entered using the words "according to the application", for example:

If there are several applications, they are numbered with Arabic numerals.

with the sign "No." References to appendices are given in the text as the appendices are located. The order of attachments to the text of the roadmap should correspond to the order in which links to attachments are indicated in the text of the roadmap.

A multi-line attribute - the mark "APPENDIX" - indicating the name of the road map is located in the upper right corner of the first sheet of the document and is printed from the border of the upper field without quotes in capital letters.

The word "APPENDIX" is separated from the subsequent lines of the requisite 1.5 line spacing. The remaining lines of the requisite are printed with 1 line spacing.

All component parts of the attribute are centered relative to the longest line. The line length should not exceed 10 cm and is limited to the right margin of the document. For example:

List design

For the design of the lists (enumerations) contained in the text of the roadmap, sub-items are used, which are indicated by letters with brackets (for example: “a”, b), c)”) or in the presence of a large amount of enumerations, numbers with brackets (for example: “1), 2 ), 3)”).

Each sub-item of the list (enumeration) begins with a paragraph with a lowercase letter and ends with a semicolon, except for the last sub-item, which ends with a period.

Dashes, circles, rhombuses, etc. are not used as a substitute for alphabetic or numeric headings to indicate the positions of the list.

Table design

To highlight and designate a table in the text of a document, depending on the structure of the document, thematic and (or) numbering headings (headings indicated by a number that determines the ordinal number of the table) are used.

The tables provided for by the plan form (section I, subsection 3 of section II, sections III and IV) are drawn up in accordance with the officially published text of Decree of the Government of the Russian Federation dated April 18, 2016 No. 317.

As a general rule, tables are designed as open (without rulers on the sides and bottom).

If necessary, tables can be designed as closed (framed with rulers) or combined (the head of the table is framed with rulers).

In the sidebar of the table (the left column of the table containing data about the rows of the table), the text of each position must begin with an uppercase letter. Punctuation marks are placed only inside the sentence. In the sidebar, after the words “Total”, “Total”, the colon is not put.

If the table is printed on more than one page, it is advisable to repeat the head (the upper part of the table in which the column headings are placed) of the table on each page. Table columns (a row of data in a table located vertically and usually placed between vertical rulers) can be numbered, in which case only the numbers of these columns can be printed on the following pages.

It is not recommended to include in the tables a column with the designation of a serial number (in the form of the symbol "No" or "No. p / p") in the tables provided for by the form of the action plan, which is an annex to the Rules for the development and implementation of action plans ("road maps") of the National Technological initiatives (hereinafter referred to as the Rules) approved by Decree of the Government of the Russian Federation of April 18, 2016 No. 317

The text in the table is printed along the left border of the table line without paragraph indentation or in the center of the column (numbers, units of measurement, etc.).

To format the text in the table, Times New Roman font is used, 1-2 points smaller than the point size of the main text of the roadmap.