JP2004192336A - Program for collecting bulky refuse - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To set a suitable collection date in preparing a bulky refuse collection plan and to promote the recycling of collected bulky refuse. <P>SOLUTION: A program for collecting bulky refuse includes a step for storing a collection reservation data in a collection reservation data storage part when collection reservation data concerned with a collection reservation in a prescribed period are received from a terminal of a bulky refuse collection requester and a step for registering any one of collection dates set in the prescribed period in the collection reservation data storage part correspondingly to the collection reservation data of the collection reservation in the prescribed period on the basis of a prescribed rule in detecting that the collection date set by the collection reservation data including data for specifying a specific collection date in the prescribed period reaches the previously set date. The program includes also a step for transmitting collection article data included in the collection reservation data of the collection reservation to a terminal which is operated by a taking over requester in accordance with a request from the taking over requester. <P>COPYRIGHT: (C)2004,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to an information processing technique for collecting bulky waste.
[0002]
[Prior art]
Collection of bulky refuse is usually performed by a government agency in accordance with the recovery plan. The collection plan compiled by the administrative organization includes information such as the date of collection and the place of collection, and the person in charge of collection at the administrative organization (the person who actually performs the collection work) or a private collection company requested by the administrative organization ( Hereafter, the collection agency, including the person in charge of collection at the administrative agency) collects oversized garbage by patroling the collection site on the collection day. Those who wish to collect oversized garbage should bring the oversized garbage to the collection place or place it around their home on the collection date determined by the administrative agency.
[0003]
There are various modes for collecting collection plans depending on the administrative organization. For example, there are cases where the request of the collection applicant is considered, such as the desired date and time of collection, and in the same way as general garbage, the location and date and time (for example, , Once every month on the second Saturday, etc.). Each operation has its advantages and disadvantages. For example, when the demands of the collection applicants are considered, unnecessary patrols can be eliminated for collection, but it is necessary to create a collection plan each time, which is troublesome. On the other hand, if the location and date and time are determined in advance, the collection plan created once can be used every time. Lack of efficiency.
[0004]
In order to efficiently collect such bulky waste, there is a system for generating a collection route (for example, see Patent Document 1). In other words, the user operates a reception terminal installed at the store of a 24-hour store, and the user performs an oversized garbage collection application and purchases a garbage collection ticket. The oversized garbage collection center lists the collection points for each collection day based on the oversized garbage collection application information from the reception terminal, and creates the shortest collection circulation route. The collection vehicle travels around the collection site according to the collection circulation route to collect oversized garbage.
[0005]
[Patent Document 1]
JP-A-2002-60004
[0006]
[Problems to be solved by the invention]
However, according to the above-described conventional technology, it is possible to improve the efficiency of collection when the place and date and time are determined in advance, but an appropriate collection plan when considering the demands of the collection applicant is considered. The method of creation is not shown.
[0007]
In addition, the type of oversized garbage is known only to the applicants for collection of oversized garbage, administrative organizations, and collection companies, and for example, those who want to take over depending on the type of oversized garbage (individual or business) ), It is not possible to know the type of bulky waste before it is collected. Further, even when there are many applicants for picking up specific articles due to factors such as seasons, the supply and demand balance in recycling is not balanced because collection of specific articles is not performed in a focused manner.
[0008]
Therefore, an object of the present invention is to provide an information processing technique for setting an appropriate collection date in creating a bulky waste collection plan.
[0009]
Another object of the present invention is to provide an information processing technique for promoting recycling in collecting bulky waste.
[0010]
[Means for Solving the Problems]
According to the present invention, the information processing method for oversized garbage collection includes, when receiving collection reservation data regarding collection reservation within a predetermined period from a terminal of a bulk garbage collection applicant, the collection reservation data storage unit. Storing, and when it is detected that the number of collection days set by the collection reservation data including the data specifying the specific collection date within the predetermined period has reached the preset number of days, Registering any one of the set collection dates within a predetermined period based on a predetermined rule with collection reservation data related to collection reservation within the predetermined period in the collection reservation data storage unit.
[0011]
In this way, a person who wishes to collect oversized garbage can make a collection reservation by designating a specific collection date or without specifying a specific collection date. In addition, when the set number of days of collection days reaches a preset number of days, one of the set collection days includes, for example, collection dates of collection reservations that do not specify a specific collection day. As a result, the planning of the collection plan is labor-saving.
[0012]
Further, in the present invention, as a collection fee corresponding to collection reservation data including data permitting a collection date different from the desired collection date to be set, a collection fee including data designating a specific collection date within a predetermined period is set. The configuration may further include a step of setting a lower price than the collection fee corresponding to the reservation data. As a result, for those who do not care about the desired collection date, the collection date will not be as desired but the collection fee will be reduced, and it is possible to balance the profit with the collection date designated person It becomes.
[0013]
In the present invention, a step of transmitting collected item data included in the collection reservation data related to the collection reservation stored in the collection reservation data storage unit to a terminal operated by the collection applicant according to the request of the collection applicant. May be further included. In this way, selectable items can be presented to those who wish to collect bulky garbage (collected products) if they are desired, and recycling can be promoted.
[0014]
Further, in the present invention, when receiving data relating to the collection of a specific collection item from the terminal of the collection applicant, the collection reservation data stored in the collection reservation data storage unit and including the data of the specific collection item is included in the collection reservation data. Setting a fee related to the collection of the specific collected product based on the corresponding collection fee, and further including a step of storing data regarding the collection of the specific collected product in the collection data storage unit, including the data of the fee. There may be. In this way, for the collected item determined to be collected, the collection fee borne by the collection person can be automatically set based on the collection fee of the collected item. In some cases, the collection fee of a person who wishes to collect the above specified collection item may be free.
[0015]
Further, in the present invention, when the collection date within the predetermined period is designated and the collection reservation data including the data of the predetermined collection enhanced item is received, the case where the number of collection days for the collection enhanced item is exceeded is exceeded. Except for this, the computer may further execute a registration step of registering the designated collection date in the collection reservation data storage unit in association with the collection reservation data including the data of the enhanced collection item.
[0016]
As a result, it is possible to designate a special collection date for the collection enhanced collection item within the limited collection days of the collection enhanced item. That is, it is possible to collectively collect specific items (articles).
[0017]
The program for implementing the method according to the present invention and the program according to the present invention are stored in a storage medium or a storage device such as a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, and a hard disk. In addition, it may be distributed as a digital signal via a network. The data being processed is temporarily stored in the memory of the computer.
[0018]
BEST MODE FOR CARRYING OUT THE INVENTION
FIG. 1 shows a system configuration diagram according to an embodiment of the present invention. For example, the administrative institution terminal 3, the collection applicant terminal 7, the collection applicant terminal 9, and the collection company terminal 11, which are personal computers, have a Web (Web) browser function and a mailer function (not shown), and have a wireless or wired connection. Thus, it is possible to browse a homepage by connecting to the network 1 which is the Internet, for example, and to send and receive mail. The network 1 is also connected to a bulky waste collection management server 5 that manages a bulky waste collection plan, receives a collection reservation, and the like.
[0019]
In addition, the number of administrative organizations, collection applicants, collection applicants, and collection companies that use the system is not limited, and accordingly the number of terminals is not limited. Further, a configuration in which a plurality of computers cooperate to operate as the bulky waste collection management server 5 may be employed.
[0020]
The communication via the network 1 uses devices and functions necessary for Internet connection and mail transmission and reception, such as a domain name server (DNS), a mail server, and a firewall (not shown). And
[0021]
The bulky waste collection management server 5 includes a collection plan processing unit 500, a collection reservation processing unit 502, a collection reservation processing unit 504, and a collection schedule processing unit 506. These processes will be described in the description of the process flow. The bulky waste collection management server 5 manages a collection range master database (DB) 512, a collection item master DB 514, a collection reservation master DB 516, a collection master DB 518, a calendar master DB 520, a calendar work 522, and a map DB 524. ing.
[0022]
The calendar master DB 520 stores calendar data relating to the date and day of the week, and the oversized garbage collection management server 5 may generate page data including, for example, the current month's calendar using the calendar data. it can. The calendar work 522 stores temporary data in which the calendar data is associated with the data (for example, the collection date) related to the bulky waste collection, and stores the page data in each process related to the bulky waste collection described later. Used to generate data. Further, map image data and address data are stored in the map DB 524 in association with each other, and are used for setting a collection place of oversized garbage. In some cases, data on the collection location may be kept separately.
[0023]
Next, an example of a table configuration and stored data in the collection range master DB 512, the collection item master DB 514, the collection reservation master DB 516, and the collection master DB 518 are shown in FIGS.
[0024]
FIG. 2 shows an example of a table configuration of the collection range master DB 512. In the example of FIG. 2, the column 200 of the range start date, the column 202 of the range end date, the column 204 of the number of collections, the column 206 of the enhanced item setting, the column 208 of the collection date 1, the column 210 of the collection date 2, and the enhanced item A collection date column 212 and a registration date column 214 are included. Between the column 210 of the collection date 2 and the column 212 of the enhanced item collection date, for example, a column of the collection date n (n is a positive integer) is included. In the present embodiment, n is, for example, up to 5. It has a certain configuration. That is, between the column 210 of the collection date 2 and the column 212 of the enhanced item collection date, a column of the collection date 3, a column of the collection date 4, and a column of the collection date 5 (not shown) are included. n is the maximum number of collections that may be set within a predetermined period (for example, two weeks), and may be any number. In some cases, a plurality of enhanced item collection date columns are provided.
[0025]
In this table, data on the collection plan is registered. When a new record is generated, the value in the range start date column 200, the value in the range end date column 202, the value in the collection count column 204, and the value in the registration date column 214 are registered. Further, when a collection enhanced item is set, the value of the column 206 for setting the enhanced item is also registered. An item code, which is a key of a record in the collection item master DB 514, is registered in the column 206 for setting the item to be strengthened, so that item data such as the type of the enhanced collection item can be specified.
[0026]
Further, a value is registered in the column 208 of the collection date 1, the column 210 of the collection date 2, the column of the collection date n (not shown), and the column 212 of the enhanced item collection date every time the collection date is determined. If no value is registered in the enhanced item setting column 206, no value is registered in the enhanced item collection date column 212.
[0027]
FIG. 3 shows an example of a table configuration of the collection item master DB 514. The example of FIG. 3 includes an item code column 300, an item name column 302, a fee 1 column 304, and a fee 2 column 306. In this table, data on the type (item) of the collected product is registered in advance. In the column 1 of the fee 1, a collection fee in the case where the collection applicant limits the collection date is registered, and in the column 2 of the fee 2, the collection fee in the case where the collection applicant does not limit the collection date is registered. Collection fee is registered.
[0028]
FIG. 4 shows an example of a table configuration of the collection reservation master DB 516. In the example of FIG. 4, a column 400 of a reception number (No.), a column 402 of a reception date and time, a column 404 of a desired collection date, a column 406 of a determined collection date, a column 408 of changeability, a column 410 of a collection time, and a collection Item column 412, transfer column 414, transfer destination column 416, fee column 418, name column 420, address column 422, telephone number column 424, mail address (e-mail) column 426, and image. A file column 428 and a notification column 430 are included.
[0029]
In this table, data on individual collection reservations from bulky waste collection applicants are registered. In the column 400 of the reception number (No.), a value serving as a key of the record at the time of generating the record is registered. A flag indicating whether a collection date may be set on a date different from the desired collection date is registered in the changeability column 408. In the present embodiment, “0” indicates that the collection date cannot be changed (the collection date is limited), and “1” indicates that the collection date can be changed (the collection date is not limited). When a record in which the value in the change permission / inhibition column 408 is “0” is generated, a value equal to the value in the collection desired date column 404 is registered in the collection determined date column 406.
[0030]
In the collection time column 410, a value is not registered when a record is generated, but a collection time set when a collection schedule is set by a collection company is registered. In the transfer column 414, a flag indicating whether the bulky garbage (collected product) desired to be collected may be transferred when there is a person who wants to collect it is registered. In the present embodiment, the initial value “0” indicates that transfer is not possible, and “1” indicates that transfer is possible. When the transfer destination (takeover person) is determined, the key value of the record of the transfer master DB 518 is registered in the transfer destination column 416. The collection master DB 518 will be described below. By referring to the key value, data related to collection such as the name of the collection person can be specified.
[0031]
In the fee column 418, a collection fee borne by a person who wishes to collect oversized garbage is registered. As described above, in the present embodiment, for example, two types of fees corresponding to the types of bulky garbage (collected items) are set in the record of the collected item master DB 514 (FIG. 3), and the corresponding value is the fee. Is registered in the column 418. That is, when a record in which the value of the change permission / inhibition column 408 is “0” is generated, the value of the fee 1 column 304 (FIG. 3) is registered in the fee column 418. When a record in which the value of the change permission / inhibition column 408 is “1” is generated, the value of the fee 2 column 306 (FIG. 3) is registered in the fee column 418. When the transferee (takeover party) is determined, the value in the commission column 418 is changed to “0 (yen)” in this embodiment, in order to make the collection fee borne by the takeover party.
[0032]
In the column 420 of the name, the column 422 of the address, the column 424 of the telephone number, and the column 426 of the mail address (e-mail), data relating to the collection applicant is registered at the time of record generation. In the image file column 428, a file name or the like of image data of oversized garbage (collected product) for reference by a person who wants to pick up may be registered when a record is generated. In the notification column 430, a flag is registered which indicates whether or not a notification process of confirmation has been performed to a collection applicant when a collection schedule is set by a collection company for a collection reservation corresponding to the record. In the present embodiment, since the notification process is performed by mail before the collection date (for example, the previous day), the data of the mail is generated, and it is indicated whether the reservation setting of the mail transmission has been performed. “0” indicates no notification, and “1” indicates that notification processing has been completed.
[0033]
FIG. 5 shows an example of a table configuration of the collection master DB 518. The example of FIG. 5 includes a column 550 of a reception number (No.), a column 552 of a reception date and time, a column 554 of a fee, a column 556 of a name, and a column 558 of an address. In this table, data on collection of collected items is registered. In the column 550 of the reception number (No.), the key of the record is registered, and is associated with the value of the column 416 of the transfer destination in the collection reservation master DB 516 (FIG. 4). A collection fee is registered in the fee column 554. In this embodiment, the collection fee of the collected product (the value of the fee column 418 of the corresponding record of the collection reservation master DB 516 (FIG. 4)). It is configured to be equal to That is, recycling is performed in such a manner that the collection fee originally borne by the collection applicant (transfer source) is borne by the collection applicant. Note that the collection fee may be determined based on another standard, or a configuration in which a collection fee is collected regardless of the presence or absence of transfer may be employed.
[0034]
Next, processing of the system shown in FIG. 1 will be described with reference to FIGS. The processing according to the present embodiment can be roughly classified into four, and includes a bulky waste collection plan generation processing, a collection reservation processing, a collection reservation processing, and a collection schedule setting processing. The attributes of the user who operates the terminal are different for each process, but it is assumed that the user attributes are specified by login before the processes described below.
[0035]
First, the generation processing of the oversized garbage collection plan will be described with reference to FIGS. 6 to 9. The administrative institution terminal 3 transmits a menu page data request to the oversized garbage collection management server 5 in accordance with a request from an administrative institution user (a person in charge of planning the oversized garbage collection plan) (FIG. 6: step S1). The collection plan processing unit 500 of the oversized garbage collection management server 5 receives a menu page data request from the administrative institution terminal 3 (step S3). Then, the collection plan processing unit 500 generates data of the menu page for the administrative institution, and transmits the data to the administrative institution terminal 3 (step S5). The administrative institution terminal 3 receives the data of the menu page for the administrative institution from the collection plan processing unit 500 and displays it on the display device (step S7).
[0036]
FIG. 7 shows an example of a menu page for an administrative organization. The example shown in FIG. 7 includes a bulky waste collection planning button 700. In addition, although not shown, a button for shifting to a page for maintaining the data (FIG. 3) of the collection item master DB 514, a button for shifting to a page for browsing the collection reservation status, and the like may be included.
[0037]
Returning to the flow of FIG. 6, the administrative institution terminal 3 receives a menu selection input from the administrative institution user to the administrative institution menu page (FIG. 7) (step S9). In the present embodiment, since the menu is only “Oversized garbage collection plan planning”, the administrative institution terminal 3 transmits a data request for the oversized garbage collection planning page to the oversized garbage collection management server 5 (step S11). . The collection plan processing unit 500 receives a data request for a collection plan creation page from the administrative institution terminal 3 (step S13). The collection plan processing unit 500 reads the calendar data of the current month from the calendar master DB 520 and temporarily stores the data in the calendar work 522 (step S15). Then, the collection plan processing unit 500 retrieves data related to collection in the current month from the collection range master DB 512 (FIG. 2) (part of the range calculated from the value of the column 200 of the range start date and the value of the column 202 of the range end date). Or, all the records included in the current month are read and stored in the calendar work 522 in association with the calendar data (step S17).
[0038]
The collection plan processing unit 500 uses the data stored in the calendar work 522 and the data stored in the collection item master DB 514 (FIG. 3) to generate data for the oversized garbage collection plan planning page, 3 (step S19). The administrative institution terminal 3 receives the data of the oversized garbage collection plan drafting page from the collection plan processing unit 500 and displays it on the display device (step S21).
[0039]
FIG. 8 shows an example of the oversized trash collection planning page. The example shown in FIG. 8 includes a collection plan display section 800, a target period selection section 802, a collection number selection section 804, a collection enhanced item selection section 806, a decision button 808, a cancel button 810, and an end button 812. . The collection plan display section 800 shows calendar data for one month (the current month), the number of collections, and (collection) enhanced items. Further, the period to be subjected to the oversized garbage collection plan is indicated by a difference in display such as a color or a diagonal line. The example in FIG. 8 shows that the number of collections in the period from August 2 to August 15 is set to two. Similarly, the number of collections during the period from August 16 to August 22 is set to one, indicating that the refrigerator is set as a collection-enhancing item during that period.
[0040]
Also, the collection plan display section 800 shows the data of the current month as an initial screen. When the “previous month” or “next month” shown on the collection plan display section 800 is clicked, the collection plan display section 800 shows data of the previous month or the next month (the one clicked).
[0041]
The collection plan display section 800 displays only the information. The administrative organization user selects and inputs the target period selection section 802, the collection number selection section 804, and the collection enhanced item selection section 806, thereby setting the collection plan. Registration is made. The collection-enhanced item selection unit 806 has a configuration in which “no setting” and the value of the item name column 302 of the collection item master DB 514 (FIG. 3) except “other” are indicated.
[0042]
Returning to the flow of FIG. 6, the administrative institution terminal 3 accepts a selection input from the administrative institution user on the oversized garbage collection planning page (FIG. 8), and transmits the selected input data to the oversized garbage collection management server 5 (step S23). ). The collection plan processing unit 500 receives the selection input data from the administrative institution terminal 3 and temporarily stores it in the storage device (step S25). The processing shifts to a processing of FIG. 9 via terminals A and B.
[0043]
The collection plan processing unit 500 determines the request of the administrative institution user based on which of the OK button 808, the cancel button 810, and the end button 812 is clicked on the oversized garbage collection plan drafting page (FIG. 8). I do. That is, it is determined whether or not the request of the administrative institution user has been completed (FIG. 9: step S27). When it is determined that the request has been completed (step S27: Yes route), the processing is performed via the terminal D in step S5 (FIG. Return to the processing of ()).
[0044]
If it is determined that the process has not been completed (step S27: No route), the collection plan processing unit 500 performs the process for the period set by the administrative institution user in the target period selection unit 802 of the oversized garbage collection plan drafting page (FIG. 8). It is determined whether or not data with overlapping periods already exists (step S29). That is, the collection range master DB 512 (FIG. 2) is searched, and the value of the range start date column 200 and the value of the range end date column 202 are compared with the period set in the target period selection unit 802 (FIG. 8). It is determined whether or not there is a record including the same or the same period.
[0045]
When it is determined that there is duplicate data (step S29: Yes route), the collection plan processing unit 500 determines whether the request of the administrative institution user has been canceled (step S31). When it is determined that the record has been canceled (step S31: Yes route), the record specified in step S29 is deleted from the collection range master DB 512 (FIG. 2) (step S33).
[0046]
When it is determined that it is not the cancellation (step S31: No route), the collection plan processing unit 500 generates data of an error message and transmits it to the administrative institution terminal 3 (step S35). That is, if a period during which data already exists is specified and a request for determination is made, an error is made. The administrative institution terminal 3 receives the error message data from the collection plan processing unit 500 and displays it on the display device (step S37).
[0047]
On the other hand, when it is determined in step S29 that there is no duplicate data (step S29: No route), the collection plan processing unit 500 determines whether the request of the administrative institution user has been determined (step S39). When it is determined that the decision is made (step S39: Yes route), the collection plan processing unit 500 generates a record of the collection range master DB 512 (FIG. 2) based on the selection input data of the administrative institution user, and the collection range master DB 512 (FIG. 2) (step S41).
[0048]
When it is determined that the determination has not been made (step S39: No route), the processing shifts to the processing of step S35 described above. That is, if a new period is specified and a cancellation request is made, an error is generated.
[0049]
Then, the collection plan processing unit 500 updates the data stored in the calendar work 522 based on the processing result in step S33 or step S41 (step S43). The process returns to step S19 via terminal C. In this way, the collection plan generation process is performed.
[0050]
Next, the oversized garbage collection reservation processing and the pick-up reservation processing will be described with reference to FIGS. The flow in FIG. 10 (steps S51 to S63) is a common flow in the oversized garbage collection reservation process and the collection reservation process.
[0051]
The collection applicant terminal 7 or the collection applicant terminal 9 transmits a menu page data request to the bulky garbage collection management server 5 in accordance with a request from the bulk garbage collection applicant or the collection applicant (FIG. 10: Step S51). ). The oversized garbage collection management server 5 receives a menu page data request from the collection applicant terminal 7 or the collection applicant terminal 9 (step S53). Then, the oversized garbage collection management server 5 generates data of the menu page for the citizen, and transmits it to the collection applicant terminal 7 or the collection applicant terminal 9 (step S55). The collection applicant terminal 7 or the collection applicant terminal 9 receives the menu page data for citizens from the oversized garbage collection management server 5 and displays the data on the display device (step S57).
[0052]
FIG. 11 shows an example of a menu page for citizens. The example shown in FIG. 11 includes a bulky waste collection reservation button 1100 and a collection reservation button 1110. When the oversized garbage collection reservation button 1100 is clicked, the screen shifts to a page for performing a collection reservation process. On the other hand, when the collection reservation button 1110 is clicked, the screen shifts to a page for performing a collection reservation process.
[0053]
Returning to the flow of FIG. 10, the collection applicant terminal 7 or the collection applicant terminal 9 receives the selection input from the bulky garbage collection applicant or the collection applicant on the menu page for citizens (FIG. 11) and makes a selection. The input data is transmitted to the oversized trash collection management server 5 (step S59). The oversized garbage collection management server 5 receives the selection input data from the collection applicant terminal 7 or the collection applicant terminal 9 (step S61).
[0054]
The oversized garbage collection management server 5 determines whether or not the oversized garbage collection button 1100 or the pick-up reservation button 1110 on the menu page for citizens (FIG. 11) is clicked, depending on which button is clicked. Determine the request of the applicant. That is, it is determined whether or not the request is a bulky waste collection reservation (step S63). If it is determined that the request is not a bulky waste collection reservation (step S63: No route), the processing proceeds to the processing of FIG. Transition.
On the other hand, when it is determined that the reservation is for oversized garbage collection (step S63: Yes route), the processing shifts to a processing of FIG.
[0055]
Hereinafter, the collection reservation processing of the oversized refuse after the terminal E will be described with reference to FIGS. The collection reservation processing unit 502 of the oversized garbage collection management server 5 reads the calendar data of the current month from the calendar master DB 520 and temporarily stores the data in the calendar work 522 (FIG. 12: step S71). Then, the collection reservation processing unit 502 retrieves data related to collection in the current month from the collection range master DB 512 (FIG. 2) (part of the range calculated from the value of the range start date column 200 and the range end date column 202). Or, all the records included in the current month are read and stored in the calendar work 522 in association with the calendar data (step S73).
[0056]
The collection reservation processing unit 502 generates data of a bulky garbage collection reservation page using the data stored in the calendar work 522 and the data stored in the collection item master DB 514 (FIG. 3), 7 (step S75). The collection applicant terminal 7 receives the data of the oversized garbage collection reservation page from the collection reservation processing unit 502 and displays the data on the display device (step S77).
[0057]
FIG. 13 shows an example of the oversized garbage collection reservation page. The example illustrated in FIG. 13 includes a collection reservation display unit 1300 and an end button 1310. The collection reservation display section 1300 shows calendar data for one month (the current month), the number of collections, and (collection) enhanced items. In addition, the period to be subjected to the oversized garbage collection plan is indicated by a difference in display of colors, diagonal lines, and the like, and the already determined collection date is indicated by being surrounded by an ellipse or a square.
[0058]
In the example of FIG. 13, the number of collections in the period from August 2 to August 15 is set to two, and it is shown that August 5 is the collection date. That is, in this period, another collection date can be set. Similarly, the number of collections during the period from August 16 to August 22 is set to one, indicating that the refrigerator is set as a collection-enhancing item during that period. In this period, it is shown that August 16 and August 20 are collection dates. Since August 16 is a normal collection date, it is indicated by being surrounded by an ellipse, and August 20 is a collection date limited to collection-enhanced items, and is indicated by being surrounded by a square.
[0059]
In addition, during the period from August 16 to August 22, the total number of collection days, August 16 and August 20, is two, although the number of collections is set to one. (The number of collections is two). As described in the description below the collection reservation display section 1300, when the collection enhanced item (refrigerator in the period) is set, the normal collection date is set as the collection date limited to the collection enhanced item. This is because a special collection date different from the date (August 20 in the period) can be set. In the present embodiment, since the collection date for the item whose collection is to be enhanced is limited to, for example, only one day within each collection period, the collection date is limited to the period from August 16 to August 22. Does not allow any further collection dates to be set.
[0060]
The collection reservation display section 1300 shows the data of the current month as an initial screen. When the “previous month” or “next month” shown on the collection reservation display section 1300 is clicked, the collection plan display section is displayed. 1300 shows data of the previous month or the next month (the one clicked).
[0061]
Then, the collection reservation display unit 1300 accepts the selection of the desired collection date by clicking the date of the calendar data.
[0062]
Returning to the flow of FIG. 12, the collection applicant terminal 7 accepts a selection input from the bulky garbage collection applicant on the bulky garbage collection reservation page (FIG. 13), and transmits the selection input data to the bulky garbage collection management server 5. (Step S79). The collection reservation processing unit 502 receives the selection input data from the collection applicant terminal 7 and temporarily stores it in the storage device (step S81).
[0063]
The collection reservation processing unit 502 determines the request of the bulk garbage collection applicant based on which of the end button 1310 and the calendar date of the collection reservation display unit 1300 is clicked on the oversized garbage collection reservation page (FIG. 13). I do. That is, it is determined whether or not the request of the person desiring collection of oversized garbage has been completed (step S83), and if it has been determined that the request has been completed (step S83: Yes route), the processing is performed via the terminal G in step S55 (FIG. 10). Return to the processing of ()).
[0064]
If it is determined that the collection has not been completed (step S83: No route), the collection reservation processing unit 502 performs an input check process on the date selected by the collection applicant as the collection desired date (step S85). In this embodiment, since there are a plurality of input check processes, the input check process in step S85 is hereinafter referred to as input check 1 for convenience of explanation. The details of the input check 1 process will be described later.
[0065]
The collection reservation processing unit 502 determines whether an error has been detected as a result of the input check 1 (step S87). When it is determined that an error has been detected (step S87: Yes route), the collection reservation processing unit 502 generates error message data and transmits it to the collection applicant terminal 7 (step S89). The collection applicant terminal 7 receives the error message data from the collection reservation processing unit 502 and displays it on the display device (step S91). On the other hand, when it is determined that no error is detected (step S87: No route), the processing shifts to a processing of FIG.
[0066]
The collection reservation processing unit 502 uses the date selected by the collection applicant, the data stored in the collection item master DB 514 (FIG. 3), and the data stored in the map DB 524 to convert the data of the reservation details input page. It is generated and transmitted to the collection applicant terminal 7 (FIG. 14: step S101). The collection applicant terminal 7 receives the data of the reservation details input page from the collection reservation processing unit 502 and displays the data on the display device (step S103).
[0067]
FIG. 15 shows an example of the reservation details input page. The example shown in FIG. 15 includes a name input section 1500, a desired collection date attribute selection section 1502, an oversized garbage name selection section 1504, an image attachment setting section 1506, a contact telephone number input section 1508, a mail address input section 1510, and a collection. A destination address display section 1512, a map data display section 1514, a return button 1516, a decision button 1518, and an end button 1520 are included.
[0068]
In the desired collection date attribute selection unit 1502, the date selected by the collection applicant on the oversized garbage collection reservation page (FIG. 13) as the desired collection date and the collection date on a day other than the desired collection date may be set. Radio button for selecting whether or not. The oversized garbage name selection unit 1504 indicates the value of the column 302 of the item name of the collection item master DB 514 (FIG. 3), and has a configuration in which the type of oversized garbage can be selected.
[0069]
The image attachment setting unit 1506 includes an input display field for a file name of oversized garbage image data and a reference button. For example, image data (photograph of oversized garbage) stored on the hard disk of the collection applicant terminal 7 Data) can be registered.
[0070]
In this embodiment, the collection place of the oversized garbage is not predetermined, and the collection company goes to a place designated by the collection applicant, such as the home of the collection applicant.
Therefore, the configuration is such that the collection location (collection destination address) data is registered using the collection destination address display section 1512 and the map data display section 1514 of this page.
[0071]
In the collection address display section 1512, a message "Click on the map" is displayed on the initial screen. Then, when a specific place on the map image is clicked by the collection applicant, the collection applicant terminal 7 accepts the specification of the location from the collection applicant, and receives, for example, an area on the map previously received and stored. An address is specified using a table representing the correspondence between the address and the address, or the data of the place is transmitted to the collection reservation processing unit 502. The table showing the correspondence between the area on the map and the address is collected by the collection reservation processing unit 502. Is received from the collection reservation processing unit 502, and the message shown in the collection destination address display unit 1512 is changed to the address (address) of the clicked place and displayed.
[0072]
On the map data display section 1514, the initial screen shows a map image of the entire area where oversized garbage is collected, such as municipalities. Although not shown, the map data display unit 1514 may be provided with a scale change button and a scroll button for changing a map image, and it is possible to specify a detailed address. Has become.
[0073]
In order to perform such processing, data stored in the map DB 524 is used. As described above, a part or all of necessary data is included in the initial screen data of this page. The configuration may be such that the map DB 524 is searched each time a map image is clicked. The collection address display section 1512 may be provided with an input field for directly inputting an address.
[0074]
Returning to the flow of FIG. 14, the collection applicant terminal 7 receives a selection input from the collection applicant on the reservation details input page (FIG. 15), and transmits the selection input data to the oversized garbage collection management server 5 (step S105). . The collection reservation processing unit 502 receives the selection input data from the collection applicant terminal 7 and temporarily stores it in the storage device (step S107).
[0075]
Then, the collection reservation processing unit 502 determines the request of the collection applicant based on which of the return button 1516, the cancel button 1518, and the end button 1520 is clicked on the reservation details input page (FIG. 15). . That is, it is determined whether or not the request from the collection applicant has been completed (step S109). If it is determined that the request has been completed (step S109: Yes route), the processing is performed via the terminal G in step S55 (FIG. 10). Return to
[0076]
When it is determined that the processing has not been completed (step S109: No route), it is determined whether or not the request of the collection applicant is “return” (step S111). When it is determined to be “return” (step S111: Yes route), the processing returns to the processing in FIG. If it is determined that it is not “return” (step S111: No route), the collection reservation processing unit 502 performs an input check process on the data selected and input by the collection applicant on the reservation details input page (FIG. 15). Performed (Step S113). Like the input check 1 (FIG. 12) in step S85 described above, the input check processing in step S113 is hereinafter referred to as input check 2, and the details of the processing will be described later.
[0077]
The collection reservation processing unit 502 determines whether an error has been detected as a result of the input check 2 (step S115). When it is determined that an error has been detected (step S115: Yes route), the collection reservation processing unit 502 generates error message data and transmits it to the collection applicant terminal 7 (step S117). The collection applicant terminal 7 receives the error message data from the collection reservation processing unit 502 and displays it on the display device (step S119).
[0078]
On the other hand, if it is determined that no error has been detected (step S115: No route), the collection reservation processing unit 502 determines the master based on the data selected and input by the collection applicant on the reservation details input page (FIG. 15). A DB registration / update process is performed (step S121). Although details of the master DB registration / update processing will be described later, the record registration processing of the collection reservation master DB 516 (FIG. 4) and the record update processing of the collection range master DB 512 (FIG. 2) are performed. The processing shifts to a processing of FIG. 16 via the terminal J and the terminal K.
[0079]
Next, the collection reservation processing unit 502 generates data of the transfer confirmation page and transmits the data to the collection applicant terminal 7 (FIG. 16: step S123). The collection applicant terminal 7 receives the data of the transfer confirmation page from the collection reservation processing unit 502 and displays it on the display device (step S125).
[0080]
FIG. 17 shows an example of the transfer confirmation page. The example shown in FIG. 17 includes a reception message display section 1700, a transfer button 1702, a discard button 1704, a return button 1706, and an end button 1708. In the initial screen of the transfer confirmation page, the reception message display unit 1700 may show a message different from the example shown in FIG. 17 or may not show the message. For example, the message shown in FIG. 17 is displayed when the transfer button 1702 or the discard button 1704 is clicked and the collection reservation processing is completed.
[0081]
Returning to the flow of FIG. 16, the collection applicant terminal 7 receives the selection input from the collection applicant on the transfer confirmation page (FIG. 17), and transmits the selection input data to the oversized garbage collection management server 5 (step S127). The collection reservation processing unit 502 receives the selection input data from the collection applicant terminal 7 (Step S129).
[0082]
Then, the collection reservation processing unit 502 requests the collection applicant according to which of the transfer button 1702, the discard button 1704, the return button 1706, and the end button 1708 is clicked on the transfer confirmation page (FIG. 17). Is determined. That is, it is determined whether or not the request of the collection applicant has been completed (step S131), and when it is determined that the request has been completed (step S131: Yes route), the processing is performed via the terminal G in step S55 (FIG. 10). Return to
[0083]
When it is determined that the processing has not been completed (step S131: No route), it is determined whether or not the request of the collection applicant is “return” (step S133). When it is determined that the operation is “return” (step S133: Yes route), the processing shifts to a processing of FIG. When it is determined that the request is not “return” (step S133: No route), the collection reservation processing unit 502 determines whether the request of the collection applicant is discard (step S135).
[0084]
If it is determined that the request is not discarded (step S135: No route), the collection reservation processing unit 502 determines that the request of the collection applicant is a transfer, and corresponds to the transfer of the record in the collection reservation master DB 516 (FIG. 4). And update (step S137). That is, when the request of the collection applicant is transfer, the value of the transfer column 414 of the record corresponding to the collection reservation in the collection reservation master DB 516 (FIG. 4) is changed from the initial value “0” to “1”. Update.
[0085]
On the other hand, when it is determined that the request of the collection applicant is “discard” (step S135: Yes route), step S137 is skipped. Then, the collection reservation processing unit 502 generates reception confirmation message data as shown in the reception message display unit 1700 in FIG. 17, and transmits the data to the collection applicant terminal 7 (step S139). The collection applicant terminal 7 receives the data of the reception confirmation message from the collection reservation processing unit 502 and displays it on the display device (step S141). In this way, the collection reservation processing of the bulky waste is performed. In addition, whether transfer is possible is set.
[0086]
Next, the details of the input check 1 (FIG. 12: step S85) will be described with reference to FIG. This process is an error check performed by the collection reservation processing unit 502 based on the selection input data (the date clicked) from the collection applicant with respect to the oversized garbage collection reservation page (FIG. 13).
[0087]
First, the collection reservation processing unit 502 searches the collection range master DB 512 (FIG. 2), and, based on the value of the range start date column 200 and the value of the range end date column 202, specifies the designated date (hereinafter, desired date). ) Is read (step S151).
[0088]
It is determined whether the corresponding record exists (step S153). If it is determined that the record does not exist (step S153: No route), the process proceeds to step S163.
[0089]
On the other hand, if it is determined that the record exists (step S153: Yes route), the value of the column 208 of the collection date 1 and the column 210 of the collection date 2 and the value of the column of the collection date n (not shown) in the read record. It is determined whether any of the values in the column 212 of the enhanced item collection date is equal to the desired date (step S155). That is, it is determined whether the date already set as the collection date has been designated as the desired date.
[0090]
If it is determined that any one of the set collection dates is equal to the desired date (step S155: Yes route), the input check 1 process ends.
[0091]
On the other hand, when it is determined that the desired date is not equal to any of the set collection dates (step S155: No route), it is determined whether or not the collection dates for the number of collections have been set (step S157). That is, among the columns 208 of the collection date 1, the column 210 of the collection date 2, and the column of the collection date n (not shown) in the read record, the number of columns for which values are set and the value of the column 204 of the number of collections To compare. If they are equal, the collection dates for the number of collections have been set.
[0092]
If it is determined that the collection dates for the number of collections have not been set (step S157: No route), the input check 1 process ends. On the other hand, when it is determined that the collection dates for the number of times of collection have been set (step S157: Yes route), it is determined whether or not the collection enhanced item (hereinafter, enhanced item) has been set (step S159). That is, it is determined whether or not a value has been set in the enhanced item setting column 206 in the read record.
[0093]
When it is determined that the enhanced item has not been set (step S159: No route), the process proceeds to step S163. On the other hand, when it is determined that the enhanced item has been set (step S159: Yes route), it is determined whether the collection date of the enhanced item has been set (step S161). That is, it is determined whether a value is set in the column 212 of the enhanced item collection date in the read record.
[0094]
When it is determined that the collection date of the enhanced item has not been set (step S161: No route), the processing of the input check 1 is ended. On the other hand, when it is determined that the collection date of the enhanced item has been set (step S161: Yes route), it is determined that the processing result of the input check 1 is “error”, and the determination result data is temporarily stored in the storage device ( Step S163). Then, the collection reservation processing unit 502 ends the input check 1 process. As described above, by performing an error check on the selection input data (desired date) from the applicant for collection with respect to the oversized garbage collection reservation page (FIG. 13), it is possible to prevent inappropriate selection of the desired date. .
[0095]
Next, the details of the input check 2 (FIG. 14: step S113) processing will be described with reference to FIG. This processing is an error check performed by the collection reservation processing unit 502 based on the selection input data (whether or not the desired collection date can be changed and the type of oversized garbage) on the reservation details input page (FIG. 15) from the collection applicant.
[0096]
First, the collection reservation processing unit 502 searches the collection range master DB 512 (FIG. 2), and, based on the value of the range start date column 200 and the value of the range end date column 202, a record having a range including the desired collection date. Is read (step S171). Here, the desired collection date (hereinafter referred to as “desired date”) is the date clicked on by the applicant for collection on the bulky garbage collection reservation page (FIG. 13), and the desired collection date on the reservation details input page (FIG. 15). This is the date indicated in the attribute selection unit 1502.
[0097]
Here, by the processing of input check 1 (FIG. 12: step S85), since there is a corresponding record here, the record is specified from the collection range master DB 512 (FIG. 2).
[0098]
Then, the collection reservation processing unit 502 determines whether or not the selection input from the collection applicant to the collection desired date attribute selection unit 1502 on the reservation details input page (FIG. 15) is “unchangeable” (step S173). If it is determined that it is not “unchangeable” (step S173: No route), the input check 2 process is terminated.
[0099]
On the other hand, when it is determined that “change is impossible” (step S173: Yes route), the values of the column 208 of the collection date 1 and the column 210 of the collection date 2 and the collection date n (not shown) in the read record are read. It is determined whether any of the values in the column is equal to the desired date (step S175). That is, it is determined whether or not the desired date is a date already set as the collection date (excluding the enhanced item collection date).
[0100]
If it is determined that any one of the set collection dates is equal to the desired date (step S175: Yes route), the input check 2 process ends.
[0101]
On the other hand, when it is determined that the desired dates are not equal to any of the set collection dates (step S175: No route), it is determined whether the collection dates for the number of collections have been set (step S177). That is, among the columns 208 of the collection date 1, the column 210 of the collection date 2, and the column of the collection date n (not shown) in the read record, the number of columns for which values are set and the value of the column 204 of the number of collections To compare. If they are equal, the collection dates for the number of collections have been set.
[0102]
When it is determined that the collection dates for the number of collections have not been set (step S177: No route), the processing of the input check 2 ends. On the other hand, when it is determined that the collection dates for the number of times of collection have been set (step S177: Yes route), it is determined whether or not a collection enhanced item (hereinafter, enhanced item) has been set (step S179). That is, it is determined whether or not a value has been set in the enhanced item setting column 206 in the read record.
[0103]
If it is determined that the enhanced item has not been set (step S179: No route), the process proceeds to step S185. On the other hand, when it is determined that the strengthened item has been set (step S179: Yes route), the collection desired item selected from the oversized garbage name selection unit 1504 by the collection applicant on the reservation details input page (FIG. 15). It is determined whether the item is a strengthened item (step S181). That is, the value of the column 206 of the strengthened item setting in the read record, the item code corresponding to the oversized garbage selected in the oversized garbage name selection unit 1504 (FIG. 15) (see the collection item master DB 514 (FIG. 3)) Is equal or not.
[0104]
If it is determined that the item desired to be collected is not an enhanced item (step S181: No route), the process proceeds to step S185. On the other hand, when it is determined that the item to be collected is an enhanced item (step S181: Yes route), it is determined whether a collection date of the enhanced item has been set (step S183). That is, it is determined whether a value is set in the column 212 of the enhanced item collection date in the read record.
[0105]
When it is determined that the collection date of the enhanced item has not been set (step S183: No route), the processing of the input check 2 is ended. On the other hand, when it is determined that the collection date of the enhanced item has been set (step S183: Yes route), it is determined that the processing result of the input check 2 is “error”, and the determination result data is temporarily stored in the storage device ( Step S185). Then, the collection reservation processing unit 502 ends the input check 2 process. As described above, by performing an error check on the selection input data (whether the change of the collection date is desired and the type of oversized garbage) on the reservation details input page (FIG. 15) from the collection applicant, the inappropriate selection input is performed. Can be prevented.
[0106]
Next, the details of the process of registering and updating the master DB (FIG. 14: step S121) will be described with reference to FIGS. In this processing, the collection reservation processing unit 502 performs the record registration processing to the collection reservation master DB 516 (FIG. 4) and the collection range master DB 512 based on the selection input data from the collection applicant on the reservation details input page (FIG. 15). The record updating process shown in FIG. 2 is performed.
[0107]
First, the collection reservation processing unit 502 determines whether or not the selection input from the collection applicant to the collection desired date attribute selection unit 1502 on the reservation details input page (FIG. 15) is “unchangeable” (FIG. 20: step S191). ). If it is determined that it is not “unchangeable” (step S191: No route), the processing shifts to a processing of FIG.
[0108]
On the other hand, if it is determined that “change is impossible” (step S191: Yes route), the collection reservation processing unit 502 sets the collection reservation based on the selection input data from the collection applicant on the reservation details input page (FIG. 15). A new record of the master DB 516 (FIG. 4) is generated and registered in the collection reservation master DB 516 (step S193).
[0109]
In this case, a value equal to the value of the desired collection date column 404 is set in the collection determination date column 406 of the record to be registered. In the column 418 of the fee in the record to be registered, the value of the column 304 of the fee 1 in the collection item in the collection item master DB 514 (FIG. 3) is set. That is, the fee is set higher when the collection date is limited than when the collection date is not limited.
[0110]
Then, the collection reservation processing unit 502 searches the collection range master DB 512 (FIG. 2) and, based on the value of the range start date column 200 and the value of the range end date column 202, finds a record having a range including the desired collection date. It is read (step S195). Here, the desired collection date (hereinafter referred to as “desired date”) is a date specified by the collection applicant on the bulky garbage collection reservation page (FIG. 13) and a desired collection date attribute is selected on the reservation details input page (FIG. 15). The date shown in the section 1502.
[0111]
Note that the existence of the corresponding record has been confirmed by the input check 1 (FIG. 12: step S85). Then, it is determined whether the desired date is equal to any of the values in the column 208 of the collection date 1, the column 210 of the collection date 2 and the column of the collection date n (not shown) in the read record. (Step S197). That is, it is determined whether or not the desired date is a date already set as the collection date (excluding the enhanced item collection date).
[0112]
If it is determined that any one of the set collection dates is equal to the desired date (step S197: Yes route), the master DB registration / update process ends.
[0113]
On the other hand, if it is determined that the desired dates are not equal to any of the set collection dates (step S197: No route), it is determined whether or not the collection dates for the number of collections have been set (step S199). That is, among the columns 208 of the collection date 1, the column 210 of the collection date 2, and the column of the collection date n (not shown) in the read record, the number of columns for which values are set and the value of the column 204 of the number of collections Compare. If they are equal, the collection dates for the number of collections have been set.
[0114]
When it is determined that the collection date for the number of collections has been set (step S199: Yes route), it is determined whether the collection date of the collection enhanced item (hereinafter, referred to as an enhanced item) has been set (step S201). ). That is, it is determined whether a value is set in the column 212 of the enhanced item collection date in the read record.
[0115]
If the collection date of the enhanced item has been set in the previous process, it is ensured that the desired collection date is the same as the already set collection date of the enhanced item. On the other hand, if the collection date of the enhanced item has not been set, it is necessary to set the desired collection date as the collection date of the new enhanced item.
[0116]
When it is determined that the collection date of the enhanced item has been set (step S201: Yes route), the following step S203 is skipped, and the master DB registration / update processing ends. On the other hand, when it is determined that the collection date of the enhanced item has not been set (step S201: No route), the record update process of the collection range master DB 512 (FIG. 2) is performed (step S203). That is, the desired date (the date specified by the collection applicant on the oversized garbage collection reservation page (FIG. 13)) is set in the column 212 of the enhanced item collection date in the read record. Then, the collection reservation processing unit 502 ends the master DB registration / update processing.
[0117]
On the other hand, when it is determined that the collection dates for the number of times of collection have not been set (step S199: No route), the record update processing of the collection range master DB 512 (FIG. 2) is performed (step S205). That is, in the read record, the value of the column 208 of the collection date 1, the value of the column 210 of the collection date 2, and the value of the column of the collection date n (not shown) are checked in order, and the first empty portion (the value is set). Column), set the desired date.
[0118]
Then, the collection reservation processing unit 502 determines whether or not the collection dates for the number of collections have been set by the processing in step S205 (step S207). In other words, among the columns 208 of the collection date 1, the column 210 of the collection date 2, and the column of the collection date n (not shown) in the read record, the number of columns for which values are set and the value of the column 204 of the number of collections To compare. If they are equal, the collection dates for the number of collections have been set.
[0119]
If it is determined that the collection dates for the number of collections have not yet been set (step S207: No route), the following steps S209 and S211 are skipped, and the master DB registration / update processing ends.
[0120]
On the other hand, when it is determined that the collection dates for the number of collections have been set (step S207: Yes route), the collection reservation processing unit 502 sets the value of the range start date column 200 and the range end date in the read record. From the collection reservation master DB 516 (FIG. 4), the desired date (the value of the collection desired date column 404) and the value of the collection determined date column 406 are still set from the collection reservation master DB 516 (FIG. 4). A record that has not been processed is extracted (step S209). Note that there may be a plurality of corresponding records.
[0121]
Then, the collection reservation processing unit 502 sets the value of the collection determination date column 406 in the record of the extracted collection reservation master DB 516 (FIG. 4) (step S211). That is, among the values of the column 208 of the collection date 1 and the column 210 of the collection date 2 and the value of the column of the collection date n (not shown) of the record of the collection range master DB 512 (FIG. 2) read in step S195. The value closest to the value of the column 404 of the desired collection date in the record of the collection reservation master DB 516 (FIG. 4) extracted in step S209 is registered in the value of the column 406 of the determined collection date in the extracted record. . If there are a plurality of records extracted in step S209, this process is performed for all the extracted records. Then, the master DB registration / update processing ends.
[0122]
Thus, the collection date is set in the order of reception based on the desired date of the collection applicant who limits the collection date. Also, if a collection date for the number of times of collection is set, and there is a request for collection of an enhanced item that limits the collection date, the desired collection date is set as a collection date for the enhanced item.
In addition, even before the collection date for the number of times of collection is set, if there is a request for collection of an enhanced item that limits the collection date, the configuration may be such that the enhanced item collection date is set.
[0123]
Also, in step S207, a configuration has been described in which the collection date is set automatically for a collection reservation whose collection date is undetermined after the collection date for the collection frequency is set. However, the collection date for the collection frequency is set. Even before the collection, the collection date may be automatically set for a collection reservation whose collection date is undecided.
[0124]
Next, the processing after the terminal L (step S191 (FIG. 20): No route) will be described with reference to FIG. The collection reservation processing unit 502 searches the collection range master DB 512 (FIG. 2), and includes the desired date specified by the collection reservation person from the value of the range start date column 200 and the value of the range end date column 202. A record having a range is read (step S221).
[0125]
Then, the collection reservation processing unit 502 determines whether a collection enhancement item (hereinafter, an enhancement item) has been set (step S223). That is, it is determined whether or not a value is set in the column 206 of the enhanced item setting in the record of the collection range master DB 512 (FIG. 2) read in step S221.
[0126]
If it is determined that the enhanced item has not been set (step S223: No route), the process proceeds to step S231. On the other hand, if it is determined that the enhanced item has been set (step S223: Yes route), the item to be collected selected from the oversized garbage name selection unit 1504 by the collection applicant on the reservation details input page (FIG. 15). It is determined whether the item is a strengthened item (step S225). That is, the value of the column 206 of the strengthened item setting in the read record, the item code corresponding to the oversized garbage selected in the oversized garbage name selection unit 1504 (FIG. 15) (see the collection item master DB 514 (FIG. 3)) Is equal or not.
[0127]
When it is determined that the item desired to be collected is not an enhanced item (step S225: No route), the process proceeds to step S231. On the other hand, if it is determined that the item desired to be collected is an enhanced item (step S225: Yes route), it is determined whether a collection date of the enhanced item has been set (step S227). That is, it is determined whether a value is set in the column 212 of the enhanced item collection date in the read record.
[0128]
When it is determined that the collection date of the enhanced item has been set (step S227: Yes route), the collection reservation processing unit 502 uses the selection input data from the collection applicant on the reservation details input page (FIG. 15). A new record of the collection reservation master DB 516 (FIG. 4) is generated and registered in the collection reservation master DB 516 (step S229).
[0129]
In this case, a value equal to the value of the column 212 of the enhanced item collection date in the record of the collection range master DB 512 (FIG. 2) read in step S221 is set in the collection determination date column 406 of the record to be registered. I do. In the column 418 of the fee in the record to be registered, the value of the column 306 of the fee 2 for the collection item in the collection item master DB 514 (FIG. 3) is set. That is, when the collection date is not limited, the fee is set lower than when the collection date is limited.
[0130]
As a result, especially in the case of a collection applicant who is not particular about the collection date, if the bulky garbage to be collected is an enhanced item, it is collected on the enhanced item collection date. That is, on the date of collection of the enhanced items, as much bulky waste as possible of the enhanced items is collected.
[0131]
On the other hand, if it is determined that the collection date of the enhanced item has not been set (step S227: No route), the collection reservation processing unit 502 selects the input data from the collection applicant on the reservation details input page (FIG. 15). A new record of the collection reservation master DB 516 (FIG. 4) is generated based on the information, and registered in the collection reservation master DB 516 (step S231).
[0132]
In this case, no value is registered in the column 406 of the determined collection date in the record to be registered. In the column 418 of the fee in the record to be registered, the value of the column 306 of the fee 2 for the collection item in the collection item master DB 514 (FIG. 3) is set. As in step S229, when the collection date is not limited, the fee is set lower than when the collection date is limited.
[0133]
Next, the collection reservation processing unit 502 determines whether a collection date for the number of collections has been set (step S233). That is, a value is set in the column 208 of the collection date 1, the column 210 of the collection date 2, and the column of the collection date n (not shown) in the record of the collection range master DB 512 (FIG. 2) read in step S221. Then, the number of columns and the value of the collection number column 204 are compared. If they are equal, the collection dates for the number of collections have been set.
[0134]
When it is determined that the collection dates for the number of collections have not been set yet (step S233: No route), the following step S235 is skipped, and the master DB registration / update processing ends.
[0135]
On the other hand, when it is determined that the collection dates for the number of times of collection have been set (step S233: Yes route), the collection reservation processing unit 502 determines in the record of the collection reservation master DB 516 (FIG. 4) registered in step S231. The value of the column 406 of the collection decision date is set (step S235). That is, among the values of the column 208 of the collection date 1 and the column 210 of the collection date 2 and the value of the column of the collection date n (not shown) in the record of the collection range master DB 512 (FIG. 2) read in step S221. In the record of the collection reservation master DB 516 (FIG. 4) registered in step S231, the value closest to the value of the column 404 of the desired collection date is registered in the value of the column 406 of the collection determined date in the registered record. . Then, the master DB registration / update processing ends.
[0136]
As described above, the data on the collection reservation is registered in the collection range master DB 512 (FIG. 2) and the collection reservation master DB 516 (FIG. 4). In some cases, the collection date is automatically set.
[0137]
Next, with reference to FIG. 22 to FIG. 25, a description will be given of a process for making a reservation for taking over bulky waste after the terminal F (step S63 (FIG. 10): No route). The collection reservation processing unit 504 of the oversized garbage collection management server 5 searches the collection reservation master DB 516 (FIG. 4), and the transfer column 414 is “1”, the value of the transfer destination column 416 is not set, and the collection is determined. The record in which the value of the date column 406 has been set is read (FIG. 22: step S241).
[0138]
Then, the pickup reservation processing unit 504 generates data of the pickup reservation page using the data of the record read in step S241, and transmits the data to the pickup applicant terminal 9 (step S243). If the corresponding record does not exist in step S241, for example, data of a reservation reservation page including a message such as "There is no currently available collection item" is generated and transmitted to the terminal 9 Send. The transfer applicant terminal 9 receives the data of the transfer reservation page from the transfer reservation processing unit 504 and displays the data on the display device (step S245).
[0139]
FIG. 23 shows an example of the pickup reservation page. The example illustrated in FIG. 23 includes a collection item list 2300 and an end button 2310. In addition, the collection item list 2300 includes a column 2302 of an item name, a column 2304 of an image, and a column 2306 of a property number (No.).
[0140]
The item name column 2302 indicates the item name (refer to the collection item master DB 514 (FIG. 3)) corresponding to the value of the collection item column 412 of the record (hereinafter, collection reservation record) read in step S241 (FIG. 22). Have been. When the file name or the like of the image data of the oversized garbage (collected product) is registered in the column 428 of the image file of the collection reservation record, the image column 2304 includes an image button. In the column 2306 of the property number (No.), the value of the column 400 of the reception number (No.) of the collection reservation record is shown in a page link format.
[0141]
Returning to the flow of FIG. 22, the withdrawal requester terminal 9 accepts a selection input from the withdrawal requester with respect to the withdrawal reservation page (FIG. 23), and transmits the selected input data to the oversized garbage collection management server 5 (step S247). The transfer reservation processing unit 504 receives the selection input data from the transfer applicant terminal 9 and temporarily stores the data in the storage device (step S249).
[0142]
Then, the pick-up reservation processing unit 504, in the pick-up reservation page (FIG. 23), the end button 2310, the image button included in the image column 2304, and the page link included in the property number (No.) column 2306 The request of the person who wants to pick up is determined based on which of the two is clicked. That is, it is determined whether or not the request of the takeover applicant has been completed (step S251), and when it is determined that the request has been completed (step S251: Yes route), the processing is performed via the terminal G in step S55 (FIG. 10). Return to
[0143]
If it is determined that the processing has not been completed (step S251: No route), it is determined whether or not the request of the takeover applicant is browsing of an image (step S253). If it is determined that the image has been viewed (step S253: Yes route), the pickup reservation processing unit 504 includes the image data of the collected product designated by clicking the image button on the pickup reservation page (FIG. 23). The image page data is generated and transmitted to the takeover applicant terminal 9 (step S255). The takeover applicant terminal 9 receives the image page data from the takeover reservation processing unit 504 and displays it on the display device (step S257).
[0144]
On the other hand, when it is determined that the image is not browsed (step S253: No route), the processing shifts to the processing in FIG.
[0145]
In the pickup reservation page (FIG. 23), the pickup reservation processing unit 504 generates data of a pickup confirmation page for the collection item designated by clicking the page link (property number), and transmits the data to the pickup applicant terminal 9. (Step S261). The receipt applicant terminal 9 receives the data of the receipt confirmation page from the receipt reservation processing unit 504 and displays the data on the display device (step S263).
[0146]
FIG. 25 shows an example of the receipt confirmation page. In the example shown in FIG. 25, a property number (No.) display unit 2500, a delivery date display unit 2502, a collection name input unit 2504, a collection address input unit 2506, a collection fee display unit 2508, a reception message display unit 2510, A takeover button 2512, a return button 2514, and an end button 2516 are included.
[0147]
The property number (No.) display section 2500 shows the number selected as the property number (No.) of the desired collection item on the collection reservation page (FIG. 23). Further, the delivery date display section 2502 shows the collection date of the collection item (the value of the collection determination date column 406 in the record of the collection reservation master DB 516 (FIG. 4)). That is, in the present embodiment, delivery is performed to a person who wants to collect bulky garbage (collected product), and the delivery date is set to the same date as the collection date of the collected product. In addition, the structure which accepts the delivery desired date of a collection applicant may be sufficient.
[0148]
The takeover name input section 2504 and the takeover address input section 2506 are provided with input fields for inputting the takeover attribute data. The name and address may be displayed in advance using the login data of the applicant. Further, as in the example shown in FIG. 15, a configuration in which address data is set using a map image may be employed.
[0149]
The collection fee display unit 2508 shows the collection fee of the collected product (the value of the column 418 of the fee in the record of the collection reservation master DB 516 (FIG. 4)). That is, in the present embodiment, the commission to be borne by the applicant for collection of bulky garbage (collected product) is set to the same amount as the collection fee for the collected product. Then, a collection applicant who has determined the collection destination will not be charged the collection fee. It should be noted that the collection fee and the collection fee may be separately collected.
[0150]
In the initial screen of the receipt confirmation page, a message different from the example shown in FIG. 25 may or may not be displayed on the reception message display unit 2510 in some cases. For example, the message shown in FIG. 25 is displayed when the pick-up button 2512 is clicked and the pick-up reservation processing is completed.
[0151]
Returning to the flow of FIG. 24, the withdrawal applicant terminal 9 accepts the selection input from the withdrawal confirmation page (FIG. 25) and sends the selected input data to the oversized garbage collection management server 5 (step S265). The collection reservation processing unit 504 receives the selection input data from the collection applicant terminal 9, and temporarily stores the data in the storage device (step S267).
[0152]
Then, the collection reservation processing unit 504 determines the request of the person who wants to collect, based on which of the collection button 2512, the return button 2514, and the end button 2516 is clicked on the collection confirmation page (FIG. 25). That is, it is determined whether or not the request of the applicant has been completed (step S269), and if it is determined that the request has been completed (step S269: Yes route), the processing is performed via the terminal G in step S55 (FIG. 10). Return to
[0153]
When it is determined that the processing has not been completed (step S269: No route), it is determined whether or not the request of the takeover applicant is “return” (step S271). If it is determined to be “return” (step S271: Yes route), the processing returns to the processing in FIG.
[0154]
On the other hand, when it is determined that the request is not “return” (step S271: No route), the collection reservation processing unit 504 determines that the request of the collection applicant is “collection” and responds to the collection confirmation page (FIG. 25). Then, a new record of the collection master DB 518 (FIG. 5) is generated based on the selection input data from the collection applicant, and registered in the collection master DB 518 (step S273). In the present embodiment, a value equal to the value of the fee column 418 in the record of the collection reservation master DB 516 (FIG. 4) corresponding to the collected item is set in the fee column 554 in the record to be registered.
[0155]
Then, the pick-up reservation processing unit 504 updates the record of the collection reservation master DB 516 (FIG. 4) corresponding to the collection item (step S275). That is, the value of the fee column 418 is updated to “0”, and the value of the column 550 of the receipt number (No.) in the record of the collection master DB 518 (FIG. 5) registered in step S273 is changed to the column of the transfer destination. 416.
[0156]
Then, the collection reservation processing unit 504 generates data of a reception confirmation message as shown in the reception message display unit 2510 of FIG. 25 and transmits the data to the collection applicant terminal 9 (step S277). The receipt applicant terminal 9 receives the data of the reception confirmation message from the receipt reservation processing unit 504 and displays it on the display device (step S279). In this way, a process for making a reservation for picking up oversized garbage (collected product) is performed. Further, a fee is set based on a predetermined rule.
[0157]
Next, the collection schedule setting processing of oversized garbage will be described with reference to FIGS. The collection company terminal 11 transmits a menu page data request to the oversized garbage collection management server 5 according to the request from the collection company user (FIG. 26: step S281). The collection schedule processing unit 506 of the bulky waste collection management server 5 receives the menu page data request from the collection company terminal 11 (step S283). Then, the collection schedule processing unit 506 generates menu page data for the collection company and transmits it to the collection company terminal 11 (step S285). The collection company terminal 11 receives the menu page data for the collection company from the collection schedule processing unit 506 and displays it on the display device (step S287).
[0158]
FIG. 27 shows an example of a menu page for a collection company. The example illustrated in FIG. 27 includes a bulky waste collection plan schedule button 2700.
[0159]
Returning to the flow of FIG. 26, the collection company terminal 11 receives a menu selection input from the collection company user to the menu page for the collection company (FIG. 27) (step S289). In this embodiment, since the menu is only “Oversized garbage collection scheduled”, the collection company terminal 11 transmits a data request for the oversized garbage collection schedule input page to the oversized garbage collection management server 5 (step S291). The collection schedule processing unit 506 receives a data request for the bulky waste collection schedule input page from the collection company terminal 11 (step S293).
[0160]
The collection schedule processing unit 506 reads the calendar data for the current month from the calendar master DB 520, and temporarily stores the data in the calendar work 522 (step S295). Then, the collection schedule processing unit 506 reads, from the collection range master DB 512 (FIG. 2), data related to collection in the current month (a record in which the value of the column 200 of the range start date or the value of the column 202 of the range end date is included in the current month). Is stored in the calendar work 522 in association with the calendar data (step S297).
[0161]
Further, the collection schedule processing unit 506 reads, from the collection reservation master DB 516 (FIG. 4), a record in which the value of the column 404 of the desired collection date is included in the current month and the value is not set in the column 406 of the collection determined date, and the calendar. -Store the data in the calendar work 522 in association with the data (step S299).
[0162]
The collection schedule processing unit 506 uses the data stored in the calendar work 522 and the data stored in the collection item master DB 514 (FIG. 3) to generate data of a bulky waste collection schedule input page, and 11 (step S301). The collection company terminal 11 receives the data of the bulky waste collection schedule input page from the collection schedule processing unit 506 and displays the data on the display device (step S303).
[0163]
FIG. 28 shows an example of the oversized garbage collection schedule input page. The example illustrated in FIG. 28 includes a collection schedule display unit 2800, a collection date designation button 2810, and an end button 2820. The collection schedule display section 2800 shows calendar data for one month (the current month), the number of collections, and (collection) enhanced items. In addition, the period covered by the oversized garbage collection plan is indicated by differences in the display of colors, diagonal lines, etc., and the normal collection date that has already been determined is indicated by an ellipse, and the collection date of enhanced items is indicated by a box. Have been.
[0164]
In addition, in the example of FIG. 28, the subscripts “2” and “1” are shown on the 10th and the 12th, which represent the number of collection applicants who do not limit the collection date. I have. For example, although the desired collection date is 10 days, there are two collection applicants who may set different collection dates. In addition, display items such as the number of times of collection and the date of collection of the enhanced items have the same configuration as the example of the oversized garbage collection reservation page shown in FIG.
[0165]
Then, the collection company terminal 11 receives a click on the date of the calendar data as a selection of the collection date. For example, the selected date can be specified by changing the color of the date. By clicking collection date designation button 2810, a request to set the selected date to the collection date is accepted. The collection date designation button 2810 has a configuration in which a click is not accepted unless a date is selected. However, even if a date is not selected, a click is accepted once and a message prompting the designation of the collection date is displayed. May be displayed.
[0166]
In addition, the collection company terminal 11 clicks on a date already set as a collection date (hereinafter, referred to as an existing collection date) in the calendar data dates, by referring to “collection date designation” and “reservation list” described later. Accepted as a request to move to the selected page
[0167]
That is, on this page, selection of a date other than the existing collection date and one of the click of the collection date designation button 2810, the click of the existing collection date, and the click of the end button 2820 are accepted as a selection input by the collection company user.
[0168]
In the present embodiment, for example, from the state of the page shown in the example of FIG. 28, when the collection company user selects, for example, 10 days of the calendar data and clicks the collection date designation button 2810, the collection is performed. The schedule processing unit 506 sets the 10th as a new collection date and collects the collection dates of the collection reservations indicated by subscripts on the 10th and 12th on the 10th based on a predetermined rule. Configuration. That is, the collection date of the collection reservation for which the collection date has not yet been determined is automatically set.
[0169]
On the other hand, for example, when the collection company user performs a screen operation of dragging a subscript and dropping it on the existing collection date, the collection company terminal 11 displays the collection date of the collection reservation for which the collection date has not yet been determined. A configuration in which the request is received as a setting request may be adopted. That is, the collection date of the collection reservation for which the collection date has not yet been determined may be manually set by the collection company user. Further, the configuration may be such that both automatic setting and manual setting are possible.
[0170]
Returning to the flow of FIG. 26, the collection company terminal 11 receives a selection input from the collection company user on the bulky waste collection schedule input page (FIG. 28), and transmits the selected input data to the bulky waste collection management server 5 (step S305). ). The collection schedule processing unit 506 receives the selection input data from the collection company terminal 11 and temporarily stores it in the storage device (step S307). The processing shifts to a processing of FIG. 29 via terminals P and Q.
[0171]
The collection schedule processing unit 506 determines the request of the collection company user based on which of the existing collection date, the collection date designation button 2810, and the end button 2820 is clicked on the oversized garbage collection schedule input page (FIG. 28). I do. That is, it is determined whether or not the request of the collection company user has been completed (step S311). If it is determined that the request has been completed (step S311: Yes route), the processing is performed via the terminal R in step S285 (FIG. 26). Return to
[0172]
When it is determined that the collection has not been completed (step S311: No route), it is determined whether or not the operation of the collection company user is a click on the existing collection day (step S313). When it is determined that the click is not the existing collection date (step S313: No route), the following steps S315 to S323 are skipped, and the process proceeds to step S325.
[0173]
On the other hand, when it is determined that the click was made on the existing collection date (step S313: Yes route), the collection schedule processing unit 506 includes “designation of collection date” and “list of reservations” including the data of the specified existing collection date. The data of the selected page is generated and transmitted to the collection company terminal 11 (step S315). The collection company terminal 11 receives the data of the “collection date designation” / “reservation list” selection page from the collection schedule processing unit 506 and displays it on the display device (step S317).
[0174]
Although the “collection date designation” / “reservation list” selection page is not shown, for example, the data of the existing collection date specified on the bulky waste collection schedule input page (FIG. 28) and the status of the collection reservation on the existing collection date are shown. Perform a collection date designation process that aggregates the collection dates of collection reservations with undetermined collection dates within the range that includes the option to move to the reservation list page for viewing and the existing collection date Radio button for selecting one of the options.
[0175]
The collection company terminal 11 accepts a selection input from the collection company user on the “collection date designation” / “reservation list” selection page, and transmits the selection input data to the oversized garbage collection management server 5 (step S319). The collection schedule processing unit 506 receives the selection input data from the collection company terminal 11 (step S321).
[0176]
The collection schedule processing unit 506 determines whether the request from the collection company user is a collection date designation process (step S323). If it is determined that the request is not a collection date designation process (step S323: No route), The processing shifts to a processing in FIG. 30 via the terminal S.
[0177]
On the other hand, when it is determined that the request from the collection company user is the collection date designation processing (step S323: Yes route), the collection schedule processing unit 506 searches the collection range master DB 512 (FIG. 2) and sets the range start date. A record having a range including the date specified by the collection company user is read from the value of the column 200 and the value of the range end date column 202, and the specified date is set as the collection date (step S325).
[0178]
That is, in the read record, the value of the column 208 of the collection date 1, the value of the column 210 of the collection date 2, and the value of the column of the collection date n (not shown) are checked in order, and the first empty portion (the value is set). Column) to the specified date. If the specified date is an existing collection date (step S313: via Yes route), the collection date is not set (duplicate registration).
[0179]
Then, the collection schedule processing unit 506 uses the value of the column 200 of the range start date and the value of the column 202 of the range end date in the read record of the collection range master DB 512 (FIG. 2) to collect the collection reservation master DB 516. From FIG. 4, a record in which the desired date (the value of the collection desired date column 404) is within the range and the value of the collection determined date column 406 is not yet set is extracted, and the collection determined date column 406 is extracted. Is set (step S327).
[0180]
That is, among the values of the column 208 of the collection date 1 and the column 210 of the collection date 2 and the value of the column of the collection date n (not shown) of the record of the collection range master DB 512 (FIG. 2) read in step S325. The value closest to the value of the column 404 of the desired collection date in the record of the collection reservation master DB 516 (FIG. 4) extracted in step S327 is registered in the value of the column 406 of the determined collection date in the extracted record. . If there are a plurality of records extracted in step S327, this process is performed for all the extracted records.
[0181]
Note that a simulation process is performed before performing the processes in steps S325 and S327. For example, if no collection reservations are collected for a specified new collection date, a confirmation message is generated and collected. It may be configured to transmit to the trader terminal 11. Further, when there are a plurality of closest values, the date may be set on the day with the smallest number of collections. This is in order to suppress unevenness in the amount of collection.
[0182]
Then, the collection schedule processing unit 506 updates the data stored in the calendar work 522 based on the processing results in steps S325 and S327 (step S329). The process returns to step S301 (FIG. 26) via terminal T. In this manner, the collection date designation processing based on the request from the collection company user is performed.
[0183]
Next, the processing after the terminal S (step S323 (FIG. 29): No route) will be described with reference to FIGS. The collection schedule processing unit 506 searches the collection reservation master DB 516 (FIG. 4) and finds a record in which the value of the column 406 of the determined collection date is equal to the existing collection date specified on the bulky garbage collection schedule input page (FIG. 28). It is read (step S331).
[0184]
The collection schedule processing unit 506 stores the read record data of the collection reservation master DB 516 (FIG. 4), the data stored in the collection item master DB 514 (FIG. 3), and the collection master DB 518 (FIG. 5). The reservation list page data is generated using the stored data and transmitted to the collection company terminal 11 (step S333). The collection company terminal 11 receives the reservation list page data from the collection schedule processing unit 506 and displays it on the display device (step S335).
[0185]
FIG. 31 shows an example of the reservation list page. The example illustrated in FIG. 31 includes a collection date display unit 3100, a collection reservation list display unit 3110, a return button 3120, and an end button 3130. The collection reservation list display section 3110 includes a reception number (No.) column 3111, a name column 3112, an address column 3113, a type column 3114, a delivery address column 3115, an image column 3116, and a notification process. Column 3117 and a scheduled collection time column 3118 are included.
[0186]
The collection date display section 3100 shows the collection date specified on the oversized garbage collection schedule input page (FIG. 28). A list of collection reservations scheduled to be collected on the collection date is shown in the collection reservation list display section 3110. In each column of the collection reservation list display unit 3110, data corresponding to each column of the record (hereinafter, collection reservation record) read in step S331 (FIG. 30) is shown.
[0187]
In the column 3111 of the reception number (No.), the value of the column 400 of the reception number (No.) of the collection reservation record is shown in a page link format. The type column 3114 shows the product name (see the collection item master DB 514 (FIG. 3)) corresponding to the value of the collection item column 412 of the collection reservation record. Further, a delivery destination address column 3115 indicates a transfer destination address (see the collection master DB 518 (FIG. 5)) corresponding to the value of the transfer destination column 416 of the collection reservation record.
[0188]
When the file name or the like of the image data of the oversized garbage (collected product) is registered in the column 428 of the image file of the collection reservation record, the image column 3116 includes an image button. The column 3117 of the notification process indicates “done” when the value of the column 430 of the notification of the collection reservation record is “1”.
[0189]
Returning to the flow of FIG. 30, the collection company terminal 11 accepts the selection input from the collection company user on the reservation list page (FIG. 31), and transmits the selection input data to the oversized garbage collection management server 5 (step S337). The collection schedule processing unit 506 receives the selection input data from the collection company terminal 11 and temporarily stores it in the storage device (step S339).
[0190]
Then, in the reservation list page (FIG. 31), the collection schedule processing unit 506 includes the end button 3130, the return button 3120, the image button included in the image column 3116, and the reception number (No.) column 3111. The request of the collection company user is determined based on which page link is clicked. That is, it is determined whether or not the request of the collection company user has been completed (step S341). If it is determined that the request has been completed (step S341: Yes route), the processing is performed via the terminal R in step S285 (FIG. 26). Return to
[0191]
When it is determined that the processing has not been completed (step S341: No route), it is determined whether the request of the collection company user is “return” (step S343).
If it is determined to be “return” (step S343: Yes route), the processing returns to the processing of step S301 (FIG. 26) via the terminal T.
[0192]
On the other hand, when it is determined that it is not “return” (step S343: No route), it is determined whether or not the request of the collection company user is to browse the image (step S345). If it is determined that the image has been viewed (step S345: Yes route), the collection schedule processing unit 506 includes the image data of the collection item designated by clicking the image button on the reservation list page (FIG. 31). The data of the image page is generated and transmitted to the collection company terminal 11 (step S347). The collection company terminal 11 receives the image page data from the collection schedule processing unit 506 and displays it on the display device (step S349).
[0193]
On the other hand, when it is determined that the image is not browsed (step S345: No route), the processing shifts to the processing in FIG. 32 via the terminals U and V.
[0194]
The collection schedule processing unit 506 searches the collection reservation master DB 516 (FIG. 4) based on the page link (reception number) designated by clicking on the reservation list page (FIG. 31), and a column 430 of the notice of the extracted record is retrieved. Is specified (step S351).
[0195]
Then, the collection schedule processing unit 506 determines whether the value specified in step S351 is “1” (step S353). If it is determined that the value is “1” (step S353: Yes route), the collection schedule processing unit 506 generates data of the collection reservation confirmation page using the data of the record extracted in step S351, and 11 (step S355). The collection company terminal 11 receives the data of the collection reservation confirmation page from the collection schedule processing unit 506 and displays the data on the display device (step S357).
[0196]
The collection reservation confirmation page, which is not shown, shows, for example, the same data as the data shown on the collection reservation person notification page described later. However, the input items on the collection reservation person notice page are shown as display items on the collection reservation confirmation page, and the buttons include only a return button.
[0197]
On the other hand, when it is determined that the number is not “1” (step S353: No route), the collection schedule processing unit 506 generates data of the collection reservation person notice page using the data of the record extracted in step S351, The data is transmitted to the collection company terminal 11 (step S359). The collection company terminal 11 receives the data of the collection reservation person notification page from the collection schedule processing unit 506, and displays it on the display device (step S361).
[0198]
FIG. 33 shows an example of the collection reservation person notification page. In the example shown in FIG. 33, a reception number (No.) display unit 3300, a collection date display unit 3310, a scheduled collection time input unit 3320, a fee input unit 3330, a transmission date display unit 3340, a transmission button 3350, a return button 3360, An end button 3370 is included.
[0199]
The scheduled collection time input unit 3320 receives an input of a collection time in the collection from a collection trader user. The fee input section 3330 shows a fee for the collection (refer to the collection reservation master DB 516 (FIG. 4)), and can accept a change in the fee by the collection company user.
[0200]
Further, the transmission date display unit 3340 shows, for example, the day before the collection date, and indicates that the collection reservation is notified to the collection reservation person on this day. In the present embodiment, since the notification is performed by mail, the value of the column 426 of the mail address (e-mail) of the collection reservation master DB 516 (FIG. 4) is used, for example, the day before the collection date. A setting is made to send the contents to the applicant for collection by e-mail.
[0201]
Returning to the flow of FIG. 32, the collection company terminal 11 receives a selection input from the collection company user on the collection reservation person notification page (FIG. 33), and transmits the selection input data to the oversized garbage collection management server 5 (step S363). . The collection schedule processing unit 506 receives the selection input data from the collection company terminal 11 and temporarily stores the data in the storage device (step S365).
[0202]
The collection schedule processing unit 506 determines the request of the collection company user based on which of the transmission button 3350, the return button 3360, and the end button 3370 is clicked on the collection reservation person notification page (FIG. 33). I do. That is, it is determined whether or not the request of the collection company user has been completed (step S367). If it is determined that the request has been completed (step S367: Yes route), the processing is performed via the terminal R in step S285 (FIG. 26). Return to
[0203]
When it is determined that the processing has not been completed (step S367: No route), it is determined whether the request of the collection company user is “return” (step S369).
If it is determined to be "return" (step S369: Yes route), the processing returns to the processing in FIG.
[0204]
When it is determined that it is not “return” (step S369: No route), the collection schedule processing unit 506 updates the record of the collection reservation master DB 516 (FIG. 4) (step S371). That is, the value of the collection time column 410 of the record of the collection reservation master DB 516 (FIG. 4) and the fee of the fee extracted in step S351 based on the selection input data from the collection trader user on the collection reservation user notification page (FIG. 33). The value in column 418 is registered. Further, the value of the notification column 430 of the record is updated to “1”.
[0205]
The collection schedule processing unit 506 generates a “notification to collection reservation person” mail using the updated record data of the collection reservation master DB 516 (FIG. 4), and makes a transmission reservation to a mail server (not shown). Is set (step S373).
[0206]
FIG. 34 shows an example of a “notification to collection reservation person” mail. The example shown in FIG. 34 includes a reception number (No.) display section 3400, a collection date display section 3410, a scheduled collection time display section 3420, a fee display section 3430, and a reception number (No.) enlargement display section 3450. ing. By sending an e-mail having such contents to a collection applicant on the day before the collection date, for example, the receipt number and the handling fee are notified and the forgetting of oversized garbage is prevented.
[0207]
Returning to the flow of FIG. 32, the processing returns to the processing of FIG. In this way, the collection schedule setting processing of the bulky waste is performed. In addition, a notice of confirmation is given to the applicant for collection.
[0208]
Although the embodiment of the present invention has been described above, the present invention is not limited to this. For example, the system configuration shown in FIG. 1 is an example, and any other configuration may be used as long as the above-described embodiment pattern can be realized. Further, there is a case where a program module is not created as shown in the functional block diagram of the oversized garbage collection management server 5 shown in FIG.
[0209]
Further, for example, the table configuration shown in FIGS. 2 to 5 is an example, and another configuration may be adopted as long as the same data is stored. For example, normalization may be performed, or items may be added or deleted as necessary. The screen configurations shown in FIGS. 7, 8, 11, 13, 15, 15, 17, 23, 25, 27, 28, 31, 33, and 34 are examples. The same contents can be expressed in another mode.
[0210]
(Appendix 1)
When receiving collection reservation data related to collection reservation within a predetermined period from a terminal of a bulk garbage collection applicant, storing the collection reservation data in a collection reservation data storage unit;
When it is detected that the number of collection days set by the collection reservation data including the data specifying the specific collection date within the predetermined period has reached a preset number of days, a predetermined rule is applied. Registering any of the set collection dates within the predetermined period based on the collection reservation data related to the collection reservation within the predetermined period in the collection reservation data storage unit.
A program for causing a computer to execute.
[0211]
(Appendix 2)
As a collection fee corresponding to collection reservation data including data permitting a collection date different from the desired collection date to be set, the collection fee corresponds to collection reservation data including data designating a specific collection date within the predetermined period. Steps to set an amount lower than the collection fee
According to claim 1, further causing a computer to execute the program.
[0212]
(Appendix 3)
Transmitting collected item data included in the collection reservation data relating to the collection reservation stored in the collection reservation data storage unit to a terminal operated by the collection applicant according to a request of the collection applicant;
3. The program according to claim 1 or 2, further causing a computer to execute the program.
[0213]
(Appendix 4)
A collection fee corresponding to the collection reservation data stored in the collection reservation data storage unit and including the specific collection product data, when receiving data related to collection of a specific collection item from the terminal of the collection applicant. Setting a fee related to the collection of the specific collected product based on the above, and storing data related to the collection of the specific collected product in the collection data storage unit, including the data of the fee.
3. The program according to claim 3, further causing a computer to execute the program.
[0214]
(Appendix 5)
When receiving data relating to the collection of a specific collection item from the terminal of the collection applicant, setting a predetermined fee for the collection of the specific collection item, including the data of the fee, and collecting the specific collection item. For storing data relating to the receipt data storage unit
3. The program according to claim 3, further causing a computer to execute the program.
[0215]
(Appendix 6)
Resetting the collection fee corresponding to the collection reservation data stored in the collection reservation data storage unit and including the data of the specific collection item based on a predetermined rule
6. The program according to Supplementary Note 4 or 5, further causing the computer to execute:
[0216]
(Appendix 7)
A collection reservation in which the number of days of the set collection day within the predetermined period has reached the predetermined number of days but the collection day within the predetermined period is designated and the data of the predetermined collection enhanced item is specified. When the data is received, the designated collection date is associated with the collection reservation data including the data of the collection enhancement item, and the collection reservation data is stored, unless the number of collection days for the collection enhancement item is exceeded. Registration step to register in department
According to claim 1, further causing a computer to execute the program.
[0219]
(Appendix 8)
When the collection date within the predetermined period is designated and the collection reservation data including the data of the predetermined collection enhancement item is received, the designated collection date is specified except for the case of exceeding the limit collection days for the collection enhancement item. A registration step of registering the collection date in the collection reservation data storage unit in association with the collection reservation data including the data of the collection enhanced item.
According to claim 1, further causing a computer to execute the program.
[0218]
(Appendix 9)
When the number of days of the set collection day within the predetermined period has reached the preset number of days, and collection reservation data including data permitting that a collection day different from the desired collection day is set is received. Registering any one of the set collection dates within the predetermined period in the collection reservation data storage unit in association with the collection reservation data based on the predetermined rule.
According to claim 1, further causing a computer to execute the program.
[0219]
(Appendix 10)
The program according to any one of supplementary notes 1 to 9, wherein the preset number of days is a limited number of collection days within the predetermined period.
[0220]
(Appendix 11)
Wherein the predetermined rule associates the set collection date within the predetermined period closest to the desired collection date included in the collection reservation data regarding the collection reservation within the predetermined period with the collection reservation data. 2. The program according to claim 1, wherein
[0221]
(Appendix 12)
4. The program according to claim 3, wherein the collection reservation data including the data of the collection item to be transmitted to the terminal of the collection applicant is collection reservation data associated with a specific collection date.
[0222]
(Appendix 13)
Transmitting notification data including at least the fee data to the terminal of the withdrawal applicant
6. The program according to Supplementary Note 4 or 5, further causing the computer to execute:
[0223]
(Appendix 14)
A step of storing, in the collection plan data storage unit, the collection plan data including, from the terminal of the administrative institution user, the collection plan data including the data regarding the collection period of the oversized garbage and the data regarding the limited collection days in the collection period.
According to any one of supplementary notes 1 to 13, further causing a computer to execute the program.
[0224]
(Appendix 15)
When receiving the collection plan data including the data related to the collection enhanced items in the predetermined period from the terminal of the administrative institution user, the computer further executes the step of storing the collection plan data in the collection plan data storage unit,
The registering step is based on the collection plan data stored in the collection plan data storage unit, and confirms whether or not the collection item included in the received collection reservation data is a collection enhanced item in the predetermined period. 9. The program according to Supplementary Note 7 or 8, wherein the program includes:
[0225]
(Appendix 16)
Transmitting, to the terminal operated by the collection company, data of the desired collection date stored in the collection reservation data storage unit and included in the collection reservation data for which the collection date is not set, according to the request of the collection company; ,
When receiving data for designating a collection date from the terminal of the collection company, the designated collection date corresponds to the collection reservation data stored in the collection reservation data storage unit and for which the collection date has not been set. And registering the information in the collection reservation data storage unit.
The program according to any one of 1 to 15, further causing a computer to execute the program.
[0226]
(Appendix 17)
If you receive data from the collection company's terminal that specifies the expected collection time for a specific collection reservation,
Registering the designated scheduled collection time with the collection reservation data in the collection reservation data storage unit;
Transmitting at least notification data including the scheduled collection time data to the collection applicant who has made the specific collection reservation; and
The program according to any one of 1 to 16, further causing a computer to execute the program.
[0227]
(Appendix 18)
A step of storing collection reservation data in a collection reservation data storage unit when receiving collection reservation data from a bulk garbage collection applicant;
When it is detected that the number of days of the collection date set by the collection reservation data including the data specifying the collection date has reached a preset number of days, the predetermined collection date is set based on a predetermined rule. Registering any one of them in the collection reservation data storage unit in association with the collection reservation data;
A program for causing a computer to execute.
[0228]
(Appendix 19)
When receiving collection reservation data related to collection reservation within a predetermined period from a terminal of a bulk garbage collection applicant, storing the collection reservation data in a collection reservation data storage unit;
When it is detected that the number of collection days set by the collection reservation data including the data specifying the specific collection date within the predetermined period has reached the preset number of days, the predetermined rule is set. Registering any one of the set collection dates within the predetermined period based on the collection reservation data related to the collection reservation within the predetermined period in the collection reservation data storage unit.
An information processing method for bulky waste collection executed by a computer including a computer.
[0229]
(Appendix 20)
Means for storing, in a collection reservation data storage unit, collection collection data relating to a collection reservation within a predetermined period from a terminal of a bulky garbage collection applicant;
When it is detected that the number of collection days set by the collection reservation data including the data specifying the specific collection date within the predetermined period has reached the preset number of days, the predetermined rule is set. Means for registering any one of the set collection dates within the predetermined period in the collection reservation data storage unit in association with collection reservation data relating to collection reservation within the predetermined period.
Information processing equipment for oversized garbage collection, including
[0230]
【The invention's effect】
As described above, according to the present invention, an appropriate collection date can be set in creating a collection plan for oversized refuse. In addition, recycling can be promoted in the collection of bulky waste.
[Brief description of the drawings]
FIG. 1 is a schematic diagram of a system according to an embodiment of the present invention.
FIG. 2 is a diagram showing an example of a table configuration of a collection range master DB and stored data.
FIG. 3 is a diagram illustrating an example of a table configuration of a collection item master DB and stored data.
FIG. 4 is a diagram illustrating an example of a table configuration of a collection reservation master DB and stored data.
FIG. 5 is a diagram showing an example of a table configuration of a collection master DB and stored data.
FIG. 6 is a diagram showing a processing flow (1) according to an embodiment of the present invention.
FIG. 7 is a diagram showing an example of a menu page for an administrative organization.
FIG. 8 is a diagram showing an example of a bulky waste collection planning page.
FIG. 9 is a diagram showing a processing flow (No. 2) in the embodiment of the present invention.
FIG. 10 is a diagram showing a processing flow (3) in the embodiment of the present invention.
FIG. 11 is a diagram showing an example of a menu page for citizens.
FIG. 12 is a diagram showing a processing flow (part 4) in the embodiment of the present invention.
FIG. 13 is a diagram illustrating an example of an oversized garbage collection reservation page.
FIG. 14 is a diagram showing a processing flow (part 5) in the embodiment of the present invention.
FIG. 15 is a diagram showing an example of a reservation details input page.
FIG. 16 is a diagram showing a processing flow (part 6) in the embodiment of the present invention.
FIG. 17 is a diagram illustrating an example of a transfer confirmation page.
FIG. 18 is a diagram showing a processing flow (No. 7) in the embodiment of the present invention.
FIG. 19 is a diagram showing a processing flow (No. 8) in the embodiment of the present invention.
FIG. 20 is a diagram showing a processing flow (No. 9) in the embodiment of the present invention.
FIG. 21 is a diagram showing a processing flow (No. 10) in the embodiment of the present invention.
FIG. 22 is a diagram showing a processing flow (11) in the embodiment of the present invention.
FIG. 23 is a diagram showing an example of a reservation list page.
FIG. 24 is a diagram showing a process flow (12) in the embodiment of the present invention.
FIG. 25 is a diagram illustrating an example of a collection confirmation page.
FIG. 26 is a diagram showing a process flow (13) in the embodiment of the present invention.
FIG. 27 is a diagram showing an example of a menu page for a collection company.
FIG. 28 is a diagram showing an example of a bulky waste collection schedule input page.
FIG. 29 is a diagram showing a processing flow (part 14) in the embodiment of the present invention.
FIG. 30 is a diagram showing a processing flow (15) in the embodiment of the present invention.
FIG. 31 is a diagram showing an example of a reservation list page.
FIG. 32 is a diagram showing a processing flow (16) in the embodiment of the present invention.
FIG. 33 is a diagram illustrating an example of a collection reservation person notification page.
FIG. 34 is a diagram showing an example of a “notification to collection reservation person” mail.
[Explanation of symbols]
1 network 3 administrative institution terminal
5 Oversized garbage collection management server 7 Collection applicant terminal
9 Receiving applicant terminal 11 Collection agent terminal
500 Collection plan processing unit 502 Collection reservation processing unit
504 Pick-up reservation processing unit 506 Collection scheduled processing unit
512 Collection range master DB 514 Collection item master DB
516 Collection reservation master DB 518 Collection master DB
520 Calendar Master DB 522 Calendar Work
524 Map DB

