JP6097428B1 - Report creation support system - Google Patents

Abstract

An object of the present invention is to provide a report creation support system that can reduce the labor of report creation work by employees, etc. with minimal costs and changes. A schedule acquisition function 221 accesses an external schedule management server that performs a general-purpose schedule management support service, and acquires a predetermined schedule item from registered schedule information registered by the user for each event in the schedule management server. Then, the acquisition schedule information is generated for each event using the predetermined schedule item. The report creation support function 211a automatically generates a report form 600 having an input field for inputting report items for each event. The automatic entry function 303 selects the report items to be input in the input field of the report form 600 from the schedule information included in the acquisition schedule information, and automatically inputs the report items in the input field. [Selection] Figure 3

Description

  The present invention relates to a report creation support system for supporting creation when a user electronically creates a report including a plurality of report items.

  In recent years, the number of companies that use a groupware system to manage schedules for employees and the like is increasing. By using the groupware system, it becomes easy to comprehensively manage the schedule of each employee, etc., preventing the scheduling of business negotiations etc., and the schedule of attendees It is possible to set the date and time of the conference efficiently. As a technique for managing a schedule using a groupware system, for example, a technique disclosed in Patent Document 1 below is known.

  In recent years, there are an increasing number of companies that support the activities of sales staff and the like using an SFA (Sales Force Automation) system. By using the SFA system to manage business negotiation information and reports (for example, daily reports) of each sales staff member and to collectively manage customer information, it is possible to improve the efficiency of sales activities. As a technique for performing sales support using an SFA system, for example, one disclosed in Patent Document 2 below is known.

JP 2009-169822 A JP 2008-15654 A

  In general, companies that have introduced the SFA system are obliged to create and submit reports to sales staff. For example, when a sales staff member visits a plurality of locations in one day, the sales staff member must create and submit daily reports individually for all the visiting sites. For this reason, the conventional SFA system has the disadvantage that the burden on each employee's report creation work increases.

  In addition, when there are many reports to be submitted, there is a risk of forgetting to create and submit some reports.

  Furthermore, sales staff and the like tend to easily create a report as compared to when a schedule is registered. In other words, sales staff and the like often describe memorandums and the like in detail so that there is no mistake in the name, purpose, and belongings of the person in charge to visit when registering a schedule using the schedule management service. On the other hand, when reporting an activity, the activity has become a thing of the past, so there is a tendency to conclude with a simple report. Since there is currently no means for associating the schedule action with the business report, detailed information recorded by the sales staff at the time of the schedule registration is difficult to communicate to the report destination (for example, the manager of the sales staff).

  In order to eliminate such drawbacks, it is conceivable to integrate the groupware system and the SFA system. If these systems are integrated and schedule management and report creation are performed in the same system, it is considered possible to create reports using data entered by employees for schedule management. .

  However, if the groupware system and the SFA system are changed to an integrated system, the sales staff of the company, etc., change the service from the service that has been used for both the groupware and the SFA at the same time. It will be pressed. For this reason, when such an integrated system is introduced, there is a possibility that business confusion may occur in the early stage of the introduction.

  In many cases, the groupware system is used by almost all employees of the company or the like, whereas the SFA system is mainly used by sales staff, and therefore only a part of the employees. For this reason, it is not efficient to change even the groupware in order to eliminate the drawbacks of the SFA from the viewpoints of confusion at the time of introduction and introduction costs.

  An object of the present invention is to provide a report creation support system that can reduce the labor of report creation work for employees and the like with minimal costs and changes.

