1. A method for carrying out collaborative research and development management on complex equipment is characterized by comprising the following steps:

s1, performing page login operation by a collaborative research and development management system facing complex equipment;

and S2, entering a complex equipment-oriented collaborative research and development management system after the login page successfully logs in, and responding the operation of the login user by the system.

2. A system for carrying out collaborative research and development management on complex equipment is characterized by comprising:

a collaborative portal module: the interface is used for providing a login system for various users;

the project collaborative management module: according to the research and development products or projects, one or any combination of stage division, project planning, WBS decomposition and project monitoring is carried out;

a research and development task management module: planning research and development tasks, designing a research and development workflow, issuing the research and development tasks, executing one of the research and development tasks or randomly combining the research and development tasks; monitoring the development task;

an integrated development environment module: the method is used for carrying out one or any combination of tool software packaging, tool flow template configuration, interface configuration and tool flow execution;

a process data management module: aiming at research and development data generated in the product research and development process, the used research and development flow template and/or tool flow template are managed in a unified way;

a knowledge management module: one or any combination of management for accumulating knowledge, classification, knowledge service and knowledge statistics;

a system integration module: the interface is realized with an external system through an external access interface of the system;

the input end of the collaborative portal module is connected with the output ends of the project collaborative management module, the research and development task management module, the integrated development environment module and the knowledge management module; the project collaborative management module, the research and development task management module and the integrated development environment module are connected with the system integration module and the knowledge management module, and the process data management module is connected with one or any combination of the project collaborative management module, the research and development task management module, the integrated development environment module, the system integration module and the knowledge management module.

3. The system for collaborative development management of complex equipment according to claim 2, wherein the project collaborative management module comprises:

and (3) project information management: providing an item list for each type of users, and carrying out classified display on the items related to the individuals; entering a certain project, and checking project basic information in a project profile interface, wherein the project basic information comprises project information and/or progress information;

item starting: all projects must be created uniformly in the system, project numbers are generated uniformly, and responsibility departments and responsible persons are issued uniformly; the project starting management is mainly used for a starting process after project declaration and approval or contract signing, and provides one or any combination operation control of project starting auditing, notification, reminding and early warning;

project planning: the method comprises one or any combination of product development stage division, team planning, research and development plan compilation, research and development plan resource and delivery management, research and development plan batch adjustment, research and development plan translation, research and development plan pre-and-post relationship setting, research and development plan template management, research and development plan export and import and research and development plan assignment;

item ending: after the project passes the inspection and acceptance of the organization, the project responsible person can initiate the project heading process on line; after the project ends up, the project achievements can be inquired as knowledge;

and (4) project monitoring: the method comprises one or any combination of project progress tracking, project task monitoring, project signboards and statistical reports.

4. The system of claim 3, wherein the project information management comprises: project creation, project planning in a whole period and project splitting or any combination;

the project creation includes the steps of:

s1, judging whether the operation user is the project supervisor and has a signal for creating the formal project, if yes, executing the next step;

s2, judging whether to upload one or any combination of the contract, the task book and the reply document related to the project; if yes, executing the next step;

s3, judging whether the format of one or any combination of the uploaded project related contracts, task books and copy files meets the format standard, if so, judging whether the format of the uploaded project related contracts, task books and copy files meets the format standard

The formal items include: filling one or any combination of basic information, source, expense source, period and annual distribution of the project, designated project responsible person, project return management department, technical responsible person, target, batch summary, superior competent department and research result;

the project full-period plan making method comprises the following steps:

s11, judging whether the operation user is the project supervisor, if yes, making a project full-period plan, and executing the next step;

s22, entering a project full-cycle planning interface, which comprises a first part and a second part, wherein the first part comprises: setting one or any combination of project full-period main plan nodes, completion time and completion forms, wherein the second part comprises: making a project implementation stage plan and/or an annual implementation plan;

the first part is the basis of the second part, namely the second part content belongs to the first part content;

s33, judging whether the item is a model item, if so, executing the next step;

s44, setting a full-period node of the model item, including: completion time for one or any combination of the protocol (pattern), prototype, and pattern (proof) stages;

the project making full-period plan supports Excel format import.

5. The system of claim 4, wherein the project splitting comprises the following steps:

s01, judging whether the operation user is the project supervisor and has a project split signal, if yes, executing the next step;

s02, if a project is split into multiple layers, generating a project or subsystem which is formally issued;

s03, setting one or any combination of responsibility departments, responsible persons, expenses, main research contents, technical indexes, full-period planning nodes and result forms of each topic or subsystem;

s04, the system automatically generates item numbers for the items and their subjects or subsystems according to the item number rules.

6. The system for collaborative development management of complex equipment according to claim 3, wherein the project initiation includes the following steps:

item starting auditing, item starting informing and item starting reminding;

s001, starting auditing of the project: if a signal that the project is created is received, the project supervisor submits the signal to a leader of a director to carry out auditing, and an auditor audits one or any combination of project basic information, project numbers and plan nodes;

s002, project work start notification: after the project is approved, the project related personnel can receive a project start notification automatically sent by the system, wherein the project start notification comprises one or any combination of a responsible person participating in a project department, a related leader, a related person in a financial department, a project supervisor and a project responsible person;

s003, item starting reminding: the system sends a process examination and approval completion after the project is started, reminds a project principal to plan the project, and transmits related personnel, including one or any combination of leadership, project leader of a project leader department and leadership of a related research room;

s004, judging whether the project plan is overdue or not, and if yes, providing an early warning function by the system;

the early warning function comprises: the project responsible person sends early warning information and copies related personnel;

or/and the product development stage division comprises:

in the product planning stage, a project principal automatically divides the development stages of the product according to the development method and the requirement of the product, and each product stage defines corresponding development period and/or development achievement information; in the development stage, a research and development task structure tree can be constructed, and a design flow is established;

the execution process of the development phase is executed in a serial mode;

or/and the team plan comprises:

s-1, a project team is built, personnel in the project basic information can automatically join in the team, and team members can carry out task entrusting;

s-2, executing any step in the steps S-3 to S-8;

s-3, summarizing and counting all the projects and plans born by each person according to the dimension of the person;

s-4, inquiring and generating plans and workloads born by personnel by taking time periods, personnel and departments as conditions;

s-5, enabling cross-department and cross-professional personnel management functions of an IPT (IPT) team, including adding or deleting personnel;

s-6, setting responsible persons for task decomposition in batches;

s-7, setting role authorities of different personnel in a team;

s-8, reversely feeding the project information into the integrated system through the integrated interface;

or/and the research and development plan context setting comprises:

setting the precedence relationship among the tasks, and correspondingly controlling the execution of the tasks by the system according to the precedence relationship of the tasks;

after all the tasks in the previous stage are completed, the tasks in the next stage can be developed, and under special conditions, the tasks in the next stage can be started in advance by adding an approval process;

