Server device, management information sharing method, and management information sharing program

Abstract

To provide a technique for handing over or selling a project management information activity plan so as to be reused with simple processing by others outside an organization, and receiving compensation for that.SOLUTION: A server device includes: a storage unit which stores one or more pieces of project management information for each of project managers; a management execution unit which displays, using a predetermined figure including an activity plan table, a chart or the like, and manages at least tasks or work items included in the project management information; a sale processing unit which sells any or a plurality of templates of the project management information to a user who requests purchase; and a project application unit which applies the templates of the project management information to a project of the user who requests purchase.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a server device, a management information sharing method, and a management information sharing program. [Background technology]

[0002] Patent Document 1 describes a creation system having a creation device and a terminal, the creation device comprising: an extraction unit that extracts, for each activity, electronic file information including a timestamp of each electronic file for identifying a work period and a folder name of the folder indicating the work item name from electronic files created for each work item constituting an activity of a predetermined period, the electronic files being stored in a folder created for each work item; a generation unit that generates a work schedule showing the work item name, the work period, and the work amount of each work item of the activity in chronological order using the work item name identified using the folder name, the work period identified using the timestamp, and the work amount identified using the number of electronic files stored in the folder; the terminal comprises: a creation unit that creates an activity plan table showing the work item name, the work period, and the work amount of each work item in chronological order using the generated work schedule when an input identifying a planned base date is received; and a correction unit that corrects the activity plan table when an input to change the work period is received. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2018-067090 A Summary of the Invention [Problem to be solved by the invention]

[0004] The above technique allows anyone within an organization to create a work schedule, but does not allow anyone outside the organization to create a work schedule.

[0005] An object of the present invention is to enable an organization to inherit and sell reusable activity plans to others outside the organization through simple processing, and to receive compensation for the same. [Means for solving the problem]

[0006] The present application includes a number of means for solving at least some of the above problems, examples of which are as follows: A server device according to one aspect of the present invention is characterized by comprising: a storage unit that stores one or more pieces of project management information for each project manager, a management execution unit that displays and manages at least the tasks or work items included in the project management information using predetermined diagrams such as activity plans or charts, a sales processing unit that sells one or more of the project management information templates to users who wish to purchase them, and a project application unit that applies the project management information templates to projects of the users who wish to purchase them.

[0007] In addition, in the above-mentioned server device, the sales processing unit may cause the project application unit to create activity plan information by applying a template for the project management information, and may exemplify the created activity plan information to the user who wishes to make a purchase.

[0008] In addition, in the above-mentioned server device, the sales processing unit may receive, before the sale is made, specified parameters that constitute a template activity plan for the project management information from the user who wishes to purchase, and the project application unit may create the activity plan information by applying the template for the project management information using the received specified parameters.

[0009] In addition, in the above server device, the project management information template may include one or more tasks and their dependent relationships, and the tasks may include one or more work items and their dependent relationships, and the project application unit, in a process of applying the project to the user who wishes to purchase, may assign working days and human resources to the work items in accordance with the dependent relationships of the work items and the tasks.

[0010] In addition, in the above-mentioned server device, when the sales processing unit receives a designation to exclude any one or more of the tasks and work items from being sold, it may exclude the tasks and work items together with the dependent relationships from being sold.

[0011] In addition, in the above-mentioned server device, when the sales processing unit receives a specification to keep any or more of the tasks and work items private before the sale is made, it may be configured to hide the contents of the tasks and work items in the examples of the activity plan information before purchase.

[0012] The server device may further include a sales approval section that does not approve a sale by the sales processing section if the project management information does not satisfy a predetermined condition.

[0013] In addition, the above-mentioned server device may be provided with a similarity determination unit which determines whether the project management information template is similar to other project management information templates being sold to a predetermined degree or more, and the sales approval unit may use the similarity determination unit to determine whether the template is similar to other project management information templates being sold to a predetermined degree or more, and if similar, not approve the sale by the sales processing unit.

[0014] In addition, in the above server device, the project application unit may add specified information to the project management information to which the project management information template purchased by the user who wishes to purchase has been applied, and the sales approval unit may not approve the sale by the sales processing unit of the project management information template to which the specified information has been added.

[0015] In addition, a management information sharing method according to another embodiment of the present invention is a management information sharing method using a server device, the server device comprising a memory unit that stores one or more project management information for each project manager, and a processing unit, the processing unit carrying out a management execution procedure that displays and manages at least the tasks or work items included in the project management information using a predetermined diagram such as an activity plan or chart, a sales processing procedure that sells one or more of the project management information templates to users who wish to purchase them, and a project application procedure that applies the project management information templates to a project of the user who wishes to purchase them.

[0016] In addition, a management information sharing program according to another embodiment of the present invention is a management information sharing program that shares management information using a server device, the server device having a memory unit that stores one or more project management information for each project manager, and a processing unit, and is characterized in that the processing unit executes a management execution procedure that displays and manages at least the tasks or work items included in the project management information using a specified diagram such as an activity plan or chart, a sales processing procedure that sells one or more of the project management information templates to users who wish to purchase them, and a project application procedure that applies the project management information templates to a project of the user who wishes to purchase them. Effect of the Invention

[0017] According to the present invention, it is possible to provide a technology that enables a project management information action plan to be inherited and sold to others outside an organization in a reusable manner with simple processing, and that enables a fee to be received.