In order to solve this problem, the report creation support system according to the invention of claim 1 is a support server that performs creation support when a user of a communication terminal electronically creates a report including a plurality of report items. A report creation support system comprising: storing authentication information given to a user of the communication terminal in the support server in order to log in to an external schedule management server that performs a general-purpose schedule management support service; In addition, by causing the support server to log in to the schedule management server using the authentication information, the user acquires a predetermined schedule item from the registered schedule information registered for each event in the schedule management server, A schedule acquisition function for generating acquisition schedule information for each event using the predetermined schedule item; A report form creation function that automatically generates a report form having an input field for inputting an item for each event, and the report item that is input to the input field of the report form is included in the acquisition schedule information. An automatic filling function for selecting from the schedule items included and automatically entering the input field; and a display function for displaying the report form automatically entered by the automatic filling function on the communication terminal. The schedule acquisition function accesses each of the plurality of schedule management servers that perform separate and independent schedule management support services, acquires the registered schedule information from each of the schedule management servers, and generates the acquisition schedule information , characterized in that.

  According to a second aspect of the present invention, in addition to the configuration of the first aspect, the acquisition schedule information includes execution date / time information of the event as the schedule item acquired from the registration schedule information, and the report form The creation function automatically generates the report form of the event when the timing determined based on the execution date / time information is reached.

  According to a third aspect of the present invention, in addition to the configuration of the second aspect, the report form creation function automatically generates the report form for the event when the event finish date or time is reached or later. It is characterized by doing.

According to the invention of claim 1, the support server accesses an external schedule management server that performs general-purpose services, acquires a predetermined schedule item for each event, and enters the schedule item as a report item of the report. Report preparation support can be performed without changing the schedule management support service to be used. Therefore, according to the first aspect of the invention, it is possible to introduce a report creation support service with only minimal costs and changes, thereby making it possible to improve the efficiency of the input of the reporting work and to establish the reporting work. Can be made possible.
According to the invention of claim 1, one report creation support system can correspond to a plurality of schedule management support servers. For this reason, according to the invention of claim 1, even when one company or the like uses a plurality of types of schedule management support services together, it can be handled by one report creation support system, and furthermore, one report The creation support system can provide a report creation support service to a plurality of companies that use different schedule management support services. Therefore, according to the first aspect of the invention, report creation support can be realized at a lower cost.

  In addition, according to the invention of claim 1, since a report form is automatically generated for each event, the possibility of forgetting to create and submit a report can be reduced.

  According to the invention of claim 2, since the report form is automatically created at the timing according to the execution date and time of the event, the possibility of forgetting to create and submit the report can be further reduced.

  According to the invention of claim 3, since the report form is automatically created and the report can be created after the end date or time of the event, there is a possibility that the report may be forgotten to be created / submitted. Further reduction can be achieved.