or/and the development planning comprises the following steps:

S-A, judging whether project planning is finished, if so, performing task assignment operation on A user with task allocation authority in A user-defined flow, and assigning different tasks to corresponding team personnel or departments by the user according to the duties of the team members or the departments; meanwhile, the work entrustment setting can be carried out;

and S-B, submitting the project plan to relevant leaders for examination by a project supervisor or project responsible person, judging whether the examination passes, and if so, formally issuing a task responsible department or responsible person.

7. The system for collaborative development and management of complex equipment according to claim 6, wherein the development planning further comprises:

the detailed decomposition of the plan is supported, a user with authority can perform decomposition operation on the plan, and meanwhile, the dependency relationship in the plan can be set for the processes of different products.

8. The system for collaborative development management of complex equipment according to claim 2, wherein the step S1 includes the following steps:

s11, whether the system receives the login trigger signal of the login user:

if the system receives a login trigger signal of a login user, the system pops up a login page; displaying a login code on a login page;

if the system does not receive the login trigger signal of the login user, continuing to wait, and returning to the step S11;

s12, the system judges whether it receives the check login information, and judges whether the received check login information is consistent with the check login information stored by the system:

if the system does not receive the check login information, returning to the step S12;

if the system receives the check login information, judging whether the received check login information is consistent with the check login information stored by the system:

if the received verification login information is consistent with the verification login information stored in the system, the verification is successful, and the system is entered;

if the received verification login information is inconsistent with the verification login information stored in the system, updating the login code on the login page; return is made to step S12.

9. The system for collaborative development management of complex equipment according to claim 2, wherein the step S12 includes the following steps:

s121, scanning the login code displayed on the login page by using the intelligent terminal of the logged-in system, analyzing the login security information in the login code by using the intelligent terminal, and carrying out security encryption processing on the obtained login security information before transmission to obtain security transmission information of the login security information; the calculation method for obtaining the safe sending information comprises the following steps:

wherein Lsi represents login security information;

csn represents the serial number of the CPU of the intelligent terminal;

summary [ ] represents a secure encryption algorithm;

binary represents Binary conversion;

hexadecimal represents Hexadecimal conversion;

Summary[]_Binaryindicating that the result value is converted to a binary value;

Summary[]_Hexadecimalindicating that the result value is converted to a hexadecimal value;

representing an operator, an exclusive nor operation;

the Send information security represents the security sending information;

s122, the intelligent terminal sends the obtained safety sending information to the system, and the system checks whether the received safety sending information is consistent with the verification safety information stored in the system or not:

if the received safety sending information is consistent with the verification safety information stored in the system, the system sends the login information to a login page, and the login page logs in the system according to the received login information;

and if the received safety sending information is inconsistent with the verification safety information stored in the system, the login code is rescanned by using the intelligent terminal.

Background

Nowadays, new product development has become the core driving force for enterprises to operate successfully, and enterprises adopt various research and development strategies to conform to market changes. However, market and user demands are changing constantly, research and development subject sources are wide, and domestic enterprises do not have mature research and development management systems, so that new products are slow to research and develop, and the effect is poor; each business system in an enterprise is established on a respective frame, so that information is difficult to integrate, and the requirement of research and development personnel for cooperation cannot be met; the market conversion rate of the research and development results is relatively low. In order to promote the stable operation of a research and development mechanism, the whole research and development process is coherent and effective, and a complete and feasible research and development management system is urgently needed as a foundation at the present stage, however, the traditional research and development management system often has the following problems:

1. research and development mode laggard

The cooperation and management in the product research and development process are mainly completed by manual coordination, various information is mostly transmitted in a paper information transmission mode, real-time and accurate information interaction means and cooperative working platforms are lacked among departments, professionals and systems and subsystems, the electronic technical state and configuration management are not deep enough, and a cooperative research and development mode based on a unified product structure cannot be formed.

2. Data management confusion between research and development tasks

The collaboration among research and development personnel is based on data, and the data transfer among the personnel and the data version of the data transfer are lack of management. Data transfer errors among designers cause the designers to often work under outdated input conditions and perform ineffective design, and the research and development efficiency is reduced.

3. Collaborative patterns between research and development tasks are prone to errors

The collaborative design is a continuously iterative process, and the updating of data can affect other related design works. At present, after data updating in a certain link is finished, a relevant design responsible person needs to be notified manually, and human errors such as incomplete notification of relevant persons, data transmission errors and the like easily occur in the mode. The design team leader needs to spend a great deal of effort in coordinating the task linking work between people.

4. Difficulty in controlling product research and development progress

At present, the responsible persons of the research and development group cannot know the progress of each work task in real time, and the research and development progress cannot be controlled. In the cooperative process, the workload of each designer and the key tasks in the research and development design flow are evaluated by experience, and quantitative data is lacked to realize the uniform allocation and optimization of research and development resources.

Disclosure of Invention

The invention aims to at least solve the technical problems in the prior art, and particularly creatively provides a complex equipment-oriented collaborative research and development management system.

In order to achieve the above object, the present invention provides a method for performing collaborative research and development management on complex equipment, comprising the following steps:

s1, performing page login operation by a collaborative research and development management system facing complex equipment;

and S2, entering a complex equipment-oriented collaborative research and development management system after the login page successfully logs in, and responding the operation of the login user by the system.

Further, comprising:

a collaborative portal module: the interface is used for providing a login system for various users;

the project collaborative management module: according to the research and development products or projects, one or any combination of stage division, project planning, WBS decomposition and project monitoring is carried out;

a research and development task management module: planning research and development tasks, designing a research and development workflow, issuing the research and development tasks, executing one of the research and development tasks or randomly combining the research and development tasks; monitoring the development task;

an integrated development environment module: the method is used for carrying out one or any combination of tool software packaging, tool flow template configuration, interface configuration and tool flow execution;

a process data management module: aiming at research and development data generated in the product research and development process, the used research and development flow template and/or tool flow template are managed in a unified way;

a knowledge management module: one or any combination of management for accumulating knowledge, classification, knowledge service and knowledge statistics;

a system integration module: the interface is realized with an external system through an external access interface of the system;

the input end of the collaborative portal module is connected with the output ends of the project collaborative management module, the research and development task management module, the integrated development environment module and the knowledge management module; the project collaborative management module, the research and development task management module and the integrated development environment module are connected with the system integration module and the knowledge management module, and the process data management module is connected with one or any combination of the project collaborative management module, the research and development task management module, the integrated development environment module, the system integration module and the knowledge management module.

Further, the project collaboration management module includes:

and (3) project information management: providing an item list for each type of users, and carrying out classified display on the items related to the individuals; entering a certain project, and checking project basic information in a project profile interface, wherein the project basic information comprises project information and/or progress information;