[0018] Problems, configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0019] [Figure 1] 1 is a configuration diagram of a management information sharing system according to an embodiment. [Diagram 2] FIG. 4 is a diagram illustrating an example of a data structure of user information. [Diagram 3] FIG. 13 illustrates an example of a data structure of execution project management information. [Figure 4] FIG. 4 illustrates an example of a data structure of task information. [Diagram 5] FIG. 13 illustrates an example of a data structure of work item information. [Figure 6] FIG. 4 is a diagram illustrating an example of a data structure of member information. [Figure 7] FIG. 13 is a diagram illustrating an example of a data structure of sales template information. [Figure 8] FIG. 2 illustrates an example of a hardware configuration of a management information sharing server. [Figure 9] FIG. 13 is a diagram illustrating an example of a template purchasing flow. [Figure 10] FIG. 13 is a diagram showing an example of a template list screen. [Figure 11] FIG. 13 is a diagram showing an example screen of an example activity plan. [Figure 12] FIG. 13 is a diagram illustrating an example of a template usage flow. [Figure 13] FIG. 13 is a diagram illustrating an example of a sales template generation flow. [Figure 14] FIG. 13 is a diagram showing an example of a template editing screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] A management information sharing system 1 to which an embodiment according to one aspect of the present invention is applied will be described below with reference to the drawings. In the following embodiment, when necessary for convenience, the description will be divided into a number of sections or embodiments, but unless otherwise specified, they are not unrelated to each other, and one is a partial or complete modification, detail, supplementary explanation, etc. of the other.

[0021] In addition, in the following embodiments, when referring to the number of elements (including the number, numerical values, quantities, ranges, etc.), unless specifically stated or clearly limited to a specific number in principle, the number is not limited to that specific number and may be more than or less than a specific number.

[0022] Furthermore, in the following embodiments, the components (including element steps, etc.) are not necessarily essential unless specifically stated otherwise or unless clearly considered essential in principle.

[0023] Similarly, in the following embodiments, when referring to the shapes, positional relationships, etc. of components, etc., unless otherwise specified or considered to be obviously different in principle, it includes those that are substantially similar or similar to the shapes, etc. The same applies to the above numerical values ​​and ranges.

[0024] In addition, in all the drawings for explaining the embodiments, the same members are generally given the same reference numerals, and repeated explanations thereof will be omitted.

[0025] In recent years, with the spread of networks and various electronic devices (personal computers, tablet devices, smartphones, etc.), information including various know-how that was previously kept secret or shared only with a select few is becoming public. For example, anyone can easily share efficient methods known as "life hacks." However, most of these hacks are simple, personal, and general methods, and those that are complex and highly individualized and involve special skills are not widely used. On the other hand, in corporate activities, tasks such as project management require a huge amount of personal ability and experience to be carried out efficiently, and the environments surrounding projects are also diverse, so the content that is shared publicly is often limited to generalities.

[0026] Therefore, in an embodiment of the present invention, a management information sharing system 1 is used that allows efficient means for projects, etc. (for example, not limited to projects, but including general activity plans and goal management for individuals and organizations) to be easily made public to others, the made public management means to be easily used, and the made public management information to be exchanged for monetary value as compensation for the disclosure.

[0027] 1 is a configuration diagram of a management information sharing system according to this embodiment. In the management information sharing system 1, a seller who sells management information uses a management information shared server 100 and a selling terminal 200 communicatively connected to the management information shared server 100 via a communication path 50. A purchaser who purchases management information uses the management information shared server 100 and a purchasing terminal 300 communicatively connected to the management information shared server 100 via the communication path 50.

[0028] For example, the management information shared server 100 may be a cloud computer connected via the Internet, or a server device managed by the owner of the management information shared server 100. The selling terminal 200 and the purchasing terminal 300 may be a seller's and a purchasing terminal's PC (Personal Computer), a tablet terminal, a smartphone terminal, or the like. Furthermore, without being limited to this, a wearable device such as a smart watch or smart glasses of a user may be used as the selling terminal 200 and the purchasing terminal 300. Note that the seller and the purchasing terminal are the roles played in one transaction of management information, and the seller may be the purchasing party in another situation, and the purchasing party may be the seller.

[0029] When the management information shared server 100 communicates with the seller terminal 200 and the purchaser terminal 300, they are connected via a communication path 50 which is a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, a mobile phone network, short-distance wireless communication such as Bluetooth (registered trademark), or a combination of these. The communication path 50 may be a VPN (Virtual Private Network) on a wireless communication network such as a mobile phone network.

[0030] By using the management information sharing system 1, it is possible for others to inherit the project management information so that it can be reused. Specifically, when the purchaser inputs the project management information to be purchased and payment at the purchaser terminal 300, the payment is made at the management information sharing server 100, and if the payment is successful, an incentive according to the purchase amount is given to the seller. Note that the incentive may be, for example, cash, savings, coupons that can be used as cash equivalents, electronic money, virtual currency, or other types of convertible voucher information, but is not limited to these and may also be other objects or assets.

[0031] The management information shared server 100 includes a storage unit 110, a processing unit 120, and a communication unit 150, which are communicatively connected to one another via a bus or the like.

[0032] The storage unit 110 includes user information 111, execution project management information 112, task information 113, work item information 114, member information 115, and sales template information .

