JP2004118466A - Management system of multiple stores by knowledge sharing - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system capable of controlling the managements of a plurality of stores in a form of knowledge sharing. <P>SOLUTION: The page formation part 143 of the Web server 14 of a head office involves, in reference to an information DB 151 and a navigation DB 152, operation information with marked noteworthy data, a link to another page for suggesting data to be examined, and a keyword for following retrieval in pages to be provided to the computer 19 of a store. When a user of the store is guided by the mark or link to trace the pages and requests a knowledge retrieval, a knowledge retrieval part 145 performs the retrieval of a knowledge DB 153 with a set of keywords corresponding to the traced pages. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a system for sharing knowledge among a plurality of stores, and using this knowledge to control the management of each store, and to software for realizing this system.
[0002]
[Prior art]
Conventionally, in systems in which one management entity distributes goods or provides services through multiple stores, such as franchises and sales agents, the management headquarters provides member stores and affiliated stores with information and know-how owned by the headquarters. He gave knowledge of such things and provided management guidance. In addition to this, recently, a Web service technology has been applied, and a system that enables efficient collaborative work with a franchise system (for example, see Patent Document 1), and POS data collected from each store have been processed and the headquarters have been processed. A system has been proposed in which information that changes dynamically, such as sales and costs, can be referred to at any time from a Web browser of a computer in each store.
[0003]
Further, a system is also known in which the know-how of each member is registered in a Web server, and the knowledge is shared among the members by searching the know-how using an index or a keyword. At that time, members who browsed whether or not each know-how was useful register and register information of the usefulness so that useful know-how can be preferentially presented.
[0004]
[Patent Document 1]
JP-A-2002-92295
[Problems to be solved by the invention]
However, with the conventional system, information such as sales and costs can be presented to each store manager and supervisor, etc.However, focusing on which part of this information and how to improve business performance, The degree to which information was used was left to each individual, and the degree of utilization of information varied greatly among individuals. In addition, in a system where each member searches for knowledge using an index, etc., it is still up to each member to determine when each know-how can be used, which leads to improved sales performance across all stores. Had difficulties.
[0005]
The present invention has been made in view of the above-described circumstances, and its purpose is to improve the business performance in each case from information such as sales and costs by as many store managers and supervisors as possible. To get to the same know-how. By providing such a system, the present invention makes it possible for a manager who has a plurality of stores to provide the information without having to individually teach each store manager or supervisor individually or while reducing the time for individual guidance efficiently. Can be reflected in the management of each store.
[0006]
[Means for Solving the Problems]
The management system according to the present invention includes operation information (information such as sales, costs, and employee working conditions) obtained by processing POS data, shift data, and the like collected from a plurality of stores, and a plurality of information related to the store management method. And a database in which knowledge (including know-how) is stored.
[0007]
Providing means for providing the operation information configured so as to be able to be sequentially presented together with guide information suggesting operation information to be followed by users (each store manager, supervisor, etc.) involved in the management of the plurality of stores; A search unit is provided for searching the database for the above knowledge using a plurality of keywords sequentially obtained as the operation information is traced according to the guide information.
[0008]
These providing means and search means can be configured, for example, as follows. The providing means can provide the operation information as a plurality of linked Web pages. More specifically, the created Web page can be transmitted in response to a request from a computer in each store.
[0009]
Software for creating a Web page used in this system has the following features. First, on the created Web page, a noticeable portion (for example, a count) in the operation information is displayed as the above-mentioned guide information so as to be distinguished from others. Further, the system stores which part of the operation information is to be presented next in relation to the notable count of a certain Web page (first Web page), and the Web page (second Web page) containing the operation information is stored. A link that can jump to the first Web page is included in the first Web page. This link also functions as the guide information described above. Also, a keyword is associated with each Web page.
[0010]
When the user receives the first Web page and follows the link included in the first Web page, the computer of the store that has received the second Web page sends a knowledge search request based on the second Web page. (The second Web page is created in such a manner). In response to this knowledge search request, the database is stored in the database using both the keyword corresponding to the second Web page and the keyword corresponding to the first Web page (the Web page before jumping to the second Web page). The retrieved knowledge is searched and the search results are sent to the store computer.
[0011]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0012]
FIG. 1 shows an example of a network configuration according to the present embodiment. For example, in the case of a franchise system, the headquarters 11 and a plurality of stores 12-1 to 12-n are connected by a communication network 13 (for example, the Internet). The headquarters 11 includes a Web server 14 for providing client computers with operation information such as sales and costs and knowledge such as measures for improving sales results, a database 15 for storing such information and knowledge, and a DB server 16 for managing this database. The headquarters 11 may also include a headquarters computer 17 for managing these systems and browsing a headquarters Web page provided by the Web server 14. Each store 12 includes a POS system 18 for collecting POS data serving as a basis of operation information, and a store computer 19 for browsing each store Web page provided by the Web server 14. When the number of stores is large, the stores may be divided into groups, and a branch 20 may be provided for each group. The branch 20 may be provided with a supervisor computer 21 for managing and guiding a plurality of stores in the group. it can.
[0013]
Note that the Web server and the DB server in the present embodiment are realized by executing a program describing an operation described later on a computer suitable for the server. This program can be transferred via a recording medium or a communication medium. In the present embodiment, each function of the Web server 14 and each function of the DB server 16 will be described separately. However, the method of dividing these functions is for convenience of description, and all of these functions are stored on the same server. It can be executed by any of the above methods, and any method of sharing between a plurality of servers may be used.
[0014]
FIG. 2 illustrates a functional module configuration of each of the Web server 14, the database 15, and the DB server 16 in the present embodiment. The DB server 16 manages POS data processing units 161 that process POS data collected from the POS systems 18-1 to 18-n of each store, and manages knowledge contents registered in a navigation DB 152 and a knowledge DB 153 described later. And a knowledge management unit 162. The knowledge management unit 162 is connected to the head office computer 17, and allows the manager to classify and improve sales improvement measures and the like proposed by managers and supervisors at any time and register them in the database 15.
[0015]
The database 15 stores an information DB 151 that stores data from the POS data processing unit 161 as operation information, a navigation DB 152 that stores the content illustrated in FIG. 3A, and a content illustrated in FIG. 3B. And a knowledge DB 153. The reason why the database is divided into three types in this way is for the sake of convenience of explanation. In practice, the database may be integrated or distributed in any form as long as the relation between necessary data is stored. It does not matter.
[0016]
The Web server 14 includes a page request receiving unit 141 that receives a Web page request from each of the store computers 19-1 to 19-n, the supervisor computer 21, and the head office computer 17, and a Web page corresponding to the request as a request source. A page presenting unit 144 for returning to the Web browser of the computer. The web page to be presented is created in advance by the page creation unit 143 and stored in the page storage unit 142, and dynamically created on the spot in response to the received page request. There can be things. The former includes, for example, pages created based on operation information such as sales of the day and navigation information to be described later as shown in FIGS. 4 to 6, and the latter includes related knowledge as shown in FIG. 7, for example. Includes pages showing search results.
[0017]
In the related knowledge search, for example, the page request receiving unit 141 receives an input of a search keyword in an HTML form, the knowledge search unit 145 searches the knowledge DB 153 based on the search keyword, and retrieves a page including the search result. This is realized by creating the page by the page creating unit 143 and returning the page creating unit 144 to the request source. In the present embodiment, when a set of search keywords is received, the knowledge search unit 145 performs a so-called narrow search that narrows down a more appropriate knowledge with the next keyword from the set of knowledge picked up with the first keyword. It will be explained.
[0018]
FIG. 3A exemplifying the contents of the navigation DB 152, FIG. 3B exemplifying the contents of the knowledge DB 153, FIGS. 4 to 7 which are examples of Web pages displayed on the store computer 19, The operation of the system according to the present embodiment will be described in detail with reference to FIG. 8, which is a flowchart illustrating an example of a page creation process in the server 14.
[0019]
The contents of the information DB 151 are updated, for example, once a day, reflecting daily business activities. When the operation information of the information DB 151 is updated, a Web page for presenting the operation information to each store manager or supervisor is also updated by the page creation unit 143. The page creation unit 143 first creates a page of level 1 (entire) as shown in FIG. 4 (S81 in FIG. 8). The format of the table in FIG. 4 is stored in advance in the navigation DB 152 as the format of a page called “entire count check” (not shown in FIG. 3A). Each data read from the information DB 151 is written in a table according to this format.
[0020]
Then, the data of each item in this table (for example, the "budget ratio" of "sales yesterday" in the table of FIG. 4 is 92.4%, and the data of the item "total sales budget ratio" is 92.4%). 4%) is compared with the "reference value" (100% in FIG. 3A) stored in the navigation DB 152. If the value of the data differs from the "reference value" by more than the "permissible range" (5% in FIG. 3A), a page is created so that the data is marked and displayed (S811 in FIG. 8). In the example of FIG. 4, when the result is poor beyond the “permissible range” from the “reference value”, the number is surrounded by a circle, and when the result is good beyond the “permissible range”, the numeral is underlined. A line is attached to draw the user's attention. These markings may be made by changing the color of the numbers. Marking when performance is poor is to make it clear at a glance the need for improvement.However, marking when performance is good can sometimes lead to sales improvement measures from analysis of successful cases. This is taken into account.
[0021]
The navigation DB 152 includes knowledge for presenting to the user what data is to be examined in further analyzing the noted number, in addition to the knowledge for marking the noted number. That is, in the example of FIG. 3A, when the “total sales budget ratio” is not within the allowable range, a page “sales by item” is prepared as “information to be presented next”. The page creation unit 143 creates a link to a page corresponding to the next level (level 2) of “sales by item”, and embeds this link in the “total count check” (level 1) page (FIG. 8). S812). Thus, for example, in FIG. 4, when the user clicks the marked number of 92.4%, the page jumps to the page of FIG. Similarly, another link is embedded so that clicking on the marked number of the customer unit price of 72.8% compared to the previous year jumps to another page called “Item-based customer unit price”.
[0022]
Next, the page creating unit 143 starts creating a page of level 2 (S82 and S83 in FIG. 8). Taking the above-mentioned "sales by item" page as an example, a table format as shown in FIG. 5 is stored in advance in the navigation DB 152 as a page format of "sales by item" (FIG. 3 (a) Each data read from the information DB 151 is written in a table according to this format (not shown).
[0023]
For pages at level 2 and lower levels (displayed following one or more links), a “keyword” corresponding to the page is written in, for example, the HTML source of the page (S831 in FIG. 8). ). As stored in the navigation DB 152 of FIG. 3A, for example, the “keyword” corresponding to the “sales by item” page is “sales”. This keyword can be a so-called hidden keyword that does not appear on the page itself shown in FIG. This keyword will be used in a related knowledge search described later.
[0024]
The data of each item in the above table (for example, in the column of “budget ratio” of “gyudon” in the table of FIG. 5, the data of the item of “gyudon sales budget ratio” is 90.6% 99.1% and 87.6% of the special scale) are compared with the “reference value” (100% in FIG. 3A) stored in the navigation DB 152. If the value of the data is different from the “reference value” by more than the “permissible range” (5% in FIG. 3A), the data is marked (for example, a circle when it is bad, and an underline when it is good). ) To create a page to be displayed (S832 in FIG. 8).
[0025]
The page creation unit 143 further refers to the navigation DB 152 of FIG. 3A and, when the “gyudon sales budget ratio” is not within the allowable range, sets “gyudon sales” as “information to be presented next”. A page called "Transition" is prepared. The page creation unit 143 creates a link to a page corresponding to the next level (level 3) called “gyudon sales transition”, and embeds this link in the “item sales” (level 2) page (FIG. 8 S833). Thereby, for example, in FIG. 5, when the user clicks the button “Transition” corresponding to the “budget ratio” of the marked “gyudon”, the page jumps to the page of FIG. Similarly, if you click the button labeled “Change” corresponding to the “budget ratio” of the marked “set meal”, another link is embedded so that it jumps to another page called “set meal sales change” Have been.
[0026]
Further, for example, when the user clicks a “Related Knowledge Search” button on the upper right of the screen in FIG. 5, the page creation unit 143 searches for a search request that includes a “keyword” of “sales” corresponding to this page (for example, A mechanism for transmitting the HTML form (described above) from the client computer to the knowledge search unit 145 via the page request reception unit 141 is embedded in the “sales by item” page (S834 in FIG. 8). This mechanism is realized, for example, by describing the above operation as a script in the HTML source of the “sales by item” page.
[0027]
In the example of FIG. 5, in addition to the item-by-item sales table, a total sales check table (a part of the one shown in FIG. 4) which is likely to be helpful in conducting the analysis is also presented. A link is provided so that you can jump to a change in sales (such as "Change in daily sales" at the bottom of the screen). Also, although the table of sales by item in FIG. 5 shows the data of that day, the date is displayed in the column of “display yearly, month, and day of sales by item” so that data of another date can be browsed. You can enter it and click it to jump to a page showing the data for that date. In this way, the user also presents the information of the higher level already displayed and the related link to another page of the same level to the user together with the information and the related link of the corresponding level of the page. In order to assist the user in determining what to look for, the knowledge for this is stored in advance in the navigation DB 152 in the form of a page.
[0028]
Thus, the “sales by item” page is completed. The page creation unit 143 creates another page of level 2 (for example, “customer unit price by item”) in the same manner (No in S84 of FIG. 8 and returns to S83).
[0029]
When all the level 2 pages are completed, the page creation unit 143 starts creating a level 3 page (No from S85 in FIG. 8 and returns from S86 to S83). Taking the above-mentioned “gyudon sales transition” page as an example, a table format as shown in FIG. 6 is stored in advance in the navigation DB 152 as a “gyudon sales transition” page format (FIG. 3A). , Each data read from the information DB 151 is written in a table according to this format.
[0030]
Referring to the navigation DB 152 in FIG. 3A, since “gyudon / time zone” is stored as a “keyword” corresponding to the “gyudon sales transition” page, this is hidden in the HTML source of that page. It is written as a keyword (S831 in FIG. 8). Then, the data of each item in the above table is compared with the respective "reference value", and the data exceeding the "permissible range" is marked (S832 in FIG. 8).
[0031]
Further, the page creation unit 143 executes the script so that a search request (for example, the HTML form described above) to the knowledge search unit 145 is transmitted when the button of “relevant knowledge search” at the upper right of the screen in FIG. 6 is clicked. Is embedded (S834 in FIG. 8). For pages at level 3 and lower levels (displayed following two or more links), the search request includes not only the keyword of the current page, but also the Include keywords. The information of the link source page that has been displayed before can be referred to by using the back function of the Web browser. In this example, the keyword “sales” corresponding to the previous link source page (“sales by item”) and the “gyudon / time zone” corresponding to the current page (“gyudon sales transition”) From the “keyword”, a set of search keywords “sales / gyudon / time zone” is created and included in the search request. Further, in the case of a lower-level page, not only the link source immediately before but also the keywords of all the pages that have been visited up to that point are arranged in order from the uppermost to the lowermost to form a set of search keywords.
[0032]
In this way, the “Gyudon sales transition” page is completed. The page creation unit 143 creates another page of level 3 and, when level 3 ends, creates a page of level 4 and ends all levels (“information to be presented next” is displayed in the navigation DB 152). When the information DB 151 is reached), a series of processes involved in updating the information DB 151 ends (Yes in S85 in FIG. 8).
[0033]
In the above example, it has been described that pages are created one by one from the upper level to the lower level. However, these can be processed simultaneously and in parallel, and the pages related to the updated data can be processed. Can be selectively processed.
[0034]
The page created and updated by the page creation unit 143 in this way is stored in the page storage unit 142. Then, when the page request receiving unit 141 receives the first page request from the Web browser of the store computer 19-1 (for example, Ebisu store), the first page for the store shown in FIG. It is read out, sent to the store computer 19-1 via the page presenting section 144, and displayed on the Web browser. When the user (the store manager in this case) clicks on the point indicated by the arrow in FIG. 4, the page request is received by the page request receiving unit 141, and FIG. 5 is read from the page storage unit 142 and displayed on the Web browser. . Similarly, when the point indicated by the arrow in FIG. 5 is clicked, FIG. 6 is displayed.
[0035]
When the button of “search for related knowledge” is clicked in FIG. 6, as shown in FIG. 7, the knowledge set searched for from the knowledge DB 153 (FIG. 3B) by the keyword group “sales / gyudon / time zone” is displayed. The title, registrant, registration date, etc. are displayed. If you click on the title of the knowledge you want to read here (for example, "How to shorten rice meal"), you will see know-how on how to avoid the unnecessary operation of the appropriate amount of rice, for example. You.
[0036]
Note that when the "Related Knowledge Search" button is clicked in FIG. 5, the page of the search result as shown in FIG. 7 is displayed. However, since the search keyword is only "sales", FIG. Will be selected and displayed.
[0037]
That is, as described above, when a hidden keyword is included in a page and a related knowledge search is instructed, the knowledge DB is searched with a set of keywords arranged according to the display history of the page. Then, the operation of following the page corresponds to the fact that a search keyword is added every time the page is traced to perform a narrow-down search of knowledge.
[0038]
In the above, an example in which the hidden keyword is written in the HTML source of the page has been described. However, other mounting methods are also possible. For example, there is a method in which, for example, address information (URL) for specifying each Web page and a keyword corresponding to the Web page are stored in the storage area of the knowledge search unit 145 when the Web page is created. In this method, it is not necessary to send the keyword corresponding to each Web page to the client computer, and the search request sent from the Web browser includes the address information (URL) of the Web page followed by the user and responds to this. The knowledge search unit 145 checks the keyword and executes a search.
[0039]
In the example of FIG. 7, when the search result is displayed, what kind of keyword was searched in the form of "(result, beef bowl, time zone), there were eight results." Display it on the screen, and display hint keywords related to this word at the bottom left of the screen, and let the user refer to them and try re-searching with another keyword using the "free word search" section. I can do it. The hint keyword is stored in the knowledge DB 153 in advance as a part of knowledge (not shown in FIG. 3B).
[0040]
Further, the knowledge registered in the knowledge DB 153 can be classified and stored for each purpose, ranking (usefulness), and work as shown in FIG. 3B. , It is also possible to display by index.
[0041]
FIG. 9 shows a case where the page request receiving unit 141 reads out the page request from the page storage unit 142 and receives the page presenting unit 144 when the first page request is received from the Web browser of the supervisor computer 21 (for example, in charge of the West Tokyo area). 5 is an example of a page displayed on a web browser of a supervisor via the web browser. The supervisor page is designed to collectively display information on a plurality of stores in charge. Although illustration of the screen is omitted, information of all stores can be presented together on the Web browser of the head office computer 17.
[0042]
When the administrator registers new knowledge or organizes old knowledge from the head office computer 17, not only the contents of the knowledge DB 153 but also the contents (navigation information) of the navigation DB 152 are updated as necessary. These knowledges are obtained, for example, by recruiting from store managers and supervisors (users of this system), and selecting and consolidating by an administrator.
[0043]
In the above example, all the pages are created and stored in the page storage unit 142 when the information DB is updated. However, for some or all of the pages, the page request reception unit 141 sends a page request from the client to the page request. When receiving the request, the page creation unit 143 may read the data of the information DB 151 corresponding to the requested page and return the page created by performing the processing of S81 or S83 in FIG.
[0044]
As is clear from the specific example described above, in this embodiment, the server of the headquarters marks (highlights) the data to be focused on by using the navigation information, and suggests the data to be examined next. For the user to follow the pages guided by these marks and links, the user narrows down the search for knowledge using keywords corresponding to each page. In this manner, according to the management system in the present embodiment, it is possible to guide (navigate) so that as many users as possible can reach appropriate knowledge from operation information such as sales and costs. That is, operation information and knowledge are shared between users, and navigation up to how to use the shared knowledge is provided by the system. The sharing and navigation of such knowledge can be made to reflect, for example, the intentions of the franchise headquarters, so that each store manager and supervisor can use the shared knowledge according to this navigation and obtain the information. If each store is managed or operated according to the search results, the management of the entire franchise will be controlled according to the will of the management entity.
[0045]
Hereinafter, an example of another embodiment of the present invention will be described in detail. FIG. 10 is a level 1 screen presented to a store manager of a certain store. The screen of FIG. 10 refers to a previously stored web page format of “total count check of yesterday” and writes information read from the database into a table, similar to the creation of the screen of FIG. It is created by marking numerical values that are out of tolerance from the values. The format of the Web page in FIG. 10 indicates that the manager who knew yesterday's sales situation was bad should investigate the cost situation, sales promotion activity situation and delivery time yesterday. Reflected and built. In this case, I saw this because there was a mark indicating that the delivery time yesterday deviated from the reference value at the peak of the night (the actual delivery time exceeded the specified time). The manager clicks on that part. Then, the screen jumps to the screen of FIG. 11 by the link embedded in that part. The keyword “delivery time / night peak” is associated with the Web page (or a link thereto) in FIG. 11, and the correspondence is illustrated in FIG. It is assumed that it does not appear on the screen and is hidden.
[0046]
The screen of FIG. 11 refers to a Web page format of “delivery time / sales / staff status” stored in advance and creates information read from the database in the same manner as the screen of FIG. 5 (level 2). It is created by writing in a table and marking values that are out of tolerance from the reference values. In the form of the Web page in FIG. 11, the manager who knew that there was a problem with the delivery time yesterday, made the making time, the delivery time, the number of delays, the number of customers, the number of staff in the store and the delivery for each time zone yesterday. The number has been built in light of the management's willingness to conduct a survey, in light of the situation over the past two weeks.
[0047]
Here, the number of delivery staff at 18:00 to 19:00 is marked not by direct comparison with the reference value as in other numerical values, but by the delivery time of the corresponding time zone deviating from the reference value. This is because the condition of marking when the user is present is stored in the navigation DB. Similarly, since the delivery time and the making time are out of the reference values at 19:00 to 20:00, the numbers of staff members for both the delivery and the in-store are marked. The store manager who sees the screen of FIG. 11 knows that the staff in the problematic time zone should be checked, and clicks on that part (in this example, the number of delivery staff at 19:00 to 20:00). Then, the screen jumps to the screen of FIG. 12 by the link embedded in that part. It should be noted that the keyword “number of employees / delivery” is associated with the Web page (or a link thereto) in FIG. 12, and the correspondence is illustrated in FIG. 11, but this keyword is displayed on the screen. It does not appear above and is hidden.
[0048]
The screen shown in FIG. 12 refers to a previously stored “Shift Table” Web page format in the same manner as the screen shown in FIG. 6 (level 3), and designates the designated data (here, yesterday's 19-20 It is created by reading the information of the staff who was delivering at the store at times from the database and writing it in the table. In the example of FIG. 12, marking is not performed by comparison with the reference value. Such staff information can be obtained as shift data from a database for work management. On the screen of FIG. 12, a magnifying glass mark indicating a link to the related knowledge is displayed, and when this is clicked, the same processing as when the related knowledge search button is clicked in FIG. 6 is performed. Jump to the screen.
[0049]
That is, the knowledge DB is combined with the keyword “delivery time / night peak” specified when shifting to the screen of FIG. 11 and the keyword “number of employees / delivery” specified when shifting to the screen of FIG. Are displayed as shown in FIG. In FIG. 13, as with the example of FIG. 7, what kind of keyword was searched for is displayed as “(Results searched for (delivery time / night peak / personnel number / delivery)) There are three results” In addition, a hint keyword (“work assignment, recruitment, delivery speed” in this example) is presented as another keyword as a proposal when the user is not satisfied with the search result, and the user refers to the hint keyword to search for “free word search”. To try to search again. Further, the example of FIG. 13 also indicates whether each searched knowledge is indispensable. This is for discriminating whether each store manager must refer to the knowledge and implement it as described in the knowledge, or whether the knowledge should be viewed only for reference. By separately presenting essential knowledge in this way, the intention of the management entity can be more clearly conveyed to each store manager.
[0050]
In the above example, by clicking the “Related Knowledge Search” button in FIG. 6 or the “magnifying glass” mark in FIG. 12, the keywords corresponding to the pages in FIG. 6 and FIG. And a page of the knowledge search result as shown in FIG. 7 or FIG. 13 is presented. As another example, it is also possible to configure so that when a specially marked numerical value portion of a certain page is clicked, a page of the knowledge search result is jumped. For example, in the example of marking numbers that deviate from the reference value in red, numbers in which a link to the page of the knowledge search result is embedded are marked in green. Then, the keyword is also associated with the page (knowledge search result page) indicated by the link corresponding to the special marking, and not only the keyword up to the page one level higher than the knowledge search result, but also the knowledge search result page Search for knowledge is also performed by multiplying the keyword by the keyword, and the search result is presented in the page.
[0051]
FIG. 14 shows how the table presented in FIG. 11 is created by collecting various data, for example. The format of this table is stored in advance in the navigation DB, but presents data that the manager considers to be checked by each store manager when there is any problem. It is preferable to collect and present necessary parts from some existing data instead of presenting the data as it is. As shown below the dotted line in FIG. 14, the existing forms include a list of individual orders, sales / number of items by time zone, daily attendance data, and the like. This system extracts the making time and delivery time information from the individual order list by time zone, extracts a part of the sales / number information from the hourly sales / number, and the staff by hour from the daily attendance data. The number information is extracted and written in the table shown above the dotted line in FIG. In addition to this, data inputted daily by the store manager to the system include weather information and the number of delays, and these are also extracted and written in a table.
[0052]
In FIG. 2, POS data collected from the POS system is taken as an example of data to be entered in the information DB. However, as shown in FIG. 15, data of various existing databases is unified in CSV format or XML format. Thereby, it can be incorporated into the knowledge / information database (corresponding to the database 15 in FIG. 2) of the present system. Existing databases include POS systems and other systems for managing various sales information including sales, employee masters, systems for managing personnel information such as attendance and shift data, and product-related information such as purchasing information and inventory information. There is a system that manages customer information such as customer name and purchase history, a system that manages map information and trade area information linked to it, an existing knowledge database, a system that manages existing sales information and other sales information. In cooperation with these databases, data used in the present system can be fetched. In this case, the present system has a knowledge / information management function corresponding to the DB server 16 in FIG. 2, and takes in data in cooperation with an external database, processes the captured data, and performs knowledge / processing of the processed data. Writes to the information database, etc. In this example, not only the knowledge count data corresponding to the operation information is written, but also the knowledge data obtained in cooperation with the existing knowledge database is written.
[0053]
Further, in the above example, the franchise headquarters 11 collects and manages various data and knowledge, stores these information and knowledge in a database, and presents the stored information and knowledge to each store manager and supervisor according to the navigation data. Although the processing has been described as being performed, it is also possible for an ASP (application service provider) to provide these processings as a general-purpose business support system using the Internet. In this case, the computer of the ASP company fetches the operation data including the POS data into the database, processes the fetched data by the business application, and displays the data on the screen.
[0054]
Here, in the above-mentioned business support system, various data taken in the database have a predetermined structure optimized for a specific user organization. Further, a business application that determines what data is obtained from the database and how to display it (for example, specific screen configurations shown in FIGS. 4 to 7 and FIGS. 9 to 13) is also unique to each user organization. Content. Therefore, when an ASP provider provides a business support system having the same function as a business support system provided to a certain user organization (for example, franchise A) to another user organization (for example, franchise B), Rather than rebuilding the system entirely to the specifics of the organization, the following mechanisms can be used to minimize additional costs and construction time.
[0055]
In other words, as shown in FIG. 16, a common data format is created between a plurality of user organizations, and this is used as a hierarchical standard data structure (data template) as XML DTD (Document Type Definition: XML schema language). ) Is defined (described) in advance. When sales data of a specific user organization is input, the sales data is temporarily stored in a ledger database, data is extracted from the ledger database in accordance with the description of the DTD, an XML document is generated, and the XML document is stored in the XML document database. . A layout for displaying the XML document is defined (described) in advance for each user in a style sheet such as XSL (Extensible Style Language). That is, the style sheet defines which data of the data template is to be acquired and what kind of screen configuration is to be displayed. Then, in accordance with the description of the style sheet, a screen for displaying the contents of the XML document database is created, distributed via the Internet, and displayed on the screen of a user belonging to the specific user organization.
[0056]
As a result, when trying to provide a new user organization with the same functions as those of a user organization that has already provided services, data extraction and presentation can be performed within the defined data format and display layout. It is not necessary to rewrite the program to be performed, and the maintenance is easy because the scope of the change is small, and a highly versatile business support system that is not tied to a specific user organization can be realized.
[0057]
It is needless to say that the present invention is not limited to the above embodiment, and those skilled in the art can modify and apply the above embodiment within the scope of the present invention. For example, a hierarchically structured document such as HTML or XML described above may be printed and displayed instead of or in addition to screen display.
[0058]
【The invention's effect】
As described above, according to the present invention, a system connected to a plurality of stores provides operation information and knowledge to each store, for example, in the form of a Web page, thereby sharing knowledge. When providing the operation information, it is possible to provide guidance information together with a distinctive display of a portion to be noted of the operation information and a link to a Web page including the operation information to be examined next in connection with the information. In addition, when the computer at the store receives the Web page following these links, the knowledge search can be performed by grouping the keywords corresponding to each Web page retroactively. According to the present invention, by providing such navigation from operation information to appropriate knowledge, the system can control the management of a plurality of stores in the form of sharing knowledge.
[Brief description of the drawings]
FIG. 1 is a diagram showing an example of a network configuration according to an embodiment of the present invention.
FIG. 2 is a diagram showing an example of a functional module configuration of a server and a database according to the embodiment.
FIG. 3 is a diagram showing an example of contents of a navigation DB and a knowledge DB according to the embodiment.
FIG. 4 is a view showing an example of a Web page displayed on a store computer.
FIG. 5 is a view showing an example of a Web page displayed when one link is designated from the Web page of FIG. 4;
FIG. 6 is a view showing an example of a Web page displayed when one link is designated from the Web page of FIG. 5;
FIG. 7 is a diagram showing an example of a knowledge search result page displayed when a predetermined position of the Web page in FIG. 6 is designated.
FIG. 8 is a diagram showing contents of a Web page creation process in the embodiment.
FIG. 9 is a view showing an example of a Web page displayed on a supervisor computer.
FIG. 10 is a view showing another example of a Web page displayed on the store computer.
11 is a view showing an example of a Web page displayed when one link is designated from the Web page of FIG. 10;
FIG. 12 is a view showing an example of a Web page displayed when one link is designated from the Web page of FIG. 11;
FIG. 13 is a diagram showing an example of a knowledge search result page displayed when a predetermined position of the Web page in FIG. 12 is designated.
FIG. 14 is a view showing a method of creating information displayed on the Web page of FIG. 11;
FIG. 15 is a diagram showing an example of another embodiment of the database 15 and the DB server 16 in FIG. 2;
FIG. 16 is a diagram showing an example of a system configuration in a case where an ASP provider provides the functions of a headquarters 11 of FIG. 1;
[Explanation of symbols]
11 headquarters
12 stores
13 Communication Network
14 Web server
15 Database
16 DB server
17 Computer for headquarters
18 POS system
19 Computer for store
20 chapters
21 Supervisor Computer
141 Page request reception unit
142 page storage
143 Page Creation Department
144 Page Presentation
145 Knowledge Search Department
151 Information DB
152 Navigation DB
153 Knowledge DB
161 POS data processing unit
162 Knowledge Management Department