It is a conceptual diagram which shows the network structure of the report preparation assistance system which concerns on Embodiment 1 of this invention. It is a block diagram which shows notionally the function structure of the report preparation assistance system which concerns on the same Embodiment 1. FIG. It is a block diagram which shows the principal part function structure of the report preparation assistance system which concerns on the same Embodiment 1. FIG. It is a conceptual diagram which shows the schedule registration screen of the groupware system which concerns on the same Embodiment 1. FIG. It is a table | surface for demonstrating the schedule acquisition function of the report preparation assistance system which concerns on the same Embodiment 1. FIG. It is a conceptual diagram which shows the report preparation screen of the report preparation assistance system which concerns on the same Embodiment 1. FIG.

  Embodiment 1 of the present invention will be described below with reference to the drawings.

  FIG. 1 is a conceptual diagram showing a network configuration of a report creation support system according to the first embodiment.

  As shown in FIG. 1, the network 100 according to the first embodiment includes an SFA system 110, a groupware system 120, and a plurality of communication terminals 130. These systems 110 and 120 and the communication terminal 130 are interconnected via the Internet 140, for example. The communication network may be another type of communication network such as a LAN (Local Area Network), for example, or may be a combination of a plurality of communication networks.

  The SFA system 110 corresponds to the “report creation support system” of the present invention, and is a server that provides business support services such as report creation and submission (details will be described later).

  The groupware system 120 corresponds to the “schedule management server” of the present invention, and performs a schedule management service (details will be described later). In the first embodiment, it is assumed that the groupware system 120 provides a schedule management service as a service independent of the service of the SFA system 110. In FIG. 1, only one groupware system 120 is shown, but one SFA system 110 can collect information from a plurality of types of schedule management services.

  The communication terminal 130 is a terminal for accessing the SFA system 110 and the groupware system 120 via the Internet 140 and receiving services of these systems 110 and 120. As the communication terminal 130, for example, a personal computer, a smart phone, a tablet terminal, a mobile phone, or the like can be used, but other types of communication terminals may be used.

  In the first embodiment, the user of each communication terminal 130 is a sales staff member belonging to the same company, and each sales staff member uses both the SFA system 110 and the groupware system 120. A case will be described as an example.

  FIG. 2 is a block diagram conceptually showing the functional configuration of the SFA system 110 shown in FIG. As shown in FIG. 2, the SFA system 110 includes a sales support unit 210 and an external information acquisition unit 220. The sales support unit 210 and the external information acquisition unit 220 can be constructed in hardware, but are usually constructed in software. The sales support unit 210 and the external information acquisition unit 220 may be built on the same server computer, or may be built on separate server computers in order to reduce the load on the computer.

  The sales support unit 210 is a functional block that assists and manages a company's sales activities, and includes a customer management function 211, a business negotiation management function 212, a totaling / analysis function 213, and the like.

  Here, the customer management function 211 is a function for comprehensively managing information related to the customer. The report creation support function 211a (details will be described later) and the customer information management function 211b (that is, the company name of the customer company, Functions for managing company information such as addresses).

  The negotiation management function 122 is a function for managing the expected sales of orders, a product catalog, the contents of an order contract, and the like.

  The aggregation / analysis function 213 is a function for accumulating / managing data related to sales.

  On the other hand, in FIG. 2, an external information acquisition unit 220 is a functional block that acquires various types of information from an external server or the like that provides a general-purpose service and provides the information to the sales support unit 210. An acquisition function 222 and the like are included.

  Here, the schedule acquisition function 221 acquires schedule information registered by a sales representative (that is, the user of the communication terminal 130) from the groupware system 120 (see FIG. 1) (details will be described later). For this purpose, the schedule acquisition function 221 stores an ID (identification number), a password, and the like for each sales staff member to use the groupware system 120.

  The location information acquisition function 222 receives the customer address information from the customer information management function 211b provided in the customer management function 211 of the sales support unit 210, and then accesses an external general-purpose geocoding server that provides a geocoding service. The latitude / longitude information corresponding to the address information is acquired, and the latitude / longitude information is sent to the customer information management function 211b. Thereby, the customer information management function 211b can add a function of displaying the customer's location on a map to the customer information.

  As described above, the sales support unit 210 of the SFA system 110 includes a customer management function 211, and the customer management function 211 includes a report creation support function 211a. The functional configuration of this report creation support function 211a is shown in FIG.

  As shown in FIG. 3, the report creation support function 211a includes a report form creation function 301, a date management function 302, an automatic entry function 303, a manual entry function 304, a report execution function 305, and the like. As described above, in the first embodiment, the report creation support function 211a is provided in the SFA system 110. However, a part or all of the report creation support function 211a may be provided in each communication terminal 130. is there.

  The report form creation function 301 is a function for creating a report form for each event.

  Here, the report form is a form for inputting each item of the report to the communication terminal 130, and one report form corresponds to one report (see FIG. 6 described later). This report form can be displayed on the screen of the communication terminal 130 using a browser or the like, and a sales staff member can confirm / manually input report items using this screen.

  An event is a unit of activity for which a sales staff member needs to create a report, and one event corresponds to one report.

  The report form can be manually created by a sales employee who uses the communication terminal 130, but can be automatically created at a predetermined timing under the management of the date management function 302 (details will be described later). ). For example, the timing for automatically generating the report form can be determined based on the end date / time and start date / time of the event.

  The date management function 302 is a function for managing the creation timing of the report form and the like for each event. In the first embodiment, the date and time information managed by the date and time management function 302 is acquired from the schedule information of the groupware system 120 (see FIG. 1) for each event (details will be described later).

  The automatic entry function 303 is a function for automatically filling in items acquired from the schedule information of the groupware system 120 (see FIG. 1) among the input items (that is, report items) included in the report form (details are given below). Later).

  The manual entry function 304 is a function in which a user of the communication terminal 130 (that is, an employee in charge of sales) manually inputs a report item into a report form or changes the report item automatically input by the automatic entry function 303. is there.

  The report execution function 305 saves the report form in the SFA system 110, and submits the input items to the report form as an electronic report to the report destination (for example, the manager of the sales staff). Process to do.

  Hereinafter, the operation of the systems 110 and 120 according to the first embodiment will be described along the usage procedure.

