JP2009187044A - Sns-task management cooperation system, its method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an SNS/task management cooperation system, its method and a program for increasing reply writing by transmitting alarm mail to a person concerned by determining that there is any unsolved problem when there is writing with no reply in a fixed period. <P>SOLUTION: The group of employees shares a task by a task management system, and the employees of the group share the community of SNS, and tasks and the writing of a notice board are associated by string, arranged and presented for each task, and when there is no reply to the writing in a fixed period, the employees assigned to the community are notified of alarm. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a technology for providing an SNS community (a collective space for communicating in projects and organizational units) and a mechanism (task management system) for managing business contents and progress in cooperation with each other.

  Although introducing SNS within a company, there were the following problems. First of all, writing doesn't increase easily because you don't know what to write and you don't have the courage to write. In addition, only some people use it, and as a result, only stories that are not related to work such as circle activities and excitement within the same period are shared. In addition, the number of people who use it increases at the beginning, but it gets tired and stops using. As a result, it was not used, and it was very difficult to realize information sharing, which was the original purpose.

  The reason why such problems occur is that the guidelines for using SNS and business in association have not been formulated, and it was not possible to formulate them because of the following technical problems. There is. First, the SNS does not have a function for managing business contents and business progress necessary for business execution. In addition, even if a business management system has already been installed in the company, there is a function to share and share business information of projects and organizations only with projects belonging to SNS and employees within the organization. Not done.

As a related technology, network-based sales force automation has been proposed that can improve sales and marketing efficiency as well as technical and customer support efficiency. In the configuration, business information including business, contact, account and lead is provided using a web browser via the Internet. You can electronically link related businesses and search for business information using custom profiles. The business information is accessible and shared according to the hierarchy and pre-specified territories among the members constituting the host. Radar Screen Opportunity Display (RSOD) can be selected to display business objects on it. Business objects represent several stages in the sales pipeline of the corresponding business. New business information can be selected and automatic notification of new and changed information related to the business is also provided. New business information includes information on at least one monitored customer's web site. Communication capabilities including e-mail, facsimile, telephone and pager are also provided. The communication capability can be automatically established using business information (see, for example, Patent Document 1).
Special Table 2002-523842

  The related technology described above includes a mechanism for synchronizing a group of employees who share an SNS community. In addition, it has a mechanism that links the work and the writing on the bulletin board generated from the work, and organizes and shares the writing for each work.

  However, when there is no answer to the writing for a certain period, there is a problem that it is difficult to prevent the situation where the writing is left and the writing is retained.

  The present invention has been made to solve the above-described problems. When there is a writing without a reply for a certain period of time, it is judged that there is an unsolved problem and a reply writing is performed by sending an alarm mail to the parties concerned. An object of the present invention is to provide an SNS-task management cooperation system, a method thereof, and a program for increasing the number of programs.

In the SNS-task management cooperation system of the present invention, a group of employees shares a task with the task management system,
Employees of the group share the SNS community,
Linked the work and writing on the bulletin board, organized and presented by work,
When there is no answer to the writing for a certain period, an alarm is notified to employees belonging to the community.

In addition, the SNS-task management cooperation method of the present invention is a SNS-task management cooperation method in an SNS-task management cooperation system in which a group of employees shares a task in the task management system, and the employees of the group share an SNS community. Because
A step of associating a business and writing on a bulletin board and organizing and presenting it for each business,
A step of notifying an employee belonging to the community of an alarm when there is no answer to the writing for a certain period of time.