[0033] 2 is a diagram showing an example of a data structure of user information. The user information 111 stores a plurality of people who are responsible for managing and executing projects as users. The user information 111 includes a user ID 111A, a user name 111B, an email address 111C, and a password 111D.

[0034] User ID 111A is information that distinguishes a user from other users. A user who plays the role of an administrator or an executive member for a certain project is registered in user information 111. User name 111B is information that identifies the user's name (not limited to real name, but also possible nickname, abbreviation, self-proclaimed name, etc.). Email address 111C is email address information that can be used to contact the user. Password 111D is a password for logging in by the user.

[0035] 3 is a diagram showing an example of a data structure of the execution project management information. The execution project management information 112 is project management information managed by each project manager. The execution project management information 112 includes a project ID 112A, a name 112B, a manager 112C, a start / end date 112D, a status 112E, and a basic project 112F.

[0036] Project ID 112A is information that identifies the project. Name 112B is information about the nickname of the project. Manager 112C is information that identifies the user that manages the project. Start / End Date 112D is information that identifies the project start date and end date, that is, the date when the project's activity plan starts and the date when the activity plan ends. Status 112E is information about the project's status (information that can at least identify whether the project is completed or not). Base Project 112F is information that identifies the execution project that was the basis for the project template that was applied when creating the management information for the project.

[0037] 4 is a diagram showing an example of the data structure of task information. Task information 113 is information on a task included in a project. In this embodiment, a task refers to an operation performed by one or more members among the operations to be performed. Task information 113 includes a task ID 113A, a project 113B, a task name 113C, a person in charge 113D, a content 113E, a due date 113F, a priority 113G, a status 113H, a preceding task 113J, and a succeeding task 113K.

[0038] The task ID 113A is information for distinguishing a task from other tasks. The project 113B is information for identifying a project (execution project) managed by the execution project management information to which the task belongs. The task name 113C is information for the nickname of the task. The person in charge 113D is information for identifying one or more users as members who can execute the task. The content 113E is information for reference information such as the work to be performed in the task, necessary facilities, environment, and procedure manuals. The due date 113F is information for identifying the due date for completing the task. The priority 113G is information indicating the degree to which execution should be prioritized over other tasks. The status 113H is information on the status of the task (at least information for identifying whether the task is completed or not, preferably information for identifying the degree of progress, related issues, etc.). The preceding task 113J is information for identifying a task that needs to be completed prior to the task. The succeeding task 113K is information for identifying another task that requires the completion of the task as a starting condition.

[0039] FIG. 5 is a diagram showing an example of the data structure of work item information. Work item information 114 is information on work items included in a task. In this embodiment, a work item refers to a task that is performed by one member among the tasks that constitute a task. However, the relationship between an execution project, a task, and a work item is not limited to this example, and may be, for example, a relationship between a major goal, a mid-level goal to be achieved in order to achieve the major goal, and a sub-goal to be achieved in order to achieve the mid-level goal, or a relationship between a result, a goal for each technical field to obtain the result, and a specific task to achieve the goal. The work item information 114 includes a work item ID 114A, a task 114B, an item name 114C, a person in charge 114D, a content 114E, man-hours 114F, a priority 114G, a status 114H, a preceding task 114J, and a succeeding task 114K.

[0040] The work item ID 114A is information that distinguishes the work item from other work items. The task 114B is information that identifies the task information to which the work item belongs. The task information includes one or more work items and the dependencies of the work items. The item name 114C is information on the nickname of the work item. The person in charge 114D is information that identifies the user information that performs the work item from among the users included in the person in charge of the task information. The content 114E is information on the work to be performed in the work item and reference information such as the necessary equipment, environment, and procedure manual. The labor hours 114F is information that identifies the labor hours required for the work item. The priority 114G is information that indicates the degree to which execution should be prioritized over other work items. The status 114H is information on the status of the work item (at least information that can identify whether it is completed or not, and preferably information that identifies the degree of progress, related issues, etc.). The preceding work 114J is information that identifies a work item that needs to be completed prior to the work item. The succeeding task 114K is information that identifies another task item that requires the completion of the task item in its starting condition.

[0041] 6 is a diagram showing an example of the data structure of member information. Member information 115 stores a plurality of people who play roles participating in an execution project as members. Member information 115 includes member ID 115A, user 115B, project 115C, man-hours 115D, and holidays 115E.

[0042] The member ID 115A is information for distinguishing a member of an active project from other users. The user 115B is information for registering a user who participates in some active project as a member who provides human resources to the active project.

[0043] Project 115C is information for identifying an active project to which a member will provide human resources. Man-hours 115D is information for identifying the amount of human resources a member will provide to an active project. Days off 115E is information for identifying days on which a member will not provide human resources to an active project.

[0044] 7 is a diagram showing an example of the data structure of sales template information. Sales template information 116 stores one or more tasks / work items and the dependencies of the tasks / work items as templates among the information constituting the execution project management information. In addition, sales template information 116 includes information such as sales explanations and sales price required for selling the sales template. Sales template information 116 includes sales ID 116A, reference project 116B, sales name 116C, seller 116D, price 116E, product description 116F, task / work items 116G, sales excluded task / work items 116H, and private task / work items 116J.