Claims (5)

When receiving collection reservation data related to collection reservation within a predetermined period from a terminal of a bulk garbage collection applicant, storing the collection reservation data in a collection reservation data storage unit;
When it is detected that the number of collection days set by the collection reservation data including the data specifying the specific collection date within the predetermined period has reached the preset number of days, the predetermined rule is set. Registering any one of the set collection dates within the predetermined period in the collection reservation data storage unit in association with the collection reservation data related to the collection reservation within the predetermined period. Program. The collection fee corresponding to the collection reservation data including the data permitting the collection date different from the desired collection date to be set corresponds to the collection reservation data including the data specifying the specific collection date within the predetermined period. The program according to claim 1, wherein the program further causes the computer to execute a step of setting an amount lower than the collection fee. Transmitting the collected item data contained in the collection reservation data relating to the collection reservation stored in the collection reservation data storage unit to a terminal operated by the collection applicant in accordance with a request of the collection applicant. The program according to claim 1, wherein the program is executed by a computer. A collection fee corresponding to the collection reservation data stored in the collection reservation data storage unit and including the data of the specific collection product when receiving data relating to collection of the specific collection product from the terminal of the collection applicant. 4. The method according to claim 3, further comprising the steps of: setting a fee relating to the collection of the specific collected item based on the information; and causing the computer to further execute a step of storing data relating to the collection of the specific collected item in the collection data storage unit, including the data of the fee. Program. If the collection date within the predetermined period is designated and the collection reservation data including the data of the predetermined collection enhancement item is received, the designated collection date is not applied unless the collection collection date for the collection enhancement item is exceeded. The program according to claim 1, further comprising the step of causing the computer to execute the step of registering the collection date in the collection reservation data storage unit in association with the collection reservation data including the data of the collection enhancement item.

Images