item starting: all projects must be created uniformly in the system, project numbers are generated uniformly, and responsibility departments and responsible persons are issued uniformly; the project starting management is mainly used for a starting process after project declaration and approval or contract signing, and provides one or any combination operation control of project starting auditing, notification, reminding and early warning;

project planning: the method comprises one or any combination of product development stage division, team planning, research and development plan compilation, research and development plan resource and delivery management, research and development plan batch adjustment, research and development plan translation, research and development plan pre-and-post relationship setting, research and development plan template management, research and development plan export and import and research and development plan assignment;

item ending: after the project passes the inspection and acceptance of the organization, the project responsible person can initiate the project heading process on line; after the project ends up, the project achievements can be inquired as knowledge;

and (4) project monitoring: the method comprises one or any combination of project progress tracking, project task monitoring, project signboards and statistical reports.

Further, the project information management includes: project creation, project planning in a whole period and project splitting or any combination;

the project creation includes the steps of:

s1, judging whether the operation user is the project supervisor and has a signal for creating the formal project, if yes, executing the next step;

s2, judging whether to upload one or any combination of the contract, the task book and the reply document related to the project; if yes, executing the next step;

s3, judging whether the format of one or any combination of the uploaded project related contracts, task books and copy files meets the format standard, if so, judging whether the format of the uploaded project related contracts, task books and copy files meets the format standard

The formal items include: filling one or any combination of basic information, source, expense source, period and annual distribution of the project, designated project responsible person, project return management department, technical responsible person, target, batch summary, superior competent department and research result;

the project full-period plan making method comprises the following steps:

s11, judging whether the operation user is the project supervisor, if yes, making a project full-period plan, and executing the next step;

s22, entering a project full-cycle planning interface, which comprises a first part and a second part, wherein the first part comprises: setting one or any combination of project full-period main plan nodes, completion time and completion forms, wherein the second part comprises: making a project implementation stage plan and/or an annual implementation plan;

the first part is the basis of the second part, namely the second part content belongs to the first part content;

s33, judging whether the item is a model item, if so, executing the next step;

s44, setting a full-period node of the model item, including: completion time for one or any combination of the protocol (pattern), prototype, and pattern (proof) stages;

the project making full-period plan supports Excel format import.

Further, the item splitting comprises the following steps:

s01, judging whether the operation user is the project supervisor and has a project split signal, if yes, executing the next step;

s02, according to the actual situation, if a project is split into multiple layers, a project or subsystem which is formally issued is generated;

s03, setting one or any combination of responsibility departments, responsible persons, expenses, main research contents, technical indexes, full-period planning nodes and result forms of each topic or subsystem;

s04, the system automatically generates item numbers for the items and their subjects or subsystems according to the item number rules.

Further, the project launch includes the steps of:

item starting auditing, item starting informing and item starting reminding;

s001, starting auditing of the project: if a signal that the project is created is received, the project supervisor submits the signal to a leader of a director to carry out auditing, and an auditor audits one or any combination of project basic information, project numbers and plan nodes;

s002, project work start notification: after the project is approved, the project related personnel can receive a project start notification automatically sent by the system, wherein the project start notification comprises one or any combination of a responsible person participating in a project department, a related leader, a related person in a financial department, a project supervisor and a project responsible person;

s003, item starting reminding: the system sends a process examination and approval completion after the project is started, reminds a project principal to plan the project, and transmits related personnel, including one or any combination of leadership, project leader of a project leader department and leadership of a related research room;

s004, judging whether the project plan is overdue or not, and if yes, providing an early warning function by the system;

the early warning function comprises: the project responsible person sends early warning information and copies related personnel;

or/and the product development stage division comprises:

in the product planning stage, a project principal automatically divides the development stages of the product according to the development method and the requirement of the product, and each product stage defines corresponding development period and/or development achievement information; in the development stage, a research and development task structure tree can be constructed, and a design flow is established;

the execution process of the development phase is executed in a serial mode; the key information of the development stage is the basis of WBS task decomposition;

or/and the team plan comprises:

s-1, a project team is built, personnel in the project basic information can automatically join in the team, and team members can carry out task entrusting;

s-2, executing any step in the steps S-3 to S-8;

s-3, summarizing and counting all the projects and plans born by each person according to the dimension of the person so as to monitor the working load of all human resources in a centralized manner;

s-4, inquiring and generating plans and workloads born by personnel by taking time periods, personnel and departments as conditions;

s-5, enabling cross-department and cross-professional personnel management functions of an IPT (IPT) team, including adding or deleting personnel;

s-6, setting responsible persons for task decomposition in batches;

s-7, setting role authorities of different personnel in a team;

s-8, reversely feeding the project information into the integrated system through the integrated interface;

the team members are shown in a list form, and the serial numbers, the posts, the main responsibilities, the units, the names and the remarks of the team members are displayed, wherein the project post information can be edited and expanded;

or/and the research and development plan context setting comprises:

setting the precedence relationship among the tasks, and correspondingly controlling the execution of the tasks by the system according to the precedence relationship of the tasks;

after all the tasks in the previous stage are completed, the tasks in the next stage can be developed, and under special conditions, the tasks in the next stage can be started in advance by adding an approval process;

or/and the development planning comprises the following steps:

S-A, judging whether project planning is finished, if so, performing task assignment operation on A user with task allocation authority in A user-defined flow, and assigning different tasks to corresponding team personnel or departments by the user according to the duties of the team members or the departments; meanwhile, the work entrustment setting can be carried out;

and S-B, submitting the project plan to relevant leaders for examination by a project supervisor or project responsible person, judging whether the examination passes, and if so, formally issuing a task responsible department or responsible person.

Further, the development planning further comprises:

the detailed decomposition of the plan is supported, a user with authority can perform decomposition operation on the plan, and meanwhile, the dependency relationship in the plan can be set for the processes of different products.

Further, the step S1 includes the following steps:

s11, whether the system receives the login trigger signal of the login user:

if the system receives a login trigger signal of a login user, the system pops up a login page; displaying a login code on a login page;

if the system does not receive the login trigger signal of the login user, continuing to wait, and returning to the step S11;

s12, the system judges whether it receives the check login information, and judges whether the received check login information is consistent with the check login information stored by the system:

if the system does not receive the check login information, returning to the step S12;

if the system receives the check login information, judging whether the received check login information is consistent with the check login information stored by the system:

if the received verification login information is consistent with the verification login information stored in the system, the verification is successful, and the system is entered;

if the received verification login information is inconsistent with the verification login information stored in the system, updating the login code on the login page; return is made to step S12.

Further, the step S12 includes the following steps:

s121, scanning the login code displayed on the login page by using the intelligent terminal of the logged-in system, analyzing the login security information in the login code by using the intelligent terminal, and carrying out security encryption processing on the obtained login security information before transmission to obtain security transmission information of the login security information; the calculation method for obtaining the safe sending information comprises the following steps:

wherein Lsi represents login security information;

csn represents the serial number of the CPU of the intelligent terminal;

summary [ ] represents a secure encryption algorithm;

binary represents Binary conversion;

hexadecimal represents Hexadecimal conversion;

Summary[]_Binaryindicating that the result value is converted to a binary value;

Summary[]_Hexadecimalindicating that the result value is converted to a hexadecimal value;

representing an operator, an exclusive nor operation;

the Send information security represents the security sending information;

s122, the intelligent terminal sends the obtained safety sending information to the system, and the system checks whether the received safety sending information is consistent with the verification safety information stored in the system or not:

if the received safety sending information is consistent with the verification safety information stored in the system, the system sends the login information to a login page, and the login page logs in the system according to the received login information;

and if the received safety sending information is inconsistent with the verification safety information stored in the system, the login code is rescanned by using the intelligent terminal.

In summary, due to the adoption of the technical scheme, the invention has the beneficial effects that: data between research and development tasks can be managed conveniently and rapidly, and the whole research and development process is coherent and effective; the occurrence of errors of the collaborative mode between the research and development tasks is greatly reduced; the real-time control of the product research and development progress is realized.

Additional aspects and advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.

Drawings

The above and/or additional aspects and advantages of the present invention will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:

FIG. 1 is a general architectural diagram of the present invention;

FIG. 2 is a schematic overview of the project of the present invention;

FIG. 3 is a project creation diagram of the present invention;

FIG. 4 is a schematic view of a resource association of the present invention;

FIG. 5 is a schematic view of a delivery setup of the present invention;

FIG. 6 is a schematic view of a project bulletin board of the present invention;

FIG. 7 is a schematic diagram of a development task structure tree of the present invention;

FIG. 8 is a development workflow design diagram of the present invention;

FIG. 9 is a schematic illustration of data type selection according to the present invention;

FIG. 10 is a schematic view of a work item detail interface of the present invention;

FIG. 11 is a schematic diagram of integrated development environment task execution of the present invention;

FIG. 12 is a schematic diagram of the present invention for performing data result generation;

FIG. 13 is a data lineage diagram according to an embodiment of the invention;

FIG. 14 is a schematic diagram of a normal submission of data in accordance with an embodiment of the present invention.

Detailed Description

Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the accompanying drawings are illustrative only for the purpose of explaining the present invention, and are not to be construed as limiting the present invention.

The platform adopts a modular and scalable technical architecture. The specific frame is shown in figure 1:

the platform is divided into 8 modules, namely a collaborative portal, project collaborative management, research and development task management, an integrated development environment, knowledge management, system integration, process data management and system management.

(1) A collaboration portal: and providing interfaces for various users to log in the system.

(2) And (3) project collaborative management: according to the research and development products or projects, the stage division, project planning, WBS decomposition and project monitoring can be carried out.

(3) Managing research and development tasks: the method comprises the steps of planning research and development tasks, designing research and development workflows, issuing the research and development tasks, executing the research and development tasks and monitoring the research and development tasks.

(4) An integrated development environment: the method can be used for packaging tool software, configuring a tool flow template, configuring an interface and executing a tool flow.

(5) And (3) process data management: and aiming at research and development data generated in the product research and development process, the used research and development flow templates, tool flow templates and the like are managed in a unified way.

(6) Knowledge management: the system can accumulate knowledge, manage classification, provide knowledge service and perform knowledge statistics.

(7) And (3) system management: and the management and compliance of the user, role, authority, confidentiality and the like of the system are realized.

(8) System integration: the interface is realized with an external system through an external access interface and strong customized development capability of the system.

1. Detailed platform design

The platform function module comprises: collaborative portals, project collaborative management, research and development task management, integrated development environments, process data management, knowledge management and application, system integration, system management, and the like.

1.1 collaboration portal

The platform provides an integrated environment for constructing a system access portal based on roles and cooperative work, supports system operators to manage related processes in a model development process, and can establish corresponding access portals according to different roles and applications of access users, so that the users of the related roles can quickly acquire required information through the different portals, check and receive all tasks required to be processed, and can develop the corresponding cooperative work in the system based on a single system environment. The system provides functions of task prompting, state monitoring, early warning, overdue warning and the like.

The platform supports the configuration of personalized portal pages according to the requirements of users, and the users access multiple portals through a uniform entrance and only access authorized portals. The portal self-defined management can self-define functions of system login interfaces, system navigation, system shortcut channels and the like for different departments and different roles, and meets the requirement of system use personalization.

1.1.1 functional Inlet

The system provides a uniform portal and displays different functional modules according to the authority of different roles. Quick access to functions is achieved.

The system provides professional subsystems for storage according to different users, and access to each professional subsystem through the authority and the role is achieved.

1.1.2 My tasks

The system provides a task management function related to a current logged-in user, provides items to be processed by the logged-in user, and presents the items in a list form, and the user clicks the items to be transferred to an actual operation page of a task to process the items to be processed by the user. Mainly including tasks to be done (tasks to be done and candidate tasks), tasks already done (matters the user has done and the process instance has not completed), and tasks done (archived or terminated process requests the user has initiated themselves).

The links and the number of the tasks to be handled of all types can be uniformly pushed to the portal, and the task to be handled is reminded at the eye-catching position. The task to be done and the candidate task of the current user can be checked.

1.1.3 message alerts

Message reminding for notification in an eye-catching position is supported. The user is provided with a function of viewing the message receiving box and the message sending box in the message module, and the message receiving box can identify the source type of the message and whether the message is read or not besides basic information for identifying the message. The user clicks the corresponding message entry to check the detailed information of the message and the reply condition of the message; clicking on the message in the outbox will see whether the message has been reviewed by the addressee and a reply to the sent message.

1.1.4 early warning information

The system pushes various risks, problems and monitoring states to a portal home page, early warning information such as threshold early warning and the like is carried out, early warning and overdue early warning are carried out, and a user can check early warning prompts and take precautionary measures as soon as possible.

1.1.5 My Schedule

The system can automatically push the work plan to the personal schedule, can manually add backlog to the schedule, and can check the calendar view based on the month, week and day.

1.1.6 Notification information

And providing a task announcement function, and issuing information such as task review, acceptance and the like to a portal home page in an announcement form for related personnel to know.

1.2 project collaboration management

The project collaborative process management function is provided, and elements such as stages and plans in the project implementation process are comprehensively managed.

1.2.1 project information management

As shown in fig. 2, a list of items is provided for each type of user for categorizing the personally relevant items for presentation. Entering a project, the basic information of the project, including project information, progress information, etc., can be viewed in a project profile interface.

1.2.1.1 project creation