[0045] The sales ID 116A is information that distinguishes the sales template from other sales templates. The reference project 116B is information that identifies the execution project (basic project) that is the basis of the sales template. The sales name 116C is information that identifies the name of the sales template. The seller 116D is information that identifies the user information of the person who sells the sales template. The price 116E is information that identifies the sales price of the sales template. The product description 116F is an explanation of the sales template (e.g., presentation information) for users who wish to purchase the sales template. The tasks and work items 116G are information that identifies the tasks and work items included in the sales template and their predecessor-successor relationships. The sales excluded tasks and work items 116H are information that identifies the tasks and work items included in the execution project management information and that are excluded from the sales template. The non-disclosed tasks and work items 116J are information that identifies tasks and work items that are included in the execution project management information and the sales template and that are not to be disclosed before the sale.

[0046] The processing unit 120 includes a management execution unit 121 , a sales processing unit 122 , a settlement unit 123 , a project application unit 124 , a sales approval unit 125 , and a similarity determination unit 126 .

[0047] The management execution unit 121 manages progress information for projects that are being implemented, are being implemented, or have been implemented. For example, the management execution unit 121 provides the manager and members of the project with so-called project management functions, such as updating the status of the project, listing tasks and work items to be executed, or displaying an activity plan (activity plan information) to be executed using a predetermined diagram such as a Gantt chart.

[0048] The sales processing unit 122 sells one or more templates (sales template information 116) of project management information (execution project management information 112) to users who wish to purchase. The sales processing unit 122 also causes the project application unit 124 to create activity plan information by applying the template of the project management information, and presents an example of the created activity plan information to users who wish to purchase. The sales processing unit 122 also receives, before the sale is carried out, predetermined parameters constituting the activity plan of the sales template of the execution project management information from the users who wish to purchase. The predetermined parameters constituting the activity plan include, but are not limited to, the amount of human resources that members can invest in the execution project (for example, the work hours (man-hours) that can be invested per day), the number of members, the start date, the end date, etc.

[0049] Furthermore, when the sales processing unit 122 receives a designation to exclude one or more of the tasks and work items included in the project management information from the sale, it excludes the tasks and work items together with their dependencies from the sale. Furthermore, when the sales processing unit 122 receives a designation to keep one or more of the tasks and work items included in the project management information private before the sale is carried out, it hides the contents of the tasks and work items.

[0050] The settlement unit 123 transfers money from the purchaser's account to a specified account according to the sales amount of the purchased template. The settlement unit 123 transfers money through a remittance means according to the type of the sales amount (for example, cash, deposits, coupons that can be used as cash equivalents, electronic money, virtual currency, and other types of convertible voucher information).

[0051] The project application unit 124 applies the template of the execution project management information and the received parameters to the project in the automatic planning process of the activity plan in the management execution unit 121 (part of the template usage flow described later) and the process of illustrating the activity plan information for the user who wishes to purchase the template of the execution project management information. The project application unit 124 may use default parameters (predetermined initial values) in creating the activity plan information. The project application unit 124 determines the work date of the work item according to the dependency relationship between the work item and the task for the work item, and allocates human resources. Specifically, the project application unit 124 derives a critical path by constructing an arrow diagram or the like according to the dependency relationship between the tasks and the work items, and for the work items on the critical path, prioritizes the member who can input the most man-hours as the person in charge and assigns the earliest possible date as the work day, thereby efficiently allocating the human resources of the members. In addition, the project application unit 124 adds specified information (the name or project ID of the project that is the basis of the applied template) as basic project information to the executed project management information to which the template for project management information purchased by the user who wishes to purchase is applied.

[0052] If the execution project management information 112 does not satisfy predetermined conditions, the sales approval unit 125 does not approve the sale by the sales processing unit 122. The sales approval unit 125 also uses the similarity determination unit 126 to determine whether the template for sale is similar to other templates for sale by a predetermined amount or more, and if it is similar, does not approve the sale by the sales processing unit 122. The sales approval unit 125 also does not approve the sale by the sales processing unit 122 of execution project management information to which predetermined information (basic project name or basic project ID) has been added, that is, a template of an execution project to which a purchased template has been applied (prevention of resale).

[0053] The similarity determination unit 126 determines whether the sales template of the execution project management information is similar to other sales templates that are already on the market by a predetermined amount or more. For example, the similarity determination unit 126 may determine that execution projects that have approximately the same number of tasks, number of work items, number of dependencies, etc. included in the execution project management information 112 are similar to each other. Alternatively, the similarity determination unit 126 may determine that execution projects that have approximately the same keywords included in the tasks and work items included in the execution project management information 112 are similar to each other. Furthermore, without being limited to this, the similarity determination unit 126 may be something similar to so-called artificial intelligence, such as a classifier that has learned using multiple pieces of execution project management information as learning data.

[0054] The communication unit 150 communicates via a communication path 50 with the seller terminal 200, the buyer terminal 300, and other terminals that communicate via the Internet.

[0055] The sales terminal 200 includes a communication unit 210, a processing unit 220, an input unit 230, and a display unit 240, which are communicatively connected to one another via a bus or the like.

[0056] The communication unit 210 communicates with the management information shared server 100 and other terminals that communicate with each other via the Internet via the communication path 50. For example, the communication unit 210 transmits input information to the management information shared server 100.

[0057] The processing unit 220, like a web browser, constructs access information to the management information shared server 100 and sends a request to the management information shared server 100, receives a response from the management information shared server 100, constructs presentation information, and displays it on the display unit 240.

[0058] The input unit 230 accepts input from a user. For example, the input unit 230 accepts various types of input, such as various contact inputs, such as typing, touching, or flick input, or eye gaze input.

[0059] The display unit 240 outputs information to a user. The information to be output includes various types of output information such as screens, forms, and presentation information.

[0060] The purchase side terminal 300 includes a communication unit 310, a processing unit 320, an input unit 330, and a display unit 340, which are communicatively connected to one another via a bus or the like.

[0061] The communication unit 310 communicates with the management information shared server 100 and other terminals that communicate via the Internet via the communication path 50. For example, the communication unit 310 transmits input contents to the management information shared server 100.

[0062] The processing unit 320, like a web browser, constructs access information to the management information shared server 100 and sends a request to the management information shared server 100, receives a response from the management information shared server 100, constructs presentation information, and displays it on the display unit 340.

[0063] The input unit 330 accepts input from a user. For example, the input unit 330 accepts various types of input, such as various contact inputs, such as typing, touching, or flick input, or various types of inputs, such as gaze input.

[0064] The display unit 340 outputs information to the user. The information to be output includes various types of output information such as screens, forms, and presentation information.

[0065] 8 is a diagram showing an example of the hardware configuration of a management information shared server. The management information shared server 100 has a hardware configuration realized by the housing of a so-called server device, a workstation, a personal computer, a smartphone, or a tablet terminal. The management information shared server 100 has a processor 101, a memory 102, a storage 103, an input device 104, a display device 105, a communication device 106, and a bus connecting each device.

[0066] The processor 101 is an arithmetic device such as a central processing unit (CPU) or a graphics processing unit (GPU).

[0067] The memory 102 is a memory device such as a RAM (Random Access Memory).

[0068] The storage 103 is a non-volatile storage device capable of storing digital information, such as a so-called hard disk drive, a solid state drive (SSD), or a flash memory.

[0069] The input device 104 is a device that accepts input from one or more of a keyboard, a mouse, a touch panel, and a microphone. The display device 105 is a device that displays one or more of various output devices such as an organic EL (Electro-Luminescence) display.

[0070] The communication device 106 is a network interface card (NIC) or the like that communicates with other devices via a network.

[0071] The selling terminal 200 and the purchasing terminal 300 also have substantially the same hardware configuration as the management information shared server 100 .

[0072] The processing unit 120, management execution unit 121, sales processing unit 122, settlement unit 123, project application unit 124, sales approval unit 125, and similarity determination unit 126 of the management information shared server 100 described above are realized by a program that causes the processor 101 to perform processing. This program is stored in the memory 102, storage 103, or a ROM device (not shown), and is loaded onto the memory 102 when executed and executed by the processor 101.

[0073] Moreover, the storage unit 110 of the management information shared server 100 is realized by the memory 102 and the storage 103. Moreover, the communication unit 150 is realized by the communication device 106. An example of the hardware configuration of the management information shared server 100 has been described above.

[0074] The configuration of the management information shared server 100 can be further divided into components according to the processing content, or can be divided so that one component executes even more processing.

[0075] Furthermore, each processing unit (management execution unit 121, sales processing unit 122, settlement unit 123, project application unit 124, sales approval unit 125, and similarity determination unit 126) may be constructed with dedicated hardware (ASIC, GPU, etc.) for realizing each function. Furthermore, the processing of each processing unit may be executed by one piece of hardware or by multiple pieces of hardware.

[0076] Next, the operation of the management information sharing system 1 in this embodiment will be described.

[0077] 9 is a diagram showing an example of a template purchase flow. The template purchase flow starts when a purchaser requests a sales list from management information shared server 100 at purchaser terminal 300 when purchasing a template for a project (step S001).

[0078] The sales processing unit 122 extracts a sales template (step S002). Specifically, the sales processing unit 122 extracts a template included in the sales template information 116.

[0079] Then, the sales processing unit 122 transmits to the purchase side terminal 300 display information including a template list that lists the extracted sales templates.

[0080] The processing unit 320 receives a selection input from the input unit 330 of any one of the templates included in the template list (step S003), and transmits a template display request to the management information shared server 100 (step S004).

[0081] The sales processing unit 122 causes the project application unit 124 to process and create the activity plan information included in the execution project that is the basis of the sales template, and exemplifies it (step S005). Here, the project application unit 124 creates the activity plan information using default parameters (predetermined initial values) set in the sales template. Note that, when the sales processing unit 122 receives a designation to make any or more of the tasks and work items private before the sale is carried out, it hides the contents of the tasks and work items. The tasks and work items designated to be private are the tasks and work items included in the private tasks / work items 116J of the sales template information 116.

[0082] The processing unit 320 displays the example activity plan, accepts input of predetermined parameters by the input unit 330 (step S006), and transmits a sample correction request to the management information sharing server 100 (step S007). For example, the input unit 330 accepts input of the amount of human resources (man-hours) that a member will provide to the execution project, the number of members, the start date, and the end date as parameters.

[0083] The sales processing unit 122 receives the transmitted parameters, and uses the received parameters in the project application unit 124 to apply the sales template in the execution project management information to process and create activity plan information, thereby correcting and illustrating the activity plan example (step S008). For example, if the execution project on which the sales template was based was carried out by two members, if the user who wishes to purchase the project has four project members, the activity plan may be significantly different, such as being half the period.

[0084] The processing unit 320 displays the revised example activity plan, accepts input of a predetermined purchase request and payment information by the input unit 330 (step S009), and transmits a purchase request to the management information shared server 100 (step S010).

[0085] The settlement unit 123 transfers the settlement process associated with the purchase to an external settlement service 10 (step S011). The settlement service 10 transfers the sales amount to the user's account through a remittance means according to the type of payment (for example, cash, savings, coupons that can be used as cash equivalents, electronic money, virtual currency, and other types of convertible voucher information) (step S012). Note that, when direct transactions are permitted, the settlement service 10 may transfer the money to the seller's account. The settlement unit 123 may not only perform settlement using the external settlement service 10, but may also perform settlement processing using the management information shared server 100's own settlement module.

[0086] Then, the settlement unit 123 checks whether the settlement has been successful (step S013), and if successful, the sales processing unit 122 associates the purchased template with the purchaser (step S014). For example, the sales processing unit 122 records the sales ID of the purchased template in association with the purchaser's user ID, and makes it available when generating an execution project. The sales processing unit 122 transfers default parameters (predetermined initial values) from the template for sale to the sold template. The default parameters may include members and their available man-hours, holidays, and persons in charge of each task.

[0087] The above is an example of a template purchase flow. According to the template purchase flow, a user who wishes to purchase a template can purchase a sales template sold by a seller and make it applicable to an execution project.

[0088] Fig. 10 is a diagram showing an example of a template list screen. Template list 370 is an example of a screen displayed on purchaser terminal 300 in step S003 of the template purchase flow. Template list 370 includes a plurality of templates for sale, and for example, in Fig. 10, template 371 for "First Web Application" and template 372 for "Web Application Infrastructure Construction" are displayed. Template list 370 may also include templates for sale of projects related to fields of interest of the user who wishes to purchase, as recommended projects 373, according to the purchase history and attributes of the user.

[0089] FIG. 11 is a diagram showing an example of a screen of an example of an activity plan. The example of an activity plan 380 is an example of a screen displayed on the purchase side terminal 300 in steps S006 and S009 of the template purchase flow. The example of an activity plan 380 includes a parameter reception area 381 that receives input of the number of members and the amount of human resources (man-hours) that the members provide to the execution project as changeable parameters, and a Gantt chart 382 based on the execution project. Note that the hidden work items 383 are displayed in a blurred state so that the details cannot be read. Furthermore, tasks or work items that are excluded from the sale are also excluded from the example of the activity plan. In the case of an example in which the activity plan has been modified, the Gantt chart 382 is changed to a chart based on the parameters received in the parameter reception area 381 and displayed.

[0090] 12 is a diagram showing an example of a template usage flow. The template usage flow starts when a purchaser uses a sales template to generate an execution project and requests the management information shared server 100 to generate execution project management information at the purchaser terminal 300 (step S101).

[0091] The management execution unit 121 generates a parameter setting screen (step S102). The parameter setting screen prompts the manager of the execution project to input parameters such as a template to be applied to the execution project, members and their available man-hours, holidays, and the person in charge of each task, and accepts the input. If default parameters are set in the template to be applied, the parameter setting screen may display the default parameters as the initial values ​​of each input as part of the input support. This reduces the hassle of inputting information for the manager of the execution project.

[0092] The processing unit 320 displays a parameter setting screen, accepts input of predetermined parameters by the input unit 330 (step S103), and transmits an instruction to generate execution project management information to the management information shared server 100 (step S104).

[0093] The project application unit 124 receives the transmitted parameters, and if a template is specified in the execution project management information, applies the template and creates tasks, work items, and activity plan information (step S105).Then, the project application unit 124 stores the basic project ID that is the basis of the applied template in the basic project 112F of the execution project management information 112.

[0094] If the tasks and work items included in the template include specifications for their dependency relationships (predecessor-successor relationships and inclusion relationships), priority, work item contents, etc., the project application unit 124 creates activity plan information taking these into consideration. Specifically, the project application unit 124 determines the order of tasks and work items with respect to dependency relationships and priority so as to prevent deadlocks and unnecessary waiting times. Also, if the accepted parameters include specifications for members, the number of man-hours they can input, and holidays, the project application unit 124 creates activity plan information using the relevant human resources.

[0095] Then, the management execution unit 121 generates an editing screen (step S106). The editing screen prompts the project manager to input corrections to parameters for correcting the execution project, such as tasks and work items, their dependencies (predecessor-successor relationships and inclusion relationships), members and their available man-hours, holidays, priorities, and people in charge of work items, and accepts the inputs. For example, if the activity plan is tighter than expected, the input is accepted to adjust the man-hours that members can put in to reduce their workload, or to change the people in charge of tasks or work items in consideration of the members' skill sets.

[0096] The processing unit 320 displays an editing screen, accepts input of predetermined parameters by the input unit 330 (step S107), and transmits an instruction to correct the execution project management information to the management information shared server 100 (step S108).

[0097] The project application unit 124 accepts the transmitted parameters and modifies the tasks, work items, and activity plan information (step S109). For example, if there are changes in the tasks and work items included in the execution project, their dependencies (predecessor-successor relationships and inclusion relationships), members and their available man-hours, holidays, priorities, and people in charge of each task, the project application unit 124 forcibly modifies the work of the people in charge and reassigns the tasks and activity plans of the workers to prevent inconsistencies (for example, to prevent two work items from being performed at the same time).

[0098] The above is an example of a template usage flow. According to the template usage flow, a user who has purchased a sales template can apply the purchased template to an actual project. In addition, in order to better fit the actual project management information to which the sales template has been applied, the user can revise the activity plan by adjusting parameters, including human resources.

[0099] 13 is a diagram showing an example of a sales template generation flow. The sales template generation flow starts when a user who wishes to sell generates a sales template and requests the management information shared server 100 to complete execution project management information at the sales terminal 200 (step S201).

[0100] The management execution unit 121 changes at least the status of the execution project management information related to the execution project requested to be completed to "completed" (step S202). Note that the management execution unit 121 may also process other processes associated with the completion of the execution project in conjunction with the change of the status to "completed."

[0101] Then, the sales processing unit 122 generates a template sales intention input screen (step S203). The template sales intention input screen prompts the manager of the completed execution project to input whether or not he / she intends to sell the tasks and work items, and their dependencies (predecessor-successor relationships and inclusion relationships) to others (users who wish to purchase them), and accepts the input.

[0102] The processing unit 220 displays a template sales intention input screen, accepts input of the specified sales intention and payment information such as account information and wallet information for receiving the sales consideration via the input unit 330 (step S204), and transmits a report of the sales intention to the management information shared server 100 (step S205).

[0103] When the sales processing unit 122 receives the sales intention, it creates sales template information 116 (step S206). Specifically, the sales processing unit 122 generates the sales template information 116 using the execution project management information 112 of the target project. For example, the sales processing unit 122 complements the reference project 116B with the project ID of the target execution project, complements the seller 116D with the user ID of the manager of the execution project, and complements the task / work item 116G with the task information 113 and work item information 114 included in the execution project management information. In addition, the sales processing unit 122 copies the parameters of the original execution project and sets them in the sales template. The parameters to be set may include the members and their available man-hours, holidays, and the person in charge of each task.

[0104] The sales processing unit 122 generates a template editing screen (step S207). The template editing screen prompts and accepts input from a user who wishes to sell a template for sale regarding tasks and work items, their dependencies (predecessor-successor relationships and inclusion relationships), at least whether they are for sale or not, and whether they are to be made public before the sale. In addition, the template editing screen prompts and accepts input from a user who wishes to sell regarding the sales name of the template for sale, the sales price, and presentation information that explains the template for sale to users who wish to purchase it.

[0105] The processing unit 320 displays a template editing screen, accepts information entered on the template editing screen by the input unit 330 (step S208), and upon accepting an instruction to make a publication application (sales application), sends an instruction to modify the sales template to the management information shared server 100 (step S209).

[0106] The sales processing unit 122 applies at least the inputs of whether to sell or not and whether to make the sales template public before the sale, the sales name of the sales template, the sales price, and the presentation information for explaining the sales template to the user who wishes to purchase the template at the time of sale to the editing contents received from the user who wishes to sell, that is, the tasks and work items, and their dependencies (predecessor-successor relationships and inclusion relationships), to modify the sales template (step S210). Specifically, the sales processing unit 122 uses the input information to complement the sales name 116C, the price 116E, the product description 116F, the tasks and work items excluded from sales 116H, and the private tasks and work items 116J. The sales processing unit 122 also replaces the parameters of the original execution project with default parameters (predetermined initial values) and sets them in the sales template.

[0107] Then, the sales approval unit 125 performs an approval process to determine whether the revised sales template satisfies a predetermined condition (step S211). If the predetermined condition is not satisfied, the sales approval unit 125 does not approve the sale by the sales processing unit 122. For example, the sales approval unit 125 determines whether the template is similar to other sales templates being sold by the similarity determination unit 126 to a predetermined degree or more, and if similar, does not approve the sale by the sales processing unit 122. Furthermore, the sales approval unit 125 does not approve the sale by the sales processing unit 122 of the execution project management information to which predetermined information (basic project name or basic project ID) has been added, that is, the template of the execution project to which the purchased template has been applied.

[0108] Then, the sales processing unit 122 stores the sales template approved for sale by the sales approval unit 125 in the sales template information 116. Note that the sales templates stored in the sales template information 116 are not limited to those approved for sale by the sales approval unit 125, and may be those approved for sale by a separate administrator of the management information sharing system 1, etc.

[0109] The above is an example of a sales template creation flow. With this sales template creation flow, the project manager can create a sales template from a completed execution project. In addition, the sales template can be edited before the sale to match the desired sales method and sales content.

[0110] 14 is a diagram showing an example of a template editing screen. The template editing screen 390 is an example of a screen displayed on the sales terminal 200 in step S208 of the sales template generation flow. The template editing screen 390 includes a sales promotion information input area 391 for receiving input of the sales name of the sales template and presentation information for explaining the sales template to users who wish to purchase the template, a sales content editing area 392 for receiving the removal of tasks / work items from the sale target and the non-disclosure before the sale, a sales condition editing area 395 for the sales price, discount rate, publication date and time, etc., and a disclosure application instruction input area 396. The sales content editing area 392 includes a non-disclosure designation button 393 for receiving the selection of tasks / work items to be made non-disclosure before the sale, and a check box 394 for receiving an instruction to remove them from the sale target. The disclosure application instruction input area 396 accepts input as an instruction to make a disclosure application (sales application) and transmits an instruction to amend the sales template to the management information shared server 100 .

[0111] The above is the management information sharing system 1. As in the above embodiment, according to the management information sharing system 1, it is possible to inherit and sell a project management information action plan in a reusable manner even to a third party outside the organization with a simple process, and to receive compensation for the same.

[0112] The present invention is not limited to the above embodiment. The above embodiment can be modified in various ways within the scope of the technical concept of the present invention. For example, in the above embodiment, the management information shared server 100 settles via an external settlement service 10, but this is not limited to this. For example, settlement may be made by issuing local points or various vouchers issued by a specific business entity. In this case, it is possible to reduce the fee.

[0113] Furthermore, the functions of the management information shared server 100 may be realized by a cloud service configured with one or more computers.

[0114] Furthermore, the technical elements of the above-described embodiments may be applied independently, or may be divided into a plurality of parts, such as program parts and hardware parts, and then applied.

[0115] The present invention has been described above mainly with reference to the embodiment. [Explanation of symbols]

[0116] 1 Management information sharing system, 50 Communication path, 100 Management information sharing server, 110 Storage unit, 111 User information, 112 Project execution management information, 113 Task information, 114 Work item information, 115 Member information, 116 Sales template information, 120 Processing unit, 121 Management execution unit, 122 Sales processing unit management unit, 123... settlement unit, 124... project application unit, 125... sales approval unit, 126... similarity determination unit, 150... communication unit, 200... selling side terminal, 210... communication unit, 220... processing unit, 230... input unit, 240... display unit, 300... purchasing side terminal, 310... communication unit, 320... processing unit, 330... input unit, 340... display unit.

Claims

1. a storage unit for storing one or more pieces of project management information for each project manager; a management execution unit that displays and manages at least the tasks or work items included in the project management information using a predetermined diagram, such as an activity plan or chart; a sales processing section that sells one or more of the templates for project management information to users who wish to purchase the templates; a project application unit that applies the template of the project management information to a project of the user who desires to purchase the project; A server device comprising:

2. 2. The server device according to claim 1, the sales processing unit causes the project application unit to create activity plan information by applying a template of the project management information, and presents an example of the created activity plan information to the user who wishes to make a purchase; A server device comprising:

3. 3. The server device according to claim 2, the sales processing unit receives, before the sale is carried out, from the user who desires to purchase, predetermined parameters constituting a template activity plan for the project management information; the project application unit uses the received predetermined parameters to apply a template of the project management information to create the activity plan information; A server device comprising:

4. The server device according to any one of claims 1 to 3, the project management information template includes one or more tasks and dependencies of the tasks; The task includes one or more work items and dependencies of the work items; the project application unit, in a process of applying the project to the user who desires to purchase, assigns work dates and human resources to the work items according to dependencies between the work items and the tasks; A server device comprising:

5. 5. The server device according to claim 4, When the sales processing unit receives a designation to exclude one or more of the tasks and the work items from the sale, the sales processing unit excludes the tasks and the work items from the sale together with the dependencies. A server device comprising:

6. 3. The server device according to claim 2, When the sales processing unit receives a designation to make any one or more of the tasks and the work items private before the sale is carried out, the sales processing unit makes the contents of the tasks and the work items hidden in the example of the activity plan information before the purchase. A server device comprising:

7. The server device according to any one of claims 1 to 3, a sales approval unit that does not approve a sale by the sales processing unit if the project management information does not satisfy a predetermined condition; A server device comprising:

8. 8. The server device according to claim 7, a similarity determination unit that determines whether the template of the project management information is similar to templates of other project management information that are on sale to a predetermined degree or more; the sales approval unit determines whether the template is similar to a template of other project management information being sold by the similarity determination unit to a predetermined degree or more, and if similar, does not approve the sale by the sales processing unit; A server device comprising:

9. 8. The server device according to claim 7, the project application unit adds predetermined information to the project management information to which a template of the project management information purchased by the user desiring to purchase has been applied; the sales approval unit does not approve the sale by the sales processing unit of the template of the project management information to which the predetermined information has been added; A server device comprising:

10. A management information sharing method using a server device, comprising: The server device A storage unit for storing one or more pieces of project management information for each project manager, and a processing unit, The processing unit includes: a management execution procedure for displaying and managing at least the tasks or work items included in the project management information using a predetermined diagram, such as an activity plan or chart; a sales processing procedure for selling one or more of the templates for project management information to a user who wishes to purchase the templates; a project application step of applying the template of the project management information to a project of the user who desires to purchase the project; A management information sharing method comprising:

11. A management information sharing program for sharing management information using a server device, The server device A storage unit for storing one or more pieces of project management information for each project manager, and a processing unit, With respect to the processing unit, a management execution procedure for displaying and managing at least the tasks or work items included in the project management information using a predetermined diagram, such as an activity plan or chart; a sales processing procedure for selling one or more of the templates for project management information to a user who wishes to purchase the templates; a project application step of applying the template of the project management information to a project of the user who desires to purchase the project; A management information sharing program that causes the user to execute the above steps.

Images