GOST compliance with env. The order of execution of the env.
To narrow down the search results, you can refine your query by specifying the fields to search for. The list of fields is presented above. For example:
You can search in several fields at the same time:
Logical operators
The default operator is AND.
Operator AND means that the document must match all elements in the group:
research development
Operator OR means that the document must match one of the values in the group:
study OR development
Operator NOT excludes documents containing this element:
study NOT development
Search type
When writing a query, you can specify the method in which the phrase will be searched. Four methods are supported: search taking into account morphology, without morphology, prefix search, phrase search.
By default, the search is performed taking into account morphology.
To search without morphology, just put a “dollar” sign in front of the words in the phrase:
$ study $ development
To search for a prefix, you need to put an asterisk after the query:
study *
To search for a phrase, you need to enclose the query in double quotes:
" research and development "
Search by synonyms
To include synonyms of a word in the search results, you need to put a hash " #
" before a word or before an expression in parentheses.
When applied to one word, up to three synonyms will be found for it.
When applied to a parenthetical expression, a synonym will be added to each word if one is found.
Not compatible with morphology-free search, prefix search, or phrase search.
# study
Grouping
In order to group search phrases you need to use brackets. This allows you to control the Boolean logic of the request.
For example, you need to make a request: find documents whose author is Ivanov or Petrov, and the title contains the words research or development:
Approximate word search
For an approximate search you need to put a tilde " ~ " at the end of a word from a phrase. For example:
bromine ~
When searching, words such as "bromine", "rum", "industrial", etc. will be found.
You can additionally specify the maximum number of possible edits: 0, 1 or 2. For example:
bromine ~1
By default, 2 edits are allowed.
Proximity criterion
To search by proximity criterion, you need to put a tilde " ~ " at the end of the phrase. For example, to find documents with the words research and development within 2 words, use the following query:
" research development "~2
Relevance of expressions
To change the relevance of individual expressions in the search, use the " sign ^
" at the end of the expression, followed by the level of relevance of this expression in relation to the others.
The higher the level, the more relevant the expression is.
For example, in this expression, the word “research” is four times more relevant than the word “development”:
study ^4 development
By default, the level is 1. Valid values are a positive real number.
Search within an interval
To indicate the interval in which the value of a field should be located, you should indicate the boundary values in parentheses, separated by the operator TO.
Lexicographic sorting will be performed.
Such a query will return results with an author starting from Ivanov and ending with Petrov, but Ivanov and Petrov will not be included in the result.
To include a value in a range, use square brackets. To exclude a value, use curly braces.
5. The R&D process and the strategic objectives of its individual stages
5.6. R&D is the most important link in the implementation of the corporation’s strategy
After completion of applied research, subject to positive results of the economic analysis that satisfies the company in terms of its goals, resources and market conditions, they begin to carry out development work (R&D). R&D is the most important link in the materialization of the results of previous research projects.
Its main task is to create a set of design documentation for mass production.
Main stages of development work (GOST 15.001-73):
1) development of technical specifications for development work;
2) technical proposal;
3) preliminary design;
4) technical design;
5) development of working documentation, production of a prototype;
6) preliminary tests of the prototype;
7) state (departmental) tests of a prototype;
8) development of documentation based on test results.
An approximate list of works at the stages of development work is reflected in table. 5.13.
Table 5.13
|
Approximate list of works at the stages of development work |
Stages of OCD |
|
Main tasks and scope of work |
Development of technical specifications for R&D |
|
Coordination and approval of technical specifications |
Identification of additional or clarified requirements for the product, its technical characteristics and quality indicators that cannot be specified in the technical specifications: |
|
Schematic design (serves as the basis for technical design) |
Development of fundamental technical solutions: |
|
Technical design |
The final choice of technical solutions for the product as a whole and its components: |
|
Development of working documentation, production of a prototype |
Formation of a set of design documents: |
|
Preliminary tests |
Checking the compliance of the prototype with the requirements of the technical specifications and determining the possibility of submitting it for state (departmental) tests: |
|
State (departmental) tests |
Assessment of compliance with technical requirements and the possibility of organizing mass production |
|
Development of documentation based on test results |
Making necessary clarifications and changes to the documentation. |
Design is a set of activities that ensure the search for technical solutions that meet specified requirements, their optimization and implementation in the form of a set of design documents and a prototype (samples), subjected to a cycle of tests for compliance with the requirements of the technical specifications.
Any modern complex technical device is the result of complex knowledge. The designer must know marketing, the economy of the country and the world, the physics of phenomena, numerous technical disciplines (radio engineering, computer technology, mathematics, mechanical engineering, metrology, organization and production technology, etc.), operating conditions of the product, governing technical documents and standards.
In addition, you should take into account: the characteristics of the team and the requirements of real life, other people's experience, the ability to receive and evaluate information.
Not the least requirement for a designer is complexity of thinking and the ability to work with a large number of organizations. This skill is especially necessary for the developer of a product that is part of a more complex complex (for example, a radio station for a ship, an aircraft) or associated with other systems (for data output, power supply, control, etc.).
As an illustration, let us consider the typical procedure for the development and mastery of new technology in the interests of a specific department (Ministry of Defense, geological departments, Agroprom, etc.), see also table. 5.13:
|
Performers |
Works |
|
Academic Research Institute |
Search research, problem |
|
Research institute, head research institute of the industry, OKB |
Applied research (research into the possibility of creating a product) |
|
Research performer |
Main tasks and scope of work |
|
Technical proposal (determining the possibility of obtaining characteristics according to the technical specifications) |
|
|
customer research institute |
Specification of technical specifications |
|
Research Institute, OKB |
Draft design (definition of basic technical solutions, possible execution options) |
|
Technical design (definition of the main development option, main technical solutions) |
|
|
Detailed draft (development of prototype documentation) |
|
|
Research Institute, Design Bureau, |
Manufacturing a prototype |
|
Preliminary (bench) testing of a prototype |
|
|
Research institute, design bureau, pilot plant, object manufacturer |
Installation of a prototype on a carrier object |
|
Preliminary tests of the prototype on site |
|
|
State commission of the customer with the participation of research institutes, design bureaus |
State tests |
|
Development of documentation based on test results |
|
|
Transfer of documentation to the series manufacturer |
|
|
Plant, research institute, design bureau |
Preparation of production at a serial plant |
|
Release of a pilot batch |
|
|
Plant, research institute, design bureau |
Correction of documentation based on the results of the production of a pilot batch |
|
Release of installation series |
|
|
Established serial production |
The logical model of the developer's decision making can be stated as follows. Many technical solutions to satisfy i-th constraint, we denote A i. Then the set of technical solutions admissible under n restrictions will be defined as the intersection of the sets. First of all, the developer must find out that the last set is non-empty. Next, solutions and elements are identified from this set X which meet all the criteria specified in the technical specifications:
.
When designing any system, you can establish its input and output signals (in the information sense), external conditions and criteria for the success of the solution. In a general sense, the input of a system is the reaction of the environment to the system, and the output is the reaction of the system to the environment. External conditions can manifest themselves in two aspects: design constraints and the set of situations in which the system must operate.
The most complex and least developed task is the convolution of many criteria into a single one (objective function) (see, for example,).
The choice of specific technical solutions mathematically represents an optimization problem, for the solution of which well-known methods of the theory of operations can be used (direct calculation, classical method of differentiation, Lagrange multiplier method, calculus of variations, numerical search methods, linear and nonlinear programming, Pontryagin's maximum principle).
The ISO standard recommends comparing its characteristics with the corresponding characteristics of an analogue as a method for assessing the quality of a new product. Naturally, the validity of the assessment depends on the correct choice of the analogue. First of all, you should choose an analogue that is closest in functionality, available on the market with a stable market price and known technical and economic characteristics. If the designed product replaces several existing products in its functional purpose, then their totality is used as an analogue. Assessment of the quality level of developed products is made on the basis of a comparison of the main groups of technical and operational parameters: purpose, reliability, manufacturability, unification, ergonomics, patent-legal and environmental. The choice of the range of indicators is made in accordance with available materials (standards, industry materials, etc.) or is made by the developer himself. The rationale for such a choice should be contained in the R&D reporting materials. For example, different functional indicators are recommended for different groups of electronic equipment (Table 5.14.).
For each of the selected indicators for comparison, a coefficient of its weight (importance) must be determined by expert means.
As already indicated, the form of presentation of a complex quality indicator cannot be unambiguously justified. Therefore, you should use the requirements of regulatory documents or justify your choice.
Table 5.14
Composition of functional indicators
for different groups of radio-electronic equipment (REA)
|
Indicators |
radio |
radio transmitter |
radio measuring equipment |
TV receiver |
||
|
Sensitivity |
||||||
|
frequency range |
||||||
|
Range |
||||||
|
Range resolution |
||||||
|
Angle resolution |
||||||
|
Radiated Power |
||||||
|
Process performance |
||||||
|
Memory |
||||||
|
Time of perestroika |
||||||
|
Power efficiency |
||||||
|
Information processing time |
||||||
|
Noise immunity |
||||||
|
Contrast |
||||||
|
Nonlinear distortion |
||||||
The most widely used are two main forms of integral quality indicator:
1) additive
Where g i- weight coefficient i-th parameter; A i- quality indicator for i-th parameter; n- the number of parameters by which comparison is made;
2) multiplicative
The additive form (weighted average summation) is the most common, although its disadvantage is the possibility of “compensating” for the quality level for some parameters at the expense of others. In addition, it allows for a situation where the integral quality indicator is significant when one or more parameters are zero. In this sense, the multiplicative form of representation is preferable, although it should be noted that the multiplicative form is easily converted to additive by simple logarithm.
Other forms of estimates are also possible, which nevertheless reduce to the two listed monotonic transformations. For example, relative estimates of the potential of a project option are used in the following form:
where is the degree of influence i- option to achieve design goals;
– probability of the designer choosing this option.
For i th assessment of the total potential, then the summation of the partial potentials is performed. Since when assessing project options or the resulting effectiveness of the design and development work, relative assessments are made (that is, the absolute value of the complex quality indicator is not significant), the rules for using private criteria, their weights and the rules for making final decisions on the continuation and termination of the project are much more important. As already indicated, it is also important to take into account the possible compensation of some partial assessments at the expense of others in the additive form of a complex quality criterion. The author has repeatedly given the following example in various discussions on this issue. Suppose two versions of a vessel are being compared. The particular criteria of one of them have some average, mediocre values, and the other - all are excellent, with the exception of one - buoyancy, which is equal to zero. The formal application of the additive form of a complex quality criterion can lead to a paradoxical result - the second vessel will be preferred.
In the multiplicative form, the equality of one of the partial criteria to zero leads to a zero rating for the entire project. If such a criterion is unimportant, then it is better to exclude it from the list of criteria altogether. Another problem is of significant importance - bringing the compared options to a comparable form in terms of areas and operating conditions, the regulatory framework for calculating costs and useful results, and the final beneficial effect.
Comparability across areas and operating conditions is ensured by selecting appropriate design options.
Comparability in terms of useful results is necessary when there are differences in the technical and operational parameters used. Reduction to comparability using reduction factors is usually used. Essentially, they provide comparability for some selected reference parameters (energy, number of parameters and modes, accuracy, etc.). Thus, they indicate, for example, that in a comprehensive comparison of the radiated power of a radar and its reliability, the failure rate should be used for the latter parameter, rather than the probability of failure-free operation.
This is due to the fact that both the emitted power and the failure rate correlate with hardware costs in the same direction and approximately equally.
The coefficients of reduction to a comparable form are contained in table. 5.15.
|
Table 5.15 |
Reduction coefficients for various REA parameters |
Parameter |
|
Performance |
Annual volume of work of an analogue and a new product |
|
|
Versatility |
The number of analogue and new product objects required to simultaneously receive information from a certain number of points Number of working channels |
|
|
Accuracy of measurements |
|
The probability of obtaining a result with a given limit of permissible error between an analogue and a new product |
|
Communication range |
Ranges of analogue and new products |
|
|
Reliability |
|
Probabilities of failure-free operation of an analogue and a new device |
|
Receiver sensitivity |
Sensitivity of analogue and new product |
|
|
Radiated Power |
Radiated powers of the analogue and new product |
The consumption price serves as an integral economic indicator of a new product when comparing it with an analogue. It is expressed by the following formula:
Where TO– one-time capital costs (for acquisition, transportation, installation, as well as related costs);
Z e– operating costs for the entire operating time of the product.
With a long service life, naturally, dynamic estimates must be made using discounting. If, as a result of a change in the reliability of a new product compared to an analogue, the assessment of damage changes (including in adjacent units), this must be taken into account. In the same way, the associated positive results of using a new product should be taken into account. These include, in particular:
– reducing the dimensions and weight of aircraft and ships when installing new products on them instead of analogues;
– increasing the accuracy and speed of the control system (aircraft, ship, air transport, etc.), which reduces the path length, and therefore reduces fuel consumption and control costs.
Thus, the complete formula for determining the integral economic indicator has the form
where is the total amount of damage from failures;
R s– accompanying positive results from using the new product.
It is convenient to assess the technical and economic efficiency of a new product using table. 5.16.
Table 5.16
Assessment of the technical and economic efficiency of a new product
|
Parameter, |
New product |
||||
|
weightiness |
|||||
|
Integral technical indicator |
|||||
|
Integral cost indicator |
|||||
|
Technical and economic efficiency |
|||||
|
Relative technical and economic efficiency of R&D |
|
||||
The integral cost indicator can hardly be more or less accurately calculated in the early stages of development work. This is due to the incompleteness of design documentation and the lack of technological documentation. The only way out is to compare this indicator with the price of a product with a similar element base, technology and design. It is advisable to isolate large and complex components of the product and evaluate them separately. In accordance with international standards ISO 9000 (GOST 40.9000), the efficiency and quality of a new product is compared by comparing it with an analogue.
As indicated in, attempts to extremely formalize the work of developers and impose a strict program of actions on them are usually harmful, and in fact cannot be implemented. The methods proposed by some authors to fully automate the stages of search and conceptual design mainly come down to the creation of developed information and expert systems. It was indicated above that even when trying to formally assess the quality of technical systems, serious fundamental difficulties arise associated with the so-called second Gödel theorem, which states that within the framework of the created system it is fundamentally impossible to assess its quality. Criteria for assessing the quality and effectiveness of the system must be formulated within the supersystem.
It should be noted that there is no such thing as purely technical design. Any design is technical and economic and, therefore, the previously expressed considerations on the problems of mathematical modeling of economic and economic-production systems are applicable to it. However, such unity of the technical and economic aspects of design is often forgotten. Thus, the fundamentals of a systematic approach to the design process are set out as follows:
- project development proceeds from the general to the specific, and not vice versa;
- the designer should take on solving specific problems only after working on the general ones;
- when developing particular problems, it is necessary to take into account technical solutions (TS) adopted at earlier stages of design;
- new technical solutions appear as a result of a creative process that has an iterative nature of successive approaches to the goal;
- when making a decision, the requirements for the optimal functioning of a technical device (TS) prevail over others, for example, economic ones;
- the maximum design parameters of technical means are dictated only by physical and technical, and not economic factors, therefore, when designing, it is necessary to start with engineering calculations;
- the design of products is carried out taking into account the possibility and complexity of their production;
economic assessment of the design is always an important incentive to obtain rational solutions, but can not be done until options appear that meet the requirements for the functioning of the product and are technically feasible;
- when designing, it is necessary to make maximum use of known technical solutions, which represent a generalization of the vast experience of previous generations of engineers;
- to evaluate the decisions made, the designer must take into account the entire set of criteria contained in such indicators of the quality of technical equipment as operation, reliability, manufacturability, standardization and unification, as well as ergonomic, aesthetic and economic indicators;
- patent and legal indicators - necessary criteria for assessing new competitive technical solutions;
- when designing new technical means, you should think about their painless disposal after the expiration of their service life.
It is obvious that the author is inconvenient for the long-recognized principles of a unified technical and economic design, the inclusion of strategic issues in the design, a marketing approach, and so on. This is all the more strange since such an article was published in a journal published by the Institute of Management Problems of the Russian Academy of Sciences, and the author is an employee of one of the leading technical universities (MSTU). Nevertheless, a consistent presentation of approaches to the design of technical means is of some interest.
The described system design scheme consists of four stages of setting the problem of creating a new technical tool, exploratory design, conceptual design and engineering design.
At the stage of setting the task of creating a new technical tool, based on an understanding and in-depth analysis of the problem of the emergence of an urgent need, a system model of the new product is formed, describing its connections and relationships with the external environment (Fig. 42).
Consideration of this model allows us to formulate the general task of creating a new technical tool - to formulate its service purpose, determine the restrictions and boundary conditions for the implementation of the work function, evaluation criteria, etc. When analyzing a problem for novelty and technical feasibility, the ways of further solving it are determined: using an existing technical solution, designing a new technical tool, or re-examining the problem with the formulation of currently realistic problems. This stage should answer the questions: is a new technical tool needed and what problems should it solve?
If these issues are resolved positively, a task is drawn up in which the general task of creating a new product is finally formulated, which is the basis for completing the stages of the design and construction process.
Rice. 42. Scheme of system design of technical means and systems:
1 – problem statement
Rice. 43. Scheme of system design of technical means and systems:
2 – exploratory design
Rice. 44. Scheme of system design of technical means and systems:
3 – conceptual design
Rice. 45. Scheme of system design of technical means and systems:
4 – engineering design
The conceptual design stage resolves the issue of technical implementation of the concept of the future design (Fig. 44). The development and analysis of various options for fundamental solutions (functional, layout, kinematic and other diagrams) provides a design concept. At this stage, an economic assessment of the selected options is carried out. The result of the conceptual design stage should be a formalized technical proposal, which should determine the design concept of the future technical device and the technical and economic feasibility of its creation.
At the engineering design stage (Fig. 45), options for the most important elements of a technical device (ETS) are developed, which are analyzed and refined (draft design). Then technical and detailed design is carried out, which gives a complete and final idea of the structure and functioning of the future product, and provides for detailed design by developing drawings for each manufactured element. The scope of the design documentation set should answer the questions - what the future technical device should actually be like, how it works, how to repair it, transport it, etc.
The diagrams also show the elements of the necessary information support for the design and construction process. They are catalogs of known technical solutions of technical means and their elements (K.01), reference books on physical effects, methods and methods of converting matter, energy and information (K.02 and K.03), collections of proven rules for the synthesis of technical solutions for technical means of various types (K.05), methods for analyzing options for technical solutions (K.06) and decision-making methods (K.07) at different stages of design, a description of the recommended rules for calculating technical and economic indicators (TEI) of new technical means and their elements (K.04). Documentation must be completed in accordance with the requirements of ESKD and ESTD.
It should be noted that in Fig. 44 the development of basic structural diagrams precedes the calculation of technical and economic indicators. In this sequence, the calculation of technical and economic indicators essentially turns into an economic justification for already adopted technical decisions. In fact, the development of circuits itself should be carried out in conjunction with TEP calculations. Otherwise, for example, it is not clear how to take into account reliability requirements. By the way, this parameter most clearly characterizes the technical and economic unity of development. The author repeatedly answered his question “What reliability should the development ensure?” I heard the answer “The higher the better.” And to the next question: “Why, in this case, don’t you use tenfold redundancy and make all the contacts from gold?” the answer followed: “It’s expensive,” after which the respondent himself came to the elementary truth about the inseparability of technical and economic design. What is known to a qualified engineer sometimes gives rise to strange interpretations by serious authors. Thus, in the work, the reliability of the system is classified as a qualitative criterion, as opposed to such quantitative criteria, in the opinion of the authors, as measurement error, weight and size characteristics, labor intensity of development, etc. It is known that any R&D report contains a calculation of the overall reliability of the system, no matter how complex it is. These indicators are necessarily included in the technical specifications for the system.
In recent years, issues of combinatorial system design have been widely studied.
The article alone provides a bibliographic list of 52 titles. The author believes that “the design of complex solutions in many applications is now based on the selection of local design options and their composition into the resulting system.” The concept of a decomposed system (consisting of parts for which alternative design options exist) is introduced. The approach to designing decomposable systems includes the following stages:
– setting requirements for the system and its components;
– formation of the system structure;
– generation of design alternatives for components;
– evaluation and ranking of the latter;
– composition of components;
– analysis of components and their improvement.
Basic assumptions in this case:
– the designed system has a hierarchical tree structure;
– multi-criteria characteristics of the quality of parts and their compatibility can be displayed on certain ordinal agreed upon scales.
These assumptions and approaches proceed from the fact that the effectiveness of a system is one or another combination of the qualities of its components, which in the general case is far from true.
When creating a system, a fundamentally new property arises and it is this that is the essence of the system’s effectiveness. If two metal sheets are connected by bolts and nuts, this does not mean that the quality of this system is the sum of the qualities of the sheets, nuts and bolts. When connected, some new quality appeared (for example, a box-shaped design, which is what the consumer needs). There is nothing fundamentally new in using existing components, especially standard ones, it is just a normal design method that in itself does not solve any previously noted problems.
Since reengineering of information systems is mentioned as one of the examples of the application of combinatorial systems design, this example of system design should be considered in more detail. The material from the works was used as the basis for the consideration. These works define the principles and methods of a new system design (NSD) of an information system (IS) based on new information technologies.
In many new methods, project plans of development or consulting firms, BPR (or BPR+) procedures include a large number of similar elements.
2. The execution of work in the general case is aimed at the formation of an effective and beneficial state of the IS “for today” with planning of transitions to the next, largely unknown today states of the IS “for tomorrow” (in contrast to planning the IS as some result, and therefore - receiving IP tomorrow in the form of “as it should” or “as it should be”, but from the point of view of “yesterday”).
3. Based on the principles of NSP, without separating business reengineering and aspects of labor psychology from IS design, a list of works is given indicating the types of instrumental components and IT methods used.
4. The list, and most importantly the substantive scope of work and methods, is not exhaustive. It is assumed that there will be additions (primarily in comparison with the design work described in foreign methods), which should be used to take into account the position of the enterprise in the domestic market and factors of national, professional and corporate culture.
5. The proposed description gives only a partial idea of the IT methods used in NSP, since it represents the multidimensional structure of NSP in one context.
Other dimensions of NSP are characterized by a description of new architectural aspects of information systems or new approaches to the design of corporate databases (see, for example).
As indicated, work in the NSP is used in a sequence that is adapted to the conditions of a particular enterprise and IP project. In accordance with this, Fig. 46 illustrates the NSP work below in the form of a “daisy” model.
List of main NSP works and methods used in them:
2) 1) regulations of the enterprise. enterprise and critical factors for its success. A conclusion is made about the technological, market and social trends and capabilities of the enterprise, the provisions of a new business architecture or, in the case of more radical reengineering, the provisions of a new business platform are formulated (see Henderson model).
Forecast functions in analytical marketing systems, precedent databases, lines of open market information, information about the most successful competitors, etc. are used.
3) Analysis of enterprise risk factors in relation to the implementation of business reengineering programs in the personnel aspect (for strict BPR, total reengineering, structural reorganization, etc.) and the ability to manage these factors.
Methods of socio-psychological examinations are used, the possibility of restructuring personnel attitudes is assessed, personnel training is planned, starting with the management of the enterprise, and the sequence of other steps to prepare personnel for reengineering is modeled.
4) Inventory and assessment of the state of the enterprise's IP: on applied application systems, information classification and coding systems, information composition of databases, decision support methods, the use of local and global network technologies, the composition of the computer park, open architecture and other indicators of the quality of applied IT. In addition, the useful result that each subsystem (automated task, function) contributes to the activities of the enterprise is assessed.
Information and functional systems modeling tools are used (separate tools for describing IT models, CASE systems, DD/D systems, automated thesaurus systems, local computer network modeling systems, etc.), logical rules for classifying concepts, well-known classification and coding systems, information about standards in the field of IT, industrial technologies, which serve as typical and promising representatives of IT in their classes, is used. Quantitative cost estimates of the efficiency of using each subsystem are used (if it is impossible to obtain them, estimates in natural units or qualitative).
5) Detailed inspection of the enterprise(or its parts) and building models of the existing structure of the organization, procedures and performance indicators (the current state of the organizational structure, regulatory documents of the enterprise, performance indicators of departments and the enterprise as a whole), analysis of documents and regulations used in production processes. The useful result that each automated task and set of functions brings to the enterprise’s activities is assessed.
CASE systems and separate special modeling tools are used: tools for an enlarged formal description of an object (for example, a description of the hierarchy of functions and departments), declarative detailed functional models of business procedures, simulation models in terms of queuing, dynamic models on Petri nets, declarative descriptions of information elements and data structures that make up data streams; a thesaurus of concepts that make up an enterprise-specific conceptual model and define professional jargon is built (or supplemented), active conceptual models are built based on frame representations, etc. Quantitative cost estimates of the effectiveness of automation of tasks (sets of functions) are used; if it is impossible to obtain them, estimates in natural terms are used units or quality.
6) End-to-end analysis and synthesis of new business processes: their contribution to production activities is determined and optimized, primarily in the form of final results and performance indicators.
Methods of functional and organizational design are used: isolating the main or defining new key functional roles of workers with their focus on the results of business processes as a whole, designing the amount of power and resources necessary for these workers to perform all functions in the process; designing new organizational structures and processes, planning transformations of existing processes and the existing organizational structure to strengthen the functional roles of employees in business processes and minimize the number of decision-making employees; introducing measurability into business processes, allowing us to know the state of affairs at every moment of time, expressed in monetary units, percentage growth, forecast of completion time or deviation from planned indicators, etc.
Target models of the enterprise are built (subsequently reconstructed): conceptual, organizational, informational, functional, territorial, etc., while using: software tools (components of CASE systems, individual programs) for modeling and assessing business processes, using methods of formalized static description , functional-cost business analysis (ABC, “activity-based costing”), dynamic modeling (CP models, models based on the JPSS language, etc.); CASE systems for recording decisions made in the form of new functional, informational, object-oriented and other models.
7) Introduction of the necessary elements of a marketing organization firm as a producer of market goods (services).
Information and analytical systems are developed or purchased to support the implementation of marketing expertise in the product life cycle, systems for supporting data warehouses (Data WareHouse - DWH) and operational analytical processing (OLAP) are used.
8) Designing a reduced number hierarchical levels of management and their support using: socio-psychological methods for arranging new structures and relationships (special trainings, monitoring relationships, adjusting the types and forms of motivation); means of automated support for group work in new conditions: workflow tools, group development systems, parallel design, etc.; Database of templates for working documents, standards, constant monitoring of the real current situation with the resources available to the employee;
9) corporate mail, teleconferences and video conferences connected to them, with databases and workflow tools for planning and execution of orders, including for the transition from managing directly subordinates in a ratio of 1:7 to a ratio of 1:15 or more. Creation and information support of autonomous and mobile business units
and workers, providing “field” engineers and repairmen, rescue teams or ambulances with constant communication with the corporate IS.
10) Various IT technical means are used, for example: laptops with modem (including radio) connections and communication programs that have a user-friendly interface that is simple for non-programmers; the use of replication (replication) of documents and databases, asynchronous modes of working with information systems in three-tier architectures “client - application server - database server”, etc. performance of maximum functions in business processes by the employee receiving the final result.
Technical methods and tools of new IT are also used: tools
access to all necessary data in the modes of using distributed databases, data replication tools, event management in data and transaction processing processes; concept and software tools of DWH, OLAP tools, rapid application development (RAD) for creating an “executive information system” (EIS), creation of decision support tools (DSS) based on DWH, OLAP and EIS; the use of DSS tools based on logical inference methods, neural networks and neurocomputers, precedent analysis, etc.; offering a single user interface for working with different components of data and applications, using in this interface tools that increase the ease of searching for information and accessing specific application functions, for example, interfaces of geoinformation systems, natural language, speech input.
11) Development of the concept and structure of a corporate database for a new IS, implementation of the database structure and management of its development.
The following are used: methods of component design of subject databases for both operational and historical databases of data warehouses, document archives, geoinformation data, etc.; development of procedures for component changes in the corporate database when business procedures, types of activities, applications used and geographic location of the enterprise change; constant updating of the conceptual model of the enterprise to take into account new concepts that arise both when replacing application components with functionally similar ones, and when changing the types of activities of the enterprise; connecting the corporate database to the channels of the global information highway, granting rights to include information from it in the database to employees of all hierarchical levels; dynamic administration of fragments of a distributed corporate database when their logical structure, frequency of use and location change.
12) Development of the concept and structure of the internal corporate network.
Technical standards of open systems are used (for example, Internet and WWW technologies for building a corporate network similar to the Internet).
A minimum of operational reservation of network resources is laid down to remove restrictions on its development and reconfiguration.
13) Application system development as a set of components based on a common conceptual model and available for refurbishment by including new ones, primarily purchased components.
The following are used: DBMS and database models using languages (data models) that meet industrial legal standards for data presentation and processing; tested legal standards of open systems regarding the exchange of requests, data, documents, objects; development of applications based on portable RAD systems (including elements of object-oriented programming).
In the future, it is possible to use new standards in the field
object-oriented environments.
14) Information and functional support for business globalization.
The enterprise is connected to global communications. Used: global digital (computer) networks and their services, for example, the Internet, building exits from corporate networks to the Internet; tools and tools for working in global networks: tools for hypertext viewing of databases of WWW (World Wide Web) servers, applications for remote financial settlements, etc.; regimes and standards of the information superhighway for widespread access to information of any kind - from price lists and standard conditions of possible business partners to dynamic flows of market and general reference information; refusal to embed restrictions on the capabilities of computer communication in the hardware architecture, communication channel architecture, software or in a dedicated center for remote administration of a distributed corporate network; means of protecting confidential data that do not limit the ability of subscribers to freely contact the desired address (except for special cases in which the creation of “computer islands” is justified);
15) operating modes of communications and information systems in 24*365 mode. Construction of a support and document management system
as part of a system for implementing a current set of business procedures.
For this purpose, the means of corporate and global e-mail, electronic document archives, instrumental and infrastructure systems of the groupware and workflow classes are used, writing and administering specific regulations (business procedures) covering enterprise employees, providing each employee with dynamic reports on the situation with the implementation of regulated work, achieved values of estimated indicators, etc.
16) Retraining and advanced training of personnel.
Providing employees with maximum basic information as a basis for making independent decisions. Forming their knowledge and skills using all IT tools in training programs that reduce subsequent employee overhead costs for implementing business procedures to a minimum, for example: multimedia training computer programs with dynamic scenarios simulating various situations; context clues, hypertext help guides, context-sensitive tutorials; use of workflow tools for supplying and training with current business procedures, etc.
17) Planning the set and sequence of transition steps from the current state of the enterprise business architecture to the new one (with an assessment of the cost of transition).
Planning such steps in terms of personnel training, in terms of resource and project management, in terms of financial accounting and analysis, etc., including using project management software systems (construction and dynamic recalculation of linear and network schedules, resource planning, evaluation project cost).
18) Planning and executing the transition from the current state of the enterprise's IT architecture and its functioning IS to a new one.
For example, in terms of reconstruction of a corporate database and application complexes, the following are used: software systems for managing IS development projects; use of software for the development and implementation of database transfer and reengineering schemes; development of programs for interface use of existing (inherited) or newly integrated components: applications, subject databases and subsystems in a new IS, implementation of technical and semantic aspects of the joint functioning of components, application of known methods and software tools for reengineering existing application programs into a new environment (changing the programming language , interfaces with databases, etc.).
19) Documenting design processes and results and redesign of both business processes and computer IS components.
The following are used: means for issuing reports and certificates of CASE systems and other special modeling programs; developed tools for text and graphics editors (maybe with elements of animation or multimedia) for creating high-quality documentation on business conditions, procedures and processes; inclusion of current documents in the corporate network, training programs, contextual help, etc.
20) Creation of external documentation programs for the production and supply of goods and services of the enterprise’s core activities at a competitively high level.
Output streams of information are generated aimed at clients, business partners, government circles, and the general public, for the formation of which the following are used: the editors described above, computer layout systems, animation and multimedia for creating interactive reference applications, video discs, catalogs, price lists, etc.; object programming systems that provide the recipient with “remote interpretation” of the content of the above interactive help applications, video disks, catalogs, price lists, etc.; WWW server programming, other information superhighway opportunities for posting your external documentation of your core business.
21) Providing prompt feedback from potential consumers, commercial clients, business partners, etc.
Methods and systems of marketing monitoring and analysis are used to obtain primary and secondary information. IT methods and tools are used to: create applications that provide feedback to clients and consumers through global network systems; ensuring round-the-clock functioning of the enterprise’s information system for the purpose of informing, receiving and fulfilling customer requests and claims; administration of operational databases for this purpose with non-stop functioning of OLTP.
NSP does not impose on the customer and developer a common standard scheme for the mandatory implementation of a full cycle of work on BPR, or total reengineering, or anything similar. Taking into account the real situation with IP, the real needs of the enterprise and its real readiness for BPR, the work that this enterprise can master is carried out.
However, in general, the NSP examines the need and possibility of performing all types of work potentially necessary for the enterprise. Because of this, the construction of flexible organizational design schemes is proposed, which consists in the construction and dynamic refinement of an adaptive organizational scheme focused on the specifics of a particular enterprise, its internal state and external position.
Adaptability is also manifested in the fact that a scheme is constructed, according to which, in the process of performing work, the design option and future information system for which the enterprise is ready or can be prepared in an acceptable time is selected.
The initial ones are analytical expert procedures that determine the state of the enterprise and its need for BPR and readiness for it.
Example of an adaptive scheme
1) Below is a simplified and truncated example of a variant of such an organizational chart. Situational and diagnostic analysis
position of the enterprise.
2) (Situational analysis of the external position of the enterprise and the presence of internal requirements for conducting BPR.)
Does the enterprise require BPR? Yes
– carry out an assessment of the enterprise’s readiness for BРR. No -
3) plan the feasibility study and pre-feasibility study stages for an improved waterfall scheme. Performance
4) (sociopsychological and financial) examination of the enterprise’s readiness for BPR.
Is the enterprise ready for BPR? Yes -
carry out the stages of IS development according to the BPR scheme adapted to the given enterprise. No
5) – develop a report on the critical factors of the enterprise and complete the work (or plan with the management of the enterprise the procedures for preparing the enterprise to a state in which it is possible to begin work on BPR). Development of a critical
6) factors of the enterprise. Execute as the first step
BРR mobilization stage (a BРR team is formed, resources are planned, orders are issued).
7) Upon successful completion, proceed to the strategic analysis stage. Strategic analysis,
(The current external state of the enterprise, its declared and other goals, the state of organizational structures, business procedures, databases, etc. are documented, and basic general recommendations are developed.)
8) Execution for existing organizational structures, business processes and IS examinations such as “review” and “inventory” at an enlarged level.
9) Implementation of the strategic stage planning.
(The concept of strategic planning of BPR and IS is being developed).
A synthesis of extremely generalized basic models of BPR and IS is carried out - perhaps on the basis of additional survey procedures: conceptual, functional, informational, organizational, recommendations and plans are developed for the detailed design of business procedures and IS, including general architecture, organizational, functional, informational, hardware, network, system-wide software, application software, etc. parts.)
10) Complete the first development cycle priority components of the IP (maybe in the style of prototyping or the spiral method).
10.1) Conduct clarifying detailed information and functional analysis and synthesis for the component being prototyped.
10.2) Develop a prototype (design, programs, database, documentation) of the component.
10.3) Perform expert assessment of the progress of the project.
11) Develop transition procedures from the existing state to the new one - in the areas of system support.
12) Perform receiving procedures quality IP component.
13) Carry out commissioning IS component with the implementation of procedures for the enterprise’s transition to a new IS state.
(Personnel training, integration of the component with existing ones, etc.)
14) Repeat, including– in parallel, stages 10 – 13 a planned but regulated number of times, if necessary, perform additional examinations included in clauses 2, 3, 6, 8 and 10.3.
The principles of NSP involve the use of many new design methods and a new look at the application of classical approaches. We need to have an answer to the question: how radically should system design really be changed? It is advisable to maintain a healthy immunity to revolutions (see). This means relying on a combination of two rules: not to succumb recklessly to the “hot” slogans of fashion trends and, at the same time, not to miss the real changes that should be included in design practice.
Such a detailed presentation of approaches to the IS design methodology in relation to reengineering tasks is given here, since it best demonstrates what a real systems approach in R&D is, what the role of the conceptual design stage is, how we must not forget for a minute about the economic side of the project and at the same time This is a clear illustration of the strategic role of R&D not only for a specific enterprise (indeed, the greater the number of partner enterprises that are subjected to such reengineering, the more efficiently each of them will work). And lastly: the complexity, multi-stage, high cost of creating a reengineering IS is really justified if a business architecture solution is designed that will provide a “breakthrough,” that is, an organization of business processes that in reality can provide a radical increase in efficiency by 100% or more .
It is obvious that the information systems of “cyber corporations” are far from the most voluminous and strategically significant object of R&D. An example is the so-called complex special-purpose systems. They are understood as systems whose operational goals are of national importance. These include, for example, systems for space exploration, development of the transport network, energy, national security, etc.
Their main features:
– the goals of their functioning are formulated based on state interests;
– achievement of goals is ensured not only by the presence of the necessary systems, but also by the creation and development of the necessary organizational structure with the inclusion of government bodies in it;
– the basis for the implementation of such systems is centralized budget financing;
– management of their creation and development is a state monopoly and is carried out by special state bodies.
| Previous |
GOST R 15.201-2000
Group T52
STATE STANDARD OF THE RUSSIAN FEDERATION
System for developing and launching products
PRODUCTS FOR PRODUCTION AND TECHNICAL PURPOSE
The procedure for developing and putting products into production
System of product development and launching into manufacture. Products of industrial and technical design. Procedure of product development and launching into manufacture
Text Comparison of GOST R 15.201-2000 with GOST R 15.301-2016, see the link.
- Database manufacturer's note.
____________________________________________________________________
OKS 01.040.01
01.110
OKSTU 0015
Date of introduction 2001-01-01
Preface
1 DEVELOPED by the All-Russian Scientific Research Institute of Standardization (VNIIstandart) of the State Standard of Russia
INTRODUCED by the Scientific and Technical Directorate of the State Standard of Russia
2 ADOPTED AND ENTERED INTO EFFECT by Resolution of the State Standard of Russia of October 17, 2000 N 263-st
3 INTRODUCED FOR THE FIRST TIME
4 REPUBLICATION. August 2010
1 area of use
1 area of use
This standard applies to national economic products for industrial and technical purposes (hereinafter referred to as products) and establishes the procedure for their development and production.
The standard establishes the basic provisions for the development of technical specifications (TOR), design and technological documentation, acceptance of development results, preparation and development of production, testing of prototypes of products and products manufactured during the development of production, as well as confirmation of their compliance with mandatory requirements. If necessary, the requirements of this standard may be specified in other standards and methodological documents of different scopes.
The standard does not apply to civil vessels.
2 Normative references
This standard uses references to the following standards:
GOST 2.124-85 Unified system of design documentation. Procedure for using purchased products
GOST 15.311-90 System for development and production of products. Launching production of products according to technical documentation of foreign companies
GOST R 15.000-94 System for developing and putting products into production. Basic provisions
GOST R 15.011-96 System for developing and putting products into production. Patent research. Contents and procedure
GOST R ISO 9001-96 * Quality systems. Quality assurance model for design, development, production, installation and maintenance
_________________
* Valid until December 15, 2003.
GOST ISO 9001-2011
GOST R ISO 9001-2001 * Quality management systems. Requirements
________________
* Since November 13, 2009, GOST R ISO 9001-2008 has been in force.
GOST ISO 9001-2011 is in force on the territory of the Russian Federation, hereinafter in the text
3 Definitions
3.1 This standard uses terms with corresponding definitions according to, as well as those given below:
3.1.1 national economic products: Products developed and manufactured to meet the needs of the national economy, population and export.
3.1.2 products for industrial and technical purposes: Products intended for use as means of industrial and agricultural production.
3.1.3 mandatory requirements: Requirements established by state standards and other regulatory documents based on the legislation of the Russian Federation to ensure the safety of products, works and services for the environment, life, health and property, technical and information compatibility, interchangeability of products, unity of control methods and unity of labeling, as well as others mandatory requirements established by the legislation of the Russian Federation.
3.1.4 competitive basis: The principle of distributing orders for the development (production) of products, which consists in using competitive selection based on the results of bidding (competitions).
3.1.5 work organization model: According to GOST R 15.000.
3.1.6 work organization module: According to GOST R 15.000.
3.1.7 state supervisory authorities: Federal executive authorities supervising the implementation of mandatory requirements.
4 General provisions
4.1 This standard considers the following stages and types of work in the product life cycle, established by GOST R 15.000:
- stage "Development", type of work "Experimental design work (R&D) for product development";
- part of the “Production” stage, type of work “Putting into production”.
4.2 Certain types of work on the development and production of products, characterized by target orientation, organizational completeness, a certain sequential order of execution and planning, the presence of certain performers, are combined into work organization modules that meet the requirements of GOST R 15.000 in composition and content.
4.3 Depending on the availability of targeted product development programs, the presence or absence of a customer, the nature of the relationship between business entities, the development and production of products is carried out according to the following work organization models:
1 - creation of products under state and municipal orders, as well as other orders financed from the federal budget and budgets of constituent entities of the Russian Federation (hereinafter referred to as government orders);
2 - creation of products ordered by a specific consumer (interested organizations, societies, commercial structures);
3 - proactive product development without a specific customer at the commercial risk of the developer and manufacturer.
The work organization model is chosen based on the ability to ensure the required product quality, compliance with mandatory requirements and product competitiveness during their implementation.
4.4 Government orders are placed on a competitive basis, taking into account data on the qualifications of the contractor, in accordance with the current procedure for organizing the procurement of goods, works and services for government needs.
4.5 When creating products under government orders and orders of a specific consumer, an agreement (contract) for the work performed is concluded in the prescribed manner, and technical specifications for the work performed are developed.
If necessary, the contract and (or) technical specifications indicate regulatory documents regulating the procedure for performing work, and documents defining mandatory rules and requirements for products.
If necessary, the agreement (contract) specifies a set of work organization modules that ensure the fulfillment and confirmation of mandatory requirements, as well as the requirements established by laws and regulations of state supervisory authorities.
4.6 Based on the initial requirements of the customer (if any), the product developer carries out the necessary research, development and technological work, paying special attention to ensuring the following requirements:
- safety, health and environmental protection (including their preservation during product operation);
- resource saving;
- values of indicators established for the conditions of use of the product that determine its technical level;
- resistance to external influences;
- interchangeability and compatibility of components and products as a whole.
4.7 The decision to develop products on an initiative basis is made taking into account the conditions of the sales market.
4.8 Development and production of products generally provides for:
1) development of technical specifications for development work (R&D);
2) carrying out development work, including:
- development of technical documentation [design (CD) and technological (TD)],
- production of prototypes,
- testing of prototypes,
- acceptance of R&D results;
3) production launch, including:
- production preparation,
- development of production:
production of installation series,
qualification tests.
The stages of a specific design and development work (a component of the design and development work), as well as the procedure for their acceptance, must be defined in the terms of reference for the design and development work (a component of the design and development work) and the agreement (contract) for its implementation.
4.9 At all stages of R&D (an integral part of R&D) and when placing products into production, performers ensure compliance with mandatory requirements.
The achieved indicators and their compliance with the requirements of the technical specifications for R&D (an integral part of R&D) are assessed upon acceptance of the stages and are reflected in the test reports (acts) of prototypes of products and acceptance certificates for the stages of R&D and R&D as a whole.
4.10 The relationship between the developer (manufacturer) and state supervisory authorities is determined by the current legislation.
4.11 Documents confirming compliance with mandatory requirements are submitted to state supervisory authorities in accordance with their rules.
The composition of these documents is established by the relevant state supervision body.
4.12 Products of intellectual labor obtained in the process of creating and putting products into production and being objects of intellectual property protection are used in the manner established by the legislation of the Russian Federation.
5 Development of technical specifications for R&D
5.1 The basis for performing the design and development work is the technical specifications approved by the customer and the agreement (contract) with him. Another document containing necessary and sufficient requirements for product development and mutually recognized by the customer and developer can be used as technical specifications.
Requirements for the analysis of an agreement (contract) are given in 4.3 GOST R ISO 9001.
In the case of proactive product development, the basis for performing R&D is the technical specification approved by the management of the developer enterprise (or a document replacing it), based on the results of product market research, as well as patent research in accordance with GOST R 15.011.
When developing technical specifications, the developer takes into account information about similar products contained in databases (all-Russian and regional) created in the State Standard of Russia on the basis of product catalog sheets.
5.2 It is recommended that the technical specifications indicate technical and economic requirements for products that determine their consumer properties and effectiveness of use, a list of documents requiring joint consideration, and the procedure for delivery and acceptance of development results.
The technical specifications provide for the implementation of all mandatory requirements that apply to these products.
The technical specifications indicate the form of confirmation of product compliance with mandatory requirements provided for by law.
It is recommended that the technical specifications take into account the interests of all possible consumers.
The specific content of the technical specification is determined by the customer and the developer, and in case of proactive development - by the developer.
It is not allowed to include in the technical specifications requirements that contradict the laws of the Russian Federation and mandatory requirements.
5.3 It is recommended that the TOR include the following provisions:
- forecast of the development of requirements for this product for the expected period of its release;
- recommended stages of product modernization taking into account the forecast for the development of requirements;
- compliance with the requirements of the countries of intended export, taking into account the forecast for the development of these requirements;
- maintainability characteristics;
Possibility of replacing spare parts without the use of industrial technology;
- accessibility and safety of effective use of products by disabled people and elderly citizens (for relevant products provided for by the legislation of the Russian Federation).
5.4 Technical specifications are developed and approved in the manner established by the customer and developer.
Other interested organizations (enterprises) may be involved in the development of technical specifications: manufacturer, trade (intermediary) organization, insurance organization, design organization, installation organization, etc.
5.5 To confirm individual requirements for products, including safety, health and environmental requirements, as well as assessing the technical level of products, the technical specifications can be sent by the developer or customer for examination (conclusion) to third-party organizations. The decision on the conclusions received is made by the developer and the customer before approval of the technical specifications.
5.6 At any stage of product development, with the consent of the customer and developer, changes and additions may be made to the technical specifications or a document replacing it that do not violate the conditions for fulfilling the mandatory requirements.
6 Development of documentation, production and testing of prototypes of products
6.1 The development of design and technological, and, if necessary, program documentation for products is carried out according to the rules established respectively by the standards of the Unified System of Design Documentation (USD), the Unified System of Technological Documentation (ESTD) and the Unified System of Program Documentation (USPD).
General requirements for design management - according to 4.4 GOST R ISO 9001.
The rules for the development of technical documentation for materials and substances are established by the developer, taking into account current state standards, the specifics of the product and the organization of its production.
6.2 In the process of developing documentation for the selection and testing of new technical solutions that ensure the achievement of the basic consumer properties of products, laboratory research, bench and other tests, as well as development tests of experimental and pre-production samples of products can be carried out under conditions simulating real operating (consumption) conditions. , while taking into account the patent and legal aspects of the economic use of these technical solutions.
For certain types of products or their components, tests of prototypes can be carried out under operating conditions (including at enterprises that are consumers of the products).
The scope and content of tests necessary to prevent the production of unproven products that do not comply with the specifications are determined by the developer, taking into account the novelty, complexity, features of production and use of the product, and customer requirements. In this case, tests must be carried out to ensure compliance with all mandatory requirements.
The need to develop, manufacture and test prototypes (models), experimental and pre-production samples of products, their list and quantity are determined in the technical specifications and the agreement (contract) for R&D (an integral part of R&D). This does not exclude the possibility of such work being carried out by the developer if their need is revealed later, while appropriate changes are made to the technical specifications and the agreement (contract), with the consent of the customer.
Requirements for control and testing procedures are established in accordance with 4.10-4.12 GOST R ISO 9001.
6.3 For repairable products, it is advisable in the agreement (contract) and technical specifications for development work to provide for the development of repair documentation intended for preparation of production, repair and control of products after repair.
6.4 To confirm the compliance of the developed technical documentation with the initial requirements and to select the best solution (if options are available), prototypes (pilot batches) of products are produced if the products are intended for serial production (with an expected constant need). For non-serial production of products, head samples are also made.
When creating a single product, prototype product samples, as a rule, are subject to sale to the customer (unless otherwise specified in the contract and technical specifications for development work).
6.5 Testing of prototype products
6.5.1 To assess and control the quality of the results obtained at certain stages of the development work (an integral part of the development work), prototypes (pilot batch) of products (head samples* of products) are subjected to control tests in the following categories:
- preliminary tests carried out for the purpose of preliminary assessment of the compliance of a prototype product with the requirements of the technical specifications, as well as to determine the readiness of the prototype for acceptance testing;
- acceptance tests carried out with the aim of assessing all product characteristics determined by the technical specifications, checking and confirming the compliance of a prototype product with the requirements of the technical specifications in conditions as close as possible to the conditions of actual operation (application, use) of the product, as well as for making decisions on the possibility of industrial production and sale products.
* Lead product samples are development objects that simultaneously act as the first samples of non-serial and small-scale products sold to the customer on special delivery terms.
6.5.2 If products are subject to mandatory requirements that are subsequently subject to mandatory confirmation of conformity (certification), the results of product acceptance tests in terms of mandatory requirements, carried out in laboratories (centers) accredited in the prescribed manner, can be used to obtain confirmation of conformity according to the established requirements. rules.
The place for testing prototypes of products is determined by the developer together with the manufacturer of serial products (if the functions of the developer and manufacturer are performed by different enterprises and there are no specific test conditions established by state supervisory authorities).
6.5.3 When creating products according to work organization model 1 (4.3), state acceptance tests are carried out; for models 2 and 3 - acceptance tests are carried out with the participation of the relevant state supervisory authorities and other interested organizations.
For component parts of products developed according to the technical specifications of the lead R&D contractor, independent acceptance tests are carried out with the participation of interested organizations. The ultimate goal of these tests is to assess compliance with the requirements of the technical specifications for which they are developed, and to determine the possibility of installing components in a prototype product intended for its preliminary testing.
6.5.4 Lead samples of non-serial products are subjected to acceptance tests in order to resolve the issue of the admissibility of their use for their intended purpose, and for repeating non-serial products - and to resolve the issue of the advisability of putting the product into non-serial production.
6.5.5 Lead product samples are tested according to the rules of this standard, taking into account the features established for it in the relevant regulatory documents.
6.5.6 Preliminary testing of products is organized by the R&D contractor.
State acceptance tests of products (model 1 to 4.3) are organized by the state customer, unless otherwise specified in the agreement (contract).
Acceptance tests of products according to work organization models 2 and 3 to 4.3 with the participation of interested bodies and organizations specified in 6.5.3 are organized by the developer.
Acceptance tests of prototypes of product components (developed according to the technical specifications of the lead R&D contractor) with the participation of interested organizations are organized by the lead developer for the creation of the product. In other cases, testing of prototypes of product components is organized by their developer.
If R&D is carried out during proactive development (without a specific customer), acceptance tests are organized by the developer.
The organizer is responsible for conducting the tests.
6.5.7 Preliminary and acceptance tests are carried out according to the relevant programs and test methods (hereinafter referred to as test programs), developed and approved by the party responsible for conducting these tests.
Test programs are developed based on the requirements of technical specifications, design documentation using, if necessary, standard programs, standard (standardized) test methods and other regulatory documents regarding the organization and conduct of tests.
The test program includes:
test object,
purpose of testing,
scope of tests
conditions and procedure for testing,
logistics support for testing,
metrological testing support,
test reporting.
The test programs include lists of specific checks (tasks to be solved, assessments) that should be carried out during tests to confirm compliance with the requirements of the technical specifications with links to the relevant test methods. The program and methodology for acceptance testing of prototype products must, in addition, contain a quality check of the working design and operational documentation (including draft technical conditions for industrial production of products) to make a decision on the suitability of the documentation for industrial production.
The test procedure includes:
assessed characteristics (properties, indicators) of products;
conditions and procedure for testing;
methods of processing, analysis and evaluation of test results;
the testing, control and measurement equipment used;
reporting.
Test methods used to determine product compliance with mandatory requirements, if they are not standard standardized methods, must be certified in the prescribed manner and agreed upon with the relevant state supervisory authorities.
6.5.8 Tests are carried out after checking the readiness of testing sites (laboratories, testing centers, etc.) to meet technical requirements, safety requirements and after appointing responsible specialists for all work during the preparation and conduct of tests, assessing product characteristics with established measurement accuracy , as well as recording their results.
6.5.9 To conduct acceptance tests, as a rule, a commission is appointed that monitors the completeness, reliability and objectivity of the test results, as well as the completeness of information, compliance with test deadlines and documentation of their results. With the consent of the interested organizations, it is allowed to conduct tests without appointing a commission, but with the assignment of its functions and responsibilities to the relevant services of the organization conducting the tests, which must be reflected in the technical specifications and (or) agreement (contract) for the implementation of the development work.
6.5.10 By the start of the tests, preparation measures must be completed, including:
- availability, suitability and readiness at the test site of logistics and metrological support facilities that guarantee the creation of conditions and test regimes corresponding to those specified in the test program;
- training and, if necessary, certification of personnel admitted to testing;
- appointment of a commission or relevant organizations (enterprises) and their services (if a commission is not appointed);
- timely submission to the testing site of a prototype product with a set of design, regulatory, reference and other documentation provided for by the test program.
6.5.11 During the testing process, the progress and results of the tests are documented in the form and within the time limits provided for in the test program.
In justified cases, tests may be interrupted or terminated, which is documented.
6.5.12 The specified and actual data obtained during testing are reflected in the protocol(s).
6.5.13 In test reports, texts relating to verification of mandatory requirements should be formatted in accordance with the requirements of the conformity assessment rules.
6.5.14 Tests are considered completed if their results are documented in an act confirming the implementation of the test program and containing an assessment of the test results with specific, precise wording reflecting the compliance of the tested prototype product with the requirements of the technical specifications.
Upon completion of acceptance tests, prototypes or samples of a pilot batch are considered to have fulfilled their functions. Their further use (as units of non-serial products), recycling or destruction is determined by a special decision that complies with current legislation.
6.5.15 During acceptance tests, state supervisory authorities determine the degree of product compliance with mandatory requirements and issue a final conclusion based on the test results, which is reflected in the act or in a separate documented conclusion.
7 Acceptance of product development results
7.1 The results of product development are assessed by an acceptance committee, which includes representatives of the customer, developer and manufacturer. Experts from third-party organizations can participate in the work of the commission, and for products for which mandatory requirements have been established, state supervisory authorities (or the conclusion of these authorities is presented).
If there is a customer, his representative is appointed chairman of the commission. The composition of the commission is formed and approved by the customer or, with the customer’s consent, by the developer.
7.2 The acceptance committee conducts acceptance tests of prototypes (pilot batches) of products in accordance with 6.5.
At the request of the customer or in accordance with the rules for assessing compliance with mandatory requirements, testing can be entrusted to a specialized testing organization (testing center) or to the manufacturer, if this is stipulated in the terms of reference for the implementation of R&D (agreement, contract).
The manufacturer and state supervisory authorities have the right to take part in acceptance tests, regardless of the place where they are carried out, who must be informed about the upcoming tests one month before their start.
All state supervisory authorities determined by current legislation for this product either participate in acceptance tests or issue conclusions based on test results.
In the absence of a representative of the state supervisory authority or its conclusion, it is considered that the state supervisory authority agrees to accept the development or is not interested in it.
7.3 The developer submits to the acceptance committee the technical specifications for the implementation of the development work, draft technical conditions (TS) or standard technical conditions (if their development is envisaged), design and (or) technological documents requiring joint consideration, a report on patent research, other technical documents and materials, required by law, confirming the compliance of the developed product with the specifications and the agreement (contract) and certifying its technical level and competitiveness. The acceptance committee, as a rule, is also presented with prototypes of products, and if their production was not envisaged - a head sample or a single product created as part of the development work.
7.4 Based on the results of acceptance tests and consideration of submitted materials, the commission draws up a report in which it indicates:
1) compliance of samples of developed (manufactured) products with the requirements specified in the technical specifications, admissibility of their production (delivery to the consumer);
2) the results of assessing the technical level and competitiveness of products, including in the patent and legal aspect;
3) results of assessment of the developed technical documentation (including draft technical specifications);
6) comments and suggestions for improving products and documentation (if necessary);
7) other recommendations, comments and suggestions of the acceptance committee.
The acceptance committee report is approved by the customer.
Approval of the acceptance committee's act means the end of development, termination of the technical specifications (if it does not apply to further work), approval of the submitted specifications and technical documentation.
7.5 The acceptance committee’s act, with the consent of the relevant state supervisory authorities, may reflect the requirements of 4.9, 4.10, 5.2, 6.5.15, 7.2, 8.3.
8 Preparation and development of production (putting into production) products
8.1 Preparation and development of production, which are the stages of putting products into production, are carried out in order to ensure the readiness of production for the manufacture and release (delivery) of newly developed (modernized) or previously produced by another enterprise products in a given volume that meets the requirements of design documentation.
8.2 The basis for putting into production is an agreement (contract) concluded with the customer for the purchase from the supplier (manufacturer) of products manufactured within a specified period.
In the absence of a specific customer, the basis is the decision of the supplier’s management at its own commercial risk.
8.3 By the time the product is put into production, the results of acceptance tests must be recognized by state supervisory authorities (6.5.15, 7.2).
8.4 The manufacturer accepts from the product developer:
set of CD and TD letter O or higher;
special means of control and testing;
a prototype product (if necessary) in accordance with the conditions for the use of scientific and technical products specified in the agreement (contract) for development work;
documents on approval of the use of components in accordance with GOST 2.124;
conclusions on the examinations carried out (including metrological, environmental, etc.);
a copy of the acceptance test report;
documents confirming compliance of the developed products with mandatory requirements.
8.5 At the pre-production stage, the manufacturer must carry out work to ensure the technological readiness of the enterprise for the manufacture of products within the terms specified in the contract (agreement) in specified volumes, in accordance with the requirements of the design documentation and the legislation of the Russian Federation, as well as the following main works:
- development of technical documentation (or adjustment of the received technical documentation) for the manufacture of products for delivery, control and testing;
- development of the design for manufacturability taking into account ESTD standards;
- concluding agreements (contracts) with suppliers of components and materials and licensing agreements with copyright holders for the use of industrial and intellectual property;
- preparation and submission of product catalog sheets to the territorial bodies of Gosstandart of Russia in the prescribed manner;
- other jobs.
Preparation of production is considered complete when the manufacturer of the product has received all the necessary documentation, developed (worked out) TD for the manufacture of products, tested and adjusted technological equipment and technological processes, trained personnel involved in the manufacture, testing and control of products, and established readiness for mastering production products.
8.6 At the production development stage the following is performed:
- production of the number of units of product of the installation series (first industrial batch) established by the agreement (contract) or other document in accordance with the requirements of the design documentation (letter O or higher), finalization of the developed technological process for the production of products according to the design documentation (letter O or higher);
- qualification tests;
- further development (if necessary) of the design for manufacturability;
- approval of the design documentation and technical documentation with the assignment of the letter A.
8.7 During the period of launching production of products, the manufacturer (supplier) carries out all the necessary work for subsequent certification of products required by law.
8.8 Production of products based on the technical documentation of foreign companies is carried out in accordance with GOST 15.311, taking into account the requirements of this standard.
8.9 In order to demonstrate the readiness of the enterprise to produce products that meet the requirements of the design documentation, to verify the developed technological process that ensures the stability of product characteristics, as well as to assess the readiness of the enterprise to produce products in the quantity determined by the agreement (contract), qualification tests are carried out.
8.10 Qualification tests are carried out according to a program developed by the manufacturer with the participation of the product developer and agreed with the customer (if any). The program indicates:
- the number of product units subjected to testing and inspection based on their complexity, cost, reliability and other factors necessary for reliable assessments;
- all types of tests corresponding to the periodic tests specified in the technical specifications, as well as other tests and inspections that allow achieving the purpose of qualification tests;
- testing location.
The qualification testing program may not include verification of individual design documentation requirements that cannot change during production launch.
8.11 Qualification tests are organized and carried out by the manufacturer (supplier) of the product. Qualification tests are carried out by a commission consisting of representatives of the manufacturer, product developer, developers and suppliers of components and, if necessary, government supervisory authorities and other interested parties (for example, insurance organizations, public organizations for the protection of consumer rights, etc.).
8.12 The tests are documented in test reports, which reflect the actual data of checks, inspections, controls, measurements and other data, which must be signed by members of the commission and persons participating in a specific type of test.
8.13 The results of qualification tests are considered positive if the product (installation series) has passed the tests on all points of the qualification test program, the technological equipment of production and the stability of the manufacturing process are positively assessed for the possibility of producing in specified volumes of products that comply with design documentation, as well as technical specifications.
Positive results are documented in a document indicating:
- product compliance with mandatory requirements and design documentation, results of consideration of materials submitted to the commission, results of selective control of the technological process of manufacturing (assembling) products (parts, assembly units) at workplaces;
- recommendations for establishing standards for established industrial production (if necessary);
- assessment of the manufacturer’s readiness to produce serial products for the implementation of the agreement (contract) and the readiness of the design documentation, technical documentation for approval in the prescribed manner with the assignment of the letter A;
- recommendations on the possibility of supplying products from those manufactured during the development of production (with mandatory notification of consumers about this and the sale of such products only with their consent and after carrying out acceptance tests in the prescribed manner).
8.14 Delivery of products during the period of mastering its production is allowed if the manufacturer can confirm the compliance of these products with mandatory requirements.
Product units of the installation series are not classified as commercial products, as a result of which the Quality Control Department only carries out their control, and accepts them for delivery only at the request of the consumer.
8.15 If the results of qualification tests are positive, production development is considered completed.
APPENDIX A (for reference). Bibliography
APPENDIX A
(informative)
R 50-605-80-93* System for developing and launching products into production. Terms and Definitions
________________
* The document is the author's work. For more information please follow the link. - Database manufacturer's note.
PR 50-718-94* Rules for filling out and submitting product catalog sheets
________________
* The document is not valid on the territory of the Russian Federation. PR 50-718-99 is valid. - Database manufacturer's note.
Electronic document text
prepared by Kodeks JSC and verified against:
official publication
Development and staging system
products for production:
Collection of national standards. -
M.: Standartinform, 2010
The technical specifications for R&D GOST, issued for development work, is the most important component of the state contract. During its development, GOST and standards as a tool for technical control must be applied by all interested bodies and constituent entities of the Russian Federation involved in the development.
Requirements for the construction, content, presentation and execution of technical specifications
The terms of reference for state development work consist of requirements approved by GOST of the Russian Federation.
OCD includes stages:
- creation and approval of a preliminary design (ED) and/or tactical and technical specifications (TTZ);
- preparation of relevant documents;
- release of a prototype product and testing of the product;
- registration and acceptance of documents for the production of products on a large scale.
The terms of reference are developed on the basis of technical specifications or electronic documentation issued by the customer or his representative. Issued in accordance with GOST of the Russian Federation in A4 format. A separate clause specifies the conditions for maintaining the safety of state secrets relating to the work performed.
Scientific research work (R&D) – These are scientific developments related to searching, conducting research, experiments in order to obtain new knowledge, test hypotheses, establish patterns, and scientific substantiation of projects.
The implementation of research work is regulated by the following regulatory documents: GOST 15.101-98 “Procedure for carrying out research work”, GOST 7.32-2001 “Preparing a report on research work”, STB-1080-2011 “Procedure for performing research, development and experimental technological work on the creation scientific and technical products”, etc. (Appendix 10).
Distinguish fundamental, search and applied Research
Fundamental and exploratory work is, as a rule, not included in the product life cycle, but on their basis ideas are generated that can be transformed into applied research.
Basic Research can be divided into “pure” (free) and targeted.
“Pure” fundamental research– these are studies whose main goal is to discover and understand unknown laws and patterns of nature and society, the causes of phenomena and the discovery of connections between them, as well as to increase the volume of scientific knowledge. In “pure” research there is freedom to choose the field of research and methods of scientific work.
Targeted basic research are aimed at solving specific problems using strictly scientific methods based on available data. They are limited to a certain area of science, and their goal is not only to understand the laws of nature and society, but also to explain phenomena and processes, to more fully understand the object being studied, and to expand human knowledge.
This basic research can be called goal-oriented. They retain the freedom to choose work methods, but unlike “pure” fundamental research, there is no freedom to choose research objects; the area and purpose of the research are tentatively set (for example, the development of a controlled thermonuclear reaction).
Basic Research carried out by academic research institutes and universities. Results of fundamental research - theories, discoveries, new principles of action. The probability of their use is 5 - 10%.
Exploratory Research cover work aimed at studying ways and means of practical application of the results of fundamental research. Their implementation presupposes the possibility of alternative directions for solving an applied problem and the choice of the most promising direction for solving it. They are based on known results of fundamental research, although as a result of the search, their main provisions may be revised.
The main purpose of exploratory research– use of the results of fundamental research for practical application in various fields in the near future (for example, searching and identifying opportunities for using lasers in practice).
Exploratory research may include work on the creation of fundamentally new materials, metal processing technologies, the study and development of scientific foundations for optimizing technological processes, the search for new drugs, the analysis of the biological effects of new chemical compounds on the body, etc.
Exploratory research has varieties: exploratory research of a broad profile without a special application to a particular production and of a narrowly focused nature for solving issues of specific industries.
Search work is carried out in universities, academic and industry research institutes. In certain branch institutes of industry and other sectors of the national economy, the share of search work reaches 10%.
The probability of practical use of exploratory research is about 30%.
Applied research (R&D) are one of the stages of the life cycle of creating new types of products. These include research that is carried out for the purpose of practical use of the results of fundamental and exploratory research in relation to specific tasks.
The purpose of applied research is to answer the question “is it possible to create a new type of product, material or technological process based on the results of fundamental and exploratory research, and with what characteristics.”
Applied research is carried out mainly in industrial research institutes. The results of applied research are patentable designs, scientific recommendations proving the technical feasibility of creating innovations (machines, devices, technologies). At this stage, it is possible to set a market target with a high degree of probability. The probability of practical use of applied research is 75 - 85%.
Research work consists of stages (phases), which are understood as a logically justified set of works that has independent significance and is the object of planning and financing.
The specific composition of the stages and the nature of the work performed within them are determined by the specifics of the research work.
According to GOST 15.101-98 “Procedure for carrying out research work,” the main stages of research work are:
1. Development of technical specifications (TOR)– selection and study of scientific and technical literature, patent information and other materials on the topic, discussion of the data obtained, on the basis of which an analytical review is compiled, hypotheses and forecasts are put forward, and customer requirements are taken into account. Based on the results of the analysis, areas of research and ways to implement the requirements that the product must satisfy are selected. Reporting scientific and technical documentation for the stage is drawn up, the necessary performers are determined, technical specifications are prepared and issued.
At the stage of developing technical specifications for research work, the following types of information are used:
· object of study;
· description of the requirements for the object of research;
· list of functions of the research object of a general technical nature;
· a list of physical and other effects, patterns and theories that may be the basis for the operating principle of a new product;
· technical solutions (in forecasting studies);
· information about the scientific and technical potential of the research performer;
· information about the production and material resources of the research performer;
· marketing research;
· data on the expected economic effect.
Additionally, the following information is used:
· methods for solving individual problems;
· general technical requirements (standards, environmental and other restrictions, requirements for reliability, maintainability, ergonomics, and so on);
· projected timing of product updates;
· offers of licenses and know-how on the subject of research.
2. Choosing the direction of research– collection and study of scientific and technical information, drawing up an analytical review, conducting patent research, formulating possible directions for solving problems set in the research specifications and their comparative assessment, choosing and justifying the adopted direction of research and methods for solving problems, comparing the expected performance of new products after implementation of research results with existing indicators of analogue products, assessment of the estimated economic efficiency of new products, development of a general research methodology. Drawing up an interim report.
3. Conducting theoretical and experimental research– development of working hypotheses, construction of models of the research object, justification of assumptions, scientific and technical ideas are tested, research methods are developed, the choice of various types of schemes is justified, calculation and research methods are selected, the need for experimental work is identified, and methods for their implementation are developed.
If the need for experimental work is determined, the design and manufacture of mock-ups and an experimental sample are carried out.
Bench and field experimental tests of the sample are carried out using developed programs and methods, the test results are analyzed, and the degree of compliance of the data obtained on the experimental sample with the calculated and theoretical conclusions is determined.
If there are deviations from the technical specifications, then the experimental sample is revised, additional tests are carried out, and if necessary, changes are made to the developed diagrams, calculations, and technical documentation.
4. Registration of research results– drawing up reporting documentation on the results of research work, including materials on the novelty and feasibility of using the results of research work, on economic efficiency. If positive results are obtained, then scientific and technical documentation and a draft technical specification for development work are developed. The compiled and executed set of scientific and technical documentation is presented to the customer for acceptance. If private technical solutions are new, they are registered through the patent service, regardless of the completion of all technical documentation. Before presenting the research work to the commission, the topic leader draws up a notice of its readiness for acceptance.
5. Topic acceptance– discussion and approval of the research results (scientific and technical report) and signing of the customer’s act of acceptance of the work. If positive results are obtained and the acceptance certificate is signed, the developer transfers to the customer:
An experimental sample of a new product accepted by the commission;
Acceptance test protocols and acceptance certificates for a prototype (mock-up) of the product;
Calculations of economic efficiency of using development results;
Necessary design and technological documentation for the production of an experimental sample.
The developer takes part in the design and development of a new product and, along with the customer, is responsible for achieving the product performance guaranteed by him.
Comprehensive research work according to a specific target program allows not only to solve a scientific and technical problem, but also to create a sufficient basis for more efficient and high-quality development work, design and technological preparation of production, as well as significantly reduce the amount of modifications and the time required for the creation and development of a new technology.
Experimental design developments (R&D). A continuation of applied research is technical developments: experimental design (R&D), design and technological (PTR) and design (PR) developments. At this stage, new technological processes are developed, samples of new products, machines and devices are created, etc.
The conduct of R&D is regulated by:
· STB 1218-2000. Development and production of products. Terms and Definitions.
· STB-1080-2011. “The procedure for carrying out research, development and experimental-technological work to create scientific and technical products.”
· TKP 424-2012 (02260). The procedure for developing and putting products into production. Technical Code. The provisions of the technical code apply to work on the creation of new or improved products (services, technologies), including the creation of innovative products.
· GOST R 15.201-2000, System for development and production of products. Products for industrial and technical purposes. The procedure for developing and putting products into production.
· etc. (see Appendix 10).
The purpose of the development work is the development of a set of working design documentation in the volume and quality of development sufficient to launch production of a certain type of product (GOST R 15.201-2000).
Experimental design work for its purposes is a consistent implementation of the results of previously conducted applied research.
Development work is mainly carried out by design and engineering organizations. The tangible result of this stage is drawings, projects, standards, instructions, prototypes. The probability of practical use of the results is 90 - 95%.
Main types of work, which are included in the OKR:
1) preliminary design (development of fundamental technical solutions for the product, giving a general idea of the principle of operation and (or) design of the product);
2) technical design (development of final technical solutions that give a complete understanding of the design of the product);
3) design (design implementation of technical solutions);
4) modeling, experimental production of product samples;
5) confirmation of technical solutions and their design implementation by testing mock-ups and prototypes.
Typical stages OCD are:
1. Technical task – the source document on the basis of which all work on the creation of a new product is carried out, developed by the manufacturer of the product and agreed upon with the customer (main consumer). Approved by the leading ministry (to whose profile the product being developed belongs).
The technical specifications determine the purpose of the future product, carefully justify its technical and operational parameters and characteristics: productivity, dimensions, speed, reliability, durability and other indicators determined by the nature of the future product. It also contains information about the nature of production, conditions of transportation, storage and repair, recommendations for completing the necessary stages of development of design documentation and its composition, feasibility study and other requirements.
The development of technical specifications is based on completed research work, marketing research information, analysis of existing similar models and their operating conditions.
When developing technical specifications for R&D, information similar to that used for developing technical specifications for research and development work is used (see above).
After coordination and approval, the technical specification is the basis for the development of a preliminary design.
2. Preliminary design consists of a graphic part and an explanatory note. The first part contains fundamental design solutions that give an idea of the product and the principle of its operation, as well as data defining the purpose, main parameters and overall dimensions. It gives an idea of the future design of the product, including general drawings, functional blocks, input and output electrical data of all nodes (blocks) that make up the overall block diagram.
At this stage, documentation for the production of mock-ups is developed, their production and testing are carried out, after which the design documentation is adjusted. The second part of the preliminary design contains the calculation of the main design parameters, a description of operational features and an approximate schedule of work for technical preparation of production.
The product layout allows you to achieve a successful layout of individual parts, find more correct aesthetic and ergonomic solutions and thereby speed up the development of design documentation at subsequent stages.
The tasks of the preliminary design include the development of guidelines for ensuring manufacturability, reliability, standardization and unification at subsequent stages, as well as drawing up a list of specifications of materials and components for prototypes for their subsequent transfer to the logistics service.
The preliminary design goes through the same stages of coordination and approval as the technical specifications.
3. Technical project is developed on the basis of an approved preliminary design and provides for the implementation of graphic and calculation parts, as well as clarification of the technical and economic indicators of the product being created. It consists of a set of design documents containing final technical solutions that provide a complete picture of the design of the product being developed and the initial data for the development of working documentation.
The graphic part of the technical project contains drawings of the general view of the designed product, assemblies in the assembly and main parts. Drawings must be coordinated with technologists.
The explanatory note contains a description and calculation of the parameters of the main assembly units and basic parts of the product, a description of the principles of its operation, justification for the choice of materials and types of protective coatings, a description of all schemes and final technical and economic calculations. At this stage, when developing product options, a prototype is manufactured and tested. The technical project goes through the same stages of coordination and approval as the technical specifications.
4. Working draft is a further development and specification of the technical project. This stage is divided into three levels: development of working documentation for a pilot batch (prototype); development of working documentation for the installation series; development of working documentation for serial or mass production.
The result of R&D is a set of working design documentation (WDC) for launching production of a new type of product.
Detailed design documentation (DKD)– a set of design documents intended for the manufacture, control, acceptance, delivery, operation and repair of a product. Along with the term “working design documentation,” the terms “working technological documentation” and “working technical documentation” are used with a similar definition. Working documentation, depending on the scope of use, is divided into production, operational and repair work documentation.
Thus, the result of R&D, or in other words scientific and technical products (STP), is a set of design and development documents. Such a set of design documentation may contain:
· actual design documentation,
· software documentation,
· operational documentation.
In some cases, if provided for by the requirements of the technical specifications, technological documentation may also be included in the working technical documentation.
The various stages of OCD, as they are carried out, must contain their characteristic results, such results are:
· technical documentation based on the results of preliminary technical design;
· mock-ups, experimental and pre-production samples made during the implementation of development work;
· test results of prototypes: preliminary (PI), interdepartmental (MI), acceptance (PRI), state (GI), etc.
Related information.