The project supervisor creates formal projects in the system, fills in basic information of the projects, project sources, project expense sources, project periods, full-period expenses and annual distribution, specifies project responsible persons, project return management departments, technical responsible persons, targets, reply abstracts, superior supervisor departments, research results and the like, and uploads project-related contracts, task books and reply documents.

The system supports rapid implementation of extensions to project attributes through dynamic modeling tools. A project creation diagram is shown in fig. 3.

1.2.1.2 compiling a full cycle plan

The project supervisor can make a project full-period plan, and make a project full-period main plan node, completion time and completion form as a basis for making a project implementation stage plan and an annual implementation plan. The full period node of the model item includes completion time of a scenario (pattern), a prototype, a pattern (prototype) phase, and the like.

And supporting the import of the full-period plan by using Excel.

1.2.1.3 project resolution

The project supervisor can divide a project into multiple layers according to actual conditions to generate a project or a subsystem which is formally issued. When the project is divided, the responsibility department, the responsible person, the expense, the main research content, the technical index, the whole period plan node, the result form and the like of each topic or subsystem can be set. The system can automatically generate project numbers for projects and their topics or subsystems according to the project number rules.

1.2.2 project Start

The project starting process is a process which each project must go through, and is an indispensable link, and all projects must be uniformly created in the system, uniformly generated with project numbers, and uniformly issued to responsibility departments and responsible persons. The project starting management is mainly used for the starting process after project declaration and approval or contract signing, and provides operation control of project starting auditing, notification, reminding, early warning and the like.

1.2.2.1 project Start Auditing

And after the project is created, the project manager submits the project to the leader of the administrative department for auditing, and auditors audit the information such as the basic information, the project number, the plan node and the like of the project.

1.2.2.2 project work on Notification

After the project is approved, the project related personnel can receive project start-up notification automatically sent by the system, wherein the project start-up notification comprises a responsible person (business department leader) participating in a project department, a related leadership, related personnel at a financial department, a project supervisor, a project responsible person and the like.

1.2.2.3 project Start reminding

The system sends out the process examination and approval to finish when the project is started, reminds the project responsible person to plan the project, and transmits the related personnel, including the leadership, the project director, the related research room leadership and the like.

If the project plan is overdue, the system provides an early warning function, and sends early warning information to a project responsible person and copies related personnel.

1.2.3 project plans

1.2.3.1 product development staging

The project principal can divide the development stages of the product by oneself according to the development method and the requirement of the product in the product planning stage, and each product stage can define key information such as the development period, the development achievement and the like. A research and development task structure tree can be constructed in the research and development stage, and a design flow is established. The execution of the development phase is performed in a serial manner. The key information of the development stage is the basis of WBS task decomposition. The model items are divided into a scheme (pattern) stage, a preliminary sample stage and a sample (normal sample) stage by default.

1.2.3.2 team plans

And (4) building a project team, and enabling personnel in the basic information of the project to automatically join the team. Team members may perform task delegation. The team members are shown in a list form (including serial numbers, positions, main duties, units, names, remarks and the like), wherein the project position information can be edited and expanded.

The method supports the collection and statistics of all the projects and plans born by each person by the dimension of the person so as to carry out centralized monitoring on the workload of all human resources; the plan and the workload born by the personnel can be inquired and generated by taking the time period, the personnel and the department as conditions. The cross-department and cross-professional personnel management functions of the IPT team are supported, including personnel addition, personnel deletion and the like; supporting the responsible person who sets task decomposition in batches; supporting setting of role permissions of different personnel in a team; supporting the back feeding of project information into the integrated system through the integrated interface.

1.2.3.3 development planning

The visual step-by-step task decomposition tool based on the WBS is provided, the project supervisor or the project responsible person is supported to compile implementation plans by stages according to the year, month and year, and the annual scientific research plan is supported to be generated according to the scientific research task data. The Project planning method and the Project planning system support rapid planning by importing Project planning templates, excels, projects and the like, and also support exporting Project plans into plan templates, excels or Project files. Quality control points (e.g., reviews, delivery checks, etc.) are set to project plans and quality management personnel can track quality control point completion. And the planning of up-and-down translation of the batch, batch postponing or advancing and batch compression are supported.

A right-click menu is provided, including add, edit, delete phases or tasks, for manually defining WBSs. The work item types in the WBS comprise stages, common tasks, outsourcing tasks, department cooperative tasks, contract nodes, control nodes and the like.

The WBS viewing function is provided, the WBS can be unfolded and folded, the Gantt chart can be moved forwards or backwards, the Gantt chart can be viewed by day or week, the WBS viewing function can be adaptively viewed, and the like.

1.2.3.4 developing planned resources and deliverable management

Resource association: the support task plan is associated with resources (team, object) so as to timely find out the condition of resource usage conflict, as shown in fig. 4.

Delivery setting: when planning, the achievement of each task, the pre-task, the type of task assessment (whether assessment is performed or not), the task responsibility department or the responsible person can be specified, and the task level (important, general) can be set, as shown in fig. 5.

1.2.3.5 development plan batch tuning

The development plan can be adjusted in batches, and the method specifically comprises the steps of carrying out batch translation (advancing or delaying), batch compression (reducing the planning duration time at the same time), and batch extension (increasing the planning duration time at the same time) on the selected plan, so that the planning efficiency is improved.

1.2.3.6 development plan translation

Bulk movement of the selected plan is supported to adjust the position of the planning tasks throughout the project plan, including up, down, left, and right. When the plan moves left or right, the system will automatically adjust the parent-child relationships of the tasks.

1.2.3.7 development planning context setting

The precedence relationship between the tasks can be set, and the system can correspondingly control the execution sequence of the tasks. Generally, after all tasks in the previous stage are completed, the next stage of tasks can be performed, and in a special case, the next stage of tasks can be started in advance by adding an approval process. Setting a plan precedence relationship: through the menu [ setting the preposition ], the task precedence relationship among activities can be defined, and the system can correspondingly control the execution sequence of the tasks. The selected pre-task can be deleted through the menu [ delete pre-task ].

1.2.3.8 development plan template management

And providing a project research and development plan template library and providing functions of importing and exporting project plan templates. The project full life cycle template can be customized according to the project type. The project plan template is imported to quickly generate the plan tasks, so that the project template is reused. Meanwhile, the definition and management of various approval processes in the scientific research process can be realized through a process design tool.

1.2.3.9 development plan export and import

Exporting the current plan to Excel, compiling a new plan in the Excel according to a specified format, and importing the Excel into a system to realize rapid planning.

1.2.3.10 development planning

After project planning is finished, task assignment operation can be carried out on users with task allocation authority in the user-defined flow, and the users can assign different tasks to corresponding team members or departments according to the duties of the team members or the departments; and simultaneously, work request setting can be carried out. And submitting the project plan to a related leader for examination by a project supervisor or a project principal, and formally issuing a task responsibility department or a responsible person after the examination is passed. The detailed decomposition of the plan is supported, a user with authority can perform decomposition operation on the plan, and meanwhile, the dependency relationship in the plan can be set for the processes of different products.