(1) Schedule Registration Processing to Groupware System 120 When the sales staff member determines the event schedule, he / she uses the communication terminal 130 to access the groupware system 120 and displays the schedule registration screen 400 on the communication terminal 130. Display. FIG. 4 is a conceptual diagram illustrating an example of the schedule registration screen 400. As shown in FIG. 4, the schedule registration screen 400 displays input fields 401 to 409 for inputting schedule items and operation icons 410 and 411.

  In the schedule registration screen 400 of FIG. 4, in the “registrant” column 401, the department and name of the person in charge of the schedule (here, the sales employee) is entered.

  In the “subject” column 402, the type of the event is input. FIG. 4 is an example in which “customer visit” is set as “subject”.

  In the date and time input field 403, “start date and time” and “end date and time” are entered and set.

  In the “name” column 404, for example, the name of a company / individual subject to the event, such as a visited company, is input.

  In the “address” column 405, the address of the company or the like input in the “name” column 404 is input.

  The “name” field 404 and the “address” field 405 may be collectively input by clicking the address book icon 410 to display a customer name list and selecting from the customer names included therein.

  In the “person in charge” field 406, the names of persons in charge such as companies entered in the “name” field 404 and the “address” field 405 are entered.

  The “content” column 407 is a memo column related to the schedule, and the sales staff member inputs an arbitrary sentence.

  The “file” column 408 is used when an electronic file is to be attached to the schedule registration.

  In the “Notification” column 409, when the alarm is used to notify the sales staff that the start date and time of the schedule is imminent (or the start date and time has been reached), the date and time when the alarm is activated is set. It is a column to do.

  The “Register” button 411 is an icon for registering and saving information input on the schedule registration screen in a database (not shown) in the groupware system 120.

  The sales staff member inputs a schedule item in a part or all of the input fields 401 to 409 on the schedule registration screen, and then clicks a “register” button 411. As a result, the schedule items input in these input fields 401 to 409 are stored in a database (not shown) in the groupware system 120 together with the event number assigned to the event.

  Hereinafter, the schedule information input using the schedule registration screen is referred to as “registration schedule information”.

  Based on such registration schedule information, this groupware system 120 creates a schedule for all sales staff members in a calendar and displays them on the communication terminal 130, or creates a schedule for each sales staff member in the communication terminal 130. Processing to be displayed can be performed (both not shown).

(2) Schedule acquisition processing by the SFA system 110 The external information acquisition unit 220 of the SFA system 110 includes the schedule acquisition function 221 as described above. Further, as described above, the schedule acquisition function 221 stores an ID, a password, and the like for each sales staff member to use the groupware system 120.

  The schedule acquisition function 221 accesses the groupware system 120 at a predetermined timing and logs in using these IDs, passwords, and the like. The timing at which the schedule acquisition function 221 logs into the groupware system 120 may be, for example, every predetermined time, may be a predetermined time every business day, or may be a timing determined by other rules. Also good. Further, in addition to the function of automatically logging in to the groupware system 120 to the schedule acquisition function 221 (or in place of that function), each sales employee operates his / her communication terminal 130 to log in. A function may be provided.

  When the schedule acquisition function 221 logs in to the groupware system 120, the schedule acquisition function 221 checks the registration schedule information by the sales staff member for each event and each schedule item. If the checked schedule items include schedule items that have not yet been acquired or schedule items that have been changed since the previous check, those schedule items are acquired. Note that every time the user logs in, all the schedule information registered by the sales staff may be acquired.

  Then, the schedule acquisition function 221 stores the acquired schedule items in an internal database (not shown). FIG. 5 is a conceptual diagram showing the schedule items stored in the schedule acquisition function 221 as a table. As shown in FIG. 5, the schedule items acquired from the groupware system 120 are stored for each schedule information unit (that is, for each event).

  Hereinafter, schedule information including schedule items acquired for each event by the schedule acquisition function 221 is referred to as “acquisition schedule information”.

  In the acquisition schedule information shown in FIG. 5, “event number” 501 is a number for identifying the event, and the schedule acquisition function 221 gives it to each acquisition schedule information. The “start date / time” 502 is data input to the “start date / time” included in the date / time input field 403 of the registration schedule information (see FIG. 4), and the “end date / time” 503 is the same as the date / time input field 403. This is the data input to “End Date”. Further, “customer name” 504 is data input to the “name” column 404, “address” 505 is data input to the “address” column 405, and “person in charge” 506 is the “contact” column. The “registrant” 507 is the data input to the “registrant” column 401, the “memorandum” 508 is the data input to the “content” column 407, and “ The “attached file” 509 is an electronic file designated in the “file” column 408.

  As described above, in the first embodiment, in the registration schedule information (see FIG. 4), the date / time input field 403 is stored separately as “start date / time” 502 and “end date / time” 503. In the “registrant” column 401 of the registration schedule information, only the name is extracted and stored. Thus, the predetermined schedule item of the registration schedule information may be stored by performing a predetermined process instead of storing it as it is.

  Furthermore, it is not necessary to add all the schedule items included in the registration schedule information to the acquisition schedule information, and only predetermined schedule items may be selectively acquired.

  Even when one SFA system 110 corresponds to a plurality of groupware systems 120, it is desirable to unify the format of the “acquisition schedule information”. This is because the processing (described later) of the report creation support function 211a can be simplified.

Then, the schedule acquisition function 221 extracts “end date and time” 503 from the acquisition schedule information (see FIG. 5). This “end date and time” 503 is sent to the customer management function 211 of the sales support unit 210 together with the corresponding “event number” 501. The “event number” 501 and “end date / time” 503 received by the customer management function 211 are managed by the date / time management function 302 in the report creation support function 211a (described later).
(3) Report Creation Support Processing by the SFA System 110 The date / time management function 302 in the report creation support function 211a checks the “end date / time” 503 received from the schedule acquisition function 221 for each event at predetermined time intervals. . When it is determined that the current time has reached the “end date and time” of any event, the date and time management function 302 sends an event end notification to the report form creation function 301 and the automatic entry function 303, and “event” It is transmitted together with “Number” 501.

  Upon receiving this event end notification, the report form creation function 301 automatically creates a report form for the report corresponding to the “event number” 501.

  Further, when receiving the event end notification, the automatic entry function 303 receives the acquisition schedule information corresponding to the event number from the schedule acquisition function 221. The automatic entry function 303 automatically enters each schedule item included in the acquired schedule information in the corresponding input field of the report form created by the report form creation function 301.

  FIG. 6 is a conceptual diagram showing an example of this report form 600.

  As shown in FIG. 6, this report form 600 is automatically generated as a new worksheet every time an event end notification is received. In the tab 600a of these worksheets, “ Headings such as “Report 1”, “Report 2”, “Report 3” are attached.

  In each report form 600, input fields 601 to 609 for inputting report items and operation icons 610 to 612 are displayed.

  In the report form 600 of FIG. 6, a “date” column 601 is a column for inputting the creation date of the report. The automatic entry function 303 automatically inputs the date part of the “end date” 503 of the acquisition schedule information (see FIG. 5) in the “date” field 601.

  The “start / end date / time” column 602 is a column for inputting the start date / time and end date / time of the event. The automatic entry function 303 automatically inputs the “start date and time” 502 and the “end date and time” 503 of the acquisition schedule information in the “start / end date and time” column 602.

  The “reporter” column 603 is a column for inputting the name of the reporter. The automatic entry function 303 automatically enters the “registrant” 507 of the acquisition schedule information in the “reporter” field 603.

  The “visit destination” column 604 is a column for entering the name and address of the company that visited the site. The automatic entry function 303 automatically enters the “customer name” 504 and the “address” 505 of the acquisition schedule information in this “visit destination” column 604.

  The “person in charge” column 605 is a column for inputting the person in charge of “visit destination” 604. The automatic entry function 303 automatically fills in the “person in charge” field 605 with the “person in charge” 506 of the acquisition schedule information.

  The “visit type” column 606 is a column indicating the type of visit, and for example, a distinction between first visit / revisit and the like is input. Here, the schedule registration screen (see FIG. 4) does not have an input field corresponding to the “visit type” field 606. Therefore, the acquisition schedule information (see FIG. 5) includes a corresponding schedule item. Not. For this reason, the automatic entry function 303 does not automatically fill in the “visit type” column 606.

  The “importance” column 607 is a column indicating the importance of the visit, and the importance is set by numbers and colors. Here, on the schedule registration screen (see FIG. 4), there is no input column corresponding to the “importance” column 607, and accordingly, the acquisition schedule information (see FIG. 5) includes a corresponding schedule item. Not. For this reason, the automatic entry function 303 does not automatically fill in the “importance” column 607.

  The “report item” column 608 is a column for entering the purpose and result of the visit. The automatic entry function 303 automatically enters “memorandum” of the acquisition schedule information in the “report item” column 608.

  The “file” column 609 is used when an electronic file is to be attached to the schedule registration. The automatic entry function 303 does not automatically fill in the “file” field 609 but automatically attaches an “attached file” 509 of the acquisition schedule information. As a result, the attached file icon 610 is displayed on the report form 600.

  The “search” icon 620 is used when the customer name list is displayed to correct the customer name and address.

  The “Submit” button 612 is an icon for creating an electronic report from the information input in the report form 600 and submitting it to a supervisor or the like.

  The sales staff member confirms the report items automatically entered in the input fields 601 to 605 of the report form 600 and corrects them as necessary. For example, if the report creation date is different from the event end date, the “date” column 601 may be corrected.

  Further, the sales staff member sets the “visit type” column 606 and the “importance” column 607 and corrects / adds the “report item” column 608.

  Then, add / delete attachments as necessary, then click the “Submit” button. As a result, a report based on these report items is created electronically and the submission process is performed.

  As described above, according to the first embodiment, an external groupware system 120 is accessed to acquire a predetermined schedule item for each event, and the schedule item is entered as a report item of the report. Report creation support can be performed without changing the schedule management service received from the groupware system 120.

  Further, according to the first embodiment, when a new event is registered in the groupware system 120, the report form 600 of the report corresponding to the event is automatically created, so that the burden on the user is further reduced. it can.

  Furthermore, according to the first embodiment, the report form 600 of the report is automatically created when the execution date and time of the event (here, the end date and time) is reached. The risk of forgetting can be reduced.

  In addition, according to the first embodiment, one SFA system 110 can support a plurality of types of groupware systems 120. Therefore, even when one company or the like uses a plurality of types of schedule management support services, it can be handled by one SFA system 110. In addition, an operator of one SFA system 110 can provide a report creation support service to a plurality of companies that use different schedule management support services. For this reason, according to this Embodiment 1, report preparation assistance can be implement | achieved cheaply.

100 Network 110 System 120 Groupware System 130 Communication Terminal 140 Internet 400 Schedule Registration Screen 401-409, 601-609 Input Field 409, 410, 609-611 Icon 600 Report Form 600a Tab

Claims (3)

A report creation support system having a support server for supporting creation when a user of a communication terminal electronically creates a report including a plurality of report items,
Authentication information given to a user of the communication terminal for logging in to an external schedule management server that performs a general-purpose schedule management support service is stored in the support server, and the schedule management using the authentication information is performed. The support server is made to log in to the server, the user acquires a predetermined schedule item from the registered schedule information registered for each event in the schedule management server, and each event is recorded using the predetermined schedule item. A schedule acquisition function that generates acquisition schedule information in
A report form creation function for automatically generating a report form having an input field for inputting the report item for each event;
The report item to be input in the input field of the report form is selected from the schedule items included in the acquisition schedule information, and is automatically entered in the input field.
A display function for causing the communication terminal to display the report form that has been automatically entered by the automatic filling function;
Equipped with a,
The schedule acquisition function accesses each of the plurality of schedule management servers that perform separate independent schedule management support services, acquires the registration schedule information from each of the schedule management servers, and generates the acquisition schedule information.
This is a report creation support system. The acquisition schedule information includes execution date information of the event as the schedule item acquired from the registration schedule information, and
The report form creation function automatically generates the report form of the event when the timing determined based on the execution date / time information is reached.
The report creation support system according to claim 1.   3. The report creation support system according to claim 2, wherein the report form creation function automatically generates the report form of the event when the end date and time of the event is reached.

Images