Claims (10)

An operation information database that stores operation information obtained by processing data collected from a plurality of stores;
A knowledge database that stores a plurality of knowledge relating to a store management method in association with a keyword,
Providing means for providing the operation information configured to be able to be sequentially presented, together with guidance information suggesting operation information to be followed by a user involved in the management of the plurality of stores;
A management system comprising: a search unit configured to search the knowledge database using a plurality of keywords sequentially obtained as operation information is traced according to the guide information. 2. The management system according to claim 1, wherein the providing unit provides the operation information as a plurality of linked Web pages. The providing means displays the provision of the guide information such that a portion to be focused on in the operation information is distinguishable from other portions, and operation information to be next presented in relation to the portion to be focused on is provided. 3. The management system according to claim 2, wherein the management system is provided by providing a link to a Web page that includes the management information. The providing means provides a keyword in association with each of the Web pages,
3. The management system according to claim 2, wherein the search unit searches the knowledge database by using a plurality of keywords corresponding to a plurality of Web pages traced by a user. The providing unit includes: a creating unit that creates a Web page; and a unit that transmits the created Web page in response to a request from a computer of each store.
The creating means reads the information of the operation information database, reads the Web page, and displays a portion to be noted in the operation information separately from other portions. 3. The management system according to claim 2, wherein the management system is created by including a link to a Web page including operation information to be presented next. The providing unit includes: a creating unit that creates a Web page; and a unit that transmits the created Web page in response to a request from a computer of each store.
The creating means associates a keyword with each of the Web pages, and when the user makes a search request based on a certain Web page, the search means matches the keyword corresponding to the certain Web page with the Web traced by the user so far. 3. The management system according to claim 2, wherein a Web page is created so as to perform a search using a keyword of the page. Means for processing data collected from a plurality of stores and storing it as operation information;
Means for creating a Web page presenting a part of the stored operation information, wherein the Web page is configured to display a count to be focused on separately from other counts;
Means for transmitting the created web page in response to a request from a computer in each store;
Means for searching a database in which a plurality of knowledge on a store management method is stored using a keyword,
The creating means associates a first Web page with a first keyword, and includes a second Web page including operation information to be presented next in relation to a notable count of the first Web page. And the second Web page is associated with a second keyword, and when the database is searched based on the second Web page, the searching means includes the second Web page. A management system which is created so as to use one keyword and the second keyword. It has a database in which operation information obtained by processing data collected from a plurality of stores and a plurality of knowledge related to a store management method are stored, and a Web page is transmitted in response to a request from a computer of each store. A program executed by a computer system having a function, which is a Web page that presents a part of the operation information, and that creates a Web page in which a notable count is displayed separately from other counts. Program code for
A program code for associating a keyword with the created web page and including a link for jumping to a web page including operation information to be presented next in relation to the target count;
When a search is made from the plurality of knowledges based on the Web page, a keyword corresponding to the Web page and a keyword corresponding to the Web page before jumping to the Web page are created. And a program code for including a mechanism for performing a search by using a program. A method of controlling the management of the plurality of stores, using a database in which operation information obtained by processing data collected from a plurality of stores and a plurality of knowledge are stored,
A first Web page that presents a part of the operation information so that a count to be focused can be distinguished from other counts is associated with a first keyword, and is presented next in relation to the count to be focused. Created to include a link to a second web page containing operation information to be
Transmitting the first Web page in response to a request from the store computer,
When a Web page is requested by designating the link from the computer of the store, the second Web page associated with the second keyword is transmitted;
When receiving a knowledge search request based on the second Web page from the computer at the store, performing a search from the plurality of knowledge using the first keyword and the second keyword. Management control method. Based on a data format common to a plurality of user organizations, the operation information collected and stored in the user organization is input, and a ledger database for temporarily storing the document information and a document format defined in advance as a document type definition of the hierarchical structure document are used. A document database for storing data read from the database as a hierarchical document,
Means for displaying a hierarchically structured document stored in the document database based on a layout for a specific user organization described in advance as a style sheet of the hierarchically structured document.

Images