1.2.4 project Ends

1.2.4.1 item conclusion

After the project passes the acceptance of the organization, the project responsible person can initiate the project heading process on line. After the project is ended, the project achievement can be inquired as knowledge (the whole-station search comprises the project achievement).

1.2.4.2 project suspend/resume

For an item in progress, a pause may be required for a period of time, either for external or internal reasons. The project principal can initiate the project abort process online.

When an item in the suspended state is resolved, perhaps for some reason, it needs to proceed. The project principal can initiate the project recovery process online.

1.2.5 project monitoring

Providing rich chart functions provides the manager with a greater view to the status of the progress of the project. Including business and task angles.

1.2.5.1 project progress tracking

The progress tracking of the project can check the progress state of each task in the project through the progress in the project view, and meanwhile, the progress of the whole project can be displayed more intuitively by utilizing a Gantt chart provided by the system.

1.2.5.2 project task monitoring

Project task monitoring is used for summarizing and consulting project tasks by staff at all levels. Various personnel can check the project tasks which are neutralized and completed according to the authority scope. The system automatically filters out a list of personally relevant items according to user permissions, and enters a state in which each item can monitor the progress of all tasks in the item.

For an individual, all the items that the individual participates in can be viewed;

for department leaders, all projects of a department can be viewed;

for the project supervisor of the returning department, all the projects managed by the manager can be checked;

for the leaders of the gate returning department, all projects of gate returning management can be checked;

all items can be viewed for the leader.

1.2.5.3 project board

The method provides rich task boards and data statistics functions, can conveniently and comprehensively understand and control the operation condition of the whole project through the boards, such as the percentage of completion of each task, the predicted completion time of the task, the current tasks of task managers, and the like, and is convenient for a decision maker to dynamically adjust the project task.

1. Project plan signboard

The planned completion (completed, incomplete, adjusted, etc.) of the selected project task within the specified time frame is viewed, as shown in FIG. 6.

And checking the planned completion of the selected project and department within a certain time period.

And checking data such as the number of issued or executed plans of all departments in all project modules within the appointed time range, the completion rate of the issued plans, the on-time completion rate, the adjustment rate, the cancellation rate and the like.

2. Project staff billboard

The time period, personnel and department can be used as conditions to inquire and generate a work hour summary table of the tasks undertaken by the personnel.

The workload statistics, work completion condition statistics and work efficiency conditions of project personnel can be checked.

1.2.5.4 statistical form

The method provides rich report statistics functions, comprises various types such as column charts, pie charts, curve charts, line charts and the like in form, and can perform various statistics on different objects and object combinations such as personnel, tasks, task states, task attributes, deliveries and the like on statistical objects.

1.3 research and development task management

The collaborative task management relies on a collaborative research and development task flow engine, provides an environment for the construction and operation of research and development tasks, and has general functions of research and development task flow design, construction, operation, monitoring and the like.

Providing a personal task billboard for each user, and allowing the users to view tasks to be handled and emergency tasks which are responsible for the users in a classified manner; the basic information of the task can be checked, the task data can be submitted, the task can be designed and decomposed, the task progress explanation can be filled in, and the like.

1.3.1 development task creation

The development task creation may be automatically created by receiving the WBS plan or may be manually created.

1.3.1.1WBS development plan reception

After the WBS research and development plan is issued, the user can receive the notification of the WBS plan after logging in the system. The system can display the tasks to be handled in a classified mode in a list mode. The WBS plan to be handled mainly comprises attributes of a plan name, an item to which the WBS plan belongs, a state, a plan start time, a plan end time and the like. The lowest layer elements of the WBS are called development tasks (development work packages), the development tasks are basic units for executing model development processes, and the development tasks are connected according to the sequence and the data relationship to form the development processes.

After the responsible person receives the WBS plan, the system automatically creates a research and development task according to the planning information of the WBS, such as the responsible person, the planning starting time, the planning ending time, the delivery and the project information. The automatically created development task interface is as follows:

1.3.1.2 building a research and development task Structure Tree

The research and development process is displayed through the research and development task structure tree, and through the research and development task structure tree, research and development tasks can be newly added, imported, modified, deleted and the like.

Newly adding a research and development task: if the WBS is received, the research and development task structure tree is directly created. If the basic information is manually created, basic information of a research and development task needs to be input: and the initial time of a research and development task plan, basic information of a task responsible person, a belonging project, a model and the like. In addition, the system has a flexible dynamic modeling function, and can quickly expand the attributes which need to be added by the research and development task nodes. As shown in fig. 7:

and (3) importing a research and development task template: a research and development task structure tree is created by importing a template of a research and development task, and the research and development task template is one of research and development knowledge.

Modifying the research and development tasks: the responsible persons and the planned starting and stopping time of the research and development tasks can be modified according to actual conditions.

And (3) deleting the research and development tasks: due to misoperation or model requirements, the established development tasks can be deleted.

1.3.2 development task planning

The specific execution of each development task is performed by a series of works (development work items), which are development workflows. The development workflow embodies the collaboration between designers. The research and development task design is that research and development workflows are designed, and the research and development task workflow comprises research and development task workflow template management, workflow authority management, workflow design, research and development work item design and the like.

1.3.2.1 development workflow template management

For specific types of research and development products, research and development work items of research and development tasks are divided into a plurality of similar parts, product responsible persons can store the research and development task structure tree into a template, and research and development of other product responsible persons or similar products can directly cut the research and development tasks on the original basis. When a user creates a research and development task, the user can select a research and development task template to construct a research and development workflow, and the research and development task can be quickly decomposed.

Each development workflow is composed of a plurality of development work items. When executing research and development work items, designers can use research and development components or tool flow templates to execute research and development work, and can also innovate the tool flow templates to carry out research and development work.

1.3.2.2 developing component library

The development component is a specific execution form of the development work items, and the definition of each work item needs to be bound with a specific development component.

The development components are divided into specific development components and general development components. The specific development component is a development task processing component realized by system customization development, such as: a certain computing development component, a demand analysis component, and the like. The universal research and development component is a research and development task processing component designed through an integrated development environment, and the development of the universal research and development component is specifically seen in the integrated development environment section.

And the component library is developed, so that the functions of newly adding, modifying, deleting and inquiring the development components are realized.

1.3.2.3 developing workflow design

After receiving the research and development task, the research and development task responsible person can also design the research and development workflow according to the output list of the research and development task. The design of the development workflow needs to be defined as follows:

the development task is broken down into work items.

The input manifest definition for each work item. Each work item input data list can be files, parameters and the like, and principle model machine parameters can be bound.

The output manifest definition for each work item. Each workitem output data manifest can be a file, integer, floating point number, text, and the like. Each data has a name and a version.

Each work item may be a development component that has solidified or may be innovatively designed through an integrated development environment. The integrated development environment may establish a tool flow for each work item. The work item execution is driven by the data flow engine (serial or parallel). A particular piece of content integrates a development environment section.

The responsible designer for each work item is specified.

Through the design of research and development task flow, the work division cooperation mode of a designer aiming at a specific type of task can be solidified, and the work division cooperation mode can be clearly expressed and solidified in an information digitalization mode. The research and development task responsible personnel can carry out templated storage on a specific research and development workflow, and later-stage similar research and development tasks can be directly used. The development task workflow design interface is shown in FIG. 8.

1.3.2.4 work item entry List settings

The research and development task delivery lists in the product research and development workflow combing and decomposing are sorted and summarized to form a preliminary work item list, and the product research and development workflow sorting and compiling system has a work item input setting function and can complete functions of new construction, editing, query and the like of work item input parameters of products.

Each work item input data list can be files, parameters and the like, and principle model machine parameters can be bound.

For the input list of the work items, the user can define the work content of the work items, and the platform has the functions of adding, modifying and deleting the input list.

Newly adding an input data item: information such as the name of the input parameter, the type of the input parameter, the initial value of the input parameter, the unit, etc. can be defined. The input parameters can bind parameter data of the principle model.

Input data item modification: the input parameter item can modify the value of the input parameter and also can modify the name of the input parameter, but the data type cannot be modified because an explicit type is already defined when the data type is created. After each modification, there is a data version record.

Deletion of input data item: some input parameters are not required to be used for specific tasks and models, so that a person in charge can delete the input parameters.

1.3.2.5 work item delivery List settings

And a work item delivery list maintenance function is provided, the functions of creating, editing, inquiring and the like of a product work item delivery list are completed, and the work item delivery list is gradually improved through maintenance of a research and development task structure tree.

In the delivery list, each delivery data may be set to an explicit type. The method comprises a basic data type, an enumeration data type, an extension data type and a complex data type.

The basic data type: integer, boolean, real, date, file, string.

Enumerated types: the method can be flexibly defined according to the needs of users, such as: sex (Man, woman)

The extension type is as follows: for example, the extension can be performed according to the needs of the user, such as the extension of file types, CATIA files, PRO/E files and the like

Complex types: the data types which can be nested are defined according to the requirements of users, for example, the design requirement types of the plunger pump are defined: including length (real), width (real), height (real), weight (real), stigma type (enumeration).

When setting the data type of the delivered item, the user may select the data type that has already been set. As shown in fig. 9:

for the output list of the work items, the user can define the work content of the work items, and the platform has the functions of adding, modifying and deleting the deliverables.

Newly added output data items: information such as the name of the delivered product, the type of the delivered product, the initial value of the delivered product, and the unit can be defined. When newly adding the delivery data item, the system can automatically check the duplicate name of the delivered object and other problems.

Output data item modification: deliverable modification can modify the value of the deliverable as well as the name of the deliverable, but the data type cannot be modified because an explicit type is already defined at the time of creation. After each modification, there is a data version record.

Deletion of output data item: some delivery data items do not need to be submitted for a particular task and model, and therefore can be deleted by a person in charge.

1.3.2.6 work item task authorization

The system provides a fine authority Control function Based on RBAC (Role-Based Access Control) strategy, and a developer or authorized person of the development work task structure tree grants the work items to other persons in the project group to grant the authority of viewing or operating within the authority permission range of the developer or authorized person.

The research and development task responsible person can carry out fine-grained division on different personnel, such as data permission, data modification permission, data stream modification permission and the like. In order to facilitate task authorization, the system provides sharing type, strict type and self-defining type. And providing a structure tree authorization management function. Various authorization allocation modes can be predefined according to specific service forms (project types, project states, classified levels and the like, and specific requirements are detailed after investigation).

1.3.3 development task assignment

And constructing a completed research and development task structure tree and a research and development workflow, wherein the research and development task of the structure tree is sent to a work item responsible person. The principle of task assignment is determined according to the relation between the research and development tasks. The task issuing has two modes, namely, a task A starts and a task B starts again; and after the task A is finished, the task B is restarted. And the assignment of the tasks is carried out according to the states of the related tasks and the driving rules. After the research and development task is issued, the task responsible person can receive the task. The parallel and serial relation of the tasks is realized by setting the mode assigned to the tasks.

The system also supports manual issuing of research and development tasks, and project managers can appoint the research and development tasks to issue according to the progress of the project.

1.3.4 development task execution

After receiving a specific research and development work item task, a designer can start the work item task and can use a related tool flow or a research and development component to quickly complete the task.

1.3.4.1 development work item creation

The creation of the development task may be automatically created by receiving the development task or may be manually created.

(1) Task reception and creation

After the research and development task is issued, a user logs in the system and can receive the notification of the research and development work item task. The system can display the tasks to be handled in a classified mode in a list mode. The tasks of the to-be-processed research and development work items mainly comprise attributes such as task names, belonged items, states, plan starting time and plan ending time. The lowest level elements of the research and development tasks are called research and development work items, and the research and development work items are basic units for executing the model research and development tasks.

After the task is received by the task responsible person, the system automatically creates the research and development task according to the information of the research and development task, such as the responsible person, the planning start time, the planning end time, the delivery and the project information. The automatically created development work item task interface is as follows:

(2) task manual creation

Basic information of research and development work item tasks needs to be input: the starting time of the work item plan, and basic information such as task responsible persons, affiliated projects and models. In addition, the system has a flexible dynamic modeling function, and can quickly expand the attribute to be added to the work item information.

(3) Task delegation

After receiving the work item task, the work item responsible person provides an entrusting application according to the work item task and the work saturation, and other persons complete the content of the work item.

1.3.4.2 research and development work item query and early warning

Supporting the query in the states of the research and development work item tasks, such as the states of started, in progress and completed; the query of the record data of the relevant process of the research and development work item task is supported; the system can count project plans, project milestones and whether research and development work item tasks in node time of each research and development work flow can not be completed on time every day, the research and development work item tasks which are about to be overdue and unfinished in the plans can be pushed by system information to remind, related users and other responsible persons can remind that the research and development work item tasks are overdue in the set time, and early warning or warning rules are summarized and calculated by the system through past data or threshold values are set by users with authority.

1.3.4.3 work item task execution

After the research and development work item task is confirmed by the responsible person, the work item can be executed, and if the task is objected, the task responsible person can apply for task return. The designer enters the work item interface, as shown in FIG. 10:

through the work item interface, the basic information of the work item and the input and output requirements are known. And entering different research and development working areas according to the research and development components bound by the working items. The working area of the generic development component is shown in fig. 11.

In the process of executing research and development work, through an integrated development environment, a designer can obtain a corresponding template from a tool flow template library according to the content of a work item to complete a design simulation task, can also innovate a tool flow template, and executes a tool flow process after the setting parameters of tool components in the tool flow template are completed to obtain a corresponding work execution result. In addition, the relevant standard specification, data and design parameters can be used as knowledge to be pushed to the working area.

After the research and development work is executed, corresponding execution result data is generated in the research and development task structure tree. And generates a corresponding data version as shown in fig. 12.

1.3.4.4 work item task submission

The work item task can execute the work item task for multiple times according to the technical index requirements, and generate work item results of multiple versions. The design can select a proper data result from a plurality of versions of design results as an execution result of the work item to submit the work item task.

1.3.4.5 cooperating with data stream driving

The work items in the research and development task flow are automatically dispatched by a data flow driving engine. In the mode, each designer can clearly know own work items, data required by the designer is pushed to a desktop through a collaborative data stream, and each work item has a clear output list.

The whole product research and development process is embodied by the technical state change of each work item. The technical state of each work item consists of both version numbers (V1, V2, V3 …) and states (latest, to be updated, outdated). Each submission of a work item causes a change in the technical state of the work item and, at the same time, a change in the technical state of the associated work item.

The data flow driving engine senses the technical state change of the work items, can automatically update the technical state of the related work items and is informed to each product designer by the message engine.

In the product design stage, the submission mode of the designer work item task is selected from the following 4 modes, and the modes are suitable for different application scenes of design simulation work types:

taking the data relationship of the work items as shown in FIG. 13 as an example:

the data output by the designers responsible for the population will be used by the designs responsible for the aerodynamics and the ballistic, and the data output by the work items of the air profession will be used by the designers of the ballistic.

a. And (4) normal submission: and after the designer finishes the work, submitting the data and submitting the work items. After the work items are submitted, the technical state of the related work items can be automatically updated according to the circulation of the data flow. As shown in fig. 14:

b. and rolling back: after the designer submits the data and the work items, the designer finds that the data is wrongly modified, and returns the latest version to the previous data version

c. No need of updating: after the data of the work item at the upstream is updated, the work item is not affected, and the work item is submitted only by working without updating.

d. Feeding back upstream: after the data at the upstream is updated, the work item is subjected to redesign simulation, but obvious errors exist, and the data submitted by the responsible person of the work item at the upstream can be reminded to re-verify through upstream feedback operation.

1.3.5 development task submission

After the designers complete all the work item tasks of the research and development process, the task responsible person can submit the research and development task. And the task responsible person fills in the progress of the task and uploads the deliverables in the research and development task interface.

After the task is completed, the task can be submitted to a task affirmor for examination, and the task affirmor can evaluate the task completion condition (such as quality and progress).

1.3.6 development task monitoring

The research and development task monitoring is divided into multiple levels of monitoring, and rich chart functions are provided for managers to view the state of project progress from more angles. The method comprises the steps of monitoring the progress of a research and development task, repeating the research and development task, watching a board of the research and development task and the like.

1.3.6.1 development task progress monitoring

The development task progress monitor shows the stage and progress of the project in a Gantt chart mode.

The development process and the detailed information of the development process can be checked according to various dimensions of the current development process of different users or roles, the development process of departments and the development process of model products.

1.3.6.2 research and development task replication

And displaying the development process progress condition in the research and development task in a data pedigree diagram mode, and repeating the research and development task for multiple rounds of iteration detailed processes. The actor and the arrival time and execution time may be viewed in the design flow. And the specific design work progress is visually shown by marking in different colors.

1.3.6.3 research and development task board

The method provides rich task boards and data statistics functions, can conveniently and comprehensively understand and control the operation condition of the whole project through the boards, such as the percentage of completion of each task, the predicted completion time of the task, the current tasks of task managers, and the like, and is convenient for a decision maker to dynamically adjust the project task.

The platform provides a plurality of filtering condition input pages, and statistics and visual board output can be carried out according to a plurality of dimensions such as months, seasons, years, models, products, professionals and staff.

1.3.6.4 develop statistical report

The system provides rich report statistics functions, comprises various types such as column diagrams, pie charts, curve diagrams, line diagrams and the like in form, and can perform various statistics on different objects and object combinations such as personnel, tasks, task states, task attributes, deliveries and the like on statistical objects.

The platform provides a user-defined statistical function, implementers can perform related implementation work on the basis to complete customized statistical demands according to estimated data volume and data increment, and the platform provides two statistical modes.

Direct statistics: and when the total data amount of the system is small and the annual data growth amount is limited, the platform directly performs statistical operation in the current database, and queries a statistical result and graphically displays the statistical result by adopting functions such as aggregation and the like of SQL statements from each business table.

Off-line statistics: when the system data volume is large, the annual data growth is rapid, and the real-time requirement of statistics is not very high, the platform establishes an offline statistics service, periodically counts data from the business database, stores the statistics result in the offline statistics service, and acquires the counted result from the offline statistics service for visual display when the user uses the statistics function.

1) According to the model statistics

Counting the task quantities (including completed, unfinished and inactivated processes) of different models, and outputting a histogram; the abscissa is the model number and the ordinate is the task volume.

Counting the total task amount of all models which are finished, unfinished and inactivated, and outputting a pie chart

Counting the number of tasks of which the specified type is finished, unfinished and inactivated, and outputting a pie chart

2) By product statistics

Counting the task quantities (including completed, unfinished and inactivated processes) of different product codes, and outputting a histogram; the abscissa is the product code, and the ordinate is the task amount;

counting the total task amount of completed, unfinished and unactivated all the products, and outputting a pie chart

Counting the completed, unfinished and unactivated task amount of the specified product, and outputting a pie chart

3) Statistics by professional group

Counting the task quantities (including completed, unfinished and inactivated processes) of different professional groups, and outputting a histogram; the abscissa is professional group and the ordinate is task amount;

counting the total task amount of all professional groups which are finished, unfinished and inactivated, and outputting a pie chart

Counting the completed, unfinished and inactivated task amount of the designated professional group, and outputting a pie chart

4) Statistics by designer

Counting the task quantities (including completed, unfinished and inactivated flows) of different designers, and outputting a histogram; the abscissa is professional group and the ordinate is task amount;

and (4) counting the total task amount of all designers which are finished, unfinished and inactivated, and outputting a pie chart.

And counting the amount of tasks which are finished, unfinished and inactivated by a designated designer, and outputting a pie chart.

5) Statistics on planned completion rates

And (5) counting the plan completion rate of different designers.

While embodiments of the invention have been shown and described, it will be understood by those of ordinary skill in the art that: various changes, modifications, substitutions and alterations can be made to the embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the claims and their equivalents.