Further, the program of the present invention is a program in an SNS-task management cooperation system in which a group of employees shares a task in a task management system, and the group of employees shares an SNS community.
A process of associating business and writing on the bulletin board and organizing and presenting by business,
When there is no answer to the writing for a certain period, a process of notifying an alarm to an employee belonging to the community is executed.

  According to the present invention, when there is writing for which there is no reply for a certain period of time, it is possible to increase reply writing by determining that there is an unsolved problem and sending an alarm mail to the parties concerned.

  Hereinafter, a first embodiment of the present invention will be described in detail with reference to the drawings. Referring to FIG. 1, the SNS-task management cooperation system according to the present embodiment includes a project DB 10 for storing task management data, a community / diary DB 20 for storing community and diary information in the SNS, and employee information. Three databases of the employee DB 30 to be stored are used.

  Further, a project registration function 11 for registering project information in the project DB 10, a project browsing function 12 for browsing registered project information, a business registration function 13 for registering business information, and browsing registered business information. A business browsing function 14 for registering and a business progress registration function 15 for registering the progress of the business.

  Furthermore, a bulletin board writing function 21 for registering writing on the bulletin board of the community / diary DB 20, a bulletin board browsing function 22 for browsing information written on the bulletin board, and a bulletin board for writing advice, providing information, etc. When a problem is written on the comment writing function 23 and the bulletin board, but an answer is not provided from another employee belonging to the project, it is determined that the writing is stagnant and an alert mail is sent to the employee belonging to the project Bulletin board writing retention determination function 24, diary writing function 25 for registering a diary, diary browsing function 26 for browsing diary information, diary comment writing function 27 for writing advice, information provision, etc. to the diary, Consists of.

  Next, FIGS. 1, 2, 3, 4, 5, 6, 7, 8, 8, 9, 10, 11, 12, 12, 13, 15, 15, and 16 17, 18, 19, 19, 20, 21, 22, 23, 24, 25, 26, 27, and 28, the operation of the present embodiment will be described in detail. To do.

  In the present invention, as shown in FIG. 2, when there is a community (101) related to “sales of product A” in the SNS (100), a project corresponding to the “sales of product A” community (101) in the task management (200). (201) exists. In addition, the same group of employees (301) related to sales of the product A belongs to the community (101) and the project (201). Information existing in the community (101) and the project (201) is only disclosed to the employees who belong to the group.

  The employee registers the work contents in the project (201) and registers the progress as needed. When a problem occurs in business, the problem is written on the bulletin board (102), and advice is obtained from employees who belong to the project. If employees who belong to the project think that they cannot solve the problem, write advice in the diary (103) to seek advice throughout the company. For example, the sales member 302 of the product B who has read the diary writes advice.

  Next, the actual operation will be described. A procedure for registering a project team (hereinafter referred to as a project) for performing a task in the task management (200) will be described with reference to FIGS.

  First, the project registration page (203 in FIG. 4) is displayed (S1001), and the project name and employee are entered and selected (S1002). The project ID (numerical serial number) and the input project name are registered in the project table (FIG. 22) of the project DB (S1003). Next, the employee ID name of the member employee is registered in the project member table (FIG. 24) of the project DB, and the community ID (numerical serial number) is entered in the community table (FIG. 26) of the community / diary DB. The name is registered as a community name (S1005). Finally, the community ID registered in S1005 is registered in the project table (FIG. 22) of the project DB (S1006). A community having the same name as the project name is created as indicated by 104 and 105 in FIG.

  Next, a procedure for browsing a list of registered projects will be described with reference to FIGS. First, the project list page (202 in FIG. 7) is displayed (S2001), and when a project to be browsed is selected (S2002), the project ID of the selected project is transferred (S2003), and the project table of the project DB (FIG. 22). The project name that matches the project ID passed from) is acquired (S2004). Next, an employee ID that matches the project ID passed from the project member table (FIG. 24) in the project DB is acquired (S2005). Finally, the surname matching the person-in-charge ID is acquired from the employee table (FIG. 21) in the employee DB (S2006), and the project browsing (204 in FIG. 7) page is displayed.

  Next, the procedure for registering a business in a project will be described with reference to FIGS. First, the project browsing page (204 in FIG. 7) is displayed (S3001), and business registration is selected (S3002). The project ID of the project is transferred (S3003), and the business registration page (205 in FIG. 7) is displayed (S3004). On the business registration page, the business name, the employee in charge, and the time limit are entered and selected (S3005). In 205, since there are three unprocessed input tasks such as “price review”, “price material creation”, and “pamphlet creation” (S3006), one task is listed in the project DB task information table (FIG. 23). The ID (numerical serial number), business name, project ID, work order (business order), progress (unstarted), employee ID and deadline are registered (S3007), and all cases are processed.

  Next, a procedure for browsing a list of registered tasks will be described with reference to FIGS. First, a project browsing page (204 in FIG. 7) is displayed (S4001), and business browsing is selected (S4002). The project ID of the project is delivered (S4003), and the business name, person-in-charge ID, progress, and time limit that match the project ID are acquired from the business table (FIG. 23) of the project DB (S4004). Next, the last name of the employee corresponding to the acquired person-in-charge ID is acquired from the employee table (FIG. 21) of the employee DB (S4005), and the business browsing page (206 in FIG. 13) is displayed (S4006).

  Next, a procedure for registering the progress of a registered job will be described with reference to FIGS. First, a business browsing page (206 in FIG. 13) is displayed (S5001). The business progress is selected from “Unstarted”, “Started”, and “Completed” (S5002). In 206, there are unprocessed progress work because the two work progresses, “Price Review” and “Pricing Material Creation” are changed from “Unstarted” (S5003). The progress of the business that matches the business ID of 23) is registered (S5004).

  Next, a procedure for writing business-related problems on the bulletin board will be described with reference to FIGS. First, a bulletin board writing page (106 in FIG. 13) is displayed (S6001), and a subject and written contents are input (S6002). Then, the community ID that matches the project ID is obtained from the project table in the project DB (FIG. 22) (S6003), written in the bulletin board table in the community / diary DB (FIG. 27), and the entered subject. The written contents, the acquired community ID, the written employee ID, and the original written ID are empty, and the writing time is registered (S6004). Further, the project ID, write ID, and write type (“bulletin board”) are registered in the business-bulletin board / diary writing relation table (FIG. 25) of the project DB (S6005).

  Next, the procedure for browsing the registered bulletin board writing list will be described with reference to FIGS. First, the business browsing page (206 in FIG. 13) is displayed (S7001), and related bulletin board browsing is selected (S7002). Then, a write ID whose project ID matches and whose write type matches “bulletin board” is acquired from the business DB bulletin board / diary write related table (FIG. 25) (S7003). Since there is one unprocessed write ID with a write ID of 5 in FIG. 25, a subject whose write ID or original write ID matches the acquired write ID from the bulletin board table of the community / diary DB (FIG. 27), Write content, employee ID, and write time are acquired (S7005). In FIG. 27, two cases with write IDs of 5 and 6 are applicable. Further, the last name of the employee corresponding to the acquired employee ID is acquired from the employee table (FIG. 21) of the employee DB (S7006), and the bulletin board browsing page is displayed (107 in FIGS. 13 and 14).

  Next, a procedure for writing a comment in order to give advice on the content written on the bulletin board will be described with reference to FIGS. First, the bulletin board browsing page (107 in FIG. 13) is displayed (S8001), and when a comment is selected (S8002), the writing ID of the bulletin board is received (S8003), and the comment writing page (108 in FIG. 14) is displayed (S8004). Is done. When the subject and the written content are input (S8005), the write ID, the subject, the written content, the written employee ID, the original written ID (the written ID received in S8003), and the writing time are entered in the bulletin board table of the community / diary DB (FIG. 27). Is registered (S8006).

  Next, if you write a problem on the bulletin board but no answer is provided by another employee who belongs to the project, the procedure for sending an alert email to the employee who belongs to the project is judged to be stuck. 15 will be used for explanation. First, from the bulletin board table of the community / diary DB (FIG. 27), a write ID whose original write ID is blank and whose write time is 72 hours or more ago is acquired (S9001). It is assumed that writing with a writing ID of 15 corresponds to this time. Next, it is confirmed whether or not there is writing in which the acquired writing ID is set as the original writing ID (S9002). Since there is no corresponding writing in FIG. 27, a project ID matching the writing community ID acquired from the project table (FIG. 22) of the project DB is acquired (S9003). Next, an employee ID belonging to the project employee table (FIG. 24) in the project DB is acquired (S9004). In FIG. 24, three employees with employee IDs 1, 2, and 3 correspond. Finally, an alert mail is transmitted from the employee table in the employee DB (FIG. 21) to the mail address that matches the employee ID. In the above description, the writing retention standard is 72 hours without comment, but the retention standard time is not limited to this and can be changed.

  Next, a procedure for writing in the diary a problem that the employee who belongs to the project thinks cannot be solved will be described with reference to FIGS. First, a diary writing page (109 in FIG. 19) is displayed (S10001), and a subject and written contents are input (S10002). Then, the diary ID (numerical serial number), the inputted subject, the written content, the written employee ID, the original diary ID are empty, and the writing time is registered in the diary table (FIG. 28) of the community / diary DB (S10003). Further, the project ID, the write ID, and the write type (“diary”) are registered in the business-bulletin board / diary writing relation table (FIG. 25) of the project DB (S10004).

  Next, the procedure for browsing the registered diary list will be described with reference to FIGS. First, a business browsing page (206 in FIG. 19) is displayed (S11001), and related diary browsing is selected (S11002). Then, a write ID whose project ID matches and whose write type matches “diary” is acquired from the work-bulletin board / diary write related table (FIG. 25) of the project DB (S11003). Since there is one unprocessed write ID with a write ID of 5 in FIG. 25, a subject whose diary ID or original diary ID matches the acquired write ID from the diary table (FIG. 28) of the community / diary DB, Write content, employee ID, and write time are acquired (S11005). In FIG. 28, two cases with diary IDs 5 and 6 are applicable. Further, the last name of the employee corresponding to the acquired employee ID is acquired from the employee table (FIG. 21) of the employee DB (S11006), and the diary browsing page is displayed (110 in FIGS. 19 and 20).

  Next, a procedure for writing a comment in order to give advice on the contents written in the diary will be described with reference to FIGS. First, the diary browsing page (110 in FIG. 19) is displayed (S12001), and when a comment is selected (S12002), the diary ID is received (S12003), and the comment writing page (111 in FIG. 20) is displayed (S12004). . When the subject and the written content are input (S12005), the diary ID, the subject, the written content, the written employee ID, the original diary ID (diary ID received in S12003), the writing time in the diary table of the community / diary DB (FIG. 28). Is registered (S12006).

  In the present embodiment, when there is writing for which there is no reply for a certain period of time, it is determined that there is an unsolved problem and the reply writing is increased by transmitting an alarm mail to the related parties. In addition, if there is a message without advice for a certain period of time, information sharing and activation of communication can be realized by a mechanism for requesting advice by sending an alert mail to the project employees. In addition, new communication occurs between employees other than the project through the diary. In addition, since problems and ideas are organized for each business information, information can be searched efficiently.

Further explanation regarding the present embodiment will be given below.
In this embodiment, first, in order to use the SNS in the business flow, a system that manages the business information and the SNS are provided. In other words, by registering and managing the contents, progress, and history of personal work using the work management system described above (hereinafter referred to as the task management system), and further sharing the contents for each project and organization, We can carry out business from the starting point. There are various problems and troubles that I face in my work. At that time, a bulletin board (a community that exists in the community and a community) Information sharing and problem solving can be studied. You can also discuss ideas that you have come up with in your work.

  In order to realize these, the present embodiment includes a mechanism for synchronizing a set of employees sharing a task with a task management system and a set of employees sharing an SNS community. In addition, it has a mechanism that links the work and the writing on the bulletin board generated from the work, and organizes and shares the writing for each work. Furthermore, when there is no answer to writing for a certain period, it is considered that writing has been left unattended, and an alarm mail is sent to employees belonging to the community.

  With the above system, there is no risk of information being disclosed to employees who are not involved in work, and it prevents situations where necessary information cannot be shared by participating in only one of the work and community. I can do it. Furthermore, it is possible to prevent a situation where writing is retained.

  However, there are, of course, problems that cannot be solved only by the knowledge of the employees of the project and organization. In such a case, if problems can be disclosed to employees beyond the project, and advice can be sought from in-house experts, problems will be solved quickly, and new in-house personnel exchange will occur. . In order to realize this mechanism, the present embodiment includes a mechanism for writing a problem from a task management system to an SNS diary (a place where information that can be disclosed to an unspecified number of employees is written). In addition, it has a mechanism that links work and diary generated from work, and organizes and shares the diary for each work.

  If it is the above mechanism, the following change will arise with respect to said subject. First, since the contents to be written to the SNS are naturally generated from the work, the trouble of not knowing what to write can be solved. In addition, if the business problem is left as it is, it will greatly hinder the performance of the business, so it can be actively written. Furthermore, the written problem does not stay, and you can expect answers and information. As a result, information can be shared in a wide range within the project / organization and within the company. In addition, it is possible to activate communication among employees who have never known in the company.

Next, a second embodiment of the present invention will be described with reference to FIGS.
In the flow of FIG. 29, as shown in FIG. 30, after the “XXX technology seminar” is written on the bulletin board, it is possible to register the research work related to the seminar from the bulletin board browsing page. In the second embodiment, business registration can be performed from a bulletin board. Unlike the first embodiment, information registration based on both SNS and task management can be performed.

  Each of the above-described embodiments is a preferred embodiment of the present invention, and various modifications can be made without departing from the scope of the present invention. For example, processing for realizing the functions of the system may be performed by causing the system to read and execute a program for realizing the functions of the system. Further, the program is transmitted to another computer system by a transmission wave via a computer-readable recording medium such as a CD-ROM or a magneto-optical disk, or via a transmission medium such as the Internet or a telephone line. Also good. Further, a mode in which functions are distributed by an additional device is also within the scope of the present invention.

It is a figure which shows the system configuration | structure which concerns on 1st embodiment of this invention. It is a figure which shows the process outline | summary which concerns on 1st embodiment of this invention. It is a flowchart of the project registration function which concerns on 1st embodiment of this invention. It is a figure which shows the procedure which registers the project team for performing business in the task management which concerns on 1st embodiment of this invention. It is a flowchart of the project browsing function which concerns on 1st embodiment of this invention. It is a flowchart of the business registration function which concerns on 1st embodiment of this invention. It is a figure which shows the procedure which browses the list | wrist of the registered project which concerns on 1st embodiment of this invention. It is a flowchart of the business browsing function which concerns on 1st embodiment of this invention. It is a flowchart of the work progress registration function which concerns on 1st embodiment of this invention. It is a flowchart of the bulletin board writing function which concerns on 1st embodiment of this invention. It is a flowchart of the bulletin board browsing function which concerns on 1st embodiment of this invention. It is a flowchart of the bulletin board comment writing function which concerns on 1st embodiment of this invention. It is a figure which shows the procedure which browses the list | wrist of the registered work which concerns on 1st embodiment of this invention. It is a figure which shows the procedure which browses the writing list of the registered bulletin board which concerns on 1st embodiment of this invention. It is a flowchart of the bulletin board writing stay determination function according to the first embodiment of the present invention. It is a flowchart of the diary writing function which concerns on 1st embodiment of this invention. It is a flowchart of the diary browsing function which concerns on 1st embodiment of this invention. It is a flowchart of the diary comment writing function which concerns on 1st embodiment of this invention. It is a figure which shows the procedure which writes in the diary the problem etc. which the employee who belongs to the project which concerns on 1st embodiment of this invention thought that it cannot solve. It is a figure which shows the procedure which writes in the diary the problem etc. which the employee who belongs to the project which concerns on 1st embodiment of this invention thought that it cannot solve. It is a figure which shows the structure of the employee table of employee DB in 1st embodiment of this invention. It is a figure which shows the structure of the project table of project DB in 1st embodiment of this invention. It is a figure which shows the structure of the work table of project DB in 1st embodiment of this invention. It is a figure which shows the structure of the project affiliation employee table of project DB in 1st embodiment of this invention. It is a figure which shows the structure of the work-bulletin board / diary writing relation table of project DB in 1st embodiment of this invention. It is a figure which shows the structure of the community table of community / diary DB in 1st embodiment of this invention. It is a figure which shows the structure of the bulletin board table of community / diary DB in 1st embodiment of this invention. It is a figure which shows the structure of the diary table of community / diary DB in 1st embodiment of this invention. It is a flowchart of the business registration function which concerns on 2nd embodiment of this invention. It is a figure which shows the procedure which carries out business registration of the investigation business regarding a seminar from the bulletin board browsing page which concerns on 2nd embodiment of this invention.

Explanation of symbols

10 Project DB
11 Project Registration Function 12 Project Browsing Function 13 Business Registration Function 14 Business Browsing Function 15 Business Progress Registration Function 20 Community / Diary DB
21 Bulletin board writing function 22 Bulletin board browsing function 23 Bulletin board comment writing function 24 Bulletin board writing retention judgment function 25 Diary writing function 26 Diary browsing function 27 Diary comment writing function 30 Employee DB

Claims (7)

A group of employees share tasks in a task management system,
Employees of the group share the SNS community,
Linked the work and writing on the bulletin board, organized and presented by work,
An SNS-task management cooperation system, wherein an alarm is notified to employees belonging to a community when there is no answer to the writing for a certain period of time.   The SNS-task management cooperation system according to claim 1, wherein the alarm is an e-mail. Write the problem from the task management system to the SNS diary,
The SNS-task management cooperation system according to claim 1 or 2, wherein a business and a diary generated from the business are linked, and the diary is organized and shared for each business. An SNS-task management cooperation method in an SNS-task management cooperation system in which a group of employees shares a task in a task management system, and the employees of the group share an SNS community,
A step of associating a business and writing on a bulletin board and organizing and presenting it for each business,
And a step of notifying an alarm to employees belonging to the community when there is no answer to the writing for a certain period of time.   5. The SNS-task management cooperation method according to claim 4, wherein the alarm is an electronic mail. Writing a problem from the task management system to the SNS diary;
6. The SNS-task management linkage method according to claim 4, further comprising a step of associating a business with a diary generated from the business and organizing and sharing the diary for each business. A program in an SNS-task management cooperation system in which a group of employees shares a task in a task management system, and the group of employees shares a SNS community,
A process of associating business and writing on the bulletin board and organizing and presenting by business,
When there is no answer to the writing for a certain period of time, a program for causing an employee who belongs to the community to execute an alarm is executed